Yes, its a perfect use case for classifier. I just wish they'd use it...
As Marco already pointed out, the Geronimo dependencies are much more
useful than the API-only j2ee.jar file. I use them in all my J2EE
projects.
Wayne
On 1/24/08, Simon Kitching <[EMAIL PROTECTED]> wrote:
> Stephen Co
Stephen Connolly <[EMAIL PROTECTED]> schrieb:
> Don't use the borked j2ee.jar from the java.net or java.net2 maven
> repositories.
>
> I had the same problem. Basically, the j2ee.jar on the java.net repos is
> not a real jar, just stripped classes that have no method bodies, but just
> the m
Hello,
For my j2ee-components I use the jars provided by geronimo for building
To solve you problem you could switch to the following:
org.apache.geronimo.javamail
geronimo-javamail_1.4_mail
1.3
This will add a jar containing the
javax.mail.internet.AddressException.c
By the way, the individual component jars that go to make up j2ee.jar are
fine, so all you need to do is figure out which parts of the j2ee spec you
need and include the relevant artifact, i.e. mail, servlet, ejb, etc
On Jan 24, 2008 8:59 AM, Stephen Connolly <[EMAIL PROTECTED]>
wrote:
> Don't us
Don't use the borked j2ee.jar from the java.net or java.net2 maven
repositories.
I had the same problem. Basically, the j2ee.jar on the java.net repos is
not a real jar, just stripped classes that have no method bodies, but just
the method definitions.
The borked jar is only good for compiling.
Wayne,
Thanks for the solutions you've provided. I went with the 2nd choice and
got my JUnit tests to build and execute. Thanks again, very much
appreciate the help.
Enrique
"Wayne Fay" <[EMAIL PROTECTED]> wrote on 04/18/2007 11:22:41 AM:
> I figured as much. Here's your problem...
>
> You
I figured as much. Here's your problem...
Your junit artifact is brought in with scope test.
Your test is currently situated in src/main/java which is "main java
code" directory. So when maven-compiler is trying to compile your
code, the junit dependency is not available.
You have two choices:
Arik,
Thanks for the tip. I got a bit further and it actually tries to build
AssetManagerTest.java files, but its failing saying it can't find
junit.framework. junit is located in ~/.m2/repository/junit/junit/3.8.1
directory. I have the import junit.framework.* in my code, so not sure
why it c
What is the file named? And where is it located with respect to your
pom.xml (the complete relative path)?
Wayne
On 4/18/07, Enrique Gaona <[EMAIL PROTECTED]> wrote:
Hi,
I'm trying to run a JUnit test in Maven, but for some reason, the tests are
being skipped. In my pom.xml file, I have the j
try:
**/AssetManagerTest.java
On 4/18/07, Enrique Gaona <[EMAIL PROTECTED]> wrote:
Hi,
I'm trying to run a JUnit test in Maven, but for some reason, the tests
are
being skipped. In my pom.xml file, I have the junit dependency and added
the maven-surefire-plugin in the hopes my JUnit test get
you should set the ignore property to 'true' so that the failure
doesn't halt the build, then look at 'maven.test.failure' to see if
they failed or not.
- Brett
On 5/11/05, Bahaa Nasrallah <[EMAIL PROTECTED]> wrote:
> Hi,
> I need to know if after running the unit tests is there any variable
> th
Eric Pugh wrote:
I've had this challenge as well. It seems wrong to have unit tests away
from the unit. However, really you could think of those tests are
"functional" or "Technology Compatiblity Kit" type of tests.
I do agree with you that testing with dbUnit crosses the line between
real
I've had this challenge as well. It seems wrong to have unit tests away
from the unit. However, really you could think of those tests are
"functional" or "Technology Compatiblity Kit" type of tests.
The DAO tests are focused (I'm guessing) mainly on verifing that the
DAO's for multiple impleme
SomeTest.class.getResourceAsStream (or
getClass().getResourceAsStream()) would work just as effectively. This
is how I would do it whether I was using Maven or not.
This is not a "weird thing" - Maven doesn't shove everything onto the
system classloader, it builds up its own.
- Brett
On Fri, 18
In case anyone is following this thread or finds it while solving their own problem in
the future,
here is what I ended up having to do:
InputStream is =
Thread.currentThread().getContextClassLoader()
.getResourceAsStream(testResource);
Apparentl
Yes, the call simply returns null. It really doesn't make much sense. When I run
maven with the
-X option I can see the path being included, but when I try to access the resource, I
get null.
WM
--- Dion Gillard <[EMAIL PROTECTED]> wrote:
> The resources aren't on the system classloader?
>
>
The resources aren't on the system classloader?
On Thu, 17 Jun 2004 12:39:04 -0700 (PDT), Webb Morris
<[EMAIL PROTECTED]> wrote:
>
> I have set up some resources for my unit tests in the unittest/resources area of my
> project.xml.
> These resources are being correctly copied to the target/test-
jdom
> b8
>
>
>
>
> junit
> 3.8.1
>
>
>
>
> src
> test
>
>
> **/*Test.java
>
>
>
>
>
>maven-statcvs-plugin
>maven-jdepend-pl
3 12:39 PM
To: Maven Users List
Cc:
Subject: RE: JUnit Tests
Andy was right about the tags not being there. Thanks for your
help. Now the unit tests run, but I can't get JCoverage or Clover to run? I ran it
twice, once with the Clover repor
not being set at execution
time? Or perhaps they are not in the classpath.
Try running maven with "-X" and check the output.
> -Original Message-
> From: Arthur I. Walker [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 26, 2003 10:59 AM
> To: Maven Users Lis
On Friday 26 Sep 2003 18:59, Arthur I. Walker wrote:
> My Maven build works then it doesn't .
>
> I converted my build over from beta 7 to beta 10, and everything was
> working. However, after logging off, and then logging back on to the
> build machine, the build stops working (after no changes).
My Maven build works then it doesn't .
I converted my build over from beta 7 to beta 10, and everything was
working. However, after logging off, and then logging back on to the
build machine, the build stops working (after no changes). Maven keeps
complaining about the javax.xml.parsers.SAXParse
ction
Total time: 47 seconds
-Original Message-
From: Andy Jefferson [mailto:[EMAIL PROTECTED]
Sent: Thu 9/25/2003 2:07 PM
To: Maven Users List
Cc:
Subject: Re: JUnit Tests
On Thursday 25 Sep 2003 19:34, Askren, Jay wrote:
> I am running Maven beta 10 and I cant seem to get the J-Uni
On Thursday 25 Sep 2003 19:34, Askren, Jay wrote:
> I am running Maven beta 10 and I cant seem to get the J-Unit tests plugin
> to work to work. Im running Maven on Windows XP with Java 1.41_02-b06.
> Here is the output from Maven before it dies:
> BUILD FAILED
> File.. file:/C:/Documents a
24 matches
Mail list logo
