DataNucleus

[ http://issues.datanucleus.org/browse/NUCACCESS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Jefferson updated NUCACCESS-63:
------------------------------------

    Fix Version/s: 3.0.0.m1

> Convert "local.repository" into Maven2 layout
> ---------------------------------------------
>
>                 Key: NUCACCESS-63
>                 URL: http://issues.datanucleus.org/browse/NUCACCESS-63
>             Project: DataNucleus Access Platform
>          Issue Type: Task
>          Components: Dependency
>            Reporter: Andy Jefferson
>             Fix For: 3.0.0.m1
>
>
> Awaiting a volunteer. Would need change to layout, and addition of POM files

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.datanucleus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://issues.datanucleus.org/browse/NUCACCESS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Jefferson updated NUCACCESS-63:
------------------------------------

    Fix Version/s:     (was: 3.0.0.m1)

> Convert "local.repository" into Maven2 layout
> ---------------------------------------------
>
>                 Key: NUCACCESS-63
>                 URL: http://issues.datanucleus.org/browse/NUCACCESS-63
>             Project: DataNucleus Access Platform
>          Issue Type: Task
>          Components: Dependency
>            Reporter: Andy Jefferson
>
> Awaiting a volunteer. Would need change to layout, and addition of POM files

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.datanucleus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://issues.datanucleus.org/browse/NUCACCESS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Jefferson updated NUCACCESS-63:
------------------------------------

          Summary: Change "local.repository" to just contain dependencies not in Maven standard repository  (was: Convert "local.repository" into Maven2 layout)
         Assignee: Andy Jefferson
    Fix Version/s: 3.0.0.release
      Description: 
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.

  was:Awaiting a volunteer. Would need change to layout, and addition of POM files


> Change "local.repository" to just contain dependencies not in Maven standard repository
> ---------------------------------------------------------------------------------------
>
>                 Key: NUCACCESS-63
>                 URL: http://issues.datanucleus.org/browse/NUCACCESS-63
>             Project: DataNucleus Access Platform
>          Issue Type: Task
>          Components: Dependency
>            Reporter: Andy Jefferson
>            Assignee: Andy Jefferson
>             Fix For: 3.0.0.release
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.datanucleus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://issues.datanucleus.org/browse/NUCACCESS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18983#action_18983 ] 

Andy Jefferson commented on NUCACCESS-63:
-----------------------------------------

Other issue is if we drop "local.repository" then we break Eclipse building, unless we move to using Eclipse M2 plugin.

> Change "local.repository" to just contain dependencies not in Maven standard repository
> ---------------------------------------------------------------------------------------
>
>                 Key: NUCACCESS-63
>                 URL: http://issues.datanucleus.org/browse/NUCACCESS-63
>             Project: DataNucleus Access Platform
>          Issue Type: Task
>          Components: Dependency
>            Reporter: Andy Jefferson
>            Assignee: Andy Jefferson
>             Fix For: 3.0.0.release
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.datanucleus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://issues.datanucleus.org/browse/NUCACCESS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18994#action_18994 ] 

Andy Jefferson commented on NUCACCESS-63:
-----------------------------------------

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.

> Change "local.repository" to just contain dependencies not in Maven standard repository
> ---------------------------------------------------------------------------------------
>
>                 Key: NUCACCESS-63
>                 URL: http://issues.datanucleus.org/browse/NUCACCESS-63
>             Project: DataNucleus Access Platform
>          Issue Type: Task
>          Components: Dependency
>            Reporter: Andy Jefferson
>            Assignee: Andy Jefferson
>             Fix For: 3.0.0.release
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.datanucleus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://issues.datanucleus.org/browse/NUCACCESS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Jefferson updated NUCACCESS-63:
------------------------------------

    Fix Version/s:     (was: 3.0.0.release)

> Change "local.repository" to just contain dependencies not in Maven standard repository
> ---------------------------------------------------------------------------------------
>
>                 Key: NUCACCESS-63
>                 URL: http://issues.datanucleus.org/browse/NUCACCESS-63
>             Project: DataNucleus Access Platform
>          Issue Type: Task
>          Components: Dependency
>            Reporter: Andy Jefferson
>            Assignee: Andy Jefferson
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.datanucleus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://issues.datanucleus.org/browse/NUCACCESS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Jefferson reassigned NUCACCESS-63:
---------------------------------------

    Assignee:     (was: Andy Jefferson)

> Change "local.repository" to just contain dependencies not in Maven standard repository
> ---------------------------------------------------------------------------------------
>
>                 Key: NUCACCESS-63
>                 URL: http://issues.datanucleus.org/browse/NUCACCESS-63
>             Project: DataNucleus Access Platform
>          Issue Type: Task
>          Components: Dependency
>            Reporter: Andy Jefferson
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.datanucleus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira