[m2e-users] Handling binary-only jars

[Toolforger <toolforger@xxxxxxxxxxxxx>]

Hi all,

I have a binary-only jar that I need to include as a dependency.
It is available from an svn repository, which needs to stay the 
authoritative source of that jar (the jar is subject to potential updates.

What's the best way to mavenize it so that projects can access it?

What I tried:

1) The usual advice is to install it to the maven repository via the 
command line.
I don't like this because retrieving the jar from a defined SVN 
coordinate is part of the build process and belongs into the pom.

2) Use maven-scm-plugin to get the jar from a known revision number, use 
copy-maven-plugin to overwrite the mostly-empty jar generated by the 
compiler.
This works without any noticeable problems from a "Maven Build" launch 
configuration with an "package" goal. I have a project that depends on 
the binary-only-jar-project, and mvn package does everything as expected.
It does not work using Workspace Resolution. Switching off Workspace 
Resolution makes it all work (after I had applied mvn install to all 
projects; I guess without mvn install it wouldn't have worked, but I 
haven't tested that scenario).

Now... is there a way to make Workspace Resolution work for this 
scenario? (I.e. when I'm producing the jar artifact not via 
maven-jar-plugin but via some other means.)

Regards,
Jo