Re: how to configure Default Repository Layout for local repository
Using install:install-file or deploy:deploy-file will enable you to install your "legacy" named jars into the repository format by passing metadata on the command line. Though jars may not have the version in their name they still have metadata or a release number associated with them where this information will be available. Andy On 3 Jul 2007, at 20:56, Harish Kachoria wrote: I understand.. But the bad thing is backward compatiablty. Maven 1.0 support tag by which we can avoid version number. and Maven 2.0 not. and renaming of legacy jar is not a good idea. Because they are provided by third party. and because Maven don't like the name of jar, so rename the jar Maven designer should consider the fact that Many of Legacy jars do not have version numbers. and Mangement always afraid to touch such jars. even if it is a small change. I think I have to convince for renaming jar on development env. Wayne Fay wrote: Your only option (if you want to continue using Maven) is to starting using versions. Even if you use scope=system you still need to set a version in the node. And system scope is just a bad idea in the first place, generally. Wayne On 7/3/07, Harish Kachoria wrote: OK it works from me.. I created remote repo on my local machine. and maven downloded the jars stored them in the way he likes. still I have one problem, my libraries does not have any version number. and version number is mandatory for maven 2.0. ( tag had been removed in maven 2.0) so now I have two solution - - rename all jar with some fake version(may be 1.0) and then convince management for this. which I know won't happen - forget maven. which I don't prefer. (this was my idea to use maven in this project) so can you find any other solution. Carlos Sanchez-4 wrote: you can't change the local repository layout, it's a cache for maven and it shouldn't matter how it's stored you can change the remote repositories layout, so just create a remote repo for your projects in whatever style you want, although not a great idea On 7/3/07, Harish Kachoria wrote: It would be better if I can explain my problem then you can suggest me some solution Currently I have one project which has around 30+sub projects (Which I can say modules) Each sub project has its own ear which contains 1 war module and 1 ejb module. There are some common libraries also which are shared accros the projects. In development env we copy this library at local location and use them from JBuilder. In production env, many ears are deployed (this project as well as other projects) and all common libraries are in server lib folder. now I want to build one sub project using maven. and I need to refer all common libraries just for compilations (as we never include common library in EAR) To use maven I need to define dependancy and needs to copy common library in repo. I wants to copy all jars in one folder of repo and trying to use it but with Maven 2.0 it seems to be not possible. If you have any alternate way then please let me know -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout- for-local-repository-tf4018468s177.html#a11417704 Sent from the Maven - Users mailing list archive at Nabble.com. -- --- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout- for-local-repository-tf4018468s177.html#a11418660 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] :arguing::arguing::arguing::arguing::arguing::arguing::arguing: -- View this message in context: http://www.nabble.com/how-to- configure-Default-Repository-Layout-for-local-repository- tf4018468s177.html#a11419527 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: how to configure Default Repository Layout for local repository
ya I think we also need to manage our dependdancy in same way. But one thing worried me the Version number. Some of my third party jars do not have version number. and I think I have to rename them by some version number. That I can do on development env but for production I need to convince many peoples. other wise I need to maintain 2 copy of such jars. one orignal and one with version num post fix. We wants to make thing more easier rather then introducing complications. Timothy Reilly-2 wrote: > > > [Harish wrote:] >> so can you find any other solution. > > Here is how we are managing our application server libraries and server > shared libraries on my current project. > > We have internal corporate repositories (several - one per environment. > E.g. unit, dev, test, release, etc.) > We have an additional repository (third-party) > We load the third-party jars using a script in the same manner posted to > this thread earlier. > We define the artifact version in the script to match the product > version. > There is no maintanance here (which I think you objected to) - leave > that version in place indefinitely. > When a new third-party product version is released, then run the script > again with the new version. > Projects declare their dependencies on a particular third-party > dependency version and scope is "provided". > When you migrate an application to the next version (update the > dependency declarations in your pom files.) > This works for us. > > Our only nit right now is how to build for multiple target product > versions and reduce some maintenance. > We are beginning to wrap these third-party dependencies into profiles so > we can build for varying > target appservers, content management systems, or whatever the set of > third-party dependencies is for.) > > hth > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11423503 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: how to configure Default Repository Layout for local repository
If Maven 1.x behavior is that important to you, then use Maven 1.1. It is an excellent product. -Original Message- From: Harish Kachoria [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 03, 2007 2:56 PM To: users@maven.apache.org Subject: Re: how to configure Default Repository Layout for local repository I understand.. But the bad thing is backward compatiablty. Maven 1.0 support tag by which we can avoid version number. and Maven 2.0 not. and renaming of legacy jar is not a good idea. Because they are provided by third party. and because Maven don't like the name of jar, so rename the jar Maven designer should consider the fact that Many of Legacy jars do not have version numbers. and Mangement always afraid to touch such jars. even if it is a small change. I think I have to convince for renaming jar on development env. Wayne Fay wrote: > > Your only option (if you want to continue using Maven) is to starting > using versions. > > Even if you use scope=system you still need to set a version in the > node. And system scope is just a bad idea in the first > place, generally. > > Wayne > > On 7/3/07, Harish Kachoria wrote: >> >> OK it works from me.. I created remote repo on my local machine. >> and maven downloded the jars stored them in the way he likes. >> >> still I have one problem, my libraries does not have any version number. >> and >> version number is mandatory for maven 2.0. ( tag had been removed in >> maven 2.0) >> so now I have two solution - >> - rename all jar with some fake version(may be 1.0) and then convince >> management for this. which I know won't happen >> - forget maven. which I don't prefer. (this was my idea to use maven in >> this >> project) >> >> so can you find any other solution. >> >> >> >> >> >> Carlos Sanchez-4 wrote: >> > >> > you can't change the local repository layout, it's a cache for maven >> > and it shouldn't matter how it's stored >> > >> > you can change the remote repositories layout, so just create a remote >> > repo for your projects in whatever style you want, although not a >> > great idea >> > >> > On 7/3/07, Harish Kachoria wrote: >> >> >> >> It would be better if I can explain my problem then you can suggest me >> >> some >> >> solution >> >> >> >> Currently I have one project which has around 30+sub projects (Which I >> >> can >> >> say modules) >> >> Each sub project has its own ear which contains 1 war module and 1 ejb >> >> module. >> >> >> >> There are some common libraries also which are shared accros the >> >> projects. >> >> >> >> In development env we copy this library at local location and use them >> >> from >> >> JBuilder. >> >> >> >> In production env, many ears are deployed (this project as well as >> other >> >> projects) and all common libraries are in server lib folder. >> >> >> >> now I want to build one sub project using maven. and I need to refer >> all >> >> common libraries just for compilations (as we never include common >> >> library >> >> in EAR) >> >> >> >> To use maven I need to define dependancy and needs to copy common >> library >> >> in >> >> repo. >> >> >> >> I wants to copy all jars in one folder of repo and trying to use it >> but >> >> with >> >> Maven 2.0 it seems to be not possible. >> >> >> >> If you have any alternate way then please let me know >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-r epository-tf4018468s177.html#a11417704 >> >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> >> >> >> - >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > >> > -- >> > I could give you my word as a Spaniard. >> > No good. I've known too many Spaniards. >> > -- The Princess Bride >> > >> > - >> > To unsubsc
RE: how to configure Default Repository Layout for local repository
[Harish wrote:] > so can you find any other solution. Here is how we are managing our application server libraries and server shared libraries on my current project. We have internal corporate repositories (several - one per environment. E.g. unit, dev, test, release, etc.) We have an additional repository (third-party) We load the third-party jars using a script in the same manner posted to this thread earlier. We define the artifact version in the script to match the product version. There is no maintanance here (which I think you objected to) - leave that version in place indefinitely. When a new third-party product version is released, then run the script again with the new version. Projects declare their dependencies on a particular third-party dependency version and scope is "provided". When you migrate an application to the next version (update the dependency declarations in your pom files.) This works for us. Our only nit right now is how to build for multiple target product versions and reduce some maintenance. We are beginning to wrap these third-party dependencies into profiles so we can build for varying target appservers, content management systems, or whatever the set of third-party dependencies is for.) hth - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to configure Default Repository Layout for local repository
I understand.. But the bad thing is backward compatiablty. Maven 1.0 support tag by which we can avoid version number. and Maven 2.0 not. and renaming of legacy jar is not a good idea. Because they are provided by third party. and because Maven don't like the name of jar, so rename the jar Maven designer should consider the fact that Many of Legacy jars do not have version numbers. and Mangement always afraid to touch such jars. even if it is a small change. I think I have to convince for renaming jar on development env. Wayne Fay wrote: > > Your only option (if you want to continue using Maven) is to starting > using versions. > > Even if you use scope=system you still need to set a version in the > node. And system scope is just a bad idea in the first > place, generally. > > Wayne > > On 7/3/07, Harish Kachoria wrote: >> >> OK it works from me.. I created remote repo on my local machine. >> and maven downloded the jars stored them in the way he likes. >> >> still I have one problem, my libraries does not have any version number. >> and >> version number is mandatory for maven 2.0. ( tag had been removed in >> maven 2.0) >> so now I have two solution - >> - rename all jar with some fake version(may be 1.0) and then convince >> management for this. which I know won't happen >> - forget maven. which I don't prefer. (this was my idea to use maven in >> this >> project) >> >> so can you find any other solution. >> >> >> >> >> >> Carlos Sanchez-4 wrote: >> > >> > you can't change the local repository layout, it's a cache for maven >> > and it shouldn't matter how it's stored >> > >> > you can change the remote repositories layout, so just create a remote >> > repo for your projects in whatever style you want, although not a >> > great idea >> > >> > On 7/3/07, Harish Kachoria wrote: >> >> >> >> It would be better if I can explain my problem then you can suggest me >> >> some >> >> solution >> >> >> >> Currently I have one project which has around 30+sub projects (Which I >> >> can >> >> say modules) >> >> Each sub project has its own ear which contains 1 war module and 1 ejb >> >> module. >> >> >> >> There are some common libraries also which are shared accros the >> >> projects. >> >> >> >> In development env we copy this library at local location and use them >> >> from >> >> JBuilder. >> >> >> >> In production env, many ears are deployed (this project as well as >> other >> >> projects) and all common libraries are in server lib folder. >> >> >> >> now I want to build one sub project using maven. and I need to refer >> all >> >> common libraries just for compilations (as we never include common >> >> library >> >> in EAR) >> >> >> >> To use maven I need to define dependancy and needs to copy common >> library >> >> in >> >> repo. >> >> >> >> I wants to copy all jars in one folder of repo and trying to use it >> but >> >> with >> >> Maven 2.0 it seems to be not possible. >> >> >> >> If you have any alternate way then please let me know >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11417704 >> >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> >> >> >> - >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > >> > -- >> > I could give you my word as a Spaniard. >> > No good. I've known too many Spaniards. >> > -- The Princess Bride >> > >> > - >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11418660 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > :arguing::arguing::arguing::arguing::arguing::arguing::arguing: -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11419527 Sent from the Maven - Users mailing list archive at Nabble.com.
Re: how to configure Default Repository Layout for local repository
Your only option (if you want to continue using Maven) is to starting using versions. Even if you use scope=system you still need to set a version in the node. And system scope is just a bad idea in the first place, generally. Wayne On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote: OK it works from me.. I created remote repo on my local machine. and maven downloded the jars stored them in the way he likes. still I have one problem, my libraries does not have any version number. and version number is mandatory for maven 2.0. ( tag had been removed in maven 2.0) so now I have two solution - - rename all jar with some fake version(may be 1.0) and then convince management for this. which I know won't happen - forget maven. which I don't prefer. (this was my idea to use maven in this project) so can you find any other solution. Carlos Sanchez-4 wrote: > > you can't change the local repository layout, it's a cache for maven > and it shouldn't matter how it's stored > > you can change the remote repositories layout, so just create a remote > repo for your projects in whatever style you want, although not a > great idea > > On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote: >> >> It would be better if I can explain my problem then you can suggest me >> some >> solution >> >> Currently I have one project which has around 30+sub projects (Which I >> can >> say modules) >> Each sub project has its own ear which contains 1 war module and 1 ejb >> module. >> >> There are some common libraries also which are shared accros the >> projects. >> >> In development env we copy this library at local location and use them >> from >> JBuilder. >> >> In production env, many ears are deployed (this project as well as other >> projects) and all common libraries are in server lib folder. >> >> now I want to build one sub project using maven. and I need to refer all >> common libraries just for compilations (as we never include common >> library >> in EAR) >> >> To use maven I need to define dependancy and needs to copy common library >> in >> repo. >> >> I wants to copy all jars in one folder of repo and trying to use it but >> with >> Maven 2.0 it seems to be not possible. >> >> If you have any alternate way then please let me know >> >> -- >> View this message in context: >> http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11417704 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > I could give you my word as a Spaniard. > No good. I've known too many Spaniards. > -- The Princess Bride > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11418660 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to configure Default Repository Layout for local repository
OK it works from me.. I created remote repo on my local machine. and maven downloded the jars stored them in the way he likes. still I have one problem, my libraries does not have any version number. and version number is mandatory for maven 2.0. ( tag had been removed in maven 2.0) so now I have two solution - - rename all jar with some fake version(may be 1.0) and then convince management for this. which I know won't happen - forget maven. which I don't prefer. (this was my idea to use maven in this project) so can you find any other solution. Carlos Sanchez-4 wrote: > > you can't change the local repository layout, it's a cache for maven > and it shouldn't matter how it's stored > > you can change the remote repositories layout, so just create a remote > repo for your projects in whatever style you want, although not a > great idea > > On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote: >> >> It would be better if I can explain my problem then you can suggest me >> some >> solution >> >> Currently I have one project which has around 30+sub projects (Which I >> can >> say modules) >> Each sub project has its own ear which contains 1 war module and 1 ejb >> module. >> >> There are some common libraries also which are shared accros the >> projects. >> >> In development env we copy this library at local location and use them >> from >> JBuilder. >> >> In production env, many ears are deployed (this project as well as other >> projects) and all common libraries are in server lib folder. >> >> now I want to build one sub project using maven. and I need to refer all >> common libraries just for compilations (as we never include common >> library >> in EAR) >> >> To use maven I need to define dependancy and needs to copy common library >> in >> repo. >> >> I wants to copy all jars in one folder of repo and trying to use it but >> with >> Maven 2.0 it seems to be not possible. >> >> If you have any alternate way then please let me know >> >> -- >> View this message in context: >> http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11417704 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > I could give you my word as a Spaniard. > No good. I've known too many Spaniards. > -- The Princess Bride > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11418660 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to configure Default Repository Layout for local repository
you can't change the local repository layout, it's a cache for maven and it shouldn't matter how it's stored you can change the remote repositories layout, so just create a remote repo for your projects in whatever style you want, although not a great idea On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote: It would be better if I can explain my problem then you can suggest me some solution Currently I have one project which has around 30+sub projects (Which I can say modules) Each sub project has its own ear which contains 1 war module and 1 ejb module. There are some common libraries also which are shared accros the projects. In development env we copy this library at local location and use them from JBuilder. In production env, many ears are deployed (this project as well as other projects) and all common libraries are in server lib folder. now I want to build one sub project using maven. and I need to refer all common libraries just for compilations (as we never include common library in EAR) To use maven I need to define dependancy and needs to copy common library in repo. I wants to copy all jars in one folder of repo and trying to use it but with Maven 2.0 it seems to be not possible. If you have any alternate way then please let me know -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11417704 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to configure Default Repository Layout for local repository
It would be better if I can explain my problem then you can suggest me some solution Currently I have one project which has around 30+sub projects (Which I can say modules) Each sub project has its own ear which contains 1 war module and 1 ejb module. There are some common libraries also which are shared accros the projects. In development env we copy this library at local location and use them from JBuilder. In production env, many ears are deployed (this project as well as other projects) and all common libraries are in server lib folder. now I want to build one sub project using maven. and I need to refer all common libraries just for compilations (as we never include common library in EAR) To use maven I need to define dependancy and needs to copy common library in repo. I wants to copy all jars in one folder of repo and trying to use it but with Maven 2.0 it seems to be not possible. If you have any alternate way then please let me know -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11417704 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to configure Default Repository Layout for local repository
Where will I put dependnacy jars ?? which are required in my project. In Maven 1.0 we used to put all jar in local repository. in maven 2.0 is there any differene ?? so to refer any jar I need to put some where in repository correct .. and to use that I need to define group/artifact/version Lets say I have 30 external jars in my project. so I need to create 30 folders and need to put each jar in seprate folder. In maven 1.0 we simply have one folder in repo and then we put all jars in jars folder. and maven understand dependancy using artificate name. that was more prefarable for me. I can see all jar of group in one directory. Max O Bowsher wrote: > > Harish Kachoria wrote: >> I mean to say, If I wants to use maven then I have to use in this way, I >> have >> to maintain version, but for my project maintaing of version is not a >> problem. and Management won't like Idea to have directory for each >> module. >> So if Maven is enough flexible then adoptation in any project becomes >> very >> easy. >> >> I was using maven 1.0 in my past project and was quite comfertable and >> because of this as a System designer I propose to use Maven in my current >> project. >> But with Maven 2.0 I'm trying to fit all my requirements from past 1 week >> but not suceed. >> now I'm very much frustrated. > > > The local repository is simply a cache, maintained by Maven. It's layout > should not influence your project in any way. > > Please explain why the layout of the local repository matters to you, or > is part of your requirements. > > > Max. > > > > -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11416853 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to configure Default Repository Layout for local repository
Harish Kachoria wrote: > I mean to say, If I wants to use maven then I have to use in this way, I have > to maintain version, but for my project maintaing of version is not a > problem. and Management won't like Idea to have directory for each module. > So if Maven is enough flexible then adoptation in any project becomes very > easy. > > I was using maven 1.0 in my past project and was quite comfertable and > because of this as a System designer I propose to use Maven in my current > project. > But with Maven 2.0 I'm trying to fit all my requirements from past 1 week > but not suceed. > now I'm very much frustrated. The local repository is simply a cache, maintained by Maven. It's layout should not influence your project in any way. Please explain why the layout of the local repository matters to you, or is part of your requirements. Max. signature.asc Description: OpenPGP digital signature
Re: how to configure Default Repository Layout for local repository
Ok Do you mean to say, Can I define seprate repository for all my dependant jars ?? How ?? and can I define legacy layout for this repository ?? How to confugure this on my local machine can I give repo name in my dependancy section ?? Wayne Fay wrote: > > Wait a minute... You're asking about changing the default layout of > the LOCAL (ie c:\...\.m2\repository) repository?? > > I take back everything I said before -- this is NOT possible, and > probably will NEVER be possible. (As far as I know.) If you insist on > using this old layout, you must continue using Maven1. But I really > don't know why you care how Maven "internally" handles its own local > repository. > > You can only configure the layout for "legacy" when dealing with > remote repos ie corporate repo, snapshot repo, etc. > > Wayne > > On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote: >> >> ps >> actually before posting here, I search all possible solution and tried it >> but some how not working. >> in setting.xml I can only define localRepository and It won't allow me to >> define layout. >> I tried to define layout in my pom.xml (by giving name,id as >> localRepository >> in repositries section) but maven is always reffering to default layout. >> >> So if some can paste me configuration then it would be cery help >> >> >> >> Wayne Fay wrote: >> > >> > I don't use this legacy layout myself, so no, I can't paste my setting >> > file. But if you search Google for "maven repository legacy layout" >> > you will find all the documentation you could possibly need. >> > >> > Wayne >> > >> > On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote: >> >> >> >> Thanks Wayne >> >> >> >> Can you please give me the sytax for this. I tried various systax but >> it >> >> did't worked. >> >> please paste your Setting file which contains this setting it would be >> >> very >> >> helpful >> >> >> >> >> >> >> >> Wayne Fay wrote: >> >> > >> >> > You can always access your M1 style repo with >> legacy. >> >> > And you deploy to legacy as well with "mvn deploy:deploy-file >> >> > -DrepositoryLayout=legacy". >> >> > >> >> > So if you really believe the M1 layout is better, you can keep using >> >> it. >> >> > >> >> > Wayne >> >> > >> >> > On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> I can use that command but presently I have almost more then 30 jar >> >> >> files. >> >> >> and >> >> >> First It is bad idea to run same command for all this jar. >> >> >> Second this structure will create 30 different folder in my >> repository >> >> >> which >> >> >> I think a burden to maintain. >> >> >> I like the maven 1.0 layout in which I can put all my jar (belongs >> to >> >> a >> >> >> logical group) in single folder. >> >> >> which I feel very easy to maintain. >> >> >> >> >> >> >> >> >> Thorsten Heit-3 wrote: >> >> >> > >> >> >> > Hi, >> >> >> > >> >> >> >> Default layout of maven 2.0 is a burden for me. as I have many >> jar >> >> >> with >> >> >> >> same >> >> >> >> group and if I need to use default layour of Maven 2.0 then I >> need >> >> to >> >> >> >> create >> >> >> >> seprate directory for each jar. >> >> >> >> >> >> >> >> So please help me to configure legacy layout for local >> repository. >> >> >> >> >> >> >> >> I tried to configure it but could not suceed. >> >> >> >> >> >> >> >> IT would be very help fule if you can give me pom/setting >> >> >> configuration. >> >> >> > >> >> >> > Why don't you just use "mvn deploy:deploy-file" or "mvn >> >> >> > install:install-file"? Maven automatically creates the necessary >> >> >> directory >> >> >> > structure for you. >> >> >> > >> >> >> > >> >> >> > http://maven.apache.org/plugins/maven-install-plugin/ >> >> >> > http://maven.apache.org/plugins/maven-deploy-plugin/ >> >> >> > >> http://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html >> >> >> > >> >> >> > >> >> >> > HTH >> >> >> > >> >> >> > Thorsten >> >> >> > >> >> >> > >> >> - >> >> >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> >> > For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> >> -- >> >> >> View this message in context: >> >> >> >> >> >> http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11414400 >> >> >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> >> >> - >> >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> >> >> >> > >> >> > >> - >> >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> > For additional commands, e-mail: [EMAIL PROTECTED] >> >> > >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/how-to-configure-Default-Repository-Layo
Re: how to configure Default Repository Layout for local repository
I mean to say, If I wants to use maven then I have to use in this way, I have to maintain version, but for my project maintaing of version is not a problem. and Management won't like Idea to have directory for each module. So if Maven is enough flexible then adoptation in any project becomes very easy. I was using maven 1.0 in my past project and was quite comfertable and because of this as a System designer I propose to use Maven in my current project. But with Maven 2.0 I'm trying to fit all my requirements from past 1 week but not suceed. now I'm very much frustrated. Wayne Fay wrote: > > He means "the Maven dev group is pushing a particular agenda which my > organization disagrees with." > > Wayne > > On 7/3/07, Thorsten Heit <[EMAIL PROTECTED]> wrote: >> > I don't like directory structure which is just over burden for >> maintaince. >> > As of now we do not have any problems to maintain version of our jars. >> > But because maven thinks that we have problems in maintaing versions so >> we >> > should adopt maven directory structure is stupid idea. >> >> Sorry, but I don't understand what you mean by "Maven thinks that we have >> problems...". Can you explain that? >> >> >> Regards >> >> Thorsten >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11416350 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to configure Default Repository Layout for local repository
Wait a minute... You're asking about changing the default layout of the LOCAL (ie c:\...\.m2\repository) repository?? I take back everything I said before -- this is NOT possible, and probably will NEVER be possible. (As far as I know.) If you insist on using this old layout, you must continue using Maven1. But I really don't know why you care how Maven "internally" handles its own local repository. You can only configure the layout for "legacy" when dealing with remote repos ie corporate repo, snapshot repo, etc. Wayne On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote: ps actually before posting here, I search all possible solution and tried it but some how not working. in setting.xml I can only define localRepository and It won't allow me to define layout. I tried to define layout in my pom.xml (by giving name,id as localRepository in repositries section) but maven is always reffering to default layout. So if some can paste me configuration then it would be cery help Wayne Fay wrote: > > I don't use this legacy layout myself, so no, I can't paste my setting > file. But if you search Google for "maven repository legacy layout" > you will find all the documentation you could possibly need. > > Wayne > > On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote: >> >> Thanks Wayne >> >> Can you please give me the sytax for this. I tried various systax but it >> did't worked. >> please paste your Setting file which contains this setting it would be >> very >> helpful >> >> >> >> Wayne Fay wrote: >> > >> > You can always access your M1 style repo with legacy. >> > And you deploy to legacy as well with "mvn deploy:deploy-file >> > -DrepositoryLayout=legacy". >> > >> > So if you really believe the M1 layout is better, you can keep using >> it. >> > >> > Wayne >> > >> > On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote: >> >> >> >> I can use that command but presently I have almost more then 30 jar >> >> files. >> >> and >> >> First It is bad idea to run same command for all this jar. >> >> Second this structure will create 30 different folder in my repository >> >> which >> >> I think a burden to maintain. >> >> I like the maven 1.0 layout in which I can put all my jar (belongs to >> a >> >> logical group) in single folder. >> >> which I feel very easy to maintain. >> >> >> >> >> >> Thorsten Heit-3 wrote: >> >> > >> >> > Hi, >> >> > >> >> >> Default layout of maven 2.0 is a burden for me. as I have many jar >> >> with >> >> >> same >> >> >> group and if I need to use default layour of Maven 2.0 then I need >> to >> >> >> create >> >> >> seprate directory for each jar. >> >> >> >> >> >> So please help me to configure legacy layout for local repository. >> >> >> >> >> >> I tried to configure it but could not suceed. >> >> >> >> >> >> IT would be very help fule if you can give me pom/setting >> >> configuration. >> >> > >> >> > Why don't you just use "mvn deploy:deploy-file" or "mvn >> >> > install:install-file"? Maven automatically creates the necessary >> >> directory >> >> > structure for you. >> >> > >> >> > >> >> > http://maven.apache.org/plugins/maven-install-plugin/ >> >> > http://maven.apache.org/plugins/maven-deploy-plugin/ >> >> > http://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html >> >> > >> >> > >> >> > HTH >> >> > >> >> > Thorsten >> >> > >> >> > >> - >> >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> > For additional commands, e-mail: [EMAIL PROTECTED] >> >> > >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11414400 >> >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> >> >> >> - >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > - >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11414813 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11416083 Sent from the Maven - Users mailing list archive at Nabble.co
Re: how to configure Default Repository Layout for local repository
ps actually before posting here, I search all possible solution and tried it but some how not working. in setting.xml I can only define localRepository and It won't allow me to define layout. I tried to define layout in my pom.xml (by giving name,id as localRepository in repositries section) but maven is always reffering to default layout. So if some can paste me configuration then it would be cery help Wayne Fay wrote: > > I don't use this legacy layout myself, so no, I can't paste my setting > file. But if you search Google for "maven repository legacy layout" > you will find all the documentation you could possibly need. > > Wayne > > On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote: >> >> Thanks Wayne >> >> Can you please give me the sytax for this. I tried various systax but it >> did't worked. >> please paste your Setting file which contains this setting it would be >> very >> helpful >> >> >> >> Wayne Fay wrote: >> > >> > You can always access your M1 style repo with legacy. >> > And you deploy to legacy as well with "mvn deploy:deploy-file >> > -DrepositoryLayout=legacy". >> > >> > So if you really believe the M1 layout is better, you can keep using >> it. >> > >> > Wayne >> > >> > On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote: >> >> >> >> I can use that command but presently I have almost more then 30 jar >> >> files. >> >> and >> >> First It is bad idea to run same command for all this jar. >> >> Second this structure will create 30 different folder in my repository >> >> which >> >> I think a burden to maintain. >> >> I like the maven 1.0 layout in which I can put all my jar (belongs to >> a >> >> logical group) in single folder. >> >> which I feel very easy to maintain. >> >> >> >> >> >> Thorsten Heit-3 wrote: >> >> > >> >> > Hi, >> >> > >> >> >> Default layout of maven 2.0 is a burden for me. as I have many jar >> >> with >> >> >> same >> >> >> group and if I need to use default layour of Maven 2.0 then I need >> to >> >> >> create >> >> >> seprate directory for each jar. >> >> >> >> >> >> So please help me to configure legacy layout for local repository. >> >> >> >> >> >> I tried to configure it but could not suceed. >> >> >> >> >> >> IT would be very help fule if you can give me pom/setting >> >> configuration. >> >> > >> >> > Why don't you just use "mvn deploy:deploy-file" or "mvn >> >> > install:install-file"? Maven automatically creates the necessary >> >> directory >> >> > structure for you. >> >> > >> >> > >> >> > http://maven.apache.org/plugins/maven-install-plugin/ >> >> > http://maven.apache.org/plugins/maven-deploy-plugin/ >> >> > http://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html >> >> > >> >> > >> >> > HTH >> >> > >> >> > Thorsten >> >> > >> >> > >> - >> >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> > For additional commands, e-mail: [EMAIL PROTECTED] >> >> > >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11414400 >> >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> >> >> >> - >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > - >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11414813 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11416083 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to configure Default Repository Layout for local repository
He means "the Maven dev group is pushing a particular agenda which my organization disagrees with." Wayne On 7/3/07, Thorsten Heit <[EMAIL PROTECTED]> wrote: > I don't like directory structure which is just over burden for maintaince. > As of now we do not have any problems to maintain version of our jars. > But because maven thinks that we have problems in maintaing versions so we > should adopt maven directory structure is stupid idea. Sorry, but I don't understand what you mean by "Maven thinks that we have problems...". Can you explain that? Regards Thorsten - 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: how to configure Default Repository Layout for local repository
> I don't like directory structure which is just over burden for maintaince. > As of now we do not have any problems to maintain version of our jars. > But because maven thinks that we have problems in maintaing versions so we > should adopt maven directory structure is stupid idea. Sorry, but I don't understand what you mean by "Maven thinks that we have problems...". Can you explain that? Regards Thorsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to configure Default Repository Layout for local repository
I don't use this legacy layout myself, so no, I can't paste my setting file. But if you search Google for "maven repository legacy layout" you will find all the documentation you could possibly need. Wayne On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote: Thanks Wayne Can you please give me the sytax for this. I tried various systax but it did't worked. please paste your Setting file which contains this setting it would be very helpful Wayne Fay wrote: > > You can always access your M1 style repo with legacy. > And you deploy to legacy as well with "mvn deploy:deploy-file > -DrepositoryLayout=legacy". > > So if you really believe the M1 layout is better, you can keep using it. > > Wayne > > On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote: >> >> I can use that command but presently I have almost more then 30 jar >> files. >> and >> First It is bad idea to run same command for all this jar. >> Second this structure will create 30 different folder in my repository >> which >> I think a burden to maintain. >> I like the maven 1.0 layout in which I can put all my jar (belongs to a >> logical group) in single folder. >> which I feel very easy to maintain. >> >> >> Thorsten Heit-3 wrote: >> > >> > Hi, >> > >> >> Default layout of maven 2.0 is a burden for me. as I have many jar >> with >> >> same >> >> group and if I need to use default layour of Maven 2.0 then I need to >> >> create >> >> seprate directory for each jar. >> >> >> >> So please help me to configure legacy layout for local repository. >> >> >> >> I tried to configure it but could not suceed. >> >> >> >> IT would be very help fule if you can give me pom/setting >> configuration. >> > >> > Why don't you just use "mvn deploy:deploy-file" or "mvn >> > install:install-file"? Maven automatically creates the necessary >> directory >> > structure for you. >> > >> > >> > http://maven.apache.org/plugins/maven-install-plugin/ >> > http://maven.apache.org/plugins/maven-deploy-plugin/ >> > http://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html >> > >> > >> > HTH >> > >> > Thorsten >> > >> > - >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11414400 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11414813 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to configure Default Repository Layout for local repository
Thanks Wayne Can you please give me the sytax for this. I tried various systax but it did't worked. please paste your Setting file which contains this setting it would be very helpful Wayne Fay wrote: > > You can always access your M1 style repo with legacy. > And you deploy to legacy as well with "mvn deploy:deploy-file > -DrepositoryLayout=legacy". > > So if you really believe the M1 layout is better, you can keep using it. > > Wayne > > On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote: >> >> I can use that command but presently I have almost more then 30 jar >> files. >> and >> First It is bad idea to run same command for all this jar. >> Second this structure will create 30 different folder in my repository >> which >> I think a burden to maintain. >> I like the maven 1.0 layout in which I can put all my jar (belongs to a >> logical group) in single folder. >> which I feel very easy to maintain. >> >> >> Thorsten Heit-3 wrote: >> > >> > Hi, >> > >> >> Default layout of maven 2.0 is a burden for me. as I have many jar >> with >> >> same >> >> group and if I need to use default layour of Maven 2.0 then I need to >> >> create >> >> seprate directory for each jar. >> >> >> >> So please help me to configure legacy layout for local repository. >> >> >> >> I tried to configure it but could not suceed. >> >> >> >> IT would be very help fule if you can give me pom/setting >> configuration. >> > >> > Why don't you just use "mvn deploy:deploy-file" or "mvn >> > install:install-file"? Maven automatically creates the necessary >> directory >> > structure for you. >> > >> > >> > http://maven.apache.org/plugins/maven-install-plugin/ >> > http://maven.apache.org/plugins/maven-deploy-plugin/ >> > http://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html >> > >> > >> > HTH >> > >> > Thorsten >> > >> > - >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11414400 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11414813 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to configure Default Repository Layout for local repository
Thanks, But still is there any way in maven 2.0 by which I can put all jar of a group at one place. (not in different different directory) I don't like directory structure which is just over burden for maintaince. As of now we do not have any problems to maintain version of our jars. But because maven thinks that we have problems in maintaing versions so we should adopt maven directory structure is stupid idea. Thorsten Heit-3 wrote: > >> I can use that command but presently I have almost more then 30 jar >> files. > > If you don't want to do this by hand, let a short shell script do this for > you, so what? > > for i in *.jar; do > file=`'echo $i | sed -e 's:\.jar::g'` > mvn deploy:deploy-file -DgroupId= -DartifactId=$file > -Dpackaging=jar -Dfile=$i ... > done > > >> and >> First It is bad idea to run same command for all this jar. >> Second this structure will create 30 different folder in my repository >> which >> I think a burden to maintain. > > Erm, just for curiosity: What do you mean by maintaining a folder that is > accessed by Maven? Normally you just let Maven put stuff into its > repository, and that's it. There's no need for manually interaction... > > >> I like the maven 1.0 layout in which I can put all my jar (belongs to a >> logical group) in single folder. >> which I feel very easy to maintain. > > See above: What do you want to do manually in such a folder instead of > letting Maven manage it? > > > Cheers > > Thorsten > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11414810 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to configure Default Repository Layout for local repository
You can always access your M1 style repo with legacy. And you deploy to legacy as well with "mvn deploy:deploy-file -DrepositoryLayout=legacy". So if you really believe the M1 layout is better, you can keep using it. Wayne On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote: I can use that command but presently I have almost more then 30 jar files. and First It is bad idea to run same command for all this jar. Second this structure will create 30 different folder in my repository which I think a burden to maintain. I like the maven 1.0 layout in which I can put all my jar (belongs to a logical group) in single folder. which I feel very easy to maintain. Thorsten Heit-3 wrote: > > Hi, > >> Default layout of maven 2.0 is a burden for me. as I have many jar with >> same >> group and if I need to use default layour of Maven 2.0 then I need to >> create >> seprate directory for each jar. >> >> So please help me to configure legacy layout for local repository. >> >> I tried to configure it but could not suceed. >> >> IT would be very help fule if you can give me pom/setting configuration. > > Why don't you just use "mvn deploy:deploy-file" or "mvn > install:install-file"? Maven automatically creates the necessary directory > structure for you. > > > http://maven.apache.org/plugins/maven-install-plugin/ > http://maven.apache.org/plugins/maven-deploy-plugin/ > http://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html > > > HTH > > Thorsten > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11414400 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to configure Default Repository Layout for local repository
> I can use that command but presently I have almost more then 30 jar files. If you don't want to do this by hand, let a short shell script do this for you, so what? for i in *.jar; do file=`'echo $i | sed -e 's:\.jar::g'` mvn deploy:deploy-file -DgroupId= -DartifactId=$file -Dpackaging=jar -Dfile=$i ... done > and > First It is bad idea to run same command for all this jar. > Second this structure will create 30 different folder in my repository > which > I think a burden to maintain. Erm, just for curiosity: What do you mean by maintaining a folder that is accessed by Maven? Normally you just let Maven put stuff into its repository, and that's it. There's no need for manually interaction... > I like the maven 1.0 layout in which I can put all my jar (belongs to a > logical group) in single folder. > which I feel very easy to maintain. See above: What do you want to do manually in such a folder instead of letting Maven manage it? Cheers Thorsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to configure Default Repository Layout for local repository
I can use that command but presently I have almost more then 30 jar files. and First It is bad idea to run same command for all this jar. Second this structure will create 30 different folder in my repository which I think a burden to maintain. I like the maven 1.0 layout in which I can put all my jar (belongs to a logical group) in single folder. which I feel very easy to maintain. Thorsten Heit-3 wrote: > > Hi, > >> Default layout of maven 2.0 is a burden for me. as I have many jar with >> same >> group and if I need to use default layour of Maven 2.0 then I need to >> create >> seprate directory for each jar. >> >> So please help me to configure legacy layout for local repository. >> >> I tried to configure it but could not suceed. >> >> IT would be very help fule if you can give me pom/setting configuration. > > Why don't you just use "mvn deploy:deploy-file" or "mvn > install:install-file"? Maven automatically creates the necessary directory > structure for you. > > > http://maven.apache.org/plugins/maven-install-plugin/ > http://maven.apache.org/plugins/maven-deploy-plugin/ > http://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html > > > HTH > > Thorsten > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11414400 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to configure Default Repository Layout for local repository
Hi, > Default layout of maven 2.0 is a burden for me. as I have many jar with > same > group and if I need to use default layour of Maven 2.0 then I need to > create > seprate directory for each jar. > > So please help me to configure legacy layout for local repository. > > I tried to configure it but could not suceed. > > IT would be very help fule if you can give me pom/setting configuration. Why don't you just use "mvn deploy:deploy-file" or "mvn install:install-file"? Maven automatically creates the necessary directory structure for you. http://maven.apache.org/plugins/maven-install-plugin/ http://maven.apache.org/plugins/maven-deploy-plugin/ http://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html HTH Thorsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
