September 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2665) Link under 'Other resources' on JBoss Central is incorrect for JBDS

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2665?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2665: ------------------------------ Fix Version/s: 7.1.0.Alpha2 > Link under 'Other resources' on JBoss Central is incorrect for JBDS > ------------------------------------------------------------------- > > Key: JBDS-2665 > URL: https://issues.jboss.org/browse/JBDS-2665 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Reporter: Michelle Murray > Assignee: Fred Bricon > Fix For: 7.0.0.Beta2, 7.1.0.Alpha2 > > > I realise that JBoss Central is still under development but I wanted to point out an issue. Under 'Other resources' there is a link titled 'Product documentation' that links to http://docs.jboss.org/tools/latest/. > 1. Is this the right link for community docs? /tools/latest will store documentation under development for the next release. Should this link point to the community docs for the version of JBT installed (for example, tools/4.1.0 for JBT 4.1.0)? There is ongoing debate about what exactly the link will be - see TOOLSDOC-310. > 2. This link does not point to the right place for JBDS users. JBDS documentation is stored here: https://access.redhat.com/site/documentation/JBoss_Developer_Studio/ So how can the issue of two separate documentation locations for JBT and JBDS be got around? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2665) Link under 'Other resources' on JBoss Central is incorrect for JBDS

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2665?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2665: ------------------------------ Fix Version/s: (was: 7.1.0.Alpha2) > Link under 'Other resources' on JBoss Central is incorrect for JBDS > ------------------------------------------------------------------- > > Key: JBDS-2665 > URL: https://issues.jboss.org/browse/JBDS-2665 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Reporter: Michelle Murray > Assignee: Fred Bricon > Labels: respin-a > Fix For: 7.0.0.Beta2 > > > I realise that JBoss Central is still under development but I wanted to point out an issue. Under 'Other resources' there is a link titled 'Product documentation' that links to http://docs.jboss.org/tools/latest/. > 1. Is this the right link for community docs? /tools/latest will store documentation under development for the next release. Should this link point to the community docs for the version of JBT installed (for example, tools/4.1.0 for JBT 4.1.0)? There is ongoing debate about what exactly the link will be - see TOOLSDOC-310. > 2. This link does not point to the right place for JBDS users. JBDS documentation is stored here: https://access.redhat.com/site/documentation/JBoss_Developer_Studio/ So how can the issue of two separate documentation locations for JBT and JBDS be got around? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2665) Link under 'Other resources' on JBoss Central is incorrect for JBDS

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2665?page=com.atlassian.jira.plugin.... ] Fred Bricon resolved JBDS-2665. ------------------------------- Fix Version/s: 7.1.0.Alpha2 Resolution: Done There was a snafu with the link fix (not applied in the proper branches). I applied the commit to master and jbosstools-4.1.x > Link under 'Other resources' on JBoss Central is incorrect for JBDS > ------------------------------------------------------------------- > > Key: JBDS-2665 > URL: https://issues.jboss.org/browse/JBDS-2665 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Reporter: Michelle Murray > Assignee: Fred Bricon > Labels: respin-a > Fix For: 7.1.0.Alpha2, 7.0.0.Beta2 > > > I realise that JBoss Central is still under development but I wanted to point out an issue. Under 'Other resources' there is a link titled 'Product documentation' that links to http://docs.jboss.org/tools/latest/. > 1. Is this the right link for community docs? /tools/latest will store documentation under development for the next release. Should this link point to the community docs for the version of JBT installed (for example, tools/4.1.0 for JBT 4.1.0)? There is ongoing debate about what exactly the link will be - see TOOLSDOC-310. > 2. This link does not point to the right place for JBDS users. JBDS documentation is stored here: https://access.redhat.com/site/documentation/JBoss_Developer_Studio/ So how can the issue of two separate documentation locations for JBT and JBDS be got around? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15491) Update wildfly management bundle to include wf-alpha4 jars (and test them)

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-15491: ----------------------------------- Summary: Update wildfly management bundle to include wf-alpha4 jars (and test them) Key: JBIDE-15491 URL: https://issues.jboss.org/browse/JBIDE-15491 Project: Tools (JBoss Tools) Issue Type: Task Components: server Affects Versions: 4.2.0.Alpha1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.2.0.Alpha1 Update the jars, classpath, pom.xml, etc, and ensure the combination passes all tests -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-171) Don't override other connectors in discovery.xml

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-171: ---------------------------------- I was able to reproduce your problem using the Beta1 site. But I have a simpler solution, which uses the existing build.xml script to generate the staging discovery site that QE can use to perform an installation. I've fixed the two JBTIS and JBDSIS jobs [1], [2] so that they now pass in a value of UPSTREAM_EXTRAS_SITE to the composite site, which will therefore allow installation of JBDS Central and JBDS IS Central content from a single overriding URL. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-aggregate-disc/ [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBDSIS-aggregate-disc/ To verify this is fixed, try one of these URLs when configuring jbdevstudio.ini: {code} -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1a/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1a/ {code} or {code} -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta2a/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta2a/ {code} The benefit here is that the job can now be configured when run to produce a composite site which is a mix of any specific upstream versions of JBDS+Central+TP or JBT+Central+TP (or simply use the latest changing released version). So we can produce a staging discovery site that would target JBDS 7.0 or 7.1, simply by re-running the job. > Don't override other connectors in discovery.xml > ------------------------------------------------ > > Key: JBTIS-171 > URL: https://issues.jboss.org/browse/JBTIS-171 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > > Currently this is in discovery plugin: > siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}" > > And instructions to test it says: > -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1 > This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together. > I suggest you use your own specific site url instead, something like: > siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}" > Then the base connectors will still work. > We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of: > in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}" > in stack: > siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15488) Web Service Tester doesn't work with https and self-signed certificate

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15488?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-15488: ------------------------------------------- Do we have anything else? Any exception in the log file? > Web Service Tester doesn't work with https and self-signed certificate > ---------------------------------------------------------------------- > > Key: JBIDE-15488 > URL: https://issues.jboss.org/browse/JBIDE-15488 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Juergen Zimmermann > Assignee: Brian Fitzpatrick > > If I test a RESTful Web Service on WildFly 8 which is configured for https, then I just this error message in the response body (for both GET and POST requests): > {code} > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15488) Web Service Tester doesn't work with https and self-signed certificate

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15488?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick reassigned JBIDE-15488: ----------------------------------------- Assignee: Brian Fitzpatrick > Web Service Tester doesn't work with https and self-signed certificate > ---------------------------------------------------------------------- > > Key: JBIDE-15488 > URL: https://issues.jboss.org/browse/JBIDE-15488 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Juergen Zimmermann > Assignee: Brian Fitzpatrick > > If I test a RESTful Web Service on WildFly 8 which is configured for https, then I just this error message in the response body (for both GET and POST requests): > {code} > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-165) Regression - Cannot add a file to the attachments

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-165?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-165: ----------------------------------------- Merged into master, but forgot 4.1.x. Now merged into 4.1.x as well. > Regression - Cannot add a file to the attachments > ------------------------------------------------- > > Key: JBTIS-165 > URL: https://issues.jboss.org/browse/JBTIS-165 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.1.2 > Environment: JBoss ESB Tools 1.5.300.Final-v20130815-1755-B1189 > Reporter: Andrej Podhradsky > Assignee: Viacheslav Kabanovich > Priority: Blocker > Attachments: esb_attachment_bug.png, test.zip > > > Cannot add a file to the attachments from esbcontent folder. It's also impossible to add .txt file from the root but .zip file is possible to add. See the screenshot -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2714) JBDS 7 Core refers to an installable package's category as "JBoss Data Services" - but this is not JBoss EDS

