[
https://issues.apache.org/jira/browse/SOLR-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12851800#action_12851800
]
Noble Paul commented on SOLR-1769:
--
committed r929454
Solr 1.4 Replication - Repeater
it be possible for you to commit the
null-check?
Solr 1.4 Replication - Repeater throwing NullPointerException
-
Key: SOLR-1769
URL: https://issues.apache.org/jira/browse/SOLR-1769
Project: Solr
{noformat}
Solr 1.4 Replication - Repeater throwing NullPointerException
-
Key: SOLR-1769
URL: https://issues.apache.org/jira/browse/SOLR-1769
Project: Solr
Issue Type: Bug
Affects
latestCommit == null. Anyway, that is what
really happens.
Solr 1.4 Replication - Repeater throwing NullPointerException
-
Key: SOLR-1769
URL: https://issues.apache.org/jira/browse/SOLR-1769
Project
[
https://issues.apache.org/jira/browse/SOLR-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörgen Rydenius updated SOLR-1769:
--
Attachment: SOLR-1769-nullcheck.patch
This simple null-check solved things for me.
Solr 1.4
is the underlying reason
Solr 1.4 Replication - Repeater throwing NullPointerException
-
Key: SOLR-1769
URL: https://issues.apache.org/jira/browse/SOLR-1769
Project: Solr
Issue Type: Bug
if
the file download is successful
Solr 1.4 Replication - Repeater throwing NullPointerException
-
Key: SOLR-1769
URL: https://issues.apache.org/jira/browse/SOLR-1769
Project: Solr
Issue
[
https://issues.apache.org/jira/browse/SOLR-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842550#action_12842550
]
Ravi Gidwani commented on SOLR-1769:
Thanks Noble.. I will try this patch on Solr 1.4
a different stacktrace
Solr 1.4 Replication - Repeater throwing NullPointerException
-
Key: SOLR-1769
URL: https://issues.apache.org/jira/browse/SOLR-1769
Project: Solr
Issue Type
. Here is more information:
1) I checked the solrconfig.xml . I am using the solr 1.4 with application
specific changes. I am attaching the solrconfig.xml for your reference.
2) All our solr servers (1 master, 2 slaves) are deployed on EC2 instances.
They are all 64 bit instances.
3) Running
[
https://issues.apache.org/jira/browse/SOLR-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravi Gidwani updated SOLR-1769:
---
Attachment: solrconfig.xml
solr 1.4 solrconfig.xml file used.
Solr 1.4 Replication - Repeater
of solr?
We really do not know the problem and we are using repeaters in our org w/o
any Exception so we are unable to reproduce this
Solr 1.4 Replication - Repeater throwing NullPointerException
-
Key: SOLR-1769
str name=masterUrlhttp://master_ip/solr/replication/str
str name=pollInterval00:00:60/str
/lst
/requestHandler
My setup:
Solr 1.4 ,
3 nodes
1 master, 2 slaves
I see these exceptions on the slaves eerytime a commit happens on the master.
After this it looks like the index is out of sync
[
https://issues.apache.org/jira/browse/SOLR-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak updated SOLR-1769:
-
Attachment: solrconfigSolr1.4.xml
Hi Paul
Yes we are using Solr 1.4 release. Also, I tried with Solr 1.4 config
file),
replication works without any issue.
It does not work if data/index directory has old data. I hope that helps to
resolve the issue. Also, I have noticed old data does not get deleted after
replication is finished
Solr 1.4 Replication - Repeater throwing NullPointerException
and not a daily nightly build
I don't see anything obviously wrong. meanwhile, why don't you just pick up the
solrconfig.xml from 1.4 and make the necessary changes and test it out?
Solr 1.4 Replication - Repeater throwing NullPointerException
this
solrconfig.xml file from Solr 1.3. We have just changed LRUCache to
FastLRUCache and defined replication request handler.
Please see attached file for your reference
Regards
Deepak
Solr 1.4 Replication - Repeater throwing NullPointerException
[
https://issues.apache.org/jira/browse/SOLR-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak updated SOLR-1769:
-
Attachment: (was: solrconfig.xml)
Solr 1.4 Replication - Repeater throwing NullPointerException
[
https://issues.apache.org/jira/browse/SOLR-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak updated SOLR-1769:
-
Attachment: solrconfig.xml
Attached the correct file now
Solr 1.4 Replication - Repeater throwing
Solr 1.4 Replication - Repeater throwing NullPointerException
-
Key: SOLR-1769
URL: https://issues.apache.org/jira/browse/SOLR-1769
Project: Solr
Issue Type: Bug
Affects
?
Solr 1.4 Replication - Repeater throwing NullPointerException
-
Key: SOLR-1769
URL: https://issues.apache.org/jira/browse/SOLR-1769
Project: Solr
Issue Type: Bug
Affects Versions
[
https://issues.apache.org/jira/browse/SOLR-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul reassigned SOLR-1769:
Assignee: Noble Paul
Solr 1.4 Replication - Repeater throwing NullPointerException
@solr-dev: Could sbd. from upstream help us out with a working tomcat.policy
for solr? For now I just granted all permissions to solr.
Hi Jan-Pascal (et al),
I've uploaded the current state of my packaging effort of SOLR 1.4 to
http://github.com/thkoch2001/pkg-debian-solr
(This is a new
: @solr-dev: Could sbd. from upstream help us out with a working tomcat.policy
: for solr? For now I just granted all permissions to solr.
I'm not very familiar with tomcat security policy declarations, but in
general...
* solr needs read/write to whatever is configured to be the data dir(s)
Also, Solr's DataImportHandler needs write to a .properties files in
conf/
Erik
On Dec 21, 2009, at 5:45 PM, Chris Hostetter wrote:
: @solr-dev: Could sbd. from upstream help us out with a working
tomcat.policy
: for solr? For now I just granted all permissions to solr.
I'm
replication in Solr 1.4, people who need
configuration replication need read/write access for the conf directory.
--
Regards,
Shalin Shekhar Mangar.
Hi All,
We've deployed 4 instances of Solr on a debian server.
It is taking only 1.5 GB of RAM on local ubuntu machine but it is taking 2.0
GB plus on Debian Lenny server.
Any ideas/pointers will help.
Regards
Rajan
What are the nature of the machines / VM run on ? 32-bit / 64-bit ?
rajan chandi wrote:
Hi All,
We've deployed 4 instances of Solr on a debian server.
It is taking only 1.5 GB of RAM on local ubuntu machine but it is taking 2.0
GB plus on Debian Lenny server.
Any ideas/pointers will help.
I can't wait...
--
Good Enough is not good enough.
To give anything less than your best is to sacrifice the gift.
Quality First. Measure Twice. Cut Once.
On Sep 15, 2009, at 6:23 PM, Chris Hostetter wrote:
: Hoss' patch is a reasonable start. I think this can be
committed. We
: can iterate in 1.5. Mark or Hoss?
: I think this is a great start for 1.4 and the rest can wait till
1.5,
: but I'll defer to Hoss. I had started working on
On Sep 15, 2009, at 12:01 PM, Andrzej Bialecki wrote:
Grant Ingersoll wrote:
Here's where we are at for 1.4. My comments are marked by .
I think we are in pretty good shape, people just need to make some
final commits. If things are still unassigned tomorrow morning, I'm
going to push
Here's where we are at for 1.4. My comments are marked by .
I think we are in pretty good shape, people just need to make some
final commits. If things are still unassigned tomorrow morning, I'm
going to push them to 1.5.
Key Summary Assignee
SOLR-1427 SearchComponents aren't
Grant Ingersoll wrote:
SOLR-1366 UnsupportedOperationException may be thrown when using
custom IndexReader Mark Miller
Patch exists. Mark?
I've got to look at this - I don't think we can solve nicely, but we can
at least cauterize the wound.
SOLR-1319 Upgrade custom Solr Highlighter
On Tue, Sep 15, 2009 at 7:44 PM, Grant Ingersoll gsing...@apache.org wrote:
Here's where we are at for 1.4. My comments are marked by .
I think we are in pretty good shape, people just need to make some final
commits. If things are still unassigned tomorrow morning, I'm going to push
them to
Grant Ingersoll wrote:
Here's where we are at for 1.4. My comments are marked by .
I think we are in pretty good shape, people just need to make some final
commits. If things are still unassigned tomorrow morning, I'm going to
push them to 1.5.
KeySummaryAssignee
SOLR-1427
: SOLR-1407 SpellingQueryConverter now disallows underscores and digits in
: field names (but allows all UTF-8 letters)Shalin Shekhar Mangar
:
: Needs a patch and a unit test. Push to 1.5?
FWIW: it's a bug against trunk that worked in 1.3, so pushing to 1.5
doesn't seem like a valid
: Hoss' patch is a reasonable start. I think this can be committed. We
: can iterate in 1.5. Mark or Hoss?
: I think this is a great start for 1.4 and the rest can wait till 1.5,
: but I'll defer to Hoss. I had started working on something more
: complicated, but I prefer Hoss' route.
Mark:
On Sep 15, 2009, at 10:47 AM, Noble Paul നോബിള്
नोब्ळ् wrote:
SOLR-1170 Java replication replicates lucene lock file
Noble Paul
Noble? Has a patch that looks reasonable for now. Might be
problematic
if Lucene ever changes the extension of the lock files.
I am not sure
On Sep 15, 2009, at 6:20 PM, Chris Hostetter wrote:
: SOLR-1407 SpellingQueryConverter now disallows underscores and
digits in
: field names (but allows all UTF-8 letters)Shalin Shekhar Mangar
:
: Needs a patch and a unit test. Push to 1.5?
FWIW: it's a bug against trunk that worked
: SOLR-1294 SolrJS/Javascript client fails in IE8! Unassigned
:
: I have concerns about this client library being included at all
in Solr, as
: I don't see anyone taking it up for maintenance. I raised
concerns on the
: main issue with no response and likewise with this one. Patch
Down to 13:
https://issues.apache.org/jira/secure/BrowseVersion.jspa?id=12310230versionId=12313351showOpenIssuesOnly=true
If we are going to release soon, we need to pick up the pace!
On Sep 11, 2009, at 11:00 AM, Grant Ingersoll wrote:
https://issues.apache.org/jira/secure/BrowseVersion.jspa?id=12310230versionId=12313351showOpenIssuesOnly=true
We are down to 14 open.
On Sep 8, 2009, at 1:41 PM, Grant Ingersoll wrote:
I can be RM unless someone else is dying to do it.
On Sep 8, 2009, at 11:06 AM, Yonik Seeley wrote:
My
I can be RM unless someone else is dying to do it.
On Sep 8, 2009, at 11:06 AM, Yonik Seeley wrote:
My day-job colleagues and I are all traveling this week (company
get-together) so that may slow things down a bit for some of us, and
perhaps cause the goal of releasing Solr 1 week after Lucene
Here's another interesting view of Solr issues:
https://issues.apache.org/jira/browse/SOLR?report=com.atlassian.jira.plugin.system.project:popularissues-panel
Most popular. Field collapsing is #1 by more than twice the next
one. I'm not proposing it for 1.4, but it certainly seems like we
https://issues.apache.org/jira/secure/BrowseVersion.jspa?id=12310230versionId=12313351showOpenIssuesOnly=true
Still 20ish issues to be worked on.
Still at 24 (although they have changed): https://issues.apache.org/jira/secure/BrowseVersion.jspa?id=12310230versionId=12313351showOpenIssuesOnly=true
. Please do your part and check if you have issues slated for 1.4.
There are a few that need unit tests, some that just need to be
There is also a whole lot unassigned still, we probably should at
least give them a glance to see if there is anything that slipped that
should be in 1.4
On Aug 8, 2009, at 6:34 PM, Yonik Seeley wrote:
24 open issues left - and nothing too difficult left. It's looking
like we should be to
24 open issues left - and nothing too difficult left. It's looking
like we should be to hit the goal of releasing this month - a week
(at most) after lucene!
-Yonik
http://www.lucidimagination.com
Yikes - just saw Mark's tweet about Lucene getting close to release...
we have some catching up to do :-)
-Yonik
http://www.lucidimagination.com
On Fri, Jul 24, 2009 at 5:14 PM, Yonik Seeleyyo...@lucidimagination.com wrote:
So it seems like Solr 1.4 should be targeted for release as soon
like Solr 1.4 should be targeted for release as soon as
possible after the Lucene 2.9 release - perhaps one week after.
Lucene looks like it may release in late August, so I think there is
enough time to get all of the issues out of the way (of course new
ones having to do with all of the changes
So it seems like Solr 1.4 should be targeted for release as soon as
possible after the Lucene 2.9 release - perhaps one week after.
Lucene looks like it may release in late August, so I think there is
enough time to get all of the issues out of the way (of course new
ones having to do with all
: More than 70% of solr these days is indexing strategy or client libraries,
: rather than search.
: These are important, but are now beginning to clutter things up for
: deployment.
Just because stuff is included in a release, (even a binary
release) doesn't mean people need to deploy it.
I am opening a JIRA issue to track this
https://issues.apache.org/jira/browse/SOLR-1252
On Mon, Jun 29, 2009 at 10:55 PM, Jan Høydahlj...@cominvent.com wrote:
Instead of multiple releases, how about one minimal release, and a package
system?
An installer will be needed for this - could be as
How are we feeling about Solr 1.4?
We have about 35 bugs in JIRA for 1.4 with about half assigned (though a
good chunk of those probably really do have an assignee).
--
- Mark
http://www.lucidimagination.com
, and it seems at this point wiser to release Solr 1.4 with
Lucene 2.9 (non-dev), assuming that goes quickly as planned. Feels
like we're a bit behind schedule here in Solr-land anyway, so it
really doesn't seem like it would slow our release up much.
-Yonik
http://www.lucidimagination.com
Is bandwidth or disk space really an issue for people today ?
you should be focusing on decreasing the size and speed of indexing
stuff not the code-base. It's not like you guys have unlimited time to
spend on this project.
ps. if you don't have the examples in there, then people won't know
On Mon, Jun 15, 2009 at 2:32 PM, Ian Holsmanli...@holsman.net wrote:
Is bandwidth or disk space really an issue for people today ?
you should be focusing on decreasing the size and speed of indexing stuff
not the code-base. It's not like you guys have unlimited time to spend on
this project.
Those examples and features should still exist but in a batteries included
version
The lite version is just for those who want the simple basic search feature.
More than 70% of solr these days is indexing strategy or client libraries,
rather than search.
These are important, but are now beginning
So it looks like Lucene 2.9 has all of a sudden accelerated the
release, and it seems at this point wiser to release Solr 1.4 with
Lucene 2.9 (non-dev), assuming that goes quickly as planned. Feels
like we're a bit behind schedule here in Solr-land anyway, so it
really doesn't seem like it would
+1 Noble. I think we should be careful about using the word snap or
snapshot.
The reason I say its confusing is that: at the top of the wiki, it said
no snapshots - but indeed there were snapshots, just not in the same
sense as before. Shalin also mentioned that
this new replication method
Mark ,
I have opened an issue SOLR-1216
let us make the necessary changes right away
thanks,
On Fri, Jun 12, 2009 at 4:23 AM, Mark Millermarkrmil...@gmail.com wrote:
+1 Noble. I think we should be careful about using the word snap or
snapshot.
The reason I say its confusing is that: at the
2009/6/10 Noble Paul നോബിള് नोब्ळ् noble.p...@corp.aol.com
str name=snapshotstartup/str
str name=snapshotcommit/str
Please note that snapshots are needed only if you want backups. Replication
does not need to create snapshots.
--
Regards,
Shalin Shekhar Mangar.
-config-value-for-Solr-1.4-Replication-tp23788960p23967397.html
Sent from the Solr - Dev mailing list archive at Nabble.com.
Shalin Shekhar Mangar wrote:
2009/6/10 Noble Paul നോബിള് नोब्ळ् noble.p...@corp.aol.com
str name=snapshotstartup/str
str name=snapshotcommit/str
Please note that snapshots are needed only if you want backups. Replication
does not need to create snapshots.
The wiki is quite
On Wed, Jun 10, 2009 at 11:37 PM, Mark Miller markrmil...@gmail.comwrote:
The wiki is quite confusing on this.
Doesnt it talk about the slave pulling a snapshot (or snap pull)? What does
it pull if you don't create a snapshot?
I think the terminology around snapshot needs to be cleaned up.
Just using the apache-solr example directory, it seems to have gotten a bit
big
e.g.
$ du -sh *
13M apache-solr-1.3.0
92M apache-solr-1.4.0
The biggest space user being example-DIH
apache-solr-1.4.0/example
$ du -sh *
4.0KREADME.txt
5.5Mclustering
80K etc
*32M
Thanks for bringing this up Patrick... clearly it would be nice to
avoid (or mandate) 100MB downloads!
-Yonik
http://www.lucidimagination.com
On Wed, Jun 10, 2009 at 5:50 PM, patrick o'leary pj...@pjaol.com wrote:
Just using the apache-solr example directory, it seems to have gotten a bit
big
+1
Should be easy enough to conjure up the Ant magic.
On Jun 10, 2009, at 5:55 PM, Yonik Seeley wrote:
Thanks for bringing this up Patrick... clearly it would be nice to
avoid (or mandate) 100MB downloads!
-Yonik
http://www.lucidimagination.com
On Wed, Jun 10, 2009 at 5:50 PM, patrick
Has anyone really complained about the size of Solr? One of the
things I like about Solr is how simple it is to get things up and
running, and how accesible the example directory makes everything.
When I first played with DIH and Cell, everything was there. I didn't
have to chase down
I'd be willing to guess that the vast majority of users start off with
the example app and customize from there to meet their needs.
Thanks for your time!
Matthew Runo
Software Engineer, Zappos.com
mr...@zappos.com - 702-943-7833
On Jun 10, 2009, at 6:04 PM, Eric Pugh wrote:
Has anyone
+1 for solr lite
A lot of users are fine without those example stuff (dih , cell)
one option is to have two different distributions. solr.zip and a solr-min.zip
On Thu, Jun 11, 2009 at 6:59 AM, Matthew Runomr...@zappos.com wrote:
I'd be willing to guess that the vast majority of users start
how about renaming the 'snappull' command to 'synchronize' or 'sync'
this is the only place where it uses the term 'snap'
On Wed, Jun 10, 2009 at 11:37 PM, Mark Millermarkrmil...@gmail.com wrote:
Shalin Shekhar Mangar wrote:
2009/6/10 Noble Paul നോബിള് नोब्ळ् noble.p...@corp.aol.com
str
understand what the snapshot values do? it's not defined in
the wiki documentation.
Thanks
--Matthias
--
View this message in context:
http://www.nabble.com/snapshot-config-value-for-Solr-1.4-Replication-tp23788960p23952016.html
Sent from the Solr - Dev mailing list archive at Nabble.com.
what the snapshot values do? it's not defined in
the wiki documentation.
Thanks
--Matthias
--
View this message in context:
http://www.nabble.com/snapshot-config-value-for-Solr-1.4-Replication-tp23788960p23952016.html
Sent from the Solr - Dev mailing list archive at Nabble.com
Hi everybody,
I am using Java to access some Solr statistics directly from the
SolrInfoMBean.getStatistics() in Solr 1.4 (nightly build from June 3 '09).
In Solr 1.3, the NamedList being returned by
SolrInfoMBean.getStatistics() was in org.apache.solr.util, but it has
changed to return
:
http://www.nabble.com/snapshot-config-value-for-Solr-1.4-Replication-tp23788960p23788960.html
Sent from the Solr - Dev mailing list archive at Nabble.com.
The advantage is that there is strength in numbers. There will be a
lot of users using the release build and if there is an issue the user
can rest assured that there will others who need the same fix on the
same revision. (so a better chance of a resolution)
moreover there won't be any half
-Original Message-
From: noble.p...@gmail.com [mailto:noble.p...@gmail.com] On Behalf Of
Noble Paul ??? ??
Sent: Thursday, May 14, 2009 5:55 AM
To: solr-dev@lucene.apache.org
Subject: Re: Solr 1.4
The advantage is that there is strength in numbers. There will be a
lot of users
It's not like anything all that magical necessarily happens with a release.
Sure, we package up the bits and there is some legal ramifications, I
suppose, but the software is more or less the same. In other words, most
people should be fine with trunk, or some recent revision. In fact if
, but definitely not a CI/nightly.
Best Regards,
Patrick
-Original Message-
From: noble.p...@gmail.com [mailto:noble.p...@gmail.com] On Behalf Of
Noble Paul ??? ??
Sent: Thursday, May 14, 2009 5:55 AM
To: solr-dev@lucene.apache.org
Subject: Re: Solr 1.4
The advantage
FYI, I also planned on starting a discussion about the particular
version and features of Lucene that Solr is using on lucene-dev before
Solr releases.
-Yonik
: Solr 1.4
I'm not suggesting you don't validate it first with your own tests. I
can't imagine you take a release and just deploy it in production,
right?
I'm just observing that if everyone (besides the committers) takes
this release only approach, then you quickly realize that the large
Regards,
Patrick
-Original Message-
From: Grant Ingersoll [mailto:gsing...@apache.org]
Sent: Thursday, May 14, 2009 11:33 AM
To: solr-dev@lucene.apache.org
Subject: Re: Solr 1.4
I'm not suggesting you don't validate it first with your own
tests. I
can't imagine you take a release
Ingersoll [mailto:gsing...@apache.org]
Sent: Thursday, May 14, 2009 11:33 AM
To: solr-dev@lucene.apache.org
Subject: Re: Solr 1.4
I'm not suggesting you don't validate it first with your own
tests. I
can't imagine you take a release and just deploy it in production,
right?
I'm just observing
Seems like we're reaching critical mass again, but there is a lot of
issues that are open, or not even marked.
Do people think we can shoot for 1.4 in the coming month (say mid-
June)? I'm happy (OK, maybe happy isn't the word, how about willing)
to be the RM again.
See
On Wed, May 13, 2009 at 9:10 AM, Grant Ingersoll gsing...@apache.org wrote:
Seems like we're reaching critical mass again, but there is a lot of issues
that are open, or not even marked.
Do people think we can shoot for 1.4 in the coming month (say mid-June)?
+1
I was sort of shooting for
On Wed, May 13, 2009 at 6:40 PM, Grant Ingersoll gsing...@apache.orgwrote:
Seems like we're reaching critical mass again, but there is a lot of issues
that are open, or not even marked.
Do people think we can shoot for 1.4 in the coming month (say mid-June)?
I'm happy (OK, maybe happy isn't
On May 13, 2009, at 2:59 PM, Shalin Shekhar Mangar wrote:
See https://issues.apache.org/jira/secure/BrowseProject.jspa for
what's
currently on 1.4, 1.5 and unscheduled. The unscheduled section is
particularly large, IMO. So, we should work through these areas.
WDYT?
I wouldn't want to
On May 13, 2009, at 9:36 AM, Yonik Seeley wrote:
On Wed, May 13, 2009 at 9:10 AM, Grant Ingersoll
gsing...@apache.org wrote:
Seems like we're reaching critical mass again, but there is a lot
of issues
that are open, or not even marked.
Do people think we can shoot for 1.4 in the coming
]
Sent: Wednesday, May 13, 2009 1:02 PM
To: solr-dev@lucene.apache.org
Subject: Re: Solr 1.4
On May 13, 2009, at 9:36 AM, Yonik Seeley wrote:
On Wed, May 13, 2009 at 9:10 AM, Grant Ingersoll
gsing...@apache.org wrote:
Seems like we're reaching critical mass again, but there is a lot
Solr 1.4-SNAPSHOT seems to now be requiring:
3) org.apache.commons:commons-io:jar:1.4
which doesn't appear to exist on public repositories.
commons-io:commons-io:1.4 does exist.
If you clear your repository and build using it, the build fails.
Before entering a bug, is anyone else
dooh -- my fault. I had one in my local repos, but its non-standard
I'll make the fix in just a sec...
thanks
ryan
On Dec 4, 2008, at 6:51 PM, jayson.minard wrote:
Solr 1.4-SNAPSHOT seems to now be requiring:
3) org.apache.commons:commons-io:jar:1.4
which doesn't appear to exist
fixed in rev 723554
On Dec 4, 2008, at 6:51 PM, jayson.minard wrote:
Solr 1.4-SNAPSHOT seems to now be requiring:
3) org.apache.commons:commons-io:jar:1.4
which doesn't appear to exist on public repositories.
commons-io:commons-io:1.4 does exist.
If you clear your repository
93 matches
Mail list logo
