Netbeans 6.5 + Mevenide, external?

[Magne Nordtveit]

Now that NB 6.5 is out, what is the recommended usage of the mevenide plugin?
I read earlier that M.Klein recommended using the external maven in favour for
the bundled version, is this still the case? What are the pros and cons of
using the external in favour of the bundled version?

Cheers
Magne
--
Magne Nordtveit <magne.nordtveit@...>
Systems Engineer
Offshore Simulator Centre AS
http://www.offsimcentre.no
--
Magne Nordtveit <magne.nordtveit@...>
Systems Engineer
Offshore Simulator Centre AS
http://www.offsimcentre.no

external is recommended. you have to explicitly say you want embedded
(or have no maven on PATH) to get the embedded build now.
embedded one is not 100% compatible, more buggy, some plugins may
fail, eats up the IDE's JVM heap space.

I haven't figured how to revive the build plan browsing feature with
non-embedded execution though..

Milos



On Thu, Nov 20, 2008 at 8:53 AM, Magne Nordtveit
<magne.nordtveit@...> wrote:

> Now that NB 6.5 is out, what is the recommended usage of the mevenide plugin?
> I read earlier that M.Klein recommended using the external maven in favour for
> the bundled version, is this still the case? What are the pros and cons of
> using the external in favour of the bundled version?
>
> Cheers
> Magne
> --
> Magne Nordtveit <magne.nordtveit@...>
> Systems Engineer
> Offshore Simulator Centre AS
> http://www.offsimcentre.no
> --
> Magne Nordtveit <magne.nordtveit@...>
> Systems Engineer
> Offshore Simulator Centre AS
> http://www.offsimcentre.no
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Hartmut Lang]

Milos,

We are using netbeans 6.5 with mevenide 4.0.5.
We are facing the problem that on running a maven-project the exec-maven
plugin is only called with "compile" as classpathScope. And we would
need "runtime".
I also saw that you fixed an exec-maven plugin issue related to using
"runtime".
Do you plan to introduce "runtime" classpathScope in your mevenide
netbeans plugin?


Regards,
Hartmut

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

On Tue, Nov 25, 2008 at 1:11 PM, Hartmut Lang <hartmut.lang@...> wrote:

> Milos,
>
> We are using netbeans 6.5 with mevenide 4.0.5.
> We are facing the problem that on running a maven-project the exec-maven
> plugin is only called with "compile" as classpathScope. And we would
> need "runtime".
> I also saw that you fixed an exec-maven plugin issue related to using
> "runtime".
> Do you plan to introduce "runtime" classpathScope in your mevenide
> netbeans plugin?

once the exec plugin gets released, then the maven support will start
using the new version by default and will use the correct scope. I'm
not even sure why compile was chosen as default scope, doesn't make
much sense to me..

the current workaround for now is to use the test scope instead of
runtime in case you need it. (test extends runtime)

in 7.0 codebase, I've fixed the issue of main() classes in test
sources and the test scope for the exec plugin is added there by
default.

Regards

Milos

>
>
> Regards,
> Hartmut
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Hartmut Lang]

Milos,

Thanks for this info.
Do you expect "runtime" to be the default classpathScope in the next
release of exec-maven plugin?
Or do we have to add that to our nbactions.xml file?

Regards,
Hartmut Lang

-----Original Message-----
From: Milos Kleint [mailto:mkleint@...]
Sent: Dienstag, 25. November 2008 14:06
To: user@...
Subject: Re: [mevenide-user] mevenide 4.0.5 and runtime classpathScope

On Tue, Nov 25, 2008 at 1:11 PM, Hartmut Lang
<hartmut.lang@...> wrote:
> Milos,
>
> We are using netbeans 6.5 with mevenide 4.0.5.
> We are facing the problem that on running a maven-project the
exec-maven
> plugin is only called with "compile" as classpathScope. And we would
> need "runtime".
> I also saw that you fixed an exec-maven plugin issue related to using
> "runtime".
> Do you plan to introduce "runtime" classpathScope in your mevenide
> netbeans plugin?

once the exec plugin gets released, then the maven support will start
using the new version by default and will use the correct scope. I'm
not even sure why compile was chosen as default scope, doesn't make
much sense to me..

