Re: org.codehaus.mojo's pom root version 5 at remote repo is not the same file in SVN
should be the same but for modules. I don't think it matters as long as the rest of the elements are ok. Obviously we need to improve how Maven deals with this (another thing related to my earlier mail on POM inheritance). In future, this should be posted to [EMAIL PROTECTED], it's not really relevant here. Cheers, Brett dan tran wrote: > http://www.ibiblio.org/maven2/org/codehaus/mojo/mojo/5/ > > vs > > http://svn.codehaus.org/trunk/mojo/pom.xml?rev=1036&root=mojo&view=auto > > the one at central repo uses scpexe for deployment > > is it intended? > > -D > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
org.codehaus.mojo's pom root version 5 at remote repo is not the same file in SVN
http://www.ibiblio.org/maven2/org/codehaus/mojo/mojo/5/ vs http://svn.codehaus.org/trunk/mojo/pom.xml?rev=1036&root=mojo&view=auto the one at central repo uses scpexe for deployment is it intended? -D
Re: maven ear release 2.1 - web site not up to date
Vincent Massol wrote: > Ok, I didn't know we were following that rule... > > If we want to enforce this then we could have a config property in the site > plugin to only deploy sites if the version is not snapshot and we should > activate this feature for the maven plugins. > We can put this in the dev process. I don't think we need to enforce these things, really. > How do you want to solve the current issue about location of sites? In > version 2.0 of the parents, the location is the wrong one. An easy solution > would be to have a symlink on minotaur to the correct location. WDYT? > I think for now we need to bump up the inheritence. It's just something to watch out for. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: clover default?
Vincent Massol wrote: > No. It was because there was a bug and I had implemented the correct > algorithm only for the clover:check goal. I have fixed that yesterday or > today (can't remember). > Yep, I hadn't caught the commit there yet. It's working now. -Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Releasing Clover plugin 2.0
+1 Brett Porter wrote: > I'd like to see the other thread on the clover default resolved first > and am withholding my vote until then. > > - Brett > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - checkout] Sat Dec 24 00:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051224.003000.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051224.003000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - SUCCESS - checkout] Sat Dec 24 00:00:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20051224.00.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051224.00.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (ARCHETYPE-20) create a site skin archetype
[ http://jira.codehaus.org/browse/ARCHETYPE-20?page=comments#action_54154 ] Jason van Zyl commented on ARCHETYPE-20: I'll stat with one for the geronimo site as I'm trying to incorporate some work by volunteers who have made some skins. > create a site skin archetype > > > Key: ARCHETYPE-20 > URL: http://jira.codehaus.org/browse/ARCHETYPE-20 > Project: Maven Archetype > Type: Task > Reporter: Brett Porter > Assignee: Jason van Zyl > > -- 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: maven ear release 2.1 - web site not up to date
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: vendredi 23 décembre 2005 22:28 > To: Maven Developers List > Subject: Re: maven ear release 2.1 - web site not up to date > > I have taken the practice of not publishing snapshot websites. The > reason generatePom is not up on the site is because it isn't in the > released plugin. I think we should revert to the *released* sites (or > better yet, release those plugins - didn't John have votes up for them?) Ok, I didn't know we were following that rule... If we want to enforce this then we could have a config property in the site plugin to only deploy sites if the version is not snapshot and we should activate this feature for the maven plugins. > Changing the parent doesn't hurt, but I don't recommend it. It upgrades > dependencies to 2.0.1 and if any of those apis are used it will cause > issues running under 2.0 (if this is required, you can add a > prerequisites tag). How do you want to solve the current issue about location of sites? In version 2.0 of the parents, the location is the wrong one. An easy solution would be to have a symlink on minotaur to the correct location. WDYT? [snip] -Vincent > Vincent Massol wrote: > > > >> -Original Message- > >> From: Martin van den Bemt [mailto:[EMAIL PROTECTED] > >> Sent: vendredi 23 décembre 2005 21:11 > >> To: Maven Developers List > >> Subject: Re: maven ear release 2.1 - web site not up to date > >> > >> It prevents running the plugin on maven 2.0 (for the clover plugin I > >> needed to install 2.0.1 when you changed that) > >> > > > > Are you sure? > > > > I think it's the fact that the Clover plugin requires Maven 2.0.1 that > was > > the cause rather than using a 2.0.1 parent version. > > > > -Vincent > > > > > >> Vincent Massol wrote: > >> > -Original Message- > From: Arik Kfir [mailto:[EMAIL PROTECTED] > Sent: vendredi 23 décembre 2005 20:12 > To: Maven Developers List > Subject: Re: maven ear release 2.1 - web site not up to date > > The same is with the deploy/install sites (the 'generatePom' > arguments > are not there, for instance). They were last published in october... > > >> - > >> 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]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Fri Dec 23 22:45:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051223.224500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051223.224500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: clover default?
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: vendredi 23 décembre 2005 22:23 > To: Maven Developers List > Subject: Re: clover default? > > Without the threading settings? did you change something? The defaults are: - flushPolicy = threaded - flushInterval = 500 AFAIK they do work fine. I've just tried them again on my laptop and they worked. > I had been getting 0 results running clover:clover. This is because it > terminates immediately after the tests complete, before flushing the db. No. It was because there was a bug and I had implemented the correct algorithm only for the clover:check goal. I have fixed that yesterday or today (can't remember). > When run under site it works, because other things happen after clover > giving the jvm long enough to pick up the thread and flush the db. Try it. Everything should work fine. Thanks -Vincent > Vincent Massol wrote: > > Hi Brett, > > > > > >> -Original Message- > >> From: Brett Porter [mailto:[EMAIL PROTECTED] > >> Sent: vendredi 23 décembre 2005 04:00 > >> To: Maven Developers List > >> Subject: clover default? > >> > >> Hi, > >> > >> I'm wondering what the default for clover should be: > >> - everything as now, but set forkmode once when running the tests (this > >> is how the cobertura plugin works - I have a patch for this if agreed) > >> - set the thread interval settings by default so that forking is not > >> required > >> > >> Thoughts? > >> > > > > The current version of the clover plugin works without requiring to fork > the > > tests so I believe this is the best solution. I'm currently fixing an > issue > > in the clover:report goal WRT this but this is working fine. > > > > 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]
[maven2 build trunk - SUCCESS - update] Fri Dec 23 22:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20051223.223000.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051223.223000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Fri Dec 23 22:15:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051223.221500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051223.221500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MSITE-59) "mvn site" fails when no site.xml
[ http://jira.codehaus.org/browse/MSITE-59?page=all ]
Brett Porter closed MSITE-59:
-
Assign To: Brett Porter (was: Jason van Zyl)
Resolution: Fixed
this is a bug in SVN, not a released version. I've got it fixed locally.
> "mvn site" fails when no site.xml
> -
>
> Key: MSITE-59
> URL: http://jira.codehaus.org/browse/MSITE-59
> Project: Maven 2.x Site Plugin
> Type: Bug
> Environment: Maven 2.1-SNAPSHOT updated from 2005-12-23, ~17:00GMT+1
> Reporter: Vincent Massol
> Assignee: Brett Porter
>
>
> Here's an example:
> C:\dev\maven\trunks\plugins\maven-clover-plugin\src\it\maven-clover-plugin-sample-mulitproject>mvn
> site
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Maven Clover Plugin Multiproject Sample
> [INFO] Maven Clover Plugin Multiproject Sample - Module 1
> [INFO] Maven Clover Plugin Multiproject Sample - Module 2
> [INFO]
>
> [INFO] Building Maven Clover Plugin Multiproject Sample
> [INFO]task-segment: [site]
> [INFO]
>
> [INFO] Preparing clover:clover
> [INFO] [clover:instrument]
> [INFO] Setting property: classpath.resource.loader.class =>
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO] **
> [INFO] Starting Jakarta Velocity v1.4
> [INFO] RuntimeInstance initializing.
> [INFO] Default Properties File:
> org\apache\velocity\runtime\defaults\velocity.properties
> [INFO] Default ResourceManager initializing. (class
> org.apache.velocity.runtime.resource.ResourceManagerImpl)
> [INFO] Resource Loader Instantiated:
> org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
> [INFO] ClasspathResourceLoader : initialization starting.
> [INFO] ClasspathResourceLoader : initialization complete.
> [INFO] ResourceCache : initialized. (class
> org.apache.velocity.runtime.resource.ResourceCacheImpl)
> [INFO] Default ResourceManager initialization complete.
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
> [INFO] Created: 20 parsers.
> [INFO] Velocimacro : initialization starting.
> [INFO] Velocimacro : adding VMs from VM library template :
> VM_global_library.vm
> [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in
> any resource loader.
> [INFO] Velocimacro : error using VM library template VM_global_library.vm :
> org.apache.velocity.exception.ResourceNotFoundExcepti
> on: Unable to find resource 'VM_global_library.vm'
> [INFO] Velocimacro : VM library template macro registration complete.
> [INFO] Velocimacro : allowInline = true : VMs can be defined inline in
> templates
> [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may
> NOT replace previous VM definitions
> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
> global in scope if allowed.
> [INFO] Velocimacro : initialization complete.
> [INFO] Velocity successfully started.
> [INFO] [site:site]
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error parsing site descriptor
> Embedded error: expected START_TAG or END_TAG not TEXT (position: TEXT seen
> ..."NO_PROJECT_URL_SET"/>\r\n\r\n${par
> entProject}\r\n [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 3 seconds
> [INFO] Finished at: Fri Dec 23 17:43:27 CET 2005
> [INFO] Final Memory: 6M/10M
> [INFO]
>
> C:\dev\maven\trunks\plugins\maven-clover-plugin\src\it\maven-clover-plugin-sample-mulitproject>mvn
> site -e
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Maven Clover Plugin Multiproject Sample
> [INFO] Maven Clover Plugin Multiproject Sample - Module 1
> [INFO] Maven Clover Plugin Multiproject Sample - Module 2
> [INFO]
>
[jira] Commented: (MNG-897) allows use of Ant build files
[ http://jira.codehaus.org/browse/MNG-897?page=comments#action_54152 ] Brett Porter commented on MNG-897: -- Should this be closed John? > allows use of Ant build files > - > > Key: MNG-897 > URL: http://jira.codehaus.org/browse/MNG-897 > Project: Maven 2 > Type: Improvement > Components: Plugin Creation Tools > Versions: 2.0-alpha-3 > Reporter: Chris Berry > Assignee: John Casey > Attachments: antfile.zip > > Original Estimate: 8 hours >Time Spent: 8 hours > Remaining: 1 hour > > Per John Casey, This is logged to that it stays on the radar. > Please consider incorporating my antfile plugin. > I have included the following in the ZIP > maven-antrun-plugin --> the basic antrun w/ a few small mods > maven-antfile-plugin > maven-axisant-plugin --> an example plugin using the antfile plugin > axis-master --> a "grouping" plugin for axis example > my-app --> an example app using the axisant plugin. > Cheers, > -- Chris -- 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: maven ear release 2.1 - web site not up to date
I have taken the practice of not publishing snapshot websites. The reason generatePom is not up on the site is because it isn't in the released plugin. I think we should revert to the *released* sites (or better yet, release those plugins - didn't John have votes up for them?) Changing the parent doesn't hurt, but I don't recommend it. It upgrades dependencies to 2.0.1 and if any of those apis are used it will cause issues running under 2.0 (if this is required, you can add a prerequisites tag). If anyone cares about how to actually solve this problem of inheriting deps vs metadata, please see the "POM Problems and Inheritence" mail I sent on 30 Nov. I didn't get a lot of feedback, though I have discussed it with some other developers just prior to ApacheCon but didn't come to any conclusions to post. I'll try and pick it up again in the new year. - Brett Vincent Massol wrote: > >> -Original Message- >> From: Martin van den Bemt [mailto:[EMAIL PROTECTED] >> Sent: vendredi 23 décembre 2005 21:11 >> To: Maven Developers List >> Subject: Re: maven ear release 2.1 - web site not up to date >> >> It prevents running the plugin on maven 2.0 (for the clover plugin I >> needed to install 2.0.1 when you changed that) >> > > Are you sure? > > I think it's the fact that the Clover plugin requires Maven 2.0.1 that was > the cause rather than using a 2.0.1 parent version. > > -Vincent > > >> Vincent Massol wrote: >> -Original Message- From: Arik Kfir [mailto:[EMAIL PROTECTED] Sent: vendredi 23 décembre 2005 20:12 To: Maven Developers List Subject: Re: maven ear release 2.1 - web site not up to date The same is with the deploy/install sites (the 'generatePom' arguments are not there, for instance). They were last published in october... >> - >> 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]
Re: [VOTE] Releasing Clover plugin 2.0
I'd like to see the other thread on the clover default resolved first and am withholding my vote until then. - Brett Vincent Massol wrote: > Hi, > > I've just fixed an issue with the clover plugin when used in a multimodule > project. I think we're ready to release version 2.0. There are some issues > in JIRA but they're unconfirmed or minor and I think users have already > waited long enough for the plugin. Most are using version alpha1 which was > very buggy and non-working. > > Please cast your votes. > > Here's my +1 > > 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]
Re: clover default?
Without the threading settings? did you change something? I had been getting 0 results running clover:clover. This is because it terminates immediately after the tests complete, before flushing the db. When run under site it works, because other things happen after clover giving the jvm long enough to pick up the thread and flush the db. - Brett Vincent Massol wrote: > Hi Brett, > > >> -Original Message- >> From: Brett Porter [mailto:[EMAIL PROTECTED] >> Sent: vendredi 23 décembre 2005 04:00 >> To: Maven Developers List >> Subject: clover default? >> >> Hi, >> >> I'm wondering what the default for clover should be: >> - everything as now, but set forkmode once when running the tests (this >> is how the cobertura plugin works - I have a patch for this if agreed) >> - set the thread interval settings by default so that forking is not >> required >> >> Thoughts? >> > > The current version of the clover plugin works without requiring to fork the > tests so I believe this is the best solution. I'm currently fixing an issue > in the clover:report goal WRT this but this is working fine. > > 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]
Re: Commented: (MNG-1703) is not propagated to child POMs
Moderators: please pay more attention. This is a duped jira message that appears to be bouncing to us from [EMAIL PROTECTED] I've seen 2 or 3 of these modded through. I just ignore them. - Brett [EMAIL PROTECTED] wrote: > [ http://jira.codehaus.org/browse/MNG-1703?page=comments#action_54110 ] > > Edwin Punzalan commented on MNG-1703: > - > > Hmmm... that\'s odd. can you do a \"mvn help:effective-pom\" on the child > module and see which have been inherited? Mine definitely has the executions > inherited. > > >> is not propagated to child POMs >> -- >> >> Key: MNG-1703 >> URL: http://jira.codehaus.org/browse/MNG-1703 >> Project: Maven 2 >> Type: Bug >> > > >> Components: POM >> Versions: 2.0 >> Reporter: Yann Le Du >> Assignee: Edwin Punzalan >> Fix For: 2.0.3 >> > > >> section in isn\'t propagated to child POMs >> (as is). >> The workaround is to use with true >> Is this on purpose ? >> > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPA-36) associate Maven svn with JIRA projects
[ http://jira.codehaus.org/browse/MPA-36?page=comments#action_54151 ] Brett Porter commented on MPA-36: - since it's not associated with individual projects, then we'd just be adding: svn.root.6=http://svn.apache.org/repos/asf/maven viewcvs.url.6=http://svn.apache.org/viewcvs.cgi/maven I think this is fine. We can turn it off if there are any performance concerns. > associate Maven svn with JIRA projects > -- > > Key: MPA-36 > URL: http://jira.codehaus.org/browse/MPA-36 > Project: Maven Project Administration > Type: Task > Components: issue management > Reporter: Brett Porter > Assignee: Vincent Massol > Attachments: subversion-jira-plugin.properties > > > Let's do this so we can view related commits from JIRA. > First need some advice on how it needs to be done: can we assign > http://svn.apache.org/repos/asf/maven to all the Maven 1.x and Maven 2.x > projects, or is this really bad for performance? It would still give the > right results. > If it needs to be separated, these are the patterns: > MNG - maven/components (trunk and branches) and maven/site (if possible) > MAVEN - maven/maven-1.x/core (trunk and branches) > MPxxx - maven/maven-1.x/plugins/trunk/PLUGIN-NAME > Mxxx - maven/plugins/trunk/PLUGIN-NAME > WAGON, WAGONFTP, WAGONSSH, WAGONHTTP - maven/wagon (trunk and branches) > SCM - maven/scm (trunk and branches) > CONTINUUM - maven/continuum (trunk and branches) > MRM - maven/repository-manager (trunk and branches) > JXR - maven/jxr (trunk and branches) > ARCHETYPE - maven/archetype (trunk and branches) > DOXIA - maven/doxia (trunk and branches) > SUREFIRE - maven/surefire (trunk and branches) -- 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: (ARCHETYPE-20) create a site skin archetype
create a site skin archetype Key: ARCHETYPE-20 URL: http://jira.codehaus.org/browse/ARCHETYPE-20 Project: Maven Archetype Type: Task Reporter: Brett Porter Assigned to: Jason van Zyl -- 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: maven ear release 2.1 - web site not up to date
> -Original Message- > From: Martin van den Bemt [mailto:[EMAIL PROTECTED] > Sent: vendredi 23 décembre 2005 21:11 > To: Maven Developers List > Subject: Re: maven ear release 2.1 - web site not up to date > > It prevents running the plugin on maven 2.0 (for the clover plugin I > needed to install 2.0.1 when you changed that) Are you sure? I think it's the fact that the Clover plugin requires Maven 2.0.1 that was the cause rather than using a 2.0.1 parent version. -Vincent > Vincent Massol wrote: > > > >>-Original Message- > >>From: Arik Kfir [mailto:[EMAIL PROTECTED] > >>Sent: vendredi 23 décembre 2005 20:12 > >>To: Maven Developers List > >>Subject: Re: maven ear release 2.1 - web site not up to date > >> > >>The same is with the deploy/install sites (the 'generatePom' arguments > >>are not there, for instance). They were last published in october... > > > > - > 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]
[maven2 build trunk - SUCCESS - update] Fri Dec 23 20:00:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20051223.20.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051223.20.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven ear release 2.1 - web site not up to date
It prevents running the plugin on maven 2.0 (for the clover plugin I needed to install 2.0.1 when you changed that) Mvgr, Martin Vincent Massol wrote: -Original Message- From: Arik Kfir [mailto:[EMAIL PROTECTED] Sent: vendredi 23 décembre 2005 20:12 To: Maven Developers List Subject: Re: maven ear release 2.1 - web site not up to date The same is with the deploy/install sites (the 'generatePom' arguments are not there, for instance). They were last published in october... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Fri Dec 23 19:45:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051223.194500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051223.194500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEV-163) Groovy pom has invalid dependencies
[ http://jira.codehaus.org/browse/MEV-163?page=all ] Carlos Sanchez closed MEV-163: -- Assign To: Carlos Sanchez Resolution: Fixed Fixed as groovy:1.0-jsr-03 It'd be nice to notify groovy developers > Groovy pom has invalid dependencies > --- > > Key: MEV-163 > URL: http://jira.codehaus.org/browse/MEV-163 > Project: Maven Evangelism > Type: Bug > Reporter: Dain Sundstrom > Assignee: Carlos Sanchez > > > The groovy pom seems to be a blind conversion from the maven 1 project.xml > file, as there are no pom.xml files in the groovy cvs repository. There are > two classes of problems with the groovy pom, bad version numbers and missing > dependencies. The dependency list is excessive and I'd guess that most of > the dependencies are either optional or test only dependencies. > Error detail > --- > o classworlds 1.1-alpha-2-SNAPSHOT-NO-SYSTEM-EXIT does not exist in the repo > but 1.1-alpha-2 should work > o xpp3 version 1.1.3.4-RC8_min does not exist in the repo but 1.1.3.4-RC8 > should work > o tonic:jarjar:0.5:jar does not exist in the repo. I doubt this is a runtime > dependency. > o mockobjects artifactId and version are wrong. Should be: > >mockobjects >mockobjects-core >0.09 > > o cglib artifactId and version are wrong. Should be: > >cglib >cglib-nodep >2.1 > > Here is a diff that worked for me: > --- /Users/dain/groovy-1.0-jsr-03.pom 2005-10-31 18:27:36.0 -0800 > +++ /Users/dain/.m2/repository/groovy/groovy-1.0-jsr/03/groovy-1.0-jsr-03.pom > 2005-10-31 18:40:30.0 -0800 > @@ -404,7 +404,7 @@ > >classworlds >classworlds > - 1.1-alpha-2-SNAPSHOT-NO-SYSTEM-EXIT > + 1.1-alpha-2 > > >commons-cli > @@ -443,8 +443,8 @@ > > >cglib > - cglib > - nodep-2.1 > + cglib-nodep > + 2.1 > > >asm > @@ -478,8 +478,8 @@ > > >mockobjects > - mockobjects > - core-0.09 > + mockobjects-core > + 0.09 > > >openejb > @@ -544,13 +544,13 @@ > >xpp3 >xpp3 > - 1.1.3.4-RC8_min > + 1.1.3.4-RC8 > > - > + > > > > @@ -564,4 +564,4 @@ >scp://beaver.codehaus.org//home/projects/groovy/public_html > > > - > \ No newline at end of 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]
RE: maven ear release 2.1 - web site not up to date
> -Original Message- > From: Arik Kfir [mailto:[EMAIL PROTECTED] > Sent: vendredi 23 décembre 2005 20:12 > To: Maven Developers List > Subject: Re: maven ear release 2.1 - web site not up to date > > The same is with the deploy/install sites (the 'generatePom' arguments > are not there, for instance). They were last published in october... Done for deploy/install too. Several plugins are still using a parent version of 2.0. I think they should all be updated to 2.0.1 (at least this is required to deploy in the right location). However I don't know if this will cause any other side effect. Thanks -Vincent > On 12/23/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > > I've just redeployed the web site for the ear plugin. > > > > -Vincent > > > > > -Original Message- > > > From: Stephane Nicoll [mailto:[EMAIL PROTECTED] > > > Sent: vendredi 23 décembre 2005 17:37 > > > To: Maven Developers List > > > Subject: maven ear release 2.1 - web site not up to date > > > > > > Guys, > > > > > > Maven EAR plugin 2.1 has been released but the web site has not been > > > updated. 2.1 contains new features which are not documented on the web > > > site, > > > this is quite annoying. > > > > > > Who can fix this? > > > > > > Thanks, > > > Stéphane > > > > > > -- > > > .::You're welcome ::. > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Regards, > _ > Arik Kfir[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven ear release 2.1 - web site not up to date
better yet, we need to release install and deloy plugins, it has install-file and deploy-file features which are so useful and popular On 12/23/05, Arik Kfir <[EMAIL PROTECTED]> wrote: > > The same is with the deploy/install sites (the 'generatePom' arguments > are not there, for instance). They were last published in october... > > On 12/23/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > > I've just redeployed the web site for the ear plugin. > > > > -Vincent > > > > > -Original Message- > > > From: Stephane Nicoll [mailto:[EMAIL PROTECTED] > > > Sent: vendredi 23 décembre 2005 17:37 > > > To: Maven Developers List > > > Subject: maven ear release 2.1 - web site not up to date > > > > > > Guys, > > > > > > Maven EAR plugin 2.1 has been released but the web site has not been > > > updated. 2.1 contains new features which are not documented on the web > > > site, > > > this is quite annoying. > > > > > > Who can fix this? > > > > > > Thanks, > > > Stéphane > > > > > > -- > > > .::You're welcome ::. > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Regards, >_ >Arik Kfir[EMAIL PROTECTED] >
[jira] Closed: (MEV-2) Broken dependency for groovy
[ http://jira.codehaus.org/browse/MEV-2?page=all ] Carlos Sanchez closed MEV-2: Assign To: Carlos Sanchez Resolution: Fixed > Broken dependency for groovy > > > Key: MEV-2 > URL: http://jira.codehaus.org/browse/MEV-2 > Project: Maven Evangelism > Type: Task > Reporter: Mark Hobson > Assignee: Carlos Sanchez > > > Broken dependency for: > > http://www.ibiblio.org/maven2/groovy/groovy/1.0-beta-7/groovy-1.0-beta-7.pom > > mockobjects > mockobjects > core-0.09 > > Should be: > > mockobjects > mockobjects-core > 0.09 > -- 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: maven ear release 2.1 - web site not up to date
The same is with the deploy/install sites (the 'generatePom' arguments are not there, for instance). They were last published in october... On 12/23/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > I've just redeployed the web site for the ear plugin. > > -Vincent > > > -Original Message- > > From: Stephane Nicoll [mailto:[EMAIL PROTECTED] > > Sent: vendredi 23 décembre 2005 17:37 > > To: Maven Developers List > > Subject: maven ear release 2.1 - web site not up to date > > > > Guys, > > > > Maven EAR plugin 2.1 has been released but the web site has not been > > updated. 2.1 contains new features which are not documented on the web > > site, > > this is quite annoying. > > > > Who can fix this? > > > > Thanks, > > Stéphane > > > > -- > > .::You're welcome ::. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Regards, _ Arik Kfir[EMAIL PROTECTED]
[jira] Created: (SCM-123) scm plugin ignores -Dusername for CSV provider
scm plugin ignores -Dusername for CSV provider -- Key: SCM-123 URL: http://jira.codehaus.org/browse/SCM-123 Project: Maven SCM Type: Bug Components: maven-plugin Versions: 1.0-beta-2 Environment: xp, cvs Reporter: Dan Tran Fix For: 1.0-beta-3 mvn scm:validate -DconnectionUrl=scm:cvs:pserver:host:/cvs:module -X -Dusername=joe fails with [DEBUG] (f) basedir = C:\dev\maven\src\scm [DEBUG] (f) connectionUrl = scm:cvs:pserver:host:/cvs:module [DEBUG] (f) settings = [EMAIL PROTECTED] [DEBUG] (f) username = joe [DEBUG] -- end configuration -- [INFO] [scm:validate] [ERROR] Error scm url connection (connectionUrl) validation failed : [ERROR] The userhost part must be on the form: @. is it intended? Found this problem when looking at MNG-1783 -- 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
[maven2 build branches/maven-2.0.x - SUCCESS - update] Fri Dec 23 17:45:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051223.174500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051223.174500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Releasing Clover plugin 2.0
Vincent Massol wrote: Hi, I've just fixed an issue with the clover plugin when used in a multimodule project. I think we're ready to release version 2.0. There are some issues in JIRA but they're unconfirmed or minor and I think users have already waited long enough for the plugin. Most are using version alpha1 which was very buggy and non-working. Please cast your votes. Here's my +1 +1 Thanks -Vincent - 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 Simplex sigillum veri. (Simplicity is the seal of truth.) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Releasing Clover plugin 2.0
+1.. (non-binding) Too bad I couldn't figure out the report stuff :( We'll leave that for the next release.. Mvgr, Martin Vincent Massol wrote: Hi, I've just fixed an issue with the clover plugin when used in a multimodule project. I think we're ready to release version 2.0. There are some issues in JIRA but they're unconfirmed or minor and I think users have already waited long enough for the plugin. Most are using version alpha1 which was very buggy and non-working. Please cast your votes. Here's my +1 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]
Re: [VOTE] Releasing Clover plugin 2.0
+1 On 12/23/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > > Hi, > > I've just fixed an issue with the clover plugin when used in a multimodule > project. I think we're ready to release version 2.0. There are some issues > in JIRA but they're unconfirmed or minor and I think users have already > waited long enough for the plugin. Most are using version alpha1 which was > very buggy and non-working. > > Please cast your votes. > > Here's my +1 > > Thanks > -Vincent > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .::You're welcome ::.
[maven2 build trunk - SUCCESS - update] Fri Dec 23 17:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20051223.173000.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051223.173000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Releasing Clover plugin 2.0
Hi, I've just fixed an issue with the clover plugin when used in a multimodule project. I think we're ready to release version 2.0. There are some issues in JIRA but they're unconfirmed or minor and I think users have already waited long enough for the plugin. Most are using version alpha1 which was very buggy and non-working. Please cast your votes. Here's my +1 Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Fri Dec 23 17:15:01 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051223.171501.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051223.171501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MCLOVER-5) Clover fails on multi-module builds
[ http://jira.codehaus.org/browse/MCLOVER-5?page=all ] Vincent Massol closed MCLOVER-5: Resolution: Fixed Fixed. > Clover fails on multi-module builds > --- > > Key: MCLOVER-5 > URL: http://jira.codehaus.org/browse/MCLOVER-5 > Project: Maven 2.x Clover Plugin > Type: Bug > Versions: 2.0-alpha-1 > Reporter: mike perham > Assignee: Vincent Massol > Fix For: 2.0 > > > I added clover to my reports plugins in my top-level POM and then ran "mvn > site:site" at the top. As expected, it recurses into the child modules and > the first module's build works but the second fails with the following error: > [INFO] Error configuring: org.apache.maven.plugins:maven-clover-plugin. > Reason: ERROR: Cannot override read-only parameter: project in goal: > clover:instrument -- 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: (MEV-4) Misnamed pom for Postgresql
[ http://jira.codehaus.org/browse/MEV-4?page=all ] Carlos Sanchez closed MEV-4: Assign To: Carlos Sanchez Resolution: Fixed Fixed as 7.4.1-jdbc3 > Misnamed pom for Postgresql > --- > > Key: MEV-4 > URL: http://jira.codehaus.org/browse/MEV-4 > Project: Maven Evangelism > Type: Task > Reporter: Mark Hobson > Assignee: Carlos Sanchez > > > In http://www.ibiblio.org/maven2/postgresql/postgresql/7.4.1/ the pom is > named: > postgresql-7.4.1.pom > But should be called: > postgresql-7.4.1-jdbc3.pom > To match the jar. -- 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]
[maven2 build trunk - SUCCESS - update] Fri Dec 23 17:00:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20051223.17.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051223.17.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Fri Dec 23 17:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051223.17.txt
[jira] Commented: (MNG-1783) maven-release-plugin doesn't pass username to maven-scm-provider-cvs
[ http://jira.codehaus.org/browse/MNG-1783?page=comments#action_54137 ]
Dan Tran commented on MNG-1783:
---
mvn scm:validate -DconnectionUrl=scm:cvs:pserver:[EMAIL PROTECTED]:/cvs:module
-X
shows the url is valid. So the problem is in release plugin?
> maven-release-plugin doesn't pass username to maven-scm-provider-cvs
>
>
> Key: MNG-1783
> URL: http://jira.codehaus.org/browse/MNG-1783
> Project: Maven 2
> Type: Bug
> Versions: 2.0
> Reporter: Jochen Wiedmann
> Priority: Critical
> Fix For: 2.0.3
>
>
> The class CvsScmProvider refuses a CVS url without username. See, for
> example, line 253ff:
> int index = userhost.indexOf( "@" );
> if ( index == -1 )
> {
> result.messages.add( "The userhost part must be on the
> form: @." );
> return result;
> }
> On the other hand, the maven-release-plugin doesn't pass the full URL to the
> provider. In AbstractReleaseMojo, an instance of ScmHelper is used, see line
> 120:
>repository = getScmManager().makeScmRepository(
> scmHelper.getUrl() );
> But the ScmHelper's URL is a reformatted URL, with user, password, and so on
> removed. The effect is that any attempt to run
> mvn release:prepare
> with an URL like scm:cvs:pserver:[EMAIL PROTECTED]:/cvs:module is refused
> with an error message "The scm url is invalid."
> I can't tell which side is wrong and am thus unable to provide a patch.
--
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]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Fri Dec 23 16:45:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051223.164501.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051223.164501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEAR-3) ear includes and excludes don't handle comma separated tokens
[ http://jira.codehaus.org/browse/MEAR-3?page=all ] Stephane Nicoll closed MEAR-3: -- Resolution: Fixed This is fixed. Thanks. > ear includes and excludes don't handle comma separated tokens > - > > Key: MEAR-3 > URL: http://jira.codehaus.org/browse/MEAR-3 > Project: Maven 2.x Ear Plugin > Type: Bug > Versions: 2.1, 2.0 > Reporter: David Hawkins > Assignee: Stephane Nicoll > Fix For: 2.2 > Attachments: MNG-1696-maven-war-plugin.patch > > > The documentation for warSourceIncludes, warSourceExcludes, > dependantWarIncludes, and dependantWarExcludes all state something that they > support comma delimited tokens but it simply doesn't work when a comma is > specified. This patch makes all four parameters properly process comma > delimited values. -- 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: (MSITE-59) "mvn site" fails when no site.xml
[ http://jira.codehaus.org/browse/MSITE-59?page=comments#action_54134 ]
Vincent Massol commented on MSITE-59:
-
after some more investigation it seems the problem is not a missing site.xml.
Even with a site.xml the project is failing with the same error...
still investigating...
> "mvn site" fails when no site.xml
> -
>
> Key: MSITE-59
> URL: http://jira.codehaus.org/browse/MSITE-59
> Project: Maven 2.x Site Plugin
> Type: Bug
> Environment: Maven 2.1-SNAPSHOT updated from 2005-12-23, ~17:00GMT+1
> Reporter: Vincent Massol
> Assignee: Jason van Zyl
>
>
> Here's an example:
> C:\dev\maven\trunks\plugins\maven-clover-plugin\src\it\maven-clover-plugin-sample-mulitproject>mvn
> site
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Maven Clover Plugin Multiproject Sample
> [INFO] Maven Clover Plugin Multiproject Sample - Module 1
> [INFO] Maven Clover Plugin Multiproject Sample - Module 2
> [INFO]
>
> [INFO] Building Maven Clover Plugin Multiproject Sample
> [INFO]task-segment: [site]
> [INFO]
>
> [INFO] Preparing clover:clover
> [INFO] [clover:instrument]
> [INFO] Setting property: classpath.resource.loader.class =>
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO] **
> [INFO] Starting Jakarta Velocity v1.4
> [INFO] RuntimeInstance initializing.
> [INFO] Default Properties File:
> org\apache\velocity\runtime\defaults\velocity.properties
> [INFO] Default ResourceManager initializing. (class
> org.apache.velocity.runtime.resource.ResourceManagerImpl)
> [INFO] Resource Loader Instantiated:
> org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
> [INFO] ClasspathResourceLoader : initialization starting.
> [INFO] ClasspathResourceLoader : initialization complete.
> [INFO] ResourceCache : initialized. (class
> org.apache.velocity.runtime.resource.ResourceCacheImpl)
> [INFO] Default ResourceManager initialization complete.
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
> [INFO] Created: 20 parsers.
> [INFO] Velocimacro : initialization starting.
> [INFO] Velocimacro : adding VMs from VM library template :
> VM_global_library.vm
> [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in
> any resource loader.
> [INFO] Velocimacro : error using VM library template VM_global_library.vm :
> org.apache.velocity.exception.ResourceNotFoundExcepti
> on: Unable to find resource 'VM_global_library.vm'
> [INFO] Velocimacro : VM library template macro registration complete.
> [INFO] Velocimacro : allowInline = true : VMs can be defined inline in
> templates
> [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may
> NOT replace previous VM definitions
> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
> global in scope if allowed.
> [INFO] Velocimacro : initialization complete.
> [INFO] Velocity successfully started.
> [INFO] [site:site]
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error parsing site descriptor
> Embedded error: expected START_TAG or END_TAG not TEXT (position: TEXT seen
> ..."NO_PROJECT_URL_SET"/>\r\n\r\n${par
> entProject}\r\n [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 3 seconds
> [INFO] Finished at: Fri Dec 23 17:43:27 CET 2005
> [INFO] Final Memory: 6M/10M
> [INFO]
>
> C:\dev\maven\trunks\plugins\maven-clover-plugin\src\it\maven-clover-plugin-sample-mulitproject>mvn
> site -e
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Maven Clover Plugin Multiproject Sample
> [INFO] Maven Clover Plugin Multiproject Sample - Module 1
> [INFO] Maven Clover Plugin Multiproject Sample - Mod
[jira] Created: (MSITE-59) "mvn site" fails when no site.xml
"mvn site" fails when no site.xml
-
Key: MSITE-59
URL: http://jira.codehaus.org/browse/MSITE-59
Project: Maven 2.x Site Plugin
Type: Bug
Environment: Maven 2.1-SNAPSHOT updated from 2005-12-23, ~17:00GMT+1
Reporter: Vincent Massol
Assigned to: Jason van Zyl
Here's an example:
C:\dev\maven\trunks\plugins\maven-clover-plugin\src\it\maven-clover-plugin-sample-mulitproject>mvn
site
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Maven Clover Plugin Multiproject Sample
[INFO] Maven Clover Plugin Multiproject Sample - Module 1
[INFO] Maven Clover Plugin Multiproject Sample - Module 2
[INFO]
[INFO] Building Maven Clover Plugin Multiproject Sample
[INFO]task-segment: [site]
[INFO]
[INFO] Preparing clover:clover
[INFO] [clover:instrument]
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] **
[INFO] Starting Jakarta Velocity v1.4
[INFO] RuntimeInstance initializing.
[INFO] Default Properties File:
org\apache\velocity\runtime\defaults\velocity.properties
[INFO] Default ResourceManager initializing. (class
org.apache.velocity.runtime.resource.ResourceManagerImpl)
[INFO] Resource Loader Instantiated:
org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
[INFO] ClasspathResourceLoader : initialization starting.
[INFO] ClasspathResourceLoader : initialization complete.
[INFO] ResourceCache : initialized. (class
org.apache.velocity.runtime.resource.ResourceCacheImpl)
[INFO] Default ResourceManager initialization complete.
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
[INFO] Created: 20 parsers.
[INFO] Velocimacro : initialization starting.
[INFO] Velocimacro : adding VMs from VM library template : VM_global_library.vm
[ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any
resource loader.
[INFO] Velocimacro : error using VM library template VM_global_library.vm :
org.apache.velocity.exception.ResourceNotFoundExcepti
on: Unable to find resource 'VM_global_library.vm'
[INFO] Velocimacro : VM library template macro registration complete.
[INFO] Velocimacro : allowInline = true : VMs can be defined inline in templates
[INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may NOT
replace previous VM definitions
[INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
global in scope if allowed.
[INFO] Velocimacro : initialization complete.
[INFO] Velocity successfully started.
[INFO] [site:site]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error parsing site descriptor
Embedded error: expected START_TAG or END_TAG not TEXT (position: TEXT seen
..."NO_PROJECT_URL_SET"/>\r\n\r\n${par
entProject}\r\nmvn
site -e
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Maven Clover Plugin Multiproject Sample
[INFO] Maven Clover Plugin Multiproject Sample - Module 1
[INFO] Maven Clover Plugin Multiproject Sample - Module 2
[INFO]
[INFO] Building Maven Clover Plugin Multiproject Sample
[INFO]task-segment: [site]
[INFO]
[INFO] Preparing clover:clover
[INFO] [clover:instrument]
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] **
[INFO] Starting Jakarta Velocity v1.4
[INFO] RuntimeInstance initializing.
[INFO] Default Properties File:
org\apache\velocity\runtime\defaults\velocity.properties
[INFO] Default ResourceManager initializing. (class
org.apache.velocity.runtime.resource.ResourceManagerImpl)
[INFO] Resource Loader Instantiated:
org.codehaus.plex
[maven2 build trunk - SUCCESS - update] Fri Dec 23 16:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20051223.163000.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051223.163000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Fri Dec 23 16:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051223.163000.txt
RE: maven ear release 2.1 - web site not up to date
I've just redeployed the web site for the ear plugin. -Vincent > -Original Message- > From: Stephane Nicoll [mailto:[EMAIL PROTECTED] > Sent: vendredi 23 décembre 2005 17:37 > To: Maven Developers List > Subject: maven ear release 2.1 - web site not up to date > > Guys, > > Maven EAR plugin 2.1 has been released but the web site has not been > updated. 2.1 contains new features which are not documented on the web > site, > this is quite annoying. > > Who can fix this? > > Thanks, > Stéphane > > -- > .::You're welcome ::. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven ear release 2.1 - web site not up to date
Guys, Maven EAR plugin 2.1 has been released but the web site has not been updated. 2.1 contains new features which are not documented on the web site, this is quite annoying. Who can fix this? Thanks, Stéphane -- .::You're welcome ::.
[jira] Commented: (MEAR-3) ear includes and excludes don't handle comma separated tokens
[ http://jira.codehaus.org/browse/MEAR-3?page=comments#action_54133 ] Stephane Nicoll commented on MEAR-3: David, your patch has been applied in the WAR plugin, Thanks! > ear includes and excludes don't handle comma separated tokens > - > > Key: MEAR-3 > URL: http://jira.codehaus.org/browse/MEAR-3 > Project: Maven 2.x Ear Plugin > Type: Bug > Versions: 2.1, 2.0 > Reporter: David Hawkins > Assignee: Stephane Nicoll > Fix For: 2.2 > Attachments: MNG-1696-maven-war-plugin.patch > > > The documentation for warSourceIncludes, warSourceExcludes, > dependantWarIncludes, and dependantWarExcludes all state something that they > support comma delimited tokens but it simply doesn't work when a comma is > specified. This patch makes all four parameters properly process comma > delimited values. -- 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: (MWAR-6) dependentWarExcludes and dependentWarIncludes do not support comma-separated patterns
[ http://jira.codehaus.org/browse/MWAR-6?page=all ] Stephane Nicoll closed MWAR-6: -- Resolution: Duplicate Fix Version: 2.0 This is fixed using the patch in MEAR-3 which fixes all parameters. Thanks. > dependentWarExcludes and dependentWarIncludes do not support comma-separated > patterns > - > > Key: MWAR-6 > URL: http://jira.codehaus.org/browse/MWAR-6 > Project: Maven 2.x War Plugin > Type: Bug > Reporter: Eric Andresen > Assignee: Stephane Nicoll > Fix For: 2.0 > Attachments: maven-war-plugin-include-exclude-csv.diff > > > With the dependentWar feature added by MNG-1507, the > amd were defined as allowing comma-separated values. > This is however, not true. Attached is a small patch to make this behave as > expected. > The configuration being tested is: > > maven-war-plugin > > > **/WEB-INF/classes/**,**/lib/*.jar > > > -- 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: (MWAR-5) warSourceExcludes not working properly
[ http://jira.codehaus.org/browse/MWAR-5?page=all ]
Stephane Nicoll reopened MWAR-5:
> warSourceExcludes not working properly
> --
>
> Key: MWAR-5
> URL: http://jira.codehaus.org/browse/MWAR-5
> Project: Maven 2.x War Plugin
> Type: Bug
> Environment: Win2k, Java 1.4.2_04, m2 beta1
> Reporter: Fabrice BELLINGARD
> Assignee: Edwin Punzalan
> Fix For: 2.0
> Attachments: MNG-1038-maven-war-plugin.patch, MNG-1038-maven-war-plugin.patch
>
>
> Note: I posted a message on Maven users list
> (http://www.mail-archive.com/users%40maven.apache.org/msg24088.html), but I
> got no answer so I post this issue, which in turn may or not be a bug...
> (sorry if it's not)
> I experienced a strange behaviour with the 'warSourceExcludes' property. When
> I grab some Web projects from the CVS of my company, I usually get all the
> WEB-INF/lib Jars that the developers put in the CVS:
> - With Maven 1, I use the 'maven.war.src.excludes' property to exclude those
> Jars ('maven.war.src.excludes=**/lib/*.*'), and it works well: the Jars
> packaged in the War are only the ones defined in the pom.
> - With m2, I tried to use the 'warSourceExcludes' property, which seemed to
> me to be the equivalent property. However, when the War is generated, there
> is no jar in the WEB-INF/lib folder. This works as if the plugin is excluding
> files after having copied the needed dependencies in the WEB-INF/lib folder
> (whereas in the Maven 1 version, it was excluding them before).
> Looking at the code of the m2 plugin, the value of 'warSourceExcludes' is
> used in method #getExcludes which is actually called in #performPackaging
> method. If this property is to work the same way as in m1, its value should
> be used in #copyResources method, before copying the Jar dependencies in
> WEB-INF/lib.
> What do you guys think of that? Am I right or am I missing something?
--
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: (MWAR-11) Add war:exploded and war:inplace goals
[ http://jira.codehaus.org/browse/MWAR-11?page=all ] Stephane Nicoll closed MWAR-11: --- Resolution: Fixed Fix Version: 2.0 > Add war:exploded and war:inplace goals > -- > > Key: MWAR-11 > URL: http://jira.codehaus.org/browse/MWAR-11 > Project: Maven 2.x War Plugin > Type: Improvement > Reporter: Mark Hobson > Assignee: Allan Ramirez > Fix For: 2.0 > Attachments: MNG-1037.patch, MNG-1037_b.patch > > Original Estimate: 8 hours >Time Spent: 8 hours > Remaining: 0 minutes > > Need to add war:exploded and war:inplace goals to replace the depreciated > war:war mode config parameter. -- 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: (MWAR-5) warSourceExcludes not working properly
[ http://jira.codehaus.org/browse/MWAR-5?page=all ]
Stephane Nicoll closed MWAR-5:
--
Resolution: Fixed
Fix Version: 2.0
> warSourceExcludes not working properly
> --
>
> Key: MWAR-5
> URL: http://jira.codehaus.org/browse/MWAR-5
> Project: Maven 2.x War Plugin
> Type: Bug
> Environment: Win2k, Java 1.4.2_04, m2 beta1
> Reporter: Fabrice BELLINGARD
> Assignee: Edwin Punzalan
> Fix For: 2.0
> Attachments: MNG-1038-maven-war-plugin.patch, MNG-1038-maven-war-plugin.patch
>
>
> Note: I posted a message on Maven users list
> (http://www.mail-archive.com/users%40maven.apache.org/msg24088.html), but I
> got no answer so I post this issue, which in turn may or not be a bug...
> (sorry if it's not)
> I experienced a strange behaviour with the 'warSourceExcludes' property. When
> I grab some Web projects from the CVS of my company, I usually get all the
> WEB-INF/lib Jars that the developers put in the CVS:
> - With Maven 1, I use the 'maven.war.src.excludes' property to exclude those
> Jars ('maven.war.src.excludes=**/lib/*.*'), and it works well: the Jars
> packaged in the War are only the ones defined in the pom.
> - With m2, I tried to use the 'warSourceExcludes' property, which seemed to
> me to be the equivalent property. However, when the War is generated, there
> is no jar in the WEB-INF/lib folder. This works as if the plugin is excluding
> files after having copied the needed dependencies in the WEB-INF/lib folder
> (whereas in the Maven 1 version, it was excluding them before).
> Looking at the code of the m2 plugin, the value of 'warSourceExcludes' is
> used in method #getExcludes which is actually called in #performPackaging
> method. If this property is to work the same way as in m1, its value should
> be used in #copyResources method, before copying the Jar dependencies in
> WEB-INF/lib.
> What do you guys think of that? Am I right or am I missing something?
--
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: (MWAR-8) Merge contents of dependent wars into war being built
[ http://jira.codehaus.org/browse/MWAR-8?page=all ] Stephane Nicoll closed MWAR-8: -- Resolution: Fixed Fix Version: 2.0 > Merge contents of dependent wars into war being built > - > > Key: MWAR-8 > URL: http://jira.codehaus.org/browse/MWAR-8 > Project: Maven 2.x War Plugin > Type: New Feature > Reporter: David Hawkins > Assignee: Emmanuel Venisse > Fix For: 2.0 > Attachments: MNG-1507-maven-war-plugin.patch > > > We added functionality to the maven-war-plugin to copy the contents of > dependent wars into the war being built. It will never overwrite existing > files and has configurable includes and excludes which are applied to the > files being copied. > Also made a minor change in getExcludes to not add the default excludes from > FileUtils. The default excludes were already being added in the method > getWarFiles( File sourceDir ) by scanner.addDefaultExcludes(). > We are trying to integrate Maven into our environment and not having this > functionality was a show-stopper for us. We have applications that reuse > jsps, and .tag files from a generic war that need to be included in all of > our wars. We have also seen people request this functionality. > By default these changes will have no effect, unless you have wars specified > in your . > Here is an example configuration that uses the includes and excludes for the > dependent wars. > > org.apache.maven.plugins > maven-war-plugin > 2.0-beta-3-SNAPSHOT > > > **/*.properties > > > It will not overwrite existing files that are already in the war, the way to > get around this is to remove the files you want overwritten using the > standard excludes configuration. For example, the following configuration > would allow the overwriteme.jar to be overwritten by something in a dependent > war. > > WEB-INF/lib/overwriteme.jar > -- 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: (MWAR-11) Add war:exploded and war:inplace goals
[ http://jira.codehaus.org/browse/MWAR-11?page=all ] Stephane Nicoll reopened MWAR-11: - > Add war:exploded and war:inplace goals > -- > > Key: MWAR-11 > URL: http://jira.codehaus.org/browse/MWAR-11 > Project: Maven 2.x War Plugin > Type: Improvement > Reporter: Mark Hobson > Assignee: Allan Ramirez > Attachments: MNG-1037.patch, MNG-1037_b.patch > > Original Estimate: 8 hours >Time Spent: 8 hours > Remaining: 0 minutes > > Need to add war:exploded and war:inplace goals to replace the depreciated > war:war mode config parameter. -- 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: (MWAR-8) Merge contents of dependent wars into war being built
[ http://jira.codehaus.org/browse/MWAR-8?page=all ] Stephane Nicoll reopened MWAR-8: > Merge contents of dependent wars into war being built > - > > Key: MWAR-8 > URL: http://jira.codehaus.org/browse/MWAR-8 > Project: Maven 2.x War Plugin > Type: New Feature > Reporter: David Hawkins > Assignee: Emmanuel Venisse > Fix For: 2.0 > Attachments: MNG-1507-maven-war-plugin.patch > > > We added functionality to the maven-war-plugin to copy the contents of > dependent wars into the war being built. It will never overwrite existing > files and has configurable includes and excludes which are applied to the > files being copied. > Also made a minor change in getExcludes to not add the default excludes from > FileUtils. The default excludes were already being added in the method > getWarFiles( File sourceDir ) by scanner.addDefaultExcludes(). > We are trying to integrate Maven into our environment and not having this > functionality was a show-stopper for us. We have applications that reuse > jsps, and .tag files from a generic war that need to be included in all of > our wars. We have also seen people request this functionality. > By default these changes will have no effect, unless you have wars specified > in your . > Here is an example configuration that uses the includes and excludes for the > dependent wars. > > org.apache.maven.plugins > maven-war-plugin > 2.0-beta-3-SNAPSHOT > > > **/*.properties > > > It will not overwrite existing files that are already in the war, the way to > get around this is to remove the files you want overwritten using the > standard excludes configuration. For example, the following configuration > would allow the overwriteme.jar to be overwritten by something in a dependent > war. > > WEB-INF/lib/overwriteme.jar > -- 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]
[continuum build - FAILED - update] Fri Dec 23 16:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051223.16.txt
[jira] Closed: (MWAR-3) war:war launched from parent doesn't find module web.xml
[ http://jira.codehaus.org/browse/MWAR-3?page=all ]
Stephane Nicoll closed MWAR-3:
--
Resolution: Fixed
Fix Version: 2.0
> war:war launched from parent doesn't find module web.xml
>
>
> Key: MWAR-3
> URL: http://jira.codehaus.org/browse/MWAR-3
> Project: Maven 2.x War Plugin
> Type: Bug
> Reporter: Yann Le Du
> Assignee: Brett Porter
> Fix For: 2.0
>
>
> foo
> +-- pom.xml
> +-- foo-contact
> +-- pom.xml
> +-- contact
> +-- WebContent
> +-- WEB-INF
> +-- web.xml
> In foo-contact pom.xml :
>
> org.apache.maven.plugins
> maven-war-plugin
>
> contact/WebContent
>
>
> war:war launched from foo-contact is OK.
> war:war launched from foo produces :
> org.apache.maven.plugin.MojoExecutionException: Error assembling WAR
> at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:224)
> ...
> Caused by: org.codehaus.plexus.archiver.ArchiverException: Deployment
> descriptor:
> /devel/maven/src/RIC/trunk/ric-contact/target/contact/WEB-INF/web.xml does
> not exist.
> at
> org.codehaus.plexus.archiver.war.WarArchiver.setWebxml(WarArchiver.java:70)
> ...
> Adding contact/WebContent/WEB-INF/web.xml produces the same
> message.
> Adding ${basedir}/contact/WebContent/WEB-INF/web.xml solves
> the issue.
> I guess out two things here :
> * when you launch war:war from parent, webXml does not default to
> ${warSourceDirectory}/WEB-INF/web.xml
> * webXml isn't implicitly prefixed with ${basedir}/
> See also
> http://marc.theaimsgroup.com/?l=turbine-maven-user&m=111623705811553&w=2 for
> a previous report of this issue.
--
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: (MWAR-3) war:war launched from parent doesn't find module web.xml
[ http://jira.codehaus.org/browse/MWAR-3?page=all ]
Stephane Nicoll reopened MWAR-3:
> war:war launched from parent doesn't find module web.xml
>
>
> Key: MWAR-3
> URL: http://jira.codehaus.org/browse/MWAR-3
> Project: Maven 2.x War Plugin
> Type: Bug
> Reporter: Yann Le Du
> Assignee: Brett Porter
> Fix For: 2.0
>
>
> foo
> +-- pom.xml
> +-- foo-contact
> +-- pom.xml
> +-- contact
> +-- WebContent
> +-- WEB-INF
> +-- web.xml
> In foo-contact pom.xml :
>
> org.apache.maven.plugins
> maven-war-plugin
>
> contact/WebContent
>
>
> war:war launched from foo-contact is OK.
> war:war launched from foo produces :
> org.apache.maven.plugin.MojoExecutionException: Error assembling WAR
> at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:224)
> ...
> Caused by: org.codehaus.plexus.archiver.ArchiverException: Deployment
> descriptor:
> /devel/maven/src/RIC/trunk/ric-contact/target/contact/WEB-INF/web.xml does
> not exist.
> at
> org.codehaus.plexus.archiver.war.WarArchiver.setWebxml(WarArchiver.java:70)
> ...
> Adding contact/WebContent/WEB-INF/web.xml produces the same
> message.
> Adding ${basedir}/contact/WebContent/WEB-INF/web.xml solves
> the issue.
> I guess out two things here :
> * when you launch war:war from parent, webXml does not default to
> ${warSourceDirectory}/WEB-INF/web.xml
> * webXml isn't implicitly prefixed with ${basedir}/
> See also
> http://marc.theaimsgroup.com/?l=turbine-maven-user&m=111623705811553&w=2 for
> a previous report of this issue.
--
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: (MWAR-1) war:exploded removes content of .class files
[ http://jira.codehaus.org/browse/MWAR-1?page=all ]
Stephane Nicoll reopened MWAR-1:
> war:exploded removes content of .class files
>
>
> Key: MWAR-1
> URL: http://jira.codehaus.org/browse/MWAR-1
> Project: Maven 2.x War Plugin
> Type: Bug
> Environment: WIndowx XP
> Reporter: Victor Yushenko
> Assignee: Brett Porter
> Fix For: 2.0
> Attachments: MNG-1288-maven-war-plugin.patch
>
>
> To enable development in MyEclipse I have been configuring maven to build a
> folder with 'war' extention during the build. This then becomes an expanded
> folder that I can just copy (actually MyEclipse does it) to jboss for
> deployment.
> After the build my folder structure looks like this:
> --src
> |-main
> ...
> --target
> |---testweb.war
> |---css
> |---WEB-INF
>| classes
>| lib
>| jsp
> I also configure compiler to compile files directy into
> target/${project.build.finalName}.war/WEB-INF/classes (which would be a
> target/testweb.war/WEB-INF/classes in the example above). This worked great
> in maven 1.* (I can change any file, eclipse compiles it into the class
> folder and MyEclipse immidiately deployes it to the JBoss). It also seemed to
> work for few hours in maven 2 (I only starrted using it today). Now if I do:
> "mvn package" I get proper exploded war except that all files in the
> 'classes' folder have 0 size. It seems that compiler creates good class files
> (and copies resources there) and then war plug-in comes along and wipes
> content of these files (but not files themselfs):
> Here is a snipped from my pom.xml:
>
> testweb.war
>
> target/${project.build.finalName}.war/WEB-INF/classes
> target/war
>
>
> org.apache.maven.plugins
> maven-war-plugin
>
>
> target/${project.build.finalName}.war
>
>
>
>
> As an experimet I did following steps:
> mvn compile - this produced expected results, compiled classes in the
> WEB-INF/classes folder
> then I did:
> mvn war:exploded - this command copied files from webapp and removed content
> from files produced by the compiler, so that all *.class files now have 0
> bytes size...
> Interestingly enough it seemed to work for few hours and then just stoped. I
> have rebooted PC just to see and I still get the same result...
> my src\main\webapp\WEB-INF folder does not have classes folder, so I am not
> sure why war plug-in affects *.class files.
> P.S. I mistakenly created another issue for maven-war (which now I am
> guessing is only related to maven 1...). MPWAR-51
--
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: (MWAR-1) war:exploded removes content of .class files
[ http://jira.codehaus.org/browse/MWAR-1?page=all ]
Stephane Nicoll closed MWAR-1:
--
Resolution: Fixed
Fix Version: 2.0
> war:exploded removes content of .class files
>
>
> Key: MWAR-1
> URL: http://jira.codehaus.org/browse/MWAR-1
> Project: Maven 2.x War Plugin
> Type: Bug
> Environment: WIndowx XP
> Reporter: Victor Yushenko
> Assignee: Brett Porter
> Fix For: 2.0
> Attachments: MNG-1288-maven-war-plugin.patch
>
>
> To enable development in MyEclipse I have been configuring maven to build a
> folder with 'war' extention during the build. This then becomes an expanded
> folder that I can just copy (actually MyEclipse does it) to jboss for
> deployment.
> After the build my folder structure looks like this:
> --src
> |-main
> ...
> --target
> |---testweb.war
> |---css
> |---WEB-INF
>| classes
>| lib
>| jsp
> I also configure compiler to compile files directy into
> target/${project.build.finalName}.war/WEB-INF/classes (which would be a
> target/testweb.war/WEB-INF/classes in the example above). This worked great
> in maven 1.* (I can change any file, eclipse compiles it into the class
> folder and MyEclipse immidiately deployes it to the JBoss). It also seemed to
> work for few hours in maven 2 (I only starrted using it today). Now if I do:
> "mvn package" I get proper exploded war except that all files in the
> 'classes' folder have 0 size. It seems that compiler creates good class files
> (and copies resources there) and then war plug-in comes along and wipes
> content of these files (but not files themselfs):
> Here is a snipped from my pom.xml:
>
> testweb.war
>
> target/${project.build.finalName}.war/WEB-INF/classes
> target/war
>
>
> org.apache.maven.plugins
> maven-war-plugin
>
>
> target/${project.build.finalName}.war
>
>
>
>
> As an experimet I did following steps:
> mvn compile - this produced expected results, compiled classes in the
> WEB-INF/classes folder
> then I did:
> mvn war:exploded - this command copied files from webapp and removed content
> from files produced by the compiler, so that all *.class files now have 0
> bytes size...
> Interestingly enough it seemed to work for few hours and then just stoped. I
> have rebooted PC just to see and I still get the same result...
> my src\main\webapp\WEB-INF folder does not have classes folder, so I am not
> sure why war plug-in affects *.class files.
> P.S. I mistakenly created another issue for maven-war (which now I am
> guessing is only related to maven 1...). MPWAR-51
--
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-1783) maven-release-plugin doesn't pass username to maven-scm-provider-cvs
[ http://jira.codehaus.org/browse/MNG-1783?page=comments#action_54127 ]
Pascal Grange commented on MNG-1783:
If it is a simple fix, when do you think a new release fixing this bug will be
available ? I have to answer my boss.
Merry Christmas.
> maven-release-plugin doesn't pass username to maven-scm-provider-cvs
>
>
> Key: MNG-1783
> URL: http://jira.codehaus.org/browse/MNG-1783
> Project: Maven 2
> Type: Bug
> Versions: 2.0
> Reporter: Jochen Wiedmann
> Priority: Critical
> Fix For: 2.0.3
>
>
> The class CvsScmProvider refuses a CVS url without username. See, for
> example, line 253ff:
> int index = userhost.indexOf( "@" );
> if ( index == -1 )
> {
> result.messages.add( "The userhost part must be on the
> form: @." );
> return result;
> }
> On the other hand, the maven-release-plugin doesn't pass the full URL to the
> provider. In AbstractReleaseMojo, an instance of ScmHelper is used, see line
> 120:
>repository = getScmManager().makeScmRepository(
> scmHelper.getUrl() );
> But the ScmHelper's URL is a reformatted URL, with user, password, and so on
> removed. The effect is that any attempt to run
> mvn release:prepare
> with an URL like scm:cvs:pserver:[EMAIL PROTECTED]:/cvs:module is refused
> with an error message "The scm url is invalid."
> I can't tell which side is wrong and am thus unable to provide a patch.
--
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: (MANTRUN-28) maven.test.classpath doesn't contain test scope dependancies
[ http://jira.codehaus.org/browse/MANTRUN-28?page=all ] Gilles Scokart updated MANTRUN-28: -- Attachment: MANTRUN-28.patch > maven.test.classpath doesn't contain test scope dependancies > > > Key: MANTRUN-28 > URL: http://jira.codehaus.org/browse/MANTRUN-28 > Project: Maven 2.x Antrun Plugin > Type: Bug > Reporter: Brian Fox > Attachments: MANTRUN-28.patch, pom.xml > > > maven.test.classpath only has things in compile scope, not in test scope. -- 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: (MPA-36) associate Maven svn with JIRA projects
[ http://jira.codehaus.org/browse/MPA-36?page=all ] Vincent Massol updated MPA-36: -- Attachment: subversion-jira-plugin.properties > associate Maven svn with JIRA projects > -- > > Key: MPA-36 > URL: http://jira.codehaus.org/browse/MPA-36 > Project: Maven Project Administration > Type: Task > Components: issue management > Reporter: Brett Porter > Assignee: Vincent Massol > Attachments: subversion-jira-plugin.properties > > > Let's do this so we can view related commits from JIRA. > First need some advice on how it needs to be done: can we assign > http://svn.apache.org/repos/asf/maven to all the Maven 1.x and Maven 2.x > projects, or is this really bad for performance? It would still give the > right results. > If it needs to be separated, these are the patterns: > MNG - maven/components (trunk and branches) and maven/site (if possible) > MAVEN - maven/maven-1.x/core (trunk and branches) > MPxxx - maven/maven-1.x/plugins/trunk/PLUGIN-NAME > Mxxx - maven/plugins/trunk/PLUGIN-NAME > WAGON, WAGONFTP, WAGONSSH, WAGONHTTP - maven/wagon (trunk and branches) > SCM - maven/scm (trunk and branches) > CONTINUUM - maven/continuum (trunk and branches) > MRM - maven/repository-manager (trunk and branches) > JXR - maven/jxr (trunk and branches) > ARCHETYPE - maven/archetype (trunk and branches) > DOXIA - maven/doxia (trunk and branches) > SUREFIRE - maven/surefire (trunk and branches) -- 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-15) Output folders are not set correctly by 'Update Sources' action
[ http://jira.codehaus.org/browse/MNGECLIPSE-15?page=comments#action_54122 ] Eugene Kuleshov commented on MNGECLIPSE-15: --- It seems to me that Eclipse is actually rignt and you should have these properties files in a single place (perhaps common project for all subprojects), thoug I have to check some details on how Maven prepare classpath. What I meant about target build path for resources is that you can point output folder to the same folder where sources are. > Output folders are not set correctly by 'Update Sources' action > --- > > Key: MNGECLIPSE-15 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-15 > Project: Maven 2.x Plug-in for Eclipse > Type: Bug > Reporter: YOKOTA Takehiko > Assignee: Eugene Kuleshov > Attachments: patch.txt > > > Although source folders on build path are updated correctly by 'Update > Sources' action, > output folders are not updated at all. > For example, it is expected that output folder for 'src/test/java' and > 'src/test/resources' > is set to 'target/test-classes', but not set. -- 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: (MEV-220) spring-mock should list spring-web and spring-jdbc as optional
[ http://jira.codehaus.org/browse/MEV-220?page=all ] Carlos Sanchez closed MEV-220: -- Resolution: Fixed Set as optional in 1.2.5 and 1.2.6 Related docs for maven 2.1 http://docs.codehaus.org/display/MAVEN/Specification+Dependencies+Design > spring-mock should list spring-web and spring-jdbc as optional > -- > > Key: MEV-220 > URL: http://jira.codehaus.org/browse/MEV-220 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Matt Raible > Assignee: Carlos Sanchez > > > I know that spring-mock depends on spring-web and spring-jdbc to compile. > However, if I already have spring listed as a dependency, it seems logical > that I shouldn't need to exclude spring-web and spring-jdbc. > Rather than this: > > spring > springframework > 1.2.5 > > > spring-mock > springframework > 1.2.5 > test > > > spring-jdbc > springframework > > > spring-web > springframework > > > > I should be able to do this: > > spring > springframework > 1.2.5 > > > spring-mock > springframework > 1.2.5 > test > -- 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: (MEV-269) checkstyle 4.1 pom
[ http://jira.codehaus.org/browse/MEV-269?page=all ] Carlos Sanchez closed MEV-269: -- Assign To: Carlos Sanchez Resolution: Fixed It may take one day to reach ibiblio > checkstyle 4.1 pom > -- > > Key: MEV-269 > URL: http://jira.codehaus.org/browse/MEV-269 > Project: Maven Evangelism > Type: Task > Components: Invalid POM > Reporter: Brent Worden > Assignee: Carlos Sanchez > Attachments: checkstyle-4.1.pom > > > same as 4.0 except for version number. -- 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: (MANTRUN-35) mvn debug level not passed to ant
mvn debug level not passed to ant - Key: MANTRUN-35 URL: http://jira.codehaus.org/browse/MANTRUN-35 Project: Maven 2.x Antrun Plugin Type: Improvement Environment: Any Reporter: M. van der Plas Assigned to: Jason van Zyl Priority: Minor Ant task like have a property level which can be set to trigger activation based on the loglevel. Maven mvn has the commandline option to activate the debug log level. Currently it is not possible to set the ant task log level. The mvn log level should be passed to ant so it can be used in log level aware ant tasks. -- 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: (MEV-269) checkstyle 4.1 pom
[ http://jira.codehaus.org/browse/MEV-269?page=all ] Brent Worden updated MEV-269: - Attachment: checkstyle-4.1.pom > checkstyle 4.1 pom > -- > > Key: MEV-269 > URL: http://jira.codehaus.org/browse/MEV-269 > Project: Maven Evangelism > Type: Task > Components: Invalid POM > Reporter: Brent Worden > Attachments: checkstyle-4.1.pom > > > same as 4.0 except for version number. -- 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: (MEV-269) checkstyle 4.1 pom
checkstyle 4.1 pom -- Key: MEV-269 URL: http://jira.codehaus.org/browse/MEV-269 Project: Maven Evangelism Type: Task Components: Invalid POM Reporter: Brent Worden same as 4.0 except for version number. -- 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: clover default?
Hi Brett, > -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: vendredi 23 décembre 2005 04:00 > To: Maven Developers List > Subject: clover default? > > Hi, > > I'm wondering what the default for clover should be: > - everything as now, but set forkmode once when running the tests (this > is how the cobertura plugin works - I have a patch for this if agreed) > - set the thread interval settings by default so that forking is not > required > > Thoughts? The current version of the clover plugin works without requiring to fork the tests so I believe this is the best solution. I'm currently fixing an issue in the clover:report goal WRT this but this is working fine. Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNGECLIPSE-13) adding dependency to pom.xml changes its formating
[ http://jira.codehaus.org/browse/MNGECLIPSE-13?page=comments#action_54113 ] Michał Steiner commented on MNGECLIPSE-13: --- Adding dependency brokes also encoding ( UTF characters are changed to '?') and removes schema declaration from pom.xml. > adding dependency to pom.xml changes its formating > -- > > Key: MNGECLIPSE-13 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-13 > Project: Maven 2.x Plug-in for Eclipse > Type: Bug > Environment: win xp, eclipse 3.1, plugin 0.0.3 > Reporter: Michal Stochmialek > Assignee: Eugene Kuleshov > Priority: Minor > > > I use pom.xml as a human-readable file, so I insert empty lines between main > sections of pom etc. But after adding a depedency using maven plugin, those > blank lines have disappeared. > The similar thing happened to indentions. I usually use tabs for indenting, > but plugin changed whole file indenting to spaces. In result CVS diff shows > that whole file have been changed. > Maven plugin should modify only lines that contain new (just added) > dependency. -- 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: Commented: (MNG-1703) is not propagated to child POMs
[ http://jira.codehaus.org/browse/MNG-1703?page=comments#action_54110 ] Edwin Punzalan commented on MNG-1703: - Hmmm... that\'s odd. can you do a \"mvn help:effective-pom\" on the child module and see which have been inherited? Mine definitely has the executions inherited. > is not propagated to child POMs > -- > > Key: MNG-1703 > URL: http://jira.codehaus.org/browse/MNG-1703 > Project: Maven 2 > Type: Bug > Components: POM > Versions: 2.0 > Reporter: Yann Le Du > Assignee: Edwin Punzalan > Fix For: 2.0.3 > > > section in isn\'t propagated to child POMs > (as is). > The workaround is to use with true > Is this on purpose ? -- 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1703) is not propagated to child POMs
[ http://jira.codehaus.org/browse/MNG-1703?page=comments#action_54110 ] Edwin Punzalan commented on MNG-1703: - Hmmm... that's odd. can you do a "mvn help:effective-pom" on the child module and see which have been inherited? Mine definitely has the executions inherited. > is not propagated to child POMs > -- > > Key: MNG-1703 > URL: http://jira.codehaus.org/browse/MNG-1703 > Project: Maven 2 > Type: Bug > Components: POM > Versions: 2.0 > Reporter: Yann Le Du > Assignee: Edwin Punzalan > Fix For: 2.0.3 > > > section in isn't propagated to child POMs (as > is). > The workaround is to use with true > Is this on purpose ? -- 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]
