On Thu, Mar 27, 2008 at 11:23 AM, Bryan Pendleton
<[EMAIL PROTECTED]> wrote:
> I propose that Thomas Nielsen shall be a Derby committer.
>
> Over the last 6 months, I've worked with Thomas on some Derby
> features (http://wiki.apache.org/db-derby/OLAPOperations) as well
> as on some fairly sophi
Bryan Pendleton <[EMAIL PROTECTED]> writes:
> I propose that Thomas Nielsen shall be a Derby committer.
+1
Dag
[
https://issues.apache.org/jira/browse/DERBY-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582839#action_12582839
]
Manjula Kutty commented on DERBY-2660:
--
Happens with ibm16 also
Here is the version i
I tried ant emma-all.
The following error was on the screen
BUILD FAILED
C:\derbydev\trunk\build.xml:2199: EMMA instrumented tests failed!
It didn't create any other report file
On 3/27/08, Daniel John Debrunner <[EMAIL PROTECTED]> wrote:
>
> Manjula Kutty wrote:
> > I tried running the code c
Bryan Pendleton wrote:
I propose that Thomas Nielsen shall be a Derby committer.
Thomas has also been active in the development community,
reviewing the patches that others propose and suggesting improvements.
Please respond to this thread with your vote.
+1
Army
Daniel John Debrunner wrote:
John is actively involved on both the derby-dev and derby-user lists and
fully engages in open development. He has had a number of patches
committed, most recently taking the stalled JMX work and getting it into
a shape where it could be committed to allow others to
+1
Bryan Pendleton wrote:
I propose that Thomas Nielsen shall be a Derby committer.
Over the last 6 months, I've worked with Thomas on some Derby
features (http://wiki.apache.org/db-derby/OLAPOperations) as well
as on some fairly sophisticated bug fixes, including
https://issues.apache.org/jira
[Auto-generated mail]
*tinderbox_trunk16* 641916/2008-03-27 18:32:28 CET
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
0274274 087.04% derbyall
F:1,E:097229721 0
Manjula Kutty wrote:
I tried running the code coverage using the Wiki page instructions. But
for me the instrumentation failed. I thought all the relevant patches
are committed? Is there any other patch I have to apply before running?
What was the failure, what commands did you execute?
Dan.
[EMAIL PROTECTED] wrote:
Kathey Marsden <[EMAIL PROTECTED]> writes:
Jean T. Anderson wrote:
Isn't there something called lazy consensus? Would that not be good
enough for a beta...?
Lazy consensus never applies to a release (whether beta or not).
I respect the Apache process, but I must
Yes, it was an EG decision to correct the javadocs for setFetchSize()
as if there is no limit specified via setMaxRows(), getMaxRows()
returns 0 thus using:
0 <= |rows| <= |this.getMaxRows()|
can be problematic depending on implementations.
Also setFetchSize is a hint and can be ignored
Kathey Marsden wrote:
[EMAIL PROTECTED] wrote:
I have added a disclaimer next to the download link on the Wiki. I can
remove it if/when two additional PMC members give their approval.
I think you'd still have to have a formal vote with the 7 day minimum
like Jean says. Still might be worth
I'm renaming this thread because 2 years from now we'll search for this
topic and won't find it with the "Testing" topic. The topic surfaced in
November 2006. Here's the start of that thread:
http://www.nabble.com/new-release-policy-requires-changes-on-Derby-site-to7387188.html
Based on th
[EMAIL PROTECTED] wrote:
I have added a disclaimer next to the download link on the Wiki. I can
remove it if/when two additional PMC members give their approval.
I think you'd still have to have a formal vote with the 7 day minimum
like Jean says. Still might be worth it. Users can be vett
[
https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582770#action_12582770
]
Kim Haase commented on DERBY-3552:
--
Thanks, Narayanan. Let me see if I understand this cor
Kathey Marsden <[EMAIL PROTECTED]> writes:
> Jean T. Anderson wrote:
>>
>>> Isn't there something called lazy consensus? Would that not be good
>>> enough for a beta...?
>>>
>> Lazy consensus never applies to a release (whether beta or not).
I respect the Apache process, but I must say that I'
Kathey Marsden wrote:
Jean T. Anderson wrote:
Isn't there something called lazy consensus? Would that not be good
enough for a beta...?
Lazy consensus never applies to a release (whether beta or not).
I think the bar can be lower and the voting period shorter for beta
though. I think t
Kathey Marsden wrote:
Jean T. Anderson wrote:
Isn't there something called lazy consensus? Would that not be good
enough for a beta...?
Lazy consensus never applies to a release (whether beta or not).
I think the bar can be lower and the voting period shorter for beta
though. I think thr
+1
Thomas Nielsen is an excellent candidate for committer.
Craig
On Mar 27, 2008, at 11:26 AM, Bryan Pendleton wrote:
I propose that Thomas Nielsen shall be a Derby committer.
Over the last 6 months, I've worked with Thomas on some Derby
features (http://wiki.apache.org/db-derby/OLAPOperation
Bryan Pendleton <[EMAIL PROTECTED]> writes:
> I propose that Thomas Nielsen shall be a Derby committer.
>
> Over the last 6 months, I've worked with Thomas on some Derby
> features (http://wiki.apache.org/db-derby/OLAPOperations) as well
> as on some fairly sophisticated bug fixes, including
> htt
Jean T. Anderson wrote:
Isn't there something called lazy consensus? Would that not be good
enough for a beta...?
Lazy consensus never applies to a release (whether beta or not).
I think the bar can be lower and the voting period shorter for beta
though. I think three +1 PMC votes based
Henri van de Scheur wrote:
Thank you Mike pointing this out!
Due to Eastern holidays, things have got some delays. But I will make
both this report and fill out the platformresults on the wiki - probably
tomorrow.
But we thought it might be useful to the community to already post
results as s
[EMAIL PROTECTED] wrote:
Daniel John Debrunner <[EMAIL PROTECTED]> writes:
Kathey Marsden wrote:
Bryan Pendleton wrote:
During the process of developing software and preparing a release,
various packages are made available to the developer community for
testing purposes.
[EMAIL PROTECTED] wrote:
Is there an existing bug in Derby which you consider to be a showstopper for
10.4? (Meaning that you will veto the release unless this bug gets fixed).
Just a reminder that no-one can veto a release, though obviously any
release manager should carefully consider any -1
[
https://issues.apache.org/jira/browse/DERBY-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582763#action_12582763
]
Kathey Marsden commented on DERBY-2892:
---
I was looking at improving the error message
Daniel John Debrunner <[EMAIL PROTECTED]> writes:
> Kathey Marsden wrote:
>> Bryan Pendleton wrote:
>>>
>>> During the process of developing software and preparing a release,
>>> various packages are made available to the developer community for
>>> testing purposes. Do not include any links
+1
Kim
Bryan Pendleton wrote:
I propose that Thomas Nielsen shall be a Derby committer.
Over the last 6 months, I've worked with Thomas on some Derby
features (http://wiki.apache.org/db-derby/OLAPOperations) as well
as on some fairly sophisticated bug fixes, including
https://issues.apache.org
[
https://issues.apache.org/jira/browse/DERBY-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582761#action_12582761
]
Kim Haase commented on DERBY-3474:
--
Anurag, would you like to review the modified files fo
+1
Bryan Pendleton wrote:
I propose that Thomas Nielsen shall be a Derby committer.
Over the last 6 months, I've worked with Thomas on some Derby
features (http://wiki.apache.org/db-derby/OLAPOperations) as well
as on some fairly sophisticated bug fixes, including
https://issues.apache.org/jira
Rick Hillegas <[EMAIL PROTECTED]> writes:
> Kathey Marsden wrote:
>> Bryan Pendleton wrote:
>>>
>>> During the process of developing software and preparing a release,
>>> various packages are made available to the developer community for
>>> testing purposes. Do not include any links on the
[
https://issues.apache.org/jira/browse/DERBY-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase reopened DERBY-3169:
--
Actually, I meant to keep this issue open rather than resolving it -- there are
a couple more minor change
Bryan Pendleton <[EMAIL PROTECTED]> writes:
>> I think there was some distinction in the Apache policy regarding
>> "visible to developers" versus "visible to users", right?
>
> Following up on my own message, the two important Apache-wide
> policy links appear to be:
> http://www.apache.org/dev/r
+1
Bryan Pendleton wrote:
I propose that Thomas Nielsen shall be a Derby committer.
Over the last 6 months, I've worked with Thomas on some Derby
features (http://wiki.apache.org/db-derby/OLAPOperations) as well
as on some fairly sophisticated bug fixes, including
https://issues.apache.org/jira
Mike Matrigali <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] wrote:
>> Is there an existing bug in Derby which you consider to be a showstopper for
>> 10.4? (Meaning that you will veto the release unless this bug gets fixed).
>> If this bug is not being actively worked on, please flag it here AS
I propose that Thomas Nielsen shall be a Derby committer.
Over the last 6 months, I've worked with Thomas on some Derby
features (http://wiki.apache.org/db-derby/OLAPOperations) as well
as on some fairly sophisticated bug fixes, including
https://issues.apache.org/jira/browse/DERBY-3301 and
https
[
https://issues.apache.org/jira/browse/DERBY-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase resolved DERBY-3169.
--
Resolution: Fixed
Fix Version/s: 10.4.0.0
Derby Info: (was: [Patch Available])
Committe
[
https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-3574:
--
Attachment: TestLobLength.java
> With client, attempting to get the lob length after commit or
With client, attempting to get the lob length after commit or connection close
if there was a call to length() before commit does not throw an exception
---
Kathey Marsden wrote:
Bryan Pendleton wrote:
During the process of developing software and preparing a release,
various packages are made available to the developer community for
testing purposes. Do not include any links on the project website that
might encourage non-developers to dow
Thank you Mike pointing this out!
Due to Eastern holidays, things have got some delays. But I will make
both this report and fill out the platformresults on the wiki - probably
tomorrow.
But we thought it might be useful to the community to already post
results as soon as we had them, not real
Kathey Marsden wrote:
Bryan Pendleton wrote:
During the process of developing software and preparing a release,
various packages are made available to the developer community for
testing purposes. Do not include any links on the project website that
might encourage non-developers to dow
I tried running the code coverage using the Wiki page instructions. But for
me the instrumentation failed. I thought all the relevant patches are
committed? Is there any other patch I have to apply before running?
--
Thanks,
Manjula.
[EMAIL PROTECTED] wrote:
Is there an existing bug in Derby which you consider to be a showstopper for
10.4? (Meaning that you will veto the release unless this bug gets fixed).
If this bug is not being actively worked on, please flag it here ASAP,
so that those looking for bugs to fix can conside
Bryan Pendleton wrote:
During the process of developing software and preparing a release,
various packages are made available to the developer community for
testing purposes. Do not include any links on the project website that
might encourage non-developers to download and use nightly b
I think there was some distinction in the Apache policy regarding
"visible to developers" versus "visible to users", right?
Following up on my own message, the two important Apache-wide
policy links appear to be:
http://www.apache.org/dev/release.html
and http://incubator.apache.org/guides/gradu
Some of the links from the public test post page for 10.4
at http://dbtg.thresher.com/derby/test/ are not working. I am
sure this is new given that the release is just coming together,
so just wondering if those maintaining this are already aware.
I can report more in detail if that is useful.
F
Bryan Pendleton wrote:
Just to be clear there is no 10.4 release until a vote occurs. A while
back there was an ASF mandate that only PMC approved releases could be
visible to users, e.g. on download pages etc.
Oops! Thanks Dan. As soon as I sent my message I remembered that
discussion, and yo
[Auto-generated mail]
*Daily* 641405/2008-03-26 18:01:07 MET
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
lin
1274273 083.70% derbyall
F:6,E:497219711 0 1211.97% suitesAll
sles
Just to be clear there is no 10.4 release until a vote occurs. A while
back there was an ASF mandate that only PMC approved releases could be
visible to users, e.g. on download pages etc.
Oops! Thanks Dan. As soon as I sent my message I remembered that
discussion, and you're of course exactly r
Daniel John Debrunner wrote:
John is actively involved on both the derby-dev and derby-user lists and
fully engages in open development. He has had a number of patches
committed, most recently taking the stalled JMX work and getting it into
a shape where it could be committed to allow others to
Bryan Pendleton wrote:
Just a friendly reminder from your RM saying that Wiki pages for test
results have been created:
Dyre, might it be good to send a mail to the user list encouraging
them to try 10.4 beta with their existing applications and test drive
new features?
And should we also
Is there an existing bug in Derby which you consider to be a showstopper for
10.4? (Meaning that you will veto the release unless this bug gets fixed).
If this bug is not being actively worked on, please flag it here ASAP,
so that those looking for bugs to fix can consider it.
I hope that many peo
I didn't quite follow all of this, and admit i am not up on replication.
It would be nice if this process was the exact code as the normal
checkpoint processing. So a checkpoint would be triggered and then
after it had done it's work it would do the appropriate cleanup. If you
do the cleanup too
If you can narrow down to a specific table, then giving the ddl of that
table may help. Also if you are familar with the data that is supposed
to be in that table could you comment on if the hex dump looks sort of
valid? If you look at the right hand side of the hex dump it just
prints the ascii
Just a friendly reminder from your RM saying that Wiki pages for test
results have been created:
Dyre, might it be good to send a mail to the user list encouraging them
to try 10.4 beta with their existing applications and test drive new
features?
And should we also start to make the new re
[EMAIL PROTECTED] wrote:
Just a friendly reminder from your RM saying that Wiki pages for test
results have been created:
Dyre, might it be good to send a mail to the user list encouraging them
to try 10.4 beta with their existing applications and test drive new
features?
Kathey
Just a friendly reminder from your RM saying that Wiki pages for test
results have been created:
http://wiki.apache.org/db-derby/TenFourPlatformTesting
http://wiki.apache.org/db-derby/TenFourBuddyTesting
http://wiki.apache.org/db-derby/TenFourApplicationTesting
Please record the results of any
[
https://issues.apache.org/jira/browse/DERBY-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3571:
---
Derby Info: [Patch Available]
Affects Version/s: (was: 10.4.1.0)
[
https://issues.apache.org/jira/browse/DERBY-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dyre Tjeldvoll closed DERBY-3203.
-
> Convert jdbcapi/statementJdbc20.java to JUnit
> -
>
>
[
https://issues.apache.org/jira/browse/DERBY-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dyre Tjeldvoll resolved DERBY-3203.
---
Resolution: Fixed
Resolving since the problem with ResultSet.setFetchSize() has been factored
[
https://issues.apache.org/jira/browse/DERBY-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3571:
---
Attachment: derby-3571-1b-client_track_lob_fix.diff
'derby-3571-1b-client_track_lob_fix.diff'
Argument checking for ResultSet.setFetchSize(int) is incorrect
--
Key: DERBY-3573
URL: https://issues.apache.org/jira/browse/DERBY-3573
Project: Derby
Issue Type: Bug
Comp
+1
John will make a fine committer.
John is actively involved on both the derby-dev and derby-user lists
and fully engages in open development. He has had a number of patches
committed, most recently taking the stalled JMX work and getting it
into a shape where it could be committed to all
[
https://issues.apache.org/jira/browse/DERBY-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582707#action_12582707
]
John H. Embretsen commented on DERBY-3435:
--
Thanks for committing, Bernt!
I intend
[
https://issues.apache.org/jira/browse/DERBY-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2911:
--
Derby Info: [Patch Available]
> Implement a buffer manager using java.util.concurrent c
[
https://issues.apache.org/jira/browse/DERBY-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582698#action_12582698
]
Kristian Waagan commented on DERBY-3571:
Thanks for the comments Knut Anders.
This
Daniel John Debrunner wrote:
John is actively involved on both the derby-dev and derby-user lists and
fully engages in open development. He has had a number of patches
committed, most recently taking the stalled JMX work and getting it into
a shape where it could be committed to allow others to
Issue Subscription
Filter: Derby: JIRA issues with patch available (17 issues)
Subscriber: derby-dev
Key Summary
DERBY-3549 Unable to start slave mode after authentication failure on a
previous startSlave attempt
https://issues.apache.org/jira/browse/DERBY-3549
DERBY-3527 T
+1
Dag
[
https://issues.apache.org/jira/browse/DERBY-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner reassigned DERBY-3153:
Assignee: Vemund Østgaard (was: Daniel John Debrunner)
Assign to Vemund, s
[
https://issues.apache.org/jira/browse/DERBY-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase resolved DERBY-3542.
--
Resolution: Fixed
> New ROW_NUMBER function topic needs a few minor fixes
> ---
[
https://issues.apache.org/jira/browse/DERBY-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-3542:
-
Fix Version/s: 10.4.0.0
> New ROW_NUMBER function topic needs a few minor fixes
> ---
[
https://issues.apache.org/jira/browse/DERBY-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582686#action_12582686
]
John H. Embretsen commented on DERBY-3561:
--
I am only able to reproduce this failu
[
https://issues.apache.org/jira/browse/DERBY-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582685#action_12582685
]
Kim Haase commented on DERBY-3542:
--
Committed revision 641843 to 10.4 branch.
> New ROW_
[
https://issues.apache.org/jira/browse/DERBY-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582679#action_12582679
]
Jørgen Løland commented on DERBY-3549:
--
> Do you plan to add any test cases for this i
[
https://issues.apache.org/jira/browse/DERBY-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jørgen Løland updated DERBY-3549:
-
Attachment: derby-3549-1b.stat
derby-3549-1b.diff
Thanks for reviewing the patch.
[
https://issues.apache.org/jira/browse/DERBY-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582674#action_12582674
]
Jørgen Løland commented on DERBY-3403:
--
New test case required:
4: DERBY-3549 - unabl
[
https://issues.apache.org/jira/browse/DERBY-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erlend Birkenes reassigned DERBY-3568:
--
Assignee: Erlend Birkenes
> Convert jdbcapi/savepointJdbc30_JSR169.java and
> jdbcapi/
[
https://issues.apache.org/jira/browse/DERBY-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2911:
--
Attachment: d2911-15.diff
d2911-14.diff
Attaching two new patches for r
[
https://issues.apache.org/jira/browse/DERBY-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582649#action_12582649
]
Knut Anders Hatlen commented on DERBY-3571:
---
Hi Kristian,
I think the approach s
[Auto-generated mail]
*tinderbox_trunk16* 641764/2008-03-27 11:02:27 CET
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
0274274 086.96% derbyall
F:1,E:096949693 0
[
https://issues.apache.org/jira/browse/DERBY-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582633#action_12582633
]
Øystein Grøvlen commented on DERBY-3527:
Thanks for the new patch, Jørgen. I think
[
https://issues.apache.org/jira/browse/DERBY-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582629#action_12582629
]
Jørgen Løland commented on DERBY-3417:
--
I'm not sure this can be solved. AFAIK, the cl
[
https://issues.apache.org/jira/browse/DERBY-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jørgen Løland closed DERBY-3206.
> Replication: Add functionality to send various commands from master to slave
> using the replication
[
https://issues.apache.org/jira/browse/DERBY-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jørgen Løland resolved DERBY-3206.
--
Resolution: Fixed
Fix Version/s: 10.4.0.0
> Replication: Add functionality to send vario
[
https://issues.apache.org/jira/browse/DERBY-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Øystein Grøvlen closed DERBY-3382.
--
> Replication: Slave must inform master if DBs are out of sync.
> -
[
https://issues.apache.org/jira/browse/DERBY-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-3352:
--
Attachment: test.diff
I'm not familiar with this code, but the fix looks simple and cor
[
https://issues.apache.org/jira/browse/DERBY-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582596#action_12582596
]
Thomas Nielsen commented on DERBY-3572:
---
Junjie,
Please take a few minutes to study
[
https://issues.apache.org/jira/browse/DERBY-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junjie Peng closed DERBY-3572.
--
> directory error in the file "java/testing/README.htm"
> -
[
https://issues.apache.org/jira/browse/DERBY-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junjie Peng resolved DERBY-3572.
Resolution: Fixed
> directory error in the file "java/testing/README.htm"
> ---
[
https://issues.apache.org/jira/browse/DERBY-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
V.Narayanan updated DERBY-3526:
---
Attachment: Derby3526_1.stat
Derby3526_1.diff
Thanks for looking at the issue oystein
[
https://issues.apache.org/jira/browse/DERBY-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582590#action_12582590
]
Junjie Peng commented on DERBY-3572:
I will do it .Thank you!
> directory error in the
Daniel John Debrunner wrote:
John is actively involved on both the derby-dev and derby-user lists
and fully engages in open development. He has had a number of patches
committed, most recently taking the stalled JMX work and getting it
into a shape where it could be committed to allow others to
[
https://issues.apache.org/jira/browse/DERBY-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernt M. Johnsen resolved DERBY-3435.
-
Resolution: Fixed
Derby Info: (was: [Patch Available])
Committed revision 641765 on
[
https://issues.apache.org/jira/browse/DERBY-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3523:
--
Attachment: derby-3523-upgradetest_v2.diff
In Derby 10.0 the syntax for creating primary key al
[
https://issues.apache.org/jira/browse/DERBY-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582580#action_12582580
]
Bernt M. Johnsen commented on DERBY-3435:
-
Committed revision 641762 on trunk
> Ad
Daniel John Debrunner <[EMAIL PROTECTED]> writes:
> John is actively involved on both the derby-dev and derby-user lists
> and fully engages in open development. He has had a number of patches
> committed, most recently taking the stalled JMX work and getting it
> into a shape where it could be co
[
https://issues.apache.org/jira/browse/DERBY-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dyre Tjeldvoll updated DERBY-3138:
--
Fix Version/s: 10.4.0.0
This issue has no fix version, but has been checked in to trunk after t
[
https://issues.apache.org/jira/browse/DERBY-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dyre Tjeldvoll updated DERBY-3517:
--
Fix Version/s: 10.4.0.0
This issue has no fix version, but has been checked in to trunk after t
[
https://issues.apache.org/jira/browse/DERBY-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dyre Tjeldvoll updated DERBY-2939:
--
Fix Version/s: 10.4.0.0
This issue has no fix version, but has been checked in to trunk after t
1 - 100 of 131 matches
Mail list logo
