Hello,
sorry but I don't understand. Do you have any example or documentation
of this?
Unfortunately I can't find documentation about presented context :-(.
Can you help me, please?
thaks
JuBu
p.s.
I understand your argumentation about properties in artifact.
My idea was, that property in artifact have only information value and
don't have impact on the transitivity.
I mean that a plugin (for example APT) can divide one classpath to two
or more particular classpaths and use it.
Transitivity is managed via "optional" flag as is declared if necessary
or via "provided" scope.
The mentioned properties will not be propagated to the generated poms in
repositories (it is not productive) ....
Of course it's not my faith, I am looking for any solution .... :-)
Brett Porter wrote:
The approach we selected here was to use a particular scope as a
baseline (if appropriate), and then have includes/excludes in the
plugin configuration for selecting dependencies, such as in the EAR
plugin. eg:
<configuration>
<factories>
<factory>groupId:artifactId</factory>
</factories>
</configuration>
This can be selected from the dependency closure, not necessarily the
current POM, but the project declaring it has full control over what
it gets.
But if there is any particular defaults that can be sensibly selected,
they should definitely be selected (for example, WARs bundle all
runtime dependencies by default).
The reason we aren't using groups or properties on dependencies is
because of transitivity: if the property is specified on a dependency
in another project, it is probably not aware that the dependency will
or will not be used for that purpose in another project that depended
on it. Hence the patterns to augment the defaults.
Hope this helps.
Cheers,
Brett
---------------------------------------------------------------------
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]
