Maven POM not working

[geesen]

Using the maven pom from maven central does not work properly.

The problem seems to be the parent-artifact. Since the parent artifact mdnsjava-full is not known, the artifact mdnsjava (which was published to maven central) could not be entirely resolved.
I think, the problem is that developers of this package has mdnsjava-full in their local repository (e.g. they used mvn install). Therefore, they do not see that this parent artifact is actually missing...

So, either, the whole project, including mdnsjava-full and its dependencies must be published as well or the <parent> tag should be removed from the pom.xml

[hakanai]

I'm having the same problem. Is there a way to work around this?

[annovanvliet]

Workaround:
Take the master pom from this project and save it at the correct location in your local .m2 repository

[jubeira]

I'm facing the same issue.
A workaround I found is downloading the org.xbill.dnsjava from sourceforge and insert the classes manually into the jar.
@annovanvliet I didn't quite get your workaround. How would that be?

[annovanvliet]

@jubeira While the artefacts mdnsjava and mdnsjava-spi have a reference to a parent artefact "mdnsjava-full", you need to have this artefact also in your M2 repositry. As this is only a pom file artefact, you can just copy the pom.xml from this project to the correct location in your M2 repository and rename it to mdnsjava-full-${version}.pom

[kastork]

I got it working with https://www.jitpack.io/

[deakjahn]

Five years later:

  > Could not resolve net.posick:mdnsjava:2.2.0.
     > Could not parse POM https://repo.maven.apache.org/maven2/net/posick/mdnsjava/2.2.0/mdnsjava-2.2.0.pom
        > Could not find net.posick:mdnsjava-full:2.2.0.