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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2743?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2743: ---------------------------------- The following pages have been created: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/juno/ http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/kep... http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/kepler/ The following pages have been updated to point to the new content in /targetplatforms/*/*/: http://download.jboss.org/jbosstools/updates/juno/ http://download.jboss.org/jbosstools/updates/kepler/ http://download.jboss.org/jbosstools/updates/kepler/integration-stack/ This doc has been updated: https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... > 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 > Assignee: 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-158: ---------------------------------- Looks cool, to me - merged https://github.com/jbosstools/jbosstools-integration-stack/pull/108 > create composite site zip containing JBDS IS + dependencies for easier offline install > -------------------------------------------------------------------------------------- > > Key: JBTIS-158 > URL: https://issues.jboss.org/browse/JBTIS-158 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Rob Cernich > > Suggested by [~rcernich]: > {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like: > {code}./compositeContent.xml > ./compositeArtifacts.xml > ./7.1.0/7.1.0.Beta1-jbds-is/ > ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code} > {quote} > This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site. > If we did a similar thing for JBT IS, it would need to contain these sites: > {code} > JBT webtools aggregate site (not the full JBT aggregate site) > JBT TP > JBT IS > JBT IS TP > {code} > Or, if we assume that users will already have JBT (or some part of it) installed, then we need only: > {code} > JBT IS > JBT IS TP > {code} -- 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-133) Task created instead of SwitchYard Service Task in BPMN process

by Robert (Bob) Brodt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-133?page=com.atlassian.jira.plugin.... ] Robert (Bob) Brodt commented on JBTIS-133: ------------------------------------------ This was already fixed and will be available in the next release due tomorrow, August 30 2013. > Task created instead of SwitchYard Service Task in BPMN process > --------------------------------------------------------------- > > Key: JBTIS-133 > URL: https://issues.jboss.org/browse/JBTIS-133 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPMN2, switchyard > Environment: JBDS 7.0.0.beta2, SOA tooling http://download.jboss.org/jbosstools/updates/integration/kepler/integrati..., SwitchYard 1.0.0 > Reporter: Lucie Fabrikova > Assignee: Robert (Bob) Brodt > > If I want to append a "switchyard service task" in a BPMN process by following steps, just a "task" is created. > Ie. the created task lacks possibility to define "on enter/exit scripts", "attributes". -- 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-158) create composite site zip containing JBDS IS + dependencies for easier offline install

by Rob Cernich (JIRA)

[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ] Rob Cernich edited comment on JBTIS-158 at 8/29/13 12:57 PM: ------------------------------------------------------------- The linked PR creates an additional zip in the site project. The structure of the zip is as follows: {noformat} ./aggregate/${project.version}/<jbds-is-repo> ./targetplatform/${project.version}/<jbds-is-tp-repo> {noformat} The root composite site includes children for ./aggregate and ./targetplatform. There are no repository references in the jbds-is-repo. The jbds-is-tp-repo is created by mirroring the jbtis tp from a url specified in the pom configuration. The one drawback is that you cannot install directly using the zip; you need to expand it first (the relative paths don't seem to work). When deploying to server, you should be good to simply expand the zip in the desired location for the initial site. For updates, you will have to expand all but the composite*.xml files and will have to add the new version(s) to the existing composite*.xml files on the server. Let me know what you think of this. was (Author: rcernich): The linked PR creates an additional zip in the site project. The structure of the zip is as follows: ./aggregate/${project.version}/<jbds-is-repo> ./targetplatform/${project.version}/<jbds-is-tp-repo> The root composite site includes children for ./aggregate and ./targetplatform. There are no repository references in the jbds-is-repo. The jbds-is-tp-repo is created by mirroring the jbtis tp from a url specified in the pom configuration. The one drawback is that you cannot install directly using the zip; you need to expand it first (the relative paths don't seem to work). When deploying to server, you should be good to simply expand the zip in the desired location for the initial site. For updates, you will have to expand all but the composite*.xml files and will have to add the new version(s) to the existing composite*.xml files on the server. Let me know what you think of this. > create composite site zip containing JBDS IS + dependencies for easier offline install > -------------------------------------------------------------------------------------- > > Key: JBTIS-158 > URL: https://issues.jboss.org/browse/JBTIS-158 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Rob Cernich > > Suggested by [~rcernich]: > {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like: > {code}./compositeContent.xml > ./compositeArtifacts.xml > ./7.1.0/7.1.0.Beta1-jbds-is/ > ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code} > {quote} > This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site. > If we did a similar thing for JBT IS, it would need to contain these sites: > {code} > JBT webtools aggregate site (not the full JBT aggregate site) > JBT TP > JBT IS > JBT IS TP > {code} > Or, if we assume that users will already have JBT (or some part of it) installed, then we need only: > {code} > JBT IS > JBT IS TP > {code} -- 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-158) create composite site zip containing JBDS IS + dependencies for easier offline install

