Hello, The answers to your questions are twofold. One is for the latest released version and one is for the latest sources in trunk (nbm-plugin 3.0-SNAPSHOT) which have many concepts radically improved. I'll comment on both.
On Tue, Oct 7, 2008 at 2:26 PM, Michel Rasschaert <[EMAIL PROTECTED]> wrote: > Hi, > > I am trying to use the nbm-maven-plugin for our netbeans platform project. > > I do not understand how dependencies on other modules are processed. I > expected > the install goal to populate the local repository with the nbm of my project > but > it is only publishing the jar. Is this normal ? for 2.6.x it's normal. NBM files are not placed in local repository as they are only used when you generate the update center. in 3.0-SNAPSHOT the nbm file is always generated and uploaded to local/remote repositories as it's critical for final application assembly. The nbm:populate-repository goal in 2.6 will also only upload the jar files of netbeans platform app. the 3.0-SNAPSHOT one will upload jar files, recognize Class-Path: dependencies, upload nbm files (if passed to the goal) and generate pom files from netbeans platform clusters. > > In my tests I have 2 netbeans modules > > mvntest1 > mvntest2 > > mvntest2 depends on mvntest1 which itself only depends on the base platform > (org.openide.util). > > When in the mvntest2 project, I thought that running "mvn nbm:cluster" would > create the target cluster including the mvntest1 module. in 2.6.x the nbm:cluster goal needs to be run in the parent pom that has both mvntest1 and mvntest2 defined as modules. both nbm:cluster and nbm:updatesite goals work on top of build reactor, rather than module's dependencies in 3.0-SNAPSHOT, the reactor building of clusters is replaced by a special packaging for the final nbm application -nbm-application which will create the final bits from the nbm files (not only yours but the nbm files of the platform as well.) > However it does not and I cannot do "mvn nbm:run-platform" because of the > missing dependency in the platform. 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. > > From reading articles I get the impression that I must have a parent pom with > maven modules to emulate the suite. Is this absolutely necessary or is there a > way to work with standalone modules and a dynamically generated platform > (which > we currently generate with the nbms of the depended on modules) ? in 2.6.x you need the parent pom to simulate the suite, for some goals you also need reference on a netbeans installation directory. in 3.0-SNAPSHOT, both modules can be independent from each other and the actual final application assembly (if there is any) you can even create an update center descriptor that will reference your modules in the maven repository and itself be uploaded at maven repo as a tar.gz 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. Regards Milos > > Thanks for your help, > > > > --------------------------------------------------------------------- > 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
