You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "Vlad Rozov (JIRA)" <ji...@apache.org> on 2017/01/26 03:21:27 UTC

[jira] [Commented] (APEXCORE-620) Support Fat Jar without POM, allowing Gradle and other build systems

    [ https://issues.apache.org/jira/browse/APEXCORE-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839111#comment-15839111 ] 

Vlad Rozov commented on APEXCORE-620:
-------------------------------------

What is the proposed mechanism to resolve dependencies? Apex application developer should provide .apa file with all dependencies (except the one that will be provided at run-time) resolved.

> Support Fat Jar without POM, allowing Gradle and other build systems
> --------------------------------------------------------------------
>
>                 Key: APEXCORE-620
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-620
>             Project: Apache Apex Core
>          Issue Type: New Feature
>            Reporter: Jose Casillas
>
> For a project that is built with Gradle to be used in Apex, we must convert our suite of libraries to Maven or resort to:
> apex> launch -ignorepom -libjars x,y,z,...
> Can the launcher simply accept a jar and include all of the dependency jars within it, without requiring a POM or explicit declaration with -libjars?
> As a stop-gap, allowing -libjars to support a directory of dependencies would free us from specifying each one in the launch statement.
> The fat jar support would allow build systems other than Maven to power Apex applications.



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