Add classpath rewrite handling to mavencatalogresolver

[jahutton]

Running into an issue with multiple level of dependencies (C->B->A). It would be helpful if the MavenCatalogResolver would also handle the classpath protocols so that schemaLocations can remain as urls to be rewritten into maven uris in downstream projects.

[highsource]

Would please consider providing a test project to demonstrate the required feature?

[jahutton]

I've forked it here https:/jahutton/maven-jaxb2-plugin with the relevant changes. It would just mean merging the logic from ClasspathCatalogResolver into MavenCatalogResolver.

[highsource]

Ok, I undestand the idea technically but don't understand, why would the
MavenCatalogResolver not be sufficient. I actually thought that the
ClasspathCatalogResolver is obsolete and functionally superceeded by the
MavenCatalogResolver.

On Mon, Oct 27, 2014 at 3:57 PM, jahutton [email protected] wrote:

I've forked it here https:/jahutton/maven-jaxb2-plugin with
the relavent changes. It would just mean merging the logic from
ClasspathCatalogResolver into MavenCatalogResolver.

—
Reply to this email directly or view it on GitHub
#13 (comment)
.

[jahutton]

Ok, figured a solution to my problem just took some time to take a step back and re think it. I'll close this, however having the maven protocol self identify or allow extensions on the maven resolver could allow individuals needs to be met with out needing a pull.

The solution was to have one packaged catalog for the world (classpath for cxf) and one in a build location for jaxb.

[highsource]

I'd still be grateful if you explain the original problem that you had. I actually don't mind adding classpath: support, I just wanted to make sure that it is reasonable.

By the way, you can configure your own resolvers using the catalogResolver configuration element. But they will replace the "default" one completely, not extend it. Please file an issue if you think this would be a good feature.