February 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-15374) Create target platform from Luna M2 dependencies

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15374?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15374. --------------------------------- Closing. > Create target platform from Luna M2 dependencies > ------------------------------------------------ > > Key: JBIDE-15374 > URL: https://issues.jboss.org/browse/JBIDE-15374 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha1 > > > Create a new target platform for use with JBoss Tools 4.2 (Luna). Should be versioned 4.40.x. > Luna schedule: > http://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#Schedule -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2370) Bad/non-helping error message when central has no connection

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-2370?page=com.atlassian.jira.plugin.... ] Martin Malina reassigned JBDS-2370: ----------------------------------- Assignee: Radim Hopp (was: Martin Malina) Radim, please verify in CR1. > Bad/non-helping error message when central has no connection > ------------------------------------------------------------ > > Key: JBDS-2370 > URL: https://issues.jboss.org/browse/JBDS-2370 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 5.0.0.GA > Environment: JDK 1.7 32-bit, Windows > Reporter: David Chia > Assignee: Radim Hopp > Priority: Critical > Labels: jbds711 > Fix For: 7.1.1.CR1 > > > After a successful install, I tried to create a "Java EE Web Project" and run into an error dialog "Failed to load Wizard - Wizard metadata could not be loaded". I've also tried all other projects and result in the same error. The only project I could create is the "Dynamic Web Project". Looking at the error log, there are a lot of these "Connection errors" like below. > !SESSION 2012-10-23 15:28:07.909 ----------------------------------------------- > eclipse.buildId=unknown > java.version=1.7.0_07 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US > Framework arguments: -product com.jboss.jbds.product.product > Command-line arguments: -os win32 -ws win32 -arch x86 -product com.jboss.jbds.product.product > !ENTRY org.jboss.tools.central 4 0 2012-10-23 15:28:27.086 > !MESSAGE Permission denied: connect > !STACK 0 > java.net.SocketException: Permission denied: connect > at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) > at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:75) > at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) > at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) > at java.net.Socket.connect(Socket.java:579) > at org.eclipse.ecf.provider.filetransfer.events.socket.SocketEventCreateUtil.createSocket(SocketEventCreateUtil.java:43) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:81) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:73) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:65) > at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) > at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) > at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) > at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) > at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1142) > at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:710) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:889) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:576) > at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.transfer(ECFExamplesTransport.java:319) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.performDownload(ECFExamplesTransport.java:246) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.download(ECFExamplesTransport.java:206) > at org.jboss.tools.central.jobs.AbstractRefreshJob.run(AbstractRefreshJob.java:186) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > !ENTRY org.jboss.tools.central 4 0 2012-10-23 15:28:27.132 > !MESSAGE Permission denied: connect > !STACK 0 > java.net.SocketException: Permission denied: connect > at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) > at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:75) > at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) > at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) > at java.net.Socket.connect(Socket.java:579) > at org.eclipse.ecf.provider.filetransfer.events.socket.SocketEventCreateUtil.createSocket(SocketEventCreateUtil.java:43) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:81) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:73) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:65) > at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) > at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) > at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) > at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) > at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1142) > at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:710) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:889) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:576) > at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.transfer(ECFExamplesTransport.java:319) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.performDownload(ECFExamplesTransport.java:246) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.download(ECFExamplesTransport.java:206) > at org.jboss.tools.central.jobs.AbstractRefreshJob.run(AbstractRefreshJob.java:186) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16650) Switch to m2e profile management from m2e 1.5M6

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-16650: ----------------------------------- Summary: Switch to m2e profile management from m2e 1.5M6 Key: JBIDE-16650 URL: https://issues.jboss.org/browse/JBIDE-16650 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: testing-tools Affects Versions: 4.2.0.Beta1 Reporter: Fred Bricon Fix For: 4.2.0.Beta1 The JBoss Maven Profile Mgmt UI is moving to m2e 1.5M6. Code needs to be changed accordingly in the arquillian tooling -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-15836) Contribute the Maven Profile Management UI to m2e @eclipse.org

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15836?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15836: -------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.x) > Contribute the Maven Profile Management UI to m2e @eclipse.org > -------------------------------------------------------------- > > Key: JBIDE-15836 > URL: https://issues.jboss.org/browse/JBIDE-15836 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: maven > Affects Versions: 4.1.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.2.0.Beta1 > > > We announced during EclipseCon Europe we'd contribute the Maven Profile Management UI to the m2e project, so let's do it :-) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-15836) Contribute the Maven Profile Management UI to m2e @eclipse.org

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15836?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-15836: ------------------------------------- Contribution to Eclipse.org has been approved by the Eclipse IP team. We should hopefully have the feature moved over by Luna M6 https://bugs.eclipse.org/bugs/show_bug.cgi?id=428094 > Contribute the Maven Profile Management UI to m2e @eclipse.org > -------------------------------------------------------------- > > Key: JBIDE-15836 > URL: https://issues.jboss.org/browse/JBIDE-15836 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: maven > Affects Versions: 4.1.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.2.x > > > We announced during EclipseCon Europe we'd contribute the Maven Profile Management UI to the m2e project, so let's do it :-) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16649) Restrict Maven Profile Management to m2e < 1.5

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-16649: ----------------------------------- Summary: Restrict Maven Profile Management to m2e < 1.5 Key: JBIDE-16649 URL: https://issues.jboss.org/browse/JBIDE-16649 Project: Tools (JBoss Tools) Issue Type: Task Components: maven Affects Versions: 4.1.1.Final Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.1.2.CR1 Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts. The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it. The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16648) Investigate migration to p2 discovery API (instead of old Mylyn one)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16648?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16648: ---------------------------------------- There isn't much documentation available: * https://wiki.eclipse.org/Equinox/p2/Discovery * https://wiki.eclipse.org/EPP/MPC/Contributor_Guide > Investigate migration to p2 discovery API (instead of old Mylyn one) > -------------------------------------------------------------------- > > Key: JBIDE-16648 > URL: https://issues.jboss.org/browse/JBIDE-16648 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Alpha2 > Reporter: Mickael Istria > Fix For: LATER > > > Currently, Central seems to only rely on old mylyn discovery API. However, a part of this API has been moved to p2 a while ago, and is maintained on p2 side. > We should try to replace usage of mylyn discovery API by the p2 one. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-15488) Web Service Tester doesn't work with https and self-signed certificate

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15488?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-15488: ------------------------------------------- [~juergen.zimmermann] Can you get back to me with what uid/pwd you used for authentication using your example? > Web Service Tester doesn't work with https and self-signed certificate > ---------------------------------------------------------------------- > > Key: JBIDE-15488 > URL: https://issues.jboss.org/browse/JBIDE-15488 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Juergen Zimmermann > Assignee: Brian Fitzpatrick > Fix For: 4.2.x > > > If I test a RESTful Web Service on WildFly 8 which is configured for https, then I just this error message in the response body (for both GET and POST requests): > {code} > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target > {code} -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16427) Set Wildfly 8 java web services runtime to JBossWS/CXF from JAXWS RI

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16427?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-16427: ------------------------------------------- [~asoldano] Alessio, did you ever have any time to look deeper at the mavenized example? > Set Wildfly 8 java web services runtime to JBossWS/CXF from JAXWS RI > -------------------------------------------------------------------- > > Key: JBIDE-16427 > URL: https://issues.jboss.org/browse/JBIDE-16427 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.Final > Reporter: Joseph Hwang > Assignee: Brian Fitzpatrick > Fix For: 4.1.x, 4.2.x > > Attachments: wss-mvn.zip, WSSHelloWorld.zip > > > I implement Java Web Services with wildfly 8 and eclipse kepler jboss tools with the reference site https://docs.jboss.org/author/display/JBWS/WS-Security . > The deployment and generated client codes works well. But the the problem is web services runtime is JAXWS RI, not JBossWS/CXF. The eclipse console show the following message, > > INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default taskextensions/wssecurity}HelloWorldService from WSDL: http://localhost:8080/WSSHelloWorld/HelloWorld?wsdl > > org.apache.cxf.service.factory.ReflectionServiceFactoryBean class is involved in <WILDFLY_HOME>\modules\system\layers\base\org\apache\cxf\impl\main\cxf-rt-core-2.7.7.jar file of JAXWS RI. > So the configuration of web services mentioned in above reference site are useless, does not work at all. > But the same project works well with JBoss EAP 6.1.1 and eclipse kepler jboss tools. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16648) Investigate migration to p2 discovery API (instead of old Mylyn one)

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-16648: -------------------------------------- Summary: Investigate migration to p2 discovery API (instead of old Mylyn one) Key: JBIDE-16648 URL: https://issues.jboss.org/browse/JBIDE-16648 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: central Affects Versions: 4.2.0.Alpha2 Reporter: Mickael Istria Fix For: LATER Currently, Central seems to only rely on old mylyn discovery API. However, a part of this API has been moved to p2 a while ago, and is maintained on p2 side. We should try to replace usage of mylyn discovery API by the p2 one. -- 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, 1 month

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 February 2014