maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MNG-2045) Maven can't compile against sibling test-jar dependency in multiproject (Test Attached)
Date Sat, 01 Nov 2008 13:25:51 GMT

    [ http://jira.codehaus.org/browse/MNG-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152649#action_152649
] 

Benjamin Bentmann commented on MNG-2045:
----------------------------------------

The documentation has been fixed in [r709688|http://svn.eu.apache.org/viewvc?view=rev&revision=709688].
Left to discussion is whether the {{<classifier>tests</classifier>}} approach
should also be supported.

> Maven can't compile against sibling test-jar dependency in multiproject (Test Attached)
> ---------------------------------------------------------------------------------------
>
>                 Key: MNG-2045
>                 URL: http://jira.codehaus.org/browse/MNG-2045
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.0.2
>         Environment: WinXP
>            Reporter: Brian Fox
>            Assignee: Brian Fox
>             Fix For: 2.0.11
>
>         Attachments: it1021.tar.gz, mng-2045-ittest.zip, MNG-2045-maven-project-r577340.patch1,
MNG-2045-maven-project-r577340.patch2, sample.zip
>
>
> I have 2 projects under a parent like so:
> --Parent
>         --- sample-jar
>         --- sample-jar-user
> sample-jar builds and installs a test-jar along with the normal jar. sample-jar-user
depends on the test-jar at compile time. When I build from the parent folder, the build fails
because it can't find the class. When I go to sample-jar-user and build, it works fine.
> In the attached test case, to reproduce:
> from the root folder, run mvn clean install - See it fail.
> cd sample-jar-user; mvn clean install - see it succeed.
> I remember reading somewhere that in multiprojects, maven attempts to locate the sibling
classes in the source tree instead of using the jars from the repository. I'm guessing the
problem is here that it's not looking in ../sample-jar/target/test-classes for this code,
but really one should expect this to come from the repository.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message