If you take the user libraries and write all the dependencies to the pom, your
colleagues will not notice much a difference after a mvn eclipse:eclipse
The Javadoc is usually already in the maven repo. So if you take an artifact
from a public repo you will almost always find an attached sources.jar
artifact. The same applies if you release your own modules into a private
company repository.
So even debugging is not a problem.
LieGrü,
strub
--- Vickey <[EMAIL PROTECTED]> schrieb am Fr, 4.7.2008:
> I know it seems a quite weird demand, maven plugins should
> not depend on any
> ide, but the senario is, firstly, some developers in my
> team who have never
> used maven before have defined the dependencies with
> eclipse user libraries,
> secondery, javadoc and source location of dependencies
> seems not be able to
> be defined in pom.xml files, loading dependencies in such
> way just for the
> sake of the convenience eclipse----once javadoc and source
> code location are
> defined in user libraries, developers can open the api
> reference of the
> corresponding code with just a single press of
> "F1" in eclipse.
__________________________________________________________
Gesendet von Yahoo! Mail.
Dem pfiffigeren Posteingang.
http://de.overview.mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
