June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2416) label Central connectors that are sourced from 3rd party sites (rather than our mirrors) as being External and provide detailed description/notice of ownership

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2416?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2416: -------------------------------------- Priority: Blocker (was: Major) > label Central connectors that are sourced from 3rd party sites (rather than our mirrors) as being External and provide detailed description/notice of ownership > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2416 > URL: https://issues.jboss.org/browse/JBDS-2416 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 6.0.0.GA > Reporter: Nick Boldt > Assignee: Burr Sutter > Priority: Blocker > Labels: f2f2012 > Fix For: 7.0.0.Beta2 > > > We currently use "Supported" to define JBoss-built/maintained content in Central, and "Tested" for 3rd party stuff we mirror and try to keep up to date. > However, for content that changes frequently (Android Tooling) or for which we do not have license to redistribute (JRebel), we need to link directly to a vendor's site and simply hope for the best. > But, to make it clear this is the case, we should in JBDS provide a note about this using a some term such as: > * External > * Other > * 3rdParty > and then provide a tooltip which reads: > {quote}This content, while compatible with JBoss Developer Studio at the time of release, comes directly from another vendor's site and is subject to change without notice.{quote} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2416) label Central connectors that are sourced from 3rd party sites (rather than our mirrors) as being External and provide detailed description/notice of ownership

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2416?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2416: -------------------------------------- Fix Version/s: 7.0.0.Beta2 (was: 7.0.0.Beta1) > label Central connectors that are sourced from 3rd party sites (rather than our mirrors) as being External and provide detailed description/notice of ownership > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2416 > URL: https://issues.jboss.org/browse/JBDS-2416 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 6.0.0.GA > Reporter: Nick Boldt > Assignee: Burr Sutter > Labels: f2f2012 > Fix For: 7.0.0.Beta2 > > > We currently use "Supported" to define JBoss-built/maintained content in Central, and "Tested" for 3rd party stuff we mirror and try to keep up to date. > However, for content that changes frequently (Android Tooling) or for which we do not have license to redistribute (JRebel), we need to link directly to a vendor's site and simply hope for the best. > But, to make it clear this is the case, we should in JBDS provide a note about this using a some term such as: > * External > * Other > * 3rdParty > and then provide a tooltip which reads: > {quote}This content, while compatible with JBoss Developer Studio at the time of release, comes directly from another vendor's site and is subject to change without notice.{quote} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2486) Investigate use of GWT/GPE 3.2 in Central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2486?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2486: -------------------------------------- Assignee: Denis Golovin (was: Vlado Pakan) > Investigate use of GWT/GPE 3.2 in Central > ----------------------------------------- > > Key: JBDS-2486 > URL: https://issues.jboss.org/browse/JBDS-2486 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 7.0.0.Beta2 > > > New 3.2.0 mirrors: > http://download.jboss.org/jbosstools/updates/requirements/gwt/3.2.0.v2013... > https://devstudio.jboss.com/updates/requirements/gwt/3.2.0.v201302131858-... > New composites: > http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.1/ > https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.1/ > Note that at least one IU had been renamed: > OLD: com.google.gwt.eclipse.sdkbundle.e42.feature > NEW: com.google.gwt.eclipse.sdkbundle.feature -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2486) Investigate use of GWT/GPE 3.2 in Central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2486?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2486: -------------------------------------- Fix Version/s: 7.0.0.Beta2 (was: 7.0.0.Beta1) > Investigate use of GWT/GPE 3.2 in Central > ----------------------------------------- > > Key: JBDS-2486 > URL: https://issues.jboss.org/browse/JBDS-2486 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Vlado Pakan > Fix For: 7.0.0.Beta2 > > > New 3.2.0 mirrors: > http://download.jboss.org/jbosstools/updates/requirements/gwt/3.2.0.v2013... > https://devstudio.jboss.com/updates/requirements/gwt/3.2.0.v201302131858-... > New composites: > http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.1/ > https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.1/ > Note that at least one IU had been renamed: > OLD: com.google.gwt.eclipse.sdkbundle.e42.feature > NEW: com.google.gwt.eclipse.sdkbundle.feature -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2511) Link "Product documentation" leads to JBT 3.3.0 documentation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2511?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2511: -------------------------------------- Fix Version/s: 7.0.0.Beta2 (was: 7.0.0.Beta1) > Link "Product documentation" leads to JBT 3.3.0 documentation > ------------------------------------------------------------- > > Key: JBDS-2511 > URL: https://issues.jboss.org/browse/JBDS-2511 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 7.0.0.Alpha2 > Reporter: Radim Hopp > Assignee: Fred Bricon > Fix For: 7.0.0.Beta2 > > > Please update link "Product Documentation". Now it's pointing to JBT 3.3.0 doc. > Maybe could be good to distinguish JBT and JBDS. > For JBT update link to for example http://www.jboss.org/tools/docs/reference > And for JBDS to https://access.redhat.com/site/documentation/JBoss_Developer_Studio/ > Another possible solution is to open DOC jira to update http://docs.jboss.org/tools/latest/, but I think it would be good if JBT and JBDS could point to different doc pages. > WDYT? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2499) Not able to resize the preferences window in JDBS 6

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2499?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2499: -------------------------------------- Fix Version/s: 7.0.0.Beta2 (was: 7.0.0.Beta1) > Not able to resize the preferences window in JDBS 6 > --------------------------------------------------- > > Key: JBDS-2499 > URL: https://issues.jboss.org/browse/JBDS-2499 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Upstream > Affects Versions: 6.0.0.GA > Environment: Fedora 17 > jdbs 6.0.0.GA, build id: GA-v20121206-1855-B186, build date: 20121206-1855 > Reporter: Sande Gilda > Fix For: 7.0.0.Beta2 > > Attachments: JDBS6-01.png, JDBS6-02.png, JDBS6-03.png, JDBS6-04.png > > > To recreate: > Start JDBS. > Choose menu: Window --> Preferences > Grab a side edge to drag it wider, but it snaps down to a narrow vertical bar. > When I hover over the edges, I get the arrow resize icon, but I can't resize it. > At this point, I have to kill the 2 processes: one jbdevstudio and one java (for jbds and the popup window. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2499) Not able to resize the preferences window in JDBS 6

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2499?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2499: -------------------------------------- Assignee: Denis Golovin > Not able to resize the preferences window in JDBS 6 > --------------------------------------------------- > > Key: JBDS-2499 > URL: https://issues.jboss.org/browse/JBDS-2499 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Upstream > Affects Versions: 6.0.0.GA > Environment: Fedora 17 > jdbs 6.0.0.GA, build id: GA-v20121206-1855-B186, build date: 20121206-1855 > Reporter: Sande Gilda > Assignee: Denis Golovin > Fix For: 7.0.0.Beta2 > > Attachments: JDBS6-01.png, JDBS6-02.png, JDBS6-03.png, JDBS6-04.png > > > To recreate: > Start JDBS. > Choose menu: Window --> Preferences > Grab a side edge to drag it wider, but it snaps down to a narrow vertical bar. > When I hover over the edges, I get the arrow resize icon, but I can't resize it. > At this point, I have to kill the 2 processes: one jbdevstudio and one java (for jbds and the popup window. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2511) Link "Product documentation" leads to JBT 3.3.0 documentation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2511?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2511: -------------------------------------- Assignee: Fred Bricon (was: Snjezana Peco) > Link "Product documentation" leads to JBT 3.3.0 documentation > ------------------------------------------------------------- > > Key: JBDS-2511 > URL: https://issues.jboss.org/browse/JBDS-2511 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 7.0.0.Alpha2 > Reporter: Radim Hopp > Assignee: Fred Bricon > Fix For: 7.0.0.Beta1 > > > Please update link "Product Documentation". Now it's pointing to JBT 3.3.0 doc. > Maybe could be good to distinguish JBT and JBDS. > For JBT update link to for example http://www.jboss.org/tools/docs/reference > And for JBDS to https://access.redhat.com/site/documentation/JBoss_Developer_Studio/ > Another possible solution is to open DOC jira to update http://docs.jboss.org/tools/latest/, but I think it would be good if JBT and JBDS could point to different doc pages. > WDYT? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2623: -------------------------------------- Fix Version/s: 7.0.0.Beta2 (was: 7.0.0.Beta1) > 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: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central, updatesite, Upstream > Affects Versions: 7.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.Beta2 > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2623: ------------------------------------------- assumed not done for beta1 punting to beta2. > 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: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central, updatesite, Upstream > Affects Versions: 7.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.Beta2 > > > 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, 10 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 June 2013