Lahiru Gunathilake wrote:
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 ?
I'm -1 on a maven build. We've been down that road before with miserable
consequences. The current build does produce poms. I don't know how much
they're used/tested, so that might be something to look at if you're
interested in maven integration.
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
