Hello, I think you do not generate the ejb-client from your project : <groupId>com.mhf</groupId> <artifactId>mhfEJBModuleClient</artifactId> <version>1.0</version>
Look at this page : http://maven.apache.org/maven-1.x/plugins/ejb/properties.html. You will find how to ask Maven EJB Plugin to generate your client. Do not forget to use the property maven.ejb.client.excludes to exclude classes which are not client specific. Yan Langlois. ----- Message d'origine ---- De : Denis Bessmertniy <[EMAIL PROTECTED]> À : Maven Users List <[email protected]> Envoyé le : Lundi, 24 Septembre 2007, 9h43mn 08s Objet : RE: MAVEN BUG: <type>ejb-client</type> problem The first, I haven't received the letter form Tim about artifactId. The second, I cannot understand what do you mean here. May you resend me the letter from Tim? Thank you - Denis -----Original Message----- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Monday, September 24, 2007 10:29 AM To: Maven Users List Subject: RE: MAVEN BUG: <type>ejb-client</type> problem You did not answer the question of Tim why your artifactId for the ejb client is different from the artifactId of the ejb itself. As long as you do not answer, we assume the bug is between screen and keyboard ... ;-) Denis Bessmertniy wrote on Monday, September 24, 2007 8:57 AM: > It sound like a bug in maven, because nobody knows where is the dog. > I still have this problem and I have read a lot of manuals and also > Better Build with maven book in order to find the answer, but nothing. > > > > -----Original Message----- > From: Denis Bessmertniy > [mailto:[EMAIL PROTECTED] > Sent: Friday, September 21, 2007 6:36 PM > To: 'Maven Users List' > Subject: RE: <type>ejb-client</type> problem > > No, I still have this problem, that is why I'm asking to help me. > > Please, > > -----Original Message----- > From: Tim Kettler [mailto:[EMAIL PROTECTED] > Sent: Friday, September 21, 2007 6:33 PM > To: Maven Users List > Subject: Re: <type>ejb-client</type> problem > > Denis Bessmertniy schrieb: >> That is good, but maybe somebody will help me, because I don't have >> my client jar in application.xml. > > I don't understand what you mean. What has this to do with your > original question? Is the problem with the resolution of the > ejb-client dependency fixed now? > >> >> >> >> -----Original Message----- >> From: Tim Kettler [mailto:[EMAIL PROTECTED] >> Sent: Friday, September 21, 2007 5:50 PM >> To: Maven Users List >> Subject: Re: <type>ejb-client</type> problem >> >> Denis Bessmertniy schrieb: >>> Sorry, my last letter was with wrong topic name >> >> This wouldn't have happened if you would just create new threads for >> your questions instead of hijacking existing threads. Now there are >> messages which are irrelevant to the original question - which has >> yet to be answered. >> >>> Hi folks, >>> >>> I building J2EE application with maven and now I encounter with >>> problem: Here is the dependency part of my pom from project where I >>> consturct EAR file <dependencies> >>> <dependency> >>> <groupId>com.mhf</groupId> >>> <artifactId>mhfEJBModuleClient</artifactId> >>> <version>1.0</version> >>> <type>ejb-client</type> >>> </dependency> >> >> Shouldn't this be: >> >> <dependency> >> <groupId>com.mhf</groupId> >> <artifactId>mhfEJBModule</artifactId> >> <version>1.0</version> >> <type>ejb-client</type> >> </dependency> >> >> Or isn't your ejb-client artifact autogenerated by the ejb-plugin? >> >> -Tim >> >>> <dependency> >>> <groupId>com.mhf</groupId> >>> <artifactId>mhfEJBModule</artifactId> >>> <version>1.0</version> >>> <type>ejb</type> >>> </dependency> >>> <dependency> >>> <groupId>com.mhf</groupId> >>> <artifactId>mhfWebModule</artifactId> >>> <version>1.0</version> >>> <type>war</type> >>> </dependency> >>> </dependencies> >>> >>> All is ok, but when I use <type>ejb-client</type> for first >>> dependency, it tells me >>> >>> Missing: >>> ---------- >>> 1) com.mhf:mhfEJBModuleClient:ejb-client:client:1.0 >>> >>> Try downloading the file manually from the project website. >>> >>> Then, install it using the command: >>> mvn install:install-file -DgroupId=com.mhf >>> -DartifactId=mhfEJBModuleClient \ >>> -Dversion=1.0 -Dclassifier=client -Dpackaging=ejb-client >>> -Dfile=/path/to/file Alternatively, if you host your own repository >>> you >> can >>> deploy the file >>> there: mvn deploy:deploy-file -DgroupId=co >>> .mhf -DartifactId=mhfEJBModuleClient \ >>> -Dversion=1.0 -Dclassifier=client -Dpackaging=ejb-client >>> -Dfile=/path/to/file \ >>> -Durl=[url] -DrepositoryId=[id] >>> >>> Path to dependency: >>> 1) com.mhf:mhfApplication:ear:1.0 >>> 2) com.mhf:mhfEJBModuleClient:ejb-client:client:1.0 >>> >>> ---------- >>> 1 required artifact is missing. >>> >>> for artifact: >>> com.mhf:mhfApplication:ear:1.0 >>> >>> from the specified remote repositories: >>> central (http://repo1.maven.org/maven2) >>> >>> >>> >>> But when I don't have <type>ejb-client</type>, all is ok and this >>> jars >> just >>> copies to lib dir in my EAR. >>> But I need to have the link to this jar in generated >>> application.xml, and >> I >>> don't have it. >>> >>> Where is the dog? >>> >>> >>> >>> > --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> > --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _____________________________________________________________________________ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail
