CIM and ivysettings and absolute paths

2 views
Skip to first unread message

Soupdragon

unread,
Sep 22, 2010, 5:22:05 AM9/22/10
to usr-ivybeans
Like an increasing number of sites we are using a continuous
integration server, an environment quite different from our local
compilation environment (in fact it's unix and our local compilation
is on Windows).

So we can't tolerate absolute paths in the configuration that can't be
overridden on the ant command line.

At the moment I'm putting extra property definitions in the
project.properties file and manually editing in a reference to the
property where the ivy setting absolute path is found. e.g.

<ivy:settings file="${ivy.settings.file}"/>

Trouble is that if I make any changes on the ivy tab of the project
properties it tends to switch it back (it won't accept anything but an
absolute path name on the tab).

Anyone have a more elegant or reliable solution?

Laurent Forêt

unread,
Sep 22, 2010, 6:16:56 AM9/22/10
to usr-iv...@googlegroups.com
Put a relative path to the project or put an url (http maybe file).

BTW, It could/should be an enhancement to ivybeans.

Laurent



--
You received this message because you are subscribed to the Google Groups "usr-ivybeans" group.
To post to this group, send email to usr-iv...@googlegroups.com.
To unsubscribe from this group, send email to usr-ivybeans...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/usr-ivybeans?hl=en.


Soupdragon

unread,
Sep 22, 2010, 8:34:24 AM9/22/10
to usr-ivybeans


On Sep 22, 11:16 am, Laurent Forêt <laurent.fo...@gmail.com> wrote:
> Put a relative path to the project or put an url (http maybe file).
>

Really doesn't help. The point is that the ivysettings file is
different in the two environments. That's the way it should be, all
the settings peculiar to the environment should be in one location
outside of all the project directories, and the build directory should
contain nothing specific to the build environment. The build directory
shouldn't need to know where it is. In this case the Bamboo agents
that are our CIM environment run on the cloud, not even on our LAN.
(I'm storing our private repository on Amazon S3)

Ideally you should be able to code the settings as, say ${user.home}/
ivysettings.xml



Laurent Forêt

unread,
Sep 22, 2010, 8:36:14 AM9/22/10
to usr-iv...@googlegroups.com
Ok. I totally agree. So please fill a new issue. 


Laurent Forêt
http://www.devcoop.fr,
http://laurentforet.org
IvyBeans Creator
Membre du JUG Bordeaux





--

Bruce Chapman

unread,
Sep 24, 2010, 1:35:32 AM9/24/10
to usr-iv...@googlegroups.com
Laurent Forêt wrote:
Ok. I totally agree. So please fill a new issue.

I have already committed changes on issue 70 ( http://code.google.com/p/ivybeans/issues/detail?id=70 ) that put the ivysettings (file or url) and description file name in to project.properties.

So if you build from trunk, and regenerate the ivy-impl.xml file you can then override that property when building on your CI server.

Malcolm, does that help?

Bruce

Laurent Forêt

unread,
Sep 24, 2010, 3:40:51 AM9/24/10
to usr-iv...@googlegroups.com
This is the issue I was looking for . And I was pretty sure that you have done something on that, but I did not find it.

Thanks Bruce, I am going to close the duplicate issue.

Laurent Forêt
http://www.devcoop.fr,
http://laurentforet.org
IvyBeans Creator
Membre du JUG Bordeaux


Reply all
Reply to author
Forward
0 new messages