Re: Status of PVCS scm
Ok, subscribe to maven-scm list and we'll help you to understand/implement pvcs provider. I don't know if PVCS provide a java api, but if it isn't open sources, i prefer you use command line for PVCS calling. Emmanuel Ryan Wynn a écrit : On 1/6/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: We need a contributor for PVCS support in maven-scm. PVCS = Serena Dimension, right? A user wanted to do it but he doesn't find the time for it, so the status is not started. Do you want help us to add it in maven-scm? Emmanuel Ryan Wynn a écrit : Does anyone know the status of the work on a PVCS scm plugin for maven? I am really excited about what I have been able to do with Continuum and CVS and looking forward to intregating continuus builds with PVCS at some point. I am pretty sure Serena Dimension is PVCS. I have Merant PVCS Dimension 7.2 with no mention of Serena but I think Serena is the new company name if I am not mistaken. I would love to contribute to maven-scm for pvcs but honestly I would need to get up to speed on the pvcs api. It looks like ant already has a PVCS task so I will start there.
Re: Antw: RE: How can I create ejb-jar and ejb-client-jar withmaven-ejb-plugin in Maven 2?
Hi, Currently, I dont think that we can configure the deployment descriptor path, Please file a jira issue if not yet existing. Thanks, -allan Stefan Rademacher wrote: Hello, thank you. I already had this code in my POM but the packaging was set to jar. Now I changed it to ejb and it works fine. Now there is one more problem. The maven-ejb-plugin doesn't find the deployment descriptors. It searches in target/classes/META-INF but the files are generated by xdoclet-maven-plugin to target/generated-sources/xdoclet/META-INF. What is the right way to make the maven-ejb-plugin find the deployment descriptors? Thanks for your help! Bye, Stefan [EMAIL PROTECTED] 05.01.2006 12:24:48 To generate both jars, you need to tell the plugin that you want both of them as follows: project ... build ... plugins ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration generateClienttrue/generateClient /configuration /plugin ... plugins ... /build ... /project -Original Message- From: Stefan Rademacher [mailto:[EMAIL PROTECTED] Sent: Thursday, January 05, 2006 03:14 To: Maven Users List Subject: How can I create ejb-jar and ejb-client-jar withmaven-ejb-plugin in Maven 2? Hello, Could anyone provide me with a working example of a project, which uses the maven-ejb-plugin to generate jar files for the ejb-module and for the ejb-client? (I use the xdoclet-maven-plugin to generate the ejb artifacts to the folder 'targets/generated-sources/xdoclet') I'm quite new to maven and don't understand the usage example given on plugins' webpage (http://maven.apache.org/plugins/maven-ejb-plugin/howto.html). When I integrate that XML to my POM, nothing happens. Only calling 'mvn ejb:ejb' manually works, as long as I copy the META-INF-folder from 'target/generated-sources/xdoclet' to 'target/classes' first. How can I integrate this into my build process (mvn package: ejb-jar and ejb-client-jar are generated. mvn install: ejb-jar and ejb-client-jar are copied to my local repository...)? Thanks a lot in advance! Regards, Stefan - 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]
M2: Build error: maven-compiler-plugin does not exist
mvn clean:clean -e -X gives me
[ERROR] BUILD ERROR
[INFO] -
---
[INFO] The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not
exist or no valid version could be found
Any suggestions where to look? I get more or less the same
on windows and linux with m2 and m2-alpha2.
And it worked fine until yesterday.
The complete output:
+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from:
'/home/smorgrav/.m2/plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'/usr/local/maven/conf/plugin-registry.xml'
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'clean'.
[DEBUG] maven-compiler-plugin: using locally installed snapshot
[DEBUG] Artifact not found - using stub model: Unable to determine the
latest version
org.apache.maven.plugins:maven-compiler-plugin:LATEST:pom
[DEBUG] Using defaults for missing POM
org.apache.maven.plugins:maven-compiler-plugin:pom:LATEST
[DEBUG] maven-compiler-plugin: using locally installed snapshot
[DEBUG] Artifact not found - using stub model: Unable to determine the
release version
org.apache.maven.plugins:maven-compiler-plugin:RELEASE:pom
[DEBUG] Using defaults for missing POM
org.apache.maven.plugins:maven-compiler-plugin:pom:RELEASE
[INFO] -
---
[ERROR] BUILD ERROR
[INFO] -
---
[INFO] The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not
exist or no valid version could be found
[INFO] -
---
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
'org.apache.maven.plugins:maven-compiler-plugin' does not exist or no valid
version could be found
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLife
cycleExecutor.java:1124)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(Defaul
tLifecycleExecutor.java:1305)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggrega
tionNeeds(DefaultLifecycleExecutor.java:376)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle
Executor.java:132)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException:
The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not exist
or no valid version could be found
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVer
sion(DefaultPluginVersionManager.java:225)
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVer
sion(DefaultPluginVersionManager.java:87)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManag
er.java:158)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLife
cycleExecutor.java:1095)
... 14 more
[INFO] -
---
[INFO] Total time: 1 second
[INFO] Finished at: Fri Jan 06 10:18:16 GMT 2006
[INFO] Final Memory: 1M/2M
[INFO] -
---
-Original Message-
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: 6. januar 2006 08:54
To: Maven Users List
Subject: SCM username/password lookup
There are 3 places to look for in this order
Command line
settings.xml
connectionUrl
However in maven-release-plugin, if user does not provide username
via command line (ie -Dusername=xyz),
username is default to system property ${user.name} and by passing
settings.xml.
is it a bug?
-Dan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE : [m2] war plugin and resources filtering
Hi,
Those solutions looks OK for any resources _except_ for web.xml
Indeed I seem to me that in the package phase the original web.xml file
is copied in the target directory, overiding the one that has been
previously filtered.
Anyway this leads me to wonder if I am going in the right direction (as
I am a Maven newbie). May be the customization of the web app params
depending on the target physical node it will be deployed, should not be
done in the war build lifecycle but in an assembly project.
Do you have some good practice advices about this ?
Thanks for your help,
--
Laurent
Olivier Lamy wrote:
Hi,
To add resources (struts, tiles and others).
Two solutions :
- made your own war plugin (look at a solution proposed
http://jira.codehaus.org/browse/MNG-1683)
- using something as :
build
directorybuild/directory
outputDirectorybuild/classes/outputDirectory
resources
resource
targetPathpath to ${webappDirectory}/WEB-INF/targetPath
directorysrc/main/resources/struts/directory
includes
include**/*.xml/include
/includes
filteringtrue/filtering
/resource
I don't like it because all web resources are included when just made
mvn compile
- Olivier
-Message d'origine-
De : Laurent Berteau [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 5 janvier 2006 18:35
À : Maven Users List
Objet : Re: [m2] war plugin and resources filtering
Hi,
I think this is related to http://jira.codehaus.org/browse/MNG-791
Is there a known workaround to filter web.xml ?
This issue is blocking me from using the war plugin.
I presume I am not the only person in that situation. What kind of
solutions are you people using ?
Best regards,
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2: Build error: maven-compiler-plugin does not exist
Hi,
Please refer to this link
http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-HowdoIresolvethe%22%3Cpluginname%3Edoesnotexistornovalidversion%22error%3F
-allan
Torbjørn Smørgrav wrote:
mvn clean:clean -e -X gives me
[ERROR] BUILD ERROR
[INFO] -
---
[INFO] The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not
exist or no valid version could be found
Any suggestions where to look? I get more or less the same
on windows and linux with m2 and m2-alpha2.
And it worked fine until yesterday.
The complete output:
+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from:
'/home/smorgrav/.m2/plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'/usr/local/maven/conf/plugin-registry.xml'
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'clean'.
[DEBUG] maven-compiler-plugin: using locally installed snapshot
[DEBUG] Artifact not found - using stub model: Unable to determine the
latest version
org.apache.maven.plugins:maven-compiler-plugin:LATEST:pom
[DEBUG] Using defaults for missing POM
org.apache.maven.plugins:maven-compiler-plugin:pom:LATEST
[DEBUG] maven-compiler-plugin: using locally installed snapshot
[DEBUG] Artifact not found - using stub model: Unable to determine the
release version
org.apache.maven.plugins:maven-compiler-plugin:RELEASE:pom
[DEBUG] Using defaults for missing POM
org.apache.maven.plugins:maven-compiler-plugin:pom:RELEASE
[INFO] -
---
[ERROR] BUILD ERROR
[INFO] -
---
[INFO] The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not
exist or no valid version could be found
[INFO] -
---
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
'org.apache.maven.plugins:maven-compiler-plugin' does not exist or no valid
version could be found
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLife
cycleExecutor.java:1124)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(Defaul
tLifecycleExecutor.java:1305)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggrega
tionNeeds(DefaultLifecycleExecutor.java:376)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle
Executor.java:132)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException:
The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not exist
or no valid version could be found
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVer
sion(DefaultPluginVersionManager.java:225)
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVer
sion(DefaultPluginVersionManager.java:87)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManag
er.java:158)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLife
cycleExecutor.java:1095)
... 14 more
[INFO] -
---
[INFO] Total time: 1 second
[INFO] Finished at: Fri Jan 06 10:18:16 GMT 2006
[INFO] Final Memory: 1M/2M
[INFO] -
---
-Original Message-
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: 6. januar 2006 08:54
To: Maven Users List
Subject: SCM username/password lookup
There are 3 places to look for in this order
Command line
settings.xml
connectionUrl
However in maven-release-plugin, if user does not provide username
via command line (ie -Dusername=xyz),
username is default to system property ${user.name} and by passing
settings.xml.
is it a bug?
-Dan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: M1 or M2?
Hi, This actually works, thanks! What is annoying, is that the commons-logging is required by multiple dependencies of the ear. So I have to put an exclusion in each dependency. Edwin -Oorspronkelijk bericht- Van: Alexandre Poitras [mailto:[EMAIL PROTECTED] Verzonden: donderdag 5 januari 2006 14:33 Aan: Maven Users List Onderwerp: Re: M1 or M2? The jar probably come from transitive dependencies. Use the exclude options to get ride of it in the dependencies declaration providing the jar. It should do the trick. I have no idea about Java WebStart since I haven't use it myself. On 1/4/06, Edwin van der Elst [EMAIL PROTECTED] wrote: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: RE : [m2] war plugin and resources filtering
-Original Message-
From: Laurent Berteau [mailto:[EMAIL PROTECTED]
Sent: Friday, January 06, 2006 9:33 AM
To: Maven Users List
Subject: Re: RE : [m2] war plugin and resources filtering
Hi,
Those solutions looks OK for any resources _except_ for web.xml
Indeed I seem to me that in the package phase the original web.xml file
is copied in the target directory, overiding the one that has been
previously filtered.
Anyway this leads me to wonder if I am going in the right direction (as
I am a Maven newbie). May be the customization of the web app params
depending on the target physical node it will be deployed, should not be
done in the war build lifecycle but in an assembly project.
Do you have some good practice advices about this ?
Thanks for your help,
--
Laurent
Olivier Lamy wrote:
Hi,
To add resources (struts, tiles and others).
Two solutions :
- made your own war plugin (look at a solution proposed
http://jira.codehaus.org/browse/MNG-1683)
- using something as :
build
directorybuild/directory
outputDirectorybuild/classes/outputDirectory
resources
resource
targetPathpath to ${webappDirectory}/WEB-INF/targetPath
Try: targetPath../contentsOfYourFinalName/targetPath
ex: targetPath../${artifactId}-${version}/targetPath
directorysrc/main/resources/struts/directory
includes
include**/*.xml/include
/includes
filteringtrue/filtering
/resource
best regards,
--
Michal Stochmialek
IT Department, Technology Division
Euro Bank S.A.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE : RE : [m2] war plugin and resources filtering
Hi,
An other solution is to use antrun-plugin (attached to phase
process-classes).
But this attachment is not very good (I like to have a phase executed
just before package process-package-resources), because all of this jobs
are made when I run junit tests.
For few resources, I don't need to do this for just a junit test.
What do you need to do on the web.xml ?
Perso, I use xdoclet plugin to generate it and configue the war plugin :
webXml${basedir}/target/xdoclet/web.xml/webXml
- Olivier
-Message d'origine-
De : Laurent Berteau [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 6 janvier 2006 09:33
À : Maven Users List
Objet : Re: RE : [m2] war plugin and resources filtering
Hi,
Those solutions looks OK for any resources _except_ for web.xml Indeed I
seem to me that in the package phase the original web.xml file
is copied in the target directory, overiding the one that has been
previously filtered.
Anyway this leads me to wonder if I am going in the right direction (as
I am a Maven newbie). May be the customization of the web app params
depending on the target physical node it will be deployed, should not be
done in the war build lifecycle but in an assembly project.
Do you have some good practice advices about this ?
Thanks for your help,
--
Laurent
Olivier Lamy wrote:
Hi,
To add resources (struts, tiles and others).
Two solutions :
- made your own war plugin (look at a solution proposed
http://jira.codehaus.org/browse/MNG-1683)
- using something as :
build
directorybuild/directory
outputDirectorybuild/classes/outputDirectory
resources
resource
targetPathpath to ${webappDirectory}/WEB-INF/targetPath
directorysrc/main/resources/struts/directory
includes
include**/*.xml/include
/includes
filteringtrue/filtering
/resource
I don't like it because all web resources are included when just made
mvn compile
- Olivier
-Message d'origine-
De : Laurent Berteau [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 5 janvier 2006 18:35
À : Maven Users List
Objet : Re: [m2] war plugin and resources filtering
Hi,
I think this is related to http://jira.codehaus.org/browse/MNG-791
Is there a known workaround to filter web.xml ?
This issue is blocking me from using the war plugin.
I presume I am not the only person in that situation. What kind of
solutions are you people using ?
Best regards,
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, any attachments and the information contained therein (this
message) are confidential and intended solely for the use of the addressee(s).
If you have received this message in error please send it back to the sender
and delete it. Unauthorized publication, use, dissemination or disclosure of
this message, either in whole or in part is strictly prohibited.
--
Ce message électronique et tous les fichiers joints ainsi que les informations
contenues dans ce message ( ci après le message ), sont confidentiels et
destinés exclusivement à l'usage de la personne à laquelle ils sont adressés.
Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur
et de le détruire. Toutes diffusion, publication, totale ou partielle ou
divulgation sous quelque forme que se soit non expressément autorisées de ce
message, sont interdites.
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2] jar sources in eclipse
Hello i have a multimodule project (actually, 2 modules). I wanted to have sources of dependency jar to be usable within eclipse, so I issued: mvn -Declipse.downloadSources=true eclipse:eclipse it created .classpath and .project for both modules, and in my local repository it downloaded sources: problem is I don't know how to access them within eclipse (3.1, linux). i have installed m2 plugin. any pointer is appreciated. -- To Iterate is Human, to Recurse, Divine James O. Coplien, Bell Labs
Re: accessing environment variable in settings.xml or pom.xml
On 05.01.2006, at 22:31, Adam Altemus wrote:
Greetings, my name is Adam Altemus. I am a computer science student @
Indiana University of PA. and am doing an internship. I read in a
thread that you said that you can acess environment variables in
the pom.xml
from the settings.xml. Could you explain to me how this can be done?
AFAIK, you can use java system properties like ${user.home} etc. (see
http://java.sun.com/docs/books/tutorial/essential/system/
properties.html ), but not your operating system's environment
variables (like $CATALINA_HOME, etc).
There has been quite some discussion about this, so search the
archives if you want to know why this is so (build portability, IIRC).
Cheers,
-Ralph.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: M2: Build error: maven-compiler-plugin does not exist
I know Im behind a http cache... is that the same as a http proxy? An other observation: Maven doesn't even try to lookup the remote repository (I think). But if I hack the DefaultArtifact version to match the version in my local repository (and not RELEASE), it tries to download that version. T -Original Message- From: Allan Ramirez [mailto:[EMAIL PROTECTED] Sent: 6. januar 2006 09:35 To: Maven Users List Subject: Re: M2: Build error: maven-compiler-plugin does not exist Hi, Please refer to this link http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-HowdoIresolvethe%22%3Cp luginname%3Edoesnotexistornovalidversion%22error%3F -allan Torbjørn Smørgrav wrote: mvn clean:clean -e -X gives me [ERROR] BUILD ERROR [INFO] - --- [INFO] The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not exist or no valid version could be found Any suggestions where to look? I get more or less the same on windows and linux with m2 and m2-alpha2. And it worked fine until yesterday. The complete output: + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: '/home/smorgrav/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/usr/local/maven/conf/plugin-registry.xml' [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'clean'. [DEBUG] maven-compiler-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the latest version org.apache.maven.plugins:maven-compiler-plugin:LATEST:pom [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-compiler-plugin:pom:LATEST [DEBUG] maven-compiler-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the release version org.apache.maven.plugins:maven-compiler-plugin:RELEASE:pom [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-compiler-plugin:pom:RELEASE [INFO] - --- [ERROR] BUILD ERROR [INFO] - --- [INFO] The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not exist or no valid version could be found [INFO] - --- [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLif e cycleExecutor.java:1124) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(Defau l tLifecycleExecutor.java:1305) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggreg a tionNeeds(DefaultLifecycleExecutor.java:376) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycl e Executor.java:132) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3 9 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l .java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not exist or no valid version could be found at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVe r sion(DefaultPluginVersionManager.java:225) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVe r sion(DefaultPluginVersionManager.java:87) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginMana g er.java:158) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLif e cycleExecutor.java:1095) ... 14 more [INFO] - --- [INFO] Total time: 1 second [INFO] Finished at: Fri Jan 06 10:18:16 GMT 2006 [INFO] Final Memory: 1M/2M [INFO] - --- -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: 6. januar 2006 08:54 To:
RE: xmlbeans plugin
I filed a JIRA issue with xmlbeans: http://jira.codehaus.org/browse/MOJO-222 John Wells (Aziz) [EMAIL PROTECTED] -Original Message- From: Napoleon Esmundo Ramirez [mailto:[EMAIL PROTECTED] Sent: Thursday, January 05, 2006 10:04 PM To: Maven Users List Subject: Re: xmlbeans plugin Hello! Looks like it's not in the central repo. You could file a JIRA issue on that in the MAVENUPLOAD space. :) Nap On 1/6/06, John Wells [EMAIL PROTECTED] wrote: John Wells (Aziz) [EMAIL PROTECTED] I am trying to use the XML beans plugin from http://mojo.codehaus.org/xmlbeans-maven-plugin/ However, I get the following: [ERROR] BUILD ERROR [INFO] -- --- [INFO] Failed to resolve artifact. GroupId: xmlbeans ArtifactId: xmlbeans-jsr173-api Version: 2.0-dev Reason: Unable to download the artifact from any repository xmlbeans:xmlbeans-jsr173-api:2.0-dev:jar from the specified remote repositories: central (http://repo1.maven.org/maven2), CoreRepo (http://www-tux/wls/maven2/repository) Looks like there is a missing file in the repository. Where is this file supposed to live? John Wells (Aziz) [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: Antw: RE: How can I create ejb-jar and ejb-client-jar withmaven-ejb-plugin in Maven 2?
Hello Aramirez, I already received a reply on my question. The given solution was to specify the destDir attribute of deploymentdescriptor. This works fine, I just thought there might be a better solution (e.g. generating the deployment descriptors to generated-sources/xdoclet and moving them during compile, along with the generation of the class files). But there doesn't seem to be a need for a jira issue. Thanks, Stefan [EMAIL PROTECTED] 06.01.2006 09:21:10 Hi, Currently, I dont think that we can configure the deployment descriptor path, Please file a jira issue if not yet existing. Thanks, -allan Stefan Rademacher wrote: Hello, thank you. I already had this code in my POM but the packaging was set to jar. Now I changed it to ejb and it works fine. Now there is one more problem. The maven-ejb-plugin doesn't find the deployment descriptors. It searches in target/classes/META-INF but the files are generated by xdoclet-maven-plugin to target/generated-sources/xdoclet/META-INF. What is the right way to make the maven-ejb-plugin find the deployment descriptors? Thanks for your help! Bye, Stefan [EMAIL PROTECTED] 05.01.2006 12:24:48 To generate both jars, you need to tell the plugin that you want both of them as follows: project ... build ... plugins ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration generateClienttrue/generateClient /configuration /plugin ... plugins ... /build ... /project -Original Message- From: Stefan Rademacher [mailto:[EMAIL PROTECTED] Sent: Thursday, January 05, 2006 03:14 To: Maven Users List Subject: How can I create ejb-jar and ejb-client-jar withmaven-ejb-plugin in Maven 2? Hello, Could anyone provide me with a working example of a project, which uses the maven-ejb-plugin to generate jar files for the ejb-module and for the ejb-client? (I use the xdoclet-maven-plugin to generate the ejb artifacts to the folder 'targets/generated-sources/xdoclet') I'm quite new to maven and don't understand the usage example given on plugins' webpage (http://maven.apache.org/plugins/maven-ejb-plugin/howto.html). When I integrate that XML to my POM, nothing happens. Only calling 'mvn ejb:ejb' manually works, as long as I copy the META-INF-folder from 'target/generated-sources/xdoclet' to 'target/classes' first. How can I integrate this into my build process (mvn package: ejb-jar and ejb-client-jar are generated. mvn install: ejb-jar and ejb-client-jar are copied to my local repository...)? Thanks a lot in advance! Regards, Stefan - 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: xmlbeans plugin
To make it work you need to add this dependency dependency groupIdstax/groupId artifactIdstax/artifactId version1.1.1-dev/version scopecompile/scope exclusions exclusion artifactIdxmlbeans-jsr173-api/artifactId groupIdxmlbeans/groupId /exclusion /exclusions /dependency Pozdrawiam Sebastian Błoch John Wells [EMAIL PROTECTED] 2006-01-05 22:54 Please respond to Maven Users List users@maven.apache.org To Maven Users List users@maven.apache.org cc Subject xmlbeans plugin John Wells (Aziz) [EMAIL PROTECTED] I am trying to use the XML beans plugin from http://mojo.codehaus.org/xmlbeans-maven-plugin/ However, I get the following: [ERROR] BUILD ERROR [INFO] -- --- [INFO] Failed to resolve artifact. GroupId: xmlbeans ArtifactId: xmlbeans-jsr173-api Version: 2.0-dev Reason: Unable to download the artifact from any repository xmlbeans:xmlbeans-jsr173-api:2.0-dev:jar from the specified remote repositories: central (http://repo1.maven.org/maven2), CoreRepo (http://www-tux/wls/maven2/repository) Looks like there is a missing file in the repository. Where is this file supposed to live? John Wells (Aziz) [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: You need to define a connectionUrl parameter.
Christopher Cobb wrote: -Original Message- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] It's defined in your pom.xml. http://maven.apache.org/guides/introduction/introduction-to-the-pom.html http://maven.apache.org/maven-model/maven.html#class_scm Thanks for those URL's, although I don't see explicit mention of connectionUrl in either place. Are you talking about the connection element that I already have in my pom? scm connectionscm:svn:svn://coe10/GCSS/gvis-wms/gvis/trunk//connection /scm Yes Is there anything wrong with the URL that I am using above? Not that I can see. I thought that the error was probably talking about some other kind of parameter. The error you get comes from the maven-scm-plugin and means that there is no element project.scm.connection in the pom. Please run: mvn validate to make sure that your pom is valid. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m201] Plugin Dependency Configuration
I am trying to configure a plugin with dependencies. According to the current project descriptor document (http://maven.apache.org/maven-model/maven.html), I should do the following: project build plugins plugin groupId/ artifactId/ dependencies dependency groupId/ artifactId/ /dependency /dependencies configuration/ /plugin /plugins /build /project When I do this, I get a parse error on the POM that the dependencies tag within the plugin is unrecognized. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M1 or M2?
Yeah I know but I think the problem comes more from having dependencies already shipped with JBoss. I mean it's great when you don't use a program to handle your dependencies but with Maven they have no use. I would probably get ride of them anyway, with or without Maven since the handling of different versions can cause a lot of problems. Or at least leave them out of my deployed applications classpath. On 1/6/06, Edwin van der Elst [EMAIL PROTECTED] wrote: Hi, This actually works, thanks! What is annoying, is that the commons-logging is required by multiple dependencies of the ear. So I have to put an exclusion in each dependency. Edwin -Oorspronkelijk bericht- Van: Alexandre Poitras [mailto:[EMAIL PROTECTED] Verzonden: donderdag 5 januari 2006 14:33 Aan: Maven Users List Onderwerp: Re: M1 or M2? The jar probably come from transitive dependencies. Use the exclude options to get ride of it in the dependencies declaration providing the jar. It should do the trick. I have no idea about Java WebStart since I haven't use it myself. On 1/4/06, Edwin van der Elst [EMAIL PROTECTED] wrote: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: NullPointerException while running mvn site:site
Could you please send me your dependency tag for the plug-in? Thanks, Sandeep -Original Message- From: Hervé BOUTEMY [mailto:[EMAIL PROTECTED] Sent: Thursday, January 05, 2006 3:07 PM To: Maven Users List Subject: Re: NullPointerException while running mvn site:site I confirm : svn has a fix (modified since the patch from MNG-1455) I built and installed the plugin locally, and it works nicely Le Jeudi 05 Janvier 2006 09:04, Bernd Bohmann a écrit : Hello, see http://jira.codehaus.org/browse/MNG-1455 but the patch was reverted. I think the maven-project-info-reports-plugin in the svn has a fix for it. Maybe a SNAPSHOT version is available. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- ***National City made the following annotations --- This communication is a confidential and proprietary business communication. It is intended solely for the use of the designated recipient(s). If this communication is received in error, please contact the sender and delete this communication. === - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Support for mojos written in Ant
Hi, what happened to the maven-antfile-plugin? I can't find it anywhere... I figured it provides the possiblity to use ANT as mojo language, but the whole thing is a little unclear to me. My attention was raised by the 2.0.1 annoncement, and then I found this on the mailinglist: http://www.nabble.com/Support-for-mojos-written-in-Ant-t791610.html#a2080582 Would be great if someone could shed some light on this... Regards, Michael -- Giniality AG - Michael Böckling; Steinenberg 21, CH-4051 Basel P: +41 61 226 99 63 - F: +41 61 226 99 69 [EMAIL PROTECTED]; http://www.giniality.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Support for mojos written in Ant
-Original Message- From: Michael Böckling [mailto:[EMAIL PROTECTED] Sent: Friday, January 06, 2006 1:56 PM To: Maven Users List Subject: Support for mojos written in Ant Hi, what happened to the maven-antfile-plugin? I can't find it anywhere... I figured it provides the possiblity to use ANT as mojo language, but the whole thing is a little unclear to me. My attention was raised by the 2.0.1 annoncement, and then I found this on the mailinglist: http://www.nabble.com/Support-for-mojos-written-in-Ant- t791610.html#a2080582 Would be great if someone could shed some light on this... I was trying to write a ant-mojo few weeks ago. I had similar problems with documentation. After little investigation I found the link below. I believe it will be helpful. http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-plugin-tools/maven-plugin-tools-ant/integration-tests/ I've tried to write my plugin basing on those test cases, but I'm having following exception. I've also tried to build those test cases, but the problem is the same. Maybe you will have more luck ;) [INFO] [plugin:descriptor] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org.apache.maven.tools.plugin.extractor.AbstractScriptedMojoDescriptorExtractor.extractMojoDescriptors(Ljava/util/Map;Lorg/apache/maven/plugin/descriptor/PluginDescriptor;)Ljava/util/List; [INFO] [INFO] Trace java.lang.AbstractMethodError: org.apache.maven.tools.plugin.extractor.AbstractScriptedMojoDescriptorExtractor.extractMojoDescriptors(Ljava/util/Map;Lorg/apache/maven/plugin/descri ptor/PluginDescriptor;)Ljava/util/List; at org.apache.maven.tools.plugin.extractor.AbstractScriptedMojoDescriptorExtrator.execute(AbstractScriptedMojoDescriptorExtractor.java:32) best regards, -- Michal Stochmialek IT Department, Technology Division Euro Bank S.A. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: call for testers: scp wagon
Hi, Excellent! It works! On our local network everything has been running smoothly since early 2.0-beta releases, but we have experienced problems on slow network connections (repo in Oslo, Norway, client in Manila, Philipines). Our repo is on a Linux machine. File permissions have been set to drwxrwsr-x on folders to allow for sticky group memberhip. In addition we had to specify filePermissions0664/filePermissions on the servers in every developers settings.xml file. This is to allow for users to release the same artifacts (writes to the repo metadata files). Thanks! Ørjan Austvold Brett Porter wrote: Hi, In the lead up to the 2.0.2 release, I'd like anyone experiencing: [WAGONSSH-28] session is down [WAGONSSH-30] hangs during deployment to test the following wagon snapshots: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/wagon/wagon-ssh/1.0-alpha-6-SNAPSHOT/wagon-ssh-1.0-alpha-6-20060105.062346-2.jar by including it in your $M2_HOME/lib directory. Please also include: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6-SNAPSHOT/wagon-provider-api-1.0-alpha-6-20060105.062346-7.jar and http://www.ibiblio.org/maven2/com/jcraft/jsch/0.1.24/jsch-0.1.24.jar Replace any existing wagon/jsch libraries. Another way to test is to pick up the following integration build instead: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060105.071501.tar.gz With this build, you can also test scpexe and sftp if you were having any problems with them. Thanks! - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [M2] adding source-dir within maven-antrun-plugin tasks
One solution is to add all your directories to the maven-compile-plugin
like this:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.0/version
configuration
includes
include
implementation=java.lang.String../src/**/*.java/include
include
implementation=java.lang.String../generated-src/**/*.java/include
/includes
/configuration
/plugin
It's a kludge though. Other plugins won't know about the extra source
directory. I.e. the maven-eclipse-plugin will not generate multiple
source directories for you :(
There really ought to be a way to add multiple sourceDirectories in the
POM like you can with Maven 1. But the Maven developers seem dead
against it. Short of patching Maven yourself there is not real solution.
-Oorspronkelijk bericht-
Van: Jens Zastrow [mailto:[EMAIL PROTECTED]
Verzonden: vrijdag 6 januari 2006 14:04
Aan: users@maven.apache.org
Onderwerp: [M2] adding source-dir within maven-antrun-plugin tasks
Hi,
i need to use the sun-jaxb-compiler (xjc) which only seems to work
correctly with the antrun plugin.
The problem now is to put the generated .java files in a directory which
is a pom-source-folder or
one which is later added to the pom-source-folders.
Since i dont know a way to do this fromt he ant snipshet, my current -
bad - solution is to generate
them into ${basedir}/src/main/java.
Any ideas?
Thanks
jens
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phasevalidate/phase
configuration
tasks
taskdef name=xjc
classname=com.sun.tools.xjc.XJCTask/
xjc
schema=src/main/xsd/de/dailab/util/jaxb/agentrole/AgentRole.xsd
package=de.dailab.util.jaxb.agentrole
target=${basedir}/src/main/java
extension=false/
copy
todir=${project.build.directory}/classes
fileset
dir=${basedir}/src/main/java excludes=**/*.java/
/copy
/tasks
/configuration
/executions
/plugin
-
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]
reusing a little mvc-login-project??
hello, i don't know if i'm right here, but i didn't know where else to go. so please give me some hint, where to go, if this list isn't right for my question. question: i have one little project (using netbeans 4.1) with jsps, servlet and class to manage logging-in and user checking. now i want to use it in a bigger project. what must i do, that i don't have to rewrite anything? please help! greetings from very winterly white salzburg hans horwath - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] adding source-dir within maven-antrun-plugin tasks
Below is an example of how I've used Sun's XJC Ant task from Maven. The
sourceRoot tag is how I added the generated .java files to the sources
that are compiled. I also moved the generated non-java files to the
resources directory so that they would get included with the artifact
(JAR, WAR, etc.). All the dependencies were third party JARs that I had
to manually install in my repository.
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phasegenerate-sources/phase
goals
goalrun/goal
/goals
/execution
/executions
configuration
tasks
taskdef name=xjc classname=com.sun.tools.xjc.XJCTask/
mkdir
dir=${project.build.directory}/generated-sources/jaxb/src/main/java/
xjc
target=${project.build.directory}/generated-sources/jaxb/src/main/java
schema=${basedir}/src/main/xsd/myschema.xsd
package=com.mypackage
produces
dir=${project.build.directory}/generated-sources/jaxb/src/main/java/com/mypackage
includes=**/* /
/xjc
mkdir
dir=${project.build.directory}/generated-sources/jaxb/src/main/resources/
move
todir=${project.build.directory}/generated-sources/jaxb/src/main/resources
preservelastmodified=true
includeEmptyDirs=false
fileset
dir=${project.build.directory}/generated-sources/jaxb/src/main/java
excludes=**/*.java /
/move
/tasks
sourceRoot${project.build.directory}/generated-sources/jaxb/src/main/java/sourceRoot
/configuration
dependencies
dependency
groupIdcom.sun.tools.xjc/groupId
artifactIdjaxb-xjc/artifactId
version1.0.5/version
/dependency
dependency
groupIdjavax.xml.bind/groupId
artifactIdjaxb-api/artifactId
version1.0.5/version
/dependency
dependency
groupIdcom.sun.xml.bind/groupId
artifactIdjaxb-impl/artifactId
version1.0.5/version
/dependency
dependency
groupIdcom.sun.xml.bind/groupId
artifactIdjaxb-libs/artifactId
version1.0.5/version
/dependency
dependency
groupIdcom.sun.xml/groupId
artifactIdxsdlib/artifactId
version20050614/version
/dependency
dependency
groupIdorg.relaxng.datatype/groupId
artifactIdrelaxngDatatype/artifactId
version1.0/version
/dependency
/dependencies
/plugin
Good luck,
Richard Allen
Jens Zastrow wrote:
Hi,
i need to use the sun-jaxb-compiler (xjc) which only seems to work
correctly with the antrun plugin.
The problem now is to put the generated .java files in a directory which
is a pom-source-folder or
one which is later added to the pom-source-folders.
Since i dont know a way to do this fromt he ant snipshet, my current -
bad - solution is to generate
them into ${basedir}/src/main/java.
Any ideas?
Thanks
jens
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phasevalidate/phase
configuration
tasks
taskdef name=xjc
classname=com.sun.tools.xjc.XJCTask/
xjc
schema=src/main/xsd/de/dailab/util/jaxb/agentrole/AgentRole.xsd
package=de.dailab.util.jaxb.agentrole
target=${basedir}/src/main/java
extension=false/
copy
todir=${project.build.directory}/classes
fileset
dir=${basedir}/src/main/java excludes=**/*.java/
/copy
/tasks
/configuration
/executions
/plugin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] adding source-dir within maven-antrun-plugin tasks
Antrun has two extra config options:
sourceRoot/sourceRoot
testSourceRoot/testSourceRoot
That you can use to add a directory to either the src path or test src
path. (testSourceRoot requires antrun 1.1 released on wednesday)
Dan
On Friday 06 January 2006 08:04, Jens Zastrow wrote:
Hi,
i need to use the sun-jaxb-compiler (xjc) which only seems to work
correctly with the antrun plugin.
The problem now is to put the generated .java files in a directory
which is a pom-source-folder or
one which is later added to the pom-source-folders.
Since i dont know a way to do this fromt he ant snipshet, my current -
bad - solution is to generate
them into ${basedir}/src/main/java.
Any ideas?
Thanks
jens
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phasevalidate/phase
configuration
tasks
taskdef name=xjc
classname=com.sun.tools.xjc.XJCTask/
xjc
schema=src/main/xsd/de/dailab/util/jaxb/agentrole/AgentRole.xsd
package=de.dailab.util.jaxb.agentrole
target=${basedir}/src/main/java
extension=false/
copy
todir=${project.build.directory}/classes
fileset
dir=${basedir}/src/main/java excludes=**/*.java/
/copy
/tasks
/configuration
/executions
/plugin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 + XDoclet
plugin groupIdorg.codehaus.mojo/groupId artifactIdxdoclet-maven-plugin/ artifactId executions execution phasegenerate-sources/ phase goals goalxdoclet/ goal /goals configuration tasks hibernatedoclet destdir=./src/main/java excludedtags=@version,@author,@todo,@see,@desc force=./src/main/java verbose=true fileset dir=./src/main/java include name=**/modelo/*.java / / fileset hibernate version=3.0 / / hibernatedoclet springdoclet destdir=./src/main/webapp/WEB-INF force=true fileset dir=./src/main/java include name=**/actions/*.java / / fileset springxml destinationFile=quirografarios2-action-servlet.xml defaultAutowire=no defaultLazyInit=true / / springdoclet springdoclet destdir=./src/main/webapp/WEB-INF mergeDir=./src/main/resources/metadata/metadata-spring force=true fileset dir=./src/main/java include name=**/*.java / exclude name=**/actions/*.java / / fileset springxml destinationFile=quirografarios2-application-context.xml defaultAutowire=no defaultLazyInit=true / / springdoclet /tasks /configuration /execution /executions /plugin Saludos Ing. Henry Molina CONSULTOR INFORMATICO PNUD-IESS Dmitriy D. [EMAIL PROTECTED] 05/01/2006 03:05 Por favor, responda a Maven Users List users@maven.apache.org Para users@maven.apache.org cc Asunto Maven2 + XDoclet Hi! Has anyone experienced using xdoclet plugin on maven2? I need to perform several xdoclet tasks in my build (generate hbm.xml, struts-config.xml etc). Which plugin (group-id, artifact-id, version) should I use? I would really appreciate if you could write some example pom or point to some existing guidelines on the web. Thanks in advance! Best regards, Dmitriy - Don't limit your challenges, Challenge your limits! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Surefire w/TestNG
I have tried to put in touch a person from this list (Kaare Nilsen) that had made a 80% functional test-ng prototype plugin with Cedric Beust of TestNG and they exchanged these mails, as they were only between the four of us perhaps you'd like to follow up on it: Cedric: Hi Srepfler (and Kaare and Andy) and thanks for the note. Kaare: sorry you had such a hard time with our code base. I wasn't even aware you were working on that, I would have been happy to help you. And I agree that our dual annotation code base is not the simplest and interestingly, I have been thinking of ways to revamp it these past days. Quite a coincidence. Finally, Andrew is in copy because he's the author of the Maven 1.1 plug-in and he's currently working on a 2.0 version. Andrew, maybe you could benefit from Kaare's work so far? Kaare: Hi. First I would like to balance the sheet by saying that I think testNg is a very well put together from an user perspective, and I have really nothing bad to say about that. But from a plugin perspective my main critic is that i can't seem to find a clean interface for invoking it. With that said. I would very much like the plugin to get finished, but my effort is at the time beeing directed to the aspectJ plugin for m2 and i really do not have time to find out what part of the annotation codebase that conflicts with maven. Btw: would it not be a good idea to get testNG jars uploaded to ibiblio ? Cedric: Hi Kaare, No need to apologize :-) When a project grows big enough, you can't really like 100% of its source code any more, no matter how hard you try, so your criticism is well taken. Could you be a bit more specific as to what problems you encountered? It might be a learning experience for me and the people in CC as well, and I'll be more than happy to do my best and make sure that writing a Maven 2 plug-in for TestNG will be as effortless as possible for whoever ends up stepping up to the plate... Andy: Putting the TestNG jars on Ibiblio would be excellent. I started down this path, but lost interest when I saw the process... Do you mind sharing what you've done thus far on the plug-in- perhaps I can finish it? Thank you!! Kaare: But of course Cedric: Just wanted to let you know that I completely revamped our annotation support. Everything is working and we're back at 100% tests now. I still need to delete a few files and do some renaming, but the dual annotation support is much cleaner now. I'll be happy to write up a quick design overview (should take a few paragraphs) if you're interested. Having said that, I realized I never really asked you why you needed a better understanding of that part of our codebase for your Maven 2 plug-in... I am not familiar with the Maven plug-in API, but I have always been under the impression that interfacing with TestNG requires nothing more than being able to create a TestNG() object, set various parameters, add a listener and call run(). Care to share your findings? Kaare: Sure.. The problem does not really occur when everything works as expected, it is when problems occur and one needs to dig into how things work, and what classes one needs to provide new implementation of fixes for. It is very popssible that i have approached this plugin in a very wrong way, but basicly what happens is that I do not suspect the class in a project containing the main method to be the public api but more a wrapper for the project to use the api. So the first thing i usually do is to read the main method and see how things are wired together and how the command line args are parsed to parameters to the api. Then i try to emulate the main method. Right now (since it has been a while since i stopped the attemt) I really do not remember why I abondoned this approach, and tried another solution, but i suspect it had something to to with the annotations not working. What i could try again with the new versions released is to try the first approach again, and try to copy the privateMain method replacing the commandline args with plugin configuration params and then see what happens. But with all that said, the testng plugin should really be integrated into the surefire plugin to get it to run as an equal to junit, but i would settle for an own plugin for now. -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: antrun's antlr task problem
I got it working, take a look at the test6
On 1/5/06, dan tran [EMAIL PROTECTED] wrote:
OK the IT test1 works, I now use it as a base to test if I can load antlr
task. It fails not able to load antlr task
It seems like antrun is not able to find the entry into the antlr ant task.
Your help is greatly appreciated
here is the pom
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdorg.apache.maven.plugins.antrun/groupId
artifactIdtest1/artifactId
version1.0-SNAPSHOT/version
nameTest for compile and plugin classpath references/name
descriptionEnsure that maven.compile.classpath and
maven.plugin.classpath referencies are set/description
dependencies
/dependencies
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
version1.1/version
executions
execution
idcompile/id
phasecompile/phase
configuration
sourceRoottarget/generated/src/main/java/sourceRoot
tasks
path id=classpath
path refid=maven.compile.classpath/
path refid=maven.plugin.classpath/
/path
ant antfile=${basedir}/build.xml inheritRefs=true
target name=test/
/ant
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdant/groupId
artifactIdant-nodeps/artifactId
version1.6.5/version
/dependency
dependency
groupIdantlr/groupId
artifactIdantlrall/artifactId
version2.7.4/version
/dependency
/dependencies
/plugin
/plugins
/build
/project
Here is build.xml
=
?xml version=1.0?
project name=test1
target name=test
antlr target=${main.dir}/org/exolab/jms/selector/parser/Selector.g
outputdirectory=${parser.dir}
classpath refid=classpath/
/antlr
/target
/project
-D
On 1/5/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
Check the src/it/test1 in the plugin sources, that works for me.
BTW antlr 2.7.4 jar is not in the repo
On 1/5/06, dan tran [EMAIL PROTECTED] wrote:
Yes I am using 1.1 plugin
-D
On 1/5/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
Are you using the 1.1 plugin?
On 1/4/06, dan tran [EMAIL PROTECTED] wrote:
ok, have my plugin's configuration as
configuration
tasks
ant inheritRefs=true
property name=build.dir value=${
project.build.directory}/
/ant
/tasks
/configuration
and have my build.xml to reference maven.plugin.classpath, but got
error
Embedded error: The following error occurred while executing this
line:
M:\dtran-uscud-dtran-phoenix-i\EJB\maven\openjms\build.xml:249: The
following er
ror occurred while executing this line:
M:\dtran-uscud-dtran-phoenix-i\EJB\maven\openjms\build.xml:279:
Reference
maven.
plugin.classpath not found.
Suggestion on how to trouble shoot this issue is greatly
appreciated.
-Dan
On 1/4/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
You need to use the plugin classpath in your build.xml and call
ant
with inheritRefs=true
classpath refid=maven.plugin.classpath/
On 1/4/06, dan tran [EMAIL PROTECTED] wrote:
Folks,
Here is my build :
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.1-SNAPSHOT/version
dependencies
dependency
groupIdant/groupId
artifactIdant-nodeps/artifactId
version1.6.5/version
/dependency
dependency
groupIdantlr/groupId
artifactIdantlr/artifactId
version2.7.4/version
/dependency
/dependencies
executions
execution
phasecompile/phase
configuration
tasks
ant
property name=build.dir value=${
project.build.directory}/
/ant
Re: [ANN] m2 antrun plugin 1.1 released
It depends on what you have in your dependencies section. Usually you
would add them to the plugin dependencies (if they're only used at
build time)
On 1/5/06, Brian E. Fox [EMAIL PROTECTED] wrote:
Is there something fundamental that I need to change between 1.0 and
1.1? I just updated because I needed the
http://jira.codehaus.org/browse/MANTRUN-28 fix. I only changed the
version and now it seems to be missing more stuff on the class path:
executions
execution
idkodo-enhance/id
phasecompile/phase
configuration
tasks
ant antfile=kodo-enhance.xml inheritRefs=true
inheritAll=true/
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
Kodo-enhance.xml:
project name=Kodo Enhance default=enhance
property environment=environment/
property name=m2localrepo value=${environment.M2_REPO}/
path id=local.class.path
pathelement location=./target/classes/
pathelement location=./src/main/resources/
path refid=maven.dependency.classpath/
/path
target name=enhance
taskdef name=enhance-classes classname=kodo.ant.JDOEnhancerTask
classpathref=local.class.path/
enhance-classes
classpath refid=local.class.path/
fileset dir=./target
include name=**/*.jdo /
/fileset
/enhance-classes
/target
/project
Error:
[INFO] [antrun:run {execution: kodo-enhance}]
[INFO] Executing tasks
enhance:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: The following error occurred while executing this line:
E:\STC\workarea\svn\modules\services\supplementaldata-jdo\trunk\kodo-enh
ance.xml:10: taskdef class kodo.ant.J
OEnhancerTask cannot be found
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error executing
ant tasks
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:544
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecu
or.java:469)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:448)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleE
ecutor.java:301)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.j
va:268)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:137)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error
executing ant tasks
at
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntM
ojo.java:114)
at
org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:399)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:519
... 16 more
Caused by: The following error occurred while executing this line:
E:\STC\workarea\svn\modules\services\supplementaldata-jdo\trunk\kodo-enh
ance.xml:10: taskdef class kodo.ant.J
OEnhancerTask cannot be found
at
org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHe
lper.java:539)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntM
ojo.java:108)
... 19 more
Caused by:
Re: RE : RE : [m2] war plugin and resources filtering
Olivier Lamy wrote:
Perso, I use xdoclet plugin to generate it and configue the war plugin :
webXml${basedir}/target/xdoclet/web.xml/webXml
Sounds good to me.
Thanks!
--
Laurent
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: accessing environment variable in settings.xml or pom.xml
Here's an issue on this topic: http://jira.codehaus.org/browse/MNG-1525.
The ability to reference environment variables appears to have been
added to plexus-utils, but I haven't had the time to check it out yet.
I'm not sure how environment variables can be referenced, probably
either ${env.BLAH} or ${envars.BLAH}.
Richard Allen
Ralph Pöllath wrote:
On 05.01.2006, at 22:31, Adam Altemus wrote:
Greetings, my name is Adam Altemus. I am a computer science student @
Indiana University of PA. and am doing an internship. I read in a
thread that you said that you can acess environment variables in the
pom.xml
from the settings.xml. Could you explain to me how this can be done?
AFAIK, you can use java system properties like ${user.home} etc. (see
http://java.sun.com/docs/books/tutorial/essential/system/
properties.html ), but not your operating system's environment
variables (like $CATALINA_HOME, etc).
There has been quite some discussion about this, so search the
archives if you want to know why this is so (build portability, IIRC).
Cheers,
-Ralph.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] how to change maven-jar-plugin's basedir ?
-Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] With the changes you *can* now do this in the jar-plugin: ... to achieve what you are doing, you *can* also use a custom assembly descriptor, ... I think he was saying that its not just a matter of what *can* be done, it's a matter of things just working. The constellation of maven plugins should be set up so that you *normally* don't have customize a descriptor over here to make something work over there. In other words, I think he is saying that there should be a sensible and consistent set of default values that help all the plugins work together well in most cases. Maven is all about having best practices implemented by default reducing the amount of arbitrary trivial decisions you have to make. Maybe having the dependency plugin default to lib might be a good example. But this should be decided in coordination with the other plugins that might make use of this. - Attention: Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you received this in error, please contact the sender and delete the material from any system and destroy any copies. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] how to change maven-jar-plugin's basedir ?
On 1/7/06, Christopher Cobb [EMAIL PROTECTED] wrote: I think he was saying that its not just a matter of what *can* be done, it's a matter of things just working. The constellation of maven plugins should be set up so that you *normally* don't have customize a descriptor over here to make something work over there. That's exactly how Maven is designed to work. The only reason this discussion happened is because the defaults didn't suit their situation. Still, this could be easily used by a simple customisation. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2]release:prepare requires snapshots ?
Hi, Is there an issue with release:prepare when running against multiple projects ? I'm running this against a parent project with two child projects. When release:prepare runs from the parent project it runs correctly against the first child project and updates the version numbers in the poms to the new numbers. However because the second child project has a reference to both the parent project (through parent tags) and a dependency on the first child project it will fail the cvs diff that is part of the release:prepare. This is because during the execution of the release:prepare on the first child, it modified the second childs pom.xml with the new version numbers and didn't check second project pom.xml. Has anyone else managed to sucessfully perform a release:prepare under similar conditions ? thanks patrick Mike Perham [EMAIL PROTECTED] 01/04/2006 03:48 PM Please respond to Maven Users List users@maven.apache.org To Maven Users List users@maven.apache.org cc Subject RE: [m2]release:prepare requires snapshots ? I think the idea is that if you are releasing an entire set of projects at once, you would want to keep their versions in sync. If you want to do what you say below (which is what we want to do also), you just do finer grained releases. You don't do recursive releases but only release those modules which have changed. mike -Original Message- From: Laurent Berteau [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 04, 2006 5:06 AM To: Maven Users List Subject: Re: [m2]release:prepare requires snapshots ? Hi, dan tran wrote: It follows maven development process where - during development, every one works on snapshots - at release time, the snapshost got changed to release version, check back into SCM, label, and build. This is where customer can use, including qa, stake holder, etc - then the version is increamented with snapshot and check into SCM again. This implies that in a multi-module project, every sub-module version number is incremented even if no changes has been made. I have a multi-module project where some modules do not evolve frequentely whereas some do. I do not want to overload the repository and the scm history with different version of exactly the same code. Is the only solution to run the release plugin against each module independently ? Do my way of thinking does not fit with the maven approach of the release policy ? Best regards, -- Laurent Berteau - 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]
[m2] dependencyManagement question ?
Hi, I have a question regarding the dependencyManagement section in the pom.xml files. When I have several dependencies and there are conflicts in the transitive dependencies (e.g. commons-beanutils-1.6.1 and commons-beanutils-1.7.0) I thought I could specifiy the version to use in the dependencyManagement section. Is that correct ? Say I put dependencyManagement dependency groupIdcommons-beanutils/groupId artifactIdcommons-beanutils/artifactId version1.7.0/version /dependency /dependencyManagement in my pom. This does not lead to maven using only that version no matter what version is specified in the referenced poms ? -- Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
wtp 0.7 layout and maven layout
Hello all and I wish happy new year for all of us, I use the maven webapp archetype to create my mini-test project . So I get the maven project standard layout . I execute mvn package without changing anything everything is all right. Now I rename webapp to webcontent like on wtp project , Iget a build error when maven executes war:war Exploding webapp... Copy webapp resources to (target)... Assembling webapp ... deployment descriptor ...web.xml does not exist. Do i miss something somewhere?( I already try to declare WebContent as resource but it doesn't work better) Thanks in advance, Tom. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: antrun's antlr task problem
Thanks Carlos, the secret is ant-antlr, i did not define that
-D
On 1/6/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
I got it working, take a look at the test6
On 1/5/06, dan tran [EMAIL PROTECTED] wrote:
OK the IT test1 works, I now use it as a base to test if I can load
antlr
task. It fails not able to load antlr task
It seems like antrun is not able to find the entry into the antlr ant
task.
Your help is greatly appreciated
here is the pom
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdorg.apache.maven.plugins.antrun/groupId
artifactIdtest1/artifactId
version1.0-SNAPSHOT/version
nameTest for compile and plugin classpath references/name
descriptionEnsure that maven.compile.classpath and
maven.plugin.classpath referencies are set/description
dependencies
/dependencies
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
version1.1/version
executions
execution
idcompile/id
phasecompile/phase
configuration
sourceRoottarget/generated/src/main/java/sourceRoot
tasks
path id=classpath
path refid=maven.compile.classpath/
path refid=maven.plugin.classpath/
/path
ant antfile=${basedir}/build.xml inheritRefs=true
target name=test/
/ant
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdant/groupId
artifactIdant-nodeps/artifactId
version1.6.5/version
/dependency
dependency
groupIdantlr/groupId
artifactIdantlrall/artifactId
version2.7.4/version
/dependency
/dependencies
/plugin
/plugins
/build
/project
Here is build.xml
=
?xml version=1.0?
project name=test1
target name=test
antlr target=${main.dir
}/org/exolab/jms/selector/parser/Selector.g
outputdirectory=${parser.dir}
classpath refid=classpath/
/antlr
/target
/project
-D
On 1/5/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
Check the src/it/test1 in the plugin sources, that works for me.
BTW antlr 2.7.4 jar is not in the repo
On 1/5/06, dan tran [EMAIL PROTECTED] wrote:
Yes I am using 1.1 plugin
-D
On 1/5/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
Are you using the 1.1 plugin?
On 1/4/06, dan tran [EMAIL PROTECTED] wrote:
ok, have my plugin's configuration as
configuration
tasks
ant inheritRefs=true
property name=build.dir value=${
project.build.directory}/
/ant
/tasks
/configuration
and have my build.xml to reference maven.plugin.classpath, but
got
error
Embedded error: The following error occurred while executing
this
line:
M:\dtran-uscud-dtran-phoenix-i\EJB\maven\openjms\build.xml:249:
The
following er
ror occurred while executing this line:
M:\dtran-uscud-dtran-phoenix-i\EJB\maven\openjms\build.xml:279:
Reference
maven.
plugin.classpath not found.
Suggestion on how to trouble shoot this issue is greatly
appreciated.
-Dan
On 1/4/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
You need to use the plugin classpath in your build.xml and
call
ant
with inheritRefs=true
classpath refid=maven.plugin.classpath/
On 1/4/06, dan tran [EMAIL PROTECTED] wrote:
Folks,
Here is my build :
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.1-SNAPSHOT/version
dependencies
dependency
groupIdant/groupId
artifactIdant-nodeps/artifactId
version1.6.5/version
/dependency
dependency
groupIdantlr/groupId
artifactIdantlr/artifactId
version2.7.4/version
/dependency
/dependencies
Re: [m2] dependencyManagement question ?
Not as far as I know. What dependencyManagement allows if you to specify in a parent pom the dependencyManagement section like you wrote. Then in a child that specifies that POM as it's parent, you can create the followin dependency: dependencies dependency groupIdcommons-beanutils/groupId artifactIdcommons-beanutils/artifactId /dependency /dependencies Then the version wil be set to what is specified in dependencyManagement (scope would also be set to what the parent specifies). -Stephen On 1/6/06, Christian Schulte [EMAIL PROTECTED] wrote: Hi, I have a question regarding the dependencyManagement section in the pom.xml files. When I have several dependencies and there are conflicts in the transitive dependencies (e.g. commons-beanutils-1.6.1 and commons-beanutils-1.7.0) I thought I could specifiy the version to use in the dependencyManagement section. Is that correct ? Say I put dependencyManagement dependency groupIdcommons-beanutils/groupId artifactIdcommons-beanutils/artifactId version1.7.0/version /dependency /dependencyManagement in my pom. This does not lead to maven using only that version no matter what version is specified in the referenced poms ? -- Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wtp 0.7 layout and maven layout
Need to add configuration for the parameter warSourceDirectory in War plugin. http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html Eric On 1/6/06, Tom Joad [EMAIL PROTECTED] wrote: Hello all and I wish happy new year for all of us, I use the maven webapp archetype to create my mini-test project . So I get the maven project standard layout . I execute mvn package without changing anything everything is all right. Now I rename webapp to webcontent like on wtp project , Iget a build error when maven executes war:war Exploding webapp... Copy webapp resources to (target)... Assembling webapp ... deployment descriptor ...web.xml does not exist. Do i miss something somewhere?( I already try to declare WebContent as resource but it doesn't work better) Thanks in advance, Tom. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wtp 0.7 layout and maven layout
See also: http://mail-archives.apache.org/mod_mbox/maven-users/200505.mbox/[EMAIL PROTECTED] HTH Eric On 1/6/06, Eric Jacob [EMAIL PROTECTED] wrote: Need to add configuration for the parameter warSourceDirectory in War plugin. http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html Eric On 1/6/06, Tom Joad [EMAIL PROTECTED] wrote: Hello all and I wish happy new year for all of us, I use the maven webapp archetype to create my mini-test project . So I get the maven project standard layout . I execute mvn package without changing anything everything is all right. Now I rename webapp to webcontent like on wtp project , Iget a build error when maven executes war:war Exploding webapp... Copy webapp resources to (target)... Assembling webapp ... deployment descriptor ...web.xml does not exist. Do i miss something somewhere?( I already try to declare WebContent as resource but it doesn't work better) Thanks in advance, Tom. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wtp 0.7 layout and maven layout
Thanks for so quick reply,I 'll follow suggestions. Tom. 2006/1/6, Eric Jacob [EMAIL PROTECTED]: See also: http://mail-archives.apache.org/mod_mbox/maven-users/200505.mbox/[EMAIL PROTECTED] HTH Eric On 1/6/06, Eric Jacob [EMAIL PROTECTED] wrote: Need to add configuration for the parameter warSourceDirectory in War plugin. http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html Eric On 1/6/06, Tom Joad [EMAIL PROTECTED] wrote: Hello all and I wish happy new year for all of us, I use the maven webapp archetype to create my mini-test project . So I get the maven project standard layout . I execute mvn package without changing anything everything is all right. Now I rename webapp to webcontent like on wtp project , Iget a build error when maven executes war:war Exploding webapp... Copy webapp resources to (target)... Assembling webapp ... deployment descriptor ...web.xml does not exist. Do i miss something somewhere?( I already try to declare WebContent as resource but it doesn't work better) Thanks in advance, Tom. - 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: Resource path for testing?
Thanks Wendy. I finally realized the error of my ways. I was expecting that src/test/resources would be put in the runtime classpath for testing. Instead, I see that the contents of src/test/resources are copied into the target/test-classes directory, which is already in the classpath. My issue was really a classloader issue in my code, having nothing to do with Maven. -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 04, 2006 3:18 PM To: Maven Users List Subject: Re: Resource path for testing? On 1/4/06, Jeff Lowe [EMAIL PROTECTED] wrote: Some of my unit tests need to access files as resources, which are sitting in a directory within the source tree. Is there a setting for testing, where I can add a directory to the classpath, which will allow the tests to access the files? Assuming you're on Maven 2, here's an example of using testResources to add files outside of the standard src/test/resources directory: http://svn.apache.org/repos/asf/struts/action/trunk/pom.xml -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Siebel IT'S ALL ABOUT THE CUSTOMER Visit www.siebel.com This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Siebel Systems, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: unit test fails for 'package' but not 'site' or 'test'
I hate replying to myself. Even more than that I hate what I have to report. I don't really believe it myself but I saw it. This morning I came in. My computer was still running all the same stuff from yesterday. Eclipse was still running even. I did some Google type research and then fiddled with the classpath setting for a few jars and wars in my project. When I built, none of the failures I reported yesterday happened. I removed the xml stuff to ignore surefire errors/failures and verified it still works. I only tried it twice. I hate things to just start working because you never know when they will come back. Oh well. -- Lee Meador On 1/5/06, Lee Meador [EMAIL PROTECTED] wrote: More news: I told it to ignore surefire failures/errors on that project and it failed on another (without excludes. I repeated that a few times but it is still failing on a bunch of my projects' tests on package and the exception that happens is that a class from one of my other projects is not found. All these tests still work for site or test. What to do? Thanks. On 1/5/06, Lee Meador [EMAIL PROTECTED] wrote: I did notice (replying to my self) that the failing project is the only one with an excludes on the surefile plugin. On 1/5/06, Lee Meador [EMAIL PROTECTED] wrote: When I do 'mvn site' or 'mvn test' the tests run on all my projects. They don't fail. When I do 'mvn package', one test fails. Two projects (including the parent) have no tests. Then wo projects with tests succeed. Then two projects with no tests. And then the failure happens on the next project to build. The failure is due to a java.lang.NoClassDefFoundError pointing to a class that is in one of the earlier built projects' jar files. That jar file is in place and contains the class file. When I do -e -X it shows the classpath on the test run and that jar file (the one with the class that can't be found) is listed. I have a parent/base project and a bunch of child projects sitting in folder beside the folder for the parent. That leaves a lot of ..s in the POMs but hasn't been a problem to this point. I don't know where to go from here. Help? Thanks. -- -- Lee Meador Sent from gmail. My real email address is [EMAIL PROTECTED]
[m2] site.xml documentation? How to create a site
So, I have a hierarchy of Maven builds. I was hoping, that the site I generated from the top would contain links to the sub-sites. Looks like that does not happen by default, all I get from the top layer is a site that is about the top layer pom (not very interesting, really). So I wondered: OK, let me go a bit deeper. Ah, I see, there is something called a site.xml that seems like it will let me do a bit more with the site. Unfortunately, the documentation for this is non-existent. It says it replaces the Maven 1.0 navigation.xml, but it doesn't give any reference for it, or description of how it supposed to be used. Is there anyway someone could help me? Is there better documentation anywhere out there about site.xml. Is it the same format or different from navigation.xml? How do I get nice links to all the several sub-projects (and some of them have children too)? Thanks for the help. John Wells (Aziz) [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: unit test fails for 'package' but not 'site' or 'test'
Lee, We're going to be moving the Maven stuff around tomorrow. Over the next few days we should be settling on the final layout. Some of the unit tests do not work (as you discovered) but should be excluded from the build (for the moment.) Hopefully we'll get everything sorted out with lots of good docs to follow. Sean On 1/6/06, Lee Meador [EMAIL PROTECTED] wrote: I hate replying to myself. Even more than that I hate what I have to report. I don't really believe it myself but I saw it. This morning I came in. My computer was still running all the same stuff from yesterday. Eclipse was still running even. I did some Google type research and then fiddled with the classpath setting for a few jars and wars in my project. When I built, none of the failures I reported yesterday happened. I removed the xml stuff to ignore surefire errors/failures and verified it still works. I only tried it twice. I hate things to just start working because you never know when they will come back. Oh well. -- Lee Meador On 1/5/06, Lee Meador [EMAIL PROTECTED] wrote: More news: I told it to ignore surefire failures/errors on that project and it failed on another (without excludes. I repeated that a few times but it is still failing on a bunch of my projects' tests on package and the exception that happens is that a class from one of my other projects is not found. All these tests still work for site or test. What to do? Thanks. On 1/5/06, Lee Meador [EMAIL PROTECTED] wrote: I did notice (replying to my self) that the failing project is the only one with an excludes on the surefile plugin. On 1/5/06, Lee Meador [EMAIL PROTECTED] wrote: When I do 'mvn site' or 'mvn test' the tests run on all my projects. They don't fail. When I do 'mvn package', one test fails. Two projects (including the parent) have no tests. Then wo projects with tests succeed. Then two projects with no tests. And then the failure happens on the next project to build. The failure is due to a java.lang.NoClassDefFoundError pointing to a class that is in one of the earlier built projects' jar files. That jar file is in place and contains the class file. When I do -e -X it shows the classpath on the test run and that jar file (the one with the class that can't be found) is listed. I have a parent/base project and a bunch of child projects sitting in folder beside the folder for the parent. That leaves a lot of ..s in the POMs but hasn't been a problem to this point. I don't know where to go from here. Help? Thanks. -- -- Lee Meador Sent from gmail. My real email address is [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] maven-eclipse-plugin and Borland Together 2006
Can the generated eclipse project be somehow told to be a Java Modelling Project or UML 2.0, 1.4 Project, etc etc.? Also, how can I say which project nature my project should be? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: NullPointerException while running mvn site:site
I don't have any dependency tag for the plug-in : it is declared in its simplest form in my pom : reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId /plugin /plugins /reporting or I did not understand what you are asking for... Le Vendredi 06 Janvier 2006 13:51, Dixit, Sandeep (ProSource Solutions) a écrit : Could you please send me your dependency tag for the plug-in? Thanks, Sandeep -Original Message- From: Hervé BOUTEMY [mailto:[EMAIL PROTECTED] Sent: Thursday, January 05, 2006 3:07 PM To: Maven Users List Subject: Re: NullPointerException while running mvn site:site I confirm : svn has a fix (modified since the patch from MNG-1455) I built and installed the plugin locally, and it works nicely Le Jeudi 05 Janvier 2006 09:04, Bernd Bohmann a écrit : Hello, see http://jira.codehaus.org/browse/MNG-1455 but the patch was reverted. I think the maven-project-info-reports-plugin in the svn has a fix for it. Maybe a SNAPSHOT version is available. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- ***National City made the following annotations --- This communication is a confidential and proprietary business communication. It is intended solely for the use of the designated recipient(s). If this communication is received in error, please contact the sender and delete this communication. === - 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: unit test fails for 'package' but not 'site' or 'test'
Lee, Disregard my email. ;-) I thought the message was to myfaces-users. The two folders are next to each other in gmail. Sorry for the confusion. Sean On 1/6/06, Sean Schofield [EMAIL PROTECTED] wrote: Lee, We're going to be moving the Maven stuff around tomorrow. Over the next few days we should be settling on the final layout. Some of the unit tests do not work (as you discovered) but should be excluded from the build (for the moment.) Hopefully we'll get everything sorted out with lots of good docs to follow. Sean On 1/6/06, Lee Meador [EMAIL PROTECTED] wrote: I hate replying to myself. Even more than that I hate what I have to report. I don't really believe it myself but I saw it. This morning I came in. My computer was still running all the same stuff from yesterday. Eclipse was still running even. I did some Google type research and then fiddled with the classpath setting for a few jars and wars in my project. When I built, none of the failures I reported yesterday happened. I removed the xml stuff to ignore surefire errors/failures and verified it still works. I only tried it twice. I hate things to just start working because you never know when they will come back. Oh well. -- Lee Meador On 1/5/06, Lee Meador [EMAIL PROTECTED] wrote: More news: I told it to ignore surefire failures/errors on that project and it failed on another (without excludes. I repeated that a few times but it is still failing on a bunch of my projects' tests on package and the exception that happens is that a class from one of my other projects is not found. All these tests still work for site or test. What to do? Thanks. On 1/5/06, Lee Meador [EMAIL PROTECTED] wrote: I did notice (replying to my self) that the failing project is the only one with an excludes on the surefile plugin. On 1/5/06, Lee Meador [EMAIL PROTECTED] wrote: When I do 'mvn site' or 'mvn test' the tests run on all my projects. They don't fail. When I do 'mvn package', one test fails. Two projects (including the parent) have no tests. Then wo projects with tests succeed. Then two projects with no tests. And then the failure happens on the next project to build. The failure is due to a java.lang.NoClassDefFoundError pointing to a class that is in one of the earlier built projects' jar files. That jar file is in place and contains the class file. When I do -e -X it shows the classpath on the test run and that jar file (the one with the class that can't be found) is listed. I have a parent/base project and a bunch of child projects sitting in folder beside the folder for the parent. That leaves a lot of ..s in the POMs but hasn't been a problem to this point. I don't know where to go from here. Help? Thanks. -- -- Lee Meador Sent from gmail. My real email address is [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] site.xml documentation? How to create a site
John Wells wrote: So, I have a hierarchy of Maven builds. I was hoping, that the site I generated from the top would contain links to the sub-sites. Looks like that does not happen by default, all I get from the top layer is a site that is about the top layer pom (not very interesting, really). So I wondered: OK, let me go a bit deeper. Ah, I see, there is something called a site.xml that seems like it will let me do a bit more with the site. Unfortunately, the documentation for this is non-existent. It says it replaces the Maven 1.0 navigation.xml, but it doesn't give any reference for it, or description of how it supposed to be used. You are correct in this, documentation is sparse. The format is pretty much the same as for navigation.xml. You can have a look at this .mdo file from doxia that is used to understand the site.xml file: http://svn.apache.org/viewcvs.cgi/maven/doxia/trunk/doxia-decoration-model/src/main/mdo/decoration.mdo?rev=359931view=markup It reads pretty much like an xsd file. Is there anyway someone could help me? Is there better documentation anywhere out there about site.xml. Is it the same format or different from navigation.xml? How do I get nice links to all the several sub-projects (and some of them have children too)? Put this section into your top level pom.xml specifying the sub modules you want. modules modulemodule-1/module modulemodule-2/module ... /modules -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: NullPointerException while running mvn site:site
I added this tag in my POMs. Still the error persists. Your wrote : I built and installed the plugin locally, and it works nicely I don't have source on my machine. I am using Maven 2.0.1 (bin dist). How do I go about getting this update? Thanks, Sandeep -Original Message- From: Hervé BOUTEMY [mailto:[EMAIL PROTECTED] Sent: Friday, January 06, 2006 1:31 PM To: Maven Users List Subject: Re: NullPointerException while running mvn site:site I don't have any dependency tag for the plug-in : it is declared in its simplest form in my pom : reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId /plugin /plugins /reporting or I did not understand what you are asking for... Le Vendredi 06 Janvier 2006 13:51, Dixit, Sandeep (ProSource Solutions) a écrit : Could you please send me your dependency tag for the plug-in? Thanks, Sandeep -Original Message- From: Hervé BOUTEMY [mailto:[EMAIL PROTECTED] Sent: Thursday, January 05, 2006 3:07 PM To: Maven Users List Subject: Re: NullPointerException while running mvn site:site I confirm : svn has a fix (modified since the patch from MNG-1455) I built and installed the plugin locally, and it works nicely Le Jeudi 05 Janvier 2006 09:04, Bernd Bohmann a écrit : Hello, see http://jira.codehaus.org/browse/MNG-1455 but the patch was reverted. I think the maven-project-info-reports-plugin in the svn has a fix for it. Maybe a SNAPSHOT version is available. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- ***National City made the following annotations --- This communication is a confidential and proprietary business communication. It is intended solely for the use of the designated recipient(s). If this communication is received in error, please contact the sender and delete this communication. === - 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]
touching remote repo when running mvn install
Hi, I'm finding myself doing a bunch of mvn install and mvn eclipse:eclipse commands with my maven projects. I notice that when I execute these commands maven searches the remote repository for jars that are already in my local repo, it also searches the remote repo for jars that I know are only in my local repo (for example mail-UNKOWNVERSION is specific to my local repo). Its says something like WARNING jar not found in remote repo but found in local, why does it look in the remote repo for it if its sitting right there in my local ? Sometimes during execution of these commands the remote repo will timeout and my build will fail. I'm wondering if there is a way to configure maven to not look in remote repos for jars if they exist in the local repository and would hence get rid of the WARNING messages. I found documentation for Maven1 to run in offline mode is there something similar for Maven2 that when set would not trigger remote repo lookups, or even better a way to configure it to only look in the remote if the jar is not in the local? Thanks for Maven2, its starting to have a lot of value in our organization and the transition has not been a major hassle.
[m2]: Problem using maven-antrun-plugin twice
Hi, I am building a web app using maven 2.0. I have specified the following in my POM file: build plugins plugin artifactIdmaven-antrun-plugin/artifactId executions execution phasegenerate-sources/phase configuration tasks echo message=Hello World 1/ /tasks /configuration goals goalrun/goal /goals /execution /executions /plugin plugin artifactIdmaven-antrun-plugin/artifactId executions execution phaseinstall/phase configuration tasks echo message= Hello World 2/ /tasks /configuration goals goalrun/goal /goals /execution /executions /plugin /plugins /build Now in both the executions, it just executes 'echo message=Hello World 1/'. Any idea? Shouldn't it execute 'echo message=Hello World 2/' the second time (during install phase)? Many thanks, Miral - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] site.xml documentation? How to create a site
site.xml documentation is there : http://maven.apache.org/guides/mini/guide-site.html Emmanuel John Wells a écrit : So, I have a hierarchy of Maven builds. I was hoping, that the site I generated from the top would contain links to the sub-sites. Looks like that does not happen by default, all I get from the top layer is a site that is about the top layer pom (not very interesting, really). So I wondered: OK, let me go a bit deeper. Ah, I see, there is something called a site.xml that seems like it will let me do a bit more with the site. Unfortunately, the documentation for this is non-existent. It says it replaces the Maven 1.0 navigation.xml, but it doesn't give any reference for it, or description of how it supposed to be used. Is there anyway someone could help me? Is there better documentation anywhere out there about site.xml. Is it the same format or different from navigation.xml? How do I get nice links to all the several sub-projects (and some of them have children too)? Thanks for the help. John Wells (Aziz) [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]
[m2] Artifacts not available during the generate-sources phase?
The following code in a Mojo:
or (Iterator i = project.getArtifacts().iterator(); i.hasNext();) {
Artifact a = (Artifact) i.next();
System.out.println(a.getFile());
}
Produces a list of artifact files if executed during the 'test' phase,
but not during the 'compile-sources' phase. Why is this? We have a
code generator that may possibly need to reference resources in
dependency JAR files, but I cannot see a way to do this if there are no
artifacts available (in any scope) during this phase of the lifecycle.
Thanks in advance.
Re: [m2] Artifacts not available during the generate-sources phase?
Add this to your mojo's annotation to allow your mojo to see all
dependencies as if it is in test phase
@requiresDependencyResolution test
On 1/6/06, Allan Lewis [EMAIL PROTECTED] wrote:
The following code in a Mojo:
or (Iterator i = project.getArtifacts().iterator(); i.hasNext();) {
Artifact a = (Artifact) i.next();
System.out.println(a.getFile());
}
Produces a list of artifact files if executed during the 'test' phase,
but not during the 'compile-sources' phase. Why is this? We have a
code generator that may possibly need to reference resources in
dependency JAR files, but I cannot see a way to do this if there are no
artifacts available (in any scope) during this phase of the lifecycle.
Thanks in advance.
plexus-archiver-1.3-SNAPSHOT?
Folks, Looks like plexus-archiver-1.3-SNAPSHOT is not available from http://snapshots.maven.codehaus.org even though there are dated snapshots there. Any chance of getting this fixed in the CodeHaus snapshots repository? Kind Regards, John Fallows. -- Author Pro JSF and Ajax: Building Rich Internet Components http://www.apress.com/book/bookDisplay.html?bID=10044
RE: [m2]release:prepare requires snapshots ?
Patrick, I usually perform a synch or compare before executing the release:prepare. I agree that a failure or user abort during that goal is not transactional in nature. I know that checkpoints exist in the release.properties file, but I am not comfortable enough with them to count on it working right every time. I usually blow that file away and start over. On the bright side, once you can get through it, the process is nicer than the manual alternatives. Michael -Original Message- From: Patrick O'shea [mailto:[EMAIL PROTECTED] Sent: Friday, January 06, 2006 10:05 AM To: Maven Users List Subject: RE: [m2]release:prepare requires snapshots ? Hi, Is there an issue with release:prepare when running against multiple projects ? I'm running this against a parent project with two child projects. When release:prepare runs from the parent project it runs correctly against the first child project and updates the version numbers in the poms to the new numbers. However because the second child project has a reference to both the parent project (through parent tags) and a dependency on the first child project it will fail the cvs diff that is part of the release:prepare. This is because during the execution of the release:prepare on the first child, it modified the second childs pom.xml with the new version numbers and didn't check second project pom.xml. Has anyone else managed to sucessfully perform a release:prepare under similar conditions ? thanks patrick Mike Perham [EMAIL PROTECTED] 01/04/2006 03:48 PM Please respond to Maven Users List users@maven.apache.org To Maven Users List users@maven.apache.org cc Subject RE: [m2]release:prepare requires snapshots ? I think the idea is that if you are releasing an entire set of projects at once, you would want to keep their versions in sync. If you want to do what you say below (which is what we want to do also), you just do finer grained releases. You don't do recursive releases but only release those modules which have changed. mike -Original Message- From: Laurent Berteau [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 04, 2006 5:06 AM To: Maven Users List Subject: Re: [m2]release:prepare requires snapshots ? Hi, dan tran wrote: It follows maven development process where - during development, every one works on snapshots - at release time, the snapshost got changed to release version, check back into SCM, label, and build. This is where customer can use, including qa, stake holder, etc - then the version is increamented with snapshot and check into SCM again. This implies that in a multi-module project, every sub-module version number is incremented even if no changes has been made. I have a multi-module project where some modules do not evolve frequentely whereas some do. I do not want to overload the repository and the scm history with different version of exactly the same code. Is the only solution to run the release plugin against each module independently ? Do my way of thinking does not fit with the maven approach of the release policy ? Best regards, -- Laurent Berteau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] maven-eclipse-plugin and Borland Together 2006
If you get a helpful reply, can you forward to me? I'm in the process of abandoning jbuilder for eclipse because of maven. Would be nice if I didn't have to. John -Original Message- From: Srepfler Srgjan [mailto:[EMAIL PROTECTED] Sent: Friday, January 06, 2006 12:03 PM To: Maven Users List Subject: [m2] maven-eclipse-plugin and Borland Together 2006 Can the generated eclipse project be somehow told to be a Java Modelling Project or UML 2.0, 1.4 Project, etc etc.? Also, how can I say which project nature my project should be? - 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]
[m2] - ${localRepository} values - weired problem
Hi All,
I using some antrun plugin, and i have this problem
lets say i have my local repository at C:\.M2 and my settings.xml has
entry like localRepository/.M2//localRepository
in my tasks i have some ant scripts steps, for one of them i want to add
all the jars localRepository as my class path, so i add it like
tasks
classpath
fileset dir=${localRepository}
include name=*.jar/
/fileset
/classpath
.
/tasks
coz, i don't want to hard code my localRepository value here, but its not
working for me , and i'm getting this error
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: C:\Raghu\Shop\src\[local] - file:\.M2 not found
why its trying to subsititute ${localReposiotry} valu with file protocol
stuff.
Are is there anyother way to do it ? just by having classes in dependecies
section is not working so thats why i have to mention this classpath in
explicit
Any ideas? Please
Thanks,
Raghurajan G
RE: [m2] Artifacts not available during the generate-sources phase?
Thanks - that did the trick. Set the dependency resolution to 'compile'
and I'm now able to get the JARs I need.
-Original Message-
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: Friday, January 06, 2006 2:36 PM
To: Maven Users List
Subject: Re: [m2] Artifacts not available during the generate-sources
phase?
Add this to your mojo's annotation to allow your mojo to see all
dependencies as if it is in test phase
@requiresDependencyResolution test
On 1/6/06, Allan Lewis [EMAIL PROTECTED] wrote:
The following code in a Mojo:
or (Iterator i = project.getArtifacts().iterator(); i.hasNext();) {
Artifact a = (Artifact) i.next();
System.out.println(a.getFile());
}
Produces a list of artifact files if executed during the 'test' phase,
but not during the 'compile-sources' phase. Why is this? We have a
code generator that may possibly need to reference resources in
dependency JAR files, but I cannot see a way to do this if there are
no
artifacts available (in any scope) during this phase of the lifecycle.
Thanks in advance.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] maven-eclipse-plugin and Borland Together 2006
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html Note the projectnatures property. -Original Message- From: Srepfler Srgjan [mailto:[EMAIL PROTECTED] Sent: Friday, January 06, 2006 12:03 PM To: Maven Users List Subject: [m2] maven-eclipse-plugin and Borland Together 2006 Can the generated eclipse project be somehow told to be a Java Modelling Project or UML 2.0, 1.4 Project, etc etc.? Also, how can I say which project nature my project should be? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Using XDoclet2 Hibernate with Maven2
I'm trying to quickly ramp up and use Maven2 on my project. I'm familiar with XDoclet and have used it with Ant previously. My team is bringing Maven2 into the project and I'm tasked with moving our XDoclet stuff over. However, I can't find any documentation that shows how to configure Hibernate in the pom.xml file (I did find the XDoclet2 Maven2 plugin page) and call it with Maven2. Any help is greatly appreciated. -- Darryl L. Pierce [EMAIL PROTECTED] Homepage: http://mcpierce.multiply.com/ McVeigh's lawyer got him the death penalty, which, quite frankly, I could have done. - Jon Stewart - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using XDoclet2 Hibernate with Maven2
Example : plugin groupIdorg.codehaus.mojo/groupId artifactIdxdoclet-maven-plugin/artifactId executions execution phasegenerate-sources/phase goals goalxdoclet/goal /goals configuration tasks hibernatedoclet destdir=./src/main/java excludedtags=@version,@author,@todo,@see,@desc force=./src/main/java verbose=true fileset dir=./src/main/java include name=**/modelo/*.java / /fileset hibernate version=3.0 / /hibernatedoclet springdoclet destdir=./src/main/webapp/WEB-INF mergeDir=./src/main/resources/metadata/metadata-spring force=true fileset dir=./src/main/java include name=**/*.java / exclude name=**/actions/*.java / /fileset springxml destinationFile= quirografarios2-application-context.xml defaultAutowire=no defaultLazyInit=true / /springdoclet /tasks /configuration /execution /executions /plugin Saludos Ing. Henry Molina CONSULTOR INFORMATICO PNUD-IESS Darryl L. Pierce [EMAIL PROTECTED] 06/01/2006 15:14 Por favor, responda a Maven Users List users@maven.apache.org Para Maven Users List users@maven.apache.org cc Asunto Using XDoclet2 Hibernate with Maven2 I'm trying to quickly ramp up and use Maven2 on my project. I'm familiar with XDoclet and have used it with Ant previously. My team is bringing Maven2 into the project and I'm tasked with moving our XDoclet stuff over. However, I can't find any documentation that shows how to configure Hibernate in the pom.xml file (I did find the XDoclet2 Maven2 plugin page) and call it with Maven2. Any help is greatly appreciated. -- Darryl L. Pierce [EMAIL PROTECTED] Homepage: http://mcpierce.multiply.com/ McVeigh's lawyer got him the death penalty, which, quite frankly, I could have done. - Jon Stewart - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] site.xml documentation? How to create a site
So I have this: modules modulemaven/module moduletools/module modulemodules/module /modules And I was hoping the site generated from this top-level pom.xml would contain links to the lower level modules. It does not. Actualy, the lower level modules do not have their own associated sites, but sub-directories of these higher directories do. Perhaps if I just put dummy sites in the intermediate places I would get full linkage down the stack. I'll give that a try. Thanks for the help. John Wells (Aziz) [EMAIL PROTECTED] -Original Message- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Friday, January 06, 2006 1:35 PM To: Maven Users List Subject: Re: [m2] site.xml documentation? How to create a site John Wells wrote: So, I have a hierarchy of Maven builds. I was hoping, that the site I generated from the top would contain links to the sub-sites. Looks like that does not happen by default, all I get from the top layer is a site that is about the top layer pom (not very interesting, really). So I wondered: OK, let me go a bit deeper. Ah, I see, there is something called a site.xml that seems like it will let me do a bit more with the site. Unfortunately, the documentation for this is non-existent. It says it replaces the Maven 1.0 navigation.xml, but it doesn't give any reference for it, or description of how it supposed to be used. You are correct in this, documentation is sparse. The format is pretty much the same as for navigation.xml. You can have a look at this .mdo file from doxia that is used to understand the site.xml file: http://svn.apache.org/viewcvs.cgi/maven/doxia/trunk/doxia-decoration-mod el/src/main/mdo/decoration.mdo?rev=359931view=markup It reads pretty much like an xsd file. Is there anyway someone could help me? Is there better documentation anywhere out there about site.xml. Is it the same format or different from navigation.xml? How do I get nice links to all the several sub-projects (and some of them have children too)? Put this section into your top level pom.xml specifying the sub modules you want. modules modulemodule-1/module modulemodule-2/module ... /modules -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] site.xml documentation? How to create a site
On 1/6/06, John Wells [EMAIL PROTECTED] wrote: And I was hoping the site generated from this top-level pom.xml would contain links to the lower level modules. It does not. Brett has mentioned that support for the multiproject site should reappear in Maven 2.0.2. You might want to try a snapshot before you do a lot of work to make this happen. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] dependencyManagement question ?
another thing I find handy is for projects where you prepare a ear file that you don't want the internal war files to contain all their dependencies you can set the scope of the jars in the top lvl depedency management section to 'provided' and then in the ear toggle them back so they get put in the right place... helps prevent those 300meg ears :P jesse On 1/6/06, Rinku [EMAIL PROTECTED] wrote: I think the idea of dependencyManagement is to baseline common dependencies and their versions. If you want to use the version 1.7.0 in the quoted example you need to specify dependency groupIdcommons-beanutils/groupId artifactIdcommons-beanutils/artifactId /dependency in your child/extended poms. However, if you do specify a version in the child pom, it should override the one specified in the parent pom under dependencyManagement Cheers, Rahul - Original Message - From: Christian Schulte [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Saturday, January 07, 2006 5:20 AM Subject: [m2] dependencyManagement question ? Hi, I have a question regarding the dependencyManagement section in the pom.xml files. When I have several dependencies and there are conflicts in the transitive dependencies (e.g. commons-beanutils-1.6.1 and commons-beanutils-1.7.0) I thought I could specifiy the version to use in the dependencyManagement section. Is that correct ? Say I put dependencyManagement dependency groupIdcommons-beanutils/groupId artifactIdcommons-beanutils/artifactId version1.7.0/version /dependency /dependencyManagement in my pom. This does not lead to maven using only that version no matter what version is specified in the referenced poms ? -- Christian - 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] -- jesse mcconnell
RE: Using XDoclet2 Hibernate with Maven2
I don't know of anything which does Xdoclet2. The plugin below is for Xdoclet1. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, January 06, 2006 2:21 PM To: Maven Users List Cc: Maven Users List Subject: Re: Using XDoclet2 Hibernate with Maven2 Example : plugin groupIdorg.codehaus.mojo/groupId artifactIdxdoclet-maven-plugin/artifactId executions execution phasegenerate-sources/phase goals goalxdoclet/goal /goals configuration tasks hibernatedoclet destdir=./src/main/java excludedtags=@version,@author,@todo,@see,@desc force=./src/main/java verbose=true fileset dir=./src/main/java include name=**/modelo/*.java / /fileset hibernate version=3.0 / /hibernatedoclet springdoclet destdir=./src/main/webapp/WEB-INF mergeDir=./src/main/resources/metadata/metadata-spring force=true fileset dir=./src/main/java include name=**/*.java / exclude name=**/actions/*.java / /fileset springxml destinationFile= quirografarios2-application-context.xml defaultAutowire=no defaultLazyInit=true / /springdoclet /tasks /configuration /execution /executions /plugin Saludos Ing. Henry Molina CONSULTOR INFORMATICO PNUD-IESS Darryl L. Pierce [EMAIL PROTECTED] 06/01/2006 15:14 Por favor, responda a Maven Users List users@maven.apache.org Para Maven Users List users@maven.apache.org cc Asunto Using XDoclet2 Hibernate with Maven2 I'm trying to quickly ramp up and use Maven2 on my project. I'm familiar with XDoclet and have used it with Ant previously. My team is bringing Maven2 into the project and I'm tasked with moving our XDoclet stuff over. However, I can't find any documentation that shows how to configure Hibernate in the pom.xml file (I did find the XDoclet2 Maven2 plugin page) and call it with Maven2. Any help is greatly appreciated. -- Darryl L. Pierce [EMAIL PROTECTED] Homepage: http://mcpierce.multiply.com/ McVeigh's lawyer got him the death penalty, which, quite frankly, I could have done. - Jon Stewart - 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: SCM username/password lookup
any one?
-D
On 1/5/06, dan tran [EMAIL PROTECTED] wrote:
There are 3 places to look for in this order
Command line
settings.xml
connectionUrl
However in maven-release-plugin, if user does not provide username
via command line (ie -Dusername=xyz),
username is default to system property ${user.name} and by passing
settings.xml.
is it a bug?
-Dan
Re: SCM username/password lookup
well, it sounds like one to me
On 1/6/06, dan tran [EMAIL PROTECTED] wrote:
There are 3 places to look for in this order
Command line
settings.xml
connectionUrl
However in maven-release-plugin, if user does not provide username
via command line (ie -Dusername=xyz),
username is default to system property ${user.name} and by passing
settings.xml.
is it a bug?
-Dan
--
jesse mcconnell
RE: SCM username/password lookup
Might not be a bug in the classic sense because maybe that was the
intention, but certainly not maven like behavior.
+1 for making it use servers section like everything else.
-Original Message-
From: Jesse McConnell [mailto:[EMAIL PROTECTED]
Sent: Friday, January 06, 2006 4:07 PM
To: Maven Users List
Subject: Re: SCM username/password lookup
well, it sounds like one to me
On 1/6/06, dan tran [EMAIL PROTECTED] wrote:
There are 3 places to look for in this order
Command line
settings.xml
connectionUrl
However in maven-release-plugin, if user does not provide username via
command line (ie -Dusername=xyz), username is default to system
property ${user.name} and by passing settings.xml.
is it a bug?
-Dan
--
jesse mcconnell
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: SCM username/password lookup
Yes, i think it's a bug. We must set username to ${user.name} if other places
don't set it.
Emmanuel
dan tran a écrit :
any one?
-D
On 1/5/06, dan tran [EMAIL PROTECTED] wrote:
There are 3 places to look for in this order
Command line
settings.xml
connectionUrl
However in maven-release-plugin, if user does not provide username
via command line (ie -Dusername=xyz),
username is default to system property ${user.name} and by passing
settings.xml.
is it a bug?
-Dan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: plexus-archiver-1.3-SNAPSHOT?
Sure, now that I _know_ it's out there, I found it under the following... :-) http://www.ibiblio.org/maven2/org/codehaus/plexus/plexus-archiver/ rather than... http://www.ibiblio.org/maven2/plexus/plexus-archiver/ Thanks for the tip! Kind Regards, John Fallows. On 1/6/06, dan tran [EMAIL PROTECTED] wrote: would plexus-archiver-1.3 be ok? -D On 1/6/06, John Fallows [EMAIL PROTECTED] wrote: Folks, Looks like plexus-archiver-1.3-SNAPSHOT is not available from http://snapshots.maven.codehaus.org even though there are dated snapshots there. Any chance of getting this fixed in the CodeHaus snapshots repository? Kind Regards, John Fallows. -- Author Pro JSF and Ajax: Building Rich Internet Components http://www.apress.com/book/bookDisplay.html?bID=10044 -- Author Pro JSF and Ajax: Building Rich Internet Components http://www.apress.com/book/bookDisplay.html?bID=10044
Re: Status of PVCS scm
On 1/6/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: We need a contributor for PVCS support in maven-scm. PVCS = Serena Dimension, right? A user wanted to do it but he doesn't find the time for it, so the status is not started. Do you want help us to add it in maven-scm? Emmanuel Ryan Wynn a écrit : Does anyone know the status of the work on a PVCS scm plugin for maven? I am really excited about what I have been able to do with Continuum and CVS and looking forward to intregating continuus builds with PVCS at some point. I am pretty sure Serena Dimension is PVCS. I have Merant PVCS Dimension 7.2 with no mention of Serena but I think Serena is the new company name if I am not mistaken. I would love to contribute to maven-scm for pvcs but honestly I would need to get up to speed on the pvcs api. It looks like ant already has a PVCS task so I will start there.
Re: SCM username/password lookup
OK, JIRA is on the way
Thank your for all inputs
-D
On 1/6/06, Emmanuel Venisse [EMAIL PROTECTED] wrote:
Yes, i think it's a bug. We must set username to ${user.name} if other
places don't set it.
Emmanuel
dan tran a écrit :
any one?
-D
On 1/5/06, dan tran [EMAIL PROTECTED] wrote:
There are 3 places to look for in this order
Command line
settings.xml
connectionUrl
However in maven-release-plugin, if user does not provide username
via command line (ie -Dusername=xyz),
username is default to system property ${user.name} and by passing
settings.xml.
is it a bug?
-Dan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] site.xml documentation? How to create a site
John Wells wrote: Thanks. That is good information. Trying to ensure that all the sub-projects also had at least an index.apl did not work. The top level project still has no links to the lower level projects. I think for now I'll try the 2.0.2 snapshot or just wait for 2.0.2. When will that be out again? Someone has said the first half of January, but one can never really know. After all it's software :) -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: call for testers: scp wagon
Brett: Do you have a release date for the 2.0.2 version of Maven? The scp fixes are great! Mike -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, January 05, 2006 8:43 PM To: Maven Users List Subject: Re: call for testers: scp wagon scp is used, unless you configure putty. - Brett On 1/6/06, dan tran [EMAIL PROTECTED] wrote: I have both putty.exe and cygwin scpexe in my path. Putty if first. But i think maven picks up scp.exe, no sure thou -Dan On 1/5/06, Brett Porter [EMAIL PROTECTED] wrote: Ok, looking into it. Do you use putty? On 1/6/06, dan tran [EMAIL PROTECTED] wrote: I actually did wipe out the snapshots of native-maven-plugin at beaver and deploy the plugin again. Same problem at the end, but all the files seem the be there. Strange! Thanks again. -Dan On 1/5/06, Brett Porter [EMAIL PROTECTED] wrote: Hi dan, I think this is almost certianly permissions problems with deploying that project, rather than an scpexe error, and though the returned error is limited, its all it gets back from the server :) I'll try to reproduce it, though. - Brett On 1/6/06, dan tran [EMAIL PROTECTED] wrote: it is a great joice to see scp working with all the correct persmission settings there is one minor problem with scpexe thou Tested with the recommended snapshot build using scp, sftp,and scpexe. The project ( maven-native) consists of 2 parents, 6 jars, and 1 plugin projects. the plugin deploy always fails at the last step for SCPEXE. I also fails when I deploy the plugin alone. [INFO] [deploy:deploy] [INFO] Retrieving previous build number from snapshots Uploading: scpexe://repo1.maven.org/home/projects/maven/repository-staging/snaps hots/maven2/org/codehaus/mojo/native-maven-plugin/1.0-alpha-1-SNAPSHOT/nativ e-ma ven-plugin-1.0-alpha-1-20060105.181308-10.jar [INFO] Retrieving previous metadata from snapshots [INFO] Uploading repository metadata for: 'artifact org.codehaus.mojo:native-mav en-plugin' [INFO] Retrieving previous metadata from snapshots [INFO] Uploading repository metadata for: 'snapshot org.codehaus.mojo:native-mav en-plugin:1.0-alpha-1-SNAPSHOT' [INFO] Retrieving previous metadata from snapshots [INFO] Uploading project information for native-maven-plugin 1.0-alpha-1-2006010 5.181308-10 [INFO] Retrieving previous metadata from snapshots [INFO] Uploading repository metadata for: 'org.codehaus.mojo' [INFO] - --- [ERROR] BUILD ERROR [INFO] - --- [INFO] Error installing artifact's metadata: Error while deploying metadata: Err or executing command for transfer Exit code 1 - overall, it is a joice to see scp working with all the correct persmission settings On 1/5/06, Mike Perham [EMAIL PROTECTED] wrote: Brett, I switched from sftp to scp and it appears to work! I hope all of this can be released with 2.0.2 as we are planning a company-wide migration from 2.0 to 2.0.2 once it has been released and I have tested it internally. Is there any practical difference between the two transports? Why should I pick one versus the other? mike -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, January 05, 2006 1:34 AM To: Maven Users List Subject: call for testers: scp wagon Hi, In the lead up to the 2.0.2 release, I'd like anyone experiencing: [WAGONSSH-28] session is down [WAGONSSH-30] hangs during deployment to test the following wagon snapshots: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/wagon/wagon- ssh/1.0-alpha-6-SNAPSHOT/wagon- ssh-1.0-alpha-6-20060105.062346-2.jar by including it in your $M2_HOME/lib directory. Please also include: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/wagon/wagon- provider-api/1.0-alpha-6-SNAPSHOT/wagon- provider-api-1.0-alpha-6-2006010 5.062346-7.jar and http://www.ibiblio.org/maven2/com/jcraft/jsch/0.1.24/jsch-0.1.24.jar Replace any existing wagon/jsch libraries. Another way to test is to pick up the following integration build instead: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-2006 0105.071501.tar.gz With this build, you can also test scpexe and sftp if you were having any problems with them. Thanks!
[m2] Maven2 building Eclipse plugins, features, and update sites
I have been searching for this now for several days and have found nothing, so I thought I would ask here. Is there a maven2 plugin that supports building of Eclipse plugins, features, and update sites? Right now we have several Eclipse plugins that are built into ZIP files that can be unzipped into an Eclipse plugins directory. However, there are several problems with this: 1. There's no support for updating the plugin.xml with the version information of the plugin's jar. 2. There's no support for putting the maven pom.xml dependencies (direct or transitive) into the plugin.xml. 3. There's no support for building an Eclipse feature that includes those plugins. 4. There's no support for building an Eclipse update site from the feature or for that matter deploying to an update site. Right now we have some hackery to at least get to the ZIP file, but unless there is something already existing, I see a bunch of long nights ahead while I write my own stuff. The requirement is that we can have an update site automatically built/updated by our build system. So, is there anything that I can use here? Even if there is an open source project that goes only part of the way, it would possibly give me a head start. Thanks in advance for any help that anyone can give me. Jim Babka Senior Software Engineer Main: (512) 334 3200 Direct: (512) 334 3237 Email: [EMAIL PROTECTED] Webify Solutions Enabling the On Demand Enterprise(tm) www.webifysolutions.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Status of PVCS scm
On 1/6/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: Ok, subscribe to maven-scm list and we'll help you to understand/implement pvcs provider. I don't know if PVCS provide a java api, but if it isn't open sources, i prefer you use command line for PVCS calling. Will do. I am looking at the source code in apache ant's extension for pvcs. It doesn't look that bad and uses the command line.
Re: M2: Build error: maven-compiler-plugin does not exist
Have you tried updating you're plugins? use -U in your command -allan Torbjørn Smørgrav wrote: I know Im behind a http cache... is that the same as a http proxy? An other observation: Maven doesn't even try to lookup the remote repository (I think). But if I hack the DefaultArtifact version to match the version in my local repository (and not RELEASE), it tries to download that version. T -Original Message- From: Allan Ramirez [mailto:[EMAIL PROTECTED] Sent: 6. januar 2006 09:35 To: Maven Users List Subject: Re: M2: Build error: maven-compiler-plugin does not exist Hi, Please refer to this link http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-HowdoIresolvethe%22%3Cp luginname%3Edoesnotexistornovalidversion%22error%3F -allan Torbjørn Smørgrav wrote: mvn clean:clean -e -X gives me [ERROR] BUILD ERROR [INFO] - --- [INFO] The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not exist or no valid version could be found Any suggestions where to look? I get more or less the same on windows and linux with m2 and m2-alpha2. And it worked fine until yesterday. The complete output: + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: '/home/smorgrav/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/usr/local/maven/conf/plugin-registry.xml' [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'clean'. [DEBUG] maven-compiler-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the latest version org.apache.maven.plugins:maven-compiler-plugin:LATEST:pom [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-compiler-plugin:pom:LATEST [DEBUG] maven-compiler-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the release version org.apache.maven.plugins:maven-compiler-plugin:RELEASE:pom [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-compiler-plugin:pom:RELEASE [INFO] - --- [ERROR] BUILD ERROR [INFO] - --- [INFO] The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not exist or no valid version could be found [INFO] - --- [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLif e cycleExecutor.java:1124) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(Defau l tLifecycleExecutor.java:1305) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggreg a tionNeeds(DefaultLifecycleExecutor.java:376) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycl e Executor.java:132) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3 9 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l .java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not exist or no valid version could be found at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVe r sion(DefaultPluginVersionManager.java:225) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVe r sion(DefaultPluginVersionManager.java:87) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginMana g er.java:158) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLif e cycleExecutor.java:1095) ... 14 more [INFO] - --- [INFO] Total time: 1 second [INFO] Finished at: Fri Jan 06 10:18:16 GMT 2006 [INFO]
RE: call for testers: scp wagon
This is failing for me. I am continuing to get the session is down exception. I'm not sure what debugging information you'd like to see. I'm getting the same basic stack trace I've always gotten with a root cause like this: Caused by: com.jcraft.jsch.JSchException: session is down at com.jcraft.jsch.Channel.connect(Unknown Source) at org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:125) ... 22 more I tried downloading the jars you specified and putting them in my 2.0.1 lib directory. I also tried downloading the 2.0.x release (without modifying its /lib directory) and that failed as well. My build is on Windows XP, the remote repository is Solaris 10. K.C. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 04, 2006 11:34 PM To: Maven Users List Subject: call for testers: scp wagon Hi, In the lead up to the 2.0.2 release, I'd like anyone experiencing: [WAGONSSH-28] session is down [WAGONSSH-30] hangs during deployment to test the following wagon snapshots: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/wagon/wagon-ssh/1.0-alpha-6-SNAPSHOT/wagon-ssh-1.0-alpha-6-20060105.062346-2.jar by including it in your $M2_HOME/lib directory. Please also include: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6-SNAPSHOT/wagon-provider-api-1.0-alpha-6-20060105.062346-7.jar and http://www.ibiblio.org/maven2/com/jcraft/jsch/0.1.24/jsch-0.1.24.jar Replace any existing wagon/jsch libraries. Another way to test is to pick up the following integration build instead: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060105.071501.tar.gz With this build, you can also test scpexe and sftp if you were having any problems with them. Thanks! - Brett - 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: SCM username/password lookup
I thought the maven dev folks working very hard not to allow maven-scm from
knowing
anything about maven ( in this case, settings.xml). The prefer way is thru
plugins
is it still true?
-Dan
On 1/6/06, David Hawkins [EMAIL PROTECTED] wrote:
In the new pure java svn provider (SCM-13), I had it look up the username,
password, passphrase, etc in the servers of a user's settings. I
implemented it so that the server id could be nearly any piece of the
server
+ url. Afterwards I was thinking it might be better to implement this in a
generic way so that all scm providers either:
a.) return a server id to be used to lookup the server and the scm-api
would assign the server to the ScmProvider. The provider would then
fetch
the username, password, private key, and any other applicable settings.
b.) passed a reference to the settings object or servers list and let
the
provider find the applicable server itself.
The release plugin has StarTeam specific code which basically looks up the
auth information from the settings. If this is a common thing for
multiple
providers, we should probably handle it at a higher level than within each
provider. Something should definitely be done so that we don't have
provider specific code in various plugins.
--David
- Original Message -
From: Emmanuel Venisse [EMAIL PROTECTED]
To: Maven Users List users@maven.apache.org
Sent: Friday, January 06, 2006 3:23 PM
Subject: Re: SCM username/password lookup
Yes, i think it's a bug. We must set username to ${user.name} if other
places don't set it.
Emmanuel
dan tran a écrit :
any one?
-D
On 1/5/06, dan tran [EMAIL PROTECTED] wrote:
There are 3 places to look for in this order
Command line
settings.xml
connectionUrl
However in maven-release-plugin, if user does not provide username
via command line (ie -Dusername=xyz),
username is default to system property ${user.name} and by passing
settings.xml.
is it a bug?
-Dan
-
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: SCM username/password lookup
Yes. Anything settings.xml provides should be passed into the SCM API.
- Brett
On 1/7/06, dan tran [EMAIL PROTECTED] wrote:
I thought the maven dev folks working very hard not to allow maven-scm from
knowing
anything about maven ( in this case, settings.xml). The prefer way is thru
plugins
is it still true?
-Dan
On 1/6/06, David Hawkins [EMAIL PROTECTED] wrote:
In the new pure java svn provider (SCM-13), I had it look up the username,
password, passphrase, etc in the servers of a user's settings. I
implemented it so that the server id could be nearly any piece of the
server
+ url. Afterwards I was thinking it might be better to implement this in a
generic way so that all scm providers either:
a.) return a server id to be used to lookup the server and the scm-api
would assign the server to the ScmProvider. The provider would then
fetch
the username, password, private key, and any other applicable settings.
b.) passed a reference to the settings object or servers list and let
the
provider find the applicable server itself.
The release plugin has StarTeam specific code which basically looks up the
auth information from the settings. If this is a common thing for
multiple
providers, we should probably handle it at a higher level than within each
provider. Something should definitely be done so that we don't have
provider specific code in various plugins.
--David
- Original Message -
From: Emmanuel Venisse [EMAIL PROTECTED]
To: Maven Users List users@maven.apache.org
Sent: Friday, January 06, 2006 3:23 PM
Subject: Re: SCM username/password lookup
Yes, i think it's a bug. We must set username to ${user.name} if other
places don't set it.
Emmanuel
dan tran a écrit :
any one?
-D
On 1/5/06, dan tran [EMAIL PROTECTED] wrote:
There are 3 places to look for in this order
Command line
settings.xml
connectionUrl
However in maven-release-plugin, if user does not provide username
via command line (ie -Dusername=xyz),
username is default to system property ${user.name} and by passing
settings.xml.
is it a bug?
-Dan
-
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: [m2] How to add additional path for surefire test sources?
binzOBV5rRuqa.bin Description: this
Re: [m2] How to get artifact and Maven project for dependencies and transitive dependencies
Please try this link http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-HowdoIgetaplugin%27sdependenciesfromaMojo%3F -allan [EMAIL PROTECTED] wrote: Hi, As part of my effort to write a customized dependency report (in XML), I looked at the maven-project-reports-info-plugin to understand how the dependency resolution works. I made a slight modification, as it somehow didn't produce the results I wanted. I'm doing the following: To get a list of dependencies for a Maven project (List object contains a list of Dependency objects): // get list of dependencies List dependencies = project.getDependencies(); To get the project artifact associated with a dependency: // create project artifact for dependency Artifact depArtifact = artifactFactory .createProjectArtifact(dependency.getGroupId(), dependency .getArtifactId(), dependency.getVersion(), dependency.getScope()); To get a Maven project object associated with an artifact (assuming that the Artifact type is pom): // get project associated with artifact return mavenProjectBuilder.buildFromRepository(artifact, project.getRemoteArtifactRepositories(), localRepository); At last I'm resolving transitive dependencies by looking up the Maven project object associated with a dependency, getting a list of dependencies from that project object, getting the project artifact associated with each of those dependencies (to get download URL and description). I can parse the dependency tree by doing this recursively (though I'm stopping at level 1 at this point). Can anybody tell me if there is a better way (and possibly a way which guarantees that this still will work with Maven 2.1+) to do this work? Thanks, Chris No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.14/222 - Release Date: 1/5/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
