[ http://jira.jboss.com/jira/browse/JBIDE-2246?page=all ] Max Rydahl Andersen updated JBIDE-2246: --------------------------------------- Fix Version/s: 3.0.Exploration (was: 3.0.x) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2246?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-2246: --------------------------------------- Fix Version/s: 3.0.0.beta (was: 3.0.0.alpha) -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2246?page=com.atlassian.jira.plu... ] Nick Boldt commented on JBIDE-2246: ----------------------------------- Yes. In fact, adding p2 metadata to your update site(s) will make them faster than the old-school Eclipse 3.3 update sites. Internally, p2 has to read the site.xml and generate the metadata, so if you produce that up front, the end user will benefit. With p2's Update UI, the end user can select any of the exposed features and install those. If your update site only has, for example, and SDK, Runtime, and Examples feature, then that's all p2 can install; however, if your SDK and Runtime contain smaller features which you expose to the update site, then p2 (and 3.3's Update, too) can install more selectively. The major difference in this scenario between 3.4 and 3.3 is performance -- p2 is multithreaded. In theory, yes. An IU (installable unit) need not be a feature containing plugins. It can also be fragments or binaries -- in this way, you can now update Eclipse 3.4 to Eclipse 3.4.1 and p2 should not just install new features/plugins, but the eclipse executable as well. (I haven't done this, but it's part of p2's stated spec.) > 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, Ganymede > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Fix For: 3.0.0.cr1 > > > Is P2 stable/good enough for basing our updatesites on ? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2246?page=com.atlassian.jira.plu... ] 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/buil... /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 -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2246?page=com.atlassian.jira.plu... ] Nick Boldt commented on JBIDE-2246: ----------------------------------- You're right -- I was looking for a JIRA to contain the work of adding p2 metadata to the existing JBDS/JBT update site. I understood the issue here was not to change the way the installer works but to provide the end user with more control when installing plugins. Perhaps we need to back up and decide what the problem is -- does the installer (which I've as yet never seen or used) lack granularity? Or are we just looking to make the update sites p2-enabled and thus more performant? p2 still uses features as its base unit of install, so if we want more granular features to be installable, we need smaller features. We can have nested features so that people have options (install the whole foo SDK, including source and doc) or just the foo runtime). -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2246?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-2246: --------------------------------------- Fix Version/s: LATER (was: 3.0.0.CR2) a p2 installer is not happening for GA -- 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