Re: [VOTE] Release Apache Maven 3.0-beta-2

+0 Good news and thanks for releasing it ! 2010/8/8 Tony Chemit : > +1 (none binding) works fine on all our central safe projects. > > Great job :) > > Tony > > Le Sat, 07 Aug 2010 13:16:42 +0200, > Benjamin Bentmann a écrit : > >> Hi, >> >> We solved 28 issues: >> http://jira.codehaus.org/secur

Re: 3.0 beta 2/3/4 roadmap was Re: Merging in our Aether and Guice changes to Maven 3.x

Point of vue of a Maven user : We need to have a new beta release, ie beta-2 since the beta-1 is now 3/4 months old and Maven 2.2.1 is one year old. This will help us show our co-workers and may be more important, our IT managers, that Maven 3.0 progress. They didn't follow maven-dev list and onl

Re: Merging in our Aether and Guice changes to Maven 3.x

2010/8/4 Stephen Connolly : > Alternatively, host the Aether API in one place (hey why not codehaus), the > Maven Repo impl in Apache and the p2 repo impl in Eclipse ;-) Very good idea - To unsubscribe, e-mail: dev-unsubscr...@m

Re: Merging in our Aether and Guice changes to Maven 3.x

2010/8/4 Stephen Connolly : > If Aether has commit access for all Maven committers automatically, (and I'm > not saying it doesn't) then a large part of my concerns can be removed... I > recognise the p2 stuff as being a separate concern from the m2 repo > stuff and if that's the case then you

Re: Merging in our Aether and Guice changes to Maven 3.x

2010/8/4 Stephen Connolly : > I share concerns with respect to where the code is hosted.  I recognise that > as Apache is a meritocracy, there is a barrier for other developers getting > involved.  The Hudson model of "You want commit access, here you go" is a > tad too liberal for me, but the Apa

Re: maven-gwt-plugin 1.2 documentation

Oups, right,it should be on mojo-dev. Sorry 2010/1/11 Wayne Fay : >> It's not the wrong list, I reported some miss in the gwt plugin to Nicolas. >> Hopefully, he'll fix them quickly. > > I think Jason's point is that this discussion belongs on the mojo-dev > or mojo-users list, not Maven dev, sin

Re: maven-gwt-plugin 1.2 documentation

Sorry Jason, It's not the wrong list, I reported some miss in the gwt plugin to Nicolas. Hopefully, he'll fix them quickly. 2010/1/11 Jason van Zyl : > Wrong list. > > On 2010-01-11, at 5:31 AM, Henri Gomez wrote: > >> Hi to all, >> >> I'll do

Re: maven-gwt-plugin 1.2 documentation

=myGroupId \ -DartifactId=myArtifactId but archetype version 1.2 is available. In the doc reference to the gwt-maven-plugin are still to 1.1. 2010/1/11 nicolas de loof : > This doc is up-to-date. > > the 1.2 version is not dedicated to gwt 2.0, it just support this version as > GWT >

maven-gwt-plugin 1.2 documentation

Hi to all, I'll do some GWT 2.0.x application and get a look at http://mojo.codehaus.org/gwt-maven-plugin/ The documentation is still mainly for plugin 1.1 (gwt 1.7.x) with some notice for gwt 2.0 support. Did there is an up to date documentation available somewhere for best practices with gwt-

Re: [VOTE] Release Apache Maven 3.0-alpha-6

