subject:"Release\?"

I downloaded binary .tar.gz, unpacked, checked md5 sum - everything is correct

There is small error in README, it says that user need to switch to
dist/example directory, while there is only example directory

I run start.jar, and able to login to GUI, but in many places I see
listconnections.ListOfRepositoryConnections instead of real text

On Fri, Apr 6, 2012 at 3:25 AM, Shinichiro Abe
shinichiro.ab...@gmail.com wrote:
 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC5/
 and there is also a tag in svn under
 https://svn.apache.org/repos/asf/incubator/lcf/tags.

 Thank you,
 Shinichiro Abe



-- 
With best wishes,                    Alex Ott
http://alexott.net/
Tiwtter: alexott_en (English), alexott (Russian)
Skype: alex.ott

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC5

Hi Alex,

What you are seeing is the i18n key name rather than the localized
translation.  If you have a locale other than en_US or ja_JP, it's
supposed to map the locale to en_US, and look up the English text.  If
it can't find the key even then, it will render the key name instead.

The same issue you have seen has been reported before but it's been
impossible for me to reproduce.  I've been using an add-on in Firefox
which allows me to set the locale but it doesn't fail for me no matter
what locale I select.  However, in Italy apparently the same thing
happened on one machine as is now happening for you.  We presumed that
the setup must be broken on the Italian machine that was exhibiting
the problem, apparently incorrectly.

The other weird thing is that apparently only *some* fields have a
problem and the others are OK.  The code, though, for rendering all
the fields is, however, identical.

Any help or research you want to do would be very very welcome given
the bizarre nature of the issue.

Karl

On Fri, Apr 6, 2012 at 6:59 AM, Alex Ott alex...@gmail.com wrote:
 I downloaded binary .tar.gz, unpacked, checked md5 sum - everything is correct

 There is small error in README, it says that user need to switch to
 dist/example directory, while there is only example directory

 I run start.jar, and able to login to GUI, but in many places I see
 listconnections.ListOfRepositoryConnections instead of real text

 On Fri, Apr 6, 2012 at 3:25 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC5/
 and there is also a tag in svn under
 https://svn.apache.org/repos/asf/incubator/lcf/tags.

 Thank you,
 Shinichiro Abe



 --
 With best wishes,                    Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC5

If you want to experiment a bit, have a look at the file
listconnections.jsp (in framework/crawler-ui/src/webapp).  The line in
question is line 78.  Perhaps if you change the line to also output
the locale itself we might learn something.

Karl

On Fri, Apr 6, 2012 at 7:34 AM, Karl Wright daddy...@gmail.com wrote:
 Hi Alex,

 What you are seeing is the i18n key name rather than the localized
 translation.  If you have a locale other than en_US or ja_JP, it's
 supposed to map the locale to en_US, and look up the English text.  If
 it can't find the key even then, it will render the key name instead.

 The same issue you have seen has been reported before but it's been
 impossible for me to reproduce.  I've been using an add-on in Firefox
 which allows me to set the locale but it doesn't fail for me no matter
 what locale I select.  However, in Italy apparently the same thing
 happened on one machine as is now happening for you.  We presumed that
 the setup must be broken on the Italian machine that was exhibiting
 the problem, apparently incorrectly.

 The other weird thing is that apparently only *some* fields have a
 problem and the others are OK.  The code, though, for rendering all
 the fields is, however, identical.

 Any help or research you want to do would be very very welcome given
 the bizarre nature of the issue.

 Karl

 On Fri, Apr 6, 2012 at 6:59 AM, Alex Ott alex...@gmail.com wrote:
 I downloaded binary .tar.gz, unpacked, checked md5 sum - everything is 
 correct

 There is small error in README, it says that user need to switch to
 dist/example directory, while there is only example directory

 I run start.jar, and able to login to GUI, but in many places I see
 listconnections.ListOfRepositoryConnections instead of real text

 On Fri, Apr 6, 2012 at 3:25 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC5/
 and there is also a tag in svn under
 https://svn.apache.org/repos/asf/incubator/lcf/tags.

 Thank you,
 Shinichiro Abe



 --
 With best wishes,                    Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC5

I've created CONNECTORS-457 to track this issue.  If we can figure out
what's actually happening we may decide to spin yet another RC to fix
the problem.

Karl

On Fri, Apr 6, 2012 at 7:43 AM, Karl Wright daddy...@gmail.com wrote:
 If you want to experiment a bit, have a look at the file
 listconnections.jsp (in framework/crawler-ui/src/webapp).  The line in
 question is line 78.  Perhaps if you change the line to also output
 the locale itself we might learn something.

 Karl

 On Fri, Apr 6, 2012 at 7:34 AM, Karl Wright daddy...@gmail.com wrote:
 Hi Alex,

 What you are seeing is the i18n key name rather than the localized
 translation.  If you have a locale other than en_US or ja_JP, it's
 supposed to map the locale to en_US, and look up the English text.  If
 it can't find the key even then, it will render the key name instead.

 The same issue you have seen has been reported before but it's been
 impossible for me to reproduce.  I've been using an add-on in Firefox
 which allows me to set the locale but it doesn't fail for me no matter
 what locale I select.  However, in Italy apparently the same thing
 happened on one machine as is now happening for you.  We presumed that
 the setup must be broken on the Italian machine that was exhibiting
 the problem, apparently incorrectly.

 The other weird thing is that apparently only *some* fields have a
 problem and the others are OK.  The code, though, for rendering all
 the fields is, however, identical.

 Any help or research you want to do would be very very welcome given
 the bizarre nature of the issue.

 Karl

 On Fri, Apr 6, 2012 at 6:59 AM, Alex Ott alex...@gmail.com wrote:
 I downloaded binary .tar.gz, unpacked, checked md5 sum - everything is 
 correct

 There is small error in README, it says that user need to switch to
 dist/example directory, while there is only example directory

 I run start.jar, and able to login to GUI, but in many places I see
 listconnections.ListOfRepositoryConnections instead of real text

 On Fri, Apr 6, 2012 at 3:25 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC5/
 and there is also a tag in svn under
 https://svn.apache.org/repos/asf/incubator/lcf/tags.

 Thank you,
 Shinichiro Abe



 --
 With best wishes,                    Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC5

Hi Karl

Ok, I'll try to reproduce this using code from repository...

I'm using following locale on my machine (Mac OS X 10.6.8):

LANG=C
LC_COLLATE=ru_RU.UTF-8
LC_CTYPE=ru_RU.UTF-8
LC_MESSAGES=C
LC_MONETARY=ru_RU.UTF-8
LC_NUMERIC=C
LC_TIME=ru_RU.UTF-8
LC_ALL=

And here is example of request from my browser:

GET /~ott/ HTTP/1.1
Host: localhost
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0)
Gecko/20100101 Firefox/11.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language:
en-GB,en,ru-RU,ru;q=0.9,en-US;q=0.9,de-DE;q=0.9,de;q=0.9,en-gb;q=0.8,fr-FR;q=0.8,fr;q=0.8,it-IT;q=0.8,it;q=0.7,hu-HU;q=0.7,hu;q=0.7,en-us;q=0.7,en-ww;q=0.7,nl-NL;q=0.6,nl;q=0.6,en-ca;q=0.6,zh-CN;q=0.6,zh;q=0.5,EN-US;q=0.5,EN;q=0.5,en-US.UTF-8;q=0.5,uk-UA;q=0.4,uk;q=0.4,in-ID;q=0.4,in;q=0.4,cs-CZ;q=0.3,cs;q=0.3,en-en;q=0.3,ja-JP;q=0.3,ja;q=0.3,he-IL;q=0.2,he;q=0.2,en-GB.UTF-8;q=0.2,fi-FI;q=0.2,fi;q=0.1,en-US-ORACLE9I;q=0.1,en-s;q=0.1,en-ws;q=0.1,en-AU;q=0.0,en;q=0.0
Accept-Encoding: gzip, deflate
Connection: keep-alive

