| Re: [m2e-users] Handling binary-only jars |
Well said, please listen to this advise. Try not to 'fight' the maven conventions.--On Wed, Jan 30, 2013 at 4:22 PM, Rafał Krzewski <rafal.krzewski@xxxxxxxxx> wrote:
Keeping jars OUT of revision control systems was one of the original motivations for creating Maven, AFAIK. When you are trying to circumvent that, you are basically on your own. The "Maven way" of solving this would be changing the build process in such way that the said jar would be published to a proper Maven repository instead of being checked into SVN. There are many ways to create a locally hosted Maven repository. maven-deploy-plugin + ssh + apache httpd, or Nexus OSS are two easy possibilities.
I know that the above may be hard / not feasible in your situation because of opinionated bosses / coworkers but I'd recommend to try it anyway, because otherwise you are just struggling to push square peg into a round hole...
Cheers,
Rafał
On 01/28/2013 07:24 PM, Toolforger wrote:
Am 28.01.2013 08:28, schrieb Anders Hammar:
Regarding the jar from the svn repo, there was a similar question on the
Maven user mailing list last week.
Yes, I started that question.
You might want to search the archive for
that list for the answers and how it was solved.
That was about getting a binary library into a pom. I got that to work; the maven side is just fine.
The question here is how to make m2e's Workspace Resolution recognize that binary library.
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
Fotografie
http://schutte.name/
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users