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 Dave <da...@gmail.com> on 2008/06/04 18:06:55 UTC

Using Ivy with Telelogic Synergy

Hey all,
I believe best practice SCM means keeping your library dependencies under
version control. I'm kind of disappointed to see what limited (is there
any?) support Ivy has for SCM tools. I'm wondering in particular if any has
managed to integrate Ivy with library dependencies managed with Telelogic
Synergy. I've been looking at the IvySVN project (
http://www.audioscrobbler.net/development/ivysvn/)  for a little
inspiration, but would rather not have to port it to work with Synergy if I
can avoid it.

Any help/tips would be appreciated

Regards,
Dave

-- 
There are 10 types of people in the world.
Those who understand binary and those who do not.

Re: Using Ivy with Telelogic Synergy

Posted by Matthias Kilian <ki...@outback.escape.de>.
On Wed, Jun 04, 2008 at 05:44:35PM +0100, Dave wrote:
> As you say it's an opinion, but it does seem to be the case that most
> open-source projects store their dependencies in version control (browse the
> svn repository of any major open-source project and you'll see a lot of
> jars, not just java source).

Yes, most part of the Java world does it, and bloatware like
openoffice do it, yet it's a real disease. And it's becoming a royal
PITA if you discover that for some included dependencies no matching
sources are (no longer) available, or if the included dependencies
have been built from *patched* sources (and the patch is missing).

> dependencies in SVN. So while you are absolutely correct in saying it's an
> opinion, it seems to be an opinion a lot of people agree with including many
> experts.

Show me one expert's argument for this. I don't think there' any
arguments beyond "i'm lazy", "other people do it the same way", "we
don't have a dependency management tool".

> Still though, point taken. Now back to the question at hand....do you have
> any tips for Synergy + Ivy integration ? :-)

Well, I'd do the same as I'm doing currently with CVS: keep an
ivy.xml in the project, check in the code changes of a *delivered*
ivy.xml for each release, and put back an undelivered (i.e. with
revision wildcards in the dependencies) for further development.
This is done with a set of ant tasks.

The concrete method for Synergy/CM would be different and of course
heavily depends on the development model you're using, but I'm sure
it's possible.

Ciao,
	Kili

Re: Using Ivy with Telelogic Synergy

Posted by Dave <da...@gmail.com>.
As you say it's an opinion, but it does seem to be the case that most
open-source projects store their dependencies in version control (browse the
svn repository of any major open-source project and you'll see a lot of
jars, not just java source). Also, most SCM books recommend keeping library
dependencies in SVN. So while you are absolutely correct in saying it's an
opinion, it seems to be an opinion a lot of people agree with including many
experts.
Still though, point taken. Now back to the question at hand....do you have
any tips for Synergy + Ivy integration ? :-)

On Wed, Jun 4, 2008 at 5:34 PM, Fernandes, Gerard <
gerard.fernandes@lehman.com> wrote:

>
> That's your opinion - and everyone is entitled to one :)
>
> However, like the name SCM - Software Change Management - should
> indicate, it should be all about controlling software that you can
> change. In other words - software you have source for and can legally
> change while abiding by it's license.
>
> SCM shouldn't be about built artefacts - which is what a binary
> executable or linked library is. Built artefacts are obtained from their
> sources, who no doubt have appropriate SCM processes to control their
> code. Their code - and by extension, their artefact - should never have
> to be "managed" by you.
>
> Gerard Fernandes
>
> -----Original Message-----
> From: Dave [mailto:davidcorley@gmail.com]
> Sent: 04 June 2008 17:07
> To: ivy-user@ant.apache.org
> Subject: Using Ivy with Telelogic Synergy
>
> Hey all,
> I believe best practice SCM means keeping your library dependencies
> under version control. I'm kind of disappointed to see what limited (is
> there
> any?) support Ivy has for SCM tools. I'm wondering in particular if any
> has managed to integrate Ivy with library dependencies managed with
> Telelogic Synergy. I've been looking at the IvySVN project (
> http://www.audioscrobbler.net/development/ivysvn/)  for a little
> inspiration, but would rather not have to port it to work with Synergy
> if I can avoid it.
>
> Any help/tips would be appreciated
>
> Regards,
> Dave
>
> --
> There are 10 types of people in the world.
> Those who understand binary and those who do not.
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> - - - - - -
>
> This message is intended only for the personal and confidential use of the
> designated recipient(s) named above.  If you are not the intended recipient
> of this message you are hereby notified that any review, dissemination,
> distribution or copying of this message is strictly prohibited.  This
> communication is for information purposes only and should not be regarded as
> an offer to sell or as a solicitation of an offer to buy any financial
> product, an official confirmation of any transaction, or as an official
> statement of Lehman Brothers.  Email transmission cannot be guaranteed to be
> secure or error-free.  Therefore, we do not represent that this information
> is complete or accurate and it should not be relied upon as such.  All
> information is subject to change without notice.
>
>
>
>


-- 
There are 10 types of people in the world.
Those who understand binary and those who do not.

RE: Using Ivy with Telelogic Synergy

Posted by "Fernandes, Gerard" <ge...@lehman.com>.
That's your opinion - and everyone is entitled to one :)

However, like the name SCM - Software Change Management - should
indicate, it should be all about controlling software that you can
change. In other words - software you have source for and can legally
change while abiding by it's license.

SCM shouldn't be about built artefacts - which is what a binary
executable or linked library is. Built artefacts are obtained from their
sources, who no doubt have appropriate SCM processes to control their
code. Their code - and by extension, their artefact - should never have
to be "managed" by you.

Gerard Fernandes

-----Original Message-----
From: Dave [mailto:davidcorley@gmail.com] 
Sent: 04 June 2008 17:07
To: ivy-user@ant.apache.org
Subject: Using Ivy with Telelogic Synergy

Hey all,
I believe best practice SCM means keeping your library dependencies
under version control. I'm kind of disappointed to see what limited (is
there
any?) support Ivy has for SCM tools. I'm wondering in particular if any
has managed to integrate Ivy with library dependencies managed with
Telelogic Synergy. I've been looking at the IvySVN project (
http://www.audioscrobbler.net/development/ivysvn/)  for a little
inspiration, but would rather not have to port it to work with Synergy
if I can avoid it.

Any help/tips would be appreciated

Regards,
Dave

--
There are 10 types of people in the world.
Those who understand binary and those who do not.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

This message is intended only for the personal and confidential use of the designated recipient(s) named above.  If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited.  This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such.  All information is subject to change without notice.