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 <[email protected]
> 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 <[email protected]>:
>>
>>  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: [email protected]
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to