Deploy to Maven repository causes jar renaming

[mondain]

When I run mvn package deploy on my build, everything is properly built and available in the target directory; 1 jar and 2 nar files. On my artifact server, only the pom, xml, and 3 nars exist. My problem is that one of the nars is my jar, but has been renamed just before being uploaded; how do I stop this behavior?

[ctrueden]

Unfortunately, I don't know the answer. In general, there is no way to override the names of artifacts in Maven repositories (this is a frequently asked question on the Maven users list). So the only fix AFAIK would be to fairly radically change the behavior of NAR, to use JAR instead of NAR.

I assume your NAR is a JAR because you want to mix in Java code? We do that too in the imagej-launcher project. Our workaround is to rename the .nar back to .jar before deploying it in our final application, but this is obviously a hack.

Another option might be to have a JAR downstream which depends on the NAR, and which has your Java code isolated? I haven't played a lot with this.

Further insight on this issue from anyone else in the community would be most welcome. Ideal would be to have a wiki page with a guide on dealing with this scenario.

[00datman]

Not knowing anything about your project, I'll ask the stupid question: could you architect your project slightly differently such that you have a separate module with <package>jar</package> for that bit of code?

I'll be frank, my use of this plugin is likely different, but I don't need or want a jar from it...

The other option I'd suggest looking in to would be to add a configuration of the maven-deploy-plugin...