[JBoss JIRA] (TOOLSDOC-431) Section referring to JBDS install scripts should be removed from the docs
by Len DiMaggio (JIRA)
Len DiMaggio created TOOLSDOC-431:
-------------------------------------
Summary: Section referring to JBDS install scripts should be removed from the docs
Key: TOOLSDOC-431
URL: https://issues.jboss.org/browse/TOOLSDOC-431
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Bug
Components: Release Notes
Environment: Build Name: 22485, Release Notes 7.1.0-7.1-7.1.0
Build Date: 03-12-2013 17:56:03
Topic ID: 24020-563181 [Latest]
Reporter: Len DiMaggio
Assignee: Michelle Murray
Priority: Blocker
Title: New Features
Describe the issue:
This paragraph should be removed - as the feature was removed for 7.1.0.GA:
Scripts are available for use when installing JBoss Developer Studio using the universal installer. These scripted installation methods are useful when you need to perform repeat installations or installation in bulk, removing the need to work through the universal installer GUI for each installed instance.
Suggestions for improvement:
Additional information:
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2260) Installation of JBoss Developer Studio hangs if accented characters in TMP folder (Windows only)
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2260?page=com.atlassian.jira.plugin.... ]
Mickael Istria updated JBDS-2260:
---------------------------------
Priority: Major (was: Blocker)
> Installation of JBoss Developer Studio hangs if accented characters in TMP folder (Windows only)
> ------------------------------------------------------------------------------------------------
>
> Key: JBDS-2260
> URL: https://issues.jboss.org/browse/JBDS-2260
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 5.0.0.GA
> Reporter: Isaac Rooskov
> Assignee: Denis Golovin
> Labels: respin-b
> Fix For: 8.0.0.Alpha1
>
> Attachments: JavaVersionReader.java.patch
>
>
> *From customer in Bugzilla*
> Bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=850793
> Description of issue from customer:
> Description of problem:
> Installation of JBoss Developer Studion 5.0.0 stops at Installation Step 7 of 9 Overall Installation Progress 1/4
> Version-Release number of selected component (if applicable):
> JBOSS Developer Studio 5.0.0.GA
> How reproducible:
> Start installation using
> java - jar jbdevstudio-product-universal-5.0.0.v20120615-1714-H213-GA.jar
> Actual results:
> Installation is not passing at step 7 of 9, progress 1 of 4.
> Expected results:
> Additional info:
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2260) Installation of JBoss Developer Studio hangs if accented characters in TMP folder (Windows only)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2260?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-2260:
-------------------------------------
IMO, it is not a blocker (as I said above). Problem is in communication trough i/o streams under windows. It can be fixed by implementing installer as an OSGi bundle with Swing Based UI. It means no more communication with external process and no encoding problems.
> Installation of JBoss Developer Studio hangs if accented characters in TMP folder (Windows only)
> ------------------------------------------------------------------------------------------------
>
> Key: JBDS-2260
> URL: https://issues.jboss.org/browse/JBDS-2260
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 5.0.0.GA
> Reporter: Isaac Rooskov
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: respin-b
> Fix For: 8.0.0.Alpha1
>
> Attachments: JavaVersionReader.java.patch
>
>
> *From customer in Bugzilla*
> Bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=850793
> Description of issue from customer:
> Description of problem:
> Installation of JBoss Developer Studion 5.0.0 stops at Installation Step 7 of 9 Overall Installation Progress 1/4
> Version-Release number of selected component (if applicable):
> JBOSS Developer Studio 5.0.0.GA
> How reproducible:
> Start installation using
> java - jar jbdevstudio-product-universal-5.0.0.v20120615-1714-H213-GA.jar
> Actual results:
> Installation is not passing at step 7 of 9, progress 1 of 4.
> Expected results:
> Additional info:
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2801) Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2801?page=com.atlassian.jira.plugin.... ]
Martin Malina closed JBDS-2801.
-------------------------------
I believe this JIRA is ready to be closed now. Closing.
> Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
> --------------------------------------------------
>
> Key: JBDS-2801
> URL: https://issues.jboss.org/browse/JBDS-2801
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: new_and_noteworthy
> Fix For: 7.1.0.CR1
>
> Attachments: install-new-gpe-1.png, install-new-gpe-2.png, install-new-gpe-3.png, install-new-gpe-4.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE_installed_manual_install_of_GPEe43_throws_remediation.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE_installed_view.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1_remdiation_option_1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1_remdiation_option_2.png, JBDS2801_install_JBDS_Beta1_b441_installed.png, JBDS2801_install_JBT_CR1.png, JBDS2801_install_JBT_CR1_installed.png
>
>
> New 3.4.2 mirrors:
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> Note that at least one IU had been renamed:
> OLD:
> * com.google.gdt.eclipse.suite.e42.feature_3.4.2.v201310081840-rel-r42.jar
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081840-rel-r42.jar
> NEW:
> * com.google.gdt.eclipse.suite.e43.feature_3.4.2.v201310081834-rel-r43.jar (now e43)
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081834-rel-r43.jar (still e42)
> If we decide to move to e43, we will have to rebuild jbosstools-central due to this requirement:
> {code:title=https://github.com/jbosstools/jbosstools-central/blob/jbosstools-4.1.x/maven/features/org.jboss.tools.maven.gwt.feature/feature.xml#L24}
> <import feature="com.google.gdt.eclipse.suite.e42.feature" version="3.0.1" match="greaterOrEqual"/>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2842) Add UI for central connectors update
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2842?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2842:
-----------------------------
Description:
Provide UI to inform users that there is an updated connector in JBoss Central.
Currently, when a user has a connector installed (e.g. GPE) and this connector gets updated, the only indication of that is that the connector is visible in Central even though it has been installed (and therefore would not normally show up).
There should be some element telling users that a given installed connector can be updated, rather than it appearing as new.
was:
Provide UI to inform users that there is an updated connector in JBoss Central.
Currently, when a user has a connector installed (e.g. GPE) and this connector gets updated, the only indication of that is that the connector is visible in Central even though it has been installed (and therefore would not normally show up).
There should be some element telling users that a given installed connector can be updated.
> Add UI for central connectors update
> ------------------------------------
>
> Key: JBDS-2842
> URL: https://issues.jboss.org/browse/JBDS-2842
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.GA
> Reporter: Martin Malina
>
> Provide UI to inform users that there is an updated connector in JBoss Central.
> Currently, when a user has a connector installed (e.g. GPE) and this connector gets updated, the only indication of that is that the connector is visible in Central even though it has been installed (and therefore would not normally show up).
> There should be some element telling users that a given installed connector can be updated, rather than it appearing as new.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2801) Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2801?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-2801:
-------------------------------------
New feature request has been created to add UI for "this connector can be updated": JBDS-2842
> Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
> --------------------------------------------------
>
> Key: JBDS-2801
> URL: https://issues.jboss.org/browse/JBDS-2801
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: new_and_noteworthy
> Fix For: 7.1.0.CR1
>
> Attachments: install-new-gpe-1.png, install-new-gpe-2.png, install-new-gpe-3.png, install-new-gpe-4.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE_installed_manual_install_of_GPEe43_throws_remediation.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE_installed_view.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1_remdiation_option_1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1_remdiation_option_2.png, JBDS2801_install_JBDS_Beta1_b441_installed.png, JBDS2801_install_JBT_CR1.png, JBDS2801_install_JBT_CR1_installed.png
>
>
> New 3.4.2 mirrors:
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> Note that at least one IU had been renamed:
> OLD:
> * com.google.gdt.eclipse.suite.e42.feature_3.4.2.v201310081840-rel-r42.jar
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081840-rel-r42.jar
> NEW:
> * com.google.gdt.eclipse.suite.e43.feature_3.4.2.v201310081834-rel-r43.jar (now e43)
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081834-rel-r43.jar (still e42)
> If we decide to move to e43, we will have to rebuild jbosstools-central due to this requirement:
> {code:title=https://github.com/jbosstools/jbosstools-central/blob/jbosstools-4.1.x/maven/features/org.jboss.tools.maven.gwt.feature/feature.xml#L24}
> <import feature="com.google.gdt.eclipse.suite.e42.feature" version="3.0.1" match="greaterOrEqual"/>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2842) Add UI for central connectors update
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2842?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2842:
-----------------------------
Assignee: Snjezana Peco
> Add UI for central connectors update
> ------------------------------------
>
> Key: JBDS-2842
> URL: https://issues.jboss.org/browse/JBDS-2842
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.GA
> Reporter: Martin Malina
> Assignee: Snjezana Peco
>
> Provide UI to inform users that there is an updated connector in JBoss Central.
> Currently, when a user has a connector installed (e.g. GPE) and this connector gets updated, the only indication of that is that the connector is visible in Central even though it has been installed (and therefore would not normally show up).
> There should be some element telling users that a given installed connector can be updated, rather than it appearing as new.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2842) Add UI for central connectors update
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2842?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2842:
-----------------------------
Fix Version/s: 8.0.0.Alpha1
> Add UI for central connectors update
> ------------------------------------
>
> Key: JBDS-2842
> URL: https://issues.jboss.org/browse/JBDS-2842
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.GA
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 8.0.0.Alpha1
>
>
> Provide UI to inform users that there is an updated connector in JBoss Central.
> Currently, when a user has a connector installed (e.g. GPE) and this connector gets updated, the only indication of that is that the connector is visible in Central even though it has been installed (and therefore would not normally show up).
> There should be some element telling users that a given installed connector can be updated, rather than it appearing as new.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2842) Add UI for central connectors update
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2842?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2842:
-----------------------------
CDW pm_ack: ?
CDW release: ?
> Add UI for central connectors update
> ------------------------------------
>
> Key: JBDS-2842
> URL: https://issues.jboss.org/browse/JBDS-2842
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.GA
> Reporter: Martin Malina
>
> Provide UI to inform users that there is an updated connector in JBoss Central.
> Currently, when a user has a connector installed (e.g. GPE) and this connector gets updated, the only indication of that is that the connector is visible in Central even though it has been installed (and therefore would not normally show up).
> There should be some element telling users that a given installed connector can be updated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months