[
https://issues.jboss.org/browse/JBDS-1475?page=com.atlassian.jira.plugin....
]
Denis Golovin resolved JBDS-1475.
---------------------------------
Resolution: Done
it actually does. p2 director application can be used to materialize JBDS from remote
update site it just requires to provide p2 os,ws and arch explicitly like:
-p2.os linux -p2.ws gtk -p2.arch x86
to make p2 director work right way and extract binary root features for jbdevstudio
launcher.
Example of installing JBDS using p2 Director application
~/Java/eclipse-sdk-linux-gtk-x86-helios/eclipse -application
org.eclipse.equinox.p2.director -repository file:///home/eskimo/Temp/mirror7 -installIU
com.jboss.jbds.all -profileProperties org.eclipse.update.install.features=true
-destination /home/eskimo/Temp/jbds-test-7 -profile profile -debug -p2.os linux -p2.ws gtk
-p2.arch x86 -consoleLog -debug -purgeHistory
-pureHistory is required to cleanup eclipse installation history and log
p2 repo generated during p2 product build doesn't contains binary
features with jbdevstudio launcher for linux and windows platforms
------------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-1475
URL:
https://issues.jboss.org/browse/JBDS-1475
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Build, P2 Enabled Product
Affects Versions: 4.0.0.CR1
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 4.0.0.CR1
p2 installer and p2 director installs com.jboss.jbds.all root IU from jbds update site
without jbdevstudio launcher. This means PDE p2 build generates them from eclipse binary
root features, but doesn't update p2repo meta data and artifacts. If we have p2 repo
without jbdevstudio launchers, launcher and launcher ini file cannot be updated between
releases by installing JBDS updates from update site.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira