[JBoss JIRA] (JBDS-3250) Support for OpenShift 3 with Docker and Kubernetes
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3250?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3250:
-----------------------------
CDW devel_ack: ? (was: +)
> Support for OpenShift 3 with Docker and Kubernetes
> --------------------------------------------------
>
> Key: JBDS-3250
> URL: https://issues.jboss.org/browse/JBDS-3250
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: openshift, requirements
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Fix For: 9.0.0.GA
>
>
> Copied from JBDS-3278:
> As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API.
> The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture.
> For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"):
> {quote}
> It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo….
> Our Eclipse end-user needs to be able to “browse” for it and select it
> git clone it
> make changes
> git push it back
> {quote}
> This gives us 3 main use cases (as in mail and chats):
> # Import existing OpenShift project (JBDS-3297)
> # Push Changes to Existing OpenShift project (JBDS-3298)
> # New Project from Template (template should have a default buildconfig, deployconfig and docker image) (JBDS-3306)
> {quote}
> Use Case #1 assumes a TON about what has happened before me.
> - Assumes that OpenShift Enterprise is installed, configured and running happily at an accessible URL
> - Assumes end-user is already logged in (there is no auth method at this time)
> - Assumes that someone else (not our eclipse end-user) has manually created his/her “project” with an image, a git repo, a deployment config, a build config, defined routes, defined services, etc.
> {quote}
> We have a more extensive document that outlines the usecases:
> https://docs.google.com/a/redhat.com/document/d/1VwYNuKWUzuorU-6GcF420Vl_...
> {quote}
> These are features/capabilities currently NOT planned for OpenShift v3's Eclipse Tooling:
> 1) Create SSH Keys
> 2) Upload SSH Keys
> 3) Create Domain
> 4) Add a database, message broker, cache (embeddable cartridge)
> 5) Show In Web Browser
> 6) Review Env Vars
> 7) Edit Env Vars
> 8) Review Logs
> 9) Log Streaming
> 10) SSH in
> 11) Delete/Destroy
> 12) Remote Debugging (though that might "just work")
> 13) Snapshot creation
> 14) Snapshot restore
> 15) Port Forwarding
> 16) Marker Files
> 17) Node.js
> 18) PHP
> 19) Python
> 20) C++
> 21) Perl
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBDS-3251) Create screencasts for top features we like users to know more about from both JBoss Tools and base Eclipse
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3251?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3251:
--------------------------------------
Component/s: requirements
> Create screencasts for top features we like users to know more about from both JBoss Tools and base Eclipse
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3251
> URL: https://issues.jboss.org/browse/JBDS-3251
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: documentation, requirements
> Reporter: Max Rydahl Andersen
> Assignee: Misha Ali
> Fix For: 9.0.0.GA
>
>
> suggestions from F2F:
> |Maven Top 10 Use Cases| Import, multi-module, run on server, package vs install, update, adjust profiles, dependencies adds/removes|
> |Java EE Top 10 Use Cases JPA, db reveng, JAX-RS (including testing), CDI, content assist, Servlets, JSF, etc
> HTML5/Hybrid Mobile|
> |OpenShift v3| start, stop, deploy apps
> |eGit Top Use Cases|
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TOOLSDOC-612) Generate Release Notes for JBDS-IS 7.1 GA
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-612?page=com.atlassian.jira.plug... ]
Misha Ali commented on TOOLSDOC-612:
------------------------------------
Thanks, Andrej. In order:
Section 2: Amended list to *updated* and removed early access text.
Section 3: Amended and it should now have 7.1 issues only. (Update: Paul responded as well while I was writing this, so I have incorporated only the three he pointed out)
Section 5: Removed former Section 5 about Drools.
(New) Section 5: Added Fuse section with the one issue specified above.
Section 6: Waiting to hear.
Section 7: Former section 7 is excluded.
For BPMN2 issues:
*Added section for BPMN2 Modeler
* Added issues from 1.0.3, 10.4 (nothing for 1.0.5). Did not separate these by version, but can do if needed.
[~apodhrad], could you have a look at the fixed issues above while we wait for teiid feedback please?
> Generate Release Notes for JBDS-IS 7.1 GA
> -----------------------------------------
>
> Key: TOOLSDOC-612
> URL: https://issues.jboss.org/browse/TOOLSDOC-612
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Components: Release Notes
> Reporter: Misha Ali
> Assignee: Misha Ali
> Labels: Notes, Release, Tooling
>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBDS-3360) Align bits offered in JBoss Central with installed version of JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-3360:
--------------------------------
Assignee: Len DiMaggio
> Align bits offered in JBoss Central with installed version of JBDS
> ------------------------------------------------------------------
>
> Key: JBDS-3360
> URL: https://issues.jboss.org/browse/JBDS-3360
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, updatesite
> Affects Versions: 8.0.2.GA
> Reporter: Martin Malina
> Assignee: Len DiMaggio
> Fix For: 8.1.0.CR1
>
>
> The problem in JBDS-3359 shows a broader issue.
> (That one is about issues when clicking on an example in Central in JBDS 8.0.0 when 8.0.2 has already been released and central points to it.)
> Currently when you install JBDS 8.0.0, it will contain this update site in Preferences -> Available Software Sites:
> https://devstudio.redhat.com/updates/8.0/
> Initially this update site contained JBDS 8.0.0 core + 8.0.0 central.
> But once we released JBDS 8.0.1, the update site was updated with 8.0.1 and this update was offered to users in Eclipse. And we started to have two groups of users:
> 1. Those who stayed on JBDS 8.0.0, but their Central already pointed to 8.0.1 bits
> 2. Those who update to JBDS 8.0.1 (and their Central also pointed to 8.0.1 bits)
> Wouldn't it make more sense if central used the same version that is currently installed? I.e. if a user stays with JBDS 8.0.0, the bits offered in Central are 8.0.0 also.
> I'm not sure if this is doable or makes sense at all, so I'm looking forward to feedback :)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBDS-3285) Git: Easy Import
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3285:
-------------------------------
CDW qa_ack: + (was: ?)
> Git: Easy Import
> ----------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively):
> {quote}
> Easymport framework has been contributed to e4 (Platform Incubator): in http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/tree/bundles , see all org.eclipse.e4.ui.importer* . You can install it in your IDE from http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui . The entry-points are either the new menu "File > Import projects from folder..." or from legacy import wizard under "General > Local folder(s) as project into workspace".
> We have working extensions that allow to import Java EE & Maven: https://github.com/jbosstools/jbosstools-playground/tree/master/plugins (install from http://download.jboss.org/jbosstools/builds/staging/jbosstools-playground... ) , that we plan to contribute upstream when projects such as m2e and WTP when the framework seems mature enough.
> There is not yet an easy link from the EGit wizard to the Easymport one, nor an easy link from SVN wizard to Easymport.
> There is almost no chance that this can be included in Eclipse IDE for Mars release in June. But we could already think about including it in next JBoss Tools and JBoss Developer Studio milestones, so that we'd get more feedback. At this point, feedback from users and adopters is the key point.
> I invite you to give it a try, and to report issues here.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBDS-3285) Git: Easy Import
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3285:
--------------------------------
> Git: Easy Import
> ----------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively):
> {quote}
> Easymport framework has been contributed to e4 (Platform Incubator): in http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/tree/bundles , see all org.eclipse.e4.ui.importer* . You can install it in your IDE from http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui . The entry-points are either the new menu "File > Import projects from folder..." or from legacy import wizard under "General > Local folder(s) as project into workspace".
> We have working extensions that allow to import Java EE & Maven: https://github.com/jbosstools/jbosstools-playground/tree/master/plugins (install from http://download.jboss.org/jbosstools/builds/staging/jbosstools-playground... ) , that we plan to contribute upstream when projects such as m2e and WTP when the framework seems mature enough.
> There is not yet an easy link from the EGit wizard to the Easymport one, nor an easy link from SVN wizard to Easymport.
> There is almost no chance that this can be included in Eclipse IDE for Mars release in June. But we could already think about including it in next JBoss Tools and JBoss Developer Studio milestones, so that we'd get more feedback. At this point, feedback from users and adopters is the key point.
> I invite you to give it a try, and to report issues here.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBDS-3285) Git: Easy Import
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3285:
-----------------------------
CDW release: + (was: ?)
> Git: Easy Import
> ----------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively):
> {quote}
> Easymport framework has been contributed to e4 (Platform Incubator): in http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/tree/bundles , see all org.eclipse.e4.ui.importer* . You can install it in your IDE from http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui . The entry-points are either the new menu "File > Import projects from folder..." or from legacy import wizard under "General > Local folder(s) as project into workspace".
> We have working extensions that allow to import Java EE & Maven: https://github.com/jbosstools/jbosstools-playground/tree/master/plugins (install from http://download.jboss.org/jbosstools/builds/staging/jbosstools-playground... ) , that we plan to contribute upstream when projects such as m2e and WTP when the framework seems mature enough.
> There is not yet an easy link from the EGit wizard to the Easymport one, nor an easy link from SVN wizard to Easymport.
> There is almost no chance that this can be included in Eclipse IDE for Mars release in June. But we could already think about including it in next JBoss Tools and JBoss Developer Studio milestones, so that we'd get more feedback. At this point, feedback from users and adopters is the key point.
> I invite you to give it a try, and to report issues here.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month