[JBoss JIRA] (JBIDE-19042) Cannot login via Openshift Explorer on Openshift "Can not verify User"
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19042?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-19042.
---------------------------------
> 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
> Environment: Win7, jdk7, Openshift Online
> Reporter: Stylianos Koussouris
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.2.Final
>
> Attachments: CannotVerifyUser.JPG
>
>
> 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)
> Similar Issue reported: https://forums.openshift.com/unknown-error-can-not-verify-user
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19345) allow NN to be filtered/redefined for NN
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19345?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-19345:
---------------------------------------
commit that resolves the issue: https://github.com/jbosstools/jbosstools-website/commit/f64ee34825013d295...
> allow NN to be filtered/redefined for NN
> ----------------------------------------
>
> Key: JBIDE-19345
> URL: https://issues.jboss.org/browse/JBIDE-19345
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: website
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.2.3.Final, 4.3.0.CR1
>
>
> there been examples of auto aggregation of NN be a hit or miss for how much it makes sense in the release.
> For example:
> Beta1: Added a few components to the Ionic Palette: <c1> <c2> <c3>
> Beta2: Added a few components to the Ionic: <c4> <c5>
> Alexey Kazakov: But in the final verision I would like to have: Added new components: <c1>,...<c5>.
> One suggestion been to have ability to rewrite the full NN version at final but I just know that will kill us becase it is going to be a pain to copy/paste right.
> Alternative suggestion is:
> A) during rendering of the "final" aggregation set a asciidoc variable (i.e. "finalnn") allowing us to use asciidoc conditionals like
> {code}
> ifndef::finalnn[]
> This piece of news was only relevant for Beta1
> endif::finalnn[]
> {code}
> See: http://mrhaki.blogspot.ch/2014/08/awesome-asciidoc-using-conditional.html
> B) allow to add a .Final newnoteworthy adoc to use as place to write the aggregated news ..note, these should still be merged with the former NN's. so you only need to write the sections that are actually different.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-15609) versionwatch should ignore when there's a folder & jar which are identical
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15609?page=com.atlassian.jira.plugi... ]
Jiri Peterka closed JBIDE-15609.
--------------------------------
This was resolved in VW 0.4, closing
> versionwatch should ignore when there's a folder & jar which are identical
> --------------------------------------------------------------------------
>
> Key: JBIDE-15609
> URL: https://issues.jboss.org/browse/JBIDE-15609
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, qa
> Affects Versions: 4.1.1.Alpha2
> Reporter: Nick Boldt
> Assignee: Jiri Peterka
> Priority: Optional
> Fix For: 4.2.2.Final
>
>
> A while ago I added a facility to jar up feature and plugin folders so they could have their md5 sums compared.
> Now, the vwatch tool complains when there's a folder and a jar present.
> Two possible solutions to this come to mind:
> a) ignore this - do not report as *{color:red}a problem{color}*
> b) whenever a folder is jarred up, delete the source folder, so the above condition cannot occur
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-18878) Eclipse livelock(?) at startup with hibernate builder in stacktrace
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18878?page=com.atlassian.jira.plugi... ]
Jiri Peterka closed JBIDE-18878.
--------------------------------
Verified with JBDS 8.1.0.GA, L64
> Eclipse livelock(?) at startup with hibernate builder in stacktrace
> -------------------------------------------------------------------
>
> Key: JBIDE-18878
> URL: https://issues.jboss.org/browse/JBIDE-18878
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.Final
> Reporter: Denis Golovin
> Assignee: Snjezana Peco
> Fix For: 4.2.3.Beta1
>
> Attachments: jstack-output.txt
>
>
> See attached [^jstack-output.txt]
> Console out is:
> {code}sh ./jbt420final.sh
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
> org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
> org.eclipse.m2e.logback.configuration: Logback config file: /home/eskimo/workspace/420cr2-test1/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.5.0.20140606-0033.xml
> org.eclipse.m2e.logback.configuration: Initializing logback
> java.lang.ClassCastException: org.eclipse.osgi.internal.framework.EquinoxConfiguration$1 cannot be cast to java.lang.String
> at org.eclipse.m2e.logback.configuration.LogHelper.logJavaProperties(LogHelper.java:26)
> at org.eclipse.m2e.logback.configuration.LogPlugin.loadConfiguration(LogPlugin.java:189)
> at org.eclipse.m2e.logback.configuration.LogPlugin.configureLogback(LogPlugin.java:144)
> at org.eclipse.m2e.logback.configuration.LogPlugin.access$2(LogPlugin.java:107)
> at org.eclipse.m2e.logback.configuration.LogPlugin$1.run(LogPlugin.java:62)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Dec 05, 2014 3:41:58 PM org.hibernate.eclipse.HibernatePlugin start
> INFO: HibernatePlugin Started{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months