Re: [mevenide-user] Alternative launching with mevenide

instead of using the default mapping for run action, use something else.
like exec:java. You might want to skip the "package" phase there.
However note that
1. you won't be getting separate user program output then.
2. for debug action you need to use exec:exec because you need to spawn a
separate VM. You will also need to change the property definitions for debug
action to pass the VM params to the spawned JVM.

The current run/debug actions mappings are suboptimal performance-wise. At
least part of the issue is on maven side, some build steps just take too
much time. Additionally a lot of time seems to be often spent in touching
the remote repositories..

Milos

On Dec 10, 2007 9:33 AM, aschneider <[email protected]> wrote:

>
> Hi,
>
> I am using netbeans 6 and mevenide. New we changed a large project that it
> uses maven to build. In eclipse we are using the mvn eclipse:eclipse goal
> to
> generate the project files and it works perfect. Some developers are using
> netbeans 6 and have the problem of poor performance. When you want run or
> debug the project the mevenide plugin generates an executable jar (it
> looks
> like that it genrates it two times) to launch the project.
>
> Here the output
> -------------------------------------------------------------------------
> JPDA Listening Starting...
> JPDA Address: WS-11:1565
> Port:1565
> Scanning for projects...
> artifact org.codehaus.mevenide:netbeans-run-plugin: checking for updates
> from rieter.releases
>
> ----------------------------------------------------------------------------
> Building Vector
>   task-segment: [package,
> org.codehaus.mevenide:netbeans-run-plugin:RELEASE:run-jar]
>
> ----------------------------------------------------------------------------
> project-execute
> artifact org.apache.maven.plugins:maven-resources-plugin: checking for
> updates from netbeansIDE-repo-internal
> artifact org.apache.maven.plugins:maven-compiler-plugin: checking for
> updates from netbeansIDE-repo-internal
> artifact org.apache.maven.plugins:maven-surefire-plugin: checking for
> updates from netbeansIDE-repo-internal
> artifact org.apache.maven.plugins:maven-jar-plugin: checking for updates
> from netbeansIDE-repo-internal
> artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for
> updates from netbeansIDE-repo-internal
> artifact org.apache.maven.plugins:maven-assembly-plugin: checking for
> updates from netbeansIDE-repo-internal
> [resources:resources]
> Using default encoding to copy filtered resources.
> [compiler:compile]
> Nothing to compile - all classes are up to date
> [resources:testResources]
> Using default encoding to copy filtered resources.
> [compiler:testCompile]
> Not compiling test sources
> [surefire:test]
> Tests are skipped.
> [jar:jar]
> Building jar:
> D:\Rieter\eclipse-workspace\vector-trunk\target\vector-309-SNAPSHOT.jar
> Preparing assembly:directory
>
> ----------------------------------------------------------------------------
> Building Vector
>
> ----------------------------------------------------------------------------
> [WARN]Removing: directory from forked lifecycle, to prevent recursive
> invocation.
> [resources:resources]
> Using default encoding to copy filtered resources.
> [compiler:compile]
> Nothing to compile - all classes are up to date
> [resources:testResources]
> Using default encoding to copy filtered resources.
> [compiler:testCompile]
> Not compiling test sources
> [surefire:test]
> Tests are skipped.
> [jar:jar]
> Building jar:
> D:\Rieter\eclipse-workspace\vector-trunk\target\vector-309-SNAPSHOT.jar
> [WARN]DEPRECATED [descriptor]: Please use descriptors instead
> [assembly:directory {execution: nb}]
> Processing DependencySet (output=lib)
> Copying 48 files to
> D:\Rieter\eclipse-workspace\vector-trunk\target\executable-netbeans.dir
> [netbeans-run:run-jar]
> Executing "'C:\Programme\Java\jdk1.6.0_02\bin\java.exe' -Xdebug
> -Djava.compiler=none -Xnoagent
> -Xrunjdwp:transport=dt_socket,server=n,address=1565 -jar
> 'D:\Rieter\eclipse-workspace\vector-trunk\target\executable-
> netbeans.dir\vector-309-SNAPSHOT.jar'
> " in directory D:\Rieter\eclipse-workspace\vector-trunk\lib
>
> -------------------------------------------------------------------------
> On slower machines it takes a long time to start this project. Is there a
> way to start a project in a different way without generating the jar
> files?
>
> Thanks for every hint.
>
> --
> View this message in context:
> http://www.nabble.com/Alternative-launching-with-mevenide-tp14249070p14249070.html
> Sent from the mevenide - user mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>