xfire-parent pom missing in global Maven repository

Sorry, I didn't see the xfire/ repository on the global Maven repository.

In that case, my bug is different :
1- you should use the standard Maven 2 names (org.codehaus.xfire)
2- if you do not use the standard names, please clean up this org.codehaus.xfire repository, as it's error-prone.

hey julien!

the poms with group id xfire are maven1 poms that are automatically converted to m2 poms. (the m2 repo on ibiblio does that)
the poms with groupId org.codehaus.xfire are built with our new maven2 build. This build was not working correctly when M5 was released. We now have a much better maven 2 build, and will release 1.0rc soon.

probably the best option right now is to use groupId xfire for now, and switch to the new groupId when the rc is released.

-chris

Hi chris,

There's also a problem with xmlbeans-jsr173-api-2.0-dev.jar missing in the global Maven repository. I know this stuff is pretty hard to get working, with the Maven global repository constantly changing (I'm the releaser for DWR).

I'm going to use XFire with Tudu Lists (http://tudu.sf.net), my pet application : I can be a tester/reviewer for your next builds if you want to.

Julien.

hey!

that jsr173 dependency is a bogus dependency that doesnt exist. the xmlbeans maven plugin seems to pull it in sometimes

if I do a mvn clean
and then a mvn install
it fails
if i do a mvn install again, it works.

maybe that could work for you too.

also you could try if mvn -N install in the root xfire dir before mvn install fixes that issue.

-chris

Well, I've been putting the latest XMLBeans in my private Maven repository in order to make that work.

But if you're telling me it's a bogus dependency, I'll just exclude it from my pom. Thanks!

In case this interests anybody reading this thread, my pom is here :
http://cvs.sourceforge.net/viewcvs.py/tudu/tudu/

After some verification, this dependency is definitely needed. If you exclude it from your POM you will get errors when running XFire.

I'm experiencing the same problem (missing xfire-parent), but now for xfire 1.1-beta-1. This really blocks us (Mule project) from upgrading in m2 build. m1 seems to be ok.

The solution is to add the dist.codehaus.org repo to your build:

<repository>
<id>codehaus</id>
<name>codehaus</name>
<url>http://dist.codehaus.org</url>
<layout>legacy</layout>
</repository>

The m2 repo guys have some crazy rewrite rules that aren't working quite right, hence our pom isn't showing up.

Thanks Dan,

That did the trick

i think this is already working since at least 1.1