[JBoss JIRA] (JBTIS-523) Create a demonstration/ prototype installer for Fuse Tooling support
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-523?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-523:
-----------------------------
Description:
The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go).
Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype:
https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists:
https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
This installer has the Fuse Tooling pre-selected. A future option here would be to create an installer with *just* the Fuse Tooling components available. Another future option would be to change the default perspective to the component-specific perspective (i.e. Fuse Integration perspective) in the generated installer.
Here's a usability scenario targeting Fuse Tooling:
{code}
Test scenario A:
1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-d...
3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar`
4. Select the Software/Update tab in the JBoss Central view.
5. Select the checkbox to Enable Early Access, and click Yes to accept the warning.
6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section.
Select the following item:
JBoss Fuse Development
7. Accept/ respond 'Yes' and restart
8. Select Window > Perspective > Open Perspective > Fuse Integration
-----------------------------------------------------------------------------
Test scenario B:
1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar`
4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail!
5. Accept/ respond 'Yes' and restart
6. Select Window > Perspective > Open Perspective > Fuse Integration
-----------------------------------------------------------------------------
Test scenario C:
1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar`
4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer
5. Accept/ respond 'Yes' and restart
6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration
-----------------------------------------------------------------------------
Test scenario D: (future - not available currently)
1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar`
4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer
5. Accept/ respond 'Yes' and restart
JBDS comes up in the Fuse Integration perspective - read to go.
{code}
Comments welcome!
was:
The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go).
Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype:
https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists:
https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
This installer has the Fuse Tooling pre-selected. A future option here would be to create an installer with *just* the Fuse Tooling components available. Another future option would be to change the default perspective to the component-specific perspective (i.e. Fuse Integration perspective) in the generated installer.
Here's a usability scenario targeting Fuse Tooling:
{code}
Test scenario A:
1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-d...
3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar`
4. Select the Software/Update tab in the JBoss Central view.
5. Select the checkbox to Enable Early Access, and click Yes to accept the warning.
6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section.
Select the following item:
JBoss Fuse Development
7. Accept/ respond 'Yes' and restart
8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration
-----------------------------------------------------------------------------
Test scenario B:
1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar`
4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail!
5. Accept/ respond 'Yes' and restart
6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration
-----------------------------------------------------------------------------
Test scenario C:
1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar`
4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer
5. Accept/ respond 'Yes' and restart
6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration
-----------------------------------------------------------------------------
Test scenario D: (future - not available currently)
1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar`
4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer
5. Accept/ respond 'Yes' and restart
JBDS comes up in the Fuse Integration perspective - read to go.
{code}
Comments welcome!
> Create a demonstration/ prototype installer for Fuse Tooling support
> --------------------------------------------------------------------
>
> Key: JBTIS-523
> URL: https://issues.jboss.org/browse/JBTIS-523
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Priority: Optional
> Attachments: sai1.png
>
>
> The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go).
> Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype:
> https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists:
> https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> This installer has the Fuse Tooling pre-selected. A future option here would be to create an installer with *just* the Fuse Tooling components available. Another future option would be to change the default perspective to the component-specific perspective (i.e. Fuse Integration perspective) in the generated installer.
> Here's a usability scenario targeting Fuse Tooling:
> {code}
> Test scenario A:
>
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-d...
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar`
> 4. Select the Software/Update tab in the JBoss Central view.
> 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning.
> 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section.
> Select the following item:
> JBoss Fuse Development
> 7. Accept/ respond 'Yes' and restart
> 8. Select Window > Perspective > Open Perspective > Fuse Integration
> -----------------------------------------------------------------------------
> Test scenario B:
>
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail!
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> -----------------------------------------------------------------------------
> Test scenario C:
>
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar`
> 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration
> -----------------------------------------------------------------------------
> Test scenario D: (future - not available currently)
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar`
> 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer
> 5. Accept/ respond 'Yes' and restart
> JBDS comes up in the Fuse Integration perspective - read to go.
> {code}
> Comments welcome!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20531) Expose additional service ports from deploy docker image wizard
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20531?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-20531:
----------------------------------
Attachment: service port edit dialog.png
> Expose additional service ports from deploy docker image wizard
> ---------------------------------------------------------------
>
> Key: JBIDE-20531
> URL: https://issues.jboss.org/browse/JBIDE-20531
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: docker
> Fix For: 4.3.1.Beta1
>
> Attachments: Service and routing page.png, service port edit dialog.png
>
>
> Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image
> * Also only remove those which were added
> * Only reset those which are defaults
> * Edit via double click
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ contains wrong versions
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-20993 at 10/20/15 1:45 PM:
--------------------------------------------------------------
I put these in place to mirror what's on https://devstudio.redhat.com --
* https://devstudio.redhat.com/9.0 == https://devstudio.redhat.com/mars
* https://devstudio.redhat.com/10.0 == https://devstudio.redhat.com/neon
The reason for this is to simplify some of the release engineering / publishing / auditing scripts, so that we can key in on a common "mars" or "neon" path segment regardless of whether we're working with JBT or JBDS.
But then I thought, if there's a symlink from 9.0 -> mars on the ds.jb.com server, surely we should have the opposite symlink on the dl.jb.o server, mars -> 9.0.
This has been in place since May 21, 2015. I added the equivalent 10.0 / neon links on Sept 18, 2015. I don't recall if there was an announcement about this since I considered it simply a releng thing not worthy of announcement. And "under the covers" change, if you will.
While I understand your fear/confusion/rage, I still believe that having a logical mapping on the servers between the JBDS versioning and the JBT versioning is a good thing.
--
Would you be happy if instead of a /10.0/ folder for JBDS, we simply used a /neon/ folder? I would +1 that plan, if you really don't like seeing "10.0" on the dl.jb.o server. At least that way the folder structure would be identical for both JBT and JBDS, as they'd both target a /neon/ folder.
Thus we would publish to URLs like these:
{quote}
https://devstudio.redhat.com/neon/snapshots/builds/
https://devstudio.redhat.com/neon/snapshots/updates/
https://devstudio.redhat.com/neon/staging/builds/
https://devstudio.redhat.com/neon/staging/updates/
and
http://download.jboss.org/jbosstools/neon/snapshots/builds/
http://download.jboss.org/jbosstools/neon/snapshots/updates/
http://download.jboss.org/jbosstools/neon/staging/builds/
http://download.jboss.org/jbosstools/neon/staging/updates/
{quote}
instead of
{quote}
https://devstudio.redhat.com/10.0/snapshots/builds/
https://devstudio.redhat.com/10.0/snapshots/updates/
https://devstudio.redhat.com/10.0/staging/builds/
https://devstudio.redhat.com/10.0/staging/updates/
and
http://download.jboss.org/jbosstools/neon/snapshots/builds/
http://download.jboss.org/jbosstools/neon/snapshots/updates/
http://download.jboss.org/jbosstools/neon/staging/builds/
http://download.jboss.org/jbosstools/neon/staging/updates/
{quote}
(Of course there would also be similar URLs with /development/ and /stable/ in future.)
was (Author: nickboldt):
I put these in place to mirror what's on https://devstudio.redhat.com --
* https://devstudio.redhat.com/9.0 == https://devstudio.redhat.com/mars
* https://devstudio.redhat.com/10.0 == https://devstudio.redhat.com/neon
The reason for this is to simplify some of the release engineering / publishing / auditing scripts, so that we can key in on a common "mars" or "neon" path segment regardless of whether we're working with JBT or JBDS.
But then I thought, if there's a symlink from 9.0 -> mars on the ds.jb.com server, surely we should have the opposite symlink on the dl.jb.o server, mars -> 9.0.
This has been in place since May 21, 2015. I added the equivalent 10.0 / neon links on Sept 18, 2015. I don't recall if there was an announcement about this since I considered it simply a releng thing not worthy of announcement. And "under the covers" change, if you will.
While I understand your fear/confusion/rage, I still believe that having a logical mapping on the servers between the JBDS versioning and the JBT versioning is a good thing.
--
Would you be happy if instead of a /10.0 folder we simply used a /neon/ folder? I would +1 that plan, if you really don't like seeing "10.0" on the dl.jb.o server. At least that way the folder structure would be identical for both JBT and JBDS, as they'd both target a /neon/ folder.
> http://download.jboss.org/jbosstools/ contains wrong versions
> -------------------------------------------------------------
>
> Key: JBIDE-20993
> URL: https://issues.jboss.org/browse/JBIDE-20993
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1
>
>
> while discussing download.jboss.org with [~dgolovin] we found
> http://download.jboss.org/jbosstools/9.0/
> http://download.jboss.org/jbosstools/10.0/
> These look to be links to mars and neon.
> This is mixing in devstudio versioning with jbosstools which is just really confusing.
> No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme.
> I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ contains wrong versions
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-20993 at 10/20/15 1:41 PM:
--------------------------------------------------------------
I put these in place to mirror what's on https://devstudio.redhat.com --
* https://devstudio.redhat.com/9.0 == https://devstudio.redhat.com/mars
* https://devstudio.redhat.com/10.0 == https://devstudio.redhat.com/neon
The reason for this is to simplify some of the release engineering / publishing / auditing scripts, so that we can key in on a common "mars" or "neon" path segment regardless of whether we're working with JBT or JBDS.
But then I thought, if there's a symlink from 9.0 -> mars on the ds.jb.com server, surely we should have the opposite symlink on the dl.jb.o server, mars -> 9.0.
This has been in place since May 21, 2015. I added the equivalent 10.0 / neon links on Sept 18, 2015. I don't recall if there was an announcement about this since I considered it simply a releng thing not worthy of announcement. And "under the covers" change, if you will.
While I understand your fear/confusion/rage, I still believe that having a logical mapping on the servers between the JBDS versioning and the JBT versioning is a good thing.
--
Would you be happy if instead of a /10.0 folder we simply used a /neon/ folder? I would +1 that plan, if you really don't like seeing "10.0" on the dl.jb.o server. At least that way the folder structure would be identical for both JBT and JBDS, as they'd both target a /neon/ folder.
was (Author: nickboldt):
I put these in place to mirror what's on https://devstudio.redhat.com --
* https://devstudio.redhat.com/9.0 == https://devstudio.redhat.com/mars
* https://devstudio.redhat.com/10.0 == https://devstudio.redhat.com/neon
The reason for this is to simplify some of the release engineering / publishing / auditing scripts, so that we can key in on a common "mars" or "neon" path segment regardless of whether we're working with JBT or JBDS.
But then I thought, if there's a symlink from 9.0 -> mars on the ds.jb.com server, surely we should have the opposite symlink on the dl.jb.o server, mars -> 9.0.
This has been in place since May 21, 2015. I added the equivalent 10.0 / neon links on Sept 18, 2015.
While I understand your fear/confusion/rage, I still believe that having a logical mapping on the servers between the JBDS versioning and the JBT versioning is a good thing.
--
Would you be happy if instead of a /10.0 folder we simply used a /neon/ folder? I would +1 that plan, if you really don't like seeing "10.0" on the dl.jb.o server. At least that way the folder structure would be identical for both JBT and JBDS, as they'd both target a /neon/ folder.
> http://download.jboss.org/jbosstools/ contains wrong versions
> -------------------------------------------------------------
>
> Key: JBIDE-20993
> URL: https://issues.jboss.org/browse/JBIDE-20993
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1
>
>
> while discussing download.jboss.org with [~dgolovin] we found
> http://download.jboss.org/jbosstools/9.0/
> http://download.jboss.org/jbosstools/10.0/
> These look to be links to mars and neon.
> This is mixing in devstudio versioning with jbosstools which is just really confusing.
> No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme.
> I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20976) Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20976:
-------------------------------
Summary: Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)
> Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20976
> URL: https://issues.jboss.org/browse/JBIDE-20976
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
> Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, versionwatch-features.png, versionwatch-plugins.png
>
>
> Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS.
> Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer).
> Details in these logs:
> http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers...
> http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers...
> Affected IUs (now sorted alphabetically):
> {code}
> org.eclipse.core.runtime 3.11.1.v20150903-1804
> org.eclipse.egit 4.0.2.201509141540-r
> org.eclipse.egit.core 4.0.2.201509141540-r
> org.eclipse.egit.doc 4.0.2.201509141540-r
> org.eclipse.egit.ui 4.0.2.201509141540-r
> org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318
> org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318
> org.eclipse.jdt 3.11.1.v20150904-0015
> org.eclipse.jdt.doc.user 3.11.1.v20150819-1130
> org.eclipse.jetty.webapp 9.2.13.v20150730
> org.eclipse.jetty.xml 9.2.13.v20150730
> org.eclipse.jgit 4.0.2.201509141540-r
> org.eclipse.jgit.archive 4.0.2.201509141540-r
> org.eclipse.jst.common.frameworks 1.1.701.v201509021802
> org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356
> org.eclipse.jst.web_core.feature 3.7.1.v201509021802
> org.eclipse.jst.web_ui.feature 3.7.1.v201509021802
> org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443
> org.eclipse.pde 3.11.1.v20150904-0345
> org.eclipse.pde.doc.user 3.11.1.v20150903-1352
> org.eclipse.platform 4.5.1.v20150904-0015
> org.eclipse.platform.doc.user 4.5.1.v20150819-1130
> org.eclipse.rcp 4.5.1.v20150904-0015
> org.eclipse.sapphire 9.0.1.201509151939
> org.eclipse.sapphire.java 9.0.1.201509151939
> org.eclipse.sapphire.java.jdt 9.0.1.201509151939
> org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939
> org.eclipse.sapphire.modeling 9.0.1.201509151939
> org.eclipse.sapphire.modeling.xml 9.0.1.201509151939
> org.eclipse.sapphire.osgi 9.0.1.201509151939
> org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939
> org.eclipse.sapphire.platform 9.0.1.201509151939
> org.eclipse.sapphire.ui 9.0.1.201509151939
> org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939
> org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939
> org.eclipse.sapphire.workspace 9.0.1.201509151939
> org.eclipse.sapphire.workspace.ui 9.0.1.201509151939
> org.eclipse.swt 3.104.1.v20150825-0743
> org.eclipse.wst.common_core.feature 3.7.1.v201508262220
> org.eclipse.wst.common_ui.feature 3.7.1.v201508262220
> org.eclipse.wst.jsdt.feature 1.6.201.v201508262249
> org.eclipse.wst.server.core 1.7.0.v201508271522
> org.eclipse.wst.server.discovery 1.1.0.v201508271522
> org.eclipse.wst.server.ui 1.5.201.v201509022125
> org.eclipse.wst.server_core.feature 3.3.600.v201508271522
> org.eclipse.wst.server_ui.feature 3.3.600.v201509022125
> org.eclipse.wst.validation 1.2.700.v201508251749
> org.eclipse.wst.web_core.feature 3.7.1.v201508271605
> org.eclipse.wst.web_ui.feature 3.7.1.v201509022125
> org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926
> org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20951) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20951?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-20951 at 10/20/15 1:17 PM:
--------------------------------------------------------------
Root pom updated to the correct parent pom reference...
https://github.com/jbosstools/jbosstools-integration-tests/blob/jbosstool...
... but your plugins are still at version 4.3.0 [1], not 4.3.1. Did you ever do a 4.3.0 release, or are you STILL working toward your 4.3.0.Final bits, with the latest being 4.3.0.Beta1?
[1] http://download.jboss.org/jbosstools/9.0/snapshots/builds/jbosstools-inte...
was (Author: nickboldt):
Root pom updated to the correct parent pom reference...
https://github.com/jbosstools/jbosstools-integration-tests/blob/jbosstool...
... but your plugins are still at version 4.3.0, not 4.3.1. Did you ever do a 4.3.0 release, or are you STILL working toward your 4.3.0.Final bits?
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests]
> -------------------------------------------------------------------
>
> Key: JBIDE-20951
> URL: https://issues.jboss.org/browse/JBIDE-20951
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: qa
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Integration Tests]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months