On Fri, Apr 6, 2012 at 1:34 PM, Karl Wright daddy...@gmail.com wrote:
 Hi Alex,

 What you are seeing is the i18n key name rather than the localized
 translation.  If you have a locale other than en_US or ja_JP, it's
 supposed to map the locale to en_US, and look up the English text.  If
 it can't find the key even then, it will render the key name instead.

 The same issue you have seen has been reported before but it's been
 impossible for me to reproduce.  I've been using an add-on in Firefox
 which allows me to set the locale but it doesn't fail for me no matter
 what locale I select.  However, in Italy apparently the same thing
 happened on one machine as is now happening for you.  We presumed that
 the setup must be broken on the Italian machine that was exhibiting
 the problem, apparently incorrectly.

 The other weird thing is that apparently only *some* fields have a
 problem and the others are OK.  The code, though, for rendering all
 the fields is, however, identical.

 Any help or research you want to do would be very very welcome given
 the bizarre nature of the issue.

 Karl

 On Fri, Apr 6, 2012 at 6:59 AM, Alex Ott alex...@gmail.com wrote:
 I downloaded binary .tar.gz, unpacked, checked md5 sum - everything is 
 correct

 There is small error in README, it says that user need to switch to
 dist/example directory, while there is only example directory

 I run start.jar, and able to login to GUI, but in many places I see
 listconnections.ListOfRepositoryConnections instead of real text

 On Fri, Apr 6, 2012 at 3:25 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC5/
 and there is also a tag in svn under
 https://svn.apache.org/repos/asf/incubator/lcf/tags.

 Thank you,
 Shinichiro Abe



 --
 With best wishes,                    Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott



-- 
With best wishes,                    Alex Ott
http://alexott.net/
Tiwtter: alexott_en (English), alexott (Russian)
Skype: alex.ott

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC5

You happen to be using the very same java version as the other person
who is having trouble.

I'll have a look at the logs.

Karl

On Fri, Apr 6, 2012 at 1:02 PM, Alex Ott alex...@gmail.com wrote:
 Hi

 I see following errors:

 ERROR 2012-04-06 12:57:26,822 (1407601211@qtp-1238538872-2) - Missing
 resource 'listoutputs.DeleteOutputConnection' in bundle
 'org.apache.manifoldcf.ui.i18n.common' for locale 'en_GB'
 java.util.MissingResourceException: Can't find resource for bundle
 java.util.PropertyResourceBundle, key
 listoutputs.DeleteOutputConnection
        at java.util.ResourceBundle.getObject(ResourceBundle.java:374)
        at java.util.ResourceBundle.getString(ResourceBundle.java:334)
        at 
 org.apache.manifoldcf.core.i18n.Messages.getMessage(Messages.java:180)
        at 
 org.apache.manifoldcf.core.i18n.Messages.getString(Messages.java:195)
        at org.apache.manifoldcf.ui.i18n.Messages.getString(Messages.java:98)
        at org.apache.manifoldcf.ui.i18n.Messages.getString(Messages.java:46)
        at org.apache.jsp.listoutputs_jsp._jspService(listoutputs_jsp.java:257)
        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at 
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:388)

 and for other resources... Full log is at
 http://dl.dropbox.com/u/1796900/manifoldcf.log.gz

 Regarding Java version - I updated yesterday, and now I have:

 ott@flash:example/logs\java -version
 Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
 java version 1.6.0_31
 Java(TM) SE Runtime Environment (build 1.6.0_31-b04-413-10M3623)
 Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01-413, mixed mode)

 On Fri, Apr 6, 2012 at 6:41 PM, Karl Wright daddy...@gmail.com wrote:
 Also, very interesting that you have a Mac.  So does everyone else
 that has seen the problem.  What jdk version are you running?

 Karl

 On Fri, Apr 6, 2012 at 12:38 PM, Karl Wright daddy...@gmail.com wrote:
 What does your manifoldcf.log file have in it?

 Karl

 On Fri, Apr 6, 2012 at 12:36 PM, Alex Ott alex...@gmail.com wrote:
 Hi Karl

 Ok, I'll try to reproduce this using code from repository...

 I'm using following locale on my machine (Mac OS X 10.6.8):

 LANG=C
 LC_COLLATE=ru_RU.UTF-8
 LC_CTYPE=ru_RU.UTF-8
 LC_MESSAGES=C
 LC_MONETARY=ru_RU.UTF-8
 LC_NUMERIC=C
 LC_TIME=ru_RU.UTF-8
 LC_ALL=

 And here is example of request from my browser:

 GET /~ott/ HTTP/1.1
 Host: localhost
 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0)
 Gecko/20100101 Firefox/11.0
 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
 Accept-Language:
 en-GB,en,ru-RU,ru;q=0.9,en-US;q=0.9,de-DE;q=0.9,de;q=0.9,en-gb;q=0.8,fr-FR;q=0.8,fr;q=0.8,it-IT;q=0.8,it;q=0.7,hu-HU;q=0.7,hu;q=0.7,en-us;q=0.7,en-ww;q=0.7,nl-NL;q=0.6,nl;q=0.6,en-ca;q=0.6,zh-CN;q=0.6,zh;q=0.5,EN-US;q=0.5,EN;q=0.5,en-US.UTF-8;q=0.5,uk-UA;q=0.4,uk;q=0.4,in-ID;q=0.4,in;q=0.4,cs-CZ;q=0.3,cs;q=0.3,en-en;q=0.3,ja-JP;q=0.3,ja;q=0.3,he-IL;q=0.2,he;q=0.2,en-GB.UTF-8;q=0.2,fi-FI;q=0.2,fi;q=0.1,en-US-ORACLE9I;q=0.1,en-s;q=0.1,en-ws;q=0.1,en-AU;q=0.0,en;q=0.0
 Accept-Encoding: gzip, deflate
 Connection: keep-alive

 On Fri, Apr 6, 2012 at 1:34 PM, Karl Wright daddy...@gmail.com wrote:
 Hi Alex,

 What you are seeing is the i18n key name rather than the localized
 translation.  If you have a locale other than en_US or ja_JP, it's
 supposed to map the locale to en_US, and look up the English text.  If
 it can't find the key even then, it will render the key name instead.

 The same issue you have seen has been reported before but it's been
 impossible for me to reproduce.  I've been using an add-on in Firefox
 which allows me to set the locale but it doesn't fail for me no matter
 what locale I select.  However, in Italy apparently the same thing
 happened on one machine as is now happening for you.  We presumed that
 the setup must be broken on the Italian machine that was exhibiting
 the problem, apparently incorrectly.

 The other weird thing is that apparently only *some* fields have a
 problem and the others are OK.  The code, though, for rendering all
 the fields is, however, identical.

 Any help or research you want to do would be very very welcome given
 the bizarre nature of the issue.

 Karl

 On Fri, Apr 6, 2012 at 6:59 AM, Alex Ott alex...@gmail.com wrote:
 I downloaded binary .tar.gz, unpacked, checked md5 sum - everything is 
 correct

 There is small error in README, it says that user need to switch to
 dist/example directory, while there is only example directory

 I run start.jar, and able to login to GUI, but in many places I see
 listconnections.ListOfRepositoryConnections instead of real text

 On Fri, Apr 6, 2012 at 3:25 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC5/
 and there is also a tag

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC5


 On Fri, Apr 6, 2012 at 3:25 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC5/
 and there is also a tag in svn under
 https://svn.apache.org/repos/asf/incubator/lcf/tags.

 Thank you,
 Shinichiro Abe



 --
 With best wishes,                    Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott



 --
 With best wishes,                    Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott



 --
 With best wishes,                    Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC5

 to
 dist/example directory, while there is only example directory

 I run start.jar, and able to login to GUI, but in many places I see
 listconnections.ListOfRepositoryConnections instead of real text

 On Fri, Apr 6, 2012 at 3:25 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC5/
 and there is also a tag in svn under
 https://svn.apache.org/repos/asf/incubator/lcf/tags.

 Thank you,
 Shinichiro Abe



 --
 With best wishes,                    Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott



 --
 With best wishes,                    Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott



 --
 With best wishes,                    Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC5

 downloaded binary .tar.gz, unpacked, checked md5 sum - everything 
 is correct

 There is small error in README, it says that user need to switch to
 dist/example directory, while there is only example directory

 I run start.jar, and able to login to GUI, but in many places I see
 listconnections.ListOfRepositoryConnections instead of real text

 On Fri, Apr 6, 2012 at 3:25 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC5/
 and there is also a tag in svn under
 https://svn.apache.org/repos/asf/incubator/lcf/tags.

 Thank you,
 Shinichiro Abe



 --
 With best wishes,                    Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott



 --
 With best wishes,                    Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott



 --
 With best wishes,                    Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott



