[
http://jira.codehaus.org/browse/MOJO-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103365
]
Jaco Joubert commented on MOJO-844:
-----------------------------------
I'm experiencing the same problem, but in my case the jboss sar artifact is in
the repository as sar (not jboss-sar).
So I have project A:
a project with packaging type: jboss-sar
this project compiles successfully and installs into the repository as a
.sar.
Then, I have project B:
a normal jar project
project B depends on project A for compilation: <type>sar</type>
<scope>compile</scope>
But when I use maven to compile project B, it doesn't add A's sar to the
compile classpath, causing the compilation to fail.
You're saying:
{quote}The ESB patch which I have just submitted
(http://jira.codehaus.org/browse/MOJO-841) contains a workaround for this issue
and is generally applicable. {quote}
Is this really related, and what is the workaround?
> Dependency to project with packaging-type 'jboss-sar' doesn't work
> ------------------------------------------------------------------
>
> Key: MOJO-844
> URL: http://jira.codehaus.org/browse/MOJO-844
> Project: Mojo
> Issue Type: Bug
> Components: jboss-packaging-maven-plugin
> Reporter: Christian Presslmayr
>
> Hi!
> In my multi-module environment I have the following problem:
> - I have several projects, where one is dependent on another one, let's say
> project B is dependent on A.
> - Both projects have packaging-type 'jboss-sar'.
> - Project A compiles successfully, also the .sar file is created on mvn
> install
> - But compile for project B doesn't succeed, because it can't resolve the
> dependency to project A, i. e. it doesn't find the classes of project A,
> therefore I get an compile error. I defined this dependency in B's pom.xml as
> follows:
> <dependency>
> <groupId>mygroup</groupId>
> <artifactId>A</artifactId>
> <version>${project.version}</version>
> <type>jboss-sar</type>
> <scope>provided</scope>
> </dependency>
> I defined the scope 'provided', because I don't want the dependency to be
> packed into B's sar-file. But this seems is not the problem, because when
> omitting the scope, it doesn't work either.
> So it seems to me, that there's something wrong with the dependency mechanism
> for projects of type jboss-sar.
> Or am I missing some setting? Any help is appreciated!
> Thanks,
> Chris
--
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
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
