private fields about build-helper-maven-plugin HOT 4 CLOSED

From what kind of Java API ? And why? The plugins use the maven-plugin-api and the attributes are injected ?

from build-helper-maven-plugin.

I'm writing a Jenkins plugin for work to release a set projects. Part of the release process is to remove SNAPSHOT & increment to the next version. I could write this myself but I'd rather reuse your functionality.

I could make an external process call but that gets a bit messy.

I'm current using
FieldUtils.writeField(this, "project", project.getMvnProject(), true); FieldUtils.writeField(this, "versionString", project.getMvnProject().getVersion(), true);
but that's not maintainable really.

from build-helper-maven-plugin.

You know things like this:

mvn build-helper:parse-version versions:set \
     -DnewVersion=\${parsedVersion.nextMajorVersion}.0.0 \
     versions:commit

which can be done in a pipeline very easy? Another option would be to use maven-release-plugin ?

Furthermore if you have a dependency on the build-helper-maven-plugin you would get a large number of dependencies (transitively) which you don't need nor you like to have them in a Jenkins plugin...

Another hint: If you like to reuse code you can use the DefaultVersioning class which is really doing the parsing of the versions...The code in the plugin looks like this:

        DefaultVersioning artifactVersion = new DefaultVersioning( version );

By using artifactVersion you can now access the major, minor and patch version via:

int major = artifactVersion.getMajor();
int minor = artifactVersion.getMinor();
...

And you don't need to access ParseVersionMojo which will not work in the environment of a Jenkins plugin cause there many things which are injected by Maven which will not working in Jenkins plugins...

from build-helper-maven-plugin.

Well I do have it working in Jenkins :) Doesn't matter in the end as I need to walk the project tree anyways and this won't help, using the code I had before.

from build-helper-maven-plugin.