[
https://issues.apache.org/jira/browse/LUCENE-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-3655:
--------------------------------
Attachment: LUCENE-3655.patch
Patch against smokeTestRelease.py
I have not yet run the full script against a release with this patch - I
commented out the other checks and then ran just the Maven checks.
The additional Maven artifact checks reveal two classes of problems with the
final 3.5.0 release candidate
[http://people.apache.org/~simonw/staging_area/lucene-solr-3.5.0-RC2-rev1204988]:
# The Solr war Maven artifact was not being signed. (I have fixed this issue
with the build.)
# The Lucene (and probably Solr too) javadoc and binary jars are being built
twice, once for the non-Maven artifacts, and again for the Maven artifacts.
This results in timestamp differences in the jar manifests and in some javadoc
HTML files. I think these should only be built once.
I guess the good news is that the above two are the only problems uncovered by
the new Maven artifact checks.
This is my first attempt at Python scripting, so I welcome pythonic style
critiques.
> Add Maven artifact checks to dev-tools/scripts/smokeTestRelease.py
> ------------------------------------------------------------------
>
> Key: LUCENE-3655
> URL: https://issues.apache.org/jira/browse/LUCENE-3655
> Project: Lucene - Java
> Issue Type: Task
> Components: general/build
> Affects Versions: 3.5
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Priority: Minor
> Attachments: LUCENE-3655.patch
>
>
> smokeTestRelease.py should examine the Maven artifacts in a Lucene/Solr
> release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
