Re: [mevenide-user] Alternative launching with mevenide
"matt weiss" <[email protected]>
| Newsgroups | gmane.comp.jakarta.turbine.maven.mevenide.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Andy, Yes, you are correct. Maven fundamentally is different, and fundamentally better, for building and managing dependencies. The reality is that I don't believe a developer should have to think about this during the process of iterative development, and this is what the maven intellij plugin provides. I really cannot speak much for the maven eclipse plugin as I haven't really used it much. I feel that when I click "debug" the mevenide plugin should figure out what needs to be built, in a minimalistic fashion, and do just that then start the debugger. My out of the box experience has been that the mavenide2 plugin will either start my parent project (with dependencies that are out of date because hey, I forgot that I needed to rebuild that one component that I changed a bit) or because I'm paranoid about this haunting problem, I habitually rebuild everything in the project because I've been burned too many times by this problem. In either case the recourse seems to be that I need to know all of the ins and outs of maven goals can configurations and tweek my actions to increase my performance. When I'm developing, I shouldn't have to think about maven and maven projects, with the exception of making sure that classes and resources are put into the appropriate place and that resources must be loaded in a maven friendly manner. I do understand the disconnect between modules in maven, but when you are working on a project when you are changing multiple modules and constantly rebuilding and debugging, the mevenide2 plugin for netbeans just doesn't quite fit the bill. Matt On Dec 19, 2007 8:43 AM, andy law (RI) <[email protected]> wrote: > Matt, > > There is a fundamental difference between Netbeans/IntelliJ/IDE > development patterns and maven patterns that I have struggled with. You > sound like your head thinks along the lines that "all my code, > regardless of sub-project, is part of my project and you should 'know' > which bits need to be recompiled". Unfortunately that's the wrong way to > think about maven projects. > > Each maven project is separate. Yes, there can be nested projects but > they are all separate and self-contained (or they should be). So if you > modify code in one project then all that should matter (as far as the > 'Maven way' is concerned) is that you rebuild that project, run the > tests and create a new artifact/jar. Your other projects need not be > touched - they were built using a previous version and work just fine, > don't they? > > It takes a (very) long time to get into the way of thinking about > separate modules as separate projects and I'm still not all the way > there. Having said that, *I* think that the process is worthwhile for > several reasons. I *love* the dependency management in maven. I *love* > the independence from ide that it brings too. Now that Netbeans 6.0 is > proving to be such a dog in our hands, we *can* consider moving to > alternative IDEs only because we use maven under the hood. Of course, > these may not be considerations for you but they have been phenomenally > useful for us. > > Later, > > Andy > > ------------- > Yada, yada, yada... > > Roslin Institute is a company limited by guarantee, registered in > Scotland (registered number SC157100) and a Scottish Charity (registered > number SC023592). Our registered office is at Roslin, Midlothian, EH25 > 9PS. VAT registration number 847380013. > > The information contained in this e-mail (including any attachments) is > confidential and is intended for the use of the addressee only. The > opinions expressed within this e-mail (including any attachments) are > the opinions of the sender and do not necessarily constitute those of > Roslin Institute (Edinburgh) ("the Institute") unless specifically > stated by a sender who is duly authorised to do so on behalf of the > Institute. > > > > -----Original Message----- > > From: matt weiss [mailto:[email protected]] > > Sent: 19 December 2007 12:35 > > To: [email protected] > > Subject: Re: [mevenide-user] Alternative launching with mevenide > > > > Thanks for the reply Milos, > > > > I'll experiment around with this information. > > > > In an attempt at becoming more efficient at what I do, I've > > been trying to make it a habit of using the shortcut keys as > > much as I can. One of my favorite shortcuts is the "go to > > class" shortcut key sequence (alt-shift-o). After making > > changes, I like to just "run" my application. But I am not > > always conscious of what sub-projects I've changed since I > > use the shortcut to open them. Thus, I much too often find > > myself building all projects so that I am certain that I am > > indeed running my changes since I forget what sub-projects > > the classes that I modified are in. It seems that this type > > of feature is something that the mevenide2 plugin cannot help > > me with, that is merely "makefile" behavior; build only the > > things that are out of date. For reasons like this, I feel > > that there is still a tremendous need for the existing > > netbeans maven plugin, because of what ant and netbeans can > > provide natively. Of course it has been abandoned and I'd be > > going at it alone, so it probably would be more advantageous > > for me to consider how I could contribute to the mevenide2 > > plugin project. > > > > Thanks for your time. > > > > Matt > > > > > > On Dec 19, 2007 6:39 AM, Milos Kleint <[email protected]> wrote: > > > > > > 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-tp14 > 249070p14249070.html <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 > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > -- Matt Weiss Software Journeyman [email protected]