June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-230) Registry accounts does not accept data with _ [EBZ#495070]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-230?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg closed ERT-230. ------------------------------- Fix Version/s: Neon (4.6) Assignee: Roland Grunberg Resolution: Done Fixed in Neon. See the original Eclipse Bug for more information. > Registry accounts does not accept data with _ [EBZ#495070] > ---------------------------------------------------------- > > Key: ERT-230 > URL: https://issues.jboss.org/browse/ERT-230 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Labels: Docker, bzira > Fix For: Neon (4.6) > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-767) Fix tests that use import dialogues for TD 10.0.1 (JBDS-IS 9.0.1)

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-767?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-767. ------------------------------ PR was pushed to master branch > Fix tests that use import dialogues for TD 10.0.1 (JBDS-IS 9.0.1) > ----------------------------------------------------------------- > > Key: JBTIS-767 > URL: https://issues.jboss.org/browse/JBTIS-767 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: Matus Makovy > Assignee: Matus Makovy > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-789) Extend DroolsProjectTest and MavenProjectTest

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-789?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-789. ------------------------------ PR was pushed to master branch > Extend DroolsProjectTest and MavenProjectTest > --------------------------------------------- > > Key: JBTIS-789 > URL: https://issues.jboss.org/browse/JBTIS-789 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: drools/ jBPM, QE > Reporter: Tomas David > Assignee: Tomas David > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-790) Fuse: Extend Server Requirement

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-790?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík updated JBTIS-790: ------------------------------- Summary: Fuse: Extend Server Requirement (was: Extend Server Requirement) > Fuse: Extend Server Requirement > ------------------------------- > > Key: JBTIS-790 > URL: https://issues.jboss.org/browse/JBTIS-790 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Blocker > Fix For: 4.3.1.Final > > > We need to know a version of Camel inside JBoss Fuse runtime -> add new element for Camel Version > + also add support for JBoss Fuse 6.3 server adapter -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-790) Extend Server Requirement

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-790: ---------------------------------- Summary: Extend Server Requirement Key: JBTIS-790 URL: https://issues.jboss.org/browse/JBTIS-790 Project: JBoss Tools Integration Stack Issue Type: Sub-task Components: Fuse IDE, QE Affects Versions: 4.3.0.Final Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík Priority: Blocker Fix For: 4.3.1.Final We need to know a version of Camel inside JBoss Fuse runtime -> add new element for Camel Version + also add support for JBoss Fuse 6.3 server adapter -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22615) Explorer: Connections should get loaded from extension points

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22615?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22615: ------------------------------------- Labels: connection openshift_v2 openshift_v3 (was: ) > Explorer: Connections should get loaded from extension points > ------------------------------------------------------------- > > Key: JBIDE-22615 > URL: https://issues.jboss.org/browse/JBIDE-22615 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Labels: connection, openshift_v2, openshift_v3 > Fix For: 4.4.x > > > Connections are currently loaded in the core plugins for the v2 and v3 plugins: > * v2 [ExpressCoreActivator#start|https://github.com/jbosstools/jbosstools-opens...] > * v3 [OpenShiftCoreActivator#start|https://github.com/jbosstools/jbosstools-ope...] > We should load these with extension points. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22615) Explorer: Connections should get loaded from extension points

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-22615: ---------------------------------------- Summary: Explorer: Connections should get loaded from extension points Key: JBIDE-22615 URL: https://issues.jboss.org/browse/JBIDE-22615 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Andre Dietisheim Connections are currently loaded in the core plugins for the v2 and v3 plugins: * v2 [ExpressCoreActivator#start|https://github.com/jbosstools/jbosstools-opens...] * v3 [OpenShiftCoreActivator#start|https://github.com/jbosstools/jbosstools-ope...] We should load these with extension points. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22615) Explorer: Connections should get loaded from extension points

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22615?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22615: ------------------------------------- Fix Version/s: 4.4.x > Explorer: Connections should get loaded from extension points > ------------------------------------------------------------- > > Key: JBIDE-22615 > URL: https://issues.jboss.org/browse/JBIDE-22615 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Fix For: 4.4.x > > > Connections are currently loaded in the core plugins for the v2 and v3 plugins: > * v2 [ExpressCoreActivator#start|https://github.com/jbosstools/jbosstools-opens...] > * v3 [OpenShiftCoreActivator#start|https://github.com/jbosstools/jbosstools-ope...] > We should load these with extension points. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22614) NPE in CDIProject.rebuildXML(CDIProject.java:1458)

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-22614: --------------------------------------- Summary: NPE in CDIProject.rebuildXML(CDIProject.java:1458) Key: JBIDE-22614 URL: https://issues.jboss.org/browse/JBIDE-22614 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Reporter: Aurélien Pupier I'm currently trying to write some integration tests and found this NPE in log. {noformat} !ENTRY org.eclipse.core.resources 4 2 2016-06-17 15:43:54.521 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.NullPointerException at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildXML(CDIProject.java:1458) at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1214) at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:442) at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:267) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {noformat} i'm not sure about the impact yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22596) Impossible to connect to OpenShift when landrush is enabled (instead of xip.io)

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22596?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22596. --------------------------------- Resolution: Done I will open enhancement on monday for this. This one verified in devstudio 10 GA respin-b. > Impossible to connect to OpenShift when landrush is enabled (instead of xip.io) > ------------------------------------------------------------------------------- > > Key: JBIDE-22596 > URL: https://issues.jboss.org/browse/JBIDE-22596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.4.0.Final > > > When landrush is enabled on the CDK, the Docker registry url is https://hub.openshift.openshift.cdk, it's stored in the OpenShift connection properties when launching the CDK server adapter. > However, URL validation fails on that url, thus preventing the Connection wizard to finish, because *.cdk urls are not valid. Indeed cdk is not a known/valid TLD, according to Apache's commons UrlValidator -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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