Re: RE: Is there a way to separate maven's repository from my reposit ory?
If you cannot turn it off, maybe you can clear it with a pre-Goal for the clean goal. The compile would then repopulate it from all known repositories (meaning all repos you have specified). Maybe you should automate the building process and use cruisecontrol so that the repository of the developer doesn't matter, since only the repo of the CruiseControl users does... Hope my suggestions help... Regards Per Abich On Thu, 26 Aug 2004 13:40:37 -0500, Jarrell, Maury [EMAIL PROTECTED] wrote: -Original Message- From: Courtney, Craig [mailto:[EMAIL PROTECTED] Sent: Thursday, August 26, 2004 10:32 AM To: Maven Users List Subject: RE: Is there a way to separate maven's repository from my reposit ory? It is prudent to pay attention to this for internal only software as well. Good advice. How do you disable the local repository? Not sure. More knowledgeable folks than me have already said there really isn't one. I just ran a dist:build on my project and no libraries were included in the zip or tar.gz files. I think one might be able to write a postGoal for dist:build that jar'd the libraries referenced in your project.xml. Maybe then a separate remote repository wouldn't even have to be created. I also just commented out a dependency in my project.xml and tried to re-run a clean then a dist:build. The dist:build failed due to that dependency. The means that the classpath for compilation, unit tests, etc are based on the project.xml and not on everything that resides in the repository. It would seem that control over the dependencies in the project.xml = total control over the libraries used for your build. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Per Abich Praktikant Catenic AG - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Is there a way to separate maven's repository from my reposit ory?
-Original Message- From: Courtney, Craig [mailto:[EMAIL PROTECTED] Sent: Thursday, August 26, 2004 9:46 AM To: Maven Users List Subject: RE: Is there a way to separate maven's repository from my repository? That's exactly what I want. I want maven to be able to download what it needs... but it's repository for execution of the tool should be different than the repository I use for my builds. Doesn't seem to be a way to do this. Craig Hi, Craig, Doesn't Maven's use imply certification of the libraries it uses? In other words, why would you approve Maven's use, and thus its dependencies, and not certify those dependencies for use in other ways? I am very new to Maven and may not understand your issue at all, but I run Maven on a server with no internet access. I, somewhat tediously, downloaded all the jars Maven needed to a local repository and then manually added dependencies from my project. If my organization dictated that there was to be only one repository, then the only way for any other developer to add a library would be to go through whatever process we set up to get one manually added. Thoughts? Maury - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Is there a way to separate maven's repository from my reposit ory?
Because the code I'm writing is internal and proprietary in nature. Using maven to build it generates no licensing obligations on my code. Linking against any of the libraries that maven uses does generate licensing obligations on my code. We are looking at setting up an interanl repository where all of our shared libraries will reside. This will allow us control and tracking over licensing. It would be against company policy to use any libraries outside our central repository while writing your code. The build tool should have no requirements about what's in my repository it should only be about what my code needs. Craig -Original Message- From: Jarrell, Maury [mailto:[EMAIL PROTECTED] Sent: Thursday, August 26, 2004 10:55 AM To: 'Maven Users List' Subject: RE: Is there a way to separate maven's repository from my reposit ory? Hi, Craig, Doesn't Maven's use imply certification of the libraries it uses? In other words, why would you approve Maven's use, and thus its dependencies, and not certify those dependencies for use in other ways? I am very new to Maven and may not understand your issue at all, but I run Maven on a server with no internet access. I, somewhat tediously, downloaded all the jars Maven needed to a local repository and then manually added dependencies from my project. If my organization dictated that there was to be only one repository, then the only way for any other developer to add a library would be to go through whatever process we set up to get one manually added. Thoughts? Maury - 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: Is there a way to separate maven's repository from my reposit ory?
-Original Message- From: Courtney, Craig [mailto:[EMAIL PROTECTED] Sent: Thursday, August 26, 2004 10:02 AM To: Maven Users List Subject: RE: Is there a way to separate maven's repository from my reposit ory? Because the code I'm writing is internal and proprietary in nature. Using maven to build it generates no licensing obligations on my code. Linking against any of the libraries that maven uses does generate licensing obligations on my code. Doh! That makes sense. Our organization doesn't distribute software, thus we don't worry as much about such issues. We are looking at setting up an interanl repository where all of our shared libraries will reside. This will allow us control and tracking over licensing. It would be against company policy to use any libraries outside our central repository while writing your code. The build tool should have no requirements about what's in my repository it should only be about what my code needs. It sounds like you might already be doing this, or have already determined this wouldn't work, but if you used the maven.repo.local property to point to maven's build repository and maven.repo.remote to point to an internal repository that housed only libraries you use and can successfully license, then wouldn't solve most of the issue? I guess it would still be possible for a developer to use a Maven dependency, but his folly would get exposed when you only allowed the remote jars to be included in a distribution. Take care, Maury - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Is there a way to separate maven's repository from my reposit ory?
Doh! That makes sense. Our organization doesn't distribute software, thus we don't worry as much about such issues. It is prudent to pay attention to this for internal only software as well. It sounds like you might already be doing this, or have already determined this wouldn't work, but if you used the maven.repo.local property to point to maven's build repository and maven.repo.remote to point to an internal repository that housed only libraries you use and can successfully license, then wouldn't solve most of the issue? I guess it would still be possible for a developer to use a Maven dependency, but his folly would get exposed when you only allowed the remote jars to be included in a distribution. How do you disable the local repository? Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Is there a way to separate maven's repository from my reposit ory?
-Original Message- From: Courtney, Craig [mailto:[EMAIL PROTECTED] Sent: Thursday, August 26, 2004 10:32 AM To: Maven Users List Subject: RE: Is there a way to separate maven's repository from my reposit ory? It is prudent to pay attention to this for internal only software as well. Good advice. How do you disable the local repository? Not sure. More knowledgeable folks than me have already said there really isn't one. I just ran a dist:build on my project and no libraries were included in the zip or tar.gz files. I think one might be able to write a postGoal for dist:build that jar'd the libraries referenced in your project.xml. Maybe then a separate remote repository wouldn't even have to be created. I also just commented out a dependency in my project.xml and tried to re-run a clean then a dist:build. The dist:build failed due to that dependency. The means that the classpath for compilation, unit tests, etc are based on the project.xml and not on everything that resides in the repository. It would seem that control over the dependencies in the project.xml = total control over the libraries used for your build. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
