I got it to work with WTP, meaning you can run tests from Eclipse, "at some
point", I could not easily get it working again and gave up. I used
eclipse:eclipse goal from maven-eclipse-plugin to setup the projects, but then
you have to play around with classpaths manually, as well as prepare res
"doballve" wrote : I've placed it as attachment to Seam main page. Enjoy it:
http://wiki.jboss.org/wiki/attach?page=JBossSeam%2FBookingExample-2.0.1.GA-mavenized.zip
|
| I could not use hibernate-all-beta3 jar, tests fail with that.. using
expanded hibernate dependencies instead. Btw, depend
I've placed it as attachment to Seam main page. Enjoy it:
http://wiki.jboss.org/wiki/attach?page=JBossSeam%2FBookingExample-2.0.1.GA-mavenized.zip
I could not use hibernate-all-beta3 jar, tests fail with that.. using expanded
hibernate dependencies instead. Btw, dependencies can still be cleaned
Yes i vote for it also.
I'll soon have to start a new project on JBoss 4.2.X and so far i have been
reluctant to use Seam because it has to integrate fully to our build system
(maven + continuum). I really don't and won't have time to spend on figuring
out how to build with maven a fully functi
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
Cory, thanks for your effort and perseverance on this matter. I started from
Michael Yuan's example
(http://www.michaelyuan.com/blog/2007/10/09/jboss-seam-project-setup-with-maven-%e2%80%94-part-2-ear-deployment/),
added dependencies from Seam 2.0.1.GA but got stuck on the way.
Thanks to your i
We've come to similar conclusion (regarding source of the problem):
http://jira.jboss.com/jira/browse/JBSEAM-2371
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123950#4123950
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=repl
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.
(
Sure enough, when I tested this on Linux, it worked.
I think the classpath ordering, as shown in one of my posts above is a Maven
issue. However, Mac OS X isn't the only platform this does not work on. I
tried this on WinXP, JDK 1.5, Maven 2.0.8, and got this:
| WARN 07-01 11:32:35,838 (U
I'll find a Linux box to give this a whirl on.
Version of what from the 4th? If Maven 2.0.8, then yes. I would assume
everything else is being pulled from the Maven repositories, but I'll try with
a -U anyway.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=
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
Cory,
I checked out your updated example and the test fails for me.
| Running TestSuite
| [Parser] Running:
| Command line suite
|
| WARN 04-01 14:39:46,978 (UnifiedLoaderRepository3.java:addClassLoader:675)
-Tried to add non-URLClassLoader. Ignored
| ERROR 04-01 14:39:47,335
"[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
Yes, I don't like the -all.jar s particularly, however I don't see a nice way
around it (Seam's deps are different than those in the -all.jar)
However, this will all go away when we can target JBoss AS 5 with Seam (as this
is what Embedded is based on, and so we can sync jar versions easily). Th
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
|
Java6 can compile bytecode Java5 compatible, so I see no point in
discriminating Java6. There should be an option to force that - I do that in
Ant with
|
|
| ...
|
| ...
|
Anyway with tests skipped your project has been built ok
View the original post :
http://www.jboss.com/
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
everything compiled ok (1.6 is backwards compatible), i think you have mistake
in right parenthese:
is: [1.5,1.6)
probably should be:[1.5,1.6]
There seems to be problem with local repository. I think I need to create one,
but don't know how.
| Downloading:
http://repository.jboss.org/maven
http://in.relation.to/Bloggers/EmbeddedJBossUpdate tells you how to run
Embedded on Java 1.6
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=411#411
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=411
_
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
i've change
[1.5,1.6)
to
[1.5,1.6.0-3]
and it went ahead
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116659#4116659
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116659
___
I've tied to build your example but no luck:
| [INFO] [enforcer:enforce {execution: enforce-java}]
| [WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequireJavaVersion
failed with message:
| Detected JDK Version: 1.6.0-3 is not in the allowed range [1.5,1.6).
|
View the original pos
"[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
anonymous wrote : Would it require the new version of JBoss Embedded to be
released first?
Highly unlikely, there is nothing wrong with Seam or Embedded here, just the
way Maven sets up the classpath when running tests.
anonymous wrote : Hopefully those working on Seam and/or JBossEmbedded can
Very good idea! We need something which works. Unfortunatelly I can't help
because i'm not good with Maven
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116321#4116321
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=411
25 matches
Mail list logo
