November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21092) Application wizard: Warn when a template points Source URL to a parameter with empty value

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21092?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21092: --------------------------------------- Because the source value is just a parameter like any other that is supported by the template, we can not validate for emptiness, only that it is required. These parameters could be consumed by something like a deployment config which would pass that info to the resulting Docker image. Empty values is a valid use case depending upon how the image author consumes them. The parameter should either be marked required or the template author should accept they may get empty source values. > Application wizard: Warn when a template points Source URL to a parameter with empty value > ------------------------------------------------------------------------------------------- > > Key: JBIDE-21092 > URL: https://issues.jboss.org/browse/JBIDE-21092 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jan Richter > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > > If a template defines a parameter for Source URL {noformat}(i.e. Source_URL = ${GIT_URI}){noformat} but leaves it empty, the application wizard can be finished, but in the end the application creation fails because of the missing URL. > It might be better to validate if the actual value passed is not empty. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-531) Bouncy Castle causes Fuse Tooling full source TP build failure.

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBTIS-531: -------------------------------------- SNAPSHOT are volatile, and Nexus removes them from time to time, and when there is a release for this version. > Bouncy Castle causes Fuse Tooling full source TP build failure. > --------------------------------------------------------------- > > Key: JBTIS-531 > URL: https://issues.jboss.org/browse/JBTIS-531 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 8.0.4.CR2, 9.0.0.Alpha2 > Reporter: Paul Leacu > Assignee: Paul Richardson > Priority: Blocker > Attachments: TP-issues.png > > > Here is the issue. The JBTIS TP has a reliance on bouncycastle that was introduced as an indirect dependency by Teiid Designer because they needed the Apache directory features including the org.apache.directory.studio.connection.ui feature. The bcprov feature was removed from the JBTIS TP and Teiid Designer added a dummy feature to satisfy maven. This was built and everything in the IS builds and installs fine - no one directly needed bouncycastle. > Fuse Tooling builds a local development-only full source target platform based on the JBTIS TP. This causes all dependencies to be fully resolved which causes them to fail their target platform development-only build: > {code} > mvn -Pmultiple2repo -U -Dmirror-target-to-repo.includeSources=true clean install > ... > [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618 > [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.x509.extension 0.0.0' but it could not be found > {code} > you may also see this error: > {code} > [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618 > [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.asn1 0.0.0' but it could not be found > {code} > Both of these plugins can be found (in stub form) here: > http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... > How should this be fixed? Both Teiid Designer and Fuse Tooling use the JBTIS TP. Fuse needs this development TP to debug Fuse and SAP issues. They shouldn't have to incur a dependency that has nothing to do with them. If we pull the entire Apache directory dependency block out of the IS TP then Teiid Des will have to go back to creating their own merged TP. > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-531) Bouncy Castle causes Fuse Tooling full source TP build failure.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky edited comment on JBTIS-531 at 11/16/15 7:36 AM: ------------------------------------------------------------------- I noticed that the commit https://github.com/jbosstools/jbosstools-integration-stack/commit/e230add... updated the locus update site from https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo... to http://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/loc... Why was the SNAPSHOT site deleted? Currently I'm not able to build for example fuse tooling, see FUSETOOLS-1531 (unless I locally build the TP) was (Author: apodhrad): I noticed that the commit https://github.com/jbosstools/jbosstools-integration-stack/commit/e230add... updated the locus update site from https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo... to http://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/loc... Why was the SNAPSHOT site deleted? Currently I'm not able to build for example fuse tooling, see FUSETOOLS-1531 > Bouncy Castle causes Fuse Tooling full source TP build failure. > --------------------------------------------------------------- > > Key: JBTIS-531 > URL: https://issues.jboss.org/browse/JBTIS-531 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 8.0.4.CR2, 9.0.0.Alpha2 > Reporter: Paul Leacu > Assignee: Paul Richardson > Priority: Blocker > Attachments: TP-issues.png > > > Here is the issue. The JBTIS TP has a reliance on bouncycastle that was introduced as an indirect dependency by Teiid Designer because they needed the Apache directory features including the org.apache.directory.studio.connection.ui feature. The bcprov feature was removed from the JBTIS TP and Teiid Designer added a dummy feature to satisfy maven. This was built and everything in the IS builds and installs fine - no one directly needed bouncycastle. > Fuse Tooling builds a local development-only full source target platform based on the JBTIS TP. This causes all dependencies to be fully resolved which causes them to fail their target platform development-only build: > {code} > mvn -Pmultiple2repo -U -Dmirror-target-to-repo.includeSources=true clean install > ... > [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618 > [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.x509.extension 0.0.0' but it could not be found > {code} > you may also see this error: > {code} > [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618 > [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.asn1 0.0.0' but it could not be found > {code} > Both of these plugins can be found (in stub form) here: > http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... > How should this be fixed? Both Teiid Designer and Fuse Tooling use the JBTIS TP. Fuse needs this development TP to debug Fuse and SAP issues. They shouldn't have to incur a dependency that has nothing to do with them. If we pull the entire Apache directory dependency block out of the IS TP then Teiid Des will have to go back to creating their own merged TP. > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-531) Bouncy Castle causes Fuse Tooling full source TP build failure.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-531: ----------------------------------------- I noticed that the commit https://github.com/jbosstools/jbosstools-integration-stack/commit/e230add... updated the locus update site from https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo... to http://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/loc... Why was the SNAPSHOT site deleted? Currently I'm not able to build for example fuse tooling, see FUSETOOLS-1531 > Bouncy Castle causes Fuse Tooling full source TP build failure. > --------------------------------------------------------------- > > Key: JBTIS-531 > URL: https://issues.jboss.org/browse/JBTIS-531 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 8.0.4.CR2, 9.0.0.Alpha2 > Reporter: Paul Leacu > Assignee: Paul Richardson > Priority: Blocker > Attachments: TP-issues.png > > > Here is the issue. The JBTIS TP has a reliance on bouncycastle that was introduced as an indirect dependency by Teiid Designer because they needed the Apache directory features including the org.apache.directory.studio.connection.ui feature. The bcprov feature was removed from the JBTIS TP and Teiid Designer added a dummy feature to satisfy maven. This was built and everything in the IS builds and installs fine - no one directly needed bouncycastle. > Fuse Tooling builds a local development-only full source target platform based on the JBTIS TP. This causes all dependencies to be fully resolved which causes them to fail their target platform development-only build: > {code} > mvn -Pmultiple2repo -U -Dmirror-target-to-repo.includeSources=true clean install > ... > [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618 > [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.x509.extension 0.0.0' but it could not be found > {code} > you may also see this error: > {code} > [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618 > [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.asn1 0.0.0' but it could not be found > {code} > Both of these plugins can be found (in stub form) here: > http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... > How should this be fixed? Both Teiid Designer and Fuse Tooling use the JBTIS TP. Fuse needs this development TP to debug Fuse and SAP issues. They shouldn't have to incur a dependency that has nothing to do with them. If we pull the entire Apache directory dependency block out of the IS TP then Teiid Des will have to go back to creating their own merged TP. > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21096) Cannot extract central page when the user's home directory contains spaces

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21096?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-21096: ------------------------------------ Hi Fred, I've installed all from nightly aggregate site. And after the restart I saw the error. Here is the complete stackstrace: {code} java.lang.RuntimeException: java.net.URISyntaxException: Illegal character in path at index 19: file:/C:/Users/Pali Srna/.p2/pool/plugins/org.jboss.tools.central_2.0.1.Beta1-v20151110-2120-B55/resources/jbosstools-central-webpage.zip at org.jboss.tools.central.internal.CentralHelper.getEmbeddedCentralZipPath(CentralHelper.java:153) at org.jboss.tools.central.internal.CentralHelper.getCentralPageUrl(CentralHelper.java:115) at org.jboss.tools.central.internal.CentralHelper.getCentralUrl(CentralHelper.java:58) at org.jboss.tools.central.editors.GettingStartedHtmlPage$5.run(GettingStartedHtmlPage.java:251) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.net.URISyntaxException: Illegal character in path at index 19: file:/C:/Users/Pali Srna/.p2/pool/plugins/org.jboss.tools.central_2.0.1.Beta1-v20151110-2120-B55/resources/jbosstools-central-webpage.zip at java.net.URI$Parser.fail(URI.java:2848) at java.net.URI$Parser.checkChars(URI.java:3021) at java.net.URI$Parser.parseHierarchical(URI.java:3105) at java.net.URI$Parser.parse(URI.java:3053) at java.net.URI.<init>(URI.java:588) at java.net.URL.toURI(URL.java:939) at org.jboss.tools.central.internal.CentralHelper.getEmbeddedCentralZipPath(CentralHelper.java:151) ... 4 more {code} > Cannot extract central page when the user's home directory contains spaces > -------------------------------------------------------------------------- > > Key: JBIDE-21096 > URL: https://issues.jboss.org/browse/JBIDE-21096 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.1.Beta1 > Environment: Windows 8.1, Mars.1 Release (4.5.1), http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... > Reporter: Pavol Srna > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.Beta1 > > Attachments: central.png > > > {code} > An internal error occurred during: "Extract Central page". > java.net.URISyntaxException: Illegal character in path at index 19: file:/C:/Users/Pali Srna/.p2/pool/plugins/org.jboss.tools.central_2.0.1.Beta1-v20151110-2120-B55/resources/jbosstools-central-webpage.zip > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-691) JBDS 9.1 Beta1: Install Guide Review

