You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2007/04/20 17:40:17 UTC
[jira] Created: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Create master ant target for generating all release artifacts, including code and doc artifacts
-----------------------------------------------------------------------------------------------
Key: DERBY-2573
URL: https://issues.apache.org/jira/browse/DERBY-2573
Project: Derby
Issue Type: Improvement
Components: Build tools
Affects Versions: 10.3.0.0
Reporter: Rick Hillegas
This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750014#action_12750014 ]
Rick Hillegas commented on DERBY-2573:
--------------------------------------
Thanks for the patch, Myrna.
>I made a target - prepareforrelease - which will do all the little ant steps to prepare for the actual build step; incl clobbering and deleting stuff; checking for sane property set, checking for state.properties existing, checking that tools/ant/packaging.properties exist, ant sane, ant all, ant buildjars, ant clobber, ant insane, ant -Dsane snapshot, ant publishedapi
I took it for a test drive and it worked: it built sane and insane jars which seemed to be the right size. It told me that I needed to remove some directives from my ant.properties--I thought those error messages were helpful.
>It's not dealing with copying the built error list for the reference guide (not sure that's even possible, as we'd have to do an svn commit?) nor with attempting to build the docs, nor any of the other tasks explicitly.
One thing I noticed is that packaging.properties already has a property which tells the build where the docs live. It should be easy to use that property to figure out where to copy rrefexcept71493.dita and then where to cd to so that the docs can be built. It also ought to be possible to run subversion commands from ant. At least, that's what's promised by this web page: http://ant.apache.org/antlibs/svn/index.html . No doubt the devil is in the details.
+1
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Attachments: DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2573:
---------------------------------
Attachment: derby-2573-08-aa-useReleaseVariablesInDocsBuild.diff
Attaching derby-2573-08-aa-useReleaseVariablesInDocsBuild.diff. This patch improves the release-build so that it builds the docs using current release variables. Committed at subversion revision 1023889.
This patch takes advantage of the work done by DERBY-4851 to parameterize the docs build. This patch passes the following variables to the docs build:
copyright year
long release id (e.g., 10.7.1.0)
short release id (e.g. 10.7)
subversion revision stamp
Touches the following files:
----------
M java/build/org/apache/derbyPreBuild/ReleaseProperties.java
Writes some extra properties to release.properties so that the values can be picked up by the release-build and passed to the docs builder.
----------
M build.xml
Passes release properties to docs build as part of building release distributions.
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-2573-01-aa-masterTarget.diff, derby-2573-02-aa-generateReleaseProperties.diff, derby-2573-03-aa-propertyPrompt.diff, derby-2573-04-aa-emptyClient.diff, derby-2573-05-aa-updateReleaseProperties.diff, derby-2573-06-ab-docsClasspath.diff, derby-2573-07-aa-createBranch.diff, derby-2573-08-aa-useReleaseVariablesInDocsBuild.diff, DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas reassigned DERBY-2573:
------------------------------------
Assignee: Rick Hillegas
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2573:
---------------------------------
Labels: releasegeneration (was: )
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Attachments: DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2573:
---------------------------------
Attachment: derby-2573-10-aa-notice.diff
Attaching derby-2573-10-aa-notice.diff. This patch makes the release-build update the NOTICE file with the current copyright year and then check it in. Committed at subversion revision 1023985.
This patch makes the following changes:
1) Splits the NOTICE file up into a number of separate files, one for each software grant.
2) Parameterizes the ending copyright date on the preamble notice.
3) Makes the release-build concatenate all of these files and substitute the copyright token with the current year.
The preamble warns the user that NOTICE shouldn't be edited directly anymore. Instead, the preamble points the reader at the buildnotice target, which shows how the NOTICE file is built.
Touches the following files:
--------
A tools/release/notices
A tools/release/notices/jdbcstubs.txt
A tools/release/notices/xalan.txt
A tools/release/notices/initialgrant.txt
A tools/release/notices/felix.txt
A tools/release/notices/preamble.txt
A tools/release/notices/nisttestgrant.txt
A tools/release/notices/separator.txt
New notice files, one for each grant.
--------
M build.xml
M tools/ant/properties/dirs.properties
Machinery to generate the NOTICE file when the release is built.
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-2573-01-aa-masterTarget.diff, derby-2573-02-aa-generateReleaseProperties.diff, derby-2573-03-aa-propertyPrompt.diff, derby-2573-04-aa-emptyClient.diff, derby-2573-05-aa-updateReleaseProperties.diff, derby-2573-06-ab-docsClasspath.diff, derby-2573-07-aa-createBranch.diff, derby-2573-08-aa-useReleaseVariablesInDocsBuild.diff, derby-2573-09-aa-copySQLStateTableEarlier.diff, derby-2573-10-aa-notice.diff, DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2573:
---------------------------------
Attachment: derby-2573-03-aa-propertyPrompt.diff
Attaching derby-2573-03-aa-propertyPrompt.diff. This patch adds a new ant task, which prompts the user for properties if they haven't been set already. This target lets us move the prompts out of the buildrelease shell script into the ant script, making the release process more portable. Committed at subversion revision 1005922.
Now invoking the master build target is even simpler:
ant "-Ddocs.root=$DOCS_ROOT" -quiet release
Touches the following files:
-----------
A java/build/org/apache/derbyPreBuild/PropertyPrompt.java
New ant Task which prompts the user for a property value if the property is not set already.
-----------
M build.xml
The master release target now prompts for credentials if they weren't specified on the command line.
-----------
M buildrelease
The driving bash shell script is simpler now since it no longer needs to prompts for credentials.
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-2573-01-aa-masterTarget.diff, derby-2573-02-aa-generateReleaseProperties.diff, derby-2573-03-aa-propertyPrompt.diff, DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-2573:
--------------------------------------
Issue & fix info: [Patch Available]
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Attachments: DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2573:
---------------------------------
Attachment: derby-2573-01-aa-masterTarget.diff
Attaching derby-2573-01-aa-masterTarget.diff. This patch expands on the work Myrna did. This patch adds a master release target which builds and signs the distributions. I would appreciate it if another release manager could test-drive the master release target to see if it works for someone other than me (see the "How to Run It" section below).
After the target finishes, release/distributions holds all of the signed artifacts except for the Eclipse ui plugin.
The remainder of this comment addresses the following topics:
o What the Target Does
o How to Run It
o Future Work
o Overview of Changes
-------------- What the Target Does ------------------
The master build target does the following:
o Commits the generated SQLState tables to the docs repository.
o Syncs both the code and doc clients so that they are up to date.
o Builds sane and insane jars.
o Builds the public javadoc and the Eclipse core plugin.
o Builds the user docs.
o Builds and signs the distributions.
-------------- How to Run It ------------------
The master build target can be invoked by a bash script, buildrelease. This script does two jobs for you:
1) Sets the CLASSPATH needed to run the docs build
2) Asks you for security credentials
The very last line of the script is the actual ant command which invokes the master build target. If you don't use bash scripts, you can at least consult buildrelease for how to set up your ant command.
The buildrelease script expects that you have set the DOCS_ROOT environment variable to point at the top directory of your docs client. If you have not done so, the script fails. The script prompts you for your Apache subversion credentials and for your pgp passphrase. Then the script invokes the master build target. So, to build a release, do the following:
export DOCS_ROOT=someplaceInYourFileSystem
cd topDirectoryOfYourCodeClient
./buildrelease
...and answer the questions which buildrelease asks.
Again, if you don't use bash, you can invoke ant directly. Make sure that you have set CLASSPATH to include the libraries needed by the docs build. The actual ant command for invoking the master build target is this:
ant "-Ddocs.root=$DOCS_ROOT" "-Dpgp.passphrase=$pgpPassphrase" "-Dsvn.username=$subversionUserName" "-Dsvn.password=$subversionPassword" -quiet release
-------------- Future Work ------------------
Follow-on patches can add more functionality:
i) Fail the build if the docs and/or code clients have uncommitted work in them.
ii) Prompt for a release string and then update and checkin tools/ant/properties/release.properties accordingly.
-------------- Overview of Changes ------------------
1) Replaced the docs.out variable with docs.root. The former pointed at the output of the docs build while the latter points at the root of the whole docs client. The docs.root variable allows more straightforward references to docs files.
2) Made prepareforrelease check that docs.root has been set to something reasonable.
3) Made prepareforrelease check that your subversion username and password have been specified. These are the subversion credentials which you use to commit work to the Apache repositories. They are used to checkin the generated SQLState tables in your docs client.
4) Made prepareforrelease check that your pgp passphrase has been specified. The passphrase is needed in order to sign the distributions.
5) Synced both the code and docs clients so that they are up to date.
6) Fixed some problems in the setting of the sanity state.
7) Added a master release target which creates and signs the distributions.
Touches the following files:
M java/engine/org/apache/derby/loc/build.xml
M build.xml
M tools/release/build.xml
M tools/ant/properties/packaging.tmpl
M tools/ant/properties/dirs.properties
A buildrelease
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-2573-01-aa-masterTarget.diff, DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-2573:
--------------------------------------
Attachment: DERBY-2573.diff_1notforcommit
I'm attaching a first step for this.
Some of the things I outlined in my comment are actually checked on already by the existing build steps, so may not be necessary...
I made a target - prepareforrelease - which will do all the little ant steps to prepare for the actual build step; incl clobbering and deleting stuff; checking for sane property set, checking for state.properties existing, checking that tools/ant/packaging.properties exist, ant sane, ant all, ant buildjars, ant clobber, ant insane, ant -Dsane snapshot, ant publishedapi
That part works well enough and I think it's worth committing.
It's not dealing with copying the built error list for the reference guide (not sure that's even possible, as we'd have to do an svn commit?) nor with attempting to build the docs, nor any of the other tasks explicitly.
I played with a second target (in the current patch) that's *not* ready for commit: 'release'. I tried to make an antcall to the 'release' target in tools/release/build.xml, but so far I haven't been able to make it work.
So that one's not ready for commit.
The trunk and 10.5 build.xml files haven't diverged much (yet), so I've tried this build.xml on a 10.5 environment and it seems to work well.
I'm interested in feedback on this one.
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Attachments: DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750060#action_12750060 ]
Myrna van Lunteren commented on DERBY-2573:
-------------------------------------------
I updated the snapshotorrelease wiki. Thanks for the test drive and comments, Rick.
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Attachments: DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919770#action_12919770 ]
Knut Anders Hatlen commented on DERBY-2573:
-------------------------------------------
The renaming of docs.out to docs.root stopped the cron job that builds the binaries for the nightly tests. It should be up and running again tomorrow, I hope.
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-2573-01-aa-masterTarget.diff, derby-2573-02-aa-generateReleaseProperties.diff, derby-2573-03-aa-propertyPrompt.diff, derby-2573-04-aa-emptyClient.diff, DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (DERBY-2573) Create master ant target
for generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922211#action_12922211 ]
Rick Hillegas edited comment on DERBY-2573 at 10/18/10 2:53 PM:
----------------------------------------------------------------
Attaching derby-2573-09-aa-copySQLStateTableEarlier.diff. This moves the checkin of the SQLState documentation to an earlier point in the release-build. All of the checkins needed for the release should be finished before we sync the clients to bring them up-to-date. Committed at subversion revision 1023943.
Touches the following files:
M build.xml
was (Author: rhillegas):
Attaching derby-2573-09-aa-copySQLStateTableEarlier.diff. This moves the checkin of the SQLState documentation to an earlier point in the release-build. All of the checkins needed for the release should be finished before we sync the clients to bring them up-to-date. Committed at subversion
Touches the following files:
M build.xml
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-2573-01-aa-masterTarget.diff, derby-2573-02-aa-generateReleaseProperties.diff, derby-2573-03-aa-propertyPrompt.diff, derby-2573-04-aa-emptyClient.diff, derby-2573-05-aa-updateReleaseProperties.diff, derby-2573-06-ab-docsClasspath.diff, derby-2573-07-aa-createBranch.diff, derby-2573-08-aa-useReleaseVariablesInDocsBuild.diff, derby-2573-09-aa-copySQLStateTableEarlier.diff, DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2573:
---------------------------------
Attachment: derby-2573-02-aa-generateReleaseProperties.diff
Attaching derby-2573-02-aa-generateReleaseProperties.diff. This patch introduces a new build target which generates release.properties based on a release identifier property. Checked in at subversion revision 1005590.
A later patch will wire this machinery into the master release target after the derby-2573-01-aa-masterTarget.diff patch is committed.
To run this target, do the following:
ant -Dderby.release.id="$releaseID" writeReleaseProperties
where $releaseID is a string of the form "N.N.N.N" or "N.N.N.N beta".
E.g.:
ant -Dderby.release.id="10.7.1.0" writeReleaseProperties
Touches the following files:
-----------
A java/build/org/apache/derbyPreBuild/ReleaseProperties.java
New ant task.
-----------
M java/engine/org/apache/derby/iapi/services/info/ProductVersionHolder.java
Moved to ReleaseProperties the constant used to encode the fixpack and point numbers in the release id.
-----------
M build.xml
Added a writeReleaseProperties target to drive the new ant task.
-----------
M tools/ant/properties/release.properties
Removed a timestamp line which has not been kept up to date.
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-2573-01-aa-masterTarget.diff, derby-2573-02-aa-generateReleaseProperties.diff, DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919276#action_12919276 ]
Rick Hillegas commented on DERBY-2573:
--------------------------------------
Committed derby-2573-01-aa-masterTarget.diff at subversion revision 1005815. I will continue to improve this for a while.
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-2573-01-aa-masterTarget.diff, derby-2573-02-aa-generateReleaseProperties.diff, DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2573:
---------------------------------
Issue & fix info: (was: [Patch Available])
Reset the "Patch Available" flag because all of the patches have been committed so far. The changes can be test-driven from the trunk now.
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-2573-01-aa-masterTarget.diff, derby-2573-02-aa-generateReleaseProperties.diff, derby-2573-03-aa-propertyPrompt.diff, DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2573:
---------------------------------
Attachment: derby-2573-05-aa-updateReleaseProperties.diff
Attaching derby-2573-05-aa-updateReleaseProperties.diff. This patch automates some of the drudgery involving release ids. Committed at subversion revision 1021394.
My apologies to Knut, who has been fixing the nightly builds as my changes break them. Hopefully this change only affects code paths untrod by the nightly builds.
Now the release builder does the following:
1) Prompts you for the release id at the beginning.
2) Generates release.properties accordingly and checks it in. This step happens before building the distributions.
3) At the very end, bumps the last digit of the release id on the branch, regenerating release.properties and checking that file in again. This step happens after building the distributions.
In addition, the standalone writeReleaseProperties target is now more capable. You can use it by itself to adjust the release id on the branch just after creating the branch. You can also use it to adjust the release id on the development trunk after creating a branch.
Touches the following files:
-----------
M java/build/org/apache/derbyPreBuild/ReleaseProperties.java
Gives this ant Task a new argument, which determines whether the last digit of the release id should be incremented before writing release.properties.
-----------
M build.xml
Some refactoring so that we can call the more capable writeReleaseProperties target.
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-2573-01-aa-masterTarget.diff, derby-2573-02-aa-generateReleaseProperties.diff, derby-2573-03-aa-propertyPrompt.diff, derby-2573-04-aa-emptyClient.diff, derby-2573-05-aa-updateReleaseProperties.diff, DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2573:
---------------------------------
Attachment: derby-2573-04-aa-emptyClient.diff
Attaching derby-2573-04-aa-emptyClient.diff. This patch adds a check to the master release build: the docs and code clients must have no in-flight edits. Committed at subversion revision 1005976.
Once this patch is checked in, it becomes hard to improve the master release target because any edits to build.xml will cause the release build to fail. To get around this problem, I added a new property:
debug.release.build
When this property is set to true, the release build goes ahead even though there are in-flight edits.
Touches the following files:
M build.xml
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-2573-01-aa-masterTarget.diff, derby-2573-02-aa-generateReleaseProperties.diff, derby-2573-03-aa-propertyPrompt.diff, derby-2573-04-aa-emptyClient.diff, DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2573:
---------------------------------
Issue & fix info: [Patch Available]
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-2573-01-aa-masterTarget.diff, DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (DERBY-2573) Create master ant target
for generating all release artifacts, including code and doc artifacts
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515834 ]
Myrna van Lunteren edited comment on DERBY-2573 at 7/26/07 12:24 PM:
---------------------------------------------------------------------
This target should include the following steps:
- check setting of ant property docs.out (from tools/ant/properties/packaging.properties that should have been created based on tools/ant/properties/packaging.tmpl)
- check presence of $docs.out/../lib/DITA-OT1.1.2.1_bin-ASL.zip
- check presence of java/tools/osgi.jar
- check presence of ant property junit
- check presence of junit.jar as set by ant property junit
- check ant property setting of j14lib
- check ant property setting of jdk16
- check ant property setting of jsr169compile.classpath
- check that version number in files referenced in tools/release/build.xml for updating the masters, matches the expected version based on tools/ant/properties/release.properties
- check that $docs.out/../src/conrefs.dita has settings matching tools/ant/properties/release.properties for:
- ph id="productinstallname"
- ph id="fullversionnumber"
- ph id="shortversionnumber"
- check that $docs.out/../src/*/*copyright.dita have the current year
- ensure ant property sane is *not* set (likely from "$HOME"/ant.properties)
- ant all
- copy classes/doc/rrefexcept71493.dita to docs.out/../src/ref
- ant all for the doc tree
- ant clobber for source tree
- svn update
- ant clobber
- rm -rf jars javadoc snapshot # really clean
- rm tools/release/*.zip tools/release/*.tar.gz # really,
- rm tools/release/*.md5 tools/release/*.asc # really clean
- ant sane ; ant all ; ant buildjars # for lib-debug
- ant clobber
- ant insane
- ant -Dsane=false snapshot
- ant publishedapi
- ant release target in tools/release/build.xml
- copy snapshot/derby_core_plugin_<major.minor.maint.revision>.zip to tools/release
Any of these staps failing should stop the process.
As there may be trouble with ant sign I think that step may need to be manual.
was:
This target should include the following steps:
- check setting of ant property docs.out (from tools/ant/properties/packaging.properties that should have been created based on tools/ant/properties/packaging.tmpl)
- check presence of $docs.out/../lib/DITA-OT1.1.2.1_bin-ASL.zip
- check presence of java/tools/osgi.jar
- check presence of ant property junit
- check presence of junit.jar as set by ant property junit
- check ant property setting of j14lib
- check ant property setting of jdk16
- check ant property setting of jsr169compile.classpath
- ensure ant property sane is *not* set (likely from "$HOME"/ant.properties)
- ant all
- copy classes/doc/rrefexcept71493.dita to docs.out/../src/ref
- ant all for the doc tree
- ant clobber for source tree
- svn update
- ant clobber
- rm -rf jars javadoc snapshot # really clean
- rm tools/release/*.zip tools/release/*.tar.gz # really,
- rm tools/release/*.md5 tools/release/*.asc # really clean
- ant sane ; ant all ; ant buildjars # for lib-debug
- ant clobber
- ant insane
- ant -Dsane=false snapshot
- ant publishedapi
- ant release target in tools/release/build.xml
- copy snapshot/derby_core_plugin_<major.minor.maint.revision>.zip to tools/release
Any of these staps failing should stop the process.
As there may be trouble with ant sign I think that step may need to be manual.
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.0.0
> Reporter: Rick Hillegas
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2573:
---------------------------------
Attachment: derby-2573-06-ab-docsClasspath.diff
Attaching derby-2573-06-ab-docsClasspath.diff. This changes the way that the docs build is invoked. With this patch, the docs build is run inside another process. This lets us adjust the classpath for ant, based on ${docs.root}. And this lets us boost the memory which we need to give the docs-building process. These changes, in turn, eliminate the need for a platform-specific buildrelease script. Committed at subversion revision 1021472.
Touches the following files:
-----------
M build.xml
Prompt for docs.root if it isn't set. Then run the docs build with appropriate CLASSPATH and memory settings.
-----------
D buildrelease
This script is no longer needed.
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-2573-01-aa-masterTarget.diff, derby-2573-02-aa-generateReleaseProperties.diff, derby-2573-03-aa-propertyPrompt.diff, derby-2573-04-aa-emptyClient.diff, derby-2573-05-aa-updateReleaseProperties.diff, derby-2573-06-ab-docsClasspath.diff, DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2573:
---------------------------------
Attachment: derby-2573-07-aa-createBranch.diff
Attaching derby-2573-07-aa-createBranch.diff. This adds some targets to support branch creation as the first step toward generating a feature release. Committed at subversion revision 1021793.
This patch introduces a new top-level target: createBranch. You must specify your docs root in order to invoke this target. So you would do something like the following:
export DOCS_ROOT=$HOME/derby/docs/$BRANCH
cd $HOME/derby/$SANDBOX/$BRANCH
ant "-Ddocs.root=$DOCS_ROOT" -quiet createBranch
I have test-driven the parts of this target which determine the branch and starting subversion revision. I have not tested the actual branch creation. Will do that when it's time to create the 10.7 branch.
Touches the following file:
M build.xml
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-2573-01-aa-masterTarget.diff, derby-2573-02-aa-generateReleaseProperties.diff, derby-2573-03-aa-propertyPrompt.diff, derby-2573-04-aa-emptyClient.diff, derby-2573-05-aa-updateReleaseProperties.diff, derby-2573-06-ab-docsClasspath.diff, derby-2573-07-aa-createBranch.diff, DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-2573:
--------------------------------------
Issue & fix info: (was: [Patch Available])
I committed the prepareforrelease target to trunk with revision 810178 and backported to 10.5 with revision 810180. (I left out the 'release' target, as it wasn't working).
I'll update http://wiki.apache.org/db-derby/DerbySnapshotOrRelease with the option of running this target.
I don't plan to do more work on this at this time.
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Attachments: DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2573:
---------------------------------
Attachment: derby-2573-09-aa-copySQLStateTableEarlier.diff
Attaching derby-2573-09-aa-copySQLStateTableEarlier.diff. This moves the checkin of the SQLState documentation to an earlier point in the release-build. All of the checkins needed for the release should be finished before we sync the clients to bring them up-to-date. Committed at subversion
Touches the following files:
M build.xml
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-2573-01-aa-masterTarget.diff, derby-2573-02-aa-generateReleaseProperties.diff, derby-2573-03-aa-propertyPrompt.diff, derby-2573-04-aa-emptyClient.diff, derby-2573-05-aa-updateReleaseProperties.diff, derby-2573-06-ab-docsClasspath.diff, derby-2573-07-aa-createBranch.diff, derby-2573-08-aa-useReleaseVariablesInDocsBuild.diff, derby-2573-09-aa-copySQLStateTableEarlier.diff, DERBY-2573.diff_1notforcommit
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (DERBY-2573) Create master ant target for generating all release artifacts, including code and doc artifacts
Posted by Myrna van Lunteren <m....@gmail.com>.
On 7/27/07, Dag H. Wanvik <Da...@sun.com> wrote:
> Would it be useful to check for absense of "debug=true" and "proceed=true" also?
>
> Dag
good point, probably yes. Actually, I'm not sure I ever tried with
proceed=false, I always very carefully check the build results... but
if the build is clean, it should proceed on its own, yes? So maybe,
proceed should be false...
Some of these are less necessary than others, for instance, if
jdk14lib isn't set, I don't think much will build. But if jdk16 isn't
set, or junit, or jsr169compilepath or osgi.jar isn't there and
proceed=true, the distribution will build successfully but miss some
required parts...If sane is set, the steps in creating the
distributions of ant sane and ant insane/ant -Dsane=false snapshot
might be overwritten by the sane setting (I wasted some time on that
little detail :-) ).
Also, we should be able to have incremental development on this, start
with the basic ant targets as a first step, add more of the checking
details later...
Myrna
Re: [jira] Commented: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
[Can't attach comment, so just a mail thread reply.]
"Myrna van Lunteren (JIRA)" <ji...@apache.org> writes:
> [ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515834 ]
>
> Myrna van Lunteren commented on DERBY-2573:
> -------------------------------------------
>
> This target should include the following steps:
>
> - check setting of ant property docs.out (from tools/ant/properties/packaging.properties that should have been created based on tools/ant/properties/packaging.tmpl)
> - check presence of $docs.out/../lib/DITA-OT1.1.2.1_bin-ASL.zip
> - check presence of java/tools/osgi.jar
> - check presence of ant property junit
> - check presence of junit.jar as set by ant property junit
> - check ant property setting of j14lib
> - check ant property setting of jdk16
> - check ant property setting of jsr169compile.classpath
> - ensure ant property sane is *not* set (likely from "$HOME"/ant.properties)
Would it be useful to check for absense of "debug=true" and "proceed=true" also?
Dag
> - ant all
> - copy classes/doc/rrefexcept71493.dita to docs.out/../src/ref
> - ant all for the doc tree
> - ant clobber for source tree
> - svn update
> - ant clobber
> - rm -rf jars javadoc snapshot # really clean
> - rm tools/release/*.zip tools/release/*.tar.gz # really,
> - rm tools/release/*.md5 tools/release/*.asc # really clean
> - ant sane ; ant all ; ant buildjars # for lib-debug
> - ant clobber
> - ant insane
> - ant -Dsane=false snapshot
> - ant publishedapi
> - ant release target in tools/release/build.xml
> - copy snapshot/derby_core_plugin_<major.minor.maint.revision>.zip to tools/release
>
> Any of these staps failing should stop the process.
>
> As there may be trouble with ant sign I think that step may need to be manual.
>
>
>
>> Create master ant target for generating all release artifacts, including code and doc artifacts
>> -----------------------------------------------------------------------------------------------
>>
>> Key: DERBY-2573
>> URL: https://issues.apache.org/jira/browse/DERBY-2573
>> Project: Derby
>> Issue Type: Improvement
>> Components: Build tools
>> Affects Versions: 10.3.0.0
>> Reporter: Rick Hillegas
>>
>> This is one of the tasks tracked by master JIRA DERBY-2571.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
[jira] Commented: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515834 ]
Myrna van Lunteren commented on DERBY-2573:
-------------------------------------------
This target should include the following steps:
- check setting of ant property docs.out (from tools/ant/properties/packaging.properties that should have been created based on tools/ant/properties/packaging.tmpl)
- check presence of $docs.out/../lib/DITA-OT1.1.2.1_bin-ASL.zip
- check presence of java/tools/osgi.jar
- check presence of ant property junit
- check presence of junit.jar as set by ant property junit
- check ant property setting of j14lib
- check ant property setting of jdk16
- check ant property setting of jsr169compile.classpath
- ensure ant property sane is *not* set (likely from "$HOME"/ant.properties)
- ant all
- copy classes/doc/rrefexcept71493.dita to docs.out/../src/ref
- ant all for the doc tree
- ant clobber for source tree
- svn update
- ant clobber
- rm -rf jars javadoc snapshot # really clean
- rm tools/release/*.zip tools/release/*.tar.gz # really,
- rm tools/release/*.md5 tools/release/*.asc # really clean
- ant sane ; ant all ; ant buildjars # for lib-debug
- ant clobber
- ant insane
- ant -Dsane=false snapshot
- ant publishedapi
- ant release target in tools/release/build.xml
- copy snapshot/derby_core_plugin_<major.minor.maint.revision>.zip to tools/release
Any of these staps failing should stop the process.
As there may be trouble with ant sign I think that step may need to be manual.
> Create master ant target for generating all release artifacts, including code and doc artifacts
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2573
> URL: https://issues.apache.org/jira/browse/DERBY-2573
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.3.0.0
> Reporter: Rick Hillegas
>
> This is one of the tasks tracked by master JIRA DERBY-2571.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.