On Nov 16, 2006, at 7:43 PM, Mohammad Nour El-Din wrote:
Hi David...
The problem still exists and other errors appeared, take a look at
build
log, the beginnings of errors places are marked
http://rifers.org/paste/show/2351
That highlighting is really cool... how did you do that?
Anyway, it looks like a second failure on top of the first. This one
looks like it might be another license header issue.
05:34:49,050 FATAL [startup] OpenEJB has encountered a fatal error
and cannot be started: Assembler failed to initialize.
org.apache.openejb.OpenEJBException: Cannot parse the XML of the
openejb.xml file. Received message: Parsing Error : Content is not
allowed in prolog.
If you want to poke at that one that'd be great. I'll take a look at
this one below tomorrow:
org.exolab.castor.mapping.MappingException: A mapping for class
org.apache.openejb.test.entity.cmp.BasicCmpBean already exists
I know I fixed it, but maybe my fix isn't windows friendly.
Thanks,
David
On 11/16/06, David Blevins <[EMAIL PROTECTED]> wrote:
On Nov 15, 2006, at 3:19 PM, Mohammad Nour El-Din wrote:
> Hi all...
>
> Does anyone know about this, I just want to make sure that this
is new
> before I dig into it, here is the build log, the places of
errors are
> highlighted
> http://rifers.org/paste/show/2326
>
I fixed this a day or two ago when I ran into it. Try updating and
see if it goes away.
Seems eariler in the week maven deployed some new stuff and now
certain jars are in the classpath twice. For us this means our tests
see two sets of beans and tries to deploy them twice, hence the
"Duplicate bean" error.
-David
>
> --
> Thanks
> - Mohammad Nour
--
Thanks
- Mohammad Nour
