[JBoss JIRA] (JBIDE-18516) JAX-RS Validator should report problem when @DefaultValue is used alone
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-18516:
-------------------------------------
Summary: JAX-RS Validator should report problem when @DefaultValue is used alone
Key: JBIDE-18516
URL: https://issues.jboss.org/browse/JBIDE-18516
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: webservices
Affects Versions: 4.2.0.Final
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.3.0.Alpha1
If a method parameter is annotated with {{@DefaultValue}} but has _no_ {{@QueryParam}} (or similar) annotation, then the application will most certainly fail with an error message such as:
{code}
failed to execute: javax.ws.rs.NotSupportedException: Could not find message body reader for type: int of content type: */*
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18515) Cordova Configuration Editor has broken layout
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18515?page=com.atlassian.jira.plugi... ]
Vlado Pakan updated JBIDE-18515:
--------------------------------
Description:
1. Create Hybrid Mobile Project
2. Open Cordova Configuration Editor
3. Open dialog to add plugin from Git
!brokenlayoutgit.png!
4. Open dialog to add plugin from Directory and select some directory
ERROR: Selected directory is not displayed in dialog
!brokenlayoutdirectory.png!
Once dialog is resized all looks correct in both cases.
was:
1. Create Hybrid Mobile Project
2. Open Cordova Configuration Editor
3. Open dialog to add plugin from Git
!brokenlayoutgit.png!
4. Open dialog to add plugin from Directory and select some directory
ERROR: Selected directory is not displayed in dialog
!brokenlayoutdirectory.png!
Once dialog is resized all looks correct.
> Cordova Configuration Editor has broken layout
> ----------------------------------------------
>
> Key: JBIDE-18515
> URL: https://issues.jboss.org/browse/JBIDE-18515
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.CR1
> Environment: JBT 4.2.0.CR2-v20141005-0541-B267 Fedora 19 KDE 64 bit Java Oracle 8
> Reporter: Vlado Pakan
> Priority: Minor
> Attachments: brokenlayoutdirectory.png, brokenlayoutgit.png
>
>
> 1. Create Hybrid Mobile Project
> 2. Open Cordova Configuration Editor
> 3. Open dialog to add plugin from Git
> !brokenlayoutgit.png!
> 4. Open dialog to add plugin from Directory and select some directory
> ERROR: Selected directory is not displayed in dialog
> !brokenlayoutdirectory.png!
> Once dialog is resized all looks correct in both cases.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18515) Cordova Configuration Editor has broken layout
by Vlado Pakan (JIRA)
Vlado Pakan created JBIDE-18515:
-----------------------------------
Summary: Cordova Configuration Editor has broken layout
Key: JBIDE-18515
URL: https://issues.jboss.org/browse/JBIDE-18515
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Affects Versions: 4.2.0.CR1
Environment: JBT 4.2.0.CR2-v20141005-0541-B267 Fedora 19 KDE 64 bit Java Oracle 8
Reporter: Vlado Pakan
Priority: Minor
Attachments: brokenlayoutdirectory.png, brokenlayoutgit.png
1. Create Hybrid Mobile Project
2. Open Cordova Configuration Editor
3. Open dialog to add plugin from Git
!brokenlayoutgit.png!
4. Open dialog to add plugin from Directory and select some directory
ERROR: Selected directory is not displayed in dialog
!brokenlayoutdirectory.png!
Once dialog is resized all looks correct.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18515) Cordova Configuration Editor has broken layout
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18515?page=com.atlassian.jira.plugi... ]
Vlado Pakan updated JBIDE-18515:
--------------------------------
Attachment: brokenlayoutdirectory.png
brokenlayoutgit.png
> Cordova Configuration Editor has broken layout
> ----------------------------------------------
>
> Key: JBIDE-18515
> URL: https://issues.jboss.org/browse/JBIDE-18515
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.CR1
> Environment: JBT 4.2.0.CR2-v20141005-0541-B267 Fedora 19 KDE 64 bit Java Oracle 8
> Reporter: Vlado Pakan
> Priority: Minor
> Attachments: brokenlayoutdirectory.png, brokenlayoutgit.png
>
>
> 1. Create Hybrid Mobile Project
> 2. Open Cordova Configuration Editor
> 3. Open dialog to add plugin from Git
> !brokenlayoutgit.png!
> 4. Open dialog to add plugin from Directory and select some directory
> ERROR: Selected directory is not displayed in dialog
> !brokenlayoutdirectory.png!
> Once dialog is resized all looks correct.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18483) For JBIDE 4.2.0.CR2: Prepare for CR2 release [LiveReload]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18483?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18483:
------------------------------------
Valid point. I suppose I should have re-opened the CR1 version of this jira instead, but I was AFK when that happened. :)
> For JBIDE 4.2.0.CR2: Prepare for CR2 release [LiveReload]
> ---------------------------------------------------------
>
> Key: JBIDE-18483
> URL: https://issues.jboss.org/browse/JBIDE-18483
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: livereload
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR2
>
>
> For JBIDE 4.2.0.CR2 [LiveReload]: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA.
> [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR2-SNAPSHOT
> mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT
> {code}
> 5. If you did not already do so, *{color:orange}IN YOUR MASTER BRANCH{color}*:
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months