[
http://jira.codehaus.org/browse/MNG-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184245#action_184245
]
Obi Ezechukwu commented on MNG-4248:
------------------------------------
I have attemted Joerg's suggestion, and I am afraid that I am experiencing the
same problem with maven 2.1.0. So it does not appear that this issue has been
fixed for multi-module projects.
> CLONE -Maven can't compile against sibling test-jar dependency in
> multiproject (Test Attached)
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-4248
> URL: http://jira.codehaus.org/browse/MNG-4248
> Project: Maven 2
> Issue Type: Bug
> Environment: WinXP
> Reporter: Obi Ezechukwu
> Assignee: Brian Fox
> Fix For: 2.0.8
>
>
> 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
