You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2013/01/11 19:10:13 UTC
[jira] [Created] (LUCENE-4681) more artifact inconsistencies
Robert Muir created LUCENE-4681:
-----------------------------------
Summary: more artifact inconsistencies
Key: LUCENE-4681
URL: https://issues.apache.org/jira/browse/LUCENE-4681
Project: Lucene - Core
Issue Type: Bug
Components: general/build
Reporter: Robert Muir
Currently the tasks for releasing can easily create artifacts that are inconsistent with each other:
* the source releases (package-tgz-src) targets trigger an svn checkout to ensure the source release has no local modifications or extra files (even svn:ignore'd).
* the binary releases (and maven source/javadoc/binary artifacts too?) unfortunately are not built from this source release, which can differ than the local version.
* users who want to make their own release have to run special source targets (package-local-src-tgz) to make source tgs built from their actual checkout.
I think this can be safer and simpler.
Instead of these special source targets: imagine a prepare-release and a prepare-release-local (or swap it around and have prepare-official-release and prepare-release, i actually like that better, but it doesnt matter).
prepare-official-release would just do an svn:checkout and subant "prepare-release" from that checkout.
this way we know all artifacts are from the same consistent source.
--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org