Re: Read plugin configuration from another plugin
Thanks guys, I'll have a look. Le Jeudi 28 avril 2016 12h44, Anton Tanasenko <atg.sleepl...@gmail.com> a écrit : Hey, M2E is effectively doing LifecycleExecutor#calculateExecutionPlan(session, false, "default").getMojoExecutions(), and each returned mojo execution has a final xml config. 2016-04-28 13:00 GMT+03:00 Tamás Cservenák <ta...@cservenak.net>: > Hi there, > > there is a POC I was toying with after ApacheCon last year. It is hacky, > but I just wanted to see would it work: > > https://github.com/cstamas/configuration-maven-plugin > > If you want to _READ_ the config, same approach as above with lifecycle > participant would work as it receives the _effective_ model. How would you > _interpret_ the config is another story. > > Thanks, > T > > On Thu, Apr 28, 2016 at 10:29 AM Julien HENRY <henr...@yahoo.fr.invalid> > wrote: > > > Hi guys, > > > > The SonarQube plugin for Maven try to configure SonarQube analysis based > > on Maven project configuration. We are interested by project model > > (packaging, properties) but also by configuration of other plugins > > (m-compiler-p source and target for example). > > > > Our approach to get this configuration is to read the pom using injected > > MavenProject and get an Xpp3Dom [1]. This approach is very hacky since we > > have to manually take care of all possible ways to configure a plugin: > > - configuration can be in build/plugins or in build/pluginsManagement > or > > even in reporting section > > - I'm not sure we are supporting configuration "per execution" > > - we are not supporting configuration provided using user properties > > (see [2]) > > - we have to hardcode default values > > > > So here is my question: is it possible for a plugin to get "resolved" > > configuration from another plugin. I mean the configuration that would > have > > been injected in this other plugin at runtime. > > > > For example I would like to access value injected in compiler mojo for > the > > "source" attribute [3]. I guess m2e has a similar need but I don't know > how > > it works. > > > > Thanks for your help, > > > > Julien > > > > > > [1] > > > https://github.com/SonarSource/sonar-maven/blob/master/src/main/java/org/sonarsource/scanner/maven/bootstrap/MavenPlugin.java#L104 > > [2] https://github.com/SonarSource/sonar-maven/pull/6 > > [3] > > > http://svn.apache.org/viewvc/maven/plugins/tags/maven-compiler-plugin-3.5.1/src/main/java/org/apache/maven/plugin/compiler/AbstractCompilerMojo.java?view=markup#l133 > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- Regards, Anton. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Read plugin configuration from another plugin
Hi guys, The SonarQube plugin for Maven try to configure SonarQube analysis based on Maven project configuration. We are interested by project model (packaging, properties) but also by configuration of other plugins (m-compiler-p source and target for example). Our approach to get this configuration is to read the pom using injected MavenProject and get an Xpp3Dom [1]. This approach is very hacky since we have to manually take care of all possible ways to configure a plugin: - configuration can be in build/plugins or in build/pluginsManagement or even in reporting section - I'm not sure we are supporting configuration "per execution" - we are not supporting configuration provided using user properties (see [2]) - we have to hardcode default values So here is my question: is it possible for a plugin to get "resolved" configuration from another plugin. I mean the configuration that would have been injected in this other plugin at runtime. For example I would like to access value injected in compiler mojo for the "source" attribute [3]. I guess m2e has a similar need but I don't know how it works. Thanks for your help, Julien [1] https://github.com/SonarSource/sonar-maven/blob/master/src/main/java/org/sonarsource/scanner/maven/bootstrap/MavenPlugin.java#L104 [2] https://github.com/SonarSource/sonar-maven/pull/6 [3] http://svn.apache.org/viewvc/maven/plugins/tags/maven-compiler-plugin-3.5.1/src/main/java/org/apache/maven/plugin/compiler/AbstractCompilerMojo.java?view=markup#l133 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Aether migration = add Sonar mojo on wiki
Hi, May someone add Sonar mojo in the list of mojo needing an update for Maven 3.1 [1]. groupId: org.codehaus.mojo artifactId: sonar-maven-plugin affected goal: sonar Plugin Name: Sonar Maven Plugin [2] JIRA ticket: MSONAR-22 Thanks Julien [1] https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound [2] http://mojo.codehaus.org/sonar-maven-plugin/ [3] https://jira.codehaus.org/browse/MSONAR-22
Re: Aether migration = add Sonar mojo on wiki
Thanks. De : Robert Scholte rfscho...@apache.org Done, thanks for reporting! Robert Op Fri, 14 Jun 2013 16:02:04 +0200 schreef Julien HENRY henr...@yahoo.fr: Hi, May someone add Sonar mojo in the list of mojo needing an update for Maven 3.1 [1]. groupId: org.codehaus.mojo artifactId: sonar-maven-plugin affected goal: sonar Plugin Name: Sonar Maven Plugin [2] JIRA ticket: MSONAR-22 Thanks Julien [1] https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound [2] http://mojo.codehaus.org/sonar-maven-plugin/ [3] https://jira.codehaus.org/browse/MSONAR-22 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: pom.xml parser
Hi, I think it is https://svn.apache.org/repos/asf/maven/maven-3/trunk/maven-model/ (using modello). Regards, Julien - Mail original - De : Simone Tripodi simonetrip...@apache.org À : Maven Developers List dev@maven.apache.org Cc : Envoyé le : Dimanche 11 Décembre 2011 20h45 Objet : pom.xml parser Hi all guys, can you please point me to the pom.xml parser location on SVN? Many thanks in advance, all the best! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: PROPOSAL: Remote Profiles ( a limited alternative to mixins )
Profile are supposed to contains optional things. AFAIK it is always possible to disable a profile (-P!profileId). I don't think it is the same for mixins. I don't see a use case where mixins should be disabled. I even believe it is bad for build reproducibility. My 2 cents. De : Mark Derricutt m...@talios.com À : Maven Developers List dev@maven.apache.org Envoyé le : Lundi 5 Décembre 2011 11h31 Objet : Re: PROPOSAL: Remote Profiles ( a limited alternative to mixins ) I've not yet looked at maven internal code about how one might implement this ( to be honest, at this point in time I'm not sure even know WHERE to look, other than poking around classes named Profile :) So yes - intuition on my part and just logic really. How adding something like this to the system affects the build stability is highly important, main reason I was thinking that it SHOULDN'T support version ranges. From immediate thoughts I don't think this would be any more unstability to the mix that the existing profile support doesn't already add to the mix ( profiles in ~/.m2/settings.xml being among the most unstable/unpredicatble IMHO ). Is there currently any way of maven telling a user WHERE a profile was included from? -pl allows you to select profiles but there doesn't seem to be any option to LIST profiles? I could see that being very handy, also failing the build if a non-existing profile is requested ( maven currently only WARNs about the non existing profile ). -- Great artists are extremely selfish and arrogant things — Steven Wilson, Porcupine Tree On Sun, Dec 4, 2011 at 5:50 AM, Jason van Zyl ja...@tesla.io wrote: The profile mechanism is how any new mixin system would work. No other mechanism internally is really suited to provide full access to the model in the right place. Not sure if you looked at the code or this is intuition on your part but your analysis is correct in that it's collaboration with the profile mechanism. This is how mixins should work. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] release maven-assembly-plugin version 2.2.2
+1 (not binding) - Mail original - De : Benson Margulies bimargul...@gmail.com À : Maven Developers List dev@maven.apache.org Cc : Envoyé le : Mardi 29 Novembre 2011 18h02 Objet : [VOTE] release maven-assembly-plugin version 2.2.2 Hi, We solved N issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126version=13669 There are still a couple of issues left in JIRA: https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+MASSEMBLY+AND+status+%3D+Open+ORDER+BY+priority+DESCmode=hide Staging repo: https://repository.apache.org/content/repositories/maven-268/ Staging site: http://maven.apache.org/plugins/maven-assembly-plugin-2.2.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html NOTE: this release was built using the staged version of maven-common-filters-1.4. Add https://repository.apache.org/content/groups/staging/ to your repository list to test. Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
MASSEMBLY-561: Encoding issue with assembly filtering
Hi, Sorry for the insistence, but could someone have a look at my patch for MASSEMBLY-561. John Casey started to look at the patch but seems he is busy. We have users that are forced to use a custom released version of m-assembly-p and I wouldn’t like this situation to stay as it is. Thanks Julien
Re: [VOTE] Release Apache Maven Wagon 2.0
Hi Olivier, I just tried to use new wagon with Maven 3.0.3 to mvn clean install an already previously built project and I get tons of message in logs similar to: Downloading: http://nexus.mycompany.fr/content/groups/public-releases/org/apache/commons/commons-exec/1.0.1/commons-exec-1.0.1.pom 26 sept. 2011 16:33:08 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies ATTENTION: Cookie rejected: [version: 0][name: rememberMe][value: deleteMe][domain: nexus.mycompany.fr][path: /nexus][expiry: Mon Sep 26 16:33:08 CEST 2011]. Illegal path attribute /nexus. Path of origin: /content/groups/public-releases/org/apache/commons/commons-exec/1.0.1/commons-exec-1.0.1.pom Following executions seems to be fine (but maybe this is because of update policy). I don't know if it is really an issue, but feel free to ask if you need more info. Regards, Julien De : Olivier Lamy ol...@apache.org À : Maven Developers List dev@maven.apache.org Envoyé le : Lundi 26 Septembre 2011 15h56 Objet : [VOTE] Release Apache Maven Wagon 2.0 Hello, I'd like to release Apache Maven Wagon 2.0. We fixed 31 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17379styleName=TextprojectId=10335Create=Create Staging repo : https://repository.apache.org/content/repositories/maven-104/ Staging site : http://maven.apache.org/wagon-2.0 (wait sync). [+1] [ 0] [-1] An easy way to test it: download jar and put it your $M2_HOME/lib/ext (if you use maven 3). wagon http: wget https://repository.apache.org/content/repositories/maven-104/org/apache/maven/wagon/wagon-http/2.0/wagon-http-2.0-shaded.jar cp wagon-http-2.0-shaded.jar $M2_HOME/lib/ext/ Here my +1. Thanks, -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Wagon 2.0
In fact the artifact was already downloaded during a previous build and is in the local repository. But it seems there is a check once a day on the repository (even for releases???). Do you want that I test with a clean local repo? - Mail original - De : Olivier Lamy ol...@apache.org À : Maven Developers List dev@maven.apache.org; Julien HENRY henr...@yahoo.fr Cc : Envoyé le : Lundi 26 Septembre 2011 16h47 Objet : Re: [VOTE] Release Apache Maven Wagon 2.0 is the artifact correctly downloaded ? 2011/9/26 Julien HENRY henr...@yahoo.fr: Hi Olivier, I just tried to use new wagon with Maven 3.0.3 to mvn clean install an already previously built project and I get tons of message in logs similar to: Downloading: http://nexus.mycompany.fr/content/groups/public-releases/org/apache/commons/commons-exec/1.0.1/commons-exec-1.0.1.pom 26 sept. 2011 16:33:08 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies ATTENTION: Cookie rejected: [version: 0][name: rememberMe][value: deleteMe][domain: nexus.mycompany.fr][path: /nexus][expiry: Mon Sep 26 16:33:08 CEST 2011]. Illegal path attribute /nexus. Path of origin: /content/groups/public-releases/org/apache/commons/commons-exec/1.0.1/commons-exec-1.0.1.pom Following executions seems to be fine (but maybe this is because of update policy). I don't know if it is really an issue, but feel free to ask if you need more info. Regards, Julien De : Olivier Lamy ol...@apache.org À : Maven Developers List dev@maven.apache.org Envoyé le : Lundi 26 Septembre 2011 15h56 Objet : [VOTE] Release Apache Maven Wagon 2.0 Hello, I'd like to release Apache Maven Wagon 2.0. We fixed 31 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17379styleName=TextprojectId=10335Create=Create Staging repo : https://repository.apache.org/content/repositories/maven-104/ Staging site : http://maven.apache.org/wagon-2.0 (wait sync). [+1] [ 0] [-1] An easy way to test it: download jar and put it your $M2_HOME/lib/ext (if you use maven 3). wagon http: wget https://repository.apache.org/content/repositories/maven-104/org/apache/maven/wagon/wagon-http/2.0/wagon-http-2.0-shaded.jar cp wagon-http-2.0-shaded.jar $M2_HOME/lib/ext/ Here my +1. Thanks, -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Wagon 2.0
It was a configuration issue of my MRM, so the log was in fact good to detect the problem. Thanks for the tip about ProxyPassReverseCookiePath De : Olivier Lamy ol...@apache.org À : Maven Developers List dev@maven.apache.org; Julien HENRY henr...@yahoo.fr Envoyé le : Lundi 26 Septembre 2011 21h38 Objet : Re: [VOTE] Release Apache Maven Wagon 2.0 IMHO you must rewrite cookie path in your httpd instance with something like: ProxyPassReverseCookiePath / /nexus/ 2011/9/26 Julien HENRY henr...@yahoo.fr: Hi Olivier, I just tried to use new wagon with Maven 3.0.3 to mvn clean install an already previously built project and I get tons of message in logs similar to: Downloading: http://nexus.mycompany.fr/content/groups/public-releases/org/apache/commons/commons-exec/1.0.1/commons-exec-1.0.1.pom 26 sept. 2011 16:33:08 org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies processCookies ATTENTION: Cookie rejected: [version: 0][name: rememberMe][value: deleteMe][domain: nexus.mycompany.fr][path: /nexus][expiry: Mon Sep 26 16:33:08 CEST 2011]. Illegal path attribute /nexus. Path of origin: /content/groups/public-releases/org/apache/commons/commons-exec/1.0.1/commons-exec-1.0.1.pom Following executions seems to be fine (but maybe this is because of update policy). I don't know if it is really an issue, but feel free to ask if you need more info. Regards, Julien De : Olivier Lamy ol...@apache.org À : Maven Developers List dev@maven.apache.org Envoyé le : Lundi 26 Septembre 2011 15h56 Objet : [VOTE] Release Apache Maven Wagon 2.0 Hello, I'd like to release Apache Maven Wagon 2.0. We fixed 31 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17379styleName=TextprojectId=10335Create=Create Staging repo : https://repository.apache.org/content/repositories/maven-104/ Staging site : http://maven.apache.org/wagon-2.0 (wait sync). [+1] [ 0] [-1] An easy way to test it: download jar and put it your $M2_HOME/lib/ext (if you use maven 3). wagon http: wget https://repository.apache.org/content/repositories/maven-104/org/apache/maven/wagon/wagon-http/2.0/wagon-http-2.0-shaded.jar cp wagon-http-2.0-shaded.jar $M2_HOME/lib/ext/ Here my +1. Thanks, -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] Project local setting.xml
What is the point of putting a settings.xml in your SCM next to your pom.xml? In this case just add the repos in the root pom. ++ Julien - Mail original - De : Milos Kleint mkle...@gmail.com À : Maven Developers List dev@maven.apache.org Cc : Envoyé le : Lundi 1 Août 2011 21h02 Objet : Re: [DISCUSS] Project local setting.xml hasn't that been the purpose of profiles.xml files back in 2.x before it was removed for 3.x? Milos On Mon, Aug 1, 2011 at 9:00 PM, Paul Gier pg...@redhat.com wrote: I'd like to discuss the possibility of Maven automatically looking for a project specific settings.xml file [1]. The main use case for this is to eliminate, or at least reduce, the need to add repositories to the poms. A setting.xml file could simply be added into scm into the root directory of the project. Then it would be checked out when the project is checked out. With multi-module projects, Maven would need to search up the directory tree to find the settings.xml file, but this could be made relatively simple by checking the parent dirs until Maven finds: (1) a settings.xml, (2) a directory with no pom.xml, or (3) the root directory The only problem I can think of in this case would be when small related projects can be checked out separately (similar to Maven plugins, or codehaus mojo). The project might not be able to find the settings.xml if it is not checked out with the project. Although I think this is a relatively minor issue. [1]http://jira.codehaus.org/browse/MNG-4686 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697?
+1 for a 2.2.1 Thanks - Mail original - De : Stephen Connolly stephen.alan.conno...@gmail.com À : Maven Developers List dev@maven.apache.org Cc : Envoyé le : Jeudi 28 Juillet 2011 16h28 Objet : Re: Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697? well it was my typo in the first place, so yeah I'm willing to RM it... feck it... i'll do it On 28 July 2011 15:26, Mark Struberg strub...@yahoo.de wrote: If you are volunteering on the build, then +1 :) LieGrue, strub --- On Thu, 7/28/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697? To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 2:21 PM Since it is a rather nasty bug due to a typo on my behalf, do we push a release (2.2.1) now to include the fix and push all the unfixed issues back to 2.3 (where they currently live) -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Encoding support with m-assembly-p filtering
Hi, We are facing an issue with projects using resource filtering with m-assembly-p (filtering=true in a fileset). m-assembly-p always use default platform encoding to do filtering. It seems this plugin was forgotten during introduction of project.build.sourceEncoding property [1]. I have written a patch and integration tests to fix the issue [2]. May a commiter review it and give some feedback or apply it. Thanks, Julien [1] http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding [2] http://jira.codehaus.org/browse/MASSEMBLY-561 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
No continuous integration of maven-assembly-plugin?
Hi, I was not able to found a job on [1] building maven-assembly-plugin and associated ITs. Why maven-assembly-plugin is not in http://svn.apache.org/repos/asf/maven/plugins/trunk/pom.xml ? Regards, Julien [1] https://builds.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: No continuous integration of maven-assembly-plugin?
Thanks Lukas. Now I can try to figure out why some ITs are not working on my box (French Linux). ;) - Mail original - De : Lukas Theussl ltheu...@apache.org À : Maven Developers List dev@maven.apache.org Cc : Envoyé le : Vendredi 22 Juillet 2011 14h45 Objet : Re: No continuous integration of maven-assembly-plugin? I uncommented the module as it passed for me locally and jenkins seems happy too now: https://builds.apache.org/job/maven-plugins-ITs-2.x/251/changes https://builds.apache.org/job/maven-plugins-ITs-3.x/126/changes (there are failures from other plugins though...). Cheers, -Lukas On 07/22/2011 12:46 PM, Barrie Treloar wrote: On Fri, Jul 22, 2011 at 6:03 PM, Julien HENRYhenr...@yahoo.fr wrote: Hi, I was not able to found a job on [1] building maven-assembly-plugin and associated ITs. Why maven-assembly-plugin is not in http://svn.apache.org/repos/asf/maven/plugins/trunk/pom.xml ? Doesnt http://svn.apache.org/repos/asf/maven/plugins/trunk/pom.xml say !-- Excluded due to ongoing failuresmodulemaven-assembly-plugin/module -- Feel free to fix them. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Maven API to partially edit pom.xml
Hi, I would like to know if there is a standard Maven API to edit parts of a pom.xml. I managed to parse a pom to a Model using ModelBuilder. Then I can do some modifications and write Model to file using ModelWriter. But of course it will completly rewrite the pom (loosing comments, writing unwanted tags like default values, ...). I looked at how versions-maven-plugin works and it seems it uses its own parser (based on StAX) and then proceed with XPath to edit specific parts of the pom. Is it still the recommended way? Is there a better solution with Maven 3 API? Basically what I want is something like: Model model = new Model(path/to/pom.xml); model.setGroupId(foo); model.write(); // Only groupId is changed in pom.xml Thanks Julien - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven API to partially edit pom.xml
Thanks Jesse for the pointer. Actually it is on central: http://repo2.maven.org/maven2/de/pdark/decentxml/1.3/ Regards, Julien - Message d'origine De : Jesse Glick jesse.gl...@oracle.com À : dev@maven.apache.org Envoyé le : Mer 13 avril 2011, 16h 00min 21s Objet : Re: Maven API to partially edit pom.xml On 04/13/2011 07:56 AM, Julien HENRY wrote: I would like to know if there is a standard Maven API to edit parts of a pom.xml. I managed to parse a pom to a Model using ModelBuilder. Then I can do some modifications and write Model to file using ModelWriter. But of course it will completly rewrite the pom (loosing comments, writing unwanted tags like default values, ...). The main challenge is finding a library for high-fidelity XML round-trip structure editing, i.e. that preserves all details of whitespace and formatting for unmodified nodes. NetBeans has such a system (XAM/XDM) but the dependency tree is too deep for use in a Maven plugin. http://code.google.com/p/decentxml/ is the only such small library I can find. It has its own model rather than Document, DOMImplementationLS, etc., so your code would be tightly tied to that API. It does not appear to be published on Central and I am unsure how reliable it is, but it has a Maven POM utility already, and it seems to work as advertised in my testing - replacing a few element attribute values on some largish hand-edited XML files produced a minimal diff. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : [VOTE] Release Maven Site Plugin 3.0-beta-3 for maven 3
+1 Fix for MSITE-512 works fine. Thanks, Julien - Message d'origine De : Olivier Lamy ol...@apache.org À : Maven Developers List dev@maven.apache.org Envoyé le : Lun 18 octobre 2010, 11h 31min 28s Objet : Re: [VOTE] Release Maven Site Plugin 3.0-beta-3 for maven 3 Oups Sorry for typo. Read : The site documentation is available here : http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3 (wait sync) 2010/10/18 Olivier Lamy ol...@apache.org: Hi, I'd like to release a new beta (3.0-beta-3) of Maven Site Plugin for Maven 3. We solved 8 issues : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146version=16729 The staged repo is here : https://repository.apache.org/content/repositories/maven-002/ The site documentation is available here : http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-2/ (wait sync) The vote is open for 72H. Here my +1 Thanks, -- Olivier http://twitter.com/olamy http://www.linkedin.com/in/olamy -- Olivier http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : [VOTE] Release Apache Maven 3.0
After trying to migrate JWebUnit build to Maven 3 (especially site section) I think I found a regression: http://jira.codehaus.org/browse/MNG-4852 It seems configuration defined in reportSet section is no more taken into account. Regards, Julien - Message d'origine De : Benjamin Bentmann benjamin.bentm...@udo.edu À : Maven Developers List dev@maven.apache.org Envoyé le : Lun 4 octobre 2010, 14h 16min 07s Objet : [VOTE] Release Apache Maven 3.0 Hi, feedback on the RCs seems to be decreasing and I am currently not aware of any major regression so let's try and cross the finishing line of this marathon. We solved 31 issues since 3.0-beta-3: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=13142 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 1 Staging repo: https://repository.apache.org/content/repositories/maven-004/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/ / Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : [VOTE] Release Apache Maven 3.0
+1 (non-binding) I use it everyday on my dev computer. Missing functionalities are Hudson, Sonar and m2eclipse (simple) integration but I feel it will be quickly done once Maven 3 is officially released. Thanks for the good work! Julien - Message d'origine De : Benjamin Bentmann benjamin.bentm...@udo.edu À : Maven Developers List dev@maven.apache.org Envoyé le : Lun 4 octobre 2010, 14h 16min 07s Objet : [VOTE] Release Apache Maven 3.0 Hi, feedback on the RCs seems to be decreasing and I am currently not aware of any major regression so let's try and cross the finishing line of this marathon. We solved 31 issues since 3.0-beta-3: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=13142 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 1 Staging repo: https://repository.apache.org/content/repositories/maven-004/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/ / Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : Why is Julia Antonova/Tumlare subscribed
Don't take in consideration messages from Martin Gainty. As Julia is a great vacationer, Martin is some sort of bot that answers randomly (in the time) to a question with a totally random answer. Not totally random I think. Sometimes there is a connection between the previous post and Martin answer (see [1], [2]). Also this is not like usual spam trying to redirect you to a commercial or malicious site. So I was asking myself if it could be a research project about having a bot in OSS communities with enough intelligent behaviour to not be detected as bot. In the past I received an email from Martin that was directly addressed to me but I don't remember what it was about. However, if it is truly a research project, I'm afraid it is far from being complete as Martin's answers are often totally away from the point. The most funny is his signature block in several languages that look like a corporate signature but is full of mistakes (at least in French). [1] http://marc.info/?l=struts-userm=120994929706552w=3 [2] http://marc.info/?l=tomcat-userm=120947423115165w=3 - Message d'origine De : Antonio Petrelli antonio.petre...@gmail.com À : Maven Developers List dev@maven.apache.org Envoyé le : Sam 10 juillet 2010, 11h 47min 07s Objet : Re: Why is Julia Antonova/Tumlare subscribed 2010/7/9 lukewpatterson lukewpatter...@gmail.com: mgainty wrote: http://news.bbc.co.uk/2/hi/world/us_and_canada/10564994.stm So your theory is that she is/was a spy? Maybe from Ant? Don't take in consideration messages from Martin Gainty. As Julia is a great vacationer, Martin is some sort of bot that answers randomly (in the time) to a question with a totally random answer. I thought she might be a ghost, but newly gained empirical evidence leads me to believe that she is a vampire. In this case, Martin is a zombie :-D Antonio - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : Moving to TestNG JUnit4?
JUnit 4 apparently runs JUnit 3 tests out of the box I can confirm that (starting from JUnit 4.7 if I remember correctly). I usually upgrade all my projects to JUnit 4. This way I can write new tests using JUnit 4 style and keep old tests with JUnit 3 style. My 2 cts ++ Julien - Message d'origine De : Mark Derricutt m...@talios.com À : Maven Developers List dev@maven.apache.org Envoyé le : Mer 9 juin 2010, 14h 24min 56s Objet : Re: Moving to TestNG JUnit4? JUnit 4 apparently runs JUnit 3 tests out of the box, so one could feasibly change the dependencies to JUnit 4 at least. I understand the reasons for not physically changing old tests for the sake of change tho. Mark -- Pull me down under... On Tue, Jun 8, 2010 at 6:29 AM, Jason Chaffee href=mailto:jchaf...@ebates.com;jchaf...@ebates.com wrote: FYI, JUnit now supports concurrent running of tests. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : [VOTE] Release some Maven Archetypes
Hi, Now that latest m-compiler-p version set Java 1.5 as default, I suggest to update archetype quickstart to be Java 1.5 compliant: - JUnit 4 by default - use latest m-compiler-p or keep the default one but set source/target to 1.5 Each time I use quickstart archetype this is the things I have to change to have something working. Regards, Julien - Message d'origine De : Hervé BOUTEMY herve.bout...@free.fr À : Maven Developers List dev@maven.apache.org Envoyé le : Mar 27 avril 2010, 23 h 37 min 59 s Objet : [VOTE] Release some Maven Archetypes Hi, I want to release Maven Archetypes parent pom - maven-archetype-bundles version 4- and some Maven Archetypes: - maven-archetype-plugin version 1.1 - maven-archetype-plugin-site version 1.1 - maven-archetype-quickstart version 1.1 - maven-archetype-site version 1.1 - maven-archetype-site-simple version 1.1 Staging repo: target=_blank https://repository.apache.org/content/repositories/maven-028/ Site: href=http://maven.apache.org/archetype/maven-archetype-bundles/; target=_blank http://maven.apache.org/archetype/maven-archetype-bundles/ Guide to testing staged releases: href=http://maven.apache.org/guides/development/guide-testing-releases.html; target=_blank http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Here is my +1 Hervé - To unsubscribe, e-mail: href=mailto:dev-unsubscr...@maven.apache.org;dev-unsubscr...@maven.apache.org For additional commands, e-mail: href=mailto:dev-h...@maven.apache.org;dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : Re : [VOTE] Release Apache Maven 3.0-beta-1
It seems the enforcer plugin is set to prevent usage of SNAPSHOT in plugins
even when plugin is defined in a non active profile. I suppose you could open a
JIRA issue about that, but according to me the cleaner way is to use a released
version (or perhaps a locked SNAPSHOT) of m-site-p. If you can't wait for a
release and lockin plugin doesn't work, I suggest to perform your own release
in your MRM.
Regards,
Julien
- Message d'origine
De : Raphael Ackermann raphael.ackerm...@gmail.com
À : Maven Developers List dev@maven.apache.org
Envoyé le : Lun 26 avril 2010, 13 h 05 min 49 s
Objet : Re: Re : [VOTE] Release Apache Maven 3.0-beta-1
Added it to my corporate super pom. No complaints there. But if I try
to run
mvn install (mvn2) with the added profile I get an enforcer
error saying that
the maven-site-plugin has no version specified. If
I remove the
3.0-beta-1-SNAPSHOT m-site-p from the maven-3 profile the
build works
again.
Is this a bug in the enforcer plugin? when
running
help:active-profiles I can see that the maven-3 profile is not
active,
but the presence of the 3.0-beta-1-SNAPSHOT plugin seems to
confuse
the enforcer plugin
[INFO] [INFO] [enforcer:enforce
{execution: enforce}]
[INFO] [INFO] [enforcer:enforce {execution:
enforce-plugin-versions}]
[INFO] [WARNING] Rule
0:
org.apache.maven.plugins.enforcer.RequirePluginVersions failed
with
message:
[INFO] Some plugins are missing valid versions:(LATEST
RELEASE
SNAPSHOT are not allowed )
[INFO]
org.apache.maven.plugins:maven-site-plugin. The
version
currently in use is 2.1
[INFO] Best Practice is to always define
plugin versions!
[INFO] [INFO]
[INFO]
[ERROR] BUILD ERROR
Raphael
On Fri, Apr 23, 2010 at 12:04,
Julien HENRY
href=mailto:henr...@yahoo.fr;henr...@yahoo.fr wrote:
Hi,
This profile will only works in your projet pom (or better
in your corporate super pom). Profiles in settings.xml are not allowed to
have a
build section.
Regards,
Julien
- Message d'origine
De : Raphael Ackermann
href=mailto:raphael.ackerm...@gmail.com;raphael.ackerm...@gmail.com
À : Maven Developers List
href=mailto:dev@maven.apache.org;dev@maven.apache.org
Envoyé le : Ven 23 avril 2010, 11 h 53 min 32 s
Objet : Re: [VOTE]
Release Apache Maven 3.0-beta-1
I copied the profile
from the wiki website and added it to my
settings.xml
but
get following warnings on maven3 and error with
maven2:
maven
3
mvn install -DskipTests=true
[WARNING]
[WARNING] Some problems were
encountered while
building the effective settings
[WARNING] Unrecognised tag:
'build' (position: START_TAG
seen
.../activation\r\n\t\t\tbuild... @34:11) @
C:\Dokumente und
Einstellungen\rackermann\.m2\settings.xml, line 34,
column
11
[WARNING]
c:\devel\maven\2.2\maven-2.2.1\bin\mvn
install
Error reading
settings.xml: Unrecognised tag: 'build'
(position:
START_TAG
seen .../activation\r\n\t\t\tbuild...
@34:11)
Line: 34
Column: 11
any
ideas?
On Fri, Apr 23, 2010 at 00:46, Hervé BOUTEMY
ymailto=mailto:
href=mailto:herve.bout...@free.fr;herve.bout...@free.fr
href=mailto:
href=mailto:herve.bout...@free.fr;herve.bout...@free.fr
ymailto=mailto:herve.bout...@free.fr;
href=mailto:herve.bout...@free.fr;herve.bout...@free.fr
wrote:
this can be done simply by adding a profile
activated with ${basedir}
property:
I just added
instruction at the end of Wiki page
[1]
Regards,
Hervé
[1]
href=
href=https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin;
target=_blank
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin;
target=_blank
href=https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin;
target=_blank
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin
Le jeudi 22 avril 2010, Niall Pemberton a écrit :
On Tue, Apr
20,
2010 at 8:48 AM, Olivier Lamy
href=mailto:
ymailto=mailto:ol...@apache.org;
href=mailto:ol...@apache.org;ol...@apache.org
ymailto=mailto:ol...@apache.org;
href=mailto:ol...@apache.org;ol...@apache.org wrote:
No.
It's 3.x
prerequisite.
It would be
good if
there was some mechanism so that the site
generation
could
be made to work with either m2 or m3. Perhaps
by
activating
different profiles dependant on the
maven version -
something
like:
build
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version${site.plugin.version}/version
/plugin
/plugins
/pluginManagement
/build
profiles
profile
activation
maven2/maven
/activation
properties
site.plugin.version2.0.1/site.plugin.version
/properties
/profile
Re : [ANN] Apache Maven 3.0-beta-1 Released
Hi, I have the following error using Maven 3.0-beta-1. Before trying to reproduce on a smaller project, could you please have a look and tell me if this is a known issue. The only similar issue I have found is: MENFORCER-55 $ mvn versions:display-plugin-updates -X [...] [DEBUG] final aggregate version map org.apache.maven.plugins:maven-clean-plugin:2.3 org.apache.maven.plugins:maven-surefire-plugin:2.4.3 org.codehaus.mojo:exec-maven-plugin:1.1 org.apache.maven.plugins:maven-ear-plugin:2.3.2 org.apache.maven.plugins:maven-war-plugin:2.1-beta-1 org.apache.maven.plugins:maven-jar-plugin:2.3 org.apache.maven.plugins:maven-source-plugin:2.1.1 org.apache.maven.plugins:maven-dependency-plugin:2.1 org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-4 org.apache.maven.plugins:maven-javadoc-plugin:2.6.1 org.apache.maven.plugins:maven-compiler-plugin:2.0.2 org.apache.maven.plugins:maven-install-plugin:2.3 org.apache.maven.plugins:maven-site-plugin:2.0.1 org.apache.maven.plugins:maven-release-plugin:2.0-beta-8 [DEBUG] after adding local pluginManagement [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2.250s [INFO] Finished at: Mon Apr 26 14:18:46 CEST 2010 [INFO] Final Memory: 6M/19M [INFO] [ERROR] Failed to execute goal org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates (default-cli) on project myproject: Execution default-cli of goal org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates failed. NullPointerException - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates (default-cli) on project myproject: Execution default-cli of goal org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates failed. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:149) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:77) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:69) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:82) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:54) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.singleThreadedBuild(DefaultLifecycleExecutor.java:218) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:190) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:246) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:95) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:430) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160) at org.apache.maven.cli.MavenCli.main(MavenCli.java:124) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-cli of goal org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates failed. at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:114) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:133) ... 19 more Caused by: java.lang.NullPointerException at org.codehaus.plexus.util.ReflectionUtils.getValueIncludingSuperclasses(ReflectionUtils.java:179) at org.codehaus.mojo.versions.DisplayPluginUpdatesMojo.getBoundPlugins(DisplayPluginUpdatesMojo.java:660) at org.codehaus.mojo.versions.DisplayPluginUpdatesMojo.getLifecyclePlugins(DisplayPluginUpdatesMojo.java:619) at org.codehaus.mojo.versions.DisplayPluginUpdatesMojo.getProjectPlugins(DisplayPluginUpdatesMojo.java:1096) at org.codehaus.mojo.versions.DisplayPluginUpdatesMojo.execute(DisplayPluginUpdatesMojo.java:277) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105) ... 20 more It seems to works fine with Maven 2.2.1 (in fact
Re : [VOTE] Release Apache Maven 3.0-beta-1
Hi,
This profile will only works in your projet pom (or better in your corporate
super pom). Profiles in settings.xml are not allowed to have a build section.
Regards,
Julien
- Message d'origine
De : Raphael Ackermann raphael.ackerm...@gmail.com
À : Maven Developers List dev@maven.apache.org
Envoyé le : Ven 23 avril 2010, 11 h 53 min 32 s
Objet : Re: [VOTE] Release Apache Maven 3.0-beta-1
I copied the profile from the wiki website and added it to my
settings.xml
but get following warnings on maven3 and error with
maven2:
maven
3
mvn install -DskipTests=true
[WARNING]
[WARNING] Some problems were
encountered while building the effective settings
[WARNING] Unrecognised tag:
'build' (position: START_TAG
seen
.../activation\r\n\t\t\tbuild... @34:11) @
C:\Dokumente und
Einstellungen\rackermann\.m2\settings.xml, line 34, column
11
[WARNING]
c:\devel\maven\2.2\maven-2.2.1\bin\mvn
install
Error reading settings.xml: Unrecognised tag: 'build'
(position:
START_TAG seen .../activation\r\n\t\t\tbuild...
@34:11)
Line: 34
Column: 11
any
ideas?
On Fri, Apr 23, 2010 at 00:46, Hervé BOUTEMY
ymailto=mailto:herve.bout...@free.fr;
href=mailto:herve.bout...@free.fr;herve.bout...@free.fr wrote:
this can be done simply by adding a profile activated with ${basedir}
property:
I just added instruction at the end of Wiki page
[1]
Regards,
Hervé
[1]
href=https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin;
target=_blank
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin
Le jeudi 22 avril 2010, Niall Pemberton a écrit :
On Tue, Apr 20,
2010 at 8:48 AM, Olivier Lamy
href=mailto:ol...@apache.org;ol...@apache.org wrote:
No.
It's 3.x prerequisite.
It would be
good if there was some mechanism so that the site
generation could
be made to work with either m2 or m3. Perhaps by
activating
different profiles dependant on the maven version -
something
like:
build
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version${site.plugin.version}/version
/plugin
/plugins
/pluginManagement
/build
profiles
profile
activation
maven2/maven
/activation
properties
site.plugin.version2.0.1/site.plugin.version
/properties
/profile
profile
activation
maven3/maven
/activation
properties
site.plugin.version3.0-beta-1/site.plugin.version
/properties
/profile
/profiles
2010/4/20 Brett Porter
ymailto=mailto:br...@apache.org;
href=mailto:br...@apache.org;br...@apache.org:
On
20/04/2010, at 5:10 PM, Olivier Lamy wrote:
Hi,
2010/4/20 Hervé BOUTEMY
href=mailto:herve.bout...@free.fr;herve.bout...@free.fr:
what about releasing maven-site-plugin 3.0-beta-1?
Yup I can do that and start releasing all
needed stuff.
Olivier, is
there something critical missing?
No except some spare time :-)
Does that also work with Maven 2.x, or will we end up having two
strands
of development on it?
- Brett
--
Brett Porter
ymailto=mailto:br...@apache.org;
href=mailto:br...@apache.org;br...@apache.org
href=http://brettporter.wordpress.com/; target=_blank
http://brettporter.wordpress.com/
-
To unsubscribe, e-mail:
ymailto=mailto:dev-unsubscr...@maven.apache.org;
href=mailto:dev-unsubscr...@maven.apache.org;dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
ymailto=mailto:dev-h...@maven.apache.org;
href=mailto:dev-h...@maven.apache.org;dev-h...@maven.apache.org
--
Olivier
href=http://twitter.com/olamy; target=_blank
http://twitter.com/olamy
href=http://fr.linkedin.com/in/olamy; target=_blank
http://fr.linkedin.com/in/olamy
href=http://www.viadeo.com/fr/profile/olivier.lamy7; target=_blank
http://www.viadeo.com/fr/profile/olivier.lamy7
-
To unsubscribe, e-mail:
ymailto=mailto:dev-unsubscr...@maven.apache.org;
href=mailto:dev-unsubscr...@maven.apache.org;dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
ymailto=mailto:dev-h...@maven.apache.org;
href=mailto:dev-h...@maven.apache.org;dev-h...@maven.apache.org
-
To unsubscribe, e-mail:
href=mailto:dev-unsubscr...@maven.apache.org;dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
href=mailto:dev-h...@maven.apache.org;dev-h...@maven.apache.org
-
To
unsubscribe, e-mail:
Re : MNG-4483
+1 - Message d'origine De : Paul Benedict pbened...@apache.org À : Maven Developers List dev@maven.apache.org Envoyé le : Jeu 22 avril 2010, 17 h 14 min 15 s Objet : MNG-4483 3.0-beta-1 being a beta release, it's getting close to GA. I was wondering can MNG-4483 be addressed? I don't think Maven can keep the .m2 user directory exclusively -- it could be a good fallback for compatibility -- but it should be looking for .m3 or .mvn. Paul - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : Re : MNG-4483
1) check if .mvn exists 2) if .mvn doesn't exist then check if .m2 exists 3) if .m2 doesn't exist then create .mvn and use it ++ Julien - Message d'origine De : Wendy Smoak wsm...@gmail.com À : Maven Developers List dev@maven.apache.org Envoyé le : Jeu 22 avril 2010, 18 h 16 min 46 s Objet : Re: Re : MNG-4483 On Thu, Apr 22, 2010 at 12:00 PM, nicolas de loof ymailto=mailto:nicolas.del...@gmail.com; href=mailto:nicolas.del...@gmail.com;nicolas.del...@gmail.com wrote: +1 for .mvn and backward compatibility with .m2 if not found Wouldn't it _create_ .mvn if it's not found? Otherwise what's going to happen the first time you use m3 on a new machine? -- Wendy - To unsubscribe, e-mail: href=mailto:dev-unsubscr...@maven.apache.org;dev-unsubscr...@maven.apache.org For additional commands, e-mail: href=mailto:dev-h...@maven.apache.org;dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : [VOTE] Release Maven EJB Plugin 2.2.1
+1 Julien - Message d'origine De : Tamás Cservenák ta...@cservenak.net À : Maven Developers List dev@maven.apache.org Envoyé le : Mer 17 mars 2010, 23 h 50 min 59 s Objet : Re: [VOTE] Release Maven EJB Plugin 2.2.1 +1 On Wed, Mar 17, 2010 at 10:28 PM, Olivier Lamy ymailto=mailto:ol...@apache.org; href=mailto:ol...@apache.org;ol...@apache.org wrote: +1 2010/3/17 Benjamin Bentmann ymailto=mailto:benjamin.bentm...@udo.edu; href=mailto:benjamin.bentm...@udo.edu;benjamin.bentm...@udo.edu: Hi, We solved 2 issues: href=http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11134version=16294; target=_blank http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11134version=16294 There are still a couple of issues left in JIRA: href=http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11134status=1; target=_blank http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11134status=1 Staging repo: href=https://repository.apache.org/content/repositories/maven-001/; target=_blank https://repository.apache.org/content/repositories/maven-001/ Staging site (sync pending): href=http://maven.apache.org/plugins/maven-ejb-plugin-2.2.1/; target=_blank http://maven.apache.org/plugins/maven-ejb-plugin-2.2.1/ Guide to testing staged releases: href=http://maven.apache.org/guides/development/guide-testing-releases.html; target=_blank http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - To unsubscribe, e-mail: ymailto=mailto:dev-unsubscr...@maven.apache.org; href=mailto:dev-unsubscr...@maven.apache.org;dev-unsubscr...@maven.apache.org For additional commands, e-mail: ymailto=mailto:dev-h...@maven.apache.org; href=mailto:dev-h...@maven.apache.org;dev-h...@maven.apache.org -- Olivier href=http://twitter.com/olamy; target=_blank http://twitter.com/olamy target=_blank http://fr.linkedin.com/in/olamy - To unsubscribe, e-mail: href=mailto:dev-unsubscr...@maven.apache.org;dev-unsubscr...@maven.apache.org For additional commands, e-mail: href=mailto:dev-h...@maven.apache.org;dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : [VOTE] Release Apache Maven 3.0-alpha-7
+1 And +1 to change alpha to something less frightening for corporate projects. rc, preview, or milestone would be fine. Thanks Julien - Message d'origine De : nicolas de loof nicolas.del...@gmail.com À : Maven Developers List dev@maven.apache.org Envoyé le : Mer 10 Mars 2010, 9 h 15 min 17 s Objet : Re: [VOTE] Release Apache Maven 3.0-alpha-7 +1 Still partisant of a milestone naming convention to avoid assumptions on code quality and stability. 2010/3/10 Olivier Lamy +1 (IMHO we could change the name to at least beta as it works really fine :-) ). 2010/3/9 Benjamin Bentmann : Hi, We solved 22 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16087 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-007/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-007/org/apache/maven/apache-maven/3.0-alpha-7/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier http://twitter.com/olamy http://fr.linkedin.com/in/olamy http://www.viadeo.com/fr/profile/olivier.lamy7 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Maven 3 alpha status
Hi, Yesterday I spend 2 hours fixing a nasty bug with EAR plugin and dependency with type xml.zip. This dependency was declared in another module of the reactor, and was a dependency of a plugin (maven-andromda-plugin). So there is no reason that the ear plugin see this dependency. As I read Maven 3 is much more precise dealing with plugin classpath and dependencies, I asked the project leader to try with Maven 3 alpha 6. Hourra! It worked fine. So I told the project to migrate to Maven 3 but the project leader was reluctant as it is flagged as alpha. As it seems many Maven guys say Maven 3 alpha 6 is much better than Maven 2.2.1, could you please for next release use a version with a higher qualifier that will not afraid corporate people. IMHO beta will face the same issue, so I suggest rc or something like that. Best regards, Julien - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : Maven 3 alpha status
Hi, The bug is something similar to [1] (at leat same error message except the type is xml.zip in my case). The EAR module is building fine alone, but as soon as I launch a full reactor build, the build fails. Running with -X show the dependency is in the EAR plugin classpath but it should not be the case. The xml.zip dependency is used in that way: pom (of a transitive dependency of EAR module) plugin artifactIdandromda-maven-plugin/artifactId dependencies artifactIdfoo/artifactId typexml.zip/type /dependencies /plugin Do you think there is a chance this issue will be fixed in Maven 2.2.x? I fear the answer will be = fixed in Maven 3... [1] http://www.mail-archive.com/us...@maven.apache.org/msg94040.html - Message d'origine De : Stephane Nicoll stephane.nic...@gmail.com À : Maven Developers List dev@maven.apache.org Envoyé le : Ven 29 Janvier 2010, 15 h 14 min 59 s Objet : Re: Maven 3 alpha status Which bug are your talking about? Have you filled something in Jira? S. On Fri, Jan 29, 2010 at 12:08 PM, Julien HENRY wrote: Hi, Yesterday I spend 2 hours fixing a nasty bug with EAR plugin and dependency with type xml.zip. This dependency was declared in another module of the reactor, and was a dependency of a plugin (maven-andromda-plugin). So there is no reason that the ear plugin see this dependency. As I read Maven 3 is much more precise dealing with plugin classpath and dependencies, I asked the project leader to try with Maven 3 alpha 6. Hourra! It worked fine. So I told the project to migrate to Maven 3 but the project leader was reluctant as it is flagged as alpha. As it seems many Maven guys say Maven 3 alpha 6 is much better than Maven 2.2.1, could you please for next release use a version with a higher qualifier that will not afraid corporate people. IMHO beta will face the same issue, so I suggest rc or something like that. Best regards, Julien - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck -- S.Yegge - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : Re : [VOTE] Release Apache Maven 3.0-alpha-3
Another issue I have with Maven 3: trying to deploy an artifact with release:perform, I get the following error: [INFO] [ERROR] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find wagon which supports the requested protocol: dav - [Help 1] [INFO] [ERROR] Is it a known issue? - Message d'origine De : Julien HENRY henr...@yahoo.fr À : Maven Developers List dev@maven.apache.org Envoyé le : Mar 10 Novembre 2009, 15 h 56 min 15 s Objet : Re : [VOTE] Release Apache Maven 3.0-alpha-3 Hi, I don't know if it is related to Maven 3, but I'm not able to update to a newer SNAPSHOT that is available in my corporate repository, even by using the -U command line option. It seems Maven is not even asking the repository manager for a new version. What's wrong? mvn compile -U -X Apache Maven 3.0-alpha-3 (r834122; 2009-11-09 17:04:41+0100) [INFO] Scanning for projects... [DEBUG] Determining update check for snapshot com.mycompany:project-parent:1-SNAPSHOT (D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\maven-metadata-nexus.xml) from nexus (http://nexus.mycompany.fr/content/groups/all) [DEBUG] Searching for: nexus.maven-metadata-nexus.xml.lastUpdated in touchfile. [DEBUG] Reading resolution-state from: D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\resolver-status.properties [DEBUG] project-parent: resolved to version 1-20091110.084931-1 from repository nexus In the Nexus repository I have: project-parent-1-20091110.084931-1.pom project-parent-1-20091110.085551-2.pom Removing D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\resolver-status.properties is a workaround, but I was expecting -U option to force SNAPSHOT update whatever is in the local repository... Regards, Julien - Message d'origine De : Benjamin Bentmann À : Maven Developers List Envoyé le : Lun 9 Novembre 2009, 17 h 39 min 09 s Objet : [VOTE] Release Apache Maven 3.0-alpha-3 Hi, OK, here we go, another alpha release of Maven, for all those brave guys that want to take it for a test drive ;-) We solved many issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=14719 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-004/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0-alpha-3/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamim - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : Re : Re : [VOTE] Release Apache Maven 3.0-alpha-3
OK, thanks - Message d'origine De : Olivier Lamy ol...@apache.org À : Maven Developers List dev@maven.apache.org Envoyé le : Jeu 12 Novembre 2009, 16 h 58 min 00 s Objet : Re: Re : Re : [VOTE] Release Apache Maven 3.0-alpha-3 wagon weddav is not any more included in the distrib. You have to add it in your pom. -- Olivier 2009/11/12 Julien HENRY : Another issue I have with Maven 3: trying to deploy an artifact with release:perform, I get the following error: [INFO] [ERROR] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find wagon which supports the requested protocol: dav - [Help 1] [INFO] [ERROR] Is it a known issue? - Message d'origine De : Julien HENRY À : Maven Developers List Envoyé le : Mar 10 Novembre 2009, 15 h 56 min 15 s Objet : Re : [VOTE] Release Apache Maven 3.0-alpha-3 Hi, I don't know if it is related to Maven 3, but I'm not able to update to a newer SNAPSHOT that is available in my corporate repository, even by using the -U command line option. It seems Maven is not even asking the repository manager for a new version. What's wrong? mvn compile -U -X Apache Maven 3.0-alpha-3 (r834122; 2009-11-09 17:04:41+0100) [INFO] Scanning for projects... [DEBUG] Determining update check for snapshot com.mycompany:project-parent:1-SNAPSHOT (D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\maven-metadata-nexus.xml) from nexus (http://nexus.mycompany.fr/content/groups/all) [DEBUG] Searching for: nexus.maven-metadata-nexus.xml.lastUpdated in touchfile. [DEBUG] Reading resolution-state from: D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\resolver-status.properties [DEBUG] project-parent: resolved to version 1-20091110.084931-1 from repository nexus In the Nexus repository I have: project-parent-1-20091110.084931-1.pom project-parent-1-20091110.085551-2.pom Removing D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\resolver-status.properties is a workaround, but I was expecting -U option to force SNAPSHOT update whatever is in the local repository... Regards, Julien - Message d'origine De : Benjamin Bentmann À : Maven Developers List Envoyé le : Lun 9 Novembre 2009, 17 h 39 min 09 s Objet : [VOTE] Release Apache Maven 3.0-alpha-3 Hi, OK, here we go, another alpha release of Maven, for all those brave guys that want to take it for a test drive ;-) We solved many issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=14719 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-004/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0-alpha-3/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamim - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : [VOTE] Release Apache Maven 3.0-alpha-3
Hi, I don't know if it is related to Maven 3, but I'm not able to update to a newer SNAPSHOT that is available in my corporate repository, even by using the -U command line option. It seems Maven is not even asking the repository manager for a new version. What's wrong? mvn compile -U -X Apache Maven 3.0-alpha-3 (r834122; 2009-11-09 17:04:41+0100) [INFO] Scanning for projects... [DEBUG] Determining update check for snapshot com.mycompany:project-parent:1-SNAPSHOT (D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\maven-metadata-nexus.xml) from nexus (http://nexus.mycompany.fr/content/groups/all) [DEBUG] Searching for: nexus.maven-metadata-nexus.xml.lastUpdated in touchfile. [DEBUG] Reading resolution-state from: D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\resolver-status.properties [DEBUG] project-parent: resolved to version 1-20091110.084931-1 from repository nexus In the Nexus repository I have: project-parent-1-20091110.084931-1.pom project-parent-1-20091110.085551-2.pom Removing D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\resolver-status.properties is a workaround, but I was expecting -U option to force SNAPSHOT update whatever is in the local repository... Regards, Julien - Message d'origine De : Benjamin Bentmann benjamin.bentm...@udo.edu À : Maven Developers List dev@maven.apache.org Envoyé le : Lun 9 Novembre 2009, 17 h 39 min 09 s Objet : [VOTE] Release Apache Maven 3.0-alpha-3 Hi, OK, here we go, another alpha release of Maven, for all those brave guys that want to take it for a test drive ;-) We solved many issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=14719 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-004/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0-alpha-3/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamim - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : What's blocking releasing maven-compiler-plugin?
De : Stephen Connolly stephen.alan.conno...@gmail.com À : Maven Developers List dev@maven.apache.org Envoyé le : Lun 2 Novembre 2009, 8 h 49 min 47 s Objet : Re: What's blocking releasing maven-compiler-plugin? 2009/11/1 Jason van Zyl : I think it's akin to the surefire plugin. Where it's been so long that if we release this and people get the automatic updates and something is wrong it's not so fun. Well how about we release a 2.1-alpha-1 and up its minimum maven version to 2.0.9 That way anyone with earlier than 2.0.9 will not be able to use the alpha and anyone with 2.0.9+ will have a lock-down in place. +1 Another way would be to release 2.1-alpha-1 as 2.0.3-alpha-1-for-2.1 and re-release 2.0.2 as 2.0.4. If we stage them in one repository and then promote that repository in one go then anyone using 2.0.8- will just use m-c-p 2.0.4 which would be identical to 2.0.2, and we can get people with lock-downs to try the newer version. I don't like this solution as it will completly mess up dependency history. (my 2 cents) Maybe you and Benjamin can sort out a way to stage the plugin and run all the projects on the grid to see if it's all good. A similar strategy could be employed for the surefire plugin. The best we can do is run as many projects as we can with these new plugins to make sure they work in the wild as we've seen in the past that sometimes the releases are not so stellar. Yes I agree that this could be a first step. Then we could try as step 2 a 2.1-alpha-1 with the minimum maven version upped to 2.0.9 and finally we can roll the 2.1 release with maven 2.0.6 restored as the minimum version. Thoughts? Also, we will need to get surefire out the door. There are some good fixes in that, but let's get compiler out the door first and establish a process for that. I'm sure we could find a clean place to inject an override for the default version of the compiler plugin in 3.x and then use that version of Maven to build as many on the grid as we can. Can't think of a better way to test a core plugin to make sure we don't hose anyone. On 2009-11-01, at 12:59 PM, Stephen Connolly wrote: Now that we have maven-toolchains-plugin released, what is blocking rolling a release of maven-compiler-plugin? Toolchains support has been integrated since r649442. All the integration tests (3 of them) are passing. I am not seeing any issues in JIRA which are regressions (i.e. releasing now would probably not make things worse) There are currently 3 critical issues in JIRA: MCOMPILER-98 is an issue for plexus-compiler MCOMPILER-64 is just a higher memory requirement for large compiles with jdk6u4+ MCOMPILER-43 looks to be a plexus-compiler-eclipse issue If all that is somebody to play release manager I'll go running again. If getting a release requires applying patches or fixing issues I do not have the cycles at the moment -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Regression with maven-javadoc-plugin 2.6.1 and release:perform
Hi,
I have a multimodule project and it fails during release:perform with new
javadoc plugin.
I'm working on a simple project to open an issue, but let me explain the issue
in case someone can tell me if there is something wrong in my configuration.
Say my project is composed of:
Parent
- moduleA
- moduleB
- moduleC
moduleB depends on moduleC.
When release:perform execture mvn deploy -Dperformrelease=true on the freshly
checkouted parent, the build fails
log says:
INFO
INFO Building MyCompany moduleA
INFO task-segment: [deploy]
INFO
[...]
INFO [javadoc:jar {execution: attach-javadocs}]
INFO The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc' has
not be previously called for the project: 'com.mycompany:moduleB:jar:3.1.9'.
Trying to invoke it...
INFO MavenInvocationException: Error when invoking Maven, consult the invoker
log file:
D:\Projects\parent\target\checkout\moduleA\target\invoker\maven-javadoc-plugin1287795137.txt
INFO
INFO BUILD ERROR
INFO
And in the file there is:
Invoking Maven for the goals:
[org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc] with no properties
M2_HOME=d:\apache-maven-2.2.1\bin\..
MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=256m
JAVA_HOME=C:\Program Files\Java\jdk1.6.0_14\jre\..
JAVA_OPTS=null
INFO Scanning for projects...
INFO
INFO Building MyCompany - moduleB
INFOtask-segment:
[org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc]
INFO
INFO Preparing javadoc:javadoc
INFO No goals needed for project - skipping
Downloading: http:///com/mycompany/moduleC/3.1.9/moduleC-3.1.9.pom
INFO Unable to find resource 'com.mycompany:moduleC:pom:3.1.9' in repository
central (http://central)
INFO
ERROR BUILD ERROR
INFO
INFO Failed to resolve artifact.
Missing:
--
1) com.mycompany:moduleC:jar:3.1.9
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file xxx
Path to dependency:
1) com.mycompany:moduleB:jar:3.1.9
2) com.mycompany:moduleC:jar:3.1.9
Regards,
Julien
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re : Re : non-xml poms in 3.x
In the very specific case of groupId/artifactId/version pattern which is currently very verbose I would tend to agree to allow shorter syntax using attributes instead of elements. dependency groupId= artifactId= version= classifier= scope=/ plugin groupId= artifactId= version= configuration ... /configuration /plugin This is not what I consider a big change for endusers. Still my 2 cents. Regards, Julien - Message d'origine De : Jason Chaffee jason.chaf...@zilliontv.tv À : Maven Developers List dev@maven.apache.org Envoyé le : Samedi, 5 Septembre 2009, 1h00mn 02s Objet : RE: Re : non-xml poms in 3.x FYI, I know that in the past Resin supported both Elements and attributes in it's config XML. It was really neat. If you preferred one over the other, you could use it. Don't know if it is still that way though. Jason From: Jason Chaffee [jason.chaf...@zilliontv.tv] Sent: Friday, September 04, 2009 3:27 PM To: Maven Developers List Subject: RE: Re : non-xml poms in 3.x I like the idea of having some things as attributes. See the following links on information on when to use attributes and when to use elements. http://www.ibm.com/developerworks/xml/library/x-eleatt.html http://nedbatchelder.com/blog/200412/elements_vs_attributes.html http://www.x12.org/x12org/comments/X12Reference_Model_For_XML_Design.pdf In particular, from the X12 Reference Model for XML Design: 7.2.5 Elements vs. Attributes Description: Often it is possible to model a data item as a child element or an attribute. Benefits of Using Elements -They are more extensible because attributes can later be added to them without affecting a processing application. -They can contain other elements. For example, if you want to express a textual description using XHTML tags, this is not possible if description is an attribute. -They can be repeated. An element may only appear once now, but later you may wish to extend it to appear multiple times. -You have more control over the rules of their appearance. For example, you can say that a product can either have a number or a productCode child. This is not possible for attributes. -Their order is significant if specified as part of a sequence, while the order of attributes is not. Obviously, this is only an advantage if you care about the order. -When the values are lengthy, elements tend to be more readable than attributes. Disadvantages of Using Elements -Elements require start and end tags, so are therefore more verbose. (NOTE: not all elements require a start and end tag — elements can be declared in a single line.) Benefits of Using Attributes -They are less verbose. -Attributes can be added to the instance by specifying default values. Elements cannot (they must appear to receive a default value). -Attributes are atomic and cannot be extended and its existence should serve to remove any and all possible ambiguity of the element it describes. They are “adjectives” to the element “noun”. Disadvantages of Using Attributes -Attributes may not be extended by adding children, whereas a complex element may be extended by adding additional child elements or attributes. -If attributes are to be used in addition to elements for conveying business data, rules are required for specifying when a specific data item shall be an element or an attribute. Jason From: paulus.benedic...@gmail.com [paulus.benedic...@gmail.com] On Behalf Of Paul Benedict [pbened...@apache.org] Sent: Friday, September 04, 2009 3:05 PM To: Maven Developers List Subject: Re: Re : non-xml poms in 3.x Yes, the XML is verbose, and tooling helps but I think most people write it by hand. The only evolutionary change I support is the ability to specify simple nested elements as attributes. Paul On Fri, Sep 4, 2009 at 4:40 PM, Jason Chaffee wrote: For what it is worth, I have heard many complaints either about using XML and/or about the current structure of the XML as well. I have heard this from developers I have worked with and I have read some blogs about this too. I can't tell you where those blogs are now because I pretty much dismissed them as I like using XML myself. Jason From: Christian Edward Gruber [christianedwardgru...@gmail.com] Sent: Friday, September 04, 2009 2:29 PM To: Maven Developers List Subject: Re: Re : non-xml poms in 3.x Who said anything about a reasonable person? :) I don't have such a hatred - I'm quite used to it, but it has come up in nearly every client in the last 3 years - not as a final or deal-breaking barrier to adoption, but a barrier nonetheless. I'm happy to support it - I just need a seam or hook where I can provide something that pre-processes before
Re : non-xml poms in 3.x
Hi, De : Jason van Zyl jvan...@sonatype.com [...] Personally, I don't see a different XML format being any great usability gain. With editors and IDEs it's not that bad and you also have to consider what people are already accustom to. I honestly think another XML format would just be confusing and not really buy us a whole lot. The debate of clarity is subjective. I like the elements, you like attributes the debate could go on forever but as of today we got what we got. Just my 2 cents as a Maven evangelist in a big private company. Even if Maven is around for years now, basic endusers just start to get accustomed to pom.xml and Maven philosophy (really! people are far slowest to change than in OpenSource project team). Please, please don't mess everything. Small additions are fine, but I think a new format is a bad idea even if it is optional. One of advantage of Maven is standardization across all our projects. If there are several format allowed, some projects will start using new one when others are still using the former and it will lead to a total mess. So a big +1 to Jason. On 2009-09-04, at 5:21 PM, Christian Edward Gruber wrote: Hi all, So I saw Jason's highlights of 3.x future plans, and decoupling POMs from format. We're starting to use m3 on an open-source little project at Google, and the main problem people have with Maven has been the gawd-awful (not my words) of the xml format. I used the maven-yamlpom-plugin to simulate this, by having a wrapper script that syncs a pom.yml with the pom.xml before executing any other maven command, but it's a hack, and I'd rather (since we're already using 3 anyway) try to help us get to the point where i can just have a pom.yml and have maven (and its various integrations) understand it. So... 1. Any update on where that is - I haven't been following svn commits lately, but I'd like to start re-syncing wtih m3 progress 2. Any suggestions on where the seams are around pom building so I can start looking at how to provide an alternative format 3. Anyone already working on this specific thing? cheers, Christian. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/SonatypeNexus http://twitter.com/SonatypeM2E -- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : New release of release plugin
Thanks Olivier. De : Olivier Lamy ol...@apache.org À : Maven Developers List dev@maven.apache.org Envoyé le : Mardi, 25 Août 2009, 16h29mn 16s Objet : Re: New release of release plugin Hi, This require a scm release first. Some releases were pending due to release sources formats issue as we have solved this, we can certainly made more releases now. I can take this point and start this (but I can give an exact date it depends on my spare time :-) ). Thanks, -- Olivier 2009/8/25 Julien HENRY henr...@yahoo.fr: Hi, In my company we have pre-commit hook that expect a special comment for commit and tag. Because of MRELEASE-442 I can't use latest version of release plugin. Is it planned to do a new release as the current one was done in March? Regards, Julien -- Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
New release of release plugin
Hi, In my company we have pre-commit hook that expect a special comment for commit and tag. Because of MRELEASE-442 I can't use latest version of release plugin. Is it planned to do a new release as the current one was done in March? Regards, Julien
Re : [VOTE] Release Maven eclipse plugin version 2.6
Same problem for me. - Message d'origine De : Barrie Treloar baerr...@gmail.com À : Maven Developers List dev@maven.apache.org Envoyé le : Mardi, 24 Mars 2009, 3h13mn 30s Objet : Re: [VOTE] Release Maven eclipse plugin version 2.6 Does anyone else use xmlbeans in their projects? Could they check that generated sources get added to the classpath correctly. I'm noticing that they aren't. I'm not sure if that is a regression or a problem my end. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : Re : Maven eclipse plugin 2.6 regression with xmlbeans (was: [VOTE] Release Maven eclipse plugin version 2.6)
Sorry for the spam, but finally it seems it is an xmlbeans bug that I only discover now. So this is not a regression. http://jira.codehaus.org/browse/MXMLBEANS-54 Regards, Julien - Message d'origine De : Julien HENRY henr...@yahoo.fr À : Maven Developers List dev@maven.apache.org Envoyé le : Mercredi, 8 Avril 2009, 11h16mn 26s Objet : Re : Maven eclipse plugin 2.6 regression with xmlbeans (was: [VOTE] Release Maven eclipse plugin version 2.6) I've submitted a bug: MECLIPSE-549 - Message d'origine De : Julien HENRY henr...@yahoo.fr À : Maven Developers List dev@maven.apache.org Envoyé le : Mercredi, 8 Avril 2009, 10h37mn 07s Objet : Re : [VOTE] Release Maven eclipse plugin version 2.6 Same problem for me. - Message d'origine De : Barrie Treloar baerr...@gmail.com À : Maven Developers List dev@maven.apache.org Envoyé le : Mardi, 24 Mars 2009, 3h13mn 30s Objet : Re: [VOTE] Release Maven eclipse plugin version 2.6 Does anyone else use xmlbeans in their projects? Could they check that generated sources get added to the classpath correctly. I'm noticing that they aren't. I'm not sure if that is a regression or a problem my end. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : Maven eclipse plugin 2.6 regression with xmlbeans (was: [VOTE] Release Maven eclipse plugin version 2.6)
I've submitted a bug: MECLIPSE-549 - Message d'origine De : Julien HENRY henr...@yahoo.fr À : Maven Developers List dev@maven.apache.org Envoyé le : Mercredi, 8 Avril 2009, 10h37mn 07s Objet : Re : [VOTE] Release Maven eclipse plugin version 2.6 Same problem for me. - Message d'origine De : Barrie Treloar baerr...@gmail.com À : Maven Developers List dev@maven.apache.org Envoyé le : Mardi, 24 Mars 2009, 3h13mn 30s Objet : Re: [VOTE] Release Maven eclipse plugin version 2.6 Does anyone else use xmlbeans in their projects? Could they check that generated sources get added to the classpath correctly. I'm noticing that they aren't. I'm not sure if that is a regression or a problem my end. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : [VOTE] Release Maven eclipse plugin version 2.6
I got the following error: mvn clean install eclipse:eclipse -Pstaged -cpu ... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-eclipse-plugin:2.6:eclipse': Unable to load the mojo 'org.apache.maven.plugins:maven-eclipse-plugin:2.6:eclipse' in the plugin 'org.apache.maven.plugins:maven-eclipse-plugin'. A required class is missing: org/codehaus/plexus/resource/loader/ResourceNotFoundException mvn -v Apache Maven 2.1.0-RC3 (r754932; 2009-03-16 17:31:06+0100) Java version: 1.4.2_17 Java home: C:\j2sdk1.4.2_17\jre Default locale: fr_FR, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows Do you want I open an issue in JIRA with full stack trace? Regards, Julien - Message d'origine De : Barrie Treloar baerr...@gmail.com À : Maven Developers List dev@maven.apache.org Envoyé le : Mardi, 24 Mars 2009, 1h05mn 40s Objet : [VOTE] Release Maven eclipse plugin version 2.6 Hi, We solved 35 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14163styleName=HtmlprojectId=11133 There remaining issues left in JIRA: http://jira.codehaus..org/secure/IssueNavigator.jspa?reset=truepid=11133status=1 Staging repo: https://repository.apache.org/content/repositories/maven-staging-52acfb2f215fcf/ Staging site: http://maven.apache.org/plugins/maven-eclipse-plugin-2.6/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : [VOTE] Release Maven eclipse plugin version 2.6
Hi, It seems I can't manage to download the plugin pom.xml. Only the JAR is downloaded in my local repo: mvn -Pstaged-releases clean install eclipse:eclipse -cpu -X + Error stacktraces are turned on. Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100) Java version: 1.6.0_12 Java home: C:\Program Files\Java\jdk1.6.0_12\jre Default locale: fr_FR, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\jhenry\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'D:\apache-maven-2.1.0\bin\..\conf\plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Searching for parent-POM: com.X.itdemand:XX-itdemand:pom:1.0.2-SNAPSHOT of project: null:XX-itdemand-webapp:war:null in relative path: ../pom.xml [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for project: null:XXX-itdemand-webapp:war:null [DEBUG] Adding managed dependencies for unknown:XXX-itdemand-webapp [DEBUG] com.XXX.itdemand:XXX-itdemand-webapp:war:1.0.2-SNAPSHOT [DEBUG] com..itdemand:XXX-itdemand-ear:ejb:1.0.2-SNAPSHOT [DEBUG] Retrieving parent-POM: org.apache.maven.release:maven-release:pom:5 for project: org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.0-beta-8 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:9 for project: org.apache.maven.release:maven-release:pom:5 from the repository.. [DEBUG] Retrieving parent-POM: org.apache:apache:pom:4 for project: org..apache.maven:maven-parent:pom:9 from the repository. [DEBUG] Adding managed dependencies for org.apache.maven.plugins:maven-release-plugin [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.5.6 [DEBUG] maven-enforcer-plugin: resolved to version 1.0-alpha-3 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins:pom:8 for project: org.apache.maven.plugins:maven-enforcer-plugin:maven-plugin:1.0-alpha-3 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:5 for project: org.apache.maven.plugins:maven-plugins:pom:8 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache:pom:3 for project: org.apache.maven:maven-parent:pom:5 from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.mojo.hibernate3:maven-hibernate3:pom:2.2 for project: org.codehaus.mojo:hibernate3-maven-plugin:maven-plugin:null from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo-parent:pom:20 for project: org.codehaus.mojo.hibernate3:maven-hibernate3:pom:2.2 from the repository. [DEBUG] Adding managed dependencies for org.codehaus.mojo:hibernate3-maven-plugin [DEBUG] hsqldb:hsqldb:jar:1.8.0.7:test [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0.6 [DEBUG] org.apache.maven:maven-project:jar:2.0.6 [DEBUG] org.apache.maven:maven-model:jar:2.0.6 [DEBUG] org.apache.maven:maven-artifact:jar:2.0.6 [DEBUG] org.apache.maven.shared:maven-plugin-testing-harness:jar:1.1 [DEBUG] org.hibernate:hibernate-core:jar:3.3.1.GA [DEBUG] org.hibernate:ejb3-persistence:jar:1.0.2.GA [DEBUG] org.hibernate:hibernate-entitymanager:jar:3.4.0.GA [DEBUG] org.hibernate:hibernate-tools:jar:3.2.3..GA [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.5.6 [DEBUG] org.apache.geronimo.specs:geronimo-jta_1.0.1B_spec:jar:1.1.1:runtime [DEBUG] log4j:log4j:jar:1.2.14:runtime [DEBUG] org.slf4j:slf4j-log4j12:jar:1.5.6:runtime [DEBUG] org.slf4j:slf4j-api:jar:1.5.6:runtime [DEBUG] org.slf4j:jcl-over-slf4j:jar:1.5.6:runtime [DEBUG] junit:junit:jar:3.8.2:test [DEBUG] cobertura-maven-plugin: resolved to version 2.2 from repository central [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo:pom:16 for project: null:cobertura-maven-plugin:maven-plugin:2.2 from the repository. [DEBUG] Adding managed dependencies for unknown:cobertura-maven-plugin [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0 [DEBUG] junit:junit:jar:3.8.1:test [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo-parent:pom:18 for project: null:xmlbeans-maven-plugin:maven-plugin:2.3.2 from the repository. [DEBUG] Adding managed dependencies for unknown:xmlbeans-maven-plugin [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0 [DEBUG] junit:junit:jar:3.8.2:test [INFO] Searching repository for plugin with prefix: 'eclipse'. [DEBUG] Loading plugin prefixes from group: org..codehaus.mojo [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins [DEBUG] maven-eclipse-plugin: resolved to version 2.6 from repository central [DEBUG] Trying repository central [DEBUG] Using mirror: http://pic-java-nce.sud.capgemini.fr:8090/archiva/repository/central (id: central) [DEBUG] Checking for pre-existing User-Agent configuration. [DEBUG] Adding User-Agent configuration. [DEBUG] Connecting to repository: 'central' with url:
Re : Re : [VOTE] Release Maven eclipse plugin version 2.6
Done: http://jira.codehaus.org/browse/MECLIPSE-536 - Message d'origine De : Arnaud HERITIER aherit...@gmail.com À : Maven Developers List dev@maven.apache.org Envoyé le : Mardi, 24 Mars 2009, 10h23mn 10s Objet : Re: Re : [VOTE] Release Maven eclipse plugin version 2.6 yes please. 2009/3/24 Julien HENRY henr...@yahoo.fr I got the following error: mvn clean install eclipse:eclipse -Pstaged -cpu ... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org..apache.maven.plugins:maven-eclipse-plugin:2.6:eclipse': Unable to load the mojo 'org.apache.maven.plugins:maven-eclipse-plugin:2.6:eclipse' in the plugin 'org.apache.maven.plugins:maven-eclipse-plugin'. A required class is missing: org/codehaus/plexus/resource/loader/ResourceNotFoundException mvn -v Apache Maven 2.1.0-RC3 (r754932; 2009-03-16 17:31:06+0100) Java version: 1.4.2_17 Java home: C:\j2sdk1.4.2_17\jre Default locale: fr_FR, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows Do you want I open an issue in JIRA with full stack trace? Regards, Julien - Message d'origine De : Barrie Treloar baerr...@gmail.com À : Maven Developers List dev@maven.apache.org Envoyé le : Mardi, 24 Mars 2009, 1h05mn 40s Objet : [VOTE] Release Maven eclipse plugin version 2.6 Hi, We solved 35 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14163styleName=HtmlprojectId=11133 There remaining issues left in JIRA: http://jira.codehaus. .org/secure/IssueNavigator.jspa?reset=truepid=11133status=1 Staging repo: https://repository.apache.org/content/repositories/maven-staging-52acfb2f215fcf/ Staging site: http://maven.apache.org/plugins/maven-eclipse-plugin-2.6/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Arnaud - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : Re : [VOTE] Release Maven eclipse plugin version 2.6
yes - Message d'origine De : Arnaud HERITIER aherit...@gmail.com À : Maven Developers List dev@maven.apache.org Envoyé le : Mardi, 24 Mars 2009, 14h35mn 20s Objet : Re: Re : [VOTE] Release Maven eclipse plugin version 2.6 did you try to remove your 2.6 copy locally to retry to download the pom ? 2009/3/24 Julien HENRY henr...@yahoo.fr Hi, It seems I can't manage to download the plugin pom.xml. Only the JAR is downloaded in my local repo: mvn -Pstaged-releases clean install eclipse:eclipse -cpu -X + Error stacktraces are turned on. Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100) Java version: 1.6.0_12 Java home: C:\Program Files\Java\jdk1.6.0_12\jre Default locale: fr_FR, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\jhenry\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'D:\apache-maven-2.1.0\bin\..\conf\plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Searching for parent-POM: com.X.itdemand:XX-itdemand:pom:1.0.2-SNAPSHOT of project: null:XX-itdemand-webapp:war:null in relative path: ../pom.xml [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for project: null:XXX-itdemand-webapp:war:null [DEBUG] Adding managed dependencies for unknown:XXX-itdemand-webapp [DEBUG] com.XXX..itdemand:XXX-itdemand-webapp:war:1.0.2-SNAPSHOT [DEBUG] com..itdemand:XXX-itdemand-ear:ejb:1.0.2-SNAPSHOT [DEBUG] Retrieving parent-POM: org.apache.maven.release:maven-release:pom:5 for project: org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.0-beta-8 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:9 for project: org.apache.maven.release:maven-release:pom:5 from the repository.. [DEBUG] Retrieving parent-POM: org.apache:apache:pom:4 for project: org..apache.maven:maven-parent:pom:9 from the repository. [DEBUG] Adding managed dependencies for org.apache.maven.plugins:maven-release-plugin [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.5.6 [DEBUG] maven-enforcer-plugin: resolved to version 1.0-alpha-3 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins:pom:8 for project: org.apache.maven.plugins:maven-enforcer-plugin:maven-plugin:1.0-alpha-3 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:5 for project: org.apache.maven.plugins:maven-plugins:pom:8 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache:pom:3 for project: org.apache.maven:maven-parent:pom:5 from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.mojo.hibernate3:maven-hibernate3:pom:2.2 for project: org.codehaus.mojo:hibernate3-maven-plugin:maven-plugin:null from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo-parent:pom:20 for project: org.codehaus.mojo.hibernate3:maven-hibernate3:pom:2.2 from the repository. [DEBUG] Adding managed dependencies for org.codehaus.mojo:hibernate3-maven-plugin [DEBUG] hsqldb:hsqldb:jar:1.8.0.7:test [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0.6 [DEBUG] org.apache.maven:maven-project:jar:2.0.6 [DEBUG] org.apache.maven:maven-model:jar:2.0.6 [DEBUG] org.apache.maven:maven-artifact:jar:2.0.6 [DEBUG] org.apache.maven.shared:maven-plugin-testing-harness:jar:1.1 [DEBUG] org.hibernate:hibernate-core:jar:3.3.1.GA [DEBUG] org.hibernate:ejb3-persistence:jar:1.0.2..GA [DEBUG] org.hibernate:hibernate-entitymanager:jar:3.4.0.GA [DEBUG] org.hibernate:hibernate-tools:jar:3.2.3..GA [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.5.6 [DEBUG] org.apache.geronimo.specs:geronimo-jta_1.0.1B_spec:jar:1.1.1:runtime [DEBUG] log4j:log4j:jar:1..2.14:runtime [DEBUG] org.slf4j:slf4j-log4j12:jar:1.5.6:runtime [DEBUG] org.slf4j:slf4j-api:jar:1.5.6:runtime [DEBUG] org.slf4j:jcl-over-slf4j:jar:1.5.6:runtime [DEBUG] junit:junit:jar:3.8.2:test [DEBUG] cobertura-maven-plugin: resolved to version 2.2 from repository central [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo:pom:16 for project: null:cobertura-maven-plugin:maven-plugin:2.2 from the repository. [DEBUG] Adding managed dependencies for unknown:cobertura-maven-plugin [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0 [DEBUG] junit:junit:jar:3.8.1:test [DEBUG] Retrieving parent-POM: org.codehaus..mojo:mojo-parent:pom:18 for project: null:xmlbeans-maven-plugin:maven-plugin:2.3.2 from the repository. [DEBUG] Adding managed dependencies for unknown:xmlbeans-maven-plugin [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0 [DEBUG] junit:junit:jar:3.8.2:test [INFO] Searching repository for plugin with prefix: 'eclipse'. [DEBUG] Loading plugin prefixes from group: org..codehaus.mojo [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins [DEBUG] maven
Re : [PLEASE TEST] Maven 2.1.0-RC3
Works fine for me. Good job! - Message d'origine De : John Casey jdca...@commonjava.org À : Maven Developers List dev@maven.apache.org Envoyé le : Lundi, 16 Mars 2009, 17h51mn 16s Objet : [PLEASE TEST] Maven 2.1.0-RC3 Okay, It looks like the last known bugs are resolved for 2.1.0. So, let's take another look things with RC3, and if everything is clean I'll call a vote in the next day or two. http://tinyurl.com/maven-2-1-0-RC3 (https://repository.apache.org/content/repositories/maven-staging-5078cd01de9bd9/org/apache/maven/apache-maven/2.1.0-RC3/) Thanks for your patience. -john - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : [PLEASE TEST] Maven 2.1.0-RC1
Works fine and quickly, but here is a small question. In case of error, is it
possible to avoid duplication of the error message?
Example:
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
Failure executing javac, but could not parse the error:
javac: invalid target release: 1.5
Usage: javac options source files
where possible options include:
-gGenerate all debugging info
-g:none Generate no debugging info
-g:{lines,vars,source}Generate only some debugging info
-nowarn Generate no warnings
-verbose Output messages about what the compiler is doing
-deprecation Output source locations where deprecated APIs are
used
-classpath path Specify where to find user class files
-sourcepath pathSpecify where to find input source files
-bootclasspath path Override location of bootstrap class files
-extdirs dirs Override location of installed extensions
-d directorySpecify where to place generated class files
-encoding encoding Specify character encoding used by source files
-source release Provide source compatibility with specified release
-target release Generate class files for specific VM version
-help Print a synopsis of standard options
Failure executing javac, but could not parse the error:
javac: invalid target release: 1.5
Usage: javac options source files
where possible options include:
-gGenerate all debugging info
-g:none Generate no debugging info
-g:{lines,vars,source}Generate only some debugging info
-nowarn Generate no warnings
-verbose Output messages about what the compiler is doing
-deprecation Output source locations where deprecated APIs are
used
-classpath path Specify where to find user class files
-sourcepath pathSpecify where to find input source files
-bootclasspath path Override location of bootstrap class files
-extdirs dirs Override location of installed extensions
-d directorySpecify where to place generated class files
-encoding encoding Specify character encoding used by source files
-source release Provide source compatibility with specified release
-target release Generate class files for specific VM version
-help Print a synopsis of standard options
[INFO]
- Message d'origine
De : John Casey jdca...@commonjava.org
À : Maven Developers List dev@maven.apache.org
Envoyé le : Lundi, 9 Mars 2009, 17h00mn 13s
Objet : [PLEASE TEST] Maven 2.1.0-RC1
Hi everyone,
I've rolled the first release candidate for Maven 2.1.0. It's available at:
http://tinyurl.com/maven-2-1-0-RC1
(https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/)
The staging repository root is at:
https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
If you have time, please take a look and see if you can break it!
BTW, the JIRA version notes for this release are at:
http://tinyurl..com/maven-2-1-0-jira
(http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14587)
If we can't find anything wrong with this release candidate after maybe four or
five days at most, I'll call the vote for a release. Hopefully we can coast in
on the effort we put forth in the last release, at least to some extent! :-)
Thanks,
-john
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Please release new version of Javadoc plugin
Hi Maven team! JWebUnit project is bitten by http://jira.codehaus.org/browse/MJAVADOC-181 I would like to know if someone could apply the provided patch and push a new SNAPSHOT (and even better release a new version to avoid a SNAPSHOT dependency). Thank you very much Julien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re : [PLEASE TEST] Maven 2.0.10-RC2
During my build, Maven try to download artifacts from http://cvs.apache.org/maven-snapshot-repository I don't know where this repository come from (it's not in my pom.xml nor in my settings.xml). Is it a bug? Regards - Message d'origine De : Brett Porter [EMAIL PROTECTED] À : Maven Developers List dev@maven.apache.org Envoyé le : Jeudi, 24 Juillet 2008, 6h52mn 20s Objet : Re: [PLEASE TEST] Maven 2.0.10-RC2 Fixed in SVN (you can also see comment on the RC1 thread for the reason this was occuring). - Brett On 24/07/2008, at 1:10 PM, Michael McCallum wrote: I'm getting stack traces rather than the nice message when an artifact does not exist the repository... Downloading: http://mvn.somedomaindev.co.nz/central/nz/co/somedomain/nz.co.somedomain.parent/14-java4/nz.co.somedomain.parent-14-java4.pom org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate resource in repository at org .apache .maven .wagon .providers .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java: 132) at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java: 116) at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61) at org .apache .maven .artifact .manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java: 474) at org .apache .maven .artifact .manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:363) at org .apache .maven .artifact .manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:318) at org .apache .maven .artifact .resolver .DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:200) at org .apache .maven .artifact .resolver .DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74) at org .apache .maven .project .DefaultMavenProjectBuilder .findModelFromRepository(DefaultMavenProjectBuilder.java:557) at org .apache .maven .project .DefaultMavenProjectBuilder .assembleLineage(DefaultMavenProjectBuilder.java:1393) at org .apache .maven .project .DefaultMavenProjectBuilder .buildInternal(DefaultMavenProjectBuilder.java:822) at org .apache .maven .project .DefaultMavenProjectBuilder .buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:507) at org .apache .maven .project .DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:199) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java: 578) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: 292) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun .reflect .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun .reflect .DelegatingMethodAccessorImpl .invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.io.FileNotFoundException: http://mvn.somedomaindev.co.nz/central/nz/co/somedomain/nz.co.somedomain.parent/14-java4/nz.co.somedomain.parent-14-java4.pom at sun .net .www .protocol .http.HttpURLConnection.getInputStream(HttpURLConnection.java:1239) at org .apache .maven .wagon .providers .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java: 115) -- Michael McCallum Development Lead somedomain Ltd cell: 021.576.907 msn: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] aim: gholamses http://www.somedomain.co.nz -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Envoyez avec Yahoo! Mail. Une boite mail plus intelligente http://mail.yahoo.fr
Re : Re : [PLEASE TEST] Maven 2.0.10-RC2
I've opened an issue (MNG-3678) with steps to reproduce. This problem is not related to Maven 2.0.10 (I have reproduced it with 2.0.9). Note that in my scenario the repositories involved are http://snapshots.repository.codehaus.org and http://people.apache.org/repo/m2-snapshot-repository so I suppose there are other cases where you can have http://cvs.apache.org/maven-snapshot-repository being accessed. Regards, Julien - Message d'origine De : Dan Tran [EMAIL PROTECTED] À : Maven Developers List dev@maven.apache.org Envoyé le : Jeudi, 24 Juillet 2008, 9h35mn 37s Objet : Re: Re : [PLEASE TEST] Maven 2.0.10-RC2 I have seen this in 2.0.9 but not able to produce it. -D On Thu, Jul 24, 2008 at 12:31 AM, Julien HENRY [EMAIL PROTECTED] wrote: During my build, Maven try to download artifacts from http://cvs.apache.org/maven-snapshot-repository I don't know where this repository come from (it's not in my pom.xml nor in my settings.xml). Is it a bug? Regards - Message d'origine De : Brett Porter [EMAIL PROTECTED] À : Maven Developers List dev@maven.apache.org Envoyé le : Jeudi, 24 Juillet 2008, 6h52mn 20s Objet : Re: [PLEASE TEST] Maven 2.0.10-RC2 Fixed in SVN (you can also see comment on the RC1 thread for the reason this was occuring). - Brett On 24/07/2008, at 1:10 PM, Michael McCallum wrote: I'm getting stack traces rather than the nice message when an artifact does not exist the repository... Downloading: http://mvn.somedomaindev.co.nz/central/nz/co/somedomain/nz.co.somedomain.parent/14-java4/nz.co.somedomain.parent-14-java4.pom org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate resource in repository at org .apache .maven .wagon .providers .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java: 132) at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java: 116) at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61) at org .apache .maven .artifact .manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java: 474) at org .apache .maven .artifact .manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:363) at org .apache .maven .artifact .manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:318) at org .apache .maven .artifact .resolver .DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:200) at org .apache .maven .artifact .resolver .DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74) at org .apache .maven .project .DefaultMavenProjectBuilder .findModelFromRepository(DefaultMavenProjectBuilder.java:557) at org .apache .maven .project .DefaultMavenProjectBuilder .assembleLineage(DefaultMavenProjectBuilder.java:1393) at org .apache .maven .project .DefaultMavenProjectBuilder .buildInternal(DefaultMavenProjectBuilder.java:822) at org .apache .maven .project .DefaultMavenProjectBuilder .buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:507) at org .apache .maven .project .DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:199) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java: 578) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: 292) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun .reflect .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun .reflect .DelegatingMethodAccessorImpl .invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.io.FileNotFoundException: http://mvn.somedomaindev.co.nz/central/nz/co/somedomain/nz.co.somedomain.parent/14-java4/nz.co.somedomain.parent-14-java4.pom at sun .net .www .protocol .http.HttpURLConnection.getInputStream(HttpURLConnection.java:1239) at org .apache .maven .wagon .providers .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java: 115) -- Michael McCallum Development Lead somedomain Ltd cell: 021.576.907 msn: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] aim: gholamses http://www.somedomain.co.nz -- Michael McCallum
Re : [PLEASE TEST] Maven 2.0.10-RC1
Hi John,
I can't manage to build JWebUnit anymore with 2.0.10-RC1. One of my module is
depending on the other one using this syntax:
dependency
groupIdnet.sourceforge.jwebunit/groupId
artifactIdjwebunit-webtestcase-generator/artifactId
version${pom.version}/version
/dependency
And Maven try to download:
[INFO] Building Core - API
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory D:\Perso\jwebunit\jwebunit-core\target
[INFO] Preparing exec:java
[WARNING] Removing: java from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
Downloading:
http://repository.codehaus.org/net/sourceforge/jwebunit/jwebunit-webtestcase-generator/${pom.version}/jwebunit-webtestcase-generator-${pom.version}.pom
org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate resource
in repository
I tried to change it to ${project.version} and it doesn't work also.
If you want to try just checkout
https://jwebunit.svn.sourceforge.net/svnroot/jwebunit/trunk
Regards,
Julien
- Message d'origine
De : John Casey [EMAIL PROTECTED]
À : Maven Developers List dev@maven.apache.org
Envoyé le : Mercredi, 16 Juillet 2008, 0h23mn 46s
Objet : [PLEASE TEST] Maven 2.0.10-RC1
Hi again,
As promised, I've staged the first release candidate for Maven 2.0.10 here:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/
The issues resolved for this release (so far) are here:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112
If you look at the Road Map view in JIRA, you'll notice that MNG-3639 is
still open. This is because one of the possible solutions to this issue
- and the only one that the Maven project really has control over -
depends on re-releasing a new version of commons-build-plugin that will
depend on the eventual 2.0.10 version of maven-script-ant.
Please, try out this release candidate and let me know what's broken!
Once things stabilize, I'll kick it out to the users to have a go, then
if it's still stable after that (or, whatever RC we find is stable at
that point), I'll call a vote to release. At that point, I'll run a new
build to generate artifacts without the RC# suffix in the version.
Thanks!
-john
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_
Envoyez avec Yahoo! Mail. Une boite mail plus intelligente http://mail.yahoo.fr
Re : Re : [PLEASE TEST] Maven 2.0.10-RC1
Thanks John. I will try next RC and comment in Jira issue if there is still a
problem.
- Message d'origine
De : John Casey [EMAIL PROTECTED]
À : Maven Developers List dev@maven.apache.org
Envoyé le : Vendredi, 18 Juillet 2008, 17h18mn 53s
Objet : Re: Re : [PLEASE TEST] Maven 2.0.10-RC1
Okay, I've duplicated the problem, and generated a simple test case to
replicate it separately from the JWebUnit project, so we can create an
integration test. The JIRA issue is:
http://jira.codehaus.org/browse/MNG-3671
I have a fix for this issue (I believe), but still need to formalize the
attached test POM into an integration test before closing this issue.
-john
John Casey wrote:
I'll give it a try today and see if I can reproduce the problem. Then,
we should file a JIRA ticket so it shows up on the release notes, and
I'll fix it.
Thanks for testing!
-john
Julien HENRY wrote:
Hi John,
I can't manage to build JWebUnit anymore with 2.0.10-RC1. One of my
module is depending on the other one using this syntax:
dependency
groupIdnet.sourceforge.jwebunit/groupId
artifactIdjwebunit-webtestcase-generator/artifactId
version${pom.version}/version
/dependency
And Maven try to download:
[INFO] Building Core - API
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory D:\Perso\jwebunit\jwebunit-core\target
[INFO] Preparing exec:java
[WARNING] Removing: java from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
Downloading:
http://repository.codehaus.org/net/sourceforge/jwebunit/jwebunit-webtestcase-generator/${pom.version}/jwebunit-webtestcase-generator-${pom.version}.pom
org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate
resource in repository
I tried to change it to ${project.version} and it doesn't work also.
If you want to try just checkout
https://jwebunit.svn.sourceforge.net/svnroot/jwebunit/trunk
Regards,
Julien
- Message d'origine
De : John Casey [EMAIL PROTECTED]
À : Maven Developers List dev@maven.apache.org
Envoyé le : Mercredi, 16 Juillet 2008, 0h23mn 46s
Objet : [PLEASE TEST] Maven 2.0.10-RC1
Hi again,
As promised, I've staged the first release candidate for Maven 2.0.10
here:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/
The issues resolved for this release (so far) are here:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112
If you look at the Road Map view in JIRA, you'll notice that MNG-3639
is still open. This is because one of the possible solutions to this
issue - and the only one that the Maven project really has control
over - depends on re-releasing a new version of commons-build-plugin
that will depend on the eventual 2.0.10 version of maven-script-ant.
Please, try out this release candidate and let me know what's broken!
Once things stabilize, I'll kick it out to the users to have a go,
then if it's still stable after that (or, whatever RC we find is
stable at that point), I'll call a vote to release. At that point,
I'll run a new build to generate artifacts without the RC# suffix in
the version.
Thanks!
-john
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_
Envoyez avec Yahoo! Mail. Une boite mail plus intelligente http://mail.yahoo.fr
RE : [VOTE] Release Maven 2.0.7 (take 2)
Hi, Was something done concerning my problem with error not stopping build during release? ++ Julien --- Jason van Zyl [EMAIL PROTECTED] a écrit : Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.7
IMHO it should be fixed before 2.0.7. If not, the release process will be broken (the scm tag will be done even if something goes wrong during the build). --- Brett Porter [EMAIL PROTECTED] a écrit : It's possibly a problem in the windows batch file in 2.0.7 - I think it was changed and it may no longer be correctly propogating the error code. - Brett On 14/06/2007, at 1:07 AM, Jason van Zyl wrote: Is this not a release plugin problem? If this error halted your build, was this with an older version of the release plugin? On 13 Jun 07, at 8:01 AM 13 Jun 07, Julien HENRY wrote: (non-binding) -1 I just tried to prepare a release in a multi-module project. Usually, the release:prepare failed (because Maven does not find released dependent artifact). An easy fix was to run mvn install and then mvn release:prepare again. The problem I have with maven-2.0.7 is release preparation was not stopped (build is successful). The exception was ignored, and the release is not safe (what happend when it is a serious error?) Here is the log : [INFO] [release:prepare] [INFO] Verifying that there are no local modifications... [INFO] Executing: svn --non-interactive status [INFO] Working directory: [INFO] Checking dependencies and plugins for snapshots ... What is the release version for XXX? (X) 3.0.11: : What is the release version for ? () 3.0.11: : ... What is SCM release tag or label for X? (X) xx-3.0.11: : What is the new development version for XXX? (X) 3.0.12-SNAPSHOT: : What is the new development version for ? (YY) 3.0.12-SNAPSHOT: : ... [INFO] Transforming 'XXX'... [INFO] Transforming 'YYY'... ... [INFO] Executing preparation goals 'clean integration-test'... [INFO] Executing: mvn clean integration-test --no-plugin-updates [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] X [INFO] Y [INFO] ... [INFO] - --- [INFO] Building [INFO]task-segment: [clean, integration-test] [INFO] - --- [INFO] [clean:clean] [INFO] - --- [INFO] Building YYY [INFO]task-segment: [clean, integration-test] [INFO] - --- [INFO] [clean:clean] ... [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] No sources to compile [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] No sources to compile [INFO] [surefire:test] [INFO] No tests to run. [INFO] [war:war] [INFO] Exploding webapp... [INFO] Assembling webapp YYY in D:\Projets\xxx\target\YY-3.0.11 [INFO] Copy webapp webResources to D:\Projets\xx\target \YY-3.0.11 [INFO] - --- [ERROR] FATAL ERROR [INFO] - --- [INFO] basedir C:\Documents and Settings\jhenry\.m2\repository\xxx \YY\3.0.11 does not exist [INFO] - --- [INFO] Trace java.lang.IllegalStateException: basedir C:\Documents and Settings\jhenry\.m2\repository\x\Y \3.0.11 does not exist at org.codehaus.plexus.util.DirectoryScanner.scan (DirectoryScanner.java:542) at org.apache.maven.plugin.war.AbstractWarMojo.getWarFiles (AbstractWarMojo.java:824) at org.apache.maven.plugin.war.AbstractWarMojo.copyResources (AbstractWarMojo.java:408) at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp (AbstractWarMojo.java:518) at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp (AbstractWarMojo.java:347) at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java: 164) at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:130) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:443
Re: [VOTE] Release Maven 2.0.7
(non-binding) -1 I just tried to prepare a release in a multi-module project. Usually, the release:prepare failed (because Maven does not find released dependent artifact). An easy fix was to run mvn install and then mvn release:prepare again. The problem I have with maven-2.0.7 is release preparation was not stopped (build is successful). The exception was ignored, and the release is not safe (what happend when it is a serious error?) Here is the log : [INFO] [release:prepare] [INFO] Verifying that there are no local modifications... [INFO] Executing: svn --non-interactive status [INFO] Working directory: [INFO] Checking dependencies and plugins for snapshots ... What is the release version for XXX? (X) 3.0.11: : What is the release version for ? () 3.0.11: : ... What is SCM release tag or label for X? (X) xx-3.0.11: : What is the new development version for XXX? (X) 3.0.12-SNAPSHOT: : What is the new development version for ? (YY) 3.0.12-SNAPSHOT: : ... [INFO] Transforming 'XXX'... [INFO] Transforming 'YYY'... ... [INFO] Executing preparation goals 'clean integration-test'... [INFO] Executing: mvn clean integration-test --no-plugin-updates [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] X [INFO] Y [INFO] ... [INFO] [INFO] Building [INFO]task-segment: [clean, integration-test] [INFO] [INFO] [clean:clean] [INFO] [INFO] Building YYY [INFO]task-segment: [clean, integration-test] [INFO] [INFO] [clean:clean] ... [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] No sources to compile [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] No sources to compile [INFO] [surefire:test] [INFO] No tests to run. [INFO] [war:war] [INFO] Exploding webapp... [INFO] Assembling webapp YYY in D:\Projets\xxx\target\YY-3.0.11 [INFO] Copy webapp webResources to D:\Projets\xx\target\YY-3.0.11 [INFO] [ERROR] FATAL ERROR [INFO] [INFO] basedir C:\Documents and Settings\jhenry\.m2\repository\xxx\YY\3.0.11 does not exist [INFO] [INFO] Trace java.lang.IllegalStateException: basedir C:\Documents and Settings\jhenry\.m2\repository\x\Y\3.0.11 does not exist at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:542) at org.apache.maven.plugin.war.AbstractWarMojo.getWarFiles(AbstractWarMojo.java:824) at org.apache.maven.plugin.war.AbstractWarMojo.copyResources(AbstractWarMojo.java:408) at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:518) at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:347) at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:164) at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:130) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
Invalid link on Maven site
Hi, On this page : http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html The link : Check out the Guide to Configuring Maven if necessary. is invalid. ++ Julien ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Re : portlet archetype broken
Hi Franz, I can access Jira today, and I saw your patch this morning. Hope someone will apply it quickly. ++ Julien - Message d'origine De : Franz Allan Valencia See [EMAIL PROTECTED] À : Maven Developers List dev@maven.apache.org Envoyé le : Mercredi, 24 Janvier 2007, 3h29mn 23s Objet : Re: portlet archetype broken Good day Julien There's already openned a jira issue for that ( see [1] ). And I've already attached a patch for that, but I am not sure if it can still be applied to the current source ( I can't check right now since I am having trouble accessing the svn repoproblem in my connection ). Cheers, Franz [1] http://jira.codehaus.org/browse/ARCHETYPE-40 On 1/23/07, Julien HENRY [EMAIL PROTECTED] wrote: Hi again, I was trying the portlet archetype, but the latest release is totally broken, and it is not fixed on SVN. I don't know what happend, but in each file, the content is duplicated multiple time. ie : https://svn.apache.org/repos/asf/maven/archetype/trunk/maven-archetype-bundles/maven-archetype-portlet/src/main/resources/archetype-resources/pom.xml I can write a patch, but it's very easy to fix (remove duplicated parts in all files in archetype-resources folder). As I can't access Jira, could someone open an issue for this and fix it? Thanks Julien ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Jira down ?
Hi everyone, I can't access Jira anymore (http://jira.codehaus.org/), nor ibiblio (http://ibiblio.org/maven2). Do you know if something is broken? Thanks Julien ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
portlet archetype broken
Hi again, I was trying the portlet archetype, but the latest release is totally broken, and it is not fixed on SVN. I don't know what happend, but in each file, the content is duplicated multiple time. ie : https://svn.apache.org/repos/asf/maven/archetype/trunk/maven-archetype-bundles/maven-archetype-portlet/src/main/resources/archetype-resources/pom.xml I can write a patch, but it's very easy to fix (remove duplicated parts in all files in archetype-resources folder). As I can't access Jira, could someone open an issue for this and fix it? Thanks Julien ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re : Jira down ?
Nop, can't access to http://repo1.maven.org/maven2/ too. It should be a problem of my compagny network... Thanks for you help. - Message d'origine De : Brian E. Fox [EMAIL PROTECTED] À : Maven Developers List dev@maven.apache.org Envoyé le : Mardi, 23 Janvier 2007, 15h23mn 55s Objet : RE: Jira down ? It's working ok now. I see it was updated to 3.7.2, so perhaps it was reindexing when you checked before. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fabrice Bellingard Sent: Tuesday, January 23, 2007 9:15 AM To: Maven Developers List Subject: Re: Jira down ? JIRA works fine for me, even if it's a bit slow... As for the repository, you can use the following URL: http://repo1.maven.org/maven2/ Fabrice. On 1/23/07, Julien HENRY [EMAIL PROTECTED] wrote: Hi everyone, I can't access Jira anymore (http://jira.codehaus.org/), nor ibiblio ( http://ibiblio.org/maven2). Do you know if something is broken? Thanks Julien ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven-SCM 1.0-beta-4
Here is my +1 Julien Emmanuel Venisse a écrit : Hi I'd like to release 1.0-beta-4. We have 41 issues fixed in it since April 2006, and lot of them fix some pb in plugins that use Maven-SCM (release, changelog plugins and continuum) +1 from me. Emmanuel -- _ Julien HENRY | **Capgemini Sud **| Nice www.fr.capgemini.com http://www.capgemini.com/ Porte de l’Arénas – Entrée B | 455 Promenade des Anglais | 06200 Nice **Join the Collaborative Business Experience ** _ This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re : [vote] releasing archetype bundles
Hi, Perhaps could you update archetypes to put junit-3.8.2 instead of junit-3.8.1 in the generated pom? ++ Julien - Message d'origine De : Jason van Zyl [EMAIL PROTECTED] À : Maven Developers List dev@maven.apache.org Envoyé le : Mardi, 28 Novembre 2006, 15h29mn 10s Objet : [vote] releasing archetype bundles Hi, I don't think this requires 72 hours as I just want to release a bunch of Archetypes. I want to release them all. If no one objects I'll release them all at the end of the day. One of them is a new plugin site archetype which should help people create some doco faster. Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Re: How to use VSS in Maven 2 together with Continuum?
Hi, You don't have anything to add in your pom (only write the correct scm URL). But you have to add maven-scm-provider-vss-XXX.jar in $CONTINUUM_HOME/apps/continuum/lib, because it seems it was not packaged with Continuum 1.0.3. ++ Julien Bill Qiu a écrit : Hi, Could anybody tell me how to use Visual Source Safe in Maven 2? From the Maven 2 web page, I see the VSS has been partially implemented, and following the instruction, I am using the right scm url, I am trying to use Continuum to set up the auto build, but somehow, I got error message like below: Provider message: No such provider: 'vss'. Then I downloaded the latest maven-scm-plugin, and modify my pom to include plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.0-beta-3/version /plugin in the plugins section to override the scm plugin. but I still got the same problem. Is there particular thing I need to do to register the new scm provider? Could anybody help? Thanks a lot, Bill -- _ Julien HENRY | **Capgemini Sud **| Nice www.fr.capgemini.com http://www.capgemini.com/ Porte de l’Arénas – Entrée B | 455 Promenade des Anglais | 06200 Nice **Join the Collaborative Business Experience ** _ This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: checkout, edit and synergy
Hi, I get help from a Synergy user, and he said using Synergy checkout command is not a problem. Indeed, even if a new version is created for each checkout, it's a working (Synergy state) version that is not visible for other developpers (and could be deleted later). Now I have a new problem. When you ask Synergy to checkout project foo~1.0 in target/checkout folder, your pom is in taget/checkout/foo~1.0/foo/pom.xml. I know scm:bootstrap and Continuum expect the pom to be in the root of checkout directory, and I'm not sure how to solve this. I ask some Synergy guru about getting only the content of project directory (I'm waiting for an answer), but if it is not possible, perhaps can we add a new parameter in CheckOutScmResult that store where is the root pom.xml. This will require to patch tools using checkout command. For scm plugin, it will not be difficult (only change working dir), but I don't know what is the amount of work for Continuum. Any suggestion ? ++ Julien Julien Henry a écrit : Hi, I have another problem with Synergy scm plugin. Here is what is already done: working dir $ mvn scm:checkout -DconnectionUrl=scm:synergy:myProjet~1.0 run the following ccm commands : ccm start ... ccm wa -set working dir -pst %project_name myProjet~1.0 ccm sync -r -p myProjet~1.0 ccm stop I think it is what we can expect from maven checkout command, that is to say get a specified version of a project in a specified directory. The problem is that Synergy is a locking scm. You can't edit/add file if you don't checkout project before (take care, it is the Synergy meaning of checkout !). But the Synergy checkout command not only allow you to edit files, but increments project version in database. It is the opposite of SVN where revision is incremented after checkin. When you are in a locked directory, and you want to edit a file, I don't know what ccm command to run. If someone using CM/Synergy could help me, it would be great ! I'm considering calling ccm checkout in the maven checkout, but: 1) I had to update the POM because the version of the checkout project is incremented 2) If continuum perform a checkout each night, this will create a great number of version in the database, and lock the project (AFAIK) Thanks for any idea. -- _ Julien HENRY | **Capgemini Sud **| Nice www.fr.capgemini.com http://www.capgemini.com/ Porte de l’Arénas – Entrée B | 455 Promenade des Anglais | 06200 Nice **Join the Collaborative Business Experience ** _ This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Continuum and SVN error
Hi, I tried to add jWebUnit to Continuum, and I get: Provider message: The svn command failed. Command output: --- svn: PROPFIND request failed on '/svnroot/jwebunit/trunk' svn: PROPFIND of '/svnroot/jwebunit/trunk': Server certificate verification failed: issuer is not trusted (https://svn.sourceforge.net) --- Here is the URL I give to continuum: http://svn.sourceforge.net/viewvc/*checkout*/jwebunit/trunk/pom.xml?revision=559content-type=text%2Fplain -- _ Julien HENRY | **Capgemini Sud **| Nice www.fr.capgemini.com http://www.capgemini.com/ Porte de l’Arénas – Entrée B | 455 Promenade des Anglais | 06200 Nice **Join the Collaborative Business Experience ** _ This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Add command
Hi, I would like to know what plugin use add command in scm API? AFAIK, scm plugin do not provide a target to add a new file to the scm. How can I do such a thing? Thanks -- _ Julien HENRY | **Capgemini Sud **| Nice www.fr.capgemini.com http://www.capgemini.com/ Porte de l’Arénas – Entrée B | 455 Promenade des Anglais | 06200 Nice **Join the Collaborative Business Experience ** _ This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
How to set path environement variable ?
Hi, I try to run a simple command from the provider : mvn scm:checkout -DconnectionUrl=scm:synergy:BGZBFZH~1 -X ... [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-scm-plugin:1.0-SNAPSHOT:checkout' -- [DEBUG] (f) basedir = D:\tmp [DEBUG] (s) checkoutDirectory = D:\tmp\target\checkout [DEBUG] (f) connectionType = connection [DEBUG] (s) connectionUrl = scm:synergy:BGZBFZH~1 [DEBUG] (f) developerConnectionUrl = scm:synergy:BGZBFZH~1 [DEBUG] (f) settings = [EMAIL PROTECTED] [DEBUG] (f) skipCheckoutIfExists = false [DEBUG] -- end configuration -- [INFO] [scm:checkout] project_spec = BGZBFZH~1 [INFO] Removing D:\tmp\target\checkout [DEBUG] executing checkout command... [DEBUG] basedir: D:\tmp\target\checkout [DEBUG] Executing: D:\tmp\target\checkoutccm wa -et D:\tmp\target\checkout BGZBFZH~1 [ERROR] Provider message: [ERROR] 'ccm' n'est pas reconnu en tant que commande interne ou externe, un programme exécutable ou un fichier de commandes. [ERROR] Command output: [ERROR] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Command failed.'ccm' n'est pas reconnu en tant que commande interne ou externe, un programme exécutable ou un fichier de commandes. I can confirm ccm is a real command in the Windows %PATH%. What should I do? I tried to add -Dplexus.system.*path*=%*PATH*% but I get tons of errors, concerning my JDK. Thanks -- _ Julien HENRY | **Capgemini Sud **| Nice www.fr.capgemini.com http://www.capgemini.com/ Porte de l’Arénas – Entrée B | 455 Promenade des Anglais | 06200 Nice **Join the Collaborative Business Experience ** _ This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: How to set path environement variable ?
Oups sorry, I was playing with too many terminals... and using the only one that was not closed since I set PATH variable. Julien Henry a écrit : Hi, I try to run a simple command from the provider : mvn scm:checkout -DconnectionUrl=scm:synergy:BGZBFZH~1 -X ... [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-scm-plugin:1.0-SNAPSHOT:checkout' -- [DEBUG] (f) basedir = D:\tmp [DEBUG] (s) checkoutDirectory = D:\tmp\target\checkout [DEBUG] (f) connectionType = connection [DEBUG] (s) connectionUrl = scm:synergy:BGZBFZH~1 [DEBUG] (f) developerConnectionUrl = scm:synergy:BGZBFZH~1 [DEBUG] (f) settings = [EMAIL PROTECTED] [DEBUG] (f) skipCheckoutIfExists = false [DEBUG] -- end configuration -- [INFO] [scm:checkout] project_spec = BGZBFZH~1 [INFO] Removing D:\tmp\target\checkout [DEBUG] executing checkout command... [DEBUG] basedir: D:\tmp\target\checkout [DEBUG] Executing: D:\tmp\target\checkoutccm wa -et D:\tmp\target\checkout BGZBFZH~1 [ERROR] Provider message: [ERROR] 'ccm' n'est pas reconnu en tant que commande interne ou externe, un programme exécutable ou un fichier de commandes. [ERROR] Command output: [ERROR] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Command failed.'ccm' n'est pas reconnu en tant que commande interne ou externe, un programme exécutable ou un fichier de commandes. I can confirm ccm is a real command in the Windows %PATH%. What should I do? I tried to add -Dplexus.system.*path*=%*PATH*% but I get tons of errors, concerning my JDK. Thanks -- _ Julien HENRY | **Capgemini Sud **| Nice www.fr.capgemini.com http://www.capgemini.com/ Porte de l’Arénas – Entrée B | 455 Promenade des Anglais | 06200 Nice **Join the Collaborative Business Experience ** _ This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
How to add a new provider ?
Hi, I'm trying to test the provider I'm writing. I installed it (mvn install), and now I try to call it with maven-scm-plugin: mvn scm:update -DconnectionUrl=scm:synergy: [INFO] [scm:update] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot run checkout command : Embedded error: Can't load the scm provider. First of all, it seems there is an error in the message. It's not Cannot run checkout command but Cannot run update command. Now, how to make maven-scm-plugin aware of the presence of the synergy provider ? Thanks. -- _ Julien HENRY | **Capgemini Sud **| Nice www.fr.capgemini.com http://www.capgemini.com/ Porte de l’Arénas – Entrée B | 455 Promenade des Anglais | 06200 Nice **Join the Collaborative Business Experience ** _ This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Synergy tasks
Hi everybody, I'm starting to write the provider for Synergy CM, and the first (expected) problem is how to deal with Synergy tasks. This is a notion you can't find in CVS/SVN, but it's very important for Synergy users. I'm a newbie in Synergy, but here is a typical usecase I understood: 1) you want to work on a project/file/object foo to correct a bug 2) you create a task named fix foo asap 3) you checkout foo for task fix foo asap (foo will be associated to the task) 4) you make some changes 5) you checkin foo (implicitly for the task associated) Repeat 4, 5 (same developper) or 3, 4, 5 (another developper) X times 6) When foo is fixed, you can complete/checkin the task (don't really understand the difference) I don't know if it's possible/usefull, but I consider adding createTask and completeTask to the Scm API, and add 2 targets to the SCM plugin. Is it possible ? Is there any other scm tool that use task ? The problem is that covering all task fonctionnality is very difficult. For your information, here is all the command you can use with Synergy concerning tasks: - ccm task /assign : assign a task to someone (only used by admin, not needed in Maven) - ccm task /associate : associate object(s) to a task (don't know if it's required with Maven) - ccm task /checkin : don't know exactly what it does, perhaps checkin all objects associated with the task - ccm task /complete : close as task (I think it is very usefull, for instance for release plugin) - ccm task /copy : - ccm task /create : usefull - ccm task /dissociate : dissociate object(s) from task - ccm task /fix : - ccm task /modify : only for admin I think - ccm task /query : to find a task to work on - ccm task /relate : - ccm task /def : set or clear the Default task (this way, you don't have to specify it in each command line) - ccm task /show : display information on a task - ccm task /state : put the task in a different state (I still don't really understand if state should be managed by the provider) - ccm task /unrelate : Unrelate a task from object ? (same as /dissociate ?) If someone know Synergy better than me (not really difficult), please give me your point of view on the subject. More information on how works CM Synergy : http://confluence.public.thoughtworks.org/display/CC/CMSynergyConcepts Thanks for any suggestion ! -- _ Julien HENRY | **Capgemini Sud **| Nice www.fr.capgemini.com http://www.capgemini.com/ Porte de l’Arénas – Entrée B | 455 Promenade des Anglais | 06200 Nice **Join the Collaborative Business Experience ** _ This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Synergy provider
Hi, We are working on a Maven SCM Provider for Synergy CM. Our customer is La Poste, and it is planned that all the work will be donated to the Maven community at the end of the development (10/20/2006). We would like to obtain help from Telelogic (Synergy CM editor), and it could be interesting for us (and consequently for Maven users) to make a little bit of advertising for our work on a Maven official website. This way, Telelogic will know it's a serious project. For example, could it be possible to mention the name of our customer (La Poste), on this page: http://docs.codehaus.org/display/SCM/SCM+Matrix. Could you write something like La Poste is sponsoring/financing Synergy provider development. Will be available at the end of October Another question: what are the possible licences available when they will publish the sources? I told them about Apache Licence, that seems to be the standard in Maven, and they seemed very interested, especially by the possibility to put a custom mention (copyright) that will remain this project was financed by La Poste. But perhaps could they use another Licence? Thanks, -- _ Julien HENRY | **Capgemini Sud **| Nice www.fr.capgemini.com http://www.capgemini.com/ Porte de l’Arénas – Entrée B | 455 Promenade des Anglais | 06200 Nice **Join the Collaborative Business Experience ** _ This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Writing CM Synergy plugin for Maven
Hi,My next job (on september) will be to write a plugin for CM Synergy. I'm already an advanced user of Maven 2, and I have already used several scm (CVS, SVN and VSS). Could you give me some tips that will help me writing such a plugin?ThanksJulien
