-
1. Re: Problem creating local mirror of JBoss Tools for 3.1 final
dgolovin Mar 17, 2010 1:33 PM (in response to kenfrommera)1 of 1 people found this helpfulAs I remember p2 update doesn't use site.xml anymore. It is only required during build to define categories and relations between categories and features. I suppose you need to look into content.jar and locate in content.xm all units with
provides/provided@namespace=org.eclipse.equinox.p2.eclipse.type
provides/provided@name=feature
and then if you found unit with attributes values provided above use node
provides/provided
with attribute
provides/provided@namespace=org.eclipse.update.feature
to extract name of the feature from attribute
provides/provided@name
like for example for richfaces feature
<unit id='org.jboss.tools.richfaces.feature.feature.jar' version='3.1.0.v201003050540R-H56-GA'> <properties size='9'> <property name='org.eclipse.equinox.p2.name' value='%featureName'/> <property name='org.eclipse.equinox.p2.description' value='%description'/> <property name='org.eclipse.equinox.p2.description.url' value='http://www.jboss.org/tools'/> <property name='org.eclipse.equinox.p2.provider' value='%providerName'/> <property name='org.eclipse.update.feature.plugin' value='org.jboss.tools.vpe'/> <property name='df_LT.featureName' value='JBoss Tools RichFaces'/> <property name='df_LT.copyright' value='Copyright (c) 2007 Exadel, Inc and Red Hat, Inc.
Distributed under license by Red Hat, Inc. All rights reserved.
This program is made available under the terms of the
Eclipse Public License v1.0 which accompanies this distribution,
and is available at http://www.eclipse.org/legal/epl-v10.html
Contributors:
Exadel, Inc. and Red Hat, Inc. - initial API and implementation'/> <property name='df_LT.providerName' value='JBoss by Red Hat'/> <property name='df_LT.description' value='Visual editing'/> </properties> <provides size='3'> <provided namespace='org.eclipse.equinox.p2.iu' name='org.jboss.tools.richfaces.feature.feature.jar' version='3.1.0.v201003050540R-H56-GA'/> <provided namespace='org.eclipse.equinox.p2.eclipse.type' name='feature' version='1.0.0'/> <provided namespace='org.eclipse.update.feature' name='org.jboss.tools.richfaces.feature' version='3.1.0.v201003050540R-H56-GA'/> </provides> <filter>
-
2. Re: Problem creating local mirror of JBoss Tools for 3.1 final
nickboldt Mar 17, 2010 11:34 PM (in response to kenfrommera)Rather than pulling down pieces of the site, why not grab the whole archive in a single zip, then unpack it (if needed - you don't have to unzip the update site to use it) and use that? Here's the whole update site in a single download: http://downloads.sourceforge.net/jboss/JBossTools-Update-3.1.0.v201003050540R-H56-GA.zip1 of 1 people found this helpful -
3. Re: Problem creating local mirror of JBoss Tools for 3.1 final
dgolovin Mar 18, 2010 3:24 PM (in response to nickboldt)+1 for this option simple and elegant -
4. Re: Problem creating local mirror of JBoss Tools for 3.1 final
kenfrommera Mar 19, 2010 4:04 AM (in response to dgolovin)I would prefer mirroring only needed plug-ins, rather than having all JBoss Tools on my update site. It is because we need only few of them for our development environment.
Nevertheless, thank you for your answers. You gave me all needed information to understand how p2 update sites should be mirrored.
The following update command with the following ANT build script is used for mirroring at my site now:
Command:
eclipsec.exe -application org.eclipse.ant.core.antRunner -noSplash -consoleLog
ANT build script (build.xml):
<project name="iPat" basedir="." default="sync">
<target name="sync">
<p2.mirror source="http://download.jboss.org/jbosstools/updates/development" destination="file://E:/buildloop/eclipse-updates/site">
<slicingOptions followStrict="true" />
<iu id="org.jboss.tools.jbpm.common.feature.feature.group" />
<iu id="org.jboss.tools.cdi.feature.feature.group" />
<iu id="org.jboss.tools.flow.common.feature.feature.group" />
<iu id="org.hibernate.eclipse.feature.feature.group" />
<iu id="org.jboss.ide.eclipse.archives.feature.feature.group" />
<iu id="org.jboss.tools.bpel.feature.feature.group" />
<iu id="org.drools.eclipse.feature.feature.group" />
<iu id="org.guvnor.tools.feature.feature.group" />
<iu id="org.drools.eclipse.task.feature.feature.group" />
<iu id="org.jboss.tools.richfaces.feature.feature.group" />
<iu id="org.jboss.ide.eclipse.as.feature.feature.group" />
<iu id="org.jboss.tools.flow.jpdl4.feature.feature.group" />
<iu id="org.jboss.tools.jbpm4.feature.feature.group" />
<iu id="org.jboss.tools.jbpm.convert.feature.feature.group" />
<iu id="org.jbpm.gd.jpdl.feature.feature.group" />
<iu id="org.jboss.tools.jmx.feature.feature.group" />
<iu id="org.jboss.tools.seam.feature.feature.group" />
<iu id="org.jboss.tools.xulrunner.feature.feature.group" />
</p2.mirror>
</target>
</project>
Thank you for your help!