users@glassfish.java.net

Re: Unit testing with Maven and javaee-api dependency

From: <glassfish_at_javadesktop.org>
Date: Mon, 13 Sep 2010 19:30:21 PDT

I think I found this on Google earlier today. I tried the following dependencies in this order:

<dependency>
    <groupId>com.sun.faces</groupId>
    <artifactId>mojarra-jsf-impl</artifactId>
    <version>2.0.0-b04</version>
    <scope>provided</scope>
</dependency>

<dependency>
    <groupId>javax</groupId>
    <artifactId>javaee-api</artifactId>
    <version>6.0</version>
    <scope>provided</scope>
</dependency>


I still get the error.

Another person suggested that I use the Geronimo dependencies instead of the javaee-api dependency. They seem to all be separate like the Sun provided ones for Java EE 5 APIs, so I didn't bother trying to figure out which I need just yet. I want to know why Sun decided to do the Java EE 6 API dependency in such a way. Do they assume that nobody does unit testing? Maybe I'm doing it wrong, and I should be using something like JSFUnit instead.


Thanks,
Ryan


> I'm collecting dependencies like this... a few of
> them I already have
> http://dominikdorn.com/2010/05/maven-junit-classformat
> error-absent-code-attribute/
>
> maybe that helps.
>
> kind regards,
> dominik
>
[Message sent by forum member 'rdelaplante']

http://forums.java.net/jive/thread.jspa?messageID=482579