-- 
With best wishes,                    Alex Ott
http://alexott.net/
Tiwtter: alexott_en (English), alexott (Russian)
Skype: alex.ott

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC5

 .tar.gz, unpacked, checked md5 sum - everything 
 is correct

 There is small error in README, it says that user need to switch to
 dist/example directory, while there is only example directory

 I run start.jar, and able to login to GUI, but in many places I see
 listconnections.ListOfRepositoryConnections instead of real text

 On Fri, Apr 6, 2012 at 3:25 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC5/
 and there is also a tag in svn under
 https://svn.apache.org/repos/asf/incubator/lcf/tags.

 Thank you,
 Shinichiro Abe



 --
 With best wishes,                    Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott



 --
 With best wishes,                    Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott



 --
 With best wishes,                    Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott



-- 
With best wishes,                    Alex Ott
http://alexott.net/
Tiwtter: alexott_en (English), alexott (Russian)
Skype: alex.ott

[VOTE] Release ManifoldCF 0.5-incubating, RC4

Hi, 

You can download the release candidate from
http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC4/
and there is also a tag in svn
under https://svn.apache.org/repos/asf/incubator/lcf/tags.

RC4 fixed CONNECTORS-441 to CONNECTORS-448.

Thank you,
Shinichiro Abe

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC4

2012-04-05 Thread Alex Ott

Hi Shinichiro

what tool are you using to create md5 files? Can you make these files
compatible with md5sum -c ?

On Thu, Apr 5, 2012 at 12:10 PM, Shinichiro Abe
shinichiro.ab...@gmail.com wrote:
 Hi,

 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC4/
 and there is also a tag in svn
 under https://svn.apache.org/repos/asf/incubator/lcf/tags.

 RC4 fixed CONNECTORS-441 to CONNECTORS-448.

 Thank you,
 Shinichiro Abe



-- 
With best wishes,                    Alex Ott
http://alexott.net/
Tiwtter: alexott_en (English), alexott (Russian)
Skype: alex.ott

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC4

Hi, Alex

I use gnupg 1.4.12(gnupg-w32cli-1.4.12.exe).
I've checked checksum by command openssl md5.
But sorry, I don't know if it can be compatible with md5sum.

Shinichiro  

On 2012/04/05, at 20:18, Alex Ott wrote:

 Hi Shinichiro
 
 what tool are you using to create md5 files? Can you make these files
 compatible with md5sum -c ?
 
 On Thu, Apr 5, 2012 at 12:10 PM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 Hi,
 
 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC4/
 and there is also a tag in svn
 under https://svn.apache.org/repos/asf/incubator/lcf/tags.
 
 RC4 fixed CONNECTORS-441 to CONNECTORS-448.
 
 Thank you,
 Shinichiro Abe
 
 
 
 -- 
 With best wishes,Alex Ott
 http://alexott.net/
 Tiwtter: alexott_en (English), alexott (Russian)
 Skype: alex.ott

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC4

Found a technical problem already.  The mvn-bootstrap scripts are no
longer correct; they invoke the wrong ant target.  CONNECTORS-451.
This may not be a serious enough problem for a respin, but if we
respin for another reason I think we should pull up the fix.  Any
disagreement?

Karl


On Thu, Apr 5, 2012 at 6:10 AM, Shinichiro Abe
shinichiro.ab...@gmail.com wrote:
 Hi,

 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC4/
 and there is also a tag in svn
 under https://svn.apache.org/repos/asf/incubator/lcf/tags.

 RC4 fixed CONNECTORS-441 to CONNECTORS-448.

 Thank you,
 Shinichiro Abe

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC4

Found what I think is a blocker.  CONNECTORS-452.

Karl

On Thu, Apr 5, 2012 at 8:45 AM, Karl Wright daddy...@gmail.com wrote:
 Found a technical problem already.  The mvn-bootstrap scripts are no
 longer correct; they invoke the wrong ant target.  CONNECTORS-451.
 This may not be a serious enough problem for a respin, but if we
 respin for another reason I think we should pull up the fix.  Any
 disagreement?

 Karl


 On Thu, Apr 5, 2012 at 6:10 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 Hi,

 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC4/
 and there is also a tag in svn
 under https://svn.apache.org/repos/asf/incubator/lcf/tags.

 RC4 fixed CONNECTORS-441 to CONNECTORS-448.

 Thank you,
 Shinichiro Abe

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC4

Pulled up a fix.  Looks like we'll need another RC - but first let's
wait for feedback from the incubator about the legal
license/notice/etc files.

Karl

On Thu, Apr 5, 2012 at 1:16 PM, Karl Wright daddy...@gmail.com wrote:
 Found what I think is a blocker.  CONNECTORS-452.

 Karl

 On Thu, Apr 5, 2012 at 8:45 AM, Karl Wright daddy...@gmail.com wrote:
 Found a technical problem already.  The mvn-bootstrap scripts are no
 longer correct; they invoke the wrong ant target.  CONNECTORS-451.
 This may not be a serious enough problem for a respin, but if we
 respin for another reason I think we should pull up the fix.  Any
 disagreement?

 Karl


 On Thu, Apr 5, 2012 at 6:10 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 Hi,

 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC4/
 and there is also a tag in svn
 under https://svn.apache.org/repos/asf/incubator/lcf/tags.

 RC4 fixed CONNECTORS-441 to CONNECTORS-448.

 Thank you,
 Shinichiro Abe

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC4

I haven't heard anything back from the incubator folks, but I did find
and pull up fixes to two blocking tickets.  So I suggest we withdraw
RC4 and build RC5, and call the vote.

Thanks,
Karl

