Hi Martin,
thanks for that. Unfortunately its no help if you don't use Nexus.
All the best,
DaveLaw
On 18.02.2014 02:28, Martin Gainty wrote:
MG ...I had a chance to read the FINE manual today and when including remote
repositories:
Option=Download Remote Indexes
This field controls the
2014-02-17 7:55 GMT+01:00 David Law m2ecli...@apconsult.de:
Ron, Wayne,
this wasted several days (elapsed) of my time:
I spent ages trying out options trying to figure out what I'd done
wrong...
...rebuilding updating indices, hacking through to
Baptiste,
if you'd looked on the m2e list, you would have seen my postings.
When the problem arose, it was not at all clear which component was to
blame,
so it makes sense to post to all relevant forums.
All the best,
DaveLaw
On 17.02.2014 10:07, Baptiste Mathus wrote:
2014-02-17 7:55
Ron, Wayne,
this wasted several days (elapsed) of my time:
I spent ages trying out options trying to figure out what I'd done
wrong...
...rebuilding updating indices, hacking through to
workspace\.metadata\.plugins\org.eclipse.m2e.logback.configuration,
to set logging to ALL, but even ALL
I don't think that it has anything to do with m2e since the Nexus repo
has the same problem proxying Maven Central.
It is not a Maven problem but it is most likely that someone will find
the warning if it is added to the discussion of Maven Central in the
Maven docs.
It is unlikely that a
Hi Dave, Ron everyone,
David Law wrote:
Now, I guess the problem could be any combination of:
a) me b) POI c) maven d) m2eclipse e) eclipse?
In this sort of case, it is helpful to do more tests to narrow things down.
Maybe I missed it elsewhere in the thread, but did you actually try
Date: Mon, 17 Feb 2014 09:28:08 -0500
From: rwhee...@artifact-software.com
To: users@maven.apache.org
Subject: Re: Looking for org.apache.poi 3.10-FINAL
I don't think that it has anything to do with m2e since the Nexus repo
has the same problem proxying Maven Central
Hi,
I'm new to maven thought I'd try it out on the recently checked-in:
org.apache.poi3.10-FINAL
I'm using m2eclipse standard config with Eclipse Kepler. Repo defaults to:
http://repo.maven.apache.org/maven2
The Problem:
m2eclipse does not know the org.apache.poi 3.10-FINAL artifact.
David,
just guessing:
- indexing takes it's time, there are only two hours difference between the
commit (??l and end of indexing.
- commit (tag creation), artifact creation (jar build), deployment (upload
to staging), promotion (move of staged to released) and synchronization
from
Hi Mirko,
I think though 6 days!!! should be adequate for that.
In fact, I think 6 minutes should be adequate.
So I really need someone to explain how I can move forward with this issue.
All the best,
DaveLaw
On 16.02.2014 10:49, Mirko Friedenhagen wrote:
David,
just guessing:
- indexing
On 16 February 2014 10:31, David Law m2ecli...@apconsult.de wrote:
Hi Mirko,
I think though 6 days!!! should be adequate for that.
In fact, I think 6 minutes should be adequate.
So I really need someone to explain how I can move forward with this issue.
FWIW, I did a search today for
Date: Sun, 16 Feb 2014 10:49:48 +0100
Subject: Re: Looking for org.apache.poi 3.10-FINAL
From: mfriedenha...@gmail.com
To: users@maven.apache.org
David,
just guessing:
- indexing takes it's time, there are only two hours difference between the
commit (??l and end of indexing
Hi Stuart,
thanks for that very useful information.
Are you using the default repo?
(http://repo.maven.apache.org/maven2)
All the best,
DaveLaw
On 16.02.2014 14:36, Stuart McCulloch wrote:
On 16 February 2014 10:31, David Law m2ecli...@apconsult.de wrote:
Hi Mirko,
I think though 6
On 16 February 2014 14:36, David Law m2ecli...@apconsult.de wrote:
Hi Stuart,
thanks for that very useful information.
Are you using the default repo?
(http://repo.maven.apache.org/maven2)
I switch depending what workspace I'm using, as I have a corporate repo as
well as a local nexus
Hi Stuart,
thanks once again! The only person to supply useful information.
I checked the Nexus Index Timestamp from the repo this morning 05:39 CET
and:
nexus.index.timestamp=20140209134945.568 +
Over 6 days old!!
Just checked it again and:
nexus.index.timestamp=20140216125157.106
On Sunday, 16 February 2014, David Law m2ecli...@apconsult.de wrote:
Hi Stuart,
thanks once again! The only person to supply useful information.
I checked the Nexus Index Timestamp from the repo this morning 05:39 CET
and:
nexus.index.timestamp=20140209134945.568 +
Over 6 days old!!
thanks once again! The only person to supply useful information.
...
Over 6 days old!!
...
So that means maven central took over 6 days to index this content.
That is quite incredible!
...
This is in my opinion a bug, or at least a fundamental design error.
Also before completely blaming
And it's just an index. You can always download the artifact without it.
And as far as I know, the downloadable central index has always only been
updated once a week. Have a look here:
http://repo1.maven.org/maven2/.index/
/Anders
On Sun, Feb 16, 2014 at 9:52 PM, Wayne Fay wayne...@gmail.com
Anders,
Tack för det.
Dave
On 16.02.2014 22:03, Anders Hammar wrote:
And it's just an index. You can always download the artifact without it.
And as far as I know, the downloadable central index has always only been
updated once a week. Have a look here:
http://repo1.maven.org/maven2/.index/
Hi Wayne,
I would suggest someone documents the behaviour in the FAQ
with a tip that a not-yet-indexed artifact can be proactively retrieved
by entering its Group Id, Artifact Id Version.
That way we all save time.
All the best,
DaveLaw
On 16.02.2014 21:52, Wayne Fay wrote:
thanks once
Sure, but which FAQ should this go in - a generic Maven faq, a faq
specific to m2eclipse (bear in mind, this group has zero control over
m2e), or a FAQ related to Central? Or all of those places? Where did
you look (in the Maven website docs) for such information, prior to
posting your email to
http://stackoverflow.com/questions/10600576/nexus-index-of-maven-central-is-not-up-to-date-new-installation
The problem appears to be well known but is not something that one
expects and it will be hard to know where people are most likely to look.
It is not really a Maven problem and as I
Ron, Wayne,
this wasted several days (elapsed) of my time:
I spent ages trying out options trying to figure out what I'd done
wrong...
...rebuilding updating indices, hacking through to
workspace\.metadata\.plugins\org.eclipse.m2e.logback.configuration,
to set logging to ALL, but even ALL was
23 matches
Mail list logo
