I think that if your SCM supports the options and your MRM supports staging
then you can get the workflow you want by basically making every build a
release build e.g.
mvn -DreleaseVersion=1.0.0.${BUILD_NUMBER} \
-DdevelopmentVersion=1.0.0.0-SNAPSHOT \
-DsuppressCommitBeforeTag=true \
The deploy and install plugins act on attached artifacts, which I believe
generally requires the package phase. For a given packaging type, there should
be a plugin goal which is by default bound to the package phase to creates and
attaches the artifacts for the project. So for a standard
Hello everyone,
found a solution by using the MojoRule class in my test:
@Rule
public MojoRule mojoRule = new MojoRule(this);
My test is still a sub-class of AbstractMojoTestCase.
The execution of my plugin within the test works like this:
this.mojoRule.executeMojo(basedir, "plugin-name");
Hello everyone,
I'm currently writing a Maven plugin and I want to have some JUnit tests
for it.
The artifact maven-plugin-testing-harness offers an environment through
its AbstractMojoTestCase class.
After reading half of the Internet I also got it working.
But now I'm stuck as it seems to
