Re: Maven plugin for Eclipse
Hi, did you refresh the settings in eclipse? It has to be done under Window-Preferences-Maven-Refresh Settings. Best regards Achim De Vleeschauwer Nele wrote: Hi, I have configured my settings.xml in this way and if I execute a maven command from a dos box, it is using our company's repository. But if I call a maven command out of Eclipse, it goes directly to the Maven Repo site. -Original Message- From: COPPENS, Fabien [mailto:[EMAIL PROTECTED] Sent: donderdag 6 september 2007 14:14 To: Maven Users List Subject: RE: Maven plugin for Eclipse I believe you can configure this in your maven settings.xml file via a profile : pluginRepositories pluginRepository idMyDevRepo/id url http://myrepository /url snapshots enabledtrue/enabled /snapshots releases enabledfalse/enabled /releases /pluginRepository /pluginRepositories /profile -Message d'origine- De : De Vleeschauwer Nele [mailto:[EMAIL PROTECTED] Envoyé : jeudi 6 septembre 2007 14:11 À : Maven Users List Objet : Maven plugin for Eclipse Hi, For the moment I'm using version 3.3 of Eclipse with the Maven plugin installed. Each time when I execute a maven command in Eclipse, Eclipse tries to download the necessary artiftacts from the Maven Repo site (repo1.maven.org). How can I configure that Eclipse should use the company's central Maven Repository to download new artifacts instead of the one on the Maven site ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Version numbering
Hi, I think you can just omit the version element in the child pom. Best regards Achim EJ Ciramella wrote: Is there any way for a child pom to simply inherit the version number from the parent? We have a few use cases where this would be very helpful. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How does maven decide which dependencies to update from remote repositories
Hi, I have a project A using a parent project which is defined like that parent groupIdfoo/groupId artifactIdbar/artifactId versionRELEASE/version /parent The intention of the RELEASE version is that the latest release is used. I would expect that the latest release of my local repository is used if I do not call maven with option -U or with an updatePolicy always. So when I start my work in the morning and try to compile project A with mvn compile I get the error message org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to determine the release version How does maven try to determine the release version? Why does it not use the latest version from my local repository? The default for the updatePolicy is daily. But maven does not seem to check the remote repository on my first call in the morning. How does maven know that it is a new day? When I try mvn compile with updatePolicy set to always or option -U the latest version of the parent is resolved. The latest version already was in my local repository so no download was needed. I thought the information about which artifact was already updated on a daily basis would be somewhere in the maven-metadata-local.xml of my parent project but this file did not change after the update. I hope someone can answer some of my questions. Best regards Achim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Using axistools-maven-plugin to create Axis 1.1 stubs
Hi, I would like to use the axistools-maven-plugin to create Axis 1.1 stubs. Version 1.1-SNAPSHOT of the plugin has Axis 1.4 as dependencies and therefore creates stubs for Axis 1.4. I tried adding axis 1.1 dependencies to the plugin. From the maven output with option -X I can see the following pluginArtifacts: [DEBUG] (f) pluginArtifacts = [axis:axis-jaxrpc:jar:1.1:runtime, org.apache.axis:axis-jaxrpc:jar:1.4:runtime, org.apache.axis:axis:jar:1.4:runtime, org.codehaus.plexus:plexus-compiler-api:jar:1.5.1:runtime, axis:axis-saaj:jar:1.1:runtime, axis:axis-wsdl4j:jar:1.5.1:runtime, commons-logging:commons-logging:jar:1.0.4:runtime, axis:axis:jar:1.1-patched:runtime, org.codehaus.plexus:plexus-utils:jar:1.1:runtime, org.apache.axis:axis-saaj:jar:1.4:runtime, plexus:plexus-utils:jar:1.0.1:runtime, commons-discovery:commons-discovery:jar:20040218.194635:runtime, org.apache.maven:maven-plugin-api:jar:2.0:runtime, org.apache.maven:maven-core:jar:2.0:runtime] So, my axis 1.1 library is included but the axis 1.4 dependencies are still there and the created stubs are 1.4. Now, what is the format for the pluginArtifacts element? Everything I tried so far has no effect. The pluginArtifacts remain the dependencies defined in the plugin's pom. Thanks for help Achim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Release several artifacts depending on profiles
Hi, we have the following scenario we want to solve with maven: we have projects generating axis clients using the axistools-maven-plugin. Depending on the environment in which these client projects are deployed the clients are build with either axis 1.1 or axis 1.3. Now we want to use maven to create and release artifacts for these client projects. We can use profiles (one for Axis 1.1, one for Axis 1.3) to create different artifacts. But how can we produce release artifacts for all profiles in one run. Perhaps this can be better solved using assemblies. We would have to define one assembly for each variation which creates a release file looking something like client-axis1.1-1.0.0.jar. The next problem is then to define a dependency to this artefact in another project. Any help or best practises are welcome. Best regards Achim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to provide own codegen-config.properties for axis2-wsdl2code-maven-plugin
Hi, I would like to provide my own codegen-config.properties for the axis2-wsdl2code-maven-plugin. Looking at the sources I found out that the location of the properties file can be set via a system property org.apache.axis2.codegen.config As far as I can see the value of the property has to be a resource location. Where shall I put the file such that the plugin can find the resource? I tried src/main/resources Is there an option to define additional resources for plugins in the pom.xml? Best regards Achim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-install-plugin: checksum case sensitivity
Hi, the maven-install-plugin can generate checksum files when the property createChecksum=true is set. In my environment (a continuum server) the checksum contains upper case letters. When such a dependency is downloaded (e.g. during the compile phase of another project) the checksum is checked. On my local machine (not the continuum server) the checksum contains lower case letters and the check fails although the checksum is generally the same. Now my questions: 1. is this a bug or a configuration issue? 2. how can the checksum algorithm be changed (MD5, SHA1)? Best regards Achim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Password ignored when checking out using CVS with ext
Hi Barrie, Barrie Treloar wrote: And it does not help me to make continuum run in batch. I'm not suggesting to run continuum in batch. I have been mistaken. What I wanted to say is that it does not help me to get mvn to work in batch-mode (from the command line) since it is a problem with an ant project. And the problem occurs with the cvs update command. What I am saying is that you should be able to run the same mvn command as continuum does. When you that command it should not prompt for any information and complete correctly (i.e in a batch mode). There is no point trying to go any further until you can run the exact command that continuum would run on the command line yourself. But you are completely right to first try the same things that continuum does from the command line. After preparing the ssh key files the cvs update command worked without prompting for a password and so the whole build in continuum worked, too. Ok. I got this to work by using ssh keyfiles. But what are the username and password fields in the web interface good for? Can they only be used for pserver connections? Which screen is this? It is on the Update Continuum Project page. The path is /continuum/servlet/continuum/target/Edit.vm You get there with Show Projects - choose a project from the list - Edit Best regards Achim
Re: Password ignored when checking out using CVS with ext
Hi, Barrie Treloar wrote: On 7/11/06, Mike Lee [EMAIL PROTECTED] wrote: I had a similar problem as you described. I believe I had to do a xhost + command before I ssh'ed into the machine as root to start the Continuum server. Err, xhost + is a very insecure solution to the problem. And it does not help me to make continuum run in batch. Hi, I am using continuum 1.0.3 on linux. The continuum server is run as root. I'd create a continuum user and run as that, never run applications as root. Continuum has no need for the privileges that root enjoys. scm:cvs:ext:server:path:module [del] Error: Can't open display: :0.0 Xlib: connection to :0.0 refused by server Xlib: No protocol specified openssh tries to ask for the password in a popup which fails. [del] When I run continuum as a user which owns the display the popup appears, I can type in the password and continuum continues its work successfully. How can I configure continuum (or openssh) to take the password provided in the web interface? Continuum runs maven no differently than if you ran mvn on the command line. You should get mvn to work as the continuum user in batch-mode so that no popups occur and it works correctly from the command line. Until this happens there is no point setting up continuum. This may require configuring the key files in ~continuum/.ssh to not have a passphrase. Ok. I got this to work by using ssh keyfiles. But what are the username and password fields in the web interface good for? Can they only be used for pserver connections? Thanks for your help Achim It may also require your to have run the cvs login command by hand to create the ~/.cvspass file with a password included. Having no passphrase and storing keys in .cvspass are not ideal security choices but they rely on linux filesystem permissions which is pretty reasonable. It is much better than running continuum as root or using xhost +.
