db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-1049) make existing derby release jars available for upgrade testing and client/server compatibility testing with derbyall
Date Thu, 06 Apr 2006 23:13:31 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1049?page=all ]
     
Andrew McIntyre resolved DERBY-1049:
------------------------------------

    Fix Version: 10.2.0.0
     Resolution: Fixed
      Assign To: Andrew McIntyre

Added jars to repository with revision 392111. To fetch the jars into your current subversion
view in tools/testing/derby/10.1.1.0, do the following from the top of  the tree:

svn propedit svn:externals tools/testing

this will bring up an empty document in your editor. Then add this line and save the document:

derby/10.1.1.0 https://svn.apache.org/repos/asf/db/derby/jars/10.1.1.0

The next time you perform a sync, the jars will be fetched from the repository into the proper
directory. When the upgrade tests are in place and working, we should commit the setting of
this property to the repository so that all subversion clients fetch the jars needed by the
upgrade tests.

> make existing derby release jars available for upgrade testing and client/server compatibility
testing with derbyall
> --------------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-1049
>          URL: http://issues.apache.org/jira/browse/DERBY-1049
>      Project: Derby
>         Type: Task

>   Components: Build tools
>     Reporter: Kathey Marsden
>     Assignee: Andrew McIntyre
>      Fix For: 10.2.0.0

>
> DERBY-514 : integrate upgrade testing into derbyall
> DERBY-1048 : Include run of jdbcapi/Compatibility test with first  client release in
derbyall
>  compatibility testing with derbyall, both require that the previous derby releases be
available in svn workspaces, either by checking in the jars or by some other method.
> We need at least:
> 10.1.1.0  - First client release  (for DERBY-1048)
> I am not sure abou these:
> 10.0.2.1  - First derby  release (incubator) 
> 10.1.2.1 -  10.1 Maintenance release

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message