Re: AW: Are profiles in published POMs a supported feature?
Christian Schlichtherle wrote (1) Profiles are part of the POM reference specification. I think it's important to distinguish between the Maven build file and the (tool independent?) module descriptor. As I see it, the POM reference specification is about the former. I'm looking for a specification for the latter so that we can make Gradle behave exactly like expected when dealing with Maven modules and their dependencies. Does Maven offer a self-contained library that generates a consumption-time view of the POM for the purpose of dependency resolution? Christian Schlichtherle wrote (2) Every POM is published somehow - at least to your local repository. No doubt about that, but does this speak against resolving profiles at publication time? I think there's already some POM transformation going on at publication time. For example, variables might get replaced 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/Are-profiles-in-published-POMs-a-supported-feature-tp5469611p5473432.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Are profiles in published POMs a supported feature?
The published POM for com.sun.jersey.jersey-test-framework:jersey-test-framework-core:1.11 (1) specifies additional dependencies in the cobertura and default profiles. Are profiles in published POMs an officially supported feature, and are they supposed to be resolved at consumption time? I wonder 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://search.maven.org/#artifactdetails%7Ccom.sun.jersey.jersey-test-framework%7Cjersey-test-framework-core%7C1.11%7Cjar -- View this message in context: http://maven.40175.n5.nabble.com/Are-profiles-in-published-POMs-a-supported-feature-tp5469611p5469611.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Exact meaning of -U command line option
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: http://maven.40175.n5.nabble.com/Exact-meaning-of-U-command-line-option-tp5119606p5119606.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Clarification on Central Sync Requirements
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) https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-6.CentralSyncRequirement -- View this message in context: http://maven.40175.n5.nabble.com/Clarification-on-Central-Sync-Requirements-tp3402730p3402730.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to declare that my plugin doesn't work with Maven 3?
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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3 no longer supporting dynamic configuration of plugins?
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. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3 no longer supporting dynamic configuration of plugins?
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. Only a few settings will afterwards be enhanced. Is there really no way to configure (parts of) a plugin dynamically in Maven 3? This would mean that my testing framework (http://spockframework.org) won't be able to offer some features for Maven 3 builds that it already offers today for Ant, Maven 2, and Gradle builds. Cheers, Peter -- View this message in context: http://maven.40175.n5.nabble.com/Maven-3-no-longer-supporting-dynamic-configuration-of-plugins-tp3279670p3286870.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven 3 no longer supporting dynamic configuration of plugins?
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 configures Surefire accordingly (by adding includes). With Maven 3, this technique no longer seems to work. I don't get any errors, but the plugins to be configured don't see any changes made to their configuration section, even if I perform the changes as early as in the initialize phase. Is this an intentional change? And what is the alternative? Cheers, Peter PS: Is there any documentation about writing plugins for Maven 3 (Guice DI, new APIs, breaking changes, etc.)? Can't find anything.
Maven 3 no longer supporting dynamic configuration of plugins?
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 configures Surefire accordingly (by adding includes). With Maven 3, this technique no longer seems to work. I don't get any errors, but the plugins to be configured don't see any changes made to their configuration section, even if I perform the changes as early as in the initialize phase. Is this an intentional change? And what is the alternative? Cheers, Peter PS: Is there any documentation about writing plugins for Maven 3 (Guice DI, new APIs, breaking changes, etc.)? Can't find anything. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-3-no-longer-supporting-dynamic-configuration-of-plugins-tp3279449p3279449.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Command line output when running JUnit 4 test suite
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 -- View this message in context: http://old.nabble.com/Command-line-output-when-running-JUnit-4-test-suite-tp28786362p28807935.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Command line output when running JUnit 4 test suite
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 right there: mvn test -Dtest=MyTest; cat target/surefire-reports/com.thingMyTest.txt This will only give me feedback (plus lots of noise) once the whole suite has completed, which is exactly what I'm trying to avoid. Cheers, Peter -- View this message in context: http://old.nabble.com/Command-line-output-when-running-JUnit-4-test-suite-tp28786362p28793392.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Command line output when running JUnit 4 test suite
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 whole suite (comprised of more than hundred test classes) has finished. This means I have to wait much longer until I get feedback. Cheers, Peter -- View this message in context: http://old.nabble.com/Command-line-output-when-running-JUnit-4-test-suite-tp28786362p28786362.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven-Surefire: Unable to run the Junits
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 JUnit4-style @Test annotations). Cheers, Peter sauravs wrote: Hi All, I am using Surefire to run my Junit tests for Eclipse based plug-ins. I keep getting the following error while running the tests. java.lang.exception no runnable methods Where in a have a TestSuite and the TestSuite has a test class. The test class ends with test and all the methods have @test annotations associated with it. I am using JUnit 4 and Eclipse 3.5. Please help me to resolve the problem. Thanks and Regards, Saurav -- View this message in context: http://old.nabble.com/Maven-Surefire%3A-Unable-to-run-the-Junits-tp28535615p28538374.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven-Surefire: Unable to run the Junit
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: http://old.nabble.com/Maven-Surefire%3A-Unable-to-run-the-Junits-tp28535615p28542411.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Shade Plugin: How to include artifacts and all their dependencies?
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: http://old.nabble.com/Shade-Plugin%3A-How-to-include-artifacts-and-all-their-dependencies--tp27279215p27279215.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Problem with maven-release-plugin
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 how to
solve this problem?
Cheers,
Peter
--
View this message in context:
http://old.nabble.com/Problem-with-maven-release-plugin-tp26421272p26421272.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Problem with maven-release-plugin
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 how to
solve this problem?
Cheers,
Peter
Re: Problem with maven-release-plugin
Are we talking about the same thing? Do you also have a module with a
dependency on your OWN maven plugin located in another module that is part of
the same release?
On 19.11.2009, at 14:00, Martin Schayna wrote:
We have same scenario. Release plugin only warns can't change version 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 to 0.3, but then fails
while processing B because it cannot find version 0.3 of A. Any ideas how to
solve this problem?
Cheers, Peter
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Cannot get dependency exclusion to work
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 groupIdspring-instrument-classloading/groupId /exclusion /exclusions /dependency Nevertheless, Maven always fails with: Missing: -- 1) org.springframework:spring-instrument-classloading:jar:3.0.0.RC1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.springframework -DartifactId=spring-instrument-classloading -Dversion=3.0.0.RC1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.springframework -DartifactId=spring-instrument-classloading -Dversion=3.0.0.RC1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.grails:grails-maven-plugin:maven-plugin:1.2-SNAPSHOT 2) org.grails:grails-scripts:jar:1.2-SNAPSHOT 3) org.grails:grails-core:jar:1.2-SNAPSHOT 4) org.springframework:spring-instrument-classloading:jar:3.0.0.RC1 -- 1 required artifact is missing. for artifact: org.grails:grails-maven-plugin:maven-plugin:1.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), Codehaus Snapshots (http://snapshots.repository.codehaus.org) What goes wrong here? Why is the exclusion not working? This is with Maven 2.2.0. Cheers, Peter -- View this message in context: http://www.nabble.com/Cannot-get-dependency-exclusion-to-work-tp26051992p26051992.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Cannot get dependency exclusion to work
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 the following exclusion to its POM: dependency groupIdorg.grails/groupId artifactIdgrails-scripts/artifactId version1.2-SNAPSHOT/version scoperuntime/scope exclusions exclusion artifactIdorg.springframework/artifactId groupIdspring-instrument-classloading/groupId /exclusion /exclusions /dependency Nevertheless, Maven always fails with: Missing: -- 1) org.springframework:spring-instrument-classloading:jar:3.0.0.RC1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.springframework -DartifactId=spring-instrument-classloading -Dversion=3.0.0.RC1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.springframework -DartifactId=spring-instrument-classloading -Dversion=3.0.0.RC1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.grails:grails-maven-plugin:maven-plugin:1.2-SNAPSHOT 2) org.grails:grails-scripts:jar:1.2-SNAPSHOT 3) org.grails:grails-core:jar:1.2-SNAPSHOT 4) org.springframework:spring-instrument-classloading:jar:3.0.0.RC1 -- 1 required artifact is missing. for artifact: org.grails:grails-maven-plugin:maven-plugin:1.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), Codehaus Snapshots (http://snapshots.repository.codehaus.org) What goes wrong here? Why is the exclusion not working? This is with Maven 2.2.0. Cheers, Peter -- View this message in context: http://www.nabble.com/Cannot-get-dependency-exclusion-to-work-tp26051992p26051992.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Cannot-get-dependency-exclusion-to-work-tp26051992p26052174.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Test fails but build successful - how is this possible?
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: http://www.nabble.com/Test-fails-but-build-successful---how-is-this-possible--tp25021541p25021541.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Test fails but build successful - how is this possible?
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 Niederwieser pnied...@gmail.comwrote: 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: http://www.nabble.com/Test-fails-but-build-successful---how-is-this-possible--tp25021541p25021541.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- La mélancolie c’est communiste Tout le monde y a droit de temps en temps La mélancolie n’est pas capitaliste C’est même gratuit pour les perdants La mélancolie c’est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c’est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.lastfm.fr/listen/user/jeffmaury/personal -- View this message in context: http://www.nabble.com/Test-fails-but-build-successful---how-is-this-possible--tp25021541p25021931.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Can plugins be removed from build lifecycle as of Maven 2.1?
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 (it's inherited from the parent POM). Is this possible as of Maven 2.1? I've found some talk about BuildPlanModifier on the web, but nothing concrete. Cheers, Peter -- View this message in context: http://www.nabble.com/Can-plugins-be-removed-from-build-lifecycle-as-of-Maven-2.1--tp23704925p23704925.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Why are projects deploying to repo1.maven.org not allowed to use plugins from other repositories?
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: http://www.nabble.com/Why-are-projects-deploying-to-repo1.maven.org-not-allowed-to-use-plugins-from-other-repositories--tp22847197p22847197.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven Central Repo and Java Package Names
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 Groovy's convention: org.spockframework.xxx for internal packages (I do own spockframework.org) spock.xxx for API packages (cf. groovy.xxx, scala.xxx, java.xxx; obviously, I can't ever own spock) Is this acceptable? Is this the right place to ask this question? Cheers, Peter -- View this message in context: http://www.nabble.com/Maven-Central-Repo-and-Java-Package-Names-tp7066p7066.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Central Repo and Java Package Names
nicolas de loof-2 wrote: The convention is to use the reverse domain name you own. What is the groovy convention you mention ? I will definitely use the reverse domain name as the Maven group ID. The Groovy convention I'm referring to is to name user-visible packages groovy.xxx, and internal packages org.codehaus.groovy.xxx. I'd like to do something similar for Spock (spock.xxx, org.spockframework.xxx). nicolas de loof-2 wrote: If groovy has other convention, feel free to package groovy.spock in org.spockframework : groovy-spock artifact. Cool, thanks for the info! Cheers, 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 naming convention. But in my particular case, it would be much more sensible to follow Groovy's convention: org.spockframework.xxx for internal packages (I do own spockframework.org) spock.xxx for API packages (cf. groovy.xxx, scala.xxx, java.xxx; obviously, I can't ever own spock) Is this acceptable? Is this the right place to ask this question? Cheers, Peter -- View this message in context: http://www.nabble.com/Maven-Central-Repo-and-Java-Package-Names-tp7066p7066.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Maven-Central-Repo-and-Java-Package-Names-tp7066p8395.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Is Maven / JUnit 4.x broken (annotations)
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: http://www.nabble.com/Is-Maven---JUnit-4.x-broken-%28annotations%29-tp20929389p21016664.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Is Maven / JUnit 4.x broken (annotations)
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. Cheers, Peter -- View this message in context: http://www.nabble.com/Is-Maven---JUnit-4.x-broken-%28annotations%29-tp20929389p21019558.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to get DependencyTreeBuilder in maven-embedder?
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 construct/retrieve a DependencyTreeBuilder in maven-embedder? -- View this message in context: http://www.nabble.com/How-to-get-DependencyTreeBuilder-in-maven-embedder--tp16025222s177p16025222.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is there a property for parent directory?
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 path every time.
Cheers
Peter
MALICE wrote:
Yes it is.
${parent} gives you a 'pom', on which you can access all properties that
you
can access directly (e.g. 'groupId', 'artifactId', 'version',
'packaging').
On Tuesday 11 September 2007 13:17, [EMAIL PROTECTED] wrote:
Is this ${parent} property generally available, i.e.
${parent.artifactId},
etc
It would help me refactor a number of places where I use something
similar
to this in a parent POM
properties
super.artifactId${artifactId}super.artifactId
/properties
Roland Asmann [EMAIL PROTECTED] wrote on 09/11/2007 06:49:55 AM:
Yes there is: ${parent.basedir} should be the one you need
Be carefull though, if your child-project are deeper than one level,
you
should use ${parent.parent.basedir} (and so on).
Isn't it possible for you to make a dependency of some kind to the
tools-project? Or build your tools as maven-plugins, that way you won't
need
the variables!
[snipped discussion of why...]
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended
solely
for the designated recipient(s). If an addressing or transmission error
has misdirected this email, please notify the sender immediately and
destroy this email. Any review, dissemination, use or reliance upon this
information by unintended recipients is prohibited. Any opinions
expressed in this email are those of the author personally.
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Is-there-a-property-for-parent-directory--tf4419146s177.html#a13139517
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to run maven goals from Eclipse?
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 create some unit tests for a minimal maven project. I want to do it in eclipse. -- View this message in context: http://www.nabble.com/How-to-run-maven-goals-from-Eclipse--tf4470584s177.html#a12767228 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
