db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dibyendu Majumdar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3451) Remove dependency between StandardException class and org.apache.derby.impl.jdbc classes.
Date Sat, 23 Feb 2008 16:53:20 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571763#action_12571763

Dibyendu Majumdar commented on DERBY-3451:

The patch applies successfully if you use the patch command as follows:

patch -p1 < DERBY-3451_patch_1.txt

To use Eclipse apply patch, ignore leading path name segments should be set to 1.
However, the Eclipse apply patch fails because it seems to require exact match of base revisions.
The patch was created on a snapshot of trunk that is a few days old, and in the meantime,
StandardException appears to have changed.

I can use svn diff, but am unsure how to manage multiple patches against trunk using svn.

Mercurial allows me to maintain my changes as a series of patches, that I can keep separate
from the trunk. 

In the meantime if I update my local repository and recreate the patch, it should apply against
the latest revision in trunk.

> Remove dependency between StandardException class and org.apache.derby.impl.jdbc classes.
> -----------------------------------------------------------------------------------------
>                 Key: DERBY-3451
>                 URL: https://issues.apache.org/jira/browse/DERBY-3451
>             Project: Derby
>          Issue Type: Sub-task
>            Reporter: Dibyendu Majumdar
>            Assignee: Dibyendu Majumdar
>         Attachments: DERBY-3451_patch_1.txt
> In the package org.apache.derby.iapi.error, the class StandardException contains references
to following classes:
> org.apache.derby.impl.jdbc.Util
> org.apache.derby.impl.jdbc.EmbedSQLException
> This is undesirable as it introduces a dependency between StandardException and the implementation
of EmbedSQLException.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message