Hi Lennart,
2. One alternative is to use release:prepare-with-pom instead of
release:prepare in the process of releasing a plugin. This will generate a
release-pom.xml file, which will be included into the final artifact and also
checked into the tag. The release POM is a fully interpolated pr
Good to hear some opinions from you all. Time to throw some of my own into
the mix.
1. Yes, I recommend that PlantUML be integrated for use to improve the
documentation in all Codehaus and Apache plugins (and therefore included in
their respective parent POMs). Why?
In my experience,
Op Tue, 10 Feb 2015 14:26:57 +0100 schreef Anders Hammar
:
I would recommend that we migrate to the following requirement for all
our
plugins:
1. Minimum Maven version 3.0.4 (i.e. drop support for Maven 2.x)
As discussed (and concluded) somewhere else, we should go with a Maven
3.0
>
> I would recommend that we migrate to the following requirement for all our
> plugins:
>
>1. Minimum Maven version 3.0.4 (i.e. drop support for Maven 2.x)
>
> As discussed (and concluded) somewhere else, we should go with a Maven 3.0
minimum requirement. Unless there is a good technical reas
Hello all,
I have just changed the IT structure for the Jaxb2-Maven-Plugin in Bamboo,
in preparation for the release of version 2.0 which is a major plugin
upgrade. The change on bamboo reflects a change in requirements for the
plugin, and I believe we should approach this in a similar manner for
