You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Henri Yandell <ba...@generationjava.com> on 2004/02/16 21:42:30 UTC
project templates Was: [all] maven sites
On Mon, 16 Feb 2004, Mark R. Diggory wrote:
> I was thinking sandbox, because thats where all projects start out and
> its logical that they won't know where commons-build really is.
Sounds good. Should be based on a sandbox project then, ie)
../../jakarta-commons/commons-build/project.xml as the extend.
> I've added some files to the cvs and you can go from there.
>
> http://cvs.apache.org/viewcvs.cgi/jakarta-commons-sandbox/project-template
>
> there may be thing we want to remove/add to this. But I think this is
> the basic requirement for a project.xml.
I've removed a few things :) Hope that's okay.
Couple of questions:
Developers: Should emails be in some form of lightly obscured format?
Should url and timezone be included?
Resources: Should we include .properties by default? In fact, can't most
of the <build> go in the super-pom?
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: project templates Was: [all] maven sites
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Yes
Henri Yandell wrote:
> Discovery project.properties has:
>
> maven.repo.central=www.apache.org
> maven.repo.central.directory=/www/www.apache.org/dist/java-repository
> maven.remote.group=apcvs
>
> Should this be in the template pom.prop?
>
> Hen
>
> On Mon, 16 Feb 2004, Mark R. Diggory wrote:
>
>
>>
>>Henri Yandell wrote:
>>
>>
>>>On Mon, 16 Feb 2004, Mark R. Diggory wrote:
>>>
>>>
>>>
>>>>I was thinking sandbox, because thats where all projects start out and
>>>>its logical that they won't know where commons-build really is.
>>>
>>>
>>>Sounds good. Should be based on a sandbox project then, ie)
>>>../../jakarta-commons/commons-build/project.xml as the extend.
>>>
>>>
>>
>>Yes, I was thinking that to.
>>
>>
>>>>I've added some files to the cvs and you can go from there.
>>>>
>>>>http://cvs.apache.org/viewcvs.cgi/jakarta-commons-sandbox/project-template
>>>>
>>>>there may be thing we want to remove/add to this. But I think this is
>>>>the basic requirement for a project.xml.
>>>
>>>
>>>I've removed a few things :) Hope that's okay.
>>>
>>
>>Cool
>>
>>
>>>Couple of questions:
>>>
>>>Developers: Should emails be in some form of lightly obscured format?
>>> Should url and timezone be included?
>>>
>>>Resources: Should we include .properties by default? In fact, can't most
>>> of the <build> go in the super-pom?
>>>
>>
>>Cool, sounds very good (considering all the spam my apache account seems
>>to get)
>>
>>--
>>Mark Diggory
>>Software Developer
>>Harvard MIT Data Center
>>http://www.hmdc.harvard.edu
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: project templates Was: [all] maven sites
Posted by Henri Yandell <ba...@generationjava.com>.
Discovery project.properties has:
maven.repo.central=www.apache.org
maven.repo.central.directory=/www/www.apache.org/dist/java-repository
maven.remote.group=apcvs
Should this be in the template pom.prop?
Hen
On Mon, 16 Feb 2004, Mark R. Diggory wrote:
>
>
> Henri Yandell wrote:
>
> >
> > On Mon, 16 Feb 2004, Mark R. Diggory wrote:
> >
> >
> >>I was thinking sandbox, because thats where all projects start out and
> >>its logical that they won't know where commons-build really is.
> >
> >
> > Sounds good. Should be based on a sandbox project then, ie)
> > ../../jakarta-commons/commons-build/project.xml as the extend.
> >
> >
> Yes, I was thinking that to.
>
> >>I've added some files to the cvs and you can go from there.
> >>
> >>http://cvs.apache.org/viewcvs.cgi/jakarta-commons-sandbox/project-template
> >>
> >>there may be thing we want to remove/add to this. But I think this is
> >>the basic requirement for a project.xml.
> >
> >
> > I've removed a few things :) Hope that's okay.
> >
>
> Cool
>
> > Couple of questions:
> >
> > Developers: Should emails be in some form of lightly obscured format?
> > Should url and timezone be included?
> >
> > Resources: Should we include .properties by default? In fact, can't most
> > of the <build> go in the super-pom?
> >
>
> Cool, sounds very good (considering all the spam my apache account seems
> to get)
>
> --
> Mark Diggory
> Software Developer
> Harvard MIT Data Center
> http://www.hmdc.harvard.edu
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: project templates Was: [all] maven sites
Posted by Henri Yandell <ba...@generationjava.com>.
Some more questions:
<roles> Is this pointless? It's always 'Java Developer', unless we switch
to ASF positions [PMC, Committer, Member], which should really be in a
different file. Really we need a members.xml file that sits outside of the
pom and is linked in. ie) something like:
http://jakarta.apache.org/~bayard/pergamum/j-c/member-roles.xml
Obviously something I need to take over to Maven.
<organization> Also pointless? ie) this should really always be ASF and
not <insert-your-job-here> ?
Hen
On Mon, 16 Feb 2004, Henri Yandell wrote:
>
> Oops. jakarta-commons-sandbox/proposal is effectively the same thing for
> the old style, so we should integrate it in.
>
> Additionally, it's high time we decided what parts of PROPOSAL,
> RELEASE-NOTES and STATUS are needed for a mavenised commons project.
>
> RELEASE-NOTES could be replaced by changes.xml and the changes plugin.
> STATUS?
>
> PROPOSAL still seems necessary, and we should move it into
> xdocs/proposal.xml with a few parts removed/linked.
>
> I'll think further on this.
>
> Hen
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: project templates Was: [all] maven sites
Posted by Henri Yandell <ba...@generationjava.com>.
Oops. jakarta-commons-sandbox/proposal is effectively the same thing for
the old style, so we should integrate it in.
Additionally, it's high time we decided what parts of PROPOSAL,
RELEASE-NOTES and STATUS are needed for a mavenised commons project.
RELEASE-NOTES could be replaced by changes.xml and the changes plugin.
STATUS?
PROPOSAL still seems necessary, and we should move it into
xdocs/proposal.xml with a few parts removed/linked.
I'll think further on this.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: project templates Was: [all] maven sites
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Henri Yandell wrote:
>
> On Mon, 16 Feb 2004, Mark R. Diggory wrote:
>
>
>>I was thinking sandbox, because thats where all projects start out and
>>its logical that they won't know where commons-build really is.
>
>
> Sounds good. Should be based on a sandbox project then, ie)
> ../../jakarta-commons/commons-build/project.xml as the extend.
>
>
Yes, I was thinking that to.
>>I've added some files to the cvs and you can go from there.
>>
>>http://cvs.apache.org/viewcvs.cgi/jakarta-commons-sandbox/project-template
>>
>>there may be thing we want to remove/add to this. But I think this is
>>the basic requirement for a project.xml.
>
>
> I've removed a few things :) Hope that's okay.
>
Cool
> Couple of questions:
>
> Developers: Should emails be in some form of lightly obscured format?
> Should url and timezone be included?
>
> Resources: Should we include .properties by default? In fact, can't most
> of the <build> go in the super-pom?
>
Cool, sounds very good (considering all the spam my apache account seems
to get)
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: project templates Was: [all] maven sites
Posted by Henri Yandell <ba...@generationjava.com>.
On Mon, 16 Feb 2004, Henri Yandell wrote:
> Resources: Should we include .properties by default? In fact, can't most
> of the <build> go in the super-pom?
Me idiot. This stuff is all in there by default. So the entire <build> can
be removed in the child project I'm guessing.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org