[JBoss JIRA] (JBDS-4362) Consider eliminating the devstudio EAP installer bundle?
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4362?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4362:
-------------------------------------
That works for me, because DevSuite is not using it anyway.
> Consider eliminating the devstudio EAP installer bundle?
> --------------------------------------------------------
>
> Key: JBDS-4362
> URL: https://issues.jboss.org/browse/JBDS-4362
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer, integration-platform
> Affects Versions: 10.4.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.0.0.AM1
>
>
> For devstudio 11, we might want to eliminate the devstudio EAP installer.
> If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
> This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server.
> Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely?
> That way only the devSUITE installer would include EAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24335) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [openshift]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24335?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-24335:
------------------------------------
bump up to parent pom version = 4.4.4.Final-SNAPSHOT
> For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [openshift]
> ----------------------------------------------------------------------
>
> Key: JBIDE-24335
> URL: https://issues.jboss.org/browse/JBIDE-24335
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [openshift]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
>
> [Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
>
> 1. Check out your existing *{color:orange}master{color}* branch:
>
> {code}
> git checkout master
> {code}
>
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.Final-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
>
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
>
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final-SNAPSHOT
>
> {code}
> mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
> {code}
>
> 5. Close (do not resolve) this JIRA when done.
>
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
>
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for openshift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24335) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [openshift]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24335?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-24335.
------------------------------
Resolution: Done
> For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [openshift]
> ----------------------------------------------------------------------
>
> Key: JBIDE-24335
> URL: https://issues.jboss.org/browse/JBIDE-24335
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [openshift]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
>
> [Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
>
> 1. Check out your existing *{color:orange}master{color}* branch:
>
> {code}
> git checkout master
> {code}
>
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.Final-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
>
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
>
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final-SNAPSHOT
>
> {code}
> mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
> {code}
>
> 5. Close (do not resolve) this JIRA when done.
>
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
>
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for openshift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4377:
-----------------------------
Attachment: devstudio104am3-installer-missing-unpatched-plugin.png
> installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4377
> URL: https://issues.jboss.org/browse/JBDS-4377
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: build, installer, target-platform
> Affects Versions: 10.4.0.AM3
> Environment: Windows: DevSuite Installer v1.4 AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.4.0.GA
>
> Attachments: devstudio104am3-installer-missing-unpatched-plugin.png
>
>
> Denis reports a problem using the installer jar in automated mode (using .xml script).
> Works fine when run `java -jar \*installer\*.jar` and `echo 1 | java -jar \*installer\*.jar -console` but fails when run against an xml install script.
> Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
> So we need to figure out how to include BOTH versions in the installer jar.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4377:
-----------------------------
Description:
Denis reports a problem using the installer jar in automated mode (using .xml script).
Works fine when run `java -jar \*installer\*.jar` and `echo 1 | java -jar \*installer\*.jar -console` but fails when run against an xml install script.
Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
!devstudio104am3-installer-missing-unpatched-plugin.png|thumbnail!
So we need to figure out how to include BOTH versions in the installer jar.
was:
Denis reports a problem using the installer jar in automated mode (using .xml script).
Works fine when run `java -jar \*installer\*.jar` and `echo 1 | java -jar \*installer\*.jar -console` but fails when run against an xml install script.
Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
So we need to figure out how to include BOTH versions in the installer jar.
> installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4377
> URL: https://issues.jboss.org/browse/JBDS-4377
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: build, installer, target-platform
> Affects Versions: 10.4.0.AM3
> Environment: Windows: DevSuite Installer v1.4 AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.4.0.GA
>
> Attachments: devstudio104am3-installer-missing-unpatched-plugin.png
>
>
> Denis reports a problem using the installer jar in automated mode (using .xml script).
> Works fine when run `java -jar \*installer\*.jar` and `echo 1 | java -jar \*installer\*.jar -console` but fails when run against an xml install script.
> Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
> !devstudio104am3-installer-missing-unpatched-plugin.png|thumbnail!
> So we need to figure out how to include BOTH versions in the installer jar.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4377:
-------------------------------------
{code}c:\p\rh\dpi>"C:\DevelopmentSuite\jdk8\bin\java" -Djava.awt.headless=true -jar "c:\DevelopmentSuite\developer-studio\studio\p2\director\plugins\org.eclipse.equinox.launcher_1.3.201.v20161025-1711.jar" -roaming -vm "C:\DevelopmentSuite\jdk8" -r "jar:file:///C:/Users/eskimo/AppData/Local/Temp/7zSF05.tmp/devstudio-10.4.0.AM3-v20170421-0111-B478-installer-standalone.jar!/devstudio" -d "c:\DevelopmentSuite\developer-studio\studio" -p devstudio -i com.jboss.devstudio.core.package,org.testng.eclipse.feature.group -profileProperties org.eclipse.update.install.features=true
Installer
Installing com.jboss.devstudio.core.package 10.4.0.AM3-v20170421-0111-B478.
Installing org.testng.eclipse.feature.group 6.11.0.201703011520.
Installation failed.
Cannot complete the install because one or more required items could not be found.
Software being installed: Red Hat JBoss Developer Studio (Branded Product) 10.4.0.AM3-v20170421-0111-B478 (com.jboss.devstudio.core.package 10.4.0.AM3-v20170421-0111-B478)
Missing requirement: WST Common Core 3.8.2.v201701191735 (org.eclipse.wst.common_core.feature.feature.group 3.8.2.v201701191735) requires 'org.eclipse.wst.common.modulecore [1.2.500.v201701032135]' but it could not be found
Cannot satisfy dependency:
From: Red Hat JBoss Developer Studio (Core Features) 10.4.0.v20170421-0111 (com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170421-0111)
To: com.jboss.devstudio.core.rpmdeps.feature.feature.group [10.4.0.v20170216-1757]
Cannot satisfy dependency:
From: Red Hat JBoss Developer Studio (Branded Product) 10.4.0.AM3-v20170421-0111-B478 (com.jboss.devstudio.core.package 10.4.0.AM3-v20170421-0111-B478)
To: com.jboss.devstudio.core.feature.feature.group [10.4.0.v20170421-0111]
Cannot satisfy dependency:
From: Red Hat JBoss Developer Studio (Feature Dependencies) 10.4.0.v20170216-1757 (com.jboss.devstudio.core.rpmdeps.feature.feature.group 10.4.0.v20170216-1757)
To: org.eclipse.wst.web_ui.feature.feature.group 0.0.0
Cannot satisfy dependency:
From: WST Web Core 3.8.2.v201702270442 (org.eclipse.wst.web_core.feature.feature.group 3.8.2.v201702270442)
To: org.eclipse.wst.common_core.feature.feature.group [3.8.2.v201701191735]
Cannot satisfy dependency:
From: Eclipse Web Developer Tools 3.8.2.v201702270442 (org.eclipse.wst.web_ui.feature.feature.group 3.8.2.v201702270442)
To: org.eclipse.wst.web_core.feature.feature.group [3.8.2.v201702270442]{code}
> installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4377
> URL: https://issues.jboss.org/browse/JBDS-4377
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: build, installer, target-platform
> Affects Versions: 10.4.0.AM3
> Environment: Windows: DevSuite Installer v1.4 AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.4.0.GA
>
>
> Denis reports a problem using the installer jar in automated mode (using .xml script).
> Works fine when run `java -jar \*installer\*.jar` and `echo 1 | java -jar \*installer\*.jar -console` but fails when run against an xml install script.
> Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
> So we need to figure out how to include BOTH versions in the installer jar.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4377:
-----------------------------
Description:
Denis reports a problem using the installer jar in automated mode (using .xml script).
Works fine when run `java -jar \*installer\*.jar` and `echo 1 | java -jar \*installer\*.jar -console` but fails when run against an xml install script.
Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
So we need to figure out how to include BOTH versions in the installer jar.
was:
Denis reports a problem using the installer jar in automated mode (using .xml script).
Works fine when run `java -jar *installer*.jar` and `echo 1 | java -jar *installer*.jar -console` but fails when run against an xml install script.
Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
So we need to figure out how to include BOTH versions in the installer jar.
> installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4377
> URL: https://issues.jboss.org/browse/JBDS-4377
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: build, installer, target-platform
> Affects Versions: 10.4.0.AM3
> Environment: Windows: DevSuite Installer v1.4 AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.4.0.GA
>
>
> Denis reports a problem using the installer jar in automated mode (using .xml script).
> Works fine when run `java -jar \*installer\*.jar` and `echo 1 | java -jar \*installer\*.jar -console` but fails when run against an xml install script.
> Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
> So we need to figure out how to include BOTH versions in the installer jar.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4377:
-----------------------------
Component/s: build
installer
target-platform
> installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4377
> URL: https://issues.jboss.org/browse/JBDS-4377
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: build, installer, target-platform
> Affects Versions: 10.4.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.4.0.GA
>
>
> Denis reports a problem using the installer jar in automated mode (using .xml script).
> Works fine when run `java -jar *installer*.jar` and `echo 1 | java -jar *installer*.jar -console` but fails when run against an xml install script.
> Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
> So we need to figure out how to include BOTH versions in the installer jar.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4377:
-----------------------------
Environment: Windows: DevSuite Installer v1.4 AM3
> installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4377
> URL: https://issues.jboss.org/browse/JBDS-4377
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: build, installer, target-platform
> Affects Versions: 10.4.0.AM3
> Environment: Windows: DevSuite Installer v1.4 AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.4.0.GA
>
>
> Denis reports a problem using the installer jar in automated mode (using .xml script).
> Works fine when run `java -jar *installer*.jar` and `echo 1 | java -jar *installer*.jar -console` but fails when run against an xml install script.
> Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
> So we need to figure out how to include BOTH versions in the installer jar.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4377:
-----------------------------
Fix Version/s: 10.4.0.GA
> installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4377
> URL: https://issues.jboss.org/browse/JBDS-4377
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Affects Versions: 10.4.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.4.0.GA
>
>
> Denis reports a problem using the installer jar in automated mode (using .xml script).
> Works fine when run `java -jar *installer*.jar` and `echo 1 | java -jar *installer*.jar -console` but fails when run against an xml install script.
> Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
> So we need to figure out how to include BOTH versions in the installer jar.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months