Aggregate reports
How may I run an aggregate dependencies report on a multi-module project? Thanks. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
Re: Re: dependency management within plugin dependencies
Sounds like a job for a . Wayne On 12/7/06, Gregory Kick <[EMAIL PROTECTED]> wrote: Federico, I'm aware of what it does... The question was regarding dependencies listed relative to a plugin. Wayne, The problem with is that I don't necessarily want a dependency for every invocation of the pluign. For example, say that have a plugin that uses the jaxb api and I want to use jaxb in some situations and jaxme in others. They have the same api so it might be reasonable to want a plugin to execute using one implementation in some instances and the other implementation in another. Additionally, I'd like to standardize the versions in the same way as I would with a typical dependency, so that I always use jaxb whatever-jaxb-version and jaxme whatever-jaxme-version. My first thought is that a dependency that is listed under a plugin should also utilize , but that seems to not be the case. And, since there's no under I wondered whether this was intentional or an oversight. Thoughts? On 12/7/06, Federico Yankelevich <[EMAIL PROTECTED]> wrote: > > Hi, > dependencyManagement is inherited by children POMs. > It is useful to define a dependency within dependencyManagement tag > expliciting the version there. > Then in the children POMs you can just declare your dependecy without having > the version tag > > have a look here: http://maven.apache.org/pom.html#Dependency%20Management > > bye, > Federico > > > Gregory Kick-2 wrote: > > > > I have a question about the behavior of the > > portion of a POM as it relates to plugin dependencies. > > > > Say I have: > > ... > > > > > > > > GROUP > > ARTIFACT > > > > > > > > ... > > > > And in some project that inherits from this pom, > > > > ... > > > > > > GROUP > > ARTIFACT > > > > > > ... > > > > will fail with a missing version. > > > > Is this the expected behavior or is this a bug? > > > > > > -- > > Gregory Kick > > [EMAIL PROTECTED] > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: http://www.nabble.com/dependency-management-within-plugin-dependencies-tf2772190s177.html#a7735149 > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Gregory Kick [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: dependency management within plugin dependencies
Federico, I'm aware of what it does... The question was regarding dependencies listed relative to a plugin. Wayne, The problem with is that I don't necessarily want a dependency for every invocation of the pluign. For example, say that have a plugin that uses the jaxb api and I want to use jaxb in some situations and jaxme in others. They have the same api so it might be reasonable to want a plugin to execute using one implementation in some instances and the other implementation in another. Additionally, I'd like to standardize the versions in the same way as I would with a typical dependency, so that I always use jaxb whatever-jaxb-version and jaxme whatever-jaxme-version. My first thought is that a dependency that is listed under a plugin should also utilize , but that seems to not be the case. And, since there's no under I wondered whether this was intentional or an oversight. Thoughts? On 12/7/06, Federico Yankelevich <[EMAIL PROTECTED]> wrote: Hi, dependencyManagement is inherited by children POMs. It is useful to define a dependency within dependencyManagement tag expliciting the version there. Then in the children POMs you can just declare your dependecy without having the version tag have a look here: http://maven.apache.org/pom.html#Dependency%20Management bye, Federico Gregory Kick-2 wrote: > > I have a question about the behavior of the > portion of a POM as it relates to plugin dependencies. > > Say I have: > ... > > > > GROUP > ARTIFACT > > > > ... > > And in some project that inherits from this pom, > > ... > > > GROUP > ARTIFACT > > > ... > > will fail with a missing version. > > Is this the expected behavior or is this a bug? > > > -- > Gregory Kick > [EMAIL PROTECTED] > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/dependency-management-within-plugin-dependencies-tf2772190s177.html#a7735149 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gregory Kick [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Unrecognised tag: 'unpackOptions' with maven-assembly-plugin
I'm using version 2.1 of maven-assembly-plugin. The documentaion on the assembly saids I can have unpackOptions tag in the dependencySet but I get an "Unrecognised tag: 'unpackOptions' " error. Here's the stack trace: org.apache.maven.lifecycle.LifecycleExecutionException: Error reading descriptor at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Error reading descriptor at org.apache.maven.plugin.assembly.AbstractAssemblyMojo.getAssembly(Abstra ctAssemblyMojo.java:839) at org.apache.maven.plugin.assembly.AbstractAssemblyMojo.getAssembly(Abstra ctAssemblyMojo.java:814) at org.apache.maven.plugin.assembly.AbstractAssemblyMojo.readAssemblies(Abs tractAssemblyMojo.java:742) at org.apache.maven.plugin.assembly.AbstractAssemblyMojo.execute(AbstractAs semblyMojo.java:233) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:534) ... 16 more Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: Unrecognised tag: 'unpackOptions' (position: START_TAG seen ...\r\n \r\n ... @11:23) at org.apache.maven.plugins.assembly.model.io.xpp3.AssemblyXpp3Reader.parse DependencySet(AssemblyXpp3Reader.java:638) at org.apache.maven.plugins.assembly.model.io.xpp3.AssemblyXpp3Reader.parse Assembly(AssemblyXpp3Reader.java:456) at org.apache.maven.plugins.assembly.model.io.xpp3.AssemblyXpp3Reader.read( AssemblyXpp3Reader.java:1717) at org.apache.maven.plugins.assembly.model.io.xpp3.AssemblyXpp3Reader.read( AssemblyXpp3Reader.java:1728) at org.apache.maven.plugin.assembly.AbstractAssemblyMojo.getAssembly(Abstra ctAssemblyMojo.java:829) ... 21 more The pom: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 play.ejb play-ejb jar 1.0-SNAPSHOT play-ejb http://maven.apache.org org.springframework spring 2.0 compile junit junit 3.8.1 test maven-assembly-plugin assembly package assembly src/assemble/src.xml The assembly: jar-with-dependencies jar false true *.properties target/classes
NMaven podling started in the incubator
Hi all, An FYI for those who are interested - the PMC have voted to accept NMaven (.NET support for Maven) into the incubator, and to work to incorporate all our existing sandbox efforts into it. The proposal is here: http://maven.apache.org/proposals/incubator/ nmaven.html The lists have been created and can be found on the status file here: http://incubator.apache.org/projects/nmaven.html We hope any interested parties will come along and get involved. (Please direct any replies to dev@maven.apache.org, rather than the users list which I am cross-posting this to). Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Test failure
when looking for error stack traces do not execute mvn -e test go for somthing like: mvn -Dsurefire.useFile=false test Andy On 7 Dec 2006, at 18:40, Allan Valeriano wrote: Hi all, I'm having some problems running "mvn test". I'm receiving failure at one of my tests, but when I run it with stacktraces turned on, the exceptions are not related to what I'm testing. Instead, I receive the following error: [INFO] - --- [ERROR] BUILD FAILURE [INFO] - --- [INFO] There are test failures. [INFO] - --- [INFO] Trace org.apache.maven.BuildFailureException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:555) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle (DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures (DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: 115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced (Launcher.java :315) at org.codehaus.classworlds.Launcher.launch(Launcher.java: 255) at org.codehaus.classworlds.Launcher.mainWithExitCode( Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures. at org.apache.maven.plugin.surefire.SurefirePlugin.execute( SurefirePlugin.java:403) at org.apache.maven.plugin.DefaultPluginManager.executeMojo( DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:534) ... 16 more I've been looking for it on google, but couldn't find any conclusive help. Does anybody knows why is this error happening? thanks in advance Allan Valeriano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: User-defined phase
I generally abuse Ant for these kinds of things rather than Maven... Wayne On 12/7/06, Eric Redmond <[EMAIL PROTECTED]> wrote: The phases are community defined, and there are no plans to ever change that. This is why Maven is easy to understand and use wherever you go - rather than having to learn a bunch of "custom" stuff. If you really want to coallate your work into a single command, try using the "exec" goal: http://mojo.codehaus.org/exec-maven-plugin/ Eric On 12/7/06, Deluigi Marcus <[EMAIL PROTECTED]> wrote: > > Hi > > I want to abuse maven to perform a setup for a testing environment, such > as starting derby, starting a tomcat and deploying a WAR file which is > another project. > > Maven does a fine job in downloading all the required software if > necessary and building the WAR file which it is another project. > Besides, it is platform independent, so I am using it for all these > tasks. > > But I don't want to enter all these commands on the command line all the > time. I think a much nicer way would be to add a custom phase (such as > 'start-environment') to the module. When I am developing, I would like > to be able to execute only this phase, without the life-cycle. > > Is something like that possible? > Of course, I can make a shell-script but I think adding a custom phase > to the project would be a nice thing. > > > > Greetings > Marcus > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Eric Redmond http://codehaus.org/~eredmond - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tagging a maven project in sourceforge with release:prepare fails with this message
Just in case it's useful for someone, I've found the "curious" solution to this weird problem within the SF tracker after being knocking my head against the screen for some time... http://sourceforge.net/tracker/index.php?func=detail&aid=1599910&group_id=1&atid=21 David 2006/12/6, David <[EMAIL PROTECTED]>: Hi, As you can see, there is a commit in the second line that is executed perfectly (I have checked it at my svn repository in sourceforge), but the 4th line which should create a new directory under "tags" for the release being cooked, fails with a 403 :( Any clue? [INFO] Checking in modified POMs... [INFO] Executing: svn --username nimeacuerdo --password * --non-interactive commit --file /tmp/maven-scm-523270409.commit /Users/david/Documents/eclipseworkspace/mavenium/pom.xml [INFO] Working directory: /Users/david/Documents/eclipseworkspace/mavenium [INFO] Tagging release with the label mavenium-0.1... [INFO] Executing: svn --username nimeacuerdo --password * --non-interactive copy --file /tmp/maven-scm-884527461.commit . https://svn.sourceforge.net/svnroot/mavenium/tags/mavenium-0.1 [INFO] Working directory: /Users/david/Documents/eclipseworkspace/mavenium [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: COPY of mavenium-0.1: 403 Forbidden (https://svn.sourceforge.net) [INFO] TIA - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven proxy question
On 12/8/06, Christian Goetze <[EMAIL PROTECTED]> wrote: I am using the maven proxy as described in http://docs.codehaus.org/display/MAVENUSER/Using+Maven+in+a+corporate+environment, but I am observing spurious build failures due to some of the actual remote sites not always responding in a timely manner. Is there a way to configure maven proxy to not fail, but to simply send the cached version instead? Should I just set the cache timeout to some really large value? What I would like, though, is that it does try to get an update, but not fail if the update fails? Can you paste in the types of build failures you are getting? I haven't looked in our logs for a long time. Having a quick browse I am seeing 2006-12-07 16:31:43,168 [WARN ] commons.httpclient.HttpMethodBase - Error getting URI host org.apache.commons.httpclient.HttpException: Redirect from host www.ibiblio.org to mirrors.ibiblio.org is not supported at org.apache.commons.httpclient.HttpMethodBase.checkValidRedirect(HttpMethodBase.java:1237) at org.apache.commons.httpclient.HttpMethodBase.processRedirectResponse(HttpMethodBase.java:1185) But my builds are still working... Archiva will eventually superced mvn-proxy. But Archiva isn't ready for general use yet. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Assembly problem
On 12/7/06, Bob Arnott <[EMAIL PROTECTED]> wrote: Hello list, I've got an issue with the assembly plugin, I'm getting this error: Embedded error: Unrecognised tag: 'dependencySets' (position: START_TAG seen ...\r\n That doesn't seem to match up with what you posted, which has no tag. In addition, as Bram mentioned, the xml you posted is not well formed. (Your closing tag is missing the /.) Is the documentation wrong...? Basically I've got a multi module build and I would like one binary and one source assembly. I've got the source one, that was easy, but I would like the binary one to be like: Be aware that the documentation you see on the site is for the latest snapshot, and may include unreleased features. They *should* be marked "since [version]" but it's possible we've missed some. First, fix your XML and see if that helps. Also, run mvn with -U to make sure you've got the latest release of the assembly plugin, or add a to your pom. When you get it working, please consider adding an example to the plugin wiki. The assembly plugin's page is here: http://docs.codehaus.org/display/MAVENUSER/Assembly+Plugin I'm still one or two assembly plugin versions back, because the descriptor format changed and I haven't had time to re-do the descriptors for my projects. :( -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Assembly problem
Hi Bob,
may I suggest using an editor that understand/validates xml? Eg. eclipse,
jEdit or just good old vim ;) The assembly xml u posted below is not well
formed
regards,
Bram
> -Original Message-
> From: Bob Arnott [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 07, 2006 6:36 PM
> To: Maven Users List
> Subject: Assembly problem
>
> Hello list, I've got an issue with the assembly plugin, I'm
> getting this
> error:
>
> [INFO] [assembly:assembly]
> [INFO]
> --
> --
> [ERROR] BUILD ERROR
> [INFO]
> --
> --
> [INFO] Error reading descriptor
>
> Embedded error: Unrecognised tag: 'dependencySets' (position:
> START_TAG seen ...\r\n >... @58:25)
> [INFO]
> --
> --
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error
> reading descriptor
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa
> ls(DefaultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeSta
> ndaloneGoal(DefaultLifecycleExecutor.java:488)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa
> l(DefaultLifecycleExecutor.java:458)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa
> lAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTas
> kSegments(DefaultLifecycleExecutor.java:219)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(De
> faultLifecycleExecutor.java:140)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
> orImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
> odAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at
> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException:
> Error reading descriptor
> at
> org.apache.maven.plugin.assembly.AbstractAssemblyMojo.getAssem
> bly(AbstractAssemblyMojo.java:839)
> at
> org.apache.maven.plugin.assembly.AbstractAssemblyMojo.getAssem
> bly(AbstractAssemblyMojo.java:814)
> at
> org.apache.maven.plugin.assembly.AbstractAssemblyMojo.readAsse
> mblies(AbstractAssemblyMojo.java:742)
> at
> org.apache.maven.plugin.assembly.AbstractAssemblyMojo.execute(
> AbstractAssemblyMojo.java:233)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(Defau
> ltPluginManager.java:412)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa
> ls(DefaultLifecycleExecutor.java:534)
> ... 16 more
> Caused by:
> org.codehaus.plexus.util.xml.pull.XmlPullParserException:
> Unrecognised tag: 'dependencySets' (position: START_TAG seen
> ...\r\n... @58:25)
> at
> org.apache.maven.plugins.assembly.model.io.xpp3.AssemblyXpp3Re
> ader.parseModuleBinaries(AssemblyXpp3Reader.java:1022)
> at
> org.apache.maven.plugins.assembly.model.io.xpp3.AssemblyXpp3Re
> ader.parseModuleSet(AssemblyXpp3Reader.java:1103)
> at
> org.apache.maven.plugins.assembly.model.io.xpp3.AssemblyXpp3Re
> ader.parseAssembly(AssemblyXpp3Reader.java:393)
> at
> org.apache.maven.plugins.assembly.model.io.xpp3.AssemblyXpp3Re
> ader.read(AssemblyXpp3Reader.java:1717)
> at
> org.apache.maven.plugins.assembly.model.io.xpp3.AssemblyXpp3Re
> ader.read(AssemblyXpp3Reader.java:1728)
> at
> org.apache.maven.plugin.assembly.AbstractAssemblyMojo.getAssem
> bly(AbstractAssemblyMojo.java:829)
> ... 21 more
>
> Now
> http://maven.apache.org/plugins/maven-assembly-plugin/assembly
> .html says that I can have a like:
>
>
>bin
>
> tar.gz
> zip
>
>
>
>
> ${groupId}:${artifactId}
> ${groupId}:${artifactId}
>
>
>
>
>
> libs
> runtime
>
>${groupId}:${artifactId}
>
>
>
>
>
>
>
>
> Is the documentation wrong...? Basically I've got a multi
> module build and I would like one b
RE: skipping tests
I had another thought, in the configuration section of each pom,
couldn't I do something like this:
org.apache.maven.plugins
maven-surefire-plugin
${modulename.test}
Then in the profiles.xml file, the default active profile could have all
the ${module.name} equal to false and people could use their profiles in
their settings.xml to set these to true if they want to skip?
-Original Message-
From: Heck, Joe [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 07, 2006 4:49 PM
To: Maven Users List
Subject: RE: skipping tests
Heh - I know the feeling. I'm basing this on some examples and
discussion I found on running functional tests integrated into a Maven2
build. Not exactly what you're wanting, but the "on/off" switch
mechanism could be used almost identically.
I'm not a guru on making profiles work, but the gist would be to put all
the unit tests into a module under your master build, and instead of
defining them in the ... XML stanza of the POM, set
it up in the ... section. As an example:
example-jar
example-war
...
functional-test
enableCiProfile
true
functional-test
And then when you wanted to invoke including that module in the "build",
you'd simple invoke the profile on the command line. i.e.
mvn clean test -P functional-test
Does that help?
-joe
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of EJ Ciramella
Sent: Thursday, December 07, 2006 12:42 PM
To: Maven Users List
Subject: RE: skipping tests
Sorry - this makes my eyes go googly - can you explain a bit more in
detail?
We have everything modularized, but typically build from the topmost
level of the project. I was hoping to find a
-Dmaven.test.skipthese= kind of a solution.
>From the commandline would be the best option. Specifying a profile via
the commandline would be second best.
-Original Message-
From: Heck, Joe [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 07, 2006 3:29 PM
To: Maven Users List
Subject: RE: skipping tests
If you bundle your tests into modules, you can define which modules are
dependencies with a profile, and then drive their "run/not run" based on
whether or not a profile is defined.
-joe
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of EJ Ciramella
Sent: Thursday, December 07, 2006 12:26 PM
To: Maven Users List
Subject: skipping tests
So I know about the:
-Dmaven.test.skip=true
setting, but is there a way to skip packages or modules worth of tests?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: skipping tests
Heh - I know the feeling. I'm basing this on some examples and discussion I found on running functional tests integrated into a Maven2 build. Not exactly what you're wanting, but the "on/off" switch mechanism could be used almost identically. I'm not a guru on making profiles work, but the gist would be to put all the unit tests into a module under your master build, and instead of defining them in the ... XML stanza of the POM, set it up in the ... section. As an example: example-jar example-war ... functional-test enableCiProfile true functional-test And then when you wanted to invoke including that module in the "build", you'd simple invoke the profile on the command line. i.e. mvn clean test -P functional-test Does that help? -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of EJ Ciramella Sent: Thursday, December 07, 2006 12:42 PM To: Maven Users List Subject: RE: skipping tests Sorry - this makes my eyes go googly - can you explain a bit more in detail? We have everything modularized, but typically build from the topmost level of the project. I was hoping to find a -Dmaven.test.skipthese= kind of a solution. >From the commandline would be the best option. Specifying a profile via the commandline would be second best. -Original Message- From: Heck, Joe [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 3:29 PM To: Maven Users List Subject: RE: skipping tests If you bundle your tests into modules, you can define which modules are dependencies with a profile, and then drive their "run/not run" based on whether or not a profile is defined. -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of EJ Ciramella Sent: Thursday, December 07, 2006 12:26 PM To: Maven Users List Subject: skipping tests So I know about the: -Dmaven.test.skip=true setting, but is there a way to skip packages or modules worth of tests? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: what dependency is bringing in this artifact?
On 12/7/06, spamsucks <[EMAIL PROTECTED]> wrote: I have a project that uses a lot of dependencies (spring, hibernate, axis, etc..) My war file ends up containing multiple versions of some files (e.g. xerces-2.4.0.jar and xercesImpl-2.4.0 or xmlParserAPIs-2.2.1 and xml-apis-1.0.b2.api) I would like to set an exclusion for these in my pom, but I don't know where these dependencies are coming from. Is there a way to figure out what is bringing these in? Build the site and look at the dependencies report, or run mvn with -X and look at the indented tree view of the dependencies. (You'll probably want to redirect it to a file and view it in something that doesn't wrap lines.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
what dependency is bringing in this artifact?
I have a project that uses a lot of dependencies (spring, hibernate, axis, etc..) My war file ends up containing multiple versions of some files (e.g. xerces-2.4.0.jar and xercesImpl-2.4.0 or xmlParserAPIs-2.2.1 and xml-apis-1.0.b2.api) I would like to set an exclusion for these in my pom, but I don't know where these dependencies are coming from. Is there a way to figure out what is bringing these in? thanks for your help. phillip - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: skipping tests
Sorry - this makes my eyes go googly - can you explain a bit more in detail? We have everything modularized, but typically build from the topmost level of the project. I was hoping to find a -Dmaven.test.skipthese= kind of a solution. >From the commandline would be the best option. Specifying a profile via the commandline would be second best. -Original Message- From: Heck, Joe [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 3:29 PM To: Maven Users List Subject: RE: skipping tests If you bundle your tests into modules, you can define which modules are dependencies with a profile, and then drive their "run/not run" based on whether or not a profile is defined. -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of EJ Ciramella Sent: Thursday, December 07, 2006 12:26 PM To: Maven Users List Subject: skipping tests So I know about the: -Dmaven.test.skip=true setting, but is there a way to skip packages or modules worth of tests? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
releases on multi-module project with different scm urls
i have an application project that owns one child module, but both live in different locations in cvs. the app is atree/App whild the child is ctree/Module, so right away we can see we're dealing with "the hierarchy is flat" thinking. the flat heirarchy is inescapable at this time, and really provides a nice logical separation anyway, so the goal is to preserve it. in order to facilitate using scm:checkout after atree/App is checked out using a cvs client or commandline, i created a checkout.pom which contains the scmurl to the ctree/Module and thus checks it out into atree/App. after that, the usual atree/App/pom.xml can do most everything with atree/App/Module that it needs to...except release:perform. release:prepare succeeds in creating a release.properties file that contains the following significant lines: scm.url=scm\:cvs\:pserver\:username\:@mycvs\:/cvs\:atree/App project.scm.atree\:App.connection=scm\:cvs\:pserver\:username\:@mycvs\:/cvs\:atree/App project.scm.ctree\:Module.connection=scm\:cvs\:pserver\:username\:@mycvs\:/cvs\:ctree/Module obviously, when release:perform does its checkout into target/checkout, it uses the scm.url thereby missing out on the child module code altogether, so the remainder of release:perform fails when it can't find an atree/App/Module/pom.xml to work with. but what about those project.scm urls? why doesn't the release plugin use those when it retrieves the App and Module? both of those values come from the respective scm sections in the pom.xmls and are where the code actually lives...couldn't the release plugin realize which is the parent project's scm url, check it out as target/checkout, and then check out all the child projects into target/checkout (with all checkouts done using the release tag)? this is killing me...i've tried all manner of plugin configs and executions to coerce maven into checking out the child modules with no success. worse, i've realized that even if i had gotten any of my child checkout attempts to succeed, it wouldn't have been the correct, tagged version, it would have been the HEAD. i tried using maven-release-plugin-2.0.5-SNAPSHOT, but that version is from June and didn't solve anything. has anyone else had any success in doing multi-module releases with flat modules? thanks, jdc -- View this message in context: http://www.nabble.com/releases-on-multi-module-project-with-different-scm-urls-tf2776836s177.html#a7746955 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: skipping tests
If you bundle your tests into modules, you can define which modules are dependencies with a profile, and then drive their "run/not run" based on whether or not a profile is defined. -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of EJ Ciramella Sent: Thursday, December 07, 2006 12:26 PM To: Maven Users List Subject: skipping tests So I know about the: -Dmaven.test.skip=true setting, but is there a way to skip packages or modules worth of tests? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
skipping tests
So I know about the: -Dmaven.test.skip=true setting, but is there a way to skip packages or modules worth of tests?
Re: Test failure
On Thursday 07 December 2006 13:42, Wendy Smoak wrote: > On 12/7/06, Allan Valeriano <[EMAIL PROTECTED]> wrote: > > I'm having some problems running "mvn test". I'm receiving failure at one > > of my tests, but when I run it with stacktraces turned on, the exceptions > > are not related to what I'm testing. Instead, I receive the following > > error: > > ... > > > I've been looking for it on google, but couldn't find any conclusive > > help. Does anybody knows why is this error happening? > > Look in target/surefire-reports/*.txt for the test output, or build > the site with test failures ignored and the surefire report enabled to > get html output. Or configure the surefire plugin in your pluginManagement section to have: org.apache.maven.plugins maven-surefire-plugin brief false Then the stacktraces will go to the console as well. Much more useful for developers. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Test failure
On 12/7/06, Allan Valeriano <[EMAIL PROTECTED]> wrote: I'm having some problems running "mvn test". I'm receiving failure at one of my tests, but when I run it with stacktraces turned on, the exceptions are not related to what I'm testing. Instead, I receive the following error: ... I've been looking for it on google, but couldn't find any conclusive help. Does anybody knows why is this error happening? Look in target/surefire-reports/*.txt for the test output, or build the site with test failures ignored and the surefire report enabled to get html output. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Test failure
Hi all, I'm having some problems running "mvn test". I'm receiving failure at one of my tests, but when I run it with stacktraces turned on, the exceptions are not related to what I'm testing. Instead, I receive the following error: [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. [INFO] [INFO] Trace org.apache.maven.BuildFailureException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:555) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java :315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode( Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures. at org.apache.maven.plugin.surefire.SurefirePlugin.execute( SurefirePlugin.java:403) at org.apache.maven.plugin.DefaultPluginManager.executeMojo( DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:534) ... 16 more I've been looking for it on google, but couldn't find any conclusive help. Does anybody knows why is this error happening? thanks in advance Allan Valeriano
RE: When to initialize bean properties?
Please ignore - sent to wrong forum accidentally.
Naresh
-Original Message-
From: Naresh Bhatia
Sent: Thursday, December 07, 2006 1:21 PM
To: 'Maven Users List'
Subject: When to initialize bean properties?
I have a bean property that is displayed on a page. The value of the
property needs to be initialized by making a service layer call. When
should this initialization be done? Currently I am doing a lazy
initialization when the property is first accessed:
public class ForumDetailsBean {
private ForumDetailsVO forum;
public ForumDetailsVO getForum() {
if (forum == null) {
forum = forumService.getForumDetails(forumId);
}
return forum;
}
public void setForum(ForumDetailsVO forum) {
this.forum = forum;
}
}
In other component frameworks I have used (e.g. asp.net), such
initialization is done on page load events. What is the recommended JSF
way? (BTW, my bean is in request scope).
Naresh
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Firewall/proxy issues
By copying my repository from the windows box, I was able to determine that the settings are correctly being acquired. The problem appears to be with some interaction with the wagon client. I'll take this issue on over to that list. On 12/7/06, Mykel Alvis <[EMAIL PROTECTED]> wrote: Heh. That's a chicken and egg problem. The help plugin doesn't come with the base install, so getting it to debug the method I'm using to get plugins is a little problematic. :) Hmm... I guess I could look at using a windows machine as a proxy for my connection just to get the plugins, though. Thanks! On 12/7/06, Aaron Digulla <[EMAIL PROTECTED]> wrote: > > > > Mykel Alvis-2 wrote: > > > > The Linux build boxes, with the exact same file for settings, will > not. > > > > Does mvn help:effective-settings show your proxy settings? > > Also, you may try to install a dummy/forwarding proxy which logs all > traffic > to see what the two talk with each other. > > Regards, > > -- > Aaron Digulla > -- > View this message in context: http://www.nabble.com/Firewall-proxy-issues-tf2771836s177.html#a7738866 > > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- I'm just an unfrozen caveman software developer. I don't understand your strange, "modern" ways. -- I'm just an unfrozen caveman software developer. I don't understand your strange, "modern" ways.
maven proxy question
I am using the maven proxy as described in http://docs.codehaus.org/display/MAVENUSER/Using+Maven+in+a+corporate+environment, but I am observing spurious build failures due to some of the actual remote sites not always responding in a timely manner. Is there a way to configure maven proxy to not fail, but to simply send the cached version instead? Should I just set the cache timeout to some really large value? What I would like, though, is that it does try to get an update, but not fail if the update fails? -- cg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
When to initialize bean properties?
I have a bean property that is displayed on a page. The value of the
property needs to be initialized by making a service layer call. When
should this initialization be done? Currently I am doing a lazy
initialization when the property is first accessed:
public class ForumDetailsBean {
private ForumDetailsVO forum;
public ForumDetailsVO getForum() {
if (forum == null) {
forum = forumService.getForumDetails(forumId);
}
return forum;
}
public void setForum(ForumDetailsVO forum) {
this.forum = forum;
}
}
In other component frameworks I have used (e.g. asp.net), such
initialization is done on page load events. What is the recommended JSF
way? (BTW, my bean is in request scope).
Naresh
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Assembly problem
Hello list, I've got an issue with the assembly plugin, I'm getting this
error:
[INFO] [assembly:assembly]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error reading descriptor
Embedded error: Unrecognised tag: 'dependencySets' (position: START_TAG seen
...\r\n... @58:25)
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error reading descriptor
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:219)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error reading
descriptor
at
org.apache.maven.plugin.assembly.AbstractAssemblyMojo.getAssembly(AbstractAssemblyMojo.java:839)
at
org.apache.maven.plugin.assembly.AbstractAssemblyMojo.getAssembly(AbstractAssemblyMojo.java:814)
at
org.apache.maven.plugin.assembly.AbstractAssemblyMojo.readAssemblies(AbstractAssemblyMojo.java:742)
at
org.apache.maven.plugin.assembly.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:233)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
... 16 more
Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException:
Unrecognised tag: 'dependencySets' (position: START_TAG seen
...\r\n... @58:25)
at
org.apache.maven.plugins.assembly.model.io.xpp3.AssemblyXpp3Reader.parseModuleBinaries(AssemblyXpp3Reader.java:1022)
at
org.apache.maven.plugins.assembly.model.io.xpp3.AssemblyXpp3Reader.parseModuleSet(AssemblyXpp3Reader.java:1103)
at
org.apache.maven.plugins.assembly.model.io.xpp3.AssemblyXpp3Reader.parseAssembly(AssemblyXpp3Reader.java:393)
at
org.apache.maven.plugins.assembly.model.io.xpp3.AssemblyXpp3Reader.read(AssemblyXpp3Reader.java:1717)
at
org.apache.maven.plugins.assembly.model.io.xpp3.AssemblyXpp3Reader.read(AssemblyXpp3Reader.java:1728)
at
org.apache.maven.plugin.assembly.AbstractAssemblyMojo.getAssembly(AbstractAssemblyMojo.java:829)
... 21 more
Now http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html says
that I can have a like:
bin
tar.gz
zip
${groupId}:${artifactId}
${groupId}:${artifactId}
libs
runtime
${groupId}:${artifactId}
Is the documentation wrong...? Basically I've got a multi module build and I
would
like one binary and one source assembly. I've got the source one, that was easy,
but I would like the binary one to be like:
binary.zip
module1.jar
module2.jar
libs
module1 deps
module2 deps
docs
generated by site:site
So how do I do it if I can't use a tag...?
Cheers,
--
Bob Arnott
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Build fails on Linux 64Bit
well, you'd need to post the test result On 12/7/06, Ulrich Metzger <[EMAIL PROTECTED]> wrote: There is at least one test which fails on Linux 64Bit with jrockit-R26.4.0-jdk1.5.0_06 JDK installed. Running org.apache.maven.archiva.reporting.reporter.ChecksumArtifactReporterTest Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.261 sec <<< FAILURE! Running org.apache.maven.archiva.reporting.processor.DuplicateArtifactFileReportProcessorTest artifact = groupId:artifactId:jar:1.0-alpha-1 On Windows the build passes. Does anyone know how to get this fixed? Uli -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride
RE: mvn and JUnit 4.1
> Hi, we use JUnit 4.1 in eclipse, but when we run the tests > from the cmd line with mvn, it seems to fail and not use > JUnit 4.1 but it uses the old 3.8.1. > > Is there some way to force mvn to use JUnit 4.1? > > The mvn release is 2.0.4 we are using. Hi Davis, there is no support AFAIK. You can monitor this issue here: http://jira.codehaus.org/browse/SUREFIRE-31 regards, Bram - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn and JUnit 4.1
On 12/7/06, Davis Ford <[EMAIL PROTECTED]> wrote: Hi, we use JUnit 4.1 in eclipse, but when we run the tests from the cmd line with mvn, it seems to fail and not use JUnit 4.1 but it uses the old 3.8.1. Is there some way to force mvn to use JUnit 4.1? In general, add a on the junit version you want it to use. However, as Any mentioned, JUnit 4 features aren't supported yet. Google turned this up. I haven't tried it. http://wiki.unto.net/Maven_JUnit4_plugin -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn and JUnit 4.1
Currently maven does not support Junit 4 in the surefire plugin (default test framework) there is a JIRA for it so you can go and vote for it :) Andy Davis Ford wrote: Hi, we use JUnit 4.1 in eclipse, but when we run the tests from the cmd line with mvn, it seems to fail and not use JUnit 4.1 but it uses the old 3.8.1. Is there some way to force mvn to use JUnit 4.1? The mvn release is 2.0.4 we are using. Thanks in advance, Davis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mvn and JUnit 4.1
Hi, we use JUnit 4.1 in eclipse, but when we run the tests from the cmd line with mvn, it seems to fail and not use JUnit 4.1 but it uses the old 3.8.1. Is there some way to force mvn to use JUnit 4.1? The mvn release is 2.0.4 we are using. Thanks in advance, Davis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Firewall/proxy issues
Heh. That's a chicken and egg problem. The help plugin doesn't come with the base install, so getting it to debug the method I'm using to get plugins is a little problematic. :) Hmm... I guess I could look at using a windows machine as a proxy for my connection just to get the plugins, though. Thanks! On 12/7/06, Aaron Digulla <[EMAIL PROTECTED]> wrote: Mykel Alvis-2 wrote: > > The Linux build boxes, with the exact same file for settings, will not. > Does mvn help:effective-settings show your proxy settings? Also, you may try to install a dummy/forwarding proxy which logs all traffic to see what the two talk with each other. Regards, -- Aaron Digulla -- View this message in context: http://www.nabble.com/Firewall-proxy-issues-tf2771836s177.html#a7738866 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I'm just an unfrozen caveman software developer. I don't understand your strange, "modern" ways.
Build fails on Linux 64Bit
There is at least one test which fails on Linux 64Bit with jrockit-R26.4.0-jdk1.5.0_06 JDK installed. Running org.apache.maven.archiva.reporting.reporter.ChecksumArtifactReporterTest Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.261 sec <<< FAILURE! Running org.apache.maven.archiva.reporting.processor.DuplicateArtifactFileReportProcessorTest artifact = groupId:artifactId:jar:1.0-alpha-1 On Windows the build passes. Does anyone know how to get this fixed? Uli
Re: Firewall/proxy issues
Sorry. I should've indicated that I've already determined that it is reading the correct file. I forgot to put it in the original message. I have verified that it's reading the settings that I posted. Thanks for the suggestion! On 12/6/06, Barrie Treloar <[EMAIL PROTECTED]> wrote: > With the settings in settings.xml, my Windows laptop will connect > and download artifacts from ibiblio all day long. > The Linux build boxes, with the exact same file for settings, will not. It is odd that Linux fails where Windows works. Unfortunately Maven (even in -X mode) doesn't inform you where it is attempting to read the settings.xml file from. Can you verify that it is reading the settings.xml file you think it should be? The only way I know of doing this is to type junk into settings.xml which will cause an XML parse failure. If you do not get the XML parse failure then you know your settings.xml file is not being loaded. If it is reading the settings.xml file you expect, I don't have any other suggestions for you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I'm just an unfrozen caveman software developer. I don't understand your strange, "modern" ways.
Re: Debugging NoClassDefFoundError
Hello, I've found the bug in the maven source and filed a patch in JIRA (http://jira.codehaus.org/browse/MNG-2690 and http://jira.codehaus.org/browse/MNG-2691). Regards, -- Aaron Digulla -- View this message in context: http://www.nabble.com/Debugging-NoClassDefFoundError-tf2774329s177.html#a7741321 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: maven2 release and profiles
> > Date: Thu, 7 Dec 2006 05:48:55 -0800 (PST) > From: Aaron Digulla <[EMAIL PROTECTED]> > To: users@maven.apache.org > Subject: Re: maven2 release and profiles > > > > Attila Mezei-Horvati wrote: > > > > 1. I have 3 profiles I need to apply. I have to > copy > > them into this one release-profile for the sake of > one > > release. Since we have one codebase with different > > settings for different partners and I need a > release > > for all partners separately, I am wasting my time > > updating the release profile section manually for > > each. > > > > How about adding an ant script which uses an XSLT > task to copy the XML > around? Maybe not the prettiest solution but it > should work. Copy the data > to a new file and use mvn -s to use it. > > > Attila Mezei-Horvati wrote: > > > > 2. After release, back in development it seems > that > > the release-profile is activated no matter if it > is > > activated or not. So basically I need to delete > this > > profile and recreate it every time I want to do a > > release. > > > > Maybe you can solve this by specifying a special > settings file on the > command line with -s > > Regards, > I will look into that. thanks, Attila Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: User-defined phase
The phases are community defined, and there are no plans to ever change that. This is why Maven is easy to understand and use wherever you go - rather than having to learn a bunch of "custom" stuff. If you really want to coallate your work into a single command, try using the "exec" goal: http://mojo.codehaus.org/exec-maven-plugin/ Eric On 12/7/06, Deluigi Marcus <[EMAIL PROTECTED]> wrote: Hi I want to abuse maven to perform a setup for a testing environment, such as starting derby, starting a tomcat and deploying a WAR file which is another project. Maven does a fine job in downloading all the required software if necessary and building the WAR file which it is another project. Besides, it is platform independent, so I am using it for all these tasks. But I don't want to enter all these commands on the command line all the time. I think a much nicer way would be to add a custom phase (such as 'start-environment') to the module. When I am developing, I would like to be able to execute only this phase, without the life-cycle. Is something like that possible? Of course, I can make a shell-script but I think adding a custom phase to the project would be a nice thing. Greetings Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Eric Redmond http://codehaus.org/~eredmond
Re: NullPointerException while building archiva-webapp
plexus-archiver isn't a plugin [EMAIL PROTECTED] a écrit : Hello, Can someone please confirm that you get a NPE when you add this to the pom.xml of "archiva-webapp": org.codehaus.plexus plexus-archiver 1.0-alpha-7 The NPE is: [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:292) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:163) Regards,
Re: assembly: howto exclude basedirectory when unpacking binaries
You might try: ... Not sure, but I think that would work. -john On 12/7/06, Bram de Kruijff <[EMAIL PROTECTED]> wrote: Hello all, in my assembly I want to include and unpack a war binary of a moduleset in the root directory of the assembly. Unfortunaltly it always unpacks the war in a subdirectory with the artifactId/finalName as name. Is there anyway I can tell it not to do that? Eg. groupId:artifactId:war / false true ... results in... %assemblydir%/%artifactId%/WEB-INF/... ... but I need ... %assemblydir%/WEB-INF/... regards, Bram - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
User-defined phase
Hi I want to abuse maven to perform a setup for a testing environment, such as starting derby, starting a tomcat and deploying a WAR file which is another project. Maven does a fine job in downloading all the required software if necessary and building the WAR file which it is another project. Besides, it is platform independent, so I am using it for all these tasks. But I don't want to enter all these commands on the command line all the time. I think a much nicer way would be to add a custom phase (such as 'start-environment') to the module. When I am developing, I would like to be able to execute only this phase, without the life-cycle. Is something like that possible? Of course, I can make a shell-script but I think adding a custom phase to the project would be a nice thing. Greetings Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
assembly: howto exclude basedirectory when unpacking binaries
Hello all, in my assembly I want to include and unpack a war binary of a moduleset in the root directory of the assembly. Unfortunaltly it always unpacks the war in a subdirectory with the artifactId/finalName as name. Is there anyway I can tell it not to do that? Eg. groupId:artifactId:war / false true ... results in... %assemblydir%/%artifactId%/WEB-INF/... ... but I need ... %assemblydir%/WEB-INF/... regards, Bram - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Advice on moving to Maven 2.x
I'm running both maven1 and maven2 on my PC with no conflict. they use separate install dir and repository location, and command line for m2 is not "maven" so there is no conflict. Nico. 2006/12/7, Rakesh Patel <[EMAIL PROTECTED]>: i had a quick look at the Maven 2.x docs. Am i right in assuming that my PC can have both m1 and m2 installed? To call m1 i use "maven" and to call m2 i use "mvn"? We also keep a build.properties file in %USERHOME% that points to the remote repositories - m2 uses another file or mechanism right? Rakesh Max Cooper wrote: > On Thu, 2006-12-07 at 09:12 +, Rakesh Patel wrote: > >> Hi, >> >> I have just joined a new company which uses Maven 1.x. I have no >> experience with Maven at all and have been charged with evaluating a >> move to Maven 2.x. >> >> I am looking for some high-level information about the implications of >> moving: >> >> 1. The existing infrastructure includes a repository for maven 1.x >> builds - this must remain in place so is it possible to have a separate >> repository for maven 2.x builds? >> > > Absolutely. You can keep the m1 repo and setup a separate m2 repo with > no conflict. (It sounds like you can also use some tools to serve as a > dual m1+m2 repo as well, but I have no experience with that.) > > >> 2. We have a build machine which must be used for compiling all >> releases. This is hooked to the maven 1.x repository. Can it (easily) >> aslo use the maven 2.x repositiory or would we be better off starting >> with a new build box? >> > > Yes, m1 and m2 are configured independently, so you can point m1 at the > m1 repo and m2 at the m2 repo with no conflict. I have m1 and m2 > installed on my PC, both pointing to different internal repos, and I can > run both without having to change any settings in between. > > >> 3. Any other issues? >> > > Be aware that m1 and m2 are different, and that the conversion is > probably not going to be as easy as just installing m2 and running a > build. > > M1 and m2 both use the project.xml file, and you won't be able to have > one project.xml file that works for both m1 and m2. So that means you > can't have both builds working at the same time, generally. You could > have both working if you set one up in a parallel structure as shown > below, but I would avoid this because it is troublesome to configure and > maintain, IME: > > root/ > |-module1/ > | |-project.xml (for m1) > | |-src/ > |-module2/ > | |-project.xml (for m1) > | |-src/ > |-maven2build/ > |-module1/ > | |-project.xml (for m2, refers to ../../module1/src, etc.) > |-module2/ > |-project.xml (for m2, refers to ../../module2/src, etc.) > > The maven.xml file (used for "scripting" in m1) is gone in m2. I would > review what is in your maven.xml files and see if equivalent > functionality can be achieved with core or 3rd party m2 plugins. For > stuff that you can't do with off-the-shelf m2 plugins, you will need to > write your own plugins or use the maven-antrun-plugin to hook in some > Ant scripts. > > -Max > > >> Like i said, i have not used Maven before and the hope is that if its >> feasible to move to Maven 2.x on my project, then i can begin to learn >> there. >> >> Thanks >> >> Rakesh >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven2 release and profiles
Attila Mezei-Horvati wrote: > > 1. I have 3 profiles I need to apply. I have to copy > them into this one release-profile for the sake of one > release. Since we have one codebase with different > settings for different partners and I need a release > for all partners separately, I am wasting my time > updating the release profile section manually for > each. > How about adding an ant script which uses an XSLT task to copy the XML around? Maybe not the prettiest solution but it should work. Copy the data to a new file and use mvn -s to use it. Attila Mezei-Horvati wrote: > > 2. After release, back in development it seems that > the release-profile is activated no matter if it is > activated or not. So basically I need to delete this > profile and recreate it every time I want to do a > release. > Maybe you can solve this by specifying a special settings file on the command line with -s Regards, -- Aaron Digulla -- View this message in context: http://www.nabble.com/maven2-release-and-profiles-tf2772233s177.html#a7739470 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: Advice on moving to Maven 2.x
i had a quick look at the Maven 2.x docs. Am i right in assuming that my PC can have both m1 and m2 installed? To call m1 i use "maven" and to call m2 i use "mvn"? We also keep a build.properties file in %USERHOME% that points to the remote repositories - m2 uses another file or mechanism right? Rakesh Max Cooper wrote: On Thu, 2006-12-07 at 09:12 +, Rakesh Patel wrote: Hi, I have just joined a new company which uses Maven 1.x. I have no experience with Maven at all and have been charged with evaluating a move to Maven 2.x. I am looking for some high-level information about the implications of moving: 1. The existing infrastructure includes a repository for maven 1.x builds - this must remain in place so is it possible to have a separate repository for maven 2.x builds? Absolutely. You can keep the m1 repo and setup a separate m2 repo with no conflict. (It sounds like you can also use some tools to serve as a dual m1+m2 repo as well, but I have no experience with that.) 2. We have a build machine which must be used for compiling all releases. This is hooked to the maven 1.x repository. Can it (easily) aslo use the maven 2.x repositiory or would we be better off starting with a new build box? Yes, m1 and m2 are configured independently, so you can point m1 at the m1 repo and m2 at the m2 repo with no conflict. I have m1 and m2 installed on my PC, both pointing to different internal repos, and I can run both without having to change any settings in between. 3. Any other issues? Be aware that m1 and m2 are different, and that the conversion is probably not going to be as easy as just installing m2 and running a build. M1 and m2 both use the project.xml file, and you won't be able to have one project.xml file that works for both m1 and m2. So that means you can't have both builds working at the same time, generally. You could have both working if you set one up in a parallel structure as shown below, but I would avoid this because it is troublesome to configure and maintain, IME: root/ |-module1/ | |-project.xml (for m1) | |-src/ |-module2/ | |-project.xml (for m1) | |-src/ |-maven2build/ |-module1/ | |-project.xml (for m2, refers to ../../module1/src, etc.) |-module2/ |-project.xml (for m2, refers to ../../module2/src, etc.) The maven.xml file (used for "scripting" in m1) is gone in m2. I would review what is in your maven.xml files and see if equivalent functionality can be achieved with core or 3rd party m2 plugins. For stuff that you can't do with off-the-shelf m2 plugins, you will need to write your own plugins or use the maven-antrun-plugin to hook in some Ant scripts. -Max Like i said, i have not used Maven before and the hope is that if its feasible to move to Maven 2.x on my project, then i can begin to learn there. Thanks Rakesh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Advice on moving to Maven 2.x
Nope, you type "mvn"... regards, Wim 2006/12/7, Rakesh Patel <[EMAIL PROTECTED]>: Cheers Max, very useful information. I believe the approach will be more to try and work independently of the existing m1 system. So current projects on m1 will work as they do right now. New projects (like mine) will use an alternative based on m2. If for some reason we decide to abandon m2, i can use the existing infrastructure for m1. That leaves the question of whether a machine can run both m1 and m2? I'm guessing that to run m2 on the command line, you don't type maven(!). Cheers Rakesh Max Cooper wrote: > On Thu, 2006-12-07 at 09:12 +, Rakesh Patel wrote: > >> Hi, >> >> I have just joined a new company which uses Maven 1.x. I have no >> experience with Maven at all and have been charged with evaluating a >> move to Maven 2.x. >> >> I am looking for some high-level information about the implications of >> moving: >> >> 1. The existing infrastructure includes a repository for maven 1.x >> builds - this must remain in place so is it possible to have a separate >> repository for maven 2.x builds? >> > > Absolutely. You can keep the m1 repo and setup a separate m2 repo with > no conflict. (It sounds like you can also use some tools to serve as a > dual m1+m2 repo as well, but I have no experience with that.) > > >> 2. We have a build machine which must be used for compiling all >> releases. This is hooked to the maven 1.x repository. Can it (easily) >> aslo use the maven 2.x repositiory or would we be better off starting >> with a new build box? >> > > Yes, m1 and m2 are configured independently, so you can point m1 at the > m1 repo and m2 at the m2 repo with no conflict. I have m1 and m2 > installed on my PC, both pointing to different internal repos, and I can > run both without having to change any settings in between. > > >> 3. Any other issues? >> > > Be aware that m1 and m2 are different, and that the conversion is > probably not going to be as easy as just installing m2 and running a > build. > > M1 and m2 both use the project.xml file, and you won't be able to have > one project.xml file that works for both m1 and m2. So that means you > can't have both builds working at the same time, generally. You could > have both working if you set one up in a parallel structure as shown > below, but I would avoid this because it is troublesome to configure and > maintain, IME: > > root/ > |-module1/ > | |-project.xml (for m1) > | |-src/ > |-module2/ > | |-project.xml (for m1) > | |-src/ > |-maven2build/ > |-module1/ > | |-project.xml (for m2, refers to ../../module1/src, etc.) > |-module2/ > |-project.xml (for m2, refers to ../../module2/src, etc.) > > The maven.xml file (used for "scripting" in m1) is gone in m2. I would > review what is in your maven.xml files and see if equivalent > functionality can be achieved with core or 3rd party m2 plugins. For > stuff that you can't do with off-the-shelf m2 plugins, you will need to > write your own plugins or use the maven-antrun-plugin to hook in some > Ant scripts. > > -Max > > >> Like i said, i have not used Maven before and the hope is that if its >> feasible to move to Maven 2.x on my project, then i can begin to learn >> there. >> >> Thanks >> >> Rakesh >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Advice on moving to Maven 2.x
Cheers Max, very useful information. I believe the approach will be more to try and work independently of the existing m1 system. So current projects on m1 will work as they do right now. New projects (like mine) will use an alternative based on m2. If for some reason we decide to abandon m2, i can use the existing infrastructure for m1. That leaves the question of whether a machine can run both m1 and m2? I'm guessing that to run m2 on the command line, you don't type maven(!). Cheers Rakesh Max Cooper wrote: On Thu, 2006-12-07 at 09:12 +, Rakesh Patel wrote: Hi, I have just joined a new company which uses Maven 1.x. I have no experience with Maven at all and have been charged with evaluating a move to Maven 2.x. I am looking for some high-level information about the implications of moving: 1. The existing infrastructure includes a repository for maven 1.x builds - this must remain in place so is it possible to have a separate repository for maven 2.x builds? Absolutely. You can keep the m1 repo and setup a separate m2 repo with no conflict. (It sounds like you can also use some tools to serve as a dual m1+m2 repo as well, but I have no experience with that.) 2. We have a build machine which must be used for compiling all releases. This is hooked to the maven 1.x repository. Can it (easily) aslo use the maven 2.x repositiory or would we be better off starting with a new build box? Yes, m1 and m2 are configured independently, so you can point m1 at the m1 repo and m2 at the m2 repo with no conflict. I have m1 and m2 installed on my PC, both pointing to different internal repos, and I can run both without having to change any settings in between. 3. Any other issues? Be aware that m1 and m2 are different, and that the conversion is probably not going to be as easy as just installing m2 and running a build. M1 and m2 both use the project.xml file, and you won't be able to have one project.xml file that works for both m1 and m2. So that means you can't have both builds working at the same time, generally. You could have both working if you set one up in a parallel structure as shown below, but I would avoid this because it is troublesome to configure and maintain, IME: root/ |-module1/ | |-project.xml (for m1) | |-src/ |-module2/ | |-project.xml (for m1) | |-src/ |-maven2build/ |-module1/ | |-project.xml (for m2, refers to ../../module1/src, etc.) |-module2/ |-project.xml (for m2, refers to ../../module2/src, etc.) The maven.xml file (used for "scripting" in m1) is gone in m2. I would review what is in your maven.xml files and see if equivalent functionality can be achieved with core or 3rd party m2 plugins. For stuff that you can't do with off-the-shelf m2 plugins, you will need to write your own plugins or use the maven-antrun-plugin to hook in some Ant scripts. -Max Like i said, i have not used Maven before and the hope is that if its feasible to move to Maven 2.x on my project, then i can begin to learn there. Thanks Rakesh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Debugging NoClassDefFoundError
Hello, I'm using maven 2.0.4 to build Maven Archiva. Now, I get this error: [ERROR] FATAL ERROR [INFO] [INFO] Lorg/codehaus/plexus/archiver/manager/ArchiverManager; [INFO] [INFO] Trace java.lang.NoClassDefFoundError: Lorg/codehaus/plexus/archiver/manager/ArchiverManager; at java.lang.Class.getDeclaredFields0(Native Method) at java.lang.Class.privateGetDeclaredFields(Class.java:2259) at java.lang.Class.getDeclaredField(Class.java:1852) at org.codehaus.plexus.util.ReflectionUtils.getFieldByNameIncludingSuperlasses(ReflectionUtils.java:26) at org.codehaus.plexus.util.ReflectionUtils.getFieldByNameIncludingSuperclasses(ReflectionUtils.java:34) at org.codehaus.plexus.component.composition.FieldComponentComposer.getFieldByName(FieldComponentComposer.java:212) at org.codehaus.plexus.component.composition.FieldComponentComposer.findMatchingField(FieldComponentComposer.java:171) at org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent(FieldComponentComposer.java:62) at org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:68) at org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPlexusContainer.java:1486) at org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:29) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:101) at org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:105) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:95) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentManager.java:48) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:524) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:390) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) Unfortunately, this error message doesn't tell anything. I've checked that plexus-archiver is in my local repo, the JAR file isn't corrupt and it contains ArchiverManager.class. If I put a dependency (...) into the POM, I get a NullPointerException: [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:292) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:163) I'd like to open a JIRA but without further details, I guess you'll have to close it with "Cannot Reproduce". Regards, -- Aaron Digulla -- View this message in context: http://www.nabble.com/Debugging-NoClassDefFoundError-tf2774329s177.html#a7739001 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Sharing properties between maven and ant
Hello, What is the most simple way to define a property once which can be seen both my maven (for example, used in pom.xml) and ant? Example: I have three third party JARs in my project and I want to install them with "mvn install:file". Each JAR has it's own POM and I also need the version in the ANT build.xml, so I can run mvn three times. Regards, -- Aaron Digulla -- View this message in context: http://www.nabble.com/Sharing-properties-between-maven-and-ant-tf2774308s177.html#a7738926 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: Antwort: Re: Archiva: 507 Insufficient Storage
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 07, 2006 10:05 AM > To: archiva-users@maven.apache.org > Subject: Antwort: Re: Archiva: 507 Insufficient Storage > > Hello, > > > Just a question: Which version of wagon-webdav do you use for the > upload? > we use this: ... org.apache.maven.wagon wagon-webdav 1.0-beta-1 ... but we only tried a few projects, as we are seting up the environment for a new project... Daniel
Re: Antwort: Re: Archiva: 507 Insufficient Storage
I use wagon-webdav 1.0-beta-2-SNAPSHOT - Joakim [EMAIL PROTECTED] wrote: > Hello, > > >> Just a question: Which version of wagon-webdav do you use for the >> > upload? > > Anyone? > > > Regards, > > Mit freundlichen Grüssen, > >
Re: Firewall/proxy issues
Mykel Alvis-2 wrote: > > The Linux build boxes, with the exact same file for settings, will not. > Does mvn help:effective-settings show your proxy settings? Also, you may try to install a dummy/forwarding proxy which logs all traffic to see what the two talk with each other. Regards, -- Aaron Digulla -- View this message in context: http://www.nabble.com/Firewall-proxy-issues-tf2771836s177.html#a7738866 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
NullPointerException while building archiva-webapp
Hello, Can someone please confirm that you get a NPE when you add this to the pom.xml of "archiva-webapp": org.codehaus.plexus plexus-archiver 1.0-alpha-7 The NPE is: [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:292) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:163) Regards, -- Aaron Digulla
Re: Advice on moving to Maven 2.x
On Thu, 2006-12-07 at 09:12 +, Rakesh Patel wrote: > Hi, > > I have just joined a new company which uses Maven 1.x. I have no > experience with Maven at all and have been charged with evaluating a > move to Maven 2.x. > > I am looking for some high-level information about the implications of > moving: > > 1. The existing infrastructure includes a repository for maven 1.x > builds - this must remain in place so is it possible to have a separate > repository for maven 2.x builds? Absolutely. You can keep the m1 repo and setup a separate m2 repo with no conflict. (It sounds like you can also use some tools to serve as a dual m1+m2 repo as well, but I have no experience with that.) > 2. We have a build machine which must be used for compiling all > releases. This is hooked to the maven 1.x repository. Can it (easily) > aslo use the maven 2.x repositiory or would we be better off starting > with a new build box? Yes, m1 and m2 are configured independently, so you can point m1 at the m1 repo and m2 at the m2 repo with no conflict. I have m1 and m2 installed on my PC, both pointing to different internal repos, and I can run both without having to change any settings in between. > 3. Any other issues? Be aware that m1 and m2 are different, and that the conversion is probably not going to be as easy as just installing m2 and running a build. M1 and m2 both use the project.xml file, and you won't be able to have one project.xml file that works for both m1 and m2. So that means you can't have both builds working at the same time, generally. You could have both working if you set one up in a parallel structure as shown below, but I would avoid this because it is troublesome to configure and maintain, IME: root/ |-module1/ | |-project.xml (for m1) | |-src/ |-module2/ | |-project.xml (for m1) | |-src/ |-maven2build/ |-module1/ | |-project.xml (for m2, refers to ../../module1/src, etc.) |-module2/ |-project.xml (for m2, refers to ../../module2/src, etc.) The maven.xml file (used for "scripting" in m1) is gone in m2. I would review what is in your maven.xml files and see if equivalent functionality can be achieved with core or 3rd party m2 plugins. For stuff that you can't do with off-the-shelf m2 plugins, you will need to write your own plugins or use the maven-antrun-plugin to hook in some Ant scripts. -Max > > Like i said, i have not used Maven before and the hope is that if its > feasible to move to Maven 2.x on my project, then i can begin to learn > there. > > Thanks > > Rakesh > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] maven-exec-plugin:java command line launch
> -Original Message-
> From: Wayne Fay [mailto:[EMAIL PROTECTED]
====
>
> Your problem is that exec.arguments is a List of String
> objects, and you can only pass a single String object in from
> the command line.
>
> Unless someone knows how to pass an array of Strings from the
> CLI (I've never seen that this was possible), you can't do
> what you're trying to do from the CLI. You'll need to set up
> profiles or something to achieve this.
>
Thanks Wayne.
So there is a bug in the plugin/mojo. It needs an additional parameter
and logic. So setting a profile is probably the best thing to do for
now.
e.g.
regenerate-pom
com.acme.cartoons.BugsBunnyProgram
pilgripe
U:\internal\maven-repository
user.name
pilgripe
> On 12/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > Hi
> >
> > I am looking at Maven Exec Plugin. I found that the command line
> > option is problematic with arguments:
> >
> > converter>mvn exec:java
> > -Dexec.mainClass="com.ubs.firc.ptsp.research.Converter"
> > -Dexec.arguments="C:\foo\bar"
> >
> > [INFO] Scanning for projects...
> > [INFO] Searching repository for plugin with prefix: 'exec'.
> > [INFO]
> >
> --
> > --
> > -
> > ---
> > [INFO] Building Maven PTSP Repository Converter Tool
> > [INFO]task-segment: [exec:java]
> > [INFO]
> >
> --
> > --
> > -
> > ---
> > [INFO] Preparing exec:java
> > [INFO] No goals needed for project - skipping ...
> >
> > [INFO]
> >
> --
> > --
> > [ERROR] BUILD ERROR
> > [INFO]
> >
> --
> > -- [INFO] Failed to configure plugin parameters for:
> > org.codehaus.mojo:exec-maven-p
> > lugin:1.0.2
> >
> > on the command line, specify: '-Dexec.arguments=VALUE'
> >
> > Cause: Cannot assign configuration entry 'arguments' to 'class
> > [Ljava.lang.String;' from '${exec.arguments}', which is of
> type class
> > java.lang.String
> >
> > However it does work when I set a configuration inside the POM.
> > How can I pass arguments to maven-exec-plugin (java goal) with the
> > command line?
> >
> > How can you configure multiple the POM configured executions?
> >
> > --
> > Peter Pilgrim
> > UBS Investment Bank,
> > PTS Portal / IT FIRC OPS LDN,
> > 100 Liverpool Street, London EC2M 2RH, United Kingdom
> > +44 (0) 20 75 75692
> > :: Java EE / E-Commerce / Enterprise Integration / Development ::
> >
> > Visit our website at http://www.ubs.com
> >
> > This message contains confidential information and is intended only
> > for the individual named. If you are not the named addressee you
> > should not disseminate, distribute or copy this e-mail.
> Please notify
> > the sender immediately by e-mail if you have received this
> e-mail by
> > mistake and delete this e-mail from your system.
> >
> > E-mail transmission cannot be guaranteed to be secure or
> error-free as
> > information could be intercepted, corrupted, lost,
> destroyed, arrive
> > late or incomplete, or contain viruses. The sender
> therefore does not
> > accept liability for any errors or omissions in the
> contents of this
> > message which arise as a result of e-mail transmission. If
> > verification is required please request a hard-copy version. This
> > message is provided for informational purposes and should not be
> > construed as a solicitation or offer to buy or sell any
> securities or
> > related financial instruments.
> >
> >
> >
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Peter Pilgrim
UBS Investment Bank,
PTS Portal / IT FIRC OPS LDN,
100 Liverpool Street, London EC2M 2RH, United Kingdom
+44 (0) 20 75 75692
:: Java EE / E-Commerce / Enterprise Integration / Development ::
Visit our website at http://www.ubs.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sen
Re: War plugin and filtering webapp files
Following this thread and the JIRA issue at the end, if you use the 2.0.1
war-plugin the filtering now works. My pom.xml looks like -
mywebapp
org.apache.maven.plugins
maven-war-plugin
2.0.1
true
${basedir}/src/main/webapp
**/*.xml
and in my web.xml I have -
${project.name} v${project.version}
Hope this helps someone else coming across this thread
Cheers
Theo
--
View this message in context:
http://www.nabble.com/War-plugin-and-filtering-webapp-files-tf1617964s177.html#a7736926
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: [m2] eclipse:eclipse downloadSources
On 06/12/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote: eclipseDownloadSources is deprecated, tha name has been changed to downloadSources with the scope to make it consistent with other IDE-related plugins. The download status cache is only implemented in recent snapshots, you will not find it on 2.2 Cool, cheers for the clarification. Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Archiva Install
I am trying to install Archiva by following this guide [1]. I have checked out the trunk and installed all the javax jars as instructed. However when I run mvn install I always get a problem regarding javax.activation. I have narrowed this down to it coming from "archiva-plexus-runtime" module. The stack trace below shows the full fatal message. Any advice on what could be wrong? I have checked my local repo and javax.activation exists with version 1.0.2 jar inside. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Could not version for artifact: javax.activation:activation. [INFO] [INFO] Trace java.lang.RuntimeException: Could not version for artifact: javax.activation:activation. at org.codehaus.plexus.builder.AbstractBuilder.resolveVersion(AbstractBuilder.java:317) at org.codehaus.plexus.builder.AbstractBuilder.getCoreArtifacts(AbstractBuilder.java:240) at org.codehaus.plexus.builder.runtime.DefaultPlexusRuntimeBuilder.build(DefaultPlexusRuntimeBuilder.java:159) at org.codehaus.plexus.maven.plugin.runtime.RuntimeAssemblerMojo.execute(RuntimeAssemblerMojo.java:94) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [1]http://maven.apache.org/archiva/guides/getting-started/index.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
failure with castor plugin
Hi,
I'd like to generate java class from an xsd file using castor plugin.
But maven fails as you can see below. Thank's for help.
D:\users\marc\dev\chouette\chouette-noyau>mvn -U compile:generate
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'compile'.
[INFO] org.apache.maven.plugins: checking for updates from central
[INFO] org.codehaus.mojo: checking for updates from central
[INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking
for updates from central
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin: checking
for updates from central
[INFO] artifact org.apache.maven.plugins:maven-compile-plugin: checking
for updates from central
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] The plugin 'org.apache.maven.plugins:maven-compile-plugin' does
not exist or no valid version could be found
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 3 seconds
[INFO] Finished at: Thu Dec 07 10:25:19 CET 2006
[INFO] Final Memory: 2M/4M
[INFO]
Here's the pom file
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
fr.certu.chouette
chouette-noyau
war
1.0-SNAPSHOT
chouette-noyau
http://maven.apache.org
junit
junit
3.8.1
compile
javax.servlet
servlet-api
2.4
provided
struts
struts
1.2.9
compile
hibernate
hibernate
3.1rc2
compile
castor
castor
0.9.7
compile
commons-logging
commons-logging
1.1
compile
commons-logging
commons-logging
1.1
compile
log4j
log4j
1.2.9
compile
commons-configuration
commons-configuration
1.2
compile
postgresql
postgresql
8.1-407.jdbc3
runtime
fr/certu/chouette/bean
false
${basedir}/src/mapping
*.hbm.xml
${basedir}/src/main/resources
org.codehaus.mojo
castor-maven-plugin
1.0
1
compile
generate
${basedir}/src/main/resources/xsd/Application.xsd
fr.certu.chouette.common
2
compile
generate
${basedir}/src/main/resources/xsd/chouette/Chouette.xsd
fr.certu.chouette.schema
maven-surefire-plugin
SuiteTest.java
org.apache.maven.plugins
maven-surefire-report-plugin
--
Marc FLORISSON
[EMAIL PROTECTED]
www.dryade.net
Re: [m2] HOWTO release with a snapshot parent
So the whole point of releases is "rebuild" -- i.e. given a release label and the software repository, the system can be rebuilt. Is that correct? Thanks for your feedback, Adrian. Dan Tran wrote: > that is not allowed since there is no guarantee you can rebuild the release > with a dependent snapshot ( ie parent ) > > -D > > > On 12/6/06, Adrian Herscu <[EMAIL PROTECTED]> wrote: >> >> Hi all, >> >> I am trying to release a module using the maven-release-plugin. >> The module has a parent which was not released yet (its siblings are not >> released also). >> When running release:prepare on that module Maven complains that its >> parent is a SNAPSHOT, so it cannot complete the release preparation :-( >> >> This seems related to the following issue in Jira: >> http://jira.codehaus.org/browse/MRELEASE-96 >> >> Currently, I am thinking about releasing the whole project (from the >> root). >> >> Please advice, >> Adrian. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Advice on moving to Maven 2.x
I'm also start migrating projects to maven2. Only new projects use maven2 but I have the same issue regarding corporate repository. I've installed Archiva (Maven repository manager) that can act as a proxy for maven public repository and manager for private artifacts. As it auto-detects request from maven1 or maven2, it can be used to serve artifacts to maven1 from a maven2-layout repository. It can also manage legacy (maven1) layout repositories if required. I have converted my m1 repo to m2 layout and m1 projects now use my archiva URL as remoteRepo. If you need to deploy artifacts to your corporate repo, you have two options : 1. build those artifacts using maven2 (requires all projects to migrate) 2. configure archiva to set your corporate repo as "legacy" layout, so that maven1 can deploy on it. You may mix solution : have a dual private repo (m1 & m2 layout). M1 builds deploy to m1 private, and m2 builds deploy to m2. archiva proxying both will "merge" those two repository from a user point of view. AFAIK there is no issue having both M1 and M2 running. Nico. 2006/12/7, Rakesh Patel <[EMAIL PROTECTED]>: Hi, I have just joined a new company which uses Maven 1.x. I have no experience with Maven at all and have been charged with evaluating a move to Maven 2.x. I am looking for some high-level information about the implications of moving: 1. The existing infrastructure includes a repository for maven 1.x builds - this must remain in place so is it possible to have a separate repository for maven 2.x builds? 2. We have a build machine which must be used for compiling all releases. This is hooked to the maven 1.x repository. Can it (easily) aslo use the maven 2.x repositiory or would we be better off starting with a new build box? 3. Any other issues? Like i said, i have not used Maven before and the hope is that if its feasible to move to Maven 2.x on my project, then i can begin to learn there. Thanks Rakesh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Advice on moving to Maven 2.x
Hi, I have just joined a new company which uses Maven 1.x. I have no experience with Maven at all and have been charged with evaluating a move to Maven 2.x. I am looking for some high-level information about the implications of moving: 1. The existing infrastructure includes a repository for maven 1.x builds - this must remain in place so is it possible to have a separate repository for maven 2.x builds? 2. We have a build machine which must be used for compiling all releases. This is hooked to the maven 1.x repository. Can it (easily) aslo use the maven 2.x repositiory or would we be better off starting with a new build box? 3. Any other issues? Like i said, i have not used Maven before and the hope is that if its feasible to move to Maven 2.x on my project, then i can begin to learn there. Thanks Rakesh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Antwort: Re: Archiva: 507 Insufficient Storage
Hello, > Just a question: Which version of wagon-webdav do you use for the upload? Anyone? Regards, Mit freundlichen Grüssen, -- Aaron Digulla
RE: 504 in maven, works everywhere else
Hello all, I've now solved the problem by writing my own proxy. It's called DSMP (Dead Stu..Simple Maven Proxy) and can be used with the setting in settings.xml. It has these features: - It automatically mirrors any Maven repository, not only those mentioned in some config/POM/whatever file. - It remembers error returns from respository servers, so update checks run really fast. In the next version, I'm thinking about pluggable status caching strategies. - You can redirect requests from one URL to another. So, for example, if Maven believes that the maven-compiler-plugin has to be downloaded from http://mysterious.com/, you can rewrite that URL in the proxy without having to touch either your local repository or the broken POM. Of you can direct all maven requests to your nearest proxy without having to change the maven configuration. This will even work if there are multiple URLs to access the same file on a server (for example, on maven.sateh.com, "maven2" is a link to "repository"). - It allows to merge patches into the downloads. This way, you can add your own fixes to broken artefacts without changing maven, without having to enable SNAPSHOTs and without having to worry that all your developers use the same proxy/mirror/repository settings. Things I'm thinking about: - Forbid downloads (always return 404 for some site) - Lock down snapshots (always return "no, there is no newer version") - Version migration. There should be a simple way to create a self-contained set of files which allow a new plugin/artefact version to run/compile. The idea is that one developer examines a new version, checks that it doesn't break the build, etc. and then tells the proxy "Ok, now I want everyone to be able to see the new version" or "Nah, drop it". I was thinking if you might want to include this in Archiva. The proxy runs independent of any container, though. Since it can create an arbitrary amount of threads, starting it from tomcat or jetty might not be that smart. -- Aaron Digulla
Re: dependency management within plugin dependencies
Hi, dependencyManagement is inherited by children POMs. It is useful to define a dependency within dependencyManagement tag expliciting the version there. Then in the children POMs you can just declare your dependecy without having the version tag have a look here: http://maven.apache.org/pom.html#Dependency%20Management bye, Federico Gregory Kick-2 wrote: > > I have a question about the behavior of the > portion of a POM as it relates to plugin dependencies. > > Say I have: > ... > > > > GROUP > ARTIFACT > > > > ... > > And in some project that inherits from this pom, > > ... > > > GROUP > ARTIFACT > > > ... > > will fail with a missing version. > > Is this the expected behavior or is this a bug? > > > -- > Gregory Kick > [EMAIL PROTECTED] > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/dependency-management-within-plugin-dependencies-tf2772190s177.html#a7735149 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: Build error with pde-maven-plugin
are you able to do an eclipse export of your pde artifact per pde-maven-plugin's FAQ? -D On 12/1/06, Dan Tran <[EMAIL PROTECTED]> wrote: are you able to run the m2eclipse example? -D On 12/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi, > > i always get an error, when i try to build an eclipse plugin: > Does't anyone have an idea what is wrong? > > Thanks and best Reragrds, > Thorsten > > [INFO] Scanning for projects... > [INFO] > > [INFO] Building ... project > [INFO]task-segment: [compile] > [INFO] > > [INFO] [pde:ext] > [INFO] java -classpath C:\Programme\Eclipse\startup.jar > org.eclipse.core.launcher.Main -application > org.eclipse.ant.core.antRunner -buildfile > C:\temp\project\target\pdeBuilder\build.xml -verbose -debug > Install location: >file:/c:/Programme/eclipse/ > Configuration file: >file:/c:/Programme/eclipse/configuration/config.ini loaded > Configuration location: >file:/c:/Programme/eclipse/configuration/ > Framework located: > > file:/c:/Programme/eclipse/plugins/org.eclipse.osgi_3.2.1.R32x_v20060919.jar > Framework classpath: > > file:/c:/Programme/eclipse/plugins/org.eclipse.osgi_3.2.1.R32x_v20060919.jar > > Debug options: >file:/C:/temp/project/.options not found > Time to load bundles: 0 > Starting application: 805 > Apache Ant version 1.6.5 compiled on June 2 2005 > Apache Ant version 1.6.5 compiled on June 2 2005 > Setting ro project property: ant.file -> > C:\temp\project\target\pdeBuilder\build.xml > Buildfile: C:\temp\project\target\pdeBuilder\build.xml > +Datatype eclipse.convertPath org.eclipse.core.resources.ant.ConvertPath > +Datatype eclipse.incrementalBuild > org.eclipse.core.resources.ant.IncrementalBuild > +Datatype eclipse.refreshLocal > org.eclipse.core.resources.ant.RefreshLocalTask > +Datatype help.buildHelpIndex > org.eclipse.help.internal.base.ant.BuildHelpIndex > +Datatype eclipse.checkDebugAttributes > org.eclipse.jdt.core.CheckDebugAttributes > +Datatype eclipse.brand org.eclipse.pde.internal.build.tasks.BrandTask > +Datatype eclipse.fetch org.eclipse.pde.internal.build.tasks.FetchTask > +Datatype eclipse.buildScript > org.eclipse.pde.internal.build.tasks.BuildScriptGeneratorTask > +Datatype eclipse.generateFeature > org.eclipse.pde.internal.build.tasks.FeatureGeneratorTask > +Datatype eclipse.buildManifest > org.eclipse.pde.internal.build.tasks.BuildManifestTask > +Datatype eclipse.assembler > org.eclipse.pde.internal.build.tasks.PackagerTask > +Datatype eclipse.idReplacer > org.eclipse.pde.internal.build.tasks.IdReplaceTask > +Datatype eclipse.jnlpGenerator > org.eclipse.pde.internal.build.tasks.JNLPGeneratorTask > +Datatype eclipse.unzipperBuilder > org.eclipse.pde.internal.build.tasks.UnzipperGeneratorTask > +Datatype eclipse.fetchFilesGenerator > org.eclipse.pde.internal.build.tasks.FetchFileGeneratorTask > +Datatype eclipse.versionReplacer > org.eclipse.pde.internal.build.tasks.GenericVersionReplacer > +Datatype pde.convertSchemaToHTML > org.eclipse.pde.internal.core.ant.ConvertSchemaToHTML > +Datatype pde.exportPlugins > org.eclipse.pde.internal.core.ant.PluginExportTask > +Datatype pde.exportFeatures > org.eclipse.pde.internal.core.ant.FeatureExportTask > Adding reference: ant.projectHelper > Adding reference: ant.parsing.context > Adding reference: ant.targets > parsing buildfile C:\temp\project\target\pdeBuilder\build.xml with URI = > file:///C:/temp/project/target/pdeBuilder/build.xml > Setting ro project property: ant.file.null -> > C:\temp\project\target\pdeBuilder\build.xml > Project base dir set to: C:\temp\project\target\pdeBuilder > +Target: > +Target: generate > Adding reference: eclipse.ant.targetVector > Build sequence for target(s) `generate' is [generate] > Complete build sequence is [generate, ] > > generate: > [eclipse.buildScript] An error occured while generating manifest for > C:\temp\project\..\... > > BUILD FAILED > C:\temp\project\target\pdeBuilder\build.xml:8: Unable to find element: > project. >at > org.eclipse.pde.internal.build.tasks.BuildScriptGeneratorTask.execute( > BuildScriptGeneratorTask.java:74) >at org.apache.tools.ant.UnknownElement.execute ( > UnknownElement.java:275) >at org.apache.tools.ant.Task.perform(Task.java:364) >at org.apache.tools.ant.Target.execute(Target.java:341) >at org.apache.tools.ant.Target.performTasks(Target.java:369) >at org.apache.tools.ant.Project.executeSortedTargets(Project.java > :1216) >at org.apache.tools.ant.Project.executeTarget(Project.java:1185) >at org.apache.tools.ant.helper.DefaultExecutor.executeTargets ( > DefaultExecutor.java:40) >at > org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets( > EclipseDefaultExecutor.java:32) >at org.apache.tools.ant.Project.executeTargets(Project.java:1068) >
