April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19506) Connection wizard: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19506: ------------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Connection wizard: should have unit tests > ------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19038) Arquillian should not be in JBT EA catalog

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19038?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-19038. ------------------------------ > Arquillian should not be in JBT EA catalog > ------------------------------------------ > > Key: JBIDE-19038 > URL: https://issues.jboss.org/browse/JBIDE-19038 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.2.Final > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.2.3.Final > > Attachments: JBDS_810_GA.png > > > In JBIDE-18995 Arquillian was removed from EA (by removing it from jbosstools-earlyaccess.properties), but on Software/Update page it is still displayed under EA features. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3404) Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-3404?page=com.atlassian.jira.plugin.... ] Pavol Srna updated JBDS-3404: ----------------------------- Attachment: Screenshot 2015-04-16 15.36.03.png Screenshot 2015-04-16 15.36.38.png > Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly) > -------------------------------------------------------- > > Key: JBDS-3404 > URL: https://issues.jboss.org/browse/JBDS-3404 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Pavol Srna > Priority: Blocker > Fix For: 9.0.0.Alpha2 > > Attachments: Screenshot 2015-04-13 14.03.50.png, Screenshot 2015-04-13 14.12.04.png, Screenshot 2015-04-16 15.36.03.png, Screenshot 2015-04-16 15.36.38.png > > > When you do Check for update, only thym update is offered: > !Screenshot 2015-04-13 14.03.50.png! > Output when you do Install/Check All > {code} > Your original request has been modified. > "Java EE Batch Configuration Tools" is already installed, so an update will be performed instead. > "JBoss JAX-RS Tools" is already installed, so an update will be performed instead. > "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead. > "Apache Deltaspike Tools" is already installed, so an update will be performed instead. > "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead. > "JBoss Tools Foundation" is already installed, so an update will be performed instead. > "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead. > "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead. > "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead. > "JBoss Tools RichFaces" is already installed, so an update will be performed instead. > "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead. > "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead. > "JBoss Maven Project Examples" is already installed, so an update will be performed instead. > "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead. > "JMX Console" is already installed, so an update will be performed instead. > "JBoss OpenShift v2 Tools" is already installed, so an update will be performed instead. > "JBoss Tools JSF" is already installed, so an update will be performed instead. > "Seam Tools" is already installed, so an update will be performed instead. > "Hybrid Mobile Application Development Tools" is already installed, so an update will be performed instead. > "JBoss Archives Tools" is already installed, so an update will be performed instead. > "JBoss Stacks Tools" is already installed, so an update will be performed instead. > "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead. > "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead. > "Project Examples" is already installed, so an update will be performed instead. > "JBoss Maven Integration" is already installed, so an update will be performed instead. > "JBoss Runtime Detection Core" is already installed, so an update will be performed instead. > "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead. > "JBoss WebServices Tools" is already installed, so an update will be performed instead. > "Hibernate Tools" is already installed, so an update will be performed instead. > "JBoss Tools LiveReload" is already installed, so an update will be performed instead. > "JBoss Tools Eclipse Thym Integration" is already installed, so an update will be performed instead. > "JBoss Tools EGit Integration" is already installed, so an update will be performed instead. > "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead. > "Forge Tools" is already installed, so an update will be performed instead. > "Context and Dependency Injection Tools" is already installed, so an update will be performed instead. > "JBossAS Tools" is already installed, so an update will be performed instead. > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822) > Software currently installed: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3) > Only one of the following can be installed at once: > JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822) > JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt 3.7.0.Alpha1-v20150213-0215-B3) > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3) > To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha1-v20150213-0215-B3] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3) > To: org.jboss.tools.jst.jsdt [3.7.0.Alpha1-v20150213-0215-B3] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822) > To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19412) Cleanup ConnectionURL usage for v3 connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19412?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19412: ------------------------------------------ internal cleanup postponed to 4.3.0.Beta1 > Cleanup ConnectionURL usage for v3 connections > ---------------------------------------------- > > Key: JBIDE-19412 > URL: https://issues.jboss.org/browse/JBIDE-19412 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > In ConnectionsRegistry connections are stored by ConnectionURL. ConnectionURL is also used to persist v2 connections. v3 connections on the other hand are persisted in their very own json format. We need to clean this discrepany/inconsistency. We should either only use ConnectionURL for v2 connections or also store v3 connections in the ConnectionURL format. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19412) Cleanup ConnectionURL usage for v3 connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19412?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19412: ------------------------------------------ We should also make Connection inherit from AbstractConnection so that we could spare us from duplicate code in ExpressConnection (v2) and Connection (v3) > Cleanup ConnectionURL usage for v3 connections > ---------------------------------------------- > > Key: JBIDE-19412 > URL: https://issues.jboss.org/browse/JBIDE-19412 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > In ConnectionsRegistry connections are stored by ConnectionURL. ConnectionURL is also used to persist v2 connections. v3 connections on the other hand are persisted in their very own json format. We need to clean this discrepany/inconsistency. We should either only use ConnectionURL for v2 connections or also store v3 connections in the ConnectionURL format. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19412) Cleanup ConnectionURL usage for v3 connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19412?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19412: ------------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Cleanup ConnectionURL usage for v3 connections > ---------------------------------------------- > > Key: JBIDE-19412 > URL: https://issues.jboss.org/browse/JBIDE-19412 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > In ConnectionsRegistry connections are stored by ConnectionURL. ConnectionURL is also used to persist v2 connections. v3 connections on the other hand are persisted in their very own json format. We need to clean this discrepany/inconsistency. We should either only use ConnectionURL for v2 connections or also store v3 connections in the ConnectionURL format. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19549) Connection wizard: v3 connection should store tokens and passwords to the secure storage

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19549?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19549: ------------------------------------------ merged and pushed to upstream/master > Connection wizard: v3 connection should store tokens and passwords to the secure storage > ---------------------------------------------------------------------------------------- > > Key: JBIDE-19549 > URL: https://issues.jboss.org/browse/JBIDE-19549 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > Currently v3 connections store the authentication tokens in plaintext into some configuration file. We should store them to the secure storage. Passwords are not stored at all, we should make sure that if a user is editing his v3 connection he does not have to retype his password and have it provided from secure storage -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18652) NPE in Eclipse Error Log View when Central repo isn't available

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18652?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-18652. ------------------------------ > NPE in Eclipse Error Log View when Central repo isn't available > --------------------------------------------------------------- > > Key: JBIDE-18652 > URL: https://issues.jboss.org/browse/JBIDE-18652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.CR2 > Reporter: Denis Golovin > Assignee: Mickael Istria > Labels: respin-a > Fix For: 4.2.1.CR1 > > > Could be related to Central Update Site not being available, but it should not fail with NPE in this case. > {code}java.lang.NullPointerException > at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101) > at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1) > at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3399) http://planet.jboss.org/feeds/buzz is returning a 503 error

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3399?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-3399. ------------------------------ Fix Version/s: 8.1.0.GA Resolution: Done if (fixed) { then resolve.it().please(); } > http://planet.jboss.org/feeds/buzz is returning a 503 error > ----------------------------------------------------------- > > Key: JBDS-3399 > URL: https://issues.jboss.org/browse/JBDS-3399 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: central > Affects Versions: 8.1.0.GA > Reporter: Len DiMaggio > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 9.0.0.Alpha2, 8.1.0.GA > > > Not sure when this started failing - http://planet.jboss.org/feeds/buzz -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3399) http://planet.jboss.org/feeds/buzz is returning a 503 error

by Vladimir Vasilev (JIRA)

[ https://issues.jboss.org/browse/JBDS-3399?page=com.atlassian.jira.plugin.... ] Vladimir Vasilev commented on JBDS-3399: ---------------------------------------- This is fixed now > http://planet.jboss.org/feeds/buzz is returning a 503 error > ----------------------------------------------------------- > > Key: JBDS-3399 > URL: https://issues.jboss.org/browse/JBDS-3399 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: central > Affects Versions: 8.1.0.GA > Reporter: Len DiMaggio > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 9.0.0.Alpha2 > > > Not sure when this started failing - http://planet.jboss.org/feeds/buzz -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 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 April 2015