October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23305) Reimplement org.jboss.tools.hibernate.runtime.v_x_y.internal.ConfigurationFacadeTest using the real Configuration object as the target

by Koen Aers (JIRA)

Koen Aers created JBIDE-23305: --------------------------------- Summary: Reimplement org.jboss.tools.hibernate.runtime.v_x_y.internal.ConfigurationFacadeTest using the real Configuration object as the target Key: JBIDE-23305 URL: https://issues.jboss.org/browse/JBIDE-23305 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Affects Versions: 4.4.2.AM1 Reporter: Koen Aers -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23302) https no longer working on tools.jboss.org

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23302?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-23302: --------------------------------------------- in these cases open issue with helpdesk/engservices immediatly - don't wait. They should help reveal if something changed around https. My understanding is that we did have https enabled before but i'm not 100% sure. A chance is also that [~marcel.bruch] changed which protocol he used in setup of the switching of error reporting but I can't find traces of how that was done in past. > https no longer working on tools.jboss.org > ------------------------------------------ > > Key: JBIDE-23302 > URL: https://issues.jboss.org/browse/JBIDE-23302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri, website > Reporter: Nick Boldt > Fix For: 4.4.2.AM2 > > > Is it expected that tools.jboss.org no longer provides https? > https keeps redirecting to http for me, so I'm getting errors in Eclipse as thrown by AERI, eg: > {code}Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.1.201608030901 > {code} > To see this in action, go here: > https://tools.jboss.org --> redirects to http://tools.jboss.org > or, go here: > https://tools.jboss.org:443/ --> redirects to http://tools.jboss.org > I bet this is a problem for eng-ops@ or the new PnT portal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23304) NullPointerException in TagLibraryManager.getStaticTLD

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23304?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-23304: -------------------------------------- Assignee: Victor Rubezhny > NullPointerException in TagLibraryManager.getStaticTLD > ------------------------------------------------------ > > Key: JBIDE-23304 > URL: https://issues.jboss.org/browse/JBIDE-23304 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jst > Reporter: Automated Error Reporting Bot > Assignee: Victor Rubezhny > > The following problem was reported via the automated error reporting: > Message: > {noformat} > java.lang.NullPointerException: null > at org.jboss.tools.jst.web.kb.taglib.TagLibraryManager.getStaticTLD(TagLibraryManager.java:101) > at org.jboss.tools.jst.web.kb.internal.StaticLibraries.getLibraries(StaticLibraries.java:44) > at org.jboss.tools.jst.web.kb.internal.KbProject.getTagLibraries(KbProject.java:135) > at org.jboss.tools.jst.web.kb.taglib.TagLibraryManager.getLibraries(TagLibraryManager.java:57) > at org.jboss.tools.jst.web.kb.PageContextFactory.fillXMLNamespacesForNode(PageContextFactory.java:1166) > at org.jboss.tools.jst.web.kb.PageContextFactory.fillContextForNode(PageContextFactory.java:869) > at org.jboss.tools.jst.web.kb.PageContextFactory.fillContextForChildNodes(PageContextFactory.java:858) > at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:602) > at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:403) > at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:392) > at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:381) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateFile(ELValidator.java:299) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateAll(ELValidator.java:241) > at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:165) > at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:84) > at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.10.1.v20150725-1910 | > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | > | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 | > | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 | > | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | > | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.10.0.v20150603-1752 | > | org.eclipse.ltk.core.refactoring | 3.6.201.v20150819-1034 | 3.6.201.v20150819-1034 | > | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.401.v201510130005 | > | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 | > | org.eclipse.wst.validation.ui | 1.2.500.v201310231452 | 1.2.500.v201310231452 | > | org.eclipse.wst.xml.ui | 1.1.501.v201501212057 | 1.1.501.v201501212057 | > | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.1.v20160624-2216 | > | org.jboss.tools.jsf.ui | 3.7.1.Final-v20160330-2256-B84 | 3.7.1.Final-v20160330-2256-B84 | > | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.1.v20160829-2118 | > | org.jboss.tools.jst.web.ui | 3.7.1.Final-v20160331-0256-B96 | 3.7.1.Final-v20160331-0256-B96 | > Operating Systems: > | MacOSX | 10.11.5 | 10.11.5 | > | Windows | 6.1.0 | 6.3.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/574c32dae4b06056d2...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23304) NullPointerException in TagLibraryManager.getStaticTLD

by Automated Error Reporting Bot (JIRA)

