Liquibase version upgrade is not populating artifacts - jenkins

I am upgrading liquibase from 4.3 to 4.5 and the build artifact updateSql and rollbackSql files are not populating in jenkins.
According to this page : https://github.com/liquibase/liquibase-gradle-plugin i even added picocli dependency and changed the output file command from -PcurrentOutputFile to -PliquibaseOutputFile

Related

How can jenkins build a IntelliJ project (not maven/gradle)?

I prefer the IntelliJ project format for a Kotlin/JVM project. I.e. the dependencies and other project information is kept in files within the .idea directory:
Using IntelliJ IDEA I run tests and create an uber-JAR artifact for deployment.
Questions:
How can I build and test a IntelliJ Kotlin/JVM project on Jenkins? Is there a plug-in available that can handle the IntelliJ project format?
Or do I have to duplicate the project's information in a gradle file?

How to change JRE Libraries on Eclipse Maven Project?

is anyone knows how to change the jre libraries on java dynamic web project(I am using Eclipse and Maven)? The case is this, when I first created the project on Eclipse Oxygen package M5 the default jre was 1.6, I changed the Java Build Path(libraries) into 1.7/1.8, however upon updating the project it always returns to 1.6 and there is a red mark on the project folder. I already tried deleting the project and import it as Existing Maven Project and then update and clean but still nothing happens. This happens whenever I am creating a project without XML based configuration. I installed JDK 1.8.0 update 111, 121, and 131 and Apache Tomcat V7(XAMPP). On my brother's laptop everything works fine.
By the way, I also tried to replace .m2 folder of my laptop by copying .m2 folder from my brother's laptop.
Any help is much appreciated.
I assume you are using m2e, the Maven integration for Eclipse, which offers the import as Existing Maven Project option. m2e takes the version for the JRE System Library container from the configuration of the maven-compiler-plugin; this ensures that Eclipse and mvn behave consistently. Try changing the <source> and <target> configuration options of the maven-compiler-plugin, maybe followed by a Maven > Update Project to make sure m2e has sync’ed the changes to the pom.xml with the Eclipse buildpath.

After import of an existing project, the gradle version is less then when creating a Gradle project

When I create a new Gradle project, the Gradle version is 3.3. But when I import an existing Gradle project, the Gradle version is 2.4.11. How are the version determined, especially the last one, because as far as I can see, there is no Gradle version information in the existing Gradle project.
I don't know am I understand your issue correctly or not. But as I understood:
The version of gradle is determined in your build.gradle file.
There is a line there like below:
classpath 'com.android.tools.build:gradle: 2.2.2'
which 2.2.2 is the version.
the highest stable version till now is 2.2.3 (which it is not suitable for me) .
Note that versions above 2.2 need jdk 8 (not work with jdk 7)
I found out that you have to look at the file gradle/wrapper/gradle-wrapper.properties. The last line of this file gives the Gradle version:
distributionUrl=https\://services.gradle.org/distributions/gradle-3.3-bin.zip
Before importing an existing Gradle project, maybe you want to edit this line.

Automate version in .install4j file based on POM version

I am using Maven to automate build process of Install4j.
For every release product, POM version is updated. I want when pom version is updated Install4j version should be updated (under General Setting-> ApplicationInfo->Version).
How can i automate version in install4j file. So that version should always remain latest for my product installer.
You can set the release parameter for the install4j compile target to set the version from the maven plugin. See
http://sonatype.github.io/install4j-support/install4j-maven-plugin/compile-mojo.html
for more information.

build Grails 3 war with specific java compiler version

I am using IDEA 15. I have a grails 3 project setup. The app server I need to deploy to has Java Version 7. My local JDK is Java 8. I have set some properties in my build.gradle to use the target version 1.7.
apply plugin: 'java'
compileJava {
targetCompatibility = '1.7'
}
When I rebuild my project, it generates class files for 1.7, but when I run a maven war build from the IDEA menu, the classes are rebuilt and end up being Java 8 versions. I have set Java version in my project to 1.7 as well, but this did not help. How can I get to where I am producing a war file from my grails app that contains 1.7 versioned class files?
Thanks!
What are you using to build war file? "grails war" or "gradle war". Try to use gradle.

Resources