Because ejb type maps to jar extension
On Sunday, 4 March 2012, Markus KARG <mar...@headcrashing.eu> wrote: > You are right, when adding <type>ejb</type> it is working! I missed the fact > that maven coordinates include the packaging, while the default packaging is > <type>jar</type>. The odd thing is that dependency resolution is working > without that. So it actually seems, module resolution is working correctly > while dependency resolution ignores <type>. > > Thanks a lot! > Markus > >> -----Original Message----- >> From: Stephen Coy [mailto:st...@resolvesw.com] >> Sent: Sonntag, 4. März 2012 09:44 >> To: Maven Users List >> Subject: Re: EAR project produces application.xml, but EJB module is >> missing >> >> The number one reason I've had this problem in the past is forgetting >> to specify: >> >> <type>ejb</type> >> >> in the dependency declarations for EJB jars. >> >> >> On 04/03/2012, at 2:33 AM, Markus KARG wrote: >> >> > Maven 3.0.4 is producing application.xml containing <module> entries >> > for some dependencies (RAR modules), but which is missing <module> >> > entries for other dependencies (EJB modules). This is weird as the >> pom >> > more or less is empty. It just contains the dependencies (RAR modules >> > and EJB modules) and Java EE version (6). So I assume one cannot do >> > wrong. Is that a bug in Maven or what the heck is the trick to get >> <module> entries for EJB modules? >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
