August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2715) provide script & instructions for performing headless commandline installations of JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2715?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2715: ----------------------------- CDW devel_ack: + (was: ?) > provide script & instructions for performing headless commandline installations of JBDS > --------------------------------------------------------------------------------------- > > Key: JBDS-2715 > URL: https://issues.jboss.org/browse/JBDS-2715 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > > Script for linux: > https://gist.github.com/nickboldt/6041754 > Need a windows version & then to provide this somewhere along w/ the JBDS installer, perhaps on the CSP / EA pages? -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15383) Server Launch Configuration loses Classpath User Entries

by Daniel Atallah (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15383?page=com.atlassian.jira.plugi... ] Daniel Atallah updated JBIDE-15383: ----------------------------------- Attachment: JBIDE_3.png JBIDE_1.png JBIDE_2.png > Server Launch Configuration loses Classpath User Entries > -------------------------------------------------------- > > Key: JBIDE-15383 > URL: https://issues.jboss.org/browse/JBIDE-15383 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Final > Environment: Windows 7 64-bit, Java7u25 64-bit, Eclipse Kepler, JBoss AS 7.1.1 > Reporter: Daniel Atallah > Attachments: JBIDE_1.png, JBIDE_2.png, JBIDE_3.png > > > Any additions to the Server Launch Configuration's Classpath "User Entries" are lost when the dialog is closed and reopened. > This is likely related; there appears to be an issue where the initial values of "User Entries" are also incorrect (and are reverted from the "Restore Default Entries" value) when the dialog is reopened. > Specifically, the "org.jboss.ide.eclipse.as.core.server.launch.runJarContainer/JBoss 7.1 Runtime Server" library to a single external "jboss-modules.jar". > The attachments describe what happens: > * The initial state when editing the Launch Configuration is in [^JBIDE_1.png]. > * When the "Restore Default Entries" button is clicked, the values are changed to what should be the default state ([^JBIDE_2.png]). > * When the dialog is closed and reopened, it reverts back to the way it appeared in [^JBIDE_1.png]. > * Similarly if I manually add an external directory (or any other entry, for that matter), as appears in [^JBIDE_3.png], after closing and reopening the dialog, it reverts back to the [^JBIDE_1.png] state. > I've tried simply clicking "OK" and also making sure I click "Apply" before clicking "OK", but that doesn't seem to have an effect. > I've been able to replicate this on two separate (similarly configured) machines. > This sounds very similar to JBIDE-786, but that's very old and marked as Resolved a long time ago, so I figured it'd be appropriate to file a new issue. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2715) provide script & instructions for performing headless commandline installations of JBDS

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2715?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2715: ----------------------------- CDW devel_ack: ? CDW pm_ack: + CDW qa_ack: ? > provide script & instructions for performing headless commandline installations of JBDS > --------------------------------------------------------------------------------------- > > Key: JBDS-2715 > URL: https://issues.jboss.org/browse/JBDS-2715 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > > Script for linux: > https://gist.github.com/nickboldt/6041754 > Need a windows version & then to provide this somewhere along w/ the JBDS installer, perhaps on the CSP / EA pages? -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15383) Server Launch Configuration loses Classpath User Entries

by Daniel Atallah (JIRA)

Daniel Atallah created JBIDE-15383: -------------------------------------- Summary: Server Launch Configuration loses Classpath User Entries Key: JBIDE-15383 URL: https://issues.jboss.org/browse/JBIDE-15383 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.1.0.Final Environment: Windows 7 64-bit, Java7u25 64-bit, Eclipse Kepler, JBoss AS 7.1.1 Reporter: Daniel Atallah Any additions to the Server Launch Configuration's Classpath "User Entries" are lost when the dialog is closed and reopened. This is likely related; there appears to be an issue where the initial values of "User Entries" are also incorrect (and are reverted from the "Restore Default Entries" value) when the dialog is reopened. Specifically, the "org.jboss.ide.eclipse.as.core.server.launch.runJarContainer/JBoss 7.1 Runtime Server" library to a single external "jboss-modules.jar". The attachments describe what happens: * The initial state when editing the Launch Configuration is in [^JBIDE_1.png]. * When the "Restore Default Entries" button is clicked, the values are changed to what should be the default state ([^JBIDE_2.png]). * When the dialog is closed and reopened, it reverts back to the way it appeared in [^JBIDE_1.png]. * Similarly if I manually add an external directory (or any other entry, for that matter), as appears in [^JBIDE_3.png], after closing and reopening the dialog, it reverts back to the [^JBIDE_1.png] state. I've tried simply clicking "OK" and also making sure I click "Apply" before clicking "OK", but that doesn't seem to have an effect. I've been able to replicate this on two separate (similarly configured) machines. This sounds very similar to JBIDE-786, but that's very old and marked as Resolved a long time ago, so I figured it'd be appropriate to file a new issue. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2744) Certification for Google plugins 3.3.0

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2744?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-2744: --------------------------------- Parent: (was: JBDS-2710) Issue Type: Task (was: Sub-task) > Certification for Google plugins 3.3.0 > -------------------------------------- > > Key: JBDS-2744 > URL: https://issues.jboss.org/browse/JBDS-2744 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification > Reporter: Mickael Istria > > Google GDT plugins have been updated to version 3.3.0. Current version we use in 3.2.3. > Can we include 3.3.0 in our Target Platform for JBT 4.2.0.Alpha1 ? -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2744) Certification for Google plugins 3.3.0

by Mickael Istria (JIRA)

Mickael Istria created JBDS-2744: ------------------------------------ Summary: Certification for Google plugins 3.3.0 Key: JBDS-2744 URL: https://issues.jboss.org/browse/JBDS-2744 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Security Level: Public (Everyone can see) Components: 3rdPartyCertification Reporter: Mickael Istria Google GDT plugins have been updated to version 3.3.0. Current version we use in 3.2.3. Can we include 3.3.0 in our Target Platform for JBT 4.2.0.Alpha1 ? -- 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

10 years, 10 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 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

10 years, 10 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

10 years, 10 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

10 years, 10 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2013