[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376156#comment-16376156
]
Rick Hillegas commented on DERBY-6945:
--------------------------------------
Hey Bryan,
I have checked out a fresh workspace sync'd to the head of the trunk. I have
done a full build (including jars). Here are the results:
1) The deleted build.xml files do NOT re-appear. Hear are the build scripts
after the full build:
trunk/build.xml
trunk/java/build/build.xml
trunk/java/build/org/apache/derbyBuild/build.xml
trunk/java/build/org/apache/derbyPreBuild/build.xml
trunk/java/client/build.xml
trunk/java/demo/build.xml
trunk/java/demo/scores/build.xml
trunk/java/demo/toursdb/build.xml
trunk/java/drda/build.xml
trunk/java/engine/build.xml
trunk/java/engine/org/apache/derby/loc/build.xml
trunk/java/optional/build.xml
trunk/java/run/build.xml
trunk/java/shared/build.xml
trunk/java/storeless/build.xml
trunk/java/testing/build.xml
trunk/java/tools/build.xml
trunk/tools/l10n/build.xml
trunk/tools/release/build.xml
2) However, I DO see that nast1.jar is changed (checked-out) by the build.
Since this does not happen in my main workspace, I am cautiously hopeful that
my next checkin will fix the problem.
java/testing/org/apache/derbyTesting/functionTests/tests/lang/nast1.jar
3) When I introduce an error into NetworkServerControlImpl, the build
terminates immediately after choking on that file and I see a "BUILD FAILED"
diagnostic at the end.
Thanks,
-Rick
> 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)
