with their
values. I can't find any definitive information on this though.
Cheers,
Peter
--
Peter Niederwieser
Principal Engineer, Gradleware
http://gradleware.com
Creator, Spock Framework
http://spockframework.org
Twitter: @pniederw
--
View this message in context:
http://maven.40175.n5.nabble.com
if that makes any
sense, and whether tools like Ivy and Gradle could even support this
(currently they don't).
Cheers,
Peter
--
Peter Niederwieser
Principal Engineer, Gradleware
http://gradleware.com
Creator, Spock Framework
http://spockframework.org
Twitter: @pniederw
(1)
http
mvn --help says (both in Maven 2.2.1 and 3.0.2):
...
-U,--update-snapshots Forces a check for updated releases and snapshots on
remote repositories
...
What is updated releases supposed to mean here?
Cheers,
Peter
--
View this message in context:
According to (1), every POM must have elements like licenses, scm and
developers. So far I've always put such information into the parent only.
Is this good enough, or do you expect us to physically put this information
into every single POM?
Cheers,
Peter
(1)
Is there a way to declare that my plugin doesn't work with Maven 3? If not, how
can I handle this programmatically? In other words, how can I find out which
version of Maven my plugin gets run with, so that I can throw an exception?
Cheers,
Peter
No Maven committers reading this list? Even a No would help.
Cheers,
Peter
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-no-longer-supporting-dynamic-configuration-of-plugins-tp3279670p3292542.html
Sent from the Maven - Users mailing list archive at Nabble.com.
jochen-2 wrote:
This is a good example of my belief, that it should be possible to
invoke other plugins dynamically by supplying an own configuration
section from your own plugin.
In my example, users still have to be able to configure all aspects of the
(Surefire) plugin themselves.
Over time, I have written several Maven plugins that configure other plugins by
manipulating their configuration section (with the Xpp3Dom API). This
technique has often proved to be a life saver. For example, I have a plugin
that determines dynamically which JUnit tests should be run, and
Over time, I have written several Maven plugins that configure other plugins
by manipulating their configuration section (with the Xpp3Dom API). This
technique has often proved to be a life saver. For example, I have a plugin
that determines dynamically which JUnit tests should be run, and
I've set useFile to false, and haven't set redirectTestOutputToFile (but it
defaults to false).
Nord, James-2 wrote:
Peter,
Could it be you have redirectTestOutputToFile set to true?
http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#redirectTestOutputToFile
--
klauer wrote:
The Maven Surefire plugin allows you to explicitly set a single test or
set of tests using wildcard matching:
I'm aware of -Dtest, but that's not what I want.
klauer wrote:
And as for your better command line output, why not just use the
command line
to output the test
Is there a way to get better command line output when running a JUnit 4 test
suite with Surefire? I'd like to get the same output as when running test
classes directly, but I only get the Running ... and Tests run: ...
output once for the whole suite, and failure output only appears after the
You should provide more information:
- Source code of your test suite
- Can you run the suite from Eclipse?
- etc.
If you asked me to guess, I'd say that for some reason, your tests are run
as JUnit3 tests, but there aren't any methods whose name starts with test
(because you've used
Right, that's another likely cause I've battled with in the past. Now my bet
is on this one. :-)
Christoph Kutzinski wrote:
Do you have classes with 'Test' in the name, but without any @Test
annotations - e.g..test helper classes
--
View this message in context:
I'd like to include a specific set of artifacts and all their transitive
dependencies. However, includes only includes the artifacts themselves,
but not their dependencies. Is there a way to achieve my goal?
Cheers,
Peter
--
View this message in context:
In my multi-module project, I have a Maven plugin A and a module B that uses
version ${project.version} of A (all modules have the same version number).
release:prepare changes version A from 0.3-SNAPSHOT to 0.3, but then fails
while processing B because it cannot find version 0.3 of A. Any ideas
In my multi-module project, I have a Maven plugin A and a module B that uses
version ${project.version} of A (all modules have the same version number).
release:prepare changes version A from 0.3-SNAPSHOT to 0.3, but then fails
while processing B because it cannot find version 0.3 of A. Any
on
dependent projects. Released deliveries are OK.
Martin Schayna
Peter Niederwieser wrote:
In my multi-module project, I have a Maven plugin A and a module B that uses
version ${project.version} of A (all modules have the same version number).
release:prepare changes version A from 0.3-SNAPSHOT
I'm trying to build grails-maven-plugin, and have added the following
exclusion to its POM:
dependency
groupIdorg.grails/groupId
artifactIdgrails-scripts/artifactId
version1.2-SNAPSHOT/version
scoperuntime/scope
exclusions
exclusion
artifactIdorg.springframework/artifactId
Thanks a lot, I just didn't spot this.
Stevo Slavic wrote:
Exclusion's groupId and artifactId values seem to be permuted.
Regards,
Stevo.
On Sun, Oct 25, 2009 at 10:29 PM, Peter Niederwieser
pnied...@gmail.comwrote:
I'm trying to build grails-maven-plugin, and have added
We have a situation where the tests in one module produce one error. However,
the build of this module, and the whole project, is nevertheless considered
successful. Any ideas how this is possible? We are using Maven 2.1.
Cheers,
Peter
--
View this message in context:
You mean testFailureIgnore? We definitely don't set this, not even in a
parent POM.
jeffma...@jeffmaury.com wrote:
The Surefire plugin has one parameter that, if set to true, can force
Maven
not to if the tests have failed.
Jeff MAURY
On Tue, Aug 18, 2009 at 11:41 AM, Peter
Background: I have the problem that maven-javadoc-plugin and
maven-jetty-plugin don't seem to like each other. As soon as
maven-javadoc-plugin is bound to a lifecycle phase, jetty:run produces a
ClassNotFoundException. As a workaround, I'd like to remove the javadoc
plugin for this one module
Say I need a plugin for my release process that's not available from
repo1.maven.org. How would the inclusion of a plugin repository affect the
users of my artifact? Or why else is it not allowed to add a plugin
repository?
Cheers,
Peter
--
View this message in context:
Hi,
I'm developing a language on top of Groovy and would eventually like to have
it synced to repo1.maven.org. Now I've read that there is a requirement for
all my package names to follow the reverse domain naming convention. But in
my particular case, it would be much more sensible to follow
,
Peter
On Thu, Feb 26, 2009 at 4:55 PM, Peter Niederwieser
pnied...@gmail.comwrote:
Hi,
I'm developing a language on top of Groovy and would eventually like to
have
it synced to repo1.maven.org. Now I've read that there is a requirement
for
all my package names to follow the reverse domain
CheapLisa wrote:
What you are saying is that the surefire plugin is not JUnit4 enabled?
Unfortunately, Surefire isn't capable of detecting JUnit 4 tests by itself.
You always have to adhere to some naming convention.
Cheers,
Peter
--
View this message in context:
John Stoneham wrote:
To be clearer - surefire will certainly detect JUnit 4 tests
I think you don't get the point. By detection we mean that given a base
directory, Surefire will find all test classes beneath it, w/o us having to
adhere to any naming convention. Surefire can't do this.
Hi,
I'm using maven-embedder (2.1) to analyze dependencies in our POMs.
MavenEmbedder.readProjectWithDependencies() doesn't give me all the
information I'm looking for.
org.apache.maven.shared.dependency.tree.DependencyTreeBuilder looks like a
better fit for my needs. But, how can I
Judging from a few experiments I did, ${parent} doesn't reference the parent
POM; rather, it references the parent element of the current POM. That's
why ${parent.basedir} doesn't work.
I hoped I could write something like url${parent.url}/subproject/url,
but it seems I have to specify the full
I use Wicked Shell to run Maven from within Eclipse.
http://www.wickedshell.net/
Cheers
Peter
sieg wrote:
I've been google searching and reading the books on devzuz and
www.sonatype
http://www.sonatype/ .
However, I cannot figure out how to run maven goals from eclipse. I want
to
31 matches
Mail list logo