On Thu, Apr 5, 2012 at 1:42 PM, Karl Wright daddy...@gmail.com wrote:
 Pulled up a fix.  Looks like we'll need another RC - but first let's
 wait for feedback from the incubator about the legal
 license/notice/etc files.

 Karl

 On Thu, Apr 5, 2012 at 1:16 PM, Karl Wright daddy...@gmail.com wrote:
 Found what I think is a blocker.  CONNECTORS-452.

 Karl

 On Thu, Apr 5, 2012 at 8:45 AM, Karl Wright daddy...@gmail.com wrote:
 Found a technical problem already.  The mvn-bootstrap scripts are no
 longer correct; they invoke the wrong ant target.  CONNECTORS-451.
 This may not be a serious enough problem for a respin, but if we
 respin for another reason I think we should pull up the fix.  Any
 disagreement?

 Karl


 On Thu, Apr 5, 2012 at 6:10 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 Hi,

 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC4/
 and there is also a tag in svn
 under https://svn.apache.org/repos/asf/incubator/lcf/tags.

 RC4 fixed CONNECTORS-441 to CONNECTORS-448.

 Thank you,
 Shinichiro Abe

[WITHDRAW][VOTE] Release ManifoldCF 0.5-incubating, RC4

We withdraw RC4 and I'll create RC5 today.

Shinichiro Abe

On 2012/04/06, at 7:41, Karl Wright wrote:

 I haven't heard anything back from the incubator folks, but I did find
 and pull up fixes to two blocking tickets.  So I suggest we withdraw
 RC4 and build RC5, and call the vote.
 
 Thanks,
 Karl
 
 On Thu, Apr 5, 2012 at 1:42 PM, Karl Wright daddy...@gmail.com wrote:
 Pulled up a fix.  Looks like we'll need another RC - but first let's
 wait for feedback from the incubator about the legal
 license/notice/etc files.
 
 Karl
 
 On Thu, Apr 5, 2012 at 1:16 PM, Karl Wright daddy...@gmail.com wrote:
 Found what I think is a blocker.  CONNECTORS-452.
 
 Karl
 
 On Thu, Apr 5, 2012 at 8:45 AM, Karl Wright daddy...@gmail.com wrote:
 Found a technical problem already.  The mvn-bootstrap scripts are no
 longer correct; they invoke the wrong ant target.  CONNECTORS-451.
 This may not be a serious enough problem for a respin, but if we
 respin for another reason I think we should pull up the fix.  Any
 disagreement?
 
 Karl
 
 
 On Thu, Apr 5, 2012 at 6:10 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 Hi,
 
 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC4/
 and there is also a tag in svn
 under https://svn.apache.org/repos/asf/incubator/lcf/tags.
 
 RC4 fixed CONNECTORS-441 to CONNECTORS-448.
 
 Thank you,
 Shinichiro Abe

[VOTE] Release ManifoldCF 0.5-incubating, RC5

You can download the release candidate from
http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC5/
and there is also a tag in svn under 
https://svn.apache.org/repos/asf/incubator/lcf/tags.

Thank you,
Shinichiro Abe

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC5

Thanks, Abe-san, for doing this yet again.  I'll download the RC now.

Karl

On Thu, Apr 5, 2012 at 9:25 PM, Shinichiro Abe
shinichiro.ab...@gmail.com wrote:
 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC5/
 and there is also a tag in svn under
 https://svn.apache.org/repos/asf/incubator/lcf/tags.

 Thank you,
 Shinichiro Abe

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC5

Downloaded it, ran the binary using PostgreSQL, built it and ran the
derby and hsqldb tests.  All looks good (although I found a minor i18n
error in the UI).  +1 from me.

Karl

On Thu, Apr 5, 2012 at 9:32 PM, Karl Wright daddy...@gmail.com wrote:
 Thanks, Abe-san, for doing this yet again.  I'll download the RC now.

 Karl

 On Thu, Apr 5, 2012 at 9:25 PM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC5/
 and there is also a tag in svn under
 https://svn.apache.org/repos/asf/incubator/lcf/tags.

 Thank you,
 Shinichiro Abe

[WITHDRAW][VOTE] Release ManifoldCF 0.5-incubating, RC3

2012-04-04 Thread Shinichiro Abe

I'll create RC4 tomorrow.

Shinichiro Abe

On 2012/04/03, at 23:38, Karl Wright wrote:

 Update: I'm just about ready to ask for a new RC that contains the following:
 
 - No checked-in binaries at all
 - A new XXX-lib target just containing license files and binaries
 - Patched jars built on the fly from patch files included in the
 source distribution
 
 In order to make all this work, the ant build has been extended with
 the following targets, which replace download-dependencies:
 
 make-core-deps (downloads and/or builds dependent jars and puts them in lib)
 make-deps (downloads proprietary jars)
 
 Thus, to build from source, you need to either:
 
 (1) Unpack source tar, unpack lib tar, and run ant build, or
 optionally ant make-deps build
 (2) Unpack source tar, run ant make-core-deps, and then either ant
 build or ant make-deps build
 
 If the make-core-deps target is objectionable, I can of course remove
 it from ant help so it is hidden.  It's essential, though, for release
 engineering purposes.
 
 Karl
 
 On Mon, Apr 2, 2012 at 5:25 PM, Karl Wright daddy...@gmail.com wrote:
 If this is the next thing the community wants to try, I won't stand in
 the way.  I just got the impression that there's more wrong with our
 build than just including dependent binaries - we also have problems
 with the dependent binaries themselves in some cases.
 
 Nevertheless, should I call a vote on (say) reverting to RC1 and
 applying the stated shell commands to the resulting artifacts?  The
 commands should also include .wsp files as well as jars, but that is a
 minor issue.
 
 Karl
 
 
 On Mon, Apr 2, 2012 at 3:42 PM, Jukka Zitting jukka.zitt...@gmail.com 
 wrote:
 Hi,
 
 On Mon, Apr 2, 2012 at 8:15 PM, Karl Wright daddy...@gmail.com wrote:
 Possible solutions include:
 
 There's also the alternative that I brought up earlier:
 
 (5) Extract all dependencies from the existing pre-CONNECTORS-437
 source tree to a separate -lib package like this:
 
$ tar zxf apache-manifoldcf-0.5-incubating-src.tar.gz
$ find apache-manifoldcf-0.5-incubating -type f -name '*.jar'  lib.txt
$ echo apache-manifoldcf-0.5-incubating/LICENSE.txt  lib.txt
$ echo apache-manifoldcf-0.5-incubating/NOTICE.txt  lib.txt
$ tar zcf apache-manifoldcf-0.5-incubating-lib.tar.gz -T lib.txt
 
 We can then publish that -lib package along with the official source
 release and include build instructions like the following:
 
$ tar zxf apache-manifoldcf-0.5-incubating-src.tar.gz
$ tar zxf apache-manifoldcf-0.5-incubating-lib.tar.gz
$ cd apache-manifoldcf-0.5-incubating
$ ant build
 
 That gives us something that's immediately releasable even with the
 newly reinterpreted Apache rules. And it gives us more time and
 breathing room for following up on the various improvement ideas that
 in terms of simplifying the build and the way dependencies are handled
 would make sense even regardless of policy requirements.
 
 BR,
 
 Jukka Zitting

[jira] [Commented] (CONNECTORS-443) All patched jars must be built within ManifoldCF release process

2012-04-03 Thread Piergiorgio Lucidi (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13245062#comment-13245062
 ] 

