[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-2246) P2 vs Installer ?

Nick Boldt (JIRA) jira-events at lists.jboss.org
Tue Nov 18 15:20:36 EST 2008


     [ https://jira.jboss.org/jira/browse/JBIDE-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBIDE-2246:
------------------------------

     Original Estimate: 0 minutes
    Remaining Estimate: 0 minutes
              Assignee: Nick Boldt  (was: Snjezana Peco)


One approach is this:

http://anonsvn.jboss.org/repos/jbosstools/trunk/i18n/build.xml

<target name="p2">
		<!-- Generate P2 metadata so that update manager won't take forever.
			http://wiki.eclipse.org/Equinox_p2_Metadata_Generator /home/sflaniga/apps/eclipse-ganymede/eclipse/eclipse
		 -->
		
		<exec executable="eclipse">
			<arg value="-application" />
			<arg value="org.eclipse.equinox.p2.metadata.generator.EclipseGenerator" />
			<arg value="-updateSite" />
			<arg value="${jardir}" />
			<arg value="-site" />
			<arg value="file://${jardir}/site.xml" />
			<arg value="-metadataRepository" />
			<arg value="file://${jardir}" />
			<arg value="-metadataRepositoryName" />
			<arg value="JBoss Tools Localization Update Site" />
			<arg value="-artifactRepository" />
			<arg value="file://${jardir}" />
			<arg value="-artifactRepositoryName" />
			<arg value="JBoss Tools Localization Artifacts" />
			<arg value="-compress" />
			<arg value="-append" />
			<arg value="-reusePack200Files" />
			<arg value="-noDefaultIUs" />
			<arg value="--launcher.suppressErrors" />
			<arg value="-nosplash" />
			<arg value="-consoleLog" />
			<arg value="-vmargs" />
			<arg value="-Xmx256m" />
		</exec>
	</target>
	
Another approach is this:

http://dev.eclipse.org/viewcvs/index.cgi/releng-common/tools/scripts/buildUpdateSiteMetadata.sh?root=Modeling_Project&view=markup

/usr/bin/java -cp $launcherJar:$generatorJar:$basebuilderDir/plugins org.eclipse.equinox.launcher.Main \
	  -application org.eclipse.equinox.p2.metadata.generator.EclipseGenerator \
	  -updateSite ${targetDir}/ -site file:${targetDir}/site.xml \
	  -metadataRepository file:${targetDir}/ -metadataRepositoryName "$projectNameVanity Update Site" \
	  -artifactRepository file:${targetDir}/ -artifactRepositoryName "$projectNameVanity Artifacts" \
	  -compress -reusePack200Files -vmargs -Xmx128M

> P2 vs Installer ?
> -----------------
>
>                 Key: JBIDE-2246
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-2246
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: Build/Releng, Eclipse Migration
>            Reporter: Max Rydahl Andersen
>            Assignee: Nick Boldt
>             Fix For: 3.0.0.GA
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Is P2 stable/good enough for basing our updatesites on ? 
> Can we use it to have a more finegrained control in the installer (eg. only install some parts?)
> Can it be used to install other things than plugins ? (e.g. JBossAS ?)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jbosstools-issues mailing list