[
https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-647:
--------------------------------
Attachment: pom.xml
exectck.zip
Still have issues with classpath, even though all seems well. Using maven jar
plugin to create enhanced jar files, with partial success.
1 URL(s) for loader:
/home/michelle/jdo/jdo/trunk/tck/target/enhanced/jdori/applicationidentity/
Oct 14, 2010 8:32:15 PM org.datanucleus.enhancer.DataNucleusEnhancer <init>
INFO: DataNucleus Enhancer : Using ClassEnhancer "ASM" for API "JDO"
Oct 14, 2010 8:32:16 PM org.datanucleus.metadata.MetaDataManager loadClasses
SEVERE: Class
"org.apache.jdo.tck.api.persistencemanagerfactory.config.StoreListener" was not
found in the CLASSPATH. Please check your specification and your CLASSPATH.
org.datanucleus.exceptions.ClassNotResolvedException: Class
"org.apache.jdo.tck.api.persistencemanagerfactory.config.StoreListener" was not
found in the CLASSPATH. Please check your specification and your CLASSPATH.
at
org.datanucleus.JDOClassLoaderResolver.classForName(JDOClassLoaderResolver.java:247)
at
org.datanucleus.JDOClassLoaderResolver.classForName(JDOClassLoaderResolver.java:412)
at
org.datanucleus.metadata.MetaDataManager.loadClasses(MetaDataManager.java:436)
at
org.datanucleus.enhancer.DataNucleusEnhancer.getFileMetadataForInput(DataNucleusEnhancer.java:745)
at
org.datanucleus.enhancer.DataNucleusEnhancer.enhance(DataNucleusEnhancer.java:582)
at
org.datanucleus.jdo.JDODataNucleusEnhancer.enhance(JDODataNucleusEnhancer.java:126)
at org.apache.jdo.exectck.Enhance.execute(Enhance.java:182)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Oct 14, 2010 8:32:16 PM org.datanucleus.metadata.MetaDataManager loadClasses
SEVERE: Class "org.apache.jdo.tck.api.jdohelper.GetObjectIdForTransient" was
not found in the CLASSPATH. Please check your specification and your CLASSPATH.
org.datanucleus.exceptions.ClassNotResolvedException: Class
"org.apache.jdo.tck.api.jdohelper.GetObjectIdForTransient" was not found in the
CLASSPATH. Please check your specification and your CLASSPATH.
at
org.datanucleus.JDOClassLoaderResolver.classForName(JDOClassLoaderResolver.java:247)
at
org.datanucleus.JDOClassLoaderResolver.classForName(JDOClassLoaderResolver.java:412)
...
> Run TCK using Maven2 for consistency
> ------------------------------------
>
> Key: JDO-647
> URL: https://issues.apache.org/jira/browse/JDO-647
> Project: JDO
> Issue Type: Improvement
> Components: tck
> Affects Versions: JDO 3
> Reporter: Andy Jefferson
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1
>
> Attachments: api_pom.diff, exectck.zip, exectck2.jar, pom.xml
>
>
> Since api2 now builds using Maven2 it makes a heck of a lot of sense to
> build/run the TCK using that too. It also means that the DataNucleus M1 repo
> (which only exists for use of this TCK) can be deleted. Please consider
> upgrading to Maven2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