the current workaround for now is to use the test scope instead of
runtime in case you need it. (test extends runtime)

in 7.0 codebase, I've fixed the issue of main() classes in test
sources and the test scope for the exec plugin is added there by
default.

Regards

Milos

>
>
> Regards,
> Hartmut
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

either it becomes the default in the exec plugin or the default action
mappings will make it a default in the IDE. either way you should not
need to tweak anything in the nbactions.xml file.

Milos

On Wed, Nov 26, 2008 at 8:45 AM, Hartmut Lang <hartmut.lang@...> wrote:

> Milos,
>
> Thanks for this info.
> Do you expect "runtime" to be the default classpathScope in the next
> release of exec-maven plugin?
> Or do we have to add that to our nbactions.xml file?
>
> Regards,
> Hartmut Lang
>
> -----Original Message-----
> From: Milos Kleint [mailto:mkleint@...]
> Sent: Dienstag, 25. November 2008 14:06
> To: user@...
> Subject: Re: [mevenide-user] mevenide 4.0.5 and runtime classpathScope
>
> On Tue, Nov 25, 2008 at 1:11 PM, Hartmut Lang
> <hartmut.lang@...> wrote:
>> Milos,
>>
>> We are using netbeans 6.5 with mevenide 4.0.5.
>> We are facing the problem that on running a maven-project the
> exec-maven
>> plugin is only called with "compile" as classpathScope. And we would
>> need "runtime".
>> I also saw that you fixed an exec-maven plugin issue related to using
>> "runtime".
>> Do you plan to introduce "runtime" classpathScope in your mevenide
>> netbeans plugin?
>
> once the exec plugin gets released, then the maven support will start
> using the new version by default and will use the correct scope. I'm
> not even sure why compile was chosen as default scope, doesn't make
> much sense to me..
>
> the current workaround for now is to use the test scope instead of
> runtime in case you need it. (test extends runtime)
>
> in 7.0 codebase, I've fixed the issue of main() classes in test
> sources and the test scope for the exec plugin is added there by
> default.
>
> Regards
>
> Milos
>
>>
>>
>> Regards,
>> Hartmut
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Hartmut Lang]

Ok, that's great.

Thanks,
Hartmut Lang

-----Original Message-----
From: Milos Kleint [mailto:mkleint@...]
Sent: Mittwoch, 26. November 2008 08:49
To: user@...
Subject: Re: [mevenide-user] mevenide 4.0.5 and runtime classpathScope

either it becomes the default in the exec plugin or the default action
mappings will make it a default in the IDE. either way you should not
need to tweak anything in the nbactions.xml file.

Milos

On Wed, Nov 26, 2008 at 8:45 AM, Hartmut Lang
<hartmut.lang@...> wrote:

> Milos,
>
> Thanks for this info.
> Do you expect "runtime" to be the default classpathScope in the next
> release of exec-maven plugin?
> Or do we have to add that to our nbactions.xml file?
>
> Regards,
> Hartmut Lang
>
> -----Original Message-----
> From: Milos Kleint [mailto:mkleint@...]
> Sent: Dienstag, 25. November 2008 14:06
> To: user@...
> Subject: Re: [mevenide-user] mevenide 4.0.5 and runtime classpathScope
>
> On Tue, Nov 25, 2008 at 1:11 PM, Hartmut Lang
> <hartmut.lang@...> wrote:
>> Milos,
>>
>> We are using netbeans 6.5 with mevenide 4.0.5.
>> We are facing the problem that on running a maven-project the
> exec-maven
>> plugin is only called with "compile" as classpathScope. And we would
>> need "runtime".
>> I also saw that you fixed an exec-maven plugin issue related to using
>> "runtime".
>> Do you plan to introduce "runtime" classpathScope in your mevenide
>> netbeans plugin?
>
> once the exec plugin gets released, then the maven support will start
> using the new version by default and will use the correct scope. I'm
> not even sure why compile was chosen as default scope, doesn't make
> much sense to me..
>
> the current workaround for now is to use the test scope instead of
> runtime in case you need it. (test extends runtime)
>
> in 7.0 codebase, I've fixed the issue of main() classes in test
> sources and the test scope for the exec plugin is added there by
> default.
>
> Regards
>
> Milos
>
>>
>>
>> Regards,
>> Hartmut
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email