[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jetty-users] Classes scanned from multiple locations with Maven plugin (mvn install & mvn jetty:start)
|
Hi.
I don't understand why this thread has been left unanswered.
From the tests I made, it's enough to add:
<webAppSourceDirectory>${project.build.directory}/${project.build.finalName}</webAppSourceDirectory>
to the jetty-maven-plugin for jetty to load the jars both from
the local maven repository AND the WEB-INF/lib directory, and to
trigger the multiple locations warning for each and every class of
the webapp.
I really don't know how to circumvent this problem.
On 19-07-18 17 h 08, James Srinivasan
wrote:
I think that would be appropriate if the clash was
inside my war, but the clash is with classes inside my war and
in my .m2 and target/classes directories. So this shouldn't
happen on deployment, but does during dev/test.
Hi James,
Just a quick suggestion, can you use the Shade plugin
to use only one version of the classes?
Best Regards,
Zalan Meggyesi
Chief Support Engineer
Skawa Innovation Kft.
![]()
I'm trying to use
jetty-maven-plugin to run some integration tests
with failsafe, but getting lots of warnings similar to
the following
with mvn install, or mvn jetty:start (but *not* with mvn
jetty:run):
[WARNING] my.package.api.LinksApi scanned from multiple
locations:
file:///path/to/my/project/my-project-1.0-SNAPSHOT/WEB-INF/classes/my/package/api/LinksApi.class,
file:///path/to/my/project/my-project/target/classes/my/package/api/LinksApi.class
and
[WARNING] com.sun.xml.fastinfoset.AbstractResourceBundle
scanned from
multiple locations:
jar:file:///path/to/my/homedir/.m2/repository/com/sun/xml/fastinfoset/FastInfoset/1.2.16/FastInfoset-1.2.16.jar!/com/sun/xml/fastinfoset/AbstractResourceBundle.class,
jar:file:///C:/path/to/my/project/target/my-project-1.0-SNAPSHOT/WEB-INF/lib/FastInfoset-1.2.16.jar!/com/sun/xml/fastinfoset/AbstractResourceBundle.class
I've tried to solve this with:
<artifactId>maven-failsafe-plugin</artifactId>
<version>2.6</version>
<configuration>
<useManifestOnlyJar>false</useManifestOnlyJar>
<useSystemClassLoader>false</useSystemClassLoader>
</configuration>
[...]
and scanClassesPattern, scanTestClassesPattern,
scanTargetPatterns in
jetty-maven-plugin
and adding javax.servlet as `provided` to my
dependencies
But none of this has helped. Given the jars should all
have the same
version, it doesn't appear critical but any help would
be much
appreciated. I don't see why my local maven repo is on
my servlet's
classpath.
My full pom.xml is here:
https://gist.github.com/jrs53/dc9c14e383e814c5e2b95e439152f83e
Thanks in advance,
James
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users