March 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-27081) New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used; on both Javas 8 and 11)

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27081?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27081: ------------------------------- Component/s: jsf > New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used; on both Javas 8 and 11) > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-27081 > URL: https://issues.redhat.com/browse/JBIDE-27081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.14.0.Final > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.15.0.AM1 > > > {code:java} > ERROR] Failed to execute goal on project project123: Could not resolve dependencies for project project123:project123:war:0.0.1-SNAPSHOT: The following artifacts could not be resolved: org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1, org.apache.taglibs:taglibs-standard-spec:jar:1.2.6-RC1, org.apache.taglibs:taglibs-standard-impl:jar:1.2.6-RC1, org.infinispan:infinispan-core:jar:4.2.1.FINAL: Failure to find org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1] > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26855) Download Runtimes: License is not displayed, retrieval errors

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-26855?page=com.atlassian.jira.plug... ] Jeff MAURY commented on JBIDE-26855: ------------------------------------ I tried for master and cannot reproduce (Windows) > Download Runtimes: License is not displayed, retrieval errors > ------------------------------------------------------------- > > Key: JBIDE-26855 > URL: https://issues.redhat.com/browse/JBIDE-26855 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Priority: Major > > Steps: > # EXEC: Preferences > JBoss Tools > JBoss Runtime Detection, hit button "Download" (or access it via new server wizard) > # ASSERT: downloadable servers are listed > # EXEC: select "CDK v3.9.0" & hit "Next" > # EXEC: provide/confirm credentials & hit "Next" > Result: > License is not displayed, an error dialog pops up instead. I'd argue that the license cannot be correctly consented to if it's not displayed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27082) EAP microprofile support

by Robert Stryker (Jira)

Robert Stryker created JBIDE-27082: -------------------------------------- Summary: EAP microprofile support Key: JBIDE-27082 URL: https://issues.redhat.com/browse/JBIDE-27082 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server Reporter: Robert Stryker We are developing Quickstarts application for each specification. Here you have Jiras for quickstarts https://issues.redhat.com/browse/EAP7-1374 Quickstart for MP Config 1.4 PULL REQUEST SENT Martin Stefanko https://issues.redhat.com/browse/EAP7-1375 Quickstart for MP REST-client 1.4 Requirement PULL REQUEST SENT Martin Stefanko https://issues.redhat.com/browse/EAP7-1373 Quickstart for MP Metrics 2.3 Requirement PULL REQUEST SENT Martin Stefanko https://issues.redhat.com/browse/EAP7-1369 Quickstart for MP OpenTracing 1.3 Requirement PULL REQUEST SENT Martin Stefanko https://issues.redhat.com/browse/EAP7-1368 Quickstart for MP Health 2.2 Requirement PULL REQUEST SENT Martin Stefanko https://issues.redhat.com/browse/EAP7-1370 Quickstart for MP Fault Tolerance 2.1 Requirement PULL REQUEST SENT Radoslav Husar https://issues.redhat.com/browse/EAP7-1371 Quickstart for MP JWT 1.1 Requirement REVIEW Darran Lofthouse https://issues.redhat.com/browse/EAP7-1372 Quickstart for MP OpenAPI 1.1.2 Requirement BACKLOG Paul Ferraro -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing

by nimo stephan (Jira)

