September 2013 - jbosstools-issues

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

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2753?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2753: ------------------------------- CDW qa_ack: + > 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-2759) Document Maven Tools functionality in User Guide

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2759?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2759: ------------------------------- CDW qa_ack: + > Document Maven Tools functionality in User Guide > ------------------------------------------------ > > Key: JBDS-2759 > URL: https://issues.jboss.org/browse/JBDS-2759 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: documentation, requirements > Reporter: Michelle Murray > Assignee: Michelle Murray > > Add a chapter to the JBDS User Guide on Maven Tools. -- 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-2729) Add mobile web quickstarts for JBoss Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2729?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2729: ----------------------------------- Actually I meant to ask about all *mobile* quickstarts > Add mobile web quickstarts for JBoss Central > -------------------------------------------- > > Key: JBDS-2729 > URL: https://issues.jboss.org/browse/JBDS-2729 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: aerogear-hybrid, central > Reporter: Burr Sutter > > The mobile web quickstarts being proced on WFK2 side should be included in JBoss Central -- 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 Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2753?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2753: ----------------------------------- No example currently refers to the GWT Designer connector, so you just need to merge it with com.google.gpe.gwt. > 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-2686) Investigate use of SpringSource's Quick Search in JBT/JBDS Central

by Martin Lippert (JIRA)

[ https://issues.jboss.org/browse/JBDS-2686?page=com.atlassian.jira.plugin.... ] Martin Lippert commented on JBDS-2686: -------------------------------------- I think it is unlikely that this feature suddenly "goes away", it is such an awesome addition to the Eclipse IDE world. In case you are afraid of the update site being shut downin the future (for whatever reason), you could always fork the project on GitHub and integrate this plugin into your own build. It already uses Tycho to build, so should be easy to integrate that (in the unlikely case that the official project update site goes away). > Investigate use of SpringSource's Quick Search in JBT/JBDS Central > ------------------------------------------------------------------ > > Key: JBDS-2686 > URL: https://issues.jboss.org/browse/JBDS-2686 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, discovery, requirements, updatesite > Reporter: Nick Boldt > Fix For: 7.1.x, 8.0.x > > > @fbricon wrote: > {quote} > This looks very interesting > http://blog.springsource.org/2013/07/11/eclipse-quick-search/ > And it -apparently- doesn't depend on other spring stuff, so I > think it's a good candidate for integration in JBT/JBDS. > {quote} > Update site: > http://dist.springsource.com/release/TOOLS/eclipse-integration-commons/ -- 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] (JBTIS-170) Bump SwitchYard to 1.1.0.M2

by Rob Cernich (JIRA)

Rob Cernich created JBTIS-170: --------------------------------- Summary: Bump SwitchYard to 1.1.0.M2 Key: JBTIS-170 URL: https://issues.jboss.org/browse/JBTIS-170 Project: JBoss Tools Integration Stack Issue Type: Task Security Level: Public (Everyone can see) Reporter: Rob Cernich Assignee: Rob Cernich Fix For: 4.1.3 Bump SwitchYard version to 1.1.0.M2 -- 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-15347) Code completion for EL expression doesn't work in JEE Web Project

by Jakub Niedermertl (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15347?page=com.atlassian.jira.plugi... ] Jakub Niedermertl closed JBIDE-15347. ------------------------------------- Ok, closing. Version: 7.1.0.Alpha1 Build id: Alpha1-v20130909-0132-B378 > Code completion for EL expression doesn't work in JEE Web Project > ----------------------------------------------------------------- > > Key: JBIDE-15347 > URL: https://issues.jboss.org/browse/JBIDE-15347 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples > Affects Versions: 4.1.0.Final > Environment: JBDS 7.0.0.GA, L64 > Reporter: Jiri Peterka > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.1.1.Alpha1 > > Attachments: no-code-completion.png > > > I have no code completion while trying JBDS 7.0.0 and JEE Web Project. See steps to reproduce. This seems to be a regression because it works at least in JBDS 5. -- 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-2623) Create target platform for mirrored parts of Central / 3rd Party Extras

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2623: ----------------------------- CDW devel_ack: + (was: ?) > Create target platform for mirrored parts of Central / 3rd Party Extras > ----------------------------------------------------------------------- > > Key: JBDS-2623 > URL: https://issues.jboss.org/browse/JBDS-2623 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream > Affects Versions: 7.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.x > > > As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central. > Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files. > In future, we would: > * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org] > * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com] > * add a whole new aggregate for old + new content -- 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-2623) Create target platform for mirrored parts of Central / 3rd Party Extras

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2623: ----------------------------- CDW qa_ack: ? > Create target platform for mirrored parts of Central / 3rd Party Extras > ----------------------------------------------------------------------- > > Key: JBDS-2623 > URL: https://issues.jboss.org/browse/JBDS-2623 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream > Affects Versions: 7.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.x > > > As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central. > Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files. > In future, we would: > * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org] > * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com] > * add a whole new aggregate for old + new content -- 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-2760) openshift keyword in Eclipse Marketplace

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2760?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2760: ----------------------------- CDW devel_ack: ? > openshift keyword in Eclipse Marketplace > ---------------------------------------- > > Key: JBDS-2760 > URL: https://issues.jboss.org/browse/JBDS-2760 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Burr Sutter > > The openshift keyword search should yield results for JBoss Tools & JBoss Developer Studio > http://screencast.com/t/VEn8EdAPT8U -- 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