Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <23293655.501631285956873252.JavaMail.jira@thor>
Date: Fri, 1 Oct 2010 14:14:33 -0400 (EDT)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-3986) Stop dropping build artifacts in the
 subversion-controlled source tree
In-Reply-To: <2102942595.1229016704509.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas updated DERBY-3986:
---------------------------------

    Attachment: derby-3986-03-aa-release.diff

Attaching derby-3986-03-aa-release.diff. This patch changes the build so that release artifacts are now dropped outside subversion-controlled space as other build artifacts are. This change should not disrupt the build for most people. Committed at subversion revision 1003607.

This patch makes a number of changes:

1) Creates a new artifact directory called "release" rooted off ${out.base}. This new directory sits parallel to classes, generated, jars, and javadoc. This directory will now be created every time you build Derby and the directory will be deleted when you issue an "ant clobber".

2) Drops all release artifacts into the new release tree. This includes snapshots, release distributions, and the temporary directories needed to create them.

3) Eliminates the packaging.properties file, which release managers were expected to create from packaging.tmpl. Instead, the release machinery now just uses packaging.tmpl directly. Rather than creating packaging.properties to override the default values in packaging.tmpl, now you just override the release properties the same way you override other build properties: i.e., by putting overrides in your ant.properties or specifying them on the command line.

4) Makes environment variables visible to the release-building machinery. This makes it possible for you to phrase your ant.properties in terms of environment variables which can be overridden in your shell or script. An ant reference to an environment variable looks like this:

  ${env.FOO}

where FOO is an environment variable set by a shell statement like this:

  export FOO=/bar/wibble/wombat


Touches the following files:

---------

 M     .

Adds the new release directory to the list of files ignored by "svn status".


---------

M      tools/ant/properties/dirs.properties
M      tools/ant/properties/packaging.tmpl

Defines release directories relative to ${out.base}.


---------

M      build.xml
M      tools/release/build.xml

Wires these changes into the release machinery.


> Stop dropping build artifacts in the subversion-controlled source tree
> ----------------------------------------------------------------------
>
>                 Key: DERBY-3986
>                 URL: https://issues.apache.org/jira/browse/DERBY-3986
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.5.1.1
>            Reporter: Rick Hillegas
>         Attachments: chmod.diff, derby-3986-01-aa-checkCompilerLevel.diff, derby-3986-02-af-sanity-bin-toursdb-storeless-release.diff, derby-3986-02-ag-sanity-bin-toursdb-storeless-release.diff, derby-3986-02-ah-sanity-bin-toursdb-storeless-release.diff, derby-3986-03-aa-release.diff, filemode.diff, mk-sanity-dir.diff
>
>
> The Derby build drops various artifacts in the source tree. Build artifacts should not muddy subversion controlled directories but should, instead, go into temporary directories created by the the build. 
> The following is a (perhaps partial) list of artifacts currently dropped into subversion-controlled space:
> Sanity directives
> Generated grammars
> The English error messages
> Data type class sizes
> Toursdb
> Temporary class for verifying compiler level

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