On 8/21/06, Knut Anders Hatlen [EMAIL PROTECTED] wrote:
Don't you have to set debug=true/false as well?
Insane with line numbers:ant -Dsane=false -Ddebug=true
Insane without line numbers: ant -Dsane=false -Ddebug=false
Sane with line numbers: ant -Dsane=true -Ddebug=true
Sane without
[ http://issues.apache.org/jira/browse/DERBY-744?page=all ]
Andrew McIntyre resolved DERBY-744.
---
Fix Version/s: 10.1.4.0
10.2.1.0
(was: 10.3.0.0)
Resolution: Fixed
Merged to 10.2 branch with revision
Currently, BaseJDBCTestCase.assertSQLState() and JDBC.assertSQLState()
basically do an assertEquals() on the SQL state. If the SQL state
doesn't match the expected value, an AssertionFailure is raised, but
the original exception is thrown away.
Should we instead do something like this
if
[Auto-generated mail]
*TinderBox_Derby* 433502/2006-08-22 06:22:31 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
1672671 2 145.21% SunOS-5.10_i86pc-i386
Details in
ResultSet.rowInserted(), rowUpdated() and rowDeleted() don't throw exception on
read-only result sets
-
Key: DERBY-1744
URL:
[ http://issues.apache.org/jira/browse/DERBY-1655?page=all ]
Laura Stewart updated DERBY-1655:
-
Attachment: derby1655_devguide2.diff
derby1655_ref2.diff
Updated patch files for XML support, based on all of the comments received so
far.
[ http://issues.apache.org/jira/browse/DERBY-1655?page=all ]
Laura Stewart updated DERBY-1655:
-
Attachment: derby1655_devguide_html2.zip
derby1655_ref_html2.zip
Attaching HTML zip files with all of the changes. The latest files changed
Details from the standard (maybe I'm just nit-picking ;-)
Semicolon in SQL is used
1) After statements in trigger and procedure bodies (we don't support this)
2) In various embedded SQL variants (Statements are terminated with
semicolon when SQL is embedded in Ada, C, Pascal, PL/I.
[Auto-generated mail]
*Derby* 433306/2006-08-21 19:46:04 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.6*
3716713 0 111.32% SunOS-5.10_i86pc-i386
Details in
Hi,
Hmm, I don't really know from where to download the 10.2.0.0 version (or
10.2.1.0 version) of derby...
Should I get the sources and compile them?
Regards,
Wiktor
-Original Message-
From: Bryan Pendleton (JIRA) [mailto:[EMAIL PROTECTED]
Sent: 9 sierpnia 2006 17:45
To: Wiktor
[ http://issues.apache.org/jira/browse/DERBY-598?page=all ]
Kristian Waagan closed DERBY-598.
-
Closing this. See previous comment by Sunitha.
Ensure that with derby.language.logStatementText.true, values set by streams
are not materialized
[
http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429668 ]
Mayuresh Nirhali commented on DERBY-418:
I tried the approach suggested by Dan in DERBY-1142, and my version of change
looks like as below,
In
Daniel John Debrunner wrote:
I don't see any value in this, the existing layput looks fine to me.
org.apache.derbyTesting.junit.functionalTests.tests.jdbcapi
org.apache.derbyTesting.junit.unitTests.lang
org.apache.derbyTesting.junit.systemTests.app1 (future)
(Note: existing layout does not
[
http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429674 ]
Knut Anders Hatlen commented on DERBY-418:
--
Hi Mayuresh,
I'm afraid your fix has some unwanted consequences. First of all, the
OutOfMemoryError is still
[
http://issues.apache.org/jira/browse/DERBY-1547?page=comments#action_12429677 ]
V.Narayanan commented on DERBY-1547:
Thank you for the comments on the patch. Going by your comments of using
existing property files would it be possible to
[
http://issues.apache.org/jira/browse/DERBY-1558?page=comments#action_12429682 ]
Andreas Korneliussen commented on DERBY-1558:
-
Committed revision 433607.
enable more testcases in ConcurrencyTest
[ http://issues.apache.org/jira/browse/DERBY-1558?page=all ]
Andreas Korneliussen resolved DERBY-1558.
-
Resolution: Fixed
enable more testcases in ConcurrencyTest
Key: DERBY-1558
[ http://issues.apache.org/jira/browse/DERBY-1558?page=all ]
Andreas Korneliussen closed DERBY-1558.
---
enable more testcases in ConcurrencyTest
Key: DERBY-1558
URL:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kristian Waagan wrote:
Hi,
I still have a question regarding the placement of JUnit tests. I have
brought this up before, but got very little response (I did get some,
see below).
Do we want to support [unit] testing of package private
[ http://issues.apache.org/jira/browse/DERBY-1730?page=all ]
Knut Anders Hatlen updated DERBY-1730:
--
Description:
With osgi.jar in tools/java, 'ant buildjars' does not add the OSGi attributes
to derby.jar's manifest. Instead, a file named
[ http://issues.apache.org/jira/browse/DERBY-1730?page=all ]
Knut Anders Hatlen closed DERBY-1730.
-
Resolution: Fixed
Patch has been merged into the 10.2 branch. Thanks Andrew! Closing the issue.
Manifest file doesn't contain OSGi attributes
[
http://issues.apache.org/jira/browse/DERBY-1740?page=comments#action_12429695 ]
Kristian Waagan commented on DERBY-1740:
Could you provide more detail on this issue?
I'm not able to reproduce it. It caught my interest because I worked
Andreas Korneliussen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kristian Waagan wrote:
Hi,
I still have a question regarding the placement of JUnit tests. I have
brought this up before, but got very little response (I did get some,
see below).
Do we want to support [unit] testing
[ http://issues.apache.org/jira/browse/DERBY-23?page=all ]
Knut Anders Hatlen resolved DERBY-23.
-
Resolution: Fixed
I'm marking this issue as resolved.
The reason why I haven't resolved it before, is that I still see
OutOfMemoryError on some
[ http://issues.apache.org/jira/browse/DERBY-1473?page=all ]
Kristian Waagan updated DERBY-1473:
---
Attachment: derby-1473-1b-streaming.diff
derby-1473-2b-streamingtests.diff
Hi Knut Anders,
- Fixed.
- Thanks for catching this. It's a
[
http://issues.apache.org/jira/browse/DERBY-1731?page=comments#action_12429704 ]
Rick Hillegas commented on DERBY-1731:
--
Hey Dan, can you clarify what you'd like to see here? The one-line description
indicates some verbiage in the user
These changes were put back a while ago and rick made an integration
for this into the derby codeline.
There will be one more change to Types.java i believe in order to
prevent a collision for a large number of users of a specific database
due to their own types colliding with the JDBC
Hi David,
With build 95 of the 1.6 beta, various constants in DatabaseMetaData
changed name (see DERBY-1530). The constants named functionParameter*
changed name to functionColumn*. From this build output, it appears that
you have not synced up to the state of the mainline after DERBY-1530
Andreas Korneliussen wrote:
I think there are some testclasses which are in the same source tree as
the derby source, however the .class files are packaged into
dergbyTesting.jar. I.e: org/apache/derby/impl/drda/TestProto.class
I think that class should be moved into the derbyTesting area
Kristian Waagan wrote:
Andreas Korneliussen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kristian Waagan wrote:
Hi,
I still have a question regarding the placement of JUnit tests. I have
brought this up before, but got very little response (I did get some,
see below).
Do
[
http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429709 ]
Mayuresh Nirhali commented on DERBY-418:
Thanks Knut for pointing that out.
I did not mean to provide a patch for this JIRA, but just wanted to try out a
[ http://issues.apache.org/jira/browse/DERBY-1705?page=all ]
Rick Hillegas resolved DERBY-1705.
--
Resolution: Fixed
This test runs cleanly in the 10.2 branch after the mega merge.
Test jdbcapi/dataSourceReference.java fails with 10.2.1 beta candidate
[
http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429712 ]
Knut Anders Hatlen commented on DERBY-418:
--
Did you try to declare BaseActivation.inUse as volatile?
outofmemory error when running large query in
Alternatively, we could print out the stack trace ourselves. The logic
to do this could be re-usable by a general-purpose assertEquals()
overload which compares two Throwables. Failing by calling
assertEquals() seems like the way the JUnit wants to track errors.
Regards,
-Rick
Knut Anders
Wiktor Lisowicz wrote:
Hi,
Hmm, I don't really know from where to download the 10.2.0.0 version (or
10.2.1.0 version) of derby...
Should I get the sources and compile them?
The download link is in the 10.2 Release Summary section on the
TenTwoRelease wiki page at
[
http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429721 ]
Daniel John Debrunner commented on DERBY-418:
-
Any change must not ignore exceptions thrrown during an activation.close().
}
[
http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429725 ]
Knut Anders Hatlen commented on DERBY-418:
--
Mayuresh, with your latest changes, I don't see the memory leak any more
(neither DERBY-418 nor DERBY-1142).
[
http://issues.apache.org/jira/browse/DERBY-1743?page=comments#action_12429733 ]
Bryan Pendleton commented on DERBY-1743:
This is almost certainly from line 298 of DRDAProtocolException.java, which
reads:
[
http://issues.apache.org/jira/browse/DERBY-1535?page=comments#action_12429734 ]
Tomohito Nakayama commented on DERBY-1535:
--
Patch for rollback committed.
Sendingjava/drda/org/apache/derby/impl/drda/DDMReader.java
Sending
[
http://issues.apache.org/jira/browse/DERBY-1559?page=comments#action_12429735 ]
Tomohito Nakayama commented on DERBY-1559:
--
I rollbacked DERBY-1535 and DERBY-1513.
I think it will make a conflict on this issue.
Please take your
Bryan Pendleton (JIRA) wrote:
I reviewed d688_phase6_v1.patch and it looks good to me. The
build was fine, and derbyall ran cleanly. xml_general.sql and
xmlBinding.java ran as expected with Xalan 2.7. Committed this
patch to subversion as revision 433450, and cleared the
PatchAvailable flag.
[
http://issues.apache.org/jira/browse/DERBY-1633?page=comments#action_12429738 ]
Rick Hillegas commented on DERBY-1633:
--
Hi Army. Thanks for the new patch and the extensive explanation in this JIRA
and in the code. I am inclined to check
[
http://issues.apache.org/jira/browse/DERBY-688?page=comments#action_12429739 ]
A B commented on DERBY-688:
---
Does the phase6 patch need to be applied to the 10.2 branch?
Yes, that'd be great. Thanks for bringing this up--I'd forgotten about the
Daniel John Debrunner wrote:
Kristian Waagan wrote:
Andreas Korneliussen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kristian Waagan wrote:
Hi,
I still have a question regarding the placement of JUnit tests. I have
brought this up before, but got very little response (I did get
[
http://issues.apache.org/jira/browse/DERBY-1711?page=comments#action_12429746 ]
Francois Orsini commented on DERBY-1711:
Hi Chinmay,
This is not a bug - The 'derby.connection.requireAuthentication' derby property
is a static one -
Issue Subscription
Filter: Derby: JIRA issues with patch available (23 issues)
Subscriber: derby-dev
Key Summary
DERBY-1633 Regression: The fields of views are not being calculated properly
since 10.1.2.4
http://issues.apache.org/jira/browse/DERBY-1633
DERBY-1559 when
Rick Hillegas wrote:
Alternatively, we could print out the stack trace ourselves. The logic
to do this could be re-usable by a general-purpose assertEquals()
overload which compares two Throwables. Failing by calling
assertEquals() seems like the way the JUnit wants to track errors.
I think
[ http://issues.apache.org/jira/browse/DERBY-1731?page=all ]
Rick Hillegas updated DERBY-1731:
-
Description:
While JDBC 4.0 does not require any warning statement (see DEBRY-1639) it would
be good for Derby to have such a statement.
I think we want to
[ http://issues.apache.org/jira/browse/DERBY-1223?page=all ]
Laura Stewart updated DERBY-1223:
-
Attachment: derby1223.diff
Derby1223_html.zip
Attached a patch and html zip file for these doc updates.
Several questions:
1) When is it
[ http://issues.apache.org/jira/browse/DERBY-1223?page=all ]
Laura Stewart updated DERBY-1223:
-
Derby Info: [Patch Available]
Update Getting Started to include instructions on setting JAVA_HOME variable.
[
http://issues.apache.org/jira/browse/DERBY-1731?page=comments#action_12429759 ]
Daniel John Debrunner commented on DERBY-1731:
--
Do we need to explicitly list the problems that can occur (abstract method
errors and constant
Does the phase6 patch need to be applied to the 10.2 branch?
Yes, that'd be great. Thanks for bringing this up--I'd forgotten about the
need for this...
I intend to merge the phase6 patch for DERBY-688 to the 10.2
branch in the next day or so. Rick (or anyone else), please let
me know if
[
http://issues.apache.org/jira/browse/DERBY-1655?page=comments#action_12429760 ]
A B commented on DERBY-1655:
The latest changes to the devguide look great and can be commited:
derby1655_devguide2.diff (+1)
For the reference guide, it looks
[ http://issues.apache.org/jira/browse/DERBY-1739?page=all ]
Daniel John Debrunner updated DERBY-1739:
-
Fix Version/s: 10.3.0.0
Fixed in trunk (10.3), may still merge changes over to 10.2 to reduce
differences between branches for future
[ http://issues.apache.org/jira/browse/DERBY-1731?page=all ]
Rick Hillegas updated DERBY-1731:
-
Description:
While JDBC 4.0 does not require any warning statement (see DEBRY-1639) it would
be good for Derby to have such a statement.
I think we want to
[ http://issues.apache.org/jira/browse/DERBY-1655?page=all ]
Laura Stewart updated DERBY-1655:
-
Attachment: derby1655_ref3.diff
derby1655_ref_html3.zip
Hi Army -
You were correct, the new files were missing from the html zip file and
[Auto-generated mail]
*TinderBox_Derby* 433643/2006-08-22 16:32:58 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
1672671 2 120.47% SunOS-5.10_i86pc-i386
Details in
[ http://issues.apache.org/jira/browse/DERBY-1731?page=all ]
Rick Hillegas reassigned DERBY-1731:
Assignee: Rick Hillegas
Add warning to Derby docs that the JDBC 4.0 support is based upon the
proposed final draft of JSR 221 and might change in
[
http://issues.apache.org/jira/browse/DERBY-1731?page=comments#action_12429767 ]
Daniel John Debrunner commented on DERBY-1731:
--
Rick wrote:
When we know what the actual discrepancies are (if any), we will list them
in the
A B (JIRA) wrote:
[
http://issues.apache.org/jira/browse/DERBY-1655?page=comments#action_12429760
]
A B commented on DERBY-1655:
The latest changes to the devguide look great and can be commited:
derby1655_devguide2.diff (+1)
I'll
[
http://issues.apache.org/jira/browse/DERBY-1655?page=comments#action_12429768 ]
Jean T. Anderson commented on DERBY-1655:
-
Committed derby1655_devguide2.diff revision 433708.
Document XML functionality for 10.2
I think that the section titled branches on the web page
http://db.apache.org/derby/derby_downloads.html
needs to be updated, to reflect that there is now a 10.2 branch.
I think it's as simple as adding:
* 10.2
to the bullet list.
thanks,
bryan
[
http://issues.apache.org/jira/browse/DERBY-1731?page=comments#action_12429769 ]
Rick Hillegas commented on DERBY-1731:
--
Hm. Perhaps I am confused about the following. This is how I thought the
process played out:
1) We generate a
System catalog columns of type BIGINT and INT created with incorrect precision
of zero.
---
Key: DERBY-1745
URL: http://issues.apache.org/jira/browse/DERBY-1745
After building the docs, a devguide directory is created in
derby/docs/trunk with these files:
$ ls devguide
cdevcsecuregrantrevokeaccess.dita devconrefs.dita tdevconcepts41704.dita
I think it has been this way for a while, but I've been so focused on
commits to the src directory that I hadn't
[
http://issues.apache.org/jira/browse/DERBY-1731?page=comments#action_12429773 ]
Daniel John Debrunner commented on DERBY-1731:
--
I was assuming time 2) was still before Mustang and hence JDBC 4 went GA so
there could still be
upgrade tests should start using 10.1.3 released builds
---
Key: DERBY-1746
URL: http://issues.apache.org/jira/browse/DERBY-1746
Project: Derby
Issue Type: Test
Components: Test
Hey Andrew,
Can you clarify the following? I was under the impression that Release
Notes were compiled under the following process:
1) First the community approves a release candidate.
2) Then the release manager compiles Release Notes and posts them on the
release page hung off the web
Hi Bryan,
Thanks for pointing this out. I will make this change.
Regards,
-Rick
Bryan Pendleton wrote:
I think that the section titled branches on the web page
http://db.apache.org/derby/derby_downloads.html
needs to be updated, to reflect that there is now a 10.2 branch.
I think it's as
Jean T. Anderson wrote:
Bryan Pendleton wrote:
I think that the section titled branches on the web page
http://db.apache.org/derby/derby_downloads.html
needs to be updated, to reflect that there is now a 10.2 branch.
I think it's as simple as adding:
* 10.2
to the bullet list.
This is
[
http://issues.apache.org/jira/browse/DERBY-1223?page=comments#action_12429779 ]
Kim Haase commented on DERBY-1223:
--
1) When is it appropriate to have classpath in uppercase... such as
CLASSPATH? Normally we do this for the name of things,
On 8/22/06, Rick Hillegas [EMAIL PROTECTED] wrote:
Hey Andrew,
Can you clarify the following? I was under the impression that Release
Notes were compiled under the following process:
1) First the community approves a release candidate.
2) Then the release manager compiles Release Notes and
[Auto-generated mail]
*TinderBox_Derby* 433698/2006-08-22 19:13:06 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
1672671 2 125.70% SunOS-5.10_i86pc-i386
Details in
[
http://issues.apache.org/jira/browse/DERBY-1728?page=comments#action_12429792 ]
Stan Bradbury commented on DERBY-1728:
--
So I guess it is no surprise that this failure happened on other platforms as
well (Win 2003 Server using JVM 1.5)?
[ http://issues.apache.org/jira/browse/DERBY-1636?page=all ]
Laura Stewart updated DERBY-1636:
-
Attachment: derby1636_devguide2.diff
derby1636_devguide_html2.zip
Attached is a patch and the html zip for the Dev Guide updates.
document
[ http://issues.apache.org/jira/browse/DERBY-1636?page=all ]
Laura Stewart updated DERBY-1636:
-
Attachment: derby1636_ref2.diff
derby1636_ref_html2.zip
Attached are the patch and html zip file for the updates to the Ref Manual.
[
http://issues.apache.org/jira/browse/DERBY-1636?page=comments#action_12429799 ]
Laura Stewart commented on DERBY-1636:
--
Suresh and Sunitha -
I ran into a problem implementing your suggestion for ordering and namging the
files.
The
[ http://issues.apache.org/jira/browse/DERBY-1636?page=all ]
Laura Stewart updated DERBY-1636:
-
Attachment: toc.html
Use this toc with the dev guide html zip files.
document encryption of an un-encrypted database and re-encryption with new
[
http://issues.apache.org/jira/browse/DERBY-1520?page=comments#action_12429805 ]
Stan Bradbury commented on DERBY-1520:
--
For now I think we need to simply document the names of the tables and a biref
description of each. A simple list
It was doing this to me last week -- I noticed today that I had such a
directory, dated 8/16. But I deleted it, and when I build the docs now,
this directory no longer appears.
They looked like semi-processed files that belonged in the temp
directory. Someone seems to have fixed things so that
[ http://issues.apache.org/jira/browse/DERBY-1747?page=all ]
Francois Orsini updated DERBY-1747:
---
Fix Version/s: 10.2.2.0
(was: 10.0.2.2)
Affects Version/s: 10.2.1.0
(was: 10.0.2.0)
[ http://issues.apache.org/jira/browse/DERBY-1747?page=all ]
Francois Orsini updated DERBY-1747:
---
Attachment: cadminapps49914.html.diffs
cadminappsclientsecurity.html.diffs
tdevcsecure82556.html.diffs
attaching diffs
[ http://issues.apache.org/jira/browse/DERBY-1747?page=all ]
Francois Orsini updated DERBY-1747:
---
Attachment: cadminapps49914.html
cadminappsclientsecurity.html
tdevcsecure82556.html
Documentation for 10.2 Strong
There was a problem with the ditamap file for the dev guide that
skewed all of the tags and made it unreadable. However I fixed it, I
can't recall which patch or if it has been commited yet, so I don't
know if this is part of what was occurring...
On 8/22/06, Kim Haase [EMAIL PROTECTED] wrote:
Laura Stewart wrote:
There was a problem with the ditamap file for the dev guide that
skewed all of the tags and made it unreadable. However I fixed it, I
can't recall which patch or if it has been commited yet, so I don't
know if this is part of what was occurring...
My svn working copy is
[
http://issues.apache.org/jira/browse/DERBY-1747?page=comments#action_12429814 ]
Jean T. Anderson commented on DERBY-1747:
-
Diffs for the html are helpful to see what changed, but they can't be committed
-- I'm not sure everybody
[ http://issues.apache.org/jira/browse/DERBY-1685?page=all ]
Laura Stewart updated DERBY-1685:
-
Attachment: derby1685_ref.diff
rrefbackupdbenablelognowaitproc.html
Attached are the updates to the file to update the procedure name.
The
[ http://issues.apache.org/jira/browse/DERBY-1685?page=all ]
Laura Stewart updated DERBY-1685:
-
Derby Info: [Patch Available]
The reference manual has wrong procedure name for online bacup
--
Global case insensitive setting
---
Key: DERBY-1748
URL: http://issues.apache.org/jira/browse/DERBY-1748
Project: Derby
Issue Type: New Feature
Reporter: Terry
By default MySQL is case insensitive
[ http://issues.apache.org/jira/browse/DERBY-1685?page=all ]
Laura Stewart updated DERBY-1685:
-
Attachment: rrefonlinebackupdbnowaitproc.html
Realized that I posted the incorrect html file.
I am posting the correct file now.
The reference manual has
[ http://issues.apache.org/jira/browse/DERBY-1685?page=all ]
Jean T. Anderson updated DERBY-1685:
Attachment: (was: rrefbackupdbenablelognowaitproc.html)
The reference manual has wrong procedure name for online bacup
[
http://issues.apache.org/jira/browse/DERBY-1740?page=comments#action_12429833 ]
Kristian Waagan commented on DERBY-1740:
Thank you Rajesh :)
The reason I asked for more information was that I did not see the problem when
I *thought*
[ http://issues.apache.org/jira/browse/DERBY-1601?page=all ]
Laura Stewart updated DERBY-1601:
-
Derby Info: [Patch Available]
Document (in Tuning Guide) new subquery materialization via hash join
behavior that was introduced with DERBY-781
[ http://issues.apache.org/jira/browse/DERBY-1601?page=all ]
Laura Stewart updated DERBY-1601:
-
Attachment: derby1601_tuning.diff
ctuntransform25857.html
Updated the Materialization topic to reflect the other type of subquery that
can
I have made a stab at adding contact information to the table of
Derby-powered applications at
http://wiki.apache.org/db-derby/UsesOfDerby. There are many gaps which
other people can hopefully fill in. I didn't do anything fancy; I just
culled contact info from the websites at the ends of the
[
http://issues.apache.org/jira/browse/DERBY-1685?page=comments#action_12429838 ]
Jean T. Anderson commented on DERBY-1685:
-
With this patch I think we end up with two pages with the same procedure,
though the first takes one arg and
[
http://issues.apache.org/jira/browse/DERBY-1636?page=comments#action_12429839 ]
Suresh Thalamati commented on DERBY-1636:
-
Thanks for explaining how the tasks are organized , Laura. I think what is
needed is a new entry in the
[ http://issues.apache.org/jira/browse/DERBY-1593?page=all ]
Andrew McIntyre resolved DERBY-1593.
Resolution: Fixed
Merged to 10.2 branch in mega-merge, marking Resolved.
Separate test jar files from the product jars in a distribution
[
http://issues.apache.org/jira/browse/DERBY-1747?page=comments#action_12429841 ]
Francois Orsini commented on DERBY-1747:
Yes - Thanks Jean - I was trying to get a volunteer to help get these
documentation changes into some DITA realm
[ http://issues.apache.org/jira/browse/DERBY-1655?page=all ]
A B updated DERBY-1655:
---
Attachment: ref_html3_comments.txt
Attaching a file, ref_html3_comments.txt, that has my review comments for the
documentation of the XML operators. Thank you for tackling
1 - 100 of 134 matches
Mail list logo