You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "David Yan (JIRA)" <ji...@apache.org> on 2016/02/23 23:57:18 UTC

[jira] [Resolved] (APEXCORE-4) Package all the declared dependencies with the app packages and nothing more

     [ https://issues.apache.org/jira/browse/APEXCORE-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Yan resolved APEXCORE-4.
------------------------------
    Resolution: Won't Fix

This would be fixed by our gradual move to baby packages in malhar.  

> Package all the declared dependencies with the app packages and nothing more
> ----------------------------------------------------------------------------
>
>                 Key: APEXCORE-4
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-4
>             Project: Apache Apex Core
>          Issue Type: Improvement
>            Reporter: Chetan Narsude
>            Assignee: David Yan
>
> Today by default we provide the exclusion * clause while declaring the dependencies. These are not taken well by our build tools and they spew warnings.
> At the same time we have provided scope for a few dependencies that defeats the purpose of using Maven in the first place.
> If we packaged the declared dependencies then we get the exact same behavior and do not have to use the provided scope at all.
> Let's take the discussion up for this in the Arch meeting.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)