Publish ivy files without artifacts

Hello, Does anybody know if it is possible to publish only the ivy-files and not the artifacts ? I would like to publish the ivy-files in two locations (with different pattern), but the actual artifacts should only be published once. Tx, Marc -- View this message in context:

Re: buildlist and properties in ivy files

We are using buildlist a lot in our buildsystem. We are using it for bottom-up and for top-down builds. For our own (home-made) software modules, the ivy-files we have under version control do not contain any branch or revision information in the info section. And in the dependencies section of

Re: converttopom, pom.xml to ivy.xml conversion and publication artifacts.

parth patel wrote: can you give me an example of such maven pom file? Actually, I never had to look at the maven pom files we converted, and I am not so familiar with them either. But if you google a little bit you will surely find how you can specify the artifacts in a maven pom file.

Re: returnFirst/latest=latest-time not working

Probably the revision numbers in both your repositories are identical ? When Ivy finds in the first repository a specific revision, I think that it will no longer analyse the same revision in your second repository. This may seem strange, but you should know that Ivy relies very much on the fact

Create a report without downloading artifacts to the cache

Hello, I would like to create a dependency report using the ant task repreport. When running this task, I see that it downloads all artifacts of the dependent modules to the cache. In fact the task does a full resolve of all its dependencies. I was wondering if it is possible to create such a

IvyDE update site unavailable ?

Hello, Has anybody else on the forum tried to use the ivyde download site (http://www.apache.org/dist/ant/ivyde/updatesite) recently ? When we select this update site from our Eclipse installations, we receive the following error: http://www.apache.org/dist/ant/ivyde/updatesite; We can access

Re: resolve different dependencies from different locations

You can specify in your ivysettings the resolver that should be used for each module. For example: modules module organisation=A name=* resolver=ibiblio-resolver / module organisation=B name=* resolver=jboss-resolver / /modules Regards, Marc M4N - Jasper Floor wrote: Hi, While I'm

Re: defaultconf attribute in dependencies

Maarten Coene wrote: Looks like a bug, could you create a JIRA issue for this? https://issues.apache.org/jira/browse/IVY thanks, Maarten Done: https://issues.apache.org/jira/browse/IVY-1306 Regards, Marc -- View this message in context:

Re: defaultconf attribute in dependencies

I fixed my problem by replacing the wildcards in the defaultconf-attribute by enumerating all the configurations. So this works correctly when resolving: dependencies defaultconfmapping=* - # defaultconf=compile,rad,ear But the following doesn't work correctly (you get no errors, but the

defaultconf attribute in dependencies

We are using ivy 2.2.0 with ant 1.8.2 on Windows XP. In the ivy.xml file of a module, I have the following configurations and dependencies: configurations conf name=compile/ conf name=test extends=compile / conf name=rad / conf name=ear / conf name=wsdl/

Use ivy-dependencies to create ant-tasks

Hello, We are using an ant-task called wsimport to create java-classes from xml. This wsimport task is defined as follows in our build-file: taskdef name=wsimport classname=com.sun.tools.ws.ant.WsImport classpath refid=jaxws.classpath/ /taskdef Where classpath points to the appropriate

Re: Using ivy.xml files to describe common module information

Jeffrey Sinclair wrote: We have a custom repository at our company and I was looking to provide some meta-data at the 'module' level that would describe common information across all revisions for that module: * /info/@organisation. * /info/@module. * /info/description. *