You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polygene.apache.org by "Paul Merlin (JIRA)" <ji...@apache.org> on 2015/07/06 11:21:04 UTC
[jira] [Commented] (ZEST-25) Project -> Source SDK -> Binary SDK
[ https://issues.apache.org/jira/browse/ZEST-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614765#comment-14614765 ]
Paul Merlin commented on ZEST-25:
---------------------------------
About: {{b. Only what we consider "releasable" will be released in that source form}}.
With the current build system, non-releasable modules (see ZEST-26) are ;
- not uploaded,
- not packaged in {{-bin}} distribution,
- included in {{-src}} distribution.
In order to fix the third, that is excluding "unreleasable" modules from the source distribution we would have to ;
- exclude the module's file (eg. {{libraries/cxf/**}})
- remove the module's include in {{settings.gradle}} (easily scriptable if we keep one include per line in settings.gradle ... a bit fragile though )
- remove the module's documentation includes in the website
That last point could be solved with some gradle magic in the {{manual/}} module to generate {{libraries.txt}} and {{extensions.txt}}.
This would give the opportunity to include only releasable modules in releases documentation while keeping all modules for {{develop}} documentation.
Sounds like a plan, I'll let a few days pass before starting this.
Did I miss something? Any comment?
> Project -> Source SDK -> Binary SDK
> -----------------------------------
>
> Key: ZEST-25
> URL: https://issues.apache.org/jira/browse/ZEST-25
> Project: Zest
> Issue Type: Sub-task
> Reporter: Niclas Hedhman
> Assignee: Paul Merlin
>
> Apache Software Foundation releases Source Tarballs only.
> Our build system builds a source tarball, but it had a slightly different purpose, more like a "reference" than the actual release.
> Any binaries that we ship, are not really ASF releases, but convenience packages, and secondary in nature to the source release.
> THEREFOR, it is important that
> -a. The current src/ directory where the source is built into in the tarball is removed and moved up to its root level.- See 916cc4c
> b. Only what we consider "releasable" will be released in that source form
> -c. That building from that distributed source files, accurately builds the binaries- See ac7d88a, and 4f2a0b0
> -d. Instructions for downstream packagers on how to build (everyone doesn't know Gradle)- See ac7d88a
> Once the binaries are built, both with Java 7 and Java, we need to verify that the SDK functions as expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)