search

nikgoodley-ibboost / jstd-maven-plugin

Automatically exported from code.google.com/p/jstd-maven-plugin
0 stars 0 forks source link

pom for no deps js-test-driver #5

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Would it be possible to create a POM for a 1.2.2 release (non-Snapahot) that 
depends on the no-deps js-test-driver?

Original issue reported on code.google.com by brian.ch...@gmail.com on 29 Nov 2010 at 10:55

GoogleCodeExporter commented 9 years ago 
Catching up in time the published 1.3.2 JAR contains many popular dependencies: 

http://jstd-maven-plugin.googlecode.com/svn/maven2/com/google/jstestdriver/jstes
tdriver/1.3.2/jstestdriver-1.3.2.jar 

Examples include javax.servlet, Jetty, Joda Time, SLF4J, Apache ORO, etc.  By 
quietly introducing these dependencies into the classpath hard to track down 
issues can arise from version conflicts and such:

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in 
[jar:file:/Users/ibrandt/.m2/repository/org/slf4j/slf4j-log4j12/1.6.1/slf4j-log4
j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 
[jar:file:/Users/ibrandt/.m2/repository/com/google/jstestdriver/jstestdriver/1.3
.2/jstestdriver-1.3.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

With a no-deps JAR and a POM that declares the immediate dependencies these 
issues can be managed with the standard Maven dependency management, scoping 
and exclusion facilities.

Original comment by i...@ianbrandt.com on 9 Jan 2012 at 11:24

GoogleCodeExporter commented 9 years ago 
+1 for this issue.  In projects that contain both Java and JS source, having 
all of the transitive dependencies for the no-deps js-test-driver.jar declared 
in a POM would make  it much easier to find and resolve conflicts.

Original comment by tgjone...@gmail.com on 4 Jan 2013 at 12:14