Re: [vote] [m1] demote plugins
It looks good to me, just two remarks: - did you test it with maven 1.0.2 and artifact plugin 1.5.2? - it would be good to have some simple test cases I'd be +1 for moving it to the core plugins, do we have to do a vote for that? -Lukas Stephane Nicoll wrote: What about the source plugin? I asked twice to review it and it will be needed if we want a IDE-source integration in m1. Thanks, Stéphane - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNGECLIPSE-17) Can't Attach Source to Maven Dependencies
[ http://jira.codehaus.org/browse/MNGECLIPSE-17?page=all ] Mark Hewett updated MNGECLIPSE-17: -- Attachment: patch_prefs.txt > Can't Attach Source to Maven Dependencies > - > > Key: MNGECLIPSE-17 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-17 > Project: Maven 2.x Extension for Eclipse > Type: Improvement > Versions: 0.0.3 > Reporter: Lee Meador > Assignee: Eugene Kuleshov > Fix For: 1.0.0 > Attachments: Test.zip, attach_source_patch_r46.txt, patch_prefs.txt > > > There does not seem to be any way to attach source to any of the classpath > entries that the maven2 plugin adds. > When you are tracing around (or using ctrl-F3) and it pops up a class that > for which it doesn't know the source there is usually a button you can click > to add source. If the class is among the Maven Dependencies, there is no > button. The instructions that it does give don't really seem to apply. > You can't bring up the project properties > build classpath and add source. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn site using http://svn.apache.org/repos/asf/maven/plugins/trunk/ repository
Hi Vincent, I tried your sugesstion. No Luck. I think I will wait until skin is release or someone in the maillist might know how to fix it. Thanks, Dave On 1/25/06, Vincent Siveton <[EMAIL PROTECTED]> wrote: > > Hi Dave, > > The skins are not released yet. Try to add the following in your site.xml: > > org.apache.maven.skins > maven-site-skin > 1.0-SNAPSHOT > > > Cheers, > > Vincent > > 2006/1/25, Dave Maung <[EMAIL PROTECTED]>: > > Hi Brett, > > I installed /repos/asf/maven/skins/trunk on my machine but I still ended > up > > getting this. > > This is what i did > > 1. checkout http://svn.apache.org/repos/asf/maven/plugins/trunk/plugins > > 2. mvn install on plugins > > 3. checkout http://svn.apache.org/repos/asf/maven/skins/trunk skins > > 4 mvn install on skins > > 6. checkout http://svn.apache.org/repos/asf/maven/site/trunk/ site > > 7. mvn install on site > > 8. mvn site on plugins and I got this > > > > I am using Maven version of 2.0.2. Do I have to set up anything. > > > > > > [INFO] > > > > > [ERROR] BUILD FAILURE > > [INFO] > > > > > [INFO] The skin does not exist: Unable to determine the release version > > > > org.apache.maven.skins:maven-default-skin:jar:RELEASE > > > > > > [INFO] > > > > > [DEBUG] Trace > > org.apache.maven.BuildFailureException: The skin does not exist: Unable > to > > determine the release version > > > > org.apache.maven.skins:maven-default-skin:jar:RELEASE > > > > > >at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( > > DefaultLifecycleExecutor.java:552) > >at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle > > (DefaultLifecycleExecutor.java:472) > >at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( > > DefaultLifecycleExecutor.java:451) > >at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures > > (DefaultLifecycleExecutor.java:303) > >at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( > > DefaultLifecycleExecutor.java:270) > >at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( > > DefaultLifecycleExecutor.java:139) > >at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > >at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > >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:324) > >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: org.apache.maven.plugin.MojoFailureException: The skin does > not > > exist: Unable to determine the release version > > > > org.apache.maven.skins:maven-default-skin:jar:RELEASE > > > > > >at org.apache.maven.plugins.site.SiteMojo.getSkinArtifactFile( > > SiteMojo.java:1361) > >at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:336) > >at org.apache.maven.plugin.DefaultPluginManager.executeMojo( > > DefaultPluginManager.java:415) > >at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( > > DefaultLifecycleExecutor.java:531) > > > > On 1/21/06, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > You need to checkout the skins (/repos/asf/maven/skins/trunk) and do > mvn > > > install. > > > > > > - Brett > > > > > > Dave Maung wrote: > > > > Hi > > > > I am trying to run mvn site to compile all plugin and I got the > below > > > error. > > > > see my log file. I used repository of > > > > http://svn.apache.org/repos/asf/maven/plugins/trunk/ > > > > > > > > > > > > > - > > > 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] > >
Re: [vote] [m1] demote plugins
What about the source plugin? I asked twice to review it and it will be needed if we want a IDE-source integration in m1. Thanks, Stéphane On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > I would like also to propose that we move to the sandbox these components > that we don't use : > - examples > - touchstone > - touchstone-partner > > WDYT ? > > On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > > > > Lukas, I forgot to say that I began to update this page : > > http://docs.codehaus.org/display/MAVEN/Maven+1.X+plugins > > If you can take a look at it. > > > > Arnaud > > > > On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > On 1/24/06, Lukas Theussl < [EMAIL PROTECTED]> wrote: > > > > > > > > Hello again, > > > > > > > > We have discussed this before somewhat superficially but never got to > > > > a > > > > concrete conclusion so I'd like to call for a formal vote to finalize > > > > this and collect some opinions if necessary. Let me point out and > > > > emphasize that we are quite short of manpower for m1, so the main > > > > motivation for this call is a lack of maintainers for a lot of plugins > > > > (right now we still have 65 plugins that would ship with the core). > > > > > > > > The following are all plugins that I have never used myself, I have no > > > > idea how and if they work and I don't want to invest time to find out. > > > > They are all basically unmaintained, I therefore propose to move them > > > > back into the sandbox: > > > > > > > > > > > > Plugins to demote with work to do: > > > > > > > > [+1] repository - (do we need upload-bundle? I don't see where it's > > > > used) > > > > > > > > > Carlos, Brett, are you sure that we can always use these bundles with > > > the m2 repo ? > > > Do you continue to upload in the old m1 repository ? > > > > > > > [+1] release - move used classes to SCM plugin (Fabrizio?) > > > > [+1] j2ee - move the resolver tag into ear and j2ee:validate-war to > > > > war:validate (Stephane?) > > > > > > > > > > > > Other unmaintained plugins: > > > > > > > > > > > [] abbot > > > [] castor - not working (see MPCASTOR-7) > > > [] hibernate > > > [] jbuilder - inferior to other IDE plugins > > > [] jnlp > > > [] uberjar - not working (see MPUBERJAR-8), inferior to javaapp-plugin > > > +1 > > > > > > [] antlr > > > [] cruisecontrol > > > [] jcoverage - replaced by Cobertura > > > [] jdiff > > > [] nsis > > > -1 I can maintain and release cruisecontrol and nsis. As noticed by > > > Brett, nsis is used generate the maven installer for windows. > > > I'll take a look at the others. > > > > > > [] jboss > > > [] jetty > > > +1, I'll help Vincent M to improve the cargo plugin. > > > > > > For the dependencies updates, it's not important because those plugins > > > (even if they are not re-released) will use automatically the libraries > > > defined in the maven 1.1-beta3 core. > > > > > > Arnaud > > > > > > A single +1 signifies agreement with demoting all of them, otherwise > > > > please specify individually. I expect anybody who puts a -1 to any of > > > > them to come up with an alternative solution (re-publish as is? take > > > > over maintenance and get ready for m1.1? other?). > > > > > > > > Finally, I guess we will have to do a poll on the user list as well, > > > > even though I don't know how binding that can be if we don't find a > > > > maintainer. > > > > > > > > Here's my tentative +1, hope to hear from you within 72h. > > > > > > > > -Lukas > > > > > > > > > > > > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > -- .::You're welcome ::. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: pom: relativePath element in parent
first it looks for parent in relative path, default is one directory above. and yes, in your child pom, you must specify gid and aid of the parent -D On 1/25/06, Ersin Er <[EMAIL PROTECTED]> wrote: > > Ok, is it supposed to use gid-aid and relativePath exclusively? When I > remove gid and aid and only specify relativePath the build fails. Is > this the intended behaviour? > > Thanks. > > On 1/26/06, dan tran <[EMAIL PROTECTED]> wrote: > > Maven always looks for parent in local file system first, as long as the > > local pom matches > > with what the child project needs ( ie artifactid, groupid, version). > > > > But dont think it is working that way fully yet > > http://jira.codehaus.org/browse/MNG-740 > > > > Please vote for that JIRA ;-) > > > > -Dan > > > > > > On 1/25/06, Ersin Er <[EMAIL PROTECTED]> wrote: > > > > > > Hi all, > > > > > > I have a question, in fact a confirmation, about the difference > > > between specifying a relativePath in parent and specifying a project > > > with groupId and artifactId. Does maven work offline when we specify a > > > relativePath and online when we do it the other way? Is this the > > > working scheme? > > > > > > Thanks. > > > > > > -- > > > Ersin > > > > > > > > > > -- > Ersin >
Re: pom: relativePath element in parent
Ok, is it supposed to use gid-aid and relativePath exclusively? When I remove gid and aid and only specify relativePath the build fails. Is this the intended behaviour? Thanks. On 1/26/06, dan tran <[EMAIL PROTECTED]> wrote: > Maven always looks for parent in local file system first, as long as the > local pom matches > with what the child project needs ( ie artifactid, groupid, version). > > But dont think it is working that way fully yet > http://jira.codehaus.org/browse/MNG-740 > > Please vote for that JIRA ;-) > > -Dan > > > On 1/25/06, Ersin Er <[EMAIL PROTECTED]> wrote: > > > > Hi all, > > > > I have a question, in fact a confirmation, about the difference > > between specifying a relativePath in parent and specifying a project > > with groupId and artifactId. Does maven work offline when we specify a > > relativePath and online when we do it the other way? Is this the > > working scheme? > > > > Thanks. > > > > -- > > Ersin > > > > -- Ersin
Re: pom: relativePath element in parent
Maven always looks for parent in local file system first, as long as the local pom matches with what the child project needs ( ie artifactid, groupid, version). But dont think it is working that way fully yet http://jira.codehaus.org/browse/MNG-740 Please vote for that JIRA ;-) -Dan On 1/25/06, Ersin Er <[EMAIL PROTECTED]> wrote: > > Hi all, > > I have a question, in fact a confirmation, about the difference > between specifying a relativePath in parent and specifying a project > with groupId and artifactId. Does maven work offline when we specify a > relativePath and online when we do it the other way? Is this the > working scheme? > > Thanks. > > -- > Ersin >
pom: relativePath element in parent
Hi all, I have a question, in fact a confirmation, about the difference between specifying a relativePath in parent and specifying a project with groupId and artifactId. Does maven work offline when we specify a relativePath and online when we do it the other way? Is this the working scheme? Thanks. -- Ersin
[jira] Updated: (CONTINUUM-569) Once CRON Expression Has Error, Server Never Startup
[ http://jira.codehaus.org/browse/CONTINUUM-569?page=all ] Richard C. L. Li updated CONTINUUM-569: --- Attachment: continuum_stacktrace.log > Once CRON Expression Has Error, Server Never Startup > > > Key: CONTINUUM-569 > URL: http://jira.codehaus.org/browse/CONTINUUM-569 > Project: Continuum > Type: Bug > Versions: 1.0.2 > Environment: SuSE Linux 9.2 AMD64 > Reporter: Richard C. L. Li > Assignee: Emmanuel Venisse > Priority: Critical > Fix For: 1.1-alpha-1 > Attachments: continuum_stacktrace.log > > > To reproduce the problem: > 1. Add a schedule with the following CRON expression: > 0 0 4-1 * * ? > 2. Restart the Continuum server. > 3. The server never start up. > To workaround the problem: > 1. Use JDBC to dig int he database and fix the CRON expression: > 0 0 4-23 * * ? > 2. Start the Continuum server. > 3. Server starts successfully. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Subscription: Outstanding Repository Maintenance: Uploads
Issue Subscription Filter: Outstanding Repository Maintenance: Uploads (12 issues) Subscriber: mavendevlist Key Summary MAVENUPLOAD-690Please upload jtidy-r8-21122004 http://jira.codehaus.org/browse/MAVENUPLOAD-690 MAVENUPLOAD-659Upload AjaxTags library http://jira.codehaus.org/browse/MAVENUPLOAD-659 MAVENUPLOAD-692tlddoc 1.3 http://jira.codehaus.org/browse/MAVENUPLOAD-692 MAVENUPLOAD-693maven-taglib plugin 2.1 http://jira.codehaus.org/browse/MAVENUPLOAD-693 MAVENUPLOAD-698Weblets 0.2 http://jira.codehaus.org/browse/MAVENUPLOAD-698 MAVENUPLOAD-702httpunit 1.6.1 http://jira.codehaus.org/browse/MAVENUPLOAD-702 MAVENUPLOAD-694maven taglib plugin 2.2 http://jira.codehaus.org/browse/MAVENUPLOAD-694 MAVENUPLOAD-686Please, upload JXTA 2.3.6 to the ibiblio repository. http://jira.codehaus.org/browse/MAVENUPLOAD-686 MAVENUPLOAD-687Upload of rife-jdk1.4 http://jira.codehaus.org/browse/MAVENUPLOAD-687 MAVENUPLOAD-688Upload of rife-jdk1.5 http://jira.codehaus.org/browse/MAVENUPLOAD-688 MAVENUPLOAD-662Some Findbugs jars are corrupt http://jira.codehaus.org/browse/MAVENUPLOAD-662 MAVENUPLOAD-664jlmenu 1.0 http://jira.codehaus.org/browse/MAVENUPLOAD-664 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Subscription: Outstanding Repository Maintenance: Evangelism
Issue Subscription Filter: Outstanding Repository Maintenance: Evangelism (23 issues) Subscriber: mavendevlist Key Summary MEV-313 publish seperate spring POM's for seperate dependencies http://jira.codehaus.org/browse/MEV-313 MEV-310 POMs for hivemind:hivemind:1.1 and hivemind:hivemind-lib:1.1 are missing dependencies http://jira.codehaus.org/browse/MEV-310 MEV-312 tag is misspelled in maven2 ant-optional-1.5.3-1.pom http://jira.codehaus.org/browse/MEV-312 MEV-309 PicoContainer 1.0 POM invalid http://jira.codehaus.org/browse/MEV-309 MEV-302 Invalid m2 pom for joda-time-hibernate-0.8 http://jira.codehaus.org/browse/MEV-302 MEV-295 dom4j optional dependencies http://jira.codehaus.org/browse/MEV-295 MEV-308 dom4j-1.4-dev8 has an invalid pom http://jira.codehaus.org/browse/MEV-308 MEV-301 relocate xerces:xerces or xerces:xercesImpl http://jira.codehaus.org/browse/MEV-301 MEV-296 Activemq-core (and other activemq projects) 3.2.1 have unexpanded variables http://jira.codehaus.org/browse/MEV-296 MEV-298 Invalid deps in activemq projects http://jira.codehaus.org/browse/MEV-298 MEV-299 Pom for activeio-2.1 http://jira.codehaus.org/browse/MEV-299 MEV-282 Please relocate jspapi:jsp-api to javax.servlet:jsp-api http://jira.codehaus.org/browse/MEV-282 MEV-277 More Spring Dependencies Should be Optional http://jira.codehaus.org/browse/MEV-277 MEV-255 Problem with junit-addons 1.4 http://jira.codehaus.org/browse/MEV-255 MEV-126 poms for som emissing sun xml API + javamail 1.3.3 http://jira.codehaus.org/browse/MEV-126 MEV-201 should have dependency on org.relaxngdatatype.relaxngDatatype http://jira.codehaus.org/browse/MEV-201 MEV-173 xmlpull JARs exist in two different places on ibiblio http://jira.codehaus.org/browse/MEV-173 MEV-48 openejb poms http://jira.codehaus.org/browse/MEV-48 MEV-45 Full list of poms that doesn't respect the m2 format http://jira.codehaus.org/browse/MEV-45 MEV-36 Exo POM(s) missing dependency versions http://jira.codehaus.org/browse/MEV-36 MEV-33 XOM POM references xercesImpl v.2.2.1 which does not exist in repo http://jira.codehaus.org/browse/MEV-33 MEV-31 XOM POM references xmlParserAPIs v2.6.1 which is not in the repo http://jira.codehaus.org/browse/MEV-31 MEV-20 clean up bad IDs in the repository http://jira.codehaus.org/browse/MEV-20 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-804) maven.jar.override usage in m2
[ http://jira.codehaus.org/browse/MNG-804?page=all ] Allan Ramirez closed MNG-804: - Resolution: Fixed > maven.jar.override usage in m2 > -- > > Key: MNG-804 > URL: http://jira.codehaus.org/browse/MNG-804 > Project: Maven 2 > Type: Sub-task > Components: documentation - general > Reporter: Natalie Burdick > Assignee: Allan Ramirez > Priority: Minor > Fix For: documentation > Attachments: m1-m2-changes (revised).txt, m1-m2-changes-b.apt, > m1-m2-changes-c.apt, m1-m2-changes.JPG, m1-m2-changes.apt > > > refer to: > http://mail-archives.apache.org/mod_mbox/maven-users/200508.mbox/[EMAIL > PROTECTED] > to document that unlike m1, m2 no longer allow jar overrides via the > maven.jar.override property -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] [m1] demote plugins
Jason, in fact we're right ;-) These plugins are used in the bootstrap but they are downloaded from the remote repository instead of to be built before. I'll change that to build them during the bootstrap. It's anormal that we have to download them. arnaud On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > > No, I'm right :-) > All touchstone tests are in the core : > > http://svn.apache.org/viewcvs.cgi/maven/maven-1/core/trunk/src/test/touchstone-build/ > We don't use the plugins. > > Arnaud > > On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > > > > ouchhh > > > > I forgot it ;-) > > > > thx jason ! > > > > arnaud > > > > On 1/26/06, Jason van Zyl < [EMAIL PROTECTED]> wrote: > > > > > > Arnaud HERITIER wrote: > > > > I would like also to propose that we move to the sandbox these > > > components > > > > that we don't use : > > > > - examples > > > > > > > - touchstone > > > > - touchstone-partner > > > > > > These aren't used in the m1 bootstrap anymore? > > > > > > > > > > > WDYT ? > > > > > > > > On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > > > >> Lukas, I forgot to say that I began to update this page : > > > >> http://docs.codehaus.org/display/MAVEN/Maven+1.X+plugins > > > >> If you can take a look at it. > > > >> > > > >> Arnaud > > > >> > > > >> On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > > > >>> > > > >>> > > > >>> On 1/24/06, Lukas Theussl < [EMAIL PROTECTED]> wrote: > > > Hello again, > > > > > > We have discussed this before somewhat superficially but never > > > got to > > > a > > > concrete conclusion so I'd like to call for a formal vote to > > > finalize > > > this and collect some opinions if necessary. Let me point out and > > > emphasize that we are quite short of manpower for m1, so the main > > > motivation for this call is a lack of maintainers for a lot of > > > plugins > > > (right now we still have 65 plugins that would ship with the > > > core). > > > > > > The following are all plugins that I have never used myself, I > > > have no > > > idea how and if they work and I don't want to invest time to find > > > out. > > > They are all basically unmaintained, I therefore propose to move > > > them > > > back into the sandbox: > > > > > > > > > Plugins to demote with work to do: > > > > > > [+1] repository - (do we need upload-bundle? I don't see where > > > it's > > > used) > > > >>> > > > >>> Carlos, Brett, are you sure that we can always use these bundles > > > with > > > >>> the m2 repo ? > > > >>> Do you continue to upload in the old m1 repository ? > > > >>> > > > [+1] release - move used classes to SCM plugin (Fabrizio?) > > > [+1] j2ee - move the resolver tag into ear and j2ee:validate-war > > > to > > > war:validate (Stephane?) > > > > > > > > > Other unmaintained plugins: > > > > > > > > > >>> [] abbot > > > >>> [] castor - not working (see MPCASTOR-7) > > > >>> [] hibernate > > > >>> [] jbuilder - inferior to other IDE plugins > > > >>> [] jnlp > > > >>> [] uberjar - not working (see MPUBERJAR-8), inferior to > > > javaapp-plugin > > > >>> +1 > > > >>> > > > >>> [] antlr > > > >>> [] cruisecontrol > > > >>> [] jcoverage - replaced by Cobertura > > > >>> [] jdiff > > > >>> [] nsis > > > >>> -1 I can maintain and release cruisecontrol and nsis. As noticed > > > by > > > >>> Brett, nsis is used generate the maven installer for windows. > > > >>> I'll take a look at the others. > > > >>> > > > >>> [] jboss > > > >>> [] jetty > > > >>> +1, I'll help Vincent M to improve the cargo plugin. > > > >>> > > > >>> For the dependencies updates, it's not important because those > > > plugins > > > >>> (even if they are not re-released) will use automatically the > > > libraries > > > >>> defined in the maven 1.1-beta3 core. > > > >>> > > > >>> Arnaud > > > >>> > > > >>> A single +1 signifies agreement with demoting all of them, > > > otherwise > > > please specify individually. I expect anybody who puts a -1 to > > > any of > > > them to come up with an alternative solution (re-publish as is? > > > take > > > over maintenance and get ready for m1.1? other?). > > > > > > Finally, I guess we will have to do a poll on the user list as > > > well, > > > even though I don't know how binding that can be if we don't find > > > a > > > maintainer. > > > > > > Here's my tentative +1, hope to hear from you within 72h. > > > > > > -Lukas > > > > > > > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > -- > > > > > > jvz. > > > > > > Jason van Zyl > > > jason at maven.org > > > http://maven.apache.org > > > > > > happiness is like
Re: [vote] [m1] demote plugins
Ok, I see what you mean now. +1 to remove touchstone and touchstone-partner, if they are really unused. -1 for examples, I think it can be useful to have some example templates for illustration purpose (I think I used it once to point a user to). -Lukas Arnaud HERITIER wrote: No, I'm right :-) All touchstone tests are in the core : http://svn.apache.org/viewcvs.cgi/maven/maven-1/core/trunk/src/test/touchstone-build/ We don't use the plugins. Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] [m1] demote plugins
No, I'm right :-) All touchstone tests are in the core : http://svn.apache.org/viewcvs.cgi/maven/maven-1/core/trunk/src/test/touchstone-build/ We don't use the plugins. Arnaud On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > > ouchhh > > I forgot it ;-) > > thx jason ! > > arnaud > > On 1/26/06, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > > > Arnaud HERITIER wrote: > > > I would like also to propose that we move to the sandbox these > > components > > > that we don't use : > > > - examples > > > > > - touchstone > > > - touchstone-partner > > > > These aren't used in the m1 bootstrap anymore? > > > > > > > > WDYT ? > > > > > > On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > > >> Lukas, I forgot to say that I began to update this page : > > >> http://docs.codehaus.org/display/MAVEN/Maven+1.X+plugins > > >> If you can take a look at it. > > >> > > >> Arnaud > > >> > > >> On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > > >>> > > >>> > > >>> On 1/24/06, Lukas Theussl < [EMAIL PROTECTED]> wrote: > > Hello again, > > > > We have discussed this before somewhat superficially but never got > > to > > a > > concrete conclusion so I'd like to call for a formal vote to > > finalize > > this and collect some opinions if necessary. Let me point out and > > emphasize that we are quite short of manpower for m1, so the main > > motivation for this call is a lack of maintainers for a lot of > > plugins > > (right now we still have 65 plugins that would ship with the core). > > > > The following are all plugins that I have never used myself, I have > > no > > idea how and if they work and I don't want to invest time to find > > out. > > They are all basically unmaintained, I therefore propose to move > > them > > back into the sandbox: > > > > > > Plugins to demote with work to do: > > > > [+1] repository - (do we need upload-bundle? I don't see where it's > > used) > > >>> > > >>> Carlos, Brett, are you sure that we can always use these bundles > > with > > >>> the m2 repo ? > > >>> Do you continue to upload in the old m1 repository ? > > >>> > > [+1] release - move used classes to SCM plugin (Fabrizio?) > > [+1] j2ee - move the resolver tag into ear and j2ee:validate-war to > > > > war:validate (Stephane?) > > > > > > Other unmaintained plugins: > > > > > > >>> [] abbot > > >>> [] castor - not working (see MPCASTOR-7) > > >>> [] hibernate > > >>> [] jbuilder - inferior to other IDE plugins > > >>> [] jnlp > > >>> [] uberjar - not working (see MPUBERJAR-8), inferior to > > javaapp-plugin > > >>> +1 > > >>> > > >>> [] antlr > > >>> [] cruisecontrol > > >>> [] jcoverage - replaced by Cobertura > > >>> [] jdiff > > >>> [] nsis > > >>> -1 I can maintain and release cruisecontrol and nsis. As noticed by > > >>> Brett, nsis is used generate the maven installer for windows. > > >>> I'll take a look at the others. > > >>> > > >>> [] jboss > > >>> [] jetty > > >>> +1, I'll help Vincent M to improve the cargo plugin. > > >>> > > >>> For the dependencies updates, it's not important because those > > plugins > > >>> (even if they are not re-released) will use automatically the > > libraries > > >>> defined in the maven 1.1-beta3 core. > > >>> > > >>> Arnaud > > >>> > > >>> A single +1 signifies agreement with demoting all of them, otherwise > > please specify individually. I expect anybody who puts a -1 to any > > of > > them to come up with an alternative solution (re-publish as is? > > take > > over maintenance and get ready for m1.1? other?). > > > > Finally, I guess we will have to do a poll on the user list as > > well, > > even though I don't know how binding that can be if we don't find a > > maintainer. > > > > Here's my tentative +1, hope to hear from you within 72h. > > > > -Lukas > > > > > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > -- > > > > jvz. > > > > Jason van Zyl > > jason at maven.org > > http://maven.apache.org > > > > happiness is like a butterfly: the more you chase it, the more it will > > elude you, but if you turn your attention to other things, it will come > > and sit softly on your shoulder ... > > > > -- Thoreau > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
Re: [vote] [m1] demote plugins
ouchhh I forgot it ;-) thx jason ! arnaud On 1/26/06, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > Arnaud HERITIER wrote: > > I would like also to propose that we move to the sandbox these > components > > that we don't use : > > - examples > > > - touchstone > > - touchstone-partner > > These aren't used in the m1 bootstrap anymore? > > > > > WDYT ? > > > > On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > >> Lukas, I forgot to say that I began to update this page : > >> http://docs.codehaus.org/display/MAVEN/Maven+1.X+plugins > >> If you can take a look at it. > >> > >> Arnaud > >> > >> On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>> On 1/24/06, Lukas Theussl < [EMAIL PROTECTED]> wrote: > Hello again, > > We have discussed this before somewhat superficially but never got to > a > concrete conclusion so I'd like to call for a formal vote to finalize > this and collect some opinions if necessary. Let me point out and > emphasize that we are quite short of manpower for m1, so the main > motivation for this call is a lack of maintainers for a lot of > plugins > (right now we still have 65 plugins that would ship with the core). > > The following are all plugins that I have never used myself, I have > no > idea how and if they work and I don't want to invest time to find > out. > They are all basically unmaintained, I therefore propose to move them > back into the sandbox: > > > Plugins to demote with work to do: > > [+1] repository - (do we need upload-bundle? I don't see where it's > used) > >>> > >>> Carlos, Brett, are you sure that we can always use these bundles with > >>> the m2 repo ? > >>> Do you continue to upload in the old m1 repository ? > >>> > [+1] release - move used classes to SCM plugin (Fabrizio?) > [+1] j2ee - move the resolver tag into ear and j2ee:validate-war to > war:validate (Stephane?) > > > Other unmaintained plugins: > > > >>> [] abbot > >>> [] castor - not working (see MPCASTOR-7) > >>> [] hibernate > >>> [] jbuilder - inferior to other IDE plugins > >>> [] jnlp > >>> [] uberjar - not working (see MPUBERJAR-8), inferior to javaapp-plugin > >>> +1 > >>> > >>> [] antlr > >>> [] cruisecontrol > >>> [] jcoverage - replaced by Cobertura > >>> [] jdiff > >>> [] nsis > >>> -1 I can maintain and release cruisecontrol and nsis. As noticed by > >>> Brett, nsis is used generate the maven installer for windows. > >>> I'll take a look at the others. > >>> > >>> [] jboss > >>> [] jetty > >>> +1, I'll help Vincent M to improve the cargo plugin. > >>> > >>> For the dependencies updates, it's not important because those plugins > >>> (even if they are not re-released) will use automatically the > libraries > >>> defined in the maven 1.1-beta3 core. > >>> > >>> Arnaud > >>> > >>> A single +1 signifies agreement with demoting all of them, otherwise > please specify individually. I expect anybody who puts a -1 to any of > them to come up with an alternative solution (re-publish as is? take > over maintenance and get ready for m1.1? other?). > > Finally, I guess we will have to do a poll on the user list as well, > even though I don't know how binding that can be if we don't find a > maintainer. > > Here's my tentative +1, hope to hear from you within 72h. > > -Lukas > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > > jvz. > > Jason van Zyl > jason at maven.org > http://maven.apache.org > > happiness is like a butterfly: the more you chase it, the more it will > elude you, but if you turn your attention to other things, it will come > and sit softly on your shoulder ... > > -- Thoreau > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
[jira] Commented: (MNG-1530) Converter for maven 1 projects
[ http://jira.codehaus.org/browse/MNG-1530?page=comments#action_56957 ] Bryan Pauquette commented on MNG-1530: -- Ok, so you changed myproject to myproject. Now you need to delete your developer list and contributer lists because they have the element also. Your the last guy coding anyway, everyone else has gone home. What you need your team for? Now it works... > Converter for maven 1 projects > -- > > Key: MNG-1530 > URL: http://jira.codehaus.org/browse/MNG-1530 > Project: Maven 2 > Type: Improvement > Components: Plugin Requests > Reporter: fabrizio giustina > Assignee: fabrizio giustina > Priority: Minor > Attachments: maven-maven1-plugin.zip > > > A simple mvn plugins that converts a maven 1 project.xml to a maven 2 pom.xml. > Apart from the pom v3 to v4 conversion it also adds specific plugin > configurations to pom.xml from project.properties (there are a few samples > for some compiler, surefire, war settings and it can be easily extended). > After installing it using mvn:install you can run "mvn maven1:convert" on > maven 1 project for a quick start on maven 2. > Note: the org.apache.maven.model.v3_0_0.* classes are actually embedded in > the plugin due to MNG-1436 and MAVENUPLOAD-583 > If there is interest in this I can commit it to svn, please comment/vote here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-1630) Properties section in POM cannot be read
[ http://jira.codehaus.org/browse/MAVEN-1630?page=all ]
Lukas Theussl closed MAVEN-1630:
Resolution: Won't Fix
Fix Version: (was: 1.1-beta-3)
The properties element is not supposed to be used like that, you can only
specify simple properties (no nested elements) like this:
pomPropertyA
A custom jelly script can then access this property like:
${pom.getProperties().getProperty('propertyA')}
> Properties section in POM cannot be read
>
>
> Key: MAVEN-1630
> URL: http://jira.codehaus.org/browse/MAVEN-1630
> Project: Maven
> Type: Bug
> Versions: 1.1-beta-1
> Environment: windows xp sp1, JVM 1.4.2_05
> Reporter: Andreas Schönknecht
>
>
> I just tried the Maven 1.1 beta. Unfortunately I get errors when my
> POMs contains custom properties. Here is an example: At the end of the
> POM I have a properties section:
> ...
>
>
>
>
>
>
>
> tui-iris
> tuiiris
> 1.0.2
>
>
>
>
>
>
>
>
>
> As far as I understood it should be possible to have custom properties
> in the POM. But when I execute any Maven goal I get:
> org.codehaus.plexus.util.xml.pull.XmlPullParserException: TEXT must be
> immediately followed by END_TAG and not START_TAG (position: START_TAG seen
> .. @185:20)
> at
> org.codehaus.plexus.util.xml.pull.MXParser.nextText(MXParser.java:1059)
> at
> org.apache.maven.project.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:834)
> at
> org.apache.maven.project.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:1621)
> at org.apache.maven.project.Project.(Project.java:120)
> at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:185)
> at org.apache.maven.MavenUtils.getProject(MavenUtils.java:120)
> at org.apache.maven.MavenUtils.getProject(MavenUtils.java:99)
> at
> org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:232)
> at org.apache.maven.MavenSession.initialize(MavenSession.java:172)
> at org.apache.maven.cli.App.doMain(App.java:498)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-690) Please upload jtidy-r8-21122004
[ http://jira.codehaus.org/browse/MAVENUPLOAD-690?page=comments#action_56954 ] Johann Reyes commented on MAVENUPLOAD-690: -- Changed groupid from jtidy to org.hibernate Re-uploaded fixed bundle. > Please upload jtidy-r8-21122004 > --- > > Key: MAVENUPLOAD-690 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-690 > Project: maven-upload-requests > Type: Task > Reporter: Johann Reyes > > > http://jtidy.sourceforge.net/ > JTidy is a Java port of HTML Tidy, a HTML syntax checker and pretty printer. > Like its non-Java cousin, JTidy can be used as a tool for cleaning up > malformed and faulty HTML. In addition, JTidy provides a DOM parser for > real-world HTML. > This is a dependency for hibernate tools-3.1.0.beta2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] [m1] demote plugins
Arnaud HERITIER wrote: I would like also to propose that we move to the sandbox these components that we don't use : - examples - touchstone - touchstone-partner These aren't used in the m1 bootstrap anymore? WDYT ? On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: Lukas, I forgot to say that I began to update this page : http://docs.codehaus.org/display/MAVEN/Maven+1.X+plugins If you can take a look at it. Arnaud On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: On 1/24/06, Lukas Theussl < [EMAIL PROTECTED]> wrote: Hello again, We have discussed this before somewhat superficially but never got to a concrete conclusion so I'd like to call for a formal vote to finalize this and collect some opinions if necessary. Let me point out and emphasize that we are quite short of manpower for m1, so the main motivation for this call is a lack of maintainers for a lot of plugins (right now we still have 65 plugins that would ship with the core). The following are all plugins that I have never used myself, I have no idea how and if they work and I don't want to invest time to find out. They are all basically unmaintained, I therefore propose to move them back into the sandbox: Plugins to demote with work to do: [+1] repository - (do we need upload-bundle? I don't see where it's used) Carlos, Brett, are you sure that we can always use these bundles with the m2 repo ? Do you continue to upload in the old m1 repository ? [+1] release - move used classes to SCM plugin (Fabrizio?) [+1] j2ee - move the resolver tag into ear and j2ee:validate-war to war:validate (Stephane?) Other unmaintained plugins: [] abbot [] castor - not working (see MPCASTOR-7) [] hibernate [] jbuilder - inferior to other IDE plugins [] jnlp [] uberjar - not working (see MPUBERJAR-8), inferior to javaapp-plugin +1 [] antlr [] cruisecontrol [] jcoverage - replaced by Cobertura [] jdiff [] nsis -1 I can maintain and release cruisecontrol and nsis. As noticed by Brett, nsis is used generate the maven installer for windows. I'll take a look at the others. [] jboss [] jetty +1, I'll help Vincent M to improve the cargo plugin. For the dependencies updates, it's not important because those plugins (even if they are not re-released) will use automatically the libraries defined in the maven 1.1-beta3 core. Arnaud A single +1 signifies agreement with demoting all of them, otherwise please specify individually. I expect anybody who puts a -1 to any of them to come up with an alternative solution (re-publish as is? take over maintenance and get ready for m1.1? other?). Finally, I guess we will have to do a poll on the user list as well, even though I don't know how binding that can be if we don't find a maintainer. Here's my tentative +1, hope to hear from you within 72h. -Lukas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Closed: (MAVEN-1693) Remove unused from POM model, documentation and XSD
I don't know.
Arnaud
On 1/26/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
>
> I knew I was missing something big! ;)
>
> Thanks Arnaud, that worked. However, it's not what is used in the
> touchstone tests ... ?
>
> -Lukas
>
>
> Arnaud HERITIER wrote:
> > Isn't it ? :
> > ${pom.getProperties().getProperty('propertyA')}
> >
> > Arnaud
> >
> > On 1/25/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> >
> >>
> >>
> >>Brett Porter wrote:
> >>
> >>>IIRC, touchstone tests it.
> >>
> >>Thanks for the tip. Now I don't know how touchstone works, but as I
> >>understand it, the following should work:
> >>
> >>if you put in your project.xml:
> >>
> >>
> >> pomPropertyA
> >>
> >>
> >>then you should access the property in a custom jelly script like:
> >>
> >>propertyA = ${pom.getProperty('propertyA')}
> >>
> >>But this doesn't work, I get no output. What am I missing?
> >>
> >>-Lukas
> >>
> >>
> >>-
> >>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]
>
>
Re: [vote] [m1] demote plugins
I would like also to propose that we move to the sandbox these components that we don't use : - examples - touchstone - touchstone-partner WDYT ? On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > > Lukas, I forgot to say that I began to update this page : > http://docs.codehaus.org/display/MAVEN/Maven+1.X+plugins > If you can take a look at it. > > Arnaud > > On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > > > > > > > > On 1/24/06, Lukas Theussl < [EMAIL PROTECTED]> wrote: > > > > > > Hello again, > > > > > > We have discussed this before somewhat superficially but never got to > > > a > > > concrete conclusion so I'd like to call for a formal vote to finalize > > > this and collect some opinions if necessary. Let me point out and > > > emphasize that we are quite short of manpower for m1, so the main > > > motivation for this call is a lack of maintainers for a lot of plugins > > > (right now we still have 65 plugins that would ship with the core). > > > > > > The following are all plugins that I have never used myself, I have no > > > idea how and if they work and I don't want to invest time to find out. > > > They are all basically unmaintained, I therefore propose to move them > > > back into the sandbox: > > > > > > > > > Plugins to demote with work to do: > > > > > > [+1] repository - (do we need upload-bundle? I don't see where it's > > > used) > > > > > > Carlos, Brett, are you sure that we can always use these bundles with > > the m2 repo ? > > Do you continue to upload in the old m1 repository ? > > > > > [+1] release - move used classes to SCM plugin (Fabrizio?) > > > [+1] j2ee - move the resolver tag into ear and j2ee:validate-war to > > > war:validate (Stephane?) > > > > > > > > > Other unmaintained plugins: > > > > > > > > [] abbot > > [] castor - not working (see MPCASTOR-7) > > [] hibernate > > [] jbuilder - inferior to other IDE plugins > > [] jnlp > > [] uberjar - not working (see MPUBERJAR-8), inferior to javaapp-plugin > > +1 > > > > [] antlr > > [] cruisecontrol > > [] jcoverage - replaced by Cobertura > > [] jdiff > > [] nsis > > -1 I can maintain and release cruisecontrol and nsis. As noticed by > > Brett, nsis is used generate the maven installer for windows. > > I'll take a look at the others. > > > > [] jboss > > [] jetty > > +1, I'll help Vincent M to improve the cargo plugin. > > > > For the dependencies updates, it's not important because those plugins > > (even if they are not re-released) will use automatically the libraries > > defined in the maven 1.1-beta3 core. > > > > Arnaud > > > > A single +1 signifies agreement with demoting all of them, otherwise > > > please specify individually. I expect anybody who puts a -1 to any of > > > them to come up with an alternative solution (re-publish as is? take > > > over maintenance and get ready for m1.1? other?). > > > > > > Finally, I guess we will have to do a poll on the user list as well, > > > even though I don't know how binding that can be if we don't find a > > > maintainer. > > > > > > Here's my tentative +1, hope to hear from you within 72h. > > > > > > -Lukas > > > > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > >
Re: [jira] Closed: (MAVEN-1693) Remove unused from POM model, documentation and XSD
I knew I was missing something big! ;)
Thanks Arnaud, that worked. However, it's not what is used in the
touchstone tests ... ?
-Lukas
Arnaud HERITIER wrote:
Isn't it ? :
${pom.getProperties().getProperty('propertyA')}
Arnaud
On 1/25/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
Brett Porter wrote:
IIRC, touchstone tests it.
Thanks for the tip. Now I don't know how touchstone works, but as I
understand it, the following should work:
if you put in your project.xml:
pomPropertyA
then you should access the property in a custom jelly script like:
propertyA = ${pom.getProperty('propertyA')}
But this doesn't work, I get no output. What am I missing?
-Lukas
-
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]
Re: [jira] Closed: (MAVEN-1693) Remove unused from POM model, documentation and XSD
Isn't it ? :
${pom.getProperties().getProperty('propertyA')}
Arnaud
On 1/25/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
>
>
>
> Brett Porter wrote:
> > IIRC, touchstone tests it.
>
> Thanks for the tip. Now I don't know how touchstone works, but as I
> understand it, the following should work:
>
> if you put in your project.xml:
>
>
> pomPropertyA
>
>
> then you should access the property in a custom jelly script like:
>
> propertyA = ${pom.getProperty('propertyA')}
>
> But this doesn't work, I get no output. What am I missing?
>
> -Lukas
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
[jira] Commented: (MNG-1530) Converter for maven 1 projects
[ http://jira.codehaus.org/browse/MNG-1530?page=comments#action_56951 ] Bryan Pauquette commented on MNG-1530: -- Newbie Answer: 1) Download the file to a local directory 2) unzip it. I can't help you if you don't know how to unzip it. try google 2) Navigate to the directory where the pom.xml is stored. 3) mvn -version Maven version: 2.0.2 If your computer doesn't respond with a version number you haven't installed maven2 correctly yet. Go back and install it. This time read more carefully http://maven.apache.org/download.html#installation 4) type mvn install 5) You have installed it. 6) Navigate to your maven1 project. Where the project.xml file is. 7) type mvn maven1:convert 8) Watch it die because it didn't parse the id tag correctly because your a newbie.id is deprecated. 9) Go look up the new tag for id in maven 1.0? > Converter for maven 1 projects > -- > > Key: MNG-1530 > URL: http://jira.codehaus.org/browse/MNG-1530 > Project: Maven 2 > Type: Improvement > Components: Plugin Requests > Reporter: fabrizio giustina > Assignee: fabrizio giustina > Priority: Minor > Attachments: maven-maven1-plugin.zip > > > A simple mvn plugins that converts a maven 1 project.xml to a maven 2 pom.xml. > Apart from the pom v3 to v4 conversion it also adds specific plugin > configurations to pom.xml from project.properties (there are a few samples > for some compiler, surefire, war settings and it can be easily extended). > After installing it using mvn:install you can run "mvn maven1:convert" on > maven 1 project for a quick start on maven 2. > Note: the org.apache.maven.model.v3_0_0.* classes are actually embedded in > the plugin due to MNG-1436 and MAVENUPLOAD-583 > If there is interest in this I can commit it to svn, please comment/vote here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] [m1] demote plugins
Lukas, I forgot to say that I began to update this page : http://docs.codehaus.org/display/MAVEN/Maven+1.X+plugins If you can take a look at it. Arnaud On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > > > > On 1/24/06, Lukas Theussl <[EMAIL PROTECTED]> wrote: > > > > Hello again, > > > > We have discussed this before somewhat superficially but never got to a > > concrete conclusion so I'd like to call for a formal vote to finalize > > this and collect some opinions if necessary. Let me point out and > > emphasize that we are quite short of manpower for m1, so the main > > motivation for this call is a lack of maintainers for a lot of plugins > > (right now we still have 65 plugins that would ship with the core). > > > > The following are all plugins that I have never used myself, I have no > > idea how and if they work and I don't want to invest time to find out. > > They are all basically unmaintained, I therefore propose to move them > > back into the sandbox: > > > > > > Plugins to demote with work to do: > > > > [+1] repository - (do we need upload-bundle? I don't see where it's > > used) > > > Carlos, Brett, are you sure that we can always use these bundles with the > m2 repo ? > Do you continue to upload in the old m1 repository ? > > > [+1] release - move used classes to SCM plugin (Fabrizio?) > > [+1] j2ee - move the resolver tag into ear and j2ee:validate-war to > > war:validate (Stephane?) > > > > > > Other unmaintained plugins: > > > > > [] abbot > [] castor - not working (see MPCASTOR-7) > [] hibernate > [] jbuilder - inferior to other IDE plugins > [] jnlp > [] uberjar - not working (see MPUBERJAR-8), inferior to javaapp-plugin > +1 > > [] antlr > [] cruisecontrol > [] jcoverage - replaced by Cobertura > [] jdiff > [] nsis > -1 I can maintain and release cruisecontrol and nsis. As noticed by Brett, > nsis is used generate the maven installer for windows. > I'll take a look at the others. > > [] jboss > [] jetty > +1, I'll help Vincent M to improve the cargo plugin. > > For the dependencies updates, it's not important because those plugins > (even if they are not re-released) will use automatically the libraries > defined in the maven 1.1-beta3 core. > > Arnaud > > A single +1 signifies agreement with demoting all of them, otherwise > > please specify individually. I expect anybody who puts a -1 to any of > > them to come up with an alternative solution (re-publish as is? take > > over maintenance and get ready for m1.1? other?). > > > > Finally, I guess we will have to do a poll on the user list as well, > > even though I don't know how binding that can be if we don't find a > > maintainer. > > > > Here's my tentative +1, hope to hear from you within 72h. > > > > -Lukas > > > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
[jira] Commented: (MPDASHBOARD-31) Create aggregators for Cobertura
[ http://jira.codehaus.org/browse/MPDASHBOARD-31?page=comments#action_56950 ] Lukas Theussl commented on MPDASHBOARD-31: -- Actually, if you want to do some testing: there is a SNAPSHOT available: maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-dashboard-plugin -Dversion=1.9-SNAPSHOT Let us know how it works! > Create aggregators for Cobertura > > > Key: MPDASHBOARD-31 > URL: http://jira.codehaus.org/browse/MPDASHBOARD-31 > Project: maven-dashboard-plugin > Type: New Feature > Reporter: Carlos Sanchez > Assignee: Carlos Sanchez > Fix For: 1.9 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] [m1] demote plugins
On 1/24/06, Lukas Theussl <[EMAIL PROTECTED]> wrote: > > Hello again, > > We have discussed this before somewhat superficially but never got to a > concrete conclusion so I'd like to call for a formal vote to finalize > this and collect some opinions if necessary. Let me point out and > emphasize that we are quite short of manpower for m1, so the main > motivation for this call is a lack of maintainers for a lot of plugins > (right now we still have 65 plugins that would ship with the core). > > The following are all plugins that I have never used myself, I have no > idea how and if they work and I don't want to invest time to find out. > They are all basically unmaintained, I therefore propose to move them > back into the sandbox: > > > Plugins to demote with work to do: > > [+1] repository - (do we need upload-bundle? I don't see where it's used) Carlos, Brett, are you sure that we can always use these bundles with the m2 repo ? Do you continue to upload in the old m1 repository ? > [+1] release - move used classes to SCM plugin (Fabrizio?) > [+1] j2ee - move the resolver tag into ear and j2ee:validate-war to > war:validate (Stephane?) > > > Other unmaintained plugins: > > [] abbot [] castor - not working (see MPCASTOR-7) [] hibernate [] jbuilder - inferior to other IDE plugins [] jnlp [] uberjar - not working (see MPUBERJAR-8), inferior to javaapp-plugin +1 [] antlr [] cruisecontrol [] jcoverage - replaced by Cobertura [] jdiff [] nsis -1 I can maintain and release cruisecontrol and nsis. As noticed by Brett, nsis is used generate the maven installer for windows. I'll take a look at the others. [] jboss [] jetty +1, I'll help Vincent M to improve the cargo plugin. For the dependencies updates, it's not important because those plugins (even if they are not re-released) will use automatically the libraries defined in the maven 1.1-beta3 core. Arnaud A single +1 signifies agreement with demoting all of them, otherwise > please specify individually. I expect anybody who puts a -1 to any of > them to come up with an alternative solution (re-publish as is? take > over maintenance and get ready for m1.1? other?). > > Finally, I guess we will have to do a poll on the user list as well, > even though I don't know how binding that can be if we don't find a > maintainer. > > Here's my tentative +1, hope to hear from you within 72h. > > -Lukas > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
[jira] Commented: (MPDASHBOARD-31) Create aggregators for Cobertura
[ http://jira.codehaus.org/browse/MPDASHBOARD-31?page=comments#action_56949 ] Lukas Theussl commented on MPDASHBOARD-31: -- As you see in the fix version for this issue, the Cobertura aggregators have only been implemented in version 1.9 of the dashboard plugin. This one is not published yet (but is expected to come out maybe next week :) ). > Create aggregators for Cobertura > > > Key: MPDASHBOARD-31 > URL: http://jira.codehaus.org/browse/MPDASHBOARD-31 > Project: maven-dashboard-plugin > Type: New Feature > Reporter: Carlos Sanchez > Assignee: Carlos Sanchez > Fix For: 1.9 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPDASHBOARD-31) Create aggregators for Cobertura
[ http://jira.codehaus.org/browse/MPDASHBOARD-31?page=comments#action_56948 ] Nascif A. Abousalh-Neto commented on MPDASHBOARD-31: I just downloaded the 1.8 version of the plugin to get Cobertura support and got this error: BUILD FAILED File.. C:\Documents and Settings\naabou\.maven\cache\maven-multiproject-plugin-1.4.1\plugin.jelly Element... maven:reactor Line.. 104 Column 9 Unable to obtain goal [dashboard:report-single] -- C:\Documents and Settings\naabou\.maven\cache\maven-dashboard-plugin-1.8\plugin.jelly:192:23: Invalid aggregator name [coberturalipc] I checked the .jar and and there are no aggregators for Cobertura there, although thery are already showing in the official documentation. Any idea why? From the discussion above they should be available, right? Thanks, Nascif > Create aggregators for Cobertura > > > Key: MPDASHBOARD-31 > URL: http://jira.codehaus.org/browse/MPDASHBOARD-31 > Project: maven-dashboard-plugin > Type: New Feature > Reporter: Carlos Sanchez > Assignee: Carlos Sanchez > Fix For: 1.9 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPJXR-30) Add an option to site generation to use clover xref files rather than jxr
[ http://jira.codehaus.org/browse/MPJXR-30?page=all ] Lukas Theussl closed MPJXR-30: -- Resolution: Won't Fix > Add an option to site generation to use clover xref files rather than jxr > - > > Key: MPJXR-30 > URL: http://jira.codehaus.org/browse/MPJXR-30 > Project: maven-jxr-plugin > Type: Improvement > Reporter: Ben Walding > > Original Estimate: 4 hours > Remaining: 4 hours > > Clover generates java xref files (they contain test information also). > There seems little point in also generating jxr xref files where clover ones > exists. As such, add an option to use one or the other. > eg. > maven.site.xref=clover > or > maven.site.xref=jxr > Will need to update anywhere that refers to an xref file -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1530) Converter for maven 1 projects
[ http://jira.codehaus.org/browse/MNG-1530?page=comments#action_56947 ] Grégory Joseph commented on MNG-1530: - Check the pom ;) > Converter for maven 1 projects > -- > > Key: MNG-1530 > URL: http://jira.codehaus.org/browse/MNG-1530 > Project: Maven 2 > Type: Improvement > Components: Plugin Requests > Reporter: fabrizio giustina > Assignee: fabrizio giustina > Priority: Minor > Attachments: maven-maven1-plugin.zip > > > A simple mvn plugins that converts a maven 1 project.xml to a maven 2 pom.xml. > Apart from the pom v3 to v4 conversion it also adds specific plugin > configurations to pom.xml from project.properties (there are a few samples > for some compiler, surefire, war settings and it can be easily extended). > After installing it using mvn:install you can run "mvn maven1:convert" on > maven 1 project for a quick start on maven 2. > Note: the org.apache.maven.model.v3_0_0.* classes are actually embedded in > the plugin due to MNG-1436 and MAVENUPLOAD-583 > If there is interest in this I can commit it to svn, please comment/vote here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] [m1] plugin releases
+4 Arnaud On 1/24/06, Lukas Theussl <[EMAIL PROTECTED]> wrote: > > > Hi, > > I'd like to call for a vote on the following m1 plugin releases: > > [] maven-changelog-plugin-1.9 > [] maven-file-activity-plugin-1.6 > [] maven-developer-activity-plugin-1.6 > [] maven-simian-plugin-1.6 > > The changelog plugin is the only one with major bug fixes and new > features, all the others have zero issues open. > > For snapshot downloads and links to future web pages, see below. > > +1 from me and 72h to vote. > > Cheers, > -Lukas > > > > > http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-changelog-plugin/ > > http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-file-activity-plugin/ > > http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-developer-activity-plugin/ > > http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-simian-plugin/ > > > maven plugin:download > -Dmaven.repo.remote=http://www.ibiblio.org/maven, > http://cvs.apache.org/repository/ > > -DgroupId=maven -DartifactId=maven-changelog-plugin -Dversion=1.9-SNAPSHOT > > maven plugin:download > -Dmaven.repo.remote=http://www.ibiblio.org/maven, > http://cvs.apache.org/repository/ > > -DgroupId=maven -DartifactId=maven-file-activity-plugin > -Dversion=1.6-SNAPSHOT > > maven plugin:download > -Dmaven.repo.remote=http://www.ibiblio.org/maven, > http://cvs.apache.org/repository/ > > -DgroupId=maven -DartifactId=maven-developer-activity-plugin > -Dversion=1.6-SNAPSHOT > > maven plugin:download > -Dmaven.repo.remote=http://www.ibiblio.org/maven, > http://cvs.apache.org/repository/ > > -DgroupId=maven -DartifactId=maven-simian-plugin -Dversion=1.6-SNAPSHOT > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
[jira] Closed: (MPJXR-24) Support multiple source folders, property "maven.src.dir" has no effect.
[ http://jira.codehaus.org/browse/MPJXR-24?page=all ] Lukas Theussl closed MPJXR-24: -- Resolution: Duplicate Documentation has been updated, the rest is a dupe of MPJXR-3. > Support multiple source folders, property "maven.src.dir" has no effect. > > > Key: MPJXR-24 > URL: http://jira.codehaus.org/browse/MPJXR-24 > Project: maven-jxr-plugin > Type: Improvement > Versions: 1.4.2 > Environment: Windows XP, Maven 1.02,... > Reporter: Achim Westermann > > Original Estimate: 1 day > Remaining: 1 day > > Please compare this request for improvement with the > way Jason did it for http://jira.codehaus.org/browse/MAVEN-130 . > This would support the concept of maven: unify the source folders > to a single property. > Additionally I tried to change the source folder. > http://maven.apache.org/reference/plugins/jxr/properties.html mentions > property "maven.src.dir" to be responsible for that. A change in > project.properties > did affect nothing. On the other hand a change of property > "maven.jxr.destdir" did > take an effect. > Please document the correct property for argument jxr's source directory. > kind regards, > Achim -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1530) Converter for maven 1 projects
[ http://jira.codehaus.org/browse/MNG-1530?page=comments#action_56944 ] Bryan Pauquette commented on MNG-1530: -- Newbie answer? mvn install:install-file -DgroupId=group-id -DartifactId=artifact-id -Dversion=version -Dpackaging=packaging -Dfile=fileToInstal Now I need to know the group-id artifact-d version packaging and fileToInstal. 1 question leads to 5 new questions. My ignorance has increased by a factor of 5. > Converter for maven 1 projects > -- > > Key: MNG-1530 > URL: http://jira.codehaus.org/browse/MNG-1530 > Project: Maven 2 > Type: Improvement > Components: Plugin Requests > Reporter: fabrizio giustina > Assignee: fabrizio giustina > Priority: Minor > Attachments: maven-maven1-plugin.zip > > > A simple mvn plugins that converts a maven 1 project.xml to a maven 2 pom.xml. > Apart from the pom v3 to v4 conversion it also adds specific plugin > configurations to pom.xml from project.properties (there are a few samples > for some compiler, surefire, war settings and it can be easily extended). > After installing it using mvn:install you can run "mvn maven1:convert" on > maven 1 project for a quick start on maven 2. > Note: the org.apache.maven.model.v3_0_0.* classes are actually embedded in > the plugin due to MNG-1436 and MAVENUPLOAD-583 > If there is interest in this I can commit it to svn, please comment/vote here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MASSEMBLY-56) Refactor DirectoryMojo so it can be run either stand-alone or attached
[ http://jira.codehaus.org/browse/MASSEMBLY-56?page=comments#action_56943 ] Dan Tran commented on MASSEMBLY-56: --- here is some discussion in IRC brett, i would like to help committing an assembly patch, but having trouble coming up with a name ;-) comments? http://jira.codehaus.org/browse/MASSEMBLY-56 * henry has joined #maven dantran: no idea not attached directory-only ? hheeh, you have the same problem eh?.. i hate naming not sure what the context is, but "detached" might help if you talk about sthg "not attached" ^^ standlone? they are all confusing the current :directory is the standalone one detached is not right either * hen has joined #maven * adc|mbl has quit IRC (Leaving) now i am not sure why we need this feature, surely we dont want to bind it to a phase, we want to run it as a standlone as well dantran: what was the original use case? I think it tries to solve infinite looping in assembly:directory where packing=pom but that bug was fixed anyway I think? dont think so, it still there, ppl use assembly:attached instead that is why we dont hear any more screaming ;-) http://jira.codehaus.org/browse/MASSEMBLY-37 k I now understand how this JIRA is for If you bind assembly:attached to a package phase and run mvn assembly:directory, it will loop The work around is to run maven package to then unzip the output manually Untill we can come up with a good name, introduce this patch may create more confusion ;-) > Refactor DirectoryMojo so it can be run either stand-alone or attached > -- > > Key: MASSEMBLY-56 > URL: http://jira.codehaus.org/browse/MASSEMBLY-56 > Project: Maven 2.x Assembly Plugin > Type: Improvement > Versions: 2.1 > Reporter: John Didion > Fix For: 2.1 > Attachments: MASSEMBLY-56.patch > > > Pretty straight-forward. Just make the directory goal into two goals (like > assembly and attached), one that can be run stand-alone and one that can be > run attached to a lifecycle phase. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPJXR-17) JXR Report isn't generated for tests unless sources exist
[ http://jira.codehaus.org/browse/MPJXR-17?page=all ] Lukas Theussl closed MPJXR-17: -- Assign To: (was: Jason van Zyl) Resolution: Fixed Fix Version: (was: 1.5) 1.4.2 > JXR Report isn't generated for tests unless sources exist > - > > Key: MPJXR-17 > URL: http://jira.codehaus.org/browse/MPJXR-17 > Project: maven-jxr-plugin > Type: Bug > Versions: 1.4.1 > Reporter: Matt Read > Fix For: 1.4.2 > > > The JXR report is not generated for tests unless sources exist. I can submit > a patch if necessary but the fix is very simple. > 1. In plugin.jelly the maven-jxr-plugin:register goal nests statements > such that test sources report won't be registered unless sources report is > registered. Un-nesting these ifs solves half the problem. > 2. Exactly the same issue in the maven-jxr-plugin:report goal. Un-nesting the > ifs means that you can generate a test report even if sources don't exist. > Motivation: > I have separated out my XP style acceptance tests into a separate > sub-project. This sub-project tests the built and deployed system as a whole > and doesn't have it's own source. > Matt. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MPJXR-17) JXR Report isn't generated for tests unless sources exist
[ http://jira.codehaus.org/browse/MPJXR-17?page=all ] Lukas Theussl reopened MPJXR-17: reopen to change fix version > JXR Report isn't generated for tests unless sources exist > - > > Key: MPJXR-17 > URL: http://jira.codehaus.org/browse/MPJXR-17 > Project: maven-jxr-plugin > Type: Bug > Versions: 1.4.1 > Reporter: Matt Read > Assignee: Jason van Zyl > Fix For: 1.5 > > > The JXR report is not generated for tests unless sources exist. I can submit > a patch if necessary but the fix is very simple. > 1. In plugin.jelly the maven-jxr-plugin:register goal nests statements > such that test sources report won't be registered unless sources report is > registered. Un-nesting these ifs solves half the problem. > 2. Exactly the same issue in the maven-jxr-plugin:report goal. Un-nesting the > ifs means that you can generate a test report even if sources don't exist. > Motivation: > I have separated out my XP style acceptance tests into a separate > sub-project. This sub-project tests the built and deployed system as a whole > and doesn't have it's own source. > Matt. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MPJXR-14) Support encoding and lang
[ http://jira.codehaus.org/browse/MPJXR-14?page=all ] Lukas Theussl reopened MPJXR-14: reopen to change fix version > Support encoding and lang > - > > Key: MPJXR-14 > URL: http://jira.codehaus.org/browse/MPJXR-14 > Project: maven-jxr-plugin > Type: Improvement > Reporter: Takayoshi Kimura > Assignee: Jason van Zyl > Fix For: 1.4.2 > Attachments: jxr.encoding.patch.txt, jxr.encoding.patch.txt > > > JXR does not supported encoding and lang. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPJXR-13) Using jxr on a empty java file is causing a NullPointerException
[ http://jira.codehaus.org/browse/MPJXR-13?page=all ] Lukas Theussl closed MPJXR-13: -- Resolution: Fixed > Using jxr on a empty java file is causing a NullPointerException > > > Key: MPJXR-13 > URL: http://jira.codehaus.org/browse/MPJXR-13 > Project: maven-jxr-plugin > Type: Bug > Environment: maven rc3, jxr-plugin-1.4 > Reporter: Julien Kirch > Priority: Trivial > Fix For: 1.4.2 > > > Trying to jxr-report an empty java file (0 byte) is causing a > BUILD FAILED > File.. C:\maven-1.0-rc3\unpacked_plugins\maven-jxr-plugin-1.4\plugin.jelly > Element... jxr:jxr > Line.. 97 > Column 31 > java.lang.NullPointerException > Total time: 21 seconds > Finished at: Wed Jun 16 15:06:22 CEST 2004 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPJXR-14) Support encoding and lang
[ http://jira.codehaus.org/browse/MPJXR-14?page=all ] Lukas Theussl closed MPJXR-14: -- Assign To: (was: Jason van Zyl) Resolution: Fixed Fix Version: (was: 1.5) 1.4.2 > Support encoding and lang > - > > Key: MPJXR-14 > URL: http://jira.codehaus.org/browse/MPJXR-14 > Project: maven-jxr-plugin > Type: Improvement > Reporter: Takayoshi Kimura > Fix For: 1.4.2 > Attachments: jxr.encoding.patch.txt, jxr.encoding.patch.txt > > > JXR does not supported encoding and lang. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPJXR-13) Using jxr on a empty java file is causing a NullPointerException
[ http://jira.codehaus.org/browse/MPJXR-13?page=all ] Lukas Theussl updated MPJXR-13: --- Fix Version: (was: 1.5) 1.4.2 > Using jxr on a empty java file is causing a NullPointerException > > > Key: MPJXR-13 > URL: http://jira.codehaus.org/browse/MPJXR-13 > Project: maven-jxr-plugin > Type: Bug > Environment: maven rc3, jxr-plugin-1.4 > Reporter: Julien Kirch > Priority: Trivial > Fix For: 1.4.2 > > > Trying to jxr-report an empty java file (0 byte) is causing a > BUILD FAILED > File.. C:\maven-1.0-rc3\unpacked_plugins\maven-jxr-plugin-1.4\plugin.jelly > Element... jxr:jxr > Line.. 97 > Column 31 > java.lang.NullPointerException > Total time: 21 seconds > Finished at: Wed Jun 16 15:06:22 CEST 2004 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MPJXR-13) Using jxr on a empty java file is causing a NullPointerException
[ http://jira.codehaus.org/browse/MPJXR-13?page=all ] Lukas Theussl reopened MPJXR-13: Assign To: (was: Jason van Zyl) Reopen to change fix version > Using jxr on a empty java file is causing a NullPointerException > > > Key: MPJXR-13 > URL: http://jira.codehaus.org/browse/MPJXR-13 > Project: maven-jxr-plugin > Type: Bug > Environment: maven rc3, jxr-plugin-1.4 > Reporter: Julien Kirch > Priority: Trivial > Fix For: 1.5 > > > Trying to jxr-report an empty java file (0 byte) is causing a > BUILD FAILED > File.. C:\maven-1.0-rc3\unpacked_plugins\maven-jxr-plugin-1.4\plugin.jelly > Element... jxr:jxr > Line.. 97 > Column 31 > java.lang.NullPointerException > Total time: 21 seconds > Finished at: Wed Jun 16 15:06:22 CEST 2004 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1530) Converter for maven 1 projects
[ http://jira.codehaus.org/browse/MNG-1530?page=comments#action_56937 ] Bryan Pauquette commented on MNG-1530: -- Newbie question. How do you install it? > Converter for maven 1 projects > -- > > Key: MNG-1530 > URL: http://jira.codehaus.org/browse/MNG-1530 > Project: Maven 2 > Type: Improvement > Components: Plugin Requests > Reporter: fabrizio giustina > Assignee: fabrizio giustina > Priority: Minor > Attachments: maven-maven1-plugin.zip > > > A simple mvn plugins that converts a maven 1 project.xml to a maven 2 pom.xml. > Apart from the pom v3 to v4 conversion it also adds specific plugin > configurations to pom.xml from project.properties (there are a few samples > for some compiler, surefire, war settings and it can be easily extended). > After installing it using mvn:install you can run "mvn maven1:convert" on > maven 1 project for a quick start on maven 2. > Note: the org.apache.maven.model.v3_0_0.* classes are actually embedded in > the plugin due to MNG-1436 and MAVENUPLOAD-583 > If there is interest in this I can commit it to svn, please comment/vote here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MCLOVER-20) Please add an option to save historical clover data
Please add an option to save historical clover data --- Key: MCLOVER-20 URL: http://jira.codehaus.org/browse/MCLOVER-20 Project: Maven 2.x Clover Plugin Type: New Feature Reporter: Joe Shomphe Please add the ability to save historical data like the maven-1 plugin Check out http://maven.apache.org/maven-1.x/reference/plugins/clover/changes-report.html Release 1.8 - 2005-03-04 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (WAGON-34) CLONE -wagon-file failed when used by maven-site-plugin
[ http://jira.codehaus.org/browse/WAGON-34?page=comments#action_56935 ] Matt Hicks commented on WAGON-34: - Even with the latest version of WagonFile, we still saw the issue of the path.exists() returning false. Removing the '.' from the path when it wasn't required corrected the problem. The patch is attached above. > CLONE -wagon-file failed when used by maven-site-plugin > --- > > Key: WAGON-34 > URL: http://jira.codehaus.org/browse/WAGON-34 > Project: wagon > Type: Bug > Versions: 1.0-alpha-6 > Reporter: Matt Hicks > Assignee: Brett Porter > Fix For: 1.0-alpha-7 > Attachments: wagon-file.patch > > > When maven-site-plugin try a deploy on a file URL, an error is triggered. > This is because maven-site-plugin call "wagon.putDirectory( inputDirectory, > "." );" which fails. > See > http://www.nabble.com/With-maven-2.0.2-site%3Adeploy-doesn%27t-work-t934716.html > In attachment, you can find a patch adding a test case, and the patch fixing > the bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (WAGON-34) CLONE -wagon-file failed when used by maven-site-plugin
CLONE -wagon-file failed when used by maven-site-plugin --- Key: WAGON-34 URL: http://jira.codehaus.org/browse/WAGON-34 Project: wagon Type: Bug Versions: 1.0-alpha-6 Reporter: Matt Hicks Assigned to: Brett Porter Fix For: 1.0-alpha-7 Attachments: wagon-file.patch When maven-site-plugin try a deploy on a file URL, an error is triggered. This is because maven-site-plugin call "wagon.putDirectory( inputDirectory, "." );" which fails. See http://www.nabble.com/With-maven-2.0.2-site%3Adeploy-doesn%27t-work-t934716.html In attachment, you can find a patch adding a test case, and the patch fixing the bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (WAGON-34) CLONE -wagon-file failed when used by maven-site-plugin
[ http://jira.codehaus.org/browse/WAGON-34?page=all ] Matt Hicks updated WAGON-34: Attachment: wagon-file.patch > CLONE -wagon-file failed when used by maven-site-plugin > --- > > Key: WAGON-34 > URL: http://jira.codehaus.org/browse/WAGON-34 > Project: wagon > Type: Bug > Versions: 1.0-alpha-6 > Reporter: Matt Hicks > Assignee: Brett Porter > Fix For: 1.0-alpha-7 > Attachments: wagon-file.patch > > > When maven-site-plugin try a deploy on a file URL, an error is triggered. > This is because maven-site-plugin call "wagon.putDirectory( inputDirectory, > "." );" which fails. > See > http://www.nabble.com/With-maven-2.0.2-site%3Adeploy-doesn%27t-work-t934716.html > In attachment, you can find a patch adding a test case, and the patch fixing > the bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MSUREFIRE-51) Add a configuration element which allows artifact exclusions
Add a configuration element which allows artifact exclusions Key: MSUREFIRE-51 URL: http://jira.codehaus.org/browse/MSUREFIRE-51 Project: Maven 2.x Surefire Plugin Type: New Feature Reporter: Jason van Zyl Taken from the message on the users mailing list: This smells like a scoping problem. ASM is not required for test execution (runtime) by Cobertura, ASM is only needed for swizzling the class files and that part is run during the process-classes phase. Cobertura itself needs it to compile and to instrument but ASM shouldn't end up in the test or runtime scopes/classpaths. I think this points to a tool scope or something akin to it. If that proves to be the case it's probably not going to be fixed for 2.0.3. A solution might be to add an artifact exclusion configuration to surefire (possibly only for forking mode). Then the lifecycle.xml for the Cobertura plug-in which controls the execution of surefire could exclude ASM during test runs. That could probably make it into the surefire plug-in's next release if that solution works. That's all I can think of off the top of my head. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-2013) The front page of the site still says Maven 2.0.1
[ http://jira.codehaus.org/browse/MNG-2013?page=all ] Dennis Lundberg updated MNG-2013: - Attachment: MNG-2013.patch > The front page of the site still says Maven 2.0.1 > - > > Key: MNG-2013 > URL: http://jira.codehaus.org/browse/MNG-2013 > Project: Maven 2 > Type: Bug > Components: documentation - general > Reporter: Dennis Lundberg > Attachments: MNG-2013.patch > > > The front page of the Maven site still refers to version 2.0.1. The attched > patch updates this to 2.0.2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-2013) The front page of the site still says Maven 2.0.1
The front page of the site still says Maven 2.0.1 - Key: MNG-2013 URL: http://jira.codehaus.org/browse/MNG-2013 Project: Maven 2 Type: Bug Components: documentation - general Reporter: Dennis Lundberg The front page of the Maven site still refers to version 2.0.1. The attched patch updates this to 2.0.2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Closed: (MAVEN-1693) Remove unused from POM model, documentation and XSD
Brett Porter wrote:
IIRC, touchstone tests it.
Thanks for the tip. Now I don't know how touchstone works, but as I
understand it, the following should work:
if you put in your project.xml:
pomPropertyA
then you should access the property in a custom jelly script like:
propertyA = ${pom.getProperty('propertyA')}
But this doesn't work, I get no output. What am I missing?
-Lukas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MASSEMBLY-54) Unable to filter files while creating assembly
[ http://jira.codehaus.org/browse/MASSEMBLY-54?page=comments#action_56929 ] Corridor Software Developer commented on MASSEMBLY-54: -- agreed, this is an issue when creating distributions for various environments. We're currently working around it by having multiple file sets with the tweaks already in them and a profile per environment to specify which set to grab. Since only 2-4 lines in the files change, this is obviously inefficient, especially when the files need a sweeping change. > Unable to filter files while creating assembly > -- > > Key: MASSEMBLY-54 > URL: http://jira.codehaus.org/browse/MASSEMBLY-54 > Project: Maven 2.x Assembly Plugin > Type: Improvement > Versions: 2.0 > Reporter: Chris Hagmann > Fix For: 2.1 > > > It doesn't seem to be possible to use filtering when creating assemblies. I > have a couple of plain-text files which need to be updated when creating the > assembly (e.g. README.TXT, .version). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
The "How To Help" page needs help...
Hi The "How To Help" page at http://docs.codehaus.org/display/MAVEN/How+to+help is a great thing. It shows a selection of issues that people can help out with. Of the 25 "Novice Issues" there are patches for 15 of them. Many of them are documentation related. It would be great if one of the developers could find some time to apply or reject these patches. We, "the novice helpers", would also like some more issues to work on :-) So if someone could add some more select issues to that same list would be nice. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (CONTINUUM-571) CVS checkout with :scm:cvs:ext: url fails
[ http://jira.codehaus.org/browse/CONTINUUM-571?page=comments#action_56928 ] Emmanuel Venisse commented on CONTINUUM-571: I'll create a patch in maven-scm cvs provider to delete the directory if it exists. Normally, we can checkout in a dir even if it exist and it's empty, i don't know why it doesn't work on your machine. > CVS checkout with :scm:cvs:ext: url fails > - > > Key: CONTINUUM-571 > URL: http://jira.codehaus.org/browse/CONTINUUM-571 > Project: Continuum > Type: Bug > Components: Core system > Versions: 1.0.2 > Environment: Linux Suse 9.3 > Reporter: Carlo Bonamico > > > When the working directory is empty, requesting a "build now" for a project > with a :scm:cvs:ext: method fails. > The CVS is configured with external SSH protocol, with publick key > authentication, and checking out from command line (using the same cvs > command as in the continuum log) works fine. > The failure message is: >Provider message: The cvs command failed. >Command output: > --- >cvs checkout: in directory 52: >cvs checkout: cannot open CVS/Entries for reading: No such file or > directory >cvs [checkout aborted]: cannot write : No such file or directory > > --- > The full continuum console log says: > jvm 1| 2006-01-25 15:19:20,013 [SocketListener0-1] INFO > ContinuumStore:jdo - project :52 > jvm 1| 2006-01-25 15:19:20,018 [SocketListener0-1] INFO > ContinuumStore:jdo - nb bd for project 52 : 1 - bd id : 62 > jvm 1| 2006-01-25 15:19:20,018 [SocketListener0-1] INFO > ContinuumStore:jdo - getDefaultBuildDefinition : 5ms > jvm 1| 2006-01-25 15:19:20,068 [SocketListener0-1] INFO Continuum > - Enqueuing 'SampleTestCVS' (Build definition id=62). > jvm 1| 2006-01-25 15:19:20,349 [Thread-1] INFO ContinuumScm > - Checking out project: 'SampleTestCVS', id: '52' to > '/srv/build/continuum/apps/continuum/working-directory/52'. > jvm 1| 2006-01-25 15:19:20,350 [Thread-1] DEBUG ScmManager > - Working directory: > /srv/build/continuum/apps/continuum/working-directory/52 > jvm 1| 2006-01-25 15:19:20,350 [Thread-1] DEBUG ScmManager > - Command line: cvs -f -d :ext:[EMAIL PROTECTED]:/home/cvs -q checkout > -d 52 SANDBOX/sampleTestCVS > jvm 1| 2006-01-25 15:19:20,419 [SocketListener0-1] INFO > ContinuumStore:jdo - project :52 > jvm 1| 2006-01-25 15:19:20,426 [SocketListener0-1] INFO > ContinuumStore:jdo - nb bd for project 52 : 1 - bd id : 62 > jvm 1| 2006-01-25 15:19:20,426 [SocketListener0-1] INFO > ContinuumStore:jdo - getDefaultBuildDefinition : 6ms > jvm 1| 2006-01-25 15:19:20,611 [Thread-1] WARN ContinuumScm > - Error while checking out the code for project: 'SampleTestCVS', id: > '52' to '/srv/build/continuum/apps/continuum/working-directory/52'. > jvm 1| 2006-01-25 15:19:20,611 [Thread-1] WARN ContinuumScm > - Command output: cvs checkout: in directory 52: > jvm 1| cvs checkout: cannot open CVS/Entries for reading: No such file or > directory > jvm 1| cvs [checkout aborted]: cannot write : No such > file or directory > jvm 1| > jvm 1| 2006-01-25 15:19:20,611 [Thread-1] WARN ContinuumScm > - Provider message: The cvs command failed. > jvm 1| 2006-01-25 15:19:21,426 [Thread-1] INFO Notifier:mail > - No mail recipients for 'SampleTestCVS'. > Note - The "cannot open CVS/Entries" error could also be related to a failed > authentication. > The same happens if I add a new project. > My SCM url is a cvs:ext: url with a ssh protocol, configured with > CVS_RSH="ssh" in /etc/profiles > Manually reproducing the bug > > However, I just made this test: > I went on the command line in the folder > /srv/build/continuum/apps/continuum/working-directory > if I delete the build directory (which is 52 in my case) > working-directory> rm -rf 52 > working-directory> cvs -f -d :ext:[EMAIL PROTECTED]:/home/cvs -q checkout -d > 52 SANDBOX/sampleTestCVS > cvs correctly creates the 52 directory and does the checkout >U 52/.classpath >U 52/.cvsignore >U 52/.project >... >U 52/xdocs/navigation.xml > If I run the same command again, it works. > BUT, if I delete only the *content* of the 52 directory, and perform a cvs > checkout, it fails, with the same CVS/Entries error as above: > working-directory> rm -rf 52/* > working-directory> cvs -f -d :ext:[EMAIL PROTECTED]:/home/cvs -q checkout -d > 52 SANDBOX/sampleTestCVS > cvs checkout: in directory 52: > cvs chec
[maven2 build trunk - SUCCESS - update] Wed Jan 25 20:00:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060125.21.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060125.21.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Wed Jan 25 19:45:01 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060125.194501.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060125.194501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (SCM-142) Starteam tree stale
[ http://jira.codehaus.org/browse/SCM-142?page=comments#action_56927 ] Bob Herrmann commented on SCM-142: -- The output of bco is different enough that it doesnt detect file changes. So the "stcmd" to "bco" thing is only really useful if you only always force builds (and don't mind that it always says No Changes.) I'm experimenting some more, trying to get this stuff to work correctly. Will keep this bug advised of developements > Starteam tree stale > --- > > Key: SCM-142 > URL: http://jira.codehaus.org/browse/SCM-142 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-starteam > Environment: continuum-1.0.2 > Reporter: Bob Herrmann > > > It only takes a few changes to starteam for the checked out filesystem to > become hopelessly stale. The only recovery option is to completely remove > all files and startover. Either the code checking out is not handing the > timestamps correctly, or starteam command line has problems keeping a checked > out tree in sync (this more likely - as we also see this problem with AntHill > when using it's incremental builder.) Possible fixes might be to detect > 'unknown' status's and flush the checked out tree. Or try using the 2005 bco > command instead of stcmd. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MASSEMBLY-62) Ability to share DependencySets, FileSets, FileItems
[ http://jira.codehaus.org/browse/MASSEMBLY-62?page=all ] Dan Tran closed MASSEMBLY-62: - Assign To: Dan Tran Resolution: Fixed Fix Version: 2.1 new feature added > Ability to share DependencySets, FileSets, FileItems > > > Key: MASSEMBLY-62 > URL: http://jira.codehaus.org/browse/MASSEMBLY-62 > Project: Maven 2.x Assembly Plugin > Type: New Feature > Versions: 2.0 > Environment: xp, linux > Reporter: Dan Tran > Assignee: Dan Tran > Fix For: 2.1 > > > My assembly project can produce multiple assemblies thru mutliple > descriptors. I need ability to have multiple descriptor to share common > elements -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-659) Upload AjaxTags library
[ http://jira.codehaus.org/browse/MAVENUPLOAD-659?page=comments#action_56925 ] K.C. Baltz commented on MAVENUPLOAD-659: It looks like the dependency has changed to jericho-html, which is available on Ibiblio (http://www.ibiblio.org/maven2/net/htmlparser/jericho-html/). > Upload AjaxTags library > --- > > Key: MAVENUPLOAD-659 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-659 > Project: maven-upload-requests > Type: Task > Reporter: Olivier Lamy > Attachments: ajaxtags-1.1.5-bundle.jar, ajaxtags-1.1.5.jar, project.xml > > > Hi, > Please upload the AjaxTags library version 1.1.5. > The project url is located http://ajaxtags.sourceforge.net. > Download link : > http://sourceforge.net/project/showfiles.php?group_id=140499&package_id=154180&release_id=370728 > This project is build with maven1. > Thanks, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MANTRUN-39) When maven-antrun-plugin artifact id is defined twice in a pom, only second one is executed.
[ http://jira.codehaus.org/browse/MANTRUN-39?page=all ] Carlos Sanchez closed MANTRUN-39: - Assign To: Carlos Sanchez Resolution: Duplicate > When maven-antrun-plugin artifact id is defined twice in a pom, only second > one is executed. > > > Key: MANTRUN-39 > URL: http://jira.codehaus.org/browse/MANTRUN-39 > Project: Maven 2.x Antrun Plugin > Type: Wish > Versions: 1.1 > Environment: Windows XP > Reporter: Stu Huettier > Assignee: Carlos Sanchez > Priority: Minor > > > Could Maven give a verbose warning that the maven-antrun-plugin artifact id > is defined twice in a pom and that only second one is executed? While it is > probably a user error to define such a thing twice in a pom (clearly, > multiple executions ought to be created within a single maven-antrun-plugin > definition) it would be helpful if Maven would give a warning, perhaps > something along the lines of, "Please do not define multiple instances of the > same artifact Id." instead of just skipping over the first and running the > second. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNGECLIPSE-56) Exception running M2 build
[ http://jira.codehaus.org/browse/MNGECLIPSE-56?page=all ] Kees de Kooter updated MNGECLIPSE-56: - Attachment: bt-orderbuilder-workbench generate.launch > Exception running M2 build > -- > > Key: MNGECLIPSE-56 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-56 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Components: Maven Launcher > Versions: 0.0.4, 0.0.3 > Environment: Eclipse 3.1.1 + WTP 1.0, JRE 1.5.0_06 > Reporter: Kees de Kooter > Assignee: Dmitri Maximovich > Priority: Blocker > Attachments: bt-orderbuilder-workbench generate.launch, eclipse.log > > > When I try to run an m2 build an error pops up: "Could not find the main > class. Program will exit.". > The console shows the following: > java.lang.NoClassDefFoundError: and > Exception in thread "main" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNGECLIPSE-56) Exception running M2 build
[ http://jira.codehaus.org/browse/MNGECLIPSE-56?page=comments#action_56923 ] Kees de Kooter commented on MNGECLIPSE-56: -- Yes Dimitri, running JRE. Attached the launch file. > Exception running M2 build > -- > > Key: MNGECLIPSE-56 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-56 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Components: Maven Launcher > Versions: 0.0.4, 0.0.3 > Environment: Eclipse 3.1.1 + WTP 1.0, JRE 1.5.0_06 > Reporter: Kees de Kooter > Assignee: Dmitri Maximovich > Priority: Blocker > Attachments: bt-orderbuilder-workbench generate.launch, eclipse.log > > > When I try to run an m2 build an error pops up: "Could not find the main > class. Program will exit.". > The console shows the following: > java.lang.NoClassDefFoundError: and > Exception in thread "main" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MANTRUN-37) Antrun breaks on multi-module builds
[ http://jira.codehaus.org/browse/MANTRUN-37?page=comments#action_56919 ] Paul Zeeman commented on MANTRUN-37: I too have encountered this issue following a move to Maven 2.0.2 (to pick up another fix). While I have a multi-module project, running a specific module's pom standalone still shows the problem. Changing the version of the antrun plugin to 1.0 still shows the problem. I have a number of lines reporting through plexus before the error occurs: Please contact me if you would like more information. [INFO] Building jar: t:\optnet_ne_web_interface\firefly\craft\base\target\base-1 .0-SNAPSHOT.jar - this realm = app0.child-container[org.apache.maven.plugins:maven-antrun-plugin] urls[0] = file:/D:/Profiles/pzeeman/.m2/repository/org/apache/maven/plugins/mave n-antrun-plugin/1.1/maven-antrun-plugin-1.1.jar urls[1] = file:/D:/Profiles/pzeeman/.m2/repository/ant/ant/1.6.5/ant-1.6.5.jar urls[2] = file:/D:/Profiles/pzeeman/.m2/repository/ant/ant-launcher/1.6.5/ant-la uncher-1.6.5.jar Number of imports: 0 this realm = plexus.core.maven urls[0] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-artifact- 2.0.2.jar urls[1] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-error-dia gnostics-2.0.2.jar urls[2] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-model-2.0 .2.jar urls[3] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/jsch-0.1.24.jar urls[4] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-reporting -api-2.0.2.jar urls[5] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/plexus-interact ivity-api-1.0-alpha-4.jar urls[6] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-repositor y-metadata-2.0.2.jar urls[7] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/commons-cli-1.0 .jar urls[8] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-profile-2 .0.2.jar urls[9] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/wagon-file-1.0- alpha-6.jar urls[10] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-plugin-p arameter-documenter-2.0.2.jar urls[11] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/wagon-provider -api-1.0-alpha-6.jar urls[12] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-plugin-r egistry-2.0.2.jar urls[13] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/wagon-ssh-1.0- alpha-6.jar urls[14] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-artifact -manager-2.0.2.jar urls[15] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-project- 2.0.2.jar urls[16] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/wagon-ssh-exte rnal-1.0-alpha-6.jar urls[17] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-settings -2.0.2.jar urls[18] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-plugin-a pi-2.0.2.jar urls[19] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/doxia-sink-api -1.0-alpha-7.jar urls[20] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-monitor- 2.0.2.jar urls[21] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-plugin-d escriptor-2.0.2.jar urls[22] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/wagon-http-lig htweight-1.0-alpha-6.jar urls[23] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-core-2.0 .2.jar urls[24] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-core-2.0 .2-javadoc.jar urls[25] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/lib/maven-site-plu gin-2.0-alpha-2.jar Number of imports: 0 this realm = plexus.core urls[0] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/core/plexus-contain er-default-1.0-alpha-9.jar urls[1] = file:/t:/optnet_ne_web_interface/tools/maven-2.0.2/core/plexus-utils-1 .1.jar Number of imports: 0 - [INFO] - --- [ERROR] BUILD ERROR [INFO] - --- [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plu gins:maven-antrun-plugin:1.1:run': Unable to find the mojo 'org.apache.maven.plu gins:maven-antrun-plugin:1.1:run' in the plugin 'org.apache.maven.plugins:maven- antrun-plugin' org/apache/tools/ant/PropertyHelper [INFO] - --- [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the pl ugin manager executing goal 'org.apache.maven.plugins:maven-antrun-plugin:1.1:ru n': Unable to find the mojo 'org.apache.maven.plugins:maven-antrun-plugin:1.1:ru n' in the plugin 'org.apache.maven.plugins:maven-antrun-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:535) at org.apache.mave
[jira] Commented: (MNGECLIPSE-56) Exception running M2 build
[ http://jira.codehaus.org/browse/MNGECLIPSE-56?page=comments#action_56915 ] Dmitri Maximovich commented on MNGECLIPSE-56: - Kees, Please attach your project (or any minimal project) on which probelm is reproduceable and specify what target you're executing. To confirm: you're starting eclipse using Sun's JRE (not JDK) 1.5.0_06 on Windows XP? > Exception running M2 build > -- > > Key: MNGECLIPSE-56 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-56 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Components: Maven Launcher > Versions: 0.0.4, 0.0.3 > Environment: Eclipse 3.1.1 + WTP 1.0, JRE 1.5.0_06 > Reporter: Kees de Kooter > Assignee: Dmitri Maximovich > Priority: Blocker > Attachments: eclipse.log > > > When I try to run an m2 build an error pops up: "Could not find the main > class. Program will exit.". > The console shows the following: > java.lang.NoClassDefFoundError: and > Exception in thread "main" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNGECLIPSE-57) Unable to download the artifact from any repository
[ http://jira.codehaus.org/browse/MNGECLIPSE-57?page=comments#action_56913 ] Leonardo Quijano Vincenzi commented on MNGECLIPSE-57: - This is my debug log: 1/25/06 9:58:05 AM CST: Local repository folder "" does not exist 1/25/06 9:58:05 AM CST: [DEBUG] Found 0 components to load on start 1/25/06 9:58:05 AM CST: [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\Leonardo\.m2\plugin-registry.xml' 1/25/06 9:58:05 AM CST: [DEBUG] Building Maven global-level settings from: 'C:\Program Files\Eclipse\conf\settings.xml' 1/25/06 9:58:05 AM CST: [DEBUG] Building Maven user-level settings from: 'C:\Documents and Settings\Leonardo\.m2\settings.xml' 1/25/06 9:58:06 AM CST: [DEBUG] Trying repository central 1/25/06 9:58:06 AM CST: [WARN] Unable to get resource from repository central (http://repo1.maven.org/maven2) 1/25/06 9:58:06 AM CST: Unable to download the artifact from any repository This starts hapenning during the "indexing " phase on the plugin. This is only on the dependency resolver. I'm not building anything at this moment. Just right after Eclipse starts, it starts to show these errors. > Unable to download the artifact from any repository > --- > > Key: MNGECLIPSE-57 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-57 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Versions: 0.0.4 > Environment: Windows XPSP1, MyEclipse IDE 4.0, Eclipse 3.1.1 > Reporter: Leonardo Quijano Vincenzi > Assignee: Eugene Kuleshov > Attachments: pom.xml > > > It seems like I'm getting a lot of these (I just downloaded M2ECLIPSE 0.0.4, > but I don't know if the problems were there before) > 1/24/06 5:00:08 PM CST: Local repository folder "" does not exist > 1/24/06 5:00:11 PM CST: [WARN] Unable to get resource from repository central > (http://repo1.maven.org/maven2) > 1/24/06 5:00:11 PM CST: Unable to download the artifact from any repository > This is shown a lot of times (my guess is once for every folder in the > project) and it significantly slows down development. > Attached is my pom.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNGECLIPSE-57) Unable to download the artifact from any repository
[ http://jira.codehaus.org/browse/MNGECLIPSE-57?page=comments#action_56914 ] Leonardo Quijano Vincenzi commented on MNGECLIPSE-57: - By the way... I'm not getting anything on .log. Just some missing builder warnings: !ENTRY org.eclipse.core.resources 2 1 2006-01-25 09:58:31.314 !MESSAGE Skipping builder org.eclipse.wst.common.modulecore.ComponentStructuralBuilder for project sigep-services. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled. !ENTRY org.eclipse.core.resources 2 1 2006-01-25 10:00:49.913 !MESSAGE Skipping builder org.eclipse.wst.validation.validationbuilder for project sigep-services. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled. !ENTRY org.eclipse.core.resources 2 1 2006-01-25 10:00:49.923 !MESSAGE Skipping builder org.eclipse.wst.common.modulecore.ComponentStructuralBuilderDependencyResolver for project sigep-services. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled. !ENTRY org.eclipse.core.resources 2 1 2006-01-25 10:00:49.933 !MESSAGE Skipping builder org.eclipse.wst.common.modulecore.DependencyGraphBuilder for project sigep-services. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled. > Unable to download the artifact from any repository > --- > > Key: MNGECLIPSE-57 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-57 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Versions: 0.0.4 > Environment: Windows XPSP1, MyEclipse IDE 4.0, Eclipse 3.1.1 > Reporter: Leonardo Quijano Vincenzi > Assignee: Eugene Kuleshov > Attachments: pom.xml > > > It seems like I'm getting a lot of these (I just downloaded M2ECLIPSE 0.0.4, > but I don't know if the problems were there before) > 1/24/06 5:00:08 PM CST: Local repository folder "" does not exist > 1/24/06 5:00:11 PM CST: [WARN] Unable to get resource from repository central > (http://repo1.maven.org/maven2) > 1/24/06 5:00:11 PM CST: Unable to download the artifact from any repository > This is shown a lot of times (my guess is once for every folder in the > project) and it significantly slows down development. > Attached is my pom.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Changes M2 plugin (there is no JIRA project for this plugin)
http://jira.codehaus.org/browse/MOJO changes component -Original Message- From: Grzegorz Słowikowski [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 25, 2006 9:24 AM To: Maven Developers List Subject: Changes M2 plugin (there is no JIRA project for this plugin) Hi Maven2 changes plugin 2.0-beta-1 When parsing changes.xml we got exception. This exception is not logged. there is e.printStackTrace() instead of log statement. (org.apache.maven.changes.ChangesXML.java line 62) Greg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m1] howto log to console from java plugin
Weird, honestly, I must be missing something. If you build the eclipse
plugin locally, you should have info/warn output when using it, see
the code:
http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/eclipse/src/main/org/apache/maven/plugin/eclipse/JavaSourcesDownloader.java?rev=369028&view=markup
Your code seems OK to me.
Stéphane
On 1/25/06, Jörg Schaible <[EMAIL PROTECTED]> wrote:
> Hi Stephane,
>
> Stephane Nicoll wrote on Tuesday, January 24, 2006 3:31 PM:
>
> > Works for me, logging level should be at least info
> >
> > Show your code please
>
> Initialization from plugin.jelly:
>
> = %<
> description="Ensure all necessary properties">
>
> var="xxx"
> class="com.elsagsolutions.plugins.xxx.Bean"
> project="${pom}"
> targetDirectory="${maven.xxx.zip.dir}" />
>
>
>
> description="Prepare filesystem with any files to be included
> into the zip"
> prereqs="xxx:prereq">
>
>
>
>
> = %<
>
> Snippets from the Java-Code:
>
> = %<
> private static Log log =
> LogFactory.getLog(QualityManagementBridgeBean.class);
>
> public File prepareZip() throws MavenException {
> checkAttributes();
> final Map apps = createDomains();
> createApplications(apps);
> log.warn("Processed apps");
> final Map ejbs = new HashMap();
> final Map wars = new HashMap();
> for (final Iterator iter = apps.keySet().iterator(); iter.hasNext();)
> {
> final String appName = (String)iter.next();
> final Map ears = (Map)apps.get(appName);
> createEARs(ears, ejbs, wars);
> }
> log.warn("Processed ears");
> createEJBs(ejbs);
> log.warn("Processed ejbs");
> createWARs(wars);
> log.warn("Processed wars");
> return domsDir.getParentFile();
> }
> = %<
>
> no output to console at all. If I log as error I get the output, but again
> not synchronized with the printed lines from the jelly code:
>
> = %<
> $ maven clean xxx:prepare-zip
> __ __
> | \/ |__ _Apache__ ___
> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> |_| |_\__,_|\_/\___|_||_| v. 1.0.2
>
> build:start:
>
> clean:clean:
> [delete] Deleting directory
> C:\Work\Projects\maven-1-plugins\xxx\src\plugin-test\target
> Processed apps
> Processed ears
> Processed ejbs
> Processed wars
>
> clean:
>
> xxx:prereq:
>
> xxx:prepare-zip:
>
> BUILD SUCCESSFUL
> Total time: 43 seconds
> Finished at: Wed Jan 25 16:23:24 CET 2006
> = %<
>
> The lines should have been printed after "xxx:prepare-zip".
>
> [snip]
>
> - Jörg
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
.::You're welcome ::.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: eclipse and source plugin
Nicolas, thanks for the report, I'll have a look to it later today. Cheers, Stéphane On 1/25/06, Nicolas De Loof <[EMAIL PROTECTED]> wrote: > > Hello, > I've just installed eclipse and source plugin snapshots : "official" > sourcejars support is great ! > > Jus my 2 cents : > - when a dependency has property "eclipse.dependency", eclipse plugin > may NOT try to download sources > - eclipse plugin may avoid creating duplicate entries when > "maven.eclipse.resources.addtoclasspath" is true and a > element points to a source directory : in my case, some config files are > generated in generated-sources (with some java code) and I get duplicate > source entries > > Thanks > > Nico. > > 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. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .::You're welcome ::. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
eclipse and source plugin
Hello, I've just installed eclipse and source plugin snapshots : "official" sourcejars support is great ! Jus my 2 cents : - when a dependency has property "eclipse.dependency", eclipse plugin may NOT try to download sources - eclipse plugin may avoid creating duplicate entries when "maven.eclipse.resources.addtoclasspath" is true and a element points to a source directory : in my case, some config files are generated in generated-sources (with some java code) and I get duplicate source entries Thanks Nico. 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. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Changes M2 plugin (there is no JIRA project for this plugin)
Hi Maven2 changes plugin 2.0-beta-1 When parsing changes.xml we got exception. This exception is not logged. there is e.printStackTrace() instead of log statement. (org.apache.maven.changes.ChangesXML.java line 62) Greg
RE: [m1] howto log to console from java plugin
Hi Stephane,
Stephane Nicoll wrote on Tuesday, January 24, 2006 3:31 PM:
> Works for me, logging level should be at least info
>
> Show your code please
Initialization from plugin.jelly:
= %<
= %<
Snippets from the Java-Code:
= %<
private static Log log =
LogFactory.getLog(QualityManagementBridgeBean.class);
public File prepareZip() throws MavenException {
checkAttributes();
final Map apps = createDomains();
createApplications(apps);
log.warn("Processed apps");
final Map ejbs = new HashMap();
final Map wars = new HashMap();
for (final Iterator iter = apps.keySet().iterator(); iter.hasNext();) {
final String appName = (String)iter.next();
final Map ears = (Map)apps.get(appName);
createEARs(ears, ejbs, wars);
}
log.warn("Processed ears");
createEJBs(ejbs);
log.warn("Processed ejbs");
createWARs(wars);
log.warn("Processed wars");
return domsDir.getParentFile();
}
= %<
no output to console at all. If I log as error I get the output, but again not
synchronized with the printed lines from the jelly code:
= %<
$ maven clean xxx:prepare-zip
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
build:start:
clean:clean:
[delete] Deleting directory
C:\Work\Projects\maven-1-plugins\xxx\src\plugin-test\target
Processed apps
Processed ears
Processed ejbs
Processed wars
clean:
xxx:prereq:
xxx:prepare-zip:
BUILD SUCCESSFUL
Total time: 43 seconds
Finished at: Wed Jan 25 16:23:24 CET 2006
= %<
The lines should have been printed after "xxx:prepare-zip".
[snip]
- Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - SUCCESS - update] Wed Jan 25 15:00:00 GMT 2006
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20060125.150001.war Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060125.150001.txt
Re: why no ant tasks for m2.0.2 on the repository
Jason van Zyl wrote: Steve Loughran wrote: Brett Porter wrote: It's a manual step in the release process that hadn't been included in our docs, so each time a different person cuts the release it gets skipped. that's what automation is for :) I did not put them there because it was a signed release and as per Board policy they go to the official Apache distribution channels first i.e. our mirrors. Are you trying to pull the ant task JAR from the repository as part of a process? Ant's fetch.xml bootstraps its library management by pulling that file down first, (soon) verifying the checksum, then continuing. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [important] plugin statuses
> -Original Message- > From: Mike Perham [mailto:[EMAIL PROTECTED] > Sent: mercredi 25 janvier 2006 15:53 > To: Maven Developers List > Subject: RE: [important] plugin statuses > > About that... I'm still waiting on feedback on MCLOVER-19. See my last > three comments there. I know... But as I told you I'm not ready to implement it right now and answering your comments is very close to implementing it as it's not an easy topic... I'm doing my best and I apologize for not answering faster. Thanks -Vincent > -Original Message- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 25, 2006 2:35 AM > To: 'Maven Developers List' > Subject: RE: [important] plugin statuses > > I'm maintaining the Clover plugin (as time permits). It's already in a > good shape and I believe most issues are feature requests. It's still > missing lots of features when compared with the m1 version. > > I'm happy for any help though (Note that Mike Perham is already > helping). > > Thanks > -Vincent > > > -Original Message- > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > Sent: mercredi 25 janvier 2006 03:03 > > To: Maven Developers List > > Subject: Re: [important] plugin statuses > > > > Anyone want to update: > > clean, ear, ejb, jar, plugin, rar, war, compiler, resources, source, > > ant, antlr, release, repository, idea, eclipse, verifier, checkstyle, > > clover, javadoc, projectinforeports below? > > > > I'll pass back over this and fill in the gaps at the end of the month, > > > then this will become a monthly activity (as segregated below). > > > > Let me know if you have any thoughts on the effectiveness of this. > > > > - Brett > > > > Brett Porter wrote: > > > Hi, > > > > > > Some time back there was a proposal about plugin maintainers, and I > > > adapted that proposal for m2 a little. I don't think that our > > > community fits assigning a person to do something, so I'd like to > try this. > > > > > > Next Wednesday we have a board report due. I'd like to get the > > > status of > > > *all* the plugins summarised by people currently interested/working > > > on them. Then we'll get some others to take a look and if something > > > looks close to a release or particularly neglected we can deal with > it. > > > > > > While we do all now, I think we can do a small group each month, > > > completing them all by the end of the next board report. So here I > > > assign some for end Jan, some for end Feb, some for end Mar. > > > Remember, this time we need to do them all. > > > > > > We can try this inline, but maybe next time we need to find a better > > way. > > > > > > Anyone have additional thoughts on this? > > > > > > To be completed by Jan, April, July, Oct clean assembly > > > * Cleaned up several issues. Prep release next month. New > > > functionality and significant bugfixes. X outstanding issues ear ejb > > > > jar plugin rar war compiler deploy > > > * Just released. 1 outstanding minor issue install > > > * Just released. No outstanding issues surefire > > > * Just release. X outstanding issues resources source > > > > > > To be completed by Feb, May, Aug, Nov ant antrun > > > * Recently released. X outstanding issues. > > > antlr > > > release > > > repository > > > help > > > * Preparing release. 2 new feature requests in JIRA for next > release. > > > idea > > > eclipse > > > verifier > > > > > > To be completed by Mar, Jun, Sep, Dec checkstyle clover javadoc pmd > > > * Release in progress. No outstanding issues. > > > project-info-reports > > > site > > > * Significant new work. Nearing 2.0 release. X outstanding issues > > > > > > > > > Thanks! > > > - Brett > > > > > > > > > - 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] > > > > - > 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]
[jira] Closed: (MNG-1938) site:deploy hangs forever on remote upack command
[ http://jira.codehaus.org/browse/MNG-1938?page=all ] Mike Perham closed MNG-1938: Resolution: Duplicate WAGONSSH-36 has the fix. It just needs to be applied as I don't have commit rights to wagon. > site:deploy hangs forever on remote upack command > - > > Key: MNG-1938 > URL: http://jira.codehaus.org/browse/MNG-1938 > Project: Maven 2 > Type: Bug > Versions: 2.0.1 > Environment: maven 2.0.1 with wagon and jsch fixes as given by Brett Porter > in http://www.nabble.com/call-for-testers:-scp-wagon-t854948.html. > Site runs on Linux (CentOS 4.2). Both scp and sftp protocol produces the same > error > Reporter: Ørjan Austvold > Attachments: thread-dump.txt > > > site:deploy work fine for small artifact sites (<1MB?) but hangs forever on > the unpack command: > Executing command: cd /var/foo/.; unzip -o wagon17515.zip; rm -f > wagon17515.zip > Looking on the /var/foo directory on the server I can see that the site has > been sucessfully unpacked and the zip file has been removed. > I did a kill -3 on the vm to get a thread dump of what was going on and found > that there where 3 threads waiting on a jsch inputstreams (see the attached > thread dump). The main thread seems to be waiting for input on the > executeCommand method of the AbstractSshWagon (line 292). > Could it be that some of the fixes made on the wagon for repository > deployment/downloading should be done for executeCommand to? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [important] plugin statuses
About that... I'm still waiting on feedback on MCLOVER-19. See my last three comments there. -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 25, 2006 2:35 AM To: 'Maven Developers List' Subject: RE: [important] plugin statuses I'm maintaining the Clover plugin (as time permits). It's already in a good shape and I believe most issues are feature requests. It's still missing lots of features when compared with the m1 version. I'm happy for any help though (Note that Mike Perham is already helping). Thanks -Vincent > -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: mercredi 25 janvier 2006 03:03 > To: Maven Developers List > Subject: Re: [important] plugin statuses > > Anyone want to update: > clean, ear, ejb, jar, plugin, rar, war, compiler, resources, source, > ant, antlr, release, repository, idea, eclipse, verifier, checkstyle, > clover, javadoc, projectinforeports below? > > I'll pass back over this and fill in the gaps at the end of the month, > then this will become a monthly activity (as segregated below). > > Let me know if you have any thoughts on the effectiveness of this. > > - Brett > > Brett Porter wrote: > > Hi, > > > > Some time back there was a proposal about plugin maintainers, and I > > adapted that proposal for m2 a little. I don't think that our > > community fits assigning a person to do something, so I'd like to try this. > > > > Next Wednesday we have a board report due. I'd like to get the > > status of > > *all* the plugins summarised by people currently interested/working > > on them. Then we'll get some others to take a look and if something > > looks close to a release or particularly neglected we can deal with it. > > > > While we do all now, I think we can do a small group each month, > > completing them all by the end of the next board report. So here I > > assign some for end Jan, some for end Feb, some for end Mar. > > Remember, this time we need to do them all. > > > > We can try this inline, but maybe next time we need to find a better > way. > > > > Anyone have additional thoughts on this? > > > > To be completed by Jan, April, July, Oct clean assembly > > * Cleaned up several issues. Prep release next month. New > > functionality and significant bugfixes. X outstanding issues ear ejb > > jar plugin rar war compiler deploy > > * Just released. 1 outstanding minor issue install > > * Just released. No outstanding issues surefire > > * Just release. X outstanding issues resources source > > > > To be completed by Feb, May, Aug, Nov ant antrun > > * Recently released. X outstanding issues. > > antlr > > release > > repository > > help > > * Preparing release. 2 new feature requests in JIRA for next release. > > idea > > eclipse > > verifier > > > > To be completed by Mar, Jun, Sep, Dec checkstyle clover javadoc pmd > > * Release in progress. No outstanding issues. > > project-info-reports > > site > > * Significant new work. Nearing 2.0 release. X outstanding issues > > > > > > Thanks! > > - Brett > > > > > > - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEAR-17) Jar files packed in the EAR file should also be added to application.xml or manifest.mf
[ http://jira.codehaus.org/browse/MEAR-17?page=comments#action_56906 ] Kristoffer Peterhäesel commented on MEAR-17: After having read a bit more on my homework I should revise my suggestion to say that the manifest.mf files to add class-path information to should be the modules bundled in the ear. That of course makes it a bit more complicated to implement since it requires the module to reopen a jar file and modify (or create) the file in them before packaging them in the ear. Simply adding an option to write all included jars (that are not ejb modules) into the application.xml is by far an easier method of doing this. > Jar files packed in the EAR file should also be added to application.xml or > manifest.mf > --- > > Key: MEAR-17 > URL: http://jira.codehaus.org/browse/MEAR-17 > Project: Maven 2.x Ear Plugin > Type: Improvement > Reporter: Kristoffer Peterhäesel > > > While attempting to package an EAR for deployment on JBoss I have come across > a (for me) major issue with the way this module works. > The issue is that there are a lot dependency jars included by default. That > by itself isn't the problem. The problem is there is no way to include it in > the classpath without defining all the dependencies again in the pom.xml for > the EAR. > In an ideal world (for me) the jars would be an easy way to add the jars to > the classpath since I want to include all I need in the EAR to make it as > easy as possible to set up a depoyment environment. > There are really two options for how to do that. Either the jar files are > added to the generated Manifest.MF file or else there should be a simple > option to include all packed jar files to the application.xml. Both should > (AFAIK) work in any standard-compliant container. > The option of putting all the jar files in APP-INF/lib only works on Weblogic. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-2005) ArtifactCollector fails without looking into other repositories
[ http://jira.codehaus.org/browse/MNG-2005?page=all ]
Jerome Lacoste closed MNG-2005:
---
Resolution: Cannot Reproduce
I have been unable to reproduce this issue to day. Strange strange strange.
Will reopen if I re-encounter the issue.
> ArtifactCollector fails without looking into other repositories
> ---
>
> Key: MNG-2005
> URL: http://jira.codehaus.org/browse/MNG-2005
> Project: Maven 2
> Type: Bug
> Components: Artifacts and Repositories
> Versions: 2.0.2
> Reporter: Jerome Lacoste
> Priority: Critical
>
>
> My pom references 2 pluginRepositories (the snapshots codehaus one and the
> corporate one).
> The keytool-maven-plugin is deployed as 0.3-SNAPSHOT on the snapshots
> repository and I've built a newer version (0.4-SNAPSHOT)
> deployed in my internal repository, but it's not picked up.
> It looks like it found the plugin on snapshots, but not with the
> requested version and failed instead of looking further.
> Sounds like an issue in the DefaultArtifactCollector. Will try to investigate
> further...
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed to resolve artifact.
> Couldn't find a version in [0.3-SNAPSHOT] to match range [0.3,)
> org.codehaus.mojo:keytool-maven-plugin:jar:null
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> snapshots (http://snapshots.maven.codehaus.org/maven2/),
> embedded (file://${basedir}/tmp/m2repos),
> myrepo (http://myrepository/)
> [INFO]
>
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Couldn't find a
> version in [0.3-SNAPSHOT] to match range [0.3,)
> org.codehaus.mojo:keytool-maven-plugin:jar:null
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> snapshots (http://snapshots.maven.codehaus.org/maven2/),
> embedded (file://${basedir}/tmp/m2repos),
> myrepo (http://myrepository/)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:548)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> 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:585)
> 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:
> org.apache.maven.artifact.versioning.OverConstrainedVersionException:
> Couldn't find a version in [0.3-SNAPSHOT] to match range [0.3,)
> org.codehaus.mojo:keytool-maven-plugin:jar:null
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> snapshots (http://snapshots.maven.codehaus.org/maven2/),
> embedded (file://${basedir}/tmp/m2repos),
> myrepo (http://myrepository/)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:266)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:67)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:223)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:211)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:182)
> at
> org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsC
Re: [PROPOSAL] Integration testing proposal for Maven 2.0.x
If the POM is changing, that would then increment the pom model version, right? To 4.0.1? On 1/25/06, Vincent Massol <[EMAIL PROTECTED]> wrote: > > > > > -Original Message- > > From: Grzegorz Slowikowski [mailto:[EMAIL PROTECTED] > > Sent: mardi 24 janvier 2006 11:12 > > To: Maven Developers List > > Subject: Re: [PROPOSAL] Integration testing proposal for Maven 2.0.x > > > > > > - Original Message - > > From: "Vincent Massol" <[EMAIL PROTECTED]> > > To: "'Maven Developers List'" > > Sent: Monday, January 23, 2006 5:02 PM > > Subject: [PROPOSAL] Integration testing proposal for Maven 2.0.x > > > > > > > Hi, > > > > > ... > > > * We create a new surefire:test-integration MOJO bound to the > > > integration-test lifecycle > > > > > You meant "integration-test PHASE"? > > Yes. I actually meant "integration-test lifecycle phase" ;-) > > > And in what phase will integration tests be compiled? Now we compile > them > > (with our own plugin) in test-compile, but I think it is to early (if > you > > want only > > invoke "mvn package", you don't need it compilation). > > I think it can be done in 2 implementation steps. My first implementation > idea was to do it in test-compile and possibly add the new > integration-test-compile phase later on, with resources phase, etc too. > > > Another "problem" with it compilation is that all our testing artifacts > > needed by > > integration tests, and not by unit tests have scope "test". There is not > > "it" scope. > > So they all (there are really many artifacts needed by cactus) > > Come on, not that many jars! :-) > > > are included in classpath for unit tests. Are we going to do something > to > > avoid this, or is it ok? > > I agree with you. We'd need an it scope. > > I've created the following JIRA issues: > http://jira.codehaus.org/browse/MSUREFIRE-50 > http://jira.codehaus.org/browse/MNG-2009 > http://jira.codehaus.org/browse/MNG-2010 > http://jira.codehaus.org/browse/MNG-2011 > > Thanks > -Vincent > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
[jira] Created: (MANTRUN-39) When maven-antrun-plugin artifact id is defined twice in a pom, only second one is executed.
When maven-antrun-plugin artifact id is defined twice in a pom, only second one is executed. Key: MANTRUN-39 URL: http://jira.codehaus.org/browse/MANTRUN-39 Project: Maven 2.x Antrun Plugin Type: Wish Versions: 1.1 Environment: Windows XP Reporter: Stu Huettier Priority: Minor Could Maven give a verbose warning that the maven-antrun-plugin artifact id is defined twice in a pom and that only second one is executed? While it is probably a user error to define such a thing twice in a pom (clearly, multiple executions ought to be created within a single maven-antrun-plugin definition) it would be helpful if Maven would give a warning, perhaps something along the lines of, "Please do not define multiple instances of the same artifact Id." instead of just skipping over the first and running the second. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-2012) build with custom repository location and settings file doesn't work anymore
[ http://jira.codehaus.org/browse/MNG-2012?page=all ] Jerome Lacoste updated MNG-2012: Attachment: m2.log > build with custom repository location and settings file doesn't work anymore > > > Key: MNG-2012 > URL: http://jira.codehaus.org/browse/MNG-2012 > Project: Maven 2 > Type: Bug > Components: Bootstrap & Build > Reporter: Jerome Lacoste > Priority: Minor > Attachments: m2.log > > > And related to the MNG-1667 breakage, > ./bootstrap.sh -s ~/.m2/settings-m2trunk.xml $* > with settings-m2trunk.xml pointing to a different repository doesn't work at > all anymore > Breaks very early during the build process. Will try to get a log. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-2012) build with custom repository location and settings file doesn't work anymore
build with custom repository location and settings file doesn't work anymore Key: MNG-2012 URL: http://jira.codehaus.org/browse/MNG-2012 Project: Maven 2 Type: Bug Components: Bootstrap & Build Reporter: Jerome Lacoste Priority: Minor And related to the MNG-1667 breakage, ./bootstrap.sh -s ~/.m2/settings-m2trunk.xml $* with settings-m2trunk.xml pointing to a different repository doesn't work at all anymore Breaks very early during the build process. Will try to get a log. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1667) M2_HOME is not used in the way described in README.txt and as such bootstrap build fails
[ http://jira.codehaus.org/browse/MNG-1667?page=comments#action_56890 ]
Jerome Lacoste commented on MNG-1667:
-
While I am at it, a workaround for those who have the issue is to define
M2_HOME like
something/maven-$version
that way this matches what the BootstrapInstaller class will define, and the it
tests will work.
> M2_HOME is not used in the way described in README.txt and as such bootstrap
> build fails
>
>
> Key: MNG-1667
> URL: http://jira.codehaus.org/browse/MNG-1667
> Project: Maven 2
> Type: Bug
> Components: Bootstrap & Build
> Environment: Win32 (XP SP2)
> Reporter: John Allen
>
>
> From README.txt
> Set the environment variable M2_HOME pointing to the dir where you want
> Maven2 installed.
> NOTE: presently, the directory {M2_HOME}/bin must be in your path:
> set PATH=%PATH%;%M2_HOME%\bin
> or
> export PATH=$PATH:$M2_HOME/bin
> MVN SNAPSHOT is actually installed into %M2_HOME$/../maven-2.0.1-SNAPSHOT
> and this is not the location on the PATH so integration tests fail.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1667) M2_HOME is not used in the way described in README.txt and as such bootstrap build fails
[ http://jira.codehaus.org/browse/MNG-1667?page=comments#action_56889 ]
Jerome Lacoste commented on MNG-1667:
-
Damn it. You keep breaking stuff. That's tiring.
OK let me know if this is a doc issue or a code issue and I may have a look. I
have no idea why things were broken.
> M2_HOME is not used in the way described in README.txt and as such bootstrap
> build fails
>
>
> Key: MNG-1667
> URL: http://jira.codehaus.org/browse/MNG-1667
> Project: Maven 2
> Type: Bug
> Components: Bootstrap & Build
> Environment: Win32 (XP SP2)
> Reporter: John Allen
>
>
> From README.txt
> Set the environment variable M2_HOME pointing to the dir where you want
> Maven2 installed.
> NOTE: presently, the directory {M2_HOME}/bin must be in your path:
> set PATH=%PATH%;%M2_HOME%\bin
> or
> export PATH=$PATH:$M2_HOME/bin
> MVN SNAPSHOT is actually installed into %M2_HOME$/../maven-2.0.1-SNAPSHOT
> and this is not the location on the PATH so integration tests fail.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (SCM-118) detect and repair svn problems by running svn cleanup
[ http://jira.codehaus.org/browse/SCM-118?page=all ] Emmanuel Venisse closed SCM-118: Assign To: Emmanuel Venisse Resolution: Fixed Fixed. > detect and repair svn problems by running svn cleanup > - > > Key: SCM-118 > URL: http://jira.codehaus.org/browse/SCM-118 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-svn > Versions: 1.0-beta-2 > Reporter: Emmanuel Venisse > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: mvn site using http://svn.apache.org/repos/asf/maven/plugins/trunk/ repository
Hi Dave, The skins are not released yet. Try to add the following in your site.xml: org.apache.maven.skins maven-site-skin 1.0-SNAPSHOT Cheers, Vincent 2006/1/25, Dave Maung <[EMAIL PROTECTED]>: > Hi Brett, > I installed /repos/asf/maven/skins/trunk on my machine but I still ended up > getting this. > This is what i did > 1. checkout http://svn.apache.org/repos/asf/maven/plugins/trunk/ plugins > 2. mvn install on plugins > 3. checkout http://svn.apache.org/repos/asf/maven/skins/trunk skins > 4 mvn install on skins > 6. checkout http://svn.apache.org/repos/asf/maven/site/trunk/ site > 7. mvn install on site > 8. mvn site on plugins and I got this > > I am using Maven version of 2.0.2. Do I have to set up anything. > > > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] The skin does not exist: Unable to determine the release version > > org.apache.maven.skins:maven-default-skin:jar:RELEASE > > > [INFO] > > [DEBUG] Trace > org.apache.maven.BuildFailureException: The skin does not exist: Unable to > determine the release version > > org.apache.maven.skins:maven-default-skin:jar:RELEASE > > >at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( > DefaultLifecycleExecutor.java:552) >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle > (DefaultLifecycleExecutor.java:472) >at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( > DefaultLifecycleExecutor.java:451) >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures > (DefaultLifecycleExecutor.java:303) >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( > DefaultLifecycleExecutor.java:270) >at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( > DefaultLifecycleExecutor.java:139) >at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) >at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) >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:324) >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: org.apache.maven.plugin.MojoFailureException: The skin does not > exist: Unable to determine the release version > > org.apache.maven.skins:maven-default-skin:jar:RELEASE > > >at org.apache.maven.plugins.site.SiteMojo.getSkinArtifactFile( > SiteMojo.java:1361) >at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:336) >at org.apache.maven.plugin.DefaultPluginManager.executeMojo( > DefaultPluginManager.java:415) >at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( > DefaultLifecycleExecutor.java:531) > > On 1/21/06, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > You need to checkout the skins (/repos/asf/maven/skins/trunk) and do mvn > > install. > > > > - Brett > > > > Dave Maung wrote: > > > Hi > > > I am trying to run mvn site to compile all plugin and I got the below > > error. > > > see my log file. I used repository of > > > http://svn.apache.org/repos/asf/maven/plugins/trunk/ > > > > > > > > > - > > 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]
[jira] Commented: (MNGECLIPSE-57) Unable to download the artifact from any repository
[ http://jira.codehaus.org/browse/MNGECLIPSE-57?page=comments#action_56883 ] Marcell Manfrin Barbacena commented on MNGECLIPSE-57: - I am also getting these strange msgs.I am usgin Eclipse 3.1 and newest mvn (2.0.1) The debug output is full of this msg: 25/01/06 8h19min53s BRST: [DEBUG] Found 0 components to load on start 25/01/06 8h19min53s BRST: [DEBUG] Building Maven user-level plugin registry from: '/home/kurumin/.m2/plugin-registry.xml' 25/01/06 8h19min53s BRST: [DEBUG] Trying repository lsd 25/01/06 8h19min54s BRST: [WARN] Unable to get resource from repository lsd (http://www.lsd.ufcg.edu.br/~marcell/maven/stable) 25/01/06 8h19min54s BRST: [DEBUG] Trying repository m2default 25/01/06 8h19min55s BRST: [WARN] Unable to get resource from repository m2default (http://www.ibiblio.org/maven2) 25/01/06 8h19min55s BRST: [DEBUG] Trying repository central 25/01/06 8h19min56s BRST: [WARN] Unable to get resource from repository central (http://repo1.maven.org/maven2) 25/01/06 8h19min56s BRST: Unable to download the artifact from any repository > Unable to download the artifact from any repository > --- > > Key: MNGECLIPSE-57 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-57 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Versions: 0.0.4 > Environment: Windows XPSP1, MyEclipse IDE 4.0, Eclipse 3.1.1 > Reporter: Leonardo Quijano Vincenzi > Assignee: Eugene Kuleshov > Attachments: pom.xml > > > It seems like I'm getting a lot of these (I just downloaded M2ECLIPSE 0.0.4, > but I don't know if the problems were there before) > 1/24/06 5:00:08 PM CST: Local repository folder "" does not exist > 1/24/06 5:00:11 PM CST: [WARN] Unable to get resource from repository central > (http://repo1.maven.org/maven2) > 1/24/06 5:00:11 PM CST: Unable to download the artifact from any repository > This is shown a lot of times (my guess is once for every folder in the > project) and it significantly slows down development. > Attached is my pom.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNGECLIPSE-56) Exception running M2 build
[ http://jira.codehaus.org/browse/MNGECLIPSE-56?page=comments#action_56881 ] Kees de Kooter commented on MNGECLIPSE-56: -- Dimitri, Eugene, - The problem happends on both jre 1.4 and jre 1.5 - The windows firewall is disabled, we have no trouble running the java debugger - We already had the poblem with version 0.0.3, we upgraded to 0.0.4 - Turning "Debug output" gives the same result in the eclipse log, the console only says "Launching M2" > Exception running M2 build > -- > > Key: MNGECLIPSE-56 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-56 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Components: Maven Launcher > Versions: 0.0.4, 0.0.3 > Environment: Eclipse 3.1.1 + WTP 1.0, JRE 1.5.0_06 > Reporter: Kees de Kooter > Assignee: Dmitri Maximovich > Priority: Blocker > Attachments: eclipse.log > > > When I try to run an m2 build an error pops up: "Could not find the main > class. Program will exit.". > The console shows the following: > java.lang.NoClassDefFoundError: and > Exception in thread "main" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (CONTINUUM-488) Continuum will not use mirrors or alternate repositories
[ http://jira.codehaus.org/browse/CONTINUUM-488?page=comments#action_56880 ] Emmanuel Venisse commented on CONTINUUM-488: Hmm, very strange. So, you have copied settings.xml from $M2_HOME/conf/ to /opt/continuum-1.0.2/bin/linux/conf/settings.xml, right? I think it's a pb in settings loader in maven because Continuum use it, not the latest version(2.0.2), but 2.0. What is your maven version? Do you know/remember if something has been fix/modify since maven 2.0 about settings loading and/or proxy? I can't remember. > Continuum will not use mirrors or alternate repositories > > > Key: CONTINUUM-488 > URL: http://jira.codehaus.org/browse/CONTINUUM-488 > Project: Continuum > Type: Bug > Components: Core system > Versions: 1.0.1 > Reporter: David Hawkins > > > I can't get Continuum to use a repository other than repo1.maven.org. > Running mvn manually for my user works fine and fetches the dependencies from > the mirror specified in settings.xml. However, when I start continuum and it > attempts the build, it always tries to get dependencies from repo1.maven.org. > I have tried specifying a and also specified my server in a > profile/repositories/repository in settings.xml. Neither worked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2011) Add new integration-test scope for dependencies
Add new integration-test scope for dependencies --- Key: MNG-2011 URL: http://jira.codehaus.org/browse/MNG-2011 Project: Maven 2 Type: Task Components: Plugins and Lifecycle, integration tests Reporter: Vincent Massol This is required not to mix unit tests deps with it tests deps. See also http://www.nabble.com/-PROPOSAL-Integration-testing-proposal-for-Maven-2.0.x-t980095.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [PROPOSAL] Integration testing proposal for Maven 2.0.x
> -Original Message- > From: Grzegorz Slowikowski [mailto:[EMAIL PROTECTED] > Sent: mardi 24 janvier 2006 11:12 > To: Maven Developers List > Subject: Re: [PROPOSAL] Integration testing proposal for Maven 2.0.x > > > - Original Message - > From: "Vincent Massol" <[EMAIL PROTECTED]> > To: "'Maven Developers List'" > Sent: Monday, January 23, 2006 5:02 PM > Subject: [PROPOSAL] Integration testing proposal for Maven 2.0.x > > > > Hi, > > > ... > > * We create a new surefire:test-integration MOJO bound to the > > integration-test lifecycle > > > You meant "integration-test PHASE"? Yes. I actually meant "integration-test lifecycle phase" ;-) > And in what phase will integration tests be compiled? Now we compile them > (with our own plugin) in test-compile, but I think it is to early (if you > want only > invoke "mvn package", you don't need it compilation). I think it can be done in 2 implementation steps. My first implementation idea was to do it in test-compile and possibly add the new integration-test-compile phase later on, with resources phase, etc too. > Another "problem" with it compilation is that all our testing artifacts > needed by > integration tests, and not by unit tests have scope "test". There is not > "it" scope. > So they all (there are really many artifacts needed by cactus) Come on, not that many jars! :-) > are included in classpath for unit tests. Are we going to do something to > avoid this, or is it ok? I agree with you. We'd need an it scope. I've created the following JIRA issues: http://jira.codehaus.org/browse/MSUREFIRE-50 http://jira.codehaus.org/browse/MNG-2009 http://jira.codehaus.org/browse/MNG-2010 http://jira.codehaus.org/browse/MNG-2011 Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] [m1] plugin releases
+1 On 1/24/06, Lukas Theussl <[EMAIL PROTECTED]> wrote: > > Hi, > > I'd like to call for a vote on the following m1 plugin releases: > > [] maven-changelog-plugin-1.9 > [] maven-file-activity-plugin-1.6 > [] maven-developer-activity-plugin-1.6 > [] maven-simian-plugin-1.6 > > The changelog plugin is the only one with major bug fixes and new > features, all the others have zero issues open. > > For snapshot downloads and links to future web pages, see below. > > +1 from me and 72h to vote. > > Cheers, > -Lukas > > > > http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-changelog-plugin/ > http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-file-activity-plugin/ > http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-developer-activity-plugin/ > http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-simian-plugin/ > > > maven plugin:download > -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ > > -DgroupId=maven -DartifactId=maven-changelog-plugin -Dversion=1.9-SNAPSHOT > > maven plugin:download > -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ > > -DgroupId=maven -DartifactId=maven-file-activity-plugin > -Dversion=1.6-SNAPSHOT > > maven plugin:download > -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ > > -DgroupId=maven -DartifactId=maven-developer-activity-plugin > -Dversion=1.6-SNAPSHOT > > maven plugin:download > -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ > > -DgroupId=maven -DartifactId=maven-simian-plugin -Dversion=1.6-SNAPSHOT > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .::You're welcome ::. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-2010) Add new lifecycle phases for IT
Add new lifecycle phases for IT --- Key: MNG-2010 URL: http://jira.codehaus.org/browse/MNG-2010 Project: Maven 2 Type: Task Components: Plugins and Lifecycle, integration tests Reporter: Vincent Massol Namely: * generate-integration-test-sources * process-integration-test-sources * generate-integration-test-resources * process-integration-test-resources * integration-test-compile and possibly a: * integration-test-package -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [important] plugin statuses
On 1/25/06, Brett Porter <[EMAIL PROTECTED]> wrote: > Anyone want to update: > clean, ear, ejb, jar, plugin, rar, war, compiler, resources, source, > ant, antlr, release, repository, idea, eclipse, verifier, checkstyle, > clover, javadoc, projectinforeports below? I'm not sure I fully understant what you want. * ear: 1 minor change request ; no release planned * rar: stable, no issue (dunno if it's actually used though) I'll do war, ejb, idea tonight. Stéphane > > I'll pass back over this and fill in the gaps at the end of the month, > then this will become a monthly activity (as segregated below). > > Let me know if you have any thoughts on the effectiveness of this. > > - Brett > > Brett Porter wrote: > > Hi, > > > > Some time back there was a proposal about plugin maintainers, and I > > adapted that proposal for m2 a little. I don't think that our community > > fits assigning a person to do something, so I'd like to try this. > > > > Next Wednesday we have a board report due. I'd like to get the status of > > *all* the plugins summarised by people currently interested/working on > > them. Then we'll get some others to take a look and if something looks > > close to a release or particularly neglected we can deal with it. > > > > While we do all now, I think we can do a small group each month, > > completing them all by the end of the next board report. So here I > > assign some for end Jan, some for end Feb, some for end Mar. Remember, > > this time we need to do them all. > > > > We can try this inline, but maybe next time we need to find a better way. > > > > Anyone have additional thoughts on this? > > > > To be completed by Jan, April, July, Oct > > clean > > assembly > > * Cleaned up several issues. Prep release next month. New > > functionality and significant bugfixes. X outstanding issues > > ear > > ejb > > jar > > plugin > > rar > > war > > compiler > > deploy > > * Just released. 1 outstanding minor issue > > install > > * Just released. No outstanding issues > > surefire > > * Just release. X outstanding issues > > resources > > source > > > > To be completed by Feb, May, Aug, Nov > > ant > > antrun > > * Recently released. X outstanding issues. > > antlr > > release > > repository > > help > > * Preparing release. 2 new feature requests in JIRA for next release. > > idea > > eclipse > > verifier > > > > To be completed by Mar, Jun, Sep, Dec > > checkstyle > > clover > > javadoc > > pmd > > * Release in progress. No outstanding issues. > > project-info-reports > > site > > * Significant new work. Nearing 2.0 release. X outstanding issues > > > > > > Thanks! > > - Brett > > > > - > > 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] > > -- .::You're welcome ::. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-2009) Add new element in the POM model
Add new element in the POM model - Key: MNG-2009 URL: http://jira.codehaus.org/browse/MNG-2009 Project: Maven 2 Type: Task Components: POM Reporter: Vincent Massol This is to support the new surefire:integration-test mojo (MSUREFIRE-50). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MSUREFIRE-50) Create new surefire:integration-test mojo for IT
Create new surefire:integration-test mojo for IT Key: MSUREFIRE-50 URL: http://jira.codehaus.org/browse/MSUREFIRE-50 Project: Maven 2.x Surefire Plugin Type: Task Versions: 2.1.1 Reporter: Vincent Massol See http://www.nabble.com/-PROPOSAL-Integration-testing-proposal-for-Maven-2.0.x-t980095.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [vote] [m1] demote plugins
> -Original Message- > From: Lukas Theussl [mailto:[EMAIL PROTECTED] > Sent: mardi 24 janvier 2006 23:18 > To: Maven Developers List > Subject: Re: [vote] [m1] demote plugins > > > > > OK. Just assign the issue to me, I'll do it. > > Thanks! I will open issues as soon as the vote is finalized. > > > Personally, +1. I am surprised to see the JBoss plugin there though. > > Any contact with the JBoss people? (Maybe someone there can maintain > > it) > > No idea. Maybe Vincent M has some contacts there? Sorry but I don't have any contact there. -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [PROPOSAL] Integration testing proposal for Maven 2.0.x
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: mercredi 25 janvier 2006 00:38 > To: Maven Developers List > Subject: Re: [PROPOSAL] Integration testing proposal for Maven 2.0.x > > +1 for src/it > > I've got to say I'm greatly hesitant to add new things to 2.0.3, but it > wouldn't be the first time. Be careful :) > > How sure are we that this will be the final solution - are new test > types needed? We're not sure at all! :-) I would even say that it's pretty sure that over time the design and implementation solution will change. Which is why I think it's good for the 2.0.x series: we're not changing any existing user interface (only adding to them) and we're following the same spirit as the current strategy for unit tests. It's possible that we'll need to change that in Maven 2.1.x series but the best way to know is to implement what I suggest in 2.0.3 and get feedback. > Just trying to get a grip on where we are at with the topic as a whole. Thanks. -Vincent > Vincent Massol wrote: > > Hi, > > > > In order to progress on the topic of integration testing, I'm proposing > the > > following strategy that we can implement immediately: > > > > * We add one new element to the POM > > (similar to the current element but for > integration > > tests) > > > > * We make it default to src/test-integration. > > > > * We create a new surefire:test-integration MOJO bound to the > > integration-test lifecycle > > > > * We implement this for Maven 2.0.3. > > > > Let me know if that's ok and I'll try to implement it. > > > > Thanks > > -Vincent > > > > > > - > > 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]
