[Anthill-pro] Re: transitive dependencies question[tmon-status:ticketId=5102]

Yanko, Curtis curt_yanko at uhc.com
Thu Apr 2 06:57:39 CST 2009


Interesting. We do Use AHP for some dependency management but for
inter-project and not build dependencies. Maven codifies our build
dependencies and creates a BOM that included transitive dependencies and
breaks them down into Compile time, and run time and what we assume is
on the target environment along with the license they are governed
under.

In AHP we just use it to tell something like a WAR that a JAR that it
consumes has been successfully built so it know to rebuild (Push). 


==========
Curtis Yanko
Application & Developer Infrastructure Services
Source->Build->Deploy
W: 860.702.9059
M: 860.881.2050

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Michael
Feinberg
Sent: Wednesday, April 01, 2009 3:56 PM
To: anthill-pro at lists.urbancode.com
Subject: [Anthill-pro] Re: transitive dependencies
question[tmon-status:ticketId=5102]


 > I guess my last question would now be, do you think you could easily
walk away from AHP if you needed to?

That is why my developers think they use ivy. The fact that I go to AH
to get the jars for them is completely  hidden. Yes, they know that they
could go to a fancy AH web page to get all kinds of good information
about the jars ivy pulled in, but the degree to which the two things are
coupled is hidden.

If AH does now work, I can swap it for something else that can populate
ivy repo with numbered artifact.
If ivy does not work, I could pick some other dependency management
system.

So far both are performing fine. Codestation APIs are a bit funny and
not very well documented, but once you get to know them, they are no
better or worse than anything else out there. The big downside are the
QA cycle I need to do every time AH gets upgraded and the fact that with
OSS I know that documentation is going to suck, but one can always read
the code. I do not have this luxury with AH.

I guess you do not use AH's dependency management at all? What system do
you use? How do you manage dependencies? How do you get the map of
artifact usage?

When I started with AH, I was not planning to use its repository at all,
but rather have it be the workflow driver for the build/release
lifecycle. I then came to realize that perhaps AH s good to keep track
of a large base of installed apps; to see what is where and using what;
the lifecycle management support. Those things are outside of the scope
of dependency management system.

_mike



_______________________________________________
Anthill-pro mailing list
Anthill-pro at lists.urbancode.com
http://lists.urbancode.com/mailman/listinfo/anthill-pro

This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.



More information about the Anthill-pro mailing list