[jira] Commented: (MASSEMBLY-528) FileSet does not support filtering (again)
[ http://jira.codehaus.org/browse/MASSEMBLY-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=244552#action_244552 ] Matthieu Scholler commented on MASSEMBLY-528: - I confirm, same behaviour here, filtering in a fileset is broken for 2.2 (using some other beta instead). > FileSet does not support filtering (again) > -- > > Key: MASSEMBLY-528 > URL: http://jira.codehaus.org/browse/MASSEMBLY-528 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Maik Richey >Priority: Critical > > After switching to version 2.2 of the Assembly Plugin filtering for FileSets > does not work again as in versions prior to 2.2-beta-3. > Can anybody confirm this issue? -- 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
[jira] Created: (MNG-4918) MavenProject#clone() doubles active profiles
MavenProject#clone() doubles active profiles Key: MNG-4918 URL: http://jira.codehaus.org/browse/MNG-4918 Project: Maven 2 & 3 Issue Type: Bug Affects Versions: 3.0, 3.0.1 Environment: all Reporter: Sebastian Annies Attachments: test.patch The error occured in our Project with more than 60 submodules and aggregating JavaDoc. Due to the forking of the LifeCycle many clones of the MavenProject object seem to be performed. Since MavenProject#clone doubles the entries in the list of active profiles we start with one active profile and after a few dozen clones the list of active profiles exceeds 10.000.000 elements. This will than kill the VM by OOME. mavenProject.getActiveProfiles().size() == 1 mavenProject.clone().getActiveProfiles().size() == 2 mavenProject.clone().clone().getActiveProfiles().size() == 4 and so on -- 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
[jira] Updated: (MNG-4918) MavenProject#clone() doubles active profiles
[ http://jira.codehaus.org/browse/MNG-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Annies updated MNG-4918: -- Attachment: fix.patch A fix for the clone problem > MavenProject#clone() doubles active profiles > > > Key: MNG-4918 > URL: http://jira.codehaus.org/browse/MNG-4918 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0, 3.0.1 > Environment: all >Reporter: Sebastian Annies > Attachments: fix.patch, test.patch > > > The error occured in our Project with more than 60 submodules and aggregating > JavaDoc. Due to the forking of the LifeCycle many clones of the MavenProject > object seem to be performed. Since MavenProject#clone doubles the entries in > the list of active profiles we start with one active profile and after a few > dozen clones the list of active profiles exceeds 10.000.000 elements. This > will than kill the VM by OOME. > mavenProject.getActiveProfiles().size() == 1 > mavenProject.clone().getActiveProfiles().size() == 2 > mavenProject.clone().clone().getActiveProfiles().size() == 4 > and so on -- 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
[jira] Updated: (MNG-4917) Profile not active even though it has activeByDefault set to true
[ http://jira.codehaus.org/browse/MNG-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-4917: --- Attachment: pom.xml Standalone demo POM. > Profile not active even though it has activeByDefault set to true > - > > Key: MNG-4917 > URL: http://jira.codehaus.org/browse/MNG-4917 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Profiles >Affects Versions: 3.0 >Reporter: Benson Margulies > Attachments: pom.xml > > > I've got a parent pom with a profile with > true. > You can retrieve it for yourself via git clone > git://git.apache.org/webservices-xmlschema.git. > The problem is the sourcecheck profile in the parent pom. > running mvn -Psourcecheck works as expected, but running without the -P fails > to activate the profile. > the help plugin, I think, has separate problems in this area, or perhaps it's > not supposed to look at -P? -- 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
[jira] Closed: (MNG-4917) Profile not active even though it has activeByDefault set to true
[
http://jira.codehaus.org/browse/MNG-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4917.
--
Resolution: Not A Bug
Assignee: Benjamin Bentmann
{noformat}
>mvn help:active-profiles -N
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building XmlSchema 2.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-help-plugin:2.1.1:active-profiles (default-cli) @ xmlschema ---
[INFO]
Active Profiles for Project
'org.apache.ws.xmlschema:xmlschema:pom:2.0-SNAPSHOT':
The following profiles are active:
- maven-3 (source: pom)
{noformat}
And from [Introduction to Build
Profiles|http://maven.apache.org/guides/introduction/introduction-to-profiles.html]:
bq. This profile will automatically be active for all builds unless another
profile in the same pom is activated using one of the previously described
methods. All profiles that are active by default are automatically deactivated
when a profile in the pom is activated on the command line or through its
activation config.
In short, the profile "maven-3" disables "sourcecheck".
> Profile not active even though it has activeByDefault set to true
> -
>
> Key: MNG-4917
> URL: http://jira.codehaus.org/browse/MNG-4917
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 3.0
>Reporter: Benson Margulies
>Assignee: Benjamin Bentmann
> Attachments: pom.xml
>
>
> I've got a parent pom with a profile with
> true.
> You can retrieve it for yourself via git clone
> git://git.apache.org/webservices-xmlschema.git.
> The problem is the sourcecheck profile in the parent pom.
> running mvn -Psourcecheck works as expected, but running without the -P fails
> to activate the profile.
> the help plugin, I think, has separate problems in this area, or perhaps it's
> not supposed to look at -P?
--
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
[jira] Closed: (MNG-4918) MavenProject#clone() doubles active profiles
[ http://jira.codehaus.org/browse/MNG-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4918. -- Resolution: Fixed Fix Version/s: 3.0.2 Assignee: Benjamin Bentmann Patch applied in [r1039327|http://svn.apache.org/viewvc?view=revision&revision=1039327]. > MavenProject#clone() doubles active profiles > > > Key: MNG-4918 > URL: http://jira.codehaus.org/browse/MNG-4918 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0, 3.0.1 > Environment: all >Reporter: Sebastian Annies >Assignee: Benjamin Bentmann > Fix For: 3.0.2 > > Attachments: fix.patch, test.patch > > > The error occured in our Project with more than 60 submodules and aggregating > JavaDoc. Due to the forking of the LifeCycle many clones of the MavenProject > object seem to be performed. Since MavenProject#clone doubles the entries in > the list of active profiles we start with one active profile and after a few > dozen clones the list of active profiles exceeds 10.000.000 elements. This > will than kill the VM by OOME. > mavenProject.getActiveProfiles().size() == 1 > mavenProject.clone().getActiveProfiles().size() == 2 > mavenProject.clone().clone().getActiveProfiles().size() == 4 > and so on -- 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
[jira] Closed: (MNG-4912) Use of raw type should be Comparable
[
http://jira.codehaus.org/browse/MNG-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4912.
--
Resolution: Fixed
Fix Version/s: 3.0.2
Assignee: Benjamin Bentmann
Applied in
[r1039332|http://svn.apache.org/viewvc?view=revision&revision=1039332].
> Use of raw type should be Comparable
> -
>
> Key: MNG-4912
> URL: http://jira.codehaus.org/browse/MNG-4912
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0
>Reporter: Jesse Glick
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0.2
>
> Attachments: ArtifactVersion-Comparable.diff
>
>
> To avoid raw type and unchecked warnings, {{ArtifactVersion}} should
> implement {{Comparable}}, not raw {{Comparable}}. Compare
> {{interface Artifact extends Comparable}} etc.
--
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
[jira] Commented: (MNG-4917) Profile not active even though it has activeByDefault set to true
[ http://jira.codehaus.org/browse/MNG-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=244569#action_244569 ] Benson Margulies commented on MNG-4917: --- New behavior in 3.0, right? > Profile not active even though it has activeByDefault set to true > - > > Key: MNG-4917 > URL: http://jira.codehaus.org/browse/MNG-4917 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Profiles >Affects Versions: 3.0 >Reporter: Benson Margulies >Assignee: Benjamin Bentmann > Attachments: pom.xml > > > I've got a parent pom with a profile with > true. > You can retrieve it for yourself via git clone > git://git.apache.org/webservices-xmlschema.git. > The problem is the sourcecheck profile in the parent pom. > running mvn -Psourcecheck works as expected, but running without the -P fails > to activate the profile. > the help plugin, I think, has separate problems in this area, or perhaps it's > not supposed to look at -P? -- 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
[jira] Commented: (MNG-4917) Profile not active even though it has activeByDefault set to true
[ http://jira.codehaus.org/browse/MNG-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=244572#action_244572 ] Benjamin Bentmann commented on MNG-4917: No, as can be seen from the example POM I provided. You should also keep in mind that your POM by design uses a profile that only Maven 3.0 properly activates. > Profile not active even though it has activeByDefault set to true > - > > Key: MNG-4917 > URL: http://jira.codehaus.org/browse/MNG-4917 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Profiles >Affects Versions: 3.0 >Reporter: Benson Margulies >Assignee: Benjamin Bentmann > Attachments: pom.xml > > > I've got a parent pom with a profile with > true. > You can retrieve it for yourself via git clone > git://git.apache.org/webservices-xmlschema.git. > The problem is the sourcecheck profile in the parent pom. > running mvn -Psourcecheck works as expected, but running without the -P fails > to activate the profile. > the help plugin, I think, has separate problems in this area, or perhaps it's > not supposed to look at -P? -- 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
[jira] Closed: (MPH-80) Adding profiles with -P does not change the output of help:active-profiles
[ http://jira.codehaus.org/browse/MPH-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MPH-80. --- Resolution: Not A Bug > Adding profiles with -P does not change the output of help:active-profiles > -- > > Key: MPH-80 > URL: http://jira.codehaus.org/browse/MPH-80 > Project: Maven 2.x Help Plugin > Issue Type: Bug >Affects Versions: 2.1.1 >Reporter: Benson Margulies > > 1. git clone git://git.apache.org/webservices-xmlschema.git > 2. mvn help:active-profiles > 3. mvn help:active-profiles -Pfastinstall > same output (with maven 3.0). > This seems unhelpful. -- 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
[jira] Commented: (MPIR-163) Invalid url fragment with local license file
[
http://jira.codehaus.org/browse/MPIR-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=244574#action_244574
]
Vincent Siveton commented on MPIR-163:
--
Yes it is a known limitation of the basedir... you could define a trunk.dir
property in your parent and override it in your modules i.e.
{code}
|trunk.dir
|_LICENSE.TXT
|_ pom.xml (parent)
|_ module\
|_ pom.xml
{code}
Parent pom.xml:
{code}
${basedir}
XXX
${trunk.dir}/LICENSE.TXT
{code}
Module pom.xml:
{code}
${basedir}/..
{code}
You could make your LICENSE.TXT on a webserver or on a public svn.
> Invalid url fragment with local license file
>
>
> Key: MPIR-163
> URL: http://jira.codehaus.org/browse/MPIR-163
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.1.1
> Environment: mvn 2.0.10, xp sp2
>Reporter: Michael Osipov
> Attachments: local-license.patch
>
>
> I've set a local license file from my basedir in my pom. The dependencies
> tree report lists the license but links to /dependencies.html#LICENSE.txt
> which is incorrect. See
> [here|http://java.fckeditor.net/java-demo/dependencies.html] for
> net.fckeditor:java-core:jar:2.5-beta-1 for the failing testcase.
> I have patched 2.1.1 which works well, see attachment.
--
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
[jira] Closed: (MRELEASE-621) Add a postPrepareGoals
[ http://jira.codehaus.org/browse/MRELEASE-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly closed MRELEASE-621. - Resolution: Fixed Fix Version/s: 2.2 Implemented in r1039453 > Add a postPrepareGoals > -- > > Key: MRELEASE-621 > URL: http://jira.codehaus.org/browse/MRELEASE-621 > Project: Maven 2.x Release Plugin > Issue Type: New Feature > Components: prepare >Affects Versions: 2.1 >Reporter: Stephen Connolly >Assignee: Stephen Connolly >Priority: Minor > Fix For: 2.2 > > > At present the preparationGoals run before the tag is created. > It would be nice to have a means of doing additional stuff after the tag has > been created and before the next-version-SNAPSHOT pom is checked back into > the trunk (or branch that you were releasing from) > Could then be used to have versions-maven-plugin resolve the ranges for the > release and restore them to ranges for development. -- 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
[jira] Created: (MNG-4919) Plugin execution contributed by lifecycle mapping gets lost when same goal is bound multiple times
Plugin execution contributed by lifecycle mapping gets lost when same goal is
bound multiple times
--
Key: MNG-4919
URL: http://jira.codehaus.org/browse/MNG-4919
Project: Maven 2 & 3
Issue Type: Bug
Components: Plugins and Lifecycle, POM
Affects Versions: 3.0.1
Reporter: Benjamin Bentmann
When a plugin goal is implicitly bound twice from lifecycle mappings, the two
goal executions get the same id and clash. This clash can eventually lead to
all but one goal execution being lost (during model merging).
Originally reported as [TYCHO-546|https://issues.sonatype.org/browse/TYCHO-546]
where {{org.apache.maven.plugins:maven-clean-plugin:clean}} is bound once for
the {{clean}} lifecycle (from Maven core) and once for the {{default}}
lifecycle (from the build extension), both times using the execution id
{{default-clean}}.
--
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
[jira] Created: (MINVOKER-108) Upgrade doxia and doxia-site-tools version to 1.1.4
Upgrade doxia and doxia-site-tools version to 1.1.4 --- Key: MINVOKER-108 URL: http://jira.codehaus.org/browse/MINVOKER-108 Project: Maven 2.x Invoker Plugin Issue Type: Improvement Affects Versions: 1.5 Reporter: Olivier Lamy -- 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
[jira] Closed: (MINVOKER-108) Upgrade doxia and doxia-site-tools version to 1.1.4
[ http://jira.codehaus.org/browse/MINVOKER-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MINVOKER-108. - Resolution: Fixed Fix Version/s: 1.6 Assignee: Olivier Lamy fixed [rev 1039569|http://svn.apache.org/viewvc?rev=1039569&view=rev] > Upgrade doxia and doxia-site-tools version to 1.1.4 > --- > > Key: MINVOKER-108 > URL: http://jira.codehaus.org/browse/MINVOKER-108 > Project: Maven 2.x Invoker Plugin > Issue Type: Improvement >Affects Versions: 1.5 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 1.6 > > -- 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
[jira] Created: (MINVOKER-109) upgrade maven-reporting-api and maven-reporting-impl versions
upgrade maven-reporting-api and maven-reporting-impl versions -- Key: MINVOKER-109 URL: http://jira.codehaus.org/browse/MINVOKER-109 Project: Maven 2.x Invoker Plugin Issue Type: Improvement Reporter: Olivier Lamy maven-reporting-api -> 3.0 maven-reporting-impl -> 2.1 -- 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
[jira] Closed: (MINVOKER-109) upgrade maven-reporting-api and maven-reporting-impl versions
[ http://jira.codehaus.org/browse/MINVOKER-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MINVOKER-109. - Resolution: Fixed Fix Version/s: 1.6 Assignee: Olivier Lamy fixed [rev 1039570|http://svn.apache.org/viewvc?rev=1039570&view=rev] > upgrade maven-reporting-api and maven-reporting-impl versions > -- > > Key: MINVOKER-109 > URL: http://jira.codehaus.org/browse/MINVOKER-109 > Project: Maven 2.x Invoker Plugin > Issue Type: Improvement >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 1.6 > > > maven-reporting-api -> 3.0 > maven-reporting-impl -> 2.1 -- 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
[jira] Created: (MINVOKER-110) It tests must be runnable in parrallel
It tests must be runnable in parrallel -- Key: MINVOKER-110 URL: http://jira.codehaus.org/browse/MINVOKER-110 Project: Maven 2.x Invoker Plugin Issue Type: New Feature Affects Versions: 1.5 Reporter: Olivier Lamy Add a new feature to run its in parrallel with a configurable number of threads. -- 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
[jira] Updated: (MINVOKER-110) It tests must be runnable in parrallel
[ http://jira.codehaus.org/browse/MINVOKER-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MINVOKER-110: -- Fix Version/s: 1.6 Assignee: Olivier Lamy > It tests must be runnable in parrallel > -- > > Key: MINVOKER-110 > URL: http://jira.codehaus.org/browse/MINVOKER-110 > Project: Maven 2.x Invoker Plugin > Issue Type: New Feature >Affects Versions: 1.5 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 1.6 > > > Add a new feature to run its in parrallel with a configurable number of > threads. -- 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
