[JBoss JIRA] (JBDS-2852) Database/source/connection Usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2852:
--------------------------------------
CDW devel_ack: + (was: ?)
Status: New (was: New)
> Database/source/connection Usability
> ------------------------------------
>
> Key: JBDS-2852
> URL: https://issues.jboss.org/browse/JBDS-2852
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Security Level: Public(Everyone can see)
> Components: integration, requirements
> Reporter: Burr Sutter
> Labels: QE_JBDS80_needinfo
>
> 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, 2 months
[JBoss JIRA] (JBDS-2838) OpenShift Usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2838?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2838:
-------------------------------------------
Thanks for the list of concerns [~burrsutter], just giving a quick context on each item since some I believe are already handled - but maybe not known.
* screen prompts that don't make sense
For these we should simply just gather/open jiras and get them prioritized.
* cluttered screens in the wizard
If you mean the New App wizard - then that is/should be covered in the work around quickstarts/instantapp - see JBIDE-14744 for the current mockups for this work.
* how to find the wizard if JBoss Central is closed (which it is for most users)
Is there a specific concern you have here ? The wizard is currently available where all other wizards are available from: File > New > OpenShift.
We got JBIDE-10546 to also make it available where other non-standard/defaults features gets enabled in eclipse (via the Configure menu in project context menu)
* what if I have forgotten my password or not yet even registered
The wizard has a "Please sign up here" with link to "https://openshift.redhat.com/app/account/new"
Not sure what more we can/should provide ?
* what if I wish to debug (we did not document it yet, I am not sure how the average joe would have figured that out)
[~mmurray] is in progress of documenting this (see TOOLSDOC-446). We could probably make some of these steps simpler to do though.
We have a prototype for this that is a bit old we can revive.
* I did not properly setup my SSH keys, how do I get started or recover from errors in this area?
This is a documentation issue I believe. In past there have been lots of issues here on openshift and tooling side but I believe we should be pretty good here - the only concern is for users to remember to add the key to eclipse if they are NOT using the default ssh key.
Does OpenShift docs cover this issue ?
* I wish to push to both my enterprise git repo AND openshift simultaneously
My answer depends on *why* you want this. What usecase?
but basically you would do this by using just normal git operations. Right click project and do git Push > enterprise git repo and git push > openshift repo.
I would find it unnatural/too complex to add this kind of feature into the openshift server adapter. WDYT ?
* I wish to only push to openshift initially and when I feel the code is "solid" then push to my enterprise git repo
Same answer as above since you literally cannot push to two repos at the same time you have to do it in two operations.
The area not covered in your items above is that we have two "entry" points to openshift - openshift explorer and the server adapter and both does not have same actions availlable causing confusion and unnecessary need to switch between the two.
This is covered in JBIDE-15897 and IMO one of the things we need to fix first.
> OpenShift Usability
> -------------------
>
> Key: JBDS-2838
> URL: https://issues.jboss.org/browse/JBDS-2838
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift, requirements
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: QE_JBDS80_needinfo
>
> This task is to explore the overall usability of the OpenShift Wizard, OpenShift Explorer, the adapter in the Servers Tab and review things like Run As on OpenShift (JBIDE-16069)
--
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, 2 months
[JBoss JIRA] (JBDS-2838) OpenShift Usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2838?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2838:
--------------------------------------
CDW devel_ack: + (was: ?)
Status: New (was: New)
> OpenShift Usability
> -------------------
>
> Key: JBDS-2838
> URL: https://issues.jboss.org/browse/JBDS-2838
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift, requirements
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: QE_JBDS80_needinfo
>
> This task is to explore the overall usability of the OpenShift Wizard, OpenShift Explorer, the adapter in the Servers Tab and review things like Run As on OpenShift (JBIDE-16069)
--
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, 2 months
[JBoss JIRA] (JBDS-2852) Database/source/connection Usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2852:
-------------------------------------------
btw. forge now supports using DTP connections so that means all parts of our stack now can use DTP connections which simplifies things greatly.
> Database/source/connection Usability
> ------------------------------------
>
> Key: JBDS-2852
> URL: https://issues.jboss.org/browse/JBDS-2852
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Security Level: Public(Everyone can see)
> Components: integration, requirements
> Reporter: Burr Sutter
> Labels: QE_JBDS80_needinfo
>
> 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, 2 months
[JBoss JIRA] (JBDS-2852) Database/source/connection Usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2852:
-------------------------------------------
I'm trying to locate the other jiras we have for this discussing the option of having JBoss Servers detect the database setup and import/export them in tools but I can't locate that right now.
As I read the teiid docs you already have big parts of this via your "import connection" which reads from the server and that is exactly what we need. Lets bring this to jboss tools core server setup.
One thing I could not spot in the import is how you handle the driver jars?
> Database/source/connection Usability
> ------------------------------------
>
> Key: JBDS-2852
> URL: https://issues.jboss.org/browse/JBDS-2852
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Security Level: Public(Everyone can see)
> Components: integration, requirements
> Reporter: Burr Sutter
> Labels: QE_JBDS80_needinfo
>
> 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, 2 months
[JBoss JIRA] (JBDS-2852) Database/source/connection Usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2852:
--------------------------------------
Epic Name: Datasource usability
> Database/source/connection Usability
> ------------------------------------
>
> Key: JBDS-2852
> URL: https://issues.jboss.org/browse/JBDS-2852
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Security Level: Public(Everyone can see)
> Components: integration, requirements
> Reporter: Burr Sutter
> Labels: QE_JBDS80_needinfo
>
> 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, 2 months
[JBoss JIRA] (JBDS-2852) Database/source/connection Usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2852:
-------------------------------------------
Barry, any reason why those are not done in jboss tools core insted of just Teiid ? This is exactly what we've wanted for ages but not had anyone around to do it ;)
> 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
> Labels: QE_JBDS80_needinfo
>
> 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, 2 months
[JBoss JIRA] (JBDS-2852) Database/source/connection Usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2852:
--------------------------------------
Issue Type: Epic (was: Feature Request)
> Database/source/connection Usability
> ------------------------------------
>
> Key: JBDS-2852
> URL: https://issues.jboss.org/browse/JBDS-2852
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Security Level: Public(Everyone can see)
> Components: integration, requirements
> Reporter: Burr Sutter
> Labels: QE_JBDS80_needinfo
>
> 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, 2 months