edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christofer Dutz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (EDGENT-413) Simplify download experience
Date Sat, 03 Jun 2017 15:03:04 GMT

    [ https://issues.apache.org/jira/browse/EDGENT-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035989#comment-16035989

Christofer Dutz commented on EDGENT-413:

Well I guess the Maven migration I just sent via pull request https://github.com/apache/incubator-edgent/pull/309
would handle the distribution of Release and SNAPSHOT artifacts via Maven repository managers

In addition to simplifying things, I would suggest to create some simple Maven archetypes
to help people setup their own Edgent applications. For those of you which don't quite know
archetypes: It's a mechanism built into the default Maven system that allows you to provide
project template which users can simply execute and automate the setup of maven projects.

We did have quite good success with this in the Flex project.

> Simplify download experience
> ----------------------------
>                 Key: EDGENT-413
>                 URL: https://issues.apache.org/jira/browse/EDGENT-413
>             Project: Edgent
>          Issue Type: Improvement
>            Reporter: John D. Ament
> Edgent binaries are not distributed via maven.  To simplify consumer use cases, it would
be better to see these binaries in a java based repository manager.
> When doing this, it would also be good to remove the heavy binary distribution in favor
of a simpler maven staging repository with the binaries in it, but it may make sense to split
out that work after this is in.

This message was sent by Atlassian JIRA

View raw message