Piergiorgio Lucidi commented on CONNECTORS-443:
---

Here the two dependencies URLs for the Alfresco Connector that are not in 
public Maven repositories:

* 
http://svn.alfresco.com/repos/alfresco-open-mirror/alfresco/HEAD/root/projects/3rd-party/lib/wss4j-1.5.4-patched.jar
* 
http://svn.alfresco.com/repos/alfresco-open-mirror/alfresco/HEAD/root/projects/3rd-party/lib/opensaml-1.0.1.jar

 All patched jars must be built within ManifoldCF release process
 

 Key: CONNECTORS-443
 URL: https://issues.apache.org/jira/browse/CONNECTORS-443
 Project: ManifoldCF
  Issue Type: Task
  Components: Build
Affects Versions: ManifoldCF 0.5
Reporter: Karl Wright
Assignee: Karl Wright
Priority: Blocker
 Fix For: ManifoldCF 0.5


 Downloading already-built patched jars is not permissible within Apache any 
 longer.  The fix to this will entail downloading source and patching that as 
 part of the build process.  In order for the build process to succeed on 
 Windows, this currently means that the sources must be checked out using svn.
 The following changes will therefore need to occur under this ticket:
 (1) Apache binaries that are available as releases but which are not in Maven 
 should be downloaded and unpacked from http://archive.apache.org/dist.  This 
 will include the solr and sharepoint mcf plugins.
 (2) The download-dependencies target must be split into 
 download-dependencies and download-proprietary-dependencies.  The 
 download-dependencies target will become responsible for downloading, 
 patching, and building the non-proprietary packages.  Packages that will need 
 to be checked out by this target from svn include: httpclient 3.1, xerces 
 2.9.1, hsqldb 2.2.8, and jetty 6.1.26.
 (3) A new release artifact, XXX-dep.zip/tar.gz, will be produced which will 
 contain all the dependency binaries.
 (4) Any non-sourceable dependency binaries we find must be replaced with a 
 sourced equivalent, or code for it developed from scratch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-443) All patched jars must be built within ManifoldCF release process

2012-04-03 Thread Piergiorgio Lucidi (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13245094#comment-13245094
 ] 

Piergiorgio Lucidi commented on CONNECTORS-443:
---

Here xmlsec:
* 
http://svn.alfresco.com/repos/alfresco-open-mirror/alfresco/HEAD/root/projects/3rd-party/lib/xmlsec-1.4.1.jar

 All patched jars must be built within ManifoldCF release process
 

 Key: CONNECTORS-443
 URL: https://issues.apache.org/jira/browse/CONNECTORS-443
 Project: ManifoldCF
  Issue Type: Task
  Components: Build
Affects Versions: ManifoldCF 0.5
Reporter: Karl Wright
Assignee: Karl Wright
Priority: Blocker
 Fix For: ManifoldCF 0.5


 Downloading already-built patched jars is not permissible within Apache any 
 longer.  The fix to this will entail downloading source and patching that as 
 part of the build process.  In order for the build process to succeed on 
 Windows, this currently means that the sources must be checked out using svn.
 The following changes will therefore need to occur under this ticket:
 (1) Apache binaries that are available as releases but which are not in Maven 
 should be downloaded and unpacked from http://archive.apache.org/dist.  This 
 will include the solr and sharepoint mcf plugins.
 (2) The download-dependencies target must be split into 
 download-dependencies and download-proprietary-dependencies.  The 
 download-dependencies target will become responsible for downloading, 
 patching, and building the non-proprietary packages.  Packages that will need 
 to be checked out by this target from svn include: httpclient 3.1, xerces 
 2.9.1, hsqldb 2.2.8, and jetty 6.1.26.
 (3) A new release artifact, XXX-dep.zip/tar.gz, will be produced which will 
 contain all the dependency binaries.
 (4) Any non-sourceable dependency binaries we find must be replaced with a 
 sourced equivalent, or code for it developed from scratch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-443) All patched jars must be built within ManifoldCF release process

2012-04-03 Thread Piergiorgio Lucidi (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13245107#comment-13245107
 ] 

Piergiorgio Lucidi commented on CONNECTORS-443:
---

Here the dependencies for H2 support:
* http://clojars.org/repo/it/sk/alfresco/h2-support/1.1/h2-support-1.1.jar
* http://repo2.maven.org/maven2/com/h2database/h2/1.3.158/h2-1.3.158.jar

 All patched jars must be built within ManifoldCF release process
 

 Key: CONNECTORS-443
 URL: https://issues.apache.org/jira/browse/CONNECTORS-443
 Project: ManifoldCF
  Issue Type: Task
  Components: Build
Affects Versions: ManifoldCF 0.5
Reporter: Karl Wright
Assignee: Karl Wright
Priority: Blocker
 Fix For: ManifoldCF 0.5


 Downloading already-built patched jars is not permissible within Apache any 
 longer.  The fix to this will entail downloading source and patching that as 
 part of the build process.  In order for the build process to succeed on 
 Windows, this currently means that the sources must be checked out using svn.
 The following changes will therefore need to occur under this ticket:
 (1) Apache binaries that are available as releases but which are not in Maven 
 should be downloaded and unpacked from http://archive.apache.org/dist.  This 
 will include the solr and sharepoint mcf plugins.
 (2) The download-dependencies target must be split into 
 download-dependencies and download-proprietary-dependencies.  The 
 download-dependencies target will become responsible for downloading, 
 patching, and building the non-proprietary packages.  Packages that will need 
 to be checked out by this target from svn include: httpclient 3.1, xerces 
 2.9.1, hsqldb 2.2.8, and jetty 6.1.26.
 (3) A new release artifact, XXX-dep.zip/tar.gz, will be produced which will 
 contain all the dependency binaries.
 (4) Any non-sourceable dependency binaries we find must be replaced with a 
 sourced equivalent, or code for it developed from scratch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-443) All patched jars must be built within ManifoldCF release process

2012-04-03 Thread Piergiorgio Lucidi (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13245131#comment-13245131
]

Piergiorgio Lucidi commented on CONNECTORS-443:
---

Another here:
*
http://repo1.maven.org/maven2/org/apache/felix/org.osgi.core/1.0.0/org.osgi.core-1.0.0.jar

All patched jars must be built within ManifoldCF release process

Key: CONNECTORS-443
URL: https://issues.apache.org/jira/browse/CONNECTORS-443
Project: ManifoldCF
Issue Type: Task
Components: Build
Affects Versions: ManifoldCF 0.5
Reporter: Karl Wright
Assignee: Karl Wright
Priority: Blocker
Fix For: ManifoldCF 0.5

Downloading already-built patched jars is not permissible within Apache any
longer. The fix to this will entail downloading source and patching that as
part of the build process. In order for the build process to succeed on
Windows, this currently means that the sources must be checked out using svn.
The following changes will therefore need to occur under this ticket:
(1) Apache binaries that are available as releases but which are not in Maven
should be downloaded and unpacked from http://archive.apache.org/dist. This
will include the solr and sharepoint mcf plugins.
(2) The download-dependencies target must be split into
download-dependencies and download-proprietary-dependencies. The
download-dependencies target will become responsible for downloading,
patching, and building the non-proprietary packages. Packages that will need
to be checked out by this target from svn include: httpclient 3.1, xerces
2.9.1, hsqldb 2.2.8, and jetty 6.1.26.
(3) A new release artifact, XXX-dep.zip/tar.gz, will be produced which will
contain all the dependency binaries.
(4) Any non-sourceable dependency binaries we find must be replaced with a
sourced equivalent, or code for it developed from scratch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-443) All patched jars must be built within ManifoldCF release process

