Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 65372 invoked from network); 17 Jun 2007 20:45:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Jun 2007 20:45:47 -0000 Received: (qmail 10068 invoked by uid 500); 17 Jun 2007 20:45:50 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 10034 invoked by uid 500); 17 Jun 2007 20:45:50 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 10025 invoked by uid 99); 17 Jun 2007 20:45:50 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Jun 2007 13:45:50 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Jun 2007 13:45:46 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id EEF0871413F for ; Sun, 17 Jun 2007 13:45:25 -0700 (PDT) Message-ID: <4272678.1182113125976.JavaMail.jira@brutus> Date: Sun, 17 Jun 2007 13:45:25 -0700 (PDT) From: "Myrna van Lunteren (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2832) things noticed broken in release process. In-Reply-To: <5392571.1181944285862.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on 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.