Personally I prefer having a separat EAR project from which I reference the various EJB modules. This allows everything to be packed togehter very efficient.

Here is a snippet from the pom.xml file in the EAR project:

....
        <dependencies>
                <dependency>
                        <groupId>com.yourcompany.project.module</groupId>
                        <artifactId>componentxxxx-ejb</artifactId>
                        <version>${project.version}</version>
                        <type>ejb</type>
                </dependency>
                ... repeat at lib ....
        </dependencies>

This will cause my .ear to package all my EJB modules nicely together with all required dependencies etc.


On 1. nov. 2006, at 20.55, EJ Ciramella wrote:

I did - their example mentions building a j2ee project with a single
ejb, there's no mention of best practices in regards to multiple ejbs.

-----Original Message-----
From: Alexander Sack [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 01, 2006 2:41 PM
To: Maven Users List
Subject: Re: EJB Building

Look at the Better Builds with Maven 2 book:

http://www.mergere.com/m2book_download.jsp

This has a whole chapter dedicated to Java EE projects with examples
(downloadable from that website).

-aps

On 11/1/06, EJ Ciramella <[EMAIL PROTECTED]> wrote:

What I'm wondering is, if currently I have 6 lines of ant code that
(as
per the standard ejb task in ant) recursively finds all the deployment
descriptors and builds the ejbs into a specified directory.

These ejbs aren't stand alone projects either (as you mention below).

How does this work with maven 2?  Is there an example of building a
web
app project with many ejbs? Will this be one parent with dependencies
on 10 - 15 child projects?

-----Original Message-----
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 01, 2006 2:17 PM
To: Maven Users List
Subject: Re: EJB Building

I don't know what exactly you're looking for as a response here, EJ.
My organization has a variety of EJBs (and Libs, Wars, etc) all being
built by M2 with dependencies across modules etc.

Realistically you should just take a day or two and just convert 2 or
3 of your EJB projects to Maven2 to see how it works. The poms should
be pretty simple assuming you aren't doing anything terribly complex
in your Ant scripts.

Wayne

On 11/1/06, EJ Ciramella <[EMAIL PROTECTED]> wrote:
Is there some place where I can see how maven 2 expects to build
ejbs?

In an active project here, we have about 10 - 15 ejbs building via
ant.
Each ejb is in its own directory.

How would something like this work in Maven 2?



---------------------------------------------------------------------
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]




--
"What lies behind us and what lies in front of us is of little concern
to
what lies within us." -Ralph Waldo Emerson

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Steinar Cook
[EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to