11:31 a.m.
Mickael Istria created JBIDE-12608:
--------------------------------------
Summary: 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
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
2:38 p.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-12608:
---------------------------------------------
yes, and im surprised hearing tycho doesnt support mirroring since it seemed to work
pretty damn good for me before. maybe specific to targets.
what is diff between -gs and -s ?
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
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
12:17 a.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12608:
----------------------------------------
[~maxandersen] > yes, and im surprised hearing tycho doesnt support mirroring since it
seemed to work pretty damn good for me before. maybe specific to targets.
Tycho supports mirroring, but not for Target Platform. Mirroring of repo from target
platform will be supported with Tycho 0.16.
what is diff between -gs and -s ?
-gs = --global-settings, usually overrides (global) settings found in
$M2_HOME/conf/settings.xml
-s = --settings , usually overrides (user) settings found in
${user.home}/.m2/settings.xml
This was advised by some other Maven users:
http://mail-archives.apache.org/mod_mbox/maven-users/201209.mbox/browser
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
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
1:29 a.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-12608:
---------------------------------------------
got a more direct link than
http://mail-archives.apache.org/mod_mbox/maven-users/201209.mbox/browser ?
do we know if jenkins uses global settings file for their proxy/mirror setup allowing us
to us -s to add to that and still retain the setup that allows jenkins to have optimized
setup for normal maven dependencies?
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
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
7:12 a.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12608:
----------------------------------------
I asked Vojtech yesterday about how settings are currently configured on Jenkins and I
hope I'll get an answer soon. I also hope his answer is "we use global settings,
so you can use the -s flag in your jobs".
http://mail-archives.apache.org/mod_mbox/maven-users/201209.mbox/%3CCANyr...
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
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
2:52 a.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12608:
----------------------------------------
Got answer from Vojtech. Settings for Hudson are
* a user setting file
* /home/hudson/.m2/settings.xml
So we should try the following "mvn -P
unified.target,jbosstools-nightly-staging-composite,hudson -gs
/home/hudson/.m2/settings.xml -s hudson-settings.xml"
Hudson-settings.xml would contain definition of mirrors on Jenkins.
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
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
12:14 p.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Mickael Istria updated JBIDE-12608:
-----------------------------------
Attachment: hudson-settings.xml
Proposed settings.
This would replace local.* stuff in parent, except local.site, which should disappear with
using targets profile in Jenkins.
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
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
12:18 p.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Mickael Istria edited comment on JBIDE-12608 at 9/16/12 1:18 PM:
-----------------------------------------------------------------
Proposed settings.
This would replace local.* stuff in parent.
was (Author: mickael_istria):
Proposed settings.
This would replace local.* stuff in parent, except local.site, which should disappear with
using targets profile in Jenkins.
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
12:18 p.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Mickael Istria updated JBIDE-12608:
-----------------------------------
Attachment: hudson-settings.xml
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
10:15 a.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12608:
------------------------------------
would it make sense to have a single "bootstrap" job that document and script
everything we need to get JBT/JBDS building:
* redeploy parent pom to Nexus
* redeploy settings.xml file(s) to Nexus and copy to somewhere under
/home/hudson/static_build_env/jbds
* redeploy target platform files to Nexus (or call downstream job, if we prefer)
* cache/update other useful scripts in /home/hudson/static_build_env/jbds, such as the
~/trunk/build/ folder?
* ensure /home/hudson/static_build_env/jbds/builds/staging/_composite_ is up to date
(pulled from tools@filemgmt.jboss.org:/downloads_htdocs/tools)
* prefetch SOA/EAP runtimes into /home/hudson/static_build_env/jbds/download-cache
* ... ?
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
10:21 a.m.
[
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
2:10 a.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12608:
----------------------------------------
This job
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk...
shows that using the hudson-settings.xml works fine (it remove usage of local.composite
profile in favor of mirroring of jbosstools-nightly-staging-composite, and then resolves
against local mirror)
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
11:23 a.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12608:
----------------------------------------
Change applied o trunk.
If everything is file, I'll create an hudson-settings.xml for stable_branch jobs and
will get all stable_branch jobs to use it.
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
2:03 a.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Mickael Istria resolved JBIDE-12608.
------------------------------------
Resolution: Done
Branch now uses mirrors as defined in hudson-settings-stable_branch.xml
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
9:04 a.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-12608:
-------------------------------
Attachment: settings.xml_0.png
settings.xml_1.png
Jenkins job config, part 1: fetch settings.xml
!settings.xml_0.png!
Jenkins job config, part 2: use settings.xml
!settings.xml_1.png!
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, settings.xml_0.png,
settings.xml_1.png
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
12:34 a.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-12608 at 10/18/12 1:33 AM:
--------------------------------------------------------------
Added new settings files to deal w/ more use cases: JBT components (minimum target
platform SR0c) vs. JBT aggregates (maximum target platform SR1a) vs. JBDS (JBDS SR1a TP
instead of JBT SR1a TP).
Unfortunately, settings are being ignored and the SR0c site (instead of SR1a) is still
being read, eg., here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stabl...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk...
was (Author: nickboldt):
Added new settings files to deal w/ more use cases: JBT components (minimum target
platform SR0c) vs. JBT aggregates (maximum target platform SR1a) vs. JBDS (JBDS SR1a TP
instead of JBT SR1a TP).
Unfortunately, settings are being ignored and the SR0c site (instead of SR1a) is still
being read, eg., here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stabl...
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, settings.xml_0.png,
settings.xml_1.png
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
12:36 a.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-12608 at 10/18/12 1:34 AM:
--------------------------------------------------------------
Added new settings files to deal w/ more use cases: JBT components (minimum target
platform SR0c) vs. JBT aggregates (maximum target platform SR1a) vs. JBDS (JBDS SR1a TP
instead of JBT SR1a TP).
Unfortunately, settings are being ignored and the SR0c site (instead of SR1a) is still
being read, eg., here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stabl...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk...
Worse, in the trunk case,
/home/hudson/static_build_env/jbds/builds/staging/_composite_/core/trunk/ appears to not
get correctly parsed so we get this:
{code}
[ERROR] Missing requirement: org.jboss.tools.site.core
raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT
requires 'org.jboss.tools.central.discovery.feature.feature.group 0.0.0' but
it could not be found
{code}
was (Author: nickboldt):
Added new settings files to deal w/ more use cases: JBT components (minimum target
platform SR0c) vs. JBT aggregates (maximum target platform SR1a) vs. JBDS (JBDS SR1a TP
instead of JBT SR1a TP).
Unfortunately, settings are being ignored and the SR0c site (instead of SR1a) is still
being read, eg., here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stabl...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk...
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, 4.0.0.CR1
Attachments: hudson-settings.xml, hudson-settings.xml, settings.xml_0.png,
settings.xml_1.png
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
12:36 a.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-12608:
-------------------------------
Fix Version/s: 4.0.0.CR1
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, 4.0.0.CR1
Attachments: hudson-settings.xml, hudson-settings.xml, settings.xml_0.png,
settings.xml_1.png
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
2:18 p.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-12608 at 10/19/12 3:16 PM:
--------------------------------------------------------------
Added new settings files to deal w/ more use cases: JBT components (minimum target
platform SR0c) vs. JBT aggregates (maximum target platform SR1a) vs. JBDS (JBDS SR1a TP
instead of JBT SR1a TP).
Unfortunately, settings are being ignored and the SR0c site (instead of SR1a) is still
being read, eg., here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stabl...
pulls from SR1a and http://download.jboss.org/jbosstools/updates/juno/SR0c/latest/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk...
pulls from SR1a ONLY
Hopefully
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stabl...
will fix the above issue.
was (Author: nickboldt):
Added new settings files to deal w/ more use cases: JBT components (minimum target
platform SR0c) vs. JBT aggregates (maximum target platform SR1a) vs. JBDS (JBDS SR1a TP
instead of JBT SR1a TP).
Unfortunately, settings are being ignored and the SR0c site (instead of SR1a) is still
being read, eg., here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stabl...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk...
Worse, in the trunk case,
/home/hudson/static_build_env/jbds/builds/staging/_composite_/core/trunk/ appears to not
get correctly parsed so we get this:
{code}
[ERROR] Missing requirement: org.jboss.tools.site.core
raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT
requires 'org.jboss.tools.central.discovery.feature.feature.group 0.0.0' but
it could not be found
{code}
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, 4.0.0.CR1
Attachments: hudson-settings.xml, hudson-settings.xml, settings.xml_0.png,
settings.xml_1.png
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
3:01 p.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12608:
------------------------------------
I think the reason why trunk is using SR1a and branch is using SR0c is this difference
between trunk and branch:
{code}
diff --git a/build/aggregate/pom.xml b/build/aggregate/pom.xml
index b4757d2..521c3d0 100644
--- a/build/aggregate/pom.xml
+++ b/build/aggregate/pom.xml
@@ -11,6 +11,13 @@
<artifactId>org.jboss.tools.site</artifactId>
<version>0.0.2-SNAPSHOT</version>
<packaging>pom</packaging>
+
+ <properties>
+ <!-- override parent pom to build from latest MAXIMUM TP instead of
MINIMUM -->
+
<targetPlatformGroup>${targetPlatformGroup-maximum}</targetPlatformGroup>
+
<jbosstools-target-site>${jbosstools-target-site-maximum}</jbosstools-target-site>
+ </properties>
+
<modules>
<module>../target-platform</module>
<module>site</module>
diff --git a/build/parent/pom.xml b/build/parent/pom.xml
index 726fe13..188e80e 100644
--- a/build/parent/pom.xml
+++ b/build/parent/pom.xml
@@ -48,6 +48,7 @@
<jbosstools-target-site>http://download.jboss.org/jbosstools/updates/ju...
+
<jbosstools-target-site-maximum>http://download.jboss.org/jbosstools/up...
{code}
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, 4.0.0.CR1
Attachments: hudson-settings.xml, hudson-settings.xml, settings.xml_0.png,
settings.xml_1.png
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
11:03 a.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12608:
----------------------------------------
Currently, mirrors are defined using the id of the repository. Since for a given id, there
can be several repos depending on branch for instance, it's better and less
error-prone to move to URLs as mirror key rather than repositoryId.
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.CR1
Attachments: hudson-settings.xml, hudson-settings.xml, settings.xml_0.png,
settings.xml_1.png
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
11:09 a.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Mickael Istria updated JBIDE-12608:
-----------------------------------
Attachment: hudson-settings.xml.patch
This patch proposes some changes to prevent from conflicting URLs on the same repoId.
[~nickboldt] Since it seems like you noticed some problem with mirrors, can you please
review it?
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.CR1
Attachments: hudson-settings.xml, hudson-settings.xml, hudson-settings.xml.patch,
settings.xml_0.png, settings.xml_1.png
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
5:03 a.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Mickael Istria resolved JBIDE-12608.
------------------------------------
Resolution: Done
Local profiles are no more used on CI, mirrors are used instead.
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.CR1
Attachments: hudson-settings.xml, hudson-settings.xml, hudson-settings.xml.patch,
settings.xml_0.png, settings.xml_1.png
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
10:06 p.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-12608 at 11/21/12 11:05 PM:
---------------------------------------------------------------
This patch - [^hudson-settings.xml.patch] proposes some changes to prevent from
conflicting URLs on the same repoId.
[~nickboldt] Since it seems like you noticed some problem with mirrors, can you please
review it?
was (Author: mickael_istria):
This patch proposes some changes to prevent from conflicting URLs on the same repoId.
[~nickboldt] Since it seems like you noticed some problem with mirrors, can you please
review it?
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.CR1
Attachments: hudson-settings.xml, hudson-settings.xml, hudson-settings.xml.patch,
settings.xml_0.png, settings.xml_1.png
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
10:06 p.m.
[
https://issues.jboss.org/browse/JBIDE-12608?page=com.atlassian.jira.plugi...
]
Nick Boldt closed JBIDE-12608.
------------------------------
Closing -- using mirrors of URLs seems to work better than mirrors of IDs.
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.CR1
Attachments: hudson-settings.xml, hudson-settings.xml, hudson-settings.xml.patch,
settings.xml_0.png, settings.xml_1.png
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
4880
days inactive
4950
days old
jbosstools-issues@lists.jboss.org
24 comments
3 participants
participants (3)
-
Max Rydahl Andersen (JIRA) -
Mickael Istria (JIRA)
-
Nick Boldt (JIRA)