placing third party installation under maven

[John Harrison <jh...@cas.org>]

In my project I use a third party library that I would like to put into 
a remote maven repository. The lib is distributed as a zip file. To use 
the lib outside of maven you unzip the archive to a directory, set your 
classpath to various locations in that directory, and set an environment 
variable pointing to the directory itself. The library is proprietary 
and there are various licensing issues but these would be handled 
outside of maven.

What I'd like to be able to do is place a dependency on the third party 
lib in my project and have maven do as much of the above as possible. 
I'm looking at the assembly plugin and the dependency plugin but 
basically I'm a maven newbie and I'm horribly confused.

Thanks, John



Confidentiality Notice: This electronic message transmission, including any attachment(s), may contain confidential, proprietary, or privileged information from Chemical Abstracts Service ("CAS"), a division of the American Chemical Society ("ACS"). If you have received this transmission in error, be advised that any disclosure, copying, distribution, or use of the contents of this information is strictly prohibited. Please destroy all copies of the message and contact the sender immediately by either replying to this message or calling 614-447-3600.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: placing third party installation under maven

[Wayne Fay <wa...@gmail.com>]

> The correct Maven way to solve this is to set up an internal remote repo, in
> which you deploy these libs (artifacts). The easiest way to do this is to
> use a repo manager such as Nexus or Artifactory. You will have this up and

I also suggest that you speak with the company/team responsible for
the third-party library and ask them how you can use it along with
Maven, especially if you run into problems with the "usual" way of
handling things due to the "set classpath to various locations" and
"set environment variables" aspects.

For me at least, this seems like the most pragmatic avenue to pursue
prior to asking on the Maven Users list, especially considering you
are new to Maven. If I can ask, what prompted you to ask here first?
This kind of thing is exactly why companies charge (and customers pay)
annual maintenance/support fees.

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

RE: placing third party installation under maven

["Meeusen, Christopher W." <Me...@mayo.edu>]

Look into nexus, its free, and easy.  I'm also a Maven newb and took
less than 4 hours to setup and upload all our 3rd party artifacts.

Good luck,
Chris

-----Original Message-----
From: anders.g.hammar@gmail.com [mailto:anders.g.hammar@gmail.com] On
Behalf Of Anders Hammar
Sent: Tuesday, June 08, 2010 1:35 PM
To: Maven Users List
Subject: Re: placing third party installation under maven

The correct Maven way to solve this is to set up an internal remote
repo, in which you deploy these libs (artifacts). The easiest way to do
this is to use a repo manager such as Nexus or Artifactory. You will
have this up and running in less than a day.
The benefit of doing this is that you solve the problem for all your
developers. And you do it the correct Maven way which makes you learn
correct Maven procedures. And when you do have a repo manager already
set up, a whole new world of possibilities opens up. Such as deployment
of your own artifacts for instance.

Any other way is just a work-around. Please learn from other people
going down that path and some time later regretting it.

/Anders

On Tue, Jun 8, 2010 at 16:38, John Harrison <jh...@cas.org> wrote:

> In my project I use a third party library that I would like to put 
> into a remote maven repository. The lib is distributed as a zip file. 
> To use the lib outside of maven you unzip the archive to a directory, 
> set your classpath to various locations in that directory, and set an 
> environment variable pointing to the directory itself. The library is 
> proprietary and there are various licensing issues but these would be 
> handled outside of maven.
>
> What I'd like to be able to do is place a dependency on the third 
> party lib in my project and have maven do as much of the above as 
> possible. I'm looking at the assembly plugin and the dependency plugin

> but basically I'm a maven newbie and I'm horribly confused.
>
> Thanks, John
>
>
>
> Confidentiality Notice: This electronic message transmission, 
> including any attachment(s), may contain confidential, proprietary, or

> privileged information from Chemical Abstracts Service ("CAS"), a 
> division of the American Chemical Society ("ACS"). If you have 
> received this transmission in error, be advised that any disclosure, 
> copying, distribution, or use of the contents of this information is 
> strictly prohibited. Please destroy all copies of the message and 
> contact the sender immediately by either replying to this message or
calling 614-447-3600.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: placing third party installation under maven

[Anders Hammar <an...@hammar.net>]

The correct Maven way to solve this is to set up an internal remote repo, in
which you deploy these libs (artifacts). The easiest way to do this is to
use a repo manager such as Nexus or Artifactory. You will have this up and
running in less than a day.
The benefit of doing this is that you solve the problem for all your
developers. And you do it the correct Maven way which makes you learn
correct Maven procedures. And when you do have a repo manager already set
up, a whole new world of possibilities opens up. Such as deployment of your
own artifacts for instance.

Any other way is just a work-around. Please learn from other people going
down that path and some time later regretting it.

/Anders

On Tue, Jun 8, 2010 at 16:38, John Harrison <jh...@cas.org> wrote:

> In my project I use a third party library that I would like to put into a
> remote maven repository. The lib is distributed as a zip file. To use the
> lib outside of maven you unzip the archive to a directory, set your
> classpath to various locations in that directory, and set an environment
> variable pointing to the directory itself. The library is proprietary and
> there are various licensing issues but these would be handled outside of
> maven.
>
> What I'd like to be able to do is place a dependency on the third party lib
> in my project and have maven do as much of the above as possible. I'm
> looking at the assembly plugin and the dependency plugin but basically I'm a
> maven newbie and I'm horribly confused.
>
> Thanks, John
>
>
>
> Confidentiality Notice: This electronic message transmission, including any
> attachment(s), may contain confidential, proprietary, or privileged
> information from Chemical Abstracts Service ("CAS"), a division of the
> American Chemical Society ("ACS"). If you have received this transmission in
> error, be advised that any disclosure, copying, distribution, or use of the
> contents of this information is strictly prohibited. Please destroy all
> copies of the message and contact the sender immediately by either replying
> to this message or calling 614-447-3600.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>