I posted a sample project on Jira and copied it to the appfuse group that had a similar structure and had the poms set up to build correctly. The structure was close to what you are proposing. I will see if i can dig it up and you can just modify it to your liking.
Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -----Original Message----- From: mraible [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 10:24 AM To: [email protected] Subject: Re: Converting AppFuse to a Maven 2 Project I started working on the Maven 2 conversion last night. I'm currently using Carlos's nested recommendation. Here's a screenshot of the current structure: http://raibledesigns.com/repository/images/appfuse2-structure.png Using this structure, I get errors stating that the "data" and "web" parent projects should have a packaging type of "pom". However, I want these projects to create their own JAR artifacts. Should these be moved into "common" projects instead of having them in the root of data and web? Thanks, Matt -- View this message in context: http://www.nabble.com/Converting-AppFuse-to-a-Maven-2-Project-tf1964609.html #a5729055 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- 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]
