...@free.fr]
Gesendet: Dienstag, 2. August 2011 19:44
An: Maven Developers List
Betreff: Re: AW: PlexusContainer#lookupList(role) returns only one component
I recently used lookupMap API [1] to detect which wagon providers was
available in m-site-p 3.0
It worked like a charm
Regards
: PlexusContainer#lookupList(role) returns only one component
To: dev@maven.apache.org
Date: Wednesday, August 3, 2011, 6:22 AM
Sadly, this doesn't work for my case.
I have several components with exactly the same role and
hint, e.g. role=IFooListener.class, hint=default.
Using lookupMap returns a map
Developers List
Betreff: Re: AW: AW: PlexusContainer#lookupList(role) returns only one
component
If you like to distinguish them, what JSR-330 mechanism do you use?
Qualifiers? There must be a
precedence rule somehow...
LieGrue,
strub
--- On Wed, 8/3/11, bernd.v...@bosch-si.com bernd.v
Nachricht-
Von: Mark Struberg [mailto:strub...@yahoo.de]
Gesendet: Mittwoch, 3. August 2011 10:56
An: Maven Developers List
Betreff: Re: AW: AW: PlexusContainer#lookupList(role)
returns only one component
If you like to distinguish them, what JSR-330
mechanism do you use? Qualifiers
Nachricht-
Von: Mark Struberg [mailto:strub...@yahoo.de]
Gesendet: Mittwoch, 3. August 2011 10:56
An: Maven Developers List
Betreff: Re: AW: AW: PlexusContainer#lookupList(role)
returns only one component
If you like to distinguish them, what JSR-330
mechanism do you use? Qualifiers
]
Gesendet: Mittwoch, 3. August 2011 10:56
An: Maven Developers List
Betreff: Re: AW: AW: PlexusContainer#lookupList(role) returns only one component
If you like to distinguish them, what JSR-330 mechanism do you use? Qualifiers?
There must be a
precedence rule somehow...
LieGrue,
strub
--- On Wed, 8/3
).
-Ursprüngliche Nachricht-
Von: Igor Fedorenko [mailto:i...@ifedorenko.com]
Gesendet: Mittwoch, 3. August 2011 11:46
An: dev@maven.apache.org
Betreff: Re: AW: AW: AW: PlexusContainer#lookupList(role) returns only one
component
Wouldn't it be easier to use fully qualified
Hello Everybody,
I just noticed that PlexusContainer#lookupList(role) will only return a
list with one component even there are two components available for the
role. After playing around I figured out that the method returns a list
with both components when I use different hints in my component
In plexus role+hint forms a composite key. In your case, you had a
component conflict, and Plexus stashed one component over another
(it's undefined which wins, but probably depends on classpath
ordering or so). If you want Plexus to manage them as two distinct
components, you have to make them
I'm using the SISU-plexus-shim (sisu-inject-plexus-2.1.1).
In plexus role+hint forms a composite key. In your case, you had a
component conflict, and Plexus stashed one component over another
(it's undefined which wins, but probably depends on classpath
ordering or so).
Sure, I expected this
Inline.
On Tue, Aug 2, 2011 at 12:05 PM, bernd.v...@bosch-si.com wrote:
In plexus role+hint forms a composite key. In your case, you had a
component conflict, and Plexus stashed one component over another
(it's undefined which wins, but probably depends on classpath
ordering or so).
Sure,
: Re: PlexusContainer#lookupList(role) returns only one component
To: Maven Developers List dev@maven.apache.org
Date: Tuesday, August 2, 2011, 10:52 AM
Inline.
On Tue, Aug 2, 2011 at 12:05 PM, bernd.v...@bosch-si.com
wrote:
In plexus role+hint forms a composite key. In
your case, you had
It might be a safe route to use JSR-330 only, but it's still not
guaranteed.
Currently, I'm trying to figure out how I can use (and possibly mix up)
sisu-plexus with plain JSR-330 components.. any hints?
The thing is, that the IoC container of the environment I'm running in
is sisu-plexus and
still be the plexus way.
LieGrue,
strub
--- On Tue, 8/2/11, bernd.v...@bosch-si.com bernd.v...@bosch-si.com wrote:
From: bernd.v...@bosch-si.com bernd.v...@bosch-si.com
Subject: AW: PlexusContainer#lookupList(role) returns only one component
To: dev@maven.apache.org
Date: Tuesday, August 2
On 2 Aug 2011, at 13:33, bernd.v...@bosch-si.com wrote:
It might be a safe route to use JSR-330 only, but it's still not
guaranteed.
Currently, I'm trying to figure out how I can use (and possibly mix up)
sisu-plexus with plain JSR-330 components.. any hints?
The thing is, that the IoC
BTW, which environment are you running in?
Maven 3.0.3 :-)
Currently, I'm developing a Maven Core extension (see
apache-maven-3.0.3/lib/ext/README.txt) that extends Maven with an
extensible generator framework that is intended to generate Maven poms
and other artifacts for non-Maven projects
I recently used lookupMap API [1] to detect which wagon providers was
available in m-site-p 3.0
It worked like a charm
Regards,
Hervé
[1] http://plexus.codehaus.org/plexus-containers/plexus-container-
default/apidocs/org/codehaus/plexus/PlexusContainer.html#lookupMap(java.lang.Class)
Le mardi
17 matches
Mail list logo
