Re: new user
Maven requires access to a remote repository. If your firewall prevents this you'll need to setup a local one. Information for this can be found spread around the maven documentation and Better Builds with Maven guide. Can you get me out of my two year contract? =) On 7/31/06, Barnes, Mike [EMAIL PROTECTED] wrote: I just finished downloading maven 2 and am now trying to create a new project using the example described on the getting started page. I am able to execute mvn -version with no problems, however when I attempt to execute mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app I get the following error: [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retri eved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exi st or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 22 seconds [INFO] Finished at: Mon Jul 31 12:51:57 EDT 2006 [INFO] Final Memory: 1M/2M [INFO] Based on the above message I would have expected the archtype plugin to already be downloaded. BTW, I am behind a firewall which uses a policy file (not sure how to configure this in the proxy section) Thanks for any help. Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
uniqueVersion not inherited in child projects?
My parent project defines the following: distributionManagement snapshotRepository idYo/id nameYo Repository/name urlscp://yo/home/maven/www/url uniqueVersionfalse/uniqueVersion /snapshotRepository /distributionManagement When I run the following command in the child project: mvn help:effective-pom I get the following results: ... distributionManagement snapshotRepository idYo/id nameYo Repository/name urlscp://yo/home/maven/www/url /snapshotRepository /distributionManagement ... It looks like inheritence is ignoring the uniqueVersion element. Shouldn't the child POM be inheriting that? Or am I doing something wrong? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Issues related to snapshot versions of dependencies and filenames
Do you know what mechanism chooses snapshotRepository over repository, if both are present in distributionManagement? On 7/28/06, Jörg Schaible [EMAIL PROTECTED] wrote: Stefan Magnus Landrø wrote on Friday, July 28, 2006 10:49 AM: I believe I found the solution to this issue. I placed the following snipplet in the jar-projects that my project depend upon, and made sure to use uniqueVersion set to false. A fresh deploy of these jar-projects then wrote a -SNAPSHOT.jar to the company repository (you only get timestamped versions if you use uniqueVersion=true(default)) distributionManagement snapshotRepository idinternal/id nameCompany Repository/name urlfile:\\server\repo-local/url uniqueVersionfalse/uniqueVersion /snapshotRepository /distributionManagement To bad there is nothing about this in the mergere book and despite the fact, that this has its own quirks: http://jira.codehaus.org/browse/MNG-1908 [snip] - Jörg - 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: Ad: Re: Issues related to snapshot versions of dependencies and filenames
Right. My question is how is snapshot choosen over repository? Does the deploy plugin grep the version number or something? On 7/28/06, Stefan Magnus Landrø [EMAIL PROTECTED] wrote: I believe shapshots go in the snapshot repository, and release versions go in the release repository. korebantic [EMAIL PROTECTED] skrev 28.07.2006 14:37:25: Do you know what mechanism chooses snapshotRepository over repository, if both are present in distributionManagement? On 7/28/06, Jörg Schaible [EMAIL PROTECTED] wrote: Stefan Magnus Landrø wrote on Friday, July 28, 2006 10:49 AM: I believe I found the solution to this issue. I placed the following snipplet in the jar-projects that my project depend upon, and made sure to use uniqueVersion set to false. A fresh deploy of these jar-projects then wrote a -SNAPSHOT.jar to the company repository (you only get timestamped versions if you use uniqueVersion=true(default)) distributionManagement snapshotRepository idinternal/id nameCompany Repository/name urlfile:\\server\repo-local/url uniqueVersionfalse/uniqueVersion /snapshotRepository /distributionManagement To bad there is nothing about this in the mergere book and despite the fact, that this has its own quirks: http://jira.codehaus.org/browse/MNG-1908 [snip] - Jörg - 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: Issues related to snapshot versions of dependencies and filenames
Got it, thanks =p On 7/28/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 7/28/06, korebantic [EMAIL PROTECTED] wrote: Do you know what mechanism chooses snapshotRepository over repository, if both are present in distributionManagement? For deployment, if the version ends in -SNAPSHOT, it will go to the snapshotRepository (timestamped or not depending on the uniqueVersion setting.) Otherwise, it goes to repository. -- Wendy - 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: The authenticity of host 'www.whatever.com' can't be established
Worked perfectly! (Except that I'm on windows so c:\Document and Settings\username\.ssh) I think something is broken with Wagon -- shouldn't it create that directory and file, the same way that the command line version of ssh does? Thanks again! On 7/26/06, Wayne Fay [EMAIL PROTECTED] wrote: This was discussed recently... http://www.nabble.com/Default-dir-fo-site-src-tf1976644.html#a5431309 The resolution was: Try adding an empty file ~/.ssh/known_hosts Wayne On 7/26/06, korebantic [EMAIL PROTECTED] wrote: I'm working on creating a remote repository. I'm uploading to the repository using: http://maven.apache.org/guides/mini/guide-3rd-party-jars-remote.html In setting up ssh, I cannot get rid of the The authenticity of host 'www.whatever.com' can't be established message when executing mvn deploy:deploy-file. I don't get that message when connecting via ssh from the command line. I've followed both these suggestions carefully, but neither make any difference: http://www.csua.berkeley.edu/~ranga/notes/ssh_nopass.html http://www.mail-archive.com/users@maven.apache.org/msg42287.html Any suggestions? Thanks... - 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]
The authenticity of host 'www.whatever.com' can't be established
I'm working on creating a remote repository. I'm uploading to the repository using: http://maven.apache.org/guides/mini/guide-3rd-party-jars-remote.html In setting up ssh, I cannot get rid of the The authenticity of host 'www.whatever.com' can't be established message when executing mvn deploy:deploy-file. I don't get that message when connecting via ssh from the command line. I've followed both these suggestions carefully, but neither make any difference: http://www.csua.berkeley.edu/~ranga/notes/ssh_nopass.html http://www.mail-archive.com/users@maven.apache.org/msg42287.html Any suggestions? Thanks... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: deploying jars without version information
Ironic. I was just getting ready to ask a similar question. Although I'm fine with the versioning that occurs in the repository, I need the ability for the jar name to not contain this version string in it when I create a release or deploy the project to the integration server for testing. In my case I'm extending a pre-existing J2EE commercial application. It expects jars, even ones especially created for end-user customization, to follow certain naming conventions. It's just not feasible for these jars to be renamed to something else (yaddayadda-1.0-SNAPSHOT.jar). Yes, it's true that you can use the plug in configuration section to force a generated jar or war to have a certain name. As far as I can tell, this only affects the package phase. Am I on the wrong track here thinking that maven2 is suitable for creating official releases, for deploying to integration test servers? If it is appropriate to use maven2 for this purpose, how would you recommend I get around the naming issue? (Again, not in the repository, rather during integration testing and product release). On 7/25/06, Mike Perham [EMAIL PROTECTED] wrote: Why? Removing version info is very dangerous. You then have no idea which version was actually selected by Maven by looking in the artifact after the fact. -Original Message- From: LaCasse, John [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 25, 2006 12:57 PM To: Maven Users List Subject: RE: deploying jars without version information I'm talking about the second case; in the target\webapp\WEB-INF\lib. All compile and runtime scoped dependant jars that get put into this location; I would like the war plugin not to include the version info on all the jars it includes in this location. -Original Message- From: Alexandre Poitras [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 25, 2006 10:53 AM To: Maven Users List Subject: Re: deploying jars without version information What do you means by deploting? Deploying on a maven repository or on a application server ? In the first case, the answer is no because Maven needs those metadatas to be able to manage dependencies. In the other case, yes it's possible just change the name in your war/jar plugin configuration section. On 7/25/06, LaCasse, John [EMAIL PROTECTED] wrote: Hi, Does anybody know if you can have Maven deploy the jars that end up in webapp/WEB-INF/lib without the version information in the filename? Thanks, Jpl - 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]