[ https://issues.redhat.com/browse/JBIDE-26740?page=com.atlassian.jira.plug... ] nimo stephan commented on JBIDE-26740: -------------------------------------- The overall experience of the hot reload could be improved..look at WAD or liberty which needs only a second for server restart in hot deployments..more an issue for wildfly than jboss tools..server restarts actually needs 40-60 seconds only for one server restart..I think reload the deployment will be faster.. I tried it with "\.war$" it does not work.. > add option to Wildfly-Overview to "auto-restart" after publishing > ----------------------------------------------------------------- > > Key: JBIDE-26740 > URL: https://issues.redhat.com/browse/JBIDE-26740 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.12.0.Final > Reporter: nimo stephan > Assignee: Robert Stryker > Priority: Critical > Fix For: 4.14.0.Final > > > Actually, with *Jboss Tools* we can change to automatically *publish* to Wildfly-Server after resources has changed. However, it makes sense *to restart the server automatically* after code/resource is changed and published. > Please add a new option in "Wildfly Server Overview" beneath the "Publishing" called "*Restarting*" with a checkbox. So when user checks "restart after publish", *server will be automatically restarted* after resources has changed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing

by nimo stephan (Jira)

[ https://issues.redhat.com/browse/JBIDE-26740?page=com.atlassian.jira.plug... ] nimo stephan commented on JBIDE-26740: -------------------------------------- The default pattern is "\.jar$". So if it is changed to "\.war$" (also for exploded archives?), then deployment is reloaded on each build for my war-archive. Which pattern must I use to trigger the deployment on every java source code change? > add option to Wildfly-Overview to "auto-restart" after publishing > ----------------------------------------------------------------- > > Key: JBIDE-26740 > URL: https://issues.redhat.com/browse/JBIDE-26740 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.12.0.Final > Reporter: nimo stephan > Assignee: Robert Stryker > Priority: Critical > Fix For: 4.14.0.Final > > > Actually, with *Jboss Tools* we can change to automatically *publish* to Wildfly-Server after resources has changed. However, it makes sense *to restart the server automatically* after code/resource is changed and published. > Please add a new option in "Wildfly Server Overview" beneath the "Publishing" called "*Restarting*" with a checkbox. So when user checks "restart after publish", *server will be automatically restarted* after resources has changed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing

by Robert Stryker (Jira)

[ https://issues.redhat.com/browse/JBIDE-26740?page=com.atlassian.jira.plug... ] Robert Stryker commented on JBIDE-26740: ---------------------------------------- I'm rejecting this issue. But there's an alternative option for you. Inside the server editor, you can set a 'restart pattern' for your deployments. It won't restart the app server entirely, but it will restart the deployment. What that means is instead of just restarting a deployment when a "full publish" is requested by the user, we'll do it any time a specific restart pattern is matched. So when you change a file, we'll copy the changes and add a .dodeploy marker to inform the app server to completely reload the deployment (again, the deployment, not the server). Hope this helps. > add option to Wildfly-Overview to "auto-restart" after publishing > ----------------------------------------------------------------- > > Key: JBIDE-26740 > URL: https://issues.redhat.com/browse/JBIDE-26740 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.12.0.Final > Reporter: nimo stephan > Priority: Critical > Fix For: 4.14.0.Final > > > Actually, with *Jboss Tools* we can change to automatically *publish* to Wildfly-Server after resources has changed. However, it makes sense *to restart the server automatically* after code/resource is changed and published. > Please add a new option in "Wildfly Server Overview" beneath the "Publishing" called "*Restarting*" with a checkbox. So when user checks "restart after publish", *server will be automatically restarted* after resources has changed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing

by Robert Stryker (Jira)

[ https://issues.redhat.com/browse/JBIDE-26740?page=com.atlassian.jira.plug... ] Robert Stryker resolved JBIDE-26740. ------------------------------------ Fix Version/s: 4.14.0.Final Assignee: Robert Stryker Resolution: Rejected Rejecting, won't make changes to upstream. > add option to Wildfly-Overview to "auto-restart" after publishing > ----------------------------------------------------------------- > > Key: JBIDE-26740 > URL: https://issues.redhat.com/browse/JBIDE-26740 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.12.0.Final > Reporter: nimo stephan > Assignee: Robert Stryker > Priority: Critical > Fix For: 4.14.0.Final > > > Actually, with *Jboss Tools* we can change to automatically *publish* to Wildfly-Server after resources has changed. However, it makes sense *to restart the server automatically* after code/resource is changed and published. > Please add a new option in "Wildfly Server Overview" beneath the "Publishing" called "*Restarting*" with a checkbox. So when user checks "restart after publish", *server will be automatically restarted* after resources has changed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27081) New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used; on both Javas 8 and 11)

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27081?page=com.atlassian.jira.plug... ] Josef Kopriva commented on JBIDE-27081: --------------------------------------- [~zcervink] look at this JIRA: https://issues.redhat.com/browse/JBIDE-26727 it can be fixed by adding repo https://repository.jboss.org/nexus/content/groups/public-jboss/ > New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used; on both Javas 8 and 11) > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-27081 > URL: https://issues.redhat.com/browse/JBIDE-27081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.14.0.Final > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > > {code:java} > ERROR] Failed to execute goal on project project123: Could not resolve dependencies for project project123:project123:war:0.0.1-SNAPSHOT: The following artifacts could not be resolved: org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1, org.apache.taglibs:taglibs-standard-spec:jar:1.2.6-RC1, org.apache.taglibs:taglibs-standard-impl:jar:1.2.6-RC1, org.infinispan:infinispan-core:jar:4.2.1.FINAL: Failure to find org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1] > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27081) New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used; on both Javas 8 and 11)

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-27081?page=com.atlassian.jira.plug... ] Zbyněk Červinka commented on JBIDE-27081: ----------------------------------------- [~jkopriva] I have assigned the issue to [~jeffmaury], but you were fixing the "missing JSF 2.3 item while creating new JSF project" issue, so I have decided to inform you too. > New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used; on both Javas 8 and 11) > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-27081 > URL: https://issues.redhat.com/browse/JBIDE-27081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.14.0.Final > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > > {code:java} > ERROR] Failed to execute goal on project project123: Could not resolve dependencies for project project123:project123:war:0.0.1-SNAPSHOT: The following artifacts could not be resolved: org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1, org.apache.taglibs:taglibs-standard-spec:jar:1.2.6-RC1, org.apache.taglibs:taglibs-standard-impl:jar:1.2.6-RC1, org.infinispan:infinispan-core:jar:4.2.1.FINAL: Failure to find org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1] > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27081) New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used; on both Javas 8 and 11)

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-27081?page=com.atlassian.jira.plug... ] Zbyněk Červinka updated JBIDE-27081: ------------------------------------ Summary: New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used; on both Javas 8 and 11) (was: New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used)) > New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used; on both Javas 8 and 11) > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-27081 > URL: https://issues.redhat.com/browse/JBIDE-27081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.14.0.Final > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > > {code:java} > ERROR] Failed to execute goal on project project123: Could not resolve dependencies for project project123:project123:war:0.0.1-SNAPSHOT: The following artifacts could not be resolved: org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1, org.apache.taglibs:taglibs-standard-spec:jar:1.2.6-RC1, org.apache.taglibs:taglibs-standard-impl:jar:1.2.6-RC1, org.infinispan:infinispan-core:jar:4.2.1.FINAL: Failure to find org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1] > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 March 2020