ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus M. May" <m...@gmx.net>
Subject Re: Sharing inter-project dependencies
Date Tue, 29 Aug 2006 06:15:00 GMT
Hello once again,

you have already got an answer and you pointed out the point (versioning), which is pretty
hard (IMHO) to solve. We have three different repositories:

- Development (which contains always the Latest and Greatest Snapshot of all components)
- Maintainance (which contains components,which are in production use and are in a bugfixing
state.)
- QS (which contains all components in the production version)

The problem with this approach is, that the version of the component has to be in the component,
because a component A can have version 1.2 and be reference by another component B (Verison
2.3) and component B (Version 2.1) references component A in version 1.1. Therefor, every
classpath has to be in the Configuration Management System (e.g. Subversion). In our case
we have the problem that one component can have multiple versions in production. 

R,

Markus


-------- Original-Nachricht --------
Datum: Tue, 29 Aug 2006 08:03:20 +0200
Von: "Markus M. May" <mmay@gmx.net>
An: "Ant Users List" <user@ant.apache.org>
Betreff: Re: Sharing inter-project dependencies

> Hello Michael,
> 
> we are solving this, by having a central repository (pretty much like the
> maven repository) which contains all JAR-files of all components. Therefor
> you can then reference a fileset with all neede files from the repository. 
> The hard thing is, that the components can change their version and then
> component A is dependend from component B Version x.y. Somebody has to
> reference these correctly.
> 
> I hope this helps a little.
> 
> R,
> 
> Markus
> 
> 
> -------- Original-Nachricht --------
> Datum: Mon, 28 Aug 2006 12:14:22 -0700
> Von: "Nau, Michael" <Michael.Nau@cardinal.com>
> An: user@ant.apache.org
> Betreff: Sharing inter-project dependencies
> 
> > I have a project with two java components: componentA and componentB.
> > ComponentB had a compile-time dependency on componentA.
> > 
> > I've read many posts\articles on how to setup a master build script to
> > manage the build process for both components. So far so good. But when I
> > get to the point where I need to setup the compile classpath for
> > componentB... I stumble on how to reference componentA. Two options are:
> > 
> > 1. Setup ComponentB's build script reference the componentA/build/class
> > dir.
> > Advantage: Straightforward
> > Disadvantage: componentB has internal knowledge of componentA's
> > project's layout | componentB can not be build independently
> > 
> > 2. Have the master build script copy componentA.jar into the
> > componentB/lib or root/lib and add the path to componentB's compile
> > classpath.
> > Advantage: componentB has no knowledge of componentA's project layout
> > Disadvantage: componentB can not be build independently
> > 
> > How are other handling this?
> > 
> > -Mike
> > 
> > _________________________________________________
> > 
> > This message is for the designated recipient only and may contain
> > privileged, proprietary, or otherwise private information. If you have
> received it
> > in error, please notify the sender immediately and delete the original.
> Any
> > other use of the email by you is prohibited.
> > 
> > Dansk - Deutsch - Espanol - Francais - Italiano - Japanese - Nederlands
> -
> > Norsk - Portuguese - Svenska: www.cardinalhealth.com/legal/email
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> > For additional commands, e-mail: user-help@ant.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Mime
View raw message