db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Jefferson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JDO-717) copyjdorijars does not cleanup target directory
Date Mon, 22 Apr 2013 18:17:16 GMT

    [ https://issues.apache.org/jira/browse/JDO-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13638256#comment-13638256
] 

Andy Jefferson commented on JDO-717:
------------------------------------

This patch seems to have been checked in long ago, and the "issue" doesn't seem to happen
here. Shouldn't this be closed? and if not, then how about a statement of what is missing?
                
> 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: Matthew T. Adams
>             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

Mime
View raw message