: Subject: Re: Disappearance of post.jar from the new tutorial
:
: I removed reference to it as the same class is in solr-core's JAR.
:
: The idea is to hide the details behind bin/post and before end of year
: (before 5.0 release at least) to get that taken care of.
This doesn'
velopment
> discussions.
>
> -- Jack Krupansky
>
> -Original Message- From: Erik Hatcher
> Sent: Sunday, November 30, 2014 10:25 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Disappearance of post.jar from the new tutorial
>
>
> Indeed! It’s always been a goal
:25 AM
To: solr-user@lucene.apache.org
Subject: Re: Disappearance of post.jar from the new tutorial
Indeed! It’s always been a goal/dream of mine to have the
tutorial/quickstart be more “integrated” like that.
I’ve got some ideas/techniques in the works to make this smooth and clean.
Coming soon (mid/late
Indeed! It’s always been a goal/dream of mine to have the tutorial/quickstart
be more “integrated” like that.
I’ve got some ideas/techniques in the works to make this smooth and clean.
Coming soon (mid/late December as my plate empties for Xmas time), but by all
means feel free to start p
Could be nice to have the tutorial then as a runnable Solr core. With
tutorial text, perhaps, showing up as an admin-extra or some such.
Would that be of interest?
Regards,
Alex.
Personal: http://www.outerthoughts.com/ and @arafalov
Solr resources and newsletter: http://www.solr-start.com/ and
You can still do the same thing with the solr-core JAR (note the CLASSPATH in
the tutorial).
I didn't want the new tutorial to rely on example/exampledocs directory, and to
be able to run from the root directory.
The embedded tutorial does need to be removed, or cloned. Removing it seems
b
But before you could take that jar to another machine or whatever.
Plus, it run on Windows (I am reading SOLR-6435). Maybe it's opposite
and this single class does not need to be in the solr-core's jar? Or
the price of duplication is not that big. At least until we build a
full-blown client.
And -
I removed reference to it as the same class is in solr-core's JAR.
The idea is to hide the details behind bin/post and before end of year (before
5.0 release at least) to get that taken care of.
Maybe post.jar can go away completely, but with bin/post the internal details
won't matter.
E
