That's what I have ended up doing. Some projects don't need struts and do
use commons-xxxx, so I've ended up with duplicates where a jar may be in
the 'struts' group as well as in it's own group. I still wonder how other
people do it considering that the ibiblio repository is not strutured like
that.
[EMAIL PROTECTED]
08/05/2004 08:40
Please respond to "Maven Users List"
To: "Maven Users List" <[EMAIL PROTECTED]>
cc:
Subject: Re: compatible jars
Why not just use a groupId of struts for the commons jars?
--
dIon Gillard, Multitask Consulting
"James Hughes" <[EMAIL PROTECTED]> wrote on 07/05/2004 11:43:39 PM:
> Does Maven provide a mechanism for documenting/specifying compatible
> artifacts across groups in a repository?
>
> For example, the struts distribution bundles a number of jars from
jakarta
> commons. This implies that the struts jar/runtime depends on particular
> versions of the commons jars, but if I am putting struts into my local
> repository for the first time I have to split up this grouping into it's
> constituents, thus losing the implicit documentation of strut's
> dependencies. Now when I come back in a year's time to create a new
> project which uses struts, I have to figure out the compatible jars from
> scratch. Is there anything in Maven to help me with this problem?
>
> Thanks,
> James.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
