Forwarding this question to dev list, since I don't really know.
To me, catalog descriptor [1] should not contain goals or properties elements,
but archetype descriptor [2] should have goals instead (it already has
properties).
Any objection if I remove goals and properties elements from catalo
Issue Subscription
Filter: Design & Best Practices (24 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
On 17/09/2010, at 2:23 AM, Jörg Schaible wrote:
> Hi Baptiste,
>
> Baptiste MATHUS wrote:
>
>> Well, from my understanding, this is not a regression.
>> What Paul says in the end
>>
> http://jira.codehaus.org/browse/MNG-4687?focusedCommentId=235494&page=com.atlassian.jira.plugin.system.issuet
An odd thing I'm noticing trying to release some multi-module projects with
M3 nightlies:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on
project smx3.core: Execution default-cli of goal
org.apache.maven.plugins:maven-release-plugin:2.0:pre
David Jencks wrote:
I get the same results with maven 2.2.1 and 3 beta 1.
3.0-beta-1 was yesterday, so I recommend to try 3.0-RC1:
https://repository.apache.org/content/repositories/maven-030/org/apache/maven/apache-maven/3.0-RC1/
If that also doesn't respect the offline mode, then I would a
I asked about this on the users list about a month ago and got no response.
I think the maven-remote-resources-plugin has a problem. When I build for the
first time in 24 hours with -o, I still get stuff like this:
[INFO] --- maven-remote-resources-plugin:1.0:process (default) @
geronimo-jetty
Benjamin I just found this problem : http://jira.codehaus.org/browse/MNG-4813
It is failing for all alpha/beta I tested thus it isn't a problem in RC itself.
It occurs with an old version of the jdocbook plugin we are always using in
GateIn and few others projects.
Arnaud Héritier
Software Factor
I am getting:
java.lang.ClassNotFoundException: javax.persistence.Entity
from spring context initialization. Class not found varies depending on
the order of spring dependencies, could be a Logger, etc.
Same build works fine under 2.2.1. and 3.0-beta-2
I will create an issue if manage to lo
+1
Thinking about it - I like the idea of a (for lack of a better name)
~/.m2/resolutions.xml that provides control over the resolver.
First thoughts that come to mind:
- missing or empty file - existing 2.x behaviour, -SNAPSHOTS resolved
across the board.
- profile based (optional?)
Maybe
+1
Hervé
Le mercredi 15 septembre 2010, Dennis Lundberg a écrit :
> Hi,
>
> We solved 1 issue:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12100&styleName=
> Html&version=16674
>
> There is still an issue left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset
Works fine here.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi there,
I've been updating my environment to release the Checkstyle plugin and
am having problems even deploying a snapshot. I've configured
settings.xml as specified [1] but still get:
[INFO] Error deploying artifact: Authorization failed: Access denied
to:
https://repository.apache.org/cont
I could do with this release too and am happy to perform it. Having a
few problems updating my environment though; I'll send a separate
mail.
Mark
On 13 September 2010 22:37, Olivier Lamy wrote:
> Hi,
> I will try to work on this at the end of the week (if no spare time issue :-)
> ).
>
> 2010
Fine here (tested on some corporate builds)
Thanks (good job !)
2010/9/15 Benjamin Bentmann :
> Hi,
>
> in preparation for the release of Apache Maven 3.0, the Maven team is
> seeking your help to discover regressions since Maven 2.x. Everybody
> interested in taking a preview of the upcoming rele
Dear All:
Sorry to bother, but just wanted to let you know that on:
http://maven.apache.org/archetype/maven-archetype-plugin/source-repository.html
I believe all references to:
http://svn.apache.org/viewvc/maven/archetype/tags/maven-archetype-2.0-alpha-5/maven-archetype-plugin
should actually
Hi Baptiste,
Baptiste MATHUS wrote:
> Well, from my understanding, this is not a regression.
> What Paul says in the end
>
http://jira.codehaus.org/browse/MNG-4687?focusedCommentId=235494&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-
tabpanel#action_235494is
> not a workaround,
Well, from my understanding, this is not a regression.
What Paul says in the end
http://jira.codehaus.org/browse/MNG-4687?focusedCommentId=235494&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_235494is
not a workaround, but the right way to go.
See also
https://cwik
On 9/16/10 11:12 AM, Benjamin Bentmann wrote:
> Justin Edelson wrote:
>
>> Any clues as to what we should be looking for?
>
> Well, I would hope that the Sling guys now best what makes their tests
> fail.
Indeed we do. In this case, what's making the tests fail is using a
different Maven version
Justin Edelson wrote:
Any clues as to what we should be looking for?
Well, I would hope that the Sling guys now best what makes their tests
fail. One thing I have seen in the past were projects having duplicate
classes/resources on their class path and having a subtle dependency on
their or
no problems here so far. I was able to run the assembly plugin ITs
without trouble, which is a change from beta-3...there seemed to be some
problem with passing expressions in on the command-line in beta-3.
At any rate, it looks good.
On 9/15/10 4:34 PM, Benjamin Bentmann wrote:
Hi,
in prepa
I have a plugin where I use the maven3 api.
maven-beta-2, maven-beta-1, maven-alpha-6/7, worked
maven-beta-3 gives
Caused by: java.lang.NullPointerException
at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:185)
at
org.so
Integration tests in the Apache Sling build are pretty consistently
failing on 3.0-RC1 and 3.0-beta-3 in two different modules. Both pass
consistently in 2.2.1.
To reproduce:
$ svn co http://svn.apache.org/repos/asf/sling/trunk
$ mvn clean install
In about 4 minutes (depending upon the state of y
+1
2010/9/15 Dennis Lundberg :
> Hi,
>
> We solved 1 issue:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12100&styleName=Html&version=16674
>
> There is still an issue left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=12100&status=1
>
> Staging repo
+1
Vincent
2010/9/15 Dennis Lundberg :
> Hi,
>
> We solved 1 issue:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12100&styleName=Html&version=16674
>
> There is still an issue left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=12100&status=1
>
> Sta
Brett Porter wrote:
>
> On 15/09/2010, at 2:26 PM, Mark Derricutt wrote:
>
>> Hey guys,
>>
>> I was wondering what was happening with the new release of the
>> maven-release-plugin? Things seemed to go quiet on that front this past
>> week or so...
>>
>> I see that the SCM plugin got released
+1
Seems to work fine for me.
On 09/15/2010 03:34 PM, Benjamin Bentmann wrote:
> Hi,
>
> in preparation for the release of Apache Maven 3.0, the Maven team is
> seeking your help to discover regressions since Maven 2.x. Everybody
> interested in taking a preview of the upcoming release for a test
+1
Emmanuel
On Wed, Sep 15, 2010 at 11:36 PM, Dennis Lundberg wrote:
> Hi,
>
> We solved 1 issue:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12100&styleName=Html&version=16674
>
> There is still an issue left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?re
Le Thu, 16 Sep 2010 11:53:45 +0200,
Tony Chemit a écrit :
> Le Wed, 15 Sep 2010 22:34:47 +0200,
> Benjamin Bentmann a écrit :
>
> works fine on our project (install + site)
+ release :) (I just made one)
>
> Tony
>
> ps: my first mail was lost ?
>
> > Hi,
> >
> > in preparation for the rele
I agree with Baptiste that the explanation is ambiguous. I understand the
same thing.
Regards
Jeff MAURY
On Thu, Sep 16, 2010 at 11:30 AM, Benjamin Bentmann <
benjamin.bentm...@udo.edu> wrote:
> Baptiste MATHUS wrote:
>
> Does it mean that must now be put *even if* the parent pom
>> is
>> in t
Le Wed, 15 Sep 2010 22:34:47 +0200,
Benjamin Bentmann a écrit :
works fine on our project (install + site)
Tony
ps: my first mail was lost ?
> Hi,
>
> in preparation for the release of Apache Maven 3.0, the Maven team is
> seeking your help to discover regressions since Maven 2.x. Everybody
+1, no problem.
Tested multimodules build, on windows and AIX (ibm jvm), with and without //
build activated.
Congratulations for the work!
2010/9/16 Paul Merlin
>
> +1 (non-binding)
>
> Tested corporate and oss projects.
> Did not test the release process.
>
> /Paul
>
>
> Quoting Benjamin Ben
Baptiste MATHUS wrote:
Does it mean that must now be put *even if* the parent pom is
in the default path?
No, it means the effective value for should be correct,
whether that value is given by the user or using the implicit default.
Benjamin
-
Apologies if this is not the correct mailing list - I thought the developers
would be better suited to answering API questions.
I am implementing a mojo plugin that has a selection of modules to build
that were specified in a pom.xml.
How do I invoke a reactor to execute my List of modules filter
Hervé BOUTEMY wrote:
is this a formal vote
Neither in the mail's subject nor in its body did I refer to any vote.
This is an attempt to collect feedback from a broad audience before we
start the vote for 3.0, similar to what was done in the past [0].
Benjamin
[0] http://www.mail-archive
+1 (non-binding)
Tested corporate and oss projects.
Did not test the release process.
/Paul
Quoting Benjamin Bentmann :
> Hi,
>
> in preparation for the release of Apache Maven 3.0, the Maven team is
> seeking your help to discover regressions since Maven 2.x. Everybody
> interested in taking
Hi all,
Just read the link provided in the previous mail about m3-rc1. About this
parent pom resolution, I was aware Maven3 would now not resolve in the
project if parent project is not found in the default relative path :
../pom.xml.
But the comment here
https://cwiki.apache.org/confluence/displ
+1
Thanks Dennis!
-Lukas
Dennis Lundberg wrote:
Hi,
We solved 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12100&styleName=Html&version=16674
There is still an issue left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=12100&status=1
Stag
+1.
Sounds reasonnable for me too to remove those beta/alpha.
2010/9/15 Dennis Lundberg :
> Hi
>
> I saw that John added http://jira.codehaus.org/browse/MASSEMBLY-502 with
> a wish for Java 1.5. This is fine, but I think we need to discuss the
> contents of the coming versions.
>
> Over the last y
38 matches
Mail list logo