2012-04-03 Thread Karl Wright (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13245258#comment-13245258
]

Karl Wright commented on CONNECTORS-443:

Thanks to Piergiorgio, all downloads are now taken care of, so no Apache
resource other than Maven is accessed when grabbing the dependent jars. The
one exception is building the patched xerces and commons-httpclient jars, which
check these projects out from tags in order to build.

If tests pass, we may be ready for the next 0.5-incubating RC.

All patched jars must be built within ManifoldCF release process

[jira] [Resolved] (CONNECTORS-443) All patched jars must be built within ManifoldCF release process

2012-04-03 Thread Karl Wright (Resolved) (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl Wright resolved CONNECTORS-443.

Resolution: Fixed

All patched jars must be built within ManifoldCF release process

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC3

2012-04-03 Thread Karl Wright

Update: I'm just about ready to ask for a new RC that contains the following:

- No checked-in binaries at all
- A new XXX-lib target just containing license files and binaries
- Patched jars built on the fly from patch files included in the
source distribution

In order to make all this work, the ant build has been extended with
the following targets, which replace download-dependencies:

make-core-deps (downloads and/or builds dependent jars and puts them in lib)
make-deps (downloads proprietary jars)

Thus, to build from source, you need to either:

(1) Unpack source tar, unpack lib tar, and run ant build, or
optionally ant make-deps build
(2) Unpack source tar, run ant make-core-deps, and then either ant
build or ant make-deps build

If the make-core-deps target is objectionable, I can of course remove
it from ant help so it is hidden.  It's essential, though, for release
engineering purposes.

Karl

On Mon, Apr 2, 2012 at 5:25 PM, Karl Wright daddy...@gmail.com wrote:
 If this is the next thing the community wants to try, I won't stand in
 the way.  I just got the impression that there's more wrong with our
 build than just including dependent binaries - we also have problems
 with the dependent binaries themselves in some cases.

 Nevertheless, should I call a vote on (say) reverting to RC1 and
 applying the stated shell commands to the resulting artifacts?  The
 commands should also include .wsp files as well as jars, but that is a
 minor issue.

 Karl


 On Mon, Apr 2, 2012 at 3:42 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 Hi,

 On Mon, Apr 2, 2012 at 8:15 PM, Karl Wright daddy...@gmail.com wrote:
 Possible solutions include:

 There's also the alternative that I brought up earlier:

 (5) Extract all dependencies from the existing pre-CONNECTORS-437
 source tree to a separate -lib package like this:

    $ tar zxf apache-manifoldcf-0.5-incubating-src.tar.gz
    $ find apache-manifoldcf-0.5-incubating -type f -name '*.jar'  lib.txt
    $ echo apache-manifoldcf-0.5-incubating/LICENSE.txt  lib.txt
    $ echo apache-manifoldcf-0.5-incubating/NOTICE.txt  lib.txt
    $ tar zcf apache-manifoldcf-0.5-incubating-lib.tar.gz -T lib.txt

 We can then publish that -lib package along with the official source
 release and include build instructions like the following:

    $ tar zxf apache-manifoldcf-0.5-incubating-src.tar.gz
    $ tar zxf apache-manifoldcf-0.5-incubating-lib.tar.gz
    $ cd apache-manifoldcf-0.5-incubating
    $ ant build

 That gives us something that's immediately releasable even with the
 newly reinterpreted Apache rules. And it gives us more time and
 breathing room for following up on the various improvement ideas that
 in terms of simplifying the build and the way dependencies are handled
 would make sense even regardless of policy requirements.

 BR,

 Jukka Zitting

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC2

Ok, should be fixed.

Karl


On Mon, Apr 2, 2012 at 5:18 AM, Karl Wright daddy...@gmail.com wrote:
 Those files should not be there; it's probably a result of a missing
 exclude in the build.xml.  I'll open a ticket and look at it.

 Thanks!
 Karl


 On Mon, Apr 2, 2012 at 12:53 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 I found jar files in -src.zip and -src.tar.gz

 ./connectors/solr/integration/mcf-solr-3.x-plugin.jar
 ./connectors/solr/integration/mcf-solr-4.x-plugin.jar

 Should these files be removed?

 Shinichiro Abe

 On 2012/04/02, at 13:10, Shinichiro Abe wrote:

 Hi,

 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC2/
 and there is also a tag in svn
 under https://svn.apache.org/repos/asf/incubator/lcf/tags.

 RC2 fixed the following issues:
 CONNECTORS-437: Change the ant jar distribution model so that no
 binary files are included in the source distribution.  All of them are now
 downloaded via the ant download-dependencies target.

 I've already checked signatures.

 Thank you,
 Shinichiro Abe

[CANCEL][VOTE] Release ManifoldCF 0.5-incubating, RC2

2012-04-02 Thread Shinichiro Abe

Thank you.
I'm going to create RC3.

Shinichiro Abe
 
On 2012/04/02, at 18:27, Karl Wright wrote:

 Ok, should be fixed.
 
 Karl
 
 
 On Mon, Apr 2, 2012 at 5:18 AM, Karl Wright daddy...@gmail.com wrote:
 Those files should not be there; it's probably a result of a missing
 exclude in the build.xml.  I'll open a ticket and look at it.
 
 Thanks!
 Karl
 
 
 On Mon, Apr 2, 2012 at 12:53 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 I found jar files in -src.zip and -src.tar.gz
 
 ./connectors/solr/integration/mcf-solr-3.x-plugin.jar
 ./connectors/solr/integration/mcf-solr-4.x-plugin.jar
 
 Should these files be removed?
 
 Shinichiro Abe
 
 On 2012/04/02, at 13:10, Shinichiro Abe wrote:
 
 Hi,
 
 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC2/
 and there is also a tag in svn
 under https://svn.apache.org/repos/asf/incubator/lcf/tags.
 
 RC2 fixed the following issues:
 CONNECTORS-437: Change the ant jar distribution model so that no
 binary files are included in the source distribution.  All of them are now
 downloaded via the ant download-dependencies target.
 
 I've already checked signatures.
 
 Thank you,
 Shinichiro Abe

[VOTE] Release ManifoldCF 0.5-incubating, RC3

2012-04-02 Thread Shinichiro Abe

Hi, 

You can download the release candidate from
http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC3/
and there is also a tag in svn
under https://svn.apache.org/repos/asf/incubator/lcf/tags.

RC3 fixed the following issues:
CONNECTORS-440: Build should exclude integration content from external
sources.

Thank you,
Shinichiro Abe

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC3

2012-04-02 Thread Shinichiro Abe

+1 from me
 
I've already checked signatures.

Shinichiro Abe

On 2012/04/02, at 20:07, Shinichiro Abe wrote:

 Hi, 
 
 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC3/
 and there is also a tag in svn
 under https://svn.apache.org/repos/asf/incubator/lcf/tags.
 
 RC3 fixed the following issues:
 CONNECTORS-440: Build should exclude integration content from external
 sources.
 
 Thank you,
 Shinichiro Abe

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC3

Hi Abe-san,

The bin packages look much smaller than the ones I built here when I
was testing things out.  Did you remember to include the proprietary
materials before you built the RC?

I'm about to unpack the bin.zip to see if my suspicion is warranted...

Karl

On Mon, Apr 2, 2012 at 7:07 AM, Shinichiro Abe
shinichiro.ab...@gmail.com wrote:
 Hi,

 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC3/
 and there is also a tag in svn
 under https://svn.apache.org/repos/asf/incubator/lcf/tags.

 RC3 fixed the following issues:
 CONNECTORS-440: Build should exclude integration content from external
 sources.

 Thank you,
 Shinichiro Abe

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC3

At first glance it looks like the bin packages are complete;
apparently I must have inadvertantly included something else in my bin
packages when I built them (they were 175M each).  Trying it out
now...

Karl


On Mon, Apr 2, 2012 at 8:05 AM, Karl Wright daddy...@gmail.com wrote:
 Hi Abe-san,

 The bin packages look much smaller than the ones I built here when I
 was testing things out.  Did you remember to include the proprietary
 materials before you built the RC?

 I'm about to unpack the bin.zip to see if my suspicion is warranted...

 Karl

 On Mon, Apr 2, 2012 at 7:07 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 Hi,

 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC3/
 and there is also a tag in svn
 under https://svn.apache.org/repos/asf/incubator/lcf/tags.

 RC3 fixed the following issues:
 CONNECTORS-440: Build should exclude integration content from external
 sources.

 Thank you,
 Shinichiro Abe

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC3

I checked out the bin.zip package; all looked good.  I opened one
ticket about a minor problem (CONNECTORS-442) which is that the bin
packages include ant and maven build scripts, but that's not enough to
block release.

The only other potential problem is that the
license/notice/dependencies files may not conform strictly to
incubator guidelines.  Specifically, we are not including a different
set of files with a bin release vs. a source release, and also it was
unclear whether our format (which was once again based on Lucene/Solr)
is still acceptable or not.  The thread in general@i.a.o provided some
examples, but it is not clear whether those were the ONLY acceptable
formats.  I am hoping for Jukka and Tommaso's feedback here before we
present this artifact to the incubator.

Otherwise, +1 from me.

Karl


On Mon, Apr 2, 2012 at 8:12 AM, Karl Wright daddy...@gmail.com wrote:
 At first glance it looks like the bin packages are complete;
 apparently I must have inadvertantly included something else in my bin
 packages when I built them (they were 175M each).  Trying it out
 now...

 Karl


 On Mon, Apr 2, 2012 at 8:05 AM, Karl Wright daddy...@gmail.com wrote:
 Hi Abe-san,

 The bin packages look much smaller than the ones I built here when I
 was testing things out.  Did you remember to include the proprietary
 materials before you built the RC?

 I'm about to unpack the bin.zip to see if my suspicion is warranted...

 Karl

 On Mon, Apr 2, 2012 at 7:07 AM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
 Hi,

 You can download the release candidate from
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC3/
 and there is also a tag in svn
 under https://svn.apache.org/repos/asf/incubator/lcf/tags.

 RC3 fixed the following issues:
 CONNECTORS-440: Build should exclude integration content from external
 sources.

 Thank you,
 Shinichiro Abe

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC3

2012-04-02 Thread Jukka Zitting

Hi,

On Mon, Apr 2, 2012 at 2:31 PM, Karl Wright daddy...@gmail.com wrote:
 The only other potential problem is that the
 license/notice/dependencies files may not conform strictly to
 incubator guidelines.  Specifically, we are not including a different
 set of files with a bin release vs. a source release, and also it was
 unclear whether our format (which was once again based on Lucene/Solr)
 is still acceptable or not.  The thread in general@i.a.o provided some
 examples, but it is not clear whether those were the ONLY acceptable
 formats.  I am hoping for Jukka and Tommaso's feedback here before we
 present this artifact to the incubator.

Ideally the licensing metadata (i.e. the LICENSE and NOTICE files)
should only cover material contained in that specific package. See [1]
 for a related discussion from a few years ago. At least back then it
seemed acceptable for a project to also only maintain a single set of
license metadata that covers the contents of both source and binary
distributions. AFAIUI that approach is in use by many Apache projects.

About the RC more generally, I find the download-via-svn target a bit
troublesome as it makes the release depend on content in svn. That
essentially turns the svn server into a release distribution channel,
which it definitely shouldn't be.

I think it's fine to manage the set of binary dependencies (that
aren't available in a stable third party location like Maven Central)
in svn, but a release should not try to access them from there.
Instead we should for example package them up in a separate -lib or
-deps archive and make it available for download along with the source
release through the standard Apache mirroring network. That archive
should also come with appropriate licensing metadata that's currently
lacking in bin-dist.

[1] http://markmail.org/message/bttmkavpicxxg7gl

BR,

Jukka Zitting

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC3

My major concern with the release of binaries through the standard
Apache channel is that we then effectively have another release that
must be synchronized with the main release, since the non-maven
binaries are not, by definition, part of the main release.

I set bin-dist up with that in mind, so that it can effectively remain
unversioned, and be add only.

If there is no other choice than parallel releases of binaries and
source, with a separation of binaries and source in the svn tree, then
I will have to think through the best solution.  Certainly we will
have to treat binaries from different sources differently.  For
example, all of the following would potentially need a different
solution:

(1) Stuff that's available from maven that is license-compatible with Apache
(2) Stuff that's available from maven that is NOT license-compatible with Apache
(3) Stuff that's not available from maven that is license-compatible with Apache
(4) Stuff that's not available from maven that is not
license-compatible with Apache

We could not package dependencies that are (2) or (4).  We would
*have* to package (3), but not necessarily (1).

Is this making your head spin yet?  Mine is...

An svn-based download is technically little different than a source
checkout, seems to me, which is why I wonder why we would make a
distinction at all.

Karl





On Mon, Apr 2, 2012 at 9:49 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 Hi,

 On Mon, Apr 2, 2012 at 2:31 PM, Karl Wright daddy...@gmail.com wrote:
 The only other potential problem is that the
 license/notice/dependencies files may not conform strictly to
 incubator guidelines.  Specifically, we are not including a different
 set of files with a bin release vs. a source release, and also it was
 unclear whether our format (which was once again based on Lucene/Solr)
 is still acceptable or not.  The thread in general@i.a.o provided some
 examples, but it is not clear whether those were the ONLY acceptable
 formats.  I am hoping for Jukka and Tommaso's feedback here before we
 present this artifact to the incubator.

 Ideally the licensing metadata (i.e. the LICENSE and NOTICE files)
 should only cover material contained in that specific package. See [1]
  for a related discussion from a few years ago. At least back then it
 seemed acceptable for a project to also only maintain a single set of
 license metadata that covers the contents of both source and binary
 distributions. AFAIUI that approach is in use by many Apache projects.

 About the RC more generally, I find the download-via-svn target a bit
 troublesome as it makes the release depend on content in svn. That
 essentially turns the svn server into a release distribution channel,
 which it definitely shouldn't be.

 I think it's fine to manage the set of binary dependencies (that
 aren't available in a stable third party location like Maven Central)
 in svn, but a release should not try to access them from there.
 Instead we should for example package them up in a separate -lib or
 -deps archive and make it available for download along with the source
 release through the standard Apache mirroring network. That archive
 should also come with appropriate licensing metadata that's currently
 lacking in bin-dist.

 [1] http://markmail.org/message/bttmkavpicxxg7gl

 BR,

 Jukka Zitting

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC3

Hi folks,

As for the last pile of revisions, which download dependencies from
Maven or SVN depending, Jukka and I agreed that we'll also need either
a dependencies artifact or a source + dependencies artifact.  How we
get the dependencies in the first place, though, is still unclear, so
we decided to put the question to infrastruct...@apache.org to find
out their opinion of whether downloading binaries from svn was
acceptable.  I did not get a clear answer to that, but I can say the
following:

(1) There is a clear level of discomfort about storing ANY binaries in
apache infrastructure.
(2) For patched dependent releases, the recommended process is to
download source tar/zip, unpack it, apply patches, and build it, all
as part of the build process for the main release.
(3) For those releases that simply do not exist at all in Maven, the
ideal process is to download the sources and build them.

The problems, then, are as follows:

(1) ManifoldCF binary distributions include packages which can only be
built on specific architectures.  For example, the SharePoint 3.0 mcf
plugin.
(2) Patching of source cannot be done in a standard way on both
Windows and Linux, other than within an SVN checkout (via svn patch).
(3) There may be some binary dependencies whose sources are hard to
get hold of, e.g. jdbcpool-0.99.jar, which are also not found in
Maven.

Possible solutions include:

(1) Only patch sources that we can check out via svn.  This implies
that, during the build process, instead of checking out a single
binary, we check out an entire source tree.  Then we can apply the
patch.  Downside: svn access required during build.
(2) Remove the dependency on anything we find we can't get the sources
for, such as jdbcpool-0.99.  Downside: requires significant code
changes.
(3) Check in the binaries for all platform-dependent builds into
googlecode.  Downside: Not clear whether the Incubator will consider
this reasonable.
(4) Require that builds only take place on Windows machines with
appropriate Windows tools and upstream dependencies installed.
Downside: Essentially a non-starter.

Obviously all of this will greatly complicate the build and release
process for ManifoldCF, if indeed there is exists an acceptable
solution at all.  I honestly don't have a workable answer in mind at
this point for all of the new constraints we're dealing with.



Karl


On Mon, Apr 2, 2012 at 10:02 AM, Karl Wright daddy...@gmail.com wrote:
 My major concern with the release of binaries through the standard
 Apache channel is that we then effectively have another release that
 must be synchronized with the main release, since the non-maven
 binaries are not, by definition, part of the main release.

 I set bin-dist up with that in mind, so that it can effectively remain
 unversioned, and be add only.

 If there is no other choice than parallel releases of binaries and
 source, with a separation of binaries and source in the svn tree, then
 I will have to think through the best solution.  Certainly we will
 have to treat binaries from different sources differently.  For
 example, all of the following would potentially need a different
 solution:

 (1) Stuff that's available from maven that is license-compatible with Apache
 (2) Stuff that's available from maven that is NOT license-compatible with 
 Apache
 (3) Stuff that's not available from maven that is license-compatible with 
 Apache
 (4) Stuff that's not available from maven that is not
 license-compatible with Apache

 We could not package dependencies that are (2) or (4).  We would
 *have* to package (3), but not necessarily (1).

 Is this making your head spin yet?  Mine is...

 An svn-based download is technically little different than a source
 checkout, seems to me, which is why I wonder why we would make a
 distinction at all.

 Karl





 On Mon, Apr 2, 2012 at 9:49 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 Hi,

 On Mon, Apr 2, 2012 at 2:31 PM, Karl Wright daddy...@gmail.com wrote:
 The only other potential problem is that the
 license/notice/dependencies files may not conform strictly to
 incubator guidelines.  Specifically, we are not including a different
 set of files with a bin release vs. a source release, and also it was
 unclear whether our format (which was once again based on Lucene/Solr)
 is still acceptable or not.  The thread in general@i.a.o provided some
 examples, but it is not clear whether those were the ONLY acceptable
 formats.  I am hoping for Jukka and Tommaso's feedback here before we
 present this artifact to the incubator.

 Ideally the licensing metadata (i.e. the LICENSE and NOTICE files)
 should only cover material contained in that specific package. See [1]
  for a related discussion from a few years ago. At least back then it
 seemed acceptable for a project to also only maintain a single set of
 license metadata that covers the contents of both source and binary
 distributions. AFAIUI that approach is in use by many Apache projects

[jira] [Created] (CONNECTORS-443) All patched jars must be built within ManifoldCF release process

2012-04-02 Thread Karl Wright (Created) (JIRA)

All patched jars must be built within ManifoldCF release process


 Key: CONNECTORS-443
 URL: https://issues.apache.org/jira/browse/CONNECTORS-443
 Project: ManifoldCF
  Issue Type: Task
  Components: Build
Affects Versions: ManifoldCF 0.5
Reporter: Karl Wright
Assignee: Karl Wright
Priority: Blocker
 Fix For: ManifoldCF 0.5


Downloading already-built patched jars is not permissible within Apache any 
longer.  The fix to this will entail downloading source and patching that as 
part of the build process.  In order for the build process to succeed on 
Windows, this currently means that the sources must be checked out using svn.

The following changes will therefore need to occur under this ticket:

(1) Apache binaries that are available as releases but which are not in Maven 
should be downloaded and unpacked from http://archive.apache.org/dist.  This 
will include the solr and sharepoint mcf plugins.

(2) The download-dependencies target must be split into 
download-dependencies and download-proprietary-dependencies.  The 
download-dependencies target will become responsible for downloading, 
patching, and building the non-proprietary packages.  Packages that will need 
to be checked out by this target from svn include: httpclient 3.1, xerces 
2.9.1, hsqldb 2.2.8, and jetty 6.1.26.

(3) A new release artifact, XXX-dep.zip/tar.gz, will be produced which will 
contain all the dependency binaries.

(4) Any non-sourceable dependency binaries we find must be replaced with a 
sourced equivalent, or code for it developed from scratch.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-443) All patched jars must be built within ManifoldCF release process

