[Registry-dev] Maven structure

[Paul Fremantle]

I'm happy to have a vote. As I said I thought we already reached 
consensus two months ago.

Firstly, I'm assuming that we can make maven work reliably with a single 
module. If that's not the case then what I'm about to say is over-ruled.

I want to make something clear:

If you put maven2 cleanliness above svn structure, you are putting the 
needs of core developers over casual committers and developers.

Very few people look at Maven or pom.xml. In general they hope it will 
work and it does. Especially people new to the project. However, even an 
interested user might well come and take a look at your code. They might 
be interested in how complex the project is, or want to see how many 
comments there are, or want to look at the code behind a stack trace 
exception. Its those users we want to attract. We want them to be able 
to find the code easily, browse it, and we want them to understand this 
is a neat, small, well-structured project. Having multiple maven modules 
makes it seem large and ungainly.

My vote is to put the needs of newly interested parties over core 
developers - who are already interested.

Paul

deepal at wso2.com wrote:
>> I'm going to keep sending this till we get an answer! Alternatively you
>> can have a complete Maven novice like me start fooling around and moving
>> stuff in SVN if you prefer :)
> 
> According to the maven2 build structure it is easy having what we have now
> , but I know we can merge webapps module and core module, and then write
> code in pom.xml to create separate artifact. I personally like to keep the
> pom.xml cleaner , if you look at our pom.xml they are much cleaner and we
> only use maven2 pugings to do the work. So we do not need to do much or
> work once we have the directory structure set up.
> 
> Let's take a vote and see how many of like the current sructure, if some
> one is +1 on that he has to tell why he like the structure , same way if
> some one -1 on that then he has to say why he does not like that. :)
> 
> Apache way :)
> 
> -Deepal
> 
> 
>> Paul
>>
>> Paul Fremantle wrote:
>>> A long while back we discussed whether there was really a need for a set
>>> of Maven modules. I thought - maybe incorrectly - that we had come to a
>>> consensus that there was no need.
>>>
>>> If that is the case, then I would like us to refactor the maven build
>>> asap.
>>>
>>> Ideally, we can have a single tree which builds the standalone library
>>> and WAR by default, with specific targets if you just want one or
>>> t'other.
>>>
>>> Paul
>>>
>> --
>> Paul Fremantle
>> Co-Founder and VP of Technical Sales, WSO2
>> OASIS WS-RX TC Co-chair
>>
>> Office: +1 646 290 8050
>> Cell: +44 798 447 4618
>>
>> blog: http://pzf.fremantle.org
>> paul at wso2.com
>>
>> "Oxygenating the Web Service Platform", www.wso2.com
>>
>> _______________________________________________
>> Registry-dev mailing list
>> Registry-dev at wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
>>
> 
> 
> _______________________________________________
> Registry-dev mailing list
> Registry-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
> 

-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

Office: +1 646 290 8050
Cell: +44 798 447 4618

blog: http://pzf.fremantle.org
paul at wso2.com

"Oxygenating the Web Service Platform", www.wso2.com