Re: [VOTE] Propose graduation of ManifoldCF from the Incubator as a Top Level Project
+1, although I'm not developer... On Tue, Apr 24, 2012 at 12:08 PM, Karl Wright daddy...@gmail.com wrote: Please vote +1 if you think we should propose to the Incubator that we graduate as a top level project at this time. If this vote passes, I will open a [DISCUSS] thread in gene...@incubator.apache.org, and turn it into a [VOTE] thread if the discussion looks positive. +1(binding) from me. Karl -- With best wishes, Alex Ott http://alexott.net/ Tiwtter: alexott_en (English), alexott (Russian) Skype: alex.ott
Re: [VOTE] Release ManifoldCF 0.5-incubating, RC6
I downloaded {bin,lib,src}.zip and chekced md5 checksums - everything ok
Binary from example directory works fine, localization issue is
fixed... But README.txt still mentions 'dist/example' instead of
'example'
+1 for release
On Mon, Apr 9, 2012 at 3:04 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-RC6/
and there is also a tag in svn under
https://svn.apache.org/repos/asf/incubator/lcf/tags.
I've checked the signatures and ran example.
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 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
I'll update trunk, and will check it - maybe half hour later On Fri, Apr 6, 2012 at 8:25 PM, Karl Wright daddy...@gmail.com wrote: Alex, if you would be willing to build from trunk and try it out on your machine, I'll be able to close the ticket. Karl On Fri, Apr 6, 2012 at 2:15 PM, Karl Wright daddy...@gmail.com wrote: Hi Alex, The logs did the trick; it was clear what was happening. I've checked in a fix to trunk, and I think we'll want to spin a new RC. Thanks! Karl On Fri, Apr 6, 2012 at 1:44 PM, Karl Wright daddy...@gmail.com wrote: 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
Re: [VOTE] Release ManifoldCF 0.5-incubating, RC5
Hi Karl Yes, this issue is fixed, thank you! On Fri, Apr 6, 2012 at 8:25 PM, Karl Wright daddy...@gmail.com wrote: Alex, if you would be willing to build from trunk and try it out on your machine, I'll be able to close the ticket. Karl On Fri, Apr 6, 2012 at 2:15 PM, Karl Wright daddy...@gmail.com wrote: Hi Alex, The logs did the trick; it was clear what was happening. I've checked in a fix to trunk, and I think we'll want to spin a new RC. Thanks! Karl On Fri, Apr 6, 2012 at 1:44 PM, Karl Wright daddy...@gmail.com wrote: 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
Re: [VOTE] Release ManifoldCF 0.5-incubating, RC4
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: apache-manifoldcf-0.5-incubating, RC0 available
I downloaded RC0 (tar.gz), and tried to use it. Here notes: - downloading of dependencies took some time (around 5 minutes) - I think is too long. most of time is spent downloading ipa fonts - .md5 file for .tar.gz wasn't accepted by 'md5sum -c' on debian linux, although checksum was correct - 'ant all' finished without errors; I'm able to start service and work withy GUI - running 'mvn clean install' lead to following error -- 1) xml-security:xmlsec:jar:1.4.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=xml-security -DartifactId=xmlsec -Dversion=1.4.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=xml-security -DartifactId=xmlsec -Dversion=1.4.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.manifoldcf:mcf-alfresco-connector:jar:0.5.0-SNAPSHOT 2) xml-security:xmlsec:jar:1.4.1 2) org.opensaml:opensaml:jar:1.0.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.opensaml -DartifactId=opensaml -Dversion=1.0.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.opensaml -DartifactId=opensaml -Dversion=1.0.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.manifoldcf:mcf-alfresco-connector:jar:0.5.0-SNAPSHOT 2) org.opensaml:opensaml:jar:1.0.1 -- 2 required artifacts are missing. for artifact: org.apache.manifoldcf:mcf-alfresco-connector:jar:0.5.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), central (http://repo1.maven.org/maven2), alfresco-public (http://maven.alfresco.com/nexus/content/groups/public), alfresco-public-snapshots (http://maven.alfresco.com/nexus/content/groups/public-snapshots), alfresco-maven-repo (http://maven.alfresco.com/nexus/content/groups/enterprise-snapshots) On Wed, Mar 21, 2012 at 11:43 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-RC0/ and there is also a tag in svn under https://svn.apache.org/repos/asf/incubator/lcf/tags. There have been a number of significant changes this release, and I have create the artifact for the first time, so I think it's a good idea if at least one other person has a thorough look at it. Shinichiro Abe -- With best wishes, Alex Ott http://alexott.net/ Tiwtter: alexott_en (English), alexott (Russian) Skype: alex.ott
Re: apache-manifoldcf-0.5-incubating, RC0 available
I unpacked archive once again, and now everything is built and tested without errors The only difference that I see right now, is that ant creates dist/example, while maven - not On Wed, Mar 21, 2012 at 2:46 PM, Karl Wright daddy...@gmail.com wrote: Can you post the failure please? Thanks! Karl On Wed, Mar 21, 2012 at 9:22 AM, Alex Ott alex...@gmail.com wrote: I run mvn-bootstrap.sh, it looks like something failed when it was executed, I'll try to make test from scratch On Wed, Mar 21, 2012 at 2:18 PM, Karl Wright daddy...@gmail.com wrote: Thanks for the review. First, let's talk about Maven. You will want to run mvn-bootstrap, which contains the following lines: cmd /c mvn install:install-file -Dfile=lib/opensaml-1.0.1.jar -DgroupId=org.opensaml -DartifactId=opensaml -Dversion=1.0.1 -Dpackaging=jar cmd /c mvn install:install-file -Dfile=lib/xmlsec-1.4.1.jar -DgroupId=xml-security -DartifactId=xmlsec -Dversion=1.4.1 -Dpackaging=jar Second, and download-dependencies is optional. If you do not run it, you will not get the site or some of the connectors, but that is the tradeoff. Thanks! Karl On Wed, Mar 21, 2012 at 9:14 AM, Alex Ott alex...@gmail.com wrote: I downloaded RC0 (tar.gz), and tried to use it. Here notes: - downloading of dependencies took some time (around 5 minutes) - I think is too long. most of time is spent downloading ipa fonts - .md5 file for .tar.gz wasn't accepted by 'md5sum -c' on debian linux, although checksum was correct - 'ant all' finished without errors; I'm able to start service and work withy GUI - running 'mvn clean install' lead to following error -- 1) xml-security:xmlsec:jar:1.4.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=xml-security -DartifactId=xmlsec -Dversion=1.4.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=xml-security -DartifactId=xmlsec -Dversion=1.4.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.manifoldcf:mcf-alfresco-connector:jar:0.5.0-SNAPSHOT 2) xml-security:xmlsec:jar:1.4.1 2) org.opensaml:opensaml:jar:1.0.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.opensaml -DartifactId=opensaml -Dversion=1.0.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.opensaml -DartifactId=opensaml -Dversion=1.0.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.manifoldcf:mcf-alfresco-connector:jar:0.5.0-SNAPSHOT 2) org.opensaml:opensaml:jar:1.0.1 -- 2 required artifacts are missing. for artifact: org.apache.manifoldcf:mcf-alfresco-connector:jar:0.5.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), central (http://repo1.maven.org/maven2), alfresco-public (http://maven.alfresco.com/nexus/content/groups/public), alfresco-public-snapshots (http://maven.alfresco.com/nexus/content/groups/public-snapshots), alfresco-maven-repo (http://maven.alfresco.com/nexus/content/groups/enterprise-snapshots) On Wed, Mar 21, 2012 at 11:43 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-RC0/ and there is also a tag in svn under https://svn.apache.org/repos/asf/incubator/lcf/tags. There have been a number of significant changes this release, and I have create the artifact for the first time, so I think it's a good idea if at least one other person has a thorough look at it. 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, RC0
+1 On Wed, Mar 21, 2012 at 6:24 PM, Karl Wright daddy...@gmail.com wrote: Calling the vote... while still waiting for verification of the keys and signatures. Vote +1 if you think the 0.5 release is ready... Karl -- With best wishes, Alex Ott http://alexott.net/ Tiwtter: alexott_en (English), alexott (Russian) Skype: alex.ott
[jira] [Commented] (CONNECTORS-263) Long-running tests should all be moved to Maven's integration-test phase
[ https://issues.apache.org/jira/browse/CONNECTORS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13115820#comment-13115820 ] Alex Ott commented on CONNECTORS-263: - it looks like this change doesn't respect profile setup - I see, that it's trying to run pgsql test, and fail with: Running org.apache.manifoldcf.agents.tests.SanityPostgresqlTest Configuration file successfully read org.apache.manifoldcf.core.interfaces.ManifoldCFException: Error getting connection Long-running tests should all be moved to Maven's integration-test phase Key: CONNECTORS-263 URL: https://issues.apache.org/jira/browse/CONNECTORS-263 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Piergiorgio Lucidi Fix For: ManifoldCF 0.4 Long-running tests should be moved to Maven's integration-test phase. (which are all in root-level tests directory) -- 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-263) Long-running tests should all be moved to Maven's integration-test phase
[ https://issues.apache.org/jira/browse/CONNECTORS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13115839#comment-13115839 ] Alex Ott commented on CONNECTORS-263: - Yes, this is why I commented - in previous builds, these tests weren't running Long-running tests should all be moved to Maven's integration-test phase Key: CONNECTORS-263 URL: https://issues.apache.org/jira/browse/CONNECTORS-263 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Piergiorgio Lucidi Fix For: ManifoldCF 0.4 Long-running tests should be moved to Maven's integration-test phase. (which are all in root-level tests directory) -- 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
Re: 1.0 release, and graduation
Hello On Wed, Sep 21, 2011 at 9:43 AM, Tommaso Teofili tommaso.teof...@gmail.com wrote: (2) I'm not sure it is reasonable to go with one build system over another. Lucene/Solr has been having this battle for years. I thought we might just learn from that experience and try to be more flexible. There are excellent technical reasons to have each - for instance, building Debian packages works much better with Ant, and Eclipse works much better with Maven. I don't like wars as well about which one *is* better, maybe it's just a matter of use case and personal preferences. However I like what you say about trying to be more flexible so I am +1 to your position. I have some experience with Maven so let me know if you need my help in tweaking that part of the build. I also have some experience with Maven, and I'm interested in MCF's development, so I can try to fix some problems. The first thing, that should be achieved - building with Maven out of box, without manual work (or at least with minimum of it). -- With best wishes, Alex Ott http://alexott.net/ Tiwtter: alexott_en (English), alexott (Russian) Skype: alex.ott
Re: 1.0 release, and graduation
Hello We can put following script (in attachment) to simplify setup of missing maven dependencies that are fetched using 'ant download-dependencies' command. After using this script I was able to build everything using maven. One more comment is on tests - maybe it's better to put long-running tests, like filesystem tests, etc. into integration-test build stage (https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html)? Maven Failsafe plugin (https://maven.apache.org/plugins/maven-failsafe-plugin/usage.html) provides useful functionality to implement this. I think, that this could make developer's life easier On Wed, Sep 21, 2011 at 9:52 AM, Alex Ott alex...@gmail.com wrote: Hello On Wed, Sep 21, 2011 at 9:43 AM, Tommaso Teofili tommaso.teof...@gmail.com wrote: (2) I'm not sure it is reasonable to go with one build system over another. Lucene/Solr has been having this battle for years. I thought we might just learn from that experience and try to be more flexible. There are excellent technical reasons to have each - for instance, building Debian packages works much better with Ant, and Eclipse works much better with Maven. I don't like wars as well about which one *is* better, maybe it's just a matter of use case and personal preferences. However I like what you say about trying to be more flexible so I am +1 to your position. I have some experience with Maven so let me know if you need my help in tweaking that part of the build. I also have some experience with Maven, and I'm interested in MCF's development, so I can try to fix some problems. The first thing, that should be achieved - building with Maven out of box, without manual work (or at least with minimum of it). -- 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 mvn-bootstrap.sh Description: Bourne shell script
[jira] [Commented] (CONNECTORS-258) pom.xml refers to jars not available in public repositories
[ https://issues.apache.org/jira/browse/CONNECTORS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13109390#comment-13109390 ] Alex Ott commented on CONNECTORS-258: - Some of dependencies (hsqldb, jcifs) already exist in central maven repository - you only need to ask developers to upload latest versions. There is guide on submitting jars to central repository - https://maven.apache.org/guides/mini/guide-central-repository-upload.html, there are some requirements to jars, described separately (https://docs.sonatype.org/display/Repository/Central+Sync+Requirements). Regarding modified versions of xerces and httpclient - do patches MCF-specific, or they are already submitted to upstream? If already submitted, then we can use SNAPSHOT versions of them, taking them from Apache repository pom.xml refers to jars not available in public repositories --- Key: CONNECTORS-258 URL: https://issues.apache.org/jira/browse/CONNECTORS-258 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.4 Environment: all supported platforms Reporter: Alex Ott Priority: Minor Labels: maven Maven's pom.xmls refers to jars that aren't available in public repositories, as maven central, apache repository, etc. This includes: - com.bitmechanic:jdbcpool - org.hsqldb:hsqldb:jar:2.2.5.6-9-2011 (at maven central only version 2.2.4 is available right now) I think, that ManifoldCF should adopt the same approach as other Apache projects, like Tika, when all needed jars first promoted to public repositories, and only after that, they are used as dependency... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-258) pom.xml refers to jars not available in public repositories
[ https://issues.apache.org/jira/browse/CONNECTORS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Ott updated CONNECTORS-258: Attachment: mvn-bootstrap.sh Script to prepare clean system for maven build pom.xml refers to jars not available in public repositories --- Key: CONNECTORS-258 URL: https://issues.apache.org/jira/browse/CONNECTORS-258 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.4 Environment: all supported platforms Reporter: Alex Ott Priority: Minor Labels: maven Attachments: mvn-bootstrap.sh Maven's pom.xmls refers to jars that aren't available in public repositories, as maven central, apache repository, etc. This includes: - com.bitmechanic:jdbcpool - org.hsqldb:hsqldb:jar:2.2.5.6-9-2011 (at maven central only version 2.2.4 is available right now) I think, that ManifoldCF should adopt the same approach as other Apache projects, like Tika, when all needed jars first promoted to public repositories, and only after that, they are used as dependency... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Long running tests
I'll try to refactor poms to use failsafe plugin, but I don't expect that I'll have time until weekend On Wed, Sep 21, 2011 at 12:41 PM, Karl Wright daddy...@gmail.com wrote: I've created a ticket (CONNECTORS-263) for this work. Anybody who wants to submit a patch would be very welcome... Karl On Wed, Sep 21, 2011 at 6:04 AM, Alex Ott alex...@gmail.com wrote: Hello We can put following script (in attachment) to simplify setup of missing maven dependencies that are fetched using 'ant download-dependencies' command. After using this script I was able to build everything using maven. One more comment is on tests - maybe it's better to put long-running tests, like filesystem tests, etc. into integration-test build stage (https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html)? Maven Failsafe plugin (https://maven.apache.org/plugins/maven-failsafe-plugin/usage.html) provides useful functionality to implement this. I think, that this could make developer's life easier On Wed, Sep 21, 2011 at 9:52 AM, Alex Ott alex...@gmail.com wrote: Hello On Wed, Sep 21, 2011 at 9:43 AM, Tommaso Teofili tommaso.teof...@gmail.com wrote: (2) I'm not sure it is reasonable to go with one build system over another. Lucene/Solr has been having this battle for years. I thought we might just learn from that experience and try to be more flexible. There are excellent technical reasons to have each - for instance, building Debian packages works much better with Ant, and Eclipse works much better with Maven. I don't like wars as well about which one *is* better, maybe it's just a matter of use case and personal preferences. However I like what you say about trying to be more flexible so I am +1 to your position. I have some experience with Maven so let me know if you need my help in tweaking that part of the build. I also have some experience with Maven, and I'm interested in MCF's development, so I can try to fix some problems. The first thing, that should be achieved - building with Maven out of box, without manual work (or at least with minimum of it). -- 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
[jira] [Commented] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions
[ https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13108894#comment-13108894 ] Alex Ott commented on CONNECTORS-223: - I'm not sure, that packages not available at Maven central, or other repositories, should be used in pom's - in Tika project another approach is used - all needed jars are promoted to repository first, and only after it are used... Tests in project hierarchy do not adhere to maven conventions - Key: CONNECTORS-223 URL: https://issues.apache.org/jira/browse/CONNECTORS-223 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Attachments: CONNECTORS-223.patch, CONNECTORS-223_forkMode.patch, CONNECTORS-223_jetty-runner.patch, CONNECTORS-223_tests.patch, test_reset.patch Maven expects unit tests under .../src/test/java, and root-level project tests under tests/xxx/src/test/java (or equivalent, along with their own pom.xml at tests and tests/xxx). This is basically compatible with the ant build except in location detail. The proposal is to move stuff around to make the tests work with maven. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-258) pom.xml refers to jars not available in public repositories
[ https://issues.apache.org/jira/browse/CONNECTORS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13108928#comment-13108928 ] Alex Ott commented on CONNECTORS-258: - another possibility - setup separate maven repository and server missing jars from it pom.xml refers to jars not available in public repositories --- Key: CONNECTORS-258 URL: https://issues.apache.org/jira/browse/CONNECTORS-258 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.4 Environment: all supported platforms Reporter: Alex Ott Priority: Minor Labels: maven Maven's pom.xmls refers to jars that aren't available in public repositories, as maven central, apache repository, etc. This includes: - com.bitmechanic:jdbcpool - org.hsqldb:hsqldb:jar:2.2.5.6-9-2011 (at maven central only version 2.2.4 is available right now) I think, that ManifoldCF should adopt the same approach as other Apache projects, like Tika, when all needed jars first promoted to public repositories, and only after that, they are used as dependency... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
