You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@gora.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/07/01 07:06:35 UTC

[jira] [Commented] (GORA-164) Use instead of configuration for test dependencies

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

Hudson commented on GORA-164:
-----------------------------

Integrated in goraOracle #6 (See [https://builds.apache.org/job/goraOracle/6/])
    GORA-164 Use <type> instead of <classifier> configuration for test dependencies (Revision 6698f7c20ae97faa124b431022de8a4499ca6d6b)
GORA-164 part 2 (Revision a96d68aebc480a1a7624977ff7c3c5244228b887)

     Result = FAILURE
lewismc : 
Files : 
* gora-hbase/pom.xml
* gora-sql/pom.xml
* CHANGES.txt
* gora-accumulo/pom.xml
* gora-cassandra/pom.xml

lewismc : 
Files : 
* pom.xml

                
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira