You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@edgent.apache.org by "Dale LaBossiere (JIRA)" <ji...@apache.org> on 2017/10/04 19:03:00 UTC

[jira] [Commented] (EDGENT-273) Add scripts, etc to enable building samples against a binary-release

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

Dale LaBossiere commented on EDGENT-273:
----------------------------------------

the way the samples are being handled and distributed is being refactored in the maven retooling effort - PR-309

> Add scripts, etc to enable building samples against a binary-release
> --------------------------------------------------------------------
>
>                 Key: EDGENT-273
>                 URL: https://issues.apache.org/jira/browse/EDGENT-273
>             Project: Edgent
>          Issue Type: Improvement
>          Components: Samples
>            Reporter: Dale LaBossiere
>            Assignee: Dale LaBossiere
>            Priority: Minor
>
> Right now all of the sample jars are only built as part of building Edgent (a repo or source-release image).  At least one sample, scenarios/iotp/range/scenario, uses pi4j-core.jar and the binary-release can't include the compiled sample -- pi4j-core is LGPL and incompatible with ASF licensing.
> The binary-release does include the sample src.  It should also include scripts and Eclipse .project/.classpath to enable users to build the samples against a binary-release image.
> Consider creating samples-source and samples-binary release jars and removing that content from the binary-release?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)