[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376184#comment-16376184
]
Bryan Pendleton commented on DERBY-6945:
----------------------------------------
Good news! It seems that the only regression test that's actually failing for
me on Windows (other than my own mistakes :) ), is VetJigsawTest.
I get:
{code:java}
[Error/failure logged at Sat Feb 24 16:28:45 PST 2018]
java.lang.StringIndexOutOfBoundsException: begin 0, end -1, length 36
at java.base/java.lang.String.checkBoundsBeginEnd(String.java:3116)
at java.base/java.lang.String.substring(String.java:1885)
at
org.apache.derbyTesting.functionTests.tests.lang.VetJigsawTest.test_jarContents(VetJigsawTest.java:107)
{code}
I put a bit of debugging code into VetJigsawTest and I gathered this data:
{code}
[junit] Running
org.apache.derbyTesting.functionTests.tests.lang.VetJigsawTest
[junit] className=org.apache.derby.impl.jdbc.EmbedConnection
[junit] derbyURL=file:/C:/Users/Bryan/derby/trunk/classes/
[junit] derbyJarFileName=/C:/Users/Bryan/derby/trunk/classes/
{code}
I think the issue is that I am currently running my tests from classes, not
from jars.
Curiously, I didn't seem to get this problem on my Fedora system, where I was
also running from classes, not from jars.
But as we've seen there appear to be other problems with my Fedora system, so
let's discount that as bad reporting on my part.
Is VetJigsawTest a new test? Can you have a peek at it?
> Re-package Derby as a collection of jigsaw modules
> --------------------------------------------------
>
> Key: DERBY-6945
> URL: https://issues.apache.org/jira/browse/DERBY-6945
> Project: Derby
> Issue Type: Improvement
> Affects Versions: 10.13.1.2
> Reporter: Rick Hillegas
> Priority: Major
> Attachments: derby-6945-01-aa-remove_derbyPreBuild_dep.diff,
> derby-6945-02-ab-newDerbySharedJar.diff,
> derby-6945-02-ac-newDerbySharedJar.diff, derby-6945-03-aa-partitionTest.diff,
> derby-6945-04-aa-moveRunClass.diff,
> derby-6945-05-aa-removeRedundant_Attribute_SQLState.diff,
> derby-6945-06-aa-removeOtherSharedDuplicates.diff,
> derby-6945-07-aa-net_client_overlap.diff,
> derby-6945-08-aa-move_shared_iapi_under_shared.diff,
> derby-6945-08-ab-move_shared_iapi_under_shared.diff,
> derby-6945-08-ad-move_shared_iapi_under_shared.diff,
> derby-6945-09-ab-moveInternalDriver.diff, derby-6945-10-aa-moveDriver42.diff,
> derby-6945-11-ab-moveAutoloadedDriver.diff,
> derby-6945-12-ab-moveClientDataSourceInterface.diff,
> derby-6945-13-aa-create-ClientAutoloadedDriver.diff,
> derby-6945-14-aa-moveMoreEmbeddedClassesOutOfPublicAPI.diff,
> derby-6945-15-aa-moveMoreClientClassesOutOfPublicAPI.diff,
> derby-6945-16-aa-consolidatePublicAPI.diff,
> derby-6945-17-aa-resealPackagesIn-derbyshared.diff,
> derby-6945-18-aa-resealLocalizationPackage.diff,
> derby-6945-19-ad-movePublicAPIintoToolsJar.diff,
> derby-6945-20-aa-removeClasslister.diff,
> derby-6945-21-aa-simplifyBuildScripts.diff,
> derby-6945-21-ab-simplifyBuildScripts.diff,
> derby-6945-XX-moveDataSourceFactories, jdeps.out.tar
>
>
> Once we commit to building with Java 9 (see DERBY-6856), we should consider
> re-packaging Derby as a set of jigsaw modules. This would result in a
> different set of release artifacts. This might be a good opportunity to
> address the Tomcat artifactory issues raised by issue DERBY-6944.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
