> your jar depends on a other jar, then you declare it in a dependency and
> it ends up in the classpath entry or you dont't depend on it, then just
> don't declare the dependency at all.
>
> -Tim
>
> jzhang schrieb:
>> Tim,
>>
>> You are righ
Tim,
You are right. I had jar instead of
ejb so the ejb-plugin did not get executed. Now all
dependencies are in calss-path. Is there anyway I can select some of them? I
don't think works here.
Thanks,
J
jzhang wrote:
>
> I am using Maven 2.0.7. In my ear file, I have a ejb
in this release:
** Bug
* [MEJB-7] - Transitive Classpath not written to the manifest
Not sure what to do with it. I might want to try using jar plugin. Any help
is appreciated.
Tim Kettler wrote:
>
> jzhang schrieb:
>>
>> Tim Kettler wrote:
>>> Hi,
>
LarryS wrote:
>
> Hi I am hoping somebody can help me understand how manifests are
> created by the ejb plugin as I am having a strange proble. I have two
> ejbs in my build. Both have a dependency to another jar which has a
> jar with hibernate mappings in it. The jar with the hibernate mappin
Tim Kettler wrote:
>
> Hi,
>
> jzhang schrieb:
>> I am using Maven 2.0.7. In my ear file, I have a ejb jar (called
>> core.jar)
>> that depends on common.jar. They are all in the same ear. I want to have
>> core.jar manifest.mf file have Class-Path entry
I am using Maven 2.0.7. In my ear file, I have a ejb jar (called core.jar)
that depends on common.jar. They are all in the same ear. I want to have
core.jar manifest.mf file have Class-Path entry for common.jar. But I can
not get that work. I follow maven-ejb-plugin instruction:
