Great !

I'll make test on my side for integrating my plugin with the war plugin for
webapp packaging, and report succes/failure/suggest on this list.

Nico


2007/10/14, Stephane Nicoll <[EMAIL PROTECTED]>:
>
> Hi Nico,
>
> Yes the packaging task is *exactly* meant to provide this
> functionality. I was about to add this to the war plugin actually but
> I wanted a first alpha released first because the packaging code has
> so much changed that I expect regressions.
>
> I'll have a look to the issue you've opened.
>
> Cheers,
> Stéphane
>
> On 10/14/07, nicolas de loof <[EMAIL PROTECTED]> wrote:
> > To be more precise, the change on the war plugin would be :
> >
> > final List packagingTasks = getPackagingTasks( overlayManager );
> >   if ( getContext().contains( WarPackagingTask.CUSTOM_TASKS ) )
> >   {
> >    packagingTasks.addAll( (Collection) getContext().get(
> > WarPackagingTask.CUSTOM_TASKS ) );
> >   }
> > ...
> >
> > final List postPackagingTasks = getPostPackagingTasks();
> >   if ( getContext().contains( WarPackagingTask.CUSTOM_TASKS ) )
> >   {
> >    postPackagingTasks.addAll( (Collection) getContext().get(
> > WarPostPackagingTask.CUSTOM_TASKS ) );
> >   }
> > ...
> >
> > This enhancement would enable plugins to register to the packaging
> process,
> > before the final WAR archive is created. In my case
> (javascript-mavne-tools
> > in Mojo sandbox) I'd like to process and copy some files into the web
> > application root. As there is no pre-package phase in maven 2.0.x this
> > requires interaction between plugins.
> >
> > Nico.
> >
> >
> > 2007/10/14, nicolas de loof <[EMAIL PROTECTED]>:
> > >
> > > Hello,
> > >
> > > I'm looking for a clean way to plug into the war packaging process.
> I'd
> > > like to add some custom Taks to the pacaking, before the .WAR archive
> is
> > > created.
> > >
> > > The war plugin extends AbstractMojo, so implements ContextEnabled.
> > > Based on this, it may be possible for plugins to share some
> configuration
> > > based on this context (AFAIK this is what it is designed for).
> > >
> > > Would you consider searching the context for some custom task and add
> them
> > > to the result of getPackagingTasks() ?
> > >
> > > I can open a Jira and attach a patch for this, but would like your
> opinion
> > > first.
> > >
> > > Nico.
> > >
> > > 2007/10/14, Stephane Nicoll <[EMAIL PROTECTED]>:
> > > >
> > > > We need to patch/Release plexus utils first.
> > > >
> > > > This is a first alpha, I expect others to be released very soon.
> > > >
> > > > Stéphane
> > > >
> > > > On 10/14/07, Tomasz Pik <[EMAIL PROTECTED]> wrote:
> > > > > On 10/14/07, Stephane Nicoll < [EMAIL PROTECTED] > wrote:
> > > > > > I have identified an issue in the latest changes (zip overlays).
> I
> > > > > > have reopened the issue (MWAR-104).  As soon as we address this,
> we
> > > > > > can call a vote.
> > > > >
> > > > > What about MWAR-123?
> > > > > I've tested maven-war-plugin with plexus-utils containing patch
> > > > > attached to http://jira.codehaus.org/browse/PLXUTILS-50
> > > > > and I did not encounter any problem (and filtering with '@'
> > > > > works correctly).
> > > > >
> > > > > And current behavior is very problematic, at least for me.
> > > > >
> > > > > Regards,
> > > > > Tomek
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Large Systems Suck: This rule is 100% transitive. If you build one,
> > > > you suck" -- S.Yegge
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> >
>
>
> --
> Large Systems Suck: This rule is 100% transitive. If you build one,
> you suck" -- S.Yegge
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to