January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19042) Cannot login via Openshift Explorer on Openshift "Can not verify User"

by Stylianos Koussouris (JIRA)

Stylianos Koussouris created JBIDE-19042: -------------------------------------------- Summary: Cannot login via Openshift Explorer on Openshift "Can not verify User" Key: JBIDE-19042 URL: https://issues.jboss.org/browse/JBIDE-19042 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.1.x, 4.2.x Environment: Win7, jdk7, Openshift Online Reporter: Stylianos Koussouris Priority: Critical Trying to connect via Openshift explorer to Openshift Online, the credentials are correct and working from the Web UI, I receive Unknown error, can not verify user and in the log !ENTRY org.jboss.tools.openshift.express.ui 4 4 2015-01-15 15:01:37.848 !MESSAGE !STACK 0 java.lang.NullPointerException at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:196) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:113) at com.openshift.internal.client.RestService.request(RestService.java:151) at com.openshift.internal.client.RestService.request(RestService.java:107) at com.openshift.internal.client.RestService.request(RestService.java:100) at com.openshift.internal.client.RestService.request(RestService.java:81) at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34) at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:134) at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:103) at org.jboss.tools.openshift.express.internal.core.connection.Connection.createUser(Connection.java:219) at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:199) at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:252) at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPage$ConnectJob.run(ConnectionWizardPage.java:474) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18813) Convert JBoss Central to an HTML5 page

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18813?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18813: ------------------------------------- We only capture which examples are being used (from scratch ~65% vs from existing ~35%) and which features are being installed from the software page > Convert JBoss Central to an HTML5 page > -------------------------------------- > > Key: JBIDE-18813 > URL: https://issues.jboss.org/browse/JBIDE-18813 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.3.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.0.Alpha1 > > Attachments: JBoss Central User Stories and Flows.gliffy > > > Central Page requires new capabilities : > - needs more customization (display content depending on user preferences) > - needs to scale with JBDS-IS, Fuse content > - access to more examples, with filtering capabilities > Given that the existing page is pretty hard to maintain and suffers from scalability/UI bugs, we're heading towards an HTML5 approach : > - use an embedded SWT Browser widget (or Java FX), depending on the platform compatibility > - webpage and its content could be served remotely (as zip), and downloaded locally for offline use. this would give us more flexibility to update the content. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18692) Jenkins build for jbosstools-incubator-ripple

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18692?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18692: ---------------------------------------- I fixed https://github.com/jbosstools/jbosstools-aerogear/pull/92 to reintroduce ThymPlugin.java and rebased it on top of master. > Jenkins build for jbosstools-incubator-ripple > --------------------------------------------- > > Key: JBIDE-18692 > URL: https://issues.jboss.org/browse/JBIDE-18692 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > We need a jenkins job to build for jbosstools-incubator-ripple, and have it > invoking "./configure && jake" and distribute the builds to Nexus so that cordovasim can start using ripple from this repo. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3318) Hibernate/Persistence.next

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBDS-3318: ----------------------------------------- Summary: Hibernate/Persistence.next Key: JBDS-3318 URL: https://issues.jboss.org/browse/JBDS-3318 Project: Developer Studio (JBoss Developer Studio) Issue Type: Epic Reporter: Max Rydahl Andersen -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3317) Basic Docker support

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3317?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3317: ----------------------------- CDW pm_ack: ? > Basic Docker support > -------------------- > > Key: JBDS-3317 > URL: https://issues.jboss.org/browse/JBDS-3317 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3317) Basic Docker support

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3317?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3317: -------------------------------------- CDW release: ? Status: New (was: New) Target Release: 9.0.0.GA > Basic Docker support > -------------------- > > Key: JBDS-3317 > URL: https://issues.jboss.org/browse/JBDS-3317 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3317) Basic Docker support

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBDS-3317: ----------------------------------------- Summary: Basic Docker support Key: JBDS-3317 URL: https://issues.jboss.org/browse/JBDS-3317 Project: Developer Studio (JBoss Developer Studio) Issue Type: Epic Components: openshift Reporter: Max Rydahl Andersen Assignee: Max Rydahl Andersen -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3269) Build Farm Integration Level 1

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3269?page=com.atlassian.jira.plugin.... ] Gorkem Ercan edited comment on JBDS-3269 at 1/15/15 10:14 AM: -------------------------------------------------------------- It is related to JBDS-3287. This jira does not ask for any special UI features, so if we can correctly import a FH project and we can do a git push of our changes, the rest is done on the FH Web UI. Mostly a task for QE to verify import and changes we do is consumable by FH build farm. was (Author: gercan): It is related to JBDS-3287. This jira does not ask for any special UI features, so if we can correctly import a FH project so that we can do a git push of our changes the rest is done on the FH Web UI. Mostly a task for QE to verify import and changes we do is consumable by FH build farm. > Build Farm Integration Level 1 > ------------------------------ > > Key: JBDS-3269 > URL: https://issues.jboss.org/browse/JBDS-3269 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Burr Sutter > Assignee: Gorkem Ercan > Fix For: 9.0.0.Alpha1 > > > Level 1: > 1) git push of Hybrid Mobile Cordova Projects to FH provided URL > 2) Using the Web UI to start the build process > 3) Using the Web UI to review the QR Code -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3199) Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ] Rafael Benevides commented on JBDS-3199: ---------------------------------------- [~fbricon] Yeap! You assumption is right! It's also fixed in wildfly archetype as well > Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3199 > URL: https://issues.jboss.org/browse/JBDS-3199 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, upstream > Affects Versions: 8.0.0.GA > Reporter: Len DiMaggio > Assignee: Fred Bricon > Fix For: 8.1.0.GA > > > These "kitchensink" strings are retained: > grep -ir kitchen * > main/resources/META-INF/persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS</jta-data-source> > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS" > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: pool-name="kitchensink-quickstart" enabled="true" > test/resources/arquillian-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileTestDS" > test/resources/META-INF/test-persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileTestDS</jta-data-source> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3269) Build Farm Integration Level 1

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3269?page=com.atlassian.jira.plugin.... ] Gorkem Ercan commented on JBDS-3269: ------------------------------------ It is related to JBDS-3287. This jira does not ask for any special UI features, so if we can correctly import a FH project so that we can do a git push of our changes the rest is done on the FH Web UI. Mostly a task for QE to verify import and changes we do is consumable by FH build farm. > Build Farm Integration Level 1 > ------------------------------ > > Key: JBDS-3269 > URL: https://issues.jboss.org/browse/JBDS-3269 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Burr Sutter > Assignee: Gorkem Ercan > Fix For: 9.0.0.Alpha1 > > > Level 1: > 1) git push of Hybrid Mobile Cordova Projects to FH provided URL > 2) Using the Web UI to start the build process > 3) Using the Web UI to review the QR Code -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 January 2015