Continuum using Clearcase
Hi, We are using clearcase and on the (test)buildserver we already have a view present. We only want Continuum to: * do an update * check if there are changes (only for daily builds, a nightly build should always be build) * do a build But now it wants to create a view and check stuff out. Is there a configurable way to disable/change this? We are in the progress of testing 1.0.3 and the latest alpha release and are using Maven 2. Here is the (untested) scm-part of the top-level pom.xml scm:clearcase::load // Kind regards / Met vriendelijke groeten, Maarten Roosendaal / Capgemini / Netherlands Senior Consultant / Java Assembly Line / ADC Technologies T. +31 30 68 970 77 / Mob. +31 6 248 216 12 www.nl.capgemini.com Join the Collaborative Business Experience This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: admin account locked
If you have not yet found it.. here it is: (one of the ways) http://www.nabble.com/Change-a-user-role-to-build-admin-tf3136881.html#a8692812 Anoop On 7/19/07, Wayne Fay <[EMAIL PROTECTED]> wrote: This has been asked (and answered) several times on this list. Search the list archives at Nabble.com -- you're bound to find a few hits. And I'd assume its probably documented in the Continuum wiki as well. Wayne On 7/19/07, BDM <[EMAIL PROTECTED]> wrote: > hello, > I locked my admin account by typing to many times the wrong password (I > have checked later that it was the good one ... strange) !!! But now > how can I unlock this main account > > > Thx !! >
Re: admin account locked
This has been asked (and answered) several times on this list. Search the list archives at Nabble.com -- you're bound to find a few hits. And I'd assume its probably documented in the Continuum wiki as well. Wayne On 7/19/07, BDM <[EMAIL PROTECTED]> wrote: hello, I locked my admin account by typing to many times the wrong password (I have checked later that it was the good one ... strange) !!! But now how can I unlock this main account Thx !!
admin account locked
hello, I locked my admin account by typing to many times the wrong password (I have checked later that it was the good one ... strange) !!! But now how can I unlock this main account Thx !!
Multi-level project directories hierarchy
Hi all I am thinking about such a problem: I add a multi-level project to Continuum by choosing path to main (root) project pom.xml file on the svn. Continuum automatically adds all subprojects of the main project. I would like to build any of the subproject individually, but Continuum destroys the hierarchy of the projects and the parent project is no longer parent for any of the subproject. This cause such an annoying problem: Few of the subprojects point on the file (build.properties), which is global to the whole project and is stored in one of the parent project's directories. But in Continuum all projects are in separate directories named with numbers. This heads to the error: Error loading property file '/opt/xxx/continuum-working-directory/74/../src/filters/build.properties' I changed the arguments of the root project (deleted --non-recursive) and then it's quite fine, but I would like to build single subproject without compiling the whole, global project. Imagine that the global project is compiling let's say 10 minutes and you only want to check if you small package is done wright (which compiles in few seconds) Thanks in advance for any help. -- View this message in context: http://www.nabble.com/Multi-level-project-directories-hierarchy-tf4111727.html#a11691175 Sent from the Continuum - Users mailing list archive at Nabble.com.
RE: Unable to sync from Perforce if Continuum is run as a service
I did try both ways - 1. using Local System account 2. by selecting the other option and changing the login to my account by supplying the user name and password so that the service runs under my account It gives the same error either ways. What do you mean by environment variable / right differences ? My environment variables look fine, i guess the only one it looks for is MAVEN_HOME and JAVA_HOME, which is set in the System variables in my case. Could it have something to do with perforce? Regards, Anshula John Coleman-6 wrote: > > If your Windows service runs under a different profile, then maybe there > could be environment variables and rights differences? > > I have Continuum 1.0.3 running fine as a service using Local System > Account. > > John Coleman, MSTA > Senior Developer Consultant > > Eurobase Banking Solutions > Bury House, 31 Bury Street, > London EC3A 5AG, U.K. > > Office: +44 (0)1245 496 706, Fax: +44 (0)20 7626 6203 > Mobile: +44 (0)7734 506586 > > -Original Message- > From: Anshula [mailto:[EMAIL PROTECTED] > Sent: 19 July 2007 14:51 > To: continuum-users@maven.apache.org > Subject: Unable to sync from Perforce if Continuum is run as a service > > > Hi, > > I have been trying to setup a build system using continuum for our > projects. > I have a Maven2 project(with modules) and the SCM is Perforce. > > Initially, I started continuum from the command line using the batch > file > "bin\windows-x86-32\run.bat". I was able to add the project successfully > from the UI and build it as well. > > After that I tried to setup Continuum as a service using the script > "bin\windows-x86-32\InstallService.bat". Again I tried to build the same > project again. But it refuses to build. Following is the part of error > trace > - > > > --- > INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,333 > [pool-1-thread-1] INFO ScmManager:default - Executing: p4 > -d > C:\Try\project\254 -p hydrogen:1666 -u username client -i > INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,396 > [pool-1-thread-1] WARN ContinuumScm:default - Error while > checking out the code for project: 'project-trial', id: '254' to > 'C:\Try\project\254'. > INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,396 > [pool-1-thread-1] WARN ContinuumScm:default - Command output: > > INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,396 > [pool-1-thread-1] WARN ContinuumScm:default - Provider > message: > Unable to sync. Are you logged in? > INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,396 > [pool-1-thread-1] INFO BuildController:default- Merging SCM > results > INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,412 > [pool-1-thread-1] INFO BuildController:default- Error updating > from > SCM, not building > > --- > > The version of Continuum that I am using is "continuum-1.1-alpha-2" and > the > maven version is 2.0.5. > > > Also, here is the SCM Section of my parent POM (if needed) - > > --- > > scm:perforce:[EMAIL PROTECTED]:1666://Java-Development/pro > ject-trial > scm:perforce:[EMAIL PROTECTED]:1666://Java-Develo > pment/project-trial > > .. > > > > > org.apache.maven.plugins > maven-scm-plugin > 1.0 > > > developerConnection >username >password > > > > > > --- > > What possibly can be wrong? The same configration works fine while > Continuum > is in command line mode? > > Thanks, > Anshula > -- > View this message in context: > http://www.nabble.com/Unable-to-sync-from-Perforce-if-Continuum-is-run-a > s-a-service-tf4111233.html#a11689772 > Sent from the Continuum - Users mailing list archive at Nabble.com. > > > Eurobase International Limited and its subsidiaries (Eurobase) are unable > to exercise control over the content of information in E-Mails. Any views > and opinions expressed may be personal to the sender and are not > necessarily those of Eurobase. Eurobase will not enter into any > contractual obligations in respect of any part of its business in any > E-mail. > > Privileged / confidential information may be contained in this message and > /or any attachments. This E-mail is intended for the use of the > addressee(s) only and may contain confidential information. If you are no
RE: Unable to sync from Perforce if Continuum is run as a service
If your Windows service runs under a different profile, then maybe there could be environment variables and rights differences? I have Continuum 1.0.3 running fine as a service using Local System Account. John Coleman, MSTA Senior Developer Consultant Eurobase Banking Solutions Bury House, 31 Bury Street, London EC3A 5AG, U.K. Office: +44 (0)1245 496 706, Fax: +44 (0)20 7626 6203 Mobile: +44 (0)7734 506586 -Original Message- From: Anshula [mailto:[EMAIL PROTECTED] Sent: 19 July 2007 14:51 To: continuum-users@maven.apache.org Subject: Unable to sync from Perforce if Continuum is run as a service Hi, I have been trying to setup a build system using continuum for our projects. I have a Maven2 project(with modules) and the SCM is Perforce. Initially, I started continuum from the command line using the batch file "bin\windows-x86-32\run.bat". I was able to add the project successfully from the UI and build it as well. After that I tried to setup Continuum as a service using the script "bin\windows-x86-32\InstallService.bat". Again I tried to build the same project again. But it refuses to build. Following is the part of error trace - --- INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,333 [pool-1-thread-1] INFO ScmManager:default - Executing: p4 -d C:\Try\project\254 -p hydrogen:1666 -u username client -i INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,396 [pool-1-thread-1] WARN ContinuumScm:default - Error while checking out the code for project: 'project-trial', id: '254' to 'C:\Try\project\254'. INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,396 [pool-1-thread-1] WARN ContinuumScm:default - Command output: INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,396 [pool-1-thread-1] WARN ContinuumScm:default - Provider message: Unable to sync. Are you logged in? INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,396 [pool-1-thread-1] INFO BuildController:default- Merging SCM results INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,412 [pool-1-thread-1] INFO BuildController:default- Error updating from SCM, not building --- The version of Continuum that I am using is "continuum-1.1-alpha-2" and the maven version is 2.0.5. Also, here is the SCM Section of my parent POM (if needed) - --- scm:perforce:[EMAIL PROTECTED]:1666://Java-Development/pro ject-trial scm:perforce:[EMAIL PROTECTED]:1666://Java-Develo pment/project-trial .. org.apache.maven.plugins maven-scm-plugin 1.0 developerConnection username password --- What possibly can be wrong? The same configration works fine while Continuum is in command line mode? Thanks, Anshula -- View this message in context: http://www.nabble.com/Unable-to-sync-from-Perforce-if-Continuum-is-run-a s-a-service-tf4111233.html#a11689772 Sent from the Continuum - Users mailing list archive at Nabble.com. Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; reg
Re: Continuum file url to pom.xml
Try this - file:///C://project/pom.xml The file protocol always starts with file:/// And in the file path, the separator should be / Regards, Anshula Roosendaal, Maarten wrote: > > > Hi, > > We are trying to add a Maven 2(.0.7) project to Continuum (1.0.3). The > pom.xml is part of a clearcase view so we have > to fill in the M2 POM Url. Unfortunatly whatever we try it does not work: > * file://localhost/c://project/pom.xml > * file://c://project/pom.xml > * file://localhost/c:\\project\pom.xml > and then some. > > We've also tried following the instructions on: > http://maven.apache.org/continuum/faqs.html#can-i-use-file-protocol-in-add-project-view > > but the specified folder is not there. I added it and changed all the > application.xml's but with no luck > > We keep getting the message:[ You must provide a valid url (http, https, > ftp and file protocols are allowed) ] > > Is this a bug or are we doing something wrong? There is a clearcase view > already present there. > > Thanks, > > > > Kind regards / Met vriendelijke groeten, > Maarten Roosendaal / Capgemini / Netherlands > Senior Consultant / Java Assembly Line / ADC Technologies > T. +31 30 68 970 77 / Mob. +31 6 248 216 12 > www.nl.capgemini.com > Join the Collaborative Business Experience > > > This message contains information that may be privileged or confidential > and is the property of the Capgemini Group. It is intended only for the > person to whom it is addressed. If you are not the intended recipient, > you are not authorized to read, print, retain, copy, disseminate, > distribute, or use this message or any part thereof. If you receive this > message in error, please notify the sender immediately and delete all > copies of this message. > > -- View this message in context: http://www.nabble.com/Continuum-file-url-to-pom.xml-tf4110435.html#a11689819 Sent from the Continuum - Users mailing list archive at Nabble.com.
RE: Continuum file url to pom.xml
Hi, No luck there, no matter what i enter it always gives the same 'error'. I would like to know if anyone else has used this before? Kind regards / Met vriendelijke groeten, Maarten Roosendaal / Capgemini / Netherlands Senior Consultant / Java Assembly Line / ADC Technologies T. +31 30 68 970 77 / Mob. +31 6 248 216 12 www.nl.capgemini.com Join the Collaborative Business Experience From: Artamonov, Juri [mailto:[EMAIL PROTECTED] Sent: Thu 7/19/2007 14:50 To: continuum-users@maven.apache.org Subject: RE: Continuum file url to pom.xml Try this one: file:/c://project/pom.xml -Original Message- From: Roosendaal, Maarten [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 3:37 PM To: continuum-users@maven.apache.org Subject: Continuum file url to pom.xml Hi, We are trying to add a Maven 2(.0.7) project to Continuum (1.0.3). The pom.xml is part of a clearcase view so we have to fill in the M2 POM Url. Unfortunatly whatever we try it does not work: * file://localhost/c://project/pom.xml * file://c:/ /project/pom.xml * file://localhost/c:\ \project\pom.xml and then some. We've also tried following the instructions on: http://maven.apache.org/continuum/faqs.html#can-i-use-file-protocol-in-a dd-project-view but the specified folder is not there. I added it and changed all the application.xml's but with no luck We keep getting the message:[ You must provide a valid url (http, https, ftp and file protocols are allowed) ] Is this a bug or are we doing something wrong? There is a clearcase view already present there. Thanks, Kind regards / Met vriendelijke groeten, Maarten Roosendaal / Capgemini / Netherlands Senior Consultant / Java Assembly Line / ADC Technologies T. +31 30 68 970 77 / Mob. +31 6 248 216 12 www.nl.capgemini.com Join the Collaborative Business Experience This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
RE: Continuum file url to pom.xml
Try this one: file:/c://project/pom.xml -Original Message- From: Roosendaal, Maarten [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 3:37 PM To: continuum-users@maven.apache.org Subject: Continuum file url to pom.xml Hi, We are trying to add a Maven 2(.0.7) project to Continuum (1.0.3). The pom.xml is part of a clearcase view so we have to fill in the M2 POM Url. Unfortunatly whatever we try it does not work: * file://localhost/c://project/pom.xml * file://c://project/pom.xml * file://localhost/c:\\project\pom.xml and then some. We've also tried following the instructions on: http://maven.apache.org/continuum/faqs.html#can-i-use-file-protocol-in-a dd-project-view but the specified folder is not there. I added it and changed all the application.xml's but with no luck We keep getting the message:[ You must provide a valid url (http, https, ftp and file protocols are allowed) ] Is this a bug or are we doing something wrong? There is a clearcase view already present there. Thanks, Kind regards / Met vriendelijke groeten, Maarten Roosendaal / Capgemini / Netherlands Senior Consultant / Java Assembly Line / ADC Technologies T. +31 30 68 970 77 / Mob. +31 6 248 216 12 www.nl.capgemini.com Join the Collaborative Business Experience This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
URL Malformed
Hi, I have a parent pom with some modules: ... ../p1/trunk ../p2/trunk ../p3/trunk ... when I try to add the parent pom on continuum I have this answer: The URL provided is malformed. The URL provided is malformed. The URL provided is malformed. I think that version 1.1-alpha-2 accept "../" or..not? anyone knows where is the problem? Thanks to all Javier -- View this message in context: http://www.nabble.com/URL-Malformed-tf4109773.html#a11686952 Sent from the Continuum - Users mailing list archive at Nabble.com.
Fwd: OT: Continuum
Forwarded to continuum user list.. -- Forwarded message -- From: John Coleman <[EMAIL PROTECTED]> Date: Jul 19, 2007 1:25 PM Subject: OT: Continuum To: Maven Users List <[EMAIL PROTECTED]> Hi, is there any Continuum list? I don't see anything on the site. I just wanted to know why Continuum swallows up 2GB of Ram when idle. Regards, John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK.
RE: Maven2 release process in Continuum
> -Original Message- > From: Jesse McConnell [mailto:[EMAIL PROTECTED] > > there have been threads on this on the maven-users and maven-dev lists... > > in fact Kenny has written extensively on this topic I believe :) > I've searched the web for Kenny, version, maven-dev, maven-user and my closest article is this: http://docs.codehaus.org/display/MAVEN/Versioning?showComments=true#comm ents by Kenney Westerhof Are you referring to this article? If there are other articles that have interested you, could you please provide a link. Many thanks. > if your interested in contributing to this effort, I would take a look > there for places to help out. > Ok thanks for the tips. > the fundamental problem your dealing with is that 1.2.3 is a released > version to most people...and the -SNAPSHOT and timestamped version are > for development purposes... > Yes, 1.2.3 is good for users and it should be that way from the user's perspective of releases, but maven should also accommodate the developer's niche by standardizing the way to view builds. Best regards, Johan
Re: Maven2 POM Continuum configuration
While I am waiting for help on this, can someone point me to the docs for the maven2 pom configuration for the ciManagement tag with Continuum? I only found this which does not seem to have anything about controlling which notifications are used. http://maven.apache.org/continuum/guides/getting-started/index.html Thanks -AZ On 7/18/07, Aaron Zeckoski <[EMAIL PROTECTED]> wrote: Cool! That halfway works. The email is now appearing in continuum. Unfortunately, it is still including the full list of notifications. I tried using this: Continuum http://saffron.caret.cam.ac.uk/continuum mail true true [EMAIL PROTECTED] and this: Continuum http://saffron.caret.cam.ac.uk/continuum mail true true [EMAIL PROTECTED] But Continuum puts in the defaults of all notifications in both cases. Any ideas? -AZ On 7/18/07, Marcel Schutte <[EMAIL PROTECTED]> wrote: > Hi Aaron, > > I'm using the following: > > > >mail >true >true >true >true > > [EMAIL PROTECTED] > > > > > Regards, Marcel > > - Original Message > From: Aaron Zeckoski <[EMAIL PROTECTED]> > To: continuum-users@maven.apache.org > Sent: Wednesday, July 18, 2007 10:34:29 AM > Subject: Maven2 POM Continuum configuration > > I am trying to find the docs that describe how to setup the continuum > configuration in a maven2 pom correctly. Right now I have the > following in my pom (using maven 2.0.7): > > > Continuum > http://saffron.caret.cam.ac.uk/continuum > > >mail >[EMAIL PROTECTED] > > > > > However, this results in Continuum 1.0.3 setting up the notifcation > (as picked up from the pom) as follows: > Type Recipient Events From > Mail Success Failures Error Warnings Project > (basically the recipient field is blank and the events have all selected) > > What I really want is the configuration we use when we manually set this up: > Type Recipient Events From > Mail [EMAIL PROTECTED] Success Failures User > (i.e. my email address and only 2 events selected) > > Is there any way I can Continuum to do this from the ciManagement tag? > (pointer to docs would be great) > Thanks > -AZ > > > -- > Aaron Zeckoski ([EMAIL PROTECTED]) > Senior Research Engineer - CARET - Cambridge University > [http://bugs.sakaiproject.org/confluence/display/~aaronz/] > Sakai Fellow - [http://aaronz-sakai.blogspot.com/] > > > > > > > > Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. > http://sims.yahoo.com/ > -- Aaron Zeckoski ([EMAIL PROTECTED]) Senior Research Engineer - CARET - Cambridge University [http://bugs.sakaiproject.org/confluence/display/~aaronz/] Sakai Fellow - [http://aaronz-sakai.blogspot.com/] -- Aaron Zeckoski ([EMAIL PROTECTED]) Senior Research Engineer - CARET - Cambridge University [http://bugs.sakaiproject.org/confluence/display/~aaronz/] Sakai Fellow - [http://aaronz-sakai.blogspot.com/]
Re: Maven2 release process in Continuum
there have been threads on this on the maven-users and maven-dev lists... in fact Kenny has written extensively on this topic I believe :) if your interested in contributing to this effort, I would take a look there for places to help out. the fundamental problem your dealing with is that 1.2.3 is a released version to most people...and the -SNAPSHOT and timestamped version are for development purposes... your use case is valid, its just not supported right now :) jesse On 7/19/07, Johan Iskandar <[EMAIL PROTECTED]> wrote: > -Original Message- > From: Jesse McConnell [mailto:[EMAIL PROTECTED] > > ah, I basically see what your problem is... > > that is what the whole SNAPSHOT concept addresses... > > where you are saying a project would only care about 1.2.3 and not the > build numbers..that is functionally saying that its really only caring > about 1.2.3-SNAPSHOT. you can't just say 1.2.3 since that is a > _release_ version...so setting 1.2.3 as a version of a dependency > means that in a repository you should have a version 1.2.3 that is > _released_...ie, ain't going to change _ever_. I think this assumption is there because maven tries to be flexible in terms of how many dots in a version Which I think this should not be the case if it's standardized to just only 3 dots.. w.x.y.z Am I guessing right? If there were only 3 dots then when we state 1.2.3 we mean 1.2.3.x or the current way maven uses the -SNAPSHOT in 1.2.3-SNAPSHOT please cmiiw johan -- jesse mcconnell [EMAIL PROTECTED]
RE: Maven2 release process in Continuum
> -Original Message- > From: Jesse McConnell [mailto:[EMAIL PROTECTED] > > ah, I basically see what your problem is... > > that is what the whole SNAPSHOT concept addresses... > > where you are saying a project would only care about 1.2.3 and not the > build numbers..that is functionally saying that its really only caring > about 1.2.3-SNAPSHOT. you can't just say 1.2.3 since that is a > _release_ version...so setting 1.2.3 as a version of a dependency > means that in a repository you should have a version 1.2.3 that is > _released_...ie, ain't going to change _ever_. I think this assumption is there because maven tries to be flexible in terms of how many dots in a version Which I think this should not be the case if it's standardized to just only 3 dots.. w.x.y.z Am I guessing right? If there were only 3 dots then when we state 1.2.3 we mean 1.2.3.x or the current way maven uses the -SNAPSHOT in 1.2.3-SNAPSHOT please cmiiw johan
RE: Maven2 release process in Continuum
> But if a new test case is introduced then the maintainer of the 1.2.3.4 > pom should increment the bug-fix number (or whatever name is best used > here) so the new version would be 1.2.4.0 > I mean the maintainer should trigger maven to increment the bug-fix number He himself doesn't need to change the 3 to 4 He could also be given a way to increment minor release and major release. The build should be automatically incremented when a change in build number of the scm is detected. I dunno whether this should be implemented in continuum or maven.. where do u think best jesse? Having said all about version number, this is by no means to mix it up with the versioning mechanism of the available scm (I'm against mixing concerns of scm and build & integration tools such as maven & continuum)...IMHO it's a different thing.. In scm the talk is probably about branching for group dev, disk space saving?? But I think in build tool the concern is more in the version of the functionality to deliver.. Best regards, Johan Just my 2 cents
Re: Maven2 release process in Continuum
ah, I basically see what your problem is... that is what the whole SNAPSHOT concept addresses... where you are saying a project would only care about 1.2.3 and not the build numbers..that is functionally saying that its really only caring about 1.2.3-SNAPSHOT. you can't just say 1.2.3 since that is a _release_ version...so setting 1.2.3 as a version of a dependency means that in a repository you should have a version 1.2.3 that is _released_...ie, ain't going to change _ever_. by calling it a snapshot then it can be updated, and as the builds your referring to would showup in the repository as timestamped builds. then when release times comes, your SNAPSHOTS need to be resolved to actual released versions, the pom changed accordingly and then release your goop. maven is very focused on reproducible builds, and your build number deal is just restating the problem that SNAPSHOT's already addresses. there might be a minor difference here or there, but your basically restating snapshots. jesse On 7/19/07, Johan Iskandar <[EMAIL PROTECTED]> wrote: 1.2.3.5-SNAPSHOT I don't think we'd be needing SNAPSHOT here All is needed from the user of the parent pom's point of view is the 1.2.3 since in terms of functionality and testability nothing's changed.. So other poms that has dependencymanagement pointing at 1.2.3 doesn't need to know about the fact that it's at build 4 or 5. But if a new test case is introduced then the maintainer of the 1.2.3.4 pom should increment the bug-fix number (or whatever name is best used here) so the new version would be 1.2.4.0 While saying that the pom itself must know at what version it is in..1.2.3.5 or 1.2.4.0 Is my point clearer? johan > -Original Message- > From: Jesse McConnell [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 19, 2007 2:17 PM > To: continuum-users@maven.apache.org > Subject: Re: Maven2 release process in Continuum > > what aspect of maven do you think is killing this use case? > > 1.2.3.4-SNAPSHOT when its run through the release process will offer > up as a default 1.2.3.5-SNAPSHOT as the new development version and > 1.2.3.4 as the released version... > > deployment will work...whats killing this for you? > > and the release process will let you change that if it doesn't guess > right... > > jesse > > On 7/19/07, Johan Iskandar <[EMAIL PROTECTED]> wrote: > > > > > > > From: Jesse McConnell [mailto:[EMAIL PROTECTED] > > > > > > ok, I am a bit confused by what your actually asking here... > > > > > > but there is no reason in the world you can't use w.x.y.z > > versioning... > > > > > Well, since maven's main idea is to promote conventions.. and these > > conventions is there to ease and straighten out development process, why > > not take it to this level of detail..? > > It would ease versioning path details out of the developers mind.. > > > > Best regards, > > Johan > > > > > > > -- > jesse mcconnell > [EMAIL PROTECTED] -- jesse mcconnell [EMAIL PROTECTED]
