DO NOT REPLY [Bug 44472] New: - If there is just a (not empty) directory SCP returns No such File
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=44472. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=44472 Summary: If there is just a (not empty) directory SCP returns No such File Product: Ant Version: 1.7.0 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Optional Tasks AssignedTo: notifications@ant.apache.org ReportedBy: [EMAIL PROTECTED] When I use scp file=user:[EMAIL PROTECTED]:/home/chuck/** todir=/home/sara/ if in chuck there are more than a directory (not empty) it works and downloads everything otherwise if there is just a directory (not empty) it returns a com.jcraft.jsch.JSchException: 2: No such file -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
[EMAIL PROTECTED]: Project dotnet-antlib-test (in module ant-antlibs) failed
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 dotnet-antlib-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 40 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - dotnet-antlib-test : Task and Type Libraries for Apache Ant Full details are available at: http://vmgump.apache.org/gump/public/ant-antlibs/dotnet-antlib-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/ant-antlibs/dotnet-antlib-test/gump_work/build_ant-antlibs_dotnet-antlib-test.html Work Name: build_ant-antlibs_dotnet-antlib-test (Type: Build) Work ended in a state of : Failed Elapsed: 17 secs Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true -Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dant-testutil.jar=/srv/gump/public/workspace/ant/build/lib/ant-testutil.jar test [Working Directory: /srv/gump/public/workspace/ant-antlibs/dotnet] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant-antlibs/dotnet/build/test-classes:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant-antlibs/antunit/build/ant-antunit-22022008.jar:/srv/gump/public/workspace/ant-antlibs/dotnet/build/ant-dotnet-22022008.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar - [au:antunit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.047 sec [au:antunit] Target: test-passing took 0.019 sec [au:antunit] Build File: /srv/gump/public/workspace/ant-antlibs/dotnet/src/tests/antunit/dir with spaces/wsdl-test.xml [au:antunit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.118 sec [au:antunit] Target: testWSDL took 1.038 sec [au:antunit] Build File: /srv/gump/public/workspace/ant-antlibs/dotnet/src/tests/antunit/dotnetexec-test.xml [au:antunit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.787 sec [au:antunit] Target: testCSC took 0.762 sec [au:antunit] Build File: /srv/gump/public/workspace/ant-antlibs/dotnet/src/tests/antunit/nunit/nunit-test.xml [au:antunit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.335 sec [au:antunit] Target: test-passing took 0.004 sec [au:antunit] Target: test-failing took 0.002 sec [au:antunit] Target: test-failing-errorproperty took 0.229 sec [au:antunit] Target: test-failing-with-fail took 0.01 sec [au:antunit] Target: test-no-assembly took 0.017 sec [au:antunit] Build File: /srv/gump/public/workspace/ant-antlibs/dotnet/src/tests/antunit/old-core-test.xml [au:antunit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 5.372 sec [au:antunit] Target: testCSCintrinsicFileset took 0.779 sec [au:antunit] Target: testCSCresponseFile took 0.59 sec [au:antunit] Target: testILASM took 0.837 sec [au:antunit] Target: testCSCdll took 0.594 sec [au:antunit] Target: testILDASM took 0.705 sec [au:antunit] Target: testILDASM_empty took 0.07 sec [au:antunit] Target: testJsharp took 0.015 sec [au:antunit] Target: testCSCResources took 0.799 sec [au:antunit] Target: testCSC took 0.73 sec [au:antunit] Build File: /srv/gump/public/workspace/ant-antlibs/dotnet/src/tests/antunit/wsdl2dotnet-test.xml [au:antunit] Tests run: 15, Failures: 0, Errors: 0, Time elapsed: 3.462 sec [au:antunit] Target: testSchemaMustBeSet took 0.023 sec [au:antunit] Target: testLocalWsdlVB took 0.021 sec [au:antunit] Target: testInvalidExtraOps took 0.008 sec [au:antunit] Target: testSrcIsMissing took 0.088 sec [au:antunit] Target: testNoParams took 0.016 sec [au:antunit] Target: testBothSrc took 0.014 sec [au:antunit] Target: testSchemaFileMustHaveOneOptionOnly took 0.025 sec [au:antunit] Target: testLocalWsdl took 1.439 sec [au:antunit] Target: testSrcIsDir took 0.026 sec [au:antunit] Target: testLocalWsdlServerVB took 0.01 sec [au:antunit] Target: testLocalWsdlServer took 1.407 sec [au:antunit] Target: testNoSrc took 0.022 sec [au:antunit] Target:
[EMAIL PROTECTED]: Project test-ant (in module ant) failed
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 test-ant has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 40 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - test-ant : Java based build tool Full details are available at: http://vmgump.apache.org/gump/public/ant/test-ant/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/ant/test-ant/gump_work/build_ant_test-ant.html Work Name: build_ant_test-ant (Type: Build) Work ended in a state of : Failed Elapsed: 11 mins 29 secs Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true -Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xalan/build/serializer.jar:/srv/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dtest.haltonfailure=false -Dant.home=/srv/gump/public/workspace/ant/dist run-tests [Working Directory: /srv/gump/public/workspace/ant] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant/build/testcases:/srv/gump/public/workspace/ant/src/tests/junit:/srv/gump/public/workspace/ant/src/etc/testcases:/srv/gump/public/workspace/ant/build/lib/ant-stylebook.jar:/srv/gump/public/workspace/ant/build/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/build/lib/ant-swing.jar:/srv/gump/public/workspace/ant/build/lib/ant-junit.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/build/lib/ant-javamail.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-bcel.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-regexp.jar:/srv/gump/public/workspace/ant/build/lib/ant-trax.jar:/srv/gump/public/workspace/ant/build/lib/ant-commons-net.jar:/srv/gump/public/workspace/ant/build/lib/ant-jsch.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-log4j.jar:/srv/gump/public/workspace/ant/build/lib/ant-antlr.jar:/srv/gump/public/workspace/ant/build/li b/ant-commons-logging.jar:/srv/gump/public/workspace/ant/build/lib/ant-jdepend.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-bsf.jar:/srv/gump/public/workspace/ant/build/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/build/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-oro.jar:/srv/gump/public/workspace/ant/build/lib/ant.jar:/srv/gump/public/workspace/ant/build/lib/ant-jai.jar:/srv/gump/packages/antlr-2.7.6/antlr.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-22022008.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-22022008.jar:/srv/gump/public/workspace/apache-commons/net/dist/commons-net-22022008.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/public/workspace/jakarta-bcel/target/bcel-5.3-SNAPSHOT.jar:/srv/gump/public/workspace/jakarta-bsf/build/lib/bsf.jar:/srv/gump/public/workspace/logging-log4j-12/dist/lib/log4j-22022008.jar:/srv/gump/public/workspace/jakarta- oro/jakarta-oro-22022008.jar:/srv/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-22022008.jar:/srv/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jdepend-2.6/lib/jdepend.jar:/srv/gump/packages/jsch/jsch-0.1.28.jar:/srv/gump/public/workspace/xml-stylebook/bin/stylebook-1.0-b3_xalan-2.jar:/srv/gump/public/workspace/ant-antlibs/antunit/build/ant-antunit-22022008.jar:/srv/gump/public/workspace/junit/dist/junit-22022008.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/jakarta-tomcat-4.0/dist/common/lib/jasper-compiler.jar:/srv/gump/public/workspace/jakarta-tomcat-4.0/dist/common/lib/jasper-runtime.jar:/srv/gump/public/workspace/xml-commons/java/build/which.jar:/srv/gump/public/workspace/rhino/build/rhino_22022008/js.jar:/srv/gump/packages/bsh-2.0b4/bsh-commands-2.0b4.jar:/srv/gump/packages/bsh- 2.0b4/bsh-classpath-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-core-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-bsf-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-reflect-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-util-2.0b4.jar:/srv/gump/public/workspace/apache-commons/codec/dist/commons-codec-22022008.jar -
[EMAIL PROTECTED]: Project test-ant-no-xerces (in module ant) failed
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 test-ant-no-xerces has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 40 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - test-ant-no-xerces : Java based build tool Full details are available at: http://vmgump.apache.org/gump/public/ant/test-ant-no-xerces/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/ant/test-ant-no-xerces/gump_work/build_ant_test-ant-no-xerces.html Work Name: build_ant_test-ant-no-xerces (Type: Build) Work ended in a state of : Failed Elapsed: 11 mins 10 secs Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dtest.haltonfailure=false -Dant.home=/srv/gump/public/workspace/ant/dist run-tests [Working Directory: /srv/gump/public/workspace/ant] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant/build/testcases:/srv/gump/public/workspace/ant/src/tests/junit:/srv/gump/public/workspace/ant/src/etc/testcases:/srv/gump/public/workspace/ant/build/lib/ant-stylebook.jar:/srv/gump/public/workspace/ant/build/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/build/lib/ant-swing.jar:/srv/gump/public/workspace/ant/build/lib/ant-junit.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/build/lib/ant-javamail.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-bcel.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-regexp.jar:/srv/gump/public/workspace/ant/build/lib/ant-trax.jar:/srv/gump/public/workspace/ant/build/lib/ant-commons-net.jar:/srv/gump/public/workspace/ant/build/lib/ant-jsch.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-log4j.jar:/srv/gump/public/workspace/ant/build/lib/ant-antlr.jar:/srv/gump/public/workspace/ant/build/li b/ant-commons-logging.jar:/srv/gump/public/workspace/ant/build/lib/ant-jdepend.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-bsf.jar:/srv/gump/public/workspace/ant/build/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/build/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/build/lib/ant-apache-oro.jar:/srv/gump/public/workspace/ant/build/lib/ant.jar:/srv/gump/public/workspace/ant/build/lib/ant-jai.jar:/srv/gump/packages/antlr-2.7.6/antlr.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-22022008.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-22022008.jar:/srv/gump/public/workspace/apache-commons/net/dist/commons-net-22022008.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/public/workspace/jakarta-bcel/target/bcel-5.3-SNAPSHOT.jar:/srv/gump/public/workspace/jakarta-bsf/build/lib/bsf.jar:/srv/gump/public/workspace/logging-log4j-12/dist/lib/log4j-22022008.jar:/srv/gump/public/workspace/jakarta- oro/jakarta-oro-22022008.jar:/srv/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-22022008.jar:/srv/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jdepend-2.6/lib/jdepend.jar:/srv/gump/packages/jsch/jsch-0.1.28.jar:/srv/gump/public/workspace/xml-stylebook/bin/stylebook-1.0-b3_xalan-2.jar:/srv/gump/public/workspace/ant-antlibs/antunit/build/ant-antunit-22022008.jar:/srv/gump/public/workspace/junit/dist/junit-22022008.jar:/srv/gump/public/workspace/jakarta-tomcat-4.0/dist/common/lib/jasper-compiler.jar:/srv/gump/public/workspace/jakarta-tomcat-4.0/dist/common/lib/jasper-runtime.jar:/srv/gump/public/workspace/xml-commons/java/build/which.jar:/srv/gump/public/workspace/rhino/build/rhino_22022008/js.jar:/srv/gump/packages/bsh-2.0b4/bsh-commands-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-classpath-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-core-2.0b4.ja r:/srv/gump/packages/bsh-2.0b4/bsh-bsf-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-reflect-2.0b4.jar:/srv/gump/packages/bsh-2.0b4/bsh-util-2.0b4.jar:/srv/gump/public/workspace/apache-commons/codec/dist/commons-codec-22022008.jar - at org.apache.tools.ant.Project.executeTargets(Project.java:1176) at org.apache.tools.ant.Main.runBuild(Main.java:758) at org.apache.tools.ant.Main.startAnt(Main.java:217) at org.apache.tools.ant.Main.start(Main.java:179) at
[jira] Created: (IVYDE-79) Loading config causes BuildException and eclipse freaks out
Loading config causes BuildException and eclipse freaks out --- Key: IVYDE-79 URL: https://issues.apache.org/jira/browse/IVYDE-79 Project: IvyDE Issue Type: Bug Components: classpath container Affects Versions: 1.3.0 Environment: eclipse 3.3.1.1, openSuse 10.3 Reporter: Jonathan Doklovic When I set the ivy settings file in preferences, I get an error in eclipse. It seems like ivyde has problems parsing my settings file even though it works fine from ant. Unfortunately, the error in eclipse is: java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildException so i can't really get at the real issue. The error occurs anytime ivyde needs to parse the settings. For space sake, here's the stack trace when i try to resolve: !ENTRY org.eclipse.core.jobs 4 2 2008-02-22 13:05:28.439 !MESSAGE An internal error occurred during: Resolve all dependencies. !STACK 0 java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildException at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) at java.lang.Class.getConstructor0(Class.java:2699) at java.lang.Class.newInstance0(Class.java:326) at java.lang.Class.newInstance(Class.java:308) at org.apache.ivy.util.Configurator.addChild(Configurator.java:548) at org.apache.ivy.util.Configurator.startCreateChild(Configurator.java:477) at org.apache.ivy.core.settings.XmlSettingsParser.startElement(XmlSettingsParser.java:177) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501) at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:179) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1337) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2740) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:508) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) at javax.xml.parsers.SAXParser.parse(SAXParser.java:198) at org.apache.ivy.core.settings.XmlSettingsParser.doParse(XmlSettingsParser.java:92) at org.apache.ivy.core.settings.XmlSettingsParser.parse(XmlSettingsParser.java:84) at org.apache.ivy.core.settings.IvySettings.load(IvySettings.java:350) at org.apache.ivy.Ivy.configure(Ivy.java:254) at org.apache.ivyde.eclipse.IvyPlugin.refreshIvyConfiguration(IvyPlugin.java:289) at org.apache.ivyde.eclipse.IvyPlugin.getIvy(IvyPlugin.java:209) at org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer.computeClasspathEntries(IvyClasspathContainer.java:524) at org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer.resolve(IvyClasspathContainer.java:548) at org.apache.ivyde.eclipse.ui.actions.ResolveAllAction$1.run(ResolveAllAction.java:43) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.lang.ClassNotFoundException: org.apache.tools.ant.BuildException at java.lang.ClassLoader.findClass(ClassLoader.java:358) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:429) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:369) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:357) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) ... 31 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (IVY-739) Retain original dependency constraint rules in resolved ivy file
Retain original dependency constraint rules in resolved ivy file Key: IVY-739 URL: https://issues.apache.org/jira/browse/IVY-739 Project: Ivy Issue Type: New Feature Reporter: Shawn Castrianni ivy file metadata is lost when an ivy file is delivered since it resolves all constraint rules into specific revision numbers for publishing. This metadata should be retained by allowing a new attribute on the dependency tag, perhaps called original. Then deliver can resolve all constraint rules to place in the rev attribute but retain the original rule in the original attribute. I am not exactly sure if this is how it should be implemented but it shows the idea. Here is another explanation: keep two versions information per dependency when publishing to the repository : the original version constraint, and the version that was used when the module was published. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (IVY-741) Enhance report task such that dependency graphs can show the original constraint rule on graph edges and resolved specific revision number on graph nodes
Enhance report task such that dependency graphs can show the original constraint rule on graph edges and resolved specific revision number on graph nodes - Key: IVY-741 URL: https://issues.apache.org/jira/browse/IVY-741 Project: Ivy Issue Type: New Feature Reporter: Shawn Castrianni After IVY-739 is resolved, ivy will have new metadata that keeps the original constraint rule metadata in published/delivered ivy files. This can be used to enhance the report task. Right now, if you run the report, you can see the dependency constraint rules for the direct dependencies of the module you are reporting on, but all of the indirect (transitive) dependencies are hardcoded to their specific resolved revision numbers. Having this extra metadata could allow the report task to put the original dependency constraint rules on all the edges in the graph and the resolved specific revision numbers inside all of the nodes like it has now. In my opinion, that is a better report of the dependencies of a module. It shows the constraint rule used and the actual revision found for all nodes in the graph. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
