Rick Hillegas wrote:
Please vote on whether we should make Kristian Waagan a Derby committer.
+1
unsuscribe
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses.
Bryan Pendleton <[EMAIL PROTECTED]> writes:
> My most recent run of derbyall ran 662 tests.
>
> I can't remember for sure, but I thought that my runs
> late last week were running 669 or 670 tests.
>
> Did a number of tests recently get removed from derbyall?
Most of the JUnit tests have been rem
+1
Narayanan
Rick Hillegas wrote:
Please vote on whether we should make Kristian Waagan a Derby committer.
Kristian contributed significantly to the Derby JDBC4 effort. In my
opinion
1) His patches show consistently superior quality: they are well
thought out, well documented, and well tes
Rick Hillegas <[EMAIL PROTECTED]> writes:
> Please vote on whether we should make Kristian Waagan a Derby committer.
+1
--
Knut Anders
+1
Mamta
On 10/25/06, Olav Sandstaa <[EMAIL PROTECTED]> wrote:
Rick Hillegas wrote:> Please vote on whether we should make Kristian Waagan a Derby committer.
+1Olav
On 10/25/06, Bryan Pendleton <[EMAIL PROTECTED]> wrote:
My most recent run of derbyall ran 662 tests.I can't remember for sure, but I thought that my runslate last week were running 669 or 670 tests.I noticed this also. Last time I ran derbyall was 10/17 and it had 671 tests.
And now with the cur
My most recent run of derbyall ran 662 tests.
I can't remember for sure, but I thought that my runs
late last week were running 669 or 670 tests.
Did a number of tests recently get removed from derbyall?
thanks,
bryan
P.S. I'm a bit behind on making the transition to JUnit,
so it's possible t
Rick Hillegas wrote:
Please vote on whether we should make Kristian Waagan a Derby committer.
+1
Olav
Jean T. Anderson wrote:
...
> The current topic on
> #asfinfra is "ETA for mino: morning PDT 10/25", so hopes are high.
> ("mino" == minotaur, which is the machine that died yesterday.)
updated #asfinfra topic =
"minotaur has complete /home and /www rsyncs, ports are rebuilding, ETA:
tonight"
Tha
I created JIRA issue 2001 for the templates.
And I posted an updated task template and a new concept template to that issue.
The reference template will be posted in the next few days.
https://issues.apache.org/jira/browse/DERBY-2001
Please take a look at the templates. I value your feedback :-)
Hi Kim -
I've embedded responses below.
On 10/20/06, Kim Haase <[EMAIL PROTECTED]> wrote:
Hi, Laura,
I'd suggest sticking to an 80-character line length for easy readability
in text editors, if possible.
Thanks, my editor does not have an issue with the character length and
auto word wraps.
On 10/25/06, Kristian Waagan <[EMAIL PROTECTED]> wrote:
Laura Stewart wrote:
> I would like to put a link to a derby-dev thread into a JIRA issue.
> How can I do that?
It is also possible to link to individual messages.
You could also insert links to the Apache archives, but I don't know the
spe
On 10/25/06, Kristian Waagan <[EMAIL PROTECTED]> wrote:
Hi Laura,
One way to achieve this would be insert a link to Nabble:
http://www.nabble.com/Derby-f356.html
For instance, to link to this thread, you could use:
http://www.nabble.com/How-do-you-point-from-a-JIRA-issue-to-a-derby-dev-thread-
On 10/25/06, Rick Hillegas <[EMAIL PROTECTED]> wrote:
Please vote on whether we should make Kristian Waagan a Derby committer.
+1
andrew
Laura Stewart wrote:
I would like to put a link to a derby-dev thread into a JIRA issue.
How can I do that?
Hi Laura,
One way to achieve this would be insert a link to Nabble:
http://www.nabble.com/Derby-f356.html
For instance, to link to this thread, you could use:
http://www.nabble.com/Ho
I would like to put a link to a derby-dev thread into a JIRA issue.
How can I do that?
--
Laura Stewart
+1
Sunitha.
On 10/25/06, Rick Hillegas <[EMAIL PROTECTED]> wrote:
Please vote on whether we should make Kristian Waagan a Derby committer.
+1
Deepa
After updating to revision 467723M I can no longer build derby with
ant -Dsane=true -Ddebug=true all
[...]
checktoursdb:
toursdb:
compile:
buildschema:
[echo] Begin building toursdb
At this point it seems to hang.
Simply running
ant all
works just fine.
Anyone else having this proble
Rick Hillegas wrote:
Please vote on whether we should make Kristian Waagan a Derby committer.
+1
Army
Hello,
I was running various JUnit tests/suites and the test
'jdbcapi.BlobClob4Blob' was failing with a security exception, but when
run as part of 'suites.All' it was not.
After some investigation, I discovered the following:
1) derby.system.home was set to a non-existing directory.
Set to
On 10/25/06, Rick Hillegas <[EMAIL PROTECTED]> wrote:
I'm having trouble accessing the derby repository. Subversion is givingme diagnostics like the following. Is anyone else seeing this problem?Thanks-Ricksvn: PROPFIND request failed on '/repos/asf/db/derby/code/trunk'
svn: PROPFIND of '/repos/asf
+1
Daniel John Debrunner wrote:
I propose a vote for Fernanda Pizzorno as a Derby committer.
Fernanda worked on the implementation of scrollable updateable result
sets and has also submitted patches to fix a number of issues. Fernanda
is also currently jumping into converting tests to JUnit.
On 10/25/06, Rick Hillegas <[EMAIL PROTECTED]> wrote:
Please vote on whether we should make Kristian Waagan a Derby committer. +1Yip
Rick Hillegas wrote (2006-10-25 07:45:39):
> Please vote on whether we should make Kristian Waagan a Derby
> committer.
+1
--
Bernt Marius Johnsen, Database Technology Group,
Staff Engineer, Technical Lead Derby/Java DB
Sun Microsystems, Trondheim, Norway
signature.asc
Descriptio
Do you have time to work this issue through infra?
Yes, I'll see what I can do. Thanks for the good pointers!
bryan
Rick Hillegas wrote:
Please vote on whether we should make Kristian Waagan a Derby committer.
+1
-suresh
Bryan Pendleton wrote:
>> So ... some things are disrupted and I'm assuming the Jira email is part
>> of the people.a.o outage.
>
>
> Thanks Jean!
>
> I do notice a couple things that concern me:
>
> 1) I'm subscribed to a couple other apache.org developers lists for
> other projects, and at le
On 10/23/06, Andrew McIntyre <[EMAIL PROTECTED]> wrote:
On 10/23/06, Laura Stewart <[EMAIL PROTECTED]> wrote:
> >
> > Make a new directory and svn add it. It will then show up in your svn
> > diff. Whoever commits will have to do the svn add as well, might be
> > good to include a 'stat' listing
So ... some things are disrupted and I'm assuming the Jira email is part
of the people.a.o outage.
Thanks Jean!
I do notice a couple things that concern me:
1) I'm subscribed to a couple other apache.org developers lists for
other projects, and at least one of those projects uses Jira and
that
On 10/25/06, Bryan Pendleton <[EMAIL PROTECTED]> wrote:
I find writing in DITA format to be awkward and slow, so when I
have a lot of information I want to enter, I tend to prefer one of:
- adding information to the Wiki
- writing comments directly in the code
- writing HTML or Text documents
Rick Hillegas <[EMAIL PROTECTED]> writes:
> Please vote on whether we should make Kristian Waagan a Derby committer.
+1
Dag
+1
Rick Hillegas wrote:
Please vote on whether we should make Kristian Waagan a Derby committer.
Kristian contributed significantly to the Derby JDBC4 effort. In my
opinion
1) His patches show consistently superior quality: they are well
thought out, well documented, and well tested.
2)
On 10/25/06, Bryan Pendleton <[EMAIL PROTECTED]> wrote:
One more thing I meant to add: I find it hard to review
other people's doc changes when they are posted as DITA
diffs only, because I'm not that practiced reading DITA
diffs. So I think the preferred way to post doc patches
for review is som
One more thing I meant to add: I find it hard to review
other people's doc changes when they are posted as DITA
diffs only, because I'm not that practiced reading DITA
diffs. So I think the preferred way to post doc patches
for review is something like:
- make the change and run the build, to gen
I'd appreciate comments from any one else about updating docs...
I've been successful making a handful of documentation patches.
The changes I've made have been very small, confined to 2-3 pages
in the reference guide, and I've generally just been adding a
paragraph here and there. I simply mim
+1Regards Andreas
[Auto-generated mail]
*Daily* 467368/2006-10-24 18:00:07 MEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.6*
0679679 0 101.51% lin
0679679 0 106.44% sol
067967
I'd appreciate comments from any one else about updating docs...
On 10/10/06, Laura Stewart <[EMAIL PROTECTED]> wrote:
The Derby Documentation page that describes how to setup your
environment, update the files, and submit patches.
http://db.apache.org/derby/manuals/dita.html
Yet there are very
+1
Rick Hillegas wrote:
I am resending this message in order to bound the polling. Please cast
your vote by 5:00 pm San Francisco time on Monday October 30, 2006.
Thanks,
-Rick
Rick Hillegas wrote:
Please vote on whether we should make Kristian Waagan a Derby committer.
[...]
--
John
Rick Hillegas <[EMAIL PROTECTED]> writes:
> Please vote on whether we should make Kristian Waagan a Derby committer.
+1
--
dt
Please vote on whether we should make Kristian Waagan a Derby committer.
Kristian has been doing very good work.
+1
thanks,
bryan
Issue Subscription
Filter: Derby: JIRA issues with patch available (16 issues)
Subscriber: derby-dev
Key Summary
DERBY-1758 Enable xmlSuite to run as part of derbyall for JVMs that embed the
required external jars.
http://issues.apache.org/jira/browse/DERBY-1758
DERBY-1970
+1
Rick Hillegas wrote:
+1
Rick Hillegas wrote:
Please vote on whether we should make Kristian Waagan a Derby committer.
Kristian contributed significantly to the Derby JDBC4 effort. In my
opinion
1) His patches show consistently superior quality: they are well
thought out, well documente
I am resending this message in order to bound the polling. Please cast
your vote by 5:00 pm San Francisco time on Monday October 30, 2006.
Thanks,
-Rick
Rick Hillegas wrote:
Please vote on whether we should make Kristian Waagan a Derby committer.
Kristian contributed significantly to the Derb
+1
Rick Hillegas wrote:
Please vote on whether we should make Kristian Waagan a Derby committer.
Kristian contributed significantly to the Derby JDBC4 effort. In my
opinion
1) His patches show consistently superior quality: they are well
thought out, well documented, and well tested.
2) H
Bryan Pendleton wrote:
Jira email seems to be down, as Jean noted, so I'm just mailing the list
to indicate that I've started to look at your patch. I see in the Jira
entry that you've already updated it to patch version 2 so that's the one
I'm looking at.
Great, thanks Bryan!
Army
Please vote on whether we should make Kristian Waagan a Derby committer.
Kristian contributed significantly to the Derby JDBC4 effort. In my opinion
1) His patches show consistently superior quality: they are well thought
out, well documented, and well tested.
2) He cheerfully takes advice.
I'm having trouble accessing the derby repository. Subversion is giving
me diagnostics like the following. Is anyone else seeing this problem?
Thanks-Rick
svn: PROPFIND request failed on '/repos/asf/db/derby/code/trunk'
svn: PROPFIND of '/repos/asf/db/derby/code/trunk': Could not create SSL
co
Myrna van Lunteren wrote:
On 10/24/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Author: davidvc
[...]
Modified:
[...]
+(1) JUnit is needed for some of Derby's tests. Download a JUnit 3.8.1
+from
+
+ http://prdownloads.sourceforge.net/junit/junit3.8.1.zip?download
+
+Note th
On 10/24/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Author: davidvc
Date: Tue Oct 24 17:19:57 2006
New Revision: 467522
URL: http://svn.apache.org/viewvc?view=rev&rev=467522
Log:
Fixed to point to the correct download site for JUnit 3.8.1
Modified:
db/derby/code/trunk/BUILDING.txt
Mod
52 matches
Mail list logo