Re: svnjava provider and maven scm
On 19/03/2009, at 7:29 PM, Jason van Zyl wrote: On 19-Mar-09, at 1:25 AM, Olivier Lamy wrote: Hi, Ok. It's was not really clear for me. There is precedent - we grandfathered in Checkstyle which is LGPL as it is just a dependency of a plugin, which we don't actually distribute. The general talk - though not confirmed - is that optional dependencies that the user must obtain themselves could be ok. There isn't a legal problem with the combination, but rather a policy one that you don't distribute something that is essentially useless without a dependency of a stronger license. We should ask, but I personally think this is ok, as long as: - it is not made the default provider - instructions on the site about how to use it spell out that it requires the dependency and that it is not under the AL - we don't bundle and distribute Technically we are not redistributing anything and we can ask the board for clarification because in the strictest sense we do not redistribute. But I think folks here would interpret a dependency in your POM as being equivalent. No need to ask the board, you can file a request here: https://issues.apache.org/jira/browse/LEGAL Cheers, Brett -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/
Re: unsubscribe
write a mail to scm-dev-unsubscr...@maven.apache.org LieGrue, strub --- Christian Schlaefcke cschlaef...@wms-network.de schrieb am Do, 19.3.2009: Von: Christian Schlaefcke cschlaef...@wms-network.de Betreff: Re: unsubscribe An: cschlaef...@wms-network.de CC: scm-dev@maven.apache.org Datum: Donnerstag, 19. März 2009, 10:51 Hmm, did not work... How can unsubscribe from this list? Sorry for that... Regards, Christian
Re: svnjava provider and maven scm
In fact we are not 'packaging' it, but we 'distribute' it via download links. So from the de iure point this is really edgy. The easiest thing would be to simply ask svnkit folks to give us a consensus letter that we are allowed to use it for maven-scm or even better a general clearance for using it in Apache projects. LieGrue, strub --- Jason van Zyl jvan...@sonatype.com schrieb am Do, 19.3.2009: Von: Jason van Zyl jvan...@sonatype.com Betreff: Re: svnjava provider and maven scm An: scm-dev@maven.apache.org Datum: Donnerstag, 19. März 2009, 9:29 On 19-Mar-09, at 1:25 AM, Olivier Lamy wrote: Hi, Ok. It's was not really clear for me. Technically we are not redistributing anything and we can ask the board for clarification because in the strictest sense we do not redistribute. But I think folks here would interpret a dependency in your POM as being equivalent. Thanks for clarification, -- Olivier 2009/3/19 Jason van Zyl jvan...@sonatype.com: If the license is not one that the ASF accepts then we can't really dodge the issue by saying that it's only in the POM. On 18-Mar-09, at 5:22 PM, Olivier Lamy wrote: Hi, As we don't distribute the svnkit (it's only a dependency available in the central repo), why we can't make a release of this provider ? Any objections to move the sandbox module in trunk ? Thanks, -- Olivier Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- To do two things at once is to do neither. -—Publilius Syrus, Roman slave, first century B.C. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --
Re: svnjava provider and maven scm
On 20/03/2009, at 2:17 AM, Olivier Lamy wrote: So the Brett proposal looks fine too. I can mark the svnjava provider as optionnal and explain why on the scm site and explain how to use it. That was all my opinion, so we should get it confirmed before release. Note that under the current FAQ the Sleepycat license (which this is equivalent to), is not allowed for inclusion. I filed: https://issues.apache.org/jira/browse/LEGAL-45, and added a couple more points on the list about how we can avoid it getting used without being aware of the license - putting it in a separate build profile and making sure it is not in the aggregating POM. It can always go to mojo, but I think it'd be a shame to have to separate it, so it's worth asking. - Brett -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/
Re: [vote] Maven 2.1.0
+1 works on my favorite builds John Casey wrote: Hi everyone, It looks like Maven 2.1.0 is ready to release. You can try the binaries here: http://tinyurl.com/maven-2-1-0-vote (https://repository.apache.org/content/repositories/maven-staging-511ea882714d8b/org/apache/maven/apache-maven/2.1.0/) We've resolved 85 issues for this release (enumerated at the end of this message): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14587 Vote's open for 72 hours. Please cast your vote: [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, -john === Release Notes - Maven 2 - Version 2.1.0 ** Sub-task * [MNG-4025] - Prominently document opt-out setting for parallel artifact resolution for users * [MNG-4042] - Use plexus-sec-dispatcher 1.0 in Maven core when it is released ** Bug * [MNG-1349] - openssl checksums are not accepted by maven * [MNG-1585] - debug logging from wagon not shown in debug mode * [MNG-1992] - CLI -D should override properties in settings.xml * [MNG-1999] - Reporting inheritance does not work properly * [MNG-2432] - Apache and Mojo plugins take precendence over plugins in the pom. * [MNG-2433] - Maven looks for snapshots in offline mode * [MNG-2605] - Profiles in profiles.xml are active by default * [MNG-2668] - Plugin dependencies should be considered when the reactor creates the build order list * [MNG-2690] - DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly * [MNG-2695] - -o makes build fail for snapshot plugins * [MNG-2720] - Multiproject dependencies not accurate for project.compileClasspathElements when run from root project * [MNG-3023] - Reactor projects should be included in dependency resolution * [MNG-3057] - properties not expanded in generated POMs when building A/B/C nested projects * [MNG-3139] - The skin does not exist: Unable to determine the release version * [MNG-3217] - a plugin's dependencies can influence other plugins in a build * [MNG-3228] - Maven profile activation does not work when profile is defined in inherited 'parent' pom * [MNG-3271] - excludeDefaults does not seem to work * [MNG-3284] - Cached plugins are used, even when the specifically declared * [MNG-3314] - offline build not running, when having SNAPSHOT dependencies * [MNG-3621] - site url inheritance broken for UNC paths * [MNG-3628] - When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository * [MNG-3641] - Lack of error checks on profiles * [MNG-3645] - Maven doesn't do strict model validation for POMs in the current reactor * [MNG-3719] - [regression] plugin execution ordering no longer POM ordered in 2.0.9 * [MNG-3757] - Setting M2_HOME to nothing and running ant delets contents of the current folder * [MNG-3769] - [regression] Excluding relocated transitive dependencies does not work * [MNG-3776] - Namespace misspelled in settings.xml * [MNG-3808] - Execution order of report plugins is arbitrary if inheritance is involved * [MNG-3810] - [regression] Null Pointer Exception when Activation Profile Property is Empty * [MNG-3811] - Report plugins don't inherit configuration * [MNG-3899] - Inheritance does not merge extensions with same gid and aid * [MNG-3906] - Project-level plugin dependencies are in random order after merging * [MNG-3920] - Problem using velocity component * [MNG-3930] - mvn.bat doesn't handle ampersand in Windows user name properly * [MNG-3933] - Profiles.xml does not pickup OS family * [MNG-3940] - Interpolation of environment variables is not case-insensitive on Windows * [MNG-3948] - Remote repos defined by profiles outside of settings.xml are not used to resolve parent POMs * [MNG-3974] - New mirror syntax is not stopping on first match * [MNG-4016] - Properties with the prefix project/pom are not interpolated from the properties section * [MNG-4023] - Profiles from parent POM are injected multiple times if parent is part of reactor build * [MNG-4026] - [regression] Order of project class path does not match POM order during reactor build * [MNG-4032] - Test jar dependency not available for for main classes in multi module builds * [MNG-4043] - Resolve or rollback WebDAV wagon deployment issue where hostname is improperly extracted from URL * [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur with 2.0.10 * [MNG-4079] - Duplicate error messages * [MNG-4084] - Unnecessary Warning for an activate profile in child project * [MNG-4086] - [regression] Explicitly using plugin metaversions crashes plugin manager * [MNG-4087] - Percent encoded characters in file URLs are not decoded upon deployment ** Improvement * [MNG-1830] - add a 'compiled on timestamp' label when maven 2 is invoked with --version option * [MNG-1957] - jdk/jdk
Re: [vote] Maven 2.1.0
+1 Le jeudi 19 mars 2009 01:12:00, John Casey a écrit : Hi everyone, It looks like Maven 2.1.0 is ready to release. You can try the binaries here: http://tinyurl.com/maven-2-1-0-vote (https://repository.apache.org/content/repositories/maven-staging-511ea8827 14d8b/org/apache/maven/apache-maven/2.1.0/) We've resolved 85 issues for this release (enumerated at the end of this message): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName= Htmlversion=14587 Vote's open for 72 hours. Please cast your vote: [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, -john === Release Notes - Maven 2 - Version 2.1.0 ** Sub-task * [MNG-4025] - Prominently document opt-out setting for parallel artifact resolution for users * [MNG-4042] - Use plexus-sec-dispatcher 1.0 in Maven core when it is released ** Bug * [MNG-1349] - openssl checksums are not accepted by maven * [MNG-1585] - debug logging from wagon not shown in debug mode * [MNG-1992] - CLI -D should override properties in settings.xml * [MNG-1999] - Reporting inheritance does not work properly * [MNG-2432] - Apache and Mojo plugins take precendence over plugins in the pom. * [MNG-2433] - Maven looks for snapshots in offline mode * [MNG-2605] - Profiles in profiles.xml are active by default * [MNG-2668] - Plugin dependencies should be considered when the reactor creates the build order list * [MNG-2690] - DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly * [MNG-2695] - -o makes build fail for snapshot plugins * [MNG-2720] - Multiproject dependencies not accurate for project.compileClasspathElements when run from root project * [MNG-3023] - Reactor projects should be included in dependency resolution * [MNG-3057] - properties not expanded in generated POMs when building A/B/C nested projects * [MNG-3139] - The skin does not exist: Unable to determine the release version * [MNG-3217] - a plugin's dependencies can influence other plugins in a build * [MNG-3228] - Maven profile activation does not work when profile is defined in inherited 'parent' pom * [MNG-3271] - excludeDefaults does not seem to work * [MNG-3284] - Cached plugins are used, even when the specifically declared * [MNG-3314] - offline build not running, when having SNAPSHOT dependencies * [MNG-3621] - site url inheritance broken for UNC paths * [MNG-3628] - When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository * [MNG-3641] - Lack of error checks on profiles * [MNG-3645] - Maven doesn't do strict model validation for POMs in the current reactor * [MNG-3719] - [regression] plugin execution ordering no longer POM ordered in 2.0.9 * [MNG-3757] - Setting M2_HOME to nothing and running ant delets contents of the current folder * [MNG-3769] - [regression] Excluding relocated transitive dependencies does not work * [MNG-3776] - Namespace misspelled in settings.xml * [MNG-3808] - Execution order of report plugins is arbitrary if inheritance is involved * [MNG-3810] - [regression] Null Pointer Exception when Activation Profile Property is Empty * [MNG-3811] - Report plugins don't inherit configuration * [MNG-3899] - Inheritance does not merge extensions with same gid and aid * [MNG-3906] - Project-level plugin dependencies are in random order after merging * [MNG-3920] - Problem using velocity component * [MNG-3930] - mvn.bat doesn't handle ampersand in Windows user name properly * [MNG-3933] - Profiles.xml does not pickup OS family * [MNG-3940] - Interpolation of environment variables is not case-insensitive on Windows * [MNG-3948] - Remote repos defined by profiles outside of settings.xml are not used to resolve parent POMs * [MNG-3974] - New mirror syntax is not stopping on first match * [MNG-4016] - Properties with the prefix project/pom are not interpolated from the properties section * [MNG-4023] - Profiles from parent POM are injected multiple times if parent is part of reactor build * [MNG-4026] - [regression] Order of project class path does not match POM order during reactor build * [MNG-4032] - Test jar dependency not available for for main classes in multi module builds * [MNG-4043] - Resolve or rollback WebDAV wagon deployment issue where hostname is improperly extracted from URL * [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur with 2.0.10 * [MNG-4079] - Duplicate error messages * [MNG-4084] - Unnecessary Warning for an activate profile in child project * [MNG-4086] - [regression] Explicitly using plugin metaversions crashes plugin manager * [MNG-4087] - Percent encoded characters in file URLs are not decoded
Re: svnjava provider and maven scm
Hi, Ok. It's was not really clear for me. Thanks for clarification, -- Olivier 2009/3/19 Jason van Zyl jvan...@sonatype.com: If the license is not one that the ASF accepts then we can't really dodge the issue by saying that it's only in the POM. On 18-Mar-09, at 5:22 PM, Olivier Lamy wrote: Hi, As we don't distribute the svnkit (it's only a dependency available in the central repo), why we can't make a release of this provider ? Any objections to move the sandbox module in trunk ? Thanks, -- Olivier Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- To do two things at once is to do neither. -—Publilius Syrus, Roman slave, first century B.C.
Re: svnjava provider and maven scm
On 19-Mar-09, at 1:25 AM, Olivier Lamy wrote: Hi, Ok. It's was not really clear for me. Technically we are not redistributing anything and we can ask the board for clarification because in the strictest sense we do not redistribute. But I think folks here would interpret a dependency in your POM as being equivalent. Thanks for clarification, -- Olivier 2009/3/19 Jason van Zyl jvan...@sonatype.com: If the license is not one that the ASF accepts then we can't really dodge the issue by saying that it's only in the POM. On 18-Mar-09, at 5:22 PM, Olivier Lamy wrote: Hi, As we don't distribute the svnkit (it's only a dependency available in the central repo), why we can't make a release of this provider ? Any objections to move the sandbox module in trunk ? Thanks, -- Olivier Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- To do two things at once is to do neither. -—Publilius Syrus, Roman slave, first century B.C. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --
Re: [vote] Maven 2.1.0
Yeahhh, let's go! +1! :-) - Fabrice belling...@apache.org On Thu, Mar 19, 2009 at 1:12 AM, John Casey jdca...@commonjava.org wrote: Hi everyone, It looks like Maven 2.1.0 is ready to release. You can try the binaries here: http://tinyurl.com/maven-2-1-0-vote ( https://repository.apache.org/content/repositories/maven-staging-511ea882714d8b/org/apache/maven/apache-maven/2.1.0/ ) We've resolved 85 issues for this release (enumerated at the end of this message): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14587 Vote's open for 72 hours. Please cast your vote: [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, -john === Release Notes - Maven 2 - Version 2.1.0 ** Sub-task * [MNG-4025] - Prominently document opt-out setting for parallel artifact resolution for users * [MNG-4042] - Use plexus-sec-dispatcher 1.0 in Maven core when it is released ** Bug * [MNG-1349] - openssl checksums are not accepted by maven * [MNG-1585] - debug logging from wagon not shown in debug mode * [MNG-1992] - CLI -D should override properties in settings.xml * [MNG-1999] - Reporting inheritance does not work properly * [MNG-2432] - Apache and Mojo plugins take precendence over plugins in the pom. * [MNG-2433] - Maven looks for snapshots in offline mode * [MNG-2605] - Profiles in profiles.xml are active by default * [MNG-2668] - Plugin dependencies should be considered when the reactor creates the build order list * [MNG-2690] - DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly * [MNG-2695] - -o makes build fail for snapshot plugins * [MNG-2720] - Multiproject dependencies not accurate for project.compileClasspathElements when run from root project * [MNG-3023] - Reactor projects should be included in dependency resolution * [MNG-3057] - properties not expanded in generated POMs when building A/B/C nested projects * [MNG-3139] - The skin does not exist: Unable to determine the release version * [MNG-3217] - a plugin's dependencies can influence other plugins in a build * [MNG-3228] - Maven profile activation does not work when profile is defined in inherited 'parent' pom * [MNG-3271] - excludeDefaults does not seem to work * [MNG-3284] - Cached plugins are used, even when the specifically declared * [MNG-3314] - offline build not running, when having SNAPSHOT dependencies * [MNG-3621] - site url inheritance broken for UNC paths * [MNG-3628] - When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository * [MNG-3641] - Lack of error checks on profiles * [MNG-3645] - Maven doesn't do strict model validation for POMs in the current reactor * [MNG-3719] - [regression] plugin execution ordering no longer POM ordered in 2.0.9 * [MNG-3757] - Setting M2_HOME to nothing and running ant delets contents of the current folder * [MNG-3769] - [regression] Excluding relocated transitive dependencies does not work * [MNG-3776] - Namespace misspelled in settings.xml * [MNG-3808] - Execution order of report plugins is arbitrary if inheritance is involved * [MNG-3810] - [regression] Null Pointer Exception when Activation Profile Property is Empty * [MNG-3811] - Report plugins don't inherit configuration * [MNG-3899] - Inheritance does not merge extensions with same gid and aid * [MNG-3906] - Project-level plugin dependencies are in random order after merging * [MNG-3920] - Problem using velocity component * [MNG-3930] - mvn.bat doesn't handle ampersand in Windows user name properly * [MNG-3933] - Profiles.xml does not pickup OS family * [MNG-3940] - Interpolation of environment variables is not case-insensitive on Windows * [MNG-3948] - Remote repos defined by profiles outside of settings.xml are not used to resolve parent POMs * [MNG-3974] - New mirror syntax is not stopping on first match * [MNG-4016] - Properties with the prefix project/pom are not interpolated from the properties section * [MNG-4023] - Profiles from parent POM are injected multiple times if parent is part of reactor build * [MNG-4026] - [regression] Order of project class path does not match POM order during reactor build * [MNG-4032] - Test jar dependency not available for for main classes in multi module builds * [MNG-4043] - Resolve or rollback WebDAV wagon deployment issue where hostname is improperly extracted from URL * [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur with 2.0.10 * [MNG-4079] - Duplicate error messages * [MNG-4084] - Unnecessary Warning for an activate profile in child project * [MNG-4086] - [regression] Explicitly using plugin metaversions crashes plugin manager * [MNG-4087] - Percent encoded characters in file URLs are not decoded upon deployment
unsubscribe
unsubscribe
Re: [vote] Maven 2.1.0
It's failing for XWiki's build... Are you still running XWiki's build on your hudson ci btw? It's failing with the gwt maven plugin. It works fine with 2.1.0-M1 though. Ping me if you need help to reproduce it. Thanks -Vincent On Mar 19, 2009, at 1:12 AM, John Casey wrote: Hi everyone, It looks like Maven 2.1.0 is ready to release. You can try the binaries here: http://tinyurl.com/maven-2-1-0-vote (https://repository.apache.org/content/repositories/maven-staging-511ea882714d8b/org/apache/maven/apache-maven/2.1.0/ ) We've resolved 85 issues for this release (enumerated at the end of this message): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14587 Vote's open for 72 hours. Please cast your vote: [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, -john === Release Notes - Maven 2 - Version 2.1.0 ** Sub-task * [MNG-4025] - Prominently document opt-out setting for parallel artifact resolution for users * [MNG-4042] - Use plexus-sec-dispatcher 1.0 in Maven core when it is released ** Bug * [MNG-1349] - openssl checksums are not accepted by maven * [MNG-1585] - debug logging from wagon not shown in debug mode * [MNG-1992] - CLI -D should override properties in settings.xml * [MNG-1999] - Reporting inheritance does not work properly * [MNG-2432] - Apache and Mojo plugins take precendence over plugins in the pom. * [MNG-2433] - Maven looks for snapshots in offline mode * [MNG-2605] - Profiles in profiles.xml are active by default * [MNG-2668] - Plugin dependencies should be considered when the reactor creates the build order list * [MNG-2690] - DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly * [MNG-2695] - -o makes build fail for snapshot plugins * [MNG-2720] - Multiproject dependencies not accurate for project.compileClasspathElements when run from root project * [MNG-3023] - Reactor projects should be included in dependency resolution * [MNG-3057] - properties not expanded in generated POMs when building A/B/C nested projects * [MNG-3139] - The skin does not exist: Unable to determine the release version * [MNG-3217] - a plugin's dependencies can influence other plugins in a build * [MNG-3228] - Maven profile activation does not work when profile is defined in inherited 'parent' pom * [MNG-3271] - excludeDefaults does not seem to work * [MNG-3284] - Cached plugins are used, even when the specifically declared * [MNG-3314] - offline build not running, when having SNAPSHOT dependencies * [MNG-3621] - site url inheritance broken for UNC paths * [MNG-3628] - When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository * [MNG-3641] - Lack of error checks on profiles * [MNG-3645] - Maven doesn't do strict model validation for POMs in the current reactor * [MNG-3719] - [regression] plugin execution ordering no longer POM ordered in 2.0.9 * [MNG-3757] - Setting M2_HOME to nothing and running ant delets contents of the current folder * [MNG-3769] - [regression] Excluding relocated transitive dependencies does not work * [MNG-3776] - Namespace misspelled in settings.xml * [MNG-3808] - Execution order of report plugins is arbitrary if inheritance is involved * [MNG-3810] - [regression] Null Pointer Exception when Activation Profile Property is Empty * [MNG-3811] - Report plugins don't inherit configuration * [MNG-3899] - Inheritance does not merge extensions with same gid and aid * [MNG-3906] - Project-level plugin dependencies are in random order after merging * [MNG-3920] - Problem using velocity component * [MNG-3930] - mvn.bat doesn't handle ampersand in Windows user name properly * [MNG-3933] - Profiles.xml does not pickup OS family * [MNG-3940] - Interpolation of environment variables is not case- insensitive on Windows * [MNG-3948] - Remote repos defined by profiles outside of settings.xml are not used to resolve parent POMs * [MNG-3974] - New mirror syntax is not stopping on first match * [MNG-4016] - Properties with the prefix project/pom are not interpolated from the properties section * [MNG-4023] - Profiles from parent POM are injected multiple times if parent is part of reactor build * [MNG-4026] - [regression] Order of project class path does not match POM order during reactor build * [MNG-4032] - Test jar dependency not available for for main classes in multi module builds * [MNG-4043] - Resolve or rollback WebDAV wagon deployment issue where hostname is improperly extracted from URL * [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur with 2.0.10 * [MNG-4079] - Duplicate error messages * [MNG-4084] - Unnecessary Warning for an activate profile in child project * [MNG-4086] - [regression] Explicitly using plugin
Re: unsubscribe
Hmm, did not work... How can unsubscribe from this list? Sorry for that... Regards, Christian
AW: [vote] Maven 2.1.0
+1 looks good! Tested with my Apache projects + a few internal projects. LieGrue, strub --- John Casey jdca...@commonjava.org schrieb am Do, 19.3.2009: Von: John Casey jdca...@commonjava.org Betreff: [vote] Maven 2.1.0 An: Maven Developers List dev@maven.apache.org Datum: Donnerstag, 19. März 2009, 1:12 Hi everyone, It looks like Maven 2.1.0 is ready to release. You can try the binaries here: http://tinyurl.com/maven-2-1-0-vote (https://repository.apache.org/content/repositories/maven-staging-511ea882714d8b/org/apache/maven/apache-maven/2.1.0/) We've resolved 85 issues for this release (enumerated at the end of this message): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14587 Vote's open for 72 hours. Please cast your vote: [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, -john === Release Notes - Maven 2 - Version 2.1.0 ** Sub-task * [MNG-4025] - Prominently document opt-out setting for parallel artifact resolution for users * [MNG-4042] - Use plexus-sec-dispatcher 1.0 in Maven core when it is released ** Bug * [MNG-1349] - openssl checksums are not accepted by maven * [MNG-1585] - debug logging from wagon not shown in debug mode * [MNG-1992] - CLI -D should override properties in settings.xml * [MNG-1999] - Reporting inheritance does not work properly * [MNG-2432] - Apache and Mojo plugins take precendence over plugins in the pom. * [MNG-2433] - Maven looks for snapshots in offline mode * [MNG-2605] - Profiles in profiles.xml are active by default * [MNG-2668] - Plugin dependencies should be considered when the reactor creates the build order list * [MNG-2690] - DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly * [MNG-2695] - -o makes build fail for snapshot plugins * [MNG-2720] - Multiproject dependencies not accurate for project.compileClasspathElements when run from root project * [MNG-3023] - Reactor projects should be included in dependency resolution * [MNG-3057] - properties not expanded in generated POMs when building A/B/C nested projects * [MNG-3139] - The skin does not exist: Unable to determine the release version * [MNG-3217] - a plugin's dependencies can influence other plugins in a build * [MNG-3228] - Maven profile activation does not work when profile is defined in inherited 'parent' pom * [MNG-3271] - excludeDefaults does not seem to work * [MNG-3284] - Cached plugins are used, even when the specifically declared * [MNG-3314] - offline build not running, when having SNAPSHOT dependencies * [MNG-3621] - site url inheritance broken for UNC paths * [MNG-3628] - When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository * [MNG-3641] - Lack of error checks on profiles * [MNG-3645] - Maven doesn't do strict model validation for POMs in the current reactor * [MNG-3719] - [regression] plugin execution ordering no longer POM ordered in 2.0.9 * [MNG-3757] - Setting M2_HOME to nothing and running ant delets contents of the current folder * [MNG-3769] - [regression] Excluding relocated transitive dependencies does not work * [MNG-3776] - Namespace misspelled in settings.xml * [MNG-3808] - Execution order of report plugins is arbitrary if inheritance is involved * [MNG-3810] - [regression] Null Pointer Exception when Activation Profile Property is Empty * [MNG-3811] - Report plugins don't inherit configuration * [MNG-3899] - Inheritance does not merge extensions with same gid and aid * [MNG-3906] - Project-level plugin dependencies are in random order after merging * [MNG-3920] - Problem using velocity component * [MNG-3930] - mvn.bat doesn't handle ampersand in Windows user name properly * [MNG-3933] - Profiles.xml does not pickup OS family * [MNG-3940] - Interpolation of environment variables is not case-insensitive on Windows * [MNG-3948] - Remote repos defined by profiles outside of settings.xml are not used to resolve parent POMs * [MNG-3974] - New mirror syntax is not stopping on first match * [MNG-4016] - Properties with the prefix project/pom are not interpolated from the properties section * [MNG-4023] - Profiles from parent POM are injected multiple times if parent is part of reactor build * [MNG-4026] - [regression] Order of project class path does not match POM order during reactor build * [MNG-4032] - Test jar dependency not available for for main classes in multi module builds * [MNG-4043] - Resolve or rollback WebDAV wagon deployment issue where hostname is improperly extracted from URL * [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur with 2.0.10 * [MNG-4079] - Duplicate error messages *
Maven PDF Plugin Bugs
Hi! I have tried the maven-pdf-plugin and I've encountered some bugs. Where can I file those? -- Thanks, Jevica Arianne B. Zurbano - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven PDF Plugin Bugs
On Thu, Mar 19, 2009 at 5:35 AM, jevica.arianne jevica.aria...@gmail.com wrote: Hi! I have tried the maven-pdf-plugin and I've encountered some bugs. Where can I file those? You can use http://jira.codehaus.org/browse/MSANDBOX in the maven-pdf-plugin component for now. It was recently promoted from the sandbox, and should get its own JIRA project soon, probably 'MPDF'. -- Wendy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven PDF Plugin Bugs
Done: http://jira.codehaus.org/browse/MPDF Cheers, -Lukas Wendy Smoak wrote: On Thu, Mar 19, 2009 at 5:35 AM, jevica.arianne jevica.aria...@gmail.com wrote: Hi! I have tried the maven-pdf-plugin and I've encountered some bugs. Where can I file those? You can use http://jira.codehaus.org/browse/MSANDBOX in the maven-pdf-plugin component for now. It was recently promoted from the sandbox, and should get its own JIRA project soon, probably 'MPDF'. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
@component or @plexus.requirement?
Hello, I'm a bit confused on the use of the @component and @plexus.requirement Javadoc annotations. http://docs.codehaus.org/display/MAVEN/Deterministic+Lifecycle+Planning The above document contains the following: injected either as a @plexus.requirement or @component annotation, depending on whether you're writing a Plexus component or an implementation of the Mojo interface Within a complete Maven plugin implementation, where is the boundary for the set of classes where I have to use @component annotation? Is it only in the real plugin class (extending AbstractMojo) where I have to use @component? Use @plexus.requirement for the rest? Please enlighten me! Ringo - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svnjava provider and maven scm
From my experience asking anyone about anything legal has never been resolved in any timely manner. Whether grand fathered or anything else. Discussions have gone on for a very long time. Olivier if you want to release it then I would just taking it to mojo and then there are no issues. On 19-Mar-09, at 5:12 AM, Brett Porter wrote: On 19/03/2009, at 7:29 PM, Jason van Zyl wrote: On 19-Mar-09, at 1:25 AM, Olivier Lamy wrote: Hi, Ok. It's was not really clear for me. There is precedent - we grandfathered in Checkstyle which is LGPL as it is just a dependency of a plugin, which we don't actually distribute. The general talk - though not confirmed - is that optional dependencies that the user must obtain themselves could be ok. There isn't a legal problem with the combination, but rather a policy one that you don't distribute something that is essentially useless without a dependency of a stronger license. We should ask, but I personally think this is ok, as long as: - it is not made the default provider - instructions on the site about how to use it spell out that it requires the dependency and that it is not under the AL - we don't bundle and distribute Technically we are not redistributing anything and we can ask the board for clarification because in the strictest sense we do not redistribute. But I think folks here would interpret a dependency in your POM as being equivalent. No need to ask the board, you can file a request here: https://issues.apache.org/jira/browse/LEGAL Cheers, Brett -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --
Re: @component or @plexus.requirement?
One annotation is for Plexus components specifically and that is @plexus.requirement or @Requirement if you're doing annotations. The other is specifically for Maven plugins. The component metadata for your own types, like our Maven plugins, have their own component descriptors which are mutated on the fly inside Plexus. But for a Maven plugin that also contains other Plexus components you need to use @plexus.requirement/@Requirement with your Plexus components and @component in your Mojo-based classes. Maven plugins may often not contain any Plexus components so the use of the type of annotations is completely partitioned. Take a look at Maven trunk if you want to see examples of the annotations used for Plexus components. On 19-Mar-09, at 7:05 AM, Ringo De Smet wrote: Hello, I'm a bit confused on the use of the @component and @plexus.requirement Javadoc annotations. http://docs.codehaus.org/display/MAVEN/Deterministic+Lifecycle +Planning The above document contains the following: injected either as a @plexus.requirement or @component annotation, depending on whether you're writing a Plexus component or an implementation of the Mojo interface Within a complete Maven plugin implementation, where is the boundary for the set of classes where I have to use @component annotation? Is it only in the real plugin class (extending AbstractMojo) where I have to use @component? Use @plexus.requirement for the rest? Please enlighten me! Ringo - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] Maven 2.1.0
+1, seems to work fine for me. Nice job. Dan On Wed March 18 2009 8:12:00 pm John Casey wrote: Hi everyone, It looks like Maven 2.1.0 is ready to release. You can try the binaries here: http://tinyurl.com/maven-2-1-0-vote (https://repository.apache.org/content/repositories/maven-staging-511ea8827 14d8b/org/apache/maven/apache-maven/2.1.0/) We've resolved 85 issues for this release (enumerated at the end of this message): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName= Htmlversion=14587 Vote's open for 72 hours. Please cast your vote: [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, -john === Release Notes - Maven 2 - Version 2.1.0 ** Sub-task * [MNG-4025] - Prominently document opt-out setting for parallel artifact resolution for users * [MNG-4042] - Use plexus-sec-dispatcher 1.0 in Maven core when it is released ** Bug * [MNG-1349] - openssl checksums are not accepted by maven * [MNG-1585] - debug logging from wagon not shown in debug mode * [MNG-1992] - CLI -D should override properties in settings.xml * [MNG-1999] - Reporting inheritance does not work properly * [MNG-2432] - Apache and Mojo plugins take precendence over plugins in the pom. * [MNG-2433] - Maven looks for snapshots in offline mode * [MNG-2605] - Profiles in profiles.xml are active by default * [MNG-2668] - Plugin dependencies should be considered when the reactor creates the build order list * [MNG-2690] - DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly * [MNG-2695] - -o makes build fail for snapshot plugins * [MNG-2720] - Multiproject dependencies not accurate for project.compileClasspathElements when run from root project * [MNG-3023] - Reactor projects should be included in dependency resolution * [MNG-3057] - properties not expanded in generated POMs when building A/B/C nested projects * [MNG-3139] - The skin does not exist: Unable to determine the release version * [MNG-3217] - a plugin's dependencies can influence other plugins in a build * [MNG-3228] - Maven profile activation does not work when profile is defined in inherited 'parent' pom * [MNG-3271] - excludeDefaults does not seem to work * [MNG-3284] - Cached plugins are used, even when the specifically declared * [MNG-3314] - offline build not running, when having SNAPSHOT dependencies * [MNG-3621] - site url inheritance broken for UNC paths * [MNG-3628] - When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository * [MNG-3641] - Lack of error checks on profiles * [MNG-3645] - Maven doesn't do strict model validation for POMs in the current reactor * [MNG-3719] - [regression] plugin execution ordering no longer POM ordered in 2.0.9 * [MNG-3757] - Setting M2_HOME to nothing and running ant delets contents of the current folder * [MNG-3769] - [regression] Excluding relocated transitive dependencies does not work * [MNG-3776] - Namespace misspelled in settings.xml * [MNG-3808] - Execution order of report plugins is arbitrary if inheritance is involved * [MNG-3810] - [regression] Null Pointer Exception when Activation Profile Property is Empty * [MNG-3811] - Report plugins don't inherit configuration * [MNG-3899] - Inheritance does not merge extensions with same gid and aid * [MNG-3906] - Project-level plugin dependencies are in random order after merging * [MNG-3920] - Problem using velocity component * [MNG-3930] - mvn.bat doesn't handle ampersand in Windows user name properly * [MNG-3933] - Profiles.xml does not pickup OS family * [MNG-3940] - Interpolation of environment variables is not case-insensitive on Windows * [MNG-3948] - Remote repos defined by profiles outside of settings.xml are not used to resolve parent POMs * [MNG-3974] - New mirror syntax is not stopping on first match * [MNG-4016] - Properties with the prefix project/pom are not interpolated from the properties section * [MNG-4023] - Profiles from parent POM are injected multiple times if parent is part of reactor build * [MNG-4026] - [regression] Order of project class path does not match POM order during reactor build * [MNG-4032] - Test jar dependency not available for for main classes in multi module builds * [MNG-4043] - Resolve or rollback WebDAV wagon deployment issue where hostname is improperly extracted from URL * [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur with 2.0.10 * [MNG-4079] - Duplicate error messages * [MNG-4084] - Unnecessary Warning for an activate profile in child project * [MNG-4086] - [regression] Explicitly using plugin metaversions crashes plugin manager * [MNG-4087] - Percent
Re: @component or @plexus.requirement?
Jason, 2009/3/19 Jason van Zyl jvan...@sonatype.com: One annotation is for Plexus components specifically and that is @plexus.requirement or @Requirement if you're doing annotations. The other is specifically for Maven plugins. The component metadata for your own types, like our Maven plugins, have their own component descriptors which are mutated on the fly inside Plexus. OK, got it now! :-) But for a Maven plugin that also contains other Plexus components you need to use @plexus.requirement/@Requirement with your Plexus components and @component in your Mojo-based classes. Maven plugins may often not contain any Plexus components so the use of the type of annotations is completely partitioned. Take a look at Maven trunk if you want to see examples of the annotations used for Plexus components. Does it depend what I'm trying to resolve? I have a utility class that I wanted to give a Log object and used the @component Javadoc tag. This worked, but Log belongs to Maven. Core question is: does @component resolve *any* Plexus component when run within the Maven context, or only Maven specific components? Concerning real Java5+ annotations: I can't use them for the moment since our build system has to remain Java 1.4 compliant. Thanks for the answer! Ringo - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svnjava provider and maven scm
So the Brett proposal looks fine too. I can mark the svnjava provider as optionnal and explain why on the scm site and explain how to use it. -- Olivier 2009/3/19 Jason van Zyl jvan...@sonatype.com: From my experience asking anyone about anything legal has never been resolved in any timely manner. Whether grand fathered or anything else. Discussions have gone on for a very long time. Olivier if you want to release it then I would just taking it to mojo and then there are no issues. On 19-Mar-09, at 5:12 AM, Brett Porter wrote: On 19/03/2009, at 7:29 PM, Jason van Zyl wrote: On 19-Mar-09, at 1:25 AM, Olivier Lamy wrote: Hi, Ok. It's was not really clear for me. There is precedent - we grandfathered in Checkstyle which is LGPL as it is just a dependency of a plugin, which we don't actually distribute. The general talk - though not confirmed - is that optional dependencies that the user must obtain themselves could be ok. There isn't a legal problem with the combination, but rather a policy one that you don't distribute something that is essentially useless without a dependency of a stronger license. We should ask, but I personally think this is ok, as long as: - it is not made the default provider - instructions on the site about how to use it spell out that it requires the dependency and that it is not under the AL - we don't bundle and distribute Technically we are not redistributing anything and we can ask the board for clarification because in the strictest sense we do not redistribute. But I think folks here would interpret a dependency in your POM as being equivalent. No need to ask the board, you can file a request here: https://issues.apache.org/jira/browse/LEGAL Cheers, Brett -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --
Re: [vote] Maven 2.1.0
I'm still waiting for the XWiki build to run on the grid, but here is the result for the gwt-maven-plugin...it was successful: https://grid.sonatype.org/ci/view/Community%20Test%20Projects/job/gwt-maven-plugin/5/jdk=1.5,label=ubuntu/console Is there something I'm missing? The version of Maven I'm using was build out on the Hudson grid from the 2.1.0 tag; I'll setup one to use the staged binaries next, but there should be no difference. -john Vincent Massol wrote: It's failing for XWiki's build... Are you still running XWiki's build on your hudson ci btw? It's failing with the gwt maven plugin. It works fine with 2.1.0-M1 though. Ping me if you need help to reproduce it. Thanks -Vincent On Mar 19, 2009, at 1:12 AM, John Casey wrote: Hi everyone, It looks like Maven 2.1.0 is ready to release. You can try the binaries here: http://tinyurl.com/maven-2-1-0-vote (https://repository.apache.org/content/repositories/maven-staging-511ea882714d8b/org/apache/maven/apache-maven/2.1.0/) We've resolved 85 issues for this release (enumerated at the end of this message): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14587 Vote's open for 72 hours. Please cast your vote: [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, -john === Release Notes - Maven 2 - Version 2.1.0 ** Sub-task * [MNG-4025] - Prominently document opt-out setting for parallel artifact resolution for users * [MNG-4042] - Use plexus-sec-dispatcher 1.0 in Maven core when it is released ** Bug * [MNG-1349] - openssl checksums are not accepted by maven * [MNG-1585] - debug logging from wagon not shown in debug mode * [MNG-1992] - CLI -D should override properties in settings.xml * [MNG-1999] - Reporting inheritance does not work properly * [MNG-2432] - Apache and Mojo plugins take precendence over plugins in the pom. * [MNG-2433] - Maven looks for snapshots in offline mode * [MNG-2605] - Profiles in profiles.xml are active by default * [MNG-2668] - Plugin dependencies should be considered when the reactor creates the build order list * [MNG-2690] - DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly * [MNG-2695] - -o makes build fail for snapshot plugins * [MNG-2720] - Multiproject dependencies not accurate for project.compileClasspathElements when run from root project * [MNG-3023] - Reactor projects should be included in dependency resolution * [MNG-3057] - properties not expanded in generated POMs when building A/B/C nested projects * [MNG-3139] - The skin does not exist: Unable to determine the release version * [MNG-3217] - a plugin's dependencies can influence other plugins in a build * [MNG-3228] - Maven profile activation does not work when profile is defined in inherited 'parent' pom * [MNG-3271] - excludeDefaults does not seem to work * [MNG-3284] - Cached plugins are used, even when the specifically declared * [MNG-3314] - offline build not running, when having SNAPSHOT dependencies * [MNG-3621] - site url inheritance broken for UNC paths * [MNG-3628] - When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository * [MNG-3641] - Lack of error checks on profiles * [MNG-3645] - Maven doesn't do strict model validation for POMs in the current reactor * [MNG-3719] - [regression] plugin execution ordering no longer POM ordered in 2.0.9 * [MNG-3757] - Setting M2_HOME to nothing and running ant delets contents of the current folder * [MNG-3769] - [regression] Excluding relocated transitive dependencies does not work * [MNG-3776] - Namespace misspelled in settings.xml * [MNG-3808] - Execution order of report plugins is arbitrary if inheritance is involved * [MNG-3810] - [regression] Null Pointer Exception when Activation Profile Property is Empty * [MNG-3811] - Report plugins don't inherit configuration * [MNG-3899] - Inheritance does not merge extensions with same gid and aid * [MNG-3906] - Project-level plugin dependencies are in random order after merging * [MNG-3920] - Problem using velocity component * [MNG-3930] - mvn.bat doesn't handle ampersand in Windows user name properly * [MNG-3933] - Profiles.xml does not pickup OS family * [MNG-3940] - Interpolation of environment variables is not case-insensitive on Windows * [MNG-3948] - Remote repos defined by profiles outside of settings.xml are not used to resolve parent POMs * [MNG-3974] - New mirror syntax is not stopping on first match * [MNG-4016] - Properties with the prefix project/pom are not interpolated from the properties section * [MNG-4023] - Profiles from parent POM are injected multiple times if parent is part of reactor build * [MNG-4026] - [regression] Order of project class path does not match POM order during reactor build * [MNG-4032] - Test jar
Re: [vote] Maven 2.1.0
Used it for todays work, including with M2Eclipse. +1 (Non-binding) On Thu, Mar 19, 2009 at 1:12 AM, John Casey jdca...@commonjava.org wrote: Hi everyone, It looks like Maven 2.1.0 is ready to release. You can try the binaries here: http://tinyurl.com/maven-2-1-0-vote (https://repository.apache.org/content/repositories/maven-staging-511ea882714d8b/org/apache/maven/apache-maven/2.1.0/) We've resolved 85 issues for this release (enumerated at the end of this message): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14587 Vote's open for 72 hours. Please cast your vote: [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, -john === Release Notes - Maven 2 - Version 2.1.0 ** Sub-task * [MNG-4025] - Prominently document opt-out setting for parallel artifact resolution for users * [MNG-4042] - Use plexus-sec-dispatcher 1.0 in Maven core when it is released ** Bug * [MNG-1349] - openssl checksums are not accepted by maven * [MNG-1585] - debug logging from wagon not shown in debug mode * [MNG-1992] - CLI -D should override properties in settings.xml * [MNG-1999] - Reporting inheritance does not work properly * [MNG-2432] - Apache and Mojo plugins take precendence over plugins in the pom. * [MNG-2433] - Maven looks for snapshots in offline mode * [MNG-2605] - Profiles in profiles.xml are active by default * [MNG-2668] - Plugin dependencies should be considered when the reactor creates the build order list * [MNG-2690] - DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly * [MNG-2695] - -o makes build fail for snapshot plugins * [MNG-2720] - Multiproject dependencies not accurate for project.compileClasspathElements when run from root project * [MNG-3023] - Reactor projects should be included in dependency resolution * [MNG-3057] - properties not expanded in generated POMs when building A/B/C nested projects * [MNG-3139] - The skin does not exist: Unable to determine the release version * [MNG-3217] - a plugin's dependencies can influence other plugins in a build * [MNG-3228] - Maven profile activation does not work when profile is defined in inherited 'parent' pom * [MNG-3271] - excludeDefaults does not seem to work * [MNG-3284] - Cached plugins are used, even when the specifically declared * [MNG-3314] - offline build not running, when having SNAPSHOT dependencies * [MNG-3621] - site url inheritance broken for UNC paths * [MNG-3628] - When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository * [MNG-3641] - Lack of error checks on profiles * [MNG-3645] - Maven doesn't do strict model validation for POMs in the current reactor * [MNG-3719] - [regression] plugin execution ordering no longer POM ordered in 2.0.9 * [MNG-3757] - Setting M2_HOME to nothing and running ant delets contents of the current folder * [MNG-3769] - [regression] Excluding relocated transitive dependencies does not work * [MNG-3776] - Namespace misspelled in settings.xml * [MNG-3808] - Execution order of report plugins is arbitrary if inheritance is involved * [MNG-3810] - [regression] Null Pointer Exception when Activation Profile Property is Empty * [MNG-3811] - Report plugins don't inherit configuration * [MNG-3899] - Inheritance does not merge extensions with same gid and aid * [MNG-3906] - Project-level plugin dependencies are in random order after merging * [MNG-3920] - Problem using velocity component * [MNG-3930] - mvn.bat doesn't handle ampersand in Windows user name properly * [MNG-3933] - Profiles.xml does not pickup OS family * [MNG-3940] - Interpolation of environment variables is not case-insensitive on Windows * [MNG-3948] - Remote repos defined by profiles outside of settings.xml are not used to resolve parent POMs * [MNG-3974] - New mirror syntax is not stopping on first match * [MNG-4016] - Properties with the prefix project/pom are not interpolated from the properties section * [MNG-4023] - Profiles from parent POM are injected multiple times if parent is part of reactor build * [MNG-4026] - [regression] Order of project class path does not match POM order during reactor build * [MNG-4032] - Test jar dependency not available for for main classes in multi module builds * [MNG-4043] - Resolve or rollback WebDAV wagon deployment issue where hostname is improperly extracted from URL * [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur with 2.0.10 * [MNG-4079] - Duplicate error messages * [MNG-4084] - Unnecessary Warning for an activate profile in child project * [MNG-4086] - [regression] Explicitly using plugin metaversions crashes plugin manager * [MNG-4087] - Percent encoded characters in file URLs are not decoded upon
Re: [vote] Maven 2.1.0
+1, works fine for me John Casey wrote: Hi everyone, It looks like Maven 2.1.0 is ready to release. You can try the binaries here: http://tinyurl.com/maven-2-1-0-vote (https://repository.apache.org/content/repositories/maven-staging-511ea882714d8b/org/apache/maven/apache-maven/2.1.0/) We've resolved 85 issues for this release (enumerated at the end of this message): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14587 Vote's open for 72 hours. Please cast your vote: [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, -john === Release Notes - Maven 2 - Version 2.1.0 ** Sub-task * [MNG-4025] - Prominently document opt-out setting for parallel artifact resolution for users * [MNG-4042] - Use plexus-sec-dispatcher 1.0 in Maven core when it is released ** Bug * [MNG-1349] - openssl checksums are not accepted by maven * [MNG-1585] - debug logging from wagon not shown in debug mode * [MNG-1992] - CLI -D should override properties in settings.xml * [MNG-1999] - Reporting inheritance does not work properly * [MNG-2432] - Apache and Mojo plugins take precendence over plugins in the pom. * [MNG-2433] - Maven looks for snapshots in offline mode * [MNG-2605] - Profiles in profiles.xml are active by default * [MNG-2668] - Plugin dependencies should be considered when the reactor creates the build order list * [MNG-2690] - DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly * [MNG-2695] - -o makes build fail for snapshot plugins * [MNG-2720] - Multiproject dependencies not accurate for project.compileClasspathElements when run from root project * [MNG-3023] - Reactor projects should be included in dependency resolution * [MNG-3057] - properties not expanded in generated POMs when building A/B/C nested projects * [MNG-3139] - The skin does not exist: Unable to determine the release version * [MNG-3217] - a plugin's dependencies can influence other plugins in a build * [MNG-3228] - Maven profile activation does not work when profile is defined in inherited 'parent' pom * [MNG-3271] - excludeDefaults does not seem to work * [MNG-3284] - Cached plugins are used, even when the specifically declared * [MNG-3314] - offline build not running, when having SNAPSHOT dependencies * [MNG-3621] - site url inheritance broken for UNC paths * [MNG-3628] - When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository * [MNG-3641] - Lack of error checks on profiles * [MNG-3645] - Maven doesn't do strict model validation for POMs in the current reactor * [MNG-3719] - [regression] plugin execution ordering no longer POM ordered in 2.0.9 * [MNG-3757] - Setting M2_HOME to nothing and running ant delets contents of the current folder * [MNG-3769] - [regression] Excluding relocated transitive dependencies does not work * [MNG-3776] - Namespace misspelled in settings.xml * [MNG-3808] - Execution order of report plugins is arbitrary if inheritance is involved * [MNG-3810] - [regression] Null Pointer Exception when Activation Profile Property is Empty * [MNG-3811] - Report plugins don't inherit configuration * [MNG-3899] - Inheritance does not merge extensions with same gid and aid * [MNG-3906] - Project-level plugin dependencies are in random order after merging * [MNG-3920] - Problem using velocity component * [MNG-3930] - mvn.bat doesn't handle ampersand in Windows user name properly * [MNG-3933] - Profiles.xml does not pickup OS family * [MNG-3940] - Interpolation of environment variables is not case-insensitive on Windows * [MNG-3948] - Remote repos defined by profiles outside of settings.xml are not used to resolve parent POMs * [MNG-3974] - New mirror syntax is not stopping on first match * [MNG-4016] - Properties with the prefix project/pom are not interpolated from the properties section * [MNG-4023] - Profiles from parent POM are injected multiple times if parent is part of reactor build * [MNG-4026] - [regression] Order of project class path does not match POM order during reactor build * [MNG-4032] - Test jar dependency not available for for main classes in multi module builds * [MNG-4043] - Resolve or rollback WebDAV wagon deployment issue where hostname is improperly extracted from URL * [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur with 2.0.10 * [MNG-4079] - Duplicate error messages * [MNG-4084] - Unnecessary Warning for an activate profile in child project * [MNG-4086] - [regression] Explicitly using plugin metaversions crashes plugin manager * [MNG-4087] - Percent encoded characters in file URLs are not decoded upon deployment ** Improvement * [MNG-1830] - add a 'compiled on timestamp' label when maven 2 is invoked
Re: [vote] Maven 2.1.0
John Casey wrote: It looks like Maven 2.1.0 is ready to release. +1, thanks John! Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] Maven 2.1.0
+1 I have build my current applications with it with success. /Anders On 19/03/2009, at 01.12, John Casey wrote: Hi everyone, It looks like Maven 2.1.0 is ready to release. You can try the binaries here: http://tinyurl.com/maven-2-1-0-vote (https://repository.apache.org/content/repositories/maven-staging-511ea882714d8b/org/apache/maven/apache-maven/2.1.0/ ) We've resolved 85 issues for this release (enumerated at the end of this message): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14587 Vote's open for 72 hours. Please cast your vote: [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, -john === Release Notes - Maven 2 - Version 2.1.0 ** Sub-task * [MNG-4025] - Prominently document opt-out setting for parallel artifact resolution for users * [MNG-4042] - Use plexus-sec-dispatcher 1.0 in Maven core when it is released ** Bug * [MNG-1349] - openssl checksums are not accepted by maven * [MNG-1585] - debug logging from wagon not shown in debug mode * [MNG-1992] - CLI -D should override properties in settings.xml * [MNG-1999] - Reporting inheritance does not work properly * [MNG-2432] - Apache and Mojo plugins take precendence over plugins in the pom. * [MNG-2433] - Maven looks for snapshots in offline mode * [MNG-2605] - Profiles in profiles.xml are active by default * [MNG-2668] - Plugin dependencies should be considered when the reactor creates the build order list * [MNG-2690] - DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly * [MNG-2695] - -o makes build fail for snapshot plugins * [MNG-2720] - Multiproject dependencies not accurate for project.compileClasspathElements when run from root project * [MNG-3023] - Reactor projects should be included in dependency resolution * [MNG-3057] - properties not expanded in generated POMs when building A/B/C nested projects * [MNG-3139] - The skin does not exist: Unable to determine the release version * [MNG-3217] - a plugin's dependencies can influence other plugins in a build * [MNG-3228] - Maven profile activation does not work when profile is defined in inherited 'parent' pom * [MNG-3271] - excludeDefaults does not seem to work * [MNG-3284] - Cached plugins are used, even when the specifically declared * [MNG-3314] - offline build not running, when having SNAPSHOT dependencies * [MNG-3621] - site url inheritance broken for UNC paths * [MNG-3628] - When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository * [MNG-3641] - Lack of error checks on profiles * [MNG-3645] - Maven doesn't do strict model validation for POMs in the current reactor * [MNG-3719] - [regression] plugin execution ordering no longer POM ordered in 2.0.9 * [MNG-3757] - Setting M2_HOME to nothing and running ant delets contents of the current folder * [MNG-3769] - [regression] Excluding relocated transitive dependencies does not work * [MNG-3776] - Namespace misspelled in settings.xml * [MNG-3808] - Execution order of report plugins is arbitrary if inheritance is involved * [MNG-3810] - [regression] Null Pointer Exception when Activation Profile Property is Empty * [MNG-3811] - Report plugins don't inherit configuration * [MNG-3899] - Inheritance does not merge extensions with same gid and aid * [MNG-3906] - Project-level plugin dependencies are in random order after merging * [MNG-3920] - Problem using velocity component * [MNG-3930] - mvn.bat doesn't handle ampersand in Windows user name properly * [MNG-3933] - Profiles.xml does not pickup OS family * [MNG-3940] - Interpolation of environment variables is not case- insensitive on Windows * [MNG-3948] - Remote repos defined by profiles outside of settings.xml are not used to resolve parent POMs * [MNG-3974] - New mirror syntax is not stopping on first match * [MNG-4016] - Properties with the prefix project/pom are not interpolated from the properties section * [MNG-4023] - Profiles from parent POM are injected multiple times if parent is part of reactor build * [MNG-4026] - [regression] Order of project class path does not match POM order during reactor build * [MNG-4032] - Test jar dependency not available for for main classes in multi module builds * [MNG-4043] - Resolve or rollback WebDAV wagon deployment issue where hostname is improperly extracted from URL * [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur with 2.0.10 * [MNG-4079] - Duplicate error messages * [MNG-4084] - Unnecessary Warning for an activate profile in child project * [MNG-4086] - [regression] Explicitly using plugin metaversions crashes plugin manager * [MNG-4087] - Percent encoded characters in file URLs are not decoded upon deployment ** Improvement * [MNG-1830] - add a
Re: [vote] Maven 2.1.0
Hi all, Cactus, Cargo builds fine. +1 from me. Cheers, Petar. 2009/3/19 Anders Kristian Andersen anders.kristian.ander...@gmail.com +1 I have build my current applications with it with success. /Anders On 19/03/2009, at 01.12, John Casey wrote: Hi everyone, It looks like Maven 2.1.0 is ready to release. You can try the binaries here: http://tinyurl.com/maven-2-1-0-vote ( https://repository.apache.org/content/repositories/maven-staging-511ea882714d8b/org/apache/maven/apache-maven/2.1.0/ ) We've resolved 85 issues for this release (enumerated at the end of this message): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14587 Vote's open for 72 hours. Please cast your vote: [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, -john === Release Notes - Maven 2 - Version 2.1.0 ** Sub-task * [MNG-4025] - Prominently document opt-out setting for parallel artifact resolution for users * [MNG-4042] - Use plexus-sec-dispatcher 1.0 in Maven core when it is released ** Bug * [MNG-1349] - openssl checksums are not accepted by maven * [MNG-1585] - debug logging from wagon not shown in debug mode * [MNG-1992] - CLI -D should override properties in settings.xml * [MNG-1999] - Reporting inheritance does not work properly * [MNG-2432] - Apache and Mojo plugins take precendence over plugins in the pom. * [MNG-2433] - Maven looks for snapshots in offline mode * [MNG-2605] - Profiles in profiles.xml are active by default * [MNG-2668] - Plugin dependencies should be considered when the reactor creates the build order list * [MNG-2690] - DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly * [MNG-2695] - -o makes build fail for snapshot plugins * [MNG-2720] - Multiproject dependencies not accurate for project.compileClasspathElements when run from root project * [MNG-3023] - Reactor projects should be included in dependency resolution * [MNG-3057] - properties not expanded in generated POMs when building A/B/C nested projects * [MNG-3139] - The skin does not exist: Unable to determine the release version * [MNG-3217] - a plugin's dependencies can influence other plugins in a build * [MNG-3228] - Maven profile activation does not work when profile is defined in inherited 'parent' pom * [MNG-3271] - excludeDefaults does not seem to work * [MNG-3284] - Cached plugins are used, even when the specifically declared * [MNG-3314] - offline build not running, when having SNAPSHOT dependencies * [MNG-3621] - site url inheritance broken for UNC paths * [MNG-3628] - When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository * [MNG-3641] - Lack of error checks on profiles * [MNG-3645] - Maven doesn't do strict model validation for POMs in the current reactor * [MNG-3719] - [regression] plugin execution ordering no longer POM ordered in 2.0.9 * [MNG-3757] - Setting M2_HOME to nothing and running ant delets contents of the current folder * [MNG-3769] - [regression] Excluding relocated transitive dependencies does not work * [MNG-3776] - Namespace misspelled in settings.xml * [MNG-3808] - Execution order of report plugins is arbitrary if inheritance is involved * [MNG-3810] - [regression] Null Pointer Exception when Activation Profile Property is Empty * [MNG-3811] - Report plugins don't inherit configuration * [MNG-3899] - Inheritance does not merge extensions with same gid and aid * [MNG-3906] - Project-level plugin dependencies are in random order after merging * [MNG-3920] - Problem using velocity component * [MNG-3930] - mvn.bat doesn't handle ampersand in Windows user name properly * [MNG-3933] - Profiles.xml does not pickup OS family * [MNG-3940] - Interpolation of environment variables is not case-insensitive on Windows * [MNG-3948] - Remote repos defined by profiles outside of settings.xml are not used to resolve parent POMs * [MNG-3974] - New mirror syntax is not stopping on first match * [MNG-4016] - Properties with the prefix project/pom are not interpolated from the properties section * [MNG-4023] - Profiles from parent POM are injected multiple times if parent is part of reactor build * [MNG-4026] - [regression] Order of project class path does not match POM order during reactor build * [MNG-4032] - Test jar dependency not available for for main classes in multi module builds * [MNG-4043] - Resolve or rollback WebDAV wagon deployment issue where hostname is improperly extracted from URL * [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur with 2.0.10 * [MNG-4079] - Duplicate error messages * [MNG-4084] - Unnecessary Warning for an activate profile in child project * [MNG-4086] - [regression] Explicitly using plugin metaversions crashes plugin manager * [MNG-4087] -
Re: [vote] Maven 2.1.0
+1 Hervé Le jeudi 19 mars 2009, John Casey a écrit : Hi everyone, It looks like Maven 2.1.0 is ready to release. You can try the binaries here: http://tinyurl.com/maven-2-1-0-vote (https://repository.apache.org/content/repositories/maven-staging-511ea8827 14d8b/org/apache/maven/apache-maven/2.1.0/) We've resolved 85 issues for this release (enumerated at the end of this message): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName= Htmlversion=14587 Vote's open for 72 hours. Please cast your vote: [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, -john === Release Notes - Maven 2 - Version 2.1.0 ** Sub-task * [MNG-4025] - Prominently document opt-out setting for parallel artifact resolution for users * [MNG-4042] - Use plexus-sec-dispatcher 1.0 in Maven core when it is released ** Bug * [MNG-1349] - openssl checksums are not accepted by maven * [MNG-1585] - debug logging from wagon not shown in debug mode * [MNG-1992] - CLI -D should override properties in settings.xml * [MNG-1999] - Reporting inheritance does not work properly * [MNG-2432] - Apache and Mojo plugins take precendence over plugins in the pom. * [MNG-2433] - Maven looks for snapshots in offline mode * [MNG-2605] - Profiles in profiles.xml are active by default * [MNG-2668] - Plugin dependencies should be considered when the reactor creates the build order list * [MNG-2690] - DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly * [MNG-2695] - -o makes build fail for snapshot plugins * [MNG-2720] - Multiproject dependencies not accurate for project.compileClasspathElements when run from root project * [MNG-3023] - Reactor projects should be included in dependency resolution * [MNG-3057] - properties not expanded in generated POMs when building A/B/C nested projects * [MNG-3139] - The skin does not exist: Unable to determine the release version * [MNG-3217] - a plugin's dependencies can influence other plugins in a build * [MNG-3228] - Maven profile activation does not work when profile is defined in inherited 'parent' pom * [MNG-3271] - excludeDefaults does not seem to work * [MNG-3284] - Cached plugins are used, even when the specifically declared * [MNG-3314] - offline build not running, when having SNAPSHOT dependencies * [MNG-3621] - site url inheritance broken for UNC paths * [MNG-3628] - When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository * [MNG-3641] - Lack of error checks on profiles * [MNG-3645] - Maven doesn't do strict model validation for POMs in the current reactor * [MNG-3719] - [regression] plugin execution ordering no longer POM ordered in 2.0.9 * [MNG-3757] - Setting M2_HOME to nothing and running ant delets contents of the current folder * [MNG-3769] - [regression] Excluding relocated transitive dependencies does not work * [MNG-3776] - Namespace misspelled in settings.xml * [MNG-3808] - Execution order of report plugins is arbitrary if inheritance is involved * [MNG-3810] - [regression] Null Pointer Exception when Activation Profile Property is Empty * [MNG-3811] - Report plugins don't inherit configuration * [MNG-3899] - Inheritance does not merge extensions with same gid and aid * [MNG-3906] - Project-level plugin dependencies are in random order after merging * [MNG-3920] - Problem using velocity component * [MNG-3930] - mvn.bat doesn't handle ampersand in Windows user name properly * [MNG-3933] - Profiles.xml does not pickup OS family * [MNG-3940] - Interpolation of environment variables is not case-insensitive on Windows * [MNG-3948] - Remote repos defined by profiles outside of settings.xml are not used to resolve parent POMs * [MNG-3974] - New mirror syntax is not stopping on first match * [MNG-4016] - Properties with the prefix project/pom are not interpolated from the properties section * [MNG-4023] - Profiles from parent POM are injected multiple times if parent is part of reactor build * [MNG-4026] - [regression] Order of project class path does not match POM order during reactor build * [MNG-4032] - Test jar dependency not available for for main classes in multi module builds * [MNG-4043] - Resolve or rollback WebDAV wagon deployment issue where hostname is improperly extracted from URL * [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur with 2.0.10 * [MNG-4079] - Duplicate error messages * [MNG-4084] - Unnecessary Warning for an activate profile in child project * [MNG-4086] - [regression] Explicitly using plugin metaversions crashes plugin manager * [MNG-4087] - Percent encoded characters in file URLs are not decoded
Re: [vote] Maven 2.1.0
non-binding +4 ;-), having used all RCs and this version without any problem on a large inhouse project. John Casey wrote: Hi everyone, It looks like Maven 2.1.0 is ready to release. You can try the binaries here: http://tinyurl.com/maven-2-1-0-vote (https://repository.apache.org/content/repositories/maven-staging-511ea882714d8b/org/apache/maven/apache-maven/2.1.0/) We've resolved 85 issues for this release (enumerated at the end of this message): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14587 Vote's open for 72 hours. Please cast your vote: [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, -john === Release Notes - Maven 2 - Version 2.1.0 ** Sub-task * [MNG-4025] - Prominently document opt-out setting for parallel artifact resolution for users * [MNG-4042] - Use plexus-sec-dispatcher 1.0 in Maven core when it is released ** Bug * [MNG-1349] - openssl checksums are not accepted by maven * [MNG-1585] - debug logging from wagon not shown in debug mode * [MNG-1992] - CLI -D should override properties in settings.xml * [MNG-1999] - Reporting inheritance does not work properly * [MNG-2432] - Apache and Mojo plugins take precendence over plugins in the pom. * [MNG-2433] - Maven looks for snapshots in offline mode * [MNG-2605] - Profiles in profiles.xml are active by default * [MNG-2668] - Plugin dependencies should be considered when the reactor creates the build order list * [MNG-2690] - DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly * [MNG-2695] - -o makes build fail for snapshot plugins * [MNG-2720] - Multiproject dependencies not accurate for project.compileClasspathElements when run from root project * [MNG-3023] - Reactor projects should be included in dependency resolution * [MNG-3057] - properties not expanded in generated POMs when building A/B/C nested projects * [MNG-3139] - The skin does not exist: Unable to determine the release version * [MNG-3217] - a plugin's dependencies can influence other plugins in a build * [MNG-3228] - Maven profile activation does not work when profile is defined in inherited 'parent' pom * [MNG-3271] - excludeDefaults does not seem to work * [MNG-3284] - Cached plugins are used, even when the specifically declared * [MNG-3314] - offline build not running, when having SNAPSHOT dependencies * [MNG-3621] - site url inheritance broken for UNC paths * [MNG-3628] - When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository * [MNG-3641] - Lack of error checks on profiles * [MNG-3645] - Maven doesn't do strict model validation for POMs in the current reactor * [MNG-3719] - [regression] plugin execution ordering no longer POM ordered in 2.0.9 * [MNG-3757] - Setting M2_HOME to nothing and running ant delets contents of the current folder * [MNG-3769] - [regression] Excluding relocated transitive dependencies does not work * [MNG-3776] - Namespace misspelled in settings.xml * [MNG-3808] - Execution order of report plugins is arbitrary if inheritance is involved * [MNG-3810] - [regression] Null Pointer Exception when Activation Profile Property is Empty * [MNG-3811] - Report plugins don't inherit configuration * [MNG-3899] - Inheritance does not merge extensions with same gid and aid * [MNG-3906] - Project-level plugin dependencies are in random order after merging * [MNG-3920] - Problem using velocity component * [MNG-3930] - mvn.bat doesn't handle ampersand in Windows user name properly * [MNG-3933] - Profiles.xml does not pickup OS family * [MNG-3940] - Interpolation of environment variables is not case-insensitive on Windows * [MNG-3948] - Remote repos defined by profiles outside of settings.xml are not used to resolve parent POMs * [MNG-3974] - New mirror syntax is not stopping on first match * [MNG-4016] - Properties with the prefix project/pom are not interpolated from the properties section * [MNG-4023] - Profiles from parent POM are injected multiple times if parent is part of reactor build * [MNG-4026] - [regression] Order of project class path does not match POM order during reactor build * [MNG-4032] - Test jar dependency not available for for main classes in multi module builds * [MNG-4043] - Resolve or rollback WebDAV wagon deployment issue where hostname is improperly extracted from URL * [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur with 2.0.10 * [MNG-4079] - Duplicate error messages * [MNG-4084] - Unnecessary Warning for an activate profile in child project * [MNG-4086] - [regression] Explicitly using plugin metaversions crashes plugin
Re: [vote] Maven 2.1.0
John Casey wrote: It looks like Maven 2.1.0 is ready to release. I noticed that the maven-metadata*.xml files generated by 2.1.0 include the schema location and point at http://maven.apache.org/xsd/metadata-1.0.0.xsd which is currently non-existent. I assume this XSD will be deployed once the vote has passed? Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] Maven 2.1.0
+1 (Great Job) Thanks!! -- Olivier 2009/3/19 John Casey jdca...@commonjava.org: Hi everyone, It looks like Maven 2.1.0 is ready to release. You can try the binaries here: http://tinyurl.com/maven-2-1-0-vote (https://repository.apache.org/content/repositories/maven-staging-511ea882714d8b/org/apache/maven/apache-maven/2.1.0/) We've resolved 85 issues for this release (enumerated at the end of this message): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14587 Vote's open for 72 hours. Please cast your vote: [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, -john === Release Notes - Maven 2 - Version 2.1.0 ** Sub-task * [MNG-4025] - Prominently document opt-out setting for parallel artifact resolution for users * [MNG-4042] - Use plexus-sec-dispatcher 1.0 in Maven core when it is released ** Bug * [MNG-1349] - openssl checksums are not accepted by maven * [MNG-1585] - debug logging from wagon not shown in debug mode * [MNG-1992] - CLI -D should override properties in settings.xml * [MNG-1999] - Reporting inheritance does not work properly * [MNG-2432] - Apache and Mojo plugins take precendence over plugins in the pom. * [MNG-2433] - Maven looks for snapshots in offline mode * [MNG-2605] - Profiles in profiles.xml are active by default * [MNG-2668] - Plugin dependencies should be considered when the reactor creates the build order list * [MNG-2690] - DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly * [MNG-2695] - -o makes build fail for snapshot plugins * [MNG-2720] - Multiproject dependencies not accurate for project.compileClasspathElements when run from root project * [MNG-3023] - Reactor projects should be included in dependency resolution * [MNG-3057] - properties not expanded in generated POMs when building A/B/C nested projects * [MNG-3139] - The skin does not exist: Unable to determine the release version * [MNG-3217] - a plugin's dependencies can influence other plugins in a build * [MNG-3228] - Maven profile activation does not work when profile is defined in inherited 'parent' pom * [MNG-3271] - excludeDefaults does not seem to work * [MNG-3284] - Cached plugins are used, even when the specifically declared * [MNG-3314] - offline build not running, when having SNAPSHOT dependencies * [MNG-3621] - site url inheritance broken for UNC paths * [MNG-3628] - When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository * [MNG-3641] - Lack of error checks on profiles * [MNG-3645] - Maven doesn't do strict model validation for POMs in the current reactor * [MNG-3719] - [regression] plugin execution ordering no longer POM ordered in 2.0.9 * [MNG-3757] - Setting M2_HOME to nothing and running ant delets contents of the current folder * [MNG-3769] - [regression] Excluding relocated transitive dependencies does not work * [MNG-3776] - Namespace misspelled in settings.xml * [MNG-3808] - Execution order of report plugins is arbitrary if inheritance is involved * [MNG-3810] - [regression] Null Pointer Exception when Activation Profile Property is Empty * [MNG-3811] - Report plugins don't inherit configuration * [MNG-3899] - Inheritance does not merge extensions with same gid and aid * [MNG-3906] - Project-level plugin dependencies are in random order after merging * [MNG-3920] - Problem using velocity component * [MNG-3930] - mvn.bat doesn't handle ampersand in Windows user name properly * [MNG-3933] - Profiles.xml does not pickup OS family * [MNG-3940] - Interpolation of environment variables is not case-insensitive on Windows * [MNG-3948] - Remote repos defined by profiles outside of settings.xml are not used to resolve parent POMs * [MNG-3974] - New mirror syntax is not stopping on first match * [MNG-4016] - Properties with the prefix project/pom are not interpolated from the properties section * [MNG-4023] - Profiles from parent POM are injected multiple times if parent is part of reactor build * [MNG-4026] - [regression] Order of project class path does not match POM order during reactor build * [MNG-4032] - Test jar dependency not available for for main classes in multi module builds * [MNG-4043] - Resolve or rollback WebDAV wagon deployment issue where hostname is improperly extracted from URL * [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur with 2.0.10 * [MNG-4079] - Duplicate error messages * [MNG-4084] - Unnecessary Warning for an activate profile in child project * [MNG-4086] - [regression] Explicitly using plugin metaversions crashes plugin manager * [MNG-4087] - Percent encoded characters in file URLs are not decoded upon deployment ** Improvement * [MNG-1830] - add a 'compiled on
Re: [vote] Maven 2.1.0
*sigh* I'll make sure it's deployed. Benjamin Bentmann wrote: John Casey wrote: It looks like Maven 2.1.0 is ready to release. I noticed that the maven-metadata*.xml files generated by 2.1.0 include the schema location and point at http://maven.apache.org/xsd/metadata-1.0.0.xsd which is currently non-existent. I assume this XSD will be deployed once the vote has passed? Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: metadata schema was: [vote] Maven 2.1.0
Hmm, why was this added? We don't use a validating parser, and nobody really edits them by hand. With network traffic on these files at a premium for downloads I would think it's best left out to save some bytes. (I don't consider it a blocker to the vote though, and with regard to my vote, I'm still testing :) - Brett On 20/03/2009, at 8:26 AM, Benjamin Bentmann wrote: John Casey wrote: It looks like Maven 2.1.0 is ready to release. I noticed that the maven-metadata*.xml files generated by 2.1.0 include the schema location and point at http://maven.apache.org/xsd/metadata-1.0.0.xsd which is currently non-existent. I assume this XSD will be deployed once the vote has passed? Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] Maven 2.1.0
Hi Vincent, I'm still trying to get XWiki's dependencies to resolve out on grid.sonatype.org...the latest missing dependency is: com.sun.xml.bind:jaxb-impl:jar:2.1.10 I was wondering whether this is supposed to be available in one of the xwiki repositories, or if you have it installed somewhere else. I see versions up to 2.1.9 out on repository.sonatype.org (in the proxy repo for central), but not 2.1.10 (at least I haven't found it yet). Any thoughts? -john Vincent Massol wrote: It's failing for XWiki's build... Are you still running XWiki's build on your hudson ci btw? It's failing with the gwt maven plugin. It works fine with 2.1.0-M1 though. Ping me if you need help to reproduce it. Thanks -Vincent On Mar 19, 2009, at 1:12 AM, John Casey wrote: Hi everyone, It looks like Maven 2.1.0 is ready to release. You can try the binaries here: http://tinyurl.com/maven-2-1-0-vote (https://repository.apache.org/content/repositories/maven-staging-511ea882714d8b/org/apache/maven/apache-maven/2.1.0/) We've resolved 85 issues for this release (enumerated at the end of this message): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14587 Vote's open for 72 hours. Please cast your vote: [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, -john === Release Notes - Maven 2 - Version 2.1.0 ** Sub-task * [MNG-4025] - Prominently document opt-out setting for parallel artifact resolution for users * [MNG-4042] - Use plexus-sec-dispatcher 1.0 in Maven core when it is released ** Bug * [MNG-1349] - openssl checksums are not accepted by maven * [MNG-1585] - debug logging from wagon not shown in debug mode * [MNG-1992] - CLI -D should override properties in settings.xml * [MNG-1999] - Reporting inheritance does not work properly * [MNG-2432] - Apache and Mojo plugins take precendence over plugins in the pom. * [MNG-2433] - Maven looks for snapshots in offline mode * [MNG-2605] - Profiles in profiles.xml are active by default * [MNG-2668] - Plugin dependencies should be considered when the reactor creates the build order list * [MNG-2690] - DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly * [MNG-2695] - -o makes build fail for snapshot plugins * [MNG-2720] - Multiproject dependencies not accurate for project.compileClasspathElements when run from root project * [MNG-3023] - Reactor projects should be included in dependency resolution * [MNG-3057] - properties not expanded in generated POMs when building A/B/C nested projects * [MNG-3139] - The skin does not exist: Unable to determine the release version * [MNG-3217] - a plugin's dependencies can influence other plugins in a build * [MNG-3228] - Maven profile activation does not work when profile is defined in inherited 'parent' pom * [MNG-3271] - excludeDefaults does not seem to work * [MNG-3284] - Cached plugins are used, even when the specifically declared * [MNG-3314] - offline build not running, when having SNAPSHOT dependencies * [MNG-3621] - site url inheritance broken for UNC paths * [MNG-3628] - When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository * [MNG-3641] - Lack of error checks on profiles * [MNG-3645] - Maven doesn't do strict model validation for POMs in the current reactor * [MNG-3719] - [regression] plugin execution ordering no longer POM ordered in 2.0.9 * [MNG-3757] - Setting M2_HOME to nothing and running ant delets contents of the current folder * [MNG-3769] - [regression] Excluding relocated transitive dependencies does not work * [MNG-3776] - Namespace misspelled in settings.xml * [MNG-3808] - Execution order of report plugins is arbitrary if inheritance is involved * [MNG-3810] - [regression] Null Pointer Exception when Activation Profile Property is Empty * [MNG-3811] - Report plugins don't inherit configuration * [MNG-3899] - Inheritance does not merge extensions with same gid and aid * [MNG-3906] - Project-level plugin dependencies are in random order after merging * [MNG-3920] - Problem using velocity component * [MNG-3930] - mvn.bat doesn't handle ampersand in Windows user name properly * [MNG-3933] - Profiles.xml does not pickup OS family * [MNG-3940] - Interpolation of environment variables is not case-insensitive on Windows * [MNG-3948] - Remote repos defined by profiles outside of settings.xml are not used to resolve parent POMs * [MNG-3974] - New mirror syntax is not stopping on first match * [MNG-4016] - Properties with the prefix project/pom are not interpolated from the properties section * [MNG-4023] - Profiles from parent POM are injected multiple times if parent is part of reactor build * [MNG-4026] - [regression] Order of project class path does not match POM order during reactor build *
Re: metadata schema was: [vote] Maven 2.1.0
I haven't added anything that might change it; I'm sort of assuming it's something the new modello was adding...isn't it? -j Brett Porter wrote: Hmm, why was this added? We don't use a validating parser, and nobody really edits them by hand. With network traffic on these files at a premium for downloads I would think it's best left out to save some bytes. (I don't consider it a blocker to the vote though, and with regard to my vote, I'm still testing :) - Brett On 20/03/2009, at 8:26 AM, Benjamin Bentmann wrote: John Casey wrote: It looks like Maven 2.1.0 is ready to release. I noticed that the maven-metadata*.xml files generated by 2.1.0 include the schema location and point at http://maven.apache.org/xsd/metadata-1.0.0.xsd which is currently non-existent. I assume this XSD will be deployed once the vote has passed? Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: metadata schema was: [vote] Maven 2.1.0
That's my guess. Hervé? On 20/03/2009, at 10:47 AM, John Casey wrote: I haven't added anything that might change it; I'm sort of assuming it's something the new modello was adding...isn't it? -j Brett Porter wrote: Hmm, why was this added? We don't use a validating parser, and nobody really edits them by hand. With network traffic on these files at a premium for downloads I would think it's best left out to save some bytes. (I don't consider it a blocker to the vote though, and with regard to my vote, I'm still testing :) - Brett On 20/03/2009, at 8:26 AM, Benjamin Bentmann wrote: John Casey wrote: It looks like Maven 2.1.0 is ready to release. I noticed that the maven-metadata*.xml files generated by 2.1.0 include the schema location and point at http://maven.apache.org/xsd/metadata-1.0.0.xsd which is currently non-existent. I assume this XSD will be deployed once the vote has passed? Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/
Scope for compile only?
Is there a way to bring in a library only for compiling without making it part of the runtime (i.e., war dependency) or using transitive exclusions? Java 5 has source-level annotations and sometimes a dependency is only for compiling and has no runtime dependency. Is a new scope needed for this? Paul - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] Maven 2.1.0
+1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] Maven 2.1.0
On 19/03/2009, at 8:03 PM, Vincent Massol wrote: It's failing for XWiki's build... Are you still running XWiki's build on your hudson ci btw? It's failing with the gwt maven plugin. It works fine with 2.1.0-M1 though. Ping me if you need help to reproduce it. Can we get the error message? Like John, it's taking me a while to chase all the dependencies in weird locations to attempt the build. - Brett -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[jira] Subscription: Design Best Practices
Issue Subscription Filter: Design Best Practices (28 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles http://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques http://jira.codehaus.org/browse/MNG-612 MNG-1950Ability to introduce new lifecycles phases http://jira.codehaus.org/browse/MNG-1950 MNG-2584Rebuild on pom change http://jira.codehaus.org/browse/MNG-2584 MNG-139 server definitions should be reusable - review use of repository IDs http://jira.codehaus.org/browse/MNG-139 MNG-2125[doc] when and how to define plugins in a pom http://jira.codehaus.org/browse/MNG-2125 MNG-474 performance improvement for forked lifecycles http://jira.codehaus.org/browse/MNG-474 MNG-1381best practices: testing strategies http://jira.codehaus.org/browse/MNG-1381 MNG-1563how to write integration tests http://jira.codehaus.org/browse/MNG-1563 MNG-2381improved control over the repositories in the POM http://jira.codehaus.org/browse/MNG-2381 MNG-1931add a reportingManagement section http://jira.codehaus.org/browse/MNG-1931 MNG-1885Uniquely identify modules by module name and version number http://jira.codehaus.org/browse/MNG-1885 MNG-647 Allow Maven 2 to be monitored using JMX. http://jira.codehaus.org/browse/MNG-647 MNG-416 best practices: multiple profile deployments http://jira.codehaus.org/browse/MNG-416 MNG-367 best practices: multi-user installation http://jira.codehaus.org/browse/MNG-367 MNG-125 guarded mojo execution http://jira.codehaus.org/browse/MNG-125 MNG-1569Make build process info read-only to mojos, and provide mechanism for explicit out-params for mojos to declare http://jira.codehaus.org/browse/MNG-1569 MNG-41 best practices: site management http://jira.codehaus.org/browse/MNG-41 MNG-1441Starting thinking about a proper distributed repository mechanism a la CPAN http://jira.codehaus.org/browse/MNG-1441 MNG-657 possible chicken and egg problem with extensions http://jira.codehaus.org/browse/MNG-657 MNG-1867deprecate system scope, analyse other use cases http://jira.codehaus.org/browse/MNG-1867 MNG-868 Use uniform format for properties and other tags http://jira.codehaus.org/browse/MNG-868 MNG-1439Organization Object Model (OOM) http://jira.codehaus.org/browse/MNG-1439 MNG-1423best practices: setting up multi-module build http://jira.codehaus.org/browse/MNG-1423 MNG-1463best practices: plugin inheritance for a multi project build http://jira.codehaus.org/browse/MNG-1463 MNG-1425best practices: the location of configuration files vs resources http://jira.codehaus.org/browse/MNG-1425 MNG-1468best practices: version management in multi project builds http://jira.codehaus.org/browse/MNG-1468 MNG-1440Developer Object Model (DOM) http://jira.codehaus.org/browse/MNG-1440 You may edit this subscription at: http://jira.codehaus.org/secure/FilterSubscription!default.jspa?subId=10341filterId=11471 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Scope for compile only?
On Thu, Mar 19, 2009 at 7:25 PM, Paul Benedict pbened...@apache.org wrote: Is there a way to bring in a library only for compiling without making it part of the runtime (i.e., war dependency) or using transitive exclusions? Java 5 has source-level annotations and sometimes a dependency is only for compiling and has no runtime dependency. Is a new scope needed for this? It sounds like optionaltrue/optional would work. (It's not a scope, it's a separate element.) -- Wendy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
