[JBoss JIRA] (JBIDE-19962) org.jboss.tools.cdi.extension.core.test.ExtensionCoreAllTests failure on Windows
by Daniel Azarov (JIRA)
Daniel Azarov created JBIDE-19962:
-------------------------------------
Summary: org.jboss.tools.cdi.extension.core.test.ExtensionCoreAllTests failure on Windows
Key: JBIDE-19962
URL: https://issues.jboss.org/browse/JBIDE-19962
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi, cdi-extensions
Environment: Windows 8
Reporter: Daniel Azarov
{code}
-------------------------------------------------------------------------------
Test set: org.jboss.tools.cdi.extension.core.test.ExtensionCoreAllTests
-------------------------------------------------------------------------------
Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.896 sec <<< FAILURE! - in org.jboss.tools.cdi.extension.core.test.ExtensionCoreAllTests
testDummy(org.jboss.tools.cdi.extension.core.test.jms.JMSContextTest) Time elapsed: 0.007 sec
testBatchInjection(org.jboss.tools.cdi.extension.core.test.batch.BatchValidationTest) Time elapsed: 0.001 sec
Batch Core Project Tests(org.jboss.tools.cdi.extension.core.test.batch.BatchCoreTestSetup) Time elapsed: 0.058 sec <<< ERROR!
org.eclipse.core.internal.resources.ResourceException: Problems encountered while deleting resources.
at org.eclipse.core.internal.resources.Resource.delete(Resource.java:794)
at org.eclipse.core.internal.resources.Project.delete(Project.java:323)
at org.jboss.tools.cdi.extension.core.test.batch.BatchCoreTestSetup.tearDown(BatchCoreTestSetup.java:48)
testExceptions(org.jboss.tools.common.base.test.validation.ValidationExceptionTest) Time elapsed: 0.001 sec
testLogging(org.jboss.tools.common.base.test.validation.ValidationExceptionTest) Time elapsed: 0.008 sec
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-18316) Errors in project after import WildFly quickstarts (bundled XSD)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18316?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18316:
---------------------------------------------
this should not have been detached - fixing the xsd issues affecting JAva EE 7 and other of our prodcts was actually supposed to have happend for Mars.
[~vrubezhny] or [~rob.stryker] did you guys ever look into fixing these ?
> Errors in project after import WildFly quickstarts (bundled XSD)
> ----------------------------------------------------------------
>
> Key: JBIDE-18316
> URL: https://issues.jboss.org/browse/JBIDE-18316
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
>
> After importing all modules from https://github.com/wildfly/quickstart into JBDS 8.0.0.CR1b, a few projects have errors because of XML validation, such as:
> {code}
> Referenced file contains errors (jar:file:/Users/xcoulon/DevToolz/ide/jbossdevstudio800CR1b/studio/plugins/org.jboss.tools.as.catalog_3.0.0.CR1-v20140905-1648-B75.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-18316) Errors in project after import WildFly quickstarts (bundled XSD)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18316?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18316:
----------------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.x)
> Errors in project after import WildFly quickstarts (bundled XSD)
> ----------------------------------------------------------------
>
> Key: JBIDE-18316
> URL: https://issues.jboss.org/browse/JBIDE-18316
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
>
> After importing all modules from https://github.com/wildfly/quickstart into JBDS 8.0.0.CR1b, a few projects have errors because of XML validation, such as:
> {code}
> Referenced file contains errors (jar:file:/Users/xcoulon/DevToolz/ide/jbossdevstudio800CR1b/studio/plugins/org.jboss.tools.as.catalog_3.0.0.CR1-v20140905-1648-B75.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19919) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Base]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19919?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19919:
------------------------------------
Workaround:
{quote}
To ensure you're seeing the correct version of Central (from Beta1 / Beta1x, not Beta2 / master), you will need to add lines similar to these your eclipse.ini file after the -vmargs line for the appropriate version & URLs:
{code}
-Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.Beta1/jbosstools-directory.xml
-Djboss.discovery.site.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.Beta1/
-Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Beta1/
-Djboss.discovery.earlyaccess.list.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Beta1/jbosstools-earlyaccess.properties
{code}
{quote}
This can be fixed w/ a respin of Base and all the aggregate sites that include Base.
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Base]
> --------------------------------------------------
>
> Key: JBIDE-19919
> URL: https://issues.jboss.org/browse/JBIDE-19919
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core, usage
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [Base]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Beta1x
> git push origin jbosstools-4.3.0.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and
> * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19919) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Base]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19919?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-19919 at 6/5/15 5:36 PM:
------------------------------------------------------------
Seems that the root pom in the Beta1 branch references the Beta2 parent pom, because the change to use Beta2 parent pom happened BEFORE the Beta1x branch was created.
https://github.com/jbosstools/jbosstools-base/commits/jbosstools-4.3.0.Be...
So... org.jboss.tools.foundation.core thinks it's version 4.3.0.Beta2, not Beta1. This will confuse ide-config.properties into resolving the wrong version of Central. :(
was (Author: nickboldt):
Seems that the root pom in the Beta1 branch references the Beta2 parent pom, because the change to use Beta2 parent pom happened BEFORE the Beta1x branch was created.
So... org.jboss.tools.foundation.core thinks it's version 4.3.0.Beta2, not Beta1. This will confuse ide-config.properties into resolving the wrong version of Central. :(
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Base]
> --------------------------------------------------
>
> Key: JBIDE-19919
> URL: https://issues.jboss.org/browse/JBIDE-19919
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core, usage
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [Base]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Beta1x
> git push origin jbosstools-4.3.0.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and
> * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19631) Switch Tern.java dependency version range to the only version after code freeze
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19631?page=com.atlassian.jira.plugi... ]
Victor Rubezhny edited comment on JBIDE-19631 at 6/5/15 5:29 PM:
-----------------------------------------------------------------
[~dgolovin], [~akazakov], Could you please perform those test cases manually? Does CA works for you? Do you see any exceptions/errors?
Cause I still have the following results:
{code}
[INFO] Reactor Summary:
[INFO]
[INFO] jbosstools-jst ..................................... SUCCESS [ 2.043 s]
[INFO] jst.plugins ........................................ SUCCESS [ 0.005 s]
[INFO] org.jboss.tools.jst.web ............................ SUCCESS [ 15.103 s]
[INFO] org.jboss.tools.jst.web.kb ......................... SUCCESS [ 5.360 s]
[INFO] org.jboss.tools.jst.web.ui ......................... SUCCESS [ 12.741 s]
[INFO] org.jboss.tools.jst.jsdt ........................... SUCCESS [ 0.534 s]
[INFO] org.jboss.tools.jst.angularjs ...................... SUCCESS [ 1.867 s]
[INFO] org.jboss.tools.jst.js ............................. SUCCESS [ 0.613 s]
[INFO] jst.tests .......................................... SUCCESS [ 0.020 s]
[INFO] org.jboss.tools.jst.jsp.base.test .................. SUCCESS [ 1.151 s]
[INFO] org.jboss.tools.jst.web.kb.test .................... SUCCESS [02:38 min]
[INFO] org.jboss.tools.jst.web.test ....................... SUCCESS [01:00 min]
[INFO] org.jboss.tools.jst.web.ui.test .................... SUCCESS [08:36 min]
[INFO] org.jboss.tools.jst.angularjs.test ................. SUCCESS [01:58 min]
[INFO] org.jboss.tools.jst.jsdt.test ...................... SUCCESS [ 31.812 s]
[INFO] jst.features ....................................... SUCCESS [ 0.035 s]
[INFO] org.jboss.tools.jst.feature ........................ SUCCESS [ 0.666 s]
[INFO] org.jboss.tools.jst.test.feature ................... SUCCESS [ 0.323 s]
[INFO] org.jboss.tools.jst.jsdt.feature ................... SUCCESS [ 0.162 s]
[INFO] org.jboss.tools.jst.angularjs.feature .............. SUCCESS [ 0.135 s]
[INFO] jst.site ........................................... SUCCESS [01:46 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 19:05 min
[INFO] Finished at: 2015-06-06T01:18:00+04:00
[INFO] Final Memory: 97M/840M
[INFO] ------------------------------------------------------------------------
{code}
having in josstools-jst/pom.xml the following tern.java/angularjs-eclipse versions:
{code}
<properties>
<tycho.scmUrl>scm:git:https://github.com/jbosstools/jbosstools-jst.git</tycho.scmUrl>
<tern.reqs.url>http://download.jboss.org/jbosstools/updates/requirements/tern</tern.reqs.url>
<tern.version>0.10.0.201506020610</tern.version>
<angularjs.reqs.url>http://download.jboss.org/jbosstools/updates/requirements/angularjs</angularjs.reqs.url>
<angularjs.version>0.10.0.201506020622</angularjs.version>
</properties>
{code}
was (Author: vrubezhny):
[~dgolovin], [~akazakov], Could you please perform those test cases manually? Does CA works for you? Do you see any exceptions/errors?
> Switch Tern.java dependency version range to the only version after code freeze
> -------------------------------------------------------------------------------
>
> Key: JBIDE-19631
> URL: https://issues.jboss.org/browse/JBIDE-19631
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha1
> Reporter: Alexey Kazakov
> Assignee: Victor Rubezhny
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
>
> In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied.
> For every development/stable release the open range should be replaced to specific version.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19961) org.jboss.tools.common.core.test.WebUtilsTest failure on Windows
by Daniel Azarov (JIRA)
Daniel Azarov created JBIDE-19961:
-------------------------------------
Summary: org.jboss.tools.common.core.test.WebUtilsTest failure on Windows
Key: JBIDE-19961
URL: https://issues.jboss.org/browse/JBIDE-19961
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Environment: Windows 8.1
Reporter: Daniel Azarov
{code}
-------------------------------------------------------------------------------
Test set: org.jboss.tools.common.core.test.CommonCoreTestSuite
-------------------------------------------------------------------------------
Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 16.24 sec <<< FAILURE! - in org.jboss.tools.common.core.test.CommonCoreTestSuite
testGetWebContentPaths(org.jboss.tools.common.core.test.WebUtilsTest) Time elapsed: 9.101 sec
testGeWebRootFolders(org.jboss.tools.common.core.test.WebUtilsTest) Time elapsed: 1.293 sec
testFindResource(org.jboss.tools.common.core.test.WebUtilsTest) Time elapsed: 0.889 sec <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.jboss.tools.common.core.test.WebUtilsTest.testFindResource(WebUtilsTest.java:205)
testFirstWebContentPath(org.jboss.tools.common.core.test.WebUtilsTest) Time elapsed: 1.17 sec
testGetWebPath(org.jboss.tools.common.core.test.WebUtilsTest) Time elapsed: 0.872 sec
testGetWebRootFolder(org.jboss.tools.common.core.test.WebUtilsTest) Time elapsed: 1.119 sec
testCreateHttpURLConnection(org.jboss.tools.common.core.test.HttpUtilTest) Time elapsed: 0.03 sec
testInputStreamReader(org.jboss.tools.common.core.test.HttpUtilTest) Time elapsed: 0.917 sec
testDefaultBeanName(org.jboss.tools.common.core.test.BeanUtilTest) Time elapsed: 0.001 sec
testSubtypesInJar(org.jboss.tools.common.core.test.JandexTest) Time elapsed: 0.57 sec
testAnnotationInJar(org.jboss.tools.common.core.test.JandexTest) Time elapsed: 0.233 sec
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months