Ok, good to know it was intentional.
Thank you for clarification,
Alex.
On 13 April 2018 at 08:56, Jan Høydahl <[email protected]> wrote:
> We DO ship/distribute Changes.html, see
> http://www-us.apache.org/dist/lucene/solr/7.3.0/ in the changes folder
> But inside the tarball there is only an index.html file linking to the
> online versions, e.g.
> http://lucene.apache.org/solr/7_3_0/changes/Changes.html That was
> intentional.
> CHANGES.txt is still inside the tarball though.
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
> 12. apr. 2018 kl. 22:37 skrev Cassandra Targett <[email protected]>:
>
> I won’t speak for Jan and Uwe who worked on the patches there, but my
> feeling is that it was specifically intended - the CHANGES entry for
> SOLR-9450 says as much.
>
> Changes.html & associated files are built with the same ant target
> (“documentation”) that builds javadocs. I think it was assumed that everyone
> knew that (or would investigate if they had an interest), and would
> understand that removing javadocs and replacing it with a single file would
> also remove Changes.html from the /docs directory in the package.
>
> On Apr 12, 2018, at 3:15 PM, Alexandre Rafalovitch <[email protected]>
> wrote:
>
>
> The scope of that JIRA was Javadocs specifically.
>
> Wouldn't loosing other files, such as changes.html be an unintended
> consequences then?
>
> Regards,
> Alex.
>
> On 12 April 2018 at 16:07, Cassandra Targett <[email protected]> wrote:
>
> I believe it was in 6.5, with
> https://issues.apache.org/jira/browse/SOLR-9450.
>
> On Apr 12, 2018, at 2:45 PM, Alexandre Rafalovitch <[email protected]>
> wrote:
>
> The Solr's doc folder is suddenly looking scarily empty.
>
> Specifically, the changes.html now seems to be only online. That quite
> surprised me. Not that I am in love with the current changes.txt or
> changes.html for my usual use case (finding when something became
> available), but still.
>
> Worse, I could not figure out when that changes.html file stopped
> being shipped by trying to read or grep through changes.txt (catch-22)
> or Jiras.
>
> Could somebody please point me to the relevant issue where that was
> discussed and executed for more context.
>
> Regards,
> Alex.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
