On 11/10/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote:
> hi,
>
>   i apologize for the subject. :D
>
>   just to organize our project structure we are putting all EJB
> projects in a child-directory named EJB. then i put this in the parent
> POM
>
>   <modules>
>      <module>mod1</module>
>      <module>mod2</module>
>
>      <module>EJB/ejb1</module>
>      <module>EJB/ejb2</module>
>   </modules>
>
>
>  the problem is that only the last EJB module is being built. in my
> example above only ejb2 is going to be built. if i switch the
> positions of the two then only ejb1 will be built. i tried putting the
> EJB projects in between the mod1 and mod2 declaration and still only
> the last EJB project gets built but mod2 will be built just fine.
>
>  in reality, all EJB projects are empty. they are just popoulated by
> the mod1 project (via an ant script) because every other ejb project
> has the same classes but different manifest values.
>
>  is this a bug or an intended feature?
>
>  i also tried making the EJB a "pom" project and declaring it as a
> module in the parent project. the EJB project will then declare the
> ejbX projects as its module. i was hoping that the maven goal
> invocations  will cascade but it didn't. that is why i did it as
> stated above.
>
>  thanks.
>
> ciao!
>

here are a few more updates:

  - i tried putting the EJB projects on the same level as the other
nodes. no effect.
  - i tried changing the EJB projects' packaging type from "ejb" to
"jar". no effect.
  - only the last EJB project is being recognized by the reactor when
it scans for the build order.

each of the EJB projects have a similar pom as this
==========
  <groupId>my.app.ejb</groupId>
  <artifactId>BFFWorkerProxy</artifactId>
  <packaging>ejb</packaging>
  <version>1.0</version>
  <name>BWorkerProxy EJB</name>
  <parent>
    <groupId>my.app</groupId>
    <artifactId>Maintenance</artifactId>
    <version>1.0</version>
  </parent>

   <build>
      <finalName>BWorkerProxySL</finalName>
      <plugins>
         <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-ejb-plugin</artifactId>
            <configuration>
               <generateClient>true</generateClient>
            </configuration>
         </plugin>
      </plugins>
   </build>
==========

   if nobody can answer this by end of day then i will log a JIRA
ticket for this. i am hoping this is just some stupidity on part. :)
thanks.

ciao!

--

"Programming, an artform that fights back"

Anuerin G. Diaz
Registered Linux User #246176
Friendly Linux Board @ http://mandrivausers.org/index.php
http://capsule.ramfree17.org , when you absolutely have nothing else
better to do

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

Reply via email to