Automated Error Reporting Bot created JBIDE-23304: ----------------------------------------------------- Summary: NullPointerException in TagLibraryManager.getStaticTLD Key: JBIDE-23304 URL: https://issues.jboss.org/browse/JBIDE-23304 Project: Tools (JBoss Tools) Issue Type: Bug Components: jst Reporter: Automated Error Reporting Bot The following problem was reported via the automated error reporting: Message: {noformat} java.lang.NullPointerException: null at org.jboss.tools.jst.web.kb.taglib.TagLibraryManager.getStaticTLD(TagLibraryManager.java:101) at org.jboss.tools.jst.web.kb.internal.StaticLibraries.getLibraries(StaticLibraries.java:44) at org.jboss.tools.jst.web.kb.internal.KbProject.getTagLibraries(KbProject.java:135) at org.jboss.tools.jst.web.kb.taglib.TagLibraryManager.getLibraries(TagLibraryManager.java:57) at org.jboss.tools.jst.web.kb.PageContextFactory.fillXMLNamespacesForNode(PageContextFactory.java:1166) at org.jboss.tools.jst.web.kb.PageContextFactory.fillContextForNode(PageContextFactory.java:869) at org.jboss.tools.jst.web.kb.PageContextFactory.fillContextForChildNodes(PageContextFactory.java:858) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:602) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:403) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:392) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:381) at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateFile(ELValidator.java:299) at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateAll(ELValidator.java:241) at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:165) at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:84) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {noformat} Bundles: | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.10.1.v20150725-1910 | | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 | | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 | | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.10.0.v20150603-1752 | | org.eclipse.ltk.core.refactoring | 3.6.201.v20150819-1034 | 3.6.201.v20150819-1034 | | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.401.v201510130005 | | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 | | org.eclipse.wst.validation.ui | 1.2.500.v201310231452 | 1.2.500.v201310231452 | | org.eclipse.wst.xml.ui | 1.1.501.v201501212057 | 1.1.501.v201501212057 | | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.1.v20160624-2216 | | org.jboss.tools.jsf.ui | 3.7.1.Final-v20160330-2256-B84 | 3.7.1.Final-v20160330-2256-B84 | | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.1.v20160829-2118 | | org.jboss.tools.jst.web.ui | 3.7.1.Final-v20160331-0256-B96 | 3.7.1.Final-v20160331-0256-B96 | Operating Systems: | MacOSX | 10.11.5 | 10.11.5 | | Windows | 6.1.0 | 6.3.0 | The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/574c32dae4b06056d2...] for the latest data. Thank you for your assistance. Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4098) Support OpenShift 3.3

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4098?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBDS-4098: --------------------------------------- these are 2 good news, cool :-) > Support OpenShift 3.3 > --------------------- > > Key: JBDS-4098 > URL: https://issues.jboss.org/browse/JBDS-4098 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: openshift > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > > iPaas Fuse is using Openshift 3.3 > In order to improve Eclipse Fuse Tooling to work with iPaas Fuse, JBDS need to support OpenShift 3.3 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4098) Support OpenShift 3.3

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4098?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-4098: ------------------------------------ Assignee: Jeff MAURY (was: Alexey Kazakov) Our Tools should be fine with OS 3.3 but we at least need to test it carefully. And btw CDK is planning to switch to OS 3.3 for the next version too. > Support OpenShift 3.3 > --------------------- > > Key: JBDS-4098 > URL: https://issues.jboss.org/browse/JBDS-4098 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: openshift > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > > iPaas Fuse is using Openshift 3.3 > In order to improve Eclipse Fuse Tooling to work with iPaas Fuse, JBDS need to support OpenShift 3.3 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4100) Run PR checks for Windows and Mac

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4100: ----------------------------------- Summary: Run PR checks for Windows and Mac Key: JBDS-4100 URL: https://issues.jboss.org/browse/JBDS-4100 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.2.0.AM2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 10.2.0.AM3 Attachments: pr-checks.png Now PR's are verified only for Windows !pr-checks.png! When Mac build is ready we have to create checks for Mac as well and rename checks to show what platform was used for verification. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4099) DevStudio does not start from installer on Mac

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4099: ----------------------------------- Summary: DevStudio does not start from installer on Mac Key: JBDS-4099 URL: https://issues.jboss.org/browse/JBDS-4099 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.2.0.AM2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 10.2.0.AM2 That happens because we use .vbs script to copy environment variables to current process so running Devstudio would see them. This is windows specific code and fails on Mac. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3815) Folder validation inconsistency

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3815?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3815. --------------------------------- Resolution: Done > Folder validation inconsistency > ------------------------------- > > Key: JBDS-3815 > URL: https://issues.jboss.org/browse/JBDS-3815 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Labels: havoc > Fix For: 10.2.0.AM2 > > > - '/' or '\' as the is accepted and resolves to 'c:\' but using '\folder' or '/folder' is not accepted > - forward and back-slashes are interchangable, meaning you can create valid paths like 'c:\/\/\/\/\/\/a/\/\/\/sd/\/\/\/f\/\/\/g\/\a\/a\/d\///\s\a/a\' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3815) Folder validation inconsistency

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3815?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3815: ------------------------------------- Cannot replicate this because format validation kick is an reports that path has wrong format. > Folder validation inconsistency > ------------------------------- > > Key: JBDS-3815 > URL: https://issues.jboss.org/browse/JBDS-3815 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Labels: havoc > Fix For: 10.2.0.AM2 > > > - '/' or '\' as the is accepted and resolves to 'c:\' but using '\folder' or '/folder' is not accepted > - forward and back-slashes are interchangable, meaning you can create valid paths like 'c:\/\/\/\/\/\/a/\/\/\/sd/\/\/\/f\/\/\/g\/\a\/a\/d\///\s\a/a\' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 October 2016