[JBoss JIRA] Created: (JBDS-1351) Create JBDS Distribution using productBuild.xml from PDE, P2 director or tycho eclipse-application packaging
4:13 a.m.
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
7:27 p.m.
New subject: [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...
]
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
7:29 p.m.
New subject: [JBoss JIRA] Updated: (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...
]
Denis Golovin updated JBDS-1351:
--------------------------------
Attachment: linux-gtk-x86-installation-details.png
linux-gtk-x86-about.png
jbds-update-site.png
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
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
7:29 p.m.
New subject: [JBoss JIRA] Updated: (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...
]
Denis Golovin updated JBDS-1351:
--------------------------------
Attachment: mac-cocoa-x86-installation-root.png
mac-carbon-x86-about.png
linux-gtk-x86-installation-root.png
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
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
4:55 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
Max Andersen updated JBDS-1351:
-------------------------------
Component/s: installer
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
12:02 p.m.
New subject: [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
7:49 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
Max Andersen updated JBDS-1351:
-------------------------------
Fix Version/s: 4.0.0.CR1
(was: 4.0.0.Beta2)
Most installer issues moved of B2
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.CR1
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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:14 a.m.
New subject: [JBoss JIRA] Resolved: (JBDS-1351) Create JBDS Distribution using productBuild.xml from PDE, P2 director or tycho eclipse-application packaging
[
https://issues.jboss.org/browse/JBDS-1351?page=com.atlassian.jira.plugin....
]
Denis Golovin resolved JBDS-1351.
---------------------------------
Resolution: Done
Create JBDS Distribution using productBuild.xml from PDE, P2 director
or tycho eclipse-application packaging
------------------------------------------------------------------------------------------------------------
Key: JBDS-1351
URL: https://issues.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.CR1
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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:14 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1351) Create JBDS Distribution using productBuild.xml from PDE, P2 director or tycho eclipse-application packaging
[
https://issues.jboss.org/browse/JBDS-1351?page=com.atlassian.jira.plugin....
]
Denis Golovin commented on JBDS-1351:
-------------------------------------
build is fixed and running on hudson
- from trunk
https://hudson.qa.jboss.com/hudson/view/DevStudio_Disabled/job/devstudio-...
- from branch for coming release
https://hudson.qa.jboss.com/hudson/view/DevStudio_Disabled/job/devstudio-...
Last build from trunk is available through this link
http://reports.qa.atl.jboss.com/binaries/RHDS/builds/staging/devstudio-4....
Create JBDS Distribution using productBuild.xml from PDE, P2 director
or tycho eclipse-application packaging
------------------------------------------------------------------------------------------------------------
Key: JBDS-1351
URL: https://issues.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.CR1
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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:29 p.m.
New subject: [JBoss JIRA] Commented: (JBDS-1351) Create JBDS Distribution using productBuild.xml from PDE, P2 director or tycho eclipse-application packaging
[
https://issues.jboss.org/browse/JBDS-1351?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-1351:
----------------------------------
_stable_branch jobs are currently disabled because they point at the Beta2 sources and
therefore are obsolete (until we code freeze for CR1 and branch again). So... that
job's output shouldn't be used until post-branch.
Create JBDS Distribution using productBuild.xml from PDE, P2 director
or tycho eclipse-application packaging
------------------------------------------------------------------------------------------------------------
Key: JBDS-1351
URL: https://issues.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.CR1
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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5592
days inactive
5667
days old
jbosstools-issues@lists.jboss.org
9 comments
3 participants
participants (3)
-
Denis Golovin (JIRA) -
Max Andersen (JIRA)
-
Nick Boldt (JIRA)