I don't have the numbers, but I believe a lot of companies still rely on
an older version of Maven.
Since the 2.1.x and 2.2.0 are broken releases of Maven, everybody should
be encouraged to use at least 2.2.1
That can only be forced with a little help from the plugins by requiring
at least this version.
About the annotations: that's completely isolated from the Maven version.
The maven-plugin-plugin either translates the doclettags or the
annotations to a plexus configuration file.
Robert
On Fri, 27 Sep 2013 14:17:54 +0200, Werner Guttmann <[email protected]>
wrote:
Hi Robert,
On 01.09.2013 16:33, Robert Scholte wrote:
The tag wasn't removed, which caused a new invalid tag:
http://svn.codehaus.org/mojo/tags/castor-maven-plugin-2.5/castor-maven-plugin/
I guess Brett is referring to
<prerequisites>
<maven>3.0</maven>
</prerequisites>
The funny thing is, that the dependencyManagement refers to 2.0
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-project</artifactId>
<version>2.0</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-plugin-api</artifactId>
<version>2.0</version>
</dependency>
That's odd...
Now that I read this, yes, it is odd. My rational was to switch to using
annotations in the plugin implementation, and I *assumed* that for this
to work, I will need Maven 3 at compile time.
As such, I overlooked the run-time implication. Thanks for pointing this
out. I suppose I could still allow usage of Maven 2.2.x, but I wouldn't
mind pushing this to Maven 3.x or above. How are other plugins dealing
with this in general ?
Regards
Werner
Be aware that prerequisite has 2 meanings for plugins:
- To *build* this plugin you require at least this version
- To *use* this plugin you require at least this version
The latter is the most important one.
The first is already set to 2.2.1 by the parent to ensure a stable
release.
Since <prerequisites> cannot be inherited, it is done by an enforcer
rule.
In general keep this version as low as possible, or help/force the Maven
community to move forward.
I should at least require 2.0.6 due to a plexus-utils issue.
Robert
On Sun, 01 Sep 2013 15:51:19 +0200, Brett Okken
<[email protected]> wrote:
Should introducing a dependency on a newer major version of maven lead
to a
major version bump (ie. 3.0)?
Brett
On Sep 1, 2013 8:48 AM, "Werner Guttmann" <[email protected]> wrote:
Hi,
I'd like to release version 2.5 of the castor-maven-plugin.
The Castor plugin is a Maven plugin that provides the functionality of
Castor XML's code generator for generating Java beans and associated
descriptor classes (required for marshalling to and unmarshalling
from XML
documents) from XML Schema files.
This release fixes broken links in the plugin's documentation and
introduces Maven 3 as a new requirement.
In addition, we solved 3 issues:
http://jira.codehaus.org/**secure/ReleaseNote.jspa?**
projectId=11191&version=17220<http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11191&version=17220>
Staging Repositories:
General:
https://nexus.codehaus.org/**content/groups/staging/<https://nexus.codehaus.org/content/groups/staging/>
(Staging) Site:
http://mojo.codehaus.org/**castor-maven-plugin/<http://mojo.codehaus.org/castor-maven-plugin/>
SCM Tag:
https://svn.codehaus.org/mojo/**tags/castor-maven-plugin-5.1<https://svn.codehaus.org/mojo/tags/castor-maven-plugin-5.1>
Additonal Information:
[ ] +1
[ ] +0
[ ] -1
The vote is open for 72 hours and will succeed by lazy consensus.
Cheers
Werner Guttmann
------------------------------**------------------------------**---------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/**manage_email<http://xircles.codehaus.org/manage_email>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
