maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Russell Gold <r...@gold-family.us>
Subject Re: Best Practice for testing code that uses provided dependencies
Date Sun, 27 Oct 2013 23:59:47 GMT
I’m actually running into the same issue, and my plan was s to take advantage of the situation
to provide test versions of the classes. What I found was that the “provided” dependency
wound up in the test class path.

So I think that the fact that it is provided should have no impact on how you test it.

- Russ

On Oct 27, 2013, at 7:22 PM, Ron Wheeler <rwheeler@artifact-software.com> wrote:

> We have code that depends on "provided" libraries.
> 
> What is the best way to test the code?
> 
> I don't particularly want to add the shared libraries to the project since they are large
and will add a big load into the SCM and make it hard to check out the project.
> 
> Can I add the dependency twice, once as provided and once as test?
> Any comments or suggestions?
> 
> Ron
> 
> -- 
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 

-----------------
Author, Getting Started with Apache Maven <http://www.packtpub.com/getting-started-with-apache-maven/video>

Come read my webnovel, Take a Lemon <http://www.takealemon.com>, 
and listen to the Misfile radio play <http://www.fuzzyfacetheater.com/misfile/>!








Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message