September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15587) Convert downloadRuntime wizard to use WizardFragments in foundation

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15587?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-15587. --------------------------------- Resolution: Done This was pushed with the following commit: https://github.com/jbosstools/jbosstools-base/commit/f39421537a3520afa3e5... If you look closely, you'll see the large majority of the patch was moving 50% of one class out into a utility class and small changes for clarity. Other than that, all changes are very small and obvious when converting a wizard page to a wizard fragment. > Convert downloadRuntime wizard to use WizardFragments in foundation > ------------------------------------------------------------------- > > Key: JBIDE-15587 > URL: https://issues.jboss.org/browse/JBIDE-15587 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > Convert the download runtimes wizard to use the wizard fragment framework to allow for easier implementation of the ToC pages in the future. Very versatile framework. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15591) Stacks in Master should be version 1.1.0

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15591?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-15591. --------------------------------- Resolution: Done Pushed to master. Simple version change. > Stacks in Master should be version 1.1.0 > ---------------------------------------- > > Key: JBIDE-15591 > URL: https://issues.jboss.org/browse/JBIDE-15591 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > Self-explanatory title. Version was not bumped for master yet. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15591) Stacks in Master should be version 1.1.0

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-15591: ----------------------------------- Summary: Stacks in Master should be version 1.1.0 Key: JBIDE-15591 URL: https://issues.jboss.org/browse/JBIDE-15591 Project: Tools (JBoss Tools) Issue Type: Task Components: common/jst/core Affects Versions: 4.2.0.Alpha1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.2.0.Alpha1 Self-explanatory title. Version was not bumped for master yet. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15590) Central should avoid using internal apis inside runtime

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-15590: ----------------------------------- Summary: Central should avoid using internal apis inside runtime Key: JBIDE-15590 URL: https://issues.jboss.org/browse/JBIDE-15590 Project: Tools (JBoss Tools) Issue Type: Task Components: central Affects Versions: 4.2.0.Alpha1 Reporter: Rob Stryker Assignee: Fred Bricon Fix For: 4.2.0.Alpha1 Eventually, internal packages inside runtimes will be just that... internal. They will not be exposed. Central should ensure no internal code is being referenced. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15561) Aerogear New and Noteworthy for 4.1.1.Alpha2

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15561?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-15561. ----------------------------------- Resolution: Rejected Rejected, because no changes expected in 4.1.1.Alpha1 as it stated here JBIDE-15528. > Aerogear New and Noteworthy for 4.1.1.Alpha2 > -------------------------------------------- > > Key: JBIDE-15561 > URL: https://issues.jboss.org/browse/JBIDE-15561 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Reporter: Denis Golovin > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.1.1.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Aerogear is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Aerogear by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15561) Aerogear New and Noteworthy for 4.1.1.Alpha2

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15561?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-15561. --------------------------------- > Aerogear New and Noteworthy for 4.1.1.Alpha2 > -------------------------------------------- > > Key: JBIDE-15561 > URL: https://issues.jboss.org/browse/JBIDE-15561 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Reporter: Denis Golovin > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.1.1.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Aerogear is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Aerogear by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13647) Support Cordova Plugins

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13647?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13647: ---------------------------------- Release Notes Text: Moving this one to next 4.1.1.Beta1 because no changes are expected as it stated here JBIDE-15528 Fix Version/s: 4.1.1.Beta1 (was: 4.1.1.Alpha2) > Support Cordova Plugins > ----------------------- > > Key: JBIDE-13647 > URL: https://issues.jboss.org/browse/JBIDE-13647 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 4.1.1.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > At a minimum tools should be able to build plugins for the supported target platforms. However complete support will be the retrieval and discovery of plugins. > At the moment there is no central repository of Cordova plugins. However cordova-cli project is working to create one. We should try to create a compatible solution. -- 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, 6 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 edited comment on JBDS-2623 at 9/30/13 12:09 PM: ------------------------------------------------------------ Fixed by adding org.aspectj.runtime_1.7.3.20130613144500-a.jar to resolve package org.aspectj.lang.annotation. Pushed to 4.1.x & 4.1.1.Alpha2x branches (4.31.0.Alpha1-SNAPSHOT TP) and master (4.40.0.Alpha1-SNAPSHOT TP). Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... >=8 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... >=7 was (Author: nickboldt): Fixed by adding org.aspectj.runtime_1.7.3.20130613144500-a.jar to resolve package org.aspectj.lang.annotation. Pushed to 4.1.x branch (4.31.0.Alpha1-SNAPSHOT TP) and master (4.40.0.Alpha1-SNAPSHOT TP). Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... >=7 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... >=7 > 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.0.Alpha2, 7.1.0.Beta1 > > Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png > > > 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, 6 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 commented on JBDS-2623: ---------------------------------- Fixed by adding org.aspectj.runtime_1.7.3.20130613144500-a.jar to resolve package org.aspectj.lang.annotation. Pushed to 4.1.x branch (4.31.0.Alpha1-SNAPSHOT TP) and master (4.40.0.Alpha1-SNAPSHOT TP). Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... >=7 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... >=7 > 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.0.Alpha2, 7.1.0.Beta1 > > Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png > > > 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, 6 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 commented on JBDS-2623: ---------------------------------- Install grinder is not happy - missing IU in the new Central TP 4.40.0.Alpha1 site [1]: {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-install-grinder.install-tests.matrix_master/INSTALL_PLAN=http%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2F%3Bhttp%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2Fjbosstools-directory.xml,eclipseBundleVersion=kepler.R,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/1317/console} Contains: Missing requirement: Spring IDE Spring Meta Data Extension 3.3.0.201307091516-RELEASE (org.springframework.ide.eclipse.metadata 3.3.0.201307091516-RELEASE) requires 'package org.aspectj.lang.annotation 0.0.0' but it could not be found {code} [1] http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.4... > 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.0.Alpha2, 7.1.0.Beta1 > > Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png > > > 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, 6 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