September 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2733) Make Cordova tooling and CordovaSim available from software/update tab

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2733?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2733: ----------------------------- CDW release: + (was: ?) > Make Cordova tooling and CordovaSim available from software/update tab > ----------------------------------------------------------------------- > > Key: JBDS-2733 > URL: https://issues.jboss.org/browse/JBDS-2733 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Nick Boldt > > Cordova should be available from JBDS, but it is not fully supported tech yet thus should be included/marked as a Technology Preview -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2736) Split Web and Mobile Development into 2 categories in JBT & JBDS Central

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2736?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2736: ----------------------------- CDW release: + (was: ?) > Split Web and Mobile Development into 2 categories in JBT & JBDS Central > ------------------------------------------------------------------------ > > Key: JBDS-2736 > URL: https://issues.jboss.org/browse/JBDS-2736 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery, requirements > Reporter: Burr Sutter > Assignee: Nick Boldt > > http://screencast.com/t/7vsajdz9o > Now that Cordova tools have been proposed, we need to split Web & Mobile into there own categories on the Software/Update tab. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2736) Split Web and Mobile Development into 2 categories in JBT & JBDS Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2736?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2736: ----------------------------- CDW devel_ack: + (was: ?) > Split Web and Mobile Development into 2 categories in JBT & JBDS Central > ------------------------------------------------------------------------ > > Key: JBDS-2736 > URL: https://issues.jboss.org/browse/JBDS-2736 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery, requirements > Reporter: Burr Sutter > Assignee: Nick Boldt > > http://screencast.com/t/7vsajdz9o > Now that Cordova tools have been proposed, we need to split Web & Mobile into there own categories on the Software/Update tab. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2753) Merge "Google Plugin + Web Toolkit" + "Google Web Toolkit Designer"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2753?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-2753: -------------------------------- Assignee: Nick Boldt > Merge "Google Plugin + Web Toolkit" + "Google Web Toolkit Designer" > ------------------------------------------------------------------- > > Key: JBDS-2753 > URL: https://issues.jboss.org/browse/JBDS-2753 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery, requirements > Reporter: Burr Sutter > Assignee: Nick Boldt > Attachments: 2013-09-04_1215.png > > > See screenshot. > Do we need to keep the two Google Web Toolkit options separate? They were separated because they came in at different intervals, now it is unclear to me if they need to remain separate. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2724) Include "Mylyn Builds Connector: Hudson/Jenkins" org.eclipse.mylyn.hudson.feature in both JBT & JBDS Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2724?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2724: ----------------------------- CDW devel_ack: + (was: ?) > Include "Mylyn Builds Connector: Hudson/Jenkins" org.eclipse.mylyn.hudson.feature in both JBT & JBDS Central > ------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2724 > URL: https://issues.jboss.org/browse/JBDS-2724 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery, requirements > Reporter: Burr Sutter > Attachments: JBDS7_central.png > > > We should make it easier to work with jenkins for our devops users. > Start by including the Jenkins plugin (from Max: Mylyn build plugin) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2724) Include "Mylyn Builds Connector: Hudson/Jenkins" org.eclipse.mylyn.hudson.feature in both JBT & JBDS Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2724?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-2724: -------------------------------- Assignee: Nick Boldt > Include "Mylyn Builds Connector: Hudson/Jenkins" org.eclipse.mylyn.hudson.feature in both JBT & JBDS Central > ------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2724 > URL: https://issues.jboss.org/browse/JBDS-2724 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery, requirements > Reporter: Burr Sutter > Assignee: Nick Boldt > Attachments: JBDS7_central.png > > > We should make it easier to work with jenkins for our devops users. > Start by including the Jenkins plugin (from Max: Mylyn build plugin) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2753) Merge "Google Plugin + Web Toolkit" + "Google Web Toolkit Designer"

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2753?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2753: ----------------------------- CDW release: + (was: ?) > Merge "Google Plugin + Web Toolkit" + "Google Web Toolkit Designer" > ------------------------------------------------------------------- > > Key: JBDS-2753 > URL: https://issues.jboss.org/browse/JBDS-2753 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery, requirements > Reporter: Burr Sutter > Attachments: 2013-09-04_1215.png > > > See screenshot. > Do we need to keep the two Google Web Toolkit options separate? They were separated because they came in at different intervals, now it is unclear to me if they need to remain separate. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2753) Merge "Google Plugin + Web Toolkit" + "Google Web Toolkit Designer"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2753?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2753: ----------------------------- CDW devel_ack: + (was: ?) > Merge "Google Plugin + Web Toolkit" + "Google Web Toolkit Designer" > ------------------------------------------------------------------- > > Key: JBDS-2753 > URL: https://issues.jboss.org/browse/JBDS-2753 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery, requirements > Reporter: Burr Sutter > Attachments: 2013-09-04_1215.png > > > See screenshot. > Do we need to keep the two Google Web Toolkit options separate? They were separated because they came in at different intervals, now it is unclear to me if they need to remain separate. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2724) Include "Mylyn Builds Connector: Hudson/Jenkins" org.eclipse.mylyn.hudson.feature in both JBT & JBDS Central

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2724?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2724: ----------------------------- CDW release: + (was: ?) > Include "Mylyn Builds Connector: Hudson/Jenkins" org.eclipse.mylyn.hudson.feature in both JBT & JBDS Central > ------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2724 > URL: https://issues.jboss.org/browse/JBDS-2724 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery, requirements > Reporter: Burr Sutter > Attachments: JBDS7_central.png > > > We should make it easier to work with jenkins for our devops users. > Start by including the Jenkins plugin (from Max: Mylyn build plugin) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15392) Add api in server needed for source lookup

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15392: ------------------------------------- Version bump would definitely be required for maintenance. Maintenance should continue using hard-coded for now. > It would be just good the API to return jars for a default configuration for JBoss AS < 7.0. That isn't obliged, but can be easily added. I will add this to the PR. I have separated the PR into 2 commits. One is an api cleanup (moving some classes, marking stuff as internal, etc) and the second is the addition of the new test, new API class, etc. I will look into adding an additional method ot the API class to pass in 'default' or its equivilent for all server types (ie, standalone.xml for as7, and "default" for as<7). The PR has been updated to just show the additions. Good work all around. > Add api in server needed for source lookup > ------------------------------------------ > > Key: JBIDE-15392 > URL: https://issues.jboss.org/browse/JBIDE-15392 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > As uncovered in https://github.com/jbosstools/jbosstools-central/pull/128/files#L5L120 we got a problem with source lookup code always having to play catchup with server changes. > We need to define a stable api that can be used here. > lets outline what api is actually needed and then subjiras for the specifics. > For me it looks like server lookup needs a few things: > 0. know exact version of server > 1. know the file structure of a certain server > 2. get dir or directories that contain jar that is the "runtime" > My guess is that #2 might just be sufficient for source code lookup. > Any comments ? -- 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, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2013