Re: Does anybody Know a Small Maven 3.x Project?
On Wed, Oct 27, 2010 at 10:42 AM, Jörg Schaible joerg.schai...@gmx.de wrote: Stefan Bodewig wrote: On 2010-10-27, Jörg Schaible wrote: Stefan Bodewig wrote: Does anybody know of a small project that could be a good candidate to put into a testbed in order to test/improve the mvn builder so it works with either version? commons-lang3 ? Builds fine using Maven 2.2.1 in Gump. Do you mean it should also work with Maven 3.x (is that mvn3?) or that Maven 3.x is in fact the preferred build tool? It works also with M3, but M3 is not required. Actually I've built all released commons artifacts for the vote with M3 (starting with M3 betas) and had never problems because of M3 (apart from site generation which is normally not generated with Gump). +1 to what Jörg has said. Also this is true for all Commons *proper* components - which I have tested with M3 http://markmail.org/message/32j6w3xtwdjbi2h4 Niall - Jörg - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r999257 - /gump/metadata/project/commons-proper.xml
On Tue, Sep 21, 2010 at 8:28 AM, bode...@apache.org wrote: Author: bodewig Date: Tue Sep 21 07:28:24 2010 New Revision: 999257 URL: http://svn.apache.org/viewvc?rev=999257view=rev Log: try publishing beanutils' POM as beanutils-core POM, not sure it will work It should be OK. It will have an additional (unnecessary) dependency on Commons Collections - but that shouldn't cause any problems. Niall Modified: gump/metadata/project/commons-proper.xml Modified: gump/metadata/project/commons-proper.xml URL: http://svn.apache.org/viewvc/gump/metadata/project/commons-proper.xml?rev=999257r1=999256r2=999257view=diff == --- gump/metadata/project/commons-proper.xml (original) +++ gump/metadata/project/commons-proper.xml Tue Sep 21 07:28:24 2010 @@ -78,6 +78,7 @@ !-- alias to make mvn2 happy -- project name=commons-beanutils-core groupId=commons-beanutils depend project=commons-beanutils/ + pom name=beanutils/pom.xml/ jar name=beanutils/dist/commons-beanutils-@@DATE@@.jar id=commons-beanutils-core/ /project - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r999257 - /gump/metadata/project/commons-proper.xml
On Tue, Sep 21, 2010 at 10:30 AM, Stefan Bodewig bode...@apache.org wrote: On 2010-09-21, Niall Pemberton wrote: On Tue, Sep 21, 2010 at 8:28 AM, bode...@apache.org wrote: Author: bodewig Date: Tue Sep 21 07:28:24 2010 New Revision: 999257 URL: http://svn.apache.org/viewvc?rev=999257view=rev Log: try publishing beanutils' POM as beanutils-core POM, not sure it will work It should be OK. It will have an additional (unnecessary) dependency on Commons Collections - but that shouldn't cause any problems. The reason I added it was http://vmgump.apache.org/gump/public/checkstyle/checkstyle/gump_work/build_checkstyle_checkstyle.html Which looks like a project using (a released version of) beanutils but not depending on commons-collections, like we've seen for digester-test. checkstyle doesn't depend on beanutils but only on beantils-core but since we publish the normal beanutils jar as beanutils-core in Gump it may be that this dependency on commons-collections only exists inside Gump. BeanUtils used to have a copy of the Collections FastHashMap (and 4 other collections classes). With those BeanUtils core had no dependency on Commons Collections. There are other clases in BeanUtils which did require Commons Collections, but they were excluded from the Core jar. This was a mess so I removed the copied classes and dumped the BeanUtils core jar. So now there is only one BeanUtils jar and anything that depends on it requires Commons Collections: https://issues.apache.org/jira/browse/BEANUTILS-379 So effectively the core dependency has disappeared. Not sure how gump should/can handle that. Perhaps a *packaged* version of beanutils core. Or as I guess you're trying to do - feed in BeanUtils as core - but those projects that depend on it will now requires Commons Collections. The not sure it will work part is more about the fact that the POM will specify a different artifactId than mvn asks for and I don't know whether mvn will ignore this or reject the POM or explode or whatever. OK, me neither - I guess we'll see after the next run. Niall Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: skipTests vs maven.test.skip.exec
On Mon, Sep 6, 2010 at 5:03 AM, Stefan Bodewig bode...@apache.org wrote: Hi, some time back we had a discussion that skipTest was the preferred property to use when we want to tell mvn not to run tests - well, it doesn't work, at least not for Cocoon 2.2.x. My theory is that those properties are interpreted by the surefire plugin rather than mvn itself. Yes, they are plugin parameters: http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html And from the docs the skipTests parameter was added in version 2.4 of the surefire plugin Unlike the version of mvn we cannot influence the version of plugins used by a project, so whether skipTests works or not depends on the project. Yes and cocoon is using version 2.3 of the surefire plugin (see pluginManagement section of the pom): http://svn.apache.org/repos/asf/cocoon/trunk/parent/pom.xml skipTests was introduced to replace the more verbose maven.test.skip=true - you could use that instead though. Niall Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: skipTests vs maven.test.skip.exec
On Mon, Sep 6, 2010 at 12:16 PM, Stefan Bodewig bode...@apache.org wrote: On 2010-09-06, Niall Pemberton wrote: On Mon, Sep 6, 2010 at 5:03 AM, Stefan Bodewig bode...@apache.org wrote: Hi, some time back we had a discussion that skipTest was the preferred property to use when we want to tell mvn not to run tests - well, it doesn't work, at least not for Cocoon 2.2.x. My theory is that those properties are interpreted by the surefire plugin rather than mvn itself. Yes, they are plugin parameters: http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html Thank you for the confirmation. And from the docs the skipTests parameter was added in version 2.4 of the surefire plugin [...] and cocoon is using version 2.3 of the surefire plugin (see pluginManagement section of the pom): skipTests was introduced to replace the more verbose maven.test.skip=true - you could use that instead though. Is there a difference between maven.test.skip and maven.test.skip.exec (which we use now)? I see there is a skip property in addition to the skipTests property - the former even avoids compilation of the tests, so I gues this is the difference here as well. Yes, the skipTests and maven.test.skip.exec=true are the same - the tests get compiled, but not executed. The maven.test.skip=true doesn't compile or execute the tests. Niall As much as I would have loved consistency it seems we are best off with using skipTests when possible and fall back to maven.test.skip.exec. Coming to think of it, skip and maven.test.skip may help for builds like james-jsieve which requires JUnit 3.8 to compile because they still have one of those AllTests classes invoking swingui.TestRunner we used to write in 2000. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r887621 - /gump/metadata/project/commons-jexl-1.x.xml
I also tried another approach to fix this at the same time - but which change made this work - yours or mine? http://svn.apache.org/viewvc?view=revisionrevision=887616 I'm thinking of removing that id element and see if it still works with my change. Niall On Sun, Dec 6, 2009 at 12:47 AM, billbar...@apache.org wrote: Author: billbarker Date: Sun Dec 6 00:47:23 2009 New Revision: 887621 URL: http://svn.apache.org/viewvc?rev=887621view=rev Log: Let's try it without the version number and see if that makes maven happy Modified: gump/metadata/project/commons-jexl-1.x.xml Modified: gump/metadata/project/commons-jexl-1.x.xml URL: http://svn.apache.org/viewvc/gump/metadata/project/commons-jexl-1.x.xml?rev=887621r1=887620r2=887621view=diff == --- gump/metadata/project/commons-jexl-1.x.xml (original) +++ gump/metadata/project/commons-jexl-1.x.xml Sun Dec 6 00:47:23 2009 @@ -28,7 +28,7 @@ packageorg.apache.commons.jexl/package descriptionCommons Jexl 1.x/description mvn goal=package / - jar name=target/commons-jexl-1.1.1-SNAPSHOT.jar id=commons-jexl-1.1/ + jar name=target/commons-jexl-1.1.1-SNAPSHOT.jar id=commons-jexl/ option project=ant/ option project=commons-beanutils/ option project=commons-collections/ - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Commons Jelly - JEXL 1.x dependency
On Fri, Dec 4, 2009 at 3:24 AM, Bill Barker billwbar...@verizon.net wrote: - Original Message - From: Niall Pemberton niall.pember...@gmail.com To: general@gump.apache.org Sent: Thursday, December 03, 2009 1:56 AM Subject: Commons Jelly - JEXL 1.x dependency Commons JEXL has changed its package names in the trunk (version 2.x) , so I added a JEXL 1.x project (maven 2) to gump which builds from the JEXL 1.x branch: http://svn.apache.org/repos/asf/gump/metadata/project/commons-jexl-1.x.xml Commons Jelly is a maven 1 project and I changed the dependency to commons-jexl-1.x - but its failing with the following message: The build cannot continue because of the following unsatisfied dependency: commons-jexl-1.1.jar http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly/gump_work/build_commons-jelly_commons-jelly.html http://svn.apache.org/viewvc?view=revisionrevision=886220 Any idea why? If in the jexl 1.1 metadata you do: jar name=target/commons-jexl-1.1.1-SNAPSHOT.jar id=commons-jexl-1.1/then it should work for jelly. Haven't looked enough (and not familiar enough with Maven) to see if it will break someone else. Thanks I'll give that a go and see what happens. Niall - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Commons Jelly - JEXL 1.x dependency
Commons JEXL has changed its package names in the trunk (version 2.x) , so I added a JEXL 1.x project (maven 2) to gump which builds from the JEXL 1.x branch: http://svn.apache.org/repos/asf/gump/metadata/project/commons-jexl-1.x.xml Commons Jelly is a maven 1 project and I changed the dependency to commons-jexl-1.x - but its failing with the following message: The build cannot continue because of the following unsatisfied dependency:commons-jexl-1.1.jar http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly/gump_work/build_commons-jelly_commons-jelly.html http://svn.apache.org/viewvc?view=revisionrevision=886220 Any idea why? Niall - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Commons JCI failure
On Tue, Jan 20, 2009 at 5:22 AM, Stefan Bodewig bode...@apache.org wrote: On 2009-01-20, Stefan Bodewig bode...@apache.org wrote: If janino isn't used by any other project, simply removing it is the best thing to do. Done Thank you! Now on to the next issue... Niall Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Commons JCI failure
Commons JCI is currently failing[1] because of its janino dependency - which appears to be a packaged 2.3.8 version. JCI currently depends on the latest janino 2.5.10 release. Since JCI use a maven2 build - could it not download the version it requires and get rid of this packaged project (doesn't seem like anything else uses it) - or update the packaged janino to the latest version? tia Niall [1] http://vmgump.apache.org/gump/public/apache-commons/commons-jci/gump_work/build_apache-commons_commons-jci.html [2] http://vmgump.apache.org/gump/public/janino/janino/index.html - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r549123 - /gump/metadata/project/jakarta-commons.xml
I believe I had corrected the gump problem by amending the property for the jar name earlier (by copying what the bcel m2 gump config had): http://svn.apache.org/viewvc?view=revrevision=549101 ...and I can't see any reason to completely remove since I believe gump will fail with the same error as the last run anyway - since the config has: jar name=commons-email-@@DATE@@.jar/ Niall On 6/20/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Author: bspeakmon Date: Wed Jun 20 08:00:20 2007 New Revision: 549123 URL: http://svn.apache.org/viewvc?view=revrev=549123 Log: - fixed commons-email jar output name Modified: gump/metadata/project/jakarta-commons.xml Modified: gump/metadata/project/jakarta-commons.xml URL: http://svn.apache.org/viewvc/gump/metadata/project/jakarta-commons.xml?view=diffrev=549123r1=549122r2=549123 == --- gump/metadata/project/jakarta-commons.xml (original) +++ gump/metadata/project/jakarta-commons.xml Wed Jun 20 08:00:20 2007 @@ -425,7 +425,6 @@ descriptionCommons Email Package/description mvn basedir=email goal=package - property name=project.build.finalName value=commons-email-@@DATE@@/ depend project=javamail property=maven.jar.mail id=javamail / /mvn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r549123 - /gump/metadata/project/jakarta-commons.xml
On 6/20/07, Niall Pemberton [EMAIL PROTECTED] wrote: On 6/20/07, Ben Speakmon [EMAIL PROTECTED] wrote: I thought I was copying bcel too. I'm confused because bcel has the @@DATE@@ tag in its project.build.finalName, but the jar points to 5.3-SNAPSHOT. Good point - looks like that property has no effect - so maybe you're right ...but I think you will need to change the jar config jar name=target/commons-email-1.1-SNAPSHOT/ ...and probably specify an id - I'm guess that would mean downstream dependencies wouldn't have to change every time the version gets incremented. Not quite sure about the id but I'll try to look at other examples to try and work out the affect it has Niall Niall I'll back out the change. On 6/20/07, Niall Pemberton [EMAIL PROTECTED] wrote: I believe I had corrected the gump problem by amending the property for the jar name earlier (by copying what the bcel m2 gump config had): http://svn.apache.org/viewvc?view=revrevision=549101 ...and I can't see any reason to completely remove since I believe gump will fail with the same error as the last run anyway - since the config has: jar name=commons-email-@@DATE@@.jar/ Niall On 6/20/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Author: bspeakmon Date: Wed Jun 20 08:00:20 2007 New Revision: 549123 URL: http://svn.apache.org/viewvc?view=revrev=549123 Log: - fixed commons-email jar output name Modified: gump/metadata/project/jakarta-commons.xml Modified: gump/metadata/project/jakarta-commons.xml URL: http://svn.apache.org/viewvc/gump/metadata/project/jakarta-commons.xml?view=diffrev=549123r1=549122r2=549123 == --- gump/metadata/project/jakarta-commons.xml (original) +++ gump/metadata/project/jakarta-commons.xml Wed Jun 20 08:00:20 2007 @@ -425,7 +425,6 @@ descriptionCommons Email Package/description mvn basedir=email goal=package - property name=project.build.finalName value=commons-email-@@DATE@@/ depend project=javamail property=maven.jar.mail id=javamail / /mvn - 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: svn commit: r549123 - /gump/metadata/project/jakarta-commons.xml
On 6/20/07, Ben Speakmon [EMAIL PROTECTED] wrote: I thought I was copying bcel too. I'm confused because bcel has the @@DATE@@ tag in its project.build.finalName, but the jar points to 5.3-SNAPSHOT. Good point - looks like that property has no effect - so maybe you're right Niall I'll back out the change. On 6/20/07, Niall Pemberton [EMAIL PROTECTED] wrote: I believe I had corrected the gump problem by amending the property for the jar name earlier (by copying what the bcel m2 gump config had): http://svn.apache.org/viewvc?view=revrevision=549101 ...and I can't see any reason to completely remove since I believe gump will fail with the same error as the last run anyway - since the config has: jar name=commons-email-@@DATE@@.jar/ Niall On 6/20/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Author: bspeakmon Date: Wed Jun 20 08:00:20 2007 New Revision: 549123 URL: http://svn.apache.org/viewvc?view=revrev=549123 Log: - fixed commons-email jar output name Modified: gump/metadata/project/jakarta-commons.xml Modified: gump/metadata/project/jakarta-commons.xml URL: http://svn.apache.org/viewvc/gump/metadata/project/jakarta-commons.xml?view=diffrev=549123r1=549122r2=549123 == --- gump/metadata/project/jakarta-commons.xml (original) +++ gump/metadata/project/jakarta-commons.xml Wed Jun 20 08:00:20 2007 @@ -425,7 +425,6 @@ descriptionCommons Email Package/description mvn basedir=email goal=package - property name=project.build.finalName value=commons-email-@@DATE@@/ depend project=javamail property=maven.jar.mail id=javamail / /mvn - 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: fixing the jUDDI gump build
On 6/16/07, Leo Simons [EMAIL PROTECTED] wrote: On Jun 15, 2007, at 5:20 PM, Kurt T Stam wrote: Yeah I did: commit -m Adding axis2 dependency C:/cygwin/home/kstam/dev/gump/metadata/project/ws-juddi.xml Sendingdev/gump/metadata/project/ws-juddi.xml RA layer request failed svn: Commit failed (details follow): svn: CHECKOUT of '/repos/asf/!svn/ver/451115/gump/metadata/project/ws-juddi.xml': 403 Forbidden (https://svn.apache.org) A C:/cygwin/home/kstam/dev/gump/metadata/project/excalibur.xml That's a really weird error to get. I just checked the SVN config and you *should* have access. The problem must be elsewhere. In bash under cygwin, doing cd ~/dev/ svn co https://svn.apache.org/repos/asf/gump/metadata/ gump-metadata cd gump-metadata echo 'test' test.txt svn add test.txt svn commit -m Testing write access, please ignore test.txt should normally work. could you run `svn status` and `svn info` on the top of your checkout and send it to us? Kurt wasn't added to the general committers list - which (from infra@ messages) was just fixed a few hours ago - so maybe/probably that was the problem and he should be OK now. Niall thanks, Leo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fixing the jUDDI gump build
On 6/15/07, Kurt T Stam [EMAIL PROTECTED] wrote: Hi guys, The gump build for jUDDI has been failing for a while now because of some missing dependencies around axis2. This got added to the gump.xml: depend project=ws-axis2/ but I'm guessing that is not enough. If I can get some assistance it should be easy to fix this. Presumably you mean gump.xml in the juddi project: http://svn.apache.org/viewvc/webservices/juddi/trunk/gump.xml However looking at the gump run info - it is picking up the gump project descriptor from the project/ws-juddi.xml file in the gump repo - which still has a dependency of ws-axis rather than ws-axis2: http://svn.apache.org/repos/asf/gump/metadata/project/ws-juddi.xml So either you need to update the one that gump is currently using - or switch gump to use the one from your project's repo - I believe in the gump profile: http://svn.apache.org/repos/asf/gump/metadata/profile/gump.xml Not sure if theres a policy/thinking wrt to gump definitions in project repos - doesn't seem to be done anywhere else now - hopefully one of the gump devs. would comment on this Niall Thank you, --Kurt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fixing the jUDDI gump build
On 6/15/07, Kurt T Stam [EMAIL PROTECTED] wrote: Thanks Niall, That clears things up :). I don't have commit rights on gump (just tried to update http://svn.apache.org/repos/asf/gump/metadata/project/ws-juddi.xml So I'm stuck. Can't update which file is used either. So I hope someone can let me know about the policies since it looks that right now I can't fix this myself. Thats strange - I thought all ASF committers had commit rights on the gump metadata. Anyway if you want to email me a new version (or patch) for ws-juddi.xml - I'll commit it for you. Niall --Kurt Niall Pemberton wrote: On 6/15/07, Kurt T Stam [EMAIL PROTECTED] wrote: Hi guys, The gump build for jUDDI has been failing for a while now because of some missing dependencies around axis2. This got added to the gump.xml: depend project=ws-axis2/ but I'm guessing that is not enough. If I can get some assistance it should be easy to fix this. Presumably you mean gump.xml in the juddi project: http://svn.apache.org/viewvc/webservices/juddi/trunk/gump.xml However looking at the gump run info - it is picking up the gump project descriptor from the project/ws-juddi.xml file in the gump repo - which still has a dependency of ws-axis rather than ws-axis2: http://svn.apache.org/repos/asf/gump/metadata/project/ws-juddi.xml So either you need to update the one that gump is currently using - or switch gump to use the one from your project's repo - I believe in the gump profile: http://svn.apache.org/repos/asf/gump/metadata/profile/gump.xml Not sure if theres a policy/thinking wrt to gump definitions in project repos - doesn't seem to be done anywhere else now - hopefully one of the gump devs. would comment on this Niall Thank you, --Kurt - 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: fixing the jUDDI gump build
On 6/15/07, Niall Pemberton [EMAIL PROTECTED] wrote: On 6/15/07, Kurt T Stam [EMAIL PROTECTED] wrote: Thanks Niall, That clears things up :). I don't have commit rights on gump (just tried to update http://svn.apache.org/repos/asf/gump/metadata/project/ws-juddi.xml So I'm stuck. Can't update which file is used either. So I hope someone can let me know about the policies since it looks that right now I can't fix this myself. Thats strange - I thought all ASF committers had commit rights on the gump metadata. btw did you check out using https? https://svn.apache.org/repos/asf/gump/metadata Anyway if you want to email me a new version (or patch) for ws-juddi.xml - I'll commit it for you. Niall --Kurt Niall Pemberton wrote: On 6/15/07, Kurt T Stam [EMAIL PROTECTED] wrote: Hi guys, The gump build for jUDDI has been failing for a while now because of some missing dependencies around axis2. This got added to the gump.xml: depend project=ws-axis2/ but I'm guessing that is not enough. If I can get some assistance it should be easy to fix this. Presumably you mean gump.xml in the juddi project: http://svn.apache.org/viewvc/webservices/juddi/trunk/gump.xml However looking at the gump run info - it is picking up the gump project descriptor from the project/ws-juddi.xml file in the gump repo - which still has a dependency of ws-axis rather than ws-axis2: http://svn.apache.org/repos/asf/gump/metadata/project/ws-juddi.xml So either you need to update the one that gump is currently using - or switch gump to use the one from your project's repo - I believe in the gump profile: http://svn.apache.org/repos/asf/gump/metadata/profile/gump.xml Not sure if theres a policy/thinking wrt to gump definitions in project repos - doesn't seem to be done anywhere else now - hopefully one of the gump devs. would comment on this Niall Thank you, --Kurt - 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: fixing the jUDDI gump build
On 6/15/07, Kurt T Stam [EMAIL PROTECTED] wrote: Yeah I did: commit -m Adding axis2 dependency C:/cygwin/home/kstam/dev/gump/metadata/project/ws-juddi.xml Sendingdev/gump/metadata/project/ws-juddi.xml RA layer request failed svn: Commit failed (details follow): svn: CHECKOUT of '/repos/asf/!svn/ver/451115/gump/metadata/project/ws-juddi.xml': 403 Forbidden (https://svn.apache.org) A C:/cygwin/home/kstam/dev/gump/metadata/project/excalibur.xml I think adding depend project=ws-axis2/ should do the trick. OK done: http://svn.apache.org/viewvc?view=revrevision=547711 Niall Thanks! --Kurt Niall Pemberton wrote: On 6/15/07, Niall Pemberton [EMAIL PROTECTED] wrote: On 6/15/07, Kurt T Stam [EMAIL PROTECTED] wrote: Thanks Niall, That clears things up :). I don't have commit rights on gump (just tried to update http://svn.apache.org/repos/asf/gump/metadata/project/ws-juddi.xml So I'm stuck. Can't update which file is used either. So I hope someone can let me know about the policies since it looks that right now I can't fix this myself. Thats strange - I thought all ASF committers had commit rights on the gump metadata. btw did you check out using https? https://svn.apache.org/repos/asf/gump/metadata Anyway if you want to email me a new version (or patch) for ws-juddi.xml - I'll commit it for you. Niall --Kurt Niall Pemberton wrote: On 6/15/07, Kurt T Stam [EMAIL PROTECTED] wrote: Hi guys, The gump build for jUDDI has been failing for a while now because of some missing dependencies around axis2. This got added to the gump.xml: depend project=ws-axis2/ but I'm guessing that is not enough. If I can get some assistance it should be easy to fix this. Presumably you mean gump.xml in the juddi project: http://svn.apache.org/viewvc/webservices/juddi/trunk/gump.xml However looking at the gump run info - it is picking up the gump project descriptor from the project/ws-juddi.xml file in the gump repo - which still has a dependency of ws-axis rather than ws-axis2: http://svn.apache.org/repos/asf/gump/metadata/project/ws-juddi.xml So either you need to update the one that gump is currently using - or switch gump to use the one from your project's repo - I believe in the gump profile: http://svn.apache.org/repos/asf/gump/metadata/profile/gump.xml Not sure if theres a policy/thinking wrt to gump definitions in project repos - doesn't seem to be done anywhere else now - hopefully one of the gump devs. would comment on this Niall Thank you, --Kurt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SourceForge.net Update: June 2007 Edition
On 6/15/07, Sander Temme [EMAIL PROTECTED] wrote: Folks, The newsletter from Sourceforge arrived: Begin forwarded message: .. Lastly, VA Software, the company that owns and operates SourceForge.net, has changed its name to SourceForge, Inc. Read more here: http://web.sourceforge.com/news_archive/2007/1799.php Wow isn't that the end of and era? Wonder what they will use for stock ticker, SFGE? Anyway, I was wondering how badly the following is going to bitch- slap us: Looks to be the projects using the sourceforge-svn repository definition: ant-contrib-cpptasks.xml ant-contrib.xml mx4j.xml xmlunit.xml Smartfrog already has a separate repo definition using the new format - so I guess it just needs the above 4 adding Niall Legacy Subversion Access Method Going Away -- Back in November of 2006, we added a new preferred access method for our Subversion offering that solved most of the spurious error messages and other problems with our initial SVN rollout. The change introduced a new URL scheme: https://PROJECTNAME.svn.sourceforge.net/svnroot/PROJECTNAME Users have been receiving the notice to upgrade via a Site Status announcement and as needed via Support Request when problems were reported. As a part of our ongoing infrastructure improvements to our Subversion offering and other services, we will be decommissioning the legacy access method (the one without the PROJECTNAME prefix for the hostname) as of June 28. Past that time, Subversion operations that use the old URL scheme will no longer work. You may change over any existing Subversion checkouts you have by following the instructions detailed here: https://sourceforge.net/docs/E09#notice -- Sander Temme [EMAIL PROTECTED] PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Velocity Failure - ant taskdef
Thanks Stefan Niall - Original Message - From: Stefan Bodewig [EMAIL PROTECTED] Sent: Wednesday, October 12, 2005 5:15 AM On Mon, 10 Oct 2005, Niall Pemberton [EMAIL PROTECTED] wrote: Velocity's build has failed because it can't find the class for an ant task (i.e. taskdef) - the class was compiled in a previous step of the build. I presume this is because ant doesn't have that class in its classpath. Yes. If thats correct is there any way to make available the compiled classes to ant in gump? Yes, use a work element to point to the compiled classes for the task (I've just done so). P.S. I'm not a velocity committer, just lurk on their list and helping out with gump: Thank you Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven xdoclet plugin - version 1.2.3
struts-taglib-from-packages is failing because it uses maven:get tags, which version 1.2.1 of maven-xdoclet-plugin doesn't have -this requires version 1.2.3 http://vmgump.apache.org/gump/public/struts/struts-taglib-from-packages/index.html Could someone upload the maven-xdoclet-plugin-1.2.3.jar to the appropriate place on the gump machine (I can update the metadata). The plugin jar is in xdoclet-lib-1.2.3.zip on sourceforge: http://sourceforge.net/project/showfiles.php?group_id=31602 Thanks Niall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Taglib plugin
Great thanks Brett, all run through OK now. Niall - Original Message - From: Brett Porter [EMAIL PROTECTED] Sent: Monday, October 10, 2005 2:37 AM heh, it seems it is a sourceforge download page in there :) I'll go and get it again. - Brett On 10/9/05, Niall Pemberton [EMAIL PROTECTED] wrote: The maven-taglib-plugin project passed which is great http://vmgump.apache.org/gump/public/maven-taglib-plugin/maven-taglib-plugin/index.html ...but struts-tiles which uses the maven-taglib-plugin jar failed - for some reason maven's plugin manager couldn't seem to unzip the jar and threw an exception saying Not a valid plugin file... http://vmgump.apache.org/gump/public/struts/struts-tiles/gump_work/build_struts_struts-tiles.html org.apache.maven.MavenException: Not a valid plugin file: /usr/local/gump/packages/maven-taglib-plugin/maven-taglib-plugin-1.4.jar at org.apache.maven.plugin.PluginManager.installPlugin(PluginManager.java:910) at org.apache.maven.plugin.PluginManager.installPlugin(PluginManager.java:862) at org.apache.maven.plugin.PluginManager.processDependencies(PluginManager.java :448) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:642) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) Niall - Original Message - From: Niall Pemberton [EMAIL PROTECTED] Sent: Saturday, October 08, 2005 2:34 PM Thanks Brett, I appreciate you sorting this out. Also, if I'd known I could have fixed that myself - so hopefully next time... Niall - Original Message - From: Brett Porter [EMAIL PROTECTED] Sent: Saturday, October 08, 2005 1:56 PM should really be fixed now. I always forget to add the second packaging line in profile/gump.xml. - Brett On 10/8/05, Niall Pemberton [EMAIL PROTECTED] wrote: Sorry to nag, but this is still failing because it can't find the maven-taglib-plugin-1.4.jar Niall - Original Message - From: Brett Porter [EMAIL PROTECTED] Sent: Tuesday, October 04, 2005 3:28 PM done. On 10/4/05, Niall Pemberton [EMAIL PROTECTED] wrote: I set up maven-taglib-plugin in gump (with Bretts help) - but it still needs the maven-taglib-plugin-1.4.jar to be added to (?who knows where?) gump. http://vmgump.apache.org/gump/public/maven-taglib-plugin/maven-taglib-plugin/index.html Niall - Original Message - From: Niall Pemberton [EMAIL PROTECTED] To: general@gump.apache.org Sent: Tuesday, September 27, 2005 3:33 PM Subject: Maven Taglib plugin I've added the project descriptor for the maven-taglib-plugin: http://maven-taglib.sourceforge.net/ Could someone with the appropriate knowledge/access add the maven-taglib-plugin-1.4.jar please? Niall P.S. If this is something I could do, please let me know how. - 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]
Velocity Failure - ant taskdef
Velocity's build has failed because it can't find the class for an ant task (i.e. taskdef) - the class was compiled in a previous step of the build. I presume this is because ant doesn't have that class in its classpath. If thats correct is there any way to make available the compiled classes to ant in gump? http://vmgump.apache.org/gump/public/jakarta-velocity/jakarta-velocity/index.html ...or does do they need to change either their build or the way velocity projects are structure in gump? Niall P.S. I'm not a velocity committer, just lurk on their list and helping out with gump: http://www.mail-archive.com/velocity-dev%40jakarta.apache.org/msg13206.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Taglib plugin
The maven-taglib-plugin project passed which is great http://vmgump.apache.org/gump/public/maven-taglib-plugin/maven-taglib-plugin/index.html ...but struts-tiles which uses the maven-taglib-plugin jar failed - for some reason maven's plugin manager couldn't seem to unzip the jar and threw an exception saying Not a valid plugin file... http://vmgump.apache.org/gump/public/struts/struts-tiles/gump_work/build_struts_struts-tiles.html org.apache.maven.MavenException: Not a valid plugin file: /usr/local/gump/packages/maven-taglib-plugin/maven-taglib-plugin-1.4.jar at org.apache.maven.plugin.PluginManager.installPlugin(PluginManager.java:910) at org.apache.maven.plugin.PluginManager.installPlugin(PluginManager.java:862) at org.apache.maven.plugin.PluginManager.processDependencies(PluginManager.java :448) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:642) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) Niall - Original Message - From: Niall Pemberton [EMAIL PROTECTED] Sent: Saturday, October 08, 2005 2:34 PM Thanks Brett, I appreciate you sorting this out. Also, if I'd known I could have fixed that myself - so hopefully next time... Niall - Original Message - From: Brett Porter [EMAIL PROTECTED] Sent: Saturday, October 08, 2005 1:56 PM should really be fixed now. I always forget to add the second packaging line in profile/gump.xml. - Brett On 10/8/05, Niall Pemberton [EMAIL PROTECTED] wrote: Sorry to nag, but this is still failing because it can't find the maven-taglib-plugin-1.4.jar Niall - Original Message - From: Brett Porter [EMAIL PROTECTED] Sent: Tuesday, October 04, 2005 3:28 PM done. On 10/4/05, Niall Pemberton [EMAIL PROTECTED] wrote: I set up maven-taglib-plugin in gump (with Bretts help) - but it still needs the maven-taglib-plugin-1.4.jar to be added to (?who knows where?) gump. http://vmgump.apache.org/gump/public/maven-taglib-plugin/maven-taglib-plugin/index.html Niall - Original Message - From: Niall Pemberton [EMAIL PROTECTED] To: general@gump.apache.org Sent: Tuesday, September 27, 2005 3:33 PM Subject: Maven Taglib plugin I've added the project descriptor for the maven-taglib-plugin: http://maven-taglib.sourceforge.net/ Could someone with the appropriate knowledge/access add the maven-taglib-plugin-1.4.jar please? Niall P.S. If this is something I could do, please let me know how. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Taglib plugin
Sorry to nag, but this is still failing because it can't find the maven-taglib-plugin-1.4.jar Niall - Original Message - From: Brett Porter [EMAIL PROTECTED] Sent: Tuesday, October 04, 2005 3:28 PM done. On 10/4/05, Niall Pemberton [EMAIL PROTECTED] wrote: I set up maven-taglib-plugin in gump (with Bretts help) - but it still needs the maven-taglib-plugin-1.4.jar to be added to (?who knows where?) gump. http://vmgump.apache.org/gump/public/maven-taglib-plugin/maven-taglib-plugin/index.html Niall - Original Message - From: Niall Pemberton [EMAIL PROTECTED] To: general@gump.apache.org Sent: Tuesday, September 27, 2005 3:33 PM Subject: Maven Taglib plugin I've added the project descriptor for the maven-taglib-plugin: http://maven-taglib.sourceforge.net/ Could someone with the appropriate knowledge/access add the maven-taglib-plugin-1.4.jar please? Niall P.S. If this is something I could do, please let me know how. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Taglib plugin
Thanks Brett, I appreciate you sorting this out. Also, if I'd known I could have fixed that myself - so hopefully next time... Niall - Original Message - From: Brett Porter [EMAIL PROTECTED] Sent: Saturday, October 08, 2005 1:56 PM should really be fixed now. I always forget to add the second packaging line in profile/gump.xml. - Brett On 10/8/05, Niall Pemberton [EMAIL PROTECTED] wrote: Sorry to nag, but this is still failing because it can't find the maven-taglib-plugin-1.4.jar Niall - Original Message - From: Brett Porter [EMAIL PROTECTED] Sent: Tuesday, October 04, 2005 3:28 PM done. On 10/4/05, Niall Pemberton [EMAIL PROTECTED] wrote: I set up maven-taglib-plugin in gump (with Bretts help) - but it still needs the maven-taglib-plugin-1.4.jar to be added to (?who knows where?) gump. http://vmgump.apache.org/gump/public/maven-taglib-plugin/maven-taglib-plugin/index.html Niall - Original Message - From: Niall Pemberton [EMAIL PROTECTED] To: general@gump.apache.org Sent: Tuesday, September 27, 2005 3:33 PM Subject: Maven Taglib plugin I've added the project descriptor for the maven-taglib-plugin: http://maven-taglib.sourceforge.net/ Could someone with the appropriate knowledge/access add the maven-taglib-plugin-1.4.jar please? Niall P.S. If this is something I could do, please let me know how. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Taglib plugin
I set up maven-taglib-plugin in gump (with Bretts help) - but it still needs the maven-taglib-plugin-1.4.jar to be added to (?who knows where?) gump. http://vmgump.apache.org/gump/public/maven-taglib-plugin/maven-taglib-plugin/index.html Niall - Original Message - From: Niall Pemberton [EMAIL PROTECTED] To: general@gump.apache.org Sent: Tuesday, September 27, 2005 3:33 PM Subject: Maven Taglib plugin I've added the project descriptor for the maven-taglib-plugin: http://maven-taglib.sourceforge.net/ Could someone with the appropriate knowledge/access add the maven-taglib-plugin-1.4.jar please? Niall P.S. If this is something I could do, please let me know how. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Taglib plugin
Thanks Brett, although it still seems to be failing :-( Niall - Original Message - From: Brett Porter [EMAIL PROTECTED] Sent: Tuesday, October 04, 2005 3:28 PM done. On 10/4/05, Niall Pemberton [EMAIL PROTECTED] wrote: I set up maven-taglib-plugin in gump (with Bretts help) - but it still needs the maven-taglib-plugin-1.4.jar to be added to (?who knows where?) gump. http://vmgump.apache.org/gump/public/maven-taglib-plugin/maven-taglib-plugin/index.html Niall - Original Message - From: Niall Pemberton [EMAIL PROTECTED] To: general@gump.apache.org Sent: Tuesday, September 27, 2005 3:33 PM Subject: Maven Taglib plugin I've added the project descriptor for the maven-taglib-plugin: http://maven-taglib.sourceforge.net/ Could someone with the appropriate knowledge/access add the maven-taglib-plugin-1.4.jar please? Niall P.S. If this is something I could do, please let me know how. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven Taglib plugin
I've added the project descriptor for the maven-taglib-plugin: http://maven-taglib.sourceforge.net/ Could someone with the appropriate knowledge/access add the maven-taglib-plugin-1.4.jar please? Niall P.S. If this is something I could do, please let me know how. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Taglib plugin
I didn't know about the profile.xml - another bit of the gump jigsaw has just fallen into place for me - thanks Brett. Niall - Original Message - From: Brett Porter [EMAIL PROTECTED] Sent: Tuesday, September 27, 2005 11:16 PM I added to profile.xml. I've forgotten my password on that machine again (I'm going to have to log in once a day to remember it for a while when it comes back to me this time :) so haven't yet pushed it up there... Others - any chance we could put /packages/ in SVN somewhere and have gump update it on startup? Or take a URL in the gump profile? - Brett On 9/28/05, Niall Pemberton [EMAIL PROTECTED] wrote: I've added the project descriptor for the maven-taglib-plugin: http://maven-taglib.sourceforge.net/ Could someone with the appropriate knowledge/access add the maven-taglib-plugin-1.4.jar please? Niall P.S. If this is something I could do, please let me know how. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (GUMP-153) Gump Metadata: links no longer work
[ http://issues.apache.org/jira/browse/GUMP-153?page=comments#action_12322625 ] Niall Pemberton commented on GUMP-153: -- I agree the links need fixing, but rather than links that only show show the current versions it would be better to be able to use viewcvs so that all the subversion history can be seen. I would have expected to be able to see the gump subversion content using: http://svn.apache.org/viewcvs.cgi/gump/metadata/ but the result is a 403 Forbidden for some reason Gump Metadata: links no longer work --- Key: GUMP-153 URL: http://issues.apache.org/jira/browse/GUMP-153 Project: Gump Type: Bug Environment: http://vmgump.apache.org/gump/public/index.html Reporter: Sebb Priority: Minor The Gump meta data links no longer work, now that the metadata is in SVN. For example: http://cvs.apache.org/viewcvs.cgi/gump/project/jakarta-jmeter.xml should now be: http://svn.apache.org/repos/asf/gump/metadata/project/jakarta-jmeter.xml However, it would be better if the meta data link pointed to the actual file used by Gump for that run, rather than the current SVN contents, as that may have been updated since the run. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/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: [GUMP@brutus]: jakarta-struts/jakarta-struts failed
Martin Cooper recently applied a patch which hopefully would have sorted out the Struts gump failure. However it still failed again after he made that commit and I'm wondering whether gump is pointing to the new SVN repository that we moved to. From the looks of the jakarta-struts.xml file it isn't: cvs repository=jakarta/ Looks to me like it should probably be the following svn repository=struts/ Also the project name is showing as jakarta-struts - but struts has moved from jakarta and is now a top level project - can this be changed to just struts? Niall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
