RE: A question about dependency/
I think maybe you haven't understood what my question means since I haven't cleared my question clearly. :-) Surely I will not put the jar-files in my local repository. But sometimes I have to put the jar-files in the remote repository in the server machine. For example by using spring. The srpnig.jar has no version number. So I have to add the version number to it. In this case I have to create the dir-structure in the repository. And I don't like creating sub-dir for each version number. I just want to put them together under the same dir. ** There is a nice way to do it. Don't start putting your own files in your local repository. Take a look at mvn install:install-file [1] or mvn deploy:deploy-file [2] if you are working with a team. Hth, Nick Stolwijk [1] http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html [2] http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html -Original Message- From: Thomas Chang [mailto:[EMAIL PROTECTED] Sent: Tue 1/8/2008 9:37 AM To: users@maven.apache.org Subject: A question about dependency/ Hi all, Formerly I use the maven1 and in the project.xml I have the dependency/ as follow: dependency groupIdjsf-facelets/groupId artifactIdjsf-facelets/artifactId version1.1.12/version typejar/type /dependency And in the repository the dir-structure looks as follow: /repo /jsf-facelets /jars --jsf-facelets-1.1.12.jar If I have another version of jsf-facelets.jar, I can simply put them under the same dir. Now by maven2 I have the same dependency/ in POM.XML, but the repository structure must be as follow: /repo /jsf-facelets /jsf-facelets /1.1.12 --jsf-facelets-1.1.12 If I have another version of jsf-facelets.jar. I have to create a new sub-dir with the version number such as follow: /repo /jsf-facelets /jsf-facelets /1.1.12 --jsf-facelets-1.1.12 /1.1.13 --jsf-facelets-1.1.13 I find this is more complicated. Is there anyway to do as by maven 1? Regards Thomas - Ihre erste Baustelle? Wissenswertes für Bastler und Hobby Handwerker.
Re: A question about dependency/
You should use the deploy plugin to do it: http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html Hand based manipulations are forbidden on local and remote repositories Jeff On Jan 8, 2008 10:27 AM, Thomas Chang [EMAIL PROTECTED] wrote: I think maybe you haven't understood what my question means since I haven't cleared my question clearly. :-) Surely I will not put the jar-files in my local repository. But sometimes I have to put the jar-files in the remote repository in the server machine. For example by using spring. The srpnig.jar has no version number. So I have to add the version number to it. In this case I have to create the dir-structure in the repository. And I don't like creating sub-dir for each version number. I just want to put them together under the same dir. ** There is a nice way to do it. Don't start putting your own files in your local repository. Take a look at mvn install:install-file [1] or mvn deploy:deploy-file [2] if you are working with a team. Hth, Nick Stolwijk [1] http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html [2] http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html -Original Message- From: Thomas Chang [mailto:[EMAIL PROTECTED] Sent: Tue 1/8/2008 9:37 AM To: users@maven.apache.org Subject: A question about dependency/ Hi all, Formerly I use the maven1 and in the project.xml I have the dependency/ as follow: dependency groupIdjsf-facelets/groupId artifactIdjsf-facelets/artifactId version1.1.12/version typejar/type /dependency And in the repository the dir-structure looks as follow: /repo /jsf-facelets /jars --jsf-facelets-1.1.12.jar If I have another version of jsf-facelets.jar, I can simply put them under the same dir. Now by maven2 I have the same dependency/ in POM.XML, but the repository structure must be as follow: /repo /jsf-facelets /jsf-facelets /1.1.12 --jsf-facelets-1.1.12 If I have another version of jsf-facelets.jar. I have to create a new sub-dir with the version number such as follow: /repo /jsf-facelets /jsf-facelets /1.1.12 --jsf-facelets-1.1.12 /1.1.13 --jsf-facelets-1.1.13 I find this is more complicated. Is there anyway to do as by maven 1? Regards Thomas - Ihre erste Baustelle? Wissenswertes für Bastler und Hobby Handwerker. -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c'est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com
RE: A question about dependency/
There is a nice way to do it. Don't start putting your own files in your local repository. Take a look at mvn install:install-file [1] or mvn deploy:deploy-file [2] if you are working with a team. Hth, Nick Stolwijk [1] http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html [2] http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html -Original Message- From: Thomas Chang [mailto:[EMAIL PROTECTED] Sent: Tue 1/8/2008 9:37 AM To: users@maven.apache.org Subject: A question about dependency/ Hi all, Formerly I use the maven1 and in the project.xml I have the dependency/ as follow: dependency groupIdjsf-facelets/groupId artifactIdjsf-facelets/artifactId version1.1.12/version typejar/type /dependency And in the repository the dir-structure looks as follow: /repo /jsf-facelets /jars --jsf-facelets-1.1.12.jar If I have another version of jsf-facelets.jar, I can simply put them under the same dir. Now by maven2 I have the same dependency/ in POM.XML, but the repository structure must be as follow: /repo /jsf-facelets /jsf-facelets /1.1.12 --jsf-facelets-1.1.12 If I have another version of jsf-facelets.jar. I have to create a new sub-dir with the version number such as follow: /repo /jsf-facelets /jsf-facelets /1.1.12 --jsf-facelets-1.1.12 /1.1.13 --jsf-facelets-1.1.13 I find this is more complicated. Is there anyway to do as by maven 1? Regards Thomas - Ihr erstes Fernweh? Wo gibt es den schönsten Strand.
Re: [m2] Question about Dependency version rules and a couple suspect logging bugs.
I think the reporting of removed then selected was fixed in svn. 1) nearer is correct, the default rule is to use the nearest declared version (number of transitivie hops to the pom). 2) as above, we'll be introducing more in future (we have newest in there, but there's no way to enable it in 2.0) 3) yes, I think it is fixed. On 11/23/05, Paul Spencer [EMAIL PROTECTED] wrote: The following message is displayed during the by mvn -X compile. [DEBUG] commons-collections:commons-collections:jar:2.1 (removed - nearer found: 3.0) [DEBUG] commons-collections:commons-collections:jar:2.1 (selected for compile) 1) Should the word be newer instead of nearer in the first debug line? Is this a logging bug? 2) What are the rules around which version is select when their are multiple version for an artifact? 3) The classpath element contains commons-collection 3.0, not 2.1 as stated by the second debug line. Is this a logging bug? Paul Spencer - 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]
