[
https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265803#comment-16265803
]
Hudson commented on MRESOLVER-28:
---------------------------------
SUCCESS: Integrated in Jenkins build maven-resolver #65 (See
[https://builds.apache.org/job/maven-resolver/65/])
[MRESOLVER-28] reworked dependency graph (hboutemy:
[http://git-wip-us.apache.org/repos/asf/?p=maven-resolver.git&a=commit&h=93664e04dbbcda833a402e671cc6b70087658a72])
* (edit) maven-resolver-demos/pom.xml
* (edit) src/site/xdoc/maven-resolver-deps.odg
* (edit) src/site/site.xml
* (edit) src/site/xdoc/index.xml
* (edit) src/site/resources/images/maven-resolver-deps.png
> Move demos into master as new module
> ------------------------------------
>
> Key: MRESOLVER-28
> URL: https://issues.apache.org/jira/browse/MRESOLVER-28
> Project: Maven Resolver
> Issue Type: Task
> Components: demo
> Reporter: Manfred Moser
> Assignee: Manfred Moser
>
> The demos of Maven Resolver are currently in a separate demos branch. This
> makes it hard to keep version consistent and is also harder to understand and
> locate for users in apache git and on github.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)