May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-12) JBossTools Integration Stack :: switchyard: Verify the component configuration of the initial IS tooling release.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-12?page=com.atlassian.jira.plugin.s... ] Andrej Podhradsky closed JBTIS-12. ---------------------------------- Closed as obsolete > JBossTools Integration Stack :: switchyard: Verify the component configuration of the initial IS tooling release. > ----------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-12 > URL: https://issues.jboss.org/browse/JBTIS-12 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: switchyard > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Rob Cernich > > Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target. > Also check that all of your components are compatible with the upstream components defined in the target platform. > ref: > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-11) JBossTools Integration Stack :: savara: Verify the component configuration of the initial IS tooling release

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-11?page=com.atlassian.jira.plugin.s... ] Andrej Podhradsky closed JBTIS-11. ---------------------------------- Closed as obsolete > JBossTools Integration Stack :: savara: Verify the component configuration of the initial IS tooling release > ------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-11 > URL: https://issues.jboss.org/browse/JBTIS-11 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: savara > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Gary Brown > > Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target. > Also check that all components are compatible with the upstream components defined in the target platform. > ref: > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-10) JBossTools Integration Stack :: modeshape: Verify the component configuration of the initial IS tooling release.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-10?page=com.atlassian.jira.plugin.s... ] Andrej Podhradsky closed JBTIS-10. ---------------------------------- Closed as obsolete > JBossTools Integration Stack :: modeshape: Verify the component configuration of the initial IS tooling release. > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-10 > URL: https://issues.jboss.org/browse/JBTIS-10 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: modeshape > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Dan Florian > > Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target. > Also check that all components are compatible with the upstream components defined in the target platform. > ref: > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-14) generate index page for JBTIS aggregate site, and discard extra-repos.xml

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-14?page=com.atlassian.jira.plugin.s... ] Andrej Podhradsky closed JBTIS-14. ---------------------------------- Closed as obsolete > generate index page for JBTIS aggregate site, and discard extra-repos.xml > ------------------------------------------------------------------------- > > Key: JBTIS-14 > URL: https://issues.jboss.org/browse/JBTIS-14 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, releng > Reporter: Nick Boldt > Assignee: Paul Leacu > > generate index page for JBTIS aggregate site, and discard extra-repos.xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-13) JBossTools Integration Stack :: teiid: Verify the component configuration of the initial IS tooling release.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-13?page=com.atlassian.jira.plugin.s... ] Andrej Podhradsky closed JBTIS-13. ---------------------------------- Closed as obsolete > JBossTools Integration Stack :: teiid: Verify the component configuration of the initial IS tooling release. > ------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-13 > URL: https://issues.jboss.org/browse/JBTIS-13 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: teiid > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Barry LaFond > > Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target. > Also check that all components are compatible with the upstream components defined in the target platform. > ref: > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-28) produce a JBTIS unit tests update site (aggregate or composite)

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-28?page=com.atlassian.jira.plugin.s... ] Andrej Podhradsky closed JBTIS-28. ---------------------------------- Closed as obsolete > produce a JBTIS unit tests update site (aggregate or composite) > --------------------------------------------------------------- > > Key: JBTIS-28 > URL: https://issues.jboss.org/browse/JBTIS-28 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, ESB, releng, target-platform, testing > Affects Versions: 4.0.0 > Reporter: Nick Boldt > Assignee: Andrej Podhradsky > Fix For: 4.1.3.Final > > > JBTIS-27 asks that the core and JBTIS integration tests (itests) be split into a new repo. > However, some of those itests depend on upstream tests unit tests (utests)... ESB, for example. > So, either you > * need to publish a site from which these can be resolved [1] > ** :: more jobs to maintain, but will make downstream builds resolve p2 deps faster, and facilitate doing headless automated test plugin installation w/ install-grinder or p2.director > * or you need to ensure that when building/running the itests, you point at the composite JBTIS site [2]. > ** :: requires that you produce a folder somewhere on download.jboss.org, like this one [3], and maintain that composite site... since you can't link to a folder on raw.github.com [4] > [1] http://download.jboss.org/jbosstools/updates/nightly/soatests/ > [2] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo... > [3] http://download.jboss.org/jbosstools/updates/integration/juno/integration... > [4] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo... is 404'd > Both options would work... but I suggest that building a new aggregate might be better. > If you agree, you'll want to therefore migrate the code in > https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregat... > to a folder under > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-17) Update savara to 2.1.0.Final

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-17?page=com.atlassian.jira.plugin.s... ] Andrej Podhradsky closed JBTIS-17. ---------------------------------- Closed as obsolete > Update savara to 2.1.0.Final > ---------------------------- > > Key: JBTIS-17 > URL: https://issues.jboss.org/browse/JBTIS-17 > Project: JBoss Tools Integration Stack > Issue Type: Task > Reporter: Gary Brown > Assignee: Paul Leacu > Fix For: 4.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-18) ESB requirement zest needs to move to be a base target dependency vs. uncategorized aggregate feature

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-18?page=com.atlassian.jira.plugin.s... ] Andrej Podhradsky closed JBTIS-18. ---------------------------------- Closed as obsolete > ESB requirement zest needs to move to be a base target dependency vs. uncategorized aggregate feature > ----------------------------------------------------------------------------------------------------- > > Key: JBTIS-18 > URL: https://issues.jboss.org/browse/JBTIS-18 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: ESB > Affects Versions: 4.0.0 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.0.0 > > > Hey Brian - > Currently zest appears as an uncategorized feature in the JBTIS aggregate: >  > <feature url="features/org.eclipse.zest_0.0.0.jar" id="org.eclipse.zest" version="0.0.0"/> > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ag... > It needs to move to a base target dependency: > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-21) https://github.com/pleacu/jbosstools-integration-stack/blob/master/discovery/generation/build.xml should not hard code the value of the JBT core discovery plugin jar

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-21?page=com.atlassian.jira.plugin.s... ] Andrej Podhradsky closed JBTIS-21. ---------------------------------- Closed as obsolete > https://github.com/pleacu/jbosstools-integration-stack/blob/master/discov... should not hard code the value of the JBT core discovery plugin jar > --------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-21 > URL: https://issues.jboss.org/browse/JBTIS-21 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.0.0 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.0.0 > > > https://github.com/pleacu/jbosstools-integration-stack/blob/master/discov... should not hard code the value of the JBT core discovery plugin jar > Instead, perhaps you could fetch the latest jbosstools-directory.xml file, parse the contents from xml to ant variables [1], then write that back out into a new file. > That way when we move up to JBT 4.0.1 (or ever change the Central plugin out of band) you'll get the correct version. > [1] http://ant.apache.org/manual/Tasks/xmlproperty.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-16) Update Eclipse Target Platform to use Graphiti 0.9

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-16?page=com.atlassian.jira.plugin.s... ] Andrej Podhradsky closed JBTIS-16. ---------------------------------- Closed as obsolete > Update Eclipse Target Platform to use Graphiti 0.9 > -------------------------------------------------- > > Key: JBTIS-16 > URL: https://issues.jboss.org/browse/JBTIS-16 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: target-platform > Reporter: Rob Cernich > Assignee: Rob Cernich > Priority: Critical > > SwitchYard loosely integrates with the Eclipse BPMN2 editor, which has recently upgraded to Graphiti 0.9. Because of this, SwitchYard could not be installed alongside the BPMN2, so SwitchYard needed to upgrade to Graphiti 0.9. This has caused the soa-tools 3.3.x aggregate build to fail because it cannot locate the Graphiti 0.9 plugins. > If SwitchYard is the only project relying on Graphiti, we can simply upgrade the target platforms for Indigo and Juno to include Graphiti 0.9. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 May 2016