8:26 a.m.
Mickael Istria created JBIDE-12629:
--------------------------------------
Summary: Improve process to publish/consumes m2e-wtp
Key: JBIDE-12629
URL: https://issues.jboss.org/browse/JBIDE-12629
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform, UpStream
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
m2e gets pushed to the updates/requirements/m2e-wtp.juno url, whose content get
overridden. However, published target-platform still depends on old content until they get
modified.
We should find a better process that prevent target platforms from being broken, and that
would make build reproducible.
A solution would be to keep old versions of m2e-wtp under the m2e-wtp.juno folder (1 child
folder for each version), and to modify target-platform on request to use the newer
version.
--
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:59 a.m.
[
https://issues.jboss.org/browse/JBIDE-12629?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12629:
----------------------------------------
So it appears that output of the m2e-wtp-juno job is published at
http://download.jboss.org/jbosstools/builds/staging/m2e-wtp-juno/all/repo/ and
http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2e-w...
What makes the build complicated:
* Publishing automatically to requirements/ in a bad idea, since we expect content of site
in requirements to be fixed.
* Relying on a dynamic site in target-platform.
So I suggest:
* Stop pushing m2e-wtp-juno to requirements/
* create a requirements/m2e-wtp which would mirror content of official m2e-wtp builds
(from eclipse.org).
[~nickboldt] I need your approval for this.
Improve process to publish/consumes m2e-wtp
-------------------------------------------
Key: JBIDE-12629
URL: https://issues.jboss.org/browse/JBIDE-12629
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform, UpStream
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
m2e gets pushed to the updates/requirements/m2e-wtp.juno url, whose content get
overridden. However, published target-platform still depends on old content until they get
modified.
We should find a better process that prevent target platforms from being broken, and that
would make build reproducible.
A solution would be to keep old versions of m2e-wtp under the m2e-wtp.juno folder (1
child folder for each version), and to modify target-platform on request to use the newer
version.
--
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:08 a.m.
[
https://issues.jboss.org/browse/JBIDE-12629?page=com.atlassian.jira.plugi...
]
Mickael Istria reassigned JBIDE-12629:
--------------------------------------
Assignee: Mickael Istria (was: Nick Boldt)
Improve process to publish/consumes m2e-wtp
-------------------------------------------
Key: JBIDE-12629
URL: https://issues.jboss.org/browse/JBIDE-12629
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform, UpStream
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Beta1
m2e gets pushed to the updates/requirements/m2e-wtp.juno url, whose content get
overridden. However, published target-platform still depends on old content until they get
modified.
We should find a better process that prevent target platforms from being broken, and that
would make build reproducible.
A solution would be to keep old versions of m2e-wtp under the m2e-wtp.juno folder (1
child folder for each version), and to modify target-platform on request to use the newer
version.
--
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:26 a.m.
[
https://issues.jboss.org/browse/JBIDE-12629?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12629:
----------------------------------------
I created the mirror for m2e-wtp:
http://download.jboss.org/jbosstools/updates/requirements/m2e-wtp/0.16.0.... ,
a build.xml file is committed.
Improve process to publish/consumes m2e-wtp
-------------------------------------------
Key: JBIDE-12629
URL: https://issues.jboss.org/browse/JBIDE-12629
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform, UpStream
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Beta1
m2e gets pushed to the updates/requirements/m2e-wtp.juno url, whose content get
overridden. However, published target-platform still depends on old content until they get
modified.
We should find a better process that prevent target platforms from being broken, and that
would make build reproducible.
A solution would be to keep old versions of m2e-wtp under the m2e-wtp.juno folder (1
child folder for each version), and to modify target-platform on request to use the newer
version.
--
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-12629?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12629:
------------------------------------
I'm already half-way there, actually.
If you look in here [1] you'll see I'm already pulling m2e-wtp + latest m2e +
m2e-jdt, m2e-apt, etc. into a single snapshot, then sharing that with the juno
requirements mirror [2].
So... would it not be simpler to get Fred to announce when it's time to pull a new
mirror (JBIDE-12516, JBIDE-12517) and have you or I do so, updating not just the reqs but
the TP at the same time?
[1] http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/build...
[2] http://download.jboss.org/jbosstools/updates/juno/SR0a/
Seems like the simpler solution here would be to remove
"../../requirements/m2eclipse/m2e-wtp-juno/" from the composite reqs mirror [2]
so that its content will always match the .target files.
Improve process to publish/consumes m2e-wtp
-------------------------------------------
Key: JBIDE-12629
URL: https://issues.jboss.org/browse/JBIDE-12629
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform, UpStream
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Beta1
m2e gets pushed to the updates/requirements/m2e-wtp.juno url, whose content get
overridden. However, published target-platform still depends on old content until they get
modified.
We should find a better process that prevent target platforms from being broken, and that
would make build reproducible.
A solution would be to keep old versions of m2e-wtp under the m2e-wtp.juno folder (1
child folder for each version), and to modify target-platform on request to use the newer
version.
--
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:11 a.m.
[
https://issues.jboss.org/browse/JBIDE-12629?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-12629 at 9/17/12 12:11 PM:
--------------------------------------------------------------
I'm already half-way there, actually.
If you look in here [1] you'll see I'm already pulling m2e-wtp + latest m2e +
m2e-jdt, m2e-apt, etc. into a single snapshot, then sharing that with the juno
requirements mirror [2].
So... would it not be simpler to get Fred to announce when it's time to pull a new
mirror (JBIDE-12516, JBIDE-12517) and have you or I do so, updating not just the reqs but
the TP at the same time?
[1] http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/build...
[2] http://download.jboss.org/jbosstools/updates/juno/SR0a/
So rather than worrying about a second builder for m2e-wtp separate from the overall m2e
one, could we not just remove "requirements/m2eclipse/m2e-wtp-juno/" from the
composite reqs mirror [2] so that its content will always match the .target files?
was (Author: nickboldt):
I'm already half-way there, actually.
If you look in here [1] you'll see I'm already pulling m2e-wtp + latest m2e +
m2e-jdt, m2e-apt, etc. into a single snapshot, then sharing that with the juno
requirements mirror [2].
So... would it not be simpler to get Fred to announce when it's time to pull a new
mirror (JBIDE-12516, JBIDE-12517) and have you or I do so, updating not just the reqs but
the TP at the same time?
[1] http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/build...
[2] http://download.jboss.org/jbosstools/updates/juno/SR0a/
Seems like the simpler solution here would be to remove
"../../requirements/m2eclipse/m2e-wtp-juno/" from the composite reqs mirror [2]
so that its content will always match the .target files.
Improve process to publish/consumes m2e-wtp
-------------------------------------------
Key: JBIDE-12629
URL: https://issues.jboss.org/browse/JBIDE-12629
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform, UpStream
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Beta1
m2e gets pushed to the updates/requirements/m2e-wtp.juno url, whose content get
overridden. However, published target-platform still depends on old content until they get
modified.
We should find a better process that prevent target platforms from being broken, and that
would make build reproducible.
A solution would be to keep old versions of m2e-wtp under the m2e-wtp.juno folder (1
child folder for each version), and to modify target-platform on request to use the newer
version.
--
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:21 a.m.
[
https://issues.jboss.org/browse/JBIDE-12629?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12629:
----------------------------------------
[~nickboldt]
If you look in here [1] you'll see I'm already pulling
m2e-wtp + latest m2e + m2e-jdt, m2e-apt, etc. into a single snapshot, then sharing that
with the juno requirements mirror [2].
Ok, did not notice that, I think it's a good approach. We should replace
"URL3" in the build.xml file to reference the Eclipse build. WDYT?
So... would it not be simpler to get Fred to announce when it's
time to pull a new mirror (JBIDE-12516, JBIDE-12517) and have you or I do so, updating not
just the reqs but the TP at the same time?
Agreed.
So rather than worrying about a second builder for m2e-wtp separate
from the overall m2e one, could we not just remove
"requirements/m2eclipse/m2e-wtp-juno/" from the composite reqs mirror [2] so
that its content will always match the .target files?
Agreed again.
Improve process to publish/consumes m2e-wtp
-------------------------------------------
Key: JBIDE-12629
URL: https://issues.jboss.org/browse/JBIDE-12629
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform, UpStream
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Beta1
m2e gets pushed to the updates/requirements/m2e-wtp.juno url, whose content get
overridden. However, published target-platform still depends on old content until they get
modified.
We should find a better process that prevent target platforms from being broken, and that
would make build reproducible.
A solution would be to keep old versions of m2e-wtp under the m2e-wtp.juno folder (1
child folder for each version), and to modify target-platform on request to use the newer
version.
--
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:27 a.m.
[
https://issues.jboss.org/browse/JBIDE-12629?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12629:
------------------------------------
Did not know there was an Eclipse.org hosted "official" build we could use. I
only know of the URLs that Fred gives me. So, yes, we could certainly switch to another
one. Oh, BTW, related to all this is JBIDE-12294 - once m2e-wtp stops changing every week,
we can remove the external refs to the moving target.
Improve process to publish/consumes m2e-wtp
-------------------------------------------
Key: JBIDE-12629
URL: https://issues.jboss.org/browse/JBIDE-12629
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform, UpStream
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Beta1
m2e gets pushed to the updates/requirements/m2e-wtp.juno url, whose content get
overridden. However, published target-platform still depends on old content until they get
modified.
We should find a better process that prevent target platforms from being broken, and that
would make build reproducible.
A solution would be to keep old versions of m2e-wtp under the m2e-wtp.juno folder (1
child folder for each version), and to modify target-platform on request to use the newer
version.
--
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:09 p.m.
[
https://issues.jboss.org/browse/JBIDE-12629?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12629:
------------------------------------
http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/build... updated to
pull latest milestone from eclipse.org instead of jboss.org
http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/20120... new
mirror pulled including m2e-wtp 0.16.0.20120914-0945
http://download.jboss.org/jbosstools/updates/juno/SR0a/ updated w/ link to updated
m2e-wtp, and CI build removed (m2e-wtp-juno)
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/ *.target* updatd to
point to latest m2e-wtp 0.16.0.20120914-0945
Improve process to publish/consumes m2e-wtp
-------------------------------------------
Key: JBIDE-12629
URL: https://issues.jboss.org/browse/JBIDE-12629
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform, UpStream
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Beta1
m2e gets pushed to the updates/requirements/m2e-wtp.juno url, whose content get
overridden. However, published target-platform still depends on old content until they get
modified.
We should find a better process that prevent target platforms from being broken, and that
would make build reproducible.
A solution would be to keep old versions of m2e-wtp under the m2e-wtp.juno folder (1
child folder for each version), and to modify target-platform on request to use the newer
version.
--
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:11 p.m.
[
https://issues.jboss.org/browse/JBIDE-12629?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-12629 at 9/17/12 1:11 PM:
-------------------------------------------------------------
http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/build... updated to
pull latest milestone from eclipse.org instead of jboss.org
http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/20120... new
mirror pulled including m2e-wtp 0.16.0.20120914-0945
http://download.jboss.org/jbosstools/updates/juno/SR0a/ updated w/ link to updated
m2e-wtp, and CI build removed (m2e-wtp-juno)
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/ .target and
.target.p2mirror.xml files updated to point to latest m2e-wtp 0.16.0.20120914-0945
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/parent/pom.xml updated to point at
20120917-1234 for JBDS builds
was (Author: nickboldt):
http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/build... updated
to pull latest milestone from eclipse.org instead of jboss.org
http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/20120... new
mirror pulled including m2e-wtp 0.16.0.20120914-0945
http://download.jboss.org/jbosstools/updates/juno/SR0a/ updated w/ link to updated
m2e-wtp, and CI build removed (m2e-wtp-juno)
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/ *.target* updatd to
point to latest m2e-wtp 0.16.0.20120914-0945
Improve process to publish/consumes m2e-wtp
-------------------------------------------
Key: JBIDE-12629
URL: https://issues.jboss.org/browse/JBIDE-12629
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform, UpStream
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Beta1
m2e gets pushed to the updates/requirements/m2e-wtp.juno url, whose content get
overridden. However, published target-platform still depends on old content until they get
modified.
We should find a better process that prevent target platforms from being broken, and that
would make build reproducible.
A solution would be to keep old versions of m2e-wtp under the m2e-wtp.juno folder (1
child folder for each version), and to modify target-platform on request to use the newer
version.
--
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:41 a.m.
New subject: [JBoss JIRA] (JBIDE-12629) Improve process to publish/consume m2e-wtp
[
https://issues.jboss.org/browse/JBIDE-12629?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-12629:
-------------------------------
Summary: Improve process to publish/consume m2e-wtp (was: Improve process to
publish/consumes m2e-wtp)
Improve process to publish/consume m2e-wtp
------------------------------------------
Key: JBIDE-12629
URL: https://issues.jboss.org/browse/JBIDE-12629
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform, UpStream
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Beta1
m2e gets pushed to the updates/requirements/m2e-wtp.juno url, whose content get
overridden. However, published target-platform still depends on old content until they get
modified.
We should find a better process that prevent target platforms from being broken, and that
would make build reproducible.
A solution would be to keep old versions of m2e-wtp under the m2e-wtp.juno folder (1
child folder for each version), and to modify target-platform on request to use the newer
version.
--
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:43 a.m.
New subject: [JBoss JIRA] (JBIDE-12629) Improve process to publish/consume m2e-wtp
[
https://issues.jboss.org/browse/JBIDE-12629?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-12629:
-------------------------------
Fix Version/s: 4.0.0.Alpha2
(was: 4.0.0.Beta1)
Improve process to publish/consume m2e-wtp
------------------------------------------
Key: JBIDE-12629
URL: https://issues.jboss.org/browse/JBIDE-12629
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform, UpStream
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Alpha2
m2e gets pushed to the updates/requirements/m2e-wtp.juno url, whose content get
overridden. However, published target-platform still depends on old content until they get
modified.
We should find a better process that prevent target platforms from being broken, and that
would make build reproducible.
A solution would be to keep old versions of m2e-wtp under the m2e-wtp.juno folder (1
child folder for each version), and to modify target-platform on request to use the newer
version.
--
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:43 a.m.
New subject: [JBoss JIRA] (JBIDE-12629) Improve process to publish/consume m2e-wtp
[
https://issues.jboss.org/browse/JBIDE-12629?page=com.atlassian.jira.plugi...
]
Nick Boldt closed JBIDE-12629.
------------------------------
Resolution: Done
Closing. See linked issues for followup work
Improve process to publish/consume m2e-wtp
------------------------------------------
Key: JBIDE-12629
URL: https://issues.jboss.org/browse/JBIDE-12629
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform, UpStream
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Alpha2
m2e gets pushed to the updates/requirements/m2e-wtp.juno url, whose content get
overridden. However, published target-platform still depends on old content until they get
modified.
We should find a better process that prevent target platforms from being broken, and that
would make build reproducible.
A solution would be to keep old versions of m2e-wtp under the m2e-wtp.juno folder (1
child folder for each version), and to modify target-platform on request to use the newer
version.
--
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
4957
days inactive
4958
days old
jbosstools-issues@lists.jboss.org
12 comments
2 participants
participants (2)
-
Mickael Istria (JIRA) -
Nick Boldt (JIRA)