Why tapestry archtype project, when generated using maven and imported into
Eclipse, has much more dependencies than the ones separately downloadable
from tapestry's portal ?
Are you talking about any JAR downloaded by Maven or just the ones put in
the generated project classpath? If, for example, your .m2/repository
folder didn't exist or wasn't populated yet, Maven will download lots of
stuff used by itself.
On Wed, Jun 5, 2013 at 7:45 AM, Muhammad Gelbana
I'm talking about the generated classpath. I understand from your answer
that this is not possible or should not happen ?
I guess these libraries are for maven's sake as you suggested.
Thank you.
On Wed, Jun 5, 2013 at 1:44 PM, Thiago H. de Paula Figueiredo
thiag...@gmail.com wrote:
Are you
Which libraries are being added which you consider useless? Don't forget
that dependencies may have dependencies themselves, so Maven (or any other
tool that handles dependencies) has to deal with that too. In Eclipse, in
the POM editor, there's a dependency graph you can check. Of mvn
I can't remember the classpath entries generated by maven as I've disabled
maven dependencies but I remember seeing Apache xerces !
I guess maven just follow each dependency's dependencies in it's pom and
downloads\includes it automatically. Whats weird is that tapestry's
downloaded jars and
On Wed, 05 Jun 2013 10:12:59 -0300, Muhammad Gelbana m.gelb...@gmail.com
wrote:
I can't remember the classpath entries generated by maven as I've
disabled maven dependencies but I remember seeing Apache xerces !
Weird. I've never seen it in a Tapestry project.
I guess maven just follow