by Jakub Niedermertl (JIRA)

[ https://issues.jboss.org/browse/JBDS-2714?page=com.atlassian.jira.plugin.... ] Jakub Niedermertl closed JBDS-2714. ----------------------------------- verified, ok JBoss Tools 4.1.1.Alpha1 > JBDS 7 Core refers to an installable package's category as "JBoss Data Services" - but this is not JBoss EDS > ------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2714 > URL: https://issues.jboss.org/browse/JBDS-2714 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build > Affects Versions: 7.0.0.GA > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Critical > Fix For: 7.1.0.Alpha1 > > Attachments: Screenshot-DS.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15334) Use Java5 method to check if String is empty

by Jakub Niedermertl (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15334?page=com.atlassian.jira.plugi... ] Jakub Niedermertl closed JBIDE-15334. ------------------------------------- Resolution: Done Reopened for fix version change; closing. > Use Java5 method to check if String is empty > -------------------------------------------- > > Key: JBIDE-15334 > URL: https://issues.jboss.org/browse/JBIDE-15334 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.1.1.Alpha1 > > > When importing some Archive projects in a workspace where a Java5 JRE exists, there is a compilation error because of the use of String#isEmpty() which is defined in Java6+ > Steps to reproduce: > Import the Archives projects in a workspace where a JRE5 exists > Assert: no compilation error > Fail: compilation errors in archives/plugins/org.jboss.ide.eclipse.archives.core/src/main/org/jboss/ide/eclipse/archives/core/model/interna/xb/XMLBinding.java > because String#isEmpty() was defined in Java6 > The problem does not appear if the workspace is configured with a Java6 (or more) JRE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 2013