Execution of plugin depending on the activation of specific profile
Use-case: I have a multilevel project where the top level POM defines a number of different profiles. In some (i.e. not all) of the sublevel projetcs I need to execute a plugin only if a certain profile, say X, defined within top level POM is activated by the user. Also the configuration of the plugin is not shared among the sublevel modules that actually requires execution of the plugin. What I need is a simple construction like this: IfActive profile=X plugin ... /plugin /IfActive Considerations: I cannot just define the plugin within the profile X in the top level POM since then every subproject would then execute the plugin once the X profile was activated which is not ok since the execution of the plugin only applies to some of the subprojetcs and the configuration of the plugin is project specific. Of course I could define a new profile within the relevant submodules that takes care of the execution of the plugin however the number of profiles required this way would be unmanagble. Any suggestions on how to solve this issue ? Best regards Jorgen -- View this message in context: http://www.nabble.com/Execution-of-plugin-depending-on-the-activation-of-specific-profile-tf2050639.html#a5648574 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2 J2EE Project Just Execute this folder and not the sub modules
Have you tried the maven CLI switch -N,--non-recursive ?? i.e. execute c:\.\rootproject\mvn -N install in your top level project. Regards Jorgen -- View this message in context: http://www.nabble.com/M2-J2EE-Project-Just-Execute-this-folder-and-not-the-sub-modules-tf2046719.html#a5649330 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Need help: How to managing the version number in a multi-module
Hi Jens I'm not aware of what is considered best pratice on this matter. However we are using the M2 Release plugin to handle your maintenance problem. Eache single project included in our multiproject structure uses the version1.0-SNAPSHOT/version tag. Once we cut a new release for the multiproject we execute the M2 Release plugin. The plugin - among other things - assigns a new identical version tag to each POM located in the multiproject structure and thus the version integrity of the entire multiproject is preserved. Regards Jorgen Regards Jorgen -- View this message in context: http://www.nabble.com/-m2--Need-help%3A-How-to-managing-the-version-number-in-a-multi-module-project-tf2050906.html#a5649632 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
