June 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-27348) Unidentified dependencies while converting JSF project to maven

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-27348?page=com.atlassian.jira.plug... ] Zbyněk Červinka updated JBIDE-27348: ------------------------------------ Attachment: Snímek obrazovky 2020-06-27 v 15.22.58.png > Unidentified dependencies while converting JSF project to maven > --------------------------------------------------------------- > > Key: JBIDE-27348 > URL: https://issues.redhat.com/browse/JBIDE-27348 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.16.0.Final > Reporter: Zbyněk Červinka > Priority: Major > Fix For: 4.16.0.Final > > Attachments: Snímek obrazovky 2020-06-27 v 15.13.12.png, Snímek obrazovky 2020-06-27 v 15.22.58.png > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27348) Unidentified dependencies while converting JSF project to maven

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-27348?page=com.atlassian.jira.plug... ] Zbyněk Červinka updated JBIDE-27348: ------------------------------------ Steps to Reproduce: 1) Create new JSF project (JSF 2.2 or JSF 2.3) 2) Convert it to maven (with dependencies) * Context menu -> Configure -> Convert to Maven Project 3) See the following 2 unidentified dependencies: !Snímek obrazovky 2020-06-27 v 15.13.12.png! !Snímek obrazovky 2020-06-27 v 15.22.58.png|thumbnail! was: 1) Create new JSF project (JSF 2.2 or JSF 2.3) 2) Convert it to maven (with dependencies) * Context menu -> Configure -> Convert to Maven Project 3) See the following 2 unidentified dependencies: !Snímek obrazovky 2020-06-27 v 15.13.12.png! > Unidentified dependencies while converting JSF project to maven > --------------------------------------------------------------- > > Key: JBIDE-27348 > URL: https://issues.redhat.com/browse/JBIDE-27348 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.16.0.Final > Reporter: Zbyněk Červinka > Priority: Major > Fix For: 4.16.0.Final > > Attachments: Snímek obrazovky 2020-06-27 v 15.13.12.png, Snímek obrazovky 2020-06-27 v 15.22.58.png > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27348) Unidentified dependencies while converting JSF project to maven

by Zbyněk Červinka (Jira)

