right, the server side is not packaged as an nbm-application that was an oversight. I will try out the latest configuration and send the debug information.
As for sub projects packaging, right now I have them as nbm-file. ________________________________ From: Milos Kleint <[EMAIL PROTECTED]> To: [email protected] Sent: Thursday, October 30, 2008 6:33:46 PM Subject: Re: [mojo-user] please beta test maven nbm plugin The error you described [ERROR]Transitive dependency resolution for scope: runtime has failed for >> your project. seems to indicate that you might have created a dependency cycle for runtime scope of dependencies. However execution with debug messages on shall reveal more I guess. I don't completely follow your latest architecture description, I'm missing what the subprojects have for packaging. packaging nbm-application for server side sounds wrong however. Milos On Wed, Oct 29, 2008 at 12:19 PM, Sidart Kurias <[EMAIL PROTECTED]> wrote: > Milos > > Actually it looks like this > > Subproject4 - common to server and client > Parent - Client > subProject 1 > sub Project 2 -- depends on 2 and 4 > subProject 3 -- depends on 1 and 4 > Server > sp5 - depends on sp4 etc.... > > But if I guess correctly from your response I will have to create 2 new Poms > of type nbm-application to package the client and server modules. So > something like this > > ClientPackaging Pom -- depends on sp1,2 and 3 and 4 > ServerPackaging --- depends on sp5, sp4 , sp6... > > Subproject4 - common to server and client > > Parent - Client (Top level POM) > subProject 1 > sub Project 2 -- depends on 2 and 4 > subProject 3 -- depends on 1 and 4 > > Server Parent (Top Level POM) > sp5 - depends on sp4 > sp6 ..... > > Does that seem right? I will give it a shot. > > > >>> it's a general constraint in maven that only "pom" packaging projects can >>> have modules > > Right that is what I tried to do.... > > Thanks > Sid > ________________________________ > From: Milos Kleint <[EMAIL PROTECTED]> > To: [email protected] > Sent: Wednesday, October 29, 2008 2:28:39 PM > Subject: Re: [mojo-user] please beta test maven nbm plugin > > Well, not sure I fully understand the setup you have. >> SubProject4 - nbm-application packaging, has dependencies on suproject1-3 >> Parent - pom packaging >> SubProject1 - nbm packaging >> SubProject 2 - nbm packaging >> SubProject 3. - nbm packaging > > Does it look like this? It should be working then. Your comment about > wrongly formed parent pom implies that you tried to put the parent > pom's packaging to nbm-application. That cannot be done. it's a > general constraint in maven that only "pom" packaging projects can > have modules. > > milos > > On Mon, Oct 27, 2008 at 1:11 PM, Sidart Kurias <[EMAIL PROTECTED]> > wrote: >> Milos >> >> I am trying to use the new plugin in a multi module scenario.I am trying >> to >> convert a project that worked with 2.7-alpha to 30-SNAPSHOT. After reading >> the documentation I am trying to set it up as best as I have >> understood.... >> >> I have a main (parent pom) project with 4 sub projects. One of the >> sub-projects is on the same level as the parent project. The directory >> structure looks like this. >> >> SubProject4 >> Parent >> SubProject1 >> SubProject 2 >> SubProject 3. >> >> Now if at the parent level I define a packaging type of nbm-application >> and >> then define each sub project as a dependency and in each sub project I >> define it's parent to be 'Parent' then I get the error shown below, as it >> does not compile the sub projects. At this point the ide tells me I have a >> badly formed maven project >> >> Scanning for projects... >> project-execute >> [#clean] >> [clean:clean] >> [#process-resources] >> [ERROR]Transitive dependency resolution for scope: runtime has failed for >> your project. >> >> >> >> If I add the modules tag to the parent pom, then it complains that the >> parent project is badly formed >> >> >> >> Thanks >> Sid >> >> ________________________________ >> From: Milos Kleint <[EMAIL PROTECTED]> >> To: [email protected] >> Sent: Friday, October 17, 2008 2:55:42 PM >> Subject: [mojo-user] please beta test maven nbm plugin >> >> Hello, >> >> in case you are using Apache Maven to build your NetBeans Platform >> based application, I'd like to hear you feedback on the new version. I >> have it in the works for some time already and I think it's ready to >> be released. It reworks multiple areas that were causing trouble in >> previous releases. >> 1. matching netbeans runtime dependencies against maven dependencies in >> pom. >> 2. incomplete metadata in generated repository >> 3. support for generating final bits of a platform based application >> 4. generating webstartable bits >> >> I've uploaded the nbm-maven-plugin 3.0-SNAPSHOT to >> http://snapshots.repository.codehaus.org along with the relevant >> updated archetypes. >> The temporary website of the plugin's snapshot is at >> http://codehaus.org/~mkleint/ >> >> The new version is not really compatible with the previous ones (2.6.x >> releases and 2.7-SNAPSHOTS). For details on changes, see >> http://codehaus.org/~mkleint/2630upgrade.html >> >> for a quick start sample netbeans platform based app, use the deployed >> archetype snapshot. >> mvn -DarchetypeGroupId=org.codehaus.mojo.archetypes >> -DarchetypeArtifactId=netbeans-platform-app-archetype >> -DarchetypeVersion=1.1-SNAPSHOT >> -DarchetypeRepository=http://snapshots.repository.codehaus.org >> -DgroupId=org.kleint -DartifactId=milos -Dversion=1.0 >> archetype:generate >> Please note that you will have to include the >> http://snapshots.repository.codehaus.org in your ~/.m2/settings.xml >> file or in the generate project's pom to get the nbm-maven-plugin >> snapshot. >> >> Thanks in advance for any comments. >> >> Milos >> >> --------------------------------------------------------------------- >> 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
