db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2832) things noticed broken in release process.
Date Sat, 16 Jun 2007 18:19:26 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505515

Myrna van Lunteren commented on DERBY-2832:

doc target all fails for me (both 10.3 branch and trunk):
     [xslt] Transforming into C:\derbyt\docs\trunk\temp
     [xslt] Processing C:\derbyt\docs\trunk\temp\dita.list to C:\derbyt\docs\trunk\temp\dita.dita.pull
     [xslt] Loading stylesheet C:\derbyt\docs\trunk\DITA-OT1.1.2.1\xsl\preprocess\topicpull.xsl
     [xslt] C:\derbyt\docs\trunk\temp\dita.list:1:1: Fatal Error! Content is not allowed in
     [xslt] Failed to process null

C:\derbyt\docs\trunk\build.xml:73: The following error occurred while executing this line:
C:\derbyt\docs\trunk\build.xml:143: The following error occurred while executing this line:
C:\derbyt\docs\trunk\DITA-OT1.1.2.1\pretargets.xml:136: Fatal error during transformation

I guess I never tried all before, just books at a time...

> things noticed broken in release process.
> -----------------------------------------
>                 Key: DERBY-2832
>                 URL: https://issues.apache.org/jira/browse/DERBY-2832
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools
>    Affects Versions:
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>            Priority: Trivial
> This is a place holder for any issues I might run into.
> First:
> - add to wiki that it's important to ant clobber before attempting to build with an updated
> - org.apache.derbyBuild.maintversion2props has some issues re updating masters
>    - does not find it necessary to update major version numbers (i.e. I tried to use
it for main, for updating from 10.3 to 10.4, and it just never updated any masters)
>    - does not find it necessary to update a flag  (beta/alpha) (i.e. I tried to use it
for the branch, updating from alpha to beta, and it updated the masters
to alpha)
>    - is dependent on tools/release/build.xml having an up-to-date list of masters
> - jira: one jira issue was closed, but still showed up on the 10.3 open issues. However,
I could not bulk-edit it.

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

View raw message