FYI on what's coming up with codehaus.

James Wennmacher - Unicon
480.558.2420



-------- Forwarded Message --------
Subject:        Re: Alert -- codehaus repository termination page affecting 
ability to build with mvn
Date:   Thu, 14 May 2015 10:26:12 +1000
From:   Codehaus Support <[email protected]>
To:     James Wennmacher <[email protected]>



Also in regards your other question

After the 17th we will be progressively redirecting more and more 
traffic to other sources - if there is somewhere useful we can redirect 
to - then we will do that. Otherwise we will redirect to a "termination" 
page of some description.

We won't have the original repositories online after the 17th or 
thereabouts.

Cheers,

Ben

On 14 May 2015 at 10:24, Codehaus Support <[email protected] 
<mailto:[email protected]>> wrote:

    James,

    The termination page is now valid XHTML - although I'm not sure that
    it will resolve the many problems with Maven's archive downloader.

    Cheers,

    Ben

    On 6 May 2015 at 02:23, James Wennmacher <[email protected]
    <mailto:[email protected]>> wrote:

        Thanks Ben.

        The issue was that our project depended upon a 3rd party library
        that was on Maven Central, but it's pom file specified a
        codehaus repository (see bottom of
        
https://repo1.maven.org/maven2/org/codehaus/staxmate/staxmate/2.0.1/staxmate-2.0.1.pom).


        Despite the fact that codehaus is not even used, Maven chooses
        to reach out to codehaus to create the
        org/codehaus/woodstox/stax2-api/maven-metadata-codehaus.xml
        file.  The invalid xhtml response was stored in
        maven-metadata-codehaus.xml and maven errored on parsing it.

        It looks like codehaus must have removed the http redirect
        because around early afternoon yesterday accesses to
        http://repository.codehaus.org did not redirect to https. In
        this case I was able to get around this issue by finding a newer
        version that did not have the codehaus repository (though it
        required changes in other 3rd party libraries to accommodate the
        newer version).

        My point though is that older versions of 3rd party libraries
        still reference codehaus and if you are going to be returning an
        HTML page, please insure it is XHTML compliant so maven does not
        fail.

        Starting 5/17/15 will http://repository.codehaus.org not work or
        will it only work with HTTPS? I'm expecting the former.

        Please let me know if you have any questions.

        Thanks,

        James Wennmacher - Unicon
        480.558.2420  <tel:480.558.2420>

        On 05/04/2015 06:19 PM, Codehaus Support wrote:
>         James,
>
>         You should be moving away from using that infrastructure.
>
>         The repository should be removed from your configuration in
>         favour of nexus.codehaus.org <http://nexus.codehaus.org> or
>         central.
>
>         Cheers,
>
>         Ben
>
>         On 5 May 2015 at 05:21, James Wennmacher
>         <[email protected] <mailto:[email protected]>> wrote:
>
>             I wanted to alert you that at least for us, our mvn builds
>             are failing because your redirect page for the codehaus
>             termination is not valid XHTML.  I assume this may affect
>             others as well.
>
>             [artifact:dependencies] Unable to resolve artifact: Unable
>             to get dependency information: Unable to read local copy
>             of metadata: Cannot read metadata from
>             
> '/Users/dmderde2/.m2/repository/org/codehaus/woodstox/stax2-api/maven-metadata-codehaus.xml':
>             end tag name </body> must match start tag name <hr> from
>             line 7 (position: TEXT seen ...</address>\n</body>... @9:8)
>             [artifact:dependencies]
>             org.codehaus.woodstox:stax2-api:jar:null
>
>             Deleting the <hr> (which is not terminated with a </hr>)
>             from the indicated file allows our builds to continue. 
>             May I suggest revising your page to add </hr> so others
>             are not afflicted with this?  I haven't validated if we
>             see this because an ant build.xml launches our mvn or not
>             but if we are running into it, it is likely others are as
>             well.
>
>             Thanks,
>
>             -- 
>             James Wennmacher - Unicon
>             480.558.2420  <tel:480.558.2420>
>
>
>
>
>         -- 
>         Ben Walding :: [email protected] <mailto:[email protected]>
>         Web: http://openxource.com/




    -- 
    Ben Walding :: [email protected] <mailto:[email protected]>
    Web: http://openxource.com/




-- 
Ben Walding :: [email protected] <mailto:[email protected]>
Web: http://openxource.com/



-- 
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Reply via email to