It sounds like that stuff needs a LOT of cleaning up before it goes
into the trunk...
I don't think this makes sense to put into its own component and
should (like the older Axis stuff) go into the service and webtools
components.
If that's beyond what you want to invest in this, don't worry about
it... sooner or later it will be important enough to someone to sit
down and do it... and if not then it's a clear sign that no one cares
enough! :(
-David
On May 2, 2009, at 1:42 PM, Jacques Le Roux wrote:
In my effort to commit the new Axis2 component in framework I wonder
about licences issues.
I have added the necessary in NOTICE, it was easy, no problems
Currently in the component, at framework/axis2/webapp/axis2/WEB-INF/
lib/ precisely, there are a number of libraries which come with
their licence files. There are near hundred files (97 exactly), 40
being licence files.
I was ready to put the content of these licence files in the LICENCE
file and to put also the libraries with them as it's done for
the others.
But then I wondered if it's a worthwhile (very tedious) task.
For 2 reasons :
1) The information is already there, and we could just said that in
the LICENCE file
2) If we do so future updates will be far easier (nothing to check
but maybe updating the wiki page related to libraries)
What do you think ? Do we really need to put these informations in
LICENCE file or a simple mention in it would be sufficient ?
Something like <<Some extra libraries come with Axis2, their licence
files can be found into
framework/axis2/webapp/axis2/WEB-INF/lib/>> added after
<<Other licenses used by libraries distributed with Apache OFBiz are
listed
below. This file includes a list of all libraries distributed with
Apache
OFBiz and the full text of the license used for each.>>
Thanks
Jacques
From: "Jacques Le Roux" <jacques.le.r...@les7arts.com>
Yes, this sounds like the better place. Webtools with a link seems
more accessible. I will do
Jacques
From: "Ashish Vijaywargiya" <ashish.vijaywarg...@hotwaxmedia.com>
+1 on David's comment.
Somehow I missed to think like this.
--
Ashish
David E Jones wrote:
Sorry I missed the earlier message...
Shouldn't this be in the framework and refactored to be part of
the service or perhaps webtools components? I ask because I
think this is more of a core/technical type of functionality.
-David
