[JBoss JIRA] (JBDS-3286) Remove Seam tooling from default JBDS installation
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3286?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3286:
-----------------------------
Fix Version/s: 9.0.0.Alpha1
> Remove Seam tooling from default JBDS installation
> --------------------------------------------------
>
> Key: JBDS-3286
> URL: https://issues.jboss.org/browse/JBDS-3286
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, installer, seam
> Affects Versions: 9.0.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha1
>
>
> With Seam being pretty much dead and the tools in maintenance mode, I'm opening this issue to discuss whether we should drop Seam from the JBDS installer and only keep it available from JBoss Central (required as part of JBIDE-18922 already).
> [~burrsutter], [~maxandersen], [~ldimaggio], [~akazakov], [~mmurray] : WDYT?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3210) create a JBDS Central feature which includes only JBDS Central branding plugin
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3210?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3210:
-----------------------------------
Be aware JBIDE-18426 requires breaking changes so can't be done in 8.1
> create a JBDS Central feature which includes only JBDS Central branding plugin
> ------------------------------------------------------------------------------
>
> Key: JBDS-3210
> URL: https://issues.jboss.org/browse/JBDS-3210
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 8.1.0.GA
>
>
> Purpose:
> Provide a single feature which includes both JBoss Central (pulled from JBoss Tools, minus its "community" plugin, org.jboss.tools.community.central) and the JBDS Central branding plugin, com.jboss.devstudio.core.central.
> Reason:
> This will allow us to create Marketplace installs for things like JBDS Fuse Tooling which include ONLY the Fuse features + the bare bones of Central, without having all of JBDS come along for the ride. Without this, we can create a JBoss Tools-branded Fuse entry in the Marketplace, or a JBDS-branded Fuse entry in the Marketplace [which includes all of JBDS]. We want a JBDS-branded Fuse entry, which only includes the bare bones, not ALL the JBDS stuff.
> Technical problems:
> * Marketplace can only install features, not individual plugins
> * Today, the only way to install JBDS Central via Marketplace is to include the com.jboss.devstudio.core.feature, which includes the com.jboss.devstudio.core.central branding plugin. But doing so installs ALL of JBDS, too.
> Solution:
> 1. Create a com.jboss.devstudio.core.central.feature which includes:
> * com.jboss.devstudio.core.central
> * org.jboss.tools.central
> 2. Optionally, could also include these plugins:
> * com.jboss.devstudio.core.project.examples
> * com.jboss.devstudio.core.usage.branding
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18901) git clone + cordova import
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18901?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-18901.
----------------------------------
Resolution: Rejected
Creating an import wizard is an easier solution with a better user experience
created JBDS-3287 for the wizard
> git clone + cordova import
> --------------------------
>
> Key: JBIDE-18901
> URL: https://issues.jboss.org/browse/JBIDE-18901
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Burr Sutter
> Assignee: Gorkem Ercan
> Fix For: 4.2.3.Final, 4.3.0.Beta1
>
>
> Currently, the git clone wizard does not work with the Cordova project import. The end-user must run the git clone wizard to a point, then cancel out, then start the cordova project import wizard.
> In addition, the git clone wizard is fairly "hard to use".
> Feature proposal: add git clone support to the Cordova project import - so it can import from file system AND import from a git URL.
> Current UI: http://www.screencast.com/t/2bjzPI6EuEgl
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3287) Import FeedHenry Cordova (full or advanced) project to JBDS
by Gorkem Ercan (JIRA)
Gorkem Ercan created JBDS-3287:
----------------------------------
Summary: Import FeedHenry Cordova (full or advanced) project to JBDS
Key: JBDS-3287
URL: https://issues.jboss.org/browse/JBDS-3287
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: aerogear-hybrid
Reporter: Gorkem Ercan
Assignee: Gorkem Ercan
Implement an import wizard that queries the list of projects on a FeedHenry account and allows importing the Cordova (advanced) applications to JBDS as a Hybrid Mobile project.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3275) Add wildfly archetypes to JBoss Central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3275?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3275:
--------------------------------------
Component/s: requirements
> Add wildfly archetypes to JBoss Central
> ---------------------------------------
>
> Key: JBDS-3275
> URL: https://issues.jboss.org/browse/JBDS-3275
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 8.1.0.GA
>
>
> Supporting Wildfly archetypes with JBoss Central. As an Java EE developer, I need to be able to switch between EAP and Wildfly, when I select Wildfly, the archetype needs to correctly include the right BOMs, where all artifacts are available only on Maven Central.
> This should include both the Java EE Web Project, Java EE EAR Project, and HTML5 Project
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3275) Add wildfly archetypes to JBoss Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3275?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-3275:
------------------------------
Fix Version/s: 8.1.0.GA
(was: 9.0.0.Alpha1)
> Add wildfly archetypes to JBoss Central
> ---------------------------------------
>
> Key: JBDS-3275
> URL: https://issues.jboss.org/browse/JBDS-3275
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 8.1.0.GA
>
>
> Supporting Wildfly archetypes with JBoss Central. As an Java EE developer, I need to be able to switch between EAP and Wildfly, when I select Wildfly, the archetype needs to correctly include the right BOMs, where all artifacts are available only on Maven Central.
> This should include both the Java EE Web Project, Java EE EAR Project, and HTML5 Project
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months