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/06/15 23:51:25 UTC
[jira] Created: (DERBY-2832) things noticed broken in release
process.
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: 10.3.1.0
Reporter: 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 release.properties
- 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 10.3.0.0 alpha to 10.3.1.0 beta, and it updated the masters to 10.3.1.0 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.
[jira] Commented: (DERBY-2832) things noticed broken in release
process.
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505524 ]
Myrna van Lunteren commented on DERBY-2832:
-------------------------------------------
At the end of the trunk pdf adminguide build, I see this:
[fop] Jun 16, 2007 11:24:08 AM org.apache.fop.area.RenderPagesModel checkPreparedPages
[fop] WARNING: Page 22: Unresolved id reference "radminappsclientsecuritytable" found.
at the end of the trunk pdf devguide build I see this:
[fop] Jun 16, 2007 11:24:59 AM org.apache.fop.area.RenderPagesModel checkPreparedPages
[fop] WARNING: Page 57: Unresolved id reference "cdevconcepts17741" found.
[fop] Jun 16, 2007 11:24:59 AM org.apache.fop.area.RenderPagesModel checkPreparedPages
[fop] WARNING: Page 57: Unresolved id reference "cdevconcepts28076" found.
[fop] Jun 16, 2007 11:24:59 AM org.apache.fop.area.RenderPagesModel checkPreparedPages
[fop] WARNING: Page 58: Unresolved id reference "cdevconcepts17741" found.
[fop] Jun 16, 2007 11:24:59 AM org.apache.fop.area.RenderPagesModel checkPreparedPages
[fop] WARNING: Page 67: Unresolved id reference "cdevconcepts40343" found.
ref and tools and tuning have a ton of them...
(also the brazilian ref manual).
I'm not going to do anything about these now.
> 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: 10.3.1.0
> 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 release.properties
> - 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 10.3.0.0 alpha to 10.3.1.0 beta, and it updated the masters to 10.3.1.0 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.
[jira] Commented: (DERBY-2832) things noticed broken in release
process.
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505627 ]
Myrna van Lunteren commented on DERBY-2832:
-------------------------------------------
ok, tried again, in a clean eclipse environment, and that worked better.
> 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: 10.3.1.0
> 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 release.properties
> - 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 10.3.0.0 alpha to 10.3.1.0 beta, and it updated the masters to 10.3.1.0 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.
[jira] Commented: (DERBY-2832) things noticed broken in release
process.
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505572 ]
Myrna van Lunteren commented on DERBY-2832:
-------------------------------------------
Finally had to do some manual work on the release notes.
Not so good.
Also, I had thought to do fix up the OSGI bundle details before now - see DERBY-1945, but I don't remember where packages are exported for the bundling, nor do I know if it's ok to export the two packages referenced.
> 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: 10.3.1.0
> 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 release.properties
> - 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 10.3.0.0 alpha to 10.3.1.0 beta, and it updated the masters to 10.3.1.0 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.
[jira] Closed: (DERBY-2832) things noticed broken in release
process.
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren closed DERBY-2832.
-------------------------------------
Resolution: Invalid
> things noticed broken in release process.
> -----------------------------------------
>
> Key: DERBY-2832
> URL: https://issues.apache.org/jira/browse/DERBY-2832
> Project: Derby
> Issue Type: Task
> Components: Build tools
> Affects Versions: 10.3.1.0
> 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 release.properties
> - 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 10.3.0.0 alpha to 10.3.1.0 beta, and it updated the masters to 10.3.1.0 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.
[jira] Commented: (DERBY-2832) things noticed broken in release
process.
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ 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):
...
topicpull:
[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 prolog.
[xslt] Failed to process null
BUILD FAILED
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: 10.3.1.0
> 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 release.properties
> - 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 10.3.0.0 alpha to 10.3.1.0 beta, and it updated the masters to 10.3.1.0 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.
[jira] Commented: (DERBY-2832) things noticed broken in release
process.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506350 ]
Daniel John Debrunner commented on DERBY-2832:
----------------------------------------------
The ant sane , ant all then ant insane etc. really seems like it should be a single target in ant rather than a number of manual steps.
> things noticed broken in release process.
> -----------------------------------------
>
> Key: DERBY-2832
> URL: https://issues.apache.org/jira/browse/DERBY-2832
> Project: Derby
> Issue Type: Task
> Components: Build tools
> Affects Versions: 10.3.1.0
> 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 release.properties
> - 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 10.3.0.0 alpha to 10.3.1.0 beta, and it updated the masters to 10.3.1.0 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.
[jira] Updated: (DERBY-2832) things noticed broken in release
process.
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-2832:
--------------------------------------
Issue Type: Task (was: Bug)
> things noticed broken in release process.
> -----------------------------------------
>
> Key: DERBY-2832
> URL: https://issues.apache.org/jira/browse/DERBY-2832
> Project: Derby
> Issue Type: Task
> Components: Build tools
> Affects Versions: 10.3.1.0
> 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 release.properties
> - 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 10.3.0.0 alpha to 10.3.1.0 beta, and it updated the masters to 10.3.1.0 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.
[jira] Commented: (DERBY-2832) things noticed broken in release
process.
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506266 ]
Myrna van Lunteren commented on DERBY-2832:
-------------------------------------------
I forgot about this one: the instructions say to do set ant.properties sane=false, then do ant sane, followed by ant all and ant buildjars. However, ant all when you've got sane=false will overwrite the state.properties setting. I first set sane=true in my ant.properties; did ant sane, ant all, ant buildjars, then set sane=false in ant.properties and did the snapshot step.
I hope that is correct.
> 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: 10.3.1.0
> 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 release.properties
> - 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 10.3.0.0 alpha to 10.3.1.0 beta, and it updated the masters to 10.3.1.0 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.
[jira] Commented: (DERBY-2832) things noticed broken in release
process.
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505521 ]
Myrna van Lunteren commented on DERBY-2832:
-------------------------------------------
troubles with release note generator. Which was only to be expected as we hadn't finished working on it.
Rick patched things up.
See DERBY-2570, and mail with thread heading: http://thread.gmane.org/gmane.comp.apache.db.derby.devel/44760/focus=44792
> 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: 10.3.1.0
> 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 release.properties
> - 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 10.3.0.0 alpha to 10.3.1.0 beta, and it updated the masters to 10.3.1.0 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.
[jira] Assigned: (DERBY-2832) things noticed broken in release
process.
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren reassigned DERBY-2832:
-----------------------------------------
Assignee: Myrna van Lunteren
> 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: 10.3.1.0
> 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 release.properties
> - 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 10.3.0.0 alpha to 10.3.1.0 beta, and it updated the masters to 10.3.1.0 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.
[jira] Commented: (DERBY-2832) things noticed broken in release
process.
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506318 ]
Myrna van Lunteren commented on DERBY-2832:
-------------------------------------------
On rereading the derbysnapshotorrelease page, I see it says *remove* the sane property. I set it to false. So, that bit is pilot error.
There already is a note indicating the maintversionprops2 does not handle the beta flag...
There are a number of bugs regarding the build failures with dita with the docs.
So that's all ok.
I made some small changes to the wiki.
I think this issue can be closed.
> 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: 10.3.1.0
> 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 release.properties
> - 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 10.3.0.0 alpha to 10.3.1.0 beta, and it updated the masters to 10.3.1.0 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.
[jira] Commented: (DERBY-2832) things noticed broken in release
process.
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505520 ]
Myrna van Lunteren commented on DERBY-2832:
-------------------------------------------
The working with derby target wasn't removed from the docs build.xml, although the source is no longer there. I'll check in a fix.
> 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: 10.3.1.0
> 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 release.properties
> - 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 10.3.0.0 alpha to 10.3.1.0 beta, and it updated the masters to 10.3.1.0 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.
[jira] Commented: (DERBY-2832) things noticed broken in release
process.
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505622 ]
Myrna van Lunteren commented on DERBY-2832:
-------------------------------------------
because of misremembering my gpg passphrase and other reasons, we'll go ahead & not call this a release candidate, but a beta. i.e for testing.
Now for the eclipse plugin.
Based on ../branches/10.3/plugins/eclipse/Readme.txt
step 2 says to install an old core plugin. Seems illogical, is that really needed?
Then, after import, I see some errors:
Severity and Description Path Resource Location Creation Time Id
Cannot resolve plug-in: org.apache.derby.core org.apache.derby.ui plugin.xml line 35 1182112383578 8
And Warnings:
Severity and Description Path Resource Location Creation Time Id
The field StopAction.server is never read locally org.apache.derby.ui/src/org/apache/derby/ui/actions StopAction.java line 42 1182112382922 7
The file "install_plugin.html" does not exist in the workspace org.apache.derby.ui build.properties line 18 1182112384156 9
The local variable plugin is never read org.apache.derby.ui/src/org/apache/derby/ui/util DerbyUtils.java line 260 1182112382156 4
The method asLocalURL(URL) from the type Platform is deprecated org.apache.derby.ui/src/org/apache/derby/ui/util DerbyUtils.java line 130 1182112382156 2
The method asLocalURL(URL) from the type Platform is deprecated org.apache.derby.ui/src/org/apache/derby/ui/util DerbyUtils.java line 151 1182112382156 3
The method asLocalURL(URL) from the type Platform is deprecated org.apache.derby.ui/src/org/apache/derby/ui/util DerbyUtils.java line 284 1182112382156 5
The method asLocalURL(URL) from the type Platform is deprecated org.apache.derby.ui/src/org/apache/derby/ui/util DerbyUtils.java line 295 1182112382156 6
> 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: 10.3.1.0
> 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 release.properties
> - 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 10.3.0.0 alpha to 10.3.1.0 beta, and it updated the masters to 10.3.1.0 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.