[jbosstools-issues] [JBoss JIRA] Commented: (JBDS-1351) Create JBDS Distribution using productBuild.xml from PDE, P2 director or tycho eclipse-application packaging
[
https://jira.jboss.org/browse/JBDS-1351?page=com.atlassian.jira.plugin.sy...
]
Nick Boldt commented on JBDS-1351:
----------------------------------
create requirement or at least describe how to prepare all p2 repos
required during build
Try this:
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/bui...
That will generate a p2.mirror script from the .target file, fetch all the stuff via the
mirror script into a local p2 repo, then perform an install (p2.director) into a
particular version of Eclipse + its accompanying deltapack.
If you want to modify the script to do 5 installs into 5 different Eclipse SDKs (instead
of the platform binary + delta pack), it should be fairly trivial to add a new target to
the script to do so for multiple platforms instead of just linux 32/64, as currently
coded.
Bear in mind that this target platform includes deps for JBoss Tools, and does not include
additional reqs for things that are only in JBDS. We could have a second .target file for
that, if necessary.
Create JBDS Distribution using productBuild.xml from PDE, P2 director
or tycho eclipse-application packaging
------------------------------------------------------------------------------------------------------------
Key: JBDS-1351
URL: https://jira.jboss.org/browse/JBDS-1351
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: installer
Affects Versions: 4.0.0.Beta2
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 4.0.0.Beta2
Attachments: jbds-update-site.png, linux-gtk-x86-about.png,
linux-gtk-x86-installation-details.png, linux-gtk-x86-installation-root.png,
mac-carbon-x86-about.png, mac-cocoa-x86-installation-root.png
That might be implemented using tycho application packaging or PDE build features.
It would let us:
- have any number of JBDS distribution we want (for WEB, SOA and etc development);
- simplified installer build, because build script would just create installer from JBDS
distribution and EAP;
- no meta info generation during installation required;
- have only one way to launch JBDS using jbds.exe/jbds/jbds.app platform dependent
launcher.
- change root feature from Eclipse Platform to JBDS and make JBDS real eclipse based
product;
- trigger update for jbds by updating JBDS feature version;
- control list of available update sites in preferences.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira