Re: Is ManifoldCF OSI certified?

2011-12-18 Thread Hitoshi Ozawa
Hi,
Just tried to upload the modified version but the max file size is
10MB, which would mean I won't be able to add the jar files I've
added.
Any option to upload the modified zip file which is about 167MB?

Regards,
H.Ozawa

2011/12/13 Karl Wright daddy...@gmail.com:
 You can go to the ticket here:

 https://issues.apache.org/jira/browse/CONNECTORS-314

 As I am sure you know, please make sure when attaching any files that
 you click the Grant license to ASF radio button.

 Thanks!
 Karl

 On Tue, Dec 13, 2011 at 8:57 AM, Karl Wright daddy...@gmail.com wrote:
 Glad to have your help!

 I'm going to go ahead then and create a combined ticket that you can
 attach your combined patch to.  Then one of us will have the fun of
 trying to figure out exactly how to commit it. :-)

 Karl

 On Tue, Dec 13, 2011 at 8:45 AM, Hitoshi Ozawa htshoz...@gmail.com wrote:
The i18n issues, as I said before, are not trivial, and may well
require several iterations to get right.  Tab names are just one
aspect of it.  This is one reason I wanted to separate any i18n
contribution from the database contribution.

 Too late. Almost finished. It's seems to be working alright.

 Forgot to introduce myself. I'm the one who I18N and L10N ESB Mule
 and is currently active in Liferay.

 I'm the one of the top on this page:
 http://www.liferay.com/community/forums/-/message_boards/statistics

 Japanese Wiki pages I've written:
 http://www.liferay.com/community/wiki/-/wiki/Main/%E6%97%A5%E6%9C%AC%E8%AA%9E%E3%83%89%E3%82%AD%E3%83%A5%E3%83%A1%E3%83%B3%E3%83%88

 Mule Japanese page:
 http://www.mulesoft.org/documentation/display/JPNDOC/Mule+Guides

 Regards,
 H.Ozawa


Re: Is ManifoldCF OSI certified?

2011-12-18 Thread Karl Wright
How big is the patch if you simply do not include the jars?  I can
download these myself from a URL.
Karl

On Sun, Dec 18, 2011 at 10:31 AM, Karl Wright daddy...@gmail.com wrote:
 167MB is the entire size of our current binary deliverable.  As a zip
 that is huge.

 Can't this be broken up?  If it can't your only real choice is to
 create a project in googlecode and then I'd need to incorporate the
 changes piecemeal.  But now I'm really very curious as to why this
 patch is so large.  Perhaps you can do a bit of analysis to determine
 why?

 Karl

 On Sun, Dec 18, 2011 at 10:20 AM, Hitoshi Ozawa htshoz...@gmail.com wrote:
 Hi,
 Just tried to upload the modified version but the max file size is
 10MB, which would mean I won't be able to add the jar files I've
 added.
 Any option to upload the modified zip file which is about 167MB?

 Regards,
 H.Ozawa

 2011/12/13 Karl Wright daddy...@gmail.com:
 You can go to the ticket here:

 https://issues.apache.org/jira/browse/CONNECTORS-314

 As I am sure you know, please make sure when attaching any files that
 you click the Grant license to ASF radio button.

 Thanks!
 Karl

 On Tue, Dec 13, 2011 at 8:57 AM, Karl Wright daddy...@gmail.com wrote:
 Glad to have your help!

 I'm going to go ahead then and create a combined ticket that you can
 attach your combined patch to.  Then one of us will have the fun of
 trying to figure out exactly how to commit it. :-)

 Karl

 On Tue, Dec 13, 2011 at 8:45 AM, Hitoshi Ozawa htshoz...@gmail.com wrote:
The i18n issues, as I said before, are not trivial, and may well
require several iterations to get right.  Tab names are just one
aspect of it.  This is one reason I wanted to separate any i18n
contribution from the database contribution.

 Too late. Almost finished. It's seems to be working alright.

 Forgot to introduce myself. I'm the one who I18N and L10N ESB Mule
 and is currently active in Liferay.

 I'm the one of the top on this page:
 http://www.liferay.com/community/forums/-/message_boards/statistics

 Japanese Wiki pages I've written:
 http://www.liferay.com/community/wiki/-/wiki/Main/%E6%97%A5%E6%9C%AC%E8%AA%9E%E3%83%89%E3%82%AD%E3%83%A5%E3%83%A1%E3%83%B3%E3%83%88

 Mule Japanese page:
 http://www.mulesoft.org/documentation/display/JPNDOC/Mule+Guides

 Regards,
 H.Ozawa


