Re: using public keys

2006-11-11 Thread Rahul Akolkar
On 11/9/06, robert burrell donkin <[EMAIL PROTECTED]> wrote: On 11/9/06, Marshall Schor <[EMAIL PROTECTED]> wrote: > One of the tasks suggested in the welcome-to-apache was to set up a > public/private key pair for signing in (instead of using a password). > > Another task in the new-committers i

Re: Maven pom, groupId and version for incubating projects

2006-11-11 Thread Daniel Kulp
On Saturday November 11 2006 3:51 pm, Wendy Smoak wrote: > On 11/11/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > Or is it ok to do: > > > > org.apache.wicket > > wicket-parent > > 1.3-incubating-SNAPSHOT > > From a Maven point of view, this one is preferable so that the groupId > and artifac

Re: Re: Re: Maven pom, groupId and version for incubating projects

2006-11-11 Thread Martijn Dashorst
On 11/11/06, Stephen Duncan <[EMAIL PROTECTED]> wrote: Right. But if they specify org.apache.wicket:wicket:1.0, and some dependency they have has a dependency on org.apache.incubator.wicket:wicket:1.0-incubating, they'll end up with both. If the groupId is the same, they'll just the dependency

Re: Re: Maven pom, groupId and version for incubating projects

2006-11-11 Thread Yoav Shapira
My understanding is the same as Wendy and Stephen's. Put incubating in the version (required), not the groupId or artifactId. Yoav On 11/11/06, Stephen Duncan <[EMAIL PROTECTED]> wrote: Right. But if they specify org.apache.wicket:wicket:1.0, and some dependency they have has a dependency on

Re: Re: Maven pom, groupId and version for incubating projects

2006-11-11 Thread Stephen Duncan
Right. But if they specify org.apache.wicket:wicket:1.0, and some dependency they have has a dependency on org.apache.incubator.wicket:wicket:1.0-incubating, they'll end up with both. If the groupId is the same, they'll just the dependency they specified. -Stephen On 11/11/06, Martijn Dashorst

Re: Maven pom, groupId and version for incubating projects

2006-11-11 Thread Wendy Smoak
On 11/11/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote: Or is it ok to do: org.apache.wicket wicket-parent 1.3-incubating-SNAPSHOT From a Maven point of view, this one is preferable so that the groupId and artifactId will not have to change after graduation. It also meets the requirement

Re: Re: Maven pom, groupId and version for incubating projects

2006-11-11 Thread Martijn Dashorst
On 11/11/06, Stephen Duncan <[EMAIL PROTECTED]> wrote: On 11/11/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > org.apache.incubator.wicket > wicket-parent > 1.3-incubating-SNAPSHOT I think that's a bad thing, as upon the first release after graduation, the groupId will change, and therefore y

Re: Maven pom, groupId and version for incubating projects

2006-11-11 Thread Stephen Duncan
On 11/11/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote: All, Is it a requirement or a 'good thing (tm)' to have the following groupId and version for maven built incubator projects? e.g. take wicket-parent: org.apache.incubator.wicket wicket-parent 1.3-incubating-SNAPSHOT I think that's a b

Maven pom, groupId and version for incubating projects

2006-11-11 Thread Martijn Dashorst
All, Is it a requirement or a 'good thing (tm)' to have the following groupId and version for maven built incubator projects? e.g. take wicket-parent: org.apache.incubator.wicket wicket-parent 1.3-incubating-SNAPSHOT Or is it ok to do: org.apache.wicket wicket-parent 1.3-incubating-SNAPSHOT

Re: Weirdness with the web site

2006-11-11 Thread Marshall Schor
The referred to email 13-oct points to this JIRA issue: https://issues.apache.org/jira/browse/INFRA-881 This says there are some problems with line ends when tools are used to generate websites. I tried an experiment: we have a XDOC-style website. I scanned our XDOC source files and found the

Re: Weirdness with the web site

2006-11-11 Thread Gwyn Evans
On 11/11/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote: > There is an issue with building the site from a windows platform that > causes the eols to get all mixed up. See http://www.apache.org/dev/version-control.html#https-svn, specifically the last two paragraphs, starting with "Committers wil