July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13053) Explorer: Cannot remove several connections at once

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13053?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-13053: ---------------------------------- Attachment: RemoveConnections3.png RemoveConnections1.png RemoveConnections2.png > Explorer: Cannot remove several connections at once > --------------------------------------------------- > > Key: JBIDE-13053 > URL: https://issues.jboss.org/browse/JBIDE-13053 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Beta2 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: RemoveConnections1.png, RemoveConnections2.png, RemoveConnections3.png, several-connections.png > > > The *OpenShift Explorer* allows you to remove a single connection from the context-menu: select your connection and pick *Remove from View*. Your connection will be removed from the OpenShift Explorer. This is currently not possible for several connections at once - the menu entry is missing from the context menu. > !several-connections.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13053) Explorer: Cannot remove several connections at once

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13053?page=com.atlassian.jira.plugi... ] Daniel Azarov reassigned JBIDE-13053: ------------------------------------- Assignee: Andre Dietisheim [~adietish], please verify my PR !RemoveConnections1.png! !RemoveConnections2.png! !RemoveConnections3.png! > Explorer: Cannot remove several connections at once > --------------------------------------------------- > > Key: JBIDE-13053 > URL: https://issues.jboss.org/browse/JBIDE-13053 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: RemoveConnections1.png, RemoveConnections2.png, RemoveConnections3.png, several-connections.png > > > The *OpenShift Explorer* allows you to remove a single connection from the context-menu: select your connection and pick *Remove from View*. Your connection will be removed from the OpenShift Explorer. This is currently not possible for several connections at once - the menu entry is missing from the context menu. > !several-connections.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-289) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration - 4.1.x

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-289?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-289: ----------------------------------------- Merged into 4.1.x > JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration - 4.1.x > ---------------------------------------------------------------- > > Key: JBTIS-289 > URL: https://issues.jboss.org/browse/JBTIS-289 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.0.0 > Reporter: Brian Fitzpatrick > Assignee: Brian Fitzpatrick > Fix For: 4.0.0 > > > 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] (JBDS-3092) Remove content in JBDS update site which is duplicated in the JBDS TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3092?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3092: ---------------------------------- Got a better idea to reduce the size of the JBDS update site zip: build it again to remove the pack200 cruft. Requires a minor adjustment to the publish.sh script: https://github.com/jbosstools/jbosstools-build-ci/pull/102 And these changes to the job config: https://github.com/jbdevstudio/jbdevstudio-ci/pull/128 > Remove content in JBDS update site which is duplicated in the JBDS TP > --------------------------------------------------------------------- > > Key: JBDS-3092 > URL: https://issues.jboss.org/browse/JBDS-3092 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: target-platform, updatesite > Affects Versions: 8.0.0.Beta3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.0.CR1 > > Attachments: beta2-vs-cr1-installer-jar-cr1-has-less-eclipse.org-compare-compressed-dir-sizes.png, beta2-vs-cr1-installer-jar-cr1-has-less-eclipse.org-features-included.png, beta3-vs-cr1-installer-jar-cr1-has-more-plugins-included.png, jbds3092-dgolovin-pr.png > > > From Max: > {quote} Why is parts of TP included inside https://devstudio.jboss.com/updates/8.0.0/jboss-devstudio-8.0.0.Beta3-upd... ? > why not *just* our plugins ? {quote} > Ref: https://wiki.eclipse.org/Tycho/Packaging_Types#eclipse-repository > Haha: http://memegenerator.net/instance/52610169 > Reason for the extraneous inclusions is that this config param is set in the JBDS update site pom: > {code:title=https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/pom.xml#L29} > <includeAllDependencies>true</includeAllDependencies> > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-289) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration - 4.1.x

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-289?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-289: ----------------------------------------- Migrating code done on master branch back to 4.1.x branch. > JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration - 4.1.x > ---------------------------------------------------------------- > > Key: JBTIS-289 > URL: https://issues.jboss.org/browse/JBTIS-289 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.0.0 > Reporter: Brian Fitzpatrick > Assignee: Brian Fitzpatrick > Fix For: 4.0.0 > > > 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-289) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration - 4.1.x

by Brian Fitzpatrick (JIRA)

Brian Fitzpatrick created JBTIS-289: --------------------------------------- Summary: JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration - 4.1.x Key: JBTIS-289 URL: https://issues.jboss.org/browse/JBTIS-289 Project: JBoss Tools Integration Stack Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Affects Versions: 4.0.0 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 4.0.0 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. Just pushed my changes into master. Running a full build and will then push the same changes back to 4.1.x so they're available for JBDS 7. Thanks for all the help [~maxandersen] and [~nickboldt]! > 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-13283) Use Akamai for Target-Platform, Mirror, releases stuff

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13283?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-13283. ------------------------------ Closing as nothing to QE. > Use Akamai for Target-Platform, Mirror, releases stuff > ------------------------------------------------------ > > Key: JBIDE-13283 > URL: https://issues.jboss.org/browse/JBIDE-13283 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, target-platform, updatesite > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Beta2 > > > All our repositories that are either mirrors or target-platform are not updated often. Then we could use Akamai to improve performances. At least these folders would be good: > * http://download.jboss.org/jbosstools/updates/requirements/ > * http://download.jboss.org/jbosstools/updates/stable/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17964) add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17964?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17964: ------------------------------------ We have two options: a) list feature(s) and a URL from which the feature(s) can be installed - this is how the JBDS and JBT entries work b) provide NO URL: just a description and link to the compatible JBDS marketplace entry - https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-ke... IMHO ( b ) is better because it will put eyeballs onto JBDSIS without splitting the install statistics across two solutions. We already split our user base between JBT and JBDS, resulting in a lower position in the standings of "top 10 solutions". If we further split that user base into 2 more buckets (JBT IS and JBDS IS) we'll lose our pole position in the top ten. ( b ) is also better because it doesn't provide yet another way to install JBDSIS which needs to have GSS support. All we're doing is driving traffic to JBDS and JBoss Central, which uses the existing supported install path. > add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric > ------------------------------------------------------------------------------------------ > > Key: JBIDE-17964 > URL: https://issues.jboss.org/browse/JBIDE-17964 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 4.1.2.Final > Reporter: Lars Heinemann > Assignee: Nick Boldt > Fix For: 4.1.2.Final > > > Currently when people search the marketplace for Fuse, Fabric, Fabric8 or Camel they don't find JBoss products. We should add those keywords to JBT and JBDS. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17964) add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17964?page=com.atlassian.jira.plugi... ] Paul Leacu commented on JBIDE-17964: ------------------------------------ I meant the JBDSIS update site - I don't know what a "solution" description link typically pointed to. > add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric > ------------------------------------------------------------------------------------------ > > Key: JBIDE-17964 > URL: https://issues.jboss.org/browse/JBIDE-17964 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 4.1.2.Final > Reporter: Lars Heinemann > Assignee: Nick Boldt > Fix For: 4.1.2.Final > > > Currently when people search the marketplace for Fuse, Fabric, Fabric8 or Camel they don't find JBoss products. We should add those keywords to JBT and JBDS. -- 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