>> BTW, I'd like to generalize to our Hudson instance, but it seems >> Hudson still didn't support maven 3.0 :( > > Just use free-style projects and you're free to use any Maven version you > like. i'd like to but about 250 projects to update ;( ---

Re: [VOTE] Release Apache Maven 3.0-alpha-6

No problem here. Many projects build with m2eclipse (from trunk), with the maven3-alpha-6 BTW, I'd like to generalize to our Hudson instance, but it seems Hudson still didn't support maven 3.0 :( 2010/1/7 Olivier Lamy : > Hi, > +1. > Tested on company builds with success. > > Thanks, > -- > Oliv

Re: [VOTE] Release Apache Maven 3.0-alpha-3

+0 (non binding) I'm using m2eclipse from the trunk, using the embedded maven 3 from the trunk, to build several in-house projects. No problems for now 2009/11/9 Arnaud HERITIER : > +1 > Tested with success on several projects > It becomes to be interesting :-) > > Arnaud Héritier > Software Fact

Re: missing artifact for maven-3 dev

I see yesterday night (CET), build works now 2009/11/6 Brian Fox : > On Fri, Nov 6, 2009 at 8:34 AM, Henri Gomez wrote: >> Ok. >> >> For now, I'm building it thru our corp Nexus, and so I should define them. >> Do you recommand to use instead a pure proxy se

Re: maven 3.0 build failure with IBM SDK 5

plugin at all, or relying on defaults?  You > might try specifying UTF-8 explicitly in there. > > On Tue, Nov 3, 2009 at 8:46 AM, Benjamin Bentmann > wrote: > >> Henri Gomez wrote: >> >>  What's the JIRA for this problem (and fix in r832389) ? >>> I

Re: maven 3.0 build failure with IBM SDK 5

Linux x86-32 j9vmxi3223-20090707 (JIT enabled) J9VM - 20090706_38445_lHdSMr JIT - 20090623_1334_r8 GC - 200906_09) JCL - 20090705 Regards 2009/11/3 Henri Gomez : > Hi Benjamin, > > What's the JIRA for this problem (and fix in r832389) ? > I'd like to verify if this bug co

Re: maven 3.0 build failure with IBM SDK 5

Hi Benjamin, What's the JIRA for this problem (and fix in r832389) ? I'd like to verify if this bug could affect some of ours projects Regards 2009/11/3 Benjamin Bentmann : > Henri Gomez wrote: > >> Caused by: org.apache.maven.shared.filtering.MavenFiltering

Re: maven 3.0 build failure with IBM SDK 5

> Henri Gomez wrote: > >> Caused by: org.apache.maven.shared.filtering.MavenFilteringException >>        at >> org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile(DefaultMavenFileFilte

Re: maven 3.0 build failure with IBM SDK 5

A note on this one. Build works with an IBM SDK 6. 2009/11/3 Henri Gomez : > Hi to all, > > I just added a job on our Hudson server to build Maven 3.0 from the trunk. > The job use maven 2.2.1 and a custom repository (to avoid collisions > with our others projects). > Goals

maven 3.0 build failure with IBM SDK 5

Hi to all, I just added a job on our Hudson server to build Maven 3.0 from the trunk. The job use maven 2.2.1 and a custom repository (to avoid collisions with our others projects). Goals are clean install and MAVEN_OPTS is set to -Xmx512m No problem when I use a Sun JVM Java 5. But if I select

Re: Building Maven 3.0 from trunk

2009/10/29 Henri Gomez : >> If you have a missing SVN command, that may mean you do not have an >> SVN client installed. You should have one installed on your path so >> when you type "svn --version" (that's two dashes), you'll know what >> version yo

Re: Building Maven 3.0 from trunk

> If you have a missing SVN command, that may mean you do not have an > SVN client installed. You should have one installed on your path so > when you type "svn --version" (that's two dashes), you'll know what > version you have. yep, I know that, svn command is installed on my OS/X but not on my

Building Maven 3.0 from trunk

Hi to all, After build Maven 3 from trunk (https://svn.apache.org/repos/asf/maven/maven-3/trunk/) with ant, I tried to build it with maven 2.2.1 but the build failed about a missing svn command. - To unsubscribe, e-mail: dev-unsu

Re: preparing for the next 3.x alpha release

No problem with both jaxws-maven-plugin 1.10 and the latest one, jaxws-maven-plugin 1.12. Sorry for the noise 2009/10/22 Henri Gomez : > More on this one. > > Occurs on Snow Leopard (didn't tried yet on Linux/Windows) and with > the jaxws-maven-plugin 1.11. > I works with th

Re: preparing for the next 3.x alpha release

More on this one. Occurs on Snow Leopard (didn't tried yet on Linux/Windows) and with the jaxws-maven-plugin 1.11. I works with the jaxws-maven-plugin 1.10 :-( 2009/10/22 Henri Gomez : > I just tried a project build with the latest maven 3.0 snapshot > (Apache Maven 3.0-SNAPSHOT (r8

Re: preparing for the next 3.x alpha release

I just tried a project build with the latest maven 3.0 snapshot (Apache Maven 3.0-SNAPSHOT (r828677; 2009-10-22 15:19:50+0200)) It seems to be a problem with the jaxws-maven-plugin 1.11 : Here is the stack trace : [DEBUG] /Users/henri/.m2/repository/javax/servlet/servlet-api/2.5/servlet-api-2.5

Re: Maven 2.1.0 regression with war plugin

Not really related, but what about 'un etat de l'art' of the plugins to be used with maven 2.1.0 ? I could see in the 'embedded master pom' : maven-antrun-plugin 1.3 maven-assembly-plugin 2.2-beta-2

Re: The Future of OSGi & Maven

2009/3/17 Georgy Bolyuba : > There is a comment [1] by Igor on [2]: > >   > Henri, Tycho already discovers OSGi dependencies from bundle manifest. > > Does this mean that dependencies can be osgi-bundles? Where can one > find more information about it? > > All I am able to find on Maven + OSGi is h

maven archetypes questions

I'm creating some in-house archectypes. I've got some questions : - I need to add extra parameters, ie -DappId and got it resolved in the generated pom.xml I do : mvn archetype:generate -DarchetypeGroupId=org.mycorp.archetypes -DarchetypeArtifactId=myapp -DarchetypeVersion=1.0-SNAPSHOT -DgroupI

jspc plugins : org.codehaus.mojo.jspc/jspc-maven-plugin or org.codehaus.mojo/jspc-maven-plugin ?

Hi to all, Which maven plugin should be use for JSP compilation ? org.codehaus.mojo.jspc jspc 2.0-alpha-3 or org.codehaus.mojo jspc-maven-plugin 1.4.6 I tried the 2.0-alpha-3 but it failed with : [INFO] [ERROR] BUILD E

Re: Maven 2.1.0 Plans (a proposal of sorts)

2009/2/18 Brett Porter : > On 18/02/2009, at 11:59 PM, Henri Gomez wrote: > >> I build my JAX-WS project with maven 2.1.0-M1 and it works :) >> >> Good news, but could it be used in m2eclipse ? > > It's really something to take up with m2eclipse... but I don&#x

Re: Maven 2.1.0 Plans (a proposal of sorts)

included): > > http://www.sonatype.com/people/2008/11/a-visual-history-of-maven-2/ > > - Brett > > On 18/02/2009, at 10:32 PM, Henri Gomez wrote: > >> 2009/2/18 Brett Porter : >>> >>> On 18/02/2009, at 7:43 PM, Henri Gomez wrote: >>> >>>>

Re: Maven 2.1.0 Plans (a proposal of sorts)

2009/2/18 Brett Porter : > > On 18/02/2009, at 7:43 PM, Henri Gomez wrote: > >> Question about 2.1.0 / 3.0.0. >> >> In 3.0 alpha2 Jason fix a problem with jaxws-maven. >> >> Could it be backported to 2.1.0 ? > > I believe that problem doesn't

Re: Maven 2.1.0 Plans (a proposal of sorts)

Question about 2.1.0 / 3.0.0. In 3.0 alpha2 Jason fix a problem with jaxws-maven. Could it be backported to 2.1.0 ? Also did this new 'mileston' will be used in m2eclipse. I know Maven 3.0 is the target for m2eclipse but during the intermin, having a stable and known 2.1 would be nice. Regards

Re: [vote] release maven 2.0.10

2009/2/11 Olivier Lamy : > Hi, > Tested with company builds : looks fine. > > +1 > > Thanks ! Ditto here, tried with various company projects, and no problems so far - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For

Re: [VOTE] Maven 3.0-alpha-2

> I'll do a sample project. Done >> If you pull a new update-dev build of m2e you'll notice that we have the >> problem reporting integrated now. With latest build you can go down to the >> "Maven" menu and at the bottom you'll see the "Report Issue..." option. You >> can put in the summary, desc

Re: [VOTE] Maven 3.0-alpha-2

> I think your problem is specifically with ant so something that represents > what you tried to do in the project that failed would be handy. I'll do a sample project. > If you pull a new update-dev build of m2e you'll notice that we have the > problem reporting integrated now. With latest build

Re: [VOTE] Maven 3.0-alpha-2

> Ant stuff doesn't work properly. Let's do the same thing, make a test > project and we'll work through it. Do you need a sample projet using ant task or something without ant ? - To unsubscribe, e-mail: dev-unsubscr...@maven.ap

Re: [VOTE] Maven 3.0-alpha-2

I checked it with on a simple project using jaxws wsgen and it works now (it was failing with 3.0-alpha1), good news. I tried on other projects where I got an maven ant involved to grab some system informations : org.apache.maven.plugins maven-antrun-plugin

Re: releasing 2.0.10?

2009/2/2 Brian E. Fox : > Who knows. Maybe, maybe not depending on the timing and uptake of 3.x > Well if 2.1.0 is quickly stable and you need to add more stuff, 2.2.0 could be a good idea. But 2.x.y should stop at some time when 3.0 will be available or users will be stuck by so many differents

Re: releasing 2.0.10?

I agree. But no 2.2.x is planned ? 2009/2/2 Brian E. Fox : > Yes, but hopefully 2.0.x is end of life with either 2.0.10 or 2.0.11 and > 2.1.x becomes the active line. > > -Original Message----- > From: Henri Gomez [mailto:henri.go...@gmail.com] > Sent: Monday, February 02,

Re: maven 3.0-alpha-2 tagged

binaries available ? 2009/1/31 Jason van Zyl : > Shane/Benjamin, > > Go ahead and roll your changes into trunk. > > The alpha-2 is tagged. No messages about the vote because of a problem with > the upgrade on people.apache.org which is preventing me from deploying. > > Thanks, > > Jason > > --

Re: releasing 2.0.10?

ned it out, > there was a lot of interest in new features but I don't think much has > been done in the last 5 months, so I don't see the point in waiting for > future features, lets get 2.1 out so people will start to use it. > > -----Original Message- > From: He

Re: releasing 2.0.10?

I was thinking : 2.0.x is the current Maven 2 2.1 deprecated and will became 3.0 But what is 2.2 ? or 2.1 ? I'm puzzled 2009/1/30 Brian E. Fox : > My original intent was to shift the focus to 2.1 and bring that quickly > to GA. The development on it has stalled so it's irrelevant if it's > fe

Re: maven 3.0.0-alpha-1 / wsgen

> 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 a

maven 3.0.0-alpha-1 / wsgen

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, C:\workspace-34\slib-erable-framework\target\classes;c:\maven-repository\fr\slib\sx\canopee\slib-j

Re: pre maven 3.0 binaries available ?

> Jason, not sure if you remember, but m2eclipse allows to install embedder > updates separately from the core. > So, can publish updated embedder for early adopters consumption and it > will also help to catch incompatibilities in 3.0 earlier. +1, I'll be happy to check them -

Re: pre maven 3.0 binaries available ?

2008/12/29 Jason van Zyl : > > On 29-Dec-08, at 4:48 AM, Henri Gomez wrote: > >> Hi to all, >> >> I wonder if there is pre maven 3.0 tarball available somewhere. >> >> I still got problem with jaxws and maven embedded (in m2eclipse) and >> reopened JI

pre maven 3.0 binaries available ?

Hi to all, I wonder if there is pre maven 3.0 tarball available somewhere. I still got problem with jaxws and maven embedded (in m2eclipse) and reopened JIRA #3586 (http://jira.codehaus.org/browse/MNG-3586). BTW, the embedded maven included in latest m2eclipse is pretty old now and may be the bu

custom packaging, how to get jars from wars

Hi to all, I'm writing a custom packager to help my IT create ZIP archives from a sum of jars/wars. I could get the jars/wars but can't figure how to get the jars required by wars (we didn't put them in WEB-INF/lib since we should share them). here is my actual code, how could I get jar dependen

Re: central repository cleanup please

> sync to central for groupId com.extjs occured just during a content update.I > now have a > "gxt-1.1.jar.filepart"file > in > http://repo1.maven.org/maven2/com/extjs/gxt/1.1/ > > Can someone please delete this 1.1 folder, so

Re: 2.0.10: Plan to update super pom dependencies?

Could be a good idea to send on this list, a list of up to date plugins for those of us who set the plugins dependencies in their enterprise POM. 2008/7/11 Paul Benedict <[EMAIL PROTECTED]>: > What will be the procedure going forward to upgrade super POM dependencies? > > Before the RC is cut, I'd

Re: Developing Maven 2.1

> It builds fine for me now with 2.0.9, we've never needed to bootstrap to > build 2.1 before, so what's different now? You got it works with 2.0.9 ? Just with mvn install ? > If we can't trust Maven to build our own applications here, then we have > a serious problem IMO that needs to be fixed.

Re: Developing Maven 2.1

Well I 'll put your maven 2.1 build to our Hudson instance :) 2008/7/10 Jason van Zyl <[EMAIL PROTECTED]>: > Henri, > > Here's the most recent build: > > http://ci.sonatype.org/view/Maven%202.1x/job/maven-2.1.x-bootstrap/ws/trunk/maven-distribution/target/ >

Re: Developing Maven 2.1

I tried to build the latest maven 2.1 from trunk with mvn install but it still failed in tests. What should be done to get a build of maven 2.1 ? I need it to track a classloader issue with jaxws-maven-plugin even if it seems to be a general problem with the system scope. Regards and thanks for

Re: Vetting issues for 2.1-alpha-XX

More on this. With maven 2.0.9 here is the 'classpath' constructed by maven to jaxws : Maven 2.0.9 [DEBUG] Configuring mojo 'org.codehaus.mojo:jaxws-maven-plugin:1.10:wsgen' --> [DEBUG] (f) destDir = C:\Documents and Settings\gomezhe\Bureau\sample-wsgen\target\classes [DEBUG] (f) extension =

Re: jaxws-maven-plugin failure on non Sun SDK

> It will be supported. Ok, so the bug (MNG-3586) is still open, but I feel it's a problem with the tools.jar (apt) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: jaxws-maven-plugin failure on non Sun SDK

> I think it should be. it should be available or no more supported ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: jaxws-maven-plugin failure on non Sun SDK

> Please take this to the users list. This is not even a plugin from Apache. A question for the dev list. Did the system scope is still available with maven 2.1 ? --- com.sun tools 1.5.0 system ${java.home}/../lib/tools.jar

Re: jaxws-maven-plugin failure on non Sun SDK

> No, it's for our development of the core and our plugins. ok. > Your questions are user questions, users also develop plugins. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECT

Re: jaxws-maven-plugin failure on non Sun SDK

> register an account with java.net, the url is here Allready got one. > https://svn.dev.java.net/svn/jax-ws-commons/ Ok I'll use my account. Next step, how to provide fixes and patches ? - To unsubscribe, e-mail: [EMAIL PROT

Re: jaxws-maven-plugin failure on non Sun SDK

> Please take this to the users list. This is not even a plugin from Apache. maven dev list is not also a list for maven plugin/mojo ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: jaxws-maven-plugin failure on non Sun SDK

Any news on how to get the source of jaxws-maven-plugin via SVN ? I'd like to track in sources why the plugin try to open (and read) POM as zip when using IBM SDK and not with Sun SDK. [WrapperGen - method: placeOrder(com.mycorp.myapp.orderbook.service.PlaceOrderRequest)] [method.getDeclaringType

Re: jaxws-maven-plugin failure on non Sun SDK

>at >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) >>at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) >>... 16 more >> [INFO] >> --

Re: jaxws-maven-plugin failure on non Sun SDK

More on this : More on this : In the 1.10 pom file I could see : default-tools.jar java.vendor Sun Microsystems Inc. com.sun tools 1.5.0 system ${java.home}/.

Re: jaxws-maven-plugin failure on non Sun SDK

I'll do 2008/7/7 Dan Tran <[EMAIL PROTECTED]>: > you may want ping java.net ws group, they own this plugin > > -D > > On Mon, Jul 7, 2008 at 9:15 AM, Henri Gomez <[EMAIL PROTECTED]> wrote: >> BTW, I didn't get more success

Re: jaxws-maven-plugin failure on non Sun SDK

[INFO] [INFO] Total time: 6 seconds [INFO] Finished at: Mon Jul 07 18:13:48 CEST 2008 [INFO] Final Memory: 10M/36M [INFO] 2008/7/7 Henri Gomez <[EMAIL PROTECTED]>: >> the

Re: jaxws-maven-plugin failure on non Sun SDK

> the dependeny must in yes, but there is no mention about this on the plugin doc ;( - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: jaxws-maven-plugin failure on non Sun SDK

tools is only included when a Sun JVM is used. Very restrictive 2008/7/7 Dan Tran <[EMAIL PROTECTED]>: > Caused by: java.lang.NoClassDefFoundError: com.sun.tools.apt.Main > > > you forgot to include tool.jar, check the plugin doc for exampl > > -D > > On Mon, Jul 7

Re: jaxws-maven-plugin failure on non Sun SDK

> A possible workaround: You could try the CXF plugins. They generate > JAX-WS compliant code. Why not as a quick workaround but we should stick with JAXWS 2.1.4 impl for now ;( - To unsubscribe, e-mail: [EMAIL PROTECTED] For

jaxws-maven-plugin failure on non Sun SDK

Hi to all, We still get errors with jaxws-maven-plugin when were using a non Sun JDK. DEBUG] jaxws:wsgen args: [-d, C:\workspace\slib-ws-core-service\target\classes, -cp, C:\workspace\slib-ws-core-service\target\classes;c:\maven-repository\com\sun\xml\ws\jaxws-rt\2.1.4\jaxws-rt-2.1.4.jar;c:\maven

Re: Vetting issues for 2.1-alpha-XX

2008/7/4 Brett Porter <[EMAIL PROTECTED]>: > I was just looking at this Henri - though I'm not longer able to compile the > provided test project so it's impossible to test. > > Can you review the project to help make it reproducible? Done. Redone the test with m2eclipse 0.9.4 (using embedded) >

Re: Vetting issues for 2.1-alpha-XX

> Here's some tips for folks trying to debug Maven/Plexus/Plugins in Eclipse. > Using m2e you can actually debug/execute plugin _inside_ Eclipse. That means > the plugin executes from the workspace in-situ. Extremely handy. > > http://docs.codehaus.org/display/M2ECLIPSE/Developing+and+debugging+Ma

Re: Vetting issues for 2.1-alpha-XX

Did the MNG-3586 is allready fixed or fix is delayed ? I got this mail : - Jason van Zyl updated MNG-3586: --- Fix Version/s: (was: 2.1-alpha-1) 2.1-alpha-2 -- Very annoying bug for those of us using m2eclipse 0.9.4 and hav

Re: Configuration guide for developping / contributing to maven 2.1

> It's recent - I reported it on this list yesterday. If you take trunk back > about a week, you should find that it works a bit better. I'll wait it to be fixed. > On the other hand, if you want a slightly easier way to get started - you > might like to help correct these / vs \ issues on Window

Re: Configuration guide for developping / contributing to maven 2.1

>>Tests run: 190, Failures: 4, Errors: 0, Skipped: 0 > > what are the failures you are getting in the target/surefire-reports > directory? in maven-project/target/surefire-reports : org.apache.maven.project.MavenProjectDynamismTest.txt : -

Re: Configuration guide for developping / contributing to maven 2.1

Just grab maven 2.1 trunk to a new location (At revision: 672783) mvn clean => works mvn compile => works but I see this message : [INFO] [aspectj:compile {execution: compile-aspects}] [WARNING] bad version number found in C:\maven-repository\aspectj\aspectjrt\1.5.3\aspectjrt-1.5.3.jar expected

Re: Configuration guide for developping / contributing to maven 2.1

> It's the same problem I was working on recently, the embedder tests don't > honour your settings, so they don't work with a clean local repository. I > added some plugin definitions to the build itself to try and trigger it to > download the right artifacts (eg, resources plugin 2.2) - do you hav

Configuration guide for developping / contributing to maven 2.1

Hi to all, I'd like to works on maven 2.1 to locate and fix a problem with jaxws-mojo (http://jira.codehaus.org/browse/MNG-3586) (Eugene suggestion :) I grabbed the trunk from maven 2.1 into my Eclipse 3.4 workspace. I use m2eclipse 0.9.4 so I enabled Maven Dependencies Management and Enabled Ne