On Tue, Oct 7, 2008 at 3:48 PM, Michel Rasschaert <[EMAIL PROTECTED]> wrote: > Milos Kleint <mkleint <at> gmail.com> writes: > >> in 2.6.x you need to run the nbm:run-platform goal on the parent pom again. >> in 3.0-SNAPSHOT you define another project myapp that has both module1 >> and module2 as dependencies and has packaging "nbm-application". >> Running "mvn install" shall create the application binaries and >> mvn:run-platform shall run it. >> > > Will it be possible with 3.0-SNAPSHOT to use mvn:run-platform on the module2 > (mvntest2 in my example) and have it work correctly (meaning building the > netbeans cluster with the dependant module) or will I need to create this > nbm-application pom (which is already far more flexible than the aggregating > project approach of 2.X) ?
you will need the nbm-application project, run-platform will not work on nbm projects. there's no more property to point to an existing platform installation and the actual platform is constructed from the project's dependencies. that's impossible/impractical for nbm project. > >> in general I would suggest you try out the 3.0-SNAPSHOT if you are >> just starting. I suppose it shall make many things easier. >> However you will need to check it out from svn, build it yourself, >> also build the website for it and check the new docs I written so far. >> Additionally there's update archetypes at mojo's trunk in >> mojo-archetypes that already incorporates the changes. Generating >> projects from it should give you a rough playground. >> > > Is there an ETA for the first 3.0 release ? coming weeks/months.. Milos > > Thank you for your detailed answer. > > Regards, > > > > --------------------------------------------------------------------- > 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
