RE: single artifact mantra and ejb projects
Thanks for the response Rob. I went through the documentation I had posted and updated a couple things (eclipse explanation, changing common to ejb-client, some of the maven script). I had the same problem as you, and I fixed it by making sure that all of my property files didn't have an extra space at the end of each line. That will throw off pretty much everything. If you could try again (maybe grab the updated files off the wiki), and let me know if you have any other problems. Thanks! Ryan -Original Message- From: Rob Moore [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 14, 2004 6:41 PM To: [EMAIL PROTECTED] Subject: Re: single artifact mantra and ejb projects Hi, Ryan, I just reviewed your wiki posting pretty extensively and found it to be a great help. However, I've had a problem with the part about running 'maven multiproject:install' in the root project. I get this error: Starting the reactor... BUILD FAILED File.. file:/C:/Documents and Settings/Rob/.maven/plugins/maven-multiproject-plugin-1.1/ Element... maven:reactor Line.. 174 Column 9 IO error scanning directory c:\WUTemp\myproject\root\..\ Total time: 3 seconds Finished at: Wed Jan 14 18:37:35 CST 2004 Have you seen this kind of thing before? Also, I was curious about your statement regarding Eclipse compatibility. Can you offer a bit more on what happens within Eclipse if the more 'traditional' approach is taken? I find the root project difficult to swallow -- but will accept it if I must. :^) Thanks, Rob Sonnek, Ryan wrote: I just finished added an entry to the wiki about how I have structured my EJB project. I would be very interested in hearing some feedback if it is on target with what other developers are doing. http://wiki.codehaus.org/maven/CreatingEjbApplications Ryan - 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]
RE: single artifact mantra and ejb projects
Hello Ryan, thanks for writing this documentation. I just set up such an environment following your description. One question: If I start maven I will always get an exception: = snip org.apache.maven.verifier.UnsatisfiedDependencyException: The build cannot continue because of the following unsatisfied dependency: xjavadoc-1.0.2.jar (no download url specified) at org.apache.maven.verifier.DependencyVerifier.satisfyDependencies(DependencyVerifier.java:219) at org.apache.maven.verifier.DependencyVerifier.verify(DependencyVerifier.java:135) at org.apache.maven.project.Project.verifyDependencies(Project.java:1384) at org.apache.maven.plugin.JellyPlugin.load(JellyPlugin.java:190) at org.apache.maven.plugin.PluginManager.loadPlugin(PluginManager.java:324) at org.apache.maven.plugin.PluginManager.loadPlugin(PluginManager.java:311) at org.apache.maven.plugin.PluginManager.processPluginFile(PluginManager.java:227) at org.apache.maven.plugin.PluginManager.expandPluginJars(PluginManager.java:209) at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:297) at org.apache.maven.MavenSession.initializePluginManager(MavenSession.java:242) at org.apache.maven.MavenSession.initialize(MavenSession.java:209) at org.apache.maven.cli.App.doMain(App.java:481) at org.apache.maven.cli.App.main(App.java:1145) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) = snap Did you modify locally your xdoclet-plugin? It seems to express its dependency with the id-tag and cannot find the xjavadoc-1.0.2 on ibiblio (although it is there ...). I also added this artifact in my root project.xml (like you did), but it does not help here. Any hint? Regards, Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: single artifact mantra and ejb projects
Ryan, First off all, many thanks for your continued work on the wiki entry. Here are some questions/points: 1. Might I suggest that you add a jar/zip file containing the example code? 2. What is the eclipse.dependency declaration do in the ejb project.xml? It seems odd to see it in the ejb project.xml. I guess I'd assume it would be in the ejb-client project.xml if it depends on the ejb project. 3. I noticed that you are referencing version 1.2b4 of the xdoclet-jboss-module. Is there a reason you are using that version and not 1.2 (as you do everywhere else)? dependency groupIdxdoclet/groupId artifactIdxdoclet-jboss-module/artifactId version1.2b4/version urlhttp://xdoclet.sourceforge.net/url /dependency 4. I just created the project using the changes you posted and I get the following error: BUILD FAILED File.. file:/C:/Documents and Settings/Rob/.maven/plugins/maven-multiproject-plugin-1.1/ Element... maven:reactor Line.. 174 Column 9 Unable to obtain goal [multiproject:install-callback] -- file:/C:/Documents and Settings/Rob/.maven/plugins/maven-multiproject-plugin-1.1/:210:61: attainGoal No goal [jar :install] Total time: 12 seconds Finished at: Thu Jan 15 10:54:45 CST 2004 Notice the space between 'jar' and ':install' on the attainGoal line. Also, I have a project of my own built using the guidelines you put forward and I see something similar when I try to run maven multiproject:install in my root project, except the line is 'No goal [ejb: install]'. Rob Sonnek, Ryan wrote: Thanks for the response Rob. I went through the documentation I had posted and updated a couple things (eclipse explanation, changing common to ejb-client, some of the maven script). I had the same problem as you, and I fixed it by making sure that all of my property files didn't have an extra space at the end of each line. That will throw off pretty much everything. If you could try again (maybe grab the updated files off the wiki), and let me know if you have any other problems. Thanks! Ryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: single artifact mantra and ejb projects
The problem you are havins is due to the xdoclet plugin looking for the xjavadoc artifact in the xjavadoc groupId (which doesn't exist on ibiblio). I've filed a upload request to have xjavadoc moved into it's own groupId, but it hasn't been done yet. That being said, there's more wrong with the xdoclet plugin than just the xjavadoc dependency.. I originally the wiki documentation with the intent of using the xdoclet-maven-plugin. After several failed attempts to get it up and working, I reverted to my existing build using only the xdoclet ant tags within maven.xml. I don't know if this is the correct direction, but IMO the xdoclet-maven-plugin is absolutely atrocious. I would rather have the maintenance of my maven.xml script over trying to use the xdoclet plugin. I would check out the latest changes I made on the wiki, and uninstall the xdoclet plugin (just delete it), and try building again. I didn't have any problems getting the listed documentation up and running. Let me know if you have any other problems. Ryan -Original Message- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 10:44 AM To: Maven Users List Subject: RE: single artifact mantra and ejb projects Hello Ryan, thanks for writing this documentation. I just set up such an environment following your description. One question: If I start maven I will always get an exception: = snip org.apache.maven.verifier.UnsatisfiedDependencyException: The build cannot continue because of the following unsatisfied dependency: xjavadoc-1.0.2.jar (no download url specified) at org.apache.maven.verifier.DependencyVerifier.satisfyDependencies(DependencyV erifier.java:219) at org.apache.maven.verifier.DependencyVerifier.verify(DependencyVerifier.java: 135) at org.apache.maven.project.Project.verifyDependencies(Project.java:1384) at org.apache.maven.plugin.JellyPlugin.load(JellyPlugin.java:190) at org.apache.maven.plugin.PluginManager.loadPlugin(PluginManager.java:324) at org.apache.maven.plugin.PluginManager.loadPlugin(PluginManager.java:311) at org.apache.maven.plugin.PluginManager.processPluginFile(PluginManager.java:2 27) at org.apache.maven.plugin.PluginManager.expandPluginJars(PluginManager.java:20 9) at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:297) at org.apache.maven.MavenSession.initializePluginManager(MavenSession.java:242) at org.apache.maven.MavenSession.initialize(MavenSession.java:209) at org.apache.maven.cli.App.doMain(App.java:481) at org.apache.maven.cli.App.main(App.java:1145) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) = snap Did you modify locally your xdoclet-plugin? It seems to express its dependency with the id-tag and cannot find the xjavadoc-1.0.2 on ibiblio (although it is there ...). I also added this artifact in my root project.xml (like you did), but it does not help here. Any hint? Regards, Jörg - 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]
RE: single artifact mantra and ejb projects
You have to make sure all the properties files contain no extra space after the value. Clear those out and you won't have a problem (ie: change maven.multiproject.type=jar_ to maven.multiproject.type=jar). The jboss plugin is version 1.2b4 because the final 1.2 module is not on ibiblio. I've put in a JIRA request for it to be uploaded, but it hasn't been done yet. I don't know if there was a reason it was not put on ibiblio, or if it was just accidentally overlooked. If I knew how to attach a zip file of the sample to the wiki I certainly would! I have never done that before, so if there's a way, let me know and I'll put it up there. The eclipse dependency is used to map the EJB classes to their interfaces. In my example, I package the EJB interfaces and Data Objects (or value objects), into the ejb-client. IMO, this is the easiest way for 3rd party apps to gain access to your application. They only need this one jar file and they're good to go. Because the data objects are in the ejb-client subproject, and the data objects are used within the signatures of the ejb java code, there is a dependency between the two. You'll notice that in the ejb's maven.xml, I intentionally delete the interfaces and data objects after they are generated to avoid duplicate classes existing. Feel free to ask any other questions, or if you think there is a better way, I'd love to hear it! Ryan -Original Message- From: Rob Moore [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 11:02 AM To: Maven Users List Subject: Re: single artifact mantra and ejb projects Ryan, First off all, many thanks for your continued work on the wiki entry. Here are some questions/points: 1. Might I suggest that you add a jar/zip file containing the example code? 2. What is the eclipse.dependency declaration do in the ejb project.xml? It seems odd to see it in the ejb project.xml. I guess I'd assume it would be in the ejb-client project.xml if it depends on the ejb project. 3. I noticed that you are referencing version 1.2b4 of the xdoclet-jboss-module. Is there a reason you are using that version and not 1.2 (as you do everywhere else)? dependency groupIdxdoclet/groupId artifactIdxdoclet-jboss-module/artifactId version1.2b4/version urlhttp://xdoclet.sourceforge.net/url /dependency 4. I just created the project using the changes you posted and I get the following error: BUILD FAILED File.. file:/C:/Documents and Settings/Rob/.maven/plugins/maven-multiproject-plugin-1.1/ Element... maven:reactor Line.. 174 Column 9 Unable to obtain goal [multiproject:install-callback] -- file:/C:/Documents and Settings/Rob/.maven/plugins/maven-multiproject-plugin-1.1/:210:61: attainGoal No goal [jar :install] Total time: 12 seconds Finished at: Thu Jan 15 10:54:45 CST 2004 Notice the space between 'jar' and ':install' on the attainGoal line. Also, I have a project of my own built using the guidelines you put forward and I see something similar when I try to run maven multiproject:install in my root project, except the line is 'No goal [ejb: install]'. Rob Sonnek, Ryan wrote: Thanks for the response Rob. I went through the documentation I had posted and updated a couple things (eclipse explanation, changing common to ejb-client, some of the maven script). I had the same problem as you, and I fixed it by making sure that all of my property files didn't have an extra space at the end of each line. That will throw off pretty much everything. If you could try again (maybe grab the updated files off the wiki), and let me know if you have any other problems. Thanks! Ryan - 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]
RE: single artifact mantra and ejb projects
A little investigation into the wiki has shown me the light... I was able to upload a sample project in a ZIP format. -Original Message- From: Sonnek, Ryan [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 11:38 AM To: 'Maven Users List' Subject: RE: single artifact mantra and ejb projects You have to make sure all the properties files contain no extra space after the value. Clear those out and you won't have a problem (ie: change maven.multiproject.type=jar_ to maven.multiproject.type=jar). The jboss plugin is version 1.2b4 because the final 1.2 module is not on ibiblio. I've put in a JIRA request for it to be uploaded, but it hasn't been done yet. I don't know if there was a reason it was not put on ibiblio, or if it was just accidentally overlooked. If I knew how to attach a zip file of the sample to the wiki I certainly would! I have never done that before, so if there's a way, let me know and I'll put it up there. The eclipse dependency is used to map the EJB classes to their interfaces. In my example, I package the EJB interfaces and Data Objects (or value objects), into the ejb-client. IMO, this is the easiest way for 3rd party apps to gain access to your application. They only need this one jar file and they're good to go. Because the data objects are in the ejb-client subproject, and the data objects are used within the signatures of the ejb java code, there is a dependency between the two. You'll notice that in the ejb's maven.xml, I intentionally delete the interfaces and data objects after they are generated to avoid duplicate classes existing. Feel free to ask any other questions, or if you think there is a better way, I'd love to hear it! Ryan -Original Message- From: Rob Moore [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 11:02 AM To: Maven Users List Subject: Re: single artifact mantra and ejb projects Ryan, First off all, many thanks for your continued work on the wiki entry. Here are some questions/points: 1. Might I suggest that you add a jar/zip file containing the example code? 2. What is the eclipse.dependency declaration do in the ejb project.xml? It seems odd to see it in the ejb project.xml. I guess I'd assume it would be in the ejb-client project.xml if it depends on the ejb project. 3. I noticed that you are referencing version 1.2b4 of the xdoclet-jboss-module. Is there a reason you are using that version and not 1.2 (as you do everywhere else)? dependency groupIdxdoclet/groupId artifactIdxdoclet-jboss-module/artifactId version1.2b4/version urlhttp://xdoclet.sourceforge.net/url /dependency 4. I just created the project using the changes you posted and I get the following error: BUILD FAILED File.. file:/C:/Documents and Settings/Rob/.maven/plugins/maven-multiproject-plugin-1.1/ Element... maven:reactor Line.. 174 Column 9 Unable to obtain goal [multiproject:install-callback] -- file:/C:/Documents and Settings/Rob/.maven/plugins/maven-multiproject-plugin-1.1/:210:61: attainGoal No goal [jar :install] Total time: 12 seconds Finished at: Thu Jan 15 10:54:45 CST 2004 Notice the space between 'jar' and ':install' on the attainGoal line. Also, I have a project of my own built using the guidelines you put forward and I see something similar when I try to run maven multiproject:install in my root project, except the line is 'No goal [ejb: install]'. Rob Sonnek, Ryan wrote: Thanks for the response Rob. I went through the documentation I had posted and updated a couple things (eclipse explanation, changing common to ejb-client, some of the maven script). I had the same problem as you, and I fixed it by making sure that all of my property files didn't have an extra space at the end of each line. That will throw off pretty much everything. If you could try again (maybe grab the updated files off the wiki), and let me know if you have any other problems. Thanks! Ryan - 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]
Re: single artifact mantra and ejb projects
Regarding the xdoclet plugin. I hacked it myself to fix the issue. All you need to change is the last dependency in the project.xml so that it has this: dependency groupIdxdoclet/groupId artifactIdxjavadoc/artifactId version1.0.2/version urlhttp://xdoclet.sourceforge.net/url /dependency I've attached my hacked version of the original plugin. Hopefully it will make it through. Rob Sonnek, Ryan wrote: The problem you are havins is due to the xdoclet plugin looking for the xjavadoc artifact in the xjavadoc groupId (which doesn't exist on ibiblio). I've filed a upload request to have xjavadoc moved into it's own groupId, but it hasn't been done yet. That being said, there's more wrong with the xdoclet plugin than just the xjavadoc dependency.. maven-xdoclet-plugin-1.2.jar Description: application/java-archive - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: single artifact mantra and ejb projects
Sonnek, Ryan wrote: You have to make sure all the properties files contain no extra space after the value. Clear those out and you won't have a problem (ie: change maven.multiproject.type=jar_ to maven.multiproject.type=jar). D'oh! I forgot about checking the maven.multiproject.type line for a trailing space. Sorry about that... The jboss plugin is version 1.2b4 because the final 1.2 module is not on ibiblio. I've put in a JIRA request for it to be uploaded, but it hasn't been done yet. I don't know if there was a reason it was not put on ibiblio, or if it was just accidentally overlooked. Ah, yes. I set up my own repository just for that reason. If I knew how to attach a zip file of the sample to the wiki I certainly would! I have never done that before, so if there's a way, let me know and I'll put it up there. Down at the very bottom of the page is an action called Attach File. Easy to miss. The eclipse dependency is used to map the EJB classes to their interfaces. In my example, I package the EJB interfaces and Data Objects (or value objects), into the ejb-client. IMO, this is the easiest way for 3rd party apps to gain access to your application. They only need this one jar file and they're good to go. Because the data objects are in the ejb-client subproject, and the data objects are used within the signatures of the ejb java code, there is a dependency between the two. You'll notice that in the ejb's maven.xml, I intentionally delete the interfaces and data objects after they are generated to avoid duplicate classes existing. Okay, so the Java files that are used by the EJB project are really in the client project. In other words, these 'shared' files don't live in the parent project at all. Is that correct? Thanks again, Rob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: single artifact mantra and ejb projects
Sonnek, Ryan wrote: A little investigation into the wiki has shown me the light... I was able to upload a sample project in a ZIP format. Cool! Rob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: single artifact mantra and ejb projects
-Original Message- From: Rob Moore [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 12:29 PM To: Maven Users List Subject: Re: single artifact mantra and ejb projects Sonnek, Ryan wrote: You have to make sure all the properties files contain no extra space after the value. Clear those out and you won't have a problem (ie: change maven.multiproject.type=jar_ to maven.multiproject.type=jar). D'oh! I forgot about checking the maven.multiproject.type line for a trailing space. Sorry about that... The jboss plugin is version 1.2b4 because the final 1.2 module is not on ibiblio. I've put in a JIRA request for it to be uploaded, but it hasn't been done yet. I don't know if there was a reason it was not put on ibiblio, or if it was just accidentally overlooked. Ah, yes. I set up my own repository just for that reason. If I knew how to attach a zip file of the sample to the wiki I certainly would! I have never done that before, so if there's a way, let me know and I'll put it up there. Down at the very bottom of the page is an action called Attach File. Easy to miss. The eclipse dependency is used to map the EJB classes to their interfaces. In my example, I package the EJB interfaces and Data Objects (or value objects), into the ejb-client. IMO, this is the easiest way for 3rd party apps to gain access to your application. They only need this one jar file and they're good to go. Because the data objects are in the ejb-client subproject, and the data objects are used within the signatures of the ejb java code, there is a dependency between the two. You'll notice that in the ejb's maven.xml, I intentionally delete the interfaces and data objects after they are generated to avoid duplicate classes existing. Okay, so the Java files that are used by the EJB project are really in the client project. In other words, these 'shared' files don't live in the parent project at all. Is that correct? Right on. I wouldn't really call the EJB project the parent, but yes, the interfaces and data classes ONLY exist in the ejb-client project. Thanks again, Rob - 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]
single artifact mantra and ejb projects
I have a question about the mantra that a single project should produce a single artifact. I can buy into that in every case I have run across or have thought about, except for projects involving ejb creation. Typically an ejb project will produce both an ejb-jar file as well as a client-jar file. But wouldn't that be two artifacts? I have read a lot of external docs on setting up j2ee projects using maven, most of which suggest a multi project layout. I can totally justify that for say a j2ee project producing an ear made up of sub ejb-jars and wars. But in the case of a stand-alone ejb-jar producing project or an ejb-jar producing subproject of an ear project it seems like overkill to define a subproject for the ejb-jar generation and the client-jar generation, especially when both are ultimately logically tied to the attainment of an ejb goal. Could someone help me out in my understanding here? Thanks, Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: single artifact mantra and ejb projects
I would be very interested to hear other peoples opinion on this as well. I'm currently working on 4 separate EJB projects and have gone through this same situation. I have heard talk on the mailing list about adding support for an artifact type ejb-client.jar, but I don't remember who was looking into that. I've used the multiproject setup you've listed above, and with a little hack on the xdoclet plugin, got it up and running without any major problems. I would really like to flesh out some kind of maven methodology on this subject as I know it is a big area of question. I might put some time into putting something on the wiki regarding this. Ryan -Original Message- From: Ebersole, Steven [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 14, 2004 7:25 AM To: Maven Users List Subject: single artifact mantra and ejb projects I have a question about the mantra that a single project should produce a single artifact. I can buy into that in every case I have run across or have thought about, except for projects involving ejb creation. Typically an ejb project will produce both an ejb-jar file as well as a client-jar file. But wouldn't that be two artifacts? I have read a lot of external docs on setting up j2ee projects using maven, most of which suggest a multi project layout. I can totally justify that for say a j2ee project producing an ear made up of sub ejb-jars and wars. But in the case of a stand-alone ejb-jar producing project or an ejb-jar producing subproject of an ear project it seems like overkill to define a subproject for the ejb-jar generation and the client-jar generation, especially when both are ultimately logically tied to the attainment of an ejb goal. Could someone help me out in my understanding here? Thanks, Steve - 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]
RE: single artifact mantra and ejb projects
I just finished added an entry to the wiki about how I have structured my EJB project. I would be very interested in hearing some feedback if it is on target with what other developers are doing. http://wiki.codehaus.org/maven/CreatingEjbApplications Ryan -Original Message- From: Sonnek, Ryan [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 14, 2004 2:47 PM To: 'Maven Users List' Subject: RE: single artifact mantra and ejb projects I would be very interested to hear other peoples opinion on this as well. I'm currently working on 4 separate EJB projects and have gone through this same situation. I have heard talk on the mailing list about adding support for an artifact type ejb-client.jar, but I don't remember who was looking into that. I've used the multiproject setup you've listed above, and with a little hack on the xdoclet plugin, got it up and running without any major problems. I would really like to flesh out some kind of maven methodology on this subject as I know it is a big area of question. I might put some time into putting something on the wiki regarding this. Ryan -Original Message- From: Ebersole, Steven [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 14, 2004 7:25 AM To: Maven Users List Subject: single artifact mantra and ejb projects I have a question about the mantra that a single project should produce a single artifact. I can buy into that in every case I have run across or have thought about, except for projects involving ejb creation. Typically an ejb project will produce both an ejb-jar file as well as a client-jar file. But wouldn't that be two artifacts? I have read a lot of external docs on setting up j2ee projects using maven, most of which suggest a multi project layout. I can totally justify that for say a j2ee project producing an ear made up of sub ejb-jars and wars. But in the case of a stand-alone ejb-jar producing project or an ejb-jar producing subproject of an ear project it seems like overkill to define a subproject for the ejb-jar generation and the client-jar generation, especially when both are ultimately logically tied to the attainment of an ejb goal. Could someone help me out in my understanding here? Thanks, Steve - 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]
Re: single artifact mantra and ejb projects
Hi, Ryan, I just reviewed your wiki posting pretty extensively and found it to be a great help. However, I've had a problem with the part about running 'maven multiproject:install' in the root project. I get this error: Starting the reactor... BUILD FAILED File.. file:/C:/Documents and Settings/Rob/.maven/plugins/maven-multiproject-plugin-1.1/ Element... maven:reactor Line.. 174 Column 9 IO error scanning directory c:\WUTemp\myproject\root\..\ Total time: 3 seconds Finished at: Wed Jan 14 18:37:35 CST 2004 Have you seen this kind of thing before? Also, I was curious about your statement regarding Eclipse compatibility. Can you offer a bit more on what happens within Eclipse if the more 'traditional' approach is taken? I find the root project difficult to swallow -- but will accept it if I must. :^) Thanks, Rob Sonnek, Ryan wrote: I just finished added an entry to the wiki about how I have structured my EJB project. I would be very interested in hearing some feedback if it is on target with what other developers are doing. http://wiki.codehaus.org/maven/CreatingEjbApplications Ryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