2012-04-02 Thread Karl Wright (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13244493#comment-13244493
]

Karl Wright commented on CONNECTORS-443:

Another complication is other Apache Java projects which have patched jars in
their dependencies. Apache Chemistry has a couple, I believe, and we have a
CMIS connector.

All patched jars must be built within ManifoldCF release process

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC3

2012-04-02 Thread Jukka Zitting

Hi,

On Mon, Apr 2, 2012 at 8:15 PM, Karl Wright daddy...@gmail.com wrote:
 Possible solutions include:

There's also the alternative that I brought up earlier:

(5) Extract all dependencies from the existing pre-CONNECTORS-437
source tree to a separate -lib package like this:

$ tar zxf apache-manifoldcf-0.5-incubating-src.tar.gz
$ find apache-manifoldcf-0.5-incubating -type f -name '*.jar'  lib.txt
$ echo apache-manifoldcf-0.5-incubating/LICENSE.txt  lib.txt
$ echo apache-manifoldcf-0.5-incubating/NOTICE.txt  lib.txt
$ tar zcf apache-manifoldcf-0.5-incubating-lib.tar.gz -T lib.txt

We can then publish that -lib package along with the official source
release and include build instructions like the following:

$ tar zxf apache-manifoldcf-0.5-incubating-src.tar.gz
$ tar zxf apache-manifoldcf-0.5-incubating-lib.tar.gz
$ cd apache-manifoldcf-0.5-incubating
$ ant build

That gives us something that's immediately releasable even with the
newly reinterpreted Apache rules. And it gives us more time and
breathing room for following up on the various improvement ideas that
in terms of simplifying the build and the way dependencies are handled
would make sense even regardless of policy requirements.

BR,

Jukka Zitting

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC3