ivy

I have a special situation where I need to package up some jars, and I need BOTH versions of a jar. My ivy definitions looks like this: <dependency org="blah" name="blahname" rev="1.0.0" conf="baseline->default" /> I would like the same dependency resolved twice, once with version 1.0.0 and another with say version 2.0.0. Is that possible? What's the easiest way to achieve this. Use ivy configurations to create and manage custom groups of dependencies. Example ivy.xml <ivy-module version="2.0"> <info organisation="com.myspotontheweb" module="demo"/> <configurations> <conf name="group1"

tl;dr version Dependencies of my custom grails plugin weren't getting inherited and resolved by projects I installed the plugin to. Install the latest version of the release plugin to your plugin (fixes the issue for jar dependencies) Clear out any references to plugins that might exist in your BuildConfig.groovy file (fixes the issue for plugin dependencies) grails maven-install to make the plugin available in the mavenLocal() source Long version So, I've been trying to create a custom grails plugin for internal use at my University. I'd really like it if putting the plugin in your

I have found IvyDE which allows me to solve an outstanding problem of having a frozen core version of a web application, which needs to be able to pull in extra code from an update library so it is on the classpath of the web application. For development speed I've found that the "Resolve in Workspace" facility allows Eclipse to put the folders of the update library project directly on the build path of the frozen core web application. Works well for normal Java applications. For Web Applications, however, it seems that WTP (the Eclipse Java EE module) does not deploy the folders denoted by

I'd like to use the Artifact only notation to download a single artifact whose filename is completely different from the module name. My Ivy artifact pattern is configured as: ivy { artifactPattern 'http://host/[organization]/[module]/[revision]/[artifact]-[revision].[ext]' } However, the "Artifact only notation" seem to only support: group (maps to [organization] ), name (maps to [module] ), version (maps to [revision] ), ext (maps to [exp] ) and classifier (maps to [classifier] , not used here). The [artifact] part of the URLs seems to always be replaced with name . Is there a way to

For example, when I open a well developed opensource project (like lucene) into Eclipse (with both ant build.xml and ivy ivysetting.xml), I can run ant with build.xml to build the whole project successfully. However, the project is full of errors in a mess of .java classes. This is caused by unlinking to the external jars. These jars are already download by ivy and stored in {user}/.ivy2/cache/. Also, when I manually put each of these jars into the build path of this project, the errors are gone. Can ivy or ivyDE or some other tools put the jars into the JAVA build path automatically? Here is

I have near zero knowledge of Maven/Ivy but know that these technologies are behind SBT's ability to download and manage libraries automatically. When I was trying to generate an IntelliJ Idea project from SBT it (Idea or the generator plug-in) has failed to find cached libraries stored in the common Ivy 2 cache. I've solved the problem by setting up the SBT project to use the old scheme storing downloaded libraries under the project directory. Another project of mine uses old SBT version which does it this way by default. In both cases I use clean command to remove library binaries before

I'm trying to ivy:install jogl and gluegen from maven to my local depository. I cannot get the native dependencies to install correctly. My ivysettings is <ivysettings> <settings defaultResolver="central" defaultConflictManager="all" /> <caches defaultCacheDir="${ivy.cache.dir}" artifactPattern="[organisation]/[module]/[type]s/[artifact]-[revision](-[classifier]).[ext]" /> <resolvers> <ibiblio name="central" m2compatible="true" pattern="[organisation]/[module]/[revision]/[artifact]-[revision](-[classifier]).[ext]" /> <filesystem name="depository"> <ivy pattern="${dest.repo.dir}/[organisation]/