RE: [mevenide-user] mevenide 4.0.5 and runtime classpathScope
"Hartmut Lang" <hartmut.lang-IzeFyvvaP7pWk0Htik3J/[email protected]> Wed, 26 Nov 2008 08:52:21 +0100
| Newsgroups | gmane.comp.jakarta.turbine.maven.mevenide.user |
|---|---|
| Message-ID | <E5E9C6CC7DC8844A8DA7A9EFE7B5350E02BFEFDA@esealmw118.eemea.ericsson.se> |
Ok, that's great. Thanks, Hartmut Lang -----Original Message----- From: Milos Kleint [mailto:[email protected]]=20 Sent: Mittwoch, 26. November 2008 08:49 To: [email protected] 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-IzeFyvvaP7pWk0Htik3J/[email protected]> 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:[email protected]] > Sent: Dienstag, 25. November 2008 14:06 > To: [email protected] > Subject: Re: [mevenide-user] mevenide 4.0.5 and runtime classpathScope > > On Tue, Nov 25, 2008 at 1:11 PM, Hartmut Lang > <hartmut.lang-IzeFyvvaP7pWk0Htik3J/[email protected]> 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