January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13232: ------------------------------------ Note, due to Jenkins bug (https://engineering.redhat.com/rt/Ticket/Display.html?id=186020) I've had to split the single matrix job into three jobs: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... > refactor target platforms' GAVs, names, labels (was target platforms has the same name) > --------------------------------------------------------------------------------------- > > Key: JBIDE-13232 > URL: https://issues.jboss.org/browse/JBIDE-13232 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Environment: > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha1 > > Attachments: JBIDE13232.parent.pom.tweaks.txt > > > .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either. > Makes it hard to actually see which target platform to choose -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13439) ESB Tests are failing locating project examples

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13439?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13439: ------------------------------------------- After looking at this, I think it's even simpler than we're making it out to be. I think all that's missing is registering http://download.jboss.org/jbosstools/examples/project-examples-jbds40.xml in JBDS when we install SOA-P plugins. To solve the problem so that ESB examples show up in the Project Examples list, all I had to do was add http://download.jboss.org/jbosstools/examples/project-examples-jbds40.xml to the JBossTools -> Project Examples preference page as a new "User Site". I expect that there's some kind of magic that goes on during installation to get that initial list of project example files registered, and the XML file that we want with the ESB examples isn't getting registered somehow when we pull in our features via the update site. Is there a step we need to do during installation to cure this problem? Maybe Denis Golovin knows? > ESB Tests are failing locating project examples > ----------------------------------------------- > > Key: JBIDE-13439 > URL: https://issues.jboss.org/browse/JBIDE-13439 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > > Problem: > ESB tests stopped being able to find project examples when executing test. Why ? > Nick's original theory, but that does not answer why the content that is still there is not showing up: > Problem: > a) you're missing stuff in http://download.jboss.org/jbosstools/examples/ > b) because people published their examples into their SVN workspaces instead of github, and expected it would magically appear in the /examples/ folder > c) yet no one bothered to audit that their content was properly published, aaaand... it's gone. > >> http://memegenerator.net/instance/33999035 << > Solution: > a) submit PRs for their stuff to contribute it to the new github repo, https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... > b) kick this job to sync: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j... > c) update this doc: https://community.jboss.org/wiki/ProjectExamplesSites > d) update this README: http://download.jboss.org/jbosstools/examples/readme.process.txt with new instructions -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13439) ESB Tests are failing locating project examples

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13439?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13439: ------------------------------------------- We'll likely need Max or Burr to chime in on why some of those things were split up. I honestly don't remember. I'm certainly good with merging them. Though there may be examples in JBT that are for Alpha/Beta/early release tooling that may not ever appear in JBDS with supported products. > ESB Tests are failing locating project examples > ----------------------------------------------- > > Key: JBIDE-13439 > URL: https://issues.jboss.org/browse/JBIDE-13439 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > > Problem: > ESB tests stopped being able to find project examples when executing test. Why ? > Nick's original theory, but that does not answer why the content that is still there is not showing up: > Problem: > a) you're missing stuff in http://download.jboss.org/jbosstools/examples/ > b) because people published their examples into their SVN workspaces instead of github, and expected it would magically appear in the /examples/ folder > c) yet no one bothered to audit that their content was properly published, aaaand... it's gone. > >> http://memegenerator.net/instance/33999035 << > Solution: > a) submit PRs for their stuff to contribute it to the new github repo, https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... > b) kick this job to sync: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j... > c) update this doc: https://community.jboss.org/wiki/ProjectExamplesSites > d) update this README: http://download.jboss.org/jbosstools/examples/readme.process.txt with new instructions -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1?page=com.atlassian.jira.plugin.sy... ] Barry LaFond commented on JBTIS-1: ---------------------------------- FYI, As of 8.0 Teiid Designer, we no longer depend on UML2 > Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone > --------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-1 > URL: https://issues.jboss.org/browse/JBTIS-1 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Paul Leacu > Labels: f2f2012 > Attachments: JBIDE-11121.tweak.txt, ModeShapeToolsBuildLog.txt > > > Generate target platforms for JBT/JBDS SOA Tooling which include: > 1. JBT Core TP + last stable JBT Core milestone. > 2. JBDS Core TP + last stable JBDS Core milestone. > Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones. > This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti). -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13439) ESB Tests are failing locating project examples

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13439?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13439: ------------------------------------ /me mumbles something about how we'd all benefit from JBDS and JBT not having different examples, because failing to test the community version (in favour of testing the product version) wouldn't matter, if the examples xml were the same file. :) Why are these example sets different between JBT and JBDS? I'm sure there's a good (historical) reason ... just wondering if that still needs to be true. > ESB Tests are failing locating project examples > ----------------------------------------------- > > Key: JBIDE-13439 > URL: https://issues.jboss.org/browse/JBIDE-13439 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > > Problem: > ESB tests stopped being able to find project examples when executing test. Why ? > Nick's original theory, but that does not answer why the content that is still there is not showing up: > Problem: > a) you're missing stuff in http://download.jboss.org/jbosstools/examples/ > b) because people published their examples into their SVN workspaces instead of github, and expected it would magically appear in the /examples/ folder > c) yet no one bothered to audit that their content was properly published, aaaand... it's gone. > >> http://memegenerator.net/instance/33999035 << > Solution: > a) submit PRs for their stuff to contribute it to the new github repo, https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... > b) kick this job to sync: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j... > c) update this doc: https://community.jboss.org/wiki/ProjectExamplesSites > d) update this README: http://download.jboss.org/jbosstools/examples/readme.process.txt with new instructions -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12974) merge contents of coretests and soatests sites into new integrationtests site (was: add missing IUs to coretests and soatests sites)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12974: ------------------------------- Summary: merge contents of coretests and soatests sites into new integrationtests site (was: add missing IUs to coretests and soatests sites) (was: add missing IUs to coretests and soatests sites) > merge contents of coretests and soatests sites into new integrationtests site (was: add missing IUs to coretests and soatests sites) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-12974 > URL: https://issues.jboss.org/browse/JBIDE-12974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.1.0.Alpha1 > > > The coretests [3] and soatests [4] sites are missing requirements/dependencies such as org.jboss.tools.ui.bot.ext. For JBDS 6.1 / 7.0, that missing dep can be added if you open a JIRA and specify what needs to be added. I might have to create a new feature to wrap the missing content. > [3] http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/ > [4] http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/ > Are there any other missing IUs you need on those sites? -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12974) add missing IUs to coretests and soatests sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12974: ------------------------------------ Agreed, the title asked for something that's now on the integrationtests site to be also on the coretests and soatests sites. But instead, I merged the content of all three sites into a single one. Isn't that far simpler? integrationtests now includes the unit tests from core/soa, plus all the ui/bot tests, and the test harness stuff (bot ext, etc.) So, I ask again. If you have a site which contains all the bot/harness/ui and headless test plugins too... why do you need coretests and soatests? And why would you disable the integrationtests site, when it's more useful IMHO? Besides, without it, you have no way to publish all these plugins: https://github.com/jbosstools/jbosstools-integration-tests/tree/master/te... > add missing IUs to coretests and soatests sites > ----------------------------------------------- > > Key: JBIDE-12974 > URL: https://issues.jboss.org/browse/JBIDE-12974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.1.0.Alpha1 > > > The coretests [3] and soatests [4] sites are missing requirements/dependencies such as org.jboss.tools.ui.bot.ext. For JBDS 6.1 / 7.0, that missing dep can be added if you open a JIRA and specify what needs to be added. I might have to create a new feature to wrap the missing content. > [3] http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/ > [4] http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/ > Are there any other missing IUs you need on those sites? -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13430) 'open' can open file in Eclipse AND the system editor

