[JBoss JIRA] (JBDS-2842) Add UI for central connectors update
by Martin Malina (JIRA)
Martin Malina created JBDS-2842:
-----------------------------------
Summary: 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
[JBoss JIRA] (JBIDE-16175) Support browser reload after changes in JSP on both AS7+ and EAP6+
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16175?page=com.atlassian.jira.plugi... ]
Burr Sutter commented on JBIDE-16175:
-------------------------------------
Now that I think about this item...JSP change/livereload would be a relatively lower priority item - as our focus is on HTML5-focused (rich client/thin server) app development (.html not .jsp).
> Support browser reload after changes in JSP on both AS7+ and EAP6+
> ------------------------------------------------------------------
>
> Key: JBIDE-16175
> URL: https://issues.jboss.org/browse/JBIDE-16175
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Affects Versions: 4.1.1.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.x
>
>
> See if there anything that can be done on the tooling side to trigger a browser refresh after a JSP was modified.
> [~nsaad] reported that he needed to modify his EAP configuration by adding a <configuration> tag for JSP development re-deployment to subsystem "default-host” to get it working.
--
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 5.0.0 stops at Installation Step 7 of 9 Overall Installation Progress 1/4
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2260?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2260:
----------------------------------
[~psrna] As the last person to test this, can you confirm if the problem's still present in JBDS 7.1.0.CR1?
[~maxandersen] [~dgolovin] Should this be set as a blocker for 7.1.0 and fixed ASAP, as it's been pending so long? (Or should we just document the workaround, which is "don't use long paths for your TMP/TEMP variable, and don't use accented characters"? cc: [~mmurray])
> Installation of JBoss Developer Studio 5.0.0 stops at Installation Step 7 of 9 Overall Installation Progress 1/4
> ----------------------------------------------------------------------------------------------------------------
>
> 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-2260) Installation of JBoss Developer Studio hangs if accented characters in TMP folder (Windows only)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2260?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2260:
-----------------------------
Summary: Installation of JBoss Developer Studio hangs if accented characters in TMP folder (Windows only) (was: Installation of JBoss Developer Studio 5.0.0 stops at Installation Step 7 of 9 Overall Installation Progress 1/4)
> 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] (JBIDE-16161) Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-16161:
---------------------------------------
I have tried the base component. It seems to work. The org.jboss.tools.stacks.core.test tests fail randomly, but that is another issue, I suppose.
As to the webservices component, the org.jboss.tools.ws.ui.test tests fail. They pass when using the rcp feature.
> Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna
> -------------------------------------------------------------------------
>
> Key: JBIDE-16161
> URL: https://issues.jboss.org/browse/JBIDE-16161
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Mickael Istria
>
> Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin.
> The easiest way is to add the org.eclipse.e4.rcp feature to the main build.
--
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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2801?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2801 at 12/3/13 11:23 AM:
------------------------------------------------------------
AFAIR Central just checks if the contents of the connector (the list of features in the connector) are installed and if the version on the Central site are the same as those installed.
It's fairly easy to test this...
a) install JBDS 7.1.0.CR1
b) install GWT from http://download.jboss.org/jbosstools/updates/requirements/gwt/3.2.3.v2013... into JBDS. Restart when prompted.
c) Central > Software tab > see if the GWT connector is shown to be installed or not (it should be shown as not installed, because a newer version & different IUs are available).
d) or, install Spring IDE 3.2 from http://download.jboss.org/jbosstools/updates/requirements/springide/3.2.0... into JBDS. Restart when prompted.
e) Central > Software tab > see if the SpringIDE connector is shown to be installed or not (it should be shown as not installed, because a newer version is available for the same IUs).
And yes, we should have a new requirement JIRA to track this new UI candy.
[~mmalina] please open a new JIRA for JBDS 8 requesting a new UI to show that "this connector can be updated".
was (Author: nickboldt):
AFAIR Central just checks if the contents of the connector (the list of features in the connector) are installed and if the version on the Central site are the same as those installed.
It's fairly easy to test this...
a) install JBDS 7.1.0.CR1
b) install GWT from http://download.jboss.org/jbosstools/updates/requirements/gwt/3.2.3.v2013... into JBDS. Restart when prompted.
c) Central > Software tab > see if the GWT connector is shown to be installed or not (it should be shown as not installed, because a newer version & different IUs are available).
d) or, install Spring IDE 3.2 from http://download.jboss.org/jbosstools/updates/requirements/springide/3.2.0... into JBDS. Restart when prompted.
e) Central > Software tab > see if the SpringIDE connector is shown to be installed or not (it should be shown as not installed, because a newer version is available for the same IUs).
> 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-2801) Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2801?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2801:
-------------------------------------------
I dont think it checks the exact versions.
and yes, central should provide a Update button/workflow too. [~mmalina] can you open new jira for that ?
> 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-2801) Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2801?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2801:
----------------------------------
AFAIR Central just checks if the contents of the connector (the list of features in the connector) are installed and if the version on the Central site are the same as those installed.
It's fairly easy to test this...
a) install JBDS 7.1.0.CR1
b) install GWT from http://download.jboss.org/jbosstools/updates/requirements/gwt/3.2.3.v2013... into JBDS. Restart when prompted.
c) Central > Software tab > see if the GWT connector is shown to be installed or not (it should be shown as not installed, because a newer version & different IUs are available).
d) or, install Spring IDE 3.2 from http://download.jboss.org/jbosstools/updates/requirements/springide/3.2.0... into JBDS. Restart when prompted.
e) Central > Software tab > see if the SpringIDE connector is shown to be installed or not (it should be shown as not installed, because a newer version is available for the same IUs).
> 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] (JBIDE-16170) Latest HTML5 archetype doesn't show unavailable maven repo in wizard
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16170?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16170:
----------------------------------------
Labels: (was: respin-b)
Fix Version/s: 4.1.1.Final
(was: 4.1.1.CR1)
set to be part of Final build
> Latest HTML5 archetype doesn't show unavailable maven repo in wizard
> --------------------------------------------------------------------
>
> Key: JBIDE-16170
> URL: https://issues.jboss.org/browse/JBIDE-16170
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.1.1.CR1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.1.1.Final
>
>
> The latest HTML 5 archetype now depends on WFK dependencies by default (there used to be a community/enterprise distinction before, not anymore)
> Problem is, the missing enterprise dependencies warning (JBIDE-14909) only shows up if an enterprise runtime is selected. In this case, it should also be displayed for all runtimes.
> So all JBoss Central users not selecting an enterprise runtime will create a broken project if the maven redhat repo is missing from their settings.xml. Which is bad :/
--
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