[jbosstools-issues] [JBoss JIRA] (JBIDE-13977) updates/requirements/*/build.xml scripts should include pack.gz artifacts (using p2.process.artifacts pack="true") to make resolving multiple.target faster
[
https://issues.jboss.org/browse/JBIDE-13977?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13977:
----------------------------------------
I think your request for refactoring is another enhancement that should be tracked in a
separate jira (with lower priority as it doesn't provide new feature and does not
drastically improves maintainability).
I agree it's not necessary for indigo and juno, but assuming we need to rebuild the
mirror one day in the future, it's cool to have pack.gz artifacts in those new
mirrors.
With those arguments, I'd like you to revise your judgement regarding PR 129 and merge
it "as it" (except if you notice something wrong in it), and we'll address
your comments as part of other jiras.
WDYT?
updates/requirements/*/build.xml scripts should include pack.gz
artifacts (using p2.process.artifacts pack="true") to make resolving
multiple.target faster
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13977
URL: https://issues.jboss.org/browse/JBIDE-13977
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite, upstream
Affects Versions: 4.1.0.Alpha2
Reporter: Nick Boldt
Assignee: Mickael Istria
Fix For: 4.1.0.Beta1
All ant scripts (updates/requirements/*/build.xml) used to mirror 3rd party reqs from
Eclipse.org and other places should be updated to generate .pack.gz artifacts too.
{code}<p2.process.artifacts pack="true"
repositoryPath="file:/${repoDirLocation}" />{code}
Refs:
*
http://git.eclipse.org/c/platform/eclipse.platform.releng.eclipsebuilder....
*
http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc....
--
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