[JBoss JIRA] (JBIDE-23528) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [livereload]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23528?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23528:
----------------------------------
Assignee: Xavier Coulon
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [livereload]
> -----------------------------------------------------------------------
>
> Key: JBIDE-23528
> URL: https://issues.jboss.org/browse/JBIDE-23528
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: livereload
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [livereload]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.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.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: features plugins pom.xml pom.xml.orig README.md site tests *{color:orange}4.4.2.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.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: features plugins pom.xml pom.xml.orig README.md site tests *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.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.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {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 livereload 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)
9 years, 4 months
[JBoss JIRA] (JBIDE-23531) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [visual-page-editor-core]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23531?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23531:
----------------------------------
Assignee: Ilya Buziuk
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [visual-page-editor-core]
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-23531
> URL: https://issues.jboss.org/browse/JBIDE-23531
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: visual-page-editor-core
> Reporter: Friendly Jira Robot
> Assignee: Ilya Buziuk
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [visual-page-editor-core]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.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.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: features plugins pom.xml pom.xml.orig README.md site tests *{color:orange}4.4.2.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.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: features plugins pom.xml pom.xml.orig README.md site tests *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.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.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {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 visual-page-editor-core 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)
9 years, 4 months
[JBoss JIRA] (JBIDE-23532) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [webservices]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23532?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23532:
----------------------------------
Assignee: Xavier Coulon
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [webservices]
> ------------------------------------------------------------------------
>
> Key: JBIDE-23532
> URL: https://issues.jboss.org/browse/JBIDE-23532
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: webservices
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [webservices]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.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.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: docs features plugins pom.xml pom.xml.orig README.md site tests *{color:orange}4.4.2.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.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: docs features plugins pom.xml pom.xml.orig README.md site tests *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.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.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {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 webservices 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)
9 years, 4 months
[JBoss JIRA] (JBDS-4201) CLI-only installation is available but does not provide necessary info
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ]
Misha Ali edited comment on JBDS-4201 at 11/25/16 12:09 AM:
------------------------------------------------------------
Thanks, [~nickboldt]. Are you able to confirm this is a supported installation type? Or perhaps [~rick_wagner] or [~mmalina] can confirm this. I don't want to add it to the docs if we don't want to support it.
Edit: Meant to tag Rick Wagner for GSS instead of Rastislav Wagner. Sorry, Rastislav!
was (Author: mhusnain):
Thanks, [~nickboldt]. Are you able to confirm this is a supported installation type? Or perhaps [~rawagner] or [~mmalina] can confirm this. I don't want to add it to the docs if we don't want to support it.
> CLI-only installation is available but does not provide necessary info
> ----------------------------------------------------------------------
>
> Key: JBDS-4201
> URL: https://issues.jboss.org/browse/JBDS-4201
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 10.2.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Fix For: 10.x
>
> Attachments: InstallConfigRecord.xml
>
>
> I had some feedback from another writer testing a procedure with devstudio. He was using a CLI-only VM and was confused because the installer worked but offered little information, as would be expected.
> Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did not ask where to install devstudio, nor did it provide the default target folder it used. The GUI version asks if the user wants to deploy devstudio after the installation, but the non-GUI version does nothing. The resulting user experience was confusion, not knowing where devstudio was installed or how to start it.
> My questions here are:
> - is the non-GUI way a valid installation path? If yes, we should document it, and if not, we should mention it, either in the docs or when installation happens.
> - If the non-GUI installation is a valid path, it should replicate the questions in the wizard, such as where to install devstudio and which jdk to use, etc. The difference between the two installation paths causes confusion.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4201) CLI-only installation is available but does not provide necessary info
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ]
Misha Ali commented on JBDS-4201:
---------------------------------
Thanks, [~nickboldt]. Are you able to confirm this is a supported installation type? Or perhaps [~rawagner] or [~mmalina] can confirm this. I don't want to add it to the docs if we don't want to support it.
> CLI-only installation is available but does not provide necessary info
> ----------------------------------------------------------------------
>
> Key: JBDS-4201
> URL: https://issues.jboss.org/browse/JBDS-4201
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 10.2.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Fix For: 10.x
>
> Attachments: InstallConfigRecord.xml
>
>
> I had some feedback from another writer testing a procedure with devstudio. He was using a CLI-only VM and was confused because the installer worked but offered little information, as would be expected.
> Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did not ask where to install devstudio, nor did it provide the default target folder it used. The GUI version asks if the user wants to deploy devstudio after the installation, but the non-GUI version does nothing. The resulting user experience was confusion, not knowing where devstudio was installed or how to start it.
> My questions here are:
> - is the non-GUI way a valid installation path? If yes, we should document it, and if not, we should mention it, either in the docs or when installation happens.
> - If the non-GUI installation is a valid path, it should replicate the questions in the wizard, such as where to install devstudio and which jdk to use, etc. The difference between the two installation paths causes confusion.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4201) CLI-only installation is available but does not provide necessary info
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4201:
-----------------------------
Fix Version/s: 10.x
(was: 10.3.0.GA)
> CLI-only installation is available but does not provide necessary info
> ----------------------------------------------------------------------
>
> Key: JBDS-4201
> URL: https://issues.jboss.org/browse/JBDS-4201
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 10.2.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Fix For: 10.x
>
> Attachments: InstallConfigRecord.xml
>
>
> I had some feedback from another writer testing a procedure with devstudio. He was using a CLI-only VM and was confused because the installer worked but offered little information, as would be expected.
> Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did not ask where to install devstudio, nor did it provide the default target folder it used. The GUI version asks if the user wants to deploy devstudio after the installation, but the non-GUI version does nothing. The resulting user experience was confusion, not knowing where devstudio was installed or how to start it.
> My questions here are:
> - is the non-GUI way a valid installation path? If yes, we should document it, and if not, we should mention it, either in the docs or when installation happens.
> - If the non-GUI installation is a valid path, it should replicate the questions in the wizard, such as where to install devstudio and which jdk to use, etc. The difference between the two installation paths causes confusion.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4201) CLI-only installation is available but does not provide necessary info
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4201 at 11/25/16 12:00 AM:
-------------------------------------------------------------
There is no way to specify the install folder via commandline unless you first generate an InstallConfigRecord.xml file, and use that file to define the path used.
Here's a sample one, which defines both the required *installpath* and *jrelocation* parameters. [^InstallConfigRecord.xml]
To generate this file, simply run the installer (with UI) and then look at the file placed into the installation folder.
To use an installConfigRecord.xml file, I believe the syntax is:
{code}java -jar /path/to/installer.jar /path/to/InstallConfigRecord.xml{code}
was (Author: nickboldt):
There is no way to specify the install folder via commandline unless you first generate an InstallConfigRecord.xml file, and use that file to define the path used.
Here's a sample one, which defines both installpath and jrelocation. [^InstallConfigRecord.xml]
To generate this file, simply run the installer (with UI) and then look at the file placed into the installation folder.
To use an installConfigRecord.xml file, I believe the syntax is:
{code}java -jar /path/to/installer.jar /path/to/InstallConfigRecord.xml{code}
> CLI-only installation is available but does not provide necessary info
> ----------------------------------------------------------------------
>
> Key: JBDS-4201
> URL: https://issues.jboss.org/browse/JBDS-4201
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 10.2.0.GA
> Reporter: Misha Ali
> Fix For: 10.3.0.GA
>
> Attachments: InstallConfigRecord.xml
>
>
> I had some feedback from another writer testing a procedure with devstudio. He was using a CLI-only VM and was confused because the installer worked but offered little information, as would be expected.
> Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did not ask where to install devstudio, nor did it provide the default target folder it used. The GUI version asks if the user wants to deploy devstudio after the installation, but the non-GUI version does nothing. The resulting user experience was confusion, not knowing where devstudio was installed or how to start it.
> My questions here are:
> - is the non-GUI way a valid installation path? If yes, we should document it, and if not, we should mention it, either in the docs or when installation happens.
> - If the non-GUI installation is a valid path, it should replicate the questions in the wizard, such as where to install devstudio and which jdk to use, etc. The difference between the two installation paths causes confusion.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4201) CLI-only installation is available but does not provide necessary info
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-4201:
--------------------------------
Assignee: Denis Golovin
> CLI-only installation is available but does not provide necessary info
> ----------------------------------------------------------------------
>
> Key: JBDS-4201
> URL: https://issues.jboss.org/browse/JBDS-4201
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 10.2.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Fix For: 10.3.0.GA
>
> Attachments: InstallConfigRecord.xml
>
>
> I had some feedback from another writer testing a procedure with devstudio. He was using a CLI-only VM and was confused because the installer worked but offered little information, as would be expected.
> Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did not ask where to install devstudio, nor did it provide the default target folder it used. The GUI version asks if the user wants to deploy devstudio after the installation, but the non-GUI version does nothing. The resulting user experience was confusion, not knowing where devstudio was installed or how to start it.
> My questions here are:
> - is the non-GUI way a valid installation path? If yes, we should document it, and if not, we should mention it, either in the docs or when installation happens.
> - If the non-GUI installation is a valid path, it should replicate the questions in the wizard, such as where to install devstudio and which jdk to use, etc. The difference between the two installation paths causes confusion.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4201) CLI-only installation is available but does not provide necessary info
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4201:
----------------------------------
There is no way to specify the install folder via commandline unless you first generate an InstallConfigRecord.xml file, and use that file to define the path used.
Here's a sample one, which defines both installpath and jrelocation. [^InstallConfigRecord.xml]
To generate this file, simply run the installer (with UI) and then look at the file placed into the installation folder.
To use an installConfigRecord.xml file, I believe the syntax is:
{code}java -jar /path/to/installer.jar /path/to/InstallConfigRecord.xml{code}
> CLI-only installation is available but does not provide necessary info
> ----------------------------------------------------------------------
>
> Key: JBDS-4201
> URL: https://issues.jboss.org/browse/JBDS-4201
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 10.2.0.GA
> Reporter: Misha Ali
> Fix For: 10.3.0.GA
>
> Attachments: InstallConfigRecord.xml
>
>
> I had some feedback from another writer testing a procedure with devstudio. He was using a CLI-only VM and was confused because the installer worked but offered little information, as would be expected.
> Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did not ask where to install devstudio, nor did it provide the default target folder it used. The GUI version asks if the user wants to deploy devstudio after the installation, but the non-GUI version does nothing. The resulting user experience was confusion, not knowing where devstudio was installed or how to start it.
> My questions here are:
> - is the non-GUI way a valid installation path? If yes, we should document it, and if not, we should mention it, either in the docs or when installation happens.
> - If the non-GUI installation is a valid path, it should replicate the questions in the wizard, such as where to install devstudio and which jdk to use, etc. The difference between the two installation paths causes confusion.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months