[
https://issues.jboss.org/browse/JBIDE-12836?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-12836:
---------------------------------------------
Notes:
mvn -Dtycho.mode=true help:all-profiles
Profile Id: osx (Active: true , Source: pom)
Profile Id: jbosstools-nightly-staging-composite (Active: false , Source: pom)
Profile Id: jbosstools-nightly-staging-composite-soa-tooling (Active: false , Source:
pom)
Profile Id: jbosstools-staging-aggregate (Active: false , Source: pom)
Profile Id: local.requirements (Active: false , Source: pom)
Profile Id: local.composite (Active: false , Source: pom)
Profile Id: jboss-requirements-composite-mirror (Active: false , Source: pom)
Profile Id: jboss-requirements-composite-extras-mirror (Active: false , Source: pom)
Profile Id: multiple.target (Active: false , Source: pom)
Profile Id: unified.target (Active: false , Source: pom)
Profile Id: jenkins.target (Active: false , Source: pom)
Profile Id: local.target (Active: false , Source: pom)
Profile Id: local.site (Active: false , Source: pom)
Profile Id: applejdk (Active: false , Source: pom)
Profile Id: hudson (Active: false , Source: pom)
Profile Id: default (Active: false , Source: pom)
Profile Id: mavenTestSkip (Active: false , Source: pom)
we should get these documented, split up in "systemprofiles" i.e. applejdk/osx
are autodtected., "helpers" i.e. mavenTestSkip (how is that different from
normal -D props?) and those .target / mirror profiles seems to be overlapping ...which can
be used together, not together?
Answer questions like, why is there both an applejdk and osx profile?
why is there a hudson when the system is running on jenkins ? is this profile unique for
jboss servers? then should have another name.
Review and clean parent pom
---------------------------
Key: JBIDE-12836
URL:
https://issues.jboss.org/browse/JBIDE-12836
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng
Reporter: Mickael Istria
Assignee: Max Rydahl Andersen
Labels: ece2012
Fix For: 4.0.0.CR1
With introduction of new target-platforms, enforcement of usage of target platforms over
repositories, usage of Maven mirroring on Jenkins... the parent pom has seen its
responsibilities reduced.
We should improve it to remove from it all legacy profiles and properties that are now
replaced by more flexible mechanisms. Also, we should re-think some profiles to make them
simpler to use.
Goal is to make it easier to read, and then to maintain, without loosing any optimization
we've made for end-users or CI.
--
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