by Misha Ali (JIRA)

Misha Ali created TOOLSDOC-691: ---------------------------------- Summary: JBDS 9.1 Beta1: Install Guide Review Key: TOOLSDOC-691 URL: https://issues.jboss.org/browse/TOOLSDOC-691 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Reporter: Misha Ali Assignee: Misha Ali -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21099) ModelUiPreferencesPageTest.testEditorsPreferencesPage failure

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-21099: -------------------------------------- Summary: ModelUiPreferencesPageTest.testEditorsPreferencesPage failure Key: JBIDE-21099 URL: https://issues.jboss.org/browse/JBIDE-21099 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.4.0.Alpha1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.4.0.Alpha1 Failed tests: ModelUiPreferencesPageTest.testEditorsPreferencesPage:53->PreferencePageTest.doDefaultTest:49 Selected page is not an instance of PreferencePage -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21092) Application wizard: Warn when a template points Source URL to a parameter with empty value

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21092?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-21092. -------------------------------------- Fix Version/s: 4.3.1.Beta1 Assignee: Andre Dietisheim Resolution: Done > Application wizard: Warn when a template points Source URL to a parameter with empty value > ------------------------------------------------------------------------------------------- > > Key: JBIDE-21092 > URL: https://issues.jboss.org/browse/JBIDE-21092 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jan Richter > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > > If a template defines a parameter for Source URL {noformat}(i.e. Source_URL = ${GIT_URI}){noformat} but leaves it empty, the application wizard can be finished, but in the end the application creation fails because of the missing URL. > It might be better to validate if the actual value passed is not empty. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21092) Application wizard: Warn when a template points Source URL to a parameter with empty value

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21092?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-21092. ------------------------------------ > Application wizard: Warn when a template points Source URL to a parameter with empty value > ------------------------------------------------------------------------------------------- > > Key: JBIDE-21092 > URL: https://issues.jboss.org/browse/JBIDE-21092 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jan Richter > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > > If a template defines a parameter for Source URL {noformat}(i.e. Source_URL = ${GIT_URI}){noformat} but leaves it empty, the application wizard can be finished, but in the end the application creation fails because of the missing URL. > It might be better to validate if the actual value passed is not empty. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21092) Application wizard: Warn when a template points Source URL to a parameter with empty value

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21092?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21092: ------------------------------------------ [~fbricon] ok, thanks for confirming. > Application wizard: Warn when a template points Source URL to a parameter with empty value > ------------------------------------------------------------------------------------------- > > Key: JBIDE-21092 > URL: https://issues.jboss.org/browse/JBIDE-21092 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jan Richter > Labels: application_wizard, openshift_v3 > > If a template defines a parameter for Source URL {noformat}(i.e. Source_URL = ${GIT_URI}){noformat} but leaves it empty, the application wizard can be finished, but in the end the application creation fails because of the missing URL. > It might be better to validate if the actual value passed is not empty. -- 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 November 2015