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/11/24 16:39:13 UTC
[jira] [Updated] (EASYANT-70) Specified targets order not kept when
building multi-modules
[ https://issues.apache.org/jira/browse/EASYANT-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jérôme Leroux updated EASYANT-70:
---------------------------------
Attachment: 0001-easyant-Fix-issue-EASYANT-71.patch
Patch attached for project easyant.
Fix issue EASYANT-70:
* Fix SubModule task
* Add a test for SubModule task
> Specified targets order not kept when building multi-modules
> ------------------------------------------------------------
>
> Key: EASYANT-70
> URL: https://issues.apache.org/jira/browse/EASYANT-70
> Project: EasyAnt
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.9
> Reporter: Jérôme Leroux
> Attachments: 0001-easyant-Fix-issue-EASYANT-71.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> When buildng a multi-modules projects, the targets specified in the command line are not always executed in the right order.
> For example, with the following command:
> {{easyant clean publish-shared}}
> We get the following verbose:
> {quote}
> Executing [clean, publish-shared] on mySubModule
> ======================================================================
> Setting project property: project.executed.targets -> publish-shared,clean
> Setting ro project property: ant.project.invoked-targets -> publish-shared,clean
> Build sequence for target(s) `publish-shared', `clean' is
> {quote}
> The {{publish-shared}} target is executed before the {{clean}} target.
> The issue seems to come from the method {{org.apache.easyant.tasks.SubModule.filterTargets()}}. This method creates a set of targets (unordered) from a list of targets (ordered).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)