db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3700) Get rid of tools/java/empty.jar
Date Mon, 02 Jun 2008 14:25:45 GMT

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

Knut Anders Hatlen commented on DERBY-3700:

The point is that we'll have one less *binary* file under source
control. Since it's a source code repository, I think we should try to
have as few binary files as possible. The patch basically replaces a
binary file with one line of source code that generates a replacement
for it at build-time. Whether it generates an empty jar or an empty
directory is not important, but the ant command for making a directory
was shorter. :)

> Get rid of tools/java/empty.jar
> -------------------------------
>                 Key: DERBY-3700
>                 URL: https://issues.apache.org/jira/browse/DERBY-3700
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Trivial
>         Attachments: d3700.diff
> empty.jar is used to prevent the Java compiler from putting the default Java runtime
libraries in the boot classpath. An empty directory would also work, so we could remove the
jar file from the source repository and instead let the build scripts create an empty directory
for us.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message