I'll check into it.
On Aug 23, 2007, at 12:35 AM, Chris Hostetter wrote:
While the main index page for the javadocs generated by hudson...
http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/
javadoc/overview-summary.html
...says it is from the 2007-08-23_02-46-02 build, some jav
Michael,
If we wanted to publish M2 snapshots, we could configure Hudson to
call generate-maven-artifacts and have them deployed to the M2
snapshots repository, right?
This would mean we would have to change the deploy call a bit in
common-build.xml so that it could take in the remote repo
Grant Ingersoll wrote:
> Michael,
>
> If we wanted to publish M2 snapshots, we could configure Hudson to call
> generate-maven-artifacts and have them deployed to the M2 snapshots
> repository, right?
> This would mean we would have to change the deploy call a bit in
> common-build.xml so that it
[
https://issues.apache.org/jira/browse/LUCENE-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch reopened LUCENE-935:
--
* Define property "m2.repository.url" that defaults to
"file://${maven.dist.dir}" and use it
: I'm hoping that coord similarity API can be changed from:
: float coord(int overlap, int maxOverlap)
...
: float coord(int overlap, int maxOverlap, int docSize)
that's a pretty significant change ... especally considering Lucene
doesn't know the docSize. you my want to review the comme
