Thanks for your response. By basedir do you mean the path that directly contains the artifacts? e.g. http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/axis2/ in the case where org.apache.axis2 is the groupId?
In this case, is the axis2-1.1.pom wrong, or am I mistaken? Because in that .pom file, it refers to <module>modules/parent</module> Shouldn't it refer to <module>../axis2-parent</module> because that's how it looks to me to be structured in their repository. So it seems like 2 mistakes have been made - there's no modules directory underneath the axis2 artifact directory, and it doesn't seem to be called parent, but rather axis2-parent (or is their way of writing it correct because of some default prefixing or something like that?) What also confuses me is that for each of the modules, for example "java2wsdl" at http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/axis2/axis2-java2wsdl/1.1/ there is no pom.xml! Only a axis2-java2wsdl-1.1.pom...but that file looks pretty close to a pom.xml...? Wow, I'm so confused. Please help! Thanks. franz see wrote: > > Good day, > > The <modules/> tag actually refers to directories from the ${basedir}. > Thus if you have > > <project> > ... > <modules> > ... > <module>modules/parent</module> > <module>modules/java2wsdl</module> > </modules > </project> > > Maven will try to find ${basedir}/modules/parent/pom.xml and > ${basedir}/modules/java2wsdl/pom.xml. > > As for the difference between pom.xml and axis2-1.1.pom, ...the former is > the one maven uses for its build and can be found in your source, while > the latter is generated by maven when you're installing or deploying a > maven project to a repository ( which would also be used by maven in some > of its processes ). > > As for the packages, try looking at the modules/xxx/target/ for the > generated binaries. If you don't see it there, try looking at the output > log. > > If a module is a jar, then you'd probably see something like > > [INFO] Building <some-module> > ... > [INFO] jar:jar > ... > [INFO] Building jar: <path to the generated jar> > > Then from there, you can take a look at the <path to the generated jar> to > see whether it really was created. > > The same goes for non-jar modules...you would have something like > > [INFO] Building <some-module> > ... > [INFO] <goal to build the binary> > ... > [INFO] Building <binary type>: <path to the generated binary> > > Cheers, > Franz > > > lightbulb432 wrote: >> >> I want to build a multi-module project from the following pom, but I'm >> not sure if I'm doing it correctly. The POM of the containing project is >> below: >> >> http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/axis2/axis2/1.1/axis2-1.1.pom >> >> When I do a "mvn package" in that directly after downloading it, it only >> packages itself but not the specified modules. I'm not sure why the >> modules start with "modules/" and don't contain a prefix of "axis2-", >> which I'd guess it should be based on the naming of what the other >> modules are listed as (if you go up a couple of levels from the POM link >> above) >> >> Also, what's the difference between a pom.xml and a axis2-1.1.pom? >> >> Your help would be really appreciated. >> > > -- View this message in context: http://www.nabble.com/Multi-module-not-picking-up-modules-tf3566005s177.html#a9963613 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
