gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lewis John McGibbney (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GORA-164) Use <type> instead of <classifier> configuration for test dependencies
Date Mon, 06 Aug 2012 17:13:02 GMT

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

Lewis John McGibbney updated GORA-164:

    Attachment: GORA-164.patch

patch for trunk
> Use <type> instead of <classifier> configuration for test dependencies
> ----------------------------------------------------------------------
>                 Key: GORA-164
>                 URL: https://issues.apache.org/jira/browse/GORA-164
>             Project: Apache Gora
>          Issue Type: Bug
>          Components: build process, maven
>    Affects Versions: 0.2.1
>         Environment: Maven 3
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>            Priority: Critical
>             Fix For: 0.3
>         Attachments: GORA-164.patch
> Previous maven guides suggested to use <classifier>tests</classifier> instead
of <type>test-jar</type>. While this currently works for some cases, it does not
properly work during a reactor build of the test JAR module and any consumer if a lifecycle
phase prior to install is invoked. In such a scenario, Maven will not resolve the test JAR
from the output of the reactor build but from the local/remote repository. Apparently, the
JAR from the repositories could be outdated or completely missing, causing a build failure
(cf. MNG-2045).
> A fix is required for all pom's which I will get sorted out ASAP

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message