Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of markus.joschko@gmail.com
 designates 209.85.161.42 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=OrqQZh268aXvXMMH+1g+DdnSu0OI+gDtKwZjGRgw6BoPlzPcnw8J/RKaVw5ARHhWnC
         nXPBHJzKzxtdk+kBnL1751v0jHJEtVHbc4cBhgsvRUrSsEoa5WDWF+iEF2ToZNN+nh3y
         dqG3Pv1VjqGcrprI5NRvPpO6SweQSaaFohgvI=
MIME-Version: 1.0
Date: Wed, 13 Apr 2011 08:53:27 +0200
Message-ID: <BANLkTik=3CfVraz_3n4eDUs1F6Yed0OxUA@mail.gmail.com>
Subject: Temporarily switching jackrabbit version
From: Markus Joschko <markus.joschko@gmail.com>
To: users@jackrabbit.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I have asked that question before on the sling mailing list but I
guess it is more appropraite here:
The current stable sling release uses jackrabbit 2.1.1 which has a bug
as it does not respect sv:multiple
on properties during import operation.

This bug is fixed in the latest jackrabbit release (which is available
in sling trunk). However I would like to stick to the stable release
of sling.

So I tried some kind of workaround and connected with the latest
jackrabbit cli to the existing repository (2.1.1) and imported
successfully.
Afterwards I continued with sling and jackrabbit 2.1.1 and so far
haven't had any problems.

Before doing so in production I would like to ask whether this
temporary switching of jackrabbit versions on the repository can have
consequences
I can not easily recognize.

Thanks,
 Markus