August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-141) fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-141?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBTIS-141 at 8/19/13 10:10 AM: ------------------------------------------------------------ Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=8 Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=2 was (Author: nickboldt): Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=8 > fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb > ----------------------------------------------------------------------------- > > Key: JBTIS-141 > URL: https://issues.jboss.org/browse/JBTIS-141 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL, distribution, ESB, jBPM3 > Affects Versions: 4.0.0, 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.1, 4.1.1 > > > Need to update the URLs in the composite*.xml files to point at the newly minted esb, jbpm3 and bpel update sites for 4.0.x and 4.1.x streams. > Also found some other problems in the compositeContent.xml files in that they contain a compositeArtifactRepository instead of compositeMetadataRepository so I'll attach a PR for that fix too. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-141) fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-141?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBTIS-141 at 8/19/13 10:10 AM: ------------------------------------------------------------ Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=8 *DONE* Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=2 was (Author: nickboldt): Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=8 Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=2 > fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb > ----------------------------------------------------------------------------- > > Key: JBTIS-141 > URL: https://issues.jboss.org/browse/JBTIS-141 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL, distribution, ESB, jBPM3 > Affects Versions: 4.0.0, 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.1, 4.1.1 > > > Need to update the URLs in the composite*.xml files to point at the newly minted esb, jbpm3 and bpel update sites for 4.0.x and 4.1.x streams. > Also found some other problems in the compositeContent.xml files in that they contain a compositeArtifactRepository instead of compositeMetadataRepository so I'll attach a PR for that fix too. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15340) Remove site references from Locus site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15340?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15340: ------------------------------------ They've been there since day one, so that you can install anything from the Locus site w/o having to add additional sites to Eclipse to resolve deps. Please clarify how having the Locus site automatically add references to the latest JBT TP and JBT Aggregate sites causes a *cyclic* dependency, if nothing in JBT depends on Locus? Perhaps we should instead be referring to these 4 sites? https://github.com/jbosstools/jbosstools-locus/blob/master/target-platfor... (Orbit R20130517) https://github.com/jbosstools/jbosstools-locus/blob/master/target-platfor... (Juno SR2) https://github.com/jbosstools/jbosstools-locus/blob/master/target-platfor... (SpringIDE 3.2) https://github.com/jbosstools/jbosstools-locus/blob/master/target-platfor... (Eclipse Gemini Management 2.0.0 / osgi.jmx) > Remove site references from Locus site > -------------------------------------- > > Key: JBIDE-15340 > URL: https://issues.jboss.org/browse/JBIDE-15340 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: locus > Reporter: Rob Cernich > Assignee: Nick Boldt > Priority: Blocker > Fix For: 1.1.0-LOCUS > > > The Locus p2 repo/update site should not include references to other update sites. Currently it includes references to other sites, e.g. http://download.jboss.org/jbosstools/updates/development/juno/ -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2425) JBoss Central lists features as tested or supported - but the tooltip link provided does not include a definition of these terms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2425?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2425 at 8/19/13 9:54 AM: ----------------------------------------------------------- New plugin produced and pushed to devstudio.jboss.com server (https://github.com/jbdevstudio/jbdevstudio-website/pull/25). Once the server refreshes (~30mins), we can verify this is fixed in the default OOTB JBDS 7 install (without using `-vmargs` override). {code:title=https://devstudio.jboss.com/updates/7.0/devstudio-directory.xml} <entry url="discovery/com.jboss.jbds.central.discovery_7.0.0.Final-v20130819-0921-B276.jar" permitCategories="true"/> {code} was (Author: nickboldt): New plugin produced and pushed to devstudio.jboss.com server. Once the server refreshes (~30mins), we can verify this is fixed in the default OOTB JBDS 7 install (without using `-vmargs` override). {code:title=https://devstudio.jboss.com/updates/7.0/devstudio-directory.xml} <entry url="discovery/com.jboss.jbds.central.discovery_7.0.0.Final-v20130819-0921-B276.jar" permitCategories="true"/> {code} > JBoss Central lists features as tested or supported - but the tooltip link provided does not include a definition of these terms > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2425 > URL: https://issues.jboss.org/browse/JBDS-2425 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Central > Affects Versions: 6.0.0.CR1 > Environment: Version: 6.0.0.CR1 > Build id: CR1-v20121204-0201-B166 > Build date: 20121204-0201 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 7.0.0.GA > > Attachments: 2425.png, 2425_2.png, 2425_3.png > > > In JBoss Central (see attached screenshot), features are listed as "tested" or "supported" - but the active links provided take the user to: https://devstudio.jboss.com/download/ > Where these terms are not defined. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15352) Include more mobile quickstarts on central page

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-15352: ------------------------------------------- Summary: Include more mobile quickstarts on central page Key: JBIDE-15352 URL: https://issues.jboss.org/browse/JBIDE-15352 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Max Rydahl Andersen incorporate quickstarts produced at WFK2-105 -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15345) use latest parent pom & target platform so we can release ESB tooling v 1.5.200.Final

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15345?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-15345: ------------------------------------------- should be good to go. have been zero changes for quite a while, so we ought to be good and stable > use latest parent pom & target platform so we can release ESB tooling v 1.5.200.Final > ------------------------------------------------------------------------------------- > > Key: JBIDE-15345 > URL: https://issues.jboss.org/browse/JBIDE-15345 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: esb > Affects Versions: 4.0.1.Final > Reporter: Nick Boldt > Assignee: Brian Fitzpatrick > Fix For: 4.0.2.Final > > > Target platform referenced should be the latest Juno version (4.0.1.Final) rather than the 4.0.0-SNAPSHOT one. > Once that's fixed and the build is blue, we should release ESB tooling v 1.5.200.Final and include it in the latest JBTIS 4.0.x aggregate site builds. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2425) JBoss Central lists features as tested or supported - but the tooltip link provided does not include a definition of these terms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2425?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2425: ---------------------------------- Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=276 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=1559 Tested using JBDS 7 (7.0.0.GA-v20130720-0044-B364) launched like this (build #1559): {code}./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/devstudio-directory.xml{code} And when I click the links for "Experimental" or "Tested" or "Supported" or "External" the page that opens is now https://devstudio.jboss.com/updates/7.0-development/central/ > JBoss Central lists features as tested or supported - but the tooltip link provided does not include a definition of these terms > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2425 > URL: https://issues.jboss.org/browse/JBDS-2425 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Central > Affects Versions: 6.0.0.CR1 > Environment: Version: 6.0.0.CR1 > Build id: CR1-v20121204-0201-B166 > Build date: 20121204-0201 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 7.0.0.GA > > Attachments: 2425.png, 2425_2.png, 2425_3.png > > > In JBoss Central (see attached screenshot), features are listed as "tested" or "supported" - but the active links provided take the user to: https://devstudio.jboss.com/download/ > Where these terms are not defined. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2425) JBoss Central lists features as tested or supported - but the tooltip link provided does not include a definition of these terms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2425?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2425 at 8/19/13 9:29 AM: ----------------------------------------------------------- Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=276 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=1559 Tested using JBDS 7 (7.0.0.GA-v20130720-0044-B364) launched like this (build #1559): {code}./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/devstudio-directory.xml{code} And when I open JBoss Central, then switch to the Software/Update tab, and click the links for "Experimental" or "Tested" or "Supported" or "External" the page that opens is now: https://devstudio.jboss.com/updates/7.0-development/central/ was (Author: nickboldt): Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=276 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=1559 Tested using JBDS 7 (7.0.0.GA-v20130720-0044-B364) launched like this (build #1559): {code}./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/devstudio-directory.xml{code} And when I click the links for "Experimental" or "Tested" or "Supported" or "External" the page that opens is now https://devstudio.jboss.com/updates/7.0-development/central/ > JBoss Central lists features as tested or supported - but the tooltip link provided does not include a definition of these terms > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2425 > URL: https://issues.jboss.org/browse/JBDS-2425 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Central > Affects Versions: 6.0.0.CR1 > Environment: Version: 6.0.0.CR1 > Build id: CR1-v20121204-0201-B166 > Build date: 20121204-0201 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 7.0.0.GA > > Attachments: 2425.png, 2425_2.png, 2425_3.png > > > In JBoss Central (see attached screenshot), features are listed as "tested" or "supported" - but the active links provided take the user to: https://devstudio.jboss.com/download/ > Where these terms are not defined. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-148) JBDSIS - re-enable devstudio support

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-148: -------------------------------- Summary: JBDSIS - re-enable devstudio support Key: JBTIS-148 URL: https://issues.jboss.org/browse/JBTIS-148 Project: JBoss Tools Integration Stack Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 7.1.0-JBDS Reporter: Paul Leacu Assignee: Paul Leacu Re-enable fuse - make sure associated sites and correct -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-141) fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-141?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-141: ---------------------------------- Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=8 > fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb > ----------------------------------------------------------------------------- > > Key: JBTIS-141 > URL: https://issues.jboss.org/browse/JBTIS-141 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL, distribution, ESB, jBPM3 > Affects Versions: 4.0.0, 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.1, 4.1.1 > > > Need to update the URLs in the composite*.xml files to point at the newly minted esb, jbpm3 and bpel update sites for 4.0.x and 4.1.x streams. > Also found some other problems in the compositeContent.xml files in that they contain a compositeArtifactRepository instead of compositeMetadataRepository so I'll attach a PR for that fix too. -- 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, 7 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