[
https://issues.apache.org/jira/browse/MNG-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848309#comment-15848309
]
Grzegorz Slowikowski commented on MNG-5567:
-------------------------------------------
I'm plugin developer, not user. Zip finding and processing logic is in my
plugin. I would have to change my plugin and instruct all plugin users to
upgrade and remove all zip dependencies from their project files or at least to
change scope to `provided`. All this just because Maven decides to break
backward compatibility.
I know that jars can contain sources, javadocs, etc. They were always added to
classpaths (and e.g. Maven GWT Plugin even requires jars with sources to be
added to dependencies because GWT will need then on the classpath) so all users
and developers know about it.
Zip format is very uncommon in Java world and some (including me) used it on
purpose to package non-classpath Maven dependencies.
My proposal is to not change current behavior. I don't see any really important
reason to do this. Backward compatibility is more important than compliance
with Java technical notes (after so many years of not being compliant) IMO.
> Zip files are not included in classpaths at all
> -----------------------------------------------
>
> Key: MNG-5567
> URL: https://issues.apache.org/jira/browse/MNG-5567
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.3.9
> Reporter: Pablo La Greca
> Assignee: Michael Osipov
> Priority: Critical
> Fix For: 3.5.1
>
>
> when i added a dependency that was zip file
> eg
> {code:xml} <dependency>
> <groupId>hsqldb</groupId>
> <artifactId>hsqldb</artifactId>
> <version>1.7.3.0</version>
> <scope>provided</scope>
> <type>zip</type>
> </dependency>
> {code}
> this file was not included in the test classpath and so the test would not
> pass
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