Zbyněk Červinka created JBIDE-27348: --------------------------------------- Summary: Unidentified dependencies while converting JSF project to maven Key: JBIDE-27348 URL: https://issues.redhat.com/browse/JBIDE-27348 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsf Affects Versions: 4.16.0.Final Reporter: Zbyněk Červinka Fix For: 4.16.0.Final Attachments: Snímek obrazovky 2020-06-27 v 15.13.12.png -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27345) jbosstools-base cannot be build due to not bumped up version

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-27345?page=com.atlassian.jira.plug... ] Zbyněk Červinka updated JBIDE-27345: ------------------------------------ Component/s: base Fix Version/s: 4.16.0.Final Steps to Reproduce: Clone the *jbosstools-base* repository, try to build it. Sprint: devex #186 July 2020 Estimated Difficulty: Low Affects Version/s: 4.16.0.Final > jbosstools-base cannot be build due to not bumped up version > ------------------------------------------------------------ > > Key: JBIDE-27345 > URL: https://issues.redhat.com/browse/JBIDE-27345 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: base > Affects Versions: 4.16.0.Final > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.16.0.Final > > > h1. *Error description:* > [ERROR] Invalid value of default.version = 4.16.0.AM1 for parent = 4.16.0.Final-SNAPSHOT ! > Must set default.version = 4.16.0.Final (or = 4.16.0.Final) in this file: > /Users/zcervink/git/jbosstools-base/foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/properties/internal/currentversion.properties > > ... > > [*INFO*] *BUILD FAILURE* > [*INFO*] *------------------------------------------------------------------------* > [*INFO*] Total time: 40.428 s > [*INFO*] Finished at: 2020-06-25T13:44:53+02:00 > [*INFO*] *------------------------------------------------------------------------* > [*ERROR*] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce *(foundation-core-default-version-check)* on project org.jboss.tools.foundation.core: *Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.* -> *[Help 1]* > [*ERROR*] > [*ERROR*] To see the full stack trace of the errors, re-run Maven with the *-e* switch. > [*ERROR*] Re-run Maven using the *-X* switch to enable full debug logging. > [*ERROR*] > [*ERROR*] For more information about the errors and possible solutions, please read the following articles: > [*ERROR*] *[Help 1]* [http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException] > [*ERROR*] > [*ERROR*] After correcting the problems, you can resume the build with the command > [*ERROR*] *mvn <args> -rf :org.jboss.tools.foundation.core* -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27345) jbosstools-base cannot be build due to not bumped up version

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-27345?page=com.atlassian.jira.plug... ] Zbyněk Červinka closed JBIDE-27345. ----------------------------------- > jbosstools-base cannot be build due to not bumped up version > ------------------------------------------------------------ > > Key: JBIDE-27345 > URL: https://issues.redhat.com/browse/JBIDE-27345 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: base > Affects Versions: 4.16.0.Final > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.16.0.Final > > > h1. *Error description:* > [ERROR] Invalid value of default.version = 4.16.0.AM1 for parent = 4.16.0.Final-SNAPSHOT ! > Must set default.version = 4.16.0.Final (or = 4.16.0.Final) in this file: > /Users/zcervink/git/jbosstools-base/foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/properties/internal/currentversion.properties > > ... > > [*INFO*] *BUILD FAILURE* > [*INFO*] *------------------------------------------------------------------------* > [*INFO*] Total time: 40.428 s > [*INFO*] Finished at: 2020-06-25T13:44:53+02:00 > [*INFO*] *------------------------------------------------------------------------* > [*ERROR*] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce *(foundation-core-default-version-check)* on project org.jboss.tools.foundation.core: *Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.* -> *[Help 1]* > [*ERROR*] > [*ERROR*] To see the full stack trace of the errors, re-run Maven with the *-e* switch. > [*ERROR*] Re-run Maven using the *-X* switch to enable full debug logging. > [*ERROR*] > [*ERROR*] For more information about the errors and possible solutions, please read the following articles: > [*ERROR*] *[Help 1]* [http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException] > [*ERROR*] > [*ERROR*] After correcting the problems, you can resume the build with the command > [*ERROR*] *mvn <args> -rf :org.jboss.tools.foundation.core* -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27079) ADT is not correctly installed

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27079?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-27079: ------------------------------------- Sprint: devex #186 July 2020 > ADT is not correctly installed > ------------------------------ > > Key: JBIDE-27079 > URL: https://issues.redhat.com/browse/JBIDE-27079 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.14.0.Final > Reporter: Josef Kopriva > Assignee: Stephane Bouchet > Priority: Major > Fix For: 4.16.x > > Attachments: Capture d’écran de 2020-03-23 12-44-45.png, image-2020-03-03-07-52-43-757.png > > > Android SDK is not correctly installed, after installation and restart there is error message: > !image-2020-03-03-07-52-43-757.png|thumbnail! > When I click on OPenSDK manager, nothing happens. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27347) pull yaml editor from its own repository

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27347?page=com.atlassian.jira.plug... ] Jeff MAURY commented on JBIDE-27347: ------------------------------------ Can we get the changelog between 1.0.18 and 1.0.20 ? > pull yaml editor from its own repository > ---------------------------------------- > > Key: JBIDE-27347 > URL: https://issues.redhat.com/browse/JBIDE-27347 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.16.0.AM1 > Reporter: Stephane Bouchet > Priority: Major > > Currently, the YAML editor is pulled from springide 3.x repo, which is deprecated from a while. > the original issue for using a YAML editor is JBIDE-21377. > looking at the springide repo, the YAML editor is pulled from another repo: > https://dist.springsource.com/release/TOOLS/third-party/yedit > and I can also find a marketplace entry for the same editor: > [http://dadacoalition.org/yedit|http://dadacoalition.org/yedit/] from [htt...] > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27347) pull yaml editor from its own repository

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27347?page=com.atlassian.jira.plug... ] Stephane Bouchet commented on JBIDE-27347: ------------------------------------------ the problem is that springide stopped to use the official repo since 2015 ([https://github.com/spring-projects/spring-ide/commit/6869d4b98495cde54588... order to provide signed content and did not update version since so we have a choice : * use official yaml 1.0.20 / not signed * use unofficial yaml 1.0.18 / signed * use another yaml editor since there is no update for quite some time CC [~jeffmaury] > pull yaml editor from its own repository > ---------------------------------------- > > Key: JBIDE-27347 > URL: https://issues.redhat.com/browse/JBIDE-27347 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.16.0.AM1 > Reporter: Stephane Bouchet > Priority: Major > > Currently, the YAML editor is pulled from springide 3.x repo, which is deprecated from a while. > the original issue for using a YAML editor is JBIDE-21377. > looking at the springide repo, the YAML editor is pulled from another repo: > https://dist.springsource.com/release/TOOLS/third-party/yedit > and I can also find a marketplace entry for the same editor: > [http://dadacoalition.org/yedit|http://dadacoalition.org/yedit/] from [htt...] > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27347) pull yaml editor from its own repository

by Stephane Bouchet (Jira)

Stephane Bouchet created JBIDE-27347: ---------------------------------------- Summary: pull yaml editor from its own repository Key: JBIDE-27347 URL: https://issues.redhat.com/browse/JBIDE-27347 Project: Tools (JBoss Tools) Issue Type: Task Components: target-platform Affects Versions: 4.16.0.AM1 Reporter: Stephane Bouchet Currently, the YAML editor is pulled from springide 3.x repo, which is deprecated from a while. the original issue for using a YAML editor is JBIDE-21377. looking at the springide repo, the YAML editor is pulled from another repo: https://dist.springsource.com/release/TOOLS/third-party/yedit and I can also find a marketplace entry for the same editor: [http://dadacoalition.org/yedit|http://dadacoalition.org/yedit/] from [htt...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24551) reactivate Sonarcloud.io updates for jbosstools-server

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-24551?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-24551. --------------------------------- Resolution: Done Closing - see my previous comment. > reactivate Sonarcloud.io updates for jbosstools-server > ------------------------------------------------------ > > Key: JBIDE-24551 > URL: https://issues.redhat.com/browse/JBIDE-24551 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, server > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Priority: Major > Fix For: 4.16.0.Final > > Attachments: screenshot-1.png, screenshot-2.png > > > last update was the 21 February > !screenshot-1.png|thumbnail! > https://sonarcloud.io/dashboard?id=org.jboss.tools%3Aserver.all -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

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 June 2020