by Rob Cernich (JIRA)

[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ] Rob Cernich commented on JBTIS-158: ----------------------------------- The linked PR creates an additional zip in the site project. The structure of the zip is as follows: ./aggregate/${project.version}/<jbds-is-repo> ./targetplatform/${project.version}/<jbds-is-tp-repo> The root composite site includes children for ./aggregate and ./targetplatform. There are no repository references in the jbds-is-repo. The jbds-is-tp-repo is created by mirroring the jbtis tp from a url specified in the pom configuration. The one drawback is that you cannot install directly using the zip; you need to expand it first (the relative paths don't seem to work). When deploying to server, you should be good to simply expand the zip in the desired location for the initial site. For updates, you will have to expand all but the composite*.xml files and will have to add the new version(s) to the existing composite*.xml files on the server. Let me know what you think of this. > create composite site zip containing JBDS IS + dependencies for easier offline install > -------------------------------------------------------------------------------------- > > Key: JBTIS-158 > URL: https://issues.jboss.org/browse/JBTIS-158 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Rob Cernich > > Suggested by [~rcernich]: > {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like: > {code}./compositeContent.xml > ./compositeArtifacts.xml > ./7.1.0/7.1.0.Beta1-jbds-is/ > ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code} > {quote} > This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site. > If we did a similar thing for JBT IS, it would need to contain these sites: > {code} > JBT webtools aggregate site (not the full JBT aggregate site) > JBT TP > JBT IS > JBT IS TP > {code} > Or, if we assume that users will already have JBT (or some part of it) installed, then we need only: > {code} > JBT IS > JBT IS TP > {code} -- 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-15382) Create target platform from Kepler SR1 (RC) dependencies

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15382?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15382: ---------------------------------------- To find the latest URLs for Kepler SR1 contributions, it's fine to use this link: https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/tree/?h=Kep... > Create target platform from Kepler SR1 (RC) dependencies > -------------------------------------------------------- > > Key: JBIDE-15382 > URL: https://issues.jboss.org/browse/JBIDE-15382 > Project: Tools (JBoss Tools) > Issue Type: Bug > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2737) Archive old JBDS docs on devstudio.jboss.com

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2737?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2737: ----------------------------- Assignee: Michelle Murray (was: Nick Boldt) > Archive old JBDS docs on devstudio.jboss.com > --------------------------------------------- > > Key: JBDS-2737 > URL: https://issues.jboss.org/browse/JBDS-2737 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: documentation > Affects Versions: 3.0.1.GA, 4.0.1.GA, 4.1.3.GA, 5.0.2.GA, 6.0.0.GA, 7.0.0.GA > Reporter: Nick Boldt > Assignee: Michelle Murray > Fix For: 7.0.0.GA > > Attachments: JBDS2737_draft-css.png > > > This is a workaround for https://bugzilla.redhat.com/show_bug.cgi?id=983934 because it's easier to download the internet (apparently) than to fix portal code. *sigh* > Docs will be posted to devstudio.jboss.com/site/documentation/ as they include absolute path references. > _Hack: 1. Proper solution: 0._ -- 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-2737) Archive old JBDS docs on devstudio.jboss.com

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2737?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-2737. ------------------------------ Fix Version/s: 7.0.0.GA Resolution: Done OK, for now I'm happy w/ the above URLs. * For all the HTML/PDF/epub files (with at least a clean / usable skin): https://devstudio.jboss.com/site/documentation/ * For just the PDFs: https://devstudio.jboss.com/download/documentation/ Feel free to re-open, if further reskinnning is still needed. > Archive old JBDS docs on devstudio.jboss.com > --------------------------------------------- > > Key: JBDS-2737 > URL: https://issues.jboss.org/browse/JBDS-2737 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: documentation > Affects Versions: 3.0.1.GA, 4.0.1.GA, 4.1.3.GA, 5.0.2.GA, 6.0.0.GA, 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.GA > > Attachments: JBDS2737_draft-css.png > > > This is a workaround for https://bugzilla.redhat.com/show_bug.cgi?id=983934 because it's easier to download the internet (apparently) than to fix portal code. *sigh* > Docs will be posted to devstudio.jboss.com/site/documentation/ as they include absolute path references. > _Hack: 1. Proper solution: 0._ -- 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-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: ----------------------------- Target Release: (was: 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, 7 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 CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2743?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2743: ----------------------------- CDW pm_ack: (was: ?) CDW release: (was: ?) > 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, 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