I admit it, I'm now completely confused about lifecycle phases and goals and packages.
The first thing is that I need to create a JAR archive of my code. Ok, this works fine using the standard stuff. In a second step, I need to create a source code archive of my code. Ok, this I can get working easily. In a third step, I need to create an archive of the generated Javadoc of my code. Ok, this I can get working easily. In a fourth step however, I need to be able to create a distribution for my library. This distribution is a zip archive of the following content: - README.TXT (copied from src/main/packaging and filtering applied) - docs/javadoc (Javadoc generated from source code, plus ideally Javadoc for dependencies) - docs/release-notes.html (Release Notes generated using my own custom plugin) - docs/dependencies.html (Dependency Report generated using my own custom plugin) - lib (containing the JAR version of my library, but also any dependencies) - some other files (e.g. licenses, etc. copied from src/main/packaging, but no filtering applied) I'd like to use "mvn package" to create my distribution archive, use "mvn install" to install the distribution archive, the JAR archive, the source code archive and the Javadoc archive in the repository. Originally, I was planning to customize the lifecycle to add new phases to it, each mapped to one or more goals. However, this doesn't seem to be possible as I wasn't able to create custom lifecycle phases. Any idea, how to have a single POM, be able to create all those different artifacts, and to be able to install them in the repository using a single phase (e.g. install)? Any help is very much appreciated, as I'm at a dead end now. Thanks Chris
