April 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4831) Missing Repository in pom.xml

by Andre Kreienbring (Jira)

[ https://issues.redhat.com/browse/JBDS-4831?page=com.atlassian.jira.plugin... ] Andre Kreienbring edited comment on JBDS-4831 at 4/25/20 7:27 AM: ------------------------------------------------------------------ The same for {quote}[WARNING] The POM for org.apache.activemq:activemq-camel-starter:jar:5.11.0 is missing, no dependency information available{quote} I changed the dependency to: {quote} <dependency> <groupId>org.apache.activemq</groupId> <artifactId>activemq-camel</artifactId> <version>5.11.0</version> </dependency> {quote} and it worked. Why are there so many errors regarding dependencies and repositories? For a newbie like me (with fuse tooling) this means a LOT of searching around the internet to make things work. :-( was (Author: akreienbring): The same for {quote}[WARNING] The POM for org.apache.activemq:activemq-camel-starter:jar:5.11.0 is missing, no dependency information available{quote} I changed the dependency to: {quote} <dependency> <groupId>org.apache.activemq</groupId> <artifactId>activemq-camel</artifactId> <version>5.11.0</version> </dependency> {quote} and it worked? Why are there so many errors regarding dependencies and repositories? For a newbie like me (with fuse tooling) this means a LOT of searching around the internet to make things work. :-( > Missing Repository in pom.xml > ----------------------------- > > Key: JBDS-4831 > URL: https://issues.redhat.com/browse/JBDS-4831 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Affects Versions: 12.15.0.GA > Reporter: Andre Kreienbring > Priority: Critical > > Using CodeReady Studio with Eclipse 202003 I've seen a BUILD Failure when I added the Restlet Component to a route: > {quote}[WARNING] The POM for org.restlet.jee:org.restlet:jar:2.3.12 is missing, no dependency information available > [WARNING] The POM for org.restlet.jee:org.restlet.ext.httpclient:jar:2.3.12 is missing, no dependency information available{quote} > Adding > {quote} <repository> > <id>spring-plugin-repository</id> > <url>https://repo.spring.io/plugins-release</url> > </repository> > {quote}to the pom.xml solved the issue. > The projekt was autogenerated by New -> Fuse Integration Projekt and selecting "Springboot"... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4831) Missing Repository in pom.xml

by Andre Kreienbring (Jira)

Andre Kreienbring created JBDS-4831: --------------------------------------- Summary: Missing Repository in pom.xml Key: JBDS-4831 URL: https://issues.redhat.com/browse/JBDS-4831 Project: Red Hat CodeReady Studio (devstudio) Issue Type: Bug Affects Versions: 12.15.0.GA Reporter: Andre Kreienbring Using CodeReady Studio with Eclipse 202003 I've seen a BUILD Failure when I added the Restlet Component to a route: {quote}[WARNING] The POM for org.restlet.jee:org.restlet:jar:2.3.12 is missing, no dependency information available [WARNING] The POM for org.restlet.jee:org.restlet.ext.httpclient:jar:2.3.12 is missing, no dependency information available{quote} Adding {quote} <repository> <id>spring-plugin-repository</id> <url>https://repo.spring.io/plugins-release</url> </repository> {quote}to the pom.xml solved the issue. The projekt was autogenerated by New -> Fuse Integration Projekt and selecting "Springboot"... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27239) Install IntelliJ Idea, learn the basics to use the IDE, compare to well known Eclipse

by Zbyněk Červinka (Jira)

Zbyněk Červinka created JBIDE-27239: --------------------------------------- Summary: Install IntelliJ Idea, learn the basics to use the IDE, compare to well known Eclipse Key: JBIDE-27239 URL: https://issues.redhat.com/browse/JBIDE-27239 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: qa Reporter: Zbyněk Červinka -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27238) Study and try the quarkus quickstarts

by Zbyněk Červinka (Jira)

Zbyněk Červinka created JBIDE-27238: --------------------------------------- Summary: Study and try the quarkus quickstarts Key: JBIDE-27238 URL: https://issues.redhat.com/browse/JBIDE-27238 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: qa Reporter: Zbyněk Červinka Assignee: Zbyněk Červinka -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27186) Quarkus Tools- Debugger failed to attach: handshake failed - connection prematurally closed

by Marc Baumgartner (Jira)

[ https://issues.redhat.com/browse/JBIDE-27186?page=com.atlassian.jira.plug... ] Marc Baumgartner commented on JBIDE-27186: ------------------------------------------ [~jeffmaury]: I have this on MacOS with 4.14.0.Final in Eclipse 2020-03. I get the following output: {code:java} [INFO] Scanning for projects... [INFO] [INFO] -----------------------< ch.mabaka:journal-app >------------------------ [INFO] Building journal-app 1.0-SNAPSHOT [INFO] --------------------------------[ jar ]--------------------------------- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ journal-app --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ journal-app --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- quarkus-maven-plugin:1.4.1.Final:dev (default-cli) @ journal-app --- OpenJDK 64-Bit Server VM warning: forcing TieredStopAtLevel to full optimization because JVMCI is enabled Listening for transport dt_socket at address: 5005 Debugger failed to attach: handshake failed - connection prematurally closed __ ____ __ _____ ___ __ ____ ______ --/ __ \/ / / / _ | / _ \/ //_/ / / / __/ -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \ --\___\_\____/_/ |_/_/|_/_/|_|\____/___/ 2020-04-24 21:44:57,084 INFO [io.qua.arc.pro.BeanProcessor] (build-27) Found unrecommended usage of private members (use package-private instead) in application beans: - @Inject field ch.mabaka.journal.app.GreetingResource#greetingService 2020-04-24 21:44:57,688 INFO [io.quarkus] (Quarkus Main Thread) journal-app 1.0-SNAPSHOT (powered by Quarkus 1.4.1.Final) started in 1.750s. Listening on: http://0.0.0.0:8080 2020-04-24 21:44:57,688 INFO [io.quarkus] (Quarkus Main Thread) Profile dev activated. Live Coding activated. 2020-04-24 21:44:57,688 INFO [io.quarkus] (Quarkus Main Thread) Installed features: [cdi, resteasy] {code} > Quarkus Tools- Debugger failed to attach: handshake failed - connection prematurally closed > ------------------------------------------------------------------------------------------- > > Key: JBIDE-27186 > URL: https://issues.redhat.com/browse/JBIDE-27186 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: quarkus > Affects Versions: 4.14.0.AM1 > Reporter: Daniele Tasinato > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.16.0.AM1 > > > [INFO] Compiling 4 source files to C:\Users\developer\Documents\findmagazine\findmagazine\target\classes > [INFO] > [INFO] --- quarkus-maven-plugin:1.3.1.Final:dev (default-cli) @ findmagazine --- > Listening for transport dt_socket at address: 5005 > {color:red}Debugger failed to attach: handshake failed - connection prematurally closed{color} > __ ____ __ _____ ___ __ ____ ______ > --/ __ \/ / / / _ | / _ \/ //_/ / / / __/ > -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \ > --\___\_\____/_/ |_/_/|_/_/|_|\____/___/ > 2020-04-04 17:05:04,813 WARN [io.qua.agr.dep.AgroalProcessor] (build-7) The Agroal dependency is present but no JDBC datasources have been defined. > 2020-04-04 17:05:09,416 WARN [io.qua.net.run.NettyRecorder] (Thread-71) Localhost lookup took more than one second, you need to add a /etc/hosts entry to improve Quarkus startup time. On Windows the path is C:\Windows\System32\Drivers\etc\hosts. See https://thoeni.io/post/macos-sierra-java/ for macOS details. > 2020-04-04 17:05:09,455 INFO [io.qua.qua.run.QuartzScheduler] (main) No scheduled business methods found - Quartz scheduler will not be started > 2020-04-04 17:05:09,468 INFO [io.quarkus] (main) findmagazine 1.0.0-SNAPSHOT (powered by Quarkus 1.3.1.Final) started in 6.097s. Listening on: http://0.0.0.0:8080 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27202) Wildfly-19.0.0.Final unable to run services

by Robert Stryker (Jira)

[ https://issues.redhat.com/browse/JBIDE-27202?page=com.atlassian.jira.plug... ] Robert Stryker commented on JBIDE-27202: ---------------------------------------- Hi [~sachinsinghai1008] Does this version also fail to run your service when launched via command line? OR is it only failing when starting the server from eclipse / jbosstools / devstudio / codeready studio / etc? If this version fails to run your application's services even when launched via the command line, then it's not a tooling problem. But if it is successfully running your services when launched on command line, but failing to do so when launched in eclipse, then that would be a tooling issue. Get back to us! We'd love to be able to solve your issue if possible. > Wildfly-19.0.0.Final unable to run services > ------------------------------------------- > > Key: JBIDE-27202 > URL: https://issues.redhat.com/browse/JBIDE-27202 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.14.0.Final > Reporter: sachin singhai > Priority: Major > > I am updating wildfly-19.0.0.Final from Wildfly-18.0.1.Final version. > And this update is unable to run services of my application. > I have done the version upgrade for sub-systems in standalone-full and other jar version which is upgraded. Due to security concerns I am unable to attach complete server.log file > I have checked the server.log file and found that it is failing for below: > 1) 2020-04-14 12:34:28,648 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 51) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "pojo")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found > 2) 2020-04-14 12:34:28,658 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 55) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "sar")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found > at java.xml/javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:196) > 3) 2020-04-14 12:34:29,052 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 37) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "ee")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found > at java.xml/javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:196) > > 4) 2020-04-14 12:34:29,504 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 49) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "messaging-activemq")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found > 5) 2020-04-14 12:34:31,354 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 59) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "webservices")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4826) Installer do not extract EXE file

by Luca Preziati (Jira)

[ https://issues.redhat.com/browse/JBDS-4826?page=com.atlassian.jira.plugin... ] Luca Preziati commented on JBDS-4826: ------------------------------------- Hi, the installer with openJDK 11+28 work. It is really strange. File are missing, do not previously start, and codereadystudio.ini file was missing. There was just an eclipse.ini with this line -startup plugins/org.eclipse.equinox.launcher_1.5.600.v20191014-2022.jar Currently i have codereadystudio.ini with this configuration. -product com.jboss.devstudio.core.product -showsplash platform\:/base/plugins/com.jboss.devstudio.core --launcher.defaultAction openFile -vmargs -Xms512m -Xmx1024m --add-modules=ALL-SYSTEM -Dosgi.instance.area.default=(a)user.home/workspace For other purpouse i change JAVA_HOME to jdk11, before was setted on JAVA jdk8. > Installer do not extract EXE file > ---------------------------------- > > Key: JBDS-4826 > URL: https://issues.redhat.com/browse/JBDS-4826 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.13.0.GA, 12.14.0.GA > Reporter: Luca Preziati > Priority: Blocker > Attachments: exe-missing.jpg, shared-libraries.jpg > > > The installer do not extract exe. > I extract manually from file I extract from this path the exe: codereadystudio-12.14.0.GA-installer-standalone.jar\devstudio\binary\com.jboss.devstudio.core.package.executable.win32.win32.x86_64_12.14.0.GA-v20200305-0719-B6018\ > !exe-missing.jpg|thumbnail! > But the companion shared libraries are missing. > !shared-libraries.jpg|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4814) Container Development Environment 3.2+ (v3.11.157) is marked as [Stopped, Synchronized] while CDK successfully started

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBDS-4814?page=com.atlassian.jira.plugin... ] Ondrej Dockal closed JBDS-4814. ------------------------------- Closing for now, if it appears again, we can reopen. > Container Development Environment 3.2+ (v3.11.157) is marked as [Stopped, Synchronized] while CDK successfully started > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4814 > URL: https://issues.redhat.com/browse/JBDS-4814 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: cdk > Affects Versions: 12.13.0.GA > Reporter: Lei Yu > Assignee: Jeff MAURY > Priority: Major > Fix For: 12.15.0.GA > > Attachments: minishift-2nd-start.log, minishift.log > > > Container Development Environment 3.2+ (v3.11.157) is marked as [Stopped, Synchronized] while CDK successfully started on Windows -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27231) For JBIDE 4.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [server]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27231?page=com.atlassian.jira.plug... ] Stephane Bouchet commented on JBIDE-27231: ------------------------------------------ bump up to parent pom version = 4.16.0.AM1-SNAPSHOT > For JBIDE 4.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [server] > ------------------------------------------------------------------- > > Key: JBIDE-27231 > URL: https://issues.redhat.com/browse/JBIDE-27231 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Reporter: Stephane Bouchet > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.16.0.AM1 > > > For JBIDE 4.16.0.AM1 [server]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.16.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.15.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.15.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.15.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.15.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for server task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27231) For JBIDE 4.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [server]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27231?page=com.atlassian.jira.plug... ] Stephane Bouchet closed JBIDE-27231. ------------------------------------ Resolution: Done > For JBIDE 4.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [server] > ------------------------------------------------------------------- > > Key: JBIDE-27231 > URL: https://issues.redhat.com/browse/JBIDE-27231 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Reporter: Stephane Bouchet > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.16.0.AM1 > > > For JBIDE 4.16.0.AM1 [server]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.16.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.15.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.15.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.15.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.15.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for server task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2020