Re: [mevenide-user] Why mevenide2 for netbeans?

On Dec 18, 2007 3:20 PM, matt weiss <[email protected]> wrote:

> Hey all,
>
> Here's an opportunity to jump on someone for not understanding or
> knowing.  In any case my question is why?  Why was mevenide started?  My
> experience with mevenide has been rather poor compared to my experience with
> the intellij plugin for maven.  As many of you are aware, the intellij
> plugin works in a different fashion than the mevenide2 plugin.  A command is
> issued for your root pom file and all the intellij project files are
> generated.  Then one can open up intellij and develop in a familiar fashion
> without regards to dependencies or even the fact that maven is used because
> the maven in this scenario is transparent.  My experience has been rather
> seemless with this approach.
>
> My experience with the mevenide2 plugin has been much different.  The
> mevenide2 plugin is a plugin for Netbeans rather than a plugin for maven2.
> Thus Netbeans treats the pom.xml files as project files and essentially
> issues maven goals to maven the appropriate projects when actions are
> performed such as build, debug, etc.  This means that prerequisite goals
> have to be ran before your desired goal is ran.
>
> My biggest point of disappointment, is how long it takes to just debug and
> run a project.  Let's  say I make a change to my project.  In order for me
> to debug my project all the prerequisite goals must be ran before I can
> debug my project, like the jar goal.  In my uninformed and biased opinion, I
> don't have any interest in making artifacts when I want to debug.  I merely
> want all my java files compiled to classes and I want them loaded into the
> class path so I can debug.  Furthermore, I desire only modified java files
> to be recompiled. mevenide2 does all java files all the time and creates the
> jar files wasting my time.


Just out of interest, how long does take before the project starts?

there space for improvements on multiple levels.
1. mevenide code
2. maven itself
3. finetuning your project to do less and faster when invoked from the IDE.
(eg. by skipping test compilation/execution on Run action, or by making sure
the network is not touched by the build)
4. on windows, disabling virus scanning helps a lot of people I heard.

feel free to contribute any improvements you find that make the Run/Debug
invokation faster.


>
>
> There was a maven plugin for for netbeans, similar to the one developed
> for intellij.  This plugin produced native netbeans project files so that
> one could have a similar native development experience with netbeans as with
> the intellij plugin.  It seems though that this has been pretty much
> abandoned.  My question and purpose for this post is to understand the
> rationale behind this.  I am an advocate of maven, but I don't understand
> why anyone would want it to be a development environment such as what it has
> been made into with the mevenide2 plugin rather than a dependency management
> tool.


creating netbeans projects means generating ant scripts, not one but
multiple different ones. So when building in the IDE, you would be executing
ant build anyway, instead of maven one.
not everything in maven build would convert fine into the ant based
projects. The idea of having sources and resources separate etc.
no change in the IDE  makes it into the project pom and vice versa.

feel free to revive the maven plugin for netbeans, AFAIK the author
abandoned the work on it and started using mevenide.



>
>
> Is there a way to get what I want out of the mevenide2 plugin?


not sure. Required speed is relative to one's development style.


Milos

>
>
> Please advise.
>
> Thanks,
> Matt