You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by Andy Piper <an...@bea.com> on 2007/08/15 18:10:17 UTC
Problems with ivy:install
I'm having problems with install. I use virtual modules which seems
to cause install some problems, but if I try and set haltonunresolved
I get the following.
Any clues?
andy
BUILD FAILED
g:\weblogic\dev\wlevs\common\build-ce-repo.xml:10: ivy:install
doesn't support t
he "haltonunresolved" attribute
at
org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfig
urable.java:400)
at
org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfig
urable.java:349)
at org.apache.tools.ant.Task.maybeConfigure(Task.java:202)
at
org.apache.tools.ant.UnknownElement.configure(UnknownElement.java:193
)
at
org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.jav
a:160)
at org.apache.tools.ant.Task.perform(Task.java:347)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe
cutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
at org.apache.tools.ant.Main.runBuild(Main.java:698)
at org.apache.tools.ant.Main.startAnt(Main.java:199)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
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.
Re: Problems with ivy:install
Posted by Gilles Scokart <gs...@gmail.com>.
try the ant -v or -d option. It should give more info.
Gilles
2007/8/15, Andy Piper <an...@bea.com>:
> At 17:49 15/08/2007, Xavier Hanin wrote:
> >Which version of Ivy are you using? haltonunresolved was introduced in 2.0..
>
> alpha 2
>
> >BTW, which kind of problem are you having with ivy:install? Is it some
> >unresolved modules? If this is the case, have you tried a simple resolve
> >instead of an install (using the inline resolve for example). This could
> >help narrowing down the problem.
>
> I'm not sure it gives no output just says it failed. I am assuming
> that some modules are unresolved since some are in a different
> resolver which I do not specify in the install tag.
>
> 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.
>
--
Gilles SCOKART
Re: Problems with ivy:install
Posted by Andy Piper <an...@bea.com>.
haltonfailure fixes the error - thanks
I still don't get anything published however :(
andy
At 08:13 16/08/2007, Xavier Hanin wrote:
>On 8/15/07, Andy Piper <an...@bea.com> wrote:
> >
> > At 17:49 15/08/2007, Xavier Hanin wrote:
> > >Which version of Ivy are you using? haltonunresolved was introduced in
> > 2.0..
> >
> > alpha 2
>
>
>It seems this is a documentation bug, the attribute has been renamed
>haltonfailure for consistency with other tasks, but the documentation has
>not been updated. You can try with haltonfailure="true" instead, and could
>you open an issue for that in JIRA?
>
>Xavier
>
> >BTW, which kind of problem are you having with ivy:install? Is it some
> > >unresolved modules? If this is the case, have you tried a simple resolve
> > >instead of an install (using the inline resolve for example). This could
> > >help narrowing down the problem.
> >
> > I'm not sure it gives no output just says it failed. I am assuming
> > that some modules are unresolved since some are in a different
> > resolver which I do not specify in the install tag.
> >
> > 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.
Re: Problems with ivy:install
Posted by Xavier Hanin <xa...@gmail.com>.
On 8/29/07, Andy Piper <an...@bea.com> wrote:
>
> At 15:09 29/08/2007, Xavier Hanin wrote:
> > > So you are saying that it should work, assuming my repositories and
> > > specification are correct?
> >
> >
> >Yes !
>
> Ok, I think the feature is broken then
Ok, so let's try to see how it's broken, since it works in most cases, it's
maybe you've found a specific case. Could you give more details about your
setup: settings file, snippets of build.xml, description of your
repositories and workspace? Then we could try to see if it's broken and how,
or if you've something wrong with your setup.
Xavier
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/
Re: Problems with ivy:install
Posted by Andy Piper <an...@bea.com>.
At 15:09 29/08/2007, Xavier Hanin wrote:
> > So you are saying that it should work, assuming my repositories and
> > specification are correct?
>
>
>Yes !
Ok, I think the feature is broken then
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.
Re: Problems with ivy:install
Posted by Xavier Hanin <xa...@gmail.com>.
On 8/29/07, Andy Piper <an...@bea.com> wrote:
>
> At 13:38 29/08/2007, Xavier Hanin wrote:
> >I think there's a problem of vocabulary. In Ivy terminology, you always
> >install from a repository *to* another one. Here you're talking about
> >installing from A and B. But to which repository?
> >
> >1. Without ivy:retrieve, nothing from B gets installed.
> >
> >
> >If install means copied from one repo to another, this is possible to do
> >with the install task. But you need to specify a chain of A and B as
> source
> >and another repo as destination.
>
> This is exactly what I have. A chain of A and B, but still nothing
> gets installed from B to my taregt. I am trying to install to shared
> (if it matters).
It should work if you have the module and its dependencies in your chain,
and specify the chain as source repo, Ivy should be able to install your
module and dependencies into your target repo.
>2. With ivy:retrieve everything gets installed from both A and B (but
> > > A is the repo I specified in the install task)
> >
> >Retrieve is used to copy artifacts to a loca destination (which can later
> be
> >used as a repository, but it's unknown by Ivy at the moment of the
> retrieve
> >call).
>
> ? I think this is my point. I understand what ivy:retrieve does, I
> don't understand why it has _any affect at all_ on what ivy:install
> does. The two are not conceptually related and yet clearly, based on
> my experiments, there are side effects of one to the other.
There shouldn't be too much side effects between the two except that the two
download files to your cache at one moment so if you use the same cache for
both operations, it will speed up the second one. It may even make the
second one work while without it wouldn't if a module is made available in
your cache by the first while it isn't accessible for the second operation.
>3. If I specify B as the repo in the install task then the build
> > > fails and nothing is installed.
> >
> >
> >Maybe it's because is lacking information about where to find information
> >about your modules, because B is not enough. The install task is very
> >similar to an inline resolve using only one repository, followed by a
> >publish of bunch of modules. If the resolve with only one repository does
> >not work, the install won't work.
>
> So you are saying that it should work, assuming my repositories and
> specification are correct?
Yes !
>For consistency I would expect either:
> > >
> > > a. For (2) only transitive modules in A to be installed
> > >
> > > or
> > >
> > > b. (3) to succeed and the source repo to be ignored when transitive
> > > is set to true.
> > >
> > > But, for the record, I don't want (a), I want (b). (2) is close
> > > enough, except that I would expect there to be an implicit retrieve.
> >
> >
> >I think you're confusing what install and retrieve are meant for. I don't
> >say they're obvious, but I think that by combining the resolve, retrieve
> and
> >install tasks you have a pretty flexible set of tools, with which you
> should
>
> I agree, but what is their relationship? I cannot find any
> documentation on how retrieve affects install. I think if I
> understood that then all would become clear.
They affect each other because they use the same cache. If you use a
different cache for each, they shouldn't have any side effects (except that
install make some modules available in one repo that may then be used by
retrieve).
HTH,
Xavier
>be able to do what you want. Maybe if you explained what you want to do, we
> >could help by explaining which tasks are better suited?
>
> 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/
Re: Problems with ivy:install
Posted by Andy Piper <an...@bea.com>.
At 13:38 29/08/2007, Xavier Hanin wrote:
>I think there's a problem of vocabulary. In Ivy terminology, you always
>install from a repository *to* another one. Here you're talking about
>installing from A and B. But to which repository?
>
>1. Without ivy:retrieve, nothing from B gets installed.
>
>
>If install means copied from one repo to another, this is possible to do
>with the install task. But you need to specify a chain of A and B as source
>and another repo as destination.
This is exactly what I have. A chain of A and B, but still nothing
gets installed from B to my taregt. I am trying to install to shared
(if it matters).
>2. With ivy:retrieve everything gets installed from both A and B (but
> > A is the repo I specified in the install task)
>
>Retrieve is used to copy artifacts to a loca destination (which can later be
>used as a repository, but it's unknown by Ivy at the moment of the retrieve
>call).
? I think this is my point. I understand what ivy:retrieve does, I
don't understand why it has _any affect at all_ on what ivy:install
does. The two are not conceptually related and yet clearly, based on
my experiments, there are side effects of one to the other.
>3. If I specify B as the repo in the install task then the build
> > fails and nothing is installed.
>
>
>Maybe it's because is lacking information about where to find information
>about your modules, because B is not enough. The install task is very
>similar to an inline resolve using only one repository, followed by a
>publish of bunch of modules. If the resolve with only one repository does
>not work, the install won't work.
So you are saying that it should work, assuming my repositories and
specification are correct?
>For consistency I would expect either:
> >
> > a. For (2) only transitive modules in A to be installed
> >
> > or
> >
> > b. (3) to succeed and the source repo to be ignored when transitive
> > is set to true.
> >
> > But, for the record, I don't want (a), I want (b). (2) is close
> > enough, except that I would expect there to be an implicit retrieve.
>
>
>I think you're confusing what install and retrieve are meant for. I don't
>say they're obvious, but I think that by combining the resolve, retrieve and
>install tasks you have a pretty flexible set of tools, with which you should
I agree, but what is their relationship? I cannot find any
documentation on how retrieve affects install. I think if I
understood that then all would become clear.
>be able to do what you want. Maybe if you explained what you want to do, we
>could help by explaining which tasks are better suited?
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.
Re: Problems with ivy:install
Posted by Xavier Hanin <xa...@gmail.com>.
On 8/29/07, Andy Piper <an...@bea.com> wrote:
>
> At 07:40 29/08/2007, Xavier Hanin wrote:
> >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.
>
> So I'm still not convinced that what is happening in logical.
> I have two repositories A and B. A only contains virtual modules. B
> contains the real artifacts I am interested in. I tell ivy to install
> modules from A and include transitive dependencies (which are all in
> B). I observe the following.
I think there's a problem of vocabulary. In Ivy terminology, you always
install from a repository *to* another one. Here you're talking about
installing from A and B. But to which repository?
1. Without ivy:retrieve, nothing from B gets installed.
If install means copied from one repo to another, this is possible to do
with the install task. But you need to specify a chain of A and B as source
and another repo as destination.
2. With ivy:retrieve everything gets installed from both A and B (but
> A is the repo I specified in the install task)
Retrieve is used to copy artifacts to a loca destination (which can later be
used as a repository, but it's unknown by Ivy at the moment of the retrieve
call).
3. If I specify B as the repo in the install task then the build
> fails and nothing is installed.
Maybe it's because is lacking information about where to find information
about your modules, because B is not enough. The install task is very
similar to an inline resolve using only one repository, followed by a
publish of bunch of modules. If the resolve with only one repository does
not work, the install won't work.
For consistency I would expect either:
>
> a. For (2) only transitive modules in A to be installed
>
> or
>
> b. (3) to succeed and the source repo to be ignored when transitive
> is set to true.
>
> But, for the record, I don't want (a), I want (b). (2) is close
> enough, except that I would expect there to be an implicit retrieve.
I think you're confusing what install and retrieve are meant for. I don't
say they're obvious, but I think that by combining the resolve, retrieve and
install tasks you have a pretty flexible set of tools, with which you should
be able to do what you want. Maybe if you explained what you want to do, we
could help by explaining which tasks are better suited?
Xavier
andy
>
>
>
> >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.
>
>
> 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/
Re: Problems with ivy:install
Posted by Andy Piper <an...@bea.com>.
At 07:40 29/08/2007, Xavier Hanin wrote:
>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.
So I'm still not convinced that what is happening in logical.
I have two repositories A and B. A only contains virtual modules. B
contains the real artifacts I am interested in. I tell ivy to install
modules from A and include transitive dependencies (which are all in
B). I observe the following.
1. Without ivy:retrieve, nothing from B gets installed.
2. With ivy:retrieve everything gets installed from both A and B (but
A is the repo I specified in the install task)
3. If I specify B as the repo in the install task then the build
fails and nothing is installed.
For consistency I would expect either:
a. For (2) only transitive modules in A to be installed
or
b. (3) to succeed and the source repo to be ignored when transitive
is set to true.
But, for the record, I don't want (a), I want (b). (2) is close
enough, except that I would expect there to be an implicit retrieve.
andy
>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.
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.
Re: Problems with ivy:install
Posted by Xavier Hanin <xa...@gmail.com>.
On 8/29/07, Andy Piper <an...@bea.com> wrote:
>
> At 07:40 29/08/2007, Xavier Hanin wrote:
> >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
>
> I am doing this for performance since always accessing the network
> for repository artifacts is very slow (and the artifacts in question
> change very infrequently).
Performance reason is a good reason too, but then you have to keep your
repositories in sync. Using a proxy for this may be a better alternative;
even though for the moment there is now proxy dedicated to Ivy, and maven
specific ones are not usable with Ivy, but it's something we plan to fix.
Xavier
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/
Re: Problems with ivy:install
Posted by Andy Piper <an...@bea.com>.
At 07:40 29/08/2007, Xavier Hanin wrote:
>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
I am doing this for performance since always accessing the network
for repository artifacts is very slow (and the artifacts in question
change very infrequently).
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.
Re: Problems with ivy:install
Posted by Xavier Hanin <xa...@gmail.com>.
On 8/28/07, Andy Piper <an...@bea.com> 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 <an...@bea.com> 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/
Re: Problems with ivy:install
Posted by Andy Piper <an...@bea.com>.
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?
andy
At 13:32 28/08/2007, Xavier Hanin wrote:
>On 8/28/07, Andy Piper <an...@bea.com> 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.
Re: Problems with ivy:install
Posted by Xavier Hanin <xa...@gmail.com>.
On 8/28/07, Andy Piper <an...@bea.com> 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/
Re: Problems with ivy:install
Posted by Andy Piper <an...@bea.com>.
So ant -v reveals:
[ivy:install] == resolving dependencies [ apache | ivy-install | 1.0
]->[ featur
e | com.bea.core.ce | 3.0 ] [default->*]
[ivy:install] :: downloading artifacts to cache ::
[ivy:install] :: installing in shared ::
[ivy:install] :: install resolution report ::
---------------------------------------------------------------------
| | modules || artifacts |
| conf | number| search|dwnlded|evicted|| number|dwnlded|
---------------------------------------------------------------------
| default | 1 | 0 | 0 | 0 || 0 | 0 |
---------------------------------------------------------------------
[ivy:install] WARN: ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:install] WARN: :: UNRESOLVED DEPENDENCIES ::
[ivy:install] WARN: ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:install] WARN: :: [ feature | com.bea.core.ce | 3.0 ]: not found
[ivy:install] WARN: ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:install] report for [ apache | ivy-install | 1.0 ] default
produced in C:
\Documents and Settings\Andrew Piper\.ivy2\cache\apache-ivy-install-default.xml
Which is weird because a normal resolve works fine. The module is
defined in the ivy.xml file in the current directory. Is there
something special about where install expects modules to be defined?
For reference the ivy.xml looks something like this:
<?xml version="1.0" encoding="UTF-8"?>
<ivy-module xmlns:feature="http://www.bea.com/ns/cie/feature"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.0"
xsi:noNamespaceSchemaLocation="http://incubator.apache.org/ivy/schemas/ivy.xsd">
<info organisation="feature" module="com.bea.core.ce" revision="3.0"/>
<publications/>
<dependencies>
<dependency org="feature" name="com.bea.core.base"
rev="latest.integration" conf="default->com.bea.core.base"/>
</dependencies>
</ivy-module>
Thanks
andy
At 13:28 28/08/2007, Andy Piper 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.
>
>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.
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.
Re: Problems with ivy:install
Posted by Andy Piper <an...@bea.com>.
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.
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.
Re: Problems with ivy:install
Posted by Andy Piper <an...@bea.com>.
At 15:01 29/08/2007, Xavier Hanin wrote:
>No, they don't need to be there. They have to in a repository, either remote
>or local, it doesn't matter. During the install process, Ivy will first
>download them to your local disk, then publish them to the target
>repository.
Its not doing this.
So, a bug?
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.
Re: Problems with ivy:install
Posted by Xavier Hanin <xa...@gmail.com>.
On 8/29/07, Andy Piper <an...@bea.com> wrote:
>
> At 13:39 29/08/2007, Xavier Hanin wrote:
> >No, install is only made to copy modules from one repository to another.
> >That's all. It is not meant to copy them to your local disk, which is the
> >purpose of retrieve.
>
> Right, but I don't want/need them on my local disk, but the
> transitive dependencies seem to have to be there to get installed.
No, they don't need to be there. They have to in a repository, either remote
or local, it doesn't matter. During the install process, Ivy will first
download them to your local disk, then publish them to the target
repository.
Xavier
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/
Re: Problems with ivy:install
Posted by Andy Piper <an...@bea.com>.
At 13:39 29/08/2007, Xavier Hanin wrote:
>No, install is only made to copy modules from one repository to another.
>That's all. It is not meant to copy them to your local disk, which is the
>purpose of retrieve.
Right, but I don't want/need them on my local disk, but the
transitive dependencies seem to have to be there to get installed.
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.
Re: Problems with ivy:install
Posted by Xavier Hanin <xa...@gmail.com>.
On 8/29/07, Andy Piper <an...@bea.com> wrote:
>
> At 07:42 29/08/2007, Xavier Hanin wrote:
> >If you don't call retrieve, the dependencies won't be retrieved... But
> I'm
> >not sure to get your question. Could you elaborate about what you do and
> >what you expect?
>
> Shouldn't ivy:install do an implicit retrieve? Basically without
> doing a retrieve, install says it succeeded but does not install any
> transitive dependencies.
No, install is only made to copy modules from one repository to another.
That's all. It is not meant to copy them to your local disk, which is the
purpose of retrieve.
Xavier
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/
Re: Problems with ivy:install
Posted by Andy Piper <an...@bea.com>.
At 07:42 29/08/2007, Xavier Hanin wrote:
>If you don't call retrieve, the dependencies won't be retrieved... But I'm
>not sure to get your question. Could you elaborate about what you do and
>what you expect?
Shouldn't ivy:install do an implicit retrieve? Basically without
doing a retrieve, install says it succeeded but does not install any
transitive dependencies.
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.
Re: Problems with ivy:install
Posted by Xavier Hanin <xa...@gmail.com>.
On 8/28/07, Andy Piper <an...@bea.com> wrote:
>
> I am having another problem with this in that unless I have done an
> ivy:retrieve first then none of the transitive dependencies are
> retrieved or copied. Is this to be expected?
If you don't call retrieve, the dependencies won't be retrieved... But I'm
not sure to get your question. Could you elaborate about what you do and
what you expect?
Xavier
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/
Re: Problems with ivy:install
Posted by Andy Piper <an...@bea.com>.
I am having another problem with this in that unless I have done an
ivy:retrieve first then none of the transitive dependencies are
retrieved or copied. Is this to be expected?
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.
Re: Problems with ivy:install
Posted by Andy Piper <an...@bea.com>.
https://issues.apache.org/jira/browse/IVY-599
At 08:13 16/08/2007, Xavier Hanin wrote:
>On 8/15/07, Andy Piper <an...@bea.com> wrote:
> >
> > At 17:49 15/08/2007, Xavier Hanin wrote:
> > >Which version of Ivy are you using? haltonunresolved was introduced in
> > 2.0..
> >
> > alpha 2
>
>
>It seems this is a documentation bug, the attribute has been renamed
>haltonfailure for consistency with other tasks, but the documentation has
>not been updated. You can try with haltonfailure="true" instead, and could
>you open an issue for that in JIRA?
>
>Xavier
>
> >BTW, which kind of problem are you having with ivy:install? Is it some
> > >unresolved modules? If this is the case, have you tried a simple resolve
> > >instead of an install (using the inline resolve for example). This could
> > >help narrowing down the problem.
> >
> > I'm not sure it gives no output just says it failed. I am assuming
> > that some modules are unresolved since some are in a different
> > resolver which I do not specify in the install tag.
> >
> > 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.
Re: Problems with ivy:install
Posted by Xavier Hanin <xa...@gmail.com>.
On 8/15/07, Andy Piper <an...@bea.com> wrote:
>
> At 17:49 15/08/2007, Xavier Hanin wrote:
> >Which version of Ivy are you using? haltonunresolved was introduced in
> 2.0..
>
> alpha 2
It seems this is a documentation bug, the attribute has been renamed
haltonfailure for consistency with other tasks, but the documentation has
not been updated. You can try with haltonfailure="true" instead, and could
you open an issue for that in JIRA?
Xavier
>BTW, which kind of problem are you having with ivy:install? Is it some
> >unresolved modules? If this is the case, have you tried a simple resolve
> >instead of an install (using the inline resolve for example). This could
> >help narrowing down the problem.
>
> I'm not sure it gives no output just says it failed. I am assuming
> that some modules are unresolved since some are in a different
> resolver which I do not specify in the install tag.
>
> 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/
Re: Problems with ivy:install
Posted by Andy Piper <an...@bea.com>.
At 17:49 15/08/2007, Xavier Hanin wrote:
>Which version of Ivy are you using? haltonunresolved was introduced in 2.0..
alpha 2
>BTW, which kind of problem are you having with ivy:install? Is it some
>unresolved modules? If this is the case, have you tried a simple resolve
>instead of an install (using the inline resolve for example). This could
>help narrowing down the problem.
I'm not sure it gives no output just says it failed. I am assuming
that some modules are unresolved since some are in a different
resolver which I do not specify in the install tag.
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.
Re: Problems with ivy:install
Posted by Xavier Hanin <xa...@gmail.com>.
On 8/15/07, Andy Piper <an...@bea.com> wrote:
>
> I'm having problems with install. I use virtual modules which seems
> to cause install some problems, but if I try and set haltonunresolved
> I get the following.
> Any clues?
Which version of Ivy are you using? haltonunresolved was introduced in 2.0..
.
BTW, which kind of problem are you having with ivy:install? Is it some
unresolved modules? If this is the case, have you tried a simple resolve
instead of an install (using the inline resolve for example). This could
help narrowing down the problem.
Xavier
andy
>
> BUILD FAILED
> g:\weblogic\dev\wlevs\common\build-ce-repo.xml:10: ivy:install
> doesn't support t
> he "haltonunresolved" attribute
> at
> org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfig
> urable.java:400)
> at
> org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfig
> urable.java:349)
> at org.apache.tools.ant.Task.maybeConfigure(Task.java:202)
> at
> org.apache.tools.ant.UnknownElement.configure(UnknownElement.java:193
> )
> at
> org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.jav
> a:160)
> at org.apache.tools.ant.Task.perform(Task.java:347)
> at org.apache.tools.ant.Target.execute(Target.java:357)
> at org.apache.tools.ant.Target.performTasks(Target.java:385)
> at
> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
> at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe
> cutor.java:41)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
> at org.apache.tools.ant.Main.runBuild(Main.java:698)
> at org.apache.tools.ant.Main.startAnt(Main.java:199)
> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
>
>
> 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/