[JBoss JIRA] (JBDS-4823) Multiple: javax.net.ssl.SSLPeerUnverifiedException errors after start CRS
by Stephane Bouchet (Jira)
[ https://issues.redhat.com/browse/JBDS-4823?page=com.atlassian.jira.plugin... ]
Stephane Bouchet commented on JBDS-4823:
----------------------------------------
Tested with 12.16.0.AM1 and jdk11.0.5 and cannot reproduce.
opened error log, no errors.
Checked for updates ( as it seems to be triggered from automatic check for updates ) --> no errors.
open/closed central, activating/deactivating early access --> no errors.
log:
SESSION 2020-05-07 15:52:28.653 -----------------------------------------------
eclipse.buildId=12.16.0.AM1-v20200507-1016-B6313
java.version=11.0.5
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=fr_FR
Framework arguments: -product com.jboss.devstudio.core.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> Multiple: javax.net.ssl.SSLPeerUnverifiedException errors after start CRS
> -------------------------------------------------------------------------
>
> Key: JBDS-4823
> URL: https://issues.redhat.com/browse/JBDS-4823
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: build
> Affects Versions: 12.15.0.AM1
> Reporter: Josef Kopriva
> Assignee: Stephane Bouchet
> Priority: Minor
> Fix For: 12.16.0.AM1
>
>
> There are a lot javax.net.ssl.SSLPeerUnverifiedException errors after start:
> {code:java}
> eclipse.buildId=12.15.0.AM1-v20200325-0554-B6116
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB
> Framework arguments: -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> org.eclipse.equinox.p2.transport.ecf
> Warning
> Wed Mar 25 08:32:41 CET 2020
> Connection to https://devstudio.redhat.com/12/stable/updates/p2.index failed on peer not authenticated. Retry attempt 0 started
> javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
> at java.base/sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:526)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:504)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:437)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:384)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:374)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
> at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1000)
> at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientRetrieveFileTransfer.access$0(HttpClientRetrieveFileTransfer.java:992)
> at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientRetrieveFileTransfer$1.performFileTransfer(HttpClientRetrieveFileTransfer.java:988)
> at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:74)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
> {code:java}
> eclipse.buildId=12.15.0.AM1-v20200325-0554-B6116
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB
> Framework arguments: -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> org.eclipse.equinox.p2.transport.ecf
> Warning
> Wed Mar 25 08:32:44 CET 2020
> Connection to https://devstudio.redhat.com/12/snapshots/updates/discovery.earlyaccess/m... failed on peer not authenticated. Retry attempt 0 started
> javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
> at java.base/sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:526)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:504)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:437)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:384)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:374)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
> at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1000)
> at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientRetrieveFileTransfer.access$0(HttpClientRetrieveFileTransfer.java:992)
> at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientRetrieveFileTransfer$1.performFileTransfer(HttpClientRetrieveFileTransfer.java:988)
> at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:74)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
> {code:java}
> eclipse.buildId=12.15.0.AM1-v20200325-0554-B6116
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB
> Framework arguments: -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> org.eclipse.equinox.p2.transport.ecf
> Warning
> Wed Mar 25 08:32:57 CET 2020
> Connection to http://jope.ow2.org/update/jope/site.xml failed on jope.ow2.org: nodename nor servname provided, or not known. Retry attempt 0 started
> java.net.UnknownHostException: jope.ow2.org: nodename nor servname provided, or not known
> at java.base/java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
> at java.base/java.net.InetAddress$PlatformNameService.lookupAllHostAddr(InetAddress.java:929)
> at java.base/java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1515)
> at java.base/java.net.InetAddress$NameServiceAddresses.get(InetAddress.java:848)
> at java.base/java.net.InetAddress.getAllByName0(InetAddress.java:1505)
> at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1364)
> at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1298)
> at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:45)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:112)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:374)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
> at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1000)
> at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientRetrieveFileTransfer.access$0(HttpClientRetrieveFileTransfer.java:992)
> at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientRetrieveFileTransfer$1.performFileTransfer(HttpClientRetrieveFileTransfer.java:988)
> at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:74)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
> {code:java}
> eclipse.buildId=12.15.0.AM1-v20200325-0554-B6116
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB
> Framework arguments: -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> org.eclipse.equinox.p2.transport.ecf
> Warning
> Wed Mar 25 08:32:57 CET 2020
> Connection to http://jope.ow2.org/update/jope/p2.index failed on jope.ow2.org. Retry attempt 0 started
> java.net.UnknownHostException: jope.ow2.org
> at java.base/java.net.InetAddress$CachedAddresses.get(InetAddress.java:797)
> at java.base/java.net.InetAddress.getAllByName0(InetAddress.java:1505)
> at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1364)
> at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1298)
> at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:45)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:112)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:374)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
> at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1000)
> at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientRetrieveFileTransfer.access$0(HttpClientRetrieveFileTransfer.java:992)
> at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientRetrieveFileTransfer$1.performFileTransfer(HttpClientRetrieveFileTransfer.java:988)
> at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:74)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
> {code:java}
> eclipse.buildId=12.15.0.AM1-v20200325-0554-B6116
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB
> Framework arguments: -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> org.eclipse.equinox.p2.transport.ecf
> Warning
> Wed Mar 25 08:33:00 CET 2020
> Connection to http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.1... failed on peer not authenticated. Retry attempt 0 started
> javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
> at java.base/sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:526)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:504)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:437)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:384)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:374)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
> at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1000)
> at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientRetrieveFileTransfer.access$0(HttpClientRetrieveFileTransfer.java:992)
> at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientRetrieveFileTransfer$1.performFileTransfer(HttpClientRetrieveFileTransfer.java:988)
> at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:74)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
> This is probably related to JDK11 and its similar to JBIDE-27066.
> I have not seen this errors with JDK11.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (JBIDE-27262) Wildfly 19 not recognized as JEE 8 compliant in eclipse
by Juan Antonio Viñuales Martínez (Jira)
[ https://issues.redhat.com/browse/JBIDE-27262?page=com.atlassian.jira.plug... ]
Juan Antonio Viñuales Martínez updated JBIDE-27262:
---------------------------------------------------
Summary: Wildfly 19 not recognized as JEE 8 compliant in eclipse (was: Wildfly 19 nor recognized as JEE 8 compliant in eclipse)
> Wildfly 19 not recognized as JEE 8 compliant in eclipse
> -------------------------------------------------------
>
> Key: JBIDE-27262
> URL: https://issues.redhat.com/browse/JBIDE-27262
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.15.0.Final
> Reporter: Juan Antonio Viñuales Martínez
> Assignee: Robert Stryker
> Priority: Major
> Attachments: error1.png, error2.png
>
>
> In Eclipse (2020-03 version), when creating a new Enterprise Application Project, if you select WildFly 19 as target runtime, the JEE version only goes up to 7. However, if you select WildFly 18 as target runtime, JEE version goes up to 8, as expected.
> Alternatively, if you have already a JEE 8 project, and then you try to add it to an existing WildFly 19 server, you receive the following message:
> The server does not support version 8.0 of the J2EE Enterprise application specification
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (JBIDE-27262) Wildfly 19 nor recognized as JEE 8 compliant in eclipse
by Juan Antonio Viñuales Martínez (Jira)
Juan Antonio Viñuales Martínez created JBIDE-27262:
------------------------------------------------------
Summary: Wildfly 19 nor recognized as JEE 8 compliant in eclipse
Key: JBIDE-27262
URL: https://issues.redhat.com/browse/JBIDE-27262
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.15.0.Final
Reporter: Juan Antonio Viñuales Martínez
Assignee: Robert Stryker
Attachments: error1.png, error2.png
In Eclipse (2020-03 version), when creating a new Enterprise Application Project, if you select WildFly 19 as target runtime, the JEE version only goes up to 7. However, if you select WildFly 18 as target runtime, JEE version goes up to 8, as expected.
Alternatively, if you have already a JEE 8 project, and then you try to add it to an existing WildFly 19 server, you receive the following message:
The server does not support version 8.0 of the J2EE Enterprise application specification
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (JBIDE-27145) Newly created WEB Project and EJB Project with WildFly 19 as a runtime does not have CDI Project Facet enabled after conversion to maven project
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-27145?page=com.atlassian.jira.plug... ]
Zbyněk Červinka updated JBIDE-27145:
------------------------------------
Steps to Reproduce:
1) Add WildFly 19 as runtime into CodeReady studio
2) Create new Web Project or new EJB Project, set WildFly 19 as target runtime while creating them, then finish the New project wizard
3) Convert the newly created project to maven project (Context menu -> Configure -> Convert to Maven Project)
- when the "Create new POM" dialog appears, click finish
- when the "Convert to Maven Dependencies" dialogue opens, click finish
4) Open Context menu -> Properties -> Project Facets
5) See, that the CDI checkbox is disabled (should be enabled according to our tests)
!project_facets.png|thumbnail!
was:
1) Add WildFly 19 as runtime into CodeReady studio
2) Create new Web Project or new EJB Project, set WildFly 19 as target runtime while creating them, then finish the New project wizard
3) Convert the newly created project to maven project (Context menu -> Configure -> Convert to Maven Project)
- when the "Create new POM" dialog appears, click finish
- when the "Convert to Maven Dependencies" dialogue opens, click finish
4) Check the Project Facets, the CDI checkbox will be disabled
!project_facets.png|thumbnail!
> Newly created WEB Project and EJB Project with WildFly 19 as a runtime does not have CDI Project Facet enabled after conversion to maven project
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-27145
> URL: https://issues.redhat.com/browse/JBIDE-27145
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, server
> Affects Versions: 4.15.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Robert Stryker
> Priority: Major
> Fix For: 4.16.0.AM1
>
> Attachments: project_facets.png
>
>
> Red Hat CodeReady Studio version
> Version: 12.14.0.GA
> Build id: GA-v20200323-0744-B6101
> Build date: 20200323-0744
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (JBIDE-27145) Newly created WEB Project and EJB Project with WildFly 19 as a runtime does not have CDI Project Facet enabled after conversion to maven project
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-27145?page=com.atlassian.jira.plug... ]
Zbyněk Červinka updated JBIDE-27145:
------------------------------------
Steps to Reproduce:
1) Add WildFly 19 as runtime into CodeReady studio
2) Create new Web Project or new EJB Project, set WildFly 19 as target runtime while creating them, then finish the New project wizard
3) Convert the newly created project to maven project (Context menu -> Configure -> Convert to Maven Project)
- when the "Create new POM" dialog appears, click finish
- when the "Convert to Maven Dependencies" dialogue opens, click finish
4) Open Context menu -> Properties -> Project Facets
5) See, that the CDI checkbox is disabled (should be enabled according to our tests)
!project_facets.png|thumbnail!
was:
1) Add WildFly 19 as runtime into CodeReady studio
2) Create new Web Project or new EJB Project, set WildFly 19 as target runtime while creating them, then finish the New project wizard
3) Convert the newly created project to maven project (Context menu -> Configure -> Convert to Maven Project)
- when the "Create new POM" dialog appears, click finish
- when the "Convert to Maven Dependencies" dialogue opens, click finish
4) Open Context menu -> Properties -> Project Facets
5) See, that the CDI checkbox is disabled (should be enabled according to our tests)
!project_facets.png|thumbnail!
> Newly created WEB Project and EJB Project with WildFly 19 as a runtime does not have CDI Project Facet enabled after conversion to maven project
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-27145
> URL: https://issues.redhat.com/browse/JBIDE-27145
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, server
> Affects Versions: 4.15.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Robert Stryker
> Priority: Major
> Fix For: 4.16.0.AM1
>
> Attachments: project_facets.png
>
>
> Red Hat CodeReady Studio version
> Version: 12.14.0.GA
> Build id: GA-v20200323-0744-B6101
> Build date: 20200323-0744
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (JBIDE-27145) Newly created WEB Project and EJB Project with WildFly 19 as a runtime does not have CDI Project Facet enabled after conversion to maven project
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-27145?page=com.atlassian.jira.plug... ]
Zbyněk Červinka updated JBIDE-27145:
------------------------------------
Steps to Reproduce:
1) Add WildFly 19 as runtime into CodeReady studio
2) Create new Web Project or new EJB Project, set WildFly 19 as target runtime while creating them, then finish the New project wizard
3) Convert the newly created project to maven project (Context menu -> Configure -> Convert to Maven Project)
- when the "Create new POM" dialog appears, click finish
- when the "Convert to Maven Dependencies" dialogue opens, click finish
4) Check the Project Facets, the CDI checkbox will be disabled
!project_facets.png|thumbnail!
was:
1) Add WildFly 19 as runtime into CodeReady studio
2) Create new Web Project or new EJB Project, set WildFly 19 as target runtime while creating them, then finish the New project wizard
3) Convert the project with dependencies to maven project (use "war" for Web Project and "ejb" for EJB Project as packaging)
4) Check the Project Facets, the CDI checkbox will be disabled
!project_facets.png|thumbnail!
> Newly created WEB Project and EJB Project with WildFly 19 as a runtime does not have CDI Project Facet enabled after conversion to maven project
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-27145
> URL: https://issues.redhat.com/browse/JBIDE-27145
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, server
> Affects Versions: 4.15.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Robert Stryker
> Priority: Major
> Fix For: 4.16.0.AM1
>
> Attachments: project_facets.png
>
>
> Red Hat CodeReady Studio version
> Version: 12.14.0.GA
> Build id: GA-v20200323-0744-B6101
> Build date: 20200323-0744
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (JBIDE-27145) Newly created WEB Project and EJB Project with WildFly 19 as a runtime does not have CDI Project Facet enabled after conversion to maven project
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-27145?page=com.atlassian.jira.plug... ]
Zbyněk Červinka updated JBIDE-27145:
------------------------------------
Steps to Reproduce:
1) Add WildFly 19 as runtime into CodeReady studio
2) Create new Web Project or new EJB Project, set WildFly 19 as target runtime while creating them, then finish the New project wizard
3) Convert the project with dependencies to maven project (use "war" for Web Project and "ejb" for EJB Project as packaging)
4) Check the Project Facets, the CDI checkbox will be disabled
!project_facets.png|thumbnail!
was:
1) Create new Web Project or new EJB Project with WildFly 19 as runtime
2) Convert the project with dependencies to maven project (use "war" for Web Project and "ejb" for EJB Project as packaging)
3) Check the Project Facets, the CDI checkbox will be disabled
!project_facets.png|thumbnail!
> Newly created WEB Project and EJB Project with WildFly 19 as a runtime does not have CDI Project Facet enabled after conversion to maven project
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-27145
> URL: https://issues.redhat.com/browse/JBIDE-27145
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, server
> Affects Versions: 4.15.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Robert Stryker
> Priority: Major
> Fix For: 4.16.0.AM1
>
> Attachments: project_facets.png
>
>
> Red Hat CodeReady Studio version
> Version: 12.14.0.GA
> Build id: GA-v20200323-0744-B6101
> Build date: 20200323-0744
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months