[JBoss JIRA] (JBDS-3363) Remove Protlet tooling from default JBDS installation
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3363?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-3363:
------------------------------
CDW docs_ack: ? (was: +)
> Remove Protlet tooling from default JBDS installation
> -----------------------------------------------------
>
> Key: JBDS-3363
> URL: https://issues.jboss.org/browse/JBDS-3363
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, installer, requirements
> Affects Versions: 9.0.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha2
>
>
> 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, 1 month
[JBoss JIRA] (JBDS-3363) Remove Protlet tooling from default JBDS installation
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3363?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-3363:
------------------------------
CDW pm_ack: ? (was: +)
> Remove Protlet tooling from default JBDS installation
> -----------------------------------------------------
>
> Key: JBDS-3363
> URL: https://issues.jboss.org/browse/JBDS-3363
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, installer, requirements
> Affects Versions: 9.0.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha2
>
>
> 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, 1 month
[JBoss JIRA] (JBDS-3363) Remove Protlet tooling from default JBDS installation
by Fred Bricon (JIRA)
Fred Bricon created JBDS-3363:
---------------------------------
Summary: Remove Protlet tooling from default JBDS installation
Key: JBDS-3363
URL: https://issues.jboss.org/browse/JBDS-3363
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: central, installer, requirements, seam
Affects Versions: 9.0.0.Alpha1
Reporter: Fred Bricon
Assignee: Nick Boldt
Fix For: 9.0.0.Alpha2
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, 1 month
[JBoss JIRA] (JBDS-3363) Remove Protlet tooling from default JBDS installation
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3363?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3363:
-----------------------------
CDW devel_ack: ? (was: +)
CDW release: ? (was: +)
> Remove Protlet tooling from default JBDS installation
> -----------------------------------------------------
>
> Key: JBDS-3363
> URL: https://issues.jboss.org/browse/JBDS-3363
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, installer, requirements
> Affects Versions: 9.0.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha2
>
>
> 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, 1 month
[JBoss JIRA] (JBDS-3363) Remove Protlet tooling from default JBDS installation
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3363?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-3363:
------------------------------
Component/s: (was: seam)
> Remove Protlet tooling from default JBDS installation
> -----------------------------------------------------
>
> Key: JBDS-3363
> URL: https://issues.jboss.org/browse/JBDS-3363
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, installer, requirements
> Affects Versions: 9.0.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha2
>
>
> 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, 1 month
[JBoss JIRA] (JBDS-3281) Screencasts: Git
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3281?page=com.atlassian.jira.plugin.... ]
Burr Sutter commented on JBDS-3281:
-----------------------------------
I would like to see the "from engineering perspective", based on what we think is included (plugins, features, capabilities, etc), the following N things should work. One of our challenges has been that docs, QE, engineering, PM and our end-users all have different views of how something should be done - git and maven are two great examples of lots of possible pitfalls and traps.
> Screencasts: Git
> ----------------
>
> Key: JBDS-3281
> URL: https://issues.jboss.org/browse/JBDS-3281
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, requirements
> Reporter: Burr Sutter
> Assignee: Michelle Murray
> Priority: Minor
>
> As a Java EE developer, new to Eclipse + Git, I need educational, 5 minute screencasts on the most common uses of Git inside of Eclipse.
> Use cases include:
> 1) as a new member of the team, just having only installed JBDS, I need to add an element to the project
> assume a clone, add (or modify), commit, push workflow
> a- Getting started as a new member of an existing git project (I need to clone a repo, import the project, insure my facets/Maven are set correctly)
> b- navigate/browse an existing repository
> c- git add - for a newly added class or file
> d- git commit -a
> e- git push
> as a new member of the team, just having only installed JBDS, I need to resolve a pull request.
> 2) other scenarios
> - git init a current project that I have in my workspace (and should I move it outside of my workspace first)
> - git checkout for a specific branch - getting Maven and Eclipse Facets to properly recognize my newly checked out branch
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBDS-3279) Screencasts: Maven
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3279?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3279:
-------------------------------------------
+1
> Screencasts: Maven
> ------------------
>
> Key: JBDS-3279
> URL: https://issues.jboss.org/browse/JBDS-3279
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, maven, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Priority: Minor
> Fix For: 9.0.x
>
>
> As a Java EE developer, new to using Eclipse + Maven, I need short, sub-6 minute screencasts of individual key Maven focused use cases, so that I can better understand how Maven is integrated into the Eclipse + Java EE development workflow.
> Use cases include:
> - creation of a new project and its pom.xml, with the pom.xml editor
> - dependencies adds/removes
> - Import maven projects - from a SVN or Git repo
> - multi-module maven projects
> - run on server
> - package vs install
> - update - the magic "update project" that helps get Eclipse and Maven back into agreement
> - adjust profiles - address the Arquillian profile
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month