I agree that first variant seems to be better and easier to implement
(that is why it is first).
J.B.
Rafal Krzewski wrote:
Juraj Burian wrote:
For example, when running JBoss AOP it is necessary to supply
classpath where aspects are found and a different classpath where
classes that should be weaved are (ie. 2 different classpath).
We can see 2 possible solutions:
1) Adding properties to dependency (as in Maven1). That could be used
to distinguish between different dependency groups.
2) Adding group attribute to <depencies> xml tag and allowing to have
more than one <dependencies> sections. group attribute would be
propagated to individual dependency objects.
3) any other idea?
In our opinion this "dependency grouping" may be required in many
plugins (JBoss AOP, AspectJ, APT, ...).
Do you reckon that an artifact - dependency group is one-to-one or
one-to-many? If one-to-many, adding a property will require less
copy&paste in the POMs. I also think that adding a property does no
require POM schema change at all, in contrast to the other option.
R.
---------------------------------------------------------------------
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]
