Re: The ManifoldCF PPMC welcomes Shinichiro Abe as a ManifoldCF committer!
Welcome Shinichiro :-) Tommaso 2011/5/13 Karl Wright > Please join us in welcoming Shinichiro to the ManifoldCF team! > > Karl >
Re: Tommaso Teofili has joined ManifoldCF as a new mentor!
Thanks all for your trust, I'll do my best to help ManifoldCF get his way through the Incubator. Tommaso 2011/5/16 Robert Muir > welcome Tommaso! > > On Sun, May 15, 2011 at 4:41 PM, Karl Wright wrote: > > Please join me in thanking Tommaso for taking on this responsibility! > > > > Karl > > >
Re: The burning technical issues of the day
Hello Karl, thanks so much again for the warm welcome and for these insights. I agree with you that testability is a major concern we need to engage and get sorted. One thing I think right now is that having tests rely on a testing infrastructure would possibly expose ManifoldCF to this issue again in case of maintenance, versions evolution and so on therefore, although I still have to investigate if that can be sorted technically for the supported systems, my "design time" opinion is that we should try to mock those systems. Did you try to mock any of them yet? Does this sound good/bad to you? Regards, Tommaso 2011/5/17 Karl Wright > For those who have just entered the ManifoldCF project, I'd like to > first extend my congratulations once again! > > You are probably still trying to figure out exactly what's going on > and where we are going. Unfortunately, this being Apache, I cannot > actually answer your question, because you are part of the process > now, and you will now be able to act on your own ideas and goals for > the project. But in the interests of planning and consensus building, > I'd like to share my thoughts as to what I think are the major > technical issues the project faces. > > The first and foremost issue is one of testability. ManifoldCF is > unique in that every connector requires a system to test against. In > some cases this is a proprietary system, such as Documentum or > LiveLink. In other cases, it's a large number of web servers. > > When MetaCarta developed the project in the first place, we had a > stable of VMs against which our tests worked. They had proprietary > software installed in some cases, or some Apache hackery to emulate a > large number of individual web sites. When MetaCarta assets were sold > to qBase, those assets included those VMs. We desperately need > something like this again. I've tried to get access to the old > MetaCarta VM's, but qBase has not yet granted this, and may never > grant it due to ongoing technical reasons. > > Given this, it seems that we need some way of doing the same thing. > It would be great to hear your ideas, especially if you have access to > any of the proprietary systems we support and would be willing to set > up and maintain testing infrastructure. > > Again, welcome to our new committers and new mentor! > Karl >
Re: The burning technical issues of the day
2011/5/17 Koji Sekiguchi > I've been thinking mock for unit test, too. > > Does anyone know there are any projects that connect proprietary software > in Apache? We can consult them, if any. > > Tommaso, do you know Alchemy Annotator uses mock for the test in UIMA? > Yes, I wrote it :-) That is a basic mocking as there is a clear API for the alchemyapi.comwebservice and I only wrote an implementation returning a predefined XML response, so nothing special actually. In the past I remember I used Selenium [1] to write mocked integration tests while writing a proxy but I remember that was hard to maintain in a changing environment. Let's keep the discussion and ideas flow :-) Tommaso [1] : http://seleniumhq.org/ > > Koji > -- > http://www.rondhuit.com/en/ > > > (11/05/17 22:10), Tommaso Teofili wrote: > >> Hello Karl, >> thanks so much again for the warm welcome and for these insights. >> I agree with you that testability is a major concern we need to engage and >> get sorted. >> One thing I think right now is that having tests rely on a testing >> infrastructure would possibly expose ManifoldCF to this issue again in >> case >> of maintenance, versions evolution and so on therefore, although I still >> have to investigate if that can be sorted technically for the supported >> systems, my "design time" opinion is that we should try to mock those >> systems. >> Did you try to mock any of them yet? Does this sound good/bad to you? >> Regards, >> Tommaso >> >> >> 2011/5/17 Karl Wright >> >> For those who have just entered the ManifoldCF project, I'd like to >>> first extend my congratulations once again! >>> >>> You are probably still trying to figure out exactly what's going on >>> and where we are going. Unfortunately, this being Apache, I cannot >>> actually answer your question, because you are part of the process >>> now, and you will now be able to act on your own ideas and goals for >>> the project. But in the interests of planning and consensus building, >>> I'd like to share my thoughts as to what I think are the major >>> technical issues the project faces. >>> >>> The first and foremost issue is one of testability. ManifoldCF is >>> unique in that every connector requires a system to test against. In >>> some cases this is a proprietary system, such as Documentum or >>> LiveLink. In other cases, it's a large number of web servers. >>> >>> When MetaCarta developed the project in the first place, we had a >>> stable of VMs against which our tests worked. They had proprietary >>> software installed in some cases, or some Apache hackery to emulate a >>> large number of individual web sites. When MetaCarta assets were sold >>> to qBase, those assets included those VMs. We desperately need >>> something like this again. I've tried to get access to the old >>> MetaCarta VM's, but qBase has not yet granted this, and may never >>> grant it due to ongoing technical reasons. >>> >>> Given this, it seems that we need some way of doing the same thing. >>> It would be great to hear your ideas, especially if you have access to >>> any of the proprietary systems we support and would be willing to set >>> up and maintain testing infrastructure. >>> >>> Again, welcome to our new committers and new mentor! >>> Karl >>> >>> >> > >
Re: Criteria for graduation?
It'd be good that all of us take a look at the Incubator graduation page [1]. Even if that's "only" a checklist it does help us define what still has to be done. In my opinion, ManifoldCF has demonstrated the ability to make releases but we should work on community growth; also diversity is an important concern to address, looking at Lucene Connectors Framework incubating proposal [2] I see committers have different affiliations but if there are 3 active committers that doesn't sound so helpful in granting diversity. Regards, Tommaso [1] : http://incubator.apache.org/guides/graduation.html#checklist [2] : http://wiki.apache.org/incubator/LuceneConnectorFrameworkProposal 2011/5/28 Otis Gospodnetic > I was going to say the developer/contrib community needs to be bigger, but > I see > there are now 3 active committers, which looks like good progress > though > maybe still not enough to exit incubator? Not sure. > > Is http://incubator.apache.org/connectors/who.html up to date? No, looks > like > it's not... > > Otis > > Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch > Lucene ecosystem search :: http://search-lucene.com/ > > > > - Original Message > > From: Karl Wright > > To: connectors-dev > > Sent: Thu, May 26, 2011 9:59:48 AM > > Subject: Criteria for graduation? > > > > Does anyone have a firm sense of what additional milestones will be > > necessary for ManifoldCF to meet to graduate from the incubator? > > > > Karl > > >
Re: [VOTE] Adopt Java 1.5 as the minimum Java release for ManifoldCF
+1 (already voted on the issue) Tommaso 2011/5/31 Koji Sekiguchi > +1. Let's adopt 1.5 before we go TLP. > > koji > -- > http://www.rondhuit.com/en/ > > > (11/05/31 8:32), Karl Wright wrote: > >> Please have a look at CONNECTORS-203 and vote +1 if you think it's >> time to move beyond Java 1.4 at the source level, to Java 1.5. I did >> some work on this over the weekend and managed to convince myself that >> a migration to a newer Java version will have no obvious ill effects. >> But I'd like your thoughts. >> >> Especially interesting will be whether or not we try to maintain >> backwards compatibility in the connector interfaces: IConnector, >> IRepositoryConnector, IAuthorityConnector, and IOutputConnector. I >> have some ideas how I could bring these into the modern world in a >> relatively painless manner, should the community require it. But I'd >> like to hear your views as to whether we *should* work towards that >> end, or be willing to disrupt our early adopters in this process. >> >> Karl >> >>
Re: Incubator PMC/Board report for June 2011 (connectors-dev@incubator.apache.org)
I think the successful release should be mentioned too :-) Tommaso 2011/6/1 Karl Wright > The March report looked like this: > > ManifoldCF > > --Description-- > > ManifoldCF is an incremental crawler framework and set of connectors > designed to pull documents from various kinds of repositories into > search engine indexes or other targets. The current bevy of connectors > includes Documentum (EMC), FileNet (IBM), LiveLink (OpenText), Meridio > (Autonomy), SharePoint (Microsoft), RSS feeds, and web content. > ManifoldCF also provides components for individual document security > within a target search engine, so that repository security access > conventions can be enforced in the search results. > > ManifoldCF has been in incubation since January, 2010. It was > originally a planned subproject of Lucene but is now a likely > top-level project. > > --A list of the three most important issues to address in the move > towards graduation-- > > 1. We need at least three additional active committers, as well as > additional users and repeat contributors > 2. We should have at least one or two more releases before graduating > 3. We'd like to see long-term contributions for project testing, > especially infrastructure access > > --Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to > be aware of?-- > > All issues have been addressed to our satisfaction at this time. > > --How has the community developed since the last report?-- > > A book is being written, and has entered the early-release phase, > available from Manning Publishing. We continue to have user community > interest. We've had a number of extremely helpful bug reports and > contributions from the field. The active committer list remains > short, however. > > --How has the project developed since the last report?-- > > An 0.1 release was made on January 31, 2011, and another release is > being considered. Contributions extending the FileNet connector have > been made, as well as contributions to the Solr connector. > > Signed off by mentor: Grant Ingersoll > > I'd like to mention our new committers and mentor, and the completion > of the book. Anything else that should be added? > Karl > > > -- Forwarded message -- > From: > Date: Wed, Jun 1, 2011 at 10:00 AM > Subject: Incubator PMC/Board report for June 2011 > (connectors-dev@incubator.apache.org) > To: connectors-dev@incubator.apache.org > > > Dear ManifoldCF Developers, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. > It is an initial reminder to give you plenty of time to prepare your > quarterly > board report. > > The board meeting is scheduled for Wed, 15 June 2011, 10 am Pacific. The > report > for your podling will form a part of the Incubator PMC report. The > Incubator PMC > requires your report to be submitted one week before the board meeting, to > allow > sufficient time for review. > > Please submit your report with sufficient time to allow the incubator PMC, > and > subsequently board members to review and digest. Again, the very latest you > should submit your report is one week prior to the board meeting. > > Thanks, > > The Apache Incubator PMC > > Submitting your Report > -- > > Your report should contain the following: > > * Your project name > * A brief description of your project, which assumes no knowledge of > the project > or necessarily of its field > * A list of the three most important issues to address in the move towards > graduation. > * Any issues that the Incubator PMC or ASF Board might wish/need to be > aware of > * How has the community developed since the last report > * How has the project developed since the last report. > > This should be appended to the Incubator Wiki page at: > > http://wiki.apache.org/incubator/June2011 > > Note: This manually populated. You may need to wait a little before this > page is > created from a template. > > Mentors > --- > Mentors should review reports for their project(s) and sign them off on the > Incubator wiki page. Signing off reports shows that you are following the > project - projects that are not signed may raise alarms for the Incubator > PMC. > > Incubator PMC >
Re: Incubator PMC/Board report for June 2011 (connectors-dev@incubator.apache.org)
it sounds good to me, any others? Tommaso 2011/6/1 Karl Wright > Here's my proposed text: > > ManifoldCF > > --Description-- > > ManifoldCF is an incremental crawler framework and set of connectors > designed to pull documents from various kinds of repositories into > search engine indexes or other targets. The current bevy of connectors > includes Documentum (EMC), FileNet (IBM), LiveLink (OpenText), Meridio > (Autonomy), SharePoint (Microsoft), RSS feeds, and web content. > ManifoldCF also provides components for individual document security > within a target search engine, so that repository security access > conventions can be enforced in the search results. > > ManifoldCF has been in incubation since January, 2010. It was > originally a planned subproject of Lucene but is now a likely > top-level project. > > --A list of the three most important issues to address in the move > towards graduation-- > > 1. We need at least one additional active committers, as well as > additional users and repeat contributors > 2. We may want another release before graduating > 3. We'd like to see long-term contributions for project testing, > especially infrastructure access > > --Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to > be aware of?-- > > All issues have been addressed to our satisfaction at this time. > > --How has the community developed since the last report?-- > > A book has being completed, and is becoming available in early-release > form, available from Manning Publishing. We have signed up two new > committers and one new mentor. We continue to have user community > interest. We've had a number of extremely helpful bug reports and > contributions from the field. > > --How has the project developed since the last report?-- > > An 0.1 release was made on January 31, 2011, and a 0.2 release > occurred on May 17, 2011. Another release is being considered. > > Signed off by mentor: > > > > Karl > > On Wed, Jun 1, 2011 at 10:23 AM, Tommaso Teofili > wrote: > > I think the successful release should be mentioned too :-) > > Tommaso > > > > 2011/6/1 Karl Wright > > > >> The March report looked like this: > >> > >> ManifoldCF > >> > >> --Description-- > >> > >> ManifoldCF is an incremental crawler framework and set of connectors > >> designed to pull documents from various kinds of repositories into > >> search engine indexes or other targets. The current bevy of connectors > >> includes Documentum (EMC), FileNet (IBM), LiveLink (OpenText), Meridio > >> (Autonomy), SharePoint (Microsoft), RSS feeds, and web content. > >> ManifoldCF also provides components for individual document security > >> within a target search engine, so that repository security access > >> conventions can be enforced in the search results. > >> > >> ManifoldCF has been in incubation since January, 2010. It was > >> originally a planned subproject of Lucene but is now a likely > >> top-level project. > >> > >> --A list of the three most important issues to address in the move > >> towards graduation-- > >> > >> 1. We need at least three additional active committers, as well as > >> additional users and repeat contributors > >> 2. We should have at least one or two more releases before graduating > >> 3. We'd like to see long-term contributions for project testing, > >> especially infrastructure access > >> > >> --Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to > >> be aware of?-- > >> > >> All issues have been addressed to our satisfaction at this time. > >> > >> --How has the community developed since the last report?-- > >> > >> A book is being written, and has entered the early-release phase, > >> available from Manning Publishing. We continue to have user community > >> interest. We've had a number of extremely helpful bug reports and > >> contributions from the field. The active committer list remains > >> short, however. > >> > >> --How has the project developed since the last report?-- > >> > >> An 0.1 release was made on January 31, 2011, and another release is > >> being considered. Contributions extending the FileNet connector have > >> been made, as well as contributions to the Solr connector. > >> > >> Signed off by mentor: Grant Ingersoll > >> > >> I'd like to mention our new committers and mentor, and the completio
Re: Incubator PMC/Board report for June 2011 (connectors-dev@incubator.apache.org)
I've signed off our report, thanks Karl for taking care. Tommaso 2011/6/2 Karl Wright > I've now edited the page accordingly. Let me know of any changes > you'd like to see. > Karl > > On Thu, Jun 2, 2011 at 4:18 AM, Tommaso Teofili > wrote: > > it sounds good to me, any others? > > Tommaso > > > > 2011/6/1 Karl Wright > > > >> Here's my proposed text: > >> > >> ManifoldCF > >> > >> --Description-- > >> > >> ManifoldCF is an incremental crawler framework and set of connectors > >> designed to pull documents from various kinds of repositories into > >> search engine indexes or other targets. The current bevy of connectors > >> includes Documentum (EMC), FileNet (IBM), LiveLink (OpenText), Meridio > >> (Autonomy), SharePoint (Microsoft), RSS feeds, and web content. > >> ManifoldCF also provides components for individual document security > >> within a target search engine, so that repository security access > >> conventions can be enforced in the search results. > >> > >> ManifoldCF has been in incubation since January, 2010. It was > >> originally a planned subproject of Lucene but is now a likely > >> top-level project. > >> > >> --A list of the three most important issues to address in the move > >> towards graduation-- > >> > >> 1. We need at least one additional active committers, as well as > >> additional users and repeat contributors > >> 2. We may want another release before graduating > >> 3. We'd like to see long-term contributions for project testing, > >> especially infrastructure access > >> > >> --Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to > >> be aware of?-- > >> > >> All issues have been addressed to our satisfaction at this time. > >> > >> --How has the community developed since the last report?-- > >> > >> A book has being completed, and is becoming available in early-release > >> form, available from Manning Publishing. We have signed up two new > >> committers and one new mentor. We continue to have user community > >> interest. We've had a number of extremely helpful bug reports and > >> contributions from the field. > >> > >> --How has the project developed since the last report?-- > >> > >> An 0.1 release was made on January 31, 2011, and a 0.2 release > >> occurred on May 17, 2011. Another release is being considered. > >> > >> Signed off by mentor: > >> > >> > >> > >> Karl > >> > >> On Wed, Jun 1, 2011 at 10:23 AM, Tommaso Teofili > >> wrote: > >> > I think the successful release should be mentioned too :-) > >> > Tommaso > >> > > >> > 2011/6/1 Karl Wright > >> > > >> >> The March report looked like this: > >> >> > >> >> ManifoldCF > >> >> > >> >> --Description-- > >> >> > >> >> ManifoldCF is an incremental crawler framework and set of connectors > >> >> designed to pull documents from various kinds of repositories into > >> >> search engine indexes or other targets. The current bevy of > connectors > >> >> includes Documentum (EMC), FileNet (IBM), LiveLink (OpenText), > Meridio > >> >> (Autonomy), SharePoint (Microsoft), RSS feeds, and web content. > >> >> ManifoldCF also provides components for individual document security > >> >> within a target search engine, so that repository security access > >> >> conventions can be enforced in the search results. > >> >> > >> >> ManifoldCF has been in incubation since January, 2010. It was > >> >> originally a planned subproject of Lucene but is now a likely > >> >> top-level project. > >> >> > >> >> --A list of the three most important issues to address in the move > >> >> towards graduation-- > >> >> > >> >> 1. We need at least three additional active committers, as well as > >> >> additional users and repeat contributors > >> >> 2. We should have at least one or two more releases before graduating > >> >> 3. We'd like to see long-term contributions for project testing, > >> >> especially infrastructure access > >> >> > >> >> --Any issues that the Inc
Re: Problems during committing
Hi PJ, your problems should be fixed now. Cheers, Tommaso 2011/8/30 Piergiorgio Lucidi > Infrastructure said me that I don't have permissions to commit on Manifold > because my account now is associated only to incubator. > > I forwarded to Tommaso the problem and he confirmed that last week the > committership procedure has changed. > That's why now I can't execute a commit, my account needs to be associated > to lucene-connectors group. > > Tommaso should solve this problem soon. > > Thank you all for the support. > Piergiorgio > > 2011/8/30 Karl Wright > > > If they don't get back to you soon, I'd ask Tommaso to talk to his > > infrastructure contact to see if they can figure out what's wrong. > > > > Karl > > > > > > On Tue, Aug 30, 2011 at 3:13 AM, Piergiorgio Lucidi > > wrote: > > > I created an issue on Infrastructure in Jira. > > > I hope that they help me quickly. > > > > > > Thank you. > > > Piergiorgio > > > > > > 2011/8/30 Karl Wright > > > > > >> Still works for me. > > >> If you can't figure out what changed, you might want to file an INFRA > > >> ticket in Jira. > > >> > > >> Karl > > >> > > >> > > >> On Mon, Aug 29, 2011 at 1:54 PM, Karl Wright > > wrote: > > >> > I haven't had trouble, but the last time I tried a commit was at > 9:00 > > >> > AM EDT this morning. > > >> > Karl > > >> > > > >> > On Mon, Aug 29, 2011 at 12:18 PM, Piergiorgio Lucidi > > >> > wrote: > > >> >> Hi guys, > > >> >> > > >> >> I can't commit anymore on the project, do you have the same > problem? > > >> >> > > >> >> The SVN server returns to me the following message for any file > that > > I'm > > >> >> trying to commit: > > >> >> > > >> >> svn: Commit failed (details follow): > > >> >>> svn: CHECKOUT of > > >> >>> > > >> > > > '/repos/asf/!svn/ver/1056132/incubator/lcf/trunk/site/src/documentation/content/xdocs/end-user-documentation.xml': > > >> >>> 403 Forbidden (https://svn.apache.org) > > >> >> > > >> >> > > >> >> I tried to directly access to > > >> >> > > >> > > > https://svn.apache.org/repos/asf/!svn/ver/1056132/incubator/lcf/trunk/site/src/documentation/content/xdocs/end-user-documentation.xmland > > >> >> this file from the browser could be read correctly. > > >> >> > > >> >> Could be a problem of the Apache server certificate that now is not > > >> valid? > > >> >> > > >> >> Thank you any suggestions. > > >> >> Piergiorgio > > >> >> > > >> >> -- > > >> >> Piergiorgio Lucidi > > >> >> http://about.me/piergiorgiolucidi > > >> >> > > >> > > > >> > > > > > > > > > > > > -- > > > Piergiorgio Lucidi > > > http://about.me/piergiorgiolucidi > > > > > > > > > -- > Piergiorgio Lucidi > http://about.me/piergiorgiolucidi >
Re: Incubator PMC/Board report for September 2011 (connectors-dev@incubator.apache.org)
nice one Karl :) Tommaso 2011/9/1 Karl Wright > Here's a report proposal: > > ManifoldCF > > --Description-- > > ManifoldCF is an incremental crawler framework and set of connectors > designed to pull documents from various kinds of repositories into > search engine indexes or other targets. The current bevy of repository > connectors includes Documentum (EMC), FileNet (IBM), LiveLink > (OpenText), Meridio (Autonomy), SharePoint (Microsoft), JDBC, CIFS > file systems, CMIS repositories, RSS feeds, and web content. Output > support includes Solr, MetaCarta GTS, and OpenSearchServer. > ManifoldCF also provides components for individual document security > within a target search engine, so that repository security access > conventions can be enforced in the search results. > > ManifoldCF has been in incubation since January, 2010. It was > originally a planned subproject of Lucene but is now a likely > top-level project. > > --A list of the three most important issues to address in the move > towards graduation-- > > 1. We need at least one additional active committer, as well as > additional users and repeat contributors > 2. We want to finish the current release before graduating > 3. We'd like to see long-term contributions for project testing, > especially infrastructure access > > --Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to > be aware of?-- > > All issues have been addressed to our satisfaction at this time. > > --How has the community developed since the last report?-- > > A book has been completed, and is now available in early-release form, > available from Manning Publishing, at http://www.manning.com/wright. > We have signed up a new committer in this quarter and are discussing a > second. One of our mentors (Grant Ingersoll) resigned. > > We continue to have user community interest. We are participating > this year in both Apache Eurocon and Apache North America. We've had > a number of extremely helpful contributions from the field, including > the CMIS connector and the OpenSearchServer output connector. We have > started to discuss graduation from the incubator, which may come to > pass by the end of the year. > > --How has the project developed since the last report?-- > > An 0.1 release was made on January 31, 2011, and a 0.2 release > occurred on May 17, 2011. Another release is scheduled for September > 15, 2011, and will contain significant new features, including two new > connectors and a client scripting language. > > Signed off by mentor: > > > On Thu, Sep 1, 2011 at 10:00 AM, wrote: > > Dear ManifoldCF Developers, > > > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. > > It is an initial reminder to give you plenty of time to prepare your > quarterly > > board report. > > > > The board meeting is scheduled for Wed, 21 September 2011, 10 am > Pacific. The report > > for your podling will form a part of the Incubator PMC report. The > Incubator PMC > > requires your report to be submitted one week before the board meeting, > to allow > > sufficient time for review. > > > > Please submit your report with sufficient time to allow the incubator > PMC, and > > subsequently board members to review and digest. Again, the very latest > you > > should submit your report is one week prior to the board meeting. > > > > Thanks, > > > > The Apache Incubator PMC > > > > Submitting your Report > > -- > > > > Your report should contain the following: > > > > * Your project name > > * A brief description of your project, which assumes no knowledge of the > project > > or necessarily of its field > > * A list of the three most important issues to address in the move > towards > > graduation. > > * Any issues that the Incubator PMC or ASF Board might wish/need to be > aware of > > * How has the community developed since the last report > > * How has the project developed since the last report. > > > > This should be appended to the Incubator Wiki page at: > > > > http://wiki.apache.org/incubator/September2011 > > > > Note: This manually populated. You may need to wait a little before this > page is > > created from a template. > > > > Mentors > > --- > > Mentors should review reports for their project(s) and sign them off on > the > > Incubator wiki page. Signing off reports shows that you are following the > > project - projects that are not signed may raise alarms for the Incubator > PMC. > > > > Incubator PMC > > > > >
Re: Maven release conventions?
Nope, using the maven-release-plugin [1] would be enough as it takes care of checking/changing versions both in the dependencies (if there is any -SNAPSHOT dependency) and in the modules' versions. A very quickly look at the process goes like running mvn release:prepare which signs artifact, creating a svn tag with the release version and preparing the poms for the next development version, then if the RC is ok run mvn release:perform otherwise if there is any problem run mvn release:rollback to bring back the trunk to the -SNAPSHOT version. One more nice thing would be to add the apache-pom as parent pom of our manifoldcf-parent: org.apache apache 9 this will allow using the -Papache-release option (enabling the apache-release profile) to create reports and sign artifacts. Hope this helps. Tommaso 2011/9/8 Karl Wright > Hi folks, > > I'm handling the 0.3-incubating release of MCF, and I'm trying to > figure out what the tags in the maven pom files should say. > They currently say 0.3-SNAPSHOT. Should I edit them in the release > branch to be just 0.3? > > Karl >
Re: 1.0 release, and graduation
Hello Karl, all 2011/9/19 Karl Wright > Folks, > I'd like to begin discussion about the next release, currently labeled > 0.4, and also our potential for graduation from the incubator. What > I'd like is a sense of: > > (a) what we are still missing as far as incubator graduation is concerned, at the moment I think we're in the right direction towards the graduation (see the clutch report [1] which however doesn't count the new committers/mentors as our page on Incubator website has to be updated). > and > (b) what a 1.0 release might look like to everyone > my point here relates also to the graduation: I think we're building a nice community and the ManifoldCF code is being bettered every day but it seems to me there are some (few) parts which need some refactoring as they can't work as they are now (i.e.: support to MySQL DBs), also in my opinion we should choose one of Maven or Ant and drop the other building system as I fear this could confuse new users/devs. A minor thing in my opinion is that a restyle of the UI would make ManifoldCF some more "nice" to use, however this can be pretty personal and less important than functional requirements. > > Please try to be as concrete as possible. My own personal goal is to > see this happen by the end of the year, more or less +1 > To that end > I've already begun triaging JIRA tickets for the 0.4 release that I > think would be appropriate for a 1.0 release. > > It's entirely possible that some things that people feel strongly > about may not be doable in that time frame, but so be it. This may > also be true of our status as a project. > > What do others think? All the best. Tommaso [1] : http://incubator.apache.org/clutch.html [2] : http://incubator.apache.org/projects/manifoldcf.html > Thanks, > Karl >
Re: 1.0 release, and graduation
Hello Karl 2011/9/21 Karl Wright > Hi Tommaso, > > Thanks for your feedback! > > Are you in a position to update the status page? I don't think I can. > I should be able to do it, will try and see if I can get that updated finally :) > If you disagree please point me in the right direction.. > > > As far as the technical aspects: > (1) If MySQL support is something important then I will triage the > appropriate ticket accordingly. I'm curious where this requirement > comes from, though. > this requirement just comes from my little experience; since I started mentoring here I tried to see if/where ManifoldCF would fit a particular business case (dealing almost always with managing communication between some source and Solr) and quite always I got asked if it could be used with MySQL instead of PostgreSQL. Personally I always prefer the latter for it's just faster (at least where I've seen meaningful comparisons) but often MySQL gets chosen as a DBMS maybe just for the reason that it's more popular. So this comes from some people asking me about the possibility of using ManifoldCF with MySQL instead of PostgreSQL. However this is not a 'blocker', just I think that it should give much architecture flexibility (and, thus, adoption) to the project. > (2) I'm not sure it is reasonable to go with one build system over > another. Lucene/Solr has been having this battle for years. I > thought we might just learn from that experience and try to be more > flexible. There are excellent technical reasons to have each - for > instance, building Debian packages works much better with Ant, and > Eclipse works much better with Maven. > I don't like "wars" as well about which one *is* better, maybe it's just a matter of use case and personal preferences. However I like what you say about trying to be more flexible so I am +1 to your position. I have some experience with Maven so let me know if you need my help in tweaking that part of the build. > (3) I would love to have the UI look cooler. Stylistic work on the UI > is definitely not the right job for me though. Now, Piergiorgio > mentioned going to a spring-based UI but I'm not sure that will fix > anything stylistically, and it might well require redefinition of the > connector interfaces, which would be a bad thing at this point, so I > don't see much benefit to this architectural change proposal. Is this > what you were thinking of, or were you more thinking of look and feel? > My concern at the moment with this point is more related to the look and feel than on the appropriate (MVC) framework since I am not sure I'd want to inject another framework (I think l&f can be better than the current one just using servlets and some JS). However if changing the framework would fasten the process of enhancing the UI style I'm ok for that too, on the contrary if that would affect connector interfaces it maybe a huge work to do right now. I'd love to hear other opinions on this and other topics as I'm sure MySQL and UI aren't the only open points the community would like to get sorted. Have a nice day you all. Cheers, Tommaso > > Karl > > > On Tue, Sep 20, 2011 at 5:51 PM, Tommaso Teofili > wrote: > > Hello Karl, all > > > > > > 2011/9/19 Karl Wright > > > >> Folks, > >> I'd like to begin discussion about the next release, currently labeled > >> 0.4, and also our potential for graduation from the incubator. What > >> I'd like is a sense of: > >> > >> (a) what we are still missing as far as incubator graduation is > concerned, > > > > > > at the moment I think we're in the right direction towards the graduation > > (see the clutch report [1] which however doesn't count the new > > committers/mentors as our page on Incubator website has to be updated). > > > > > >> and > >> (b) what a 1.0 release might look like to everyone > >> > > > > my point here relates also to the graduation: I think we're building a > nice > > community and the ManifoldCF code is being bettered every day but it > seems > > to me there are some (few) parts which need some refactoring as they > can't > > work as they are now (i.e.: support to MySQL DBs), also in my opinion we > > should choose one of Maven or Ant and drop the other building system as I > > fear this could confuse new users/devs. > > A minor thing in my opinion is that a restyle of the UI would make > > ManifoldCF some more "nice" to use, however this can be pretty personal > and > > less important than functional requirements. > > > > >
Re: ManifoldCF 0.4-incubating release
I am taking a look at the stuff regarding licenses and the like for the Alfresco connector (help from Jukka would be appreciated here) which I'd like to see included in the next release. Tommaso 2011/12/6 Karl Wright > Hi all, > > I think we're just about done with ManifoldCF 0.4-incubating. There's > one ticket outstanding that belongs to Erlend, but I'm happy to > postpone it if he is not yet ready to work on it. Once that's > decided, is there any reason we should not go ahead and spin a release > candidate? Does anyone want to volunteer to run some of the load > tests to be sure nothing unexpected has crept in? > > Thanks! > Karl >
Re: Delivery of source of integration packages for 0.4-incubating
Hi all 2011/12/8 Karl Wright > Hi Folks, > > The manifoldcf 0.4-incubating release does not include sources for the > following components that are meant to be installed on repositories, > in order to enable the corresponding connector: > > - the solr 3.x security plugin > - the solr 4.x security plugin > - the SharePoint 3.0 MCPermissions.asmx web service > - the Meridio user lookup web service > > I have put together all of these under > https://svn.apache.org/repos/asf/incubator/lcf/integration. Each of > them has their own license, notice, etc. My plan was to release them > independently and somewhat before ManifoldCF 0.4-incubating, as > separate packages with different names and version numbers (e.g. > "Apache SharePoint 3.0 ManifoldCF Plugin", > "apache-sharepoint-3.0-manifoldcf-plugin-0.1-incubating"). > > First, some things to note: > (1) I have no intention to deliver anything other than source > zips/tar.gzs for these, and of course corresponding signature files. > Why only sources? I guess (not checked yet) the Sharepoint / Meridio ones could not be redistributed as binaries with an Apache License but I think the Solr stuff can be. > (2) I have no idea what the incubator release process should look like > for something like this. Tommaso, what do you think? Should we put > the packages up and request an incubator vote on each one? > We may create a module called "MCF-integration" which aggregates the sources for each of these modules. I've seen this being done in the past where the source release contained all the modules' sources while the single source artifacts could be retrieved from the Apache Maven repository. Otherwise if you want to have separate source packages being released separately then yes we have to call a vote on general@ for each of them. > I'd like to get the ball rolling quickly, before the holidays mess us > up, since these are prerequisites for the main 0.4 release. > > Karl > Tommaso
Re: Proposed March incubator report
sounds good, thanks Karl (signed it off now). Tommaso 2012/2/27 Karl Wright > I've edited the Wiki page accordingly, and now wait for a mentor signature. > > Karl > > On Thu, Feb 23, 2012 at 9:30 AM, Piergiorgio Lucidi > wrote: > > Hi Karl, > > > > it's ok for me, thank you for writing the report. > > > > Piergiorgio > > > > Il 23 febbraio 2012 14:53, Karl Wright ha scritto: > >> Hi all, > >> > >> What do you think of this proposed report for March? > >> > >> Karl > >> > >> > >> ManifoldCF > >> > >> --Description-- > >> > >> ManifoldCF is an incremental crawler framework and set of connectors > >> designed to pull documents from various kinds of repositories into > >> search engine indexes or other targets. The current bevy of repository > >> connectors includes Documentum (EMC), FileNet (IBM), LiveLink > >> (OpenText), Meridio (Autonomy), SharePoint (Microsoft), JDBC, CIFS > >> file systems, CMIS repositories, Alfresco, RSS feeds, Wiki content, > >> and web content. Output support includes Solr, MetaCarta GTS, and > >> OpenSearchServer. > >> > >> ManifoldCF also provides components for individual document security > >> within a target search engine, so that repository security access > >> conventions can be enforced in search results. > >> > >> ManifoldCF has been in incubation since January, 2010. It was > >> originally a planned subproject of Lucene but is now a likely > >> top-level project. > >> > >> --A list of the three most important issues to address in the move > >> towards graduation-- > >> > >> 1. We believe we've reached graduation threshold. More committers and > >> greater breadth in the committer base is always welcome, of course. > >> 2. We need the current committer base to continue to broaden their > commits > >> to new areas of the project > >> > >> --Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to > >> be aware of?-- > >> > >> We have an outstanding request to Apache Legal to determine whether we > >> can distribute PDF files containing Japanese characters rendered with > the IPA > >> family of fonts. It would be great to know the answer prior to the > release of > >> ManifoldCF 0.5-incubating. A ticket is open (LEGAL-123) but no activity > >> has taken place on it. > >> > >> --How has the community developed since the last report?-- > >> > >> We've received sustained contributions from multiple individuals, and > >> signed up one new committer. Deployments of the project software are > >> also now clearly reaching a much broader audience than they were a year > >> ago, and this trend seems likely to continue. A second revision of > >> ManifoldCF in Action is also planned to keep up with developments on the > >> project. > >> > >> --How has the project developed since the last report?-- > >> > >> An 0.1 release was made on January 31, 2011, and a 0.2 release > >> occurred on May 17, 2011. The 0.3 release occurred on September > >> 20, 2011. The 0.4 release took place on February 2, 2012. The fifth > >> incubator release is planned for March 30, 2012, and will include an > >> ElasticSearch connector, full internationalization support and a > Japanese > >> localization, MySQL support, automated UI testing, and more. > > > > -- > > Piergiorgio Lucidi > > http://www.open4dev.com >
Re: Heads up
Hi Karl, I'm trying to catch up all the points raised in the general@ thread in order to better understand them and what we actually need (not) to do. Will come back on this as soon as I can with more comments. Tommaso 2012/3/28 Karl Wright > Dear Developers, > > In case you haven't been following our fortunes in the > gene...@incubator.apache.org list, it has become clear that ManifoldCF > has resurrected an old battle having to do with rules pertaining to > the legality of including binaries in a source release. It is > therefore my opinion that the 0.5-incubating release will not occur > until we substantially rework our build process, especially where it > pertains to dependencies. A short way of stating the problem is that > binary dependencies can no longer be included in the source zip/tar.gz > that gets voted on. A request has also been made for us to remove all > previous releases that violate this principle, which is all of them. > I am waiting to see how the discussion pans out before acting on this > request. > > Our build and release process was modeled, unfortunately, on other > Apache Java projects, and these too have come under fire from the > Board because the same practice has been followed, in some cases for > more than a decade. I'm not sure what ManifoldCF did to become the > focal point of this discussion, but there it is - and my personal > opinion is that there is no chance of us releasing 0.5 without making > significant changes. > > I've captured what I think needs to be done in CONNECTORS-437, and > have been working through an ordered process of first setting up an > svn-based repository for those binaries which have been patched or > otherwise contain fixes not present in official released code, with a > long-term goal in mind of eventually having all dependencies come from > the Maven repository. This is in svn under > "https://svn.apache.org/repos/asf/incubator/lcf/bin-dist";. I will > also be extending the "ant download-dependencies" target to pull in > ALL binaries, not just those which come with incompatible licenses. > The ticket is probably incomplete; I'll be adding more stuff as I find > it. > > Thanks, > Karl >
Re: [VOTE] Upgrade ManifoldCF to jdk 1.6 prior to next release
big +1. Tommaso 2012/4/11 Karl Wright > Folks, > > When doing the dependency rework, it became clear that many of our > binary dependencies are "stuck" without fixes or upgrades because we > are still using jdk 1.5. I'd like to get a sense from the community > whether everyone thinks we should abandon support for jdk1.5 in our > next release. The "pros" of such a move include allowing us to > upgrade to jetty 7 (which brings in a number of bug fixes), tomcat 7 > components, and off-the-shelf hsqldb builds. I cannot at this time > identify any obvious "cons". Please let me know your opinion. +1 to > upgrade, from me. > > Thanks, > Karl >
Re: Thoughts on graduation?
Hi Karl, I think times are mature for talking about graduation, it may be helpful to explicitly get through the graduation requirements [1][2] and open a [DISCUSSION] thread before start voting to check everyone is happy with it and also, for example, to choose the right target (TLP or subproject). However I'm confident we can graduate soon. Tommaso [1] : http://incubator.apache.org/guides/graduation.html [2] : http://incubator.apache.org/guides/graduation.html#checklist 2012/4/23 Karl Wright > It may be a little too soon after the last (somewhat traumatic) > release, but I'm thinking we've pretty well met the diversity > requirement now for graduation. Should we open a graduation vote in > the incubator at this time? > > Karl >
Re: Thoughts on graduation?
Hi Karl 2012/4/23 Karl Wright > Hi Tommaso, > > I didn't see anything in the checklist we hadn't done. Indeed, for > some things (like the name) we've done it more than once. Do you > think we're missing anything? Do you think the incubator page is > sufficiently up to date as well? Looked reasonable to me... > same here, just I wanted to remind us to have a look in order to double check, I think we're fine. > > Are we agreed that ManifoldCF would graduate as a TLP at this time? > The Lucene PMC dropped us some two years ago so it would be > appropriate, I think. > +1 just since that needs to be explicitly figured out we need that at least the PPMC is aware and happy with that. Tommaso > > Karl > > On Mon, Apr 23, 2012 at 8:05 AM, Tommaso Teofili > wrote: > > Hi Karl, > > I think times are mature for talking about graduation, it may be helpful > to > > explicitly get through the graduation requirements [1][2] and open a > > [DISCUSSION] thread before start voting to check everyone is happy with > it > > and also, for example, to choose the right target (TLP or subproject). > > However I'm confident we can graduate soon. > > Tommaso > > > > [1] : http://incubator.apache.org/guides/graduation.html > > [2] : http://incubator.apache.org/guides/graduation.html#checklist > > > > 2012/4/23 Karl Wright > > > >> It may be a little too soon after the last (somewhat traumatic) > >> release, but I'm thinking we've pretty well met the diversity > >> requirement now for graduation. Should we open a graduation vote in > >> the incubator at this time? > >> > >> Karl > >> >
Re: [VOTE] Propose graduation of ManifoldCF from the Incubator as a Top Level Project
+1 Cheers, Tommaso 2012/4/25 Jukka Zitting > Hi, > > On Tue, Apr 24, 2012 at 12:08 PM, 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. > > +1 > > BR, > > Jukka Zitting >
Re: [VOTE] Graduation resolution for ManifoldCF
+1 Tommaso 2012/5/2 Jukka Zitting > +1 > > Jukka Zitting > > 1.5.2012 14.18 "Karl Wright" kirjoitti: > > > > 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 >
Re: FW: ASF Board Meeting Summary - May 16, 2012
Thanks and congratulations to you all for this great achievement ! Cheers Tommaso 2012/5/16 Piergiorgio Lucidi > Hi Karl, > > this is a great news! > > Congratulations for all the people that contributed on the project, this is > a very important step! > > Thank you all! > > Cheers, > Piergiorgio > > 2012/5/16 Karl Wright > > > Congratulations to all - we are now an official Apache project! > > > > Karl > > > > Sent from my Windows Phone > > From: Doug Cutting > > Sent: 5/16/2012 4:32 PM > > To: committ...@apache.org > > Subject: ASF Board Meeting Summary - May 16, 2012 > > The May board meeting took place on the 16th. > > > > The following directors were present: > > > > Shane Curcuru > > Doug Cutting > > Bertrand Delacretaz > > Roy T. Fielding > > Jim Jagielski > > Daniel Kulp > > Brett Porter > > Sam Ruby > > Greg Stein > > > > The following officers were present: > > > > Noirin Plunkett > > Craig L Russell > > > > The following guests were present: > > > > Gavin McDonald > > Hadrian Zbarcea > > > > The April minutes were approved. > > > > All of the received reports to the board were approved. > > > > The following reports were not received and are expected next month: > > > > Status report for the Apache Abdera Project > > Status report for the Apache Attic Project > > Status report for the Apache Creadur Project > > Status report for the Apache XMLBeans Project > > > > The following resolutions were passed unaminously: > > > > A. Change the Apache James Project Chair (Eric Charles, VP) > > B. Establish the Apache Hama Project (Edward J. Yoon, VP) > > C. Establish the Apache MRUnit Project (Brock Noland, VP) > > D. Establish the Apache Giraph Project (Avery Ching, VP) > > E. Establish the Apache ManifoldCF Project (Karl Wright, VP) > > F. Change the Apache MINA Project Chair (Emmanuel Lecharny, VP) > > G. Change the Apache Tcl Project Chair (Massimo Manghi, VP) > > H. Change the Apache Web Services Project Chair (Sagara Gunathunga) > > I. Change the Apache Continuum Project Chair (Brett Porter, VP) > > J. Approve the 2012-2013FY Budget > > > > The next board meeting will be on the 20th of June. > > > > Doug > > > > -- > > Piergiorgio Lucidi > > http://www.open4dev.com > > > > >
Re: Proposed first graduation step: Moving the repository
2012/5/17 Karl Wright > Looks like I don't have permissions to do this. I suppose I would > need to open an infra ticket? > Yes, I think so. Tommaso > Karl > > On Wed, May 16, 2012 at 10:25 PM, Karl Wright wrote: > > Folks, > > > > Heads up: Now that we've graduated, I'd like to move the repository > > from https://svn.apache.org/repos/asf/incubator/lcf to > > https://svn.apache.org/repos/asf/manifoldcf. This, of course, will > > mean that all workspaces will need to do a "svn switch" operation to > > change their path. "svn help switch" should give you sufficient hints > > as to how. > > > > I'm planning to do the move tomorrow morning, as soon as Abe-san is > > done producing a 0.5.1 RC0 release candidate. Please object if you > > want me to hold off. > > > > [I'm hoping, of course, that I now have the proper permissions to do > > this. We'll see shortly.] > > > > Karl >
[jira] [Commented] (CONNECTORS-203) Consider porting ManifoldCF to Java 1.5 code standards
[ https://issues.apache.org/jira/browse/CONNECTORS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041518#comment-13041518 ] Tommaso Teofili commented on CONNECTORS-203: as it's a wide scope change, it sounds good to me. > Consider porting ManifoldCF to Java 1.5 code standards > -- > > Key: CONNECTORS-203 > URL: https://issues.apache.org/jira/browse/CONNECTORS-203 > Project: ManifoldCF > Issue Type: Improvement > Components: Active Directory authority, Authority Service, Build, > Documentation, Documentum connector, File system connector, FileNet > connector, Framework agents process, Framework core, Framework crawler agent, > GTS connector, JCIFS connector, JDBC connector, LiveLink connector, > Lucene/SOLR connector, Meridio connector, RSS connector, SharePoint > connector, Web connector >Affects Versions: ManifoldCF 0.3 >Reporter: Karl Wright > > Consider porting ManifoldCF to Java 1.5 standards. This includes (but is not > limited to): > - build files > - removing use of "enum" variable name > - introducing generics in both implementation code and interfaces (cautiously) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156621#comment-13156621 ] Tommaso Teofili commented on CONNECTORS-287: according to [1] software under : - CDDL may be included in binary form within an Apache product if the inclusion is appropriately labeled - CPL 1.0 may be included in binary form within an Apache product if the inclusion is appropriately labeled - Apache is obviously ok so I think we're ok with regards to Alfresco WebServices Client as long as we highlight the CDDL and CPL pieces in the NOTICE file. [1] : http://apache.org/legal/resolved.html > An Alfresco connector would be helpful > -- > > Key: CONNECTORS-287 > URL: https://issues.apache.org/jira/browse/CONNECTORS-287 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi > Original Estimate: 120h > Remaining Estimate: 120h > > The idea of this connector is based on the fact that there are many Alfresco > installations that don't yet support the CMIS protocol (2.1-2.9). > I'm starting to think about the Alfresco Repository Connector. > Alfresco doesn't expose any REST API to execute Lucene queries without adding > some custom WebScripts. I would like to implement a connector that doesn't > need to install any other custom plugin and that it can work with any > Alfresco 2.x out of the box installation. > The unique search service exposed by Alfresco via REST is a keyword search > service, but it is not useful for our connector. > I think that the right way to follow is to use the Alfresco Web Services API, > this API is based on the SOAP protocol and we have a specific Alfresco Web > Services Client provided by Alfresco. -- 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-288) An ElasticSearch connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200692#comment-13200692 ] Tommaso Teofili commented on CONNECTORS-288: Nice thing Luce, looking forward to a patch for it :) > An ElasticSearch connector would be helpful > --- > > Key: CONNECTORS-288 > URL: https://issues.apache.org/jira/browse/CONNECTORS-288 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi > Fix For: ManifoldCF next > > Original Estimate: 120h > Remaining Estimate: 120h > > An ElasticSearch connector could be very useful to spread the use of > ManifoldCF -- 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] [Issue Comment Edited] (CONNECTORS-288) An ElasticSearch connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200692#comment-13200692 ] Tommaso Teofili edited comment on CONNECTORS-288 at 2/5/12 8:37 AM: Nice thing Luca, looking forward to a patch for it :) was (Author: teofili): Nice thing Luce, looking forward to a patch for it :) > An ElasticSearch connector would be helpful > --- > > Key: CONNECTORS-288 > URL: https://issues.apache.org/jira/browse/CONNECTORS-288 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi > Fix For: ManifoldCF next > > Original Estimate: 120h > Remaining Estimate: 120h > > An ElasticSearch connector could be very useful to spread the use of > ManifoldCF -- 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
