You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ju...@bnpparibas.com on 2005/04/12 09:45:12 UTC
xml entities and maven 2
Hi,
Regarding xml entities and maven 2
(http://maven.apache.org/faq.html#using-entities)
Here we use external dependencies and project inheritrance for two reasons
:
* because we just don't want to add all the dependencies to the root
project but only to the ones requiring them so the external entities permit
us to do it and to be sure to use consistent versions among projects
* as we have a non-trivial number of projects, external entites permit us
to have consistent project dependencies between our projects, in this case
we just can't have the dependencies in the root project (as the projects
being build inherit from it)
Furthermore I don't understand the "ability to be reproduced from a history
at any point in time" thing because as the dependies file is in the VCS
just as the project.xml files, their are just historized the same way.
I hope I showed why external dependy usage can not be solved throught
inheritrance, so I would know if this design choice is definitive, and if
it is, how to solve our use case without using them.
Best regards
Julien Kirch
This message and any attachments (the "message") is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
---------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le
"message") sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce
message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce
message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Réf. : Re: xml entities and maven 2
Posted by ju...@bnpparibas.com.
thanks much
This message and any attachments (the "message") is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
---------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le
"message") sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce
message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce
message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: xml entities and maven 2
Posted by Brett Porter <br...@apache.org>.
julien.kirch@bnpparibas.com wrote:
>* because we just don't want to add all the dependencies to the root
>project but only to the ones requiring them so the external entities permit
>us to do it and to be sure to use consistent versions among projects
>
>
<dependencyManagement /> has been introduced for this purpose.
eg:
http://cvs.openejb.codehaus.org/viewrep/openejb/openejb/m2/ejb-group.pom?r=1.7
which is the parent of
http://cvs.openejb.codehaus.org/viewrep/openejb/openejb/m2/ejb-core.pom?r=1.3
(they are not in the correct directory layout at present)
>* as we have a non-trivial number of projects, external entites permit us
>to have consistent project dependencies between our projects, in this case
>we just can't have the dependencies in the root project (as the projects
>being build inherit from it)
>
>
same as above.
In addition, transitive dependencies will greatly reduce the number of
these you need to define...
>Furthermore I don't understand the "ability to be reproduced from a history
>at any point in time" thing because as the dependies file is in the VCS
>just as the project.xml files, their are just historized the same way.
>
>
Yes, but you are unable to get just the project file and be able to use
it effectively. We have other software that does this for zero
configuration setup.
Regards,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org