I'm a past user of Maven 1 on some simple projects and am trying to come up to speed on Maven 2 on a project that has multiple artifacts and I'm not sure how to proceed.
I read somewhere that the model of Maven is one artifact per project, which indicates that I should break it up into a hierarchy of projects, but their could be some problems with that. Here is the artifacts for this project: - Jar with java code and a source jar - A DLL of native code that requires running javah on a subset of the Java source files - Some Java example source code showing how to use the API - Eventually, an eclipse plugin-jar containing the jar and DLL. I understand how to do the main java jar and src jar with unit tests. And I think it makes sense to make the eclipse plug-in a separate project from the rest under the same parent project. But I'm not sure how to organize the DLL generation and the sample source code. I suppose the sample source code could be its own subproject. It depends on the main jar and would need to be compiled to check for errors. I suppose the real issue is the DLL. It of course depends on the source from the main jar. The unit tests for the main jar depend on the DLL for testing. In reality I am probably going to have to create another DLL for testing as well. It seems that it makes sense for the DLL to be built as part of the POM for the main jar, but I'm not sure if that actually works in the Maven world. Can you really do another artifact as part of the pom? Any thoughts? -- Dale King --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
