ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <>
Subject [jira] Commented: (IVYDE-139) IvyDE does not work with VFS resolvers
Date Sat, 30 May 2009 11:55:08 GMT


Nicolas Lalevée commented on IVYDE-139:

I have found a good OSGi-enable Apache Common-vfs:

I have done a little test: I put this file into the "dropins" folder of my Eclipse install,
restart my Eclipse, and then Ivy is able to find common-vfs. If you use an Eclipse older than
3.4, putting it into the "plugins" folder should work the same way.

So to make things simple here, I am in favor of just documenting this, with the urls (I am
very confident that the pointed jars will never change or disappear on both orbit and maven
repositories), rather than packaging them into Eclipse features and putting them into the
IvyDE updatesite. Actually the installation process into Eclipse will be similar to the one
into ant.

So could some of you using common-vfs in real settings tells me if it works for him ? Thanks
in advance.

> IvyDE does not work with VFS resolvers
> --------------------------------------
>                 Key: IVYDE-139
>                 URL:
>             Project: IvyDE
>          Issue Type: Bug
>    Affects Versions: 2.0.0.beta1
>            Reporter: Robert Munteanu
>             Fix For:
>         Attachments: ivysettings-custom.xml
>   Original Estimate: 0h
>  Remaining Estimate: 0h
> With a custom settings file which declares a vfs resolver, IvyDE fails hard with a ClassNotFoundException
( below ) and the ivy.xml classpath container dissapears from the project.
> I guess it's a matter of including the right jars from Ivy.
> {code}
> Message: An internal error occurred during: "Resolve project 'project' and ivy file 'ivy.xml'
> Exception stack trace: java.lang.NoClassDefFoundError: org/apache/commons/vfs/FileSystemException
> at org.apache.ivy.plugins.resolver.VfsResolver.<init>(
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
> at java.lang.reflect.Constructor.newInstance(
> at java.lang.Class.newInstance0(
> at java.lang.Class.newInstance(
> at org.apache.ivy.util.Configurator.addChild(
> at org.apache.ivy.util.Configurator.startCreateChild(
> at org.apache.ivy.core.settings.XmlSettingsParser.inConfiguratorStarted(
> at org.apache.ivy.core.settings.XmlSettingsParser.startElement(
> at
> at
> at$
> at
> at
> at
> at
> at
> at
> at$JAXPSAXParser.parse(
> at javax.xml.parsers.SAXParser.parse(
> at javax.xml.parsers.SAXParser.parse(
> at org.apache.ivy.core.settings.XmlSettingsParser.doParse(
> at org.apache.ivy.core.settings.XmlSettingsParser.parse(
> at org.apache.ivy.core.settings.IvySettings.load(
> at org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainerConfiguration.getIvy(
> at org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainerConfiguration.getIvy(
> at
> at
> Caused by: java.lang.ClassNotFoundException: org.apache.commons.vfs.FileSystemException
> at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(
> at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(
> at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(
> at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(
> at java.lang.ClassLoader.loadClass(
> at java.lang.ClassLoader.loadClassInternal(
> ... 30 more
> {code}

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message