[jbosstools-issues] [JBoss JIRA] (JBIDE-13463) Replace eclipse-update-site for aggregator by eclipse-repository

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-13463 at 3/9/13 12:59 AM:
-------------------------------------------------------------

PR looked good, but I added some extra bling to it: https://github.com/jbosstools/jbosstools-build-sites/pull/36

Verified w/ webtools-site and corestest-site.

Next:

* need to verify this works for the more complex cases of site and soa-site, which have additional steps (custom.build instead of basic.build task in build.xml).
* need to verify that publish.sh will work with a repository folder instead of a site folder. Might have to update shell scripts in jobs.
* need to disable redundant steps:
** migrate contents of associate.properties into <associateSites> in the pom.xml; disable that task
** disable duplicate generation of the index.html

* migrate these steps to maven:
** add.repo.properties :: use org.eclipse.wtp.releng.tools.addRepoProperties to add p2.statsURI and download.stats properties for a list of features
** remove.uncategorized.category
** remove.uninstallable (eg., central discovery feature)
** collect.zips :: look for http://download.jboss.org/jbosstools/builds/staging/<job_name>/logs/zip.list.txt; if found, load file get list of relative path zips to then fetch
** collect.metadata :: collect metadata (JOB_NAME, BUILD_ID, BUILD_NUMBER, WORKSPACE, HUDSON_SLAVE), zip file names+sizes+md5sums
** copy.to.site_assembly.zip :: ensure that org.jboss.tools.site.webtools-4.1.0-SNAPSHOT.zip contents match site_assembly.zip contents


                
      was (Author: nickboldt):
    PR looked good, but I added some extra bling to it: https://github.com/jbosstools/jbosstools-build-sites/pull/36

Verified w/ webtools-site and corestest-site.

Next:

* need to verify this works for the more complex cases of site and soa-site, which have additional steps (custom.build instead of basic.build task in build.xml).
* need to verify that publish.sh will work with a repository folder instead of a site folder. Might have to update shell scripts in jobs.
* need to disable redundant steps:
** migrate contents of associate.properties into <associateSites> in the pom.xml; disable that task
** disable duplicate generation of the index.html



                  
> Replace eclipse-update-site for aggregator by eclipse-repository
> ----------------------------------------------------------------
>
>                 Key: JBIDE-13463
>                 URL: https://issues.jboss.org/browse/JBIDE-13463
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: Build/Releng
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>             Fix For: 4.1.0.Alpha2
>
>
> The "eclipse-update-site" packaging type we've been using for aggregate sites is deprecated. Moreover it now shows some limitations (doesn't support pack.gz and other new Tycho stuff) that make it worth migrating to "eclipse-repository".

--
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