[
https://issues.apache.org/jira/browse/LUCENE-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-3754:
Attachment: LUCENE-3754.patch
This version of the patch only provides per-artifact manifest files - these
manifest files are always rebuilt, as is currently the case. (I'd rather not
make manifests the only part of the build that can get stale between {{ant
clean}} invocations.)
The patch also contains a new macro {{solr-jarify}}, which provides
Solr-specific default attributes, and then calls {{jarify}}, so that these
values don't have to be specified everywhere in Solr build files - I noticed
that one of the Solr {{jarify}} invocations was missing a Solr-specific value.
The manifest filename can now have more than one value in a module, though only
the facet module uses this capability right now, to provide a different value
in the manifest for the examples jar.
Unless there are objections, I will commit this tomorrow.
Store generated archive manifests in per-module output directories
--
Key: LUCENE-3754
URL: https://issues.apache.org/jira/browse/LUCENE-3754
Project: Lucene - Java
Issue Type: Improvement
Reporter: Steven Rowe
Assignee: Steven Rowe
Priority: Minor
Attachments: LUCENE-3754.patch, LUCENE-3754.patch
Currently, generated archive manifests are all stored in the same location,
so each module's build overwrites the previously built module's manifest.
Locating these files in the per-module build dirs will allow them to be
rebuilt only when necessary, rather than every time a module's {{jar}} target
is called.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
