[jbosstools-issues] [JBoss JIRA] (JBIDE-12629) Improve process to publish/consumes m2e-wtp

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719185#comment-12719185 ] 

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.xml
[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.xml
[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