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
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Jason van Zyl, Olivier Lamy, Arnaud
Héritier
I will promote the artifacts to the central repository and continue with
the release.
Benjamin
I'm updating to 2.2.1 but it still not working :(
2009/11/19 Stephane Nicoll
> Agreed. Try to upgrade to Maven 2.2.1
>
> On Thu, Nov 19, 2009 at 7:09 PM, Brian Fox wrote:
>
> > This is a user list problem first, second there isn't much info to go
> > on here, but someone you have a conflict on
Agreed. Try to upgrade to Maven 2.2.1
On Thu, Nov 19, 2009 at 7:09 PM, Brian Fox wrote:
> This is a user list problem first, second there isn't much info to go
> on here, but someone you have a conflict on the plexus-utils version
> it appears.
>
> On Thu, Nov 19, 2009 at 4:05 AM, Abdelouahab ZA
Brian Fox wrote:
I guess what I had in mind was given a single reactor build:
A : Jar
B: War but binds jar to a phase.
Will B always get the same version of the jar plugin as A?
No, the projects are handled independently regarding their build plugins.
For instance, if B doesn't lock down the
This is a user list problem first, second there isn't much info to go
on here, but someone you have a conflict on the plexus-utils version
it appears.
On Thu, Nov 19, 2009 at 4:05 AM, Abdelouahab ZALMATE
wrote:
> Aidez moi SVP.
>
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [
>> 2) what are the impacts to the plugin when it's run in multiple
>> lifecycles, or if the user binds it to a phase of some other
>> lifecycle? Would this cause the version to vary in unpredictable ways?
>
> Good questions, let's look closer at the edge cases:
>
I guess what I had in mind was giv
Hi Siarhei!
I'm still trying to figure our if JGit-core gets finally released or if we
should fork it and release it ourselfs. Once we have it on maven-central, I'll
commit maven-scm-providers-jgit into SVN.
We should look into Jira what other important bugs could be fixed easily. You
could su
We've tested it and it works.
What are the possibilities to have this released anytime soon?
Best regards,
Siarhei Dudzin
On Wed, Nov 18, 2009 at 3:23 PM, Siarhei Dudzin wrote:
> we are doing it anyway :)
>
> Regards,
> Siarhei
>
> On 18 Nov 2009 11:22, "Jason van Zyl" wrote:
>
> On 2009-11-1
Brian Fox wrote:
1) we included some plugins that are commonly used but aren't in a
lifecycle such as the dependency and enforcer plugins.
I know, if those are declared in the POM they have to have/inherit a
version or Maven 3.0 will output a warning.
In other words, what we consider "commo
2009/11/19 Benjamin Bentmann :
> Done.
>
> For the future, please remember to cc the result to the PMC as well (cf.
> step 9 of the [0]).
Ah ha, thanks, I missed that. Oh for a plugin to automate this process!
Mark
-
To unsubsc
Mark Hobson done:
The Maven Checkstyle Plugin has been released.
Can this get added to the next board report please.
Done.
For the future, please remember to cc the result to the PMC as well (cf.
step 9 of the [0]).
Benjamin
[0] http://maven.apache.org/developers/release/apache-release.
The Maven Checkstyle Plugin has been released.
Can this get added to the next board report please.
Cheers,
Mark
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.or
Aidez moi SVP.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] wysiwyf
[INFO] [wysiwyf-ria] Application
[INFO] [wysiwyf-web] Application
[INFO] [wysiwyf-config] Flex remoting service config
[INFO]
[
14 matches
Mail list logo
