You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Andy Jefferson (JIRA)" <ji...@apache.org> on 2009/10/22 14:53:59 UTC
[jira] Created: (JDO-647) Run TCK using Maven2 for consistency
Run TCK using Maven2 for consistency
------------------------------------
Key: JDO-647
URL: https://issues.apache.org/jira/browse/JDO-647
Project: JDO
Issue Type: Improvement
Components: tck2
Reporter: Andy Jefferson
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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-647:
--------------------------------
Attachment: api_pom.diff
Diff of generated modified api/pom.xml with original
> 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, pom.xml, 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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ 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
pom.xml
pom.xml for api and tck2. Both were generated with the maven one plugin. api pom is approximately a superset of the generated file and the content in the already checked-in aip/pom.xml.
> 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: pom.xml, 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.
[jira] Commented: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900559#action_12900559 ]
Michelle Caisse commented on JDO-647:
-------------------------------------
api test fails when running tests with maven2 (mvn clean compile test; OR maven clean build; mvn test). Test failure occurs with both original pom.xml and new pom.xml attached to this issue.
-------------------------------------------------------------------------------
Test set: javax.jdo.JDOHelperTest
-------------------------------------------------------------------------------
Tests run: 35, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.023 sec <<< FAILURE!
testGetPMFNullResource(javax.jdo.JDOHelperTest) Time elapsed: 0.005 sec <<< FAILURE!
junit.framework.AssertionFailedError: Null resource name should result in JDOFatalUserException
at junit.framework.Assert.fail(Assert.java:47)
at javax.jdo.JDOHelperTest.testGetPMFNullResource(JDOHelperTest.java:199)
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
1,1 All
> 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, pom.xml, 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.
[jira] Issue Comment Edited: (JDO-647) Run TCK using Maven2 for
consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900559#action_12900559 ]
Michelle Caisse edited comment on JDO-647 at 8/20/10 11:20 AM:
---------------------------------------------------------------
api test fails when running tests with maven2 (mvn clean compile test; OR maven clean build; mvn test). Test failure occurs with both original pom.xml and new pom.xml attached to this issue.
-------------------------------------------------------------------------------
Test set: javax.jdo.JDOHelperTest
-------------------------------------------------------------------------------
Tests run: 35, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.023 sec <<< FAILURE!
testGetPMFNullResource(javax.jdo.JDOHelperTest) Time elapsed: 0.005 sec <<< FAILURE!
junit.framework.AssertionFailedError: Null resource name should result in JDOFatalUserException
at junit.framework.Assert.fail(Assert.java:47)
at javax.jdo.JDOHelperTest.testGetPMFNullResource(JDOHelperTest.java:199)
was (Author: mcaisse):
api test fails when running tests with maven2 (mvn clean compile test; OR maven clean build; mvn test). Test failure occurs with both original pom.xml and new pom.xml attached to this issue.
-------------------------------------------------------------------------------
Test set: javax.jdo.JDOHelperTest
-------------------------------------------------------------------------------
Tests run: 35, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.023 sec <<< FAILURE!
testGetPMFNullResource(javax.jdo.JDOHelperTest) Time elapsed: 0.005 sec <<< FAILURE!
junit.framework.AssertionFailedError: Null resource name should result in JDOFatalUserException
at junit.framework.Assert.fail(Assert.java:47)
at javax.jdo.JDOHelperTest.testGetPMFNullResource(JDOHelperTest.java:199)
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
1,1 All
> 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, pom.xml, 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.
[jira] Commented: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903199#action_12903199 ]
Michelle Caisse commented on JDO-647:
-------------------------------------
Checked in enhanced pom.xml for the api project. svn revision 990005.
> 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, pom.xml, 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.
[jira] Commented: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900729#action_12900729 ]
Michelle Caisse commented on JDO-647:
-------------------------------------
All api tests pass when building & testing in NetBeans IDE.
> 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, pom.xml, 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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-647:
--------------------------------
Attachment: (was: pom.xml)
> 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.jar, 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.
[jira] Assigned: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse reassigned JDO-647:
-----------------------------------
Assignee: Michelle Caisse
> 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
> Reporter: Andy Jefferson
> Assignee: Michelle Caisse
>
> 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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-647:
--------------------------------
Attachment: (was: exectck.zip)
> 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, 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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bouschen updated JDO-647:
---------------------------------
Fix Version/s: JDO 3 maintenance release 1
Affects Version/s: JDO 2 maintenance release 2
> 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 2 maintenance release 2
> Reporter: Andy Jefferson
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1
>
>
> 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.
[jira] Commented: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927203#action_12927203 ]
Michael Bouschen commented on JDO-647:
--------------------------------------
The patch looks good!
Just a question: when calling mvn install it skips installing the schema (see output below). Is this on purpose, because you want to test class enhancement?
--- part of mvn install output ---
[INFO] [jdo-exectck:installSchema {execution: default}]
Skipping InstallSchema!
[INFO] [jdo-exectck:enhance {execution: default}]
2 URL(s) for loader:
/Users/mbouschen/Projects/JDO/workspace/jdo/trunk/tck/target/enhanced/jdori/applicationidentity/
/Users/mbouschen/Projects/JDO/workspace/jdo/trunk/tck/target/classes/
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes
2 URL(s) for loader:
/Users/mbouschen/Projects/JDO/workspace/jdo/trunk/tck/target/enhanced/jdori/datastoreidentity/
/Users/mbouschen/Projects/JDO/workspace/jdo/trunk/tck/target/classes/
Enhancing classes
> 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, 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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-647:
--------------------------------
Attachment: (was: pom.xml)
> 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
>
>
> 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.
[jira] Commented: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927217#action_12927217 ]
Michelle Caisse commented on JDO-647:
-------------------------------------
Yes, I added parameters to turn each of the goals on and off, and I turned InstallSchema off for testing. You can edit the TCK's pom.xml to set the parameter to your liking.
> 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, 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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-647:
--------------------------------
Attachment: (was: exectck.jar)
> 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, exectck2.jar
>
>
> 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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bouschen updated JDO-647:
---------------------------------
Attachment: JDO-647-pom-properties.zip
Hi Michelle,
the attached zip file JDO-647-pom-properties.zip changes the pom.xml files in the root directory and in api, exectck and tck. The root pom defines properties e.g. <junit.version>3.8.1</junit.version> that are used in the dependency definitions of the subprojects poms. This way only the root pom.xml defines the version number in case the same dependency occurs in multiple subprojects. I added a <parent>...</parent> section in the poms of the subprojects to make the properties available.
I also changed the version number to 3.1-SNAPSHOT in all of the poms. Other than that I did not change any version number (e.g. update the datanucleus version number). This needs to be done afterwards.
You need to run mvn install in teh root directory. This copies the root pom in your local mvn repository.
Regards Michael
> 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, exectck.zip, JDO-647-pom-properties.zip, pom.xml, 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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ 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
Contains goals for installing schema and enhancing classes. I think it works.
> 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, 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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-647:
--------------------------------
Attachment: (was: exectck2.jar)
> 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
>
>
> 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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ 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
Next iteration. Contains RunTCK goal, but not fully functional. executes the command line, produces output with errors for one test, and never returns.
> 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, exectck.zip, pom.xml, 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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-647:
--------------------------------
Attachment: (was: pom.xml)
> 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, 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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-647:
--------------------------------
Attachment: (was: pom.xml)
> 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
>
>
> 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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ 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.jar
Attaching new Maven plugin project exectck and tck pom.xml that configures the plugin for tck. It currently has two goals - installSchema and help. To test,
- copy the pom.xml to the tck directory
- unjar the exectck project into an exectck directory sister to tck
- build exectck with maven2
- build tck with maven2
>From the tck directory, type "mvn jdo-exectck:help" for more information.
> 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.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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-647:
--------------------------------
Attachment: (was: pom.xml)
> 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, exectck2.jar
>
>
> 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.
[jira] Commented: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900770#action_12900770 ]
Michelle Caisse commented on JDO-647:
-------------------------------------
Good documentation on developing maven2 plugins:
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
> 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, pom.xml, 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.
[jira] Commented: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Craig L Russell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898298#action_12898298 ]
Craig L Russell commented on JDO-647:
-------------------------------------
I'd like to see a diff of the pom in the api project versus your generated pom here.
The pom for the tck is a good start. Ok to check in so we can at least start to compile using mvn while working on the running of the tck as a mvn integration phase item.
> 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: pom.xml, 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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-647:
--------------------------------
Attachment: exectck2.jar
pom.xml
These attachments include the enhance goal. Almost works, but there is a classpath problem:
[jdo-exectck:enhance {execution: default}]
Oct 7, 2010 7:42:29 PM org.datanucleus.enhancer.DataNucleusEnhancer <init>
INFO: DataNucleus Enhancer : Using ClassEnhancer "ASM" for API "JDO"
Oct 7, 2010 7:42:29 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:205)
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)
etc....
> 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.jar, 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.
[jira] Updated: (JDO-647) Run TCK using Maven2 for consistency
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bouschen updated JDO-647:
---------------------------------
Affects Version/s: JDO 3
(was: JDO 2 maintenance release 2)
> 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
>
>
> 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.