... and some answer to some questions;
Marco Tedone wrote:
I noted few things that seemed to me strange:
1) The /target folder is created under /api (is this the default behaviour?)
Yes. Each subroject (api, impl, whatever) generates a single artifact. As such you will see a target folder generated as a result of the subproject build.
2) The maven.xml under /api is different from the maven.xml under /impl. The one under /api contains only the following: <project default="jar:install"/>
While the one under /impl contains the following:
<project default="jar:install">
<preGoal name="java:compile">
<attainGoal name="avalon:meta"/>
</preGoal>
</project>
Correct.
The maven.xml in the api project is used to declare the default goal to execute. In the case of the impl subproject we also have the requirement of running the avalon:meta goal to generate the xinfo file.
The jars created at the end contains only the Manifest.mf and the Sample.class file
Tha't correct - because its only a template - you would notmally throw away the Sample.java and put in place you own sources. They are only there to validate that the build is working, that unit tests using merlin are running, and that the site generate is correctly aggregating content.
Cheers, Steve.
Any idea?
Marco
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