by Matt Benson (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13430?page=com.atlassian.jira.plugi... ] Matt Benson commented on JBIDE-13430: ------------------------------------- workaround is to issue the command as 'open '. > 'open' can open file in Eclipse AND the system editor > ----------------------------------------------------- > > Key: JBIDE-13430 > URL: https://issues.jboss.org/browse/JBIDE-13430 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.Final > Reporter: Matt Benson > Assignee: Koen Aers > > There is a no-args version of the 'open' command that implicitly refers to the '.' resource, usable, for example, after using commands from the Java plugin to create a new type, leaving that new type's source file as the current context. It appears that the AllCommandsInterceptor looks for commands followed by a space and as such misses commands without arguments. -- 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

13 years, 2 months

1
0
0 / 0

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

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-6?page=com.atlassian.jira.plugin.sy... ] Paul Leacu resolved JBTIS-6. ---------------------------- Resolution: Done Updated bpmn2 target dependency to the jboss mirror. > JBossTools Integration Stack :: BPMN2: Verify the component configuration of the initial IS tooling release. > ------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-6 > URL: https://issues.jboss.org/browse/JBTIS-6 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: BPMN2 > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Paul Leacu > > 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 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

13 years, 2 months

1
0
0 / 0

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

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-5?page=com.atlassian.jira.plugin.sy... ] Paul Leacu resolved JBTIS-5. ---------------------------- Resolution: Done Bob has verified BPEL in JBTIS - no issues. > JBossTools Integration Stack :: BPEL: Verify the component configuration of the initial IS tooling release. > ----------------------------------------------------------------------------------------------------------- > > Key: JBTIS-5 > URL: https://issues.jboss.org/browse/JBTIS-5 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: BPEL > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Paul Leacu > > 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 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

13 years, 2 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 January 2013