[JBoss JIRA] (JBIDE-15774) Runtime edit window shows EAP 6.1 instead of EAP 6.1+
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15774?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-15774:
----------------------------------
Description:
In line with JBIDE-15614 and JBIDE-15751, this should be updated, too:
When I detect EAP 6.2 using runtime detection, it rightly shows the type as EAP 6.2, but then when I check the runtime later, it displays EAP 6.1 at the top:
!eap-6.2-runtime.png!
was:
In line with JBIDE-15614 and JBIDE-15751, this should be updated, too:
When I detect EAP 6.2 using runtime detection, it rightly shows the type as EAP 6.2, but then when I check the runtime later, it displays EAP 6.1 at the top:
> Runtime edit window shows EAP 6.1 instead of EAP 6.1+
> -----------------------------------------------------
>
> Key: JBIDE-15774
> URL: https://issues.jboss.org/browse/JBIDE-15774
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS 7.1.0.Beta1 B441
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.1.Beta1
>
> Attachments: eap-6.2-runtime.png
>
>
> In line with JBIDE-15614 and JBIDE-15751, this should be updated, too:
> When I detect EAP 6.2 using runtime detection, it rightly shows the type as EAP 6.2, but then when I check the runtime later, it displays EAP 6.1 at the top:
> !eap-6.2-runtime.png!
--
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, 8 months
[JBoss JIRA] (JBDS-2801) Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2801?page=com.atlassian.jira.plugin.... ]
Fred Bricon edited comment on JBDS-2801 at 10/24/13 4:42 AM:
-------------------------------------------------------------
Since we're targetting kepler, we should reference the gwt *e43* feature. No the only problem I can think of is if you upgraded from *e42* to *e43*, what will happen? [same concerns as Martin]
[~maxandersen] : we reference a gwt feature to be sure all GWT tooling is installed and can be actually used, when installing maven.gwt
was (Author: fbricon):
Since we're targetting kepler, we should reference the gwt *e43* feature. No the only problem I can think of is if you upgraded from *e42* to *e43*, what will happen?
[~maxandersen] : we reference a gwt feature to be sure all GWT tooling is installed and can be actually used, when installing maven.gwt
> 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: Martin Malina
> Fix For: 7.1.0.Beta1
>
>
> 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, 8 months
[JBoss JIRA] (JBDS-2801) Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2801?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-2801:
-----------------------------------
Since we're targetting kepler, we should reference the gwt *e43* feature. No the only problem I can think of is if you upgraded from *e42* to *e43*, what will happen?
[~maxandersen] : we reference a gwt feature to be sure all GWT tooling is installed and can be actually used, when installing maven.gwt
> 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: Martin Malina
> Fix For: 7.1.0.Beta1
>
>
> 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, 8 months
[JBoss JIRA] (JBIDE-15774) Runtime edit window shows EAP 6.1 instead of EAP 6.1+
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15774?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-15774:
----------------------------------
Fix Version/s: 4.1.1.Beta1
Description:
In line with JBIDE-15614 and JBIDE-15751, this should be updated, too:
When I detect EAP 6.2 using runtime detection, it rightly shows the type as EAP 6.2, but then when I check the runtime later, it displays EAP 6.1 at the top:
Assignee: Rob Stryker
Affects Version/s: 4.1.1.Beta1
Environment: JBDS 7.1.0.Beta1 B441
Component/s: server
> Runtime edit window shows EAP 6.1 instead of EAP 6.1+
> -----------------------------------------------------
>
> Key: JBIDE-15774
> URL: https://issues.jboss.org/browse/JBIDE-15774
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS 7.1.0.Beta1 B441
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.1.Beta1
>
>
> In line with JBIDE-15614 and JBIDE-15751, this should be updated, too:
> When I detect EAP 6.2 using runtime detection, it rightly shows the type as EAP 6.2, but then when I check the runtime later, it displays EAP 6.1 at the top:
--
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, 8 months
[JBoss JIRA] (JBIDE-15773) Forge Generate Entities wizard: Select connection profile name automatically
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-15773:
----------------------------------
Summary: Forge Generate Entities wizard: Select connection profile name automatically
Key: JBIDE-15773
URL: https://issues.jboss.org/browse/JBIDE-15773
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: forge
Reporter: Pavol Srna
Fix For: 4.1.1.CR1
Attachments: forge-connection.png
Imagine a situation when there is no connection profile defined. You click on new, fill in all details - click on finish (in the new profile connection dialog). Then I would expect to have Connection Profile Name pre-filled with the 'in previous step' created connection profile.
--
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, 8 months