September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20100: ------------------------------------ Link to JBDS-3509. > how to make users aware of fuse and other tooling only being available from earlyaccess? > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20100 > URL: https://issues.jboss.org/browse/JBIDE-20100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.CR1 > > Attachments: JBIDE-20100-2.png > > > [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page. > Some comments: > "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list." > "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something." > Suggestion: > "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature." > I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ? > and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ? > But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9) > [~crobson], [~aileenc] and [~lhein] got any suggestions ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3510) Consider including Buildship in JBT/JBDS - add new connector to Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3510?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3510: ----------------------------------- -1 from me. Not until it gets WTP support. > Consider including Buildship in JBT/JBDS - add new connector to Central > ----------------------------------------------------------------------- > > Key: JBDS-3510 > URL: https://issues.jboss.org/browse/JBDS-3510 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: 3rd-party-certification, 3rd-party-dependencies, central, discovery > Affects Versions: 9.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > {quote} > support for Gradle via BuildShip project is set to be included in Eclipse Mars SR1. > Something we probably need to at least test/coexist with in near future. > /max{quote} > Info: > * https://gradle.org/eclipse/ > * https://projects.eclipse.org/projects/tools.buildship > Update sites: > * http://download.eclipse.org/buildship/updates/e45/releases > * http://download.eclipse.org/buildship/updates/e45/milestones/1.0 > * http://download.eclipse.org/buildship/updates/e45/snapshots/1.0 > (also should be in Mars.1 release [1] coming out in a few weeks) > [1] https://wiki.eclipse.org/Mars/Simultaneous_Release_Plan#Mars.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3510) Consider including Buildship in JBT/JBDS - add new connector to Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3510?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3510: ----------------------------- Summary: Consider including Buildship in JBT/JBDS - add new connector to Central (was: Consider including Buildship in JBT/JBDS) > Consider including Buildship in JBT/JBDS - add new connector to Central > ----------------------------------------------------------------------- > > Key: JBDS-3510 > URL: https://issues.jboss.org/browse/JBDS-3510 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: 3rd-party-certification, 3rd-party-dependencies, central, discovery > Affects Versions: 9.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > {quote} > support for Gradle via BuildShip project is set to be included in Eclipse Mars SR1. > Something we probably need to at least test/coexist with in near future. > /max{quote} > Info: > * https://gradle.org/eclipse/ > * https://projects.eclipse.org/projects/tools.buildship > Update sites: > * http://download.eclipse.org/buildship/updates/e45/releases > * http://download.eclipse.org/buildship/updates/e45/milestones/1.0 > * http://download.eclipse.org/buildship/updates/e45/snapshots/1.0 > (also should be in Mars.1 release [1] coming out in a few weeks) > [1] https://wiki.eclipse.org/Mars/Simultaneous_Release_Plan#Mars.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3510) Consider including Buildship in JBT/JBDS

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3510?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3510: ----------------------------- CDW pm_ack: ? CDW release: ? > Consider including Buildship in JBT/JBDS > ---------------------------------------- > > Key: JBDS-3510 > URL: https://issues.jboss.org/browse/JBDS-3510 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: 3rd-party-certification, 3rd-party-dependencies, central, discovery > Affects Versions: 9.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > {quote} > support for Gradle via BuildShip project is set to be included in Eclipse Mars SR1. > Something we probably need to at least test/coexist with in near future. > /max{quote} > Info: > * https://gradle.org/eclipse/ > * https://projects.eclipse.org/projects/tools.buildship > Update sites: > * http://download.eclipse.org/buildship/updates/e45/releases > * http://download.eclipse.org/buildship/updates/e45/milestones/1.0 > * http://download.eclipse.org/buildship/updates/e45/snapshots/1.0 > (also should be in Mars.1 release [1] coming out in a few weeks) > [1] https://wiki.eclipse.org/Mars/Simultaneous_Release_Plan#Mars.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3510) Consider including Buildship in JBT/JBDS

by Nick Boldt (JIRA)

