archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <>
Subject Re: proposed structural change to the source repo
Date Sun, 30 Mar 2008 00:20:01 GMT
I finished this up yesterday.

To build/deploy the reference docs, run site/site-deploy from archiva- 
modules (not yet in the release process - it takes too long until the  
tests are faster).

To build/deploy the release docs, run site/site-deploy from archiva- 
docs (this is now wired in to the release process)

A site will build from the top level, but it's not intended to be  
deployed or used anywhere.

The only one I'm not sure about is the cli module - it's at the top  
level since it seems separate enough and for distribution, but it  
contains code so it's excluded from the reference. It also results in  
more content in the root POM that could be pushed down to the modules  
POM. What do others think?

- Brett

On 29/03/2008, at 2:19 PM, Brett Porter wrote:

> Ok, I've done this - will now work on cleaning up the reporting.
> I also changed the group ID to org.apache.archiva. I have not done  
> this on the branch for 1.0.x however.
> - Brett
> On 28/03/2008, at 7:36 AM, Brett Porter wrote:
>> Since we're moving tomorrow anyway, I'd like to propose making the  
>> following change subsequently:
>> /archiva
>> /archiva-docs
>> /archiva-jetty
>> /archiva-modules
>>  .. current structure under here
>> This means we can retain the one release, one build - but all the  
>> Java code sites under -modules. This allows us to put all the Java  
>> code reporting in there, and not pollute the -docs and the distro  
>> with it.
>> I think more changes can be made to the structure of -modules, but  
>> that can be done at a later time.
>> Any objections?
>> - Brett
>> --
>> Brett Porter
> --
> Brett Porter

Brett Porter

View raw message