I've got a multiproject-based Maven setup. Currently, there's only one EJB
(more coming after I get all the build kinks like this one ironed out), and
that gets built into an EAR.
/
+-root/
+-project.xml
+-project.properties
+-maven.xml
+-EJB/
+-project.xml
+-project.properties
+-maven.xml
+-src/
+-java/
+-mycp/
+-MyBean.java
+-EAR/
+-project.xml
+-project.properties
+-maven.xml
+-src/
+-test-cactus/
+-mycp/
+-test/
+-MyBeanTest.java
I may be misunderstanding how/where to put and run the cactus tests... my
first inclination was to put it in the EJB folder next to the Bean
implementation. However, that project's goal is a .jar file (with the EJB), so
I can't build an EAR there also. But when I run "maven cactus:test-ear" in the
EAR/ directory, or "maven multiproject:site" in the / directory (which runs
the cactus:test-ear goal in the EAR/ directory), javac is unable to find the
EJB's jar file, even though I have it configured as a dependency in EAR/
project.xml.
I've got a preGoal on cactus:compile that echos a bunch of classpaths, which
are all empty: ${cactus.classpath}, ${maven.classpath},
${maven.ear.classpath}, ${maven.war.classpath}, ${classpath},
${maven.dependency.classpath}
Is there a way I can explicitly add the EJB's jar file (which is in the local
repository), or is there a way to get cactus to create a correct EAR file for
testing as a goal of the EJB project and still have the "normal" goal create
the standard EJB jar file?
Thanks!
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
