[
https://issues.apache.org/jira/browse/LUCENE-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652592#comment-13652592
]
Robert Muir commented on LUCENE-4988:
-------------------------------------
I'm not saying its totally unfixable, but i think hard.
The only idea i had, would be some kinda alternate 'prepare-release' like
'prepare-local-release' (calls package-local-src-tgz instead of package-tgz-src
and so on).
The thing i dont like about nightly-smoke calling that, is that then we aren't
really testing 'actual' release anymore, only testing hacked ones that are
generated via this other mechanism...
But the benefit would be you could test the impact of 'code' changes too.
Another workaround for the immediate moment is to just commit to a throwaway
svn branch and then run nightly-smoke.
> "ant nightly-smoke" ignores local code changes
> ----------------------------------------------
>
> Key: LUCENE-4988
> URL: https://issues.apache.org/jira/browse/LUCENE-4988
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Hoss Man
>
> While trying to test SOLR-4803 i discovered that "ant nightly-smoke" was
> ignoring my local (uncommited) source changes in it's smoke checks.
> specifically: it was running the solr example using an unpacked version of
> artifacts built from an svn-export that did not include my changes, so
> test_utf8.sh was still failing.
> i'm not sure if it is intentional that the svn export is used instead of the
> current working checkout, but it seems like something needs to change,
> either...
> * "ant nightly-smoke" should fail if the working dir is a dirty checkout
> * "ant nightly-smoke" should use the current working dir even if it's a dirty
> checkout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
