[
https://issues.apache.org/jira/browse/POLYGENE-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009376#comment-16009376
]
Paul Merlin commented on POLYGENE-245:
--------------------------------------
> 1. The tools/generator-polygene needs to be part of the source release.
Done!
> 2. The tools/generator-polygene should be part of the binary release for
> install on the user's system.
Let's drop this for 3.0, I opened POLYGENE-252 for doing this in 3.1.
> 3. The tools/generator-polygene npm package is treated the same way as Maven
> published to Maven Central.
This is the meat of this issue.
Artifacts published to the NPM registry are convenience binaries.
We'll publish them as such once 3.0 is veted.
> Process for Publish to NPM registry
> -----------------------------------
>
> Key: POLYGENE-245
> URL: https://issues.apache.org/jira/browse/POLYGENE-245
> Project: Polygene
> Issue Type: New Feature
> Reporter: Niclas Hedhman
> Fix For: 3.0
>
>
> In http://www.apache.org/legal/release-policy#publication, there are some
> important bits that will affect our Yeoman project creator, especially that
> whatever is published there, needs to be published as source artifact first.
> So,
> 1. The tools/generator-polygene needs to be part of the source release.
> 2. The tools/generator-polygene should be part of the binary release for
> install on the user's system.
> 3. The tools/generator-polygene npm package is treated the same way as
> Maven published to Maven Central.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