Nick Boldt created JBDS-3510: -------------------------------- Summary: Consider including Buildship in JBT/JBDS Key: JBDS-3510 URL: https://issues.jboss.org/browse/JBDS-3510 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: 3rd-party-certification, 3rd-party-dependencies, central, discovery Affects Versions: 9.0.0.CR1 Reporter: Nick Boldt Assignee: Nick Boldt {quote} support for Gradle via BuildShip project is set to be included in Eclipse Mars SR1. Something we probably need to at least test/coexist with in near future. /max{quote} Info: * https://gradle.org/eclipse/ * https://projects.eclipse.org/projects/tools.buildship Update sites: * http://download.eclipse.org/buildship/updates/e45/releases * http://download.eclipse.org/buildship/updates/e45/milestones/1.0 * http://download.eclipse.org/buildship/updates/e45/snapshots/1.0 (also should be in Mars.1 release [1] coming out in a few weeks) [1] https://wiki.eclipse.org/Mars/Simultaneous_Release_Plan#Mars.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-47) Locus plug-ins have errors after importing into workspace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/LOCUS-47?page=com.atlassian.jira.plugin.s... ] Nick Boldt commented on LOCUS-47: --------------------------------- Move from JBIDE to LOCUS. Set fixversion 1.3.0 but that might have to be 1.4.0 -- not sure when we plan to release 1.3.0. > Locus plug-ins have errors after importing into workspace > --------------------------------------------------------- > > Key: LOCUS-47 > URL: https://issues.jboss.org/browse/LOCUS-47 > Project: JBoss Tools Locus > Issue Type: Enhancement > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 1.3.0 > > > There are several problems with locus plrojects after importing them into workspace as maven projects: > 1. plugins/pom.xml appears in workspace with name "plugins" and it could conflict with other imported modules because we have the same names all over jbosstools; > 2. org.jboss.tools.locus.mockito uses restricted API and JDT reports it as Error; > 3. org.jboss.tools.locus.dmr export packages that created during maven build and reported as missing in eclipse. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-47) Locus plug-ins have errors after importing into workspace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/LOCUS-47?page=com.atlassian.jira.plugin.s... ] Nick Boldt updated LOCUS-47: ---------------------------- Project: JBoss Tools Locus (was: Tools (JBoss Tools)) Key: LOCUS-47 (was: JBIDE-20191) Component/s: (was: build) Affects Version/s: (was: 4.3.0.Beta1) Fix Version/s: 1.3.0 (was: 4.4.x) > Locus plug-ins have errors after importing into workspace > --------------------------------------------------------- > > Key: LOCUS-47 > URL: https://issues.jboss.org/browse/LOCUS-47 > Project: JBoss Tools Locus > Issue Type: Enhancement > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 1.3.0 > > > There are several problems with locus plrojects after importing them into workspace as maven projects: > 1. plugins/pom.xml appears in workspace with name "plugins" and it could conflict with other imported modules because we have the same names all over jbosstools; > 2. org.jboss.tools.locus.mockito uses restricted API and JDT reports it as Error; > 3. org.jboss.tools.locus.dmr export packages that created during maven build and reported as missing in eclipse. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20380) The current implemetnation of JDF REST service may cause downloading incorrect content

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20380?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20380: --------------------------------------------- I see no reason why 302 is not okey. only our response would contain headers to follow further, right? > The current implemetnation of JDF REST service may cause downloading incorrect content > -------------------------------------------------------------------------------------- > > Key: JBIDE-20380 > URL: https://issues.jboss.org/browse/JBIDE-20380 > Project: Tools (JBoss Tools) > Issue Type: Quality Risk > Components: server > Reporter: David Hladky > > The Eclipse wizard created by [~rob.stryker] uses https://www.jboss.org/download-manager/jdf rest service. > The problem is in the wizard the final step is identified by 302 response from the server, which is problematic, because not only the rest service itself can return 302, also other infrastructure can add its 302, such as an internet access in a hotel requesting payment for the connection. > There is no way where the 302 response is coming from and therefore we should use safer approach. > I described the problem in detail [here|https://mojo.redhat.com/docs/DOC-967368] - see the chapter Entry Point In Eclipse Plugin (REST) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-488) JBTIS/JBDSIS target platform contains old version of org.jboss.tools.foundation.security.linux.feature; needs update to latest

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-488?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-488: ---------------------------------- That's not really an error as much as a notification/warning. "You can't install the old stuff because JBDS already includes a newer version" is only a nuissance, but we should definitely have the latest JBT/JBDS stuff in the IS target platforms so as to avoid this. Once 9 CR1 is out, you can pull those bits and be more up to date. > JBTIS/JBDSIS target platform contains old version of org.jboss.tools.foundation.security.linux.feature; needs update to latest > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-488 > URL: https://issues.jboss.org/browse/JBTIS-488 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > > Update site at > http://www.qa.jboss.com/binaries/RHDS/mars/development/updates/integratio... > contains > org.jboss.tools.foundation.security.linux_1.1.2.Final-v20150325-0456-B99 > but JBDS 9 contains org.jboss.tools.foundation.security.linux_1.2.0.Beta2-v20150724-1456-B25. So, if we try to install all features (uncheck 'Group items by category'), we will get an error > Cannot complete the request. See the error log for details. > "JBoss Tools Foundation Security for Linux" will be ignored because a newer version is already installed. > This feature is required by Teiid Designer and it was included in JBTIS-112 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-488) JBTIS/JBDSIS target platform contains old version of org.jboss.tools.foundation.security.linux.feature; needs update to latest

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-488?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-488: ----------------------------- Summary: JBTIS/JBDSIS target platform contains old version of org.jboss.tools.foundation.security.linux.feature; needs update to latest (was: Update site contains old org.jboss.tools.foundation.security.linux.feature) > JBTIS/JBDSIS target platform contains old version of org.jboss.tools.foundation.security.linux.feature; needs update to latest > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-488 > URL: https://issues.jboss.org/browse/JBTIS-488 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > > Update site at > http://www.qa.jboss.com/binaries/RHDS/mars/development/updates/integratio... > contains > org.jboss.tools.foundation.security.linux_1.1.2.Final-v20150325-0456-B99 > but JBDS 9 contains org.jboss.tools.foundation.security.linux_1.2.0.Beta2-v20150724-1456-B25. So, if we try to install all features (uncheck 'Group items by category'), we will get an error > Cannot complete the request. See the error log for details. > "JBoss Tools Foundation Security for Linux" will be ignored because a newer version is already installed. > This feature is required by Teiid Designer and it was included in JBTIS-112 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 September 2015