On 6/27/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
That must be it then, though I don't know how you get a mojo
to be run, declared as an extension..
I am simply following the section on "Specifying a New Packaging" from
http://maven.apache.org/guides/introduction/introduction-to-the-l
That must be it then, though I don't know how you get a mojo
to be run, declared as an extension..
Btw, i hoped for the output to name the realm, but this apparently is
maven 2.0.x. if you could typecast the classloader to ClassRealm
and then call 'getId()' on it, I think you'll find it prints
More info: I cannot reproduce the problem with another Mojo, which
isn't declared as an extension.
--
"Besides, manipulating elections is under penalty of law, resulting in
a preventative effect against manipulating elections.
The german government justifying the use of electronic voting machine
On 6/26/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
Can you add
static { System.out.println( "XXX " + Contextualizable.class + ": " +
Contextualizable.class.getClassLoader() ); }
to your mojo and see what it prints?
Here's the output:
XXX interface
org.codehaus.plexus.personality.pl
Jochen Wiedmann wrote:
On 6/26/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
It must be being pulled in by a dep in the mojo. Is this something
that I can see?
Unfortunately not yet. Shall I file a Jira issue with some sample code?
Can you add
static { System.out.println( "XXX " + Contex
On 6/26/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
It must be being pulled in by a dep in the mojo. Is this something
that I can see?
Unfortunately not yet. Shall I file a Jira issue with some sample code?
Thanks,
Jochen
--
"Besides, manipulating elections is under penalty of law, result
On 25 Jun 07, at 10:16 PM 25 Jun 07, Jochen Wiedmann wrote:
Hi,
from using the debugger, I now know that the Contextualizable
interface in use by the Maven core is from the maven-2.0.7 uber jar,
as suspected. From the jar files info
(META-INF/maven/.../plexus-container-default), this is versio
Hi,
from using the debugger, I now know that the Contextualizable
interface in use by the Maven core is from the maven-2.0.7 uber jar,
as suspected. From the jar files info
(META-INF/maven/.../plexus-container-default), this is version
1.0-alpha-9-stable-1, the same version I am using. Neverthele
On 25 Jun 07, at 4:11 PM 25 Jun 07, Jochen Wiedmann wrote:
On 6/26/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
You probably have the plexus double jar problem. We separated the API
and implementation JARs and you're pulling in an old version of
plexus which has everything and then plugin whi
On 6/26/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
You probably have the plexus double jar problem. We separated the API
and implementation JARs and you're pulling in an old version of
plexus which has everything and then plugin which must be pulling in
the API jar. Because they come from diff
On 25 Jun 07, at 3:01 PM 25 Jun 07, Jochen Wiedmann wrote:
Hi,
I've got a Mojo, which implements the Contextualizable interface.
However, the contextualizable(Context) method is not invoked: When
running maven-2.0.7 in the debugger, I can watch that the
ContextualizePhase is executed, but the
Hi,
I've got a Mojo, which implements the Contextualizable interface.
However, the contextualizable(Context) method is not invoked: When
running maven-2.0.7 in the debugger, I can watch that the
ContextualizePhase is executed, but the check "object instanceof
Contextualizable" fails.
Any ideas,
12 matches
Mail list logo
