Hi Dennis,
2009/1/7 Dennis Lundberg denn...@apache.org:
Is it really a chicken and egg issue?
I think so. Imagine this use case:
0. clean repo
1. svn co tag/maven-stylus-skin-1.1 with the site.xml using 1.1
2. mvn -o site will fail: no download of maven-stylus-skin artifact.
I think it
+1 now
Thanks Brian!
Vincent
2009/1/7 Brian E. Fox bri...@reply.infinity.nu:
-1 since we need to have a link to privacy policy page using the Maven
Stylus Skin.
Site is restaged and tag is updated:
http://maven.apache.org/plugins/maven-clean-plugin-2.3/
I checked if the maven 2.1 / wsgen (1.11) mojo problem was fixed with
maven 3.0-alpha-1, but same problem ;-(
[DEBUG] jaxws:wsgen args: [-d,
C:\workspace-34\slib-erable-framework\target\classes, -cp,
It's not in the iteration for alpha-2 either, but if you want to try
and tackle this we can add it to the iteration.
We really need to focus on the POM specification and recent
regressions we can track. The version of the embedder in m2e is from
May so we are going to try and tackle things
It's not in the iteration for alpha-2 either, but if you want to try and
tackle this we can add it to the iteration.
Yes, it was a simple test case.
We really need to focus on the POM specification and recent regressions we
can track. The version of the embedder in m2e is from May so we are
And the other vote too I assume? ;-)
-Original Message-
From: Vincent Siveton [mailto:vincent.sive...@gmail.com]
Sent: Thursday, January 08, 2009 8:12 AM
To: Maven Developers List
Subject: Re: [vote] release maven-clean-plugin 2.3 and file-management
1.2.1
+1 now
Thanks Brian!
Vincent
Hi all,
I've been trying to write an enforcer plugin that will validate the SCM
information contained in a POM actually reflects the actual repository
location. I'm only concerned with SVN.
Basically I am trying to do is a svn info project.getBaseDir() and
compare the repository url that
take a look at buildhelper-maven-plugin, it has code dealing with svn
info output
BTW, perhaps we should ask svn provider to support svn info command.
file a JIRA is a good start
-D
On Thu, Jan 8, 2009 at 10:42 AM, Nord, James jn...@nds.com wrote:
Hi all,
I've been trying to write an
sorry, it should be buildnumber-maven-plugin
On Thu, Jan 8, 2009 at 10:51 AM, Dan Tran dant...@gmail.com wrote:
take a look at buildhelper-maven-plugin, it has code dealing with svn
info output
BTW, perhaps we should ask svn provider to support svn info command.
file a JIRA is a good start
This problem concerns issue MNG-3586 (which is planned for alpha-3)
It doesn't concern only WSGEN plugin but all plugins that use tools.jar
dependency with system scope
Henri Gomez a écrit :
It's not in the iteration for alpha-2 either, but if you want to try and
tackle this we can add it to
2009/1/8, Brian E. Fox bri...@reply.infinity.nu:
And the other vote too I assume? ;-)
I already voted for it.
Cheers,
Vincent
-Original Message-
From: Vincent Siveton [mailto:vincent.sive...@gmail.com]
Sent: Thursday, January 08, 2009 8:12 AM
To: Maven Developers List
On 8-Jan-09, at 10:28 AM, Henri Gomez wrote:
It's not in the iteration for alpha-2 either, but if you want to
try and
tackle this we can add it to the iteration.
Yes, it was a simple test case.
We really need to focus on the POM specification and recent
regressions we
can track. The
+1
Brian E. Fox wrote:
Another smallish release that's been waiting a while. I'm going to work
with Oleg next week to have the dependency plugin use mercury so I'd
like to get the current fixes out in a stable form first.
Release Notes:
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
14 matches
Mail list logo
