Just a curiosity question and not really worth a JIRA comment: Why only
put the profile in core and not in the parent pom? Seems like if you
want to build and test against 1.4, the parent pom would be the better
place.
--David
Gregory Joseph (JIRA) wrote:
[
http://jira.magnolia.info/browse/MAGNOLIA-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory Joseph resolved MAGNOLIA-2006.
--------------------------------------
Resolution: Fixed
Added a profile in magnolia-core for the 3.5 branch which allows building core
against JR1.4
For 3.6, we won't support JR1.3 unless really needed (in which case we'll
either add a profile too)
We could split the JR provider out of core, but that requires a bit more work,
as the RepositoryTestCase in core currently rely on the ProviderImpl (and
simply taking it out creates a cyclic dependency)
Jackrabbit 1.4 support
----------------------
Key: MAGNOLIA-2006
URL: http://jira.magnolia.info/browse/MAGNOLIA-2006
Project: Magnolia
Issue Type: Task
Components: core
Affects Versions: 3.5.3
Reporter: Fabrizio Giustina
Assignee: Philipp Bracher
Fix For: 3.6
Jackrabbit 1.4 is out: unfortunately the Provider implementation used for
jackrabbit 1.3 is not binary compatible with jackrabbit 1.4, although it is
source compatible (it just needs to be compiled with the appropriate jackrabbit
version).
In order to support jackrabbit we should create a different provider
implementation (two modules compiled with two different jackrabbit versions,
not really nice) or doing some dirty hack using reflection (should be just a
single method call actually).
PS: I've been testing snapshots builds from jackrabbit 1.4 for a few months in a clustered environment and it looks very good (faster, never had memory issues)
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
