You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by David Law <m2...@apconsult.de> on 2014/02/16 09:43:08 UTC
Looking for org.apache.poi 3.10-FINAL
Hi,
I'm new to maven & thought I'd try it out on the recently checked-in:
org.apache.poi 3.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.
Now, I guess the problem could be any combination of:
a) me b) POI c) maven d) m2eclipse e) eclipse?
QUESTION) Can anyone help to localise it?
Here's what I've found out so far:
0) repo is: http://repo.maven.apache.org/maven2
1) org.apache.poi 3.10-FINAL was committed @ 09-Feb-2014 11:50
2) as of now repo Timestamp is: 09-Feb-2014 13:50
(nexus.index.timestamp=20140209134945.568 +0000)
(found in
http://repo.maven.apache.org/maven2/.index/nexus-maven-repository-index.properties)
3) -> so repo has been reindexed since org.apache.poi 3.10-FINAL commit
(6 days ago).
4) exit eclipse
5) deleted the index
C:\...\Eclipse\workspace\.metadata\.plugins\org.eclipse.m2e.core\nexus
6) start eclipse -> "updating index"
7) org.apache.poi 3.10-FINAL is still not there (that is: "here") in my
list of artifacts
All the best,
DaveLaw
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Looking for org.apache.poi 3.10-FINAL
Posted by David Law <m2...@apconsult.de>.
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 GMT+01:00 David Law <m2...@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
>> workspace\.metadata\.plugins\org.eclipse.m2e.logback.configuration,
>> to set logging to ALL, but even ALL was somewhat sparse.
>>
> M2E is not Maven per-se. When a question is about a particular tool, I'd
> advice you to try and target the most specific ML/support system:
> https://eclipse.org/m2e/support/
>
>
>
>> I tried Google & found loads of hits that had nothing to do with it.
>> I found nothing at apache maven or maven central or m2eclipse.
>> I tried the POI Forum, but it became clear that wasn't the problem.
>>
>> As Wayne rightly points out "where is the right place to document it?".
>> With a complex issue like this with multiple components where do you start?
>> But thats all the more reason to document it somewhere...
>
>> Right now it seems to me not to be a maven problem as such.
>> Its about how maven central creates its indices & how m2e uses them.
>> So in theory it needs to be documented in both, correspondingly
>> cross-referenced.
>> But as the m2e FAQ is subscription-only it would seem the only place is the
>> maven central FAQ. And its so important, it should be a point in its
>> own right:
>>
>> "Why can't I see new artifacts in my client (e.g. m2eclipse)?"
>> (Tip -> you can get as-yet-unindexed artifacts explicitly...blah, blah)
>>
> Again, not the best ML to discuss it.
>
>
>> And then there's the question, why does m2e use the high-latency index?
> If its performance/server-load, then it could be
>> a rethink of the index-structure is necessary.
>> Is that a maven issue?
>> I have some ideas there...
>>
> Definitely not Maven related. Maven core has nothing to do with the indexes
> you describe, doesn't know/need it.
> It's more an IDE/search engine facility to help people find versions. I
> personally almost never use those for example.
>
> Cheers
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Looking for org.apache.poi 3.10-FINAL
Posted by Curtis Rueden <ct...@wisc.edu>.
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
building from the command line, to eliminate M2E from the equation? Of
course, it is too late now, since 3.10-FINAL is already indexed in Central
at this point, but if you encounter the issue again, would be worth a shot.
Ron Wheeler wrote:
> I don't think that it has anything to do with m2e since the Nexus repo
> has the same problem proxying Maven Central.
FWIW, my team has a hacky way to force Nexus to update its cache for a
given proxy repository; see:
https://github.com/scijava/scijava-scripts/blob/c7fadf95eae7a231ed729fc7a1b23c6a2944ee12/maven-helper.sh#L195
Basically it just deletes the maven-metadata.xml and artifact JAR out of
the /service/local/data_cache/repositories/*/content area, so that the next
time that information is requested, Nexus is forced to query upstream
immediately. Without this hack, we were not seeing our new releases on OSS
Sonatype trickle down to our Nexus right away.
Regards,
Curtis
On Mon, Feb 17, 2014 at 8:28 AM, Ron Wheeler <rwheeler@artifact-software.com
> wrote:
> 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 Maven user would read the FAQ on Maven Central since
> once you set up the link in your Repo or (God forbid in your settings.xml),
> you don't really have any direct contact with Maven Central.
>
> The most likely place that a new person would encounter Maven Central is
> in that section that I referenced in the Maven site.
>
> We have not had this problem but I occasionally use my Nexus repo to check
> for the latest version of a utility rather than look at the utility's web
> site since it is faster when looking up several dependencies at once. I
> have learned something important in this discussion!!!
>
> Ron
>
>
> On 17/02/2014 4:07 AM, Baptiste Mathus wrote:
>
>> 2014-02-17 7:55 GMT+01:00 David Law <m2...@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
>>> workspace\.metadata\.plugins\org.eclipse.m2e.logback.configuration,
>>> to set logging to ALL, but even ALL was somewhat sparse.
>>>
>>> M2E is not Maven per-se. When a question is about a particular tool, I'd
>> advice you to try and target the most specific ML/support system:
>> https://eclipse.org/m2e/support/
>>
>>
>>
>> I tried Google & found loads of hits that had nothing to do with it.
>>> I found nothing at apache maven or maven central or m2eclipse.
>>> I tried the POI Forum, but it became clear that wasn't the problem.
>>>
>>> As Wayne rightly points out "where is the right place to document it?".
>>> With a complex issue like this with multiple components where do you
>>> start?
>>> But thats all the more reason to document it somewhere...
>>>
>>
>> Right now it seems to me not to be a maven problem as such.
>>> Its about how maven central creates its indices & how m2e uses them.
>>> So in theory it needs to be documented in both, correspondingly
>>> cross-referenced.
>>> But as the m2e FAQ is subscription-only it would seem the only place is
>>> the
>>> maven central FAQ. And its so important, it should be a point in its
>>> own right:
>>>
>>> "Why can't I see new artifacts in my client (e.g. m2eclipse)?"
>>> (Tip -> you can get as-yet-unindexed artifacts explicitly...blah, blah)
>>>
>>> Again, not the best ML to discuss it.
>>
>>
>> And then there's the question, why does m2e use the high-latency index?
>>>
>> If its performance/server-load, then it could be
>>
>>> a rethink of the index-structure is necessary.
>>> Is that a maven issue?
>>> I have some ideas there...
>>>
>>> Definitely not Maven related. Maven core has nothing to do with the
>> indexes
>> you describe, doesn't know/need it.
>> It's more an IDE/search engine facility to help people find versions. I
>> personally almost never use those for example.
>>
>> Cheers
>>
>>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Looking for org.apache.poi 3.10-FINAL
Posted by David Law <m2...@apconsult.de>.
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 downloading of the remote indexes. If enabled, Nexus will download
> the index, if it exists, and use that for its searches as well as serve that up to any clients which
> ask for the index (like m2eclipse). The default for new proxy repositories is enabled, but all
> of the default repositories included in Nexus have this option disabled. To change this setting
> for one of the proxy repositories that ship with Nexus, change the option, save the repository,
>
>
On 16.02.2014 09:43, David Law wrote:
> Hi,
>
> I'm new to maven & thought I'd try it out on the recently checked-in:
> org.apache.poi 3.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.
>
> Now, I guess the problem could be any combination of:
> a) me b) POI c) maven d) m2eclipse e) eclipse?
>
> QUESTION) Can anyone help to localise it?
>
> Here's what I've found out so far:
>
> 0) repo is: http://repo.maven.apache.org/maven2
>
> 1) org.apache.poi 3.10-FINAL was committed @ 09-Feb-2014 11:50
>
> 2) as of now repo Timestamp is: 09-Feb-2014 13:50
> (nexus.index.timestamp=20140209134945.568 +0000)
> (found in
> http://repo.maven.apache.org/maven2/.index/nexus-maven-repository-index.properties)
>
>
> 3) -> so repo has been reindexed since org.apache.poi 3.10-FINAL commit
> (6 days ago).
>
> 4) exit eclipse
>
> 5) deleted the index
> C:\...\Eclipse\workspace\.metadata\.plugins\org.eclipse.m2e.core\nexus
>
> 6) start eclipse -> "updating index"
>
> 7) org.apache.poi 3.10-FINAL is still not there (that is: "here") in my
> list of artifacts
>
> All the best,
> DaveLaw
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Looking for org.apache.poi 3.10-FINAL
Posted by Martin Gainty <mg...@hotmail.com>.
> Date: Mon, 17 Feb 2014 09:28:08 -0500
> From: rwheeler@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.
>
> 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 Maven user would read the FAQ on Maven Central
> since once you set up the link in your Repo or (God forbid in your
> settings.xml), you don't really have any direct contact with Maven Central.
>
> The most likely place that a new person would encounter Maven Central is
MG> ...I had a chance to read the FINE manual today and when including remote repositories:
Option=Download Remote Indexes
This field controls the downloading of the remote indexes. If enabled, Nexus will download
the index, if it exists, and use that for its searches as well as serve that up to any clients which
ask for the index (like m2eclipse). The default for new proxy repositories is enabled, but all
of the default repositories included in Nexus have this option disabled. To change this setting
for one of the proxy repositories that ship with Nexus, change the option, save the repository,
> We have not had this problem but I occasionally use my Nexus repo to
> check for the latest version of a utility rather than look at the
> utility's web site since it is faster when looking up several
> dependencies at once. I have learned something important in this
> discussion!!!
>MG>(me too)
> Ron
MG>Martin
> On 17/02/2014 4:07 AM, Baptiste Mathus wrote:
> > 2014-02-17 7:55 GMT+01:00 David Law <m2...@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
> >> workspace\.metadata\.plugins\org.eclipse.m2e.logback.configuration,
> >> to set logging to ALL, but even ALL was somewhat sparse.
> >>
> > M2E is not Maven per-se. When a question is about a particular tool, I'd
> > advice you to try and target the most specific ML/support system:
> > https://eclipse.org/m2e/support/
> >
> >
> >
> >> I tried Google & found loads of hits that had nothing to do with it.
> >> I found nothing at apache maven or maven central or m2eclipse.
> >> I tried the POI Forum, but it became clear that wasn't the problem.
> >>
> >> As Wayne rightly points out "where is the right place to document it?".
> >> With a complex issue like this with multiple components where do you start?
> >> But thats all the more reason to document it somewhere...
> >
> >> Right now it seems to me not to be a maven problem as such.
> >> Its about how maven central creates its indices & how m2e uses them.
> >> So in theory it needs to be documented in both, correspondingly
> >> cross-referenced.
> >> But as the m2e FAQ is subscription-only it would seem the only place is the
> >> maven central FAQ. And its so important, it should be a point in its
> >> own right:
> >>
> >> "Why can't I see new artifacts in my client (e.g. m2eclipse)?"
> >> (Tip -> you can get as-yet-unindexed artifacts explicitly...blah, blah)
> >>
> > Again, not the best ML to discuss it.
> >
> >
> >> And then there's the question, why does m2e use the high-latency index?
> > If its performance/server-load, then it could be
> >> a rethink of the index-structure is necessary.
> >> Is that a maven issue?
> >> I have some ideas there...
> >>
> > Definitely not Maven related. Maven core has nothing to do with the indexes
> > you describe, doesn't know/need it.
> > It's more an IDE/search engine facility to help people find versions. I
> > personally almost never use those for example.
> >
> > Cheers
> >
>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
Re: Looking for org.apache.poi 3.10-FINAL
Posted by Ron Wheeler <rw...@artifact-software.com>.
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 Maven user would read the FAQ on Maven Central
since once you set up the link in your Repo or (God forbid in your
settings.xml), you don't really have any direct contact with Maven Central.
The most likely place that a new person would encounter Maven Central is
in that section that I referenced in the Maven site.
We have not had this problem but I occasionally use my Nexus repo to
check for the latest version of a utility rather than look at the
utility's web site since it is faster when looking up several
dependencies at once. I have learned something important in this
discussion!!!
Ron
On 17/02/2014 4:07 AM, Baptiste Mathus wrote:
> 2014-02-17 7:55 GMT+01:00 David Law <m2...@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
>> workspace\.metadata\.plugins\org.eclipse.m2e.logback.configuration,
>> to set logging to ALL, but even ALL was somewhat sparse.
>>
> M2E is not Maven per-se. When a question is about a particular tool, I'd
> advice you to try and target the most specific ML/support system:
> https://eclipse.org/m2e/support/
>
>
>
>> I tried Google & found loads of hits that had nothing to do with it.
>> I found nothing at apache maven or maven central or m2eclipse.
>> I tried the POI Forum, but it became clear that wasn't the problem.
>>
>> As Wayne rightly points out "where is the right place to document it?".
>> With a complex issue like this with multiple components where do you start?
>> But thats all the more reason to document it somewhere...
>
>> Right now it seems to me not to be a maven problem as such.
>> Its about how maven central creates its indices & how m2e uses them.
>> So in theory it needs to be documented in both, correspondingly
>> cross-referenced.
>> But as the m2e FAQ is subscription-only it would seem the only place is the
>> maven central FAQ. And its so important, it should be a point in its
>> own right:
>>
>> "Why can't I see new artifacts in my client (e.g. m2eclipse)?"
>> (Tip -> you can get as-yet-unindexed artifacts explicitly...blah, blah)
>>
> Again, not the best ML to discuss it.
>
>
>> And then there's the question, why does m2e use the high-latency index?
> If its performance/server-load, then it could be
>> a rethink of the index-structure is necessary.
>> Is that a maven issue?
>> I have some ideas there...
>>
> Definitely not Maven related. Maven core has nothing to do with the indexes
> you describe, doesn't know/need it.
> It's more an IDE/search engine facility to help people find versions. I
> personally almost never use those for example.
>
> Cheers
>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Looking for org.apache.poi 3.10-FINAL
Posted by Baptiste Mathus <ml...@batmat.net>.
2014-02-17 7:55 GMT+01:00 David Law <m2...@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
> workspace\.metadata\.plugins\org.eclipse.m2e.logback.configuration,
> to set logging to ALL, but even ALL was somewhat sparse.
>
M2E is not Maven per-se. When a question is about a particular tool, I'd
advice you to try and target the most specific ML/support system:
https://eclipse.org/m2e/support/
> I tried Google & found loads of hits that had nothing to do with it.
> I found nothing at apache maven or maven central or m2eclipse.
> I tried the POI Forum, but it became clear that wasn't the problem.
>
> As Wayne rightly points out "where is the right place to document it?".
> With a complex issue like this with multiple components where do you start?
> But thats all the more reason to document it somewhere...
> Right now it seems to me not to be a maven problem as such.
> Its about how maven central creates its indices & how m2e uses them.
> So in theory it needs to be documented in both, correspondingly
> cross-referenced.
> But as the m2e FAQ is subscription-only it would seem the only place is the
> maven central FAQ. And its so important, it should be a point in its
> own right:
>
> "Why can't I see new artifacts in my client (e.g. m2eclipse)?"
> (Tip -> you can get as-yet-unindexed artifacts explicitly...blah, blah)
>
Again, not the best ML to discuss it.
>
> And then there's the question, why does m2e use the high-latency index?
If its performance/server-load, then it could be
> a rethink of the index-structure is necessary.
> Is that a maven issue?
> I have some ideas there...
>
Definitely not Maven related. Maven core has nothing to do with the indexes
you describe, doesn't know/need it.
It's more an IDE/search engine facility to help people find versions. I
personally almost never use those for example.
Cheers
Re: Looking for org.apache.poi 3.10-FINAL
Posted by David Law <m2...@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
workspace\.metadata\.plugins\org.eclipse.m2e.logback.configuration,
to set logging to ALL, but even ALL was somewhat sparse.
I tried Google & found loads of hits that had nothing to do with it.
I found nothing at apache maven or maven central or m2eclipse.
I tried the POI Forum, but it became clear that wasn't the problem.
As Wayne rightly points out "where is the right place to document it?".
With a complex issue like this with multiple components where do you start?
But thats all the more reason to document it somewhere...
Right now it seems to me not to be a maven problem as such.
Its about how maven central creates its indices & how m2e uses them.
So in theory it needs to be documented in both, correspondingly
cross-referenced.
But as the m2e FAQ is subscription-only it would seem the only place is the
maven central FAQ. And its so important, it should be a point in its
own right:
"Why can't I see new artifacts in my client (e.g. m2eclipse)?"
(Tip -> you can get as-yet-unindexed artifacts explicitly...blah, blah)
And then there's the question, why does m2e use the high-latency index?
If its performance/server-load, then it could be
a rethink of the index-structure is necessary.
Is that a maven issue?
I have some ideas there...
All the best,
DaveLaw
On 17/02/2014 00:56, Ron Wheeler wrote:
> 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 understand it, if you just
> set your dependencies and build, you will not see the problem or be
> affected by it.
> If you are trying to use your own repository's proxy to Maven Central
> to quickly find the latest version rather than visiting the website of
> the developer of the library, you will have trouble.
> If you go to directly to searching Maven Central, you will not have
> the problem.
>
> It seems that you need to separate the problem from the point where
> the user will run into it.
> The most likely place to look for it is in Maven since that is where
> one might read documentation about setting up dependencies, even if it
> has nothing to do with Maven.
>
> http://maven.apache.org/guides/getting-started/index.html#How_do_I_use_external_dependencies
>
> is probably the most likely place to see a note about browsing Maven
> Central
> It most likely could go somewhere in this paragraph:
> <quote>
> What about dependencies built somewhere else? How do they get into my
> local repository? Whenever a project references a dependency that
> isn't available in the local repository, Maven will download the
> dependency from a remote repository into the local repository. You
> probably noticed Maven downloading a lot of things when you built your
> very first project (these downloads were dependencies for the various
> plugins used to build the project). By default, the remote repository
> Maven uses can be found (and browsed)
> athttp://repo.maven.apache.org/maven2/. You can also set up your own
> remote repository (maybe a central repository for your company) to use
> instead of or in addition to the default remote repository. For more
> information on repositories you can refer to theIntroduction to
> Repositories
> <http://maven.apache.org/guides/introduction/introduction-to-repositories.html>.
>
> </quote>
>
> It would still be an odd notation and might still be hard to find,
> given the initial analysis that a new Maven user would have of the
> apparent problem.
>
> I am not sure what the cost of creating a new index is, but perhaps it
> could be done more frequently.
>
> I also do not understand how the index is propagated to my proxy for
> Maven Central in my Nexus repo but I still don't see the latest POI
> either ( my Nexus is very old so perhaps the problem is at my end)
>
> Ron
>
>
>
> On 16/02/2014 6:31 PM, Wayne Fay wrote:
>> 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 this list?
>>
>> It may not sound like it but I am genuinely curious where this
>> information should go to ensure the right people can see/find it when
>> they need to know such information.
>>
>> Wayne
>>
>> On Sun, Feb 16, 2014 at 4:43 PM, David Law <m2...@apconsult.de>
>> wrote:
>>> 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 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 Sonatype I would suggest you find out
>>>> You may also want to lose some of the attitude. No one here is getting
>>>> paid (by you) to do what we're doing -- in fact Sonatype has spent a
>>>> considerable amount of money building and maintaining Central over the
>>>> years. Attacking them (or those on this list) because you couldn't use
>>>> the latest POI immediately after it was released seems like a bad
>>>> move. You catch more flies with honey and all that.
>>>>
>>>> Wayne
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Looking for org.apache.poi 3.10-FINAL
Posted by David Law <Da...@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
workspace\.metadata\.plugins\org.eclipse.m2e.logback.configuration,
to set logging to ALL, but even ALL was somewhat sparse.
I tried Google & found loads of hits that had nothing to do with it.
I found nothing at apache maven or maven central or m2eclipse.
I tried the POI Forum, but it became clear that wasn't the problem.
As Wayne rightly points out "where is the right place to document it?".
With a complex issue like this with multiple components where do you start?
But thats all the more reason to document it somewhere...
Right now it seems to me not to be a maven problem as such.
Its about how maven central creates its indices & how m2e uses them.
So in theory it needs to be documented in both, correspondingly
cross-referenced.
But as the m2e FAQ is subscription-only it would seem the only place is the
maven central FAQ. And its so important, it should be a point in its
own right:
"Why can't I see new artifacts in my client (e.g. m2eclipse)?"
(Tip -> you can get as-yet-unindexed artifacts explicitly...)
And then there's the question, why does m2e use the high-latency index?
If its performance/server-load, then it could be
a rethink of the index-structure is necessary.
Is that a maven issue?
I have some ideas there...
All the best,
DaveLaw
On 17/02/2014 00:56, Ron Wheeler wrote:
> 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 understand it, if you just
> set your dependencies and build, you will not see the problem or be
> affected by it.
> If you are trying to use your own repository's proxy to Maven Central
> to quickly find the latest version rather than visiting the website of
> the developer of the library, you will have trouble.
> If you go to directly to searching Maven Central, you will not have
> the problem.
>
> It seems that you need to separate the problem from the point where
> the user will run into it.
> The most likely place to look for it is in Maven since that is where
> one might read documentation about setting up dependencies, even if it
> has nothing to do with Maven.
>
> http://maven.apache.org/guides/getting-started/index.html#How_do_I_use_external_dependencies
>
> is probably the most likely place to see a note about browsing Maven
> Central
> It most likely could go somewhere in this paragraph:
> <quote>
> What about dependencies built somewhere else? How do they get into my
> local repository? Whenever a project references a dependency that
> isn't available in the local repository, Maven will download the
> dependency from a remote repository into the local repository. You
> probably noticed Maven downloading a lot of things when you built your
> very first project (these downloads were dependencies for the various
> plugins used to build the project). By default, the remote repository
> Maven uses can be found (and browsed)
> athttp://repo.maven.apache.org/maven2/. You can also set up your own
> remote repository (maybe a central repository for your company) to use
> instead of or in addition to the default remote repository. For more
> information on repositories you can refer to theIntroduction to
> Repositories
> <http://maven.apache.org/guides/introduction/introduction-to-repositories.html>.
>
> </quote>
>
> It would still be an odd notation and might still be hard to find,
> given the initial analysis that a new Maven user would have of the
> apparent problem.
>
> I am not sure what the cost of creating a new index is, but perhaps it
> could be done more frequently.
>
> I also do not understand how the index is propagated to my proxy for
> Maven Central in my Nexus repo but I still don't see the latest POI
> either ( my Nexus is very old so perhaps the problem is at my end)
>
> Ron
>
>
>
> On 16/02/2014 6:31 PM, Wayne Fay wrote:
>> 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 this list?
>>
>> It may not sound like it but I am genuinely curious where this
>> information should go to ensure the right people can see/find it when
>> they need to know such information.
>>
>> Wayne
>>
>> On Sun, Feb 16, 2014 at 4:43 PM, David Law <m2...@apconsult.de>
>> wrote:
>>> 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 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 Sonatype I would suggest you find out
>>>> You may also want to lose some of the attitude. No one here is getting
>>>> paid (by you) to do what we're doing -- in fact Sonatype has spent a
>>>> considerable amount of money building and maintaining Central over the
>>>> years. Attacking them (or those on this list) because you couldn't use
>>>> the latest POI immediately after it was released seems like a bad
>>>> move. You catch more flies with honey and all that.
>>>>
>>>> Wayne
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Looking for org.apache.poi 3.10-FINAL
Posted by Ron Wheeler <rw...@artifact-software.com>.
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 understand it, if you just set
your dependencies and build, you will not see the problem or be affected
by it.
If you are trying to use your own repository's proxy to Maven Central to
quickly find the latest version rather than visiting the website of the
developer of the library, you will have trouble.
If you go to directly to searching Maven Central, you will not have the
problem.
It seems that you need to separate the problem from the point where the
user will run into it.
The most likely place to look for it is in Maven since that is where one
might read documentation about setting up dependencies, even if it has
nothing to do with Maven.
http://maven.apache.org/guides/getting-started/index.html#How_do_I_use_external_dependencies
is probably the most likely place to see a note about browsing Maven
Central
It most likely could go somewhere in this paragraph:
<quote>
What about dependencies built somewhere else? How do they get into my
local repository? Whenever a project references a dependency that isn't
available in the local repository, Maven will download the dependency
from a remote repository into the local repository. You probably noticed
Maven downloading a lot of things when you built your very first project
(these downloads were dependencies for the various plugins used to build
the project). By default, the remote repository Maven uses can be found
(and browsed) athttp://repo.maven.apache.org/maven2/. You can also set
up your own remote repository (maybe a central repository for your
company) to use instead of or in addition to the default remote
repository. For more information on repositories you can refer to
theIntroduction to Repositories
<http://maven.apache.org/guides/introduction/introduction-to-repositories.html>.
</quote>
It would still be an odd notation and might still be hard to find, given
the initial analysis that a new Maven user would have of the apparent
problem.
I am not sure what the cost of creating a new index is, but perhaps it
could be done more frequently.
I also do not understand how the index is propagated to my proxy for
Maven Central in my Nexus repo but I still don't see the latest POI
either ( my Nexus is very old so perhaps the problem is at my end)
Ron
On 16/02/2014 6:31 PM, Wayne Fay wrote:
> 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 this list?
>
> It may not sound like it but I am genuinely curious where this
> information should go to ensure the right people can see/find it when
> they need to know such information.
>
> Wayne
>
> On Sun, Feb 16, 2014 at 4:43 PM, David Law <m2...@apconsult.de> wrote:
>> 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 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 Sonatype I would suggest you find out
>>> You may also want to lose some of the attitude. No one here is getting
>>> paid (by you) to do what we're doing -- in fact Sonatype has spent a
>>> considerable amount of money building and maintaining Central over the
>>> years. Attacking them (or those on this list) because you couldn't use
>>> the latest POI immediately after it was released seems like a bad
>>> move. You catch more flies with honey and all that.
>>>
>>> Wayne
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
Re: Looking for org.apache.poi 3.10-FINAL
Posted by Wayne Fay <wa...@gmail.com>.
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 this list?
It may not sound like it but I am genuinely curious where this
information should go to ensure the right people can see/find it when
they need to know such information.
Wayne
On Sun, Feb 16, 2014 at 4:43 PM, David Law <m2...@apconsult.de> wrote:
> 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 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 Sonatype I would suggest you find out
>>
>> You may also want to lose some of the attitude. No one here is getting
>> paid (by you) to do what we're doing -- in fact Sonatype has spent a
>> considerable amount of money building and maintaining Central over the
>> years. Attacking them (or those on this list) because you couldn't use
>> the latest POI immediately after it was released seems like a bad
>> move. You catch more flies with honey and all that.
>>
>> Wayne
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Looking for org.apache.poi 3.10-FINAL
Posted by David Law <m2...@apconsult.de>.
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 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 Sonatype I would suggest you find out
> You may also want to lose some of the attitude. No one here is getting
> paid (by you) to do what we're doing -- in fact Sonatype has spent a
> considerable amount of money building and maintaining Central over the
> years. Attacking them (or those on this list) because you couldn't use
> the latest POI immediately after it was released seems like a bad
> move. You catch more flies with honey and all that.
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Looking for org.apache.poi 3.10-FINAL
Posted by David Law <m2...@apconsult.de>.
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/
>
> /Anders
>
>
> On Sun, Feb 16, 2014 at 9:52 PM, Wayne Fay <wa...@gmail.com> wrote:
>
>>>> 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 Sonatype I would suggest you find out
>> You may also want to lose some of the attitude. No one here is getting
>> paid (by you) to do what we're doing -- in fact Sonatype has spent a
>> considerable amount of money building and maintaining Central over the
>> years. Attacking them (or those on this list) because you couldn't use
>> the latest POI immediately after it was released seems like a bad
>> move. You catch more flies with honey and all that.
>>
>> Wayne
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Looking for org.apache.poi 3.10-FINAL
Posted by Anders Hammar <an...@hammar.net>.
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 <wa...@gmail.com> wrote:
> >> 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 Sonatype I would suggest you find out
>
> You may also want to lose some of the attitude. No one here is getting
> paid (by you) to do what we're doing -- in fact Sonatype has spent a
> considerable amount of money building and maintaining Central over the
> years. Attacking them (or those on this list) because you couldn't use
> the latest POI immediately after it was released seems like a bad
> move. You catch more flies with honey and all that.
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Looking for org.apache.poi 3.10-FINAL
Posted by Wayne Fay <wa...@gmail.com>.
>> 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 Sonatype I would suggest you find out
You may also want to lose some of the attitude. No one here is getting
paid (by you) to do what we're doing -- in fact Sonatype has spent a
considerable amount of money building and maintaining Central over the
years. Attacking them (or those on this list) because you couldn't use
the latest POI immediately after it was released seems like a bad
move. You catch more flies with honey and all that.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Looking for org.apache.poi 3.10-FINAL
Posted by Stephen Connolly <st...@gmail.com>.
On Sunday, 16 February 2014, David Law <m2...@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 +0000
> Over 6 days old!!
>
> Just checked it again and:
> nexus.index.timestamp=20140216125157.106 +0000
>
> And, not surprisingly, my m2eclipse can now find the artifact.
>
> So that means maven central took over 6 days to index this content.
> That is quite incredible!
>
>
I would suggest you take this issue up with Sonatype, who maintain central
and it's indexing
Also before completely blaming Sonatype I would suggest you find out
exactly when POI released the staging repo on repository.a.o as it only
gets synced to central IIRC up to 8h after being promoted on the ASF nexus
instance
This is in my opinion a bug, or at least a fundamental design error.
>
> Thank you once again.
>
> All the best,
> DaveLaw
>
>
> On 16.02.2014 16:20, Stuart McCulloch wrote:
>
>> On 16 February 2014 14:36, David Law <m2...@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 instance (enabled to download remote indexes)
>>
>> But I just tried from a fresh installation with the default repo to
>> confirm
>> and it is in the latest index with nexus.index.timestamp=
>> 20140216125157.106
>>
>>
>> All the best,
>>> DaveLaw
>>>
>>> On 16.02.2014 14:36, Stuart McCulloch wrote:
>>>
>>> On 16 February 2014 10:31, David Law <m2...@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 org.apache.poi:poi in my local m2e
>>>>>
>>>> and 3.10-FINAL appeared - so it's definitely in the index from the 15th
>>>> (which is the index downloaded on my local computer according to the
>>>> file
>>>> under .metadata/.plugins/org.eclipse.m2e.core/nexus), but not sure when
>>>> it
>>>> was indexed...
>>>>
>>>> You could always post a question on
>>>> https://issues.sonatype.org/browse/MVNCENTRAL if you want a definitive
>>>> answer of what happened, when, and why.
>>>>
>>>> All the best,
>>>>
>>>> DaveLaw
>>>>>
>>>>>
>>>>> On 16.02.2014 10:49, Mirko Friedenhagen wrote:
>>>>>
>>>>> 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 oss.sonatype.org to repo1 add delays :-)
>>>>>>
>>>>>> Regards
>>>>>> Mirko
>>>>>>
>>>>>> On 16.02.2014 09:43, David Law wrote:
>>>>>>
>>>>> Hi,
>>>>>
>>>>>> I'm new to maven & thought I'd try it out on the recently checked-in:
>>>>>> org.apache.poi 3.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.
>>>>>>
>>>>>> Now, I guess the problem could be any combination of:
>>>>>> a) me b) POI c) maven d) m2eclipse e) eclipse?
>>>>>>
>>>>>> QUESTION) Can anyone help to localise it?
>>>>>>
>>>>>> Here's what I've found out so far:
>>>>>>
>>>>>> 0) repo is: http://repo.maven.apache.org/maven2
>>>>>>
>>>>>> 1) org.apache.poi 3.10-FINAL was committed @ 09-Feb-2014 11:50
>>>>>>
>>>>>> 2) as of now repo Timestamp is: 09-Feb-2014 13:50
>>>>>> (nexus.index.timestamp=20140209134945.568 +0000)
>>>>>> (found in
>>>>>> http://repo.maven.apache.org/maven2/.index/nexus-maven-
>>>>>> repository-index.properties)
>>>>>>
>>>>>> 3) -> so repo has been reindexed since org.apache.poi 3.10-FINAL
>>>>>> commit
>>>>>> (6 days ago).
>>>>>>
>>>>>> 4) exit eclipse
>>>>>>
>>>>>> 5) deleted the index
>>>>>> C:\...\Eclipse\workspace\.metadata\.plugins\org.eclipse.
>>>>>> m2e.core\nexus
>>>>>>
>>>>>> 6) start eclipse -> "updating index"
>>>>>>
>>>>>> 7) org.apache.poi 3.10-FINAL is still not there (that is: "here") in
>>>>>> my
>>>>>> list of artifacts
>>>>>>
>>>>>> All the best,
>>>>>> DaveLaw
>>>>>>
>>>>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Sent from my phone
Re: Looking for org.apache.poi 3.10-FINAL
Posted by David Law <m2...@apconsult.de>.
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 +0000
Over 6 days old!!
Just checked it again and:
nexus.index.timestamp=20140216125157.106 +0000
And, not surprisingly, my m2eclipse can now find the artifact.
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.
Thank you once again.
All the best,
DaveLaw
On 16.02.2014 16:20, Stuart McCulloch wrote:
> On 16 February 2014 14:36, David Law <m2...@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 instance (enabled to download remote indexes)
>
> But I just tried from a fresh installation with the default repo to confirm
> and it is in the latest index with nexus.index.timestamp=20140216125157.106
>
>
>> All the best,
>> DaveLaw
>>
>> On 16.02.2014 14:36, Stuart McCulloch wrote:
>>
>>> On 16 February 2014 10:31, David Law <m2...@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 org.apache.poi:poi in my local m2e
>>> and 3.10-FINAL appeared - so it's definitely in the index from the 15th
>>> (which is the index downloaded on my local computer according to the file
>>> under .metadata/.plugins/org.eclipse.m2e.core/nexus), but not sure when
>>> it
>>> was indexed...
>>>
>>> You could always post a question on
>>> https://issues.sonatype.org/browse/MVNCENTRAL if you want a definitive
>>> answer of what happened, when, and why.
>>>
>>> All the best,
>>>
>>>> DaveLaw
>>>>
>>>>
>>>> On 16.02.2014 10:49, Mirko Friedenhagen wrote:
>>>>
>>>> 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 oss.sonatype.org to repo1 add delays :-)
>>>>>
>>>>> Regards
>>>>> Mirko
>>>>>
>>>>> On 16.02.2014 09:43, David Law wrote:
>>>> Hi,
>>>>> I'm new to maven & thought I'd try it out on the recently checked-in:
>>>>> org.apache.poi 3.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.
>>>>>
>>>>> Now, I guess the problem could be any combination of:
>>>>> a) me b) POI c) maven d) m2eclipse e) eclipse?
>>>>>
>>>>> QUESTION) Can anyone help to localise it?
>>>>>
>>>>> Here's what I've found out so far:
>>>>>
>>>>> 0) repo is: http://repo.maven.apache.org/maven2
>>>>>
>>>>> 1) org.apache.poi 3.10-FINAL was committed @ 09-Feb-2014 11:50
>>>>>
>>>>> 2) as of now repo Timestamp is: 09-Feb-2014 13:50
>>>>> (nexus.index.timestamp=20140209134945.568 +0000)
>>>>> (found in
>>>>> http://repo.maven.apache.org/maven2/.index/nexus-maven-
>>>>> repository-index.properties)
>>>>>
>>>>> 3) -> so repo has been reindexed since org.apache.poi 3.10-FINAL commit
>>>>> (6 days ago).
>>>>>
>>>>> 4) exit eclipse
>>>>>
>>>>> 5) deleted the index
>>>>> C:\...\Eclipse\workspace\.metadata\.plugins\org.eclipse.m2e.core\nexus
>>>>>
>>>>> 6) start eclipse -> "updating index"
>>>>>
>>>>> 7) org.apache.poi 3.10-FINAL is still not there (that is: "here") in my
>>>>> list of artifacts
>>>>>
>>>>> All the best,
>>>>> DaveLaw
>>>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Looking for org.apache.poi 3.10-FINAL
Posted by Stuart McCulloch <mc...@gmail.com>.
On 16 February 2014 14:36, David Law <m2...@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 instance (enabled to download remote indexes)
But I just tried from a fresh installation with the default repo to confirm
and it is in the latest index with nexus.index.timestamp=20140216125157.106
> All the best,
> DaveLaw
>
> On 16.02.2014 14:36, Stuart McCulloch wrote:
>
>> On 16 February 2014 10:31, David Law <m2...@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 org.apache.poi:poi in my local m2e
>> and 3.10-FINAL appeared - so it's definitely in the index from the 15th
>> (which is the index downloaded on my local computer according to the file
>> under .metadata/.plugins/org.eclipse.m2e.core/nexus), but not sure when
>> it
>> was indexed...
>>
>> You could always post a question on
>> https://issues.sonatype.org/browse/MVNCENTRAL if you want a definitive
>> answer of what happened, when, and why.
>>
>> All the best,
>>
>>> DaveLaw
>>>
>>>
>>> On 16.02.2014 10:49, Mirko Friedenhagen wrote:
>>>
>>> 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 oss.sonatype.org to repo1 add delays :-)
>>>>
>>>> Regards
>>>> Mirko
>>>>
>>>> On 16.02.2014 09:43, David Law wrote:
>>>
>>> Hi,
>>>>
>>>> I'm new to maven & thought I'd try it out on the recently checked-in:
>>>> org.apache.poi 3.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.
>>>>
>>>> Now, I guess the problem could be any combination of:
>>>> a) me b) POI c) maven d) m2eclipse e) eclipse?
>>>>
>>>> QUESTION) Can anyone help to localise it?
>>>>
>>>> Here's what I've found out so far:
>>>>
>>>> 0) repo is: http://repo.maven.apache.org/maven2
>>>>
>>>> 1) org.apache.poi 3.10-FINAL was committed @ 09-Feb-2014 11:50
>>>>
>>>> 2) as of now repo Timestamp is: 09-Feb-2014 13:50
>>>> (nexus.index.timestamp=20140209134945.568 +0000)
>>>> (found in
>>>> http://repo.maven.apache.org/maven2/.index/nexus-maven-
>>>> repository-index.properties)
>>>>
>>>> 3) -> so repo has been reindexed since org.apache.poi 3.10-FINAL commit
>>>> (6 days ago).
>>>>
>>>> 4) exit eclipse
>>>>
>>>> 5) deleted the index
>>>> C:\...\Eclipse\workspace\.metadata\.plugins\org.eclipse.m2e.core\nexus
>>>>
>>>> 6) start eclipse -> "updating index"
>>>>
>>>> 7) org.apache.poi 3.10-FINAL is still not there (that is: "here") in my
>>>> list of artifacts
>>>>
>>>> All the best,
>>>> DaveLaw
>>>>
>>>
--
Cheers, Stuart
Re: Looking for org.apache.poi 3.10-FINAL
Posted by David Law <m2...@apconsult.de>.
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 <m2...@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 org.apache.poi:poi in my local m2e
> and 3.10-FINAL appeared - so it's definitely in the index from the 15th
> (which is the index downloaded on my local computer according to the file
> under .metadata/.plugins/org.eclipse.m2e.core/nexus), but not sure when it
> was indexed...
>
> You could always post a question on
> https://issues.sonatype.org/browse/MVNCENTRAL if you want a definitive
> answer of what happened, when, and why.
>
> All the best,
>> DaveLaw
>>
>>
>> On 16.02.2014 10:49, Mirko Friedenhagen wrote:
>>
>>> 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 oss.sonatype.org to repo1 add delays :-)
>>>
>>> Regards
>>> Mirko
>>>
>> On 16.02.2014 09:43, David Law wrote:
>>
>>> Hi,
>>>
>>> I'm new to maven & thought I'd try it out on the recently checked-in:
>>> org.apache.poi 3.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.
>>>
>>> Now, I guess the problem could be any combination of:
>>> a) me b) POI c) maven d) m2eclipse e) eclipse?
>>>
>>> QUESTION) Can anyone help to localise it?
>>>
>>> Here's what I've found out so far:
>>>
>>> 0) repo is: http://repo.maven.apache.org/maven2
>>>
>>> 1) org.apache.poi 3.10-FINAL was committed @ 09-Feb-2014 11:50
>>>
>>> 2) as of now repo Timestamp is: 09-Feb-2014 13:50
>>> (nexus.index.timestamp=20140209134945.568 +0000)
>>> (found in
>>> http://repo.maven.apache.org/maven2/.index/nexus-maven-
>>> repository-index.properties)
>>>
>>> 3) -> so repo has been reindexed since org.apache.poi 3.10-FINAL commit
>>> (6 days ago).
>>>
>>> 4) exit eclipse
>>>
>>> 5) deleted the index
>>> C:\...\Eclipse\workspace\.metadata\.plugins\org.eclipse.m2e.core\nexus
>>>
>>> 6) start eclipse -> "updating index"
>>>
>>> 7) org.apache.poi 3.10-FINAL is still not there (that is: "here") in my
>>> list of artifacts
>>>
>>> All the best,
>>> DaveLaw
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Looking for org.apache.poi 3.10-FINAL
Posted by Stuart McCulloch <mc...@gmail.com>.
On 16 February 2014 10:31, David Law <m2...@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 org.apache.poi:poi in my local m2e
and 3.10-FINAL appeared - so it's definitely in the index from the 15th
(which is the index downloaded on my local computer according to the file
under .metadata/.plugins/org.eclipse.m2e.core/nexus), but not sure when it
was indexed...
You could always post a question on
https://issues.sonatype.org/browse/MVNCENTRAL if you want a definitive
answer of what happened, when, and why.
All the best,
> DaveLaw
>
>
> On 16.02.2014 10:49, Mirko Friedenhagen wrote:
>
>> 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 oss.sonatype.org to repo1 add delays :-)
>>
>> Regards
>> Mirko
>>
>
> On 16.02.2014 09:43, David Law wrote:
>
>> Hi,
>>
>> I'm new to maven & thought I'd try it out on the recently checked-in:
>> org.apache.poi 3.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.
>>
>> Now, I guess the problem could be any combination of:
>> a) me b) POI c) maven d) m2eclipse e) eclipse?
>>
>> QUESTION) Can anyone help to localise it?
>>
>> Here's what I've found out so far:
>>
>> 0) repo is: http://repo.maven.apache.org/maven2
>>
>> 1) org.apache.poi 3.10-FINAL was committed @ 09-Feb-2014 11:50
>>
>> 2) as of now repo Timestamp is: 09-Feb-2014 13:50
>> (nexus.index.timestamp=20140209134945.568 +0000)
>> (found in
>> http://repo.maven.apache.org/maven2/.index/nexus-maven-
>> repository-index.properties)
>>
>> 3) -> so repo has been reindexed since org.apache.poi 3.10-FINAL commit
>> (6 days ago).
>>
>> 4) exit eclipse
>>
>> 5) deleted the index
>> C:\...\Eclipse\workspace\.metadata\.plugins\org.eclipse.m2e.core\nexus
>>
>> 6) start eclipse -> "updating index"
>>
>> 7) org.apache.poi 3.10-FINAL is still not there (that is: "here") in my
>> list of artifacts
>>
>> All the best,
>> DaveLaw
>>
>
--
Cheers, Stuart
Re: Looking for org.apache.poi 3.10-FINAL
Posted by David Law <m2...@apconsult.de>.
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 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 oss.sonatype.org to repo1 add delays :-)
>
> Regards
> Mirko
On 16.02.2014 09:43, David Law wrote:
> Hi,
>
> I'm new to maven & thought I'd try it out on the recently checked-in:
> org.apache.poi 3.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.
>
> Now, I guess the problem could be any combination of:
> a) me b) POI c) maven d) m2eclipse e) eclipse?
>
> QUESTION) Can anyone help to localise it?
>
> Here's what I've found out so far:
>
> 0) repo is: http://repo.maven.apache.org/maven2
>
> 1) org.apache.poi 3.10-FINAL was committed @ 09-Feb-2014 11:50
>
> 2) as of now repo Timestamp is: 09-Feb-2014 13:50
> (nexus.index.timestamp=20140209134945.568 +0000)
> (found in
> http://repo.maven.apache.org/maven2/.index/nexus-maven-repository-index.properties)
>
>
> 3) -> so repo has been reindexed since org.apache.poi 3.10-FINAL commit
> (6 days ago).
>
> 4) exit eclipse
>
> 5) deleted the index
> C:\...\Eclipse\workspace\.metadata\.plugins\org.eclipse.m2e.core\nexus
>
> 6) start eclipse -> "updating index"
>
> 7) org.apache.poi 3.10-FINAL is still not there (that is: "here") in my
> list of artifacts
>
> All the best,
> DaveLaw
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Looking for org.apache.poi 3.10-FINAL
Posted by Martin Gainty <mg...@hotmail.com>.
> Date: Sun, 16 Feb 2014 10:49:48 +0100
> Subject: Re: Looking for org.apache.poi 3.10-FINAL
> From: mfriedenhagen@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.
> - commit (tag creation), artifact creation (jar build), deployment (upload
> to staging), promotion (move of staged to released) and synchronization
> from oss.sonatype.org to repo1 add delays :-)
>
> Regards
> Mirko
> --
> Sent from my mobile
> On Feb 16, 2014 9:43 AM, "David Law" <m2...@apconsult.de> wrote:
>
> > Hi,
> >
> > I'm new to maven & thought I'd try it out on the recently checked-in:
> > org.apache.poi 3.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.
> >
> > Now, I guess the problem could be any combination of:
> > a) me b) POI c) maven d) m2eclipse e) eclipse?
> >
> > QUESTION) Can anyone help to localise it?
> >
> > Here's what I've found out so far:
> >
> > 0) repo is: http://repo.maven.apache.org/maven2
> >
> > 1) org.apache.poi 3.10-FINAL was committed @ 09-Feb-2014 11:50
> >
> > 2) as of now repo Timestamp is: 09-Feb-2014 13:50
> > (nexus.index.timestamp=20140209134945.568 +0000)
> > (found in
> > http://repo.maven.apache.org/maven2/.index/nexus-maven-
> > repository-index.properties)
> >
> > 3) -> so repo has been reindexed since org.apache.poi 3.10-FINAL commit
> > (6 days ago).
> >
> > 4) exit eclipse
> >
> > 5) deleted the index
> > C:\...\Eclipse\workspace\.metadata\.plugins\org.eclipse.m2e.core\nexus
> >
> > 6) start eclipse -> "updating index"
> >
> > 7) org.apache.poi 3.10-FINAL is still not there (that is: "here") in my
> > list of artifacts
> >
> > All the best,
> > DaveLaw
MG>I think whats happening is when you say add repository ..Eclipse assumes you want to add a CVS repo
MG>(where repo.maven.apache.org is not a a CVS repo)
MG>I was able to coax Exlipse to add repo host = central.maven.org
MG>as far as authentication to central.maven.org I tried
MG>1)ssh ...no
MG>2)pserver..no
MG>3)pserverssh2..no
MG>4)ext..no
MG>since the built in hooks to IBM repositories seem to confine to one of the 4 authentication schemes
MG>to a *known* CVS repo maybe use IDEA instead?
MG>Martin-
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
Re: Looking for org.apache.poi 3.10-FINAL
Posted by Mirko Friedenhagen <mf...@gmail.com>.
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 oss.sonatype.org to repo1 add delays :-)
Regards
Mirko
--
Sent from my mobile
On Feb 16, 2014 9:43 AM, "David Law" <m2...@apconsult.de> wrote:
> Hi,
>
> I'm new to maven & thought I'd try it out on the recently checked-in:
> org.apache.poi 3.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.
>
> Now, I guess the problem could be any combination of:
> a) me b) POI c) maven d) m2eclipse e) eclipse?
>
> QUESTION) Can anyone help to localise it?
>
> Here's what I've found out so far:
>
> 0) repo is: http://repo.maven.apache.org/maven2
>
> 1) org.apache.poi 3.10-FINAL was committed @ 09-Feb-2014 11:50
>
> 2) as of now repo Timestamp is: 09-Feb-2014 13:50
> (nexus.index.timestamp=20140209134945.568 +0000)
> (found in
> http://repo.maven.apache.org/maven2/.index/nexus-maven-
> repository-index.properties)
>
> 3) -> so repo has been reindexed since org.apache.poi 3.10-FINAL commit
> (6 days ago).
>
> 4) exit eclipse
>
> 5) deleted the index
> C:\...\Eclipse\workspace\.metadata\.plugins\org.eclipse.m2e.core\nexus
>
> 6) start eclipse -> "updating index"
>
> 7) org.apache.poi 3.10-FINAL is still not there (that is: "here") in my
> list of artifacts
>
> All the best,
> DaveLaw
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>