[jira] [Updated] (VELOCITY-970) velocity-engine-core contains commons-io Maven descriptor

"Claude Brisson (Jira)" <[email protected]>
Newsgroups gmane.comp.jakarta.velocity.devel
Message-ID <[email protected]>
     [ https://issues.apache.org/jira/browse/VELOCITY-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claude Brisson updated VELOCITY-970:
------------------------------------
    Fix Version/s:     (was: 2.4.1)
                       (was: 2.4.2)

> velocity-engine-core contains commons-io Maven descriptor
> ---------------------------------------------------------
>
>                 Key: VELOCITY-970
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-970
>             Project: Velocity
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: 2.3
>            Reporter: Thomas Mortagne
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 2.4
>
>
> commons-io is embedded in velocity-engine-core, which is OK from Java point of view since its package is renamed (not causing any dependency problems).
> The problem is that it contains the commons-io Maven descriptors at the standard location (/META-INF/maven/commons-io/commons-io/), which is a problem when you analyze JAR files to find what's in it because it ends up being identified as a JAR exposing commons-io (which is not the case since it's weaved).
> Honestly, it feels very strange to embed commons-io in the first place given that commons-lang for example is a transitive dependency, so I feel like the simplest would just be to remove all the plumbing to embed and weave commons-io and simply keep it as a regular transitive dependency.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.