db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-348) Fostore20 doesn't compile with latest changes to api20
Date Fri, 24 Mar 2006 02:10:24 GMT
    [ http://issues.apache.org/jira/browse/JDO-348?page=comments#action_12371662 ] 

Craig Russell commented on JDO-348:

My preference is to put these methods into the runtime implementation of PersistenceManagerImpl.
I don't feel strongly but I'm expecting that we will add the FetchPlan implementation into
runtime20 and put at least a skeleton of the makeTransient methods into runtime20 as well.
The structure of runtime20, core20, and fostore20 will need to be laid out in more detail
when we get to the detail design phase.

> Fostore20 doesn't compile with latest changes to api20
> ------------------------------------------------------
>          Key: JDO-348
>          URL: http://issues.apache.org/jira/browse/JDO-348
>      Project: JDO
>         Type: Bug
>   Components: runtime20
>     Versions: JDO 2 rc1
>     Reporter: Craig Russell
>     Assignee: Martin Zaun
>  Attachments: FOStorePM.newMakeTransient.patch
> java:compile:
>     [echo] Compiling to g:\olsen\jdo\apache_clean\jdo\trunk\fostore20/target/cla
> sses
>     [javac] Compiling 100 source files to G:\olsen\jdo\apache_clean\jdo\trunk\fo
> store20\target\classes
> G:\olsen\jdo\apache_clean\jdo\trunk\fostore20\src\java\org\apache\jdo\impl\fosto
> re\FOStorePM.java:35: org.apache.jdo.impl.fostore.FOStorePM is not abstract and
> does not override abstract method makeTransientAll(java.util.Collection,boolean)
>  in javax.jdo.PersistenceManager
> public class FOStorePM extends PersistenceManagerImpl
>        ^
> Note: G:\olsen\jdo\apache_clean\jdo\trunk\fostore20\src\java\org\apache\jdo\impl
> \fostore\FOStoreInput.java uses or overrides a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> 1 error

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message