[JBoss JIRA] (JBIDE-13799) Source Lookup enhancements
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13799?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-13799:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Source Lookup enhancements
> --------------------------
>
> Key: JBIDE-13799
> URL: https://issues.jboss.org/browse/JBIDE-13799
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Fred Bricon
> Fix For: 4.6.x
>
>
> The PR includes the following enhancements:
> - AS 7.2/EAP 6.1 are now recognized correctly
> - the fix for the issue caused by changing the editor ID for ClassFileEdtor in 3.8/4.2
> - the fix for the ConcurrentModificationException exception
> - included libraries can be filtered - jsf 1.2 and hibernate 3 will be excluded by default for JBoss AS Container
> - JBoss Runtimes now can be included in the Java Search (this feature has been implemented in a similar way to adding PDE plugins to the Java Search)
> - JBoss Java Project Source Container
> See http://screencast.com/t/39LHqYx5m
> Screenshot shows debugging the WeldBootstrap class in JBoss AS 7.1 and JBoss AS 7.2.
> Note:
> You have to have some deployment on the servers in order the WeldBootstrap class to be created.
> You can add more JBoss servers to the Java Search, but it is the best to use only one at a time because of the performance reason.
> The "Automatically add the JBoss Maven source container to all JBoss AS launch configurations" and "Include the following JBoss Servers in the Java Search" checkboxes aren't related. The first checkbox adds the source container that enables finding a Java source file when debugging, the second enables finding a Java source file using the Java Search (using the "Open type" command, for instance).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-21652) We should make OS 3 application status more visible for users
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21652?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21652:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> We should make OS 3 application status more visible for users
> -------------------------------------------------------------
>
> Key: JBIDE-21652
> URL: https://issues.jboss.org/browse/JBIDE-21652
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Alexey Kazakov
> Fix For: 4.6.x
>
>
> Currently it can be confusing for users when an application is not available because it's building.
> We should think about our options, how we could improve visibility of the application status in both OS Explorer and Servers view (for OS server adapters).
> For example we could add a status line for an "application" node (or even for a project?) and show "Building..." or something if any of its services is building. We also could use a red font for such statuses. An gif icon would be ideal but I'm not sure it's technically possible.
> OS Server adapter is a separate story but we need to add status for it too. Maybe it's worth a separate issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25505) New application wizard: Configure > Deploy to OpenShift wont create a server adapter
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25505?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25505:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> New application wizard: Configure > Deploy to OpenShift wont create a server adapter
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-25505
> URL: https://issues.jboss.org/browse/JBIDE-25505
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.2.AM2
> Reporter: Andre Dietisheim
> Labels: application_wizard, configure_openshift, openshift_v3
> Fix For: 4.6.x
>
>
> steps:
> # ASSERT: have a project in your workspace. The project has to be git shared with an origin pointing to the internet. (to create it ex. create an app in OpenShift via template, import it to the workspace and then kill the OpenShift app)
> # EXEC: in the context menu to your workspace project pick Configure > Deploy to OpenShift and step through the wizard until the end
> Result:
> You're never asked if you want to create a server adapter. And there is no server adapter being created. While if you go File > New > Other > OpenShift Application and create an app, you get asked if you want to create a server adapter. And it gets created if you agree to.
> Expected result:
> A server adapter is created
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-13003) No support for inheritance in JAX-RS API scan
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13003?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-13003:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> No support for inheritance in JAX-RS API scan
> ---------------------------------------------
>
> Key: JBIDE-13003
> URL: https://issues.jboss.org/browse/JBIDE-13003
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: webservices
> Affects Versions: 4.0.0.Alpha1, 4.0.0.Alpha2
> Reporter: Ron Ratovsky
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.6.x
>
>
> Assume:
> class BaseRest {
> @POST
> public Response save(Object o) {
> ....
> }
> }
> @Path("/url")
> class RealRest extends BaseRest {}
> The JAX-RS tools won't add a "POST /url" entry to the JAX-RS calls overview.
> While not tested (due to another bug) - they may also apply to definitions of @PathParam's in the parent class.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22307) XML validation exclude group accidentally not working
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22307?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22307:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> XML validation exclude group accidentally not working
> -----------------------------------------------------
>
> Key: JBIDE-22307
> URL: https://issues.jboss.org/browse/JBIDE-22307
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing, upstream
> Environment: Eclipse Mars.2
> Reporter: Leonid Rozenblyum
> Fix For: 4.6.x
>
>
> The problem started to occur after recent JBoss Tools update:
> Windows -> Preferences -> Validation -> XML,
> Add a directory to exclude group.
> A directory contains a lot of xml files.
> Accidentally after SVN update or anything else the XML files inside the directory become validated and therefor a lot of XML errors are shown in Markers view.
> The problem is not stable to reproduce, however occurs rather often.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months