December 2015 - jbosstools-issues

[JBoss JIRA] (JBTIS-537) Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector)

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBTIS-537?page=com.atlassian.jira.plugin.... ] Radim Hopp commented on JBTIS-537: ---------------------------------- [~pleacu] it looks like this was fixed by JBTIS-529. I tried it today with jbdevstudio-9.0.0-CVE-2015-7501 and it seems ok. > Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-537 > URL: https://issues.jboss.org/browse/JBTIS-537 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 4.3.0.Final > Environment: JBDS 9.0.0 > Reporter: Radim Hopp > Assignee: Paul Leacu > Priority: Critical > Attachments: fuse1.png, fuse2.png, fuse3.png, fuse4.png, fuse5.png, fuse6.png > > > I'm unable to import Fuse Integration Project from Central, when Fuse tooling isn't installed (but is available in EA). > This might be split to two issues: > 1) EA is disabled -> Fuse Integration Project should not appear in Central or at least it should tell user to enable EA to be able to install needed fuse tooling. > 2) EA is enabled -> After clicking on "Fuse Integration Project" user is prompted to install necessary connectors (The required features to use this wizard need to be installed."). After clicking on "Yes", error occurs: > {noformat} > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > {noformat} > {noformat} > java.lang.IllegalArgumentException: There are no connectors to install > at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:109) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > {noformat} > Note: When Fuse tooling is already installed, everything is ok . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21267) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21267?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21267: ---------------------------------------- I just checked the repositories and no change has happened on those 2 repositories since 4.3.0, so we don't need any new release. > For JBIDE 4.3.1.Beta1: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21267 > URL: https://issues.jboss.org/browse/JBIDE-21267 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks: > 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta1 > [Unresolved JIRAs with fixVersion = 4.3.1.Beta1, 9.1.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101 > *NOTE:* If you already did this earlier when we were preparing for Beta1 (after 4.3.0.Final was released), you do *not* need to do so again. > Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.1.Beta1-SNAPSHOT. > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.2.Beta1 (or 4.50.2.Beta1-SNAPSHOT). > {code} > mvn clean verify -Dtpc.version=4.50.2.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) > or > mvn clean verify -Dtpc.version=4.50.2.Beta1 # (if the TP is already released) > {code} > 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch; > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > git checkout -b jbosstools-4.3.1.Beta1x > git push origin jbosstools-4.3.1.Beta1x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*. > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > {code} > 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.Beta2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch, and > * *{color:orange}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21034) new Runtime detector fails to use default (ext-pt) enablement if user has previouslymodified enablement list

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21034?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21034: ------------------------------------- [~rob.stryker] I believe this issue can be resolved, amirite? > new Runtime detector fails to use default (ext-pt) enablement if user has previouslymodified enablement list > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21034 > URL: https://issues.jboss.org/browse/JBIDE-21034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1 > > > Small coding error causes a new runtime detector to not have its default enablement respected if a user has previously modified the enablement of any detector. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21034) new Runtime detector fails to use default (ext-pt) enablement if user has previouslymodified enablement list

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21034?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21034: ----------------------------------- Assignee: Rob Stryker > new Runtime detector fails to use default (ext-pt) enablement if user has previouslymodified enablement list > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21034 > URL: https://issues.jboss.org/browse/JBIDE-21034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1 > > > Small coding error causes a new runtime detector to not have its default enablement respected if a user has previously modified the enablement of any detector. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20991) support automatic setup of CDK start/stop server

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20991?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20991. --------------------------------- Resolution: Done CDK automatic detection has been added as part of JBIDE-20990 > support automatic setup of CDK start/stop server > ------------------------------------------------ > > Key: JBIDE-20991 > URL: https://issues.jboss.org/browse/JBIDE-20991 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1 > > > related to JBIDE-20990 it should be possible to automatically setup the CDK server based on what Installer have installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20991) support automatic setup of CDK start/stop server

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20991?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20991: ----------------------------------- Assignee: Rob Stryker > support automatic setup of CDK start/stop server > ------------------------------------------------ > > Key: JBIDE-20991 > URL: https://issues.jboss.org/browse/JBIDE-20991 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1 > > > related to JBIDE-20990 it should be possible to automatically setup the CDK server based on what Installer have installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3565) Include Target Platform Zip with JBDS for offline install on CSP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3565?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3565: ----------------------------- Fix Version/s: 9.1.0.Beta2 (was: 9.1.0.Beta1) > Include Target Platform Zip with JBDS for offline install on CSP > ---------------------------------------------------------------- > > Key: JBDS-3565 > URL: https://issues.jboss.org/browse/JBDS-3565 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.1.0.Beta1 > Environment: Customer Support Portal > Reporter: Mustafa Musaji > Assignee: Nick Boldt > Fix For: 9.1.0.Beta2 > > > Offline ZIP installation allows for JBDSIS tooling to be installed when there is no internet connection available. These zips for the JBDSIS and early access tooling is available from the CSP, however, some dependencies for this tooling is only available on the Target Platform zip. > This TP zip is only available on the jboss.org site https://devstudio.jboss.com/9.0/stable/updates/ and not on the customer portal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3560) Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3560?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3560: ----------------------------------- Future m2e 1.6.3, containing the fixed commons-collections-3.2.2 will be available for beta2. So we have to decide to either: - mark this issue as resolved in beta1 (even partially) and then focus on JBIDE-21119 - or punt resolution of this version to beta2 I would go with the 1st option, but don't have strong feelings about it. [~nickboldt]? > Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580) > ------------------------------------------------------------------------- > > Key: JBDS-3560 > URL: https://issues.jboss.org/browse/JBDS-3560 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 8.1.0.GA, 9.0.0.GA, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 9.0.0.Beta1, 10.0.0.Alpha1 > > Attachments: apache-commons-collections-in-JBDS7,8,9,10.png, apache-commons-collections-in-JBDS7,8,9,10_refs1.png, apache-commons-collections-in-JBDS7,8,9,10_refs10.png, apache-commons-collections-in-JBDS7,8,9,10_refs7.png, apache-commons-collections-in-JBDS7,8,9,10_refs8-IS-fuse.png, apache-commons-collections-in-JBDS7,8,9,10_refs8.png, apache-commons-collections-in-JBDS7,8,9,10_refs9.png, orbit.R20150519210750_vs_I20151117200049.log.txt, orbit.R20150519210750_vs_I20151117200049.log_onlyLatest.txt > > > This is a container issue to wrap & track https://issues.apache.org/jira/browse/COLLECTIONS-580 > Problem is that JBDS 9 (and probably 8 and 10 too) include org.apache.commons.collections 3.2.0.v2013030210310, which is affected by COLLECTIONS-580 - Arbitrary remote code execution with InvokerTransformer -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3565) Include Target Platform Zip with JBDS for offline install on CSP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3565?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3565: ---------------------------------- Denis raises a valid point that for offline installs of JBDS, the JBDS installer can be used (either run with the UI, headless via console, scripted to run headless over a wire, or even treated as an update site zip). So really the issue is that to perform an offline JBDS IS install, a user needs MORE than the JBDS installer + JBDS IS zip. Perhaps we should be looking at what 3rd party dependencies are missing from the JBDS IS zip and adding those IUs to that zip? > Include Target Platform Zip with JBDS for offline install on CSP > ---------------------------------------------------------------- > > Key: JBDS-3565 > URL: https://issues.jboss.org/browse/JBDS-3565 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.1.0.Beta1 > Environment: Customer Support Portal > Reporter: Mustafa Musaji > Assignee: Nick Boldt > Fix For: 9.1.0.Beta1 > > > Offline ZIP installation allows for JBDSIS tooling to be installed when there is no internet connection available. These zips for the JBDSIS and early access tooling is available from the CSP, however, some dependencies for this tooling is only available on the Target Platform zip. > This TP zip is only available on the jboss.org site https://devstudio.jboss.com/9.0/stable/updates/ and not on the customer portal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20761) Support editing Build Configuration parameters

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20761?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-20761: ----------------------------------------------- 1. Editor input should implement equals() to make sure that second invoking Open command selects already opened editor rather than opens new copy of it. 2. When Eclipse is closed/reopened, only those editors persist that return non-null IPersistableElement in getPersistable(). Editor input may implement IPersistableElement storing data that allows later to restore Connection and IResource. To restore editor, IElementFactory should be implemented and registered in extension org.eclipse.ui.elementFactories. 3. It would be cool to open JSON editor for resources that use that language. Validation, syntax colouring and other good things are too habitual to cope without. Plain text editor is in a gruesome contrast to other cool features. > Support editing Build Configuration parameters > ---------------------------------------------- > > Key: JBIDE-20761 > URL: https://issues.jboss.org/browse/JBIDE-20761 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1 > > > As a developer I want to be able to update the git url used in my existing OpenShift application buildconfig to use a different repository than what the default template used so I can publish my own changes to OS > Pre-Req: > - An application is deployed on OpenShift, using git for its source repository > Goal: > - Modify the git source url used to build and redeploy the application > Build Config parameters should be editable from either the Properties view (but how exactly?) or another mechanism from OpenShift Explorer (TBD) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 December 2015