[
http://jira.codehaus.org/browse/MNG-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Gyongyi updated MNG-4760:
-------------------------------
Attachment: MNG-4760-maven-model-builder.patch
MNG-4760-maven-model.patch
maven-model.patch: This patch adds the "mavenVersion" field to the
src/main/mdo/maven.mdo file.
maven-model-builder.patch: This patch adds a class and its test to the project
so that maven version can be checked when activating a profile.
I added the maven-artifact dependency to the maven-model-builder pom because I
used the VersionRange class to handle version numbers.
After applying the patches, the mavenVersion tag can be used with version
ranges and exact versions to activate a profile by maven version.
Regards,
Gabor Gyongyi
> Way to activate profile based on Maven version
> ----------------------------------------------
>
> Key: MNG-4760
> URL: http://jira.codehaus.org/browse/MNG-4760
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Profiles
> Affects Versions: 3.0-beta-2
> Environment: n/a
> Reporter: Anders Hammar
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: MNG-4760-maven-model-builder.patch,
> MNG-4760-maven-model.patch
>
>
> A profile activation that checks the version of Maven being used would be
> good. For example, the site plugin requires a different version when Maven 3
> is used. Currently, this is done through a profile that activates based on
> teh fact that the basedir expression is only recognized by Maven 3.x, which
> is IMO a not-so-pretty solution. (See
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin#Maven3.xandsiteplugin-Usingmavensiteplugin2.xwithMaven2.xandmavensiteplugin3.xwithMaven3.x)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
