On 8/28/07, Andy Piper <[EMAIL PROTECTED]> wrote: > > So I have now resolved this. It seems that the "from" repository > needs to specify _exactly_ which repository the required module is in > even though chaining seems to be honoured. Is this logical? Surely > transitive="true" kind of implies that the artifact should be > installed from wherever it is found?
No, transitive="true" indicates that not only the module but also its dependencies must be installed (i.e. copied from one repository to another). If you're looking for a way to publish one module to a repository (equivalent to maven 2 install goal), use the publish task. This won't copy the dependencies of the module though, but the dependencies must already be in a repository. In your case, you could publish your module the ce-repository, and then install it and its dependencies from ce-repository to shared, if it's really what you want. Note that usually you use install only when you want to setup an enterprise repository that will be accessed by the team(s), and create its content from another repository (maybe a public one, or a legacy one) that you don't want the team to access. Otherwise you can use the heterogeneous repositories directly from Ivy. HTH, Xavier andy > > At 13:32 28/08/2007, Xavier Hanin wrote: > >On 8/28/07, Andy Piper <[EMAIL PROTECTED]> wrote: > > > > > > So now to my real problem - nothing is installed. > > > > > > My build directive looks like this: > > > > > > > > > <target name="publish" depends="configure, clean-build"> > > > <ivy:install from="ce-repository" to="shared" > > > organisation="feature" > > > haltonfailure="false" > > > module="com.bea.core.ce" revision="3.0" > > > overwrite="true" transitive="true"/> > > > </target> > > > > > > my ivy file contains this module, but it is a virtual dependency (no > > > publications) and its dependencies are also virtual. It is only the > > > third layer down that actually specifies any real artifacts. However > > > the transitive="true" setting should ensure they get copied right? > > > Right now I get nothing, although the build successfully completes. > > > > > > Any help appreciated. > > > > > >Could you give more detail about your settings, and what is available in > >your repositories. The install task is used to copy modules and their > >dependencies from one repository to another one. So before calling > install > >you should have the com.bea.core.ce module properly available with all > its > >dependencies in your ce-repository. Is it your case? > > > >If you want more help, posting some of your output may help us find what > can > >be wrong. > > > >Xavier > > > >Thanks > > > > > > andy > > > > > > > > > Notice: This email message, together with any attachments, may > contain > > > information of BEA Systems, Inc., its > subsidiaries and affiliated > > > entities, that may be > confidential, proprietary, copyrighted and/or > > > legally privileged, and is intended solely for the use of the > individual or > > > entity named in this message. If you are not the intended recipient, > and > > > have received this message in error, please immediately return > > this by email > > > and then delete it. > > > > > > > > > > >-- > >Xavier Hanin - Independent Java Consultant > >http://xhab.blogspot.com/ > >http://incubator.apache.org/ivy/ > >http://www.xoocode.org/ > > > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual or > entity named in this message. If you are not the intended recipient, and > have received this message in error, please immediately return this by email > and then delete it. > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://incubator.apache.org/ivy/ http://www.xoocode.org/
