[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...
]
Nick Boldt commented on JBIDE-13977:
------------------------------------
new FAQ entry "How do I ignore MD5sum checks when resolving dependencies or
building?" added to https://community.jboss.org/wiki/HowToBuildJBossTools41FAQ:
{quote}
If for some reason the site against which you're buidling has invalid metadata
(perhaps because the site's IUs were pack200'd AFTER the artifacts.xml /
content.xml metadata was created) you may get errors like "MD5 hash is not as
expected". To ignore these errors, simply build like this:
{code}mvn install -Declipse.p2.MD5ArtifactCheck=false -Declipse.p2.MD5Check=false{code}
{quote}
Meanwhile, still regenerating packed artifacts and then metadata for Kepler site. All
others have been fixed (I hope).
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, target-platform, 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