[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12608:
----------------------------------------
{quote}
would it make sense to have a single "bootstrap" job
{quote}
Don't forget we also have one Maven plugin ;)
Each of these tasks generally involves several build step. Having all in one job would
probably make it a monster (15-steps or so) job in Jenkins. Moreover, we may want to have
some parts clearly separated (why rebuild parent to update target-platform...).
I'm not against reducing the number of jobs, but keeping some separation generally
makes stuff easier to understand and maintain.
Replace local.* properties and profiles by Maven mirroring
----------------------------------------------------------
Key: JBIDE-12608
URL:
https://issues.jboss.org/browse/JBIDE-12608
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng
Affects Versions: 4.0.0.Alpha2
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Beta1
Attachments: hudson-settings.xml, hudson-settings.xml
Currently, we deal with optimization for Jenkins by multiple local.* properties and
local.* profiles.
Those properties and profiles are just used in order to replace repository URL.
Maven has the concept of mirroring for that, and without adding a profile, we can tell
Maven to consume another URL for a given repo. Moreover, Tycho will support mirrors for
repo in .target files starting from 0.16.0.
WE should move to the mirror approach since it keeps things clear and separate issues:
pom describe build, mirror allow to override repo without any change.
Seems like Maven supports having 2 settings.xml files as input (one with -gs and one with
-s), so no big difficulty here.
--
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