December 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-3241) Camel Routes Are Not Being Rendered

by Joe Fernandez (JIRA)

Joe Fernandez created JBDS-3241: ----------------------------------- Summary: Camel Routes Are Not Being Rendered Key: JBDS-3241 URL: https://issues.jboss.org/browse/JBDS-3241 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: integration-platform Affects Versions: 7.1.1.GA Reporter: Joe Fernandez If you open an XML file with multiple Camel routes defined, only the first route is rendered in "Design" view/mode. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-350) Missing BPEL source plugins

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-350?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-350: ---------------------------------- Hey Bob - Ya - we've got tp bang this one out. It's a big company that's looking for it and if we have to start backpeddling on why bpel doesn't have sources... I appreciate any help you can give here. --Paul > Missing BPEL source plugins > --------------------------- > > Key: JBTIS-350 > URL: https://issues.jboss.org/browse/JBTIS-350 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.Beta1 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > > After installing all components included in Beta1 there are only the following souce plugins for BPEL > org.jboss.tools.bpel.runtimes.source_1.2.101.Final-v20140108-1353-B1045.jar > org.switchyard.tools.ui.bpel.source_2.0.0.v20141011-0508-H499-Alpha3.jar > but there are much more BPEL plugins such as > org.eclipse.bpel.ui, org.eclipse.bpel.ui.validator -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3241) Camel Routes Are Not Being Rendered

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3241?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3241: ----------------------------- CDW docs_ack: ? CDW devel_ack: ? CDW pm_ack: + CDW qa_ack: ? CDW release: ? Target Release: 8.0.1.GA > Camel Routes Are Not Being Rendered > ----------------------------------- > > Key: JBDS-3241 > URL: https://issues.jboss.org/browse/JBDS-3241 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: integration-platform > Affects Versions: 7.1.1.GA > Reporter: Joe Fernandez > > If you open an XML file with multiple Camel routes defined, only the first route is rendered in "Design" view/mode. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-350) Missing BPEL source plugins

by Robert (Bob) Brodt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-350?page=com.atlassian.jira.plugin.... ] Robert (Bob) Brodt commented on JBTIS-350: ------------------------------------------ Hi Paul, Is this a big priority? I'm hoping to push this off 'til later cuz we're kinda in bugfix mode right now for jBPM... Bob > Missing BPEL source plugins > --------------------------- > > Key: JBTIS-350 > URL: https://issues.jboss.org/browse/JBTIS-350 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.Beta1 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > > After installing all components included in Beta1 there are only the following souce plugins for BPEL > org.jboss.tools.bpel.runtimes.source_1.2.101.Final-v20140108-1353-B1045.jar > org.switchyard.tools.ui.bpel.source_2.0.0.v20141011-0508-H499-Alpha3.jar > but there are much more BPEL plugins such as > org.eclipse.bpel.ui, org.eclipse.bpel.ui.validator -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18844) Fix min table size for platformList

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18844?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-18844: ------------------------------- Summary: Fix min table size for platformList (was: Make table with platforms bigger) > Fix min table size for platformList > ----------------------------------- > > Key: JBIDE-18844 > URL: https://issues.jboss.org/browse/JBIDE-18844 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid > Affects Versions: 4.2.1.CR1 > Reporter: Pavol Srna > Assignee: Pavol Srna > Attachments: hybrid-tooling.png > > > Table with platforms is too small. Please see attached screenshot. > On mac the ios platform is hidden and user needs to scroll. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18844) Make table with platforms bigger

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18844?page=com.atlassian.jira.plugi... ] Pavol Srna reassigned JBIDE-18844: ---------------------------------- Assignee: Pavol Srna > Make table with platforms bigger > -------------------------------- > > Key: JBIDE-18844 > URL: https://issues.jboss.org/browse/JBIDE-18844 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid > Affects Versions: 4.2.1.CR1 > Reporter: Pavol Srna > Assignee: Pavol Srna > Attachments: hybrid-tooling.png > > > Table with platforms is too small. Please see attached screenshot. > On mac the ios platform is hidden and user needs to scroll. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-355) Enable JBDSIS Marketplace entry or entries for product groupings - Luna

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-355?page=com.atlassian.jira.plugin.... ] Paul Leacu edited comment on JBTIS-355 at 12/2/14 1:09 PM: ----------------------------------------------------------- Note - just to log Alan's original idea for Eclipse Marketplace entries: * JBoss Business Process and Rules Development * JBoss Data Virtualization Development * JBoss Fuse Development * JBoss SOA 5.x Development * JBoss Switchyard Development (pulls in BPEL) Note that the existing 'JBoss Integration and SOA Development' goes away7. was (Author: pleacu): Note - just to log Alan's original idea for Eclipse Marketplace entries: * JBoss Business Process and Rules Development * JBoss Data Virtualization Development * JBoss Fuse Development * JBoss SOA 5.x Development * JBoss Switchyard Development (pulls in BPEL) > Enable JBDSIS Marketplace entry or entries for product groupings - Luna > ----------------------------------------------------------------------- > > Key: JBTIS-355 > URL: https://issues.jboss.org/browse/JBTIS-355 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.0.GA > Reporter: Paul Leacu > Assignee: Nick Boldt > Attachments: jbtis355.png > > > * In JBDS 8.1, add a new com.jboss.devstudio.core.central.feature that packages up com.jboss.devstudio.core.central plugin - JBDS-3210 > ** include this in com.jboss.devstudio.core.feature instead of the plugin? > * enable usage tracking in JBT IS components' MANIFST.MF files - JBTIS-290 > * create four connectors, each based on the content in JBDS IS disco plugin.xml's top four BIG connectors; include com.jboss.devstudio.core.CENTRAL.feature in order to install Central along for the ride - JBTIS-358 > (For JBDS 9, we will look at making the Central feature much smaller so the footprint is significantly smaller - see JBIDE-18734.) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-355) Enable JBDSIS Marketplace entry or entries for product groupings - Luna

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-355?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-355: ---------------------------------- Note - just to log Alan's original idea for Eclipse Marketplace entries: * JBoss Business Process and Rules Development * JBoss Data Virtualization Development * JBoss Fuse Development * JBoss SOA 5.x Development * JBoss Switchyard Development (pulls in BPEL) > Enable JBDSIS Marketplace entry or entries for product groupings - Luna > ----------------------------------------------------------------------- > > Key: JBTIS-355 > URL: https://issues.jboss.org/browse/JBTIS-355 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.0.GA > Reporter: Paul Leacu > Assignee: Nick Boldt > Attachments: jbtis355.png > > > * In JBDS 8.1, add a new com.jboss.devstudio.core.central.feature that packages up com.jboss.devstudio.core.central plugin - JBDS-3210 > ** include this in com.jboss.devstudio.core.feature instead of the plugin? > * enable usage tracking in JBT IS components' MANIFST.MF files - JBTIS-290 > * create four connectors, each based on the content in JBDS IS disco plugin.xml's top four BIG connectors; include com.jboss.devstudio.core.CENTRAL.feature in order to install Central along for the ride - JBTIS-358 > (For JBDS 9, we will look at making the Central feature much smaller so the footprint is significantly smaller - see JBIDE-18734.) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18837: ------------------------------- Attachment: generated-vs-soource-zip.png If you build the o.j.t.foundation.core plugin, as I did here passing in -DBUILD_ALIAS=foo, you will see in the currentversion.properties that the variables are correctly expanded. !generated-vs-soource-zip.png! This also works in the devstudio.core plugin, which ALSO depends on its root pom + BUILD_ALIAS for the correct version. > because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18837 > URL: https://issues.jboss.org/browse/JBIDE-18837 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, central, common/jst/core, project-examples > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Fix For: 4.3.0.Alpha1 > > Attachments: generated-vs-soource-zip.png > > > When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples. > Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating. > And we need to use the maven enforcer plugin to fail the build if these versions get out of sync. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3208 at 12/2/14 12:56 PM: ------------------------------------------------------------ Rationale for having updates/9.0/ be a composite site pointer to updates/9.0/stable/ (and similar for updates/mars/ == updates/mars/stable/ ) is because some people complain that when URLs get too long they stop being "easy" or "consistent". Since the old tradition is to just have updates/<version>, my thought was to avoid these freakouts by having /updates/<version> and /updates/<version>/stable/ result in the same content. Also, <updates,discovery>/\*/snapshots can be symlinks (easier to maintain than composite sites) to builds/\*/<jobname>/composite*.xml was (Author: nickboldt): Rationale for having updates/9.0/ be a composite site pointer to updates/9.0/stable/ (and similar for updates/mars/ == updates/mars/stable/ ) is because some people complain that when URLs get too long they stop being "easy" or "consistent". Since the old tradition is to just have updates/<version>, my thought was to avoid these freakouts by having /updates/<version> and /updates/<version>/stable/ result in the same content. Also, <updates,discovery>/*/snapshots can be symlinks (easier to maintain than composite sites) to builds/*/<jobname>/composite*.xml > reorg/refactor directories for consistency across JBT/JBDS > ---------------------------------------------------------- > > Key: JBDS-3208 > URL: https://issues.jboss.org/browse/JBDS-3208 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > Be it resolved - we should reorg directories for consistency across JBT/JBDS: > {code} > download.jboss.org > <earlyaccess,updates,discovery>/mars > /snapshots [replace nightly] > /staging [rename content for QE, moves to development when approved] > /development > /stable (updates/mars/stable is a pointer back into updates/mars) > drop /integration (not used) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > and > {code} > devstudio.redhat.com > <earlyaccess,updates,discovery>/9.0 > /snapshots > /staging > /development > /stable (updates/9.0/stable is a pointer back into updates/9.0) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112 > This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. > [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 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 December 2014