Re: How about restructuring Qpid java project in to modules

[Robbie Gemmell <ro...@gmail.com>]

Hi Lahiru,

Although I agree its not the way id go if i was doing it from scratch
just now, I dont personally find the layout that much of an issue. I
wouldnt really be in favour of moving all the modules just now as its
a change any downstream projects would need to pick up, and it makes
for pain when dealing with branches on other side of the change. The
only time I would really consider changing it is if we were ever
thinking of making a bunch wide reaching changes to the repository as
a whole (ie all or nothing type change hehe)

It seems everyone is currently in favour of creating a structured doc/
area at the top level, so i think that will ease the situation a
little for users if they are looking for documentation in the repo; id
expect most people thinking of working with the source are probably ok
finding their way around the existing layout.

Robbie

2009/11/20 Lahiru Gunathilake <gl...@gmail.com>:
> Hi all,
>
> When we go in to qpid/java directory we can see so many directories here and
> there and there's no proper structure for the project we normal see in a
> Java project.
> I think as a matured project we should have a structure like this,
>
> .
> |-- etc
> |-- legal
> |-- modules
> `-- release-docs
>
> Inside modules we can put our broker/clients/tools etc rather putting all of
> them in the parent directory with other stuff like
> build/lib/docs/release-docs etc.
> I would like to do the restructuring and add a maven build for qpid if we
> are agreeing to do that.
>
> Just a thought WDYT ?
>
> Lahiru
>
> --
> Apache Qpid, Worlds dominant messaging middleware..!!!
>

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org