[JBoss JIRA] (JBIDE-27035) jbosstools-base repo cannot be build after last commit due to not bumped up version
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-27035?page=com.atlassian.jira.plug... ]
Zbyněk Červinka closed JBIDE-27035.
-----------------------------------
Tested and verified several times, issue is now resolved and fixed, I am closing this JIRA.
> jbosstools-base repo cannot be build after last commit due to not bumped up version
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-27035
> URL: https://issues.redhat.com/browse/JBIDE-27035
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: base, build
> Affects Versions: 4.14.0.Final
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Blocker
> Fix For: 4.14.0.Final
>
>
> jbosstools-base repo cannot be build after last commit due to not bumped up version
> h2. *Error description:*
> {code:java}
> [ERROR] Invalid value of default.version = 4.14.0.AM1 for parent = 4.14.0.Final-SNAPSHOT !
> Must set default.version = 4.14.0.Final (or = 4.14.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
> ...
> [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]
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (JBIDE-27006) Several maven.itests tests fail sporadically due to timeouts (missing wait statement or short time period)
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-27006?page=com.atlassian.jira.plug... ]
Zbyněk Červinka closed JBIDE-27006.
-----------------------------------
Issue is resolved, I am closing this issue.
> Several maven.itests tests fail sporadically due to timeouts (missing wait statement or short time period)
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-27006
> URL: https://issues.redhat.com/browse/JBIDE-27006
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.14.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Minor
> Fix For: 4.14.0.Final
>
> Attachments: org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testCompilerArguments.png, org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testProcessorCustomOutput.png, org.jboss.tools.maven.ui.bot.test.configurator.CDIConfiguratorTest.testCDIConfiguratorEjbSeamInternational.png, org.jboss.tools.maven.ui.bot.test.configurator.JSFConfiguratorTest.testJSFConfigurator.png, org.jboss.tools.maven.ui.bot.test.conversion.MavenConversionTest.changeIdentifiedDependency.png
>
>
> h2. List and description of found and fixed issues:
> * *The hasNature() issue* - tests are calling the *hasNature()* method in *AbstractMavenSWTBotTest* abstract class, where a wait condition is missing. While working with the Project facets a popup window with progress bar sometimes show up. During testing it has shown up, that 10 seconds is not enought -> I am putting there 60 seconds
> !org.jboss.tools.maven.ui.bot.test.configurator.JSFConfiguratorTest.testJSFConfigurator.png|thumbnail!
> * *The createEJBProject() issue* - wait statement with too short period of time :
> !org.jboss.tools.maven.ui.bot.test.configurator.CDIConfiguratorTest.testCDIConfiguratorEjbSeamInternational.png|thumbnail!
> * *The createWebProject() issue* - wait statement with too short period of time :
> !org.jboss.tools.maven.ui.bot.test.conversion.MavenConversionTest.changeIdentifiedDependency.png|thumbnail!
> * *The createBasicMavenProject() issue* - wait statement with too short period of time
> !org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testCompilerArguments.png|thumbnail!
> * *The prepareProject() issue* - wait statement with too short period of time
> !org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testProcessorCustomOutput.png|thumbnail!
> * *The testAddRepositoryLinkInConversionWizard() issue* - wait statement with too short period of time
> * *The convertToMavenProject() issue* - wait statement with too short period of time
> * *The testMaterializeLibrary() issue* - wait statement with too short period of time
> * *The createJSFProject() issue* - wait statement with too short period of time
> h2. See the hasNature() issue stacktrace:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: window is available
> at org.eclipse.reddeer.jface.preference.PreferenceDialog.ok(PreferenceDialog.java:119)
> at org.jboss.tools.maven.ui.bot.test.AbstractMavenSWTBotTest.hasNature(AbstractMavenSWTBotTest.java:117)
> at org.jboss.tools.maven.ui.bot.test.configurator.AbstractConfiguratorsTest.checkProjectWithRuntime(AbstractConfiguratorsTest.java:94)
> at org.jboss.tools.maven.ui.bot.test.configurator.JSFConfiguratorTest.testJSFConfigurator(JSFConfiguratorTest.java:82)
> {code}
> h2. See the createEJBProject() issue stacktrace:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running:
> Validating testEJB_CDI
> at org.jboss.tools.maven.ui.bot.test.configurator.AbstractConfiguratorsTest.createEJBProject(AbstractConfiguratorsTest.java:109)
> at org.jboss.tools.maven.ui.bot.test.configurator.CDIConfiguratorTest.testCDIConfiguratorEjbSeamInternational(CDIConfiguratorTest.java:123)
> {code}
> h2. See the createWebProject() issue stacktrace:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running:
> loading https://maven.apache.org/xsd/maven-4.0.0.xsd
> org.jboss.tools.maven.ui.bot.test.AbstractMavenSWTBotTest.createWebProject(AbstractMavenSWTBotTest.java:280)
> at org.jboss.tools.maven.ui.bot.test.conversion.MavenConversionTest.createWithRuntime(MavenConversionTest.java:204)
> at org.jboss.tools.maven.ui.bot.test.conversion.MavenConversionTest.changeIdentifiedDependency(MavenConversionTest.java:123)
> {code}
> h2. See the createBasicMavenProject() issue stackstrace:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: The following jobs are still running:
> Validating test
> at org.eclipse.reddeer.eclipse.core.resources.AbstractResource.open(AbstractResource.java:78)
> at org.jboss.tools.maven.ui.bot.test.AbstractMavenSWTBotTest.openPom(AbstractMavenSWTBotTest.java:331)
> at org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.setCompilerArguments(APTPropertiesPageTest.java:298)
> at org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testCompilerArguments(APTPropertiesPageTest.java:128)
> {code}
> h2. See the prepareProject() issue stackstrace:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: The following jobs are still running:
> Validating test
> at org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.prepareProject(APTPropertiesPageTest.java:410)
> at org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testProcessorCustomOutput(APTPropertiesPageTest.java:192)
> {code}
> h2. See the testAddRepositoryLinkInConversionWizard() issue stackstrace:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running:
> Validating WebProject
> at org.jboss.tools.maven.ui.bot.test.conversion.MavenConversionTest.testAddRepositoryLinkInConversionWizard(MavenConversionTest.java:172)
> {code}
> h2. See the convertToMavenProject() issue stackstrace:
> {code:java}
> at org.eclipse.reddeer.common.wait.WaitWhile.throwWaitTimeOutException(WaitWhile.java:116)
> at org.jboss.tools.maven.ui.bot.test.AbstractMavenSWTBotTest.convertToMavenProject(AbstractMavenSWTBotTest.java:241)
> at org.jboss.tools.maven.ui.bot.test.configurator.JSFConfiguratorTest.testJSFConfigurator(JSFConfiguratorTest.java:81)
> {code}
> h2. See the testMaterializeLibrary() issue stackstrace:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running:
> Validating example
> at org.jboss.tools.maven.ui.bot.test.conversion.MaterializeLibraryTest.testMaterializeLibrary(MaterializeLibraryTest.java:86)
> {code}
> h2. See the createJSFProject() issue stackstrace:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException:
> Timeout after: 60 s.: The following jobs are still running:
> Launching JSFProject7_1.2
> Validating JSFProject7_1.2
> at org.jboss.tools.maven.ui.bot.test.project.JSFProjectTest.createJSFProject(JSFProjectTest.java:72)
> at org.jboss.tools.maven.ui.bot.test.project.JSFProjectTest.createJSFProjectTest_AS7_JSFv2(JSFProjectTest.java:46)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (JBIDE-26503) Several Imported Launcher Application projects has some error in their files after importing
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-26503?page=com.atlassian.jira.plug... ]
Zbyněk Červinka commented on JBIDE-26503:
-----------------------------------------
[~adietish] Now I am adding update for the new LA project with the *Mission: "cache"* and *Runtime: "vert.x red hat"* or *Runtime: "vert.x community"*
1) The *Mission: "cache"* and *Runtime: "vert.x red hat"* is OK (no errors and no warnings)
2) The *Mission: "cache"* and *Runtime: "vert.x community"* - now there is now issue during the import, only dozens of "Failure to transfer ...." errors after import in the Problems view:
!Snímek obrazovky 2020-02-04 v 17.11.48.png|thumbnail!
h3. Red Hat CodeReady Studio version:
Version: 12.14.0.GA
Build id: GA-v20200204-1100-B5837
Build date: 20200204-1100
> Several Imported Launcher Application projects has some error in their files after importing
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-26503
> URL: https://issues.redhat.com/browse/JBIDE-26503
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.10.0.AM1
> Environment: OS X 10.13.6
> Reporter: Zbyněk Červinka
> Assignee: André Dietisheim
> Priority: Major
> Fix For: 4.14.0.Final
>
> Attachments: Snímek obrazovky 2020-02-04 v 15.47.24.png, Snímek obrazovky 2020-02-04 v 15.47.29.png, Snímek obrazovky 2020-02-04 v 16.20.56.png, Snímek obrazovky 2020-02-04 v 17.11.48.png, cache_vert.x_red hat_1.png, cache_vert.x_red hat_2.png
>
>
> Launcher application projects and their errors (description with settings):
> 1) Mission: "crud", Runtime: "thorntail community"
> 2) Mission: "crud", Runtime: "thorntail red hat"
> - 4 missing HTML </p> tags in file "src/licences/bouncy castle licence - licence.html" on line 50, 51, 52, 53
> 3) Mission: "crud", Runtime: "vert.x community"
> 4) Mission: "crud", Runtime: "vert.x red hat"
> - 3 errors in the project:
> a) Failure to transfer org.codehaus.mojo:buildnumber-maven-plugin:pom:1.4 from https://repository.jboss.org/nexus/content/groups/public-jboss/ was cached in the local repository, resolution will not be...
> b) The project was not built since its build path is incomplete. Cannot find the class file for java.lang.Object. Fix the build path then try building this project
> c) The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files
> 5) Mission: "cache", Runtime: "vert.x red hat"
> 6) Mission: "cache", Runtime: "vert.x community"
> - several errors during import and after import (2 images; also in the attachment):
> !cache_vert.x_red hat_2.png|thumbnail! !cache_vert.x_red hat_1.png|thumbnail!
> Maybe several other errors.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months