Hi Robert, Am 13.03.2014 21:43, schrieb Robert Scholte:
Op Thu, 13 Mar 2014 01:40:23 +0100 schreef Jörg Hohwiller <jo...@j-hohwiller.de>:Hi there, I added site documentation and some other missing infos. Further I fixed some JavaDoc issues. For clarification I found the following questions: * Why do we copy <repositories> section of <profile> when we strip <repositories> from <project>? This appears inconsistent to me.I think repositories should stay, pluginRepositories not
OK. Implemented.
* Shall we prevent creating "useless" profiles (those that have no dependencies) in flattened POM?Sounds reasonable
OK. Implemented.
* Shall we consider more complex logic to figure out if properties are influenced by profiles and used in dependencies so we do not resolve such properties?I know there's a JIRA issue which suggest that dependencies shouldn't contain properties. At build-time I would like to use properties to keep a set of artifacts like Spring at the same version. But at deploy-time it's probably better to have them resolved.
OK. Not implemented. Already addressed in FAQ.
I am not talking about a mechanism in flatten-maven-plugin but about any way in maven to configure a POM so that maven-deploy-plugin will be omitted. I can override the plugin configuration but I do not know how to disable a plugin and also in a way that it is still enabled for the child modules.* Is there a way to prevent maven from deploying the parent POMs when a top-level build is triggered? See some of my examples...there are different types of parent: aggregator, release-root, sub-parent, standalone. The latter should be deployed, since this will be the parent for other projects (e.g. mojo-parent) . The rest is probably less interesting when using a flatten pom. This feature is just as dangerous as the embedBuildPRofileDependencies.
Cheers Jörg
smime.p7s
Description: S/MIME Cryptographic Signature
