[
http://jira.codehaus.org/browse/MOJO-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101763
]
JL commented on MOJO-844:
-------------------------
We have the same problem. Our sar dependencies is not included in the
classpath, resulting in compilation error.
This is a quite annoying bug, and as a quick workaround we are just creating
two artifacts for each of our sar modules, one
dummy with jar packaging that we include as a dependency just to be able to
compile our project (and generate intellij project files).
Our domain objects are packaged in these sar modules, and we have also
discussed moving the classes into a separate jar and
include this in the sar modules as a temporary workaround.
Is this bug actually related to the jboss-packaging-maven-plugin, or to the
compile and intellij plugins?
> 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
