August 2013 - jbosstools-issues - Jboss List Archives

[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

12 years, 11 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

12 years, 11 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

12 years, 11 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2722) Include Kepler SR1 by default

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2722?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2722: ----------------------------- CDW devel_ack: + (was: ?) > Include Kepler SR1 by default > ------------------------------ > > Key: JBDS-2722 > URL: https://issues.jboss.org/browse/JBDS-2722 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > > Kepler SR1 has bugfixes - we should include it in upcoming release. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2722) Include Kepler SR1 by default

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2722?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2722: ----------------------------- CDW qa_ack: ? > Include Kepler SR1 by default > ------------------------------ > > Key: JBDS-2722 > URL: https://issues.jboss.org/browse/JBDS-2722 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > > Kepler SR1 has bugfixes - we should include it in upcoming release. -- 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, 11 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: ? > 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

12 years, 11 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: ----------------------------- CDW release: ? Status: New (was: New) Target Release: 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

12 years, 11 months

1
0
0 / 0

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

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-129?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-129: ------------------------------------ Fix Version/s: 4.1.2 > Create SY bot test from existing jBPM5 > -------------------------------------- > > 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2722) Include Kepler SR1 by default

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2722?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-2722: -------------------------------- Assignee: Nick Boldt > Include Kepler SR1 by default > ------------------------------ > > Key: JBDS-2722 > URL: https://issues.jboss.org/browse/JBDS-2722 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > > Kepler SR1 has bugfixes - we should include it in upcoming release. -- 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, 11 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 August 2013