Migrating project to Maven. Adding dependencies.

["emma.sender" <em...@gmail.com>]

Hi, I'm trying to migrate a project to maven that has all the .jars in a lib
folder relative to the project root folder, and I don't want to have to
specify every .jar in a <dependency> element... Is there a way to include
lib/*.jar in the classpath? 
-- 
View this message in context: http://www.nabble.com/Migrating-project-to-Maven.-Adding-dependencies.-tp19807326p19807326.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Migrating project to Maven. Adding dependencies.

[陈思淼 <ch...@gmail.com>]

Thats just a one time work, it just cost you some time and bring you lots
of benefits.you can use http://mvnrepository.com/
to find the right groupId and artifactoryId

2008/10/6 Valerio Schiavoni <va...@gmail.com>

> Hi,
>
>
> On Sat, Oct 4, 2008 at 1:25 AM, emma.sender <em...@gmail.com> wrote:
>
> >
> > Hi, I'm trying to migrate a project to maven that has all the .jars in a
> > lib
> > folder relative to the project root folder, and I don't want to have to
> > specify every .jar in a <dependency> element... Is there a way to include
> > lib/*.jar in the classpath?
>
>
> one thing that you could technically do is to define a "virtual" repository
> pointing to your lib/ directory, and then specify that those dependencies
> come from that repository.
> Even if possible, it's a practice I would strongly discourage, and I would
> go for the conventional technique.
>
>
> WHy do you see a problem with that ? It's a do-it-once (almost) activity.
> and once you define your deps in a top-level module, those are inherited by
> the eventual submodules...
>
>
> --
> http://www.linkedin.com/in/vschiavoni
> http://jroller.com/vschiavoni
>

Re: Migrating project to Maven. Adding dependencies.

[Valerio Schiavoni <va...@gmail.com>]

Hi,


On Sat, Oct 4, 2008 at 1:25 AM, emma.sender <em...@gmail.com> wrote:

>
> Hi, I'm trying to migrate a project to maven that has all the .jars in a
> lib
> folder relative to the project root folder, and I don't want to have to
> specify every .jar in a <dependency> element... Is there a way to include
> lib/*.jar in the classpath?


one thing that you could technically do is to define a "virtual" repository
pointing to your lib/ directory, and then specify that those dependencies
come from that repository.
Even if possible, it's a practice I would strongly discourage, and I would
go for the conventional technique.


WHy do you see a problem with that ? It's a do-it-once (almost) activity.
and once you define your deps in a top-level module, those are inherited by
the eventual submodules...


-- 
http://www.linkedin.com/in/vschiavoni
http://jroller.com/vschiavoni

Re: Migrating project to Maven. Adding dependencies.

[Stevo Slavić <ss...@gmail.com>]

Hello,

One of the key reasons one would want to use Maven is because of its
dependency management feature.

Regards,
Stevo.

On Sat, Oct 4, 2008 at 1:25 AM, emma.sender <em...@gmail.com> wrote:

>
> Hi, I'm trying to migrate a project to maven that has all the .jars in a
> lib
> folder relative to the project root folder, and I don't want to have to
> specify every .jar in a <dependency> element... Is there a way to include
> lib/*.jar in the classpath?
> --
> View this message in context:
> http://www.nabble.com/Migrating-project-to-Maven.-Adding-dependencies.-tp19807326p19807326.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>