Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Date: Thu, 6 Dec 2012 20:23:09 +0000 (UTC)
From: "Michael Bouschen (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Message-ID: <JIRA.12608696.1348262430221.2198.1354825389363@arcas>
In-Reply-To: <JIRA.12608696.1348262430221@arcas>
References: <JIRA.12608696.1348262430221@arcas>
Subject: [jira] [Updated] (JDO-717) copyjdorijars does not cleanup target
 directory
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JDO-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Bouschen updated JDO-717:
---------------------------------

    Attachment: JDO-717.patch

Attached you find a patch for review. 
The patch uses the maven clean plugin to cleanup the target directory before copying the jdori jars.
                
> 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