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 "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2007/07/26 21:12:03 UTC
[jira] Commented: (DERBY-2573) Create master ant target for
generating all release artifacts, including code and doc artifacts
[ 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.
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.
>
>