Re: Incubating Chemistry (Was: IP clearance for the Chemistry contribution)
Hi, On Tue, Apr 21, 2009 at 12:12 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: * Anyone else interested in joining as an initial committer? Dominique? It's of course possible to join also later, but then we'll need to go through the standard from-patches-to-committership process. Oops, sorry for being late! I added myself to the list of initial committer, thanks for the reminder. Kind regards Dominique
Re: Incubating Chemistry (Was: IP clearance for the Chemistry contribution)
I am very interested in this project also, but I think it would be much too early for me to get commitership on this, as I need to first prove myself again, as an alumni of Jackrabbit :) Regards, Serge
[jira] Updated: (JCR-2057) When creating multiple repository instances pointing to the same home, opening a second session will remove the .lock file
[ https://issues.apache.org/jira/browse/JCR-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-2057: --- Fix Version/s: (was: 1.6.0) 1.5.5 Merged to the 1.5 branch in revision 767069. When creating multiple repository instances pointing to the same home, opening a second session will remove the .lock file -- Key: JCR-2057 URL: https://issues.apache.org/jira/browse/JCR-2057 Project: Jackrabbit Content Repository Issue Type: Bug Components: jackrabbit-core Affects Versions: core 1.4.7, 1.5.3 Environment: Ubuntu Intrepid Reporter: Sébastien Launay Fix For: 1.5.5 Attachments: JCR-2057-2009-04-07.zip The following test case can be used to reproduce the bug: Repository repo1 = new TransientRepository(repoConfig); Session session1_1 = repo1.login(...); Session session2_2 = repo1.login(...); Repository repo2 = new TransientRepository(repoConfig); // Will not fail (expected) Session session2_1 = repo2.login(...); // Will fail with javax.jcr.RepositoryException: The repository home /tmp/_repository appears to be already locked by the current process (expected) Session session2_2 = repo2.login(...); // Will work! Repository repo3 = new TransientRepository(repoConfig); // Will not fail either (expected) Session session3_1 = repo3.login(...); // Will fail with javax.jcr.RepositoryException: The repository home /tmp/_repository appears to be already locked by the current process (expected) Session session3_2 = repo3.login(...); // Will fail with javax.jcr.RepositoryException: Directory was previously created with a different LockFactory instance Open the first session in repo2 will fails but will also remove the .lock file, thus the second session will succeed and may corrupt the repository because there are multiple session opened from multiple repository. The same behaviour occurs for repo3, the .lock file is removed but it is a slightly different case as a new exception will be thrown while creating the Lucene index. This is a clearly a twisted case as repositories pointing to the same home must not be created simultaneously but i think that it must be more robust to prevent data corruption. I reproduce the bug on JR 1.4.7 and 1.5.3 but i think it affects at least all versions of JR 1.5.3. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2071) IndexMerger throws null pointer exception without stacktrace
[ https://issues.apache.org/jira/browse/JCR-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-2071: --- Component/s: jackrabbit-core Fix Version/s: (was: 1.6.0) 1.5.5 Merged to the 1.5 branch in revision 767069. IndexMerger throws null pointer exception without stacktrace Key: JCR-2071 URL: https://issues.apache.org/jira/browse/JCR-2071 Project: Jackrabbit Content Repository Issue Type: Bug Components: jackrabbit-core Affects Versions: 1.5.0 Environment: Windows OS (XP, Vista) Linux RHEL Reporter: Chris Schmidt Fix For: 1.5.5 Attachments: IndexMerger.patch I get the following errors in my log file randomly. It seems to happen most often when creating the lucene indices, but has happened at other times as well: [IndexMerger] ERROR - Error while merging indexes: java.lang.NullPointerException The code at org.apache.jackrabbit.core.query.lucene.IndexMerger line 344 appears to be the point where the error is logged, but no other information is provided because the throwable isn't sent to the log (only the toString() version of the exception). I haven't been able to tell if any indexes are corrupt when this happens. I suggest that the logger be changed to determine where the null pointer is coming from first, then resolve the actual issue that is occurring. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Jackrabbit 1.5.5 release plan
Hi, On Wed, Apr 1, 2009 at 10:11 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: More generally, with the 1.5.4 release candidate tagged and out for review, I'm moving forward with the 1.5.5 release. I'm just reviewing the last pending commits in trunk. Michael is still looking at some SPI fixes to be included in 1.5.5, and I plan to cut the release as soon as those issues are sorted out. BR, Jukka Zitting
Re: Jackrabbit 1.5.5 release plan
Hi Jukka, could issue JCR-2016 (jcr2spi) be considered for inclusion? There is a patch attached that fixes some faults in the update processing. I.e. a correct update leads to an incorrect state. thanks, Frank On Tue, Apr 21, 2009 at 12:07 PM, Jukka Zitting jukka.zitt...@gmail.comwrote: Hi, On Wed, Apr 1, 2009 at 10:11 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: More generally, with the 1.5.4 release candidate tagged and out for review, I'm moving forward with the 1.5.5 release. I'm just reviewing the last pending commits in trunk. Michael is still looking at some SPI fixes to be included in 1.5.5, and I plan to cut the release as soon as those issues are sorted out. BR, Jukka Zitting
[jira] Updated: (JCR-2048) Workspace is shut down while creating initial index
[ https://issues.apache.org/jira/browse/JCR-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-2048: --- Fix Version/s: (was: 1.6.0) 1.5.5 Merged to the 1.5 branch in revision 767106. Workspace is shut down while creating initial index --- Key: JCR-2048 URL: https://issues.apache.org/jira/browse/JCR-2048 Project: Jackrabbit Content Repository Issue Type: Bug Components: jackrabbit-core Affects Versions: 1.4, 1.5.0 Reporter: Marcel Reutegger Priority: Minor Fix For: 1.5.5 Attachments: JCR-2048.patch This only happens when a maxIdleTime is configured for the workspaces in the repository.xml and the workspace to index is not the default workspace. The idle check considers a workspace as idle when there only a system session is open and the configured idle time elapsed. This is also the case when the workspace is initializing. The repository should either check if a workspace is still initializing or we need to move the search manager initialization into the WorkspaceInfo.doInitialize() method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1216) Unreferenced sessions should get garbage collected
[
https://issues.apache.org/jira/browse/JCR-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1216:
---
Issue Type: Bug (was: Improvement)
Merged to the 1.5 branch in revision 767119.
Unreferenced sessions should get garbage collected
--
Key: JCR-1216
URL: https://issues.apache.org/jira/browse/JCR-1216
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-core
Reporter: Thomas Mueller
Assignee: Thomas Mueller
Fix For: 1.5.5
Attachments: referencePatch.txt, softReferencePatch.txt,
userSessionPatch.txt, weakReferencePatch.txt
If an application opens many sessions and doesn't close them, they are never
garbage collected. After some time, the virtual machine will run out of
memory. This code will run out of memory after a few thousand logins:
Repository rep = new TransientRepository();
for (int i = 0; ; i++) {
rep.login(new SimpleCredentials(, new char[0]));
}
Using a finalizer to close SessionImpl doesn't work, because it seems there
are references from the (hard referenced part of the cache) to the
SessionImpl objects. Maybe it is possible to remove those references, or
change them to weak references.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Hudson build became unstable: Jac krabbit-1.5 » Jackrabbit Core #50
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5/org.apache.jackrabbit$jackrabbit-core/50/
Hudson build is still unstable: Ja ckrabbit-1.5 » Jackrabbit Core #51
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5/org.apache.jackrabbit$jackrabbit-core/51/
Re: Incubating Chemistry (Was: IP clearance for the Chemistry contribution)
Hi, On Tue, Apr 21, 2009 at 9:59 AM, Serge Huber shub...@jahia.com wrote: I am very interested in this project also, but I think it would be much too early for me to get commitership on this, as I need to first prove myself again, as an alumni of Jackrabbit :) Cool, you're welcome to join as a contributor. :-) In general I'd restrict the set of initial committers to people who've already been contributing to the initial codebases or the related discussions. BR, Jukka Zitting
JCR 2.0
Hi there. Now that JSR-283 is in public review, do we have a plan how to get the Jackrabbit trunk implement the JCR 2.0 API? Best regards, Julian
Re: JCR 2.0
Hi, On Tue, Apr 21, 2009 at 3:29 PM, Julian Reschke julian.resc...@gmx.de wrote: Now that JSR-283 is in public review, do we have a plan how to get the Jackrabbit trunk implement the JCR 2.0 API? Not yet a written plan, but I'd like to branch Jackrabbit 1.6 in a few weeks after which we can replace the current JCR 1.0 dependency in trunk with JCR 2.0 and start working towards Jackrabbit 2.0. Much of the JCR 2.0 implementation work has already been taking place since last summer using the org.apache.jackrabbit.api.jsr283 extensions in jackrabbit-api. BR, Jukka Zitting
Re: JCR 2.0
What about soft references, they would be easy to do without waiting for jackrabbit 2.0? 2009/4/21 Jukka Zitting jukka.zitt...@gmail.com Hi, On Tue, Apr 21, 2009 at 3:29 PM, Julian Reschke julian.resc...@gmx.de wrote: Now that JSR-283 is in public review, do we have a plan how to get the Jackrabbit trunk implement the JCR 2.0 API? Not yet a written plan, but I'd like to branch Jackrabbit 1.6 in a few weeks after which we can replace the current JCR 1.0 dependency in trunk with JCR 2.0 and start working towards Jackrabbit 2.0. Much of the JCR 2.0 implementation work has already been taking place since last summer using the org.apache.jackrabbit.api.jsr283 extensions in jackrabbit-api. BR, Jukka Zitting -- -Tor
Re: Incubating Chemistry (Was: IP clearance for the Chemistry contribution)
Hi, On Tue, Apr 21, 2009 at 12:12 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: I'll now ping the gene...@incubator.apache.org list for some early comments on the proposal. See http://thread.gmane.org/gmane.comp.apache.incubator.general/21727 for the Incubator thread. There are some concerns over the name Chemistry and I actually found an existing Java project called Chemistry Development Kit (http://apps.sourceforge.net/mediawiki/cdk/), so as painful as it is we may still need to reconsider the project name. BR, Jukka Zitting
Re: JCR 2.0
On Tue, Apr 21, 2009 at 3:57 PM, Torgeir Veimo torg...@pobox.com wrote: What about soft references, they would be easy to do without waiting for jackrabbit 2.0? the new property types have a great impact (core, persistence, api, tests, etc) and we wanted to wait until 1.6 is branched. regards, toby 2009/4/21 Jukka Zitting jukka.zitt...@gmail.com Hi, On Tue, Apr 21, 2009 at 3:29 PM, Julian Reschke julian.resc...@gmx.de wrote: Now that JSR-283 is in public review, do we have a plan how to get the Jackrabbit trunk implement the JCR 2.0 API? Not yet a written plan, but I'd like to branch Jackrabbit 1.6 in a few weeks after which we can replace the current JCR 1.0 dependency in trunk with JCR 2.0 and start working towards Jackrabbit 2.0. Much of the JCR 2.0 implementation work has already been taking place since last summer using the org.apache.jackrabbit.api.jsr283 extensions in jackrabbit-api. BR, Jukka Zitting -- -Tor
Re: Incubating Chemistry (Was: IP clearance for the Chemistry contribution)
I might be jumping the gun a little, but if this can help, here are a few name suggestions : Apache Plug Apache Content Plug Apache Jackplug Apache Sea Miss (ok it's an awful word game :)) (or could be written Seamis, or Seemis) Apache Startle (Jackrabbit synonym) But I must admit the name Chemistry is quite good, even if potentially misleading. Regards, Serge Huber. On 21 avr. 09, at 16:04, Jukka Zitting wrote: Hi, On Tue, Apr 21, 2009 at 12:12 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: I'll now ping the gene...@incubator.apache.org list for some early comments on the proposal. See http://thread.gmane.org/gmane.comp.apache.incubator.general/21727 for the Incubator thread. There are some concerns over the name Chemistry and I actually found an existing Java project called Chemistry Development Kit (http://apps.sourceforge.net/mediawiki/cdk/), so as painful as it is we may still need to reconsider the project name. BR, Jukka Zitting
Re: Incubating Chemistry (Was: IP clearance for the Chemistry contribution)
It is a play on the letters; CheMIStry. 2009/4/22 Serge Huber shub...@jahia.com I might be jumping the gun a little, but if this can help, here are a few name suggestions : Apache Plug Apache Content Plug Apache Jackplug Apache Sea Miss (ok it's an awful word game :)) (or could be written Seamis, or Seemis) Apache Startle (Jackrabbit synonym) But I must admit the name Chemistry is quite good, even if potentially misleading. Regards, Serge Huber. On 21 avr. 09, at 16:04, Jukka Zitting wrote: Hi, On Tue, Apr 21, 2009 at 12:12 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: I'll now ping the gene...@incubator.apache.org list for some early comments on the proposal. See http://thread.gmane.org/gmane.comp.apache.incubator.general/21727 for the Incubator thread. There are some concerns over the name Chemistry and I actually found an existing Java project called Chemistry Development Kit (http://apps.sourceforge.net/mediawiki/cdk/), so as painful as it is we may still need to reconsider the project name. BR, Jukka Zitting -- -Tor
Re: Incubating Chemistry (Was: IP clearance for the Chemistry contribution)
Thank you Torgeir, I remember this being mentioned a while ago, but I was mostly hoping to help if need be. But I would miss the current name, as I agree it is good :) Regards, Serge Huber. On 21 avr. 09, at 16:36, Torgeir Veimo wrote: It is a play on the letters; CheMIStry. 2009/4/22 Serge Huber shub...@jahia.com I might be jumping the gun a little, but if this can help, here are a few name suggestions : Apache Plug Apache Content Plug Apache Jackplug Apache Sea Miss (ok it's an awful word game :)) (or could be written Seamis, or Seemis) Apache Startle (Jackrabbit synonym) But I must admit the name Chemistry is quite good, even if potentially misleading. Regards, Serge Huber. On 21 avr. 09, at 16:04, Jukka Zitting wrote: Hi, On Tue, Apr 21, 2009 at 12:12 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: I'll now ping the gene...@incubator.apache.org list for some early comments on the proposal. See http://thread.gmane.org/gmane.comp.apache.incubator.general/21727 for the Incubator thread. There are some concerns over the name Chemistry and I actually found an existing Java project called Chemistry Development Kit (http://apps.sourceforge.net/mediawiki/cdk/), so as painful as it is we may still need to reconsider the project name. BR, Jukka Zitting -- -Tor
Re: Incubating Chemistry (Was: IP clearance for the Chemistry contribution)
Hi, On Tue, Apr 21, 2009 at 4:40 PM, Serge Huber shub...@jahia.com wrote: But I would miss the current name, as I agree it is good :) Me too. How about if we just slightly modified it, say to Apache Chemi or something similar? BR, Jukka Zitting
Re: Incubating Chemistry (Was: IP clearance for the Chemistry contribution)
or Chemis ? Regards, Serge Huber. On 21 avr. 09, at 16:43, Jukka Zitting wrote: Hi, On Tue, Apr 21, 2009 at 4:40 PM, Serge Huber shub...@jahia.com wrote: But I would miss the current name, as I agree it is good :) Me too. How about if we just slightly modified it, say to Apache Chemi or something similar? BR, Jukka Zitting
Re: Incubating Chemistry (Was: IP clearance for the Chemistry contribution)
Jukka Zitting wrote: Hi, On Tue, Apr 21, 2009 at 4:40 PM, Serge Huber shub...@jahia.com wrote: But I would miss the current name, as I agree it is good :) Me too. How about if we just slightly modified it, say to Apache Chemi or something similar? Chemist BR, Julian (helping to paint the bikeshed :-))
Re: Incubating Chemistry (Was: IP clearance for the Chemistry contribution)
On Tue, Apr 21, 2009 at 12:12 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: * We now only have volunteer mentors from Day. The normal diversity rules don't really apply to mentors, but it would still be good to have someone with a different perspective join us as a mentor. Note that you need to be an Apache member to be a mentor. Happy to oblige - I added myself to the list. -- Gianugo Rabellino M: +44 779 5364 932 / +39 389 44 26 846 Sourcesense - making sense of Open Source: http://www.sourcesense.com
Jackrabbit 1.6 release plan
Hi, As noted in various recent threads, we're getting closer to branching and releasing Jackrabbit 1.6. There are no major blockers to 1.6 so we should be able to move fairly quickly with the release. We had some earlier plans about including a content browser/editor or implementing database connection pooling in 1.6, but since neither effort has moved much forward I guess it's best to not wait for them. I'm hoping to have the JCR Commons components moved outside the main codebase before the Jackrabbit 1.6 release, so the more we can do towards that before branching 1.6 the better. Also, the fewer components we have in trunk, the easier the JCR 2.0 migration work will be after 1.6 has been branched. I'll try to focus some effort on that in the next few days. Unless anything major comes up, I will create a Jackrabbit 1.x branch at the end of next week on Friday, April 30th. This branch will be used for any remaining JCR 1.0 feature work for Jackrabbit 1.6 (and a potential Jackrabbit 1.7 release later on if there's demand for that). Meanwhile the trunk will be upgraded to JCR 2.0. Once all feature changes for Jackrabbit 1.6 are in (hopefully within a week or so after the 1.x branch was created), I will branch 1.6 and cut the first preview build of the release. At that point the 1.6 branch will go into a bug fix -only mode. If you have any major fixes or features you'd like to see in Jackrabbit 1.6, now would be a good time to bring them up. BR, Jukka Zitting
Jackrabbit 2.0 release plan
Hi, As a followup to the Jackrabbit 1.6 release plan I sent earlier, here's a quick roadmap towards Jackrabbit 2.0. Once the 1.x branch has been created on April 30th, we will upgrade the JCR dependency in trunk to the JCR 2.0 jar included in the JSR 283 proposed final draft. This will replace all the org.apache.jackrabbit.api.jsr283 extension interfaces we currently have in jackrabbit-api. At the same point we will also upgrade the required runtime platform to Java 5. This means that all Java 5 language and library features will then be available in Jackrabbit trunk. The 2.0 release also gives us a changes to drop deprecated features and introduce configuration and other backwards-incompatible changes that we normally wouldn't do in a minor release. However, any such change must come with a clear explanation in the 2.0 release notes. It can be expected that the trunk may be fairly unstable in May as a result of the JCR 2.0 upgrade and other changes. If you're using the Jackrabbit trunk for anything else than development or testing, it's probably a good idea to follow the 1.x branch instead until the JCR 2.0 work has stabilized. The JSR 283 RI and TCK will be branched off from the Jackrabbit trunk at some point after both codebases have reached reasonable feature-completeness. After that, once the JSR 283 is final, we will upgrade the JCR 2.0 API dependency from the proposed final draft to the final version and focus on stabilizing the trunk for the Jackrabbit 2.0 release. I'll keep you posted as more details of these milestones and expected schedules become available. BR, Jukka Zitting
Re: Incubating Chemistry (Was: IP clearance for the Chemistry contribution)
Hi, I downloaded a word list from http://wordlist.sourceforge.net and ran: grep -i -R --include=* -E 'c.?m.?i.?s' . grep -i -R --include=* 'c.*m.*i[^s]*s' . This got me a long list, including: chromis cinematics combfish comics commissar crimison blackmails buckminster occamist (from Occam's razor) Maybe somebody else want to do something similar. Buckminster is already in use, maybe others too. Regards, Thomas On Tue, Apr 21, 2009 at 4:53 PM, Gianugo Rabellino g.rabell...@sourcesense.com wrote: On Tue, Apr 21, 2009 at 12:12 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: * We now only have volunteer mentors from Day. The normal diversity rules don't really apply to mentors, but it would still be good to have someone with a different perspective join us as a mentor. Note that you need to be an Apache member to be a mentor. Happy to oblige - I added myself to the list. -- Gianugo Rabellino M: +44 779 5364 932 / +39 389 44 26 846 Sourcesense - making sense of Open Source: http://www.sourcesense.com
Re: Jackrabbit 1.5.5 release plan
Hi, On Tue, Apr 21, 2009 at 12:31 PM, Frank van Lankvelt f.vanlankv...@onehippo.com wrote: could issue JCR-2016 (jcr2spi) be considered for inclusion? There is a patch attached that fixes some faults in the update processing. I.e. a correct update leads to an incorrect state. Sure, sorry that nobody has commented on the patch yet. (Perhaps we should start using the patch available workflow in Jira...) The patch looks reasonably OK, though I'd need to review it in a bit more detail before applying it. Any chance of getting a test case for it? :-) BR, Jukka Zitting
Re: Incubating Chemistry (Was: IP clearance for the Chemistry contribution)
Hi, On Tue, Apr 21, 2009 at 4:53 PM, Gianugo Rabellino g.rabell...@sourcesense.com wrote: On Tue, Apr 21, 2009 at 12:12 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: * We now only have volunteer mentors from Day. The normal diversity rules don't really apply to mentors, but it would still be good to have someone with a different perspective join us as a mentor. Note that you need to be an Apache member to be a mentor. Happy to oblige - I added myself to the list. Excellent, thanks! BR, Jukka Zitting
Re: Jackrabbit 2.0 release plan
Jukka Zitting wrote: Hi, As a followup to the Jackrabbit 1.6 release plan I sent earlier, here's a quick roadmap towards Jackrabbit 2.0. ... +1 on the specific plan, and also thanks a lot for doing the planning work! BR, Julian
Re: Naming Chemistry
+1 Chemistry - Original Message - From: Florent Guillaume f...@nuxeo.com To: dev@jackrabbit.apache.org Sent: Tuesday, April 21, 2009 10:00:33 AM GMT -07:00 U.S. Mountain Time (Arizona) Subject: Re: Naming Chemistry Hi, I'm hope you'll forgive me, but I won't contribute to this discussion beyond this email as I'm quite tired of playing naming games. We've already been through 3 names, so I'll concentrate on writing actual code until this is resolved. I'm ok with Chemist as well, although I expect it'll raise the same arguments as Chemistry. The objections to Chemistry as potential confusing regarding the science of chemistry seem off-base to me. If there ever was a chemistry-based project in Apache, I expect they'd choose their own codename instead of the just all-encompassing chemistry moniker. Regarding the existing chemistry-named java project, it's called CDK or Chemistry Development Kit, never just chemistry. Finally I gather that nobody complained that Lucene had nothing to do with the city, that Shale had nothing to do with the rocks, or that Jackrabbit had nothing to do with the furry animal. So why complain about chemistry... Regarding other suggestions: we've also been through the grep /usr/ share/dict/words here at Nuxeo, and considered and rejected many names. The problem is not finding potential ones, the problem is at some point saying ok this one is good enough. I contend that Chemistry is good enough. Bye, Florent -- Florent Guillaume, Head of RD, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
Re: Jackrabbit 1.5.5 release plan
thanks for reviewing! Sorry about the absense of a test, I'll have to look into how to do that. I guess it should be possible by creating a mock repository service to fabricate the updates(?) Frank On Tue, Apr 21, 2009 at 6:00 PM, Jukka Zitting jukka.zitt...@gmail.comwrote: Hi, On Tue, Apr 21, 2009 at 12:31 PM, Frank van Lankvelt f.vanlankv...@onehippo.com wrote: could issue JCR-2016 (jcr2spi) be considered for inclusion? There is a patch attached that fixes some faults in the update processing. I.e. a correct update leads to an incorrect state. Sure, sorry that nobody has commented on the patch yet. (Perhaps we should start using the patch available workflow in Jira...) The patch looks reasonably OK, though I'd need to review it in a bit more detail before applying it. Any chance of getting a test case for it? :-) BR, Jukka Zitting
Re: Naming Chemistry
Hi all, Having followed this a bit, I am feeling a bit uncomfortable with all the proposals. I have to say, that I like Chemistry quite a bit (and it immediately sounds and looks like CMIS). Now for potential mixup with CDK: I agree with Florent that there is probably not a big chance for problems. Interesting side note: they have a thing called JChemPaint, which they abbreviate to JCP ... ;-) Therefore, I concurr with Florent to keep the original name proposal Chemistry. Regards Felix Florent Guillaume schrieb: Hi, I'm hope you'll forgive me, but I won't contribute to this discussion beyond this email as I'm quite tired of playing naming games. We've already been through 3 names, so I'll concentrate on writing actual code until this is resolved. I'm ok with Chemist as well, although I expect it'll raise the same arguments as Chemistry. The objections to Chemistry as potential confusing regarding the science of chemistry seem off-base to me. If there ever was a chemistry-based project in Apache, I expect they'd choose their own codename instead of the just all-encompassing chemistry moniker. Regarding the existing chemistry-named java project, it's called CDK or Chemistry Development Kit, never just chemistry. Finally I gather that nobody complained that Lucene had nothing to do with the city, that Shale had nothing to do with the rocks, or that Jackrabbit had nothing to do with the furry animal. So why complain about chemistry... Regarding other suggestions: we've also been through the grep /usr/share/dict/words here at Nuxeo, and considered and rejected many names. The problem is not finding potential ones, the problem is at some point saying ok this one is good enough. I contend that Chemistry is good enough. Bye, Florent
Re: Naming Chemistry
On Tue, Apr 21, 2009 at 7:00 PM, Florent Guillaume f...@nuxeo.com wrote: ...I contend that Chemistry is good enough. +1 Chemistry Development Kit (CDK) is sufficiently different from Apache Chemistry. And about Chemistry in general...there's that thing called Windows somewhere, but it's not really about the openings in your house. Seems to work for them. -Bertrand (from the peanuts gallery)
