Re: Snapshot repository
To add to my confusion in this thread, there's the element that has a and element. I'm really confused! lightbulb432 wrote: > > I added a snapshotRepository element in addition to the repository element > in the distributionManagement section of my pom.xml. However, when I run > the install phase the WAR is only output to the repository, not the > snapshot repository, even when I change the version name to end in > "-SNAPSHOT". > > How can I get the WAR to go to the appropriate place? > > Also, as I'm a beginner I don't know what is expected behavior - would the > WAR go to both repositories, or only one? If it's only one, is the chosen > repository to which the WAR is installed what the "-SNAPSHOT" serves to > indicate? > > Thanks. > > > > Wayne Fay wrote: >> >> Generally people don't like to mix SNAPSHOT artifacts with released >> artifacts. So the Snapshot repo and version number stuff just helps >> organize/manage that. >> >> You can *do* whatever you want -- its just not necessarily a "build >> management best practice". I just would advise you to think long and hard >> about what you're about to do before doing it, though. >> >> Wayne >> >> On 5/7/07, lightbulb432 <[EMAIL PROTECTED]> wrote: >>> >>> What's the difference between a regular repository and a snapshot >>> repository >>> as specified under distributionManagement? I've tried using both types, >>> but >>> I didn't see any difference... >>> >>> Also, does ending the version number of a file in SNAPSHOT have >>> something to >>> do with this? >>> >>> Is it okay to end a version number with SNAPSHOT in a regular >>> repository, or >>> end without SNAPSHOT in a snapshot repository...? >>> >>> Thanks. >>> -- >>> View this message in context: >>> http://www.nabble.com/Snapshot-repository-tf3706438s177.html#a10366009 >>> 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/Snapshot-repository-tf3706438s177.html#a10421687 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: Snapshot repository
I added a snapshotRepository element in addition to the repository element in the distributionManagement section of my pom.xml. However, when I run the install phase the WAR is only output to the repository, not the snapshot repository, even when I change the version name to end in "-SNAPSHOT". How can I get the WAR to go to the appropriate place? Also, as I'm a beginner I don't know what is expected behavior - would the WAR go to both repositories, or only one? If it's only one, is the chosen repository to which the WAR is installed what the "-SNAPSHOT" serves to indicate? Thanks. Wayne Fay wrote: > > Generally people don't like to mix SNAPSHOT artifacts with released > artifacts. So the Snapshot repo and version number stuff just helps > organize/manage that. > > You can *do* whatever you want -- its just not necessarily a "build > management best practice". I just would advise you to think long and hard > about what you're about to do before doing it, though. > > Wayne > > On 5/7/07, lightbulb432 <[EMAIL PROTECTED]> wrote: >> >> What's the difference between a regular repository and a snapshot >> repository >> as specified under distributionManagement? I've tried using both types, >> but >> I didn't see any difference... >> >> Also, does ending the version number of a file in SNAPSHOT have something >> to >> do with this? >> >> Is it okay to end a version number with SNAPSHOT in a regular repository, >> or >> end without SNAPSHOT in a snapshot repository...? >> >> Thanks. >> -- >> View this message in context: >> http://www.nabble.com/Snapshot-repository-tf3706438s177.html#a10366009 >> 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/Snapshot-repository-tf3706438s177.html#a10398347 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: Snapshot repository
lightbulb432 wrote: Also, does ending the version number of a file in SNAPSHOT have something to do with this? Reading this, I don't think you know what a SNAPSHOT version means. A SNAPSHOT is every build between two released versions. This way, you can never be sure, that a new SNAPSHOT of a dependency or a plugin wouldn't break your build. (Normally a bad thing) Also, every SNAPSHOT build you deploy is put into the repository. (Snapshot repository). After a release, you can remove all the old SNAPSHOT versions. When separating SNAPSHOT builds and releases in different repositories, it is easier to keep watch on them. Hth, Nick Stolwijk Is it okay to end a version number with SNAPSHOT in a regular repository, or end without SNAPSHOT in a snapshot repository...? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Snapshot repository
Generally people don't like to mix SNAPSHOT artifacts with released artifacts. So the Snapshot repo and version number stuff just helps organize/manage that. You can *do* whatever you want -- its just not necessarily a "build management best practice". I just would advise you to think long and hard about what you're about to do before doing it, though. Wayne On 5/7/07, lightbulb432 <[EMAIL PROTECTED]> wrote: What's the difference between a regular repository and a snapshot repository as specified under distributionManagement? I've tried using both types, but I didn't see any difference... Also, does ending the version number of a file in SNAPSHOT have something to do with this? Is it okay to end a version number with SNAPSHOT in a regular repository, or end without SNAPSHOT in a snapshot repository...? Thanks. -- View this message in context: http://www.nabble.com/Snapshot-repository-tf3706438s177.html#a10366009 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: Snapshot Repository
We looked at the same problem, but decided on an entirely different solution. We don't have developers upload their snapshots to the central repository. We setup CruiseControl to run an hourly build of each project (if changes happened) on the same machine as the central Maven repository. The central build runs 'maven jar:install-snapshot' and then all developers use either the snapshot from their machine (if it's more recent), or the central snapshot. At most, developers wait an hour for a new snapshot. If we need it more quickly, we force a build through CC's web JMX interface, and the snapshot's available immediately. That way developers never upload to the central server, and when a release comes arouns then an admin can do that. --Tim On Mon, 12 Jul 2004 19:29:34 -0400, Paul Spencer <[EMAIL PROTECTED]> wrote: > I can think of two solutions: > 1) Have 2 repositories. One for snapshots and one for releases. A > project's configuration files, (project.xml, project.properties, and > build.properties) to write to the snapshot directory. The release > process would involve changing the configuration to write to the release > repository. >maven.repo.remote = http://www.foo.com/snapshot, >http://www.foo.com/release, >http://www.ibiblio.org/maven > > 2) Make the release version readonly in the repository. This will > prevent the file from being overwritten. > > Paul Spencer > > > > > Amato Massimiliano (UBM) wrote: > > Hello, > > > > We are in the process of setting up a remote repository for our group and we have > > a problem, we want to allow developers to upload snapshot release to the central > > repository but we want not to allow them to upload final release. This is due to > > the fact that we have a central configuration for maven and it could happen that a > > developer could ovverride by mistake a release with a wrong one. > > > > Basically we would like to have 2 separate directories, one for the final release > > where only the administrator can write and another one public where all the > > developers can upload their snapshot. I don't think this is supported right now in > > Maven but i'd like to know if anyone had ever thought about it since i think it > > could be a common problem. Any idea if this will be implemented in the future > > releases? > > > > Also since we need to make it work any suggestion on how we could do it? We were > > thinking about rewriting the artifact plugin in order to change the directory if > > the version is a snapshot > > > > Thanks for your help > > Max > > > > > > > >>Massimiliano Amato > >>Risk Technologies > >>UniCredit Banca Mobiliare - www.ubm.it > >>Via Tommaso Grossi, 10 > >>20121 Milano MI > >>tel. +39 02 88628093 - fax +39 02 72929309 > >> > >>The information in this email and in any attachments is confidential and intended > >>solely for the attention and use of the named addressee(s). This information may > >>be subject to legal professional or other privilege or may otherwise be protected > >>by work product immunity or other legal rules. It must not be disclosed to any > >>person without our authority. If you are not the intended recipient, or a person > >>responsible for delivering it to the intended recipient, you are not authorized to > >>and must not disclose, copy, distribute, or retain this message or any part of it. > >> > >> > > > > > > - > > 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: Snapshot Repository
Both of Paul's suggestions are good. I think (1) gives you a better level of control though: - they might end up on different machines. - you can clean out snapshot builds and keep releases (not really a good idea but some like to do it) - much tighter access controls Cheers, Brett On Mon, 12 Jul 2004 19:29:34 -0400, Paul Spencer <[EMAIL PROTECTED]> wrote: > I can think of two solutions: > 1) Have 2 repositories. One for snapshots and one for releases. A > project's configuration files, (project.xml, project.properties, and > build.properties) to write to the snapshot directory. The release > process would involve changing the configuration to write to the release > repository. >maven.repo.remote = http://www.foo.com/snapshot, >http://www.foo.com/release, >http://www.ibiblio.org/maven > > 2) Make the release version readonly in the repository. This will > prevent the file from being overwritten. > > Paul Spencer > > > > > Amato Massimiliano (UBM) wrote: > > Hello, > > > > We are in the process of setting up a remote repository for our group and we have > > a problem, we want to allow developers to upload snapshot release to the central > > repository but we want not to allow them to upload final release. This is due to > > the fact that we have a central configuration for maven and it could happen that a > > developer could ovverride by mistake a release with a wrong one. > > > > Basically we would like to have 2 separate directories, one for the final release > > where only the administrator can write and another one public where all the > > developers can upload their snapshot. I don't think this is supported right now in > > Maven but i'd like to know if anyone had ever thought about it since i think it > > could be a common problem. Any idea if this will be implemented in the future > > releases? > > > > Also since we need to make it work any suggestion on how we could do it? We were > > thinking about rewriting the artifact plugin in order to change the directory if > > the version is a snapshot > > > > Thanks for your help > > Max > > > > > > > >>Massimiliano Amato > >>Risk Technologies > >>UniCredit Banca Mobiliare - www.ubm.it > >>Via Tommaso Grossi, 10 > >>20121 Milano MI > >>tel. +39 02 88628093 - fax +39 02 72929309 > >> > >>The information in this email and in any attachments is confidential and intended > >>solely for the attention and use of the named addressee(s). This information may > >>be subject to legal professional or other privilege or may otherwise be protected > >>by work product immunity or other legal rules. It must not be disclosed to any > >>person without our authority. If you are not the intended recipient, or a person > >>responsible for delivering it to the intended recipient, you are not authorized to > >>and must not disclose, copy, distribute, or retain this message or any part of it. > >> > >> > > > > > > - > > 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: Snapshot Repository
I can think of two solutions: 1) Have 2 repositories. One for snapshots and one for releases. A project's configuration files, (project.xml, project.properties, and build.properties) to write to the snapshot directory. The release process would involve changing the configuration to write to the release repository. maven.repo.remote = http://www.foo.com/snapshot, http://www.foo.com/release, http://www.ibiblio.org/maven 2) Make the release version readonly in the repository. This will prevent the file from being overwritten. Paul Spencer Amato Massimiliano (UBM) wrote: Hello, We are in the process of setting up a remote repository for our group and we have a problem, we want to allow developers to upload snapshot release to the central repository but we want not to allow them to upload final release. This is due to the fact that we have a central configuration for maven and it could happen that a developer could ovverride by mistake a release with a wrong one. Basically we would like to have 2 separate directories, one for the final release where only the administrator can write and another one public where all the developers can upload their snapshot. I don't think this is supported right now in Maven but i'd like to know if anyone had ever thought about it since i think it could be a common problem. Any idea if this will be implemented in the future releases? Also since we need to make it work any suggestion on how we could do it? We were thinking about rewriting the artifact plugin in order to change the directory if the version is a snapshot Thanks for your help Max Massimiliano Amato Risk Technologies UniCredit Banca Mobiliare - www.ubm.it Via Tommaso Grossi, 10 20121 Milano MI tel. +39 02 88628093 - fax +39 02 72929309 The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s). This information may be subject to legal professional or other privilege or may otherwise be protected by work product immunity or other legal rules. It must not be disclosed to any person without our authority. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are not authorized to and must not disclose, copy, distribute, or retain this message or any part of it. - 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]
