[jira] Commented: (IVYDE-79) Loading config causes BuildException and eclipse freaks out
[ https://issues.apache.org/jira/browse/IVYDE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572830#action_12572830 ] Nicolas Lalevée commented on IVYDE-79: -- So does IVYDE-80 fixed this one ? 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
[jira] Created: (IVY-748) Exclude Ant jar from bin-with-deps distribution format
Exclude Ant jar from bin-with-deps distribution format -- Key: IVY-748 URL: https://issues.apache.org/jira/browse/IVY-748 Project: Ivy Issue Type: Task Reporter: Xavier Hanin Fix For: 2.0 Currently we package in bin-with-deps distribution all Ivy dependencies, including ant jar. But this doesn't make sense, people who want to use Ivy with Ant will first install Ant, then Ivy. So we should exclude ant jar from our bin-with-deps distributions format. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (IVY-747) add license to .patterns files
add license to .patterns files -- Key: IVY-747 URL: https://issues.apache.org/jira/browse/IVY-747 Project: Ivy Issue Type: Task Reporter: Xavier Hanin Fix For: 2.0 As reported by Stefan, .patterns files do not have license header yet -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-748) Exclude Ant jar from bin-with-deps distribution format
[ https://issues.apache.org/jira/browse/IVY-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572844#action_12572844 ] Xavier Hanin commented on IVY-748: -- The bin distrib already use a pretty similar mechanism, just less user friendly: in the bin distrib we provide ivy.jar, and a build.xml using ivy.jar to download the dependencies described in the ivy.xml. This requires to have Ant installed as well. But I like your idea of a webstart installer based on Ivy itself to download the dependencies required per profile. Exclude Ant jar from bin-with-deps distribution format -- Key: IVY-748 URL: https://issues.apache.org/jira/browse/IVY-748 Project: Ivy Issue Type: Task Reporter: Xavier Hanin Fix For: 2.0 Currently we package in bin-with-deps distribution all Ivy dependencies, including ant jar. But this doesn't make sense, people who want to use Ivy with Ant will first install Ant, then Ivy. So we should exclude ant jar from our bin-with-deps distributions format. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-748) Exclude Ant jar from bin-with-deps distribution format
[ https://issues.apache.org/jira/browse/IVY-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572842#action_12572842 ] Jan Matèrne commented on IVY-748: - An installer would be fine: Ivy ;) A bootstrap Ivy download without any dependency and working from commandline and a starter which asks for the dependency to load and then load them. Maybe some profiles: command line - Ant - IvyDE - all ... the starter could also be a WebStart application (just thinking loud ...) Exclude Ant jar from bin-with-deps distribution format -- Key: IVY-748 URL: https://issues.apache.org/jira/browse/IVY-748 Project: Ivy Issue Type: Task Reporter: Xavier Hanin Fix For: 2.0 Currently we package in bin-with-deps distribution all Ivy dependencies, including ant jar. But this doesn't make sense, people who want to use Ivy with Ant will first install Ant, then Ivy. So we should exclude ant jar from our bin-with-deps distributions format. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-742) Support ivy.xml parent mechanism
[
https://issues.apache.org/jira/browse/IVY-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572955#action_12572955
]
Niklas Matthies commented on IVY-742:
-
Here is a similar proposal I made on the ivy-user mailing list:
bq. Provide an inclusion facility for ivy files to semantically include/merge
the contents of some other ivy file, similar as include for the settings
files. Possibly add an attribute to choose what to do in case of
conflicting/non-mergeable specs.
I believe that it's more useful to do this as inclusion rather than as
inheritance. It would also be in anology the the inclusion mechanism of ivy
settings files.
Support ivy.xml parent mechanism
Key: IVY-742
URL: https://issues.apache.org/jira/browse/IVY-742
Project: Ivy
Issue Type: New Feature
Components: Core
Environment: Any
Reporter: Neil Lott
Here's the email that details this feature:
On Thu, Feb 21, 2008 at 11:22 PM, Neil Lott [EMAIL PROTECTED]
wrote:
Let's say I have multiple modules each with their own ivy.xml
ivy-module version=2.0
info organisation=${organization.name} module=$
{interface.jar.prefix}/
configurations
conf name=interface description=dependencies for
interface/
include file=path/to/included-configurations.xml/
/configurations
publications
artifact name=${interface.jar.prefix} type=jar
conf=interface ext=jar/
/publications
dependencies
dependency org=twc name=mas-core rev=${mas.version}
conf=interface-server/
/dependencies
/ivy-module
and I want them all to share an inherited configuration found in a
file: included-configurations.xml
configuration
conf name=test/
/configuration
dependencies
dependency name=testng rev=5.7 conf=test/
/dependencies
so in the inherited configurations file I'd also like to include a
dependency that goes along with that configuration.
Is something like this possible?
No, this is not possible in Ivy, but you can use text or xml processing
tools to recompose your Ivy file before asking Ivy to resolve the
dependencies of your module.
Alternatively, since what you ask is close to maven 2 parent mechanism, I
think it could be a nice addition to Ivy feature set. So feel free to open
an issue, and even provide a patch :-)
Xavier
Thanks,
Neil
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[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 55 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 50 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-27022008.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-27022008.jar:/srv/gump/public/workspace/apache-commons/net/dist/commons-net-27022008.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-27022008.jar:/srv/gump/public/workspace/jakarta- oro/jakarta-oro-27022008.jar:/srv/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-27022008.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-27022008.jar:/srv/gump/public/workspace/junit/dist/junit-27022008.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_27022008/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-27022008.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: (IVY-750) XML schema ambiguity
XML schema ambiguity Key: IVY-750 URL: https://issues.apache.org/jira/browse/IVY-750 Project: Ivy Issue Type: Bug Affects Versions: 2.0.0-beta-2 Reporter: Adrian Sandor While running ivy built from svn, trying to resolve an ivy file, I got this message: [Error] :43:30: cos-nonambig: :license and WC[##any] (or elements from their substitution group) violate Unique Particle Attribution. During validation against this schema, ambiguity would be created for those two particles. It doesn't seem to affect the functionality. Xavier commented: this probably due to the xs:any we have added in the info tag definition in our xsd. Adding a namespace=##other to the xs:any to tell the parser that any element *from other namespace* is allowed should fix the problem Also see IVY-156 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-750) XML schema ambiguity
[ https://issues.apache.org/jira/browse/IVY-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572989#action_12572989 ] Adrian Sandor commented on IVY-750: --- Looks like jira interpreted ##any between square brackets as a link XML schema ambiguity Key: IVY-750 URL: https://issues.apache.org/jira/browse/IVY-750 Project: Ivy Issue Type: Bug Affects Versions: 2.0.0-beta-2 Reporter: Adrian Sandor While running ivy built from svn, trying to resolve an ivy file, I got this message: [Error] :43:30: cos-nonambig: :license and WC[##any] (or elements from their substitution group) violate Unique Particle Attribution. During validation against this schema, ambiguity would be created for those two particles. It doesn't seem to affect the functionality. Xavier commented: this probably due to the xs:any we have added in the info tag definition in our xsd. Adding a namespace=##other to the xs:any to tell the parser that any element *from other namespace* is allowed should fix the problem Also see IVY-156 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (IVY-751) SFTPRepository.list(String) hides exceptions
SFTPRepository.list(String) hides exceptions
Key: IVY-751
URL: https://issues.apache.org/jira/browse/IVY-751
Project: Ivy
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0-beta-1, 2.0.0-beta-2
Reporter: Adrian Sandor
With an sftp repository, if any connection or authentication problem happens,
the error is hidden and the code behaves as if the action succeeded but nothing
was found. This makes it very hard to identify the problem and fix the
configuration.
I tracked the issue to the list method in SFTPRepository, where I found:
catch (Exception e) {
// silent fail, return null listing
}
I would change the code to something like this:
catch (SftpException e) {
IOException ioe = new IOException();
ioe.initCause(e);
throw ioe;
}
so any exception will be thrown as an IOException.
I'm sure there are other options too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (IVY-752) Wrong error message for republishing a module
Wrong error message for republishing a module - Key: IVY-752 URL: https://issues.apache.org/jira/browse/IVY-752 Project: Ivy Issue Type: Bug Components: Core Affects Versions: 2.0.0-beta-1, 2.0.0-beta-2 Reporter: Adrian Sandor Priority: Minor If the overwrite attribute is not set to true and I try to republish a module, I get this message: destination file exists and overwrite == true however, it should be: destination file exists and overwrite == false or something equivalent to that. This appears in SFTPRepository and SshRepository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (IVY-753) Compatibility with maven's dependencyMangement
Compatibility with maven's dependencyMangement -- Key: IVY-753 URL: https://issues.apache.org/jira/browse/IVY-753 Project: Ivy Issue Type: Improvement Components: Maven Compatibility Reporter: Harald Braumann Priority: Minor Maven supports a dependencyManagement section in the parent pom which allows one to override versions of both, direct and transitive, dependencies. Ivy currently lacks such a support. A discussion about this issue can be found here: http://mail-archives.apache.org/mod_mbox/ant-ivy-user/200802.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
