[
https://jira.codehaus.org/browse/MCOMPILER-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MCOMPILER-113:
------------------------------------
Summary: Dependent classes end up in target/classes (was: Depenent classes
end up in target/classes)
> Dependent classes end up in target/classes
> ------------------------------------------
>
> Key: MCOMPILER-113
> URL: https://jira.codehaus.org/browse/MCOMPILER-113
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Affects Versions: 2.0.2
> Environment: Apache Maven 3.0-alpha-5 (r883378; 2009-11-23
> 10:53:41-0500)
> Java version: 1.6.0_17
> Java home: C:\java\jdk1.6.0_17\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows xp" version: "5.2" arch: "amd64" Family: "windows"
> Reporter: Ben Tatham
>
> Some extra classes from dependent jars end up in target/classes, and
> consequently the project artifact jar.
> Specifically, javax.servlet, from servlet-api:2.4 gets added. This is
> specified as a provided scope, but even if provided is removed, it still
> happens.
> Also reported by others on maven-users list:
> http://www.mail-archive.com/users@maven.apache.org/msg101503.html
> I also tried maven-compiler-plugin:2.1, and with maven 2.2.1. Same results.
> Adding excludes to maven-compiler-plugin does not stop it from happening (I
> assume because the classes are not being built by the compiler (b/c not in
> src/main/java), and so excludes does not apply to them.
> For now, I've excluded them from the artifact in the maven-jar-plugin:
> <excludes><exclude>javax\**</exclude></excludes>
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
