[JBoss JIRA] (JBIDE-21680) Trouble installing Hibernate Tools
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21680?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21680:
---------------------------------------------
I've updated the marketplace entries to say they explicitly only works for <= Previous to Juno
> Trouble installing Hibernate Tools
> ----------------------------------
>
> Key: JBIDE-21680
> URL: https://issues.jboss.org/browse/JBIDE-21680
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.1.Beta2
> Reporter: Koen Aers
> Assignee: Koen Aers
> Fix For: 4.4.0.Alpha1
>
>
> Hello,
> I was attempting to install the Hibernate Tools for a quick demo but it somehow managed to confuse me.. I probably should know better, but I imagine this could represent quite some population out there.
> I headed for the Eclipse marketplace (not the web page but the UI element within Eclipse) after a clean installation of Eclipse Mars update 1.
> I search for "Hibernate Tools", and then it seems I have to choose between "Indigo" and "Helios".
> TBH I didn't remember that those were Eclipse codename versions, so that's one problem.. I get in trouble trying to install either of course and it takes me a while to figure I need to search for "JBoss Tools" instead.. and probably reinstall my whole IDE to clean the mess.
> Searching for "JBoss Tools" isn't great either BTW as the correct result is just third, which means it's not even visible without using the scrollbar..
> I understand we want to push the "JBoss Tools" portfolio but ultimately I think we'd be better off by making sure that people get the right stuff when searching for "Hibernate Tools", as lots of people are accustomed to this name nowadays?
> Thanks,
> Sanne
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21680) Trouble installing Hibernate Tools
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21680?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21680:
---------------------------------------------
it is a generic issue of choosing between having marketplace entry for every imaginable plugin features vs a unified install experience. Same issue occurs for switchyard, fuse, etc. for now we've gone for the "not having to test and maintain multiple marketplace entries" appraoch.
btw. you should *not* see indigo nor helios when searching from withing Eclipse marketplace.
That is definitely an error.
> Trouble installing Hibernate Tools
> ----------------------------------
>
> Key: JBIDE-21680
> URL: https://issues.jboss.org/browse/JBIDE-21680
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.1.Beta2
> Reporter: Koen Aers
> Assignee: Koen Aers
> Fix For: 4.4.0.Alpha1
>
>
> Hello,
> I was attempting to install the Hibernate Tools for a quick demo but it somehow managed to confuse me.. I probably should know better, but I imagine this could represent quite some population out there.
> I headed for the Eclipse marketplace (not the web page but the UI element within Eclipse) after a clean installation of Eclipse Mars update 1.
> I search for "Hibernate Tools", and then it seems I have to choose between "Indigo" and "Helios".
> TBH I didn't remember that those were Eclipse codename versions, so that's one problem.. I get in trouble trying to install either of course and it takes me a while to figure I need to search for "JBoss Tools" instead.. and probably reinstall my whole IDE to clean the mess.
> Searching for "JBoss Tools" isn't great either BTW as the correct result is just third, which means it's not even visible without using the scrollbar..
> I understand we want to push the "JBoss Tools" portfolio but ultimately I think we'd be better off by making sure that people get the right stuff when searching for "Hibernate Tools", as lots of people are accustomed to this name nowadays?
> Thanks,
> Sanne
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3651) Reduce the delay between the main window opening and the first page being rendered
by Jan Richter (JIRA)
Jan Richter created JBDS-3651:
---------------------------------
Summary: Reduce the delay between the main window opening and the first page being rendered
Key: JBDS-3651
URL: https://issues.jboss.org/browse/JBDS-3651
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Components: installer
Reporter: Jan Richter
Starting the installer right now leaves the user with about 3 seconds of staring at an empty window before the content shows up.
I've done a few tests on this matter and it seems majority of those 3 seconds is spent on angular bootstrap - mainly loading the required files and registering controllers. Replacing the index with simple static HTML causes the page to render almost instantaneously.
We should consider some way of showing the GUI before the user falls asleep (before angular fully loads the entire app).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21793) Zero-click import of CDK
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21793?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21793:
---------------------------------------------
[~rob.stryker] i'm definitely -1 on removing the detection info completely, but didn't we do similar for EAP bundled with JBDS at one point ? basically we had a properties file that told devstudio that the bundled EAP should just be accepted no matter what.
Has that disappeared ?
> Zero-click import of CDK
> ------------------------
>
> Key: JBIDE-21793
> URL: https://issues.jboss.org/browse/JBIDE-21793
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection
> Affects Versions: 4.3.1.Beta2
> Reporter: Pete Muir
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> When the installer with the CDK completes and JBDS opens, the runtime detection dialog shows up asking the user if he wants to create a CDK server.
> We should try to import the CDK with no-clicks, and hide the detection dialog.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3650) username used for cdk could not be used with vagrant up on cdk
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3650?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3650:
--------------------------------------
Description:
in demo by [~dgolovin] he mentions the username used for running the installer could not be used with vagrant registration.
Why is that ? just unique for denis usernames or general problem ?
> username used for cdk could not be used with vagrant up on cdk
> --------------------------------------------------------------
>
> Key: JBDS-3650
> URL: https://issues.jboss.org/browse/JBDS-3650
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: cdk, installer
> Reporter: Max Rydahl Andersen
> Priority: Blocker
>
> in demo by [~dgolovin] he mentions the username used for running the installer could not be used with vagrant registration.
> Why is that ? just unique for denis usernames or general problem ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3649) is cygwin *really* required could we just use mingw
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBDS-3649:
-----------------------------------------
Summary: is cygwin *really* required could we just use mingw
Key: JBDS-3649
URL: https://issues.jboss.org/browse/JBDS-3649
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: installer
Reporter: Max Rydahl Andersen
Priority: Critical
current installer installs cygwin - can we not just use mingw and make sure its available in path for users after the install is done ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month