callers and for extenders).
> -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
>
[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?
There must be a
precedence rule somehow...
LieG
/javase/6/docs/api/java/util/ServiceLoader.html
[2] http://download.oracle.com/javaee/6/api/javax/inject/package-summary.html
--- On Wed, 8/3/11, bernd.v...@bosch-si.com wrote:
> From: bernd.v...@bosch-si.com
> Subject: AW: AW: AW: PlexusContainer#lookupList(role) returns only one
> compo
/javase/6/docs/api/java/util/ServiceLoader.html
[2] http://download.oracle.com/javaee/6/api/javax/inject/package-summary.html
--- On Wed, 8/3/11, bernd.v...@bosch-si.com wrote:
> From: bernd.v...@bosch-si.com
> Subject: AW: AW: AW: PlexusContainer#lookupList(role) returns only one
> compo
1 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
lexus container.
> With this approach I could use simple JSR330 API without
> losing the plexus components.
>
> > -Ursprüngliche Nachricht-
> > Von: Hervé BOUTEMY [mailto:herve.bout...@free.fr]
> > Gesendet: Dienstag, 2. August 2011 19:44
> > An: Maven Developers
chricht-
> Von: Hervé BOUTEMY [mailto:herve.bout...@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
&
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
> 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 be
On 2 Aug 2011, at 13:33, 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 container of the
uld indeed still be the plexus way.
LieGrue,
strub
--- On Tue, 8/2/11, bernd.v...@bosch-si.com wrote:
> From: bernd.v...@bosch-si.com
> Subject: AW: PlexusContainer#lookupList(role) returns only one component
> To: dev@maven.apache.org
> Date: Tuesday, August 2, 2011, 12:33 PM
> &
> 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 I
upList(role) returns only one component
> To: "Maven Developers List"
> Date: Tuesday, August 2, 2011, 10:52 AM
> Inline.
>
> On Tue, Aug 2, 2011 at 12:05 PM,
> wrote:
> >> In plexus role+hint forms a "composite key". In
> your case, you had a
>
Inline.
On Tue, Aug 2, 2011 at 12:05 PM, 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, I expected
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 expect
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
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
d
17 matches
Mail list logo
