Jason,
After doing bootstrap, the geronimo-deployment-plugin that was being
used was the one that was downloaded from the repo. So it worked
fine.
It either never built the changes I had made to the local copy or
never used the changes I made.
But after rebuilding the g-d-p again, I see the same NPE again !!!
Here's the patch with the changes I made. I have also attached the
basic itests poms that will act as the framework. Please review.
Apply the startServer.patch and build it.
Unzip the itests-1.0.zip and run mvn in it.
About the StartServerMojo:
---------------------------------------
It works by simply piping both stdout and stderr of the geronimo
start
command back to the mvn process. It can silenced by using the
-Dquiet=true option.
The -DlogOutput option can be used to log the stdout and stderr of
the
Geronimo start command to a surefire xml file
(Note: The cargo plugin does seem to allow to capture the output of
the goals. But then we'd have to run another plugin to convert that
output to surefire like format. Neverthless, I shall look at the
cargo
plugin soon. But for now, we can go with what we have and know it
works)
Thanx
Prasad
---------- Forwarded message ----------
From: Jason Dillon <[EMAIL PROTECTED]>
Date: Aug 28, 2006 7:21 PM
Subject: Re: Error with geronimo-deployment-plugin ?
To: [email protected]
I have seen some problems that go away after a `mvn clean && mvn`
(not mvn clean install though)... dunno why off hand, something is
trying to intelligently cache something... and ends up being rather
stupid.
But... good that it fixed itself... wish more of it would do that.
I have also seen some similar unexpected breakage and magical fixes
that come about due to folks updating SNAPSHOTS or releasing new
versions of plugins where we are not listing the versions explicitly.
:-(
--jason
On Aug 28, 2006, at 4:15 PM, Prasad Kashyap wrote:
> Another bootstrap just did the trick. It fixed itself. Like a
windows
> reboot ? ;-)
>
> Cheers
> Prasad
>
> On 8/28/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
>> OK.. here are the logs with -X
>>
>> describe.log is generated for the help:describe plugin on the
>> startServer goal.
>>
>> startServer.log is generated for executing the startServer goal
>> directly.
>>
>> Cheers
>> Prasad
>>
>> On 8/28/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
>> > Is this the full exception? is this with -X
>> >
>> > --jason
>> >
>> >
>> > On Aug 28, 2006, at 12:44 PM, Prasad Kashyap wrote:
>> >
>> > > If the mojo extends directly from the AbstractMojo.. it
works.
>> > >
>> > > It fails when it extends from MojoSupport in genesis:plugin-
>> > > support :-(
>> > >
>> > > Cheers
>> > > Prasad
>> > >
>> > > On 8/28/06, Prasad Kashyap <[EMAIL PROTECTED]>
wrote:
>> > >> I am suspecting an error with our geronimo-deployment-plugin.
>> > >>
>> > >> Invoking any of the goals directly from the throws an NPE.
>> > >> java.lang.NullPointerException
>> > >> at
>> > >> org.apache.maven.plugin.descriptor.PluginDescriptor.getMojo
>> > >> (PluginDescriptor.java:259)
>> > >> at
>> > >>
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor
>> > >> (DefaultLifecycleExecutor.java:1524)
>> > >>
>> > >>
>> > >> Invoking the help:describe on the goals throws the same NPE.
>> > >>
>> > >> Reusing the same goal(mojo) in another plugin works.
>> > >>
>> > >> I am going to go thro 1252 lines of it's effective pom.
>> Meanwhile if
>> > >> someone can spot something out of the ordinary, please
holler.
>> > >>
>> > >> Thanx
>> > >> Prasad
>> > >>
>> > >>
>> > >>
>> >
>> >
>>
>>
>>
