August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2742) Create target platform from Kepler SR1 (RC) dependencies

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2742?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2742: ----------------------------- CDW release: - (was: ?) > Create target platform from Kepler SR1 (RC) dependencies > -------------------------------------------------------- > > Key: JBDS-2742 > URL: https://issues.jboss.org/browse/JBDS-2742 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Mickael Istria > > Based on the posted schedule [1] the first RC1 of Kepler SR1 will be available tomorrow. So, we should start mirroring those updated bits and produce a new target platform with which to build JBT 4.1.1 / JBDS 7.1.0. > [1] http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan#SR1 > There may be other 3rd party features we can also update as part of this release. See JBDS-2710 to track those items. > For example, we might want to consider including Spring's QuickSearch ( JBDS-2686 ) in JBT/JBDS. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2742) Create target platform from Kepler SR1 (RC) dependencies

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2742?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2742: ----------------------------- CDW pm_ack: (was: ?) CDW release: (was: -) > Create target platform from Kepler SR1 (RC) dependencies > -------------------------------------------------------- > > Key: JBDS-2742 > URL: https://issues.jboss.org/browse/JBDS-2742 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Mickael Istria > > Based on the posted schedule [1] the first RC1 of Kepler SR1 will be available tomorrow. So, we should start mirroring those updated bits and produce a new target platform with which to build JBT 4.1.1 / JBDS 7.1.0. > [1] http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan#SR1 > There may be other 3rd party features we can also update as part of this release. See JBDS-2710 to track those items. > For example, we might want to consider including Spring's QuickSearch ( JBDS-2686 ) in JBT/JBDS. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2742) Create target platform from Kepler SR1 (RC) dependencies

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2742?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2742: ----------------------------- Target Release: (was: 7.1.0.GA) > Create target platform from Kepler SR1 (RC) dependencies > -------------------------------------------------------- > > Key: JBDS-2742 > URL: https://issues.jboss.org/browse/JBDS-2742 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Mickael Istria > > Based on the posted schedule [1] the first RC1 of Kepler SR1 will be available tomorrow. So, we should start mirroring those updated bits and produce a new target platform with which to build JBT 4.1.1 / JBDS 7.1.0. > [1] http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan#SR1 > There may be other 3rd party features we can also update as part of this release. See JBDS-2710 to track those items. > For example, we might want to consider including Spring's QuickSearch ( JBDS-2686 ) in JBT/JBDS. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2709) Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2709?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2709: ---------------------------------- As of Aug 29, latest Svnkit is still 1.8.0 Alpha (Jul 16 2013). > Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central > ---------------------------------------------------------- > > Key: JBDS-2709 > URL: https://issues.jboss.org/browse/JBDS-2709 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, Central, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > > As reported here: > https://issues.jboss.org/browse/JBDS-2485?focusedCommentId=12791354&page=... > {quote} > Subclipse 1.10 has support for the new 1.8 working copy format, which is the format used by the current stable versions of Windows tools like TortoiseSVN and SlikSVN. > http://subclipse.tigris.org/update_1.10.x > Local repository compatibility between these tools and JBDS is very nice to have. > Unfortunately, this version of SubClipse supports only JavaHL, not SVNKit, because version 1.8.0 of the latter is still in alpha. And since we can't reliably use JavaHL (see JBIDE-14795), using 1.8.0 is out of the question. > {quote} > http://www.svnkit.com/download.php > Once there's a more stable version of SVNKit 1.8 that works with Subclipse 1.10, we can explore updating Central to include the newer version. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2710) 3rd party certification for JBDS 7.1.0.GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2710?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2710: ----------------------------- Summary: 3rd party certification for JBDS 7.1.0.GA (was: 3rd party certification for JBDS 7.0.x/7.1.x/8.0.x (next release TBD)) > 3rd party certification for JBDS 7.1.0.GA > ----------------------------------------- > > Key: JBDS-2710 > URL: https://issues.jboss.org/browse/JBDS-2710 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements > Affects Versions: 7.0.0.GA > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Priority: Blocker > Labels: respin-a > > For JBDS 7, we need to ensure this list is as current and up to date as possible. > The current list of Extras/Central connectors that we mirror are: > * atlassian/3.2.1.v20130402 - JBIDE-13682 > * gwt/3.2.3.v201304260926-rel-r42/ - JBDS-2486 > * pmd/4.0.0.v20130510-1000 - JBIDE-14902 > * SpringSource's Quick Search - JBDS-2686 *TBD* > * springide/3.3.0.201307091516-RELEASE - JBDS-2690¥, JBDS-2691¥ > * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709 > * testng/6.8.1.20130330_0839/ - JBDS-2415 > * VJET 0.10 - JBIDE-14764 > These are currently unchanged since December when we released JBDS 6.0.0: > * *[REMOVED]* eclipsecs/5.6.0.201209221626 - no new releases as of 2013.06.27, only some 5.6.1 milestones, so [~maxandersen] has requested we remove this from Central (JBIDE-14799). > * findbugs/2.0.2.20121210 - nothing new as of 2013.06.21 > Additionally (Target Platform): > * swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests) > JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only): > * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3]) > * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3]) > See comments below for latest site URLs. > [1] https://github.com/jbosstools/jbosstools-locus/ > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit... > [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/ > ¥ - These issues do not block the release of JBDS 7.0.1.GA. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2710) 3rd party certification for JBDS 7.1.0.GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2710?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2710: ----------------------------- Description: For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible. The current list of Extras/Central connectors that we mirror are: * atlassian/3.2.1.v20130402 - JBIDE-13682 * gwt/3.2.3.v201304260926-rel-r42/ - JBDS-2486 * pmd/4.0.0.v20130510-1000 - JBIDE-14902 * SpringSource's Quick Search - JBDS-2686 *TBD* * springide/3.3.0.201307091516-RELEASE - JBDS-2690¥, JBDS-2691¥ * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709 * testng/6.8.1.20130330_0839/ - JBDS-2415 * VJET 0.10 - JBIDE-14764 These are currently unchanged since December when we released JBDS 6.0.0: * *[REMOVED]* eclipsecs/5.6.0.201209221626 - no new releases as of 2013.06.27, only some 5.6.1 milestones, so [~maxandersen] has requested we remove this from Central (JBIDE-14799). * findbugs/2.0.2.20121210 - nothing new as of 2013.06.21 Additionally (Target Platform): * swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests) JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only): * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3]) * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3]) See comments below for latest site URLs. [1] https://github.com/jbosstools/jbosstools-locus/ [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit... [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/ ¥ - These issues do not block the release of JBDS 7.0.1.GA. was: For JBDS 7, we need to ensure this list is as current and up to date as possible. The current list of Extras/Central connectors that we mirror are: * atlassian/3.2.1.v20130402 - JBIDE-13682 * gwt/3.2.3.v201304260926-rel-r42/ - JBDS-2486 * pmd/4.0.0.v20130510-1000 - JBIDE-14902 * SpringSource's Quick Search - JBDS-2686 *TBD* * springide/3.3.0.201307091516-RELEASE - JBDS-2690¥, JBDS-2691¥ * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709 * testng/6.8.1.20130330_0839/ - JBDS-2415 * VJET 0.10 - JBIDE-14764 These are currently unchanged since December when we released JBDS 6.0.0: * *[REMOVED]* eclipsecs/5.6.0.201209221626 - no new releases as of 2013.06.27, only some 5.6.1 milestones, so [~maxandersen] has requested we remove this from Central (JBIDE-14799). * findbugs/2.0.2.20121210 - nothing new as of 2013.06.21 Additionally (Target Platform): * swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests) JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only): * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3]) * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3]) See comments below for latest site URLs. [1] https://github.com/jbosstools/jbosstools-locus/ [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit... [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/ ¥ - These issues do not block the release of JBDS 7.0.1.GA. > 3rd party certification for JBDS 7.1.0.GA > ----------------------------------------- > > Key: JBDS-2710 > URL: https://issues.jboss.org/browse/JBDS-2710 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements > Affects Versions: 7.0.0.GA > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Priority: Blocker > Labels: respin-a > > For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible. > The current list of Extras/Central connectors that we mirror are: > * atlassian/3.2.1.v20130402 - JBIDE-13682 > * gwt/3.2.3.v201304260926-rel-r42/ - JBDS-2486 > * pmd/4.0.0.v20130510-1000 - JBIDE-14902 > * SpringSource's Quick Search - JBDS-2686 *TBD* > * springide/3.3.0.201307091516-RELEASE - JBDS-2690¥, JBDS-2691¥ > * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709 > * testng/6.8.1.20130330_0839/ - JBDS-2415 > * VJET 0.10 - JBIDE-14764 > These are currently unchanged since December when we released JBDS 6.0.0: > * *[REMOVED]* eclipsecs/5.6.0.201209221626 - no new releases as of 2013.06.27, only some 5.6.1 milestones, so [~maxandersen] has requested we remove this from Central (JBIDE-14799). > * findbugs/2.0.2.20121210 - nothing new as of 2013.06.21 > Additionally (Target Platform): > * swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests) > JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only): > * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3]) > * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3]) > See comments below for latest site URLs. > [1] https://github.com/jbosstools/jbosstools-locus/ > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit... > [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/ > ¥ - These issues do not block the release of JBDS 7.0.1.GA. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2743) Latest target platform for a given eclipse stream should be a composite site under /targetplatforms/<project>/<eclipse-version> not /updates/<eclipse-version>/<project>/

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2743?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2743: ----------------------------- CDW pm_ack: ? > Latest target platform for a given eclipse stream should be a composite site under /targetplatforms/<project>/<eclipse-version> not /updates/<eclipse-version>/<project>/ > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2743 > URL: https://issues.jboss.org/browse/JBDS-2743 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Nick Boldt > > Traditionally, we have hosted the update site w/ the dependencies needed to install JBT here: > http://download.jboss.org/jbosstools/updates/indigo/ (composites) > http://download.jboss.org/jbosstools/updates/indigo/soa-tooling/ (composites) > http://download.jboss.org/jbosstools/updates/juno/ (target platform) > http://download.jboss.org/jbosstools/updates/juno/integration-stack/ (composites) > http://download.jboss.org/jbosstools/updates/kepler/ (target platform) > http://download.jboss.org/jbosstools/updates/kepler/integration-stack (target platform) > Now that we have all the target platforms in one place, under http://download.jboss.org/jbosstools/targetplatforms/ I think it would make sense to change "the latest TP" composite under /updates/<eclipse version>/ to instead exist under > /targetplatforms/<project>/<eclipse-version> > eg., > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/kep... > or > http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/kepler/ > That way all the TPs live under /targetplatforms/ and all the update sites live under /updates/ and never the twain shall meet. > Thoughts? -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2743) Latest target platform for a given eclipse stream should be a composite site under /targetplatforms/<project>/<eclipse-version> not /updates/<eclipse-version>/<project>/

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2743?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2743: ----------------------------- CDW release: ? Status: New (was: New) Target Release: 7.1.0.GA > Latest target platform for a given eclipse stream should be a composite site under /targetplatforms/<project>/<eclipse-version> not /updates/<eclipse-version>/<project>/ > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2743 > URL: https://issues.jboss.org/browse/JBDS-2743 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Nick Boldt > > Traditionally, we have hosted the update site w/ the dependencies needed to install JBT here: > http://download.jboss.org/jbosstools/updates/indigo/ (composites) > http://download.jboss.org/jbosstools/updates/indigo/soa-tooling/ (composites) > http://download.jboss.org/jbosstools/updates/juno/ (target platform) > http://download.jboss.org/jbosstools/updates/juno/integration-stack/ (composites) > http://download.jboss.org/jbosstools/updates/kepler/ (target platform) > http://download.jboss.org/jbosstools/updates/kepler/integration-stack (target platform) > Now that we have all the target platforms in one place, under http://download.jboss.org/jbosstools/targetplatforms/ I think it would make sense to change "the latest TP" composite under /updates/<eclipse version>/ to instead exist under > /targetplatforms/<project>/<eclipse-version> > eg., > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/kep... > or > http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/kepler/ > That way all the TPs live under /targetplatforms/ and all the update sites live under /updates/ and never the twain shall meet. > Thoughts? -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-129) Create SY bot test from existing BPM process

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-129?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-129: ------------------------------------ Summary: Create SY bot test from existing BPM process (was: Create SY bot test from existing jBPM5) > Create SY bot test from existing BPM process > -------------------------------------------- > > Key: JBTIS-129 > URL: https://issues.jboss.org/browse/JBTIS-129 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.1.0.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.1.2 > > -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-161) Should the JBTIS 4.1 target platform include SpringIDE 3.3 instead of 3.2?

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-161?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-161: ---------------------------------- [~lhein] : Our used Camel version has a set version range for springframework bundles so it does only pick up version 3.x of the springframework jars. The Spring IDE 3.3 uses 4.0 M1 of the springframework so I don't see how we can align here. Its better to test Spring IDE with Fuse Tooling as is and the do a bug report if there is an issue. > Should the JBTIS 4.1 target platform include SpringIDE 3.3 instead of 3.2? > -------------------------------------------------------------------------- > > Key: JBTIS-161 > URL: https://issues.jboss.org/browse/JBTIS-161 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.2 > Reporter: Nick Boldt > > The version of SpringIDE vetted by QE to be included in JBDS 7 Central is Spring IDE 3.3 [1]. > [1] http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0... > However, as reported in http://fusesource.com/issues/browse/ECLIPSE-955 Fuse currently depends on Spring IDE 3.2 [2] > [2] https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... > This disconnect may cause problems when co-installing SpringIDE 3.3 from JBDS Central and Fuse (which will bring in SpringIDE 3.2 jars). > Therefore, should Central, JBTIS TP 4.1, and Fuse all use the same version of Spring IDE, namely 3.3 instead of 3.2 and 3.3? -- 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2013