commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark R. Diggory" <mdigg...@latte.harvard.edu>
Subject Re: [all] maven sites
Date Mon, 16 Feb 2004 20:13:52 GMT


Henri Yandell wrote:

> To be mavenised:
> 
> Discovery
> EL
> Jexl
> Logging
> Modeler
> 
> I'll work on Discovery tonight.  Do we have a template project.xxx and
> xdocs/*.* yet for new projects?
> 
> I'm very +1 for staying on the stable release of Maven and not HEAD, use
> another machine or just change your MAVEN_HOME to get the other one [I
> bounce back and forth between rc1 and 0.7 at work without major issues].
> 
> I also like the idea of not having the Sandbox'd projects in the nav-bar
> that Stephen suggested a few days ago.
> 
> Hen

I think we should setup a project-template directory somewhere, maybe in 
the sandbox. It will contian something like:

project-template/
project-template/LICENSE.txt
project-template/project.xml
project-template/maven.xml
project-template/project.properties
project-template/xdocs
project-template/src/main
project-template/src/test

I can put this together and place it into the sandbox

-Mark

> 
> On Mon, 16 Feb 2004, robert burrell donkin wrote:
> 
> 
>>On 16 Feb 2004, at 03:56, Tim O'Brien wrote:
>>
>>
>>>Hey, someone is publishing Commons Maven sites with an unreleased
>>>version of Maven.  Probably either from Maven's CVS HEAD, or a beta
>>>version.
>>>
>>>BeanUtils, Betwixt, and Digester all have the newish Maven L+F.  A
>>>decision was reached a while back to standardize on the released
>>>version of Maven.
>>>
>>>Could whoever did that please get the released version of Maven and
>>>republish those sites?
>>
>>i'm using a version nearer cvs head. i'm not very keen on downgrading
>>since it always seems to take a couple of hours for me to get a version
>>of maven that i'm happy with.
>>
>>we're nearing a situation where we'll be able to build the entire
>>commons site from a single command. there are only a handful of site
>>remaining to be converted. anyone feel like volunteering to take care
>>of them?.
>>
>>i'd be happy to avoid deploying the website (with my development
>>version of maven) so long as we start deploying every component website
>>rather than each atomically. how close are we to having a usable
>>reactor documentation build?
>>
>>- robert
>>
>>
>>---------------------------------------------------------------------
>>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


Mime
View raw message