db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6945) Re-package Derby as a collection of jigsaw modules
Date Sun, 25 Feb 2018 18:58:00 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376195#comment-16376195

Bryan Pendleton commented on DERBY-6945:

Hi Rick, I collected some more information about the strange ant behavior I'm seeing on Fedora.

I do seem to have the same set of build.xml files that you have. So that's good, and I don't
think it's the source of my problems. I must have been looking at output from before I updated
to the most recent head of trunk, sorry for that red herring.

I attached 'weirdAnt.out', which is the output of 'ant -verbose all' in the case where I have
deliberately introduced a compile error into a Java file. If you jump down to around line
9185, you can see the section of the output that seems relevant.

The actual error is at line 9283. It's certainly the correct error message from javac.

But then processing continues, as you can see.

I seem to be using Ant 1.9.5 on Fedora, while I use Ant 1.9.9 on Windows.

And I'm using jdk 9.0.1 on Fedora, while I use jdk 9.0.4 on Windows.

Dunno what any of that means. Hopefully the 'ant -verbose' output has a clue that you can

For the time being, I will be careful not to make any compile errors in my Java :)

> 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:
>            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, weirdAnt.out
> 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

This message was sent by Atlassian JIRA

View raw message