Re: Is ManifoldCF OSI certified?

2011-12-13 Thread Hitoshi Ozawa
The i18n issues, as I said before, are not trivial, and may well
require several iterations to get right.  Tab names are just one
aspect of it.  This is one reason I wanted to separate any i18n
contribution from the database contribution.

Too late. Almost finished. It's seems to be working alright.

Forgot to introduce myself. I'm the one who I18N and L10N ESB Mule
and is currently active in Liferay.

I'm the one of the top on this page:
http://www.liferay.com/community/forums/-/message_boards/statistics

Japanese Wiki pages I've written:
http://www.liferay.com/community/wiki/-/wiki/Main/%E6%97%A5%E6%9C%AC%E8%AA%9E%E3%83%89%E3%82%AD%E3%83%A5%E3%83%A1%E3%83%B3%E3%83%88

Mule Japanese page:
http://www.mulesoft.org/documentation/display/JPNDOC/Mule+Guides

Regards,
H.Ozawa


Re: Is ManifoldCF OSI certified?

2011-12-13 Thread Karl Wright
Glad to have your help!

I'm going to go ahead then and create a combined ticket that you can
attach your combined patch to.  Then one of us will have the fun of
trying to figure out exactly how to commit it. :-)

Karl

On Tue, Dec 13, 2011 at 8:45 AM, Hitoshi Ozawa htshoz...@gmail.com wrote:
The i18n issues, as I said before, are not trivial, and may well
require several iterations to get right.  Tab names are just one
aspect of it.  This is one reason I wanted to separate any i18n
contribution from the database contribution.

 Too late. Almost finished. It's seems to be working alright.

 Forgot to introduce myself. I'm the one who I18N and L10N ESB Mule
 and is currently active in Liferay.

 I'm the one of the top on this page:
 http://www.liferay.com/community/forums/-/message_boards/statistics

 Japanese Wiki pages I've written:
 http://www.liferay.com/community/wiki/-/wiki/Main/%E6%97%A5%E6%9C%AC%E8%AA%9E%E3%83%89%E3%82%AD%E3%83%A5%E3%83%A1%E3%83%B3%E3%83%88

 Mule Japanese page:
 http://www.mulesoft.org/documentation/display/JPNDOC/Mule+Guides

 Regards,
 H.Ozawa


Re: Is ManifoldCF OSI certified?

2011-12-13 Thread Karl Wright
You can go to the ticket here:

https://issues.apache.org/jira/browse/CONNECTORS-314

As I am sure you know, please make sure when attaching any files that
you click the Grant license to ASF radio button.

Thanks!
Karl

On Tue, Dec 13, 2011 at 8:57 AM, Karl Wright daddy...@gmail.com wrote:
 Glad to have your help!

 I'm going to go ahead then and create a combined ticket that you can
 attach your combined patch to.  Then one of us will have the fun of
 trying to figure out exactly how to commit it. :-)

 Karl

 On Tue, Dec 13, 2011 at 8:45 AM, Hitoshi Ozawa htshoz...@gmail.com wrote:
The i18n issues, as I said before, are not trivial, and may well
require several iterations to get right.  Tab names are just one
aspect of it.  This is one reason I wanted to separate any i18n
contribution from the database contribution.

 Too late. Almost finished. It's seems to be working alright.

 Forgot to introduce myself. I'm the one who I18N and L10N ESB Mule
 and is currently active in Liferay.

 I'm the one of the top on this page:
 http://www.liferay.com/community/forums/-/message_boards/statistics

 Japanese Wiki pages I've written:
 http://www.liferay.com/community/wiki/-/wiki/Main/%E6%97%A5%E6%9C%AC%E8%AA%9E%E3%83%89%E3%82%AD%E3%83%A5%E3%83%A1%E3%83%B3%E3%83%88

 Mule Japanese page:
 http://www.mulesoft.org/documentation/display/JPNDOC/Mule+Guides

 Regards,
 H.Ozawa


Re: Is ManifoldCF OSI certified?

2011-12-12 Thread Karl Wright
Hi,

