[
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.
