I solved this problem with a bit of trickery using Ant within Maven.
The behaviour is correct to the EJB3 spec of scoping rules for persistence.xml.
I've submitted an issue with Surefire here which goes into more detail,
including the ant hack:
http://jira.codehaus.org/browse/SUREFIRE-443
Vie
Yes there is definitely a need for an example application on the Wiki,
uploading your example would be very helpful.
I haven't completed the test coverage I want in my example yet, all I have
proved is that Embedded JBoss works within Maven.
Now I need tests covering the Seam functionality for
I have continued to try and track down the issue and it turns out the problem
is with JBoss Embedded.
I've ruled out Maven being the problem by providing a command line that shows
how JBoss Embedded fails to load the persistence.xml file when multiple
_directories_ are given on the classpath.
(
Hmm... that's weird.
Maybe on MacOSX Maven isn't honoring the order of jars as specified in the POM?
I hate to say it but here on Linux it's working fine. I haven't tested this on
any other platform but have had it working without any changes on multiple
Linux environments, some of which start
ile should only be used in unit
tests and not included in any packaged artifacts.
The updated example can be downloaded from here:
http://www.users.on.net/~cory_prowse/seamMavenExample-20080104.zip
I'm going to post the example app to the Maven users mailing list and see if
anyone there knows w
"[EMAIL PROTECTED]" wrote : I don't know how to order the classpath with Maven
(it's easy with ant) but you need to make sure the -all jars come before
everything else when running tests.
Pete you are a legend (and not the Will Smith variety, I haven't seen that
movie yet).
Maven orders the cl
Yup you are correct, and I have enabled the option to create Java5 bytecode in
the parent pom.
| org.apache.maven.plugins
| maven-compiler-plugin
|
|
| 1.5
|
This is just a cut down version of a much larger project of which I use
Postgres with Glassfish for deployment testing (as Derby database doesn't work
with jBPM). So I deliberately force that check that Java 1.6 is not run,
meaning the right bracket is correct for a less than and not equal to c
I don't believe Embedded JBoss supports Java6?
Also Postgres JDBC doesn't support Java6 so I have that enforcement in place
for both of these reasons (the 1st one should apply to everyone)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116664#4116664
Reply t
"[EMAIL PROTECTED]" wrote : there is nothing wrong with Seam or Embedded here,
just the way Maven sets up the classpath when running tests.
Aha!
The problem then appears to be with the thirdparty-all-beta*.jar file as it
contains a separate copy of javassist.
Adding an exclusion for javassist
recently published beta3-SNAPSHOT of
Embedded JBoss.
It also will enforce using Java5 and Maven 2.0.8+ to ensure the environment is
supported correctly.
The archive can be obtained from here:
http://www.users.on.net/~cory_prowse/seamMavenExample-20080102.zip
Would love to get some help in
Apologies, the post got submitted by accident before I had completed it.
I have a complete example of using Seam2 with Maven, however I first need to
locate a place to upload the archive to and I'll post a new topic with a link
to it, and notes on how to use it.
View the original post :
http:/
I've been trying to get Seam2 building and testing within Maven 2.
I whipped up the attached
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116293#4116293
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116293
_
13 matches
Mail list logo