You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Jérôme Leroux (JIRA)" <ji...@apache.org> on 2014/01/08 16:02:04 UTC

[jira] [Created] (EASYANT-60) Allow definition of path in ivy module files

Jérôme Leroux created EASYANT-60:
------------------------------------

             Summary: Allow definition of path in ivy module files
                 Key: EASYANT-60
                 URL: https://issues.apache.org/jira/browse/EASYANT-60
             Project: EasyAnt
          Issue Type: Wish
          Components: Core
    Affects Versions: 0.9
            Reporter: Jérôme Leroux
            Priority: Minor


Currently, in ea:build tags we can define properties with ea:property to customize the definition of the module to build.
It would be convenient to allow the definition of path with ea:path directly in these module files.

I don't know if this kind of feature respect the philosophy of EasyAnt. EasyAnt build system is strongly based on naming convention for the definition of the files to compile. Even if this is very convenient for most of the projects, this does not permit to compile a project with sources dispatched in several folder.

Currently, the solution is to write an Ant file above the module file to define the path. The definition of a path directly in the ivy module can address this kind of issues easi(ant)ly.

The implementation may not be as trivial as definition of properties. I know that the propagation of data types in Ant may be a little tricky.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)