Juraj Burian wrote:
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?
I'm not sure which piece you are missing here. The configuration is a
list of strings, fr
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 ar
Sorry for the delay in responding. See comments below.
Juraj Burian wrote:
Hi Brett,
I want to take opportunity to talk with you and discuss more than this
case.
Firstly, from my point of view flag optional is named unhappily.
Better name would be transitive/nontransitive with the default val
Hi Brett,
I want to take opportunity to talk with you and discuss more than this case.
Firstly, from my point of view flag optional is named unhappily.
Better name would be transitive/nontransitive with the default value
true/false .
BTW look at : http://jira.codehaus.org/browse/MNG-1205 (bug
We hadn't planned to overload scope like this, and for similar reasons
to not adding properties - they don't hold up under transitivity because
it requires that the dependency knows something about the final project,
which is impossible.
The scope provides a sensible default for most operations (b
Rafal Krzewski wrote:
Juraj Burian wrote:
We are working on jboss-aop & APT plugins implementation.
We encountered the folowing problem (in general):
We need to split classpath into several parts. In other words, we
need to group dependencies.
For example, when running JBoss AOP it is neces
Juraj Burian wrote:
We are working on jboss-aop & APT plugins implementation.
We encountered the folowing problem (in general):
We need to split classpath into several parts. In other words, we need
to group dependencies.
For example, when running JBoss AOP it is necessary to supply classpath
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 shou
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).
Hi,
We are working on jboss-aop & APT plugins implementation.
We encountered the folowing problem (in general):
We need to split classpath into several parts. In other words, we need
to group dependencies.
For example, when running JBoss AOP it is necessary to supply classpath
where aspects ar
10 matches
Mail list logo
