Yes... you are both convincing me that deleting would be better: in fact this 
would be easier if we want to remove a part of a component (it would be 
difficult to move the code to "archive").
And the initial cleanup and version of the Confluence page could be based on 
the content of this file:

http://svn.apache.org/repos/asf/ofbiz/trunk/OPTIONAL_LIBRARIES

Jacopo

On Mar 2, 2012, at 11:07 AM, Jacques Le Roux wrote:

> Then also nstruction in main README file
> 
> Both are ok with me, but maybe less work by getting rid of hashes indeed...
> 
> Jacques
> 
> From: "Adrian Crum" <adrian.c...@sandglass-software.com>
>> We could have an "archived components" page on the wiki to describe all of 
>> that.
>> 
>> -Adrian
>> 
>> On 3/2/2012 9:33 AM, Jacopo Cappellato wrote:
>>> On Mar 2, 2012, at 10:26 AM, Adrian Crum wrote:
>>> 
>>>> I don't understand the need for the archive folder. If we just remove 
>>>> unused code, then anyone wanting to resurrect it can just check out a 
>>>> previous revision that included it.
>>> This is definitely true but I was thinking that it may be easier to 
>>> document the instructions about these old components (using README files in 
>>> the "archive" subfolders); for *example* if we will move there "webslinger" 
>>> we could add to the README files the details about how to define the OFBiz 
>>> container for it (currently in the config files in the "base" folder). But 
>>> actually the same can be retrieved from the commit logs if we will decide 
>>> to simply delete from repository. I am very open to both the solutions.
>>> 
>>> Thanks,
>>> 
>>> Jacopo
>>> 
>>>> I like the idea of moving some of the specialpurpose components outside 
>>>> the main project.
>>>> 
>>>> -Adrian
>>>> 
>>>> On 3/2/2012 9:21 AM, Jacopo Cappellato wrote:
>>>>> In preparation for bigger changes :-) I would like to propose the 
>>>>> addition of two new folders to the OFBiz svn repository:
>>>>> 
>>>>> branches/
>>>>> tags/
>>>>> archive/ (NEW)
>>>>> trunk/
>>>>> trunk/extras (NEW)
>>>>> 
>>>>> The "archive" folder will be used for keeping an archive of no more used 
>>>>> components or pieces of code: for example the specialpurpose/shark and 
>>>>> the framework/jetty components could be moved there (but of course we 
>>>>> will vote for each component's move); the idea is that the code under the 
>>>>> archive folder is not planned to be released (but of course plans could 
>>>>> change if there is an interest in the community) but in the same time we 
>>>>> prefer to keep the code available to be resurrected
>>>>> 
>>>>> The "trunk/extras" folder is actually very similar to "specialpurpose" (I 
>>>>> have also considered to propose to rename it to "extras"): it will 
>>>>> contain optional components or tools (not necessarily OFBiz components) 
>>>>> like the support for Selenium tests (and the tests themselves) etc... The 
>>>>> idea is that the content of this folder will not be released in the 
>>>>> "Apache OFBiz" releases but it will be instead released by the OFBiz 
>>>>> community as a separate product like "Apache OFBiz Extras" or similar.
>>>>> 
>>>>> What do you think?
>>>>> 
>>>>> Jacopo

Reply via email to