ManifoldCF is Apache licensed.  Apache projects cannot redistribute
GPL jars, but that is not a problem, because we probably do not need
to.  What we usually do in such cases is download the dependencies at
build time, either automatically through the maven build, or by using
the ant download-dependencies target.  For JDBC drivers that are
used by the core database layers, luckily they are loaded via
reflection so that lack of a driver will not prevent the build from
completing, although the user will need to download the driver and
build if they intend to use that driver.

The standard tag library stuff is more problematic it that does not
have redistribution license acceptable for Apache, but I believe the
glassfish stuff is acceptable.  I will verify and get back to you.

The i18n issues, as I said before, are not trivial, and may well
require several iterations to get right.  Tab names are just one
aspect of it.  This is one reason I wanted to separate any i18n
contribution from the database contribution.

Thanks,
Karl


2011/12/12 Hitoshi Ozawa ozawa_hito...@ogis-ri.co.jp:
 Hi,
 I'm checking on the MySQL licenses and it seems MySQL Connector/J is GPL
 v2 license with
 exception clause for FOSS.
 http://www.mysql.com/about/legal/licensing/foss-exception/

 To be classified as FOSS, however, it seems the software has to be OSI
 certified.
 Is Apache ManifoldCF OSI Certified?

 This software is OSI Certified Open Source Software.
 OSI Certified is a certification mark of the Open Source Initiative.

 Does somebody know the license to JSTL libraries? I can't find any
 license in the jstl-api-1.2.jar
 and jstl-impl-1.2.jar files. The files are download-able from Oracle's
 GlassFish project page but
 there's not license page.

 BTW, I just created a Java message class to read String from properties
 file. Seems you've
 hard-coded tab names into the Java source files, which means I have to
 I18N all references to tab
 names or it won't work.

 Regards,
 H.Ozawa



Re: Is ManifoldCF OSI certified?

2011-12-12 Thread Karl Wright
Glassfish is OK to redistribute; we already have two such jars under
redistribution:

 Directory of C:\wip\mcf\trunk\lib

02/27/2011  08:49 AM 1,026,818 jsp-2.1-glassfish-2.1.v20091210.jar
02/27/2011  08:49 AM   135,424 jsp-api-2.1-glassfish-2.1.v20091210.jar

This is what was recorded in the license file for those:

This product includes JSP API jars.
License: Common Development and Distribution License (CDDL) v1.0
(https://glassfish.dev.java.net/public/CDDLv1.0.html)

Karl

On Mon, Dec 12, 2011 at 11:19 PM, Karl Wright daddy...@gmail.com wrote:
 Hi,

 ManifoldCF is Apache licensed.  Apache projects cannot redistribute
 GPL jars, but that is not a problem, because we probably do not need
 to.  What we usually do in such cases is download the dependencies at
 build time, either automatically through the maven build, or by using
 the ant download-dependencies target.  For JDBC drivers that are
 used by the core database layers, luckily they are loaded via
 reflection so that lack of a driver will not prevent the build from
 completing, although the user will need to download the driver and
 build if they intend to use that driver.

 The standard tag library stuff is more problematic it that does not
 have redistribution license acceptable for Apache, but I believe the
 glassfish stuff is acceptable.  I will verify and get back to you.

 The i18n issues, as I said before, are not trivial, and may well
 require several iterations to get right.  Tab names are just one
 aspect of it.  This is one reason I wanted to separate any i18n
 contribution from the database contribution.

 Thanks,
 Karl


 2011/12/12 Hitoshi Ozawa ozawa_hito...@ogis-ri.co.jp:
 Hi,
 I'm checking on the MySQL licenses and it seems MySQL Connector/J is GPL
 v2 license with
 exception clause for FOSS.
 http://www.mysql.com/about/legal/licensing/foss-exception/

 To be classified as FOSS, however, it seems the software has to be OSI
 certified.
 Is Apache ManifoldCF OSI Certified?

 This software is OSI Certified Open Source Software.
 OSI Certified is a certification mark of the Open Source Initiative.

 Does somebody know the license to JSTL libraries? I can't find any
 license in the jstl-api-1.2.jar
 and jstl-impl-1.2.jar files. The files are download-able from Oracle's
 GlassFish project page but
 there's not license page.

 BTW, I just created a Java message class to read String from properties
 file. Seems you've
 hard-coded tab names into the Java source files, which means I have to
 I18N all references to tab
 names or it won't work.

 Regards,
 H.Ozawa