o that? If so, how?
Thanks,
Laird
--
View this message in context:
http://www.nabble.com/Exclude-dependency-from-scope-runtime-test-classpath-tp23424431p23878578.html
Sent from the Maven - Users mailing list archive at Nabble.com.
--
put it another way, I want to ensure that
>> although I reference EclipseLink annotations in my project, I don't need
>> EclipseLink on the runtime/test path. I have no way of doing this that I
>> know of ins
although I reference EclipseLink annotations in my project, I don't need
> EclipseLink on the runtime/test path. I have no way of doing this that I
> know of inside my Maven project.
>
> Thoughts?
>
> Thanks,
> Laird
> --
> View this message in context:
> http:
Laird
--
View this message in context:
http://www.nabble.com/Exclude-dependency-from-scope-runtime-test-classpath-tp23424431p23875222.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: use
To: users@maven.apache.org
Subject: Exclude dependency from scope runtime test classpath
Hi,
I was wondering if there is a way to remove a dependency from the test
classpath when using runtime
I want to make sure that the jar file is only used when running the
application and not when testing it.
So it re
dependency from scope runtime test classpath
Hi,
I was wondering if there is a way to remove a dependency from the test
classpath when using runtime
I want to make sure that the jar file is only used when running the
application and not when testing it.
So it really comes down to, I want to have
As explained in the documentation, provided is "much like compile", and
"[...] available on the compilation and test classpath.
Cheers.
2009/5/7 Fabien Kruba
> Hi.
>
> did you tried "provided" scope instead?
>
> Hi,
>>
>> I was wondering if
27;re likely to want to test this kind of
dependency too in your tests. At least, IMO you'll have to provide a good
use case to justify this new feature.
Cheers.
2009/5/7 Henrik
> Hi,
>
> I was wondering if there is a way to remove a dependency from the test
> classpath when usi
Hi.
did you tried "provided" scope instead?
Hi,
I was wondering if there is a way to remove a dependency from the test
classpath when using runtime
I want to make sure that the jar file is only used when running the
application and not when testing it.
So it really comes down to,
Hi,
I was wondering if there is a way to remove a dependency from the test
classpath when using runtime
I want to make sure that the jar file is only used when running the
application and not when testing it.
So it really comes down to, I want to have the dependency (jar file) but
i don
problem is still remaining in surefire-2.4.3, see my last posting.
- torsten
Jörg Schaible <[EMAIL PROTECTED]>
17.07.2008 11:47
Bitte antworten an
"Maven Users List"
An
"Maven Users List"
Kopie
Thema
RE: own classes and test-classes at the end of test class
[EMAIL PROTECTED] wrote:
> Hi,
>
> if I´m running JUnit Tests with Surefire-2.4 I got the following
Use latest surefire plugin.
- Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTE
SurefirePlugin#constructSurefireBooter changes the classpath by doing:
...
getLog().debug( "Test Classpath :" );
// Check if we need to add configured classes/test classes
directories here.
// If they are configured, we should remove the default to avoid
] org.codehaus.plexus:plexus-utils:jar:1.4.9
[DEBUG] org.apache.maven.surefire:surefire-junit4:jar:2.4:test (selected
for test)
[DEBUG] junit:junit:jar:4.0:test (selected for test)
[DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4:test (selected
for test)
[DEBUG] Adding to surefire test classpath:
s
s prints
>> /workspace/checkout/weather/trunk/jetjwis/jbi/jmbl-xslt/target/classes/
>>
>> To me this is a critical bug that would almost certainly cause every
>> projects unit tests that access test resources to fail.
>>
>>
>>
>
>
--
View
weather/trunk/jetjwis/jbi/jmbl-xslt/target/test-classes/
>
> On 2.0.8 and 2.0.9 this prints
> /workspace/checkout/weather/trunk/jetjwis/jbi/jmbl-xslt/target/classes/
>
> To me this is a critical bug that would almost certainly cause every
> projects unit tests that access test
jlo_gestalt wrote:
When trying to access test resources in my unit tests, maven 2.0.8 and above
are returning the wrong directory.
Here is my basic code to access the folder
def file = new JmblXsltDriverTest().getClass().getResource("/")?.file
println file
On 2.0.7 this would print
/workspace
is message in context:
http://www.nabble.com/Test-classpath-issue-with-v2.0.8-and-v2.0.9-tp17276386p17276386.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Hi Petr,
I have a default.persistence.properties in the artifact with the EJB3
abstract test case. There I can specify whatever I like. Also, in the
jboss in deploy/ejb3.deployer/META-INF there is another
persistence.properties where I specify the production properties.
Stefan
Petr Nejedly
Thanks Stefan,
Very helpful. Just a question:
You said you're using only one persistence.xml for both, testing and
live deployment. How do you specify different Hibernate properties for
those, eg dialect (Oracle vs HSQLDB), auto create schema (on vs off),
etc?
Cheers, Petr
The inform
Hi Petr,
is seems to me that you're trying to work around maven mechanisms, which
is usually not a good idea. In this case, although I haven't completely
understood what you are trying to do, I can share some experience about
EJB3 and Testing.
I have one artifact P where the JBoss embedded con
Hi guys,
I'm trying to solve this issue for a few days and haven't been able to
crack it so far. The scenario is following:
I have a parent project that includes sub-modules, each having their own
pom.xml. Each of these modules produces an ejb3 package. I want to be
able to run unit/integra
Under Maven v2.0.6, with Surefire plugin v2.3, the directory containing
the .class files generated by the test-compile phase
(${basedir}/target/test-classes/) is not included in java.class.path
when I run "mvn test". (I got this info from the
target/surefire-reports/TEST-.xml file for a failing te
With sthe system scope it is possible to specify a jar in the dependencies. I
try to write a plugin that adds all the jars contains in a directory to the
test classpath. (I can not add jars in the pom dependencies because those
jars are installed by another plugin).
How can I add dependencies to
On 27/11/06, rking999 <[EMAIL PROTECTED]> wrote:
Thank you for the reply. I tried changing the scope to provided for the
resin jar, but it still seems to be used in the test classpath. What would
be nice is if I could actually remove it completelt from the test classpath
- is there a way
Hi,
Thank you for the reply. I tried changing the scope to provided for the
resin jar, but it still seems to be used in the test classpath. What would
be nice is if I could actually remove it completelt from the test classpath
- is there a way to do this with Maven?
thanks
--
View this
serAPIs jar.
>
> I cant exclude the resin jar as it is needed to compile the java source.
> There doesnt seem to be a way to change the order of the test classpath to
> move the xmlParserApis jar above the resin one
>
> Any help would be greatly appreciated. thanks in a
it is needed to compile the java source.
There doesnt seem to be a way to change the order of the test classpath to
move the xmlParserApis jar above the resin one
Any help would be greatly appreciated. thanks in advance.
--
View this message in context:
http://www.nabble.com/Test
; My problem is that I don't have the jar available in advance to add it to
>> the
>> maven's dependency section with scopt test.
>>
>> The jar is generated as part of a maven lifecycle prior to test
>> ()generate-sources. I need the ability to add a a di
I can't have a look at this now.
Can you open an issue on Jira please ?
http://jira.codehaus.org/browse/MPTEST
thanks.
Arnaud
On 9/7/06, David G. Paschich <[EMAIL PROTECTED]> wrote:
Quick summary: It appears that the Maven test module in Maven 1.1 beta 3
is
adding, among other things, log4j
Quick summary: It appears that the Maven test module in Maven 1.1 beta 3 is
adding, among other things, log4j and Xerces to my classpath before running
unit tests. Can I get it to stop? I tried setting
maven.test.excludeXmlApis to "yes" but that had no effect.
Why do I want to do this?
I do mo
On 19/07/06, Marc L. Veary <[EMAIL PROTECTED]> wrote:
Hi All,
In Eclipse the order in which libs are placed onto the classpath can be
controlled. This is useful when you need to stub a particular class within
a library: you can load the original and then load the stubbed class so that
your stub
Hi All,
In Eclipse the order in which libs are placed onto the classpath can be
controlled. This is useful when you need to stub a particular class within
a library: you can load the original and then load the stubbed class so that
your stubbed class get called in place of the original (but leavi
Hi All,
In Eclipse the order in which libs placed onto the classpath. This is
useful when you need to stub a particular class within a library: you can
load the original and then load the stubbed class so that your stubbed class
get called in place of the original (but leaving the rest of the ori
e.com/-m2-How+to+get+files+into+test+classpath--t987507.html#a4635367
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
hamdard wrote:
My problem is that I don't have the jar available in advance to add it to the
maven's dependency section with scopt test.
The jar is generated as part of a maven lifecycle prior to test
()generate-sources. I need the ability to add a a directory to the test
classp
My problem is that I don't have the jar available in advance to add it to the
maven's dependency section with scopt test.
The jar is generated as part of a maven lifecycle prior to test
()generate-sources. I need the ability to add a a directory to the test
classpath with a filter
Hi,
since surefire 2.2 in forking lifecycle isn't used.
It appears not in the Test classpath.
Is it a bug, or do I miss something?
Best regards
Andreas
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-surefire-plugin:2.2:test' -->
[DEBUG] (f) basedir = c:\dev
esn't work when I try.
Thanks
--
View this message in context:
http://www.nabble.com/-m2-How+to+get+files+into+test+classpath--t987507.html#a4512885
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-m
Hi
I have a similar issue where I want to add a jar to the test classpath,
before running the tests.
The jar is generated dynamically (at runtime), so I can't make a static
declaration in the pom.
I need to do something like:
Kaare
I have a similar issue where I want to add a jar to the test classpath,
before running the tests.
The jar is generated dynamically (at runtime), so I can't make a static
declaration in the pom.
I need to do something like:
I have an archetype with a dependency on a plugin to generate jar file(s)
(generated in /lib)
The unit tests within this archetype need to access the jar(s), so how can
I configure the maven test classpath to include the jar(s) when I run 'mvn
test'
Thanks,
John
This communicat
Lovely, thanks!
/B-E
-Ursprungligt meddelande-
Från: Kaare Nilsen [mailto:[EMAIL PROTECTED]
Skickat: den 24 januari 2006 15:56
Till: Maven Users List
Ämne: Re: [m2]How to get files into test classpath?
You could do like this in your pom
AIL PROTECTED]> wrote:
> Hi
>
>
>
> I want to add the path /accesscontro/srcl/WEB-INF/*.xml to the test
> classpath.
>
> There I have a sping configuration file.
>
> How do I do it?
>
>
>
> Regards,
>
>
>
> /B-E
>
>
>
>
>
> =
Hi
I want to add the path /accesscontro/srcl/WEB-INF/*.xml to the test
classpath.
There I have a sping configuration file.
How do I do it?
Regards,
/B-E
==
Bengt-Erik Fröberg, Databasadministratör
Institutionen för Epidemiologi och
Hello,
I'm new to maven and Java 5 and I just started a project using Maven
2. So far everything has been great except for the following issue.
I'm currently having a problem getting a particular unit test to run
successfully. I'm using java 1.5.0_04 and was trying to validate some
XML against
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 2, 2005, at 18:03, Mark D. Hansen wrote:
I'm using XmlBeans to generated some Java/XML binding classes that get
used in my junit tests. The way XmlBeans works, these classes end up
in a jar named "xmltypes.jar".
The trick, at least for me, is
I'm using XmlBeans to generated some Java/XML binding classes that get used in
my junit tests. The way XmlBeans works, these classes end up in a jar named
"xmltypes.jar".
I can list xmltypes.jar as a dependency because it doesn't exist at the time
that I invoke "maven test". So, how do I get
Is there any possibility to use jars in the unit test classpath that
won't be repeated in the application classpath ?
Reading the user guide indicates resources can be specific to unit
tests, but what about jar dependencies ?
Tanks in advance for any help.
You are right, AFAIK, IUTest never went anywhere...
Eric Pugh
-Original Message-
From: Sonnek, Ryan [mailto:[EMAIL PROTECTED]
Sent: Monday, June 02, 2003 11:56 AM
To: 'Maven Users List'
Subject: RE: Cactus Test Classpath Problems
I had the same question a couple days ago.
I had the same question a couple days ago. It doesn't seem that the iutest
is used by anything. Am I wrong?
-Original Message-
From: Mark McBride [mailto:[EMAIL PROTECTED]
Sent: Monday, June 02, 2003 10:50 AM
To: Maven Users List
Subject: RE: Cactus Test Classpath Problems
I th
I thought the cactus test belonged in /src/iutest as stated in
http://maven.apache.org/reference/dirlayout.html . If they don't belong
there is the /src/iutest directory used for anything else?
Thanks!
-Mark
At 05:09 PM 6/2/2003 +0200, you wrote:
err?
Your cactus tests should be in /src/test-
> -Original Message-
> From: brian janaszek [mailto:[EMAIL PROTECTED]
> Sent: 02 June 2003 16:38
> To: [EMAIL PROTECTED]
> Subject: Cactus Test Classpath Problems
>
> Hi
>
> I'm not sure if I'm simply missing something in the docs regarding
>
Hi
I'm not sure if I'm simply missing something in the docs regarding
Cactus and the Maven unit testing goals, but I'm having an issue with
the classpath when Maven tries to compile my tests.
My tests reside in the /WEB-INF/src/test directory generated by Maven,
and the tests import other classes
54 matches
Mail list logo