Issue Subscription
Filter: Design & Best Practices (37 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
You need to put them in a separate tag and use a different
id. If you don't specify an execution, then it uses the default one and
will merge the config.
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Jochen Kuhnle
Sent: Thursday, November 23, 2006 8:51 AM
To: dev@m
Hi,
I am writing some plugins that have list properties, e.g.:
allspecialetc.
I now want to have different configurations (through parents, profiles,
etc.), but when merging, Maven2 only keeps entries from one
configuration (see
DefaultPluginManager.buildTopDownMergedConfiguration).
On 11/23/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
We don't like to remove things for consistency but we're not zealots
about it. The originating project, if they wish, can have anything
removed. Generally if people make mistakes in deploying it's not
really a big deal to leave them there but
Hi,
We don't like to remove things for consistency but we're not zealots
about it. The originating project, if they wish, can have anything
removed. Generally if people make mistakes in deploying it's not
really a big deal to leave them there but in this case if the
incubator policy is no
Hi
After the cleanup in the maven-info-reports-plugin with respect to JarAnalyzer,
the dependencis report is broken with an error referring to the JarAnalyzer.
When running the report now I get the following:
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the pl
ugin
