Jcr News & Articles

Nuxeo (news, site) has announced that its content repository technology, has been approved and will soon be provisioned by the Eclipse Foundation (news, site). The project even has a new, much tastier nickname than the official Eclipse Enterprise Content Repository Project -- Apricot -- and it's just in time for summer.

Web content integrator Jahia (news, site) launches a beta site to demonstrate the value and interactiveness of HTML 5.

Supporters of Content Management Interoperability Services (CMIS) may be pulling out the party hats. The Apache Software Foundation has announced that Apache Chemistry, an open source implementation of the CMIS standard has graduated from incubator status to a top-level project. This news follows Nuxeo’s announcement earlier in the month that it was contributing its CMIS supported content repository to Eclipse (news, site).

Nuxeo is putting its code where its mouth is. The open source document management vendor is contributing its content repository technology, Nuxeo Core to the Eclipse Foundation (news, site). The contribution is intended to spur the development of a CMIS-based content repository. Will this move yield a CMIS reference implementation whose popularity catches Apache’s JCR-based Jackrabbit?

There has been some debate recently about the “demise” of the JCR specification. One of the factors blamed for JCR’s demise is the relatively new CMIS standard. This begs the question: what is to prevent CMIS from the same fate as JCR?

Articles with titles like “Goodbye JCR, Hello CMIS” have been growing in numbers. The voices suggesting that the Java Content Repository standard is no longer relevant in a market dominated by non-Java content management systems are growing. Is JCR really dead?

Currently in beta, version 6.5 of Jahia Web CMS (news, site) brings considerable architectural changes to the table with focus on modularity, transition from page-centric to component-centric -- all in a composite content platform.

The Apache Software Foundation (ASF) today announced its resignation from the JCP (Java Community Process) Executive Committee (EC). This comes in only a day after Java SE 7/SE 8 specs (JSR-336 and JSR-337 respectively) were officially approved by the JCP despite the ASF and Google voting against.

Not sure which company's logo to use... Goodbye, Day Software, as we knew you. Hello, Adobe WCM/CEM, or Adobe super-duper content authoring, or whatever it is Adobe will rebrand Day to.

The deal is a done deal though, as announced earlier, with more than 98% of shares in Adobe’s pockets. The acquisition is final.

In one Ignite Chicago panel, Day’s own scientists and experts gathered to address any possible question about Day, JCR, CQ5, CRX and open development coming from the audience starving for answers. Here’s the scoop.

As previously reported, Adobe (news, site) announced its intention to acquire Web CMS and Social Collaboration maker Day (news, site). The deal is now nearly final with more than 94% of the outstanding shares of Day Software Holding AG in Adobe's pocket.

Any acquisition (and there have been quite a few of them lately) in the content management industry usually makes a splash. Today, it was Day's day to stir up the media, analysts, bloggers, twitterati and industry watchers; provoking pontifications around the announced US$ 240 mil. acquisition by Adobe.

Here’s the first look at what the industry was buzzing about and what some of the possible implications of the deal might be -- for Day, for Adobe, for the market.

Following Adobe's enormous acquisition of Omniture, in a deal roughly one-eighth the size, the company has snatched-up Switzerland-based Day Software, a well known (to us) maker of Java-based content repositories and enterprise-focused Web Content Management software, via an all-cash bid of about US$ 240 million.

It didn’t take Day Software (news, site) long to follow up on the release of CRX 2.1 with their next JCR Cup announcement.

The competition is on, but under a different name -- Agility Cup -- and open to a wider audience than in the past.

OASIS requires a minimum of 15% votes to ratify a spec as an official standard -- that amount of votes for CMIS v 1.0 has been reached yesterday. Unless something earth-shattering happens, or people wake up in the next few days leading up to April 30 and decide to vote against, we can safely declare CMIS as the newest OASIS standard.

We chatted with some of the Web CMS and Enterprise CMS vendors and contributors to the standard to get their commentary on the latest development.