[
https://issues.jboss.org/browse/JBIDE-11065?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11065:
----------------------------------------
Feedback from [~nickboldt] after fixing JBIDE-13463
{quote}
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...; 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
{quote}
Replace build.xml by a Maven plugin
-----------------------------------
Key: JBIDE-11065
URL:
https://issues.jboss.org/browse/JBIDE-11065
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng
Reporter: Mickael Istria
Assignee: Mickael Istria
Priority: Minor
Fix For: 4.1.0.Alpha2
Attachments: jbide11065.png
In order to improve the build infrastructure and make it easier to share and consumes
with all components, we should replace build.xml by a Maven plugin and make it available
througn Nexus. It should follow the parent pom versioning.
--
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