I cannot seem to get surefire to NOT load junit-3.8.1. None of my projects --
directly or transitively -- import junit-3.8.1, yet at runtime surefire adds
it to the classpath (in front of junit-dep-4.5 nonetheless).
Using --debug I can see the dependency tree of each project, none of which
I've even tried the 2.5-SNAPSHOT, which is supposed to address this issue --
but still junit-3.8.1 rules the day. I guess its time for some ant
tasks..
--
View this message in context:
http://www.nabble.com/How-to-get-surefire-to-use-junit-dep-4.5--tp20091464p20097148.html
Sent from the
I'm working with the 2.5/trunk checkout and my own build. I've removed all
the code that selects the various junits and hard-coded junit-dep. YET, I
still get junit-3.8.1 in the Test Classpath.
So maybe it some other maven-magic that is adding this jar. I have no idea
even where to begin. I'm
What is the value of importing into dependencyManagement if those
dependencies cannot then be refered to in the regular dependencies? I'm
missing the purpose/value.
--
View this message in context:
http://www.nabble.com/scope-import-and-dependencyManagement-tp19512161p19514217.html
Sent from
Can you post this plugin when you are thru. I need to create a Fitnesse
plugin, and need to also collect the full set of depenencies. An example
to start from would be nice.
thanks!
-barry
-
To unsubscribe, e-mail: [EMAIL
I would like to use a separate local repository for maven plugins and
application projects. Is this possible?
--
barry kaplan
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
Brett Porter wrote:
Not yet, but a bug was filed yesterday for a similar issue (per
project local repository, not a separate one for plugins as such).
What is your use case?
When trying to get a rather large set of project dependencies sorted
out, I frequently delete my local repository to
Kees de Kooter wrote:
Is it possible to control which output folders the eclipse plugin puts
into the .classpath file? I tried setting the outputDirectory property
in the plugin configuration but that did not have any effect.
I use this and it works:
build
pluginManagement
Allan Ramirez wrote:
Hi,
add the exclusions tag to your dependency
and put the artifacts you want to exclude.
For 72 dependencies! I think we need the ability to disable transitive
per dependency, or maybe a wildcard excludes pattern. I also dream of
the ability to have a top-level
Could there be anyway to specify this option on a dependency specific
basis?
I want to download just two or three of the dependency sources (which I
keep in a local repository), but m2 dragging on the other fifty
dependencies. And that is multiplied by a dozen or so projects. So what
was
Also, might there be a way to instead of downloading a source jar, tell
the eclipse plugin, for a particular dependency, that the source is
already in the eclipse workspace or on disk somewhere.
If I recall, this was possible with M1, but then the plugin architecture
was nowhere as decoupled
I am getting with the:
javax.xml.transform.TransformerFactoryConfigurationError: Provider
org.apache.xalan.processor.TransformerFactoryImpl not found
But only when running the test from maven/surefire. Using maven to
generate eclipse projects, and runnuing the test within eclipse the test
Sorry, this is with m2.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Is there any way to say /never/ include a specific dependency no matter
what? I need to get xml-apis out of my dependency list (its not needed
for 1.5?) but a whole gob of other project declare it as a dependency.
I'm trying to avoid having to repeat the exlusion in multiple places.
thanks
? Or is there a better way? Either to do what
I want, or should I want something else?
--
barry kaplan
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Alexandre Poitras wrote:
The plugin generates direct references between modules sharing the
same parent pom. So, you should try to make a multi-modules project.
Search for the mail Guide to using Eclipse with Maven 2.x, it has
helped me a lot and has some informations about this situation.
Hope
Mark Hobson wrote:
(Project A depends on project B; both SNAPSHOT versions; all mvn
commands done in reactor build)
* Delete A and B from local repo
* mvn install - SNAPSHOT jars created in local repo
* mvn eclipse:eclipse - project references created
* Delete B from local repo
* mvn install -
Ok, I've got direct eclipse project references now. The procedure below
worked perfectly. Thanks!!
-barry
Barry Kaplan wrote:
Mark Hobson wrote:
(Project A depends on project B; both SNAPSHOT versions; all mvn
commands done in reactor build)
* Delete A and B from local repo
* mvn install
In the eclipse plugin, EclipseUtils.findReactorProject() does the below
snippet when deciding whether a reactor project matches a dependency
artifact (and if so, a direct eclipse project dependency is created
instead of a repo jar depenency):
if ( project.getGroupId().equals(
Below is what I did to get a proper project to be created. Now I don't
really understand how snapshots are supposed to work, so I'm sure there
are problems with this solution. But at least it is creating proper
eclipse projects. Now I need to learn how to make a custom verson of a
plugin
Since I have a ton of test dependencies to manage, is there any
recommended workaround?
What I thinking of doing is simply not using tests dependencies, and
creating a issue to go back and change them once maven adds support for
test dependencies. Another option that I might consider (but it
I can't figure out what the below means. I'm running with full debug,
but get no idication as to /what/ is wrong. This pom is as trivial can
be. In fact I copied from another POM and only changed the groupid and
artifactid.
[WARNING] POM for: 'springframework:spring:pom:1.2.6' does not appear
Brett Porter wrote:
depenencies is missing a d.
-X should have output this error - you can file a bug for this to be included.
My hero! (http://jira.codehaus.org/browse/MNG-1404)
(I'm was using jedit to edit these poms until I generate working eclipse
projects, and I have not yet
Brett Porter wrote:
We deferred this until 2.1, as it was preferable to have a transitive
dependency-less solution in place for 2.0 rather than deferring the
whole feature.
Ah! I just spent an hour trying to figure out why this was not working.
I searched and searched and searched, but
Is more than one level of extends supported? I have four levels and
maven is complaining that pom.currentVersion is not defined. Its only
defined in the toplevel project.xml.
I wish the logging would indicate which files it was loading/parsing.
--
barry kaplan
[EMAIL PROTECTED
Just user foo. I must have been running from the wrong directory. It
appears that indeed maven supports n-level extends!
--
barry kaplan
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e
on how to handle this situation?
--
barry kaplan
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
downloading is seeing a null value for
the version. I have seen the following work:
dependency
groupIdgeronimo/groupId
artifactIdgeronimo-kernel/artifactId
version${pom.currentVersion}/version
/dependency
But is that because its a pom variable?
--
barry kaplan
[EMAIL
Brett Porter wrote:
you will need to put it into project.properties for that to work.
Seems that project.properties is not inherited to multiprojects (no?).
So this approach will not work for sharing version numbers across all
the subprojects.
--
barry kaplan
[EMAIL PROTECTED
the
project.properties to be used in the project.xml.
Thanks for the help Brett!
--
barry kaplan
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Brett Porter wrote:
It is inherited wherever project.xml is.
Yes, of course you are correct. What is not inherited is
'project.propeties' :-)
Thanks Brett! All works great now.
--
barry kaplan
[EMAIL PROTECTED]
-
To unsubscribe
Brett Porter wrote:
I'm not sure what you mean: project.properties IS inherited as long as
project.xml is.
'project.propeties' :-)
project.properties
I had a typo.
I just switched to the jar overrides, and its perfect. I'll let the
activemq and geronimo guys know. They were using entities for
32 matches
Mail list logo