[
https://issues.apache.org/jira/browse/ISIS-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Keir Haywood updated ISIS-2591:
--------------------------------------
Description:
For datanucleus.log, this just needs to be zapped beforehand.
For the short term (while we aren't yet releasing kroviz and vaadin), perhaps
just need to ensure that these modules are not built as part of the pre-release
steps, and to run "git clean -dfx" before hand.
For the longer term (when either of these are released), we may need to locate
node_modules outside of the repo's directory (akin to ~/.m2/repository for
maven dependencies)
was:
For the short term (while we aren't yet releasing kroviz and vaadin), perhaps
just need to ensure that these modules are not built as part of the pre-release
steps, and to run "git clean -dfx" before hand.
For the longer term (when either of these are released), we may need to locate
node_modules outside of the repo's directory (akin to ~/.m2/repository for
maven dependencies)
Summary: source release seems to zip up node_modules & datanucleus.log
(was: source release seems to zip up node_modules)
> source release seems to zip up node_modules & datanucleus.log
> -------------------------------------------------------------
>
> Key: ISIS-2591
> URL: https://issues.apache.org/jira/browse/ISIS-2591
> Project: Isis
> Issue Type: Bug
> Affects Versions: 2.0.0-M5
> Reporter: Daniel Keir Haywood
> Priority: Major
> Fix For: 2.0.0-M6
>
>
> For datanucleus.log, this just needs to be zapped beforehand.
> For the short term (while we aren't yet releasing kroviz and vaadin), perhaps
> just need to ensure that these modules are not built as part of the
> pre-release steps, and to run "git clean -dfx" before hand.
> For the longer term (when either of these are released), we may need to
> locate node_modules outside of the repo's directory (akin to ~/.m2/repository
> for maven dependencies)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
