[JBoss JIRA] (JBIDE-14769) Solutions not available reported by Marketplace
by Jiri Peterka (JIRA)
Jiri Peterka created JBIDE-14769:
------------------------------------
Summary: Solutions not available reported by Marketplace
Key: JBIDE-14769
URL: https://issues.jboss.org/browse/JBIDE-14769
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: marketplace
Affects Versions: 4.1.0.Beta1
Environment: JBT 4.1.Beta2, L64
Reporter: Jiri Peterka
Assignee: Nick Boldt
Fix For: 4.1.0.Beta2
Attachments: solutions-not-available.png
Not sure what it means but while installing JBT from Marketplace, there is this message. Installation seems ok. Can we avoid this meessage?
--
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, 10 months
[JBoss JIRA] (TOOLSDOC-337) Review: Devs to review Forge Tools chapter for JBDS 7.0.
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-337?page=com.atlassian.jira.plug... ]
Koen Aers commented on TOOLSDOC-337:
------------------------------------
[~mmurray]Sorry for the confusion. JBIDE-11217 was created because the 'set VERBOSE true' didn't work at all in Eclipse. This was fixed but your suggestion of logging the exceptions in the Error Log was not included as it asked for some more work. So JBIDE-11217 was resolved without the suggestion. JBIDE-14615 can be used to specifically track this.
> Review: Devs to review Forge Tools chapter for JBDS 7.0.
> --------------------------------------------------------
>
> Key: TOOLSDOC-337
> URL: https://issues.jboss.org/browse/TOOLSDOC-337
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - Forge Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.0
>
> Attachments: UserGuide_Forge.pdf
>
>
> Please review the content of the Forge Tools chapter from a technical viewpoint:
> 1) Are features correctly documented?
> 2) Are there any features that are missing?
> Screenshots are currently missing and will be added closer to GA.
> For ease of tracking by docs, please give feedback as comments in this JIRA.
> The chapter is available here as a pdf. The pdf has some layout issues so please disregard these and only comment on the technical content.
> Alternatively, the complete user guide to date is also available form:
> * http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Develo...
> * https://github.com/jbosstools/jbosstools-documentation/tree/master/docs/J... (build with: mvn compile)
--
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, 10 months
[JBoss JIRA] (TOOLSDOC-337) Review: Devs to review Forge Tools chapter for JBDS 7.0.
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-337?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-337:
------------------------------------------
[~koen.aers], just need a bit of clarification.
https://issues.jboss.org/browse/JBIDE-11217 release notes text states that 'A new feature has been added that allows for a user to run the Forge Verbose command from within the Forge console, and any exceptions are recorded in the Eclipse error log.' From your comment above, I guess that bit about recording exceptions in the error log is wrong. Or is it the case that exceptions are recorded in the error log but not shown in the error log tab even it the tab is opened manually?
> Review: Devs to review Forge Tools chapter for JBDS 7.0.
> --------------------------------------------------------
>
> Key: TOOLSDOC-337
> URL: https://issues.jboss.org/browse/TOOLSDOC-337
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - Forge Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.0
>
> Attachments: UserGuide_Forge.pdf
>
>
> Please review the content of the Forge Tools chapter from a technical viewpoint:
> 1) Are features correctly documented?
> 2) Are there any features that are missing?
> Screenshots are currently missing and will be added closer to GA.
> For ease of tracking by docs, please give feedback as comments in this JIRA.
> The chapter is available here as a pdf. The pdf has some layout issues so please disregard these and only comment on the technical content.
> Alternatively, the complete user guide to date is also available form:
> * http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Develo...
> * https://github.com/jbosstools/jbosstools-documentation/tree/master/docs/J... (build with: mvn compile)
--
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, 10 months
[JBoss JIRA] (JBIDE-14615) Forge set VERBOSE true command automatically opens Error Log tab
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14615?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-14615:
-----------------------------------------
Changed the JBIDE reference in the description as pointed to the wrong thing.
> Forge set VERBOSE true command automatically opens Error Log tab
> ----------------------------------------------------------------
>
> Key: JBIDE-14615
> URL: https://issues.jboss.org/browse/JBIDE-14615
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: forge
> Affects Versions: 4.1.0.Beta1
> Reporter: Michelle Murray
> Assignee: Koen Aers
> Fix For: 4.1.x
>
>
> Related to JBIDE-11217, the Forge 'set VERBOSE true' command interacts with the IDE by recording exceptions in the error log. Would it be useful to users to automatically open (but not necessarily bring to the foreground) the Error Log tab when users issue the 'set VERBOSE true' command?
--
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, 10 months
[JBoss JIRA] (JBIDE-14615) Forge set VERBOSE true command automatically opens Error Log tab
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14615?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-14615:
------------------------------------
Description: Related to JBIDE-11217, the Forge 'set VERBOSE true' command interacts with the IDE by recording exceptions in the error log. Would it be useful to users to automatically open (but not necessarily bring to the foreground) the Error Log tab when users issue the 'set VERBOSE true' command? (was: Related to JBIDE-13978, the Forge 'set VERBOSE true' command interacts with the IDE by recording exceptions in the error log. Would it be useful to users to automatically open (but not necessarily bring to the foreground) the Error Log tab when users issue the 'set VERBOSE true' command? )
> Forge set VERBOSE true command automatically opens Error Log tab
> ----------------------------------------------------------------
>
> Key: JBIDE-14615
> URL: https://issues.jboss.org/browse/JBIDE-14615
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: forge
> Affects Versions: 4.1.0.Beta1
> Reporter: Michelle Murray
> Assignee: Koen Aers
> Fix For: 4.1.x
>
>
> Related to JBIDE-11217, the Forge 'set VERBOSE true' command interacts with the IDE by recording exceptions in the error log. Would it be useful to users to automatically open (but not necessarily bring to the foreground) the Error Log tab when users issue the 'set VERBOSE true' command?
--
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, 10 months