db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bouschen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-647) Run TCK using Maven2 for consistency
Date Mon, 01 Nov 2010 22:52:26 GMT

    [ 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: 
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: 
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.

View raw message