[JBoss JIRA] (JBIDE-13698) Build As submenu
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13698?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-13698:
--------------------------------
Fix Version/s: LATER
(was: 4.1.x)
> Build As submenu
> ----------------
>
> Key: JBIDE-13698
> URL: https://issues.jboss.org/browse/JBIDE-13698
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: LATER
>
> Attachments: Screen Shot 2013-03-01 at 8.03.01 AM.png
>
>
> This is a usability issue - new users to Eclipse struggle with finding the "mvn package" or "mvn install" options hidden in the JBDS menu. Having those under Run As is simply not intuitive. Not too mention that there is a Maven menu, that does not have the build options - which would have been slightly more intuitive.
> One proposal is a Build As menu - where I can issue my various mvn commands.
> Screenshot of current JBDS 7 context menu (right-click) on a project attached.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JBIDE-15471) Cannot cancel creating Java EE project
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15471?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-15471:
--------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> Cannot cancel creating Java EE project
> --------------------------------------
>
> Key: JBIDE-15471
> URL: https://issues.jboss.org/browse/JBIDE-15471
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, project-examples
> Affects Versions: 4.1.0.Final
> Environment: Fedora Gnome 3.4.2
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Minor
> Fix For: LATER
>
>
> During creation of new Java EE Web project or Java EE EAR project is impossible to cancel task - cancellation icon is grey and unclickable. If user doesn't have EE runtime it takes significant time to download it etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JBIDE-18496) Importing EAP "ws*" quickstarts raise errors
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18496?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-18496:
--------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> Importing EAP "ws*" quickstarts raise errors
> --------------------------------------------
>
> Key: JBIDE-18496
> URL: https://issues.jboss.org/browse/JBIDE-18496
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.CR1
> Java 1.7 - OpenJDK
> RHEL6
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Fix For: LATER
>
>
> Steps to recreate issue:
> * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap
> * Install JBDS8.0.CR1
> * Import-> Existing Maven Projects - select the quickstart
> It looks like this error was logged here - JBIDE-17859 - and was believed to be fixed - but it is still present for these quickstarts.
> The quickstarts are:
> jboss-wsat-simple
> jboss-wsba-coordinator-completion-simple
> jboss-wsba-participant-completion-simple
> cvc-elt.1: Cannot find the declaration of element 'handler-chains'. context-handlers.xml /jboss-wsat-simple/src/main/webapp/WEB-INF/classes line 20 XML Problem
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JBIDE-13788) mvn package
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13788?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-13788:
--------------------------------
Fix Version/s: LATER
(was: 4.1.x)
> mvn package
> -----------
>
> Key: JBIDE-13788
> URL: https://issues.jboss.org/browse/JBIDE-13788
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: LATER
>
> Attachments: 2013-03-13_1738.png, Screen Shot 2013-03-13 at 5.39.10 PM.png
>
>
> In Java EE land you tend to use "mvn package", but that is not listed in the menu, nor is it visible in the dialog. Not too mention, having the Maven commands under the Run menu option, instead of the Maven menu is counter-intuitive.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JBIDE-15435) "installed plugins" detection seems fishy in project examples / central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15435?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-15435:
--------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> "installed plugins" detection seems fishy in project examples / central
> -----------------------------------------------------------------------
>
> Key: JBIDE-15435
> URL: https://issues.jboss.org/browse/JBIDE-15435
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, discovery, project-examples
> Affects Versions: 4.1.0.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: LATER
>
>
> Following JBDS-2753, [~maxandersen] says he installed the JBoss GWT connector, which dragged the GPE plugins.
> Some functionality seem missing according to Max (which ones?). In the JBoss Central 'software updates' page, the GWT/GPE connector is shown as missing. In the GWT example wizard, the feature appears as installed. One of the 2 is wrong, obviously.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JBIDE-13703) Explore better ways for team import/sharing of projects
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13703?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-13703:
--------------------------------
Fix Version/s: LATER
(was: 4.1.x)
> Explore better ways for team import/sharing of projects
> -------------------------------------------------------
>
> Key: JBIDE-13703
> URL: https://issues.jboss.org/browse/JBIDE-13703
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: LATER
>
> Attachments: JBDS-usability.pdf, Netbeans-Open-project.PNG
>
>
> The average end-user would like to:
> 1) check out (clone) a project from CVS, SVN or Git
> -- add repo, navigate repo, check out a project
> -- project may or may not have .classpath, .project or .settings files
> -- project may be Maven-based
> and see if the following work
> 2) Are the appropriate facets enabled?
> 3) Does it build immediately?
> 4) Can I immediately hit the run button to launch it on my app server?
> 5) Can I immediately hit the debug button to debug it on my app server?
> -- how do I step if there are no break points?
> 6) Make a change to a file, re-run/debug again
> 7) Run JUnit tests
> 8) Check the change back into the repo with comments
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JBIDE-14085) Compatible Target Runtimes in New Project Example Archetype wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14085?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-14085:
--------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> Compatible Target Runtimes in New Project Example Archetype wizard
> ------------------------------------------------------------------
>
> Key: JBIDE-14085
> URL: https://issues.jboss.org/browse/JBIDE-14085
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Affects Versions: 4.1.0.Alpha2
> Reporter: Denis Golovin
> Assignee: Fred Bricon
> Fix For: LATER
>
>
> Would be good to introduce Compatible Target Runtime in some way:
> 1. Show only compatible Target Runtimes in combo
> 2. Show all available runtimes, but let user to know what runtime is compatible with selected archetype (could be a mark on runtime in combo or warning in wizard title)
> 3. Show compatible RT only, but if there are none show all and warn in wizard title
> 4. Show compatible only by default and add preference to show all
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month