plugins disabled when using m2 build ?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

plugins disabled when using m2 build ?

nicolas de loof-2
Hello,

I'm migrating a project from maven 1 to maven 2

Using the maven1 build script I've enabled "Abort the build if it's stuck" option, from the time-out plugin.
I also have options displayed for other plugins (xvnc for example)

Configuring a maven2 build I don't have those options anymore... and this is an issue for me as my build creates an Oracle lock and doesn't end...

What's wrong with maven2 and plugins ?

Nico.
Reply | Threaded
Open this post in threaded view
|

Re: plugins disabled when using m2 build ?

stephenconnolly
Use the freestyle project type and build with Maven

The Maven2 project type is a "magic" project type that does everything
it's own way.

This basically means that each plugin must do more work to work with it

I keep on trying to use the Maven2 project type and finding it
inadequate and returning to the freestyle project type.

You'll have more control with the freestyle (but more control means
more configuration)

-Stephen

On 11/27/07, nicolas de loof <[hidden email]> wrote:

> Hello,
>
> I'm migrating a project from maven 1 to maven 2
>
> Using the maven1 build script I've enabled "Abort the build if it's stuck"
> option, from the time-out plugin.
> I also have options displayed for other plugins (xvnc for example)
>
> Configuring a maven2 build I don't have those options anymore... and this is
> an issue for me as my build creates an Oracle lock and doesn't end...
>
> What's wrong with maven2 and plugins ?
>
> Nico.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: plugins disabled when using m2 build ?

Kohsuke Kawaguchi
Administrator
Stephen Connolly wrote:

> Use the freestyle project type and build with Maven
>
> The Maven2 project type is a "magic" project type that does everything
> it's own way.
>
> This basically means that each plugin must do more work to work with it
>
> I keep on trying to use the Maven2 project type and finding it
> inadequate and returning to the freestyle project type.
>
> You'll have more control with the freestyle (but more control means
> more configuration)
I don't want to discourage people from using the maven2 project type,
and I'd like to learn more about the specific issues you had (although
maybe it's one of the many bugs filed in the issue tracker already.)

There's also a work in progress to make BuildWrapper work with Maven
project at core level, too.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment