> Note that JBDS build (including installers & sites) can now be built w/ just "mvn install", so we're certainly closer to the goal here.

Which profiles/target-platforms are activated by default?
For JBT, we have:

  1. If on CI, unified.target + snapshots composite site
  2. If JBT local development: unified.target + snapshots aggregated site (rather that composite for better performance)
  3. If SOA-Tools on CI: unified.target + JBT Milestone + SOA Snapshot composite site
  4. If SOA-Tools local development: unified.target + JBT milestone + SOA snapshots aggregated site
    Does it seem right?

Which one should be default? I'm in favor of number 2 since:

  • Jenkins does not complain, so we can configure jobs directly for 1 and 3
  • number of JBT dev > number of SOA-Tools dev, so less complaints if satisfying JBT dev

I think this also shows that we'll probably need a new parent pom for SOA to manage their own profiles to resolve dependencies.
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