thanks for your comments. The reason I thought about using ':' is because it neatly fits into the current URL schema.
scm:[provider]:push:ssh://server:port/path:fetch:http://otherserver/otherpath your suggestion would look like: scm:[provider]:|push|ssh://server:port/path|fetch|http://otherserver/otherpath I personally dont care much, both will work :) LieGrue, strub --- On Sun, 10/4/09, Dennis Lundberg <denn...@apache.org> wrote: > From: Dennis Lundberg <denn...@apache.org> > Subject: Re: [maven-scm] RFC fetch/push URL format > To: "Maven Developers List" <dev@maven.apache.org> > Date: Sunday, October 4, 2009, 8:33 AM > I agree with Brian. The parsing of > SCM URLs have been a source of many > bugs and a lot user confusion in the past. We must have a > clear way of > separating the who URLs. > > The problem is finding a suitable character to use. The '|' > character is > sometimes used in a Windows environment as a replacement > for ':' in a > path. "C:/repos" is sometimes written as "C|/repos" in an > SCM URL. I > don't know if that is a possibility for git or hg though, > as I don't > know how their URLs are constructed. > > On the other hand we can only use characters that are > allowed in a URL... > > Brian Fox wrote: > > I think it would be more legible if the fetch and push > urls were > > separated with something not part of the url normally, > ie a | instead > > of : would stand out visually. Otherwise, this seems > like the only > > workable solution in the current pom model. > > > > On Sat, Oct 3, 2009 at 2:52 AM, Mark Struberg <strub...@yahoo.de> > wrote: > >> Txs Olivier! > >> > >> The old format will remain and the new one will > added additionally as kind of container for specifying 2 > URLs in the old format. > >> > >> Hope I can check this in until tomorrow. > >> > >> LieGrue, > >> strub > >> > >> --- On Fri, 10/2/09, Olivier Lamy <ol...@apache.org> > wrote: > >> > >>> From: Olivier Lamy <ol...@apache.org> > >>> Subject: Re: [maven-scm] RFC fetch/push URL > format > >>> To: "Maven Developers List" <dev@maven.apache.org> > >>> Date: Friday, October 2, 2009, 10:05 PM > >>> If it help to improve git support : > >>> go for it ! > >>> > >>> The most important IMHO is to be backward > compatible and > >>> support the > >>> current git url which are supported : > >>> > >>> <scm> > >>> > >>> > <connection>scm:git:git://github.com/olamy/scm-git-test-one-module.git</connection> > >>> > <developerConnection>scm:git:g...@github.com:olamy/scm-git-test-one-module.git</developerConnection> > >>> </scm> > >>> > >>> -- > >>> Olivier > >>> > >>> 2009/10/1 Mark Struberg <strub...@yahoo.de>: > >>>> Hi! > >>>> > >>>> Git and a few other SCMs are able to use 2 > different > >>> URLs for reading from a server and writing to > a server. > >>>> For Git this is called fetch-URL and > push-URL, and > >>> most DCMS like hg have the same functionality. > An example > >>> would be to fetch via http and to push via > ssh. > >>>> This is not currently supported in the > maven-scm URLs > >>> currently used. We already have an idea how we > could enable > >>> scm-provider specific extensions in the pom > somehow, but > >>> maybe we don't need to do this. > >>>> Currently a git <scm> url looks > like: > >>>> scm:git:https://user:passw...@gitrepos.apache.org > >>>> > >>>> What about the following extension > >>>> scm:git:fetch:https://user:passw...@gitrepos.apache.org/myprj:push:ssh://user:passw...@gitrepos.apache.org/home/gitrepos/myprj > >>>> > >>>> So we introduce 2 new tags :fetch: and > :push: which > >>> may be parsed by the underlying scm provider. > This technique > >>> can be used for whatever scm-provider which is > able to use > >>> separate URLs for write and read operations. > Ideally we > >>> should create a helper functions somewhere > which does the > >>> parsing stuff and returns 2 URLs in the > original format. > >>>> If the old style (only 1 URL without fetch > or push) is > >>> used, we simply use this URL for both > operations. > >>>> This should easily also work for maven2 > >>>> > >>>> WDYT? > >>>> > >>>> LieGrue, > >>>> strub > >>>> > >>>> > >>>> > >>>> > >>>> > >>> > --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >>>> For additional commands, e-mail: dev-h...@maven.apache.org > >>>> > >>>> > >>> > >>> > >>> -- > >>> Olivier > >>> > >>> > --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >>> For additional commands, e-mail: dev-h...@maven.apache.org > >>> > >>> > >> > >> > >> > >> > --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > >> > >> > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > -- > Dennis Lundberg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
