The project is available on github: https://github.com/rpelisse/esb-project-mvn-directory-layout.git. If you checkout the commit b2cf34dace276971d79325b9aa34d673818971e5, you can reproduce the issue.

To make short, the goal is to have on parent project for all ESB project:

myproject/

  • pom.xml
    esb/
  • pom.xml
  • esb-app-1
  • esb-app-2

Now, again, I completly agree with you, using the pluginManagement section is the right approach. What I don't like is having the build failed because a pom.xml with packaging "pom" fails to find an ESB file. It is confusing and led one of my customer to believe that the plugin simply was not supported in a multi modules project. I do not say he was right to assume that, but I would like to enhance the plugin to avoid this situation to happen again.

If you really want to discourage this, I can modify the code I've pushed to github to log a warning statement explaining the issue (ie Why do you have "jboss-esb" plugin in a pom.xml file ? You should move this configuration to pluginManagement !).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Reply via email to