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

[Mickael Istria (JIRA)]

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

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-wtp-juno/

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