July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-83) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-83?page=com.atlassian.jira.plugin.s... ] Nick Boldt commented on JBTIS-83: --------------------------------- if you want this working in JBDS 8, then the file should be 8.0 (or 4.2, or luna) if you want it proof-of-concept in JBDS 7, well, you can't because there's no support for this ide-config properties file there therefore, the file needs to be called 8.0 (or 4.2, or luna) because I don't see a way to backport this to JBDS 7.x (maybe there is?) QED, please rename the file :) > JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration > -------------------------------------------------------- > > Key: JBTIS-83 > URL: https://issues.jboss.org/browse/JBTIS-83 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.0.0 > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 4.0.0 > > Attachments: jbtis-project-examples-community-7.1.xml > > > JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration > Steps as defined by Nick (thanks Nick!): > a) the contents of the examples are in a former employee's SVN workspace > and haven't been updated since a couple of years. They don't really work > as well as they could. > b) the examples are all mostly duplicated in the quickstarts folder that > ships with SOA-P 5.3.1. See > https://bugzilla.redhat.com/show_bug.cgi?id=951677 and > https://issues.jboss.org/browse/JBTIS-62 > Basically, we need to: > * fix the quickstarts in SOA-P 6 so they ACTUALLY WORK as importable > eclipse projects (merge in contents from duplicate examples in Denny's > workspace). Could decide to backport to 5.3 if there's a 5.3.2 planned; > if not, no great need. > * copy the older examples that are not already in SOA-P 5.3 - the ones > that are *exclusively* in Denny's workspace - into SOA-P 6 so they'll be > available there. > * update the BPEL Examples guide as needed > * document the fact that these examples are no longer available as > importable zipped example projects contributed by a plugin, but rather > as already-unpacked projects nested within the SOA-P runtime zip -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17536) JBoss Tools Core Nightly update site fails to install if a new build is published during install

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17536?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-17536: --------------------------------------- IMO, this issue is duplicate of JBIDE-15482, which is related to publishing done wrong. Changes in download site structure won't help to solve it. > JBoss Tools Core Nightly update site fails to install if a new build is published during install > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-17536 > URL: https://issues.jboss.org/browse/JBIDE-17536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > When you install JBT nightly from http://download.jboss.org/jbosstools/updates/nightly/core/master/ into Eclipse and during the build, a new nightly build replaces the old one, you can get a failure like this: > {code}http://download.jboss.org/jbosstools/updates/nightly/core/master/features/org.jboss.tools.wtp.runtimes.tomcat.feature_1.1.0.Beta3-v20140603-0027-B526.jar cannot be found{code} > This is because during your install, the old jars were replaced with the new jars, i.e. different filenames. > I'm not sure if it's something we really need to fix, it's open for discussion. But it happened to me yesterday and it wasn't the first time, so I'm throwing it on the table. > Nick offered this alternative: > install from a specific build folder instead of the "latest nightly" > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > But obviously that's just a workaround, not a real solution. > One way this could be achieved is this: plugins/ and features/ would contain jars from both the latest and previous builds. This way if you start installing (latest=build N) and in the middle of your installation there is a new build (N+1), there would still be jars for both N and N+1 builds. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17966) Application wizard: "Source Code" is editable while "Use default" is checked

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17966?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17966: ------------------------------------- Labels: application_wizard ux_review (was: ) > Application wizard: "Source Code" is editable while "Use default" is checked > ---------------------------------------------------------------------------- > > Key: JBIDE-17966 > URL: https://issues.jboss.org/browse/JBIDE-17966 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: application_wizard, ux_review > Fix For: 4.2.0.CR1 > > Attachments: source-code-editable.png > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3110) Application wizard: "Source Code" is editable while "Use default" is checked

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3110?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3110: ----------------------------------- Fix Version/s: 8.0.0.CR1 > Application wizard: "Source Code" is editable while "Use default" is checked > ---------------------------------------------------------------------------- > > Key: JBDS-3110 > URL: https://issues.jboss.org/browse/JBDS-3110 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta3 > Reporter: Andre Dietisheim > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 8.0.0.CR1 > > Attachments: source-code-editable.png > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3110) Application wizard: "Source Code" is editable while "Use default" is checked

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3110?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3110: ----------------------------------- Assignee: Andre Dietisheim (was: Max Rydahl Andersen) > Application wizard: "Source Code" is editable while "Use default" is checked > ---------------------------------------------------------------------------- > > Key: JBDS-3110 > URL: https://issues.jboss.org/browse/JBDS-3110 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 8.0.0.CR1 > > Attachments: source-code-editable.png > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3110) Application wizard: "Source Code" is editable while "Use default" is checked

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBDS-3110: -------------------------------------- Summary: Application wizard: "Source Code" is editable while "Use default" is checked Key: JBDS-3110 URL: https://issues.jboss.org/browse/JBDS-3110 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: openshift Affects Versions: 8.0.0.Beta3 Reporter: Andre Dietisheim Assignee: Max Rydahl Andersen Priority: Minor Attachments: source-code-editable.png -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3110) Application wizard: "Source Code" is editable while "Use default" is checked

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3110?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3110: ----------------------------------- Attachment: source-code-editable.png > Application wizard: "Source Code" is editable while "Use default" is checked > ---------------------------------------------------------------------------- > > Key: JBDS-3110 > URL: https://issues.jboss.org/browse/JBDS-3110 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta3 > Reporter: Andre Dietisheim > Assignee: Max Rydahl Andersen > Priority: Minor > Attachments: source-code-editable.png > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-83) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-83?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick commented on JBTIS-83: ---------------------------------------- The properties to add to the ide-config.properties file then become: integrationstack.examples.url|jbosstools|4.2=http://github.com/jbosstools... integrationstack.examples.url|devstudio|8.0=http://github.com/jbosstools/... And I'm happy to change that to 8.0 for simplicity sake. > JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration > -------------------------------------------------------- > > Key: JBTIS-83 > URL: https://issues.jboss.org/browse/JBTIS-83 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.0.0 > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 4.0.0 > > Attachments: jbtis-project-examples-community-7.1.xml > > > JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration > Steps as defined by Nick (thanks Nick!): > a) the contents of the examples are in a former employee's SVN workspace > and haven't been updated since a couple of years. They don't really work > as well as they could. > b) the examples are all mostly duplicated in the quickstarts folder that > ships with SOA-P 5.3.1. See > https://bugzilla.redhat.com/show_bug.cgi?id=951677 and > https://issues.jboss.org/browse/JBTIS-62 > Basically, we need to: > * fix the quickstarts in SOA-P 6 so they ACTUALLY WORK as importable > eclipse projects (merge in contents from duplicate examples in Denny's > workspace). Could decide to backport to 5.3 if there's a 5.3.2 planned; > if not, no great need. > * copy the older examples that are not already in SOA-P 5.3 - the ones > that are *exclusively* in Denny's workspace - into SOA-P 6 so they'll be > available there. > * update the BPEL Examples guide as needed > * document the fact that these examples are no longer available as > importable zipped example projects contributed by a plugin, but rather > as already-unpacked projects nested within the SOA-P runtime zip -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-83) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-83?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick commented on JBTIS-83: ---------------------------------------- Ok. Have updated all the paths to the zips in the project examples xml file to NOT be the static revision in the latest PR - https://github.com/jbosstools/jbosstools-esb/pull/56/files > JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration > -------------------------------------------------------- > > Key: JBTIS-83 > URL: https://issues.jboss.org/browse/JBTIS-83 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.0.0 > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 4.0.0 > > Attachments: jbtis-project-examples-community-7.1.xml > > > JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration > Steps as defined by Nick (thanks Nick!): > a) the contents of the examples are in a former employee's SVN workspace > and haven't been updated since a couple of years. They don't really work > as well as they could. > b) the examples are all mostly duplicated in the quickstarts folder that > ships with SOA-P 5.3.1. See > https://bugzilla.redhat.com/show_bug.cgi?id=951677 and > https://issues.jboss.org/browse/JBTIS-62 > Basically, we need to: > * fix the quickstarts in SOA-P 6 so they ACTUALLY WORK as importable > eclipse projects (merge in contents from duplicate examples in Denny's > workspace). Could decide to backport to 5.3 if there's a 5.3.2 planned; > if not, no great need. > * copy the older examples that are not already in SOA-P 5.3 - the ones > that are *exclusively* in Denny's workspace - into SOA-P 6 so they'll be > available there. > * update the BPEL Examples guide as needed > * document the fact that these examples are no longer available as > importable zipped example projects contributed by a plugin, but rather > as already-unpacked projects nested within the SOA-P runtime zip -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17960) "The specified JRE installation does not exist"

by Karl Pietrzak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17960?page=com.atlassian.jira.plugi... ] Karl Pietrzak commented on JBIDE-17960: --------------------------------------- @[~rob.stryker]: I grabbed the latest version from http://tools.jboss.org/downloads/jbosstools/luna/index.html, which is currently still Beta2. I'll try out Beta3 when it comes out. > "The specified JRE installation does not exist" > ----------------------------------------------- > > Key: JBIDE-17960 > URL: https://issues.jboss.org/browse/JBIDE-17960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Karl Pietrzak > Priority: Minor > Attachments: jbossastools-bad.jre.swf > > > h3. What > If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. > h3. Screencast > !jbossastools-bad.jre.swf! > If the above embedded SWF doesn't work for you, you can watch it at http://screencast.com/t/bytN53lp -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 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 July 2014