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]
fixing the jUDDI gump build
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. Thank you, --Kurt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fixing the jUDDI gump build
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. --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]
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
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. 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]
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]
Fwd: SourceForge.net Update: June 2007 Edition
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: 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 smime.p7s Description: S/MIME cryptographic signature
BATCH: Unable to send...
Dear Gumpmeisters, The following 2 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Project cddlm (in module ggf-cddlm) failed [EMAIL PROTECTED]: Project manual4eclipse (in module ant-antlibs-sandbox) failed *** G U M P [EMAIL PROTECTED]: Project cddlm (in module ggf-cddlm) failed Failed with to: [EMAIL PROTECTED] from: [Smartfrog [EMAIL PROTECTED]] Failed to send notify e-mail: (111, 'Connection refused') To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cddlm has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 268 runs. The current state of this project is 'Failed', with reason 'Configuration Failed'. For reference only, the following projects are affected by this: - cddlm : Configuration and Deployment of Grid Applications and System... Full details are available at: http://vmgump.apache.org/gump/public/ggf-cddlm/cddlm/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason configuration failed -ERROR- Bad Dependency. Project: smartfrog-private-ivy : unknown to *this* workspace -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/ggf-cddlm/cddlm/rss.xml - Atom: http://vmgump.apache.org/gump/public/ggf-cddlm/cddlm/atom.xml == Gump Tracking Only === Produced by Gump version 2.3. Gump Run 1615062007, vmgump.apache.org:vmgump-public:1615062007 Gump E-mail Identifier (unique within run) #5. *** G U M P [EMAIL PROTECTED]: Project manual4eclipse (in module ant-antlibs-sandbox) failed Failed with to: [EMAIL PROTECTED] from: [Gump Integration Build general@gump.apache.org] Failed to send notify e-mail: (111, 'Connection refused') To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project manual4eclipse has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 36 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - manual4eclipse : Task and Type Libraries for Apache Ant Full details are available at: http://vmgump.apache.org/gump/public/ant-antlibs-sandbox/manual4eclipse/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [ant-m4e-15062007.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/ant-antlibs-sandbox/manual4eclipse/gump_work/build_ant-antlibs-sandbox_manual4eclipse.html Work Name: build_ant-antlibs-sandbox_manual4eclipse (Type: Build) Work ended in a state of : Failed Elapsed: Command Line: /opt/jdk1.5/bin/java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Djarname=build/ant-m4e-15062007.jar antlib [Working Directory: /usr/local/gump/public/workspace/ant-antlibs-sandbox/antlibs/manual4eclipse] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar - Buildfile: build.xml does not exist! Build failed - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/ant-antlibs-sandbox/manual4eclipse/rss.xml - Atom: http://vmgump.apache.org/gump/public/ant-antlibs-sandbox/manual4eclipse/atom.xml
BATCH: Unable to send...
Dear Gumpmeisters, The following 2 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Project cddlm (in module ggf-cddlm) failed [EMAIL PROTECTED]: Project manual4eclipse (in module ant-antlibs-sandbox) failed *** G U M P [EMAIL PROTECTED]: Project cddlm (in module ggf-cddlm) failed Failed with to: [EMAIL PROTECTED] from: [Smartfrog [EMAIL PROTECTED]] Failed to send notify e-mail: (111, 'Connection refused') To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cddlm has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 268 runs. The current state of this project is 'Failed', with reason 'Configuration Failed'. For reference only, the following projects are affected by this: - cddlm : Configuration and Deployment of Grid Applications and System... Full details are available at: http://vmgump.apache.org/gump/public/ggf-cddlm/cddlm/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason configuration failed -ERROR- Bad Dependency. Project: smartfrog-private-ivy : unknown to *this* workspace -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/ggf-cddlm/cddlm/rss.xml - Atom: http://vmgump.apache.org/gump/public/ggf-cddlm/cddlm/atom.xml == Gump Tracking Only === Produced by Gump version 2.3. Gump Run 1615062007, vmgump.apache.org:vmgump-public:1615062007 Gump E-mail Identifier (unique within run) #5. *** G U M P [EMAIL PROTECTED]: Project manual4eclipse (in module ant-antlibs-sandbox) failed Failed with to: [EMAIL PROTECTED] from: [Gump Integration Build general@gump.apache.org] Failed to send notify e-mail: (111, 'Connection refused') To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project manual4eclipse has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 36 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - manual4eclipse : Task and Type Libraries for Apache Ant Full details are available at: http://vmgump.apache.org/gump/public/ant-antlibs-sandbox/manual4eclipse/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [ant-m4e-15062007.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/ant-antlibs-sandbox/manual4eclipse/gump_work/build_ant-antlibs-sandbox_manual4eclipse.html Work Name: build_ant-antlibs-sandbox_manual4eclipse (Type: Build) Work ended in a state of : Failed Elapsed: Command Line: /opt/jdk1.5/bin/java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Djarname=build/ant-m4e-15062007.jar antlib [Working Directory: /usr/local/gump/public/workspace/ant-antlibs-sandbox/antlibs/manual4eclipse] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar - Buildfile: build.xml does not exist! Build failed - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/ant-antlibs-sandbox/manual4eclipse/rss.xml - Atom: http://vmgump.apache.org/gump/public/ant-antlibs-sandbox/manual4eclipse/atom.xml
advice for fixing commons-email breakage
Hi all, I've been making changes to commons-email recently and gump is unhappy. I've looked into it and asked for advice on commons-dev, and now I'd like to ask the experts commons-email now depends on two things not in gump. The new dependencies are only used during test runs (they simulate an SMTP server) and are NOT required for clients. After reading the docs it seems straightforward enough to build them, but there are a few problems: 1) I want only a specific version of the test dependencies and don't really care if upstream changes break my code (and users won't care either) 2) the build system for commons-email is maven 2, but using it in gump seems unsupported 3) the build for my new dependencies is compiled under 1.5 and then translated using retroweaver to produce 1.4-compatible jars; commons-email only requires 1.4 to build Given that commons-email is going to be maven 2 from here on out, the maven 1 file will likely go away soon since it seems silly to maintain ant, m1, and m2. How would you recommend I proceed given these issues? Thanks! --Ben
