You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Dawid Weiss (JIRA)" <ji...@apache.org> on 2016/02/17 16:43:18 UTC
[jira] [Updated] (LUCENE-7033) ant prepare-release-no-sign fails
intermittently
[ https://issues.apache.org/jira/browse/LUCENE-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dawid Weiss updated LUCENE-7033:
--------------------------------
Attachment: capture-2.png
> ant prepare-release-no-sign fails intermittently
> ------------------------------------------------
>
> Key: LUCENE-7033
> URL: https://issues.apache.org/jira/browse/LUCENE-7033
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Dawid Weiss
> Priority: Minor
> Attachments: capture-2.png
>
>
> Mike reported this on the mailing list. This is fully reproducible, you just need to run it twice:
> {code}
> cd lucene
> # succeeds
> ant prepare-release-no-sign
> # fails
> ant prepare-release-no-sign
> {code}
> The problem is with this target that runs conditionally:
> {code}
> <target name="-unpack-lucene-tgz" unless="lucene.tgz.unpack.dir.exists">
> <antcall target="-ensure-lucene-tgz-exists" inheritall="false">
> <propertyset refid="uptodate.and.compiled.properties"/>
> </antcall>
> <mkdir dir="${lucene.tgz.unpack.dir}"/>
> <untar compression="gzip" src="${lucene.tgz.file}" dest="${lucene.tgz.unpack.dir}">
> <patternset refid="patternset.lucene.solr.jars"/>
> </untar>
> </target>
> {code}
> I attach a diff from the two runs -- you can see the second one skipped this task and then cleaned the output folder, which doesn't make sense.
> I don't know how to fix, but I think it's this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org