What is the problem of depending on that artifact having the effect of
depending on other jars?
The commons-net-2.0-ftp.jar is created not because of some maven
convention. Actually, the Commons-Net creates that jar just to separate
classes. The right way of doing that would be using separated modules, but
they are not doing that.
My suggestion? Keep that dependency and let your project with whatever
comes from that.
Regards,
Bruno
On Nov 12, 2008 1:47pm, Steven Jardine <[EMAIL PROTECTED]> wrote:
I have a project that uses the commons-net package. Well it actually uses
only the commons-net-2.0-ftp.jar file found at
http://repo1.maven.org/maven2/commons-net/commons-net/2.0/commons-net-2.0-ftp.jar.
It there a way for me to have my project depend on only this jar file not
the whole commons-net project. My current dependency is
commons-net
commons-netartifactId>
2.0
compile
Thanks,
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
