[JBoss JIRA] (JBIDE-14607) Forge Wizards Menu
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14607?page=com.atlassian.jira.plugi... ]
Koen Aers resolved JBIDE-14607.
-------------------------------
Resolution: Duplicate Issue
> Forge Wizards Menu
> ------------------
>
> Key: JBIDE-14607
> URL: https://issues.jboss.org/browse/JBIDE-14607
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: forge
> Affects Versions: 4.1.0.Beta1
> Reporter: Burr Sutter
> Assignee: Koen Aers
> Fix For: 4.1.0.Beta2
>
> Attachments: forge_wizards.png
>
>
> The Forge Wizards are currently "buried" under Command/Ctrl-N, under the JBoss Tools category, they have no icons.
> New Project
> Persistence Setup
> New Entity
> New Field
> Generate Entities
> Scaffold Setup
> Scaffold Entities
> I propose the following:
> These be pulled into a category called "JBoss Forge"and that category also be available on the right-click/context New menu for any Maven-based project.
> I normally will use either the HTML5, Java EE Web or RichFaces archetypes from JBoss Central as the starting point for a project - then add entities/scaffolding via Forge.
--
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-14607) Forge Wizards Menu
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14607?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-14607:
-----------------------------------
Duplicate of JBIDE-14680
> Forge Wizards Menu
> ------------------
>
> Key: JBIDE-14607
> URL: https://issues.jboss.org/browse/JBIDE-14607
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: forge
> Affects Versions: 4.1.0.Beta1
> Reporter: Burr Sutter
> Assignee: Koen Aers
> Fix For: 4.1.0.Beta2
>
> Attachments: forge_wizards.png
>
>
> The Forge Wizards are currently "buried" under Command/Ctrl-N, under the JBoss Tools category, they have no icons.
> New Project
> Persistence Setup
> New Entity
> New Field
> Generate Entities
> Scaffold Setup
> Scaffold Entities
> I propose the following:
> These be pulled into a category called "JBoss Forge"and that category also be available on the right-click/context New menu for any Maven-based project.
> I normally will use either the HTML5, Java EE Web or RichFaces archetypes from JBoss Central as the starting point for a project - then add entities/scaffolding via Forge.
--
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-14607) Forge Wizards Menu
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14607?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-14607:
------------------------------
Fix Version/s: 4.1.0.Beta2
Affects Version/s: 4.1.0.Beta1
> Forge Wizards Menu
> ------------------
>
> Key: JBIDE-14607
> URL: https://issues.jboss.org/browse/JBIDE-14607
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: forge
> Affects Versions: 4.1.0.Beta1
> Reporter: Burr Sutter
> Assignee: Koen Aers
> Fix For: 4.1.0.Beta2
>
> Attachments: forge_wizards.png
>
>
> The Forge Wizards are currently "buried" under Command/Ctrl-N, under the JBoss Tools category, they have no icons.
> New Project
> Persistence Setup
> New Entity
> New Field
> Generate Entities
> Scaffold Setup
> Scaffold Entities
> I propose the following:
> These be pulled into a category called "JBoss Forge"and that category also be available on the right-click/context New menu for any Maven-based project.
> I normally will use either the HTML5, Java EE Web or RichFaces archetypes from JBoss Central as the starting point for a project - then add entities/scaffolding via Forge.
--
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-14791) cannot rename deployed modules in AS7 server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14791?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-14791 at 6/11/13 3:16 AM:
-------------------------------------------------------------------
[~maxandersen] right now the issue looks invalid to me since my steps were just not right. To me the workflow is hard to catch, it's not obvious. It looks like we should improve it or make it more obvious. max, plz comment and clarify what you consider an issue
was (Author: adietish):
[~maxandersen] plz comment and clarify what you consider an issue
> cannot rename deployed modules in AS7 server adapter
> ----------------------------------------------------
>
> Key: JBIDE-14791
> URL: https://issues.jboss.org/browse/JBIDE-14791
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Beta2
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
> Attachments: deployments-greyed-out.png
>
>
> The as7 server adapter seem not to allow one to rename deployed modules.
> i.e. to be able to deploy testapp.war as ROOT.war for having it deployed in /
--
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-345) NeedInfo: Distinction between Eclipse and JBDS/JBT Server Tools
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-345?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-345:
-------------------------------------
Assignee: Rob Stryker (was: Michelle Murray)
> NeedInfo: Distinction between Eclipse and JBDS/JBT Server Tools
> ---------------------------------------------------------------
>
> Key: TOOLSDOC-345
> URL: https://issues.jboss.org/browse/TOOLSDOC-345
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - JBoss Server Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Rob Stryker
> Fix For: 4.1.0
>
>
> I am trying to distinguish which features are provided by Eclipse and which are provided by JBoss Server Tools so that I can accurately document JBoss Server Tools.
> The unique JBoss Server Tools features I have are:
> * automatic runtime detection
> * ability to download and install a JBoss runtime
> * JBoss Server Editor - lots of the panes in the overview tab are unique and * the deployment tab is completely unique
> * set a default server icon
> * set default filesets
> * set default classpath entries
> * create new server wizard also seems different for JBoss enterprise and community servers than in the wizard in Eclipse alone
> What have I missed?
--
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-14791) cannot rename deployed modules in AS7 server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14791?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-14791:
----------------------------------------
Assignee: Max Rydahl Andersen (was: Rob Stryker)
[~maxandersen] plz comment and clarify what you consider an issue
> cannot rename deployed modules in AS7 server adapter
> ----------------------------------------------------
>
> Key: JBIDE-14791
> URL: https://issues.jboss.org/browse/JBIDE-14791
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Beta2
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
> Attachments: deployments-greyed-out.png
>
>
> The as7 server adapter seem not to allow one to rename deployed modules.
> i.e. to be able to deploy testapp.war as ROOT.war for having it deployed in /
--
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-14668) In case of 404, display the actual URL (in case of redirection)
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14668?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-14668:
----------------------------------
Fix Version/s: 4.2.0.Alpha1
(was: 4.1.0.Beta2)
> In case of 404, display the actual URL (in case of redirection)
> ---------------------------------------------------------------
>
> Key: JBIDE-14668
> URL: https://issues.jboss.org/browse/JBIDE-14668
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: livereload
> Affects Versions: 4.1.0.Beta1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Alpha1
>
>
> For example, if the index.html page contains the following code:
> {code}
> <html>
> <head>
> <meta http-equiv="Refresh" content="0; URL=index.jsf">
> </head>
> </html>
> {code}
> then the LiveReload server will first serve the index.html page and the browser will then redirect to index.jsf which does not exist as a file, which ends up with a 404 error from the server, but the user may not be aware of the redirect and think that the LiveReload server does not work as expected...
--
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