Repository under : http://repository.codehaus.org/ is broken

Yes, I unfortunately forgot to rename the directory. This was also reported on the user mailing list. But it appears name is still not right, need to rename again.

the issue is already being worked on
woodstox needs m2 build and redeployment.

And yes, Konstantin is absolutely right: the proper longer-term solution is to automate the process. Even though this was a one-time problem (once I get dirs right, copying jars will be simple), it's better to have fool-proof system.

For what it's worth, I renamed dir, and will test this with StaxMate Maven build, as soon as the change propagates from Codehaus repo to the main maven2 repo at maven.org.

Here is the first draft of pom - it compiles fine,
and fails 30% of tests - so it is definitely work in
progress. I will fix contributor agreement ASAP
( for now - I'm agreeing with this )

Good progress Konstantin! I created a new entry WSTX-186 to track progress of this new task, let's leave this entry for resolving the short term problem.

For some reason it looks like the main maven repo is either slow at propagating the change, or doesn't notice the renamed dir. Will update when update does get propagated.

For what it's worth, here's what Codehaus Maven repo (where I upload releases) looks like:

http://repository.codehaus.org/org/codehaus/woodstox/

Thanks a lot

Hmmh. Still no action at

http://repo2.maven.org/maven2/org/codehaus/woodstox/

wonder why sync takes so long. :-/

Pointing directly at repository.codehaus.org I still get problems of the form:

Caused by: No versions are present in the repository for the artifact with a range [3.0,3.1)

From googling around, it appears to be caused by a lack of metadata in the repository [1].

Would it be possible for you to add this or change the woodstox pom to refer explicitly to 3.0.0?

Thanks,
David

[1] http://jira.codehaus.org/browse/MNG-2704

I've done the experimentation, and modifying the local pom to [3.0.0,3.1.0) didn't help me. When I added a maven-metadata.xml to my local repository, however, the [3.0,3.1) worked fine.

I am beginning to dislike Maven. maven-metadata.xml is something that would need to be auto-generated (and probably is when using maven tasks); as I really don't want to be manually tracking versions. I mean, the artifacts are in the same directory already so this is violating DRY principle. :-/

For next major version of Woodstox, it is likely that full Maven build is used, and this problem can be resolved more cleanly (along with adding checksums).

For now, I think I will just hard-code version number to make it work.
I assume "3.0" is equivalent to "3.0.0", so it won't allow using ranges.

Ok: I changed the dependency information to use exact version for stax2-api dependency, and tested this via staxmate (and explicit ref to codehaus repo). Things seem to work now.
Given all the problems with the change, I will be releasing 4.0.1 very soon now, possibly later today (there is also one actual code fix; but the main reason for release are maven deps).

Looks like updated 4.0.0 made its way into main Maven repo; but more importantly 4.0.1 is there too. Resolving.