ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nappin, Chris (IT Services)" <Chris.Nap...@capita.co.uk>
Subject Shared repository and configurations question
Date Fri, 07 Aug 2009 09:17:34 GMT
Hi,

  I'm currently evaluating ivy and have a question about shared
repositories and configurations.

I've created a simple shared repository intended to be used by a number
of in-house projects. This contains hand-written ivy module dependency
files for each artifact. Each project has a different set of
configurations.

I would like each of the artifacts to be usable by all projects and all
configurations, without having to add a list of all project
configurations to every module dependency file in the shared repository.
My repository shouldn't have to know about every project that is going
to use it. Is this possible, and if so how?

Best Regards,

Chris Nappin
Technical Architect, Application Services
OPSERV - IT Services
Mob:	07824 473044
Part of the Capita Group plc www.capita.co.uk <http://www.capita.co.uk/>
www.capita-its.co.uk <http://www.capita.co.uk/>  

'Evolving a great Operational IT Service through OPSERV'



This email and any attachment are intended solely for the addressee, are strictly confidential
and may be legally privileged. If you are not the intended recipient any reading, dissemination,
copying or any other use or reliance is prohibited. If you have received this email in error
please notify the sender immediately by email and then permanently delete the email. Copyright
reserved.

All communications, incoming and outgoing, may be recorded and are monitored for legitimate
business purposes. 

The security and reliability of email transmission cannot be guaranteed. It is the recipientís
responsibility to scan this e-mail and any attachment for the presence of viruses. 

The Capita Group plc and its subsidiaries ("Capita") exclude all liability for any loss or
damage whatsoever arising or resulting from the receipt, use or transmission of this email.


Any views or opinions expressed in this email are those of the author only.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message