TBH, I would prefer if we endorsed jboss-deployment-structure.xml more.
I believe that it is more toolable than MANIFEST.MF, and doing the
MANIFEST.MF dance in a Maven build requires adding some boilerplate code
to the pom.xml. I know that in the end it's a small change, but if I had
to do custom stuff to my project, then I'd rather just add a new file
(which would happen for MANIFEST.MF anyways) rather than adding a file
*and* changing the pom.
Jason T. Greene wrote:
That is the correct way to do it. Otherwise you can use
jboss-deployment-structure.xml if you prefer.
See:
https://docs.jboss.org/author/display/AS7/Class+Loading+in+AS7
On 7/12/11 6:20 PM, Brian Stansberry wrote:
> Does doing the same thing Carlo did on that linked file work?
>
> Dependencies: org.hornetq.ra
>
> in the war's MANIFEST.MF
>
> On 7/12/11 5:28 PM, Martin Schwartzman wrote:
>
>> Anyone know how to specify a manual dependency on the hornetq-ra module
>> in a war?
>>
>> Ah yes, at the moment you have to specify a manual dependency on the
>> hornetq-ra module.
>>
>> See
>>
https://github.com/wolfc/jboss-as/blob/AS7-579/testsuite/spec/src/test/re...
>>
>> Don't know how to specify this in a war, but somebody on the dev list
>> will...
>>
>> Thanks,
>>
>> Martin
>>
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>