edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (EDGENT-413) Simplify download experience
Date Thu, 18 May 2017 14:26:04 GMT

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

ASF GitHub Bot commented on EDGENT-413:
---------------------------------------

GitHub user johnament opened a pull request:

    https://github.com/apache/incubator-edgent/pull/307

    [EDGENT-413] Adding publishing support for ASF repos.

    This is the first step for EDGENT-413.  The publishing support was mostly there, this
adds references to the ASF managed username/password and snapshot URL, if we choose snapshots.
 When doing a release you can now publish and it will create a staging repo.
    
    To setup staging, you would need to create `~/.gradle/gradle.properties` and add `asfNexusUsername`
and `asfNexusPassword` as properties, pointing to your ASF credentials.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/johnament/incubator-edgent EDGENT-413

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-edgent/pull/307.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #307
    
----
commit da2b545f0e5850c016a33da16148d783bc7fbc43
Author: John Ament <johndament@apache.org>
Date:   2017-05-18T14:22:19Z

    [EDGENT-413] Adding publishing support for ASF repos.

----


> 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
(v6.3.15#6346)

Mime
View raw message