You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2016/01/13 16:59:39 UTC

[jira] [Comment Edited] (YETUS-280) build systems should be able to predetermine module order

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

Allen Wittenauer edited comment on YETUS-280 at 1/13/16 3:58 PM:
-----------------------------------------------------------------

The problem here is that we have no way of really knowing whether maven is failing because dependency isn't installed OR the command line actually had a problem like a dependency loop or corrupted pom.xml.  I was thinking of the latter when I made this a -1 since I figured that would be more common.


was (Author: aw):
The problem here is that we have no way of really knowing whether maven is failing because dependency isn't installed OR the command line actually had a problem like a dependency loop or corrupted pom.xml.  I thinking of the latter when I made this a -1 since I figured that would be more common.

> build systems should be able to predetermine module order
> ---------------------------------------------------------
>
>                 Key: YETUS-280
>                 URL: https://issues.apache.org/jira/browse/YETUS-280
>             Project: Yetus
>          Issue Type: Improvement
>          Components: Test Patch
>    Affects Versions: 0.1.0
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>         Attachments: HBASE-15075.yetus.log, YETUS-280.00.patch, YETUS-280.01.patch, YETUS-280.02.patch
>
>
> It'd be useful for systems that have enough metadata to provide Yetus with hints on the order of the modules.



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