DataNucleus JIRA is now in read-only mode. Raise any new issues in GitHub against the plugin that it applies to. DataNucleus JIRA will remain for the foreseeable future but will eventually be discontinued
Issue Details (XML | Word | Printable)

Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Andy Jefferson
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
DataNucleus AccessPlatform

Change "local.repository" to just contain dependencies not in Maven standard repository

Created: 04/Feb/10 12:28 PM   Updated: 01/Jan/14 12:19 PM   Resolved: 13/Dec/13 03:48 PM
Component/s: Dependency
Affects Version/s: None
Fix Version/s: 3.3.6

 Description  « Hide
We need to eventually migrate to Maven3 which doesn't support "legacy" (Maven1) repositories, so "local.repository" as we currently have it is needs changing or removing.

My current idea :
1. Put all non-standard jars in DN Maven2 repo (some are already there).
2. Remove all use of "local.repository" in pom.xml of the different projects.
3. Remove "local.repository" completely.

This means that, for offline use, currently we allow people to just download the plugins they need and "local.repository", but in the future we will need them to run Maven 2/3 to pull in the dependencies before going offline. I don't consider this an important overhead, and is what all other projects I've seen/built do.

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 19/May/11 03:54 PM
Other issue is if we drop "local.repository" then we break Eclipse building, unless we move to using Eclipse M2 plugin.

Andy Jefferson added a comment - 25/May/11 03:08 PM
All non-standard jars are in DN M2 repo now.

Maven : All "platform" pom.xml files no longer reference "local.repository", so if building using Maven you don't need it.

Eclipse : we can use M2Eclipse plugin ok, but we still need a way of Eclipse finding the imports/exports from MANIFEST.MF, unless using something like maven-bundle-plugin. The problem then is that this plugin doesn't give correct version ranges for the generated MANIFEST.MF.

Andy Jefferson added a comment - 10/Dec/13 10:22 AM
One possible solution to this is to simply change all plugin projects to be in standard Maven layout and move plugin.xml/MANIFEST under src/main/resources. This likely will result in Eclipse not thinking its a plugin project (need to check).

Andy Jefferson added a comment - 13/Dec/13 03:48 PM
GitHub as of 13/Dec/2013 removes all Eclipse plugin/manifest builders so there is no need for "local.repository".

Note : all updates for MANIFEST.MF (to be auto-generated via "bundle") should go against NUCACCESS-93