Ticket #350 (closed Task: fixed)

Opened 8 years ago

Last modified 8 years ago

Update 3rd-party components

Reported by: jri Owned by: jri
Priority: Major Milestone: Release 4.1
Component: DeepaMehta Standard Distribution Version: 4.0.12
Keywords: Cc: dgf, Malte
Complexity: 3 Area: Runtime Environment
Module:

Description

E.g. Felix, Jersey, Neo4j, ...

It's already realized by dgf (except for Neo4j).
Merging his branch should be sufficient.

Change History

comment:1 Changed 8 years ago by Jörg Richter

Revise POMs: update 3rd-party components (#350).

Updated 3rd-party components:

  • Jersey 1.8 -> 1.14
  • Jettison 1.3 -> 1.3.2
  • JUnit 4.8.2 -> 4.10
  • Easymock 3.0 -> 3.1

Updated Maven plugins:

  • Compiler plugin 2.3.2 -> 2.5.1
  • Bundle plugin 2.3.5 -> 2.3.7
  • Assembly plugin 2.2 -> 2.3

See ticket 350.

Furthermore:

  • The Plugin Parent project is revitalized. It provides the basis for 3rd-party DM plugin development.
  • Changed POM hierarchy: the development and runtime environment (Global POM and Provision POM) as well as the 3rd-party DM plugins no longer depend on the Parent POM. (the Parent POM is only used by the plugins of the DM Standard Distribution)

This commit is a merge from dgf's branch.
Thanks to dgf!

comment:2 Changed 8 years ago by Jörg Richter

Revise POMs: update 3rd-party components (#350).

Updated 3rd-party components:

  • Jersey 1.8 -> 1.14
  • Jettison 1.3 -> 1.3.2
  • JUnit 4.8.2 -> 4.10
  • Easymock 3.0 -> 3.1

Updated Maven plugins:

  • Compiler plugin 2.3.2 -> 2.5.1
  • Bundle plugin 2.3.5 -> 2.3.7
  • Assembly plugin 2.2 -> 2.3

See ticket 350.

Furthermore:

  • The Plugin Parent project is revitalized. It provides the basis for 3rd-party DM plugin development.
  • Changed POM hierarchy: the development and runtime environment (Global POM and Provision POM) as well as the 3rd-party DM plugins no longer depend on the Parent POM. (the Parent POM is only used by the plugins of the DM Standard Distribution)

This commit is a merge from dgf's branch.
Thanks to dgf!

comment:3 Changed 8 years ago by Jörg Richter

Adapt to Neo4j 1.8 (#350).

Depends on Neo4j MehtaGraph? 2.0-SNAPSHOT.
(Must be build manually. The DM public Maven repo is currently down.)

It works but is experimental.

IMPORTANT:
1) geronimo-jta-1.1-spec must appear *before* neo4j-kernel-1.8 in the bundle list.

This fixes ClassNotFoundException?: javax.transaction.TransactionManager?

2) the Neo4j jars are auto-wrapped by Pax Runner.
3) an existing database must be deleted.

Perhaps a better approach would be to embed Neo4j and JTA spec into the Neo4j MehtaGraph? bundle.
This would avoid auto-wrapping and would make building the distribution less cumbersome.

See ticket 350.

comment:4 Changed 8 years ago by Jörg Richter

Building distribution with Neo4j 1.8 works (#350).

Adapt to new Neo4j Mehtagraph packaging.
These artifacts must no longer provisioned/distributed as they are embedded in the Neo4j Mehtagraph bundle:

  • neo4j-kernel 1.8
  • neo4j-lucene-index 1.8
  • lucene-core 3.5.0
  • geronimo-jta_1.1_spec 1.1.1

No specific bundle order (and no specific start levels) required anymore.
No auto-wrapping (through Pax Runner) required anymore.

Note: the current Neo4j Mehtagraph version is 1.8-SNAPSHOT (not 2.0-SNAPSHOT).
(From now on the major and minor number are supposed to be equal to the embedded Neo4j version.)

See ticket 350.

comment:5 Changed 8 years ago by jri

Regarded as complete for the moment.
Updating Felix is postponed.

Neo4j works in the "neo4j-1.8" branch.
It will not be merged into master before a 1.2->1.8 migration tool is available (required for EduZEN installation).
On the other hand all master changes are merged into neo4j-1.8. So if you have no legacy data you should work with the neo4j-1.8 branch.

comment:6 Changed 8 years ago by jri

  • Status changed from new to closed
  • Resolution set to fixed

comment:7 Changed 8 years ago by Jörg Richter

Adapt to Neo4j 1.8 (#350).

Depends on Neo4j MehtaGraph? 2.0-SNAPSHOT.
(Must be build manually. The DM public Maven repo is currently down.)

It works but is experimental.

IMPORTANT:
1) geronimo-jta-1.1-spec must appear *before* neo4j-kernel-1.8 in the bundle list.

This fixes ClassNotFoundException?: javax.transaction.TransactionManager?

2) the Neo4j jars are auto-wrapped by Pax Runner.
3) an existing database must be deleted.

Perhaps a better approach would be to embed Neo4j and JTA spec into the Neo4j MehtaGraph? bundle.
This would avoid auto-wrapping and would make building the distribution less cumbersome.

See ticket 350.

comment:8 Changed 8 years ago by Jörg Richter

Building distribution with Neo4j 1.8 works (#350).

Adapt to new Neo4j Mehtagraph packaging.
These artifacts must no longer provisioned/distributed as they are embedded in the Neo4j Mehtagraph bundle:

  • neo4j-kernel 1.8
  • neo4j-lucene-index 1.8
  • lucene-core 3.5.0
  • geronimo-jta_1.1_spec 1.1.1

No specific bundle order (and no specific start levels) required anymore.
No auto-wrapping (through Pax Runner) required anymore.

Note: the current Neo4j Mehtagraph version is 1.8-SNAPSHOT (not 2.0-SNAPSHOT).
(From now on the major and minor number are supposed to be equal to the embedded Neo4j version.)

See ticket 350.

Note: See TracTickets for help on using tickets.