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
htt
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.0-beta-8.
http://maven.apache.org/plugins/maven-release-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-release-plugin
2.0-beta-8
Release N
Hi,
The vote has passed with the following result.
+1 (binding) : Arnaud, Emmanuel, Olivier
+1 (non binding) : Remy, Mark
I will move artifacts to central and publish the web site.
Thanks,
--
Olivier
-
To unsubscribe, e-mail: [E
Mark Hobson wrote:
I haven't pursued this of recent since there was talk of overhauling
maven-artifact and the whole dependency resolution mechanism in
general with Mercury:
http://docs.codehaus.org/display/MAVEN/Mercury
AFAIK Mercury will supersede MNG-612 and provide customisable conflict
Hi folks,
there is a massive bug in the plexus-compiler-eclipse (svn trunk as
well as 1.5.1):
If the compiler issues a warning on some Java source file, the
resulting
class is not copied to the target directory. This leads to missing
classes
in the compileTest phase.
Also - du
Hi Andrew,
2008/10/30 Andrew Lee Rubinger <[EMAIL PROTECTED]>:
> Asking here on the dev-list because I would like to contribute to any of the
> points below if unaddressed.
>
> What is the current status of the ConflictResolver SPI as outlined in:
>
> * http://docs.codehaus.org/display/MAVEN/Confl
Asking here on the dev-list because I would like to contribute to any of
the points below if unaddressed.
What is the current status of the ConflictResolver SPI as outlined in:
* http://docs.codehaus.org/display/MAVEN/Conflict+Resolvers
* http://www.nabble.com/-m2--Conflict-resolvers-td10144607
