[
https://issues.apache.org/jira/browse/MSHADE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286356#comment-16286356
]
Robert Scholte commented on MSHADE-268:
---------------------------------------
If you're working on a library and want to shade, you probably want to relocate
as well. In that case downloading the sources won't be enough. Those sources
must be relocated as well. There's no option yet to shade attachments like
sources and javadoc.
If you're working on an apllication, I don't see the need for these sources.
Shading is done during packaging, so during development you can still use the
original sources.
> improving inclusion of open source code referenced by java projects.
> ---------------------------------------------------------------------
>
> Key: MSHADE-268
> URL: https://issues.apache.org/jira/browse/MSHADE-268
> Project: Maven Shade Plugin
> Issue Type: New Feature
> Reporter: Sunil Kumar Singh
>
> All the details are on git hub at:
> https://github.com/ksunilsingh/code-collector
> This is an idea on improving inclusion of open source code referenced by java
> projects. Currently when we use a java build system (such as maven or
> gradle), the build system downloads the jar files referenced by a java
> project. What I am proposing here is a replacement for that:
> Find out all the classes referenced by the classes in a java project (say,
> project A).
> Download the source code for these dependencies recursively and include the
> downloaded source code in the source tree of project A.
> Remove the dependency(ies) from project build configuration file (e.g.
> pom.xml) and build the project.
> The resulting jar file would be smaller in size than if the full jar for the
> dependency is included as is.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)