Re: howto get scm revision information into a assembly
File an issue on Maven-SCM project and we'll fix it.
Emmanuel
berndq a écrit :
Hi,
I can get it into a property but can't get it into e.g. the manifest
file due to http://jira.codehaus.org/browse/MASSEMBLY-121
I was wrong, I can not get it into a property.
Using
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
executions
execution
phasevalidate/phase
idgetting-scm.revision/id
goals
goalupdate/goal
/goals
/execution
/executions
/plugin
as suggested on this list results in
[INFO] [scm:update {execution: getting-scm.revision}]
[INFO] Executing: svn --username maven --non-interactive update
[INFO] Working directory: D:\projekte\template\templatePom-trunk
[DEBUG] Revision 375.
[INFO] Unknown file status: 'R' in line Revision 375..
[INFO] Storing revision in 'scm.revision' project property.
This does not result in rev. 375 being replaced in filtered files
(result is xyz=0 insted of the expedted xyz=375)
If run mvn -Dscm.revision=42 ... then I get the 42 value in the
filtered file.
Bernd
I tried filtering but I could not get it to work. Anyway I am not sure
how I would have to set up a filter based on a property value.
Any help is appreciated.
Bernd
-
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]
JAXB2 versus Maven2
Hello, It seems, that http://repo1.maven.org/maven2/ is still stuck with 2.0EA3? Who can take care of this? Greetings Franz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAXB2 versus Maven2
On 1/11/07, Franz Fehringer [EMAIL PROTECTED] wrote: It seems, that http://repo1.maven.org/maven2/ is still stuck with 2.0EA3? Who can take care of this? Use the sun java repository for Maven. See https://maven-repository.dev.java.net/ -- My wife Mary and I have been married for forty-seven years and not once have we had an argument serious enough to consider divorce; murder, yes, but divorce, never. (Jack Benny) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAXB2 versus Maven2
I cannot use this, see my recent (few minutes ago) posting regarding Re: calling vote for 2.0.5 (Maven2 cannot access HTTPS (SSL) repositories from behind proxies/firewalls). Franz Jochen Wiedmann schrieb: On 1/11/07, Franz Fehringer [EMAIL PROTECTED] wrote: It seems, that http://repo1.maven.org/maven2/ is still stuck with 2.0EA3? Who can take care of this? Use the sun java repository for Maven. See https://maven-repository.dev.java.net/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAXB2 versus Maven2
On 1/11/07, Franz Fehringer [EMAIL PROTECTED] wrote: I cannot use this, see my recent (few minutes ago) posting regarding Re: calling vote for 2.0.5 (Maven2 cannot access HTTPS (SSL) repositories from behind proxies/firewalls). Use a Maven proxy like Proximity to access the Sun repository. Jochen -- My wife Mary and I have been married for forty-seven years and not once have we had an argument serious enough to consider divorce; murder, yes, but divorce, never. (Jack Benny) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m 1.1] UMLGraph: Not generating files into target/docs/apidocs
Silly me! You were right. It's all working well with version 1.8. Thanks a lot. -Gisbert Arnaud HERITIER wrote: Your problem is certainly related to MPJAVADOC-56 which is fixed in the version 1.8 Can you try to update this plugin ? Arnaud On 1/10/07, Gisbert Amm [EMAIL PROTECTED] wrote: I'm using maven-javadoc-plugin-1.7 -Gisbert Arnaud HERITIER wrote: Which version of the javadoc plugin are you using ? Arnaud On 1/10/07, Gisbert Amm [EMAIL PROTECTED] wrote: I'm trying to run UMLGraph with Maven 1.1 and it does work, BUT: The generated files are always written into the root directory of the project instead of target/docs/apidocs. This is my commandline: maven site:generate -Dmaven.build.dir=report_target -Dmaven.javadoc.doclet=gr.spinellis.umlgraph.doclet.UmlGraphDoc - Dmaven.javadoc.docletpath=/home/jbuild/.maven/repository/gr.spinellis/jars/UmlGraph-4.4.jar ... (left out the additional params for the sake of clarity) I've already tried setting maven.javadoc.usestandardparameters=true and even maven.javadoc.destdir=report_target/docs/apidocs, but both doesn't help. I found the description for Maven 2 on http://wiki.wsmoak.net/cgi-bin/wiki.pl?UMLGraph, but there is obviously nothing equivalent for Maven 1. Does anybody use UMLGraph successfully with Maven 1.1 and can give me some advice? Is my problem probably connnected with http://jira.codehaus.org/browse/MPJAVADOC-56? Thanks in advance for your help. -Gisbert -- View this message in context: http://www.nabble.com/-m-1.1--UMLGraph%3A-Not-generating-files-into-target-docs-apidocs-tf2952795s177.html#a8258632 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-m-1.1--UMLGraph%3A-Not-generating-files-into-target-docs-apidocs-tf2952795s177.html#a8262479 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-m-1.1--UMLGraph%3A-Not-generating-files-into-target-docs-apidocs-tf2952795s177.html#a8274262 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
changing phase of javadoc:jar and sources:jar
Hello, I would like my team to deploy to my repository the following jars : binaries (of course), sources and javadoc. As javadoc generation is a bit time costly, I would like to get it generated only on the deploy phase, so that, everyday work is not slowed by this generation. I did the following in my pom : ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-source-plugin/artifactId executions execution goals goaljar/goal /goals phasedeploy/phase /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId executions execution goals goaljar/goal /goals phasedelpoy/phase /execution /executions /plugin Unfortunalty, the 2 jars are generated in the deploy phase, but are not copied in the repository. I guess they are not registred in the deploy phase to get copied or something like that ? Is there something I have to change to get it work, or do I have to change the phase to install (for instance) to get them copied during the deploy phase ? By the way, concerning the eclipse:eclipse -DdownloadSources. This plugin tries to get the sources of every dependency of my pom. As all of the dependencies I use don't publish nor sources nor javadoc, it keep on trying to download them, each time I use eclipse:eclipse. Is there a way to tell eclipse:eclipse not to try downloading a set of sources / javadoc ? Best regards, Dom _ Ce message (et toutes les pièces jointes) sont confidentiels ; son contenu ne représente en aucun cas un engagement de la part de DEXIA SOFAXIS. Toute publication, utilisation ou diffusion, même partielle, doit être autorisée préalablement par l'émetteur. Si vous n'êtes pas destinataire de ce message, merci d'en avertir immédiatement l'expéditeur. Conformément aux dispositions de la loi n° 78-17 du 6 janvier 1978 relative à l'informatique, aux fichiers et aux libertés, vous pouvez obtenir communication et, le cas échéant, rectification ou suppression des informations vous concernant en vous adressant à DEXIA SOFAXIS - Route de Creton - 18110 VASSELAY _ Consultez notre site internet http://www.sofaxis.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: changing phase of javadoc:jar and sources:jar
On 1/11/07, DJP JEAN-PROST Dominique [EMAIL PROTECTED] wrote: I would like my team to deploy to my repository the following jars : binaries (of course), sources and javadoc. As javadoc generation is a bit time costly, I would like to get it generated only on the deploy phase, so that, everyday work is not slowed by this generation. The commons-parent POM from Jakarta has a different approach. It defines a special profile called release, which invokes the maven-source-plugin and the maven-javadoc-plugin and attaches the generated artifacts. In other words, the jar files are created and deployed, if you run Maven, for example, with mvn -Prelease deploy See repo1.maven.org/maven2/org/apache/commons/commons-parent/1/commons-parent-1.pom for details. Jochen -- My wife Mary and I have been married for forty-seven years and not once have we had an argument serious enough to consider divorce; murder, yes, but divorce, never. (Jack Benny) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: changing phase of javadoc:jar and sources:jar
On 11/01/07, DJP JEAN-PROST Dominique [EMAIL PROTECTED] wrote: I would like my team to deploy to my repository the following jars : binaries (of course), sources and javadoc. As javadoc generation is a bit time costly, I would like to get it generated only on the deploy phase, so that, everyday work is not slowed by this generation. I did the following in my pom : Source and javadoc jars are normally only created when performing a release, so it shouldn't impact on day-to-day work? Unfortunalty, the 2 jars are generated in the deploy phase, but are not copied in the repository. I guess they are not registred in the deploy phase to get copied or something like that ? Is there something I have to change to get it work, or do I have to change the phase to install (for instance) to get them copied during the deploy phase ? I'd recommend using a profile to control the generation of source/javadoc jars rather than moving them to a different phase. By the way, concerning the eclipse:eclipse -DdownloadSources. This plugin tries to get the sources of every dependency of my pom. As all of the dependencies I use don't publish nor sources nor javadoc, it keep on trying to download them, each time I use eclipse:eclipse. Is there a way to tell eclipse:eclipse not to try downloading a set of sources / javadoc ? See MECLIPSE-174 [1], fixed in 2.3. Mark [1] http://jira.codehaus.org/browse/MECLIPSE-174 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Eclipse throwed the error when runed compile
Hi, My project develope with Eclipse:3.2.1 , maven:2.0.4 and org.maven.ide.eclipse:0.0.9. Eclipse throwed the error when runed compile: [INFO] [INFO] Building maven_itms Maven Webapp [INFO]task-segment: [compile] [INFO] [INFO] resources:resources [INFO] Using default encoding to copy filtered resources. [INFO] compiler:compile Compiling 132 source files to D:\workspace\maven_itms\target\classes [ERROR] mojo-execute : compiler:compile Diagnosis: Compilation failure FATAL ERROR: Error executing Maven for a project [ERROR] project-execute : com.novitech.itms:maven_itms:war:1.0 ( task-segment: [compile] ) Diagnosis: Compilation failure FATAL ERROR: Error executing Maven for a project org.apache.maven.BuildFailureException: Compilation failure 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.embedder.MavenEmbedder.execute(MavenEmbedder.java:441) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:382) at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:505) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:111) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) ... 8 more But it was ok when runned mvn compile in CMD D:\workspace\maven_itmsmvn compile [INFO] Scanning for projects... [INFO] [INFO] Building maven_itms Maven Webapp [INFO]task-segment: [compile] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 132 source files to D:\workspace\maven_itms\target\classes [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 14 seconds [INFO] Finished at: Thu Jan 11 18:09:58 CST 2007 [INFO] Final Memory: 4M/21M [INFO] Why? and how I to do? -- View this message in context: http://www.nabble.com/Eclipse-throwed-the-error-when-runed-compile-tf2957962s177.html#a8274828 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: JAXB2 versus Maven2
Hi. It seems, that http://repo1.maven.org/maven2/ is still stuck with 2.0EA3? Who can take care of this? https://maven-repository.dev.java.net/ https://maven2-repository.dev.java.net/ Bye. /lexi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jar signing - the good and the bad
Great, I get alot further now. You are very helpful Tom. All my jars build ok and get signed. It's just when it gets to the EJBs that is falls over now. There exists a jar TATTestEJB\target\TATTestEJB.jar But the jarsigner is looking for TATTestEJB\target\TATTestEJB.ejb I'm using maven-ejb-plugin 2.0 (latest release). Do I need to do special config for non-jar artifacts? Thanks David Tom Huybrechts wrote: Now you're instructing the normal jar:jar to also build the jar with a classifier. Move the configuration inside the execution so that it will only effect the jar:sign. Tom -- View this message in context: http://www.nabble.com/jar-signing---the-good-and-the-bad-tf2951737s177.html#a8274897 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven 1.0.2
Hi All... I want MAven 1.0.2 version. I visit the maven site but the require version page is outdated ,so where i download. Thx in advance With regards Murugan -- View this message in context: http://www.nabble.com/Maven-1.0.2-tf2958062s177.html#a8275174 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: Maven 1.0.2
http://maven.apache.org/maven-1.x/start/download.html -Lukas Murugan wrote: Hi All... I want MAven 1.0.2 version. I visit the maven site but the require version page is outdated ,so where i download. Thx in advance With regards Murugan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 1.0.2
http://maven.apache.org/maven-1.x/start/download.html Murugan a écrit : Hi All... I want MAven 1.0.2 version. I visit the maven site but the require version page is outdated ,so where i download. Thx in advance With regards Murugan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Correlation between tagging and versioning
Hi Los, maven-release-plugin is your friend : http://maven.apache.org/plugins/maven-release-plugin/ Tag version and POM version must indeed match. - Yann 2007/1/11, moraleslos [EMAIL PROTECTED]: I'm about to tag my code in my repository to the maven-recommended x.x.x-y-z format-- probably at 1.0.0-alpha-1. I was wondering how this correlates to the version used in my POMs-- currently at 1.0-SNAPSHOT. Shouldn't they match, or are they suppose to be different? I'm new to the tagging/branching of code for release so if anyone has any suggestions, I would appreciate it. I just would like to know how maven2 can help facilitate in code releases since it has some project management functionality built in. Thanks in advance. -los -- View this message in context: http://www.nabble.com/Correlation-between-tagging-and-versioning-tf2957108s177.html#a8272307 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: Compiling with javamake
Hi all, I solved the issue on my own. I implemented my own compiler-plugin and activated it via replacing the default compiler in components.xml of maven-core.jar. It seems to work fine now. Regards, Martin Martin M wrote: Hi all, I wanted to compile my project with javamake instead of javac. Therefore I changed the compiler plugin as follows: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifacdId configuration executablejavamake/executable /configuration /plugin Now maven still tries to pass parameters like -target to the compiler-call, but -target isn't supported and causes javamake to interrupt with an error. How is this configured correctly? Do I have to use another plugin there? Thanks in advance! Regards, Martin -- Martin Moser - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Compiling-with-javamake-tf2945127s177.html#a8275324 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problems with maven-ear-plugin version 2.3
Hello, when I use the maven-ear-plugin in its latest (released) version 2.3, it seams that the plugin does not copy the resources any more. The build fails because it cannot locate the application.xml any more: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Deployment descriptor: c:\Workspace\server\application\target\mpa-application-M2-SNAPSHOT\META-INF\application.xm l does not exist. When I use the old version 2.2 everything works fine. Is this a bug or is the fault on my side? Do I have to change my maven configuration when using version 2.3? Issue MEAR-47 is about removing the resourcesDir property - did that influence the resource handling in general? thanks for your comments, Tobias. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
passing custom parameters to a custom compiler-plugin
Hi all,
I implemented a custom compiler-plugin. Now I'd like to pass some parameters
to it, but I don't get it working. My plugin always tells me that the
parameters have null-value. I assume it's possible to pass parameters to a
compiler-plugin, isn't it.
The plugin-code looks like this:
/**
* custom compiler
*
* @version $Id$
* @goal compile
* @phase compile
* @requiresDependencyResolution compile
*/
public class javamake extends AbstractMojo
{
/**
* @parameter
**/
private String testParam
public void execute() throws MojoExecutionException
{
getLog().info(Start compiling, ... with + testParam);
}
I'm calling the plugin in my pom.xml like this:
maven-compiler-plugin
c1
mygroup
customCompile
1.0-SNAPSHOT
Ihave also replaced the standard-compiler in maven's components.xml to get
my compiler activated.
org.apache.maven.lifecycle.mapping.LifecycleMapping
jar
org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping
default
org.apache.maven.plugins:maven-resources-plugin
:resources
mygroup:customCompile:1.0-SNAPSHOT:compile
etc.
Does anyone have a hint, how I could pass my custom parameter?
Thanks in advance!
Regards,
Martin
--
View this message in context:
http://www.nabble.com/passing-custom-parameters-to-a-custom-compiler-plugin-tf2958426s177.html#a8276238
Sent from the Maven - Users mailing list archive at Nabble.com.
Re: problems running project on jetty
I have been struggling with this problem for a couple of days now, any ideas? [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.codehaus.mojo:jetty-maven-plugin' does not exist or no valid version could be found I tried adding: plugin groupIdorg.codehaus.mojo/groupId artifactIdjetty-maven-plugin/artifactId /plugin But to no avail.. Any ideas? -- View this message in context: http://www.nabble.com/problems-running-project-on-jetty-tf2239041s177.html#a8276385 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: problems running project on jetty
On 11/01/07, bendg [EMAIL PROTECTED] wrote: I have been struggling with this problem for a couple of days now, any ideas? [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.codehaus.mojo:jetty-maven-plugin' does not exist or no valid version could be found I tried adding: plugin groupIdorg.codehaus.mojo/groupId artifactIdjetty-maven-plugin/artifactId /plugin But to no avail.. Any ideas? Perhaps using the correct groupId? http://jetty.mortbay.org/maven-plugin/howto.html Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems with maven-ear-plugin version 2.3
I had the same problem today
Let me quote somebody:
you can still make it work if you explicitely set the resources directory
configurationresourcesDir${project.build.outputDirectory}/resourcesDir
/configuration
tom
On 1/11/07, Tobias Jenkner [EMAIL PROTECTED] wrote:
Hello,
when I use the maven-ear-plugin in its latest (released) version 2.3, it
seams that the plugin does not copy the resources any more. The build
fails because it cannot locate the application.xml any more:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Deployment descriptor:
c:\Workspace\server\application\target\mpa-application-M2-SNAPSHOT\META-INF\application.xm
l does not exist.
When I use the old version 2.2 everything works fine.
Is this a bug or is the fault on my side? Do I have to change my maven
configuration when using version 2.3?
Issue MEAR-47 is about removing the resourcesDir property - did that
influence the resource handling in general?
thanks for your comments,
Tobias.
-
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]
Maven Compiler plugin
Hi, I am trying to compile files in a folder and move them to a directory. It gives the following error: Diagnosis: Compilation failure FATAL ERROR: Error executing Maven for a project org.apache.maven.BuildFailureException: Compilation failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) Read a lot of similar messages but am not clear what exactly causes this. plugin artifactIdmaven-compiler-plugin/artifactId executions execution phasecompile/phase goals goalcompile/goal /goals configuration sourceDirectorywrappers/sourceDirectory outputDirectorytarget/classes/outputDirectory /configuration /execution /executions /plugin Regards Raju -- View this message in context: http://www.nabble.com/Maven-Compiler-plugin-tf2958588s177.html#a8276651 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: problems running project on jetty
Thanks - this works a treat... Mark Hobson wrote: On 11/01/07, bendg [EMAIL PROTECTED] wrote: I have been struggling with this problem for a couple of days now, any ideas? [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.codehaus.mojo:jetty-maven-plugin' does not exist or no valid version could be found I tried adding: plugin groupIdorg.codehaus.mojo/groupId artifactIdjetty-maven-plugin/artifactId /plugin But to no avail.. Any ideas? Perhaps using the correct groupId? http://jetty.mortbay.org/maven-plugin/howto.html Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/problems-running-project-on-jetty-tf2239041s177.html#a8276653 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: Problems with maven-ear-plugin version 2.3
I do not understand the reason for this change?
why do I have to configure the resources directory on my own? the maven
approach is convention over configuration, isn't it?
or is it deprecated to use resources in this place? where should I place
them instead?
thanks for your help, Tobias.
Tom Huybrechts schrieb:
I had the same problem today
Let me quote somebody:
you can still make it work if you explicitely set the resources directory
configurationresourcesDir${project.build.outputDirectory}/resourcesDir
/configuration
tom
On 1/11/07, Tobias Jenkner [EMAIL PROTECTED] wrote:
Hello,
when I use the maven-ear-plugin in its latest (released) version 2.3, it
seams that the plugin does not copy the resources any more. The build
fails because it cannot locate the application.xml any more:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Deployment descriptor:
c:\Workspace\server\application\target\mpa-application-M2-SNAPSHOT\META-INF\application.xm
l does not exist.
When I use the old version 2.2 everything works fine.
Is this a bug or is the fault on my side? Do I have to change my maven
configuration when using version 2.3?
Issue MEAR-47 is about removing the resourcesDir property - did that
influence the resource handling in general?
thanks for your comments,
Tobias.
-
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: multi project interdependencies
Hi, you're saying: If a dependency of your maven project does not exist when you execute a maven command, then that project will not bulid ( assuming ofcourse the maven command requires a pom to execute ). This would be an even bigger problem during install/deploy calls: What would then happen if changed some parts in subproject A and B and try to use parts of A in B? Since A will not be deployed/installed prior to the compilation of B, you might download the wrong version of A from the repository. This would lead to broken builds!? Currently it is like that: subproject A - compile subproject A - test subproject A - jar subproject B - compile - in need of a subproject A jar (searching in repostitory) subproject B - test - proceeds only if an OLDER version is found subproject B - jar subproject A - install subproject A - deploy subproject B - install subproject B - deploy Should a project not go through the whole build lifecycle first before switching to the next project??? M -- View this message in context: http://www.nabble.com/multi-project-interdependencies-tf2916882s177.html#a8277154 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: Maven Compiler plugin
On 1/11/07, raju [EMAIL PROTECTED] wrote: Hi, I am trying to compile files in a folder and move them to a directory. It gives the following error: Diagnosis: Compilation failure FATAL ERROR: Error executing Maven for a project org.apache.maven.BuildFailureException: Compilation failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) Read a lot of similar messages but am not clear what exactly causes this. plugin artifactIdmaven-compiler-plugin/artifactId executions execution phasecompile/phase goals goalcompile/goal /goals configuration sourceDirectorywrappers/sourceDirectory I don't see 'sourceDirectory' as a configuration element for the compile goal: http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html It's actually a child element of build: http://maven.apache.org/ref/2.0.4/maven-model/maven.html In general, each module can have only one sourceDirectory and one testSourceDirectory. What are you trying to do? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems with maven-ear-plugin version 2.3
I don't know why the defaults changed...
If you want the previous behaviour, fix your plugin version to 2.2
On 1/11/07, Tobias Jenkner [EMAIL PROTECTED] wrote:
I do not understand the reason for this change?
why do I have to configure the resources directory on my own? the maven
approach is convention over configuration, isn't it?
or is it deprecated to use resources in this place? where should I place
them instead?
thanks for your help, Tobias.
Tom Huybrechts schrieb:
I had the same problem today
Let me quote somebody:
you can still make it work if you explicitely set the resources directory
configurationresourcesDir${project.build.outputDirectory}/resourcesDir
/configuration
tom
On 1/11/07, Tobias Jenkner [EMAIL PROTECTED] wrote:
Hello,
when I use the maven-ear-plugin in its latest (released) version 2.3, it
seams that the plugin does not copy the resources any more. The build
fails because it cannot locate the application.xml any more:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Deployment descriptor:
c:\Workspace\server\application\target\mpa-application-M2-SNAPSHOT\META-INF\application.xm
l does not exist.
When I use the old version 2.2 everything works fine.
Is this a bug or is the fault on my side? Do I have to change my maven
configuration when using version 2.3?
Issue MEAR-47 is about removing the resourcesDir property - did that
influence the resource handling in general?
thanks for your comments,
Tobias.
-
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]
calling Maven goal from ant
In the Ant file, create an exec task and spawn a shell and execute something like mvn goal. 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: multi project interdependencies
Good day to you, M, Actually, it's subproject A - compile subproject A - test subproject A - jar subproject A - install subproject A - deploy subproject B - compile - in need of a subproject A jar (searching in repostitory) subproject B - test - proceeds only if an OLDER version is found subproject B - jar subproject B - install subproject B - deploy IRC, maven2 will first group your tasks to segments. And then those task segments would be executed one at a time. When one task segment finishes, the next will begin. All non-aggregating goals will be set as one task segment, then every aggregating goal will have their own task segment. Aggregating goals are those that run only on the project that you invoked it upon, while non-aggregating goals are those that run on the project you invoked it upon, plus, all modules under it. The project on which a non-aggregating goal will run on would then be ordered according to dependency, making sure that the dependencies are built before the dependees. The task segment for the non-aggregating goals would then be executed to each of those projects and according to which build lifecycle phase they are bound to. Thus, with a project project-a, with two modules, module-a and module-b, where module-b depends on module-a, if you run mvn deploy on project-a, the order of the projects would be project-a module-a module-b And on each project, the goals compiler:compile, surefire:test, jar:jar, install:install, deploy:deploy (among others) would be executed on each. Thus, it's like having cd project-a mvn compiler:compiler mvn surefire:test mvn jar:jar mvn install:install mvn deploy:deploy cd module-a mvn compiler:compiler mvn surefire:test mvn jar:jar mvn install:install mvn deploy:deploy cd ..\module-b mvn compiler:compiler mvn surefire:test mvn jar:jar mvn install:install mvn deploy:deploy ( more or less ). Cheers, Franz meberts wrote: Hi, you're saying: If a dependency of your maven project does not exist when you execute a maven command, then that project will not bulid ( assuming ofcourse the maven command requires a pom to execute ). This would be an even bigger problem during install/deploy calls: What would then happen if changed some parts in subproject A and B and try to use parts of A in B? Since A will not be deployed/installed prior to the compilation of B, you might download the wrong version of A from the repository. This would lead to broken builds!? Currently it is like that: subproject A - compile subproject A - test subproject A - jar subproject B - compile - in need of a subproject A jar (searching in repostitory) subproject B - test - proceeds only if an OLDER version is found subproject B - jar subproject A - install subproject A - deploy subproject B - install subproject B - deploy Should a project not go through the whole build lifecycle first before switching to the next project??? M -- View this message in context: http://www.nabble.com/multi-project-interdependencies-tf2916882s177.html#a8278008 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: calling Maven goal from ant
Hi folks,
under Windows you loose the result code from the Maven invocation -
therefore I use the following snippet to invoken maven
target name=-mvn:invoke
property name=maven.home value=${env.CM_HOME}/tools/maven2 /
property name=maven.failonerror value=true /
java classname=org.codehaus.classworlds.Launcher fork=yes
failonerror=${maven.failonerror} dir=${basedir}
jvmarg value=-Xmx384m/
classpath
pathelement location=${maven.home}/core/boot/classworlds-1.1.jar/
/classpath
sysproperty key=classworlds.conf value=${maven.home}/bin/m2.conf/
sysproperty key=maven.home value=${maven.home}/
arg line=${maven.target}/
/java
/target
Morgovsky, Alexander (US - Glen Mills) wrote:
In the Ant file, create an exec task and spawn a shell and execute
something like mvn goal.
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: howto get scm revision information into a assembly
http://jira.codehaus.org/browse/SCM-270
File an issue on Maven-SCM project and we'll fix it.
Emmanuel
berndq a écrit :
Hi,
I can get it into a property but can't get it into e.g. the manifest
file due to http://jira.codehaus.org/browse/MASSEMBLY-121
I was wrong, I can not get it into a property.
Using
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
executions
execution
phasevalidate/phase
idgetting-scm.revision/id
goals
goalupdate/goal
/goals
/execution
/executions
/plugin
as suggested on this list results in
[INFO] [scm:update {execution: getting-scm.revision}]
[INFO] Executing: svn --username maven --non-interactive update
[INFO] Working directory: D:\projekte\template\templatePom-trunk
[DEBUG] Revision 375.
[INFO] Unknown file status: 'R' in line Revision 375..
[INFO] Storing revision in 'scm.revision' project property.
This does not result in rev. 375 being replaced in filtered files
(result is xyz=0 insted of the expedted xyz=375)
If run mvn -Dscm.revision=42 ... then I get the 42 value in the
filtered file.
Bernd
I tried filtering but I could not get it to work. Anyway I am not
sure how I would have to set up a filter based on a property value.
Any help is appreciated.
Bernd
-
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: calling Maven goal from ant
Thanks for your answer. But... Morgovsky, Alexander (US - Glen Mills) wrote: In the Ant file, create an exec task and spawn a shell and execute something like mvn goal. this won't work as on the target machine maven is probably not installed and even if it is installed might need invocation via mvn.bat, probably need full path etc. So this is not a solution for me :( Regards, Irrisor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Correlation between tagging and versioning
Hi Yann, Thanks for the reply. I guess what I was looking for is if I needed to do everything, e.g. tagging, through maven2 or can I do that in SVN and then sync the releases with maven2? -los Yann Le Du-4 wrote: Hi Los, maven-release-plugin is your friend : http://maven.apache.org/plugins/maven-release-plugin/ Tag version and POM version must indeed match. - Yann 2007/1/11, moraleslos [EMAIL PROTECTED]: I'm about to tag my code in my repository to the maven-recommended x.x.x-y-z format-- probably at 1.0.0-alpha-1. I was wondering how this correlates to the version used in my POMs-- currently at 1.0-SNAPSHOT. Shouldn't they match, or are they suppose to be different? I'm new to the tagging/branching of code for release so if anyone has any suggestions, I would appreciate it. I just would like to know how maven2 can help facilitate in code releases since it has some project management functionality built in. Thanks in advance. -los -- View this message in context: http://www.nabble.com/Correlation-between-tagging-and-versioning-tf2957108s177.html#a8272307 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Correlation-between-tagging-and-versioning-tf2957108s177.html#a8278049 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: Compiling with javamake
If this is something that others might benefit from, it would be nice if you would package it up and contribute it to the Maven Compiler plugin team for inclusion in a future release. I'm not familiar with javamake so I don't know how many people use it, why you'd choose it over javac, etc but more options are always a good thing. Wayne On 1/11/07, Martin M [EMAIL PROTECTED] wrote: Hi all, I solved the issue on my own. I implemented my own compiler-plugin and activated it via replacing the default compiler in components.xml of maven-core.jar. It seems to work fine now. Regards, Martin Martin M wrote: Hi all, I wanted to compile my project with javamake instead of javac. Therefore I changed the compiler plugin as follows: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifacdId configuration executablejavamake/executable /configuration /plugin Now maven still tries to pass parameters like -target to the compiler-call, but -target isn't supported and causes javamake to interrupt with an error. How is this configured correctly? Do I have to use another plugin there? Thanks in advance! Regards, Martin -- Martin Moser - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Compiling-with-javamake-tf2945127s177.html#a8275324 Sent from the Maven - Users mailing list archive at Nabble.com. - 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: Problems with maven-ear-plugin version 2.3
I ran into this myself and at first didn't know why suddenly my WAR
was showing up in the wrong contextPath. Then realized it was probably
due to the new EAR release.
So instead of changing the configuration to use my application.xml, I
just added some configuration to the EAR plugin node in pom.xml which
fully specifies my application.xml at build time. For config files
like this, I'd rather let Maven generate it than be responsible for it
myself.
Wayne
On 1/11/07, Tom Huybrechts [EMAIL PROTECTED] wrote:
I don't know why the defaults changed...
If you want the previous behaviour, fix your plugin version to 2.2
On 1/11/07, Tobias Jenkner [EMAIL PROTECTED] wrote:
I do not understand the reason for this change?
why do I have to configure the resources directory on my own? the maven
approach is convention over configuration, isn't it?
or is it deprecated to use resources in this place? where should I place
them instead?
thanks for your help, Tobias.
Tom Huybrechts schrieb:
I had the same problem today
Let me quote somebody:
you can still make it work if you explicitely set the resources directory
configurationresourcesDir${project.build.outputDirectory}/resourcesDir
/configuration
tom
On 1/11/07, Tobias Jenkner [EMAIL PROTECTED] wrote:
Hello,
when I use the maven-ear-plugin in its latest (released) version 2.3, it
seams that the plugin does not copy the resources any more. The build
fails because it cannot locate the application.xml any more:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Deployment descriptor:
c:\Workspace\server\application\target\mpa-application-M2-SNAPSHOT\META-INF\application.xm
l does not exist.
When I use the old version 2.2 everything works fine.
Is this a bug or is the fault on my side? Do I have to change my maven
configuration when using version 2.3?
Issue MEAR-47 is about removing the resourcesDir property - did that
influence the resource handling in general?
thanks for your comments,
Tobias.
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cobertura-maven-plugin-2.1 is brokens?
The latest version displays wrong statistiscs ( all show %100 coverage ). Do you see what I see? ;-) http://mojo.codehaus.org/dbunit-maven-plugin/cobertura/index.html -D
Re: cobertura-maven-plugin-2.1 is brokens?
Yes I think it has been broken for a while. I have seen quite a lot of recommendations to stick with 2.0. - Original message - From: Dan Tran [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Date: Thu, 11 Jan 2007 07:31:09 -0800 Subject: cobertura-maven-plugin-2.1 is brokens? The latest version displays wrong statistiscs ( all show %100 coverage ). Do you see what I see? ;-) http://mojo.codehaus.org/dbunit-maven-plugin/cobertura/index.html -D - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cobertura-maven-plugin-2.1 is brokens?
Thanks, Hate the change mojo's root pom to pin down the version ;-) -D On 1/11/07, Martin Gilday [EMAIL PROTECTED] wrote: Yes I think it has been broken for a while. I have seen quite a lot of recommendations to stick with 2.0. - Original message - From: Dan Tran [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Date: Thu, 11 Jan 2007 07:31:09 -0800 Subject: cobertura-maven-plugin-2.1 is brokens? The latest version displays wrong statistiscs ( all show %100 coverage ). Do you see what I see? ;-) http://mojo.codehaus.org/dbunit-maven-plugin/cobertura/index.html -D - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: cobertura-maven-plugin-2.1 is brokens?
Hate the change mojo's root pom to pin down the version ;-) Time to correct the bug ? Several major bugs have been raised on this version (2.1) for a while, and no one works on them. http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=11226fixfor=-1 And version 2.0 cannot be use in some multi-module applications because of http://jira.codehaus.org/browse/MCOBERTURA-39 (fixed in 2.1 ...) Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: cobertura-maven-plugin-2.1 is brokens?
I might be rememembering this incorrectly but I think quite a few of the bugs stem from the plugin version 2.1 dependeing on cobertura lib 1.8 whereas 2.0 dependds on 1.7. A killer for some people is the you cant change the location of the cobertura.ser, with it always being in the project root. - Original message - From: LECAN Damien [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Date: Thu, 11 Jan 2007 16:46:13 +0100 Subject: RE: cobertura-maven-plugin-2.1 is brokens? Hate the change mojo's root pom to pin down the version ;-) Time to correct the bug ? Several major bugs have been raised on this version (2.1) for a while, and no one works on them. http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=11226fixfor=-1 And version 2.0 cannot be use in some multi-module applications because of http://jira.codehaus.org/browse/MCOBERTURA-39 (fixed in 2.1 ...) Damien - 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]
multiple compiling for code coverage
I'm trying to compile my source more than once with debug turned off and
then turned on. I'm doing this because I want debugging off in jars but I
need debugging on for Cobertura code coverage to be able to instrument the
code. I've been trying something like this:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
executions
execution
idrelease/id
phasecompile/phase
configuration
debugfalse/debug
/configuration
/execution
execution
iddebug/id
phasecompile/phase
configuration
debugtrue/debug
/configuration
/execution
/executions
configuration
verbosefalse/verbose
showDeprecationtrue/showDeprecation
showWarningstrue/showWarnings
meminitial128m/meminitial
maxmem512m/maxmem
forkfalse/fork
executable${java.home}\bin\javac.exe/executable
/configuration
/plugin
...but it's not working. Any ideas?
Any help is appreciated.
- Dave
enabling logging
Hi, How can I enable debug level logging for maven's plugins. I'd like to see what goes on before this exception is thrown: Caused by: org.apache.maven.plugin.MojoExecutionException: Error uploading site at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:184) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) ... 10 more Caused by: org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: reject HostKey: newzealand.TRAVELSECURE.LOCAL at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(AbstractSshWagon.java:239) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106) at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:153) ... 12 more Caused by: com.jcraft.jsch.JSchException: reject HostKey: newzealand.TRAVELSECURE.LOCAL at com.jcraft.jsch.Session.checkHost(Unknown Source) at com.jcraft.jsch.Session.connect(Unknown Source) at com.jcraft.jsch.Session.connect(Unknown Source) at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(AbstractSshWagon.java:228) ... 15 more - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: passing custom parameters to a custom compiler-plugin
Good day to you, Martin M,
May I ask you to repost this again. It seems as though your message have
been made into one long line which makes it hard to read.
Thanks,
Franz
Martin M wrote:
Hi all,
I implemented a custom compiler-plugin. Now I'd like to pass some
parameters to it, but I don't get it working. My plugin always tells me
that the parameters have null-value. I assume it's possible to pass
parameters to a compiler-plugin, isn't it.
The plugin-code looks like this:
/**
* custom compiler
*
* @version $Id$
* @goal compile
* @phase compile
* @requiresDependencyResolution compile
*/
public class javamake extends AbstractMojo
{
/**
* @parameter
**/
private String testParam
public void execute() throws MojoExecutionException
{
getLog().info(Start compiling, ... with + testParam);
}
I'm calling the plugin in my pom.xml like this:
plugin
artifactIdmaven-compiler-plugin/artifactId
configuration
testParamc1/testParam
/configuration
dependencies
dependency
groupIdmygroup/groupId
artifactIdcustomCompile/artifactId
version1.0-SNAPSHOT/version
/dependency
/dependencies
/plugin
Ihave also replaced the standard-compiler in maven's components.xml to get
my compiler activated.
component
roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role
role-hintjar/role-hint
implementationorg.apache.maven.lifecycle.mapping.DefaultLifecycleMapping
/implementation
configuration
lifecycles
lifecycle
iddefault/id
!-- START SNIPPET: jar-lifecycle --
phases
process-resourcesorg.apache.maven.plugins:maven-resources-plugin
:resources/process-resources
compilemygroup:customCompile:1.0-SNAPSHOT:compile/compile
etc.
Does anyone have a hint, how I could pass my custom parameter?
Thanks in advance!
Regards,
Martin
--
View this message in context:
http://www.nabble.com/passing-custom-parameters-to-a-custom-compiler-plugin-tf2958426s177.html#a8278077
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: changing phase of javadoc:jar and sources:jar
Good day, Actually, the Super POM already has that ( see release-profile of [1] ). Cheers, Franz [1] http://maven.apache.org/guides/introduction/introduction-to-the-pom.html Jochen Wiedmann wrote: On 1/11/07, DJP JEAN-PROST Dominique [EMAIL PROTECTED] wrote: I would like my team to deploy to my repository the following jars : binaries (of course), sources and javadoc. As javadoc generation is a bit time costly, I would like to get it generated only on the deploy phase, so that, everyday work is not slowed by this generation. The commons-parent POM from Jakarta has a different approach. It defines a special profile called release, which invokes the maven-source-plugin and the maven-javadoc-plugin and attaches the generated artifacts. In other words, the jar files are created and deployed, if you run Maven, for example, with mvn -Prelease deploy See repo1.maven.org/maven2/org/apache/commons/commons-parent/1/commons-parent-1.pom for details. Jochen -- My wife Mary and I have been married for forty-seven years and not once have we had an argument serious enough to consider divorce; murder, yes, but divorce, never. (Jack Benny) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/changing-phase-of-javadoc%3Ajar-and-sources%3Ajar-tf2957919s177.html#a8278078 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: Compiling with javamake
Hi Wayne, thanks for showing this up. I intend to do so, but before I've to complete it. :-) Regards, Martin --On Donnerstag, Januar 11, 2007 09:25:30 -0600 Wayne Fay [EMAIL PROTECTED] wrote: If this is something that others might benefit from, it would be nice if you would package it up and contribute it to the Maven Compiler plugin team for inclusion in a future release. I'm not familiar with javamake so I don't know how many people use it, why you'd choose it over javac, etc but more options are always a good thing. Wayne On 1/11/07, Martin M [EMAIL PROTECTED] wrote: Hi all, I solved the issue on my own. I implemented my own compiler-plugin and activated it via replacing the default compiler in components.xml of maven-core.jar. It seems to work fine now. Regards, Martin Martin M wrote: Hi all, I wanted to compile my project with javamake instead of javac. Therefore I changed the compiler plugin as follows: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifacdId configuration executablejavamake/executable /configuration /plugin Now maven still tries to pass parameters like -target to the compiler-call, but -target isn't supported and causes javamake to interrupt with an error. How is this configured correctly? Do I have to use another plugin there? Thanks in advance! Regards, Martin -- Martin Moser - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Compiling-with-javamake-tf2945127s177.html#a8275324 Sent from the Maven - Users mailing list archive at Nabble.com. - 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] -- Martin Moser [EMAIL PROTECTED] Quality First Software GmbH http://www.qfs.de Tulpenstr. 41Tel: +49 8171 919874 DE-82538 Geretsried Fax: +49 8171 919876 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-war-plugin overwriting options
When we combine more than one war file as dependencies. Is there a way to specify overwrite priority ? We have three wars a.war, b.war and c.war and we are building a fourth war (target.war) that will combine the three wars. In case we get a collision between this wars, we want a.war to overwrite other file changes (in b.war or c.war). How should we proceed ? We have tested changing the order between a, b and c with no luck pom.xml for final project is: 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; modelVersion4.0.0/modelVersion groupIdclient/groupId artifactIdweb/artifactId packagingwar/packaging version1.2.3/version nameweb application for client/name dependencies dependency groupIdtest/groupId artifactIda/artifactId version1.0.0/version typewar/type /dependency dependency groupIdtest/groupId artifactIdb/artifactId version1.0.0/version typewar/type /dependency dependency groupIdtest/groupId artifactIdc/artifactId version1.0.0/version typewar/type /dependency /dependencies build finalNametarget/finalName !-- Quitamos el directorio de ejemplos (samples)-- plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration dependentWarExcludes css/**,js/** /dependentWarExcludes /configuration /plugin /plugins /build /project __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: enabling logging
Have you tried running mvn with -X ? | -Original Message- | From: Dmitry Beransky [mailto:[EMAIL PROTECTED] | Sent: Thursday, January 11, 2007 11:22 AM | To: Maven Users List | Subject: enabling logging | | Hi, | | How can I enable debug level logging for maven's plugins. | I'd like to see what goes on before this exception is thrown: | | Caused by: org.apache.maven.plugin.MojoExecutionException: | Error uploading site | at | org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeplo | yMojo.java:184) | at | org.apache.maven.plugin.DefaultPluginManager.executeMojo(Defau | ltPluginManager.java:412) | at | org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa | ls(DefaultLifecycleExecutor.java:534) | ... 10 more | Caused by: | org.apache.maven.wagon.authentication.AuthenticationException: | Cannot connect. Reason: reject HostKey: newzealand.TRAVELSECURE.LOCAL | at | org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConn | ection(AbstractSshWagon.java:239) | at | org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) | at | org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106) | at | org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeplo | yMojo.java:153) | ... 12 more | Caused by: com.jcraft.jsch.JSchException: reject HostKey: | newzealand.TRAVELSECURE.LOCAL | at com.jcraft.jsch.Session.checkHost(Unknown Source) | at com.jcraft.jsch.Session.connect(Unknown Source) | at com.jcraft.jsch.Session.connect(Unknown Source) | at | org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConn | ection(AbstractSshWagon.java:228) | ... 15 more | | - | 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: passing custom parameters to a custom compiler-plugin
I'm sorry,I hope now it's better :-)
Hi all,
I implemented a custom compiler-plugin. Now I'd like to pass some
parameters to it, but I don't get it working. My plugin always tells me
that the parameters have null-value. I assume it's possible to pass
parameters to a compiler-plugin, isn't it.
The plugin-code looks like this:
/**
* custom compiler
*
* @version $Id$
* @goal compile
* @phase compile
* @requiresDependencyResolution compile
*/
public class javamake extends AbstractMojo
{
/**
* @parameter
**/
private String testParam
public void execute() throws MojoExecutionException
{
getLog().info(Start compiling, ... with + testParam);
}
I'm calling the plugin in my pom.xml like this:
plugin
artifactIdmaven-compiler-plugin/artifactId
configuration
testParamc1/testParam
/configuration
dependencies
dependency
groupIdmygroup/groupId
artifactIdcustomCompile/artifactId
version1.0-SNAPSHOT/version
/dependency
/dependencies
/plugin
I have also replaced the standard-compiler in maven's components.xml to
get my compiler activated.
component
roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role
role-hintjar/role-hint
implementationorg.apache.maven.lifecycle.mapping.DefaultLifecycleMapping
/implementation
configuration
lifecycles
lifecycle
iddefault/id
!-- START SNIPPET: jar-lifecycle --
phases
process-resourcesorg.apache.maven.plugins:maven-resources-plugin:resources
/process-resources
compilemygroup:customCompile:1.0-SNAPSHOT:compile/compile
etc.
Does anyone have a hint, how I could pass my custom parameter?
Thanks in advance!
Regards,
Martin
--On Donnerstag, Januar 11, 2007 08:29:51 -0800 franz see
[EMAIL PROTECTED] wrote:
Good day to you, Martin M,
May I ask you to repost this again. It seems as though your message have
been made into one long line which makes it hard to read.
Thanks,
Franz
Martin M wrote:
Hi all,
I implemented a custom compiler-plugin. Now I'd like to pass some
parameters to it, but I don't get it working. My plugin always tells me
that the parameters have null-value. I assume it's possible to pass
parameters to a compiler-plugin, isn't it.
The plugin-code looks like this:
/**
* custom compiler
*
* @version $Id$
* @goal compile
* @phase compile
* @requiresDependencyResolution compile
*/
public class javamake extends AbstractMojo
{
/**
* @parameter
**/
private String testParam
public void execute() throws MojoExecutionException
{
getLog().info(Start compiling, ... with + testParam);
}
I'm calling the plugin in my pom.xml like this:
plugin
artifactIdmaven-compiler-plugin/artifactId
configuration
testParamc1/testParam
/configuration
dependencies
dependency
groupIdmygroup/groupId
artifactIdcustomCompile/artifactId
version1.0-SNAPSHOT/version
/dependency
/dependencies
/plugin
Ihave also replaced the standard-compiler in maven's components.xml to
get my compiler activated.
component
roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role
role-hintjar/role-hint
implementationorg.apache.maven.lifecycle.mapping.DefaultLifecycleMappi
ng /implementation
configuration
lifecycles
lifecycle
iddefault/id
!-- START SNIPPET: jar-lifecycle --
phases
process-resourcesorg.apache.maven.plugins:maven-resources-plugin
:resources/process-resources
compilemygroup:customCompile:1.0-SNAPSHOT:compile/compile
etc.
Does anyone have a hint, how I could pass my custom parameter?
Thanks in advance!
Regards,
Martin
--
View this message in context:
http://www.nabble.com/passing-custom-parameters-to-a-custom-compiler-plug
in-tf2958426s177.html#a8278077 Sent from the Maven - Users mailing list
archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Martin Moser
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
maven-war-plugin overwriting options
When we combine more than one war file as dependencies. Is there a way to specify overwrite priority ? We have three wars a.war, b.war and c.war and we are building a fourth war (target.war) that will combine the three wars. In case we get a collision between this wars, we want a.war to overwrite other file changes (in b.war or c.war). How should we proceed ? We have tested changing the order between a, b and c with no luck pom.xml for final project is: 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;; modelVersion4.0.0/modelVersion groupIdclient/groupId artifactIdweb/artifactId packagingwar/packaging version1.2.3/version nameweb application for client/name dependencies dependency groupIdtest/groupId artifactIda/artifactId version1.0.0/version typewar/type /dependency dependency groupIdtest/groupId artifactIdb/artifactId version1.0.0/version typewar/type /dependency dependency groupIdtest/groupId artifactIdc/artifactId version1.0.0/version typewar/type /dependency /dependencies build finalNametarget/finalName !-- Quitamos el directorio de ejemplos (samples)-- plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration dependentWarExcludes css/**,js/** /dependentWarExcludes /configuration /plugin /plugins /build /project __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: enabling logging
I can't. This problem happens only when I run maven under TeamCity (a continuous build app). Unfortunately, TeamCity doesn't give me an option of passing command line parameters to Maven. On 1/11/07, Ian Springer [EMAIL PROTECTED] wrote: Have you tried running mvn with -X ? | -Original Message- | From: Dmitry Beransky [mailto:[EMAIL PROTECTED] | Sent: Thursday, January 11, 2007 11:22 AM | To: Maven Users List | Subject: enabling logging | | Hi, | | How can I enable debug level logging for maven's plugins. | I'd like to see what goes on before this exception is thrown: | | Caused by: org.apache.maven.plugin.MojoExecutionException: | Error uploading site | at | org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeplo | yMojo.java:184) | at | org.apache.maven.plugin.DefaultPluginManager.executeMojo(Defau | ltPluginManager.java:412) | at | org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa | ls(DefaultLifecycleExecutor.java:534) | ... 10 more | Caused by: | org.apache.maven.wagon.authentication.AuthenticationException: | Cannot connect. Reason: reject HostKey: newzealand.TRAVELSECURE.LOCAL | at | org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConn | ection(AbstractSshWagon.java:239) | at | org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) | at | org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106) | at | org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeplo | yMojo.java:153) | ... 12 more | Caused by: com.jcraft.jsch.JSchException: reject HostKey: | newzealand.TRAVELSECURE.LOCAL | at com.jcraft.jsch.Session.checkHost(Unknown Source) | at com.jcraft.jsch.Session.connect(Unknown Source) | at com.jcraft.jsch.Session.connect(Unknown Source) | at | org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConn | ection(AbstractSshWagon.java:228) | ... 15 more | | - | 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: enabling logging
On 1/11/07, Ian Springer [EMAIL PROTECTED] wrote: Have you tried running mvn with -X ? besides, when I do this from CLI, i don't get debug level messages, just extra exception traces, which is not what I'm after. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: passing custom parameters to a custom compiler-plugin
Hi Martin,
there's no automation. You need to provide the expression for the parameter to
initialize:
[snip]
/**
* @parameter expression=${testParam}
**/
private String testParam
[snip]
Within the expression you can also address other parts of the POM ... another
typical parameter is:
/**
* The directory for the generated file.
*
* @parameter expression=${project.build.directory}
* @required
*/
private String outputDirectory;
- Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: war plugin for content managment
Thanks, I'll take a look at it. Sorry for the late reply, your email got caught by my spam filter. Do you know if cargo support deployment via scp? I'd prefer to push to the web server in the DMZ rather than have an extra process running outside the firewall. Thanks, Todd On 1/9/07, Wayne Fay [EMAIL PROTECTED] wrote: The M2 Cargo plugin is useful for deploying things. So once you have a release cut, I'd log into PROD and do a Cargo deploy, or perhaps even do the deploy right from the build machine if you find that Cargo supports remote deploy for your specific container. Wayne On 1/9/07, Todd Nine [EMAIL PROTECTED] wrote: Hi all, I have a bit of a different situation for building, and I'd like some input from the community on the best approach. Here is my problem. I will have 2 servers. 1 in production and 1 testing web. The servers contain an webapp that needs to be installed in the root context. Our webmaster will be editing the JSP's using dreamweaver and adobe contribute. I will be writing code that will need to be deployed with the webapp. I was thinking that I could install maven on our test web system and use the following flow. 1. Webmaster logs in and executes mvn scm:update. 2. execute mvn war:inplace 3. Webmaster edits content 4. Once they're ready to push, perform a mvn scm:update. Should I always have them perform a scm:add first? 5. execute mvn clean release:clean release:prepare 6. execute a mvn release:perform Now this is where I'm stuck. Hopefully this process will create a war (with pre-compiled Jsp files) and deploy it to our internal repository. Now, is there a way I can have the release plugin push to our production server, or how would I use maven on our production server to automatically download a specified version and push it to tomcat? Thanks, Todd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: war plugin for content managment
You'll need to ask on the Cargo Users list, unfortunately. I don't use it much myself at this point, though I'm getting ready to very soon. Wayne On 1/11/07, Todd Nine [EMAIL PROTECTED] wrote: Thanks, I'll take a look at it. Sorry for the late reply, your email got caught by my spam filter. Do you know if cargo support deployment via scp? I'd prefer to push to the web server in the DMZ rather than have an extra process running outside the firewall. Thanks, Todd On 1/9/07, Wayne Fay [EMAIL PROTECTED] wrote: The M2 Cargo plugin is useful for deploying things. So once you have a release cut, I'd log into PROD and do a Cargo deploy, or perhaps even do the deploy right from the build machine if you find that Cargo supports remote deploy for your specific container. Wayne On 1/9/07, Todd Nine [EMAIL PROTECTED] wrote: Hi all, I have a bit of a different situation for building, and I'd like some input from the community on the best approach. Here is my problem. I will have 2 servers. 1 in production and 1 testing web. The servers contain an webapp that needs to be installed in the root context. Our webmaster will be editing the JSP's using dreamweaver and adobe contribute. I will be writing code that will need to be deployed with the webapp. I was thinking that I could install maven on our test web system and use the following flow. 1. Webmaster logs in and executes mvn scm:update. 2. execute mvn war:inplace 3. Webmaster edits content 4. Once they're ready to push, perform a mvn scm:update. Should I always have them perform a scm:add first? 5. execute mvn clean release:clean release:prepare 6. execute a mvn release:perform Now this is where I'm stuck. Hopefully this process will create a war (with pre-compiled Jsp files) and deploy it to our internal repository. Now, is there a way I can have the release plugin push to our production server, or how would I use maven on our production server to automatically download a specified version and push it to tomcat? Thanks, Todd - 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: enabling logging
-e turns on exception stack traces, and -X turns on debug logging. Btw, I've had the same problem with not being able to turn on debug when running under TeamCity. I asked JetBrains about it, and they said there's currently no way to do it. I keep meaning to file a JIRA with JetBrains for it, so they'll add something in 1.2. | -Original Message- | From: Dmitry Beransky [mailto:[EMAIL PROTECTED] | Sent: Thursday, January 11, 2007 12:08 PM | To: Maven Users List | Subject: Re: enabling logging | | On 1/11/07, Ian Springer [EMAIL PROTECTED] wrote: | Have you tried running mvn with -X ? | | besides, when I do this from CLI, i don't get debug level | messages, just extra exception traces, which is not what I'm after. | | - | 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: calling Maven goal from ant
this works for me
project name=sample default=maven
!-- we want to exec mvn on Unix systems, and mvn.bat on windows --
condition property=maven.extension value=.bat else=
os family=windows/
/condition
property name=mvn.exe value=mvn${maven.extension}/
target name=maven
exec executable=${mvn.exe} failonerror=true
arg line=install/
/exec
/target
/project
On 1/11/07, Irrisor [EMAIL PROTECTED] wrote:
Thanks for your answer. But...
Morgovsky, Alexander (US - Glen Mills) wrote:
In the Ant file, create an exec task and spawn a shell and execute
something like mvn goal.
this won't work as on the target machine maven is probably not installed
and even if it is installed might need invocation via mvn.bat, probably
need full path etc.
So this is not a solution for me :(
Regards,
Irrisor
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAXB2 versus Maven2
we sync from the java.net repo to central when users request something missing, as long as it's properly done there On 1/11/07, Aleksei Valikov [EMAIL PROTECTED] wrote: Hi. It seems, that http://repo1.maven.org/maven2/ is still stuck with 2.0EA3? Who can take care of this? https://maven-repository.dev.java.net/ https://maven2-repository.dev.java.net/ Bye. /lexi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to get plugin mojo to run without using executions in pom?
Warning - m2 programming noobie here. I'm trying to write a mojo that will execute when maven runs anytime the plugin is referenced, without adding the executions. In other words, I want the pom to be: plugin groupIdorg.example.maven/groupId artifactIdmaven-businessrules-plugin/artifactId /plugin /plugins instead of plugin groupIdorg.example.maven/groupId artifactIdmaven-businessrules-plugin/artifactId executions execution goals goalrule1/goal goalrule2/goal goalrule3/goal goalrule4/goal goalrule5/goal goalrule6/goal /goals /execution /executions /plugin /plugins and let the plugin itself figure out which rules to execute during which phases. I've tried a number of different combinations of @goal, @phase and @execute, also different combinations of @execute parameters, but haven't had any luck yet. Can this even be done? Thanks in advance.
Re: email build notification not an href
I am also looking for this feature and also the way to send failure notifications only to the checkin users in that build activemqer wrote: Hi, How do I make the build results link a hyperlink? It seems to come in as a text string in the build notification emails. Thanks. -- View this message in context: http://www.nabble.com/email-build-notification-not-an-href-tf2892577.html#a8279824 Sent from the Continuum - Users mailing list archive at Nabble.com.
RE: maven-war-plugin overwriting options
There is no control. See this issue: http://jira.codehaus.org/browse/MWAR-66 Even worse, the plugin compares the timestamps of the files individually without regard to which overlay they come from. That means today a file from A might win, but it someone edits a file from B, then B will start to win. It makes the newer versions of the war plugin unuseable for me. It's on my long list to tackle but haven't gotten to it yet. -Original Message- From: ismael [mailto:[EMAIL PROTECTED] Sent: Thursday, January 11, 2007 11:56 AM To: users@maven.apache.org Subject: maven-war-plugin overwriting options When we combine more than one war file as dependencies. Is there a way to specify overwrite priority ? We have three wars a.war, b.war and c.war and we are building a fourth war (target.war) that will combine the three wars. In case we get a collision between this wars, we want a.war to overwrite other file changes (in b.war or c.war). How should we proceed ? We have tested changing the order between a, b and c with no luck pom.xml for final project is: 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;; modelVersion4.0.0/modelVersion groupIdclient/groupId artifactIdweb/artifactId packagingwar/packaging version1.2.3/version nameweb application for client/name dependencies dependency groupIdtest/groupId artifactIda/artifactId version1.0.0/version typewar/type /dependency dependency groupIdtest/groupId artifactIdb/artifactId version1.0.0/version typewar/type /dependency dependency groupIdtest/groupId artifactIdc/artifactId version1.0.0/version typewar/type /dependency /dependencies build finalNametarget/finalName !-- Quitamos el directorio de ejemplos (samples)-- plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration dependentWarExcludes css/**,js/** /dependentWarExcludes /configuration /plugin /plugins /build /project __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com - 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]
Can not see PluginDescriptor when running a mojo
Warning - m2 programming noobie here.
I'm trying to write a very simple mojo to display a message which will
include the version number of the plugin.
I use the following annotations to access the plugin:
/**
* Plugin descriptor.
* @parameter default-value=${plugin}
* @required
* @readonly
*/
private PluginDescriptor plugin;
and I do get a PluginDescriptor, but I find that it is completely empty.
getLog().info(Plugin: +
ReflectionToStringBuilder.reflectionToString(plugin,
ToStringStyle.MULTI_LINE_STYLE));
displays
[INFO] Plugin: [EMAIL PROTECTED]
groupId=null
artifactId=null
version=null
goalPrefix=null
source=null
inheritedByDefault=true
artifacts=null
lifecycleMappings=null
classRealm=null
artifactMap=null
introducedDependencyArtifacts=null
name=null
description=null
components=null
dependencies=null
isolatedRealm=false
id=null
]
Am I trying the wrong approach?
Proposal: maven-asf-plugin
Hi, after finding myself to do this again and again for projects, I came to the following idea: How about a special maven-asf-plugin that simplifies Apache projects (in particular, may be Maven itself)? Things this plugin could do: - Provide resources, in particular the latest LICENSE.txt and NOTICE.txt files. (Note that this would enable to remove them from the subversion repositories.) - Make sure that these LICENSE.txt and NOTICE.txt are being added to jar, war, ... files. - Verify that all source files are carrying the ASL headers (using RAT). - Replace old ASL headers with current. The most important point that I see is that such a plugin would be able to handle changes in the ASF policy. (In my few years as an Apache committer that happended two times, each time causing a lot of work and confusion.) Does such a thing already exist? Other thoughts? Thanks, Jochen -- My wife Mary and I have been married for forty-seven years and not once have we had an argument serious enough to consider divorce; murder, yes, but divorce, never. (Jack Benny) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xdoc test results for Dennis
drekka wrote: Hi Dennis, As expected, the results are the same - no p tags: Hi Derek Actually that's not what I expected. If we are using the same version of Maven and the site-plugin we should get the same results. What OS are you running this on? You might also try to nuke the org/apache/maven/plugins/maven-site-plugin and org/apache/maven/doxia directories of your local repository. This would trigger a fresh download of the site-plugin and doxia, during the next run. div id=bodyColumn div id=contentBox div class=sectionh2section 1/h2 div class=sectionh3subsection 1/h3 pparagraph 1 in subsection 1/p ul lilist item 1/li lilist item 2/li /ul paragraph 2 in subsection 1 /div div class=sectionh3subsection 2/h3 paragraph 1 in subsection 2 /div /div /div /div I'll re-install maven and try again. ciao Derek -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can not see PluginDescriptor when running a mojo
OK, I'm answering my own question. Found the maven code that evaluates the
expressions, and it seems that the string plugin does not get evaluated,
but strings starting with plugin. such as plugin.version DO get
evaluated. The eBook Better Builds With Maven indicates (in A.2.1) that
${plugin} should work. Is this a bug?
On 1/11/07, Thierry Lach [EMAIL PROTECTED] wrote:
Warning - m2 programming noobie here.
I'm trying to write a very simple mojo to display a message which will
include the version number of the plugin.
I use the following annotations to access the plugin:
/**
* Plugin descriptor.
* @parameter default-value=${plugin}
* @required
* @readonly
*/
private PluginDescriptor plugin;
and I do get a PluginDescriptor, but I find that it is completely empty.
getLog().info(Plugin: +
ReflectionToStringBuilder.reflectionToString(plugin,
ToStringStyle.MULTI_LINE_STYLE));
displays
[INFO] Plugin: [EMAIL PROTECTED]
groupId=null
artifactId=null
version=null
goalPrefix=null
source=null
inheritedByDefault=true
artifacts=null
lifecycleMappings=null
classRealm=null
artifactMap=null
introducedDependencyArtifacts=null
name=null
description=null
components=null
dependencies=null
isolatedRealm=false
id=null
]
Am I trying the wrong approach?
Issues with SCM strings
I'm copying and forwarding from another message to see if I can get a
response on this.
I have a parent pom that defines the SCM of itself and all it's children by
using
scm:svn:http://${scm.host}/svnrepos/${object.namespace}/${artifactId}/trunk
and when I do help:effective-pom, I end up with
scm:svn:http://${scm.host}/svnrepos/${object.namespace
}/${artifactId}/trunk/${artifactId}
Having read another post regarding this, I'm curious if anyone knows the
actual update that I've acquired that makes this error occur.
What do I need to revert to in order to eliminate this problem?
--
I'm just an unfrozen caveman software developer. I don't understand your
strange, modern ways.
Re: enabling logging
On 1/11/07, Ian Springer [EMAIL PROTECTED] wrote: I keep meaning to file a JIRA with JetBrains for it, so they'll add something in 1.2. there is an inssue (kind of) for it already: http://www.jetbrains.net/jira/browse/TW-1409 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal: maven-asf-plugin
On 12/01/07, Jochen Wiedmann [EMAIL PROTECTED] wrote: - Provide resources, in particular the latest LICENSE.txt and NOTICE.txt files. (Note that this would enable to remove them from the subversion repositories.) - Make sure that these LICENSE.txt and NOTICE.txt are being added to jar, war, ... files. These can be done with the asf parent POM (though we haven't moved the configuration up there yet, it's already possible). - Verify that all source files are carrying the ASL headers (using RAT). That's what the RAT plugin is for, I assume? - Replace old ASL headers with current. Probably a bit tedious to rewrite this again when there are already sufficient tools around. However, ISTR the guy that wrote the IDEA copyright plugin might have donated some code to do a maven plugin... Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal: maven-asf-plugin
On 1/11/07, Brett Porter [EMAIL PROTECTED] wrote: These can be done with the asf parent POM (though we haven't moved the configuration up there yet, it's already possible). A POM cannot provide code. For example, it cannot provide a jar file with the current LICENSE.txt or NOTICE.txt. A plugin can. In other words, my proposal would enable to use the maven-asf-plugin in the asf parent POM. - Verify that all source files are carrying the ASL headers (using RAT). That's what the RAT plugin is for, I assume? Yes, but the RAT plugin is usefull beyond the ASF. For example, I might use it to verify that the source files contain my companies copyright headers, not the ASF's. My proposal would mean that the maven-asf-plugin would use the RAT plugin. (More precisely, it's jar file, because unfortunately a plugin cannot use another plugin directly, doesn't it?) - Replace old ASL headers with current. Probably a bit tedious to rewrite this again when there are already sufficient tools around. However, ISTR the guy that wrote the IDEA copyright plugin might have donated some code to do a maven plugin... There is no reason not to do reuse such tools in the plugin. The main idea would be to simplify the process. Jochen -- How fast can a year go? As fast as your childs first year. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal: maven-asf-plugin
On 1/11/07, Jochen Wiedmann [EMAIL PROTECTED] wrote: On 1/11/07, Brett Porter [EMAIL PROTECTED] wrote: These can be done with the asf parent POM (though we haven't moved the configuration up there yet, it's already possible). A POM cannot provide code. For example, it cannot provide a jar file with the current LICENSE.txt or NOTICE.txt. A plugin can. In other words, my proposal would enable to use the maven-asf-plugin in the asf parent POM. isn't that what the remote-resources plugin is for ? Tom - Verify that all source files are carrying the ASL headers (using RAT). That's what the RAT plugin is for, I assume? Yes, but the RAT plugin is usefull beyond the ASF. For example, I might use it to verify that the source files contain my companies copyright headers, not the ASF's. My proposal would mean that the maven-asf-plugin would use the RAT plugin. (More precisely, it's jar file, because unfortunately a plugin cannot use another plugin directly, doesn't it?) - Replace old ASL headers with current. Probably a bit tedious to rewrite this again when there are already sufficient tools around. However, ISTR the guy that wrote the IDEA copyright plugin might have donated some code to do a maven plugin... There is no reason not to do reuse such tools in the plugin. The main idea would be to simplify the process. Jochen -- How fast can a year go? As fast as your childs first year. - 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: Proposal: maven-asf-plugin
On 12/01/07, Jochen Wiedmann [EMAIL PROTECTED] wrote: On 1/11/07, Brett Porter [EMAIL PROTECTED] wrote: These can be done with the asf parent POM (though we haven't moved the configuration up there yet, it's already possible). A POM cannot provide code. For example, it cannot provide a jar file with the current LICENSE.txt or NOTICE.txt. A plugin can. In other words, my proposal would enable to use the maven-asf-plugin in the asf parent POM. No, the ASF POM provides the ASF configuration for all the other plugins, so: - remote-resources plugin for inclusion of a given LICENSE.txt and NOTICE.txt - RAT plugin for a given set of ASF release check rules - copyright plugin (?) for updating ASF copyrights. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Correlation between tagging and versioning
I'm reading the maven release:prepare and noticed that it will not build because of SNAPSHOT dependencies. In my multiproject, I'm using a dependency that is currently in SNAPSHOT release and won't be upgraded for a while.Is there a way to bypass this since this 3rd party dependency's release version is out of my control? -los Yann Le Du-4 wrote: Hi Los, maven-release-plugin is your friend : http://maven.apache.org/plugins/maven-release-plugin/ Tag version and POM version must indeed match. - Yann 2007/1/11, moraleslos [EMAIL PROTECTED]: I'm about to tag my code in my repository to the maven-recommended x.x.x-y-z format-- probably at 1.0.0-alpha-1. I was wondering how this correlates to the version used in my POMs-- currently at 1.0-SNAPSHOT. Shouldn't they match, or are they suppose to be different? I'm new to the tagging/branching of code for release so if anyone has any suggestions, I would appreciate it. I just would like to know how maven2 can help facilitate in code releases since it has some project management functionality built in. Thanks in advance. -los -- View this message in context: http://www.nabble.com/Correlation-between-tagging-and-versioning-tf2957108s177.html#a8272307 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Correlation-between-tagging-and-versioning-tf2957108s177.html#a8286933 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: Dependency management
Hi Alexander, Hi, I have a few questions about modules and dependencies. Does the order of modules listed in the parent pom.xml matter? As said by others it does NOT matter for the dependency management. It only matters for the ordering when the modules are rendered to the menu of the generated site. I maintain a very big project with maven that has up to 4 level deepth modules and very complex situations like P/B/B1 depends on P/A/A1 P/B/B2 depends on P/B/B1 and P/A/A2 P/A/A2 depends on P/B/B1 Where P is the main project, A and B are modules that both have to sub modules. So it is NOT possible to build A or B completely independent of each other. My situations are sometimes even more complex and I never had trouble with this. For example, if C depends on A and B depends on C, then the correct order would be:A, C B moduleA/module moduleC/module moduleB/module If I specify instead moduleA/module moduleB/module moduleC/module, will Maven pick up the right dependency order and build as if I had written A,C,B? As for my second question, if I declare a dependency in a project, will that artifact be automatically built and deployed to maven repo so that it would be picked up for build? For example, if I declare: dependency groupIdb/groupId artifactIda/artifactId version1.0/version /dependency Will Maven go and build a for me or do I need to include a as a submodule? Thanks. Regards Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Just checking my understanding of SNAPSHOT vs real versions
A real version is only downloaded into your local repo if it isn't already there. A SNAPSHOT version is always checked against central (or other outside repos) to see if there is a newer version available. Is that correct? -- cg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m 1.1] UMLGraph: Not generating files into target/docs/apidocs
No problem. Don't forget that if you want to share it with several developers, you can add it in your project as a dependency. You'll be sure that every developer use this version of the javadoc plugin, even if it is not installed locally Arnaud On 1/11/07, Gisbert Amm [EMAIL PROTECTED] wrote: Silly me! You were right. It's all working well with version 1.8. Thanks a lot. -Gisbert Arnaud HERITIER wrote: Your problem is certainly related to MPJAVADOC-56 which is fixed in the version 1.8 Can you try to update this plugin ? Arnaud On 1/10/07, Gisbert Amm [EMAIL PROTECTED] wrote: I'm using maven-javadoc-plugin-1.7 -Gisbert Arnaud HERITIER wrote: Which version of the javadoc plugin are you using ? Arnaud On 1/10/07, Gisbert Amm [EMAIL PROTECTED] wrote: I'm trying to run UMLGraph with Maven 1.1 and it does work, BUT: The generated files are always written into the root directory of the project instead of target/docs/apidocs. This is my commandline: maven site:generate -Dmaven.build.dir=report_target -Dmaven.javadoc.doclet=gr.spinellis.umlgraph.doclet.UmlGraphDoc - Dmaven.javadoc.docletpath=/home/jbuild/.maven/repository/gr.spinellis/jars/UmlGraph-4.4.jar ... (left out the additional params for the sake of clarity) I've already tried setting maven.javadoc.usestandardparameters=true and even maven.javadoc.destdir=report_target/docs/apidocs, but both doesn't help. I found the description for Maven 2 on http://wiki.wsmoak.net/cgi-bin/wiki.pl?UMLGraph, but there is obviously nothing equivalent for Maven 1. Does anybody use UMLGraph successfully with Maven 1.1 and can give me some advice? Is my problem probably connnected with http://jira.codehaus.org/browse/MPJAVADOC-56? Thanks in advance for your help. -Gisbert -- View this message in context: http://www.nabble.com/-m-1.1--UMLGraph%3A-Not-generating-files-into-target-docs-apidocs-tf2952795s177.html#a8258632 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-m-1.1--UMLGraph%3A-Not-generating-files-into-target-docs-apidocs-tf2952795s177.html#a8262479 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-m-1.1--UMLGraph%3A-Not-generating-files-into-target-docs-apidocs-tf2952795s177.html#a8274262 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: Just checking my understanding of SNAPSHOT vs real versions
Snapshots are checked once a day by default. You can override this by passing the -U flag, forcing maven to update its snapshots. Here's a good review of snaps, by Brett: http://blogs.maven.org/brett/2005/04/15/1113510156000.html On 1/11/07, Christian Goetze [EMAIL PROTECTED] wrote: A real version is only downloaded into your local repo if it isn't already there. A SNAPSHOT version is always checked against central (or other outside repos) to see if there is a newer version available. Is that correct? -- cg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xdoc test results for Dennis
Hi Dennis, I'm running this under WinXP. Will that make a difference ? I've deleted the whole org/apache/maven directory just to be sure. Then deleted the /target directory and ran mvn clean site. Downloaded versions are: doxia(core site): 1.0-alpha-7 site: 2.0-beta-5 Same result again in index.html: div class=sectionh2section 1/h2 div class=sectionh3subsection 1/h3 pparagraph 1 in subsection 1/p ul lilist item 1/li lilist item 2/li /ul paragraph 2 in subsection 1 /div div class=sectionh3subsection 2/h3 paragraph 1 in subsection 2 /div /div Also tried: Running under cgwin - no difference. Commenting out the 2.0-beta-5 dependency - no difference. ... 2 hours later ;-) ... Been trolling the repository and jars. I've tried to check out Maven several times now and Eclipse just crashes after about 5 minutes of downloading. Gives some message about the server killing the connection. Anyway, trolling the repository directly is slow but I think I have a handle on this. Three classes are involved MXParser which parses the source index.xml, XDocParser which responds to the xml events as the file is read and feeds the data to XdocSink which formats the output and writes it to the html file. Looking inside XdocSink we see that there is a flag (as I suspected) which is set when dealing with a list. This flag is also checked when receiving p tag events. I cannot see anything wrong with the code, but it looks as if the communication between these three classes is going awry somewhere. The code in XdocSink suggests that possibly after the /ul tag is written the flag is somehow not being reset which would cause the next p to be ignored. However the next /p would still reset the flag. So I thought perhaps thing is causing the MXParser to send data following this in a way that XDocParser is not seeing as p tags. Too hard to tell from the source, I would really need to debug through and as I said I've had no luck trying to checkc it out. Hope this helps. Derek P.S. I also traced the MXParser back to the core maven pluxus lib (v1.1) and manually updaed it to v1.4, but that didn't fix it either ;-( Dennis Lundberg-2 wrote: drekka wrote: Hi Dennis, As expected, the results are the same - no p tags: Hi Derek Actually that's not what I expected. If we are using the same version of Maven and the site-plugin we should get the same results. What OS are you running this on? You might also try to nuke the org/apache/maven/plugins/maven-site-plugin and org/apache/maven/doxia directories of your local repository. This would trigger a fresh download of the site-plugin and doxia, during the next run. div id=bodyColumn div id=contentBox div class=sectionh2section 1/h2 div class=sectionh3subsection 1/h3 pparagraph 1 in subsection 1/p ul lilist item 1/li lilist item 2/li /ul paragraph 2 in subsection 1 /div div class=sectionh3subsection 2/h3 paragraph 1 in subsection 2 /div /div /div /div I'll re-install maven and try again. ciao Derek -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/xdoc-test-results-for-Dennis-tf2955728s177.html#a8289937 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: Just checking my understanding of SNAPSHOT vs real versions
Patrick Schneider wrote: Snapshots are checked once a day by default. You can override this by passing the -U flag, forcing maven to update its snapshots. Here's a good review of snaps, by Brett: http://blogs.maven.org/brett/2005/04/15/1113510156000.html Thanks - so it would seem that snapshot-policy isn't implemented yet - or that I don't know where to set it... otoh, once a day isn't too bad. -- cg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Source Archives: Source Plugin vs. Assembly Plugin
After looking through the documentation for each of these plugins, I am left with a few questions: - Isn't the functionality of the source plugin just a subset of the assembly plugin (i.e. couldn't I just use the assembly plugin to do the same thing and only have to worry about one plugin)? - Is there a reason that the assembly plugin uses -src for its archives while the sources plugin uses -sources? - Should the Source Plugin be deprecated for a pre-defined assembly descriptor with the same behavior? -- Gregory Kick [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Compiler plugin
Hi Raju, There's actually a compilation error. Did you run Maven using the -X switch? This must have caused the stacktrace produced. Try to compile again without using this switch and see the source file(s) that failed to compile. Hope this helps. Dawn raju wrote: Hi, I am trying to compile files in a folder and move them to a directory. It gives the following error: Diagnosis: Compilation failure FATAL ERROR: Error executing Maven for a project org.apache.maven.BuildFailureException: Compilation failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) Read a lot of similar messages but am not clear what exactly causes this. plugin artifactIdmaven-compiler-plugin/artifactId executions execution phasecompile/phase goals goalcompile/goal /goals configuration sourceDirectoryxyz/sourceDirectory outputDirectorytarget/classes/outputDirectory /configuration /execution /executions /plugin Regards Raju -- View this message in context: http://www.nabble.com/Maven-Compiler-plugin-tf2958588s177.html#a8291130 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Not a circular dependency...
I've got a situation where Maven is telling me I have a circular dependency that should be resolved. Let's say I've got applicationArtifact which provides an interface which I want to consume at compile time in an artifact called pluginArtifact. When applicationArtifact is ready to be packaged, I want to include pluginArtifact in the libs as a runtime dependency. ie. artifactIdapplicationArtifact/artifactId dependencies dependency artifactIdpluginArtifact/artifactId scoperuntime/scope /dependency /dependencies artifactIdpluginArtifact/artifactId dependencies dependency artifactIdapplicationArtifact/artifactId scopecompile/scope !-- such that we can use the common interface -- /dependency /dependencies Maven won't compile the above as it cites a circular dependency. This should work because of the following valid order: 1) compile applicationArtifact (ignore pluginArtifact because it's scoped at Runtime) 2) compile pluginArtifact (include a compile time reference to applicationArtifact) 3) package applicationArtifact (which drags in pluginArtifact) How should I solve this issue? Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to get plugin mojo to run without using executions in pom?
Hi, I got into this as well a few weeks ago. The answer is that you have to have a parent pom where you declare the plugin and it's executions. Inside that you have two choices: 1. Declare the plugin (and executions) as per normal. Then when executing any derived poms, the pluglin will be automatically called at the right time. You do not need to re-declare it at all. -or- 2. Declare the plugin and executions in a pluginManagement section which means it is available but not automatically run. To then get it run in a derived pom, you only need to include the plugin declaration with the group and artifact ids as you want to do. It really depends on how you want to activate the plugin. Hope this helps, Derek. Thierry Lach-2 wrote: Warning - m2 programming noobie here. I'm trying to write a mojo that will execute when maven runs anytime the plugin is referenced, without adding the executions. In other words, I want the pom to be: plugin groupIdorg.example.maven/groupId artifactIdmaven-businessrules-plugin/artifactId /plugin /plugins instead of plugin groupIdorg.example.maven/groupId artifactIdmaven-businessrules-plugin/artifactId executions execution goals goalrule1/goal goalrule2/goal goalrule3/goal goalrule4/goal goalrule5/goal goalrule6/goal /goals /execution /executions /plugin /plugins and let the plugin itself figure out which rules to execute during which phases. I've tried a number of different combinations of @goal, @phase and @execute, also different combinations of @execute parameters, but haven't had any luck yet. Can this even be done? Thanks in advance. -- View this message in context: http://www.nabble.com/How-to-get-plugin-mojo-to-run-without-using-%3Cexecutions%3E-in-pom--tf2960870s177.html#a8292154 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
applying filters to a site
after looking through the thread at
http://www.nabble.com/-M2--Insert-variables-in-xdoc-apt-files-tf1956665.html
i've gotten filters applied to a site using:
resources
resource
directorysrc/site/directory
targetPath../filtered-site/targetPath
filteringtrue/filtering
/resource
/resources
filters
filtersite-filter.properties/filter
/filters
and
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
configuration
siteDirectory${project.build.directory}/filtered-site/siteDirectory
/configuration
/plugin
Is there a better way to get this done? It seems like there are way
too many steps involved...
--
Gregory Kick
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Not a circular dependency...
Maybe you could try using the assembly plugin to assemble your final package... and use the assembly descriptor to specify which items should be included in it? This should allow you to remove the pluginArtifact dependency in your applicationArtifact pom. Just a thought... Patrick On 1/11/07, Andrew Franklin [EMAIL PROTECTED] wrote: I've got a situation where Maven is telling me I have a circular dependency that should be resolved. Let's say I've got applicationArtifact which provides an interface which I want to consume at compile time in an artifact called pluginArtifact. When applicationArtifact is ready to be packaged, I want to include pluginArtifact in the libs as a runtime dependency. ie. artifactIdapplicationArtifact/artifactId dependencies dependency artifactIdpluginArtifact/artifactId scoperuntime/scope /dependency /dependencies artifactIdpluginArtifact/artifactId dependencies dependency artifactIdapplicationArtifact/artifactId scopecompile/scope !-- such that we can use the common interface -- /dependency /dependencies Maven won't compile the above as it cites a circular dependency. This should work because of the following valid order: 1) compile applicationArtifact (ignore pluginArtifact because it's scoped at Runtime) 2) compile pluginArtifact (include a compile time reference to applicationArtifact) 3) package applicationArtifact (which drags in pluginArtifact) How should I solve this issue? Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to get plugin mojo to run without using executions in pom?
Maybe this could be helpful: http://www.nabble.com/maven-plugin-execution-phase%3A-post-site--tf2513362.html#a7014966 Kovalen
Re: Issues with SCM strings
After a bit more googling and reading some other peoples' comments, I
realized that this is apparently as designed. Which leads me to the
question of ...why would you ever want that?
I can understand that, in a multi-module build, the submodules are probably
one level under the parent. In our environments, however, every component
at its lowest level of granularity, is its own project, with its own
trunk/tags/branches trees. This way, we can use svn externals to join
everything up again and make it all look like a multi-module build with a
pom to aggregate the modules. Given the default behavior of silently
appending artifactId to the end of the svn string (and with no known way to
stop it), I'm forced to duplicate the scm tags in every child pom.
I read on another post that something to do with this is on the radar for
some eventual 2.1 release, but am I the only person who's having this much
trouble with this appended artifactId?
As a caveat, I've never before been in the position to dictate the structure
of the source repository until now. Before, every project had to be
identified by its own scm string because they rarely, if ever, followed a
pattern. But now I want to take advantage of the inheritence mechanism for
parent poms in order to force children to conform to a particular format.
Alas, the scm plugin doesn't allow me to do this, and further confounds me
by not documenting that this occurs (or if the documentation exists, it's
very effectively hidden)
On 1/11/07, Mykel Alvis [EMAIL PROTECTED] wrote:
I'm copying and forwarding from another message to see if I can get a
response on this.
I have a parent pom that defines the SCM of itself and all it's children
by using
scm:svn:http://${scm.host}/svnrepos/${object.namespace
}/${artifactId}/trunk
and when I do help:effective-pom, I end up with
scm:svn:http://${scm.host}/svnrepos/${object.namespace
}/${artifactId}/trunk/${artifactId}
Having read another post regarding this, I'm curious if anyone knows the
actual update that I've acquired that makes this error occur.
What do I need to revert to in order to eliminate this problem?
--
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.
Re: Not a circular dependency...
Sorry, I should mention the circular dependency comes about because I have a parent pom to these 2 projects which defines them each as modules... ie. artifactIdparentProject/artifactId modules moduleapplicationArtifact/module modulepluginArtifact/module /modules Andrew. Andrew Franklin wrote: I've got a situation where Maven is telling me I have a circular dependency that should be resolved. Let's say I've got applicationArtifact which provides an interface which I want to consume at compile time in an artifact called pluginArtifact. When applicationArtifact is ready to be packaged, I want to include pluginArtifact in the libs as a runtime dependency. ie. artifactIdapplicationArtifact/artifactId dependencies dependency artifactIdpluginArtifact/artifactId scoperuntime/scope /dependency /dependencies artifactIdpluginArtifact/artifactId dependencies dependency artifactIdapplicationArtifact/artifactId scopecompile/scope !-- such that we can use the common interface -- /dependency /dependencies Maven won't compile the above as it cites a circular dependency. This should work because of the following valid order: 1) compile applicationArtifact (ignore pluginArtifact because it's scoped at Runtime) 2) compile pluginArtifact (include a compile time reference to applicationArtifact) 3) package applicationArtifact (which drags in pluginArtifact) How should I solve this issue? Andrew - 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]
Compiling maven project from eclipse project
Hi, Can anybody please help me out to resolve the issue. I am building using maven in Eclipse,after configuration and setting I am getting a null pointer exception. I am using Maven 2.0.4 and further the same fatal error is there while executing from Command Prompt. Any assistance will be appreciated. Thanks and Regards Vaishali G.P. Email: [EMAIL PROTECTED] This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.com
Re: Not a circular dependency...
Patrick, I appreciate your suggestion, but unfortunately I want to use a 3rd party plugin to generate a web-start application at the package goal. The requirement of running this last goal prevents me from both using assembly, and using ant-run extensions. One solution I can potentially see if using ant-run scripts to generate the web-start component, but that's getting pretty nasty. I was hoping there'd be a cleaner solution. Cheers, Andrew Patrick Schneider wrote: Maybe you could try using the assembly plugin to assemble your final package... and use the assembly descriptor to specify which items should be included in it? This should allow you to remove the pluginArtifact dependency in your applicationArtifact pom. Just a thought... Patrick On 1/11/07, Andrew Franklin [EMAIL PROTECTED] wrote: I've got a situation where Maven is telling me I have a circular dependency that should be resolved. Let's say I've got applicationArtifact which provides an interface which I want to consume at compile time in an artifact called pluginArtifact. When applicationArtifact is ready to be packaged, I want to include pluginArtifact in the libs as a runtime dependency. ie. artifactIdapplicationArtifact/artifactId dependencies dependency artifactIdpluginArtifact/artifactId scoperuntime/scope /dependency /dependencies artifactIdpluginArtifact/artifactId dependencies dependency artifactIdapplicationArtifact/artifactId scopecompile/scope !-- such that we can use the common interface -- /dependency /dependencies Maven won't compile the above as it cites a circular dependency. This should work because of the following valid order: 1) compile applicationArtifact (ignore pluginArtifact because it's scoped at Runtime) 2) compile pluginArtifact (include a compile time reference to applicationArtifact) 3) package applicationArtifact (which drags in pluginArtifact) How should I solve this issue? Andrew - 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]
Compiling maven project from eclipse project
Hi, Can anybody assist with where I am going wrong while running Maven with Command Prompt. The options -g and -X are giving me following error:'Unable to parse command line option-Unrecognised option -g'. And while running goals as install,clean,compile I am getting a fatal error. I will be thankful if you anybody could suggest the remedy to get through. Thanks and Regards Vaishali G.P. Email: [EMAIL PROTECTED] This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.com
Re: Maven Compiler plugin
Hi Wendy, I just wanted to compile some java files in a source folder and move compiled files to some destination directory.I have put this under build section of pom file only.I gave sourcedirectoryjust after build element.It says compiling n number of files then throws this compilation error. Regards Raju Wendy Smoak-3 wrote: On 1/11/07, raju [EMAIL PROTECTED] wrote: Hi, I am trying to compile files in a folder and move them to a directory. It gives the following error: Diagnosis: Compilation failure FATAL ERROR: Error executing Maven for a project org.apache.maven.BuildFailureException: Compilation failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) Read a lot of similar messages but am not clear what exactly causes this. plugin artifactIdmaven-compiler-plugin/artifactId executions execution phasecompile/phase goals goalcompile/goal /goals configuration sourceDirectorywrappers/sourceDirectory I don't see 'sourceDirectory' as a configuration element for the compile goal: http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html It's actually a child element of build: http://maven.apache.org/ref/2.0.4/maven-model/maven.html In general, each module can have only one sourceDirectory and one testSourceDirectory. What are you trying to do? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Maven-Compiler-plugin-tf2958588s177.html#a8292724 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: enabling logging
Good day, Actually, -e sets the logging level to error, while -X sets the logging level to debug. I've seen stack traces being logged as debug in maven. Anyway, if the logs still don't give you much insights to whats happening in your plugin, then I'd guess you'd have to take a look at the source code. Cheers, Franz Ian Springer wrote: -e turns on exception stack traces, and -X turns on debug logging. Btw, I've had the same problem with not being able to turn on debug when running under TeamCity. I asked JetBrains about it, and they said there's currently no way to do it. I keep meaning to file a JIRA with JetBrains for it, so they'll add something in 1.2. | -Original Message- | From: Dmitry Beransky [mailto:[EMAIL PROTECTED] | Sent: Thursday, January 11, 2007 12:08 PM | To: Maven Users List | Subject: Re: enabling logging | | On 1/11/07, Ian Springer [EMAIL PROTECTED] wrote: | Have you tried running mvn with -X ? | | besides, when I do this from CLI, i don't get debug level | messages, just extra exception traces, which is not what I'm after. | | - | 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] -- View this message in context: http://www.nabble.com/enabling-logging-tf2959969s177.html#a8292735 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: Maven Compiler plugin
Good day to you, Raju, I agree with Dawn. It is most likely a simple compilation error on your java files ( and you probably used -X or --debug which would explain why that stacktrace was shown. note: your code did not throw the exception, maven did ). Check the output logs on your console again, you will see the compilation error. Furthermore, AFAIK, using a non-existing parameter under the plugin's configuration tag will not produce any error. But it will not warn you of such as well. Anyway, just check the output log in your console again and you would most probably see there the compilation error on your java files. Cheers, Franz raju wrote: Hi Wendy, I just wanted to compile some java files in a source folder and move compiled files to some destination directory.I have put this under build section of pom file only.I gave sourcedirectoryjust after build element.It says compiling n number of files then throws this compilation error. Regards Raju Wendy Smoak-3 wrote: On 1/11/07, raju [EMAIL PROTECTED] wrote: Hi, I am trying to compile files in a folder and move them to a directory. It gives the following error: Diagnosis: Compilation failure FATAL ERROR: Error executing Maven for a project org.apache.maven.BuildFailureException: Compilation failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) Read a lot of similar messages but am not clear what exactly causes this. plugin artifactIdmaven-compiler-plugin/artifactId executions execution phasecompile/phase goals goalcompile/goal /goals configuration sourceDirectorywrappers/sourceDirectory I don't see 'sourceDirectory' as a configuration element for the compile goal: http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html It's actually a child element of build: http://maven.apache.org/ref/2.0.4/maven-model/maven.html In general, each module can have only one sourceDirectory and one testSourceDirectory. What are you trying to do? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Maven-Compiler-plugin-tf2958588s177.html#a8292739 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
archetype:create fatal error
Hi, I have been trying to run archetype:create commmand but it's failing. C:\mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] - --- [INFO] Building Maven Default Project [INFO]task-segment: [archetype:create] (aggregator-style) [INFO] - --- [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at com.trend.iwss.jscan.appscan.runtime.PolicyRuntime.getB64StrProp(Poli cyRuntime.java:188) at com.trend.iwss.jscan.appscan.runtime.PolicyRuntime.init(PolicyRunti me.java:91) at com.trend.iwss.jscan.appscan.runtime.MiscPolicyRuntime.init(MiscPol icyRuntime.java:132) at com.trend.iwss.jscan.appscan.runtime.MiscPolicyRuntime$Factory.make(M iscPolicyRuntime.java:254) at com.trend.iwss.jscan.appscan.runtime.PolicyRuntime.accessInstance(Pol icyRuntime.java:225) at com.trend.iwss.jscan.appscan.runtime.PolicyRuntime.preFilter(PolicyRu ntime.java:127) at com.trend.iwss.jscan.appscan.runtime.MiscPolicyRuntime.preFilter(Misc PolicyRuntime.java:142) at org.apache.commons.collections.ExtendedProperties.init(ExtendedProp erties.java:197) at org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.ja va:160) at org.apache.velocity.app.VelocityEngine.init(VelocityEngine.java:71) at org.codehaus.plexus.velocity.DefaultVelocityComponent.initialize(Defa ultVelocityComponent.java:56) at org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhas e.execute(InitializePhase.java:16) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(Abstract LifecycleHandler.java:101) at org.codehaus.plexus.component.manager.AbstractComponentManager.startC omponentLifecycle(AbstractComponentManager.java:105) at org.codehaus.plexus.component.manager.AbstractComponentManager.create ComponentInstance(AbstractComponentManager.java:95) at org.codehaus.plexus.component.manager.ClassicSingletonComponentManage r.getComponent(ClassicSingletonComponentManager.java:92) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai ner.java:331) at org.codehaus.plexus.component.composition.FieldComponentComposer.assi gnRequirementToField(FieldComponentComposer.java:129) at org.codehaus.plexus.component.composition.FieldComponentComposer.asse mbleComponent(FieldComponentComposer.java:73) at org.codehaus.plexus.component.composition.DefaultComponentComposerMan ager.assembleComponent(DefaultComponentComposerManager.java:68) at org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPl exusContainer.java:1486) at org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPha se.execute(CompositionPhase.java:29) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(Abstract LifecycleHandler.java:101) at org.codehaus.plexus.component.manager.AbstractComponentManager.startC omponentLifecycle(AbstractComponentManager.java:105) at org.codehaus.plexus.component.manager.AbstractComponentManager.create ComponentInstance(AbstractComponentManager.java:95) at org.codehaus.plexus.component.manager.ClassicSingletonComponentManage r.getComponent(ClassicSingletonComponentManager.java:92) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai ner.java:331) at org.codehaus.plexus.component.composition.FieldComponentComposer.assi gnRequirementToField(FieldComponentComposer.java:129) at org.codehaus.plexus.component.composition.FieldComponentComposer.asse mbleComponent(FieldComponentComposer.java:73) at org.codehaus.plexus.component.composition.DefaultComponentComposerMan ager.assembleComponent(DefaultComponentComposerManager.java:68) at org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPl exusContainer.java:1486) at org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPha se.execute(CompositionPhase.java:29) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(Abstract LifecycleHandler.java:101) at org.codehaus.plexus.component.manager.AbstractComponentManager.startC omponentLifecycle(AbstractComponentManager.java:105) at org.codehaus.plexus.component.manager.AbstractComponentManager.create ComponentInstance(AbstractComponentManager.java:95) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getCo
Re: Just checking my understanding of SNAPSHOT vs real versions
Good day to you, cg, The snapshot policy works. You can specify that under snapshotsupdatePolicy//snapshots of your POM ( ee [1] ), Profile, or Settings.xml ( see [2] ). The accepted value for that tag are daily (the default), always, never, and interval:X (where X is the number of minutes ) ( see [3] ). Cheers, Franz [1] http://maven.apache.org/ref/current/maven-model/maven.html#class_snapshots [2] http://maven.apache.org/ref/current/maven-settings/settings.html#class_snapshots [3] http://maven.apache.org/settings.html#Repositories Christian Goetze-3 wrote: Patrick Schneider wrote: Snapshots are checked once a day by default. You can override this by passing the -U flag, forcing maven to update its snapshots. Here's a good review of snaps, by Brett: http://blogs.maven.org/brett/2005/04/15/1113510156000.html Thanks - so it would seem that snapshot-policy isn't implemented yet - or that I don't know where to set it... otoh, once a day isn't too bad. -- cg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Just-checking-my-understanding-of-SNAPSHOT-vs-real-versions-tf2962583s177.html#a8292748 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: passing custom parameters to a custom compiler-plugin
Good day,
Actually, using @parameter only should be sufficient for it to be configured
via the pom. The @expression is used for setting the parameter via
commandline.
Anyway, Martin M., try specifying in your plugin tag the groupId and version
as well. It might still be trying to configure
org.apache.maven.plugins:maven-compiler-plugin:RELEASE instead of your
custom compiler plugin.
Cheers,
Franz
Jörg Schaible wrote:
Hi Martin,
there's no automation. You need to provide the expression for the
parameter to initialize:
[snip]
/**
* @parameter expression=${testParam}
**/
private String testParam
[snip]
Within the expression you can also address other parts of the POM ...
another typical parameter is:
/**
* The directory for the generated file.
*
* @parameter expression=${project.build.directory}
* @required
*/
private String outputDirectory;
- Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/passing-custom-parameters-to-a-custom-compiler-plugin-tf2958426s177.html#a8292757
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: Maven Compiler plugin
Hi , Thanks everybody for your suggestions. I was able to compile the same using ant-run-plugin and invoking javac task from within maven.Maybe i was not setting sourceDirectory element properly in maven.Now i am able to compile using maven-compiler-plugin also. But is there a way i can chain life cycle phase.For example i am using phasegenerate-sources/phase for ant-run-plugin with run goal and phasecompile/phase with goal as compile for maven-compiler-plugin . Regards Raju franz see wrote: Good day to you, Raju, I agree with Dawn. It is most likely a simple compilation error on your java files ( and you probably used -X or --debug which would explain why that stacktrace was shown. note: your code did not throw the exception, maven did ). Check the output logs on your console again, you will see the compilation error. Furthermore, AFAIK, using a non-existing parameter under the plugin's configuration tag will not produce any error. But it will not warn you of such as well. Anyway, just check the output log in your console again and you would most probably see there the compilation error on your java files. Cheers, Franz raju wrote: Hi Wendy, I just wanted to compile some java files in a source folder and move compiled files to some destination directory.I have put this under build section of pom file only.I gave sourcedirectoryjust after build element.It says compiling n number of files then throws this compilation error. Regards Raju Wendy Smoak-3 wrote: On 1/11/07, raju [EMAIL PROTECTED] wrote: Hi, I am trying to compile files in a folder and move them to a directory. It gives the following error: Diagnosis: Compilation failure FATAL ERROR: Error executing Maven for a project org.apache.maven.BuildFailureException: Compilation failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) Read a lot of similar messages but am not clear what exactly causes this. plugin artifactIdmaven-compiler-plugin/artifactId executions execution phasecompile/phase goals goalcompile/goal /goals configuration sourceDirectorywrappers/sourceDirectory I don't see 'sourceDirectory' as a configuration element for the compile goal: http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html It's actually a child element of build: http://maven.apache.org/ref/2.0.4/maven-model/maven.html In general, each module can have only one sourceDirectory and one testSourceDirectory. What are you trying to do? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Maven-Compiler-plugin-tf2958588s177.html#a8292760 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
assembly plugin, multiple descriptors and manifest modifications
Hi all, I use the assembly plugin to create multiple assemblies from a multi module project: descriptors descriptorsrc/main/assembly/server.xml/descriptor descriptorsrc/main/assembly/client.xml/descriptor /descriptors This works nicely. But how could I make manifest modifications per assembly? Can this be configured an a per assembly basis? Think about different main classes. There seems to be no way to modify the manifest from the descriptor, I could not find manifest related things here http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html Is this a bug or at least a valid enhancement? best regards Bernd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Not a circular dependency...
Good day to you, Andrew, AFAIK, scopes are not considered when it comes to checking for circular dependencies. If you think it should be, feel free to open an issue in [1] under the Dependencies component. Also, you may want to support a pre-package phase which could probably solve your problem ( see the issue [2] and the thread [3] ). With regards to the workaround - I don't know if there is any clean way of doing it. But if you want, you can try and copy the runtime artifact into the directory where your 3rd party plugin will look for the binaries it will package, before the actual packaging. Cheers, Franz [1] http://jira.codehaus.org/browse/MNG [2] http://jira.codehaus.org/browse/MNG-2097 [3] http://www.nabble.com/forum/ViewPost.jtp?post=7667475framed=yskin=177 Andrew Franklin wrote: Patrick, I appreciate your suggestion, but unfortunately I want to use a 3rd party plugin to generate a web-start application at the package goal. The requirement of running this last goal prevents me from both using assembly, and using ant-run extensions. One solution I can potentially see if using ant-run scripts to generate the web-start component, but that's getting pretty nasty. I was hoping there'd be a cleaner solution. Cheers, Andrew Patrick Schneider wrote: Maybe you could try using the assembly plugin to assemble your final package... and use the assembly descriptor to specify which items should be included in it? This should allow you to remove the pluginArtifact dependency in your applicationArtifact pom. Just a thought... Patrick On 1/11/07, Andrew Franklin [EMAIL PROTECTED] wrote: I've got a situation where Maven is telling me I have a circular dependency that should be resolved. Let's say I've got applicationArtifact which provides an interface which I want to consume at compile time in an artifact called pluginArtifact. When applicationArtifact is ready to be packaged, I want to include pluginArtifact in the libs as a runtime dependency. ie. artifactIdapplicationArtifact/artifactId dependencies dependency artifactIdpluginArtifact/artifactId scoperuntime/scope /dependency /dependencies artifactIdpluginArtifact/artifactId dependencies dependency artifactIdapplicationArtifact/artifactId scopecompile/scope !-- such that we can use the common interface -- /dependency /dependencies Maven won't compile the above as it cites a circular dependency. This should work because of the following valid order: 1) compile applicationArtifact (ignore pluginArtifact because it's scoped at Runtime) 2) compile pluginArtifact (include a compile time reference to applicationArtifact) 3) package applicationArtifact (which drags in pluginArtifact) How should I solve this issue? Andrew - 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] -- View this message in context: http://www.nabble.com/Not-a-circular-dependency...-tf2963744s177.html#a8292763 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: maven-war-plugin overwriting options
Is there a way to make a touch of the files from the main war to make them overwrite any other file on the other wars ? This would allow to assign overwrite priority between war files. Regards, Ismael - Mensaje original De: Brian E. Fox [EMAIL PROTECTED] Para: Maven Users List users@maven.apache.org Enviado: jueves, 11 de enero, 2007 20:02:52 Asunto: RE: maven-war-plugin overwriting options There is no control. See this issue: http://jira.codehaus.org/browse/MWAR-66 Even worse, the plugin compares the timestamps of the files individually without regard to which overlay they come from. That means today a file from A might win, but it someone edits a file from B, then B will start to win. It makes the newer versions of the war plugin unuseable for me. It's on my long list to tackle but haven't gotten to it yet. -Original Message- From: ismael [mailto:[EMAIL PROTECTED] Sent: Thursday, January 11, 2007 11:56 AM To: users@maven.apache.org Subject: maven-war-plugin overwriting options When we combine more than one war file as dependencies. Is there a way to specify overwrite priority ? We have three wars a.war, b.war and c.war and we are building a fourth war (target.war) that will combine the three wars. In case we get a collision between this wars, we want a.war to overwrite other file changes (in b.war or c.war). How should we proceed ? We have tested changing the order between a, b and c with no luck pom.xml for final project is: 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;;; modelVersion4.0.0/modelVersion groupIdclient/groupId artifactIdweb/artifactId packagingwar/packaging version1.2.3/version nameweb application for client/name dependencies dependency groupIdtest/groupId artifactIda/artifactId version1.0.0/version typewar/type /dependency dependency groupIdtest/groupId artifactIdb/artifactId version1.0.0/version typewar/type /dependency dependency groupIdtest/groupId artifactIdc/artifactId version1.0.0/version typewar/type /dependency /dependencies build finalNametarget/finalName !-- Quitamos el directorio de ejemplos (samples)-- plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration dependentWarExcludes css/**,js/** /dependentWarExcludes /configuration /plugin /plugins /build /project __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com - 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] __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
