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 "Michael Bouschen (JIRA)" <ji...@apache.org> on 2013/04/28 21:06:16 UTC
[jira] [Resolved] (JDO-717) copyjdorijars does not cleanup target
directory
[ https://issues.apache.org/jira/browse/JDO-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bouschen resolved JDO-717.
----------------------------------
Resolution: Fixed
Assignee: Michael Bouschen (was: Matthew T. Adams)
Correct, the issue is resolved by the checkin.
I created another issue JDO-722 for the remaining issue of using maven profiles to handle the jdori dependencies in the CLASSPATH.
> copyjdorijars does not cleanup target directory
> -----------------------------------------------
>
> Key: JDO-717
> URL: https://issues.apache.org/jira/browse/JDO-717
> Project: JDO
> Issue Type: Improvement
> Components: site and infrastructure
> Affects Versions: JDO 3 update 1 (3.0.1)
> Reporter: Michael Bouschen
> Assignee: Michael Bouschen
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: JDO-717.patch
>
>
> The submodule copyjdorijars does not cleanup the target directory before copying the jdori artifacts. This may lead to multiple versions of the jdori in the target directory when running the tck.
> An alternative solution is adding the jdori dependencies as part of a jdori profile such that they do not get added to the CLASSPATH when running an iut.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira