[jbosstools-issues] [JBoss JIRA] Commented: (JBDS-1351) Create JBDS Distribution using productBuild.xml from PDE, P2 director or tycho eclipse-application packaging

[Denis Golovin (JIRA)]

    [ https://jira.jboss.org/browse/JBDS-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558024#action_12558024 ] 

Denis Golovin commented on JBDS-1351:
-------------------------------------

created new jbds-all-package builder as part of PDE based jbdsbuild.
Build locally using downloaded and mirrored (where was no repo available for dowmload like, for instance, tptp ) repozitories: jbdevstudio repo was used as well.
Everything almost fine (see attached pictures) but several problems are still unsolved:
1. org.eclipse.equinox.transform plugin is not included (probably simple to include)
2. testng and spring is not included (should be declared as requirements in jbds.product feature and p2 repos should be available during build)
3. Some branding issues related to icons for launchers should be taken care of
4. Installer build have not updated yet (no meta generation is required during installation and installer just should pack zip for provided distribution)

First problem to  solve is create requirement or at least describe how to prepare all p2 repos required during build (about 800M) to make it work on hudson.
Full build for 5 platforms we support takes about 1 hour 15 minutes.

> 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
>    Affects Versions: 4.0.0.Beta2
>            Reporter: Denis Golovin
>            Assignee: Denis Golovin
>             Fix For: 4.0.0.Beta2
>
>
> 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