<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Maven 2&#8217;s EAR plugin gives me a headache</title>
	<atom:link href="http://blog.leenarts.net/2007/02/11/maven-2s-ear-plugin-gives-me-a-headache/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.leenarts.net/2007/02/11/maven-2s-ear-plugin-gives-me-a-headache/</link>
	<description>Macs, Java, software development, IT related books and things I do for a living.</description>
	<pubDate>Thu, 20 Nov 2008 17:48:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: whermeling</title>
		<link>http://blog.leenarts.net/2007/02/11/maven-2s-ear-plugin-gives-me-a-headache/#comment-49746</link>
		<dc:creator>whermeling</dc:creator>
		<pubDate>Tue, 06 Nov 2007 22:40:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.leenarts.net/2007/02/11/maven-2s-ear-plugin-gives-me-a-headache/#comment-49746</guid>
		<description>TIP: Use the classifier instead of a new 'type'. This will enable you to use it as a dependency pretty much the same way and you don't have to create a custom artifact type handler.

Further more read this blog for some really throrough maven2 / rad / websphere  configuation: http://mastersad.homelinux.net/blogs/index.php?blog=5&#38;p=47&#38;more=1&#38;c=1&#38;tb=1&#38;pb=1#more47</description>
		<content:encoded><![CDATA[<p>TIP: Use the classifier instead of a new &#8216;type&#8217;. This will enable you to use it as a dependency pretty much the same way and you don&#8217;t have to create a custom artifact type handler.</p>
<p>Further more read this blog for some really throrough maven2 / rad / websphere  configuation: <a href="http://mastersad.homelinux.net/blogs/index.php?blog=5&amp;p=47&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1#more47" rel="nofollow">http://mastersad.homelinux.net/blogs/index.php?blog=5&amp;p=47&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1#more47</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeroen</title>
		<link>http://blog.leenarts.net/2007/02/11/maven-2s-ear-plugin-gives-me-a-headache/#comment-24954</link>
		<dc:creator>Jeroen</dc:creator>
		<pubDate>Mon, 21 May 2007 21:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.leenarts.net/2007/02/11/maven-2s-ear-plugin-gives-me-a-headache/#comment-24954</guid>
		<description>Hello Andrew,

Check your mailbox. While I can't send around actual project related material because of NDAs and stuff, I can send you some sterilized information.

Hope the info helps.

For the rest of the world, here is the meat from my reply to Andrew:
-----

Your questions:
1: Yes. Use mvn help:effective-pom It shows you all defaults. But the good thing is, you can modify all that. We've modified our EJB, WAR and EAR projects to match RAD6 directory structure. Maven adapts easily to that, while RAD6 is not able to do it the other way around.

2. No. I've taken the RAD6 structure as is. Everything on a single level in a directory tree. Modules and parents can be indicated with relative paths. We pick the right EJBs, WARs and JARs up by declaring them as a dependency. Check the various scope options for dependencies and understand them.

3. I can't post it, bu can describe it. Take the structure as generated by RAD6. Adapt Maven to that. Create a "project" pom in a project dir on the same level as all RAD6 projects.

My project root
&#124;
&#124;-EJB1 project
&#124;-EJB2 project
&#124;-WAR project
&#124;-JAR project
&#124;-EAR project
&#124;-Project project

The project project has all other projects as modules (by using relative paths). The EAR project has the various required EJBs, WARs and JARs as dependencies. Also the project project is declared as parent by all other projects.

Also note the documention on the EAR, EJB and WAR plugin pages.
http://maven.apache.org/plugins/maven-ear-plugin/
http://maven.apache.org/plugins/maven-ejb-plugin/
http://maven.apache.org/plugins/maven-war-plugin/

Don't forget the examples. Also a good reference is Beter Builds with Maven. It's a free download only a registration is required. It actually is a must read: http://www.mergere.com/m2book_download.jsp</description>
		<content:encoded><![CDATA[<p>Hello Andrew,</p>
<p>Check your mailbox. While I can&#8217;t send around actual project related material because of NDAs and stuff, I can send you some sterilized information.</p>
<p>Hope the info helps.</p>
<p>For the rest of the world, here is the meat from my reply to Andrew:<br />
&#8212;&#8211;</p>
<p>Your questions:<br />
1: Yes. Use mvn help:effective-pom It shows you all defaults. But the good thing is, you can modify all that. We&#8217;ve modified our EJB, WAR and EAR projects to match RAD6 directory structure. Maven adapts easily to that, while RAD6 is not able to do it the other way around.</p>
<p>2. No. I&#8217;ve taken the RAD6 structure as is. Everything on a single level in a directory tree. Modules and parents can be indicated with relative paths. We pick the right EJBs, WARs and JARs up by declaring them as a dependency. Check the various scope options for dependencies and understand them.</p>
<p>3. I can&#8217;t post it, bu can describe it. Take the structure as generated by RAD6. Adapt Maven to that. Create a &#8220;project&#8221; pom in a project dir on the same level as all RAD6 projects.</p>
<p>My project root<br />
|<br />
|-EJB1 project<br />
|-EJB2 project<br />
|-WAR project<br />
|-JAR project<br />
|-EAR project<br />
|-Project project</p>
<p>The project project has all other projects as modules (by using relative paths). The EAR project has the various required EJBs, WARs and JARs as dependencies. Also the project project is declared as parent by all other projects.</p>
<p>Also note the documention on the EAR, EJB and WAR plugin pages.<br />
<a href="http://maven.apache.org/plugins/maven-ear-plugin/" rel="nofollow">http://maven.apache.org/plugins/maven-ear-plugin/</a><br />
<a href="http://maven.apache.org/plugins/maven-ejb-plugin/" rel="nofollow">http://maven.apache.org/plugins/maven-ejb-plugin/</a><br />
<a href="http://maven.apache.org/plugins/maven-war-plugin/" rel="nofollow">http://maven.apache.org/plugins/maven-war-plugin/</a></p>
<p>Don&#8217;t forget the examples. Also a good reference is Beter Builds with Maven. It&#8217;s a free download only a registration is required. It actually is a must read: <a href="http://www.mergere.com/m2book_download.jsp" rel="nofollow">http://www.mergere.com/m2book_download.jsp</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Swan</title>
		<link>http://blog.leenarts.net/2007/02/11/maven-2s-ear-plugin-gives-me-a-headache/#comment-24880</link>
		<dc:creator>Andrew Swan</dc:creator>
		<pubDate>Mon, 21 May 2007 05:42:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.leenarts.net/2007/02/11/maven-2s-ear-plugin-gives-me-a-headache/#comment-24880</guid>
		<description>I'm trying to convert an old J2EE project to use M2's EAR plugin, and I have some questions for you please:
1. Does the EAR plugin expect a certain project directory structure? If so, is it documented somewhere?
2. The "archetype" plugin can generate the structure for a "simple" J2EE project. Did you use that to create your project's structure, or did you create yours manually?
3. Could you please post your project's structure and your POM? 

Thanks for any help,

Andrew (andrews [att] bisinfo [dott] com [dott] au)</description>
		<content:encoded><![CDATA[<p>I&#8217;m trying to convert an old J2EE project to use M2&#8217;s EAR plugin, and I have some questions for you please:<br />
1. Does the EAR plugin expect a certain project directory structure? If so, is it documented somewhere?<br />
2. The &#8220;archetype&#8221; plugin can generate the structure for a &#8220;simple&#8221; J2EE project. Did you use that to create your project&#8217;s structure, or did you create yours manually?<br />
3. Could you please post your project&#8217;s structure and your POM? </p>
<p>Thanks for any help,</p>
<p>Andrew (andrews [att] bisinfo [dott] com [dott] au)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jo Vandermeeren</title>
		<link>http://blog.leenarts.net/2007/02/11/maven-2s-ear-plugin-gives-me-a-headache/#comment-17091</link>
		<dc:creator>Jo Vandermeeren</dc:creator>
		<pubDate>Fri, 16 Mar 2007 13:30:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.leenarts.net/2007/02/11/maven-2s-ear-plugin-gives-me-a-headache/#comment-17091</guid>
		<description>thanks for the info.. quite enlightening..</description>
		<content:encoded><![CDATA[<p>thanks for the info.. quite enlightening..</p>
]]></content:encoded>
	</item>
</channel>
</rss>
