June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14292) Link under 'Other resources' on JBoss Central is incorrect for JBDS

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14292?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-14292: ----------------------------------- Assignee: Fred Bricon (was: Michelle Murray) > Link under 'Other resources' on JBoss Central is incorrect for JBDS > ------------------------------------------------------------------- > > Key: JBIDE-14292 > URL: https://issues.jboss.org/browse/JBIDE-14292 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha2 > Reporter: Michelle Murray > Assignee: Fred Bricon > Fix For: 4.1.0.Beta2 > > > I realise that JBoss Central is still under development but I wanted to point out an issue. Under 'Other resources' there is a link titled 'Product documentation' that links to http://docs.jboss.org/tools/latest/. > 1. Is this the right link for community docs? /tools/latest will store documentation under development for the next release. Should this link point to the community docs for the version of JBT installed (for example, tools/4.1.0 for JBT 4.1.0)? There is ongoing debate about what exactly the link will be - see TOOLSDOC-310. > 2. This link does not point to the right place for JBDS users. JBDS documentation is stored here: https://access.redhat.com/site/documentation/JBoss_Developer_Studio/ So how can the issue of two separate documentation locations for JBT and JBDS be got around? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14292) Link under 'Other resources' on JBoss Central is incorrect for JBDS

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14292?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-14292: ----------------------------------- Assignee: Michelle Murray (was: Fred Bricon) Michelle, please mark this issue as resolved if you're ok with it, otherwise assign it back to me and let me know what needs to be changed. > Link under 'Other resources' on JBoss Central is incorrect for JBDS > ------------------------------------------------------------------- > > Key: JBIDE-14292 > URL: https://issues.jboss.org/browse/JBIDE-14292 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha2 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0.Beta2 > > > I realise that JBoss Central is still under development but I wanted to point out an issue. Under 'Other resources' there is a link titled 'Product documentation' that links to http://docs.jboss.org/tools/latest/. > 1. Is this the right link for community docs? /tools/latest will store documentation under development for the next release. Should this link point to the community docs for the version of JBT installed (for example, tools/4.1.0 for JBT 4.1.0)? There is ongoing debate about what exactly the link will be - see TOOLSDOC-310. > 2. This link does not point to the right place for JBDS users. JBDS documentation is stored here: https://access.redhat.com/site/documentation/JBoss_Developer_Studio/ So how can the issue of two separate documentation locations for JBT and JBDS be got around? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14760) Cannot connect to OpenShift Enterprise with hostname: javax.net.ssl.SSLProtocolException (WATCHER)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14760?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-14760: ------------------------------------------------- gpei(a)redhat.com changed the Status of [bug 970805|https://bugzilla.redhat.com/show_bug.cgi?id=970805] from ON_QA to VERIFIED > Cannot connect to OpenShift Enterprise with hostname: javax.net.ssl.SSLProtocolException (WATCHER) > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-14760 > URL: https://issues.jboss.org/browse/JBIDE-14760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta2 > Environment: jdk7 > Reporter: jing zh > Assignee: Andre Dietisheim > Fix For: 4.1.x > > Attachments: JBT_test.png > > > If trying to connect openshift server ,it would be failed with following error shown. > Could not verify credentials for jinzhang1: Could not request https://broker.osetestv2.com/broker/rest/api: javax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14760) Cannot connect to OpenShift Enterprise with hostname: javax.net.ssl.SSLProtocolException (WATCHER)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14760?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-14760: ------------------------------------------------- gpei(a)redhat.com made a comment on [bug 970805|https://bugzilla.redhat.com/show_bug.cgi?id=970805] Verify this on puddle: http://buildvm-devops.usersys.redhat.com/puddle/build/OpenShiftEnterprise... After setting up OSE env, check the ServerName of broker and nodes: [root@broker conf.d]# cat 000002_openshift_origin_broker_servername.conf |grep ServerName # a consistent default ServerName broker.osevvv.com ServerName broker.osevvv.com [root@node conf.d]# cat 000001_openshift_origin_node_servername.conf|grep ServerName # a consistent default ServerName node.osevvv.com ServerName node.osevvv.com Both of them are correct. Use oo-diagnostics to verify the broker SSL cert is valid, no error throw out. [root@broker conf.d]# oo-diagnostics -v INFO: loading list of installed packages INFO: OpenShift broker installed. ... INFO: running: test_broker_certificate NO ERRORS > Cannot connect to OpenShift Enterprise with hostname: javax.net.ssl.SSLProtocolException (WATCHER) > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-14760 > URL: https://issues.jboss.org/browse/JBIDE-14760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta2 > Environment: jdk7 > Reporter: jing zh > Assignee: Andre Dietisheim > Fix For: 4.1.x > > Attachments: JBT_test.png > > > If trying to connect openshift server ,it would be failed with following error shown. > Could not verify credentials for jinzhang1: Could not request https://broker.osetestv2.com/broker/rest/api: javax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2573) JBDS70_1411: [Uncommit] (Dev) (P1) Track more

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2573?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-2573: ---------------------------------------- It is apparently possible to split keywords, report them separately and have those keywords ranked separately: http://cutroni.com/blog/2013/01/14/a-new-method-to-track-keyword-ranking-... It involves sending those keywords separately in individual events. > JBDS70_1411: [Uncommit] (Dev) (P1) Track more > --------------------------------------------- > > Key: JBDS-2573 > URL: https://issues.jboss.org/browse/JBDS-2573 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Reporter: Jiri Pallich > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 7.0.0.Beta2 > > > What JBoss and 3rd party plug-ins are end-users really using? Allowing us to invest more in the most popular. (Note: This was deferred JBDS60_0920.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13582) JBoss EAP 6.1.0.DR4 is recognized as AS 7.2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13582?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-13582: ---------------------------------- Fix Version/s: 4.1.0.Beta2 > JBoss EAP 6.1.0.DR4 is recognized as AS 7.2 > ------------------------------------------- > > Key: JBIDE-13582 > URL: https://issues.jboss.org/browse/JBIDE-13582 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.1.0.Alpha1, 4.1.0.Beta1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta2 > > Attachments: Screenshot-2.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13582) JBoss EAP 6.1.0.DR4 is recognized as AS 7.2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13582?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-13582: --------------------------------------- Setting fix version to 4.1.0.Beta2 so this issue can be picked up. > JBoss EAP 6.1.0.DR4 is recognized as AS 7.2 > ------------------------------------------- > > Key: JBIDE-13582 > URL: https://issues.jboss.org/browse/JBIDE-13582 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.1.0.Alpha1, 4.1.0.Beta1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta2 > > Attachments: Screenshot-2.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13582) JBoss EAP 6.1.0.DR4 is recognized as AS 7.2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13582?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-13582: ---------------------------------- Fix Version/s: (was: 4.1.0.Alpha2) > JBoss EAP 6.1.0.DR4 is recognized as AS 7.2 > ------------------------------------------- > > Key: JBIDE-13582 > URL: https://issues.jboss.org/browse/JBIDE-13582 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.1.0.Alpha1, 4.1.0.Beta1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Attachments: Screenshot-2.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12121) The openshift profile is added to newly created maven projects, regardless of their packaging type

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12121?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-12121: ------------------------------------------ postponed to 4.1.x since we ran out of time for this issue in 4.1.0.Beta2 > The openshift profile is added to newly created maven projects, regardless of their packaging type > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-12121 > URL: https://issues.jboss.org/browse/JBIDE-12121 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Fix For: 4.1.x > > Attachments: new-openarchetype-project-2.png, new-openarchetype-project.png > > > I created a project using the org.openarchetypes:multi-javaee6-archetype:0.0.1-SNAPSHOT from http://open-archetypes.github.com/maven-repo/snapshots/archetype-catalog.xml (Maven > Archetypes > Add Remote Catalog) > This creates a multi module project, containing a parent pom, an ear, war, ejb and utility projects. This openshift profile was added to the pom project : > {code:xml} > <profiles> > <profile> >  >  >  >  > <id>openshift</id> > <build> > <finalName>hello</finalName> > <plugins> > <plugin> > <artifactId>maven-war-plugin</artifactId> > <version>2.1.1</version> > <configuration> > <outputDirectory>deployments</outputDirectory> > <warName>ROOT</warName> > </configuration> > </plugin> > </plugins> > </build> > </profile> > {code} > Actually, it should : > - check the packaging type of *all* the generated projects > - if some EARs are found, then add the following to the parent pom (pay attention to the <pluginManagement> section) : > {code:xml} > <profile> > <id>openshift</id> > <build> > <pluginManagement> > <plugins> > <plugin> > <artifactId>maven-ear-plugin</artifactId> > <version>2.7</version> > <configuration> > <outputDirectory>deployments</outputDirectory> > </configuration> > </plugin> > </plugins> > </pluginManagement> > </build> > </profile> > {code} > - if there are no EARs but some WARs are found (count them), then add the following to the parent pom (pay attention to the <pluginManagement> section) : > {code:xml} > <profiles> > <profile> > <id>openshift</id> > <build> > <pluginManagement> > <plugins> > <plugin> > <artifactId>maven-war-plugin</artifactId> > <version>2.2</version> > <configuration> > <outputDirectory>deployments</outputDirectory> >  > <warName>ROOT</warName> > </configuration> > </plugin> > </plugins> > </pluginManagement> > </build> > </profile> > {code} > The finalName is irrelevant to openshift, only the warName counts. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13303) errors in error log when navigating openshift explorer and no connection setup

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13303?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13303: ------------------------------------------ postponed to 4.1.x since we ran out of time for 4.1.0.Beta2 > errors in error log when navigating openshift explorer and no connection setup > ------------------------------------------------------------------------------ > > Key: JBIDE-13303 > URL: https://issues.jboss.org/browse/JBIDE-13303 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.x > > > Open openshift explorer with properties view and no connection open and no network attached. > com.openshift.client.OpenShiftEndpointException: Could not request /api: java.net.UnknownHostException: openshift.redhat.com > at com.openshift.internal.client.RestService.request(RestService.java:103) > at com.openshift.internal.client.RestService.request(RestService.java:91) > at com.openshift.internal.client.RestService.request(RestService.java:72) > at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34) > at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:135) > at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:104) > 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.property.UserPropertySource$1.run(UserPropertySource.java:112) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > Caused by: com.openshift.internal.client.httpclient.HttpClientException: java.net.UnknownHostException: openshift.redhat.com > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:194) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:99) > at com.openshift.internal.client.RestService.request(RestService.java:139) > at com.openshift.internal.client.RestService.request(RestService.java:97) > ... 9 more > Caused by: java.net.UnknownHostException: openshift.redhat.com > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1491) > at java.security.AccessController.doPrivileged(Native Method) > at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1485) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:177) > ... 12 more > Caused by: java.net.UnknownHostException: openshift.redhat.com > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432) > at java.net.Socket.connect(Socket.java:529) > at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:570) > at sun.net.NetworkClient.doConnect(NetworkClient.java:158) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:388) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:523) > at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:272) > at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:329) > at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:172) > at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911) > at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:158) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:94) > ... 11 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

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