[VOTE] Release ManifoldCF 0.5.1, RC1
Hi, You can download the release candidate from http://people.apache.org/~shinichiro/apache-manifoldcf-0.5.1-RC1/ and there is also a tag in svn under https://svn.apache.org/repos/asf/incubator/lcf/tags RC1 includes revising the pom.xml versions. I've already checked signatures. Thank you, Shinichiro Abe
[WITHDRAW][VOTE] Release ManifoldCF 0.5.1, RC0
On 2012/05/18, at 10:52, Shinichiro Abe wrote:
> Thank you for checking.
> I am going to create RC1.
>
> Shinichiro Abe
>
> On 2012/05/18, at 10:48, Karl Wright wrote:
>
>> Interesting. I was browsing it using Explorer under Vista, and it
>> only shows part of the name.
>>
>> So, never mind - it seems to be a bug in Windows. You can go ahead
>> and build an RC1.
>>
>> Karl
>>
>> On Thu, May 17, 2012 at 9:33 PM, Shinichiro Abe
>> wrote:
>>>> If you open up the zip or tar, the top-level directory is
>>>> "apache-manifoldcf-0.5".
>>> I couldn't reproduce it. In my env the top-level directory is
>>> "apache-manifoldcf-0.5.1" , not "apache-manifoldcf-0.5".
>>>
>>> $ cd test
>>> $ ls
>>> apache-manifoldcf-0.5.1-src.zip
>>> $ unzip apache-manifoldcf-0.5.1-src.zip
>>> $ ls
>>> apache-manifoldcf-0.5.1
>>> apache-manifoldcf-0.5.1-src.zip
>>>
>>> I'm sorry, I didn't understand where the cause is.
>>> Should I open up the zip by another way?
>>>
>>> Regards,
>>> Shinichiro Abe
>>>
>>> On 2012/05/18, at 10:02, Karl Wright wrote:
>>>
>>>> If you open up the zip or tar, the top-level directory is
>>>> "apache-manifoldcf-0.5". That directory is set in build.xml when the
>>>> zip or tar is built:
>>>>
>>>> >>> update="false">
>>>>
>>>>
>>>> So, ${release-version} must have been incorrect. But it is correct
>>>> now on the branch:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> So somehow you must have built the artifacts from a version of the
>>>> branch before you checked in the release-version change.
>>>>
>>>> Karl
>>>>
>>>> On Thu, May 17, 2012 at 8:27 PM, Shinichiro Abe
>>>> wrote:
>>>>> What is the prefix inside?
>>>>> I ' m not sure where prefixes is.
>>>>> Where do I check? the source code or jar file?
>>>>>
>>>>> Thank you for modifying the pom.xml.
>>>>>
>>>>> Shinichiro Abe
>>>>>
>>>>> On 2012/05/18, at 7:13, Karl Wright wrote:
>>>>>
>>>>>> ok - I'm done with the maven work. Abe-san, can you check to be sure
>>>>>> that the release branch builds with the proper prefixes before tagging
>>>>>> again?
>>>>>>
>>>>>> Thanks!
>>>>>> Karl
>>>>>>
>>>>>>
>>>>>> On Thu, May 17, 2012 at 6:08 PM, Karl Wright wrote:
>>>>>>> I see two problems.
>>>>>>>
>>>>>>> First, the outer level names are correct
>>>>>>> (apache-manifoldcf-0.5.1-xxx), but the prefix inside is incorrect
>>>>>>> (apache-manifoldcf-0.5). This is odd because the build.xml has this
>>>>>>> line:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> so I cannot explain this unless somehow the artifacts were built with
>>>>>>> an old version of build.xml.
>>>>>>>
>>>>>>> The second problem is that we need to rev the pom.xml versions also.
>>>>>>> They have to be 0.5.1 not 0.5. I'll take care of that.
>>>>>>>
>>>>>>> Karl
>>>>>>>
>>>>>>> On Wed, May 16, 2012 at 10:26 PM, Karl Wright
>>>>>>> wrote:
>>>>>>>> Thanks!
>>>>>>>> I'll have a look in the morning...
>>>>>>>> Karl
>>>>>>>>
>>>>>>>> On Wed, May 16, 2012 at 10:24 PM, Shinichiro Abe
>>>>>>>> wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> You can download the release candidate from
>>>>>>>>> http://people.apache.org/~shinichiro/apache-manifoldcf-0.5.1-RC0/
>>>>>>>>> and there is also a tag in svn under
>>>>>>>>> https://svn.apache.org/repos/asf/incubator/lcf/tags
>>>>>>>>>
>>>>>>>>> I've already checked signatures,
>>>>>>>>> run example and run "ant test-dr test-hs".
>>>>>>>>>
>>>>>>>>> Thank you,
>>>>>>>>> Shinichiro Abe
>>>>>
>>>
>
Re: [VOTE] Release ManifoldCF 0.5.1, RC0
Thank you for checking.
I am going to create RC1.
Shinichiro Abe
On 2012/05/18, at 10:48, Karl Wright wrote:
> Interesting. I was browsing it using Explorer under Vista, and it
> only shows part of the name.
>
> So, never mind - it seems to be a bug in Windows. You can go ahead
> and build an RC1.
>
> Karl
>
> On Thu, May 17, 2012 at 9:33 PM, Shinichiro Abe
> wrote:
>>> If you open up the zip or tar, the top-level directory is
>>> "apache-manifoldcf-0.5".
>> I couldn't reproduce it. In my env the top-level directory is
>> "apache-manifoldcf-0.5.1" , not "apache-manifoldcf-0.5".
>>
>> $ cd test
>> $ ls
>> apache-manifoldcf-0.5.1-src.zip
>> $ unzip apache-manifoldcf-0.5.1-src.zip
>> $ ls
>> apache-manifoldcf-0.5.1
>> apache-manifoldcf-0.5.1-src.zip
>>
>> I'm sorry, I didn't understand where the cause is.
>> Should I open up the zip by another way?
>>
>> Regards,
>> Shinichiro Abe
>>
>> On 2012/05/18, at 10:02, Karl Wright wrote:
>>
>>> If you open up the zip or tar, the top-level directory is
>>> "apache-manifoldcf-0.5". That directory is set in build.xml when the
>>> zip or tar is built:
>>>
>>> >> update="false">
>>>
>>>
>>> So, ${release-version} must have been incorrect. But it is correct
>>> now on the branch:
>>>
>>>
>>>
>>>
>>>
>>> So somehow you must have built the artifacts from a version of the
>>> branch before you checked in the release-version change.
>>>
>>> Karl
>>>
>>> On Thu, May 17, 2012 at 8:27 PM, Shinichiro Abe
>>> wrote:
>>>> What is the prefix inside?
>>>> I ' m not sure where prefixes is.
>>>> Where do I check? the source code or jar file?
>>>>
>>>> Thank you for modifying the pom.xml.
>>>>
>>>> Shinichiro Abe
>>>>
>>>> On 2012/05/18, at 7:13, Karl Wright wrote:
>>>>
>>>>> ok - I'm done with the maven work. Abe-san, can you check to be sure
>>>>> that the release branch builds with the proper prefixes before tagging
>>>>> again?
>>>>>
>>>>> Thanks!
>>>>> Karl
>>>>>
>>>>>
>>>>> On Thu, May 17, 2012 at 6:08 PM, Karl Wright wrote:
>>>>>> I see two problems.
>>>>>>
>>>>>> First, the outer level names are correct
>>>>>> (apache-manifoldcf-0.5.1-xxx), but the prefix inside is incorrect
>>>>>> (apache-manifoldcf-0.5). This is odd because the build.xml has this
>>>>>> line:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> so I cannot explain this unless somehow the artifacts were built with
>>>>>> an old version of build.xml.
>>>>>>
>>>>>> The second problem is that we need to rev the pom.xml versions also.
>>>>>> They have to be 0.5.1 not 0.5. I'll take care of that.
>>>>>>
>>>>>> Karl
>>>>>>
>>>>>> On Wed, May 16, 2012 at 10:26 PM, Karl Wright wrote:
>>>>>>> Thanks!
>>>>>>> I'll have a look in the morning...
>>>>>>> Karl
>>>>>>>
>>>>>>> On Wed, May 16, 2012 at 10:24 PM, Shinichiro Abe
>>>>>>> wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> You can download the release candidate from
>>>>>>>> http://people.apache.org/~shinichiro/apache-manifoldcf-0.5.1-RC0/
>>>>>>>> and there is also a tag in svn under
>>>>>>>> https://svn.apache.org/repos/asf/incubator/lcf/tags
>>>>>>>>
>>>>>>>> I've already checked signatures,
>>>>>>>> run example and run "ant test-dr test-hs".
>>>>>>>>
>>>>>>>> Thank you,
>>>>>>>> Shinichiro Abe
>>>>
>>
Re: [VOTE] Release ManifoldCF 0.5.1, RC0
> If you open up the zip or tar, the top-level directory is
> "apache-manifoldcf-0.5".
I couldn't reproduce it. In my env the top-level directory is
"apache-manifoldcf-0.5.1" , not "apache-manifoldcf-0.5".
$ cd test
$ ls
apache-manifoldcf-0.5.1-src.zip
$ unzip apache-manifoldcf-0.5.1-src.zip
$ ls
apache-manifoldcf-0.5.1
apache-manifoldcf-0.5.1-src.zip
I'm sorry, I didn't understand where the cause is.
Should I open up the zip by another way?
Regards,
Shinichiro Abe
On 2012/05/18, at 10:02, Karl Wright wrote:
> If you open up the zip or tar, the top-level directory is
> "apache-manifoldcf-0.5". That directory is set in build.xml when the
> zip or tar is built:
>
> update="false">
>
>
> So, ${release-version} must have been incorrect. But it is correct
> now on the branch:
>
>
>
>
>
> So somehow you must have built the artifacts from a version of the
> branch before you checked in the release-version change.
>
> Karl
>
> On Thu, May 17, 2012 at 8:27 PM, Shinichiro Abe
> wrote:
>> What is the prefix inside?
>> I ' m not sure where prefixes is.
>> Where do I check? the source code or jar file?
>>
>> Thank you for modifying the pom.xml.
>>
>> Shinichiro Abe
>>
>> On 2012/05/18, at 7:13, Karl Wright wrote:
>>
>>> ok - I'm done with the maven work. Abe-san, can you check to be sure
>>> that the release branch builds with the proper prefixes before tagging
>>> again?
>>>
>>> Thanks!
>>> Karl
>>>
>>>
>>> On Thu, May 17, 2012 at 6:08 PM, Karl Wright wrote:
>>>> I see two problems.
>>>>
>>>> First, the outer level names are correct
>>>> (apache-manifoldcf-0.5.1-xxx), but the prefix inside is incorrect
>>>> (apache-manifoldcf-0.5). This is odd because the build.xml has this
>>>> line:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> so I cannot explain this unless somehow the artifacts were built with
>>>> an old version of build.xml.
>>>>
>>>> The second problem is that we need to rev the pom.xml versions also.
>>>> They have to be 0.5.1 not 0.5. I'll take care of that.
>>>>
>>>> Karl
>>>>
>>>> On Wed, May 16, 2012 at 10:26 PM, Karl Wright wrote:
>>>>> Thanks!
>>>>> I'll have a look in the morning...
>>>>> Karl
>>>>>
>>>>> On Wed, May 16, 2012 at 10:24 PM, Shinichiro Abe
>>>>> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> You can download the release candidate from
>>>>>> http://people.apache.org/~shinichiro/apache-manifoldcf-0.5.1-RC0/
>>>>>> and there is also a tag in svn under
>>>>>> https://svn.apache.org/repos/asf/incubator/lcf/tags
>>>>>>
>>>>>> I've already checked signatures,
>>>>>> run example and run "ant test-dr test-hs".
>>>>>>
>>>>>> Thank you,
>>>>>> Shinichiro Abe
>>
Re: [VOTE] Release ManifoldCF 0.5.1, RC0
What is the prefix inside? I ' m not sure where prefixes is. Where do I check? the source code or jar file? Thank you for modifying the pom.xml. Shinichiro Abe On 2012/05/18, at 7:13, Karl Wright wrote: > ok - I'm done with the maven work. Abe-san, can you check to be sure > that the release branch builds with the proper prefixes before tagging > again? > > Thanks! > Karl > > > On Thu, May 17, 2012 at 6:08 PM, Karl Wright wrote: >> I see two problems. >> >> First, the outer level names are correct >> (apache-manifoldcf-0.5.1-xxx), but the prefix inside is incorrect >> (apache-manifoldcf-0.5). This is odd because the build.xml has this >> line: >> >> >> >> >> >> so I cannot explain this unless somehow the artifacts were built with >> an old version of build.xml. >> >> The second problem is that we need to rev the pom.xml versions also. >> They have to be 0.5.1 not 0.5. I'll take care of that. >> >> Karl >> >> On Wed, May 16, 2012 at 10:26 PM, Karl Wright wrote: >>> Thanks! >>> I'll have a look in the morning... >>> Karl >>> >>> On Wed, May 16, 2012 at 10:24 PM, Shinichiro Abe >>> wrote: >>>> Hi, >>>> >>>> You can download the release candidate from >>>> http://people.apache.org/~shinichiro/apache-manifoldcf-0.5.1-RC0/ >>>> and there is also a tag in svn under >>>> https://svn.apache.org/repos/asf/incubator/lcf/tags >>>> >>>> I've already checked signatures, >>>> run example and run "ant test-dr test-hs". >>>> >>>> Thank you, >>>> Shinichiro Abe
[VOTE] Release ManifoldCF 0.5.1, RC0
Hi, You can download the release candidate from http://people.apache.org/~shinichiro/apache-manifoldcf-0.5.1-RC0/ and there is also a tag in svn under https://svn.apache.org/repos/asf/incubator/lcf/tags I've already checked signatures, run example and run "ant test-dr test-hs". Thank you, Shinichiro Abe
Re: Should we release an 0.5.1?
Okay. Do we need to change release-version into 0.5.1 at build.xml in the branch? Shinichiro Abe On 2012/05/12, at 19:39, Karl Wright wrote: > Hi Abe-san, > > For point releases, the usual standard is to use the same branch as > the main release. So we would continue to use the 0.5-incubating > branch, and just make a new release from it, and of course new tags. > > Thanks, > Karl > > > On Sat, May 12, 2012 at 5:35 AM, Shinichiro Abe > wrote: >> Yes I did. I will be able to work as release manager next week. >> Please create 0.5.1 branch. >> >> Regards, >> Shinichiro Abe >> >> On 2012/05/12, at 16:14, Karl Wright wrote: >> >>> It looks like this is probably happening, so I've pulled up three >>> tickets into the 0.5 release branch: >>> >>> CONNECTORS-453 >>> CONNECTORS-467 >>> CONNECTORS-471 >>> >>> I suppose we could even spin a release candidate now, even though we >>> shouldn't probably vote on it until we've officially graduated. >>> >>> The release candidate should be "0.5.1", not "0.5.1-incubating". >>> Abe-san, did you want to be release manager for this? >>> >>> Karl >>> >>> On Mon, May 7, 2012 at 7:00 AM, Erlend Garåsen >>> wrote: >>>> >>>> If we succeed in graduating in May, then +1 from me. >>>> >>>> This problem does not only affects Tomcat, but also Resin, and probably >>>> other web containers as well. >>>> >>>> Erlend >>>> >>>> >>>> On 04.05.12 21.03, Karl Wright wrote: >>>>> >>>>> My view: It will be relatively easy to do this once we graduate, and >>>>> too much of a pain before then. If we succeed in graduating in May, >>>>> I'd give a +1. If not, then maybe we should just try to release the >>>>> 0.6 version instead. >>>>> >>>>> Karl >>>>> >>>>> On Fri, May 4, 2012 at 1:01 PM, Piergiorgio Lucidi >>>>> wrote: >>>>>> >>>>>> I think that it is important to release a 0.5.1 version to enable >>>>>> compatibility for Tomcat 7.x. >>>>>> >>>>>> +1 for me for releasing a 0.5.1 version >>>>>> >>>>>> Piergiorgio >>>>>> >>>>>> 2012/5/1 Karl Wright >>>>>> >>>>>>> We've had a number of people using Tomcat 7.x who have tripped over >>>>>>> CONNECTORS-467. Does the community want to release a 0.5.1 version to >>>>>>> fix this one issue? Or, alternatively, try to push 0.6 out the door >>>>>>> early? >>>>>>> >>>>>>> Karl >>>>>>> >>>>>>> -- >>>>>>> Piergiorgio Lucidi >>>>>>> http://www.open4dev.com >>>>>>> >>>>>>> >>>> >>>> >>>> -- >>>> Erlend Garåsen >>>> Center for Information Technology Services >>>> University of Oslo >>>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway >>>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050 >>
Re: Should we release an 0.5.1?
Yes I did. I will be able to work as release manager next week. Please create 0.5.1 branch. Regards, Shinichiro Abe On 2012/05/12, at 16:14, Karl Wright wrote: > It looks like this is probably happening, so I've pulled up three > tickets into the 0.5 release branch: > > CONNECTORS-453 > CONNECTORS-467 > CONNECTORS-471 > > I suppose we could even spin a release candidate now, even though we > shouldn't probably vote on it until we've officially graduated. > > The release candidate should be "0.5.1", not "0.5.1-incubating". > Abe-san, did you want to be release manager for this? > > Karl > > On Mon, May 7, 2012 at 7:00 AM, Erlend Garåsen > wrote: >> >> If we succeed in graduating in May, then +1 from me. >> >> This problem does not only affects Tomcat, but also Resin, and probably >> other web containers as well. >> >> Erlend >> >> >> On 04.05.12 21.03, Karl Wright wrote: >>> >>> My view: It will be relatively easy to do this once we graduate, and >>> too much of a pain before then. If we succeed in graduating in May, >>> I'd give a +1. If not, then maybe we should just try to release the >>> 0.6 version instead. >>> >>> Karl >>> >>> On Fri, May 4, 2012 at 1:01 PM, Piergiorgio Lucidi >>> wrote: >>>> >>>> I think that it is important to release a 0.5.1 version to enable >>>> compatibility for Tomcat 7.x. >>>> >>>> +1 for me for releasing a 0.5.1 version >>>> >>>> Piergiorgio >>>> >>>> 2012/5/1 Karl Wright >>>> >>>>> We've had a number of people using Tomcat 7.x who have tripped over >>>>> CONNECTORS-467. Does the community want to release a 0.5.1 version to >>>>> fix this one issue? Or, alternatively, try to push 0.6 out the door >>>>> early? >>>>> >>>>> Karl >>>>> >>>>> -- >>>>> Piergiorgio Lucidi >>>>> http://www.open4dev.com >>>>> >>>>> >> >> >> -- >> Erlend Garåsen >> Center for Information Technology Services >> University of Oslo >> P.O. Box 1086 Blindern, N-0317 OSLO, Norway >> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Graduation resolution for ManifoldCF
+1 from me :) Shinichiro Abe On 2012/05/01, at 21:18, Karl Wright wrote: > Thanks, Jukka, I'd be honored to take on the role of VP in a > ManifoldCF top-level project. > > Incorporating Jukka's invaluable advice, I've updated the proposed > resolution, and am opening a vote on it. Please vote +1 if you agree > that this is the resolution that should be presented, in total, > including myself in the role of Vice President, or -1 if you see > changes you would like to make (or if you'd like to nominate someone > else and hold a formal vote on the VP role). > > == > WHEREAS, the Board of Directors deems it to be in the best interests > of the Foundation and consistent with the Foundation's purpose to > establish a Project Management Committee charged with the creation and > maintenance of open-source software for transferring content between > repositories or search indexes, for distribution at no charge to the > public; > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache ManifoldCF Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache ManifoldCF Project be and hereby is > responsible for the creation and maintenance of open-source software for > transferring content between repositories or search indexes, for > distribution > at no charge to the public. > > RESOLVED, that the office of "Vice President, ManifoldCF" be and hereby > is created, the person holding such office to serve at the direction > of the Board of Directors as the chair of the Apache ManifoldCF > Project, and to have primary responsibility for management of the > projects within the scope of responsibility of the Apache ManifoldCF > Project; and be it further > > RESOLVED, that the persons listed immediately below be and hereby are > appointed to serve as the initial members of the Apache ManifoldCF > Project: > >* Shinichiro Abe (shinich...@apache.org) >* Erlend Garåsen(rid...@apache.org) >* Piergiorgio Lucidi (piergior...@apache.org) > * Hitoshi Ozawa (hoz...@apache.org) >* Tommaso Teofili (tomm...@apache.org) >* Simon Willnauer(sim...@apache.org) >* Karl Wright (kwri...@apache.org) >* Jukka Zitting (ju...@apache.org) > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Karl Wright be > appointed to the office of Vice President, ManifoldCF, to serve in > accordance with and subject to the direction of the Board of Directors > and the Bylaws of the Foundation until death, resignation, retirement, > removal or disqualification, or until a successor is appointed; and be > it further > > RESOLVED, that the initial Apache ManifoldCF Project be and hereby is > tasked with the creation of a set of bylaws intended to encourage open > development and increased participation in the ManifoldCF Project; and > be it further > > RESOLVED, that the initial Apache ManifoldCF Project be and hereby is > tasked with the migration and rationalization of the Apache Incubator > ManifoldCF podling; and be it further > > RESOLVED, that all responsibility pertaining to the Apache Incubator > ManifoldCF podling encumbered upon the Apache Incubator PMC are > hereafter discharged. > == > > +1 from me. > > Thanks again for the vote of confidence! > Karl > > > On Tue, May 1, 2012 at 5:16 AM, Jukka Zitting wrote: >> Hi, >> >> On Mon, Apr 30, 2012 at 3:13 PM, Karl Wright wrote: >>> Looks like we missed a step; we need a graduation resolution for the >>> board to vote on. Here's my proposal, basically copied from Apache >>> Chemistry's, but I have a question. Since no distinction is made >>> between the PPMC members and committers in this resolution, and since >>> many of the original committers/IPMC members have become inactive, and >>> others have not yet been voted in as PPMC members, how should we deal >>> with that? >> >> * Overall the resolution looks good, though note my comment on the scope >> below. >> >> * As discussed before, I don't think making a distinction between >> committers and (P)PMC members is useful for us. IMO such a setup only >> makes sense for "umbrella" projects like the Incubator and Lucene >> befo
Re: [VOTE] Propose graduation of ManifoldCF from the Incubator as a Top Level Project
+1 from me. Shinichiro Abe On 2012/04/24, at 19:08, Karl Wright 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
[ANNOUNCE] ManifoldCF 0.5-incubating has been released!
Thanks to all who put time and effort into this release! The site and download mirrors should update in a day or so, but if you cannot wait, you can download the release in the interim from http://www.apache.org/dist/incubator/manifoldcf. Thank you, Shinichiro Abe
Re: Translations into Japanese needed for an error message
"種子リスト内の無効なURL：" --> "シードリスト内の無効なURL：" seeds = シード (Japanese reading) Thank you, Shinichiro Abe On 2012/04/12, at 4:24, Erlend Garåsen wrote: > > I need to translate an error message into Japanese in order to resolve a > ticket. > > The English text I need to translate: "Invalid URLs in seeds list:" > Google translates this to: "種子リスト内の無効なURL：" > > Is the translation correct? > > Erlend > -- > Erlend Garåsen > Center for Information Technology Services > University of Oslo > P.O. Box 1086 Blindern, N-0317 OSLO, Norway > Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
[RESULT][VOTE] Release ManifoldCF 0.5-incubating, RC6
>72 hours. Vote passes! Next, I need to open a vote in gene...@incubator.apache.org Thank you everyone. Shinichiro Abe
[VOTE] Release ManifoldCF 0.5-incubating, RC6
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
[WITHDRAW][VOTE] Release ManifoldCF 0.5-incubating, RC5
We withdraw RC5 and I'll create RC6 today. Thank you, Shinichiro Abe On 2012/04/07, at 5:04, Alex Ott wrote: > Hi Karl > > Yes, this issue is fixed, thank you! > > On Fri, Apr 6, 2012 at 8:25 PM, Karl Wright 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 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 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 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 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 wrote: >>>>>>> What does your manifoldcf.log file have in it? >>>>>>> >>>>>>> Karl >>>>>>> >>>>>>> On Fri, Apr 6, 2012 at 12:36 PM, Alex Ott 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" >>>&
[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
[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 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 wrote: >>> Found what I think is a blocker. CONNECTORS-452. >>> >>> Karl >>> >>> On Thu, Apr 5, 2012 at 8:45 AM, Karl Wright 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 >>>> 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
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 > 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
[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
[WITHDRAW][VOTE] Release ManifoldCF 0.5-incubating, RC3
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 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 >> wrote: >>> Hi, >>> >>> On Mon, Apr 2, 2012 at 8:15 PM, Karl Wright 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
+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 >
[VOTE] Release ManifoldCF 0.5-incubating, RC3
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
[CANCEL][VOTE] Release ManifoldCF 0.5-incubating, RC2
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 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 >> 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 >>>
Re: [VOTE] Release ManifoldCF 0.5-incubating, RC2
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, RC2
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
[WITHDRAW][VOTE] Release ManifoldCF 0.5-incubating, RC1
HI, I close RC1 for CONNECTORS-437 regarding embedded jar files in the source. I'll create RC2 today. Thank you, Shinichiro Abe On 2012/03/27, at 15:55, Piergiorgio Lucidi wrote: > I tried to use the binary distribution starting some jobs with CMIS and > ElasticSearch. > +1 from me. > > Piergiorgio > > Il giorno 27 marzo 2012 04:00, Shinichiro Abe > ha scritto: > >> Hi, >> >> You can download the release candidate from >> http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC1/ >> and there is also a tag in svn >> under https://svn.apache.org/repos/asf/incubator/lcf/tags. >> >> RC1 fixed the following issues by IPMC requests: >> 1. CONNECTORS-434: Describe which licenses we select for our dual-licensed >> jars.(LICENSE.txt) >> 2. CONNECTORS-433: Update copyright date.(NOTICE.txt) >> 3. My code signing Key is available online. >> >> I've already checked signatures. >> >> Thank you, >> Shinichiro Abe >> >> -- >> Piergiorgio Lucidi >> http://www.open4dev.com >> >>
[VOTE] Release ManifoldCF 0.5-incubating, RC1
Hi, You can download the release candidate from http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC1/ and there is also a tag in svn under https://svn.apache.org/repos/asf/incubator/lcf/tags. RC1 fixed the following issues by IPMC requests: 1. CONNECTORS-434: Describe which licenses we select for our dual-licensed jars.(LICENSE.txt) 2. CONNECTORS-433: Update copyright date.(NOTICE.txt) 3. My code signing Key is available online. I've already checked signatures. Thank you, Shinichiro Abe
[RESULT][VOTE] Release ManifoldCF 0.5-incubating, RC0
Three +1's. >72 hours. Vote passes! Next, I need to open a vote in gene...@incubator.apache.org Thank you everyone. Shinichiro Abe On 2012/03/22, at 18:55, Piergiorgio Lucidi wrote: > I checked signatures and I used the application from the binary package. > > +1 from me > > Piergiorgio > > Il 22 marzo 2012 02:27, Karl Wright ha scritto: >> Signatures look good. +1 from me. >> Karl >> >> >> On Wed, Mar 21, 2012 at 8:49 PM, Shinichiro Abe >> wrote: >>> >>> + 1 from me >>> >>> Shinichiro Abe >>> >>> On 2012/03/22, at 2:24, Karl Wright 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 >>> > > > > -- > Piergiorgio Lucidi > http://www.open4dev.com
Re: [VOTE] Release ManifoldCF 0.5-incubating, RC0
+ 1 from me Shinichiro Abe On 2012/03/22, at 2:24, Karl Wright 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
apache-manifoldcf-0.5-incubating, RC0 available
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
Re: Postpone localization tickets for 0.5 release?
+1 Shinichiro On 2012/03/20, at 4:33, Karl Wright wrote: > Hi all, > > I've not heard anything from Hitoshi Ozawa about whether he will be > able to complete some of the Japanese localization work that was > scheduled for 0.5-incubating. Since the day is rapidly approaching > when we have to spin the first RC, I'd like a show of hands as to > whether we should postpone the two tickets currently on Hitoshi's > plate for the next release. The tickets in question are > CONNECTORS-394 and CONNECTORS-404. > > +1 from me for postponing. > > Karl
[jira] [Resolved] (CONNECTORS-424) Add RepositoryDocument.getFileName
[ https://issues.apache.org/jira/browse/CONNECTORS-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe resolved CONNECTORS-424. --- Resolution: Fixed r1302268. > Add RepositoryDocument.getFileName > -- > > Key: CONNECTORS-424 > URL: https://issues.apache.org/jira/browse/CONNECTORS-424 > Project: ManifoldCF > Issue Type: Improvement > Components: Framework agents process >Affects Versions: ManifoldCF 0.5 > Reporter: Shinichiro Abe > Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.5 > > Attachments: CONNECTORS-424.patch > > > When posting files to Solr via file system connector or share drive > connector, the stream_name of metadata is hard-coded "docname". I want to set > the stream_name a right file name, it is useful for searching documents by > file name. -- 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-424) Add RepositoryDocument.getFileName
[ https://issues.apache.org/jira/browse/CONNECTORS-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229237#comment-13229237 ] Shinichiro Abe commented on CONNECTORS-424: --- Yes, I've tested CJK character file name at least. These file names are not garbled. I'll commit after checking a little bit. > Add RepositoryDocument.getFileName > -- > > Key: CONNECTORS-424 > URL: https://issues.apache.org/jira/browse/CONNECTORS-424 > Project: ManifoldCF > Issue Type: Improvement > Components: Framework agents process >Affects Versions: ManifoldCF 0.5 >Reporter: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.5 > > Attachments: CONNECTORS-424.patch > > > When posting files to Solr via file system connector or share drive > connector, the stream_name of metadata is hard-coded "docname". I want to set > the stream_name a right file name, it is useful for searching documents by > file name. -- 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] [Assigned] (CONNECTORS-424) Add RepositoryDocument.getFileName
[ https://issues.apache.org/jira/browse/CONNECTORS-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe reassigned CONNECTORS-424: - Assignee: Shinichiro Abe > Add RepositoryDocument.getFileName > -- > > Key: CONNECTORS-424 > URL: https://issues.apache.org/jira/browse/CONNECTORS-424 > Project: ManifoldCF > Issue Type: Improvement > Components: Framework agents process >Affects Versions: ManifoldCF 0.5 > Reporter: Shinichiro Abe > Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.5 > > Attachments: CONNECTORS-424.patch > > > When posting files to Solr via file system connector or share drive > connector, the stream_name of metadata is hard-coded "docname". I want to set > the stream_name a right file name, it is useful for searching documents by > file name. -- 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] [Updated] (CONNECTORS-424) Add RepositoryDocument.getFileName
[ https://issues.apache.org/jira/browse/CONNECTORS-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-424: -- Attachment: CONNECTORS-424.patch I want to include this patch to MCF 0.5. > Add RepositoryDocument.getFileName > -- > > Key: CONNECTORS-424 > URL: https://issues.apache.org/jira/browse/CONNECTORS-424 > Project: ManifoldCF > Issue Type: Improvement > Components: Framework agents process >Affects Versions: ManifoldCF 0.5 > Reporter: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.5 > > Attachments: CONNECTORS-424.patch > > > When posting files to Solr via file system connector or share drive > connector, the stream_name of metadata is hard-coded "docname". I want to set > the stream_name a right file name, it is useful for searching documents by > file name. -- 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] [Created] (CONNECTORS-424) Add RepositoryDocument.getFileName
Add RepositoryDocument.getFileName -- Key: CONNECTORS-424 URL: https://issues.apache.org/jira/browse/CONNECTORS-424 Project: ManifoldCF Issue Type: Improvement Components: Framework agents process Affects Versions: ManifoldCF 0.5 Reporter: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.5 When posting files to Solr via file system connector or share drive connector, the stream_name of metadata is hard-coded "docname". I want to set the stream_name a right file name, it is useful for searching documents by file name. -- 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: Release time is upon us once again
Hi. I want to volunteer to be Release Manager for 0.5-incubating. I use Mac OS, but please teach me some ways if I can work. Regards, Shinichiro Abe On 2012/03/14, at 8:44, Karl Wright wrote: > Hi fellow developers, > > Our next release date is rapidly approaching. We've been releasing a > version of ManifoldCF at roughly the end of every quarter for a year > now, and March 31 is a bit over two weeks away. > > There are currently three outstanding 0.5-incubating bugs. Two are > Japanese localization tickets, and one is for the new Elastic Search > connector. The latter is unassigned. Please finish these up as > quickly as possible! > > Finally, I've been the Release Manager for all four releases up until > now. Does anyone want to volunteer to be Release Manager for > 0.5-incubating? I'd be happy to provide assistance and check in all > of my Windows-based scripts. > > Karl
[jira] [Resolved] (CONNECTORS-414) Incorrect path in executecommand.sh, start-webapps.sh and start-database.sh
[ https://issues.apache.org/jira/browse/CONNECTORS-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe resolved CONNECTORS-414. --- Resolution: Fixed > Incorrect path in executecommand.sh, start-webapps.sh and start-database.sh > --- > > Key: CONNECTORS-414 > URL: https://issues.apache.org/jira/browse/CONNECTORS-414 > Project: ManifoldCF > Issue Type: Bug > Components: Examples >Affects Versions: ManifoldCF 0.5 > Reporter: Shinichiro Abe > Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.5 > > Attachments: CONNECTORS-414.patch > > > Currently the scripts above include an incorrect path. > I couldn't run each script at multiprocess-examples. -- 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-414) Incorrect path in executecommand.sh, start-webapps.sh and start-database.sh
[ https://issues.apache.org/jira/browse/CONNECTORS-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215468#comment-13215468 ] Shinichiro Abe commented on CONNECTORS-414: --- Thank you for your comment. r1293117. > Incorrect path in executecommand.sh, start-webapps.sh and start-database.sh > --- > > Key: CONNECTORS-414 > URL: https://issues.apache.org/jira/browse/CONNECTORS-414 > Project: ManifoldCF > Issue Type: Bug > Components: Examples >Affects Versions: ManifoldCF 0.5 > Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.5 > > Attachments: CONNECTORS-414.patch > > > Currently the scripts above include an incorrect path. > I couldn't run each script at multiprocess-examples. -- 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] [Updated] (CONNECTORS-414) Incorrect path in executecommand.sh, start-webapps.sh and start-database.sh
[ https://issues.apache.org/jira/browse/CONNECTORS-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-414: -- Attachment: CONNECTORS-414.patch I'll commit this patch immediately. > Incorrect path in executecommand.sh, start-webapps.sh and start-database.sh > --- > > Key: CONNECTORS-414 > URL: https://issues.apache.org/jira/browse/CONNECTORS-414 > Project: ManifoldCF > Issue Type: Bug > Components: Examples >Affects Versions: ManifoldCF 0.5 > Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.5 > > Attachments: CONNECTORS-414.patch > > > Currently the scripts above include an incorrect path. > I couldn't run each script at multiprocess-examples. -- 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] [Created] (CONNECTORS-414) Incorrect path in executecommand.sh, start-webapps.sh and start-database.sh
Incorrect path in executecommand.sh, start-webapps.sh and start-database.sh --- Key: CONNECTORS-414 URL: https://issues.apache.org/jira/browse/CONNECTORS-414 Project: ManifoldCF Issue Type: Bug Components: Examples Affects Versions: ManifoldCF 0.5 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.5 Attachments: CONNECTORS-414.patch Currently the scripts above include an incorrect path. I couldn't run each script at multiprocess-examples. -- 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] [Resolved] (CONNECTORS-409) mcf-ui-core.jar doesn't exist in dist/example/lib
[ https://issues.apache.org/jira/browse/CONNECTORS-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe resolved CONNECTORS-409. --- Resolution: Fixed > mcf-ui-core.jar doesn't exist in dist/example/lib > - > > Key: CONNECTORS-409 > URL: https://issues.apache.org/jira/browse/CONNECTORS-409 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Affects Versions: ManifoldCF 0.5 > Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.5 > > Attachments: CONNECTORS-409.patch > > > Currently mcf-ui-core.jar isn't copied into dist/example/lib. > So I couldn't register info by using crawler-ui at all. > I fix framework/build.xml. -- 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-409) mcf-ui-core.jar doesn't exist in dist/example/lib
[ https://issues.apache.org/jira/browse/CONNECTORS-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208289#comment-13208289 ] Shinichiro Abe commented on CONNECTORS-409: --- r1244405. Thank you. > mcf-ui-core.jar doesn't exist in dist/example/lib > - > > Key: CONNECTORS-409 > URL: https://issues.apache.org/jira/browse/CONNECTORS-409 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Affects Versions: ManifoldCF 0.5 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.5 > > Attachments: CONNECTORS-409.patch > > > Currently mcf-ui-core.jar isn't copied into dist/example/lib. > So I couldn't register info by using crawler-ui at all. > I fix framework/build.xml. -- 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] [Updated] (CONNECTORS-409) mcf-ui-core.jar doesn't exist in dist/example/lib
[ https://issues.apache.org/jira/browse/CONNECTORS-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-409: -- Attachment: CONNECTORS-409.patch I'll commit this patch if there is nothing wrong. > mcf-ui-core.jar doesn't exist in dist/example/lib > - > > Key: CONNECTORS-409 > URL: https://issues.apache.org/jira/browse/CONNECTORS-409 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Affects Versions: ManifoldCF 0.5 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.5 > > Attachments: CONNECTORS-409.patch > > > Currently mcf-ui-core.jar isn't copied into dist/example/lib. > So I couldn't register info by using crawler-ui at all. > I fix framework/build.xml. -- 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] [Created] (CONNECTORS-409) mcf-ui-core.jar doesn't exist in dist/example/lib
mcf-ui-core.jar doesn't exist in dist/example/lib - Key: CONNECTORS-409 URL: https://issues.apache.org/jira/browse/CONNECTORS-409 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.5 Currently mcf-ui-core.jar isn't copied into dist/example/lib. So I couldn't register info by using crawler-ui at all. I fix framework/build.xml. -- 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: Please welcome Hitoshi Ozawa to the ManifoldCF community!
Welcome and congratulations! Shinichiro Abe On 2012/02/07, at 11:39, Karl Wright wrote: > Hitoshi is now officially a ManifoldCF Committer. Congratulations, Hitoshi! > > Karl
Re: [VOTE] Release Apache ManifoldCF 0.4-incubating, RC0
Thank you. I understand. +1 for me. Shinichiro Abe On 2011/12/19, at 16:25, Karl Wright wrote: > The hsqldb configuration used by multiprocess-example is an external > hsqldb database. It does not require the > org.apache.manifoldcf.hsqldbdatabasepath property. If you want to try > out the multiprocess example, take the following steps: > > (1) In one shell prompt, start the database: "start-database.bat/.sh" > (2) In another shell prompt, initialize the database: "initialize.bat/.sh" > (3) When that is done, start the agents proces: "start-agents.bat/.sh" > > Thanks, > Karl > > > On Mon, Dec 19, 2011 at 2:05 AM, Shinichiro Abe > wrote: >> Hi. >> >> I checked 0.4 by running ant test, okay but one problem. >> >> In multiprocess-example, at default properties.xml, HSQLDB database requires >> 'org.apache.manifoldcf.hsqldbdatabasepath' property, containing a relative >> path: >> >> >> >> Now exception is thrown, so we need to add this property. >> Should I send a patch? Next? >> >> Regards, >> Shinichiro Abe >> >> On 2011/12/18, at 2:27, Karl Wright wrote: >> >>> I've again uploaded an apache-manifoldcf-0.4-incubating package which you >>> can download from http://people.apache.org/~kwright. If you agree >>> this should be released please vote +1. >>> >>> [Note that the release of this artifact is dependent on the release of >>> the three plugin packages upon which it depends. If we need to change >>> those packages we'll need to spin a new RC of this one. Also please >>> note that I've include SHA1 signatures for the first time, as per >>> Jukka's suggestion.] >>> >>> I apologize again for the earlier hiccup. This one is the real thing, >>> though, and passes all tests. >>> >>> Thanks! >>> Karl >>
Re: [VOTE] Release Apache ManifoldCF 0.4-incubating, RC0
Hi. I checked 0.4 by running ant test, okay but one problem. In multiprocess-example, at default properties.xml, HSQLDB database requires 'org.apache.manifoldcf.hsqldbdatabasepath' property, containing a relative path: Now exception is thrown, so we need to add this property. Should I send a patch? Next? Regards, Shinichiro Abe On 2011/12/18, at 2:27, Karl Wright wrote: > I've again uploaded an apache-manifoldcf-0.4-incubating package which you > can download from http://people.apache.org/~kwright. If you agree > this should be released please vote +1. > > [Note that the release of this artifact is dependent on the release of > the three plugin packages upon which it depends. If we need to change > those packages we'll need to spin a new RC of this one. Also please > note that I've include SHA1 signatures for the first time, as per > Jukka's suggestion.] > > I apologize again for the earlier hiccup. This one is the real thing, > though, and passes all tests. > > Thanks! > Karl
[jira] [Commented] (CONNECTORS-323) *.sh in multiprocess-example doesn't work
[ https://issues.apache.org/jira/browse/CONNECTORS-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170703#comment-13170703 ] Shinichiro Abe commented on CONNECTORS-323: --- r1215025(trunk). Please pull it up to the release branch.Thank you! > *.sh in multiprocess-example doesn't work > - > > Key: CONNECTORS-323 > URL: https://issues.apache.org/jira/browse/CONNECTORS-323 > Project: ManifoldCF > Issue Type: Bug > Components: Framework agents process >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-323.patch > > > *.sh in multiprocess-example doesn't work.Here is a patch. -- 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] [Updated] (CONNECTORS-323) *.sh in multiprocess-example doesn't work
[ https://issues.apache.org/jira/browse/CONNECTORS-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-323: -- Attachment: CONNECTORS-323.patch > *.sh in multiprocess-example doesn't work > - > > Key: CONNECTORS-323 > URL: https://issues.apache.org/jira/browse/CONNECTORS-323 > Project: ManifoldCF > Issue Type: Bug > Components: Framework agents process >Affects Versions: ManifoldCF 0.4 > Reporter: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-323.patch > > > *.sh in multiprocess-example doesn't work.Here is a patch. -- 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] [Created] (CONNECTORS-323) *.sh in multiprocess-example doesn't work
*.sh in multiprocess-example doesn't work - Key: CONNECTORS-323 URL: https://issues.apache.org/jira/browse/CONNECTORS-323 Project: ManifoldCF Issue Type: Bug Components: Framework agents process Affects Versions: ManifoldCF 0.4 Reporter: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-323.patch *.sh in multiprocess-example doesn't work.Here is a patch. -- 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-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169952#comment-13169952 ] Shinichiro Abe commented on CONNECTORS-313: --- r1214610 for replace misspelled RegsiterConnectors.java with RegisterConnectors.java > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch, > register-draft.sh > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- 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-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169943#comment-13169943 ] Shinichiro Abe commented on CONNECTORS-313: --- r1214606 for example-multiprocess properties.xml > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch, > register-draft.sh > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- 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-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[
https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169940#comment-13169940
]
Shinichiro Abe commented on CONNECTORS-313:
---
I found the cause RegisterAll command doesn't work.
example-multiprocess properties.xml doesn't have the following:
{code:xml}
{code}
I'll commit soon.
> An example multi-process properties.xml delivered to the "dist" folder would
> be very helpful
>
>
> Key: CONNECTORS-313
> URL: https://issues.apache.org/jira/browse/CONNECTORS-313
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Build
> Affects Versions: ManifoldCF 0.4
> Reporter: Shinichiro Abe
>Assignee: Shinichiro Abe
>Priority: Minor
> Fix For: ManifoldCF 0.4
>
> Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch,
> register-draft.sh
>
>
> The multiprocess setup does not have an example properties.xml file. We
> should deliver one, in the right place so that all the scripts find it (the
> "dist" directory). It would also be helpful to deliver into this directory
> scripts for:
> - Registering all the connectors that were built
> - Starting the agents process
--
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-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169905#comment-13169905 ] Shinichiro Abe commented on CONNECTORS-313: --- Please wait. RegisterAll command doesn't work from r1214041. it creates db but doesn't insert records to connectors table. Now I don't know the cause. (I will change its name into InitializeAndRegister.) > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build > Affects Versions: ManifoldCF 0.4 > Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch, > register-draft.sh > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- 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-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169206#comment-13169206 ] Shinichiro Abe commented on CONNECTORS-313: --- I agree placing a script in dist/multi. But Do we need four commands? I think one command RegisterAll is only needed. RegisterAll perform dbcreate and register output/auth/repo connectors.And my question, what does Initialize command do? I'm sorry I misspelled Regsiter.java. I'll modify later. > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 > Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch, > register-draft.sh > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- 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-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169073#comment-13169073 ] Shinichiro Abe commented on CONNECTORS-313: --- r1214051. There is a incorrect mkdir(dist/example/connector-lib at framework/build.xml), so remove it. > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch, > register-draft.sh > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- 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-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168991#comment-13168991 ] Shinichiro Abe commented on CONNECTORS-313: --- Hi Mr.Karl, I'm ok your futher changes. I will test its rearrangement. > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch, > register-draft.sh > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- 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-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168947#comment-13168947 ] Shinichiro Abe commented on CONNECTORS-313: --- I Created a new command class: ./executecommand.sh org.apache.manifoldcf.crawler.RegisterAll. And I checked single/multi processes both. Please review me. Thank you. > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch, > register-draft.sh > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- 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-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168946#comment-13168946 ] Shinichiro Abe commented on CONNECTORS-313: --- branches/CONNECTORS-313: Committed revision 1214014. > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch, > register-draft.sh > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- 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: [VOTE] Release apache-manifoldcf-sharepoint-3.0-plugin 0.1-incubating
+1 Shinichiro Abe On 2011/12/09, at 19:10, Karl Wright wrote: > I've uploaded an > apache-manifoldcf-sharepoint-3.0-plugin-0.1-incubating package which > you can download from http://people.apache.org/~kwright. If you agree > this should be released please vote +1. > > Karl
Re: [VOTE] Release apache-manifoldcf-solr-3.x-plugin 0.1-incubating
Thank you. I see, then +1 Shinichiro Abe On 2011/12/13, at 19:19, Karl Wright wrote: > It's released based on the code in the current 3.x-dev branch. They > are about to release 3.6, and it is built within Solr/Lucene as a > module, so that is the number it gets. > > Karl > > On Tue, Dec 13, 2011 at 4:55 AM, Shinichiro Abe > wrote: >> Is it correct version of jar file? 3.5 is correct, isn't it ? >> >> apache-solr-mcf-3.6-SNAPSHOT.jar >> >> Shinichiro Abe >> >> On 2011/12/09, at 19:09, Karl Wright wrote: >> >>> I've uploaded an apache-manifoldcf-solr-3.x-plugin-0.1-incubating >>> package which you can download from http://people.apache.org/~kwright. >>> If you agree this should be released please vote +1. >>> >>> Karl >>
Re: [VOTE] Release apache-manifoldcf-solr-3.x-plugin 0.1-incubating
Is it correct version of jar file? 3.5 is correct, isn't it ? apache-solr-mcf-3.6-SNAPSHOT.jar Shinichiro Abe On 2011/12/09, at 19:09, Karl Wright wrote: > I've uploaded an apache-manifoldcf-solr-3.x-plugin-0.1-incubating > package which you can download from http://people.apache.org/~kwright. > If you agree this should be released please vote +1. > > Karl
Re: [VOTE] Release apache-manifoldcf-solr-4.x-plugin 0.1-incubating
+1 Shinichiro Abe On 2011/12/09, at 19:09, Karl Wright wrote: > I've uploaded an apache-manifoldcf-solr-4.x-plugin-0.1-incubating > package which you can download from http://people.apache.org/~kwright. > If you agree this should be released please vote +1. > > Karl
[jira] [Updated] (CONNECTORS-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-313: -- Attachment: register-draft.sh About register script, sorry, I don't know how to read from connectors.xml. How can this script read xml? > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch, > register-draft.sh > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- 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] [Updated] (CONNECTORS-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-313: -- Attachment: (was: CONNECTOR-313.patch) > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- 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] [Updated] (CONNECTORS-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-313: -- Attachment: CONNECTOR-313.patch > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- 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] [Updated] (CONNECTORS-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-313: -- Attachment: CONNECTOR-313.patch properties.xml is placed at dist folder in this patch. > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- 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-313) movedir-afterbuild
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167299#comment-13167299 ] Shinichiro Abe commented on CONNECTORS-313: --- Ok, I see. I understand we have to point MCF_HOME to dist/ folder when we use for multiprocess. Do we needed that properties.xml is placed to dist/ folder for out of the box multiprocess working? If not needed, I don't mind if this issue won't fix. > movedir-afterbuild > -- > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch > > > The scripts of processes/ and script-engine/ request its location under > $MCF_HOME. I want to move those dirs to beneath example/ after building. -- 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-313) movedir-afterbuild
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165986#comment-13165986 ] Shinichiro Abe commented on CONNECTORS-313: --- Because a user always needs to move those directories if using multi-process. Now we have to read excutecommand.sh inside so that processes/ dir is placed into correct path for multi-process working. I want to do that automatically. > movedir-afterbuild > -- > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 > Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTOR-313.patch > > > The scripts of processes/ and script-engine/ request its location under > $MCF_HOME. I want to move those dirs to beneath example/ after building. -- 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] [Updated] (CONNECTORS-313) movedir-afterbuild
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-313: -- Attachment: CONNECTOR-313.patch This is a draft patch. > movedir-afterbuild > -- > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 > Reporter: Shinichiro Abe > Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTOR-313.patch > > > The scripts of processes/ and script-engine/ request its location under > $MCF_HOME. I want to move those dirs to beneath example/ after building. -- 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] [Created] (CONNECTORS-313) movedir-afterbuild
movedir-afterbuild -- Key: CONNECTORS-313 URL: https://issues.apache.org/jira/browse/CONNECTORS-313 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.4 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 The scripts of processes/ and script-engine/ request its location under $MCF_HOME. I want to move those dirs to beneath example/ after building. -- 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] [Resolved] (CONNECTORS-297) Add a description of ant download-dependencies for Building the SharePoint connector to how-to-build-and-deploy.html.
[ https://issues.apache.org/jira/browse/CONNECTORS-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe resolved CONNECTORS-297. --- Resolution: Fixed > Add a description of ant download-dependencies for Building the SharePoint > connector to how-to-build-and-deploy.html. > - > > Key: CONNECTORS-297 > URL: https://issues.apache.org/jira/browse/CONNECTORS-297 > Project: ManifoldCF > Issue Type: Improvement > Components: Documentation >Affects Versions: ManifoldCF 0.4 > Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-297.patch > > > I add a statement below to "Building the SharePoint connector" at > how-to-build-and-deploy.html. > statement: > The wsdl files download will be done automatically if you type "ant > download-dependencies" from the root 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-297) Add a description of ant download-dependencies for Building the SharePoint connector to how-to-build-and-deploy.html.
[ https://issues.apache.org/jira/browse/CONNECTORS-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159095#comment-13159095 ] Shinichiro Abe commented on CONNECTORS-297: --- r1207757 > Add a description of ant download-dependencies for Building the SharePoint > connector to how-to-build-and-deploy.html. > - > > Key: CONNECTORS-297 > URL: https://issues.apache.org/jira/browse/CONNECTORS-297 > Project: ManifoldCF > Issue Type: Improvement > Components: Documentation >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-297.patch > > > I add a statement below to "Building the SharePoint connector" at > how-to-build-and-deploy.html. > statement: > The wsdl files download will be done automatically if you type "ant > download-dependencies" from the root 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] [Updated] (CONNECTORS-297) Add a description of ant download-dependencies for Building the SharePoint connector to how-to-build-and-deploy.html.
[ https://issues.apache.org/jira/browse/CONNECTORS-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-297: -- Attachment: CONNECTORS-297.patch I confirmed docs by patching it. I will commit. > Add a description of ant download-dependencies for Building the SharePoint > connector to how-to-build-and-deploy.html. > - > > Key: CONNECTORS-297 > URL: https://issues.apache.org/jira/browse/CONNECTORS-297 > Project: ManifoldCF > Issue Type: Improvement > Components: Documentation >Affects Versions: ManifoldCF 0.4 > Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-297.patch > > > I add a statement below to "Building the SharePoint connector" at > how-to-build-and-deploy.html. > statement: > The wsdl files download will be done automatically if you type "ant > download-dependencies" from the root 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] [Created] (CONNECTORS-297) Add a description of ant download-dependencies for Building the SharePoint connector to how-to-build-and-deploy.html.
Add a description of ant download-dependencies for Building the SharePoint connector to how-to-build-and-deploy.html. - Key: CONNECTORS-297 URL: https://issues.apache.org/jira/browse/CONNECTORS-297 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.4 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 I add a statement below to "Building the SharePoint connector" at how-to-build-and-deploy.html. statement: The wsdl files download will be done automatically if you type "ant download-dependencies" from the root 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] [Resolved] (CONNECTORS-283) Upgrade to jcifs.jar 1.3.17
[ https://issues.apache.org/jira/browse/CONNECTORS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe resolved CONNECTORS-283. --- Resolution: Fixed r1189564 > Upgrade to jcifs.jar 1.3.17 > --- > > Key: CONNECTORS-283 > URL: https://issues.apache.org/jira/browse/CONNECTORS-283 > Project: ManifoldCF > Issue Type: Improvement > Components: Build, JCIFS connector >Affects Versions: ManifoldCF 0.4 > Reporter: Shinichiro Abe > Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-283.patch > > > I upgrade new jcifs version because of missing link of previous version > 1.3.16. -- 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] [Created] (CONNECTORS-283) Upgrade to jcifs.jar 1.3.17
Upgrade to jcifs.jar 1.3.17 --- Key: CONNECTORS-283 URL: https://issues.apache.org/jira/browse/CONNECTORS-283 Project: ManifoldCF Issue Type: Improvement Components: Build, JCIFS connector Affects Versions: ManifoldCF 0.4 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-283.patch I upgrade new jcifs version because of missing link of previous version 1.3.16. -- 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] [Updated] (CONNECTORS-283) Upgrade to jcifs.jar 1.3.17
[ https://issues.apache.org/jira/browse/CONNECTORS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-283: -- Attachment: CONNECTORS-283.patch > Upgrade to jcifs.jar 1.3.17 > --- > > Key: CONNECTORS-283 > URL: https://issues.apache.org/jira/browse/CONNECTORS-283 > Project: ManifoldCF > Issue Type: Improvement > Components: Build, JCIFS connector >Affects Versions: ManifoldCF 0.4 > Reporter: Shinichiro Abe > Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-283.patch > > > I upgrade new jcifs version because of missing link of previous version > 1.3.16. -- 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-262) Ant build could download WSDL's for SharePoint, if the public Microsoft SharePoint site has them
[ https://issues.apache.org/jira/browse/CONNECTORS-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117153#comment-13117153 ] Shinichiro Abe commented on CONNECTORS-262: --- I couldn't find the download site. Please teach me url. > Ant build could download WSDL's for SharePoint, if the public Microsoft > SharePoint site has them > > > Key: CONNECTORS-262 > URL: https://issues.apache.org/jira/browse/CONNECTORS-262 > Project: ManifoldCF > Issue Type: Improvement > Components: Build, SharePoint connector >Affects Versions: ManifoldCF 0.4 > Reporter: Karl Wright >Assignee: Shinichiro Abe > Fix For: ManifoldCF 0.4 > > > There is a public Microsoft SharePoint site. If we can get at it, we might > be able to download the Microsoft WSDL's we need from it automatically during > the "download-dependencies" target. -- 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] [Resolved] (CONNECTORS-257) Input-able response lifetime for Active Directory authority
[ https://issues.apache.org/jira/browse/CONNECTORS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe resolved CONNECTORS-257. --- Resolution: Fixed > Input-able response lifetime for Active Directory authority > --- > > Key: CONNECTORS-257 > URL: https://issues.apache.org/jira/browse/CONNECTORS-257 > Project: ManifoldCF > Issue Type: Improvement > Components: Active Directory authority >Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 > Reporter: Shinichiro Abe > Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-257-1.patch, CONNECTORS-257-2.patch, > CONNECTORS-257-3.patch > > > The access tokens are cached for one minute, and up to 1000 different > users' access tokens will be cached at any one time. > The access token's cache per username remains idle before expiring. > Its expiration time depends response lifetime, and > expiration time is updated after looking up the cache. > Currently response lifetime is 1 minute. > Since I want not to access Active Directory frequently, > I make this response lifetime to be input-able for users. -- 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-257) Input-able response lifetime for Active Directory authority
[ https://issues.apache.org/jira/browse/CONNECTORS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117028#comment-13117028 ] Shinichiro Abe commented on CONNECTORS-257: --- r1177173 > Input-able response lifetime for Active Directory authority > --- > > Key: CONNECTORS-257 > URL: https://issues.apache.org/jira/browse/CONNECTORS-257 > Project: ManifoldCF > Issue Type: Improvement > Components: Active Directory authority >Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 > Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-257-1.patch, CONNECTORS-257-2.patch, > CONNECTORS-257-3.patch > > > The access tokens are cached for one minute, and up to 1000 different > users' access tokens will be cached at any one time. > The access token's cache per username remains idle before expiring. > Its expiration time depends response lifetime, and > expiration time is updated after looking up the cache. > Currently response lifetime is 1 minute. > Since I want not to access Active Directory frequently, > I make this response lifetime to be input-able for users. -- 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-257) Input-able response lifetime for Active Directory authority
[ https://issues.apache.org/jira/browse/CONNECTORS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116957#comment-13116957 ] Shinichiro Abe commented on CONNECTORS-257: --- Thank you. I confirmed patch 3. I'll commit soon. > Input-able response lifetime for Active Directory authority > --- > > Key: CONNECTORS-257 > URL: https://issues.apache.org/jira/browse/CONNECTORS-257 > Project: ManifoldCF > Issue Type: Improvement > Components: Active Directory authority >Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-257-1.patch, CONNECTORS-257-2.patch, > CONNECTORS-257-3.patch > > > The access tokens are cached for one minute, and up to 1000 different > users' access tokens will be cached at any one time. > The access token's cache per username remains idle before expiring. > Its expiration time depends response lifetime, and > expiration time is updated after looking up the cache. > Currently response lifetime is 1 minute. > Since I want not to access Active Directory frequently, > I make this response lifetime to be input-able for users. -- 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] [Updated] (CONNECTORS-257) Input-able response lifetime for Active Directory authority
[ https://issues.apache.org/jira/browse/CONNECTORS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-257: -- Attachment: CONNECTORS-257-2.patch Sorry for delay. This patch is including LRU cache. But changing static class into member is not done. What should I do? > Input-able response lifetime for Active Directory authority > --- > > Key: CONNECTORS-257 > URL: https://issues.apache.org/jira/browse/CONNECTORS-257 > Project: ManifoldCF > Issue Type: Improvement > Components: Active Directory authority >Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 > Reporter: Shinichiro Abe > Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-257-1.patch, CONNECTORS-257-2.patch > > > The access tokens are cached for one minute, and up to 1000 different > users' access tokens will be cached at any one time. > The access token's cache per username remains idle before expiring. > Its expiration time depends response lifetime, and > expiration time is updated after looking up the cache. > Currently response lifetime is 1 minute. > Since I want not to access Active Directory frequently, > I make this response lifetime to be input-able for users. -- 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] [Updated] (CONNECTORS-257) Input-able response lifetime for Active Directory authority
[ https://issues.apache.org/jira/browse/CONNECTORS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-257: -- Description: The access tokens are cached for one minute, and up to 1000 different users' access tokens will be cached at any one time. The access token's cache per username remains idle before expiring. Its expiration time depends response lifetime, and expiration time is updated after looking up the cache. Currently response lifetime is 1 minute. Since I want not to access Active Directory frequently, I make this response lifetime to be input-able for users. was: The access tokens are cached for one minute, and up to 1000 different users' access tokens will be cached at any one time. The access token's cache per username remains idle before expiring. Its expiration time depends response lifetime, and expiration time is updated after looking up the cache. Currently response lifetime is 1 minute. Since I want to access Active Directory frequently, I make this response lifetime to be input-able for users. > Input-able response lifetime for Active Directory authority > --- > > Key: CONNECTORS-257 > URL: https://issues.apache.org/jira/browse/CONNECTORS-257 > Project: ManifoldCF > Issue Type: Improvement > Components: Active Directory authority >Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 > Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-257-1.patch > > > The access tokens are cached for one minute, and up to 1000 different > users' access tokens will be cached at any one time. > The access token's cache per username remains idle before expiring. > Its expiration time depends response lifetime, and > expiration time is updated after looking up the cache. > Currently response lifetime is 1 minute. > Since I want not to access Active Directory frequently, > I make this response lifetime to be input-able for users. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-257) Input-able response lifetime for Active Directory authority
Input-able response lifetime for Active Directory authority --- Key: CONNECTORS-257 URL: https://issues.apache.org/jira/browse/CONNECTORS-257 Project: ManifoldCF Issue Type: Improvement Components: Active Directory authority Affects Versions: ManifoldCF 0.2, ManifoldCF 0.1, ManifoldCF 0.3 Reporter: Shinichiro Abe Assignee: Shinichiro Abe Priority: Minor Fix For: ManifoldCF 0.4 Attachments: CONNECTORS-257-1.patch The access tokens are cached for one minute, and up to 1000 different users' access tokens will be cached at any one time. The access token's cache per username remains idle before expiring. Its expiration time depends response lifetime, and expiration time is updated after looking up the cache. Currently response lifetime is 1 minute. Since I want to access Active Directory frequently, I make this response lifetime to be input-able for users. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-257) Input-able response lifetime for Active Directory authority
[ https://issues.apache.org/jira/browse/CONNECTORS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-257: -- Attachment: CONNECTORS-257-1.patch > Input-able response lifetime for Active Directory authority > --- > > Key: CONNECTORS-257 > URL: https://issues.apache.org/jira/browse/CONNECTORS-257 > Project: ManifoldCF > Issue Type: Improvement > Components: Active Directory authority >Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 > Reporter: Shinichiro Abe > Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-257-1.patch > > > The access tokens are cached for one minute, and up to 1000 different > users' access tokens will be cached at any one time. > The access token's cache per username remains idle before expiring. > Its expiration time depends response lifetime, and > expiration time is updated after looking up the cache. > Currently response lifetime is 1 minute. > Since I want to access Active Directory frequently, > I make this response lifetime to be input-able for users. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-252) clean up build, dist and lib of each connector after build
[ https://issues.apache.org/jira/browse/CONNECTORS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe resolved CONNECTORS-252. --- Resolution: Fixed > clean up build, dist and lib of each connector after build > -- > > Key: CONNECTORS-252 > URL: https://issues.apache.org/jira/browse/CONNECTORS-252 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 > Reporter: Shinichiro Abe > Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-252-1.patch, CONNECTORS-252-2.patch, > CONNECTORS-252.patch > > > After running "ant build", folder size increases about five times. Building > resources in connectors are expected not to use, except for test output. I > want to clean up this after build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-252) clean up build, dist and lib of each connector after build
[ https://issues.apache.org/jira/browse/CONNECTORS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104487#comment-13104487 ] Shinichiro Abe commented on CONNECTORS-252: --- r1170600 > clean up build, dist and lib of each connector after build > -- > > Key: CONNECTORS-252 > URL: https://issues.apache.org/jira/browse/CONNECTORS-252 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 > Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-252-1.patch, CONNECTORS-252-2.patch, > CONNECTORS-252.patch > > > After running "ant build", folder size increases about five times. Building > resources in connectors are expected not to use, except for test output. I > want to clean up this after build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-252) clean up build, dist and lib of each connector after build
[ https://issues.apache.org/jira/browse/CONNECTORS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-252: -- Attachment: CONNECTORS-252-2.patch > clean up build, dist and lib of each connector after build > -- > > Key: CONNECTORS-252 > URL: https://issues.apache.org/jira/browse/CONNECTORS-252 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 > Reporter: Shinichiro Abe > Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-252-1.patch, CONNECTORS-252-2.patch, > CONNECTORS-252.patch > > > After running "ant build", folder size increases about five times. Building > resources in connectors are expected not to use, except for test output. I > want to clean up this after build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-252) clean up build, dist and lib of each connector after build
[ https://issues.apache.org/jira/browse/CONNECTORS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-252: -- Attachment: (was: CONNECTORS-252-2.patch) > clean up build, dist and lib of each connector after build > -- > > Key: CONNECTORS-252 > URL: https://issues.apache.org/jira/browse/CONNECTORS-252 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 > Reporter: Shinichiro Abe > Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-252-1.patch, CONNECTORS-252.patch > > > After running "ant build", folder size increases about five times. Building > resources in connectors are expected not to use, except for test output. I > want to clean up this after build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-252) clean up build, dist and lib of each connector after build
[ https://issues.apache.org/jira/browse/CONNECTORS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-252: -- Attachment: CONNECTORS-252-2.patch I think "build" would be better to depend "build-dev". > clean up build, dist and lib of each connector after build > -- > > Key: CONNECTORS-252 > URL: https://issues.apache.org/jira/browse/CONNECTORS-252 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 > Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-252-1.patch, CONNECTORS-252.patch > > > After running "ant build", folder size increases about five times. Building > resources in connectors are expected not to use, except for test output. I > want to clean up this after build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-252) clean up build, dist and lib of each connector after build
[ https://issues.apache.org/jira/browse/CONNECTORS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-252: -- Attachment: (was: CONNECTORS-252-1.patch) > clean up build, dist and lib of each connector after build > -- > > Key: CONNECTORS-252 > URL: https://issues.apache.org/jira/browse/CONNECTORS-252 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 > Reporter: Shinichiro Abe > Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-252-1.patch, CONNECTORS-252.patch > > > After running "ant build", folder size increases about five times. Building > resources in connectors are expected not to use, except for test output. I > want to clean up this after build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-252) clean up build, dist and lib of each connector after build
[ https://issues.apache.org/jira/browse/CONNECTORS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-252: -- Attachment: CONNECTORS-252-1.patch CONNECTORS-252-1.patch I add "build-dev" for development build. > clean up build, dist and lib of each connector after build > -- > > Key: CONNECTORS-252 > URL: https://issues.apache.org/jira/browse/CONNECTORS-252 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-252-1.patch, CONNECTORS-252.patch > > > After running "ant build", folder size increases about five times. Building > resources in connectors are expected not to use, except for test output. I > want to clean up this after build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-254) Bad request when posting 0 byte file to Solr
[
https://issues.apache.org/jira/browse/CONNECTORS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103670#comment-13103670
]
Shinichiro Abe commented on CONNECTORS-254:
---
I'm sorry.
I modified post.sh and posted 0 byte file. But the exception isn't thrown in
this case. Is this a GET?
---
FILES=$*
URL=http://localhost:8983/solr/update/extract?literal.id=1
for f in $FILES; do
curl $URL --data-binary @$f -H 'Content-type:application/octet-stream'
done
---
> Bad request when posting 0 byte file to Solr
>
>
> Key: CONNECTORS-254
> URL: https://issues.apache.org/jira/browse/CONNECTORS-254
> Project: ManifoldCF
> Issue Type: Bug
> Components: Lucene/SOLR connector
>Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
>Reporter: Shinichiro Abe
>Priority: Minor
> Fix For: ManifoldCF 0.3
>
> Attachments: CONNECTORS-254-1.patch, sample0byte.zip
>
>
> It seems that httpposter brings about bad request when posting 0 byte file.
> Solr log say the below. "missing content stream". Status code is 400.
> On the other hand when using Solr request handler without MCF, this exception
> is not thrown and the posting 0 byte files is indexed normally.
>
> 2011/09/13 12:30:40 org.apache.solr.core.SolrCore execute
> ???: [] webapp=/solr path=/update/extract
> params={literal.id=file:/Users/abe/Desktop/1/no-content/no-content.txt&literal.uri=/Users/abe/Desktop/1/no-content/no-content.txt}
> status=400 QTime=367
> 2011/09/13 12:30:40 org.apache.solr.common.SolrException log
> ?v???I: org.apache.solr.common.SolrException: missing content stream
> at
> org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:62)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-254) Bad request when posting 0 byte file to Solr
[
https://issues.apache.org/jira/browse/CONNECTORS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103632#comment-13103632
]
Shinichiro Abe commented on CONNECTORS-254:
---
I agree. My approach was hasty. I'll examine again.(especially adding a space)
At least the following results in posting normally on Solr. the exception isn't
thrown.
curl
"http://localhost:8983/solr/update/extract?literal.id=1&stream.file=/path/to/0bytefile&commit=true";
I want to make the same behavior for httpposter. What do you think about this?
> Bad request when posting 0 byte file to Solr
>
>
> Key: CONNECTORS-254
> URL: https://issues.apache.org/jira/browse/CONNECTORS-254
> Project: ManifoldCF
> Issue Type: Bug
> Components: Lucene/SOLR connector
>Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
>Reporter: Shinichiro Abe
>Priority: Minor
> Fix For: ManifoldCF 0.3
>
> Attachments: CONNECTORS-254-1.patch, sample0byte.zip
>
>
> It seems that httpposter brings about bad request when posting 0 byte file.
> Solr log say the below. "missing content stream". Status code is 400.
> On the other hand when using Solr request handler without MCF, this exception
> is not thrown and the posting 0 byte files is indexed normally.
>
> 2011/09/13 12:30:40 org.apache.solr.core.SolrCore execute
> ???: [] webapp=/solr path=/update/extract
> params={literal.id=file:/Users/abe/Desktop/1/no-content/no-content.txt&literal.uri=/Users/abe/Desktop/1/no-content/no-content.txt}
> status=400 QTime=367
> 2011/09/13 12:30:40 org.apache.solr.common.SolrException log
> ?v???I: org.apache.solr.common.SolrException: missing content stream
> at
> org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:62)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-254) Bad request when posting 0 byte file to Solr
[
https://issues.apache.org/jira/browse/CONNECTORS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shinichiro Abe updated CONNECTORS-254:
--
Attachment: CONNECTORS-254-1.patch
When the stream length is zero, it replaces space. If this procedure is okay,
I'll modify the indent around that.
> Bad request when posting 0 byte file to Solr
>
>
> Key: CONNECTORS-254
> URL: https://issues.apache.org/jira/browse/CONNECTORS-254
> Project: ManifoldCF
> Issue Type: Bug
> Components: Lucene/SOLR connector
>Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
> Reporter: Shinichiro Abe
>Priority: Minor
> Fix For: ManifoldCF 0.3
>
> Attachments: CONNECTORS-254-1.patch, sample0byte.zip
>
>
> It seems that httpposter brings about bad request when posting 0 byte file.
> Solr log say the below. "missing content stream". Status code is 400.
> On the other hand when using Solr request handler without MCF, this exception
> is not thrown and the posting 0 byte files is indexed normally.
>
> 2011/09/13 12:30:40 org.apache.solr.core.SolrCore execute
> ???: [] webapp=/solr path=/update/extract
> params={literal.id=file:/Users/abe/Desktop/1/no-content/no-content.txt&literal.uri=/Users/abe/Desktop/1/no-content/no-content.txt}
> status=400 QTime=367
> 2011/09/13 12:30:40 org.apache.solr.common.SolrException log
> ?v???I: org.apache.solr.common.SolrException: missing content stream
> at
> org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:62)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-254) Bad request when posting 0 byte file to Solr
[
https://issues.apache.org/jira/browse/CONNECTORS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shinichiro Abe updated CONNECTORS-254:
--
Attachment: sample0byte.zip
> Bad request when posting 0 byte file to Solr
>
>
> Key: CONNECTORS-254
> URL: https://issues.apache.org/jira/browse/CONNECTORS-254
> Project: ManifoldCF
> Issue Type: Bug
> Components: Lucene/SOLR connector
>Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
> Reporter: Shinichiro Abe
>Priority: Minor
> Fix For: ManifoldCF 0.3
>
> Attachments: sample0byte.zip
>
>
> It seems that httpposter brings about bad request when posting 0 byte file.
> Solr log say the below. "missing content stream". Status code is 400.
> On the other hand when using Solr request handler without MCF, this exception
> is not thrown and the posting 0 byte files is indexed normally.
>
> 2011/09/13 12:30:40 org.apache.solr.core.SolrCore execute
> ???: [] webapp=/solr path=/update/extract
> params={literal.id=file:/Users/abe/Desktop/1/no-content/no-content.txt&literal.uri=/Users/abe/Desktop/1/no-content/no-content.txt}
> status=400 QTime=367
> 2011/09/13 12:30:40 org.apache.solr.common.SolrException log
> ?v???I: org.apache.solr.common.SolrException: missing content stream
> at
> org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:62)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-254) Bad request when posting 0 byte file to Solr
Bad request when posting 0 byte file to Solr
Key: CONNECTORS-254
URL: https://issues.apache.org/jira/browse/CONNECTORS-254
Project: ManifoldCF
Issue Type: Bug
Components: Lucene/SOLR connector
Affects Versions: ManifoldCF 0.2, ManifoldCF 0.1, ManifoldCF 0.3
Reporter: Shinichiro Abe
Priority: Minor
Fix For: ManifoldCF 0.3
It seems that httpposter brings about bad request when posting 0 byte file.
Solr log say the below. "missing content stream". Status code is 400.
On the other hand when using Solr request handler without MCF, this exception
is not thrown and the posting 0 byte files is indexed normally.
2011/09/13 12:30:40 org.apache.solr.core.SolrCore execute
???: [] webapp=/solr path=/update/extract
params={literal.id=file:/Users/abe/Desktop/1/no-content/no-content.txt&literal.uri=/Users/abe/Desktop/1/no-content/no-content.txt}
status=400 QTime=367
2011/09/13 12:30:40 org.apache.solr.common.SolrException log
?v???I: org.apache.solr.common.SolrException: missing content stream
at
org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:62)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-251) jcifs.jar download
[ https://issues.apache.org/jira/browse/CONNECTORS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe resolved CONNECTORS-251. --- Resolution: Fixed > jcifs.jar download > -- > > Key: CONNECTORS-251 > URL: https://issues.apache.org/jira/browse/CONNECTORS-251 > Project: ManifoldCF > Issue Type: Improvement > Components: JCIFS connector >Affects Versions: ManifoldCF 0.4 > Reporter: Shinichiro Abe > Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-251-1.patch, CONNECTORS-251-2.patch, > CONNECTORS-251.patch > > > jcifs.jar should be downloaded automatically at jcifs/build.xml as a approach > similar to pom.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
