If the dependencies are optional, my POM has to explicitly state the
dependencies
it wants. Kind of defeats the whole purpose of transitive dependencies, right?
There should simply be a seperate POM for each set of dependencies.
ex:
spring-orm-hibernate
spring-orm-jdo
spring-orm-toplink
etc...
Just to followup, i've posted an issue on JIRA for this:
http://jira.codehaus.org/browse/MEV-313
And here's the corrected link:
http://jroller.com/page/wireframe/?anchor=seperate_artifacts_for_seperate_dependencies
-
To unsubscr
Why oh why is it so painful to setup a new project?Transitive dependencies
are actually causing more pain than they are helping me. This is largely
due to the poor state of the spring POM's, but I think it's highly unrealistic
to expect new java projects to jump through the hoops of specifing
Thanks for the tip. Those settings create a source archive. I would also
like to deploy a zip binary distribution (dependencies included). I have
the assembly plugin configured correctly, but it didn't work to simply add
to my configuration. Can only certain plugins be attached to goals?
is there some way to configure the assembly plugin to run during the "deploy"
phase? I would like my project to always upload the latest source any time
the snapshots are deployed.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
are there any maven2 plugins available that build a distribution (zip, tar,
etc) that include all the project dependencies? including transitive
dependencies
as well?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional co
I see on the plugin matrix
(http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Matrix)
that a jnlp plugin is available for Maven2, but where can it be found?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
