[JBoss JIRA] (JBIDE-10650) EGitUtils is too large, needs to be split into smaller parts
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10650?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-10650:
-------------------------------------
Assignee: (was: Andre Dietisheim)
Estimated Difficulty: Low
> EGitUtils is too large, needs to be split into smaller parts
> ------------------------------------------------------------
>
> Key: JBIDE-10650
> URL: https://issues.jboss.org/browse/JBIDE-10650
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.M5
> Reporter: Andre Dietisheim
> Priority: Minor
> Fix For: LATER
>
>
> EGitUtils is a collection of handy utilities to simplify tasks when dealing with EGit/JGit in OpenShift. It holds all its functionality in static methods. The class grew up to > 800 lines in its current incarnation. This is by far too large to be maintained effectively. We need to split it up into smaller parts (into commands? into several util classes?)
--
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, 4 months
[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 commented on JBIDE-15471:
-------------------------------------
I can see how the progress monitor can't be stopped which is pretty annoying. However I don't see why missing an EE runtime is relevant here. WTP runtimes are not involved/required during the Maven project creation
> 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: 4.2.0.Alpha2
>
>
> 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 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, 4 months
[JBoss JIRA] (JBDS-2866) CordovaSim Debugger
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ]
Burr Sutter updated JBDS-2866:
------------------------------
Component/s: requirements
> CordovaSim Debugger
> -------------------
>
> Key: JBDS-2866
> URL: https://issues.jboss.org/browse/JBDS-2866
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: browsersim, requirements
> Reporter: Burr Sutter
> Assignee: Ilya Buziuk
>
> The current FireBug Lite in CordovaSim has the following limitations:
> 1) When using LiveReload, the window closes with every reload
> 2) Various "page load" events with console.log statements are not visible in FireBug Lite console, like having console.log() in your deviceready
> http://screencast.com/t/RRGhV9PV
> Note: I forgot to add the Console Cordova plugin, not sure if that is necessary but the window closes, so not sure how I would see the message
--
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, 4 months
[JBoss JIRA] (JBDS-2851) Team Usability
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2851?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2851:
-----------------------------
Component/s: requirements
> Team Usability
> --------------
>
> Key: JBDS-2851
> URL: https://issues.jboss.org/browse/JBDS-2851
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
>
> It has come to our attention in the past that users, relatively new to Eclipse overall struggle with basic team dev concepts such as
> - how to integrate with CVS, SVN, Git
> - how to "import" a Maven-based project from SCM
> "Check out Maven Projects from SCM" has misfired for some users
> - how to "checkin" changes back to the SCM
> To some degree the problem is simply that Eclipse offers way too many menu-items that see to do approximately the same things.
> For example, if "Check out Maven Projects from SCM" is supposed to work then we likely need to document how it works with CVS, SVN and Git specifically.
--
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, 4 months
[JBoss JIRA] (JBDS-2852) Database/source/connection Usability
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2852:
-----------------------------
Component/s: requirements
> Database/source/connection Usability
> ------------------------------------
>
> Key: JBDS-2852
> URL: https://issues.jboss.org/browse/JBDS-2852
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: integration, requirements
> Reporter: Burr Sutter
>
> Connecting to a database from within JBDS/Eclipse is a multi-step, multi-screen, potentially error-prone challenge.
> Forge is involved as it can generate entities from schema
> Datasources are needed in/on AS/Wildfly/EAP in order for the project deploy
> Persistence.xml may needed to be tweaked for the datasource
> End-user would like to navigate the schema in the DTP/Hibernate Tools, interactively review the data and there was once a feature for viewing an ORM diagram that I seem to have forgotten how it is displayed.
> What happens when a project that needs a database connection is imported into the IDE?
> This was partially addressed with
> https://issues.jboss.org/browse/JBIDE-15263
> Let's see if we can continue to improve the workflow by reducing steps, making it more obvious what steps are required (e.g. hey developer, get the mysql driver .jar), auto generating the -ds.xml, with a decent explanation for the end-user to follow.
--
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, 4 months
[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins
by Mustafa Musaji (JIRA)
[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ]
Mustafa Musaji commented on JBDS-2745:
--------------------------------------
[~burrsutter] What sort of non-GA or Early Access content is this about? Can you give me an example of some tooling that would fall in to this category. Would this not fall in to the "technical preview" category?
> Support installation of Early Access / Experimental / Incubating plugins
> ------------------------------------------------------------------------
>
> Key: JBDS-2745
> URL: https://issues.jboss.org/browse/JBDS-2745
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, requirements
> Affects Versions: 7.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Burr Sutter
>
> It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear?
> [~burrsutter], [~maxandersen], are we talking about:
> * an additional dialog warning users about untested content? (that might be ignored / blindclicked)
> * an additional tab in Central for this type of content (what label would you use?)
> * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored)
> * some other workflow?
> See also JBDS-2068.
--
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, 4 months