[ https://issues.jboss.org/browse/JBIDE-10628?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10628: --------------------------------------------- hmm - Fred, could we be missing some plugin dependency that makes the discovery not work when you haven't installed the full m2e ? Jochen, does things get better in jbosstools if you go and install m2e explicitly ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10628?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10628: --------------------------------------------- "I add the kitchensink example from jboss central Panel, open the pom.xml and try to quickfix an missing m2e connecter. M2e fails like discribed above, with the confusing network error." Yes, and my question is if you install m2eclipse *explicitly* after installing jboss tools if the discovery works ? (since I assume you are saying if you install it expliclity *before* jboss tools then it works ?) And the best option you have is to configure m2e in your pom.xml to ignore or run the unknown parts as you want - then you get the same behavior as under 3.2. It is not optimal I know but way better than staying on Eclipse Helios where no, there won't be a JBoss 7 connector. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10628?page=com.atlassian.jira.plugi... ] Jochen Buchholz commented on JBIDE-10628: ----------------------------------------- @Max M2eclipse runs only under Eclipse Helios ;-) When I install m2e before JBoss Tools it works. When I install JBoss Tools I could do only one discover. When I install Jboss Tools directly under a fresh Indigo installation I can't install m2e after, because its already installed by JBoss Tools. When I test the Kitchensink example I can't discover any connectors @Fred Hi Fred, I did a new installation again (under linux 64bit) and install the JBoss Tools (indigo) under Marketplace. Here is the Error comes up when I try to discover m2e connectors (.metadata/.log): !ENTRY org.eclipse.equinox.p2.discovery 4 0 2012-01-24 16:05:53.633 !MESSAGE Cannot download bundle at https://repository.sonatype.org/content/repositories/forge-sites/m2e-disc...: Unable to read repository at https://repository.sonatype.org/content/repositories/forge-sites/m2e-disc.... !STACK 1 org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at https://repository.sonatype.org/content/repositories/forge-sites/m2e-disc.... at org.eclipse.equinox.internal.p2.discovery.compatibility.util.CacheManager.createCache(CacheManager.java:110) at org.eclipse.equinox.internal.p2.discovery.compatibility.util.TransportUtil.downloadResource(TransportUtil.java:56) at org.eclipse.equinox.internal.p2.discovery.compatibility.RemoteBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteBundleDiscoveryStrategy.java:203) at org.eclipse.equinox.internal.p2.discovery.compatibility.RemoteBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteBundleDiscoveryStrategy.java:1) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Caused by: java.security.ProviderException: Could not initialize NSS at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:201) at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:103) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at sun.security.jca.ProviderConfig$3.run(ProviderConfig.java:262) at sun.security.jca.ProviderConfig$3.run(ProviderConfig.java:244) at java.security.AccessController.doPrivileged(Native Method) at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:244) at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:224) at sun.security.jca.ProviderList.getProvider(ProviderList.java:232) at sun.security.jca.ProviderList$ServiceList.tryGet(ProviderList.java:433) at sun.security.jca.ProviderList$ServiceList.access$200(ProviderList.java:375) at sun.security.jca.ProviderList$ServiceList$1.hasNext(ProviderList.java:485) at sun.security.jca.GetInstance.getInstance(GetInstance.java:170) at javax.net.ssl.SSLContext.getInstance(SSLContext.java:142) at javax.net.ssl.SSLContext.getDefault(SSLContext.java:85) at javax.net.ssl.SSLSocketFactory.getDefault(SSLSocketFactory.java:119) at org.eclipse.ecf.internal.ssl.ECFSSLSocketFactory.getSSLSocketFactory(ECFSSLSocketFactory.java:38) at org.eclipse.ecf.internal.ssl.ECFSSLSocketFactory.createSocket(ECFSSLSocketFactory.java:63) at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ssl.SSLSocketFactoryModifier.createSocket(SSLSocketFactoryModifier.java:47) at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientSecureProtocolSocketFactory$1.createSocket(ECFHttpClientSecureProtocolSocketFactory.java:29) at org.eclipse.ecf.provider.filetransfer.events.socket.SocketEventCreateUtil.createSocket(SocketEventCreateUtil.java:37) 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.HttpClientFileSystemBrowser.runRequest(HttpClientFileSystemBrowser.java:227) at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.io.IOException: /mnt/flash/buchholz/eclipse/plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/xulrunner/libnssutil3.so: version `NSSUTIL_3.13' not found (required by /usr/lib64/libnss3.so) at sun.security.pkcs11.Secmod.nssLoadLibrary(Native Method) at sun.security.pkcs11.Secmod.initialize(Secmod.java:203) at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:197) ... 35 more !SUBENTRY 1 org.eclipse.equinox.p2.transport.ecf 4 1002 2012-01-24 16:05:53.634 !MESSAGE Unable to read repository at https://repository.sonatype.org/content/repositories/forge-sites/m2e-disc.... !STACK 0 java.security.ProviderException: Could not initialize NSS at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:201) at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:103) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at sun.security.jca.ProviderConfig$3.run(ProviderConfig.java:262) at sun.security.jca.ProviderConfig$3.run(ProviderConfig.java:244) at java.security.AccessController.doPrivileged(Native Method) at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:244) at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:224) at sun.security.jca.ProviderList.getProvider(ProviderList.java:232) at sun.security.jca.ProviderList$ServiceList.tryGet(ProviderList.java:433) at sun.security.jca.ProviderList$ServiceList.access$200(ProviderList.java:375) at sun.security.jca.ProviderList$ServiceList$1.hasNext(ProviderList.java:485) at sun.security.jca.GetInstance.getInstance(GetInstance.java:170) at javax.net.ssl.SSLContext.getInstance(SSLContext.java:142) at javax.net.ssl.SSLContext.getDefault(SSLContext.java:85) at javax.net.ssl.SSLSocketFactory.getDefault(SSLSocketFactory.java:119) at org.eclipse.ecf.internal.ssl.ECFSSLSocketFactory.getSSLSocketFactory(ECFSSLSocketFactory.java:38) at org.eclipse.ecf.internal.ssl.ECFSSLSocketFactory.createSocket(ECFSSLSocketFactory.java:63) at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ssl.SSLSocketFactoryModifier.createSocket(SSLSocketFactoryModifier.java:47) at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientSecureProtocolSocketFactory$1.createSocket(ECFHttpClientSecureProtocolSocketFactory.java:29) at org.eclipse.ecf.provider.filetransfer.events.socket.SocketEventCreateUtil.createSocket(SocketEventCreateUtil.java:37) 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.HttpClientFileSystemBrowser.runRequest(HttpClientFileSystemBrowser.java:227) at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.io.IOException: /mnt/flash/buchholz/eclipse/plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/xulrunner/libnssutil3.so: version `NSSUTIL_3.13' not found (required by /usr/lib64/libnss3.so) at sun.security.pkcs11.Secmod.nssLoadLibrary(Native Method) at sun.security.pkcs11.Secmod.initialize(Secmod.java:203) at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:197) ... 35 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10628?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-10628 at 1/24/12 10:51 AM: --------------------------------------------------------------- On a fresh Indigo SR1 installation (Windows 7 64bits), I installed JBoss Central, Maven Examples and the JBoss AS features from the update site. During installation, I checked m2e-wtp, m2e and the mavenarchiver features were also installed. Clicking on the kitchensink quickstart in central, the project was created without errors (no missing connectors). Window->Preferences->Maven->Discover->Open catalogs works. Importing the m2e-wtp projects, m2e discovers and offers me to install the m2e-tycho configurator. Jochen, if you didn't change anything to the stock kitchensink pom.xml and get "Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (execution: default-compile, phase: compile)" that would mean the m2e JDT integration is not installed or started correctly. Is there anything noteworthy your workspace logs (<workspaceroot>/.metadata/.log) Also, you can try diff'ing your eclipse installations when you install m2e directly or from JBT, see if some plugins/features are missing. was (Author: fbricon): On a fresh Indigo SR2 installation (Windows 7 64bits), I installed JBoss Central, Maven Examples and the JBoss AS features from the update site. During installation, I checked m2e-wtp, m2e and the mavenarchiver features were also installed. Clicking on the kitchensink quickstart in central, the project was created without errors (no missing connectors). Window->Preferences->Maven->Discover->Open catalogs works. Importing the m2e-wtp projects, m2e discovers and offers me to install the m2e-tycho configurator. Jochen, if you didn't change anything to the stock kitchensink pom.xml and get "Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (execution: default-compile, phase: compile)" that would mean the m2e JDT integration is not installed or started correctly. Is there anything noteworthy your workspace logs (<workspaceroot>/.metadata/.log) Also, you can try diff'ing your eclipse installations when you install m2e directly or from JBT, see if some plugins/features are missing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10628?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-10628: ---------------------------------------- Fix Version/s: 3.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10628?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-10628: ---------------------------------------- Labels: connectors discovery (was: connectors discovery m2e maven) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10628?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10628: --------------------------------------------- assign to Denis since you are trying to reproduce. If taking too long and no further evidence pass it on to QE for a try. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10628?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-10628: --------------------------------------- Tried to replicate it again and it is the same, no problems. fixing for now to let QA verify it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10628?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-10628. ------------------------------- Verified on JBT 3.3.0.v20120224-2315-H93-Beta1. No problems found. If problem still persist reopen this Jira. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira