Re: [mevenide-user] Executing without Jar

Hello Eric,
in the latest 3.1 snapshots, I've replaced the run/debug actions to
use exec:exec by default. No more pom.xml generation, building the jar
is not required now.
What I would like to add before 3.1 final, is configurations support
like there is for j2se ant projects. Have different profiles with
different actions associated with run/debug or others.

for download, see
http://deadlock.netbeans.org/hudson/job/mevenide/

let me know your opinion.

Milos

On Tue, Jan 29, 2008 at 10:42 PM, Putrycz, Erik
<[email protected]> wrote:
> Hi Milos,
>
>  Thanks for your answer! I spent some time looking at the exec plugin,
>  few issues:
>  - netbeans seems to often replace the custom actions with the default
>  ones
>  - I have not been able to get working "compile exec:exec" as custom
>  action, I have to do the compile separately
>  - I tried to keep the netbeans action in the custom profile with no
>  luck, somehow now the special profile doesn't get used anymore
>  - how will the debug work with the exec? I assume in your plugin, you
>  pass several parameters to the jvm to enable the debugger
>
>  Also the embedded version of maven seems to complain about plugin
>  versions that require at least 2.0.6... which version is embedded?
>
>  I think it would be nice to replace the jar template with an exec:exec
>  one. I wouldn't mind having a look at your code if I can get netbeans to
>  work correctly on my linux box and figure out how to dl correctly the
>  plugin.
>
>  Erik.
>
>
>
>  -----Original Message-----
>  From: Milos Kleint [mailto:[email protected]]
>  Sent: January 29, 2008 4:29 AM
>  To: [email protected]
>  Subject: Re: [mevenide-user] Executing without Jar
>
>  well, you can definitely override that and change all the Run and
>  Debug actions to run on top of classpath only.
>
>  exec:java will work for Run, but for Debugging you need either
>  exec:exec or execute the goals with external maven instance (as the
>  exec:java starts the app in the same JVM as the the maven build, thus
>  in the IDE's JVM in case you are runnign with the default embedded
>  maven)
>
>  the netbeans-run-plugin and the associated profiles that get created
>  in the pom is something I hacked together to get these features:
>  1. get separate console output for the user application
>  2. have a sort of setup that can be takes "as-is" and executed without
>  the ide and without maven. That was a copy of what the default j2se
>  project in netbeans was doing at that time
>  3. if I recall correctly the exec-maven-plugin was not stable and/or
>  didn't support embedded use correctly when I needed it.. I guess it's
>  time for re-evaluation but there's always more tasks than time..
>
>  What were the problems you encountered with the replacement of Run
>  action in the IDE?
>  You might need to write some config to pom, edit the bindings in the
>  Actions panel in the project properties dialog (and never ever touch
>  the Run panel there). Afterwards it should work. if not it's a bug I
>  suppose.
>
>  Milos
>
>  On Jan 29, 2008 1:09 AM, Putrycz, Erik <[email protected]>
>  wrote:
>  >
>  >
>  >
>  >
>  > I have a large multimodule project with many dependencies. Currently
>  with
>  > netbeans, to run a class, it requires a long process to build a jar...
>  >
>  > Why is the execution using jars?? Just wondering about the design of
>  the
>  > plugin... Wouldn't it have been easier to simply execute using the
>  classpath?
>  > I have been trying to execute the project inside netbeans with the
>  exec
>  > plugin, but netbeans seems to really want the netbeans-run plugin.
>  >
>  > Any suggestions for running a project without the netbeans-run?
>  >
>  >
>  >
>  > Thanks
>  >
>  >
>  >
>  > Erik Putrycz, Ph.D - Research Associate
>  >
>  > Institute for Information Technology - Software Engineering Group
>  >
>  > National Research Council, Canada - Building M-50, 1200 Montreal Road
>  >
>  > Ottawa, Ontario, CANADA K1A 0R6
>  >
>  >
>
>  ---------------------------------------------------------------------
>  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