this answers how to specify groupId, artifactId and version which can be
passed to mvn via command line as
mvn -DgroupId=org.package -DartifactId=comercial-jar -Dversion=9.0

   <groupId>org.package</groupId>
   <artifactId>comercial-jar</artifactId>
   <version>9.0</version>

I've been looking for a way to specify a location that is guaranteed to
contain
PUBLICLY ACCESSIBLE LOCATION for ALL MAVEN2 PLUGINS

Failing that.. is there a way to gain access to the plugins individually so
we can d/l them to local drives ?

Thanks
Martin-

----- Original Message -----
From: "Angel Sotirov" <[EMAIL PROTECTED]>
To: "Maven Users List" <[email protected]>
Sent: Tuesday, January 29, 2008 7:19 AM
Subject: Re: How to specify local jars as dependencies?


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Andy Grove wrote:
> | Hi,
> |
> | I'm currently updating a code generator product to generate maven build
> | scripts as an alternative to Ant build scripts. Most of the
> dependencies in
> | the generated java code are open source jars and I can use the maven
> | <dependency> tags for those. However, the generated code also has
> | dependencies on commercial jars (such as Oracle JDBC drivers) that can
not
> | go into a public maven repository and that I cannot distribute with my
> | product. The user will already have these jars locally.
> |
> | How can I tell maven to put these local jars on the classpath when
> compiling
> | java code without using the dependency mechanism? I don't want to force
> | users to set up their own local repositories or to have to run maven
> | commands to install the jars in a local repository.
> |
> | Thanks,
> |
> | Andy.
> Greetings,
>
>
> ~    We are doing almost the same thing using the dependency mechanism
> system that way the artifact is not looked up in the repository, instead
> it needs to be included in the runtime class path:
>
> <dependencies>
> ~    <groupId>org.package</groupId>
> ~    <artifactId>comercial-jar</artifactId>
> ~    <version>9.0</version>
> ~    <scope>system</scope>
> </dependencies>
>
> here is a complete reference for the dependency mechanism:
>
http://maven.apache.org/guides/introduction/introduction-to-dependency-mecha
nism.html
>
>
> Hope this helps,
>
> Angel.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.8 (GNU/Linux)
>
> iEYEARECAAYFAkefGdgACgkQhgSIDFxSFd3TfwCgrCO5xCXitAhQ9IynbUMjp419
> B4AAn0HIYWFmdbPHCSKmiocFAf6bH4TT
> =rcJe
> -----END PGP SIGNATURE-----
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to