[JBoss JIRA] (JBIDE-15269) Enterprise servers should be listed under 'Red Hat JBoss Middleware'
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15269?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-15269:
--------------------------------
Fix Version/s: 4.2.0.Alpha1
> Enterprise servers should be listed under 'Red Hat JBoss Middleware'
> --------------------------------------------------------------------
>
> Key: JBIDE-15269
> URL: https://issues.jboss.org/browse/JBIDE-15269
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Final
> Reporter: Michelle Murray
> Assignee: Rob Stryker
> Fix For: 4.2.0.Alpha1
>
> Attachments: Server_RedHatJBossEnterpriseMiddleware.png
>
>
> In the IDE, when adding new servers, EAP is listed under 'JBoss Enterprise Middleware'. This should be updated to 'Red Hat JBoss Middleware'.
> This is to reflect the rebranding:
> * 'Red Hat' is being added in front of JBoss.
> * 'Enterprise' is being dropped from everywhere, except in the title of EAP.
> For example, on the customer service portal (access.redhat.com), EAP is listed under 'Red Hat JBoss Middleware' - screen capture attached.
--
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, 5 months
[JBoss JIRA] (JBIDE-15357) Unexpected state of deployed project when project is deleted
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15357?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-15357:
-------------------------------------
An additional publish click wipes out the deployment.
The question is, why is this happening. My tests have revealed that it is calling an API I don't recall seeing "shouldIgnorePublishRequest()" which basically says, if the module has a project, and the project is not accessible, do not publish this.
This wtp code seems to be intended to ensure that if you close your project, it won't be removed from the remote server entirely, and will instead be ignored. However, the instance of the module being passed in after a delete operation still has a project, which is not accessible. It isn't closed, though, but does not exist.
So, it seems we'll need to override this method and say, if the module has a project, AND the project exists, AND it is not accessible (therefore, closed), it can be published (aka removed).
> Unexpected state of deployed project when project is deleted
> ------------------------------------------------------------
>
> Key: JBIDE-15357
> URL: https://issues.jboss.org/browse/JBIDE-15357
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Final
> Environment: JBDS 7.0.0.GA, L64
> Reporter: Jiri Peterka
> Assignee: Rob Stryker
> Fix For: 4.1.1.Final
>
>
> When project is deployed in IDE and then removed expected behavior would expect project would be undeployed. When I've tried that everything seemed as undeployed (I mean Server view) but project is still deployed. This is not user expected behavior IMO.
--
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, 5 months
[JBoss JIRA] (JBIDE-15162) User must install and reference an installed local EAP instance to create a remote server definition
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15162?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-15162:
-------------------------------------
> rob - why do you say WTP does not work with runtime less adapters ?
Deploy-only server, Live Reload and openshift all include "dummy runtime" types. A server type who has the "runtime-type" field in their extension point blank, missing, or invalid, will run into several problems.
> User must install and reference an installed local EAP instance to create a remote server definition
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15162
> URL: https://issues.jboss.org/browse/JBIDE-15162
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Attachments: Van_1.png, Van_2.png, Van_3.png
>
>
> See the attached screenshots - it seems counter-intuitive for a user to have to reference an installed local EAP instance to too create a remote server definition
> - open the "Servers" tab (where servers are stopped/started)
> - click in the area
> - now right mouse click and select "New->Server"
> - select JBoss Middleware EAP 6.1, click next
> - this next panel requires you to enter a directory to a local EAP install
--
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, 5 months
[JBoss JIRA] (JBIDE-15139) Deployment assembly fileset ignores classes on "subpackages"
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15139?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-15139:
-----------------------------------
Assignee: Rob Stryker
> Deployment assembly fileset ignores classes on "subpackages"
> ------------------------------------------------------------
>
> Key: JBIDE-15139
> URL: https://issues.jboss.org/browse/JBIDE-15139
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.0.0.Final, 4.1.0.Beta2
> Environment: Linux 3.8.2-pf #15 SMP Sun Apr 7 18:07:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
> java version "1.7.0_21"
> OpenJDK Runtime Environment (IcedTea 2.3.9) (7u21-2.3.9-1ubuntu1ppa1)
> OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
> Eclipse Juno SR2/ Kepler
> Reporter: Renato Garcia
> Assignee: Rob Stryker
> Fix For: 4.1.1.Final
>
> Attachments: sample-project.zip
>
>
> The fileset deployment assembly is ignoring classes that are inside packages with empty directories.
> For instance:
> a.Foo -> OK
> a.b.c.Bar -> NOT WORKING!
> If you add a file to a.b directory it will deploy Bar class.
> Attached the sample project that shows the error.
> It works on Helios but not on Juno and Kepler and their respective JBoss tools versions.
--
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, 5 months
[JBoss JIRA] (JBIDE-15798) Missing scroolbar in Cordova Feature Dialog
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15798?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-15798:
-------------------------------------
List of connectors should be scrollable with scrollbar I don't know what widget it is.
> Missing scroolbar in Cordova Feature Dialog
> -------------------------------------------
>
> Key: JBIDE-15798
> URL: https://issues.jboss.org/browse/JBIDE-15798
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: JBT 4.1.1 Beta1-v20131020-0207-B454
> Reporter: Vlado Pakan
> Priority: Minor
> Fix For: 4.1.1.CR1
>
>
> 1. Create new Hybrid Mobile project
> 2. Open project config.xml file in Cordova Configuration Editor
> 3. Go to Platform Properties tab. and click on Add.... button to add features
> ERROR: Opened dialog has no scroll bar
--
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, 5 months