[Springframework-rcp-dev] [Spring-JIRA] Commented: (RCP-624) migrate pom dependencies to come from the SpringSource Enterprise Bundle Repository

[Ryan O. (JIRA) <no...@sp...>]

    [ https://jira.springsource.org/browse/RCP-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50597#action_50597 ] 

Ryan Ovrevik commented on RCP-624:
----------------------------------

Geoffrey,
What do you mean by " The disadvantage is that is screws up maven entirely"? Are you referring to the fact that users of the dependencies from the spring repository will have to update their poms to resolves dependencies like commons collections from the spring repo or they run the risk of pulling the dependency (same dependency but... different name)from two places at the same time?

"Let the the spring OSGi maven-repistory hack become obsolete." is this the plan for the spring repo? Was it (the spring repo) intended only to be a short term hack? If that is the case, it does change things. I did not get the impression based on the fact other spring projects use the spring repos internally. Please correct any misunderstandings I have.

For what it is worth... On our projects, we use the spring repositories because they are consistent, cleanly isolated and carefully managed... we don't currently use any of the osgi business. It is great to have a dependency like log4j not not pulling in servlet, mail and jmx because the repo is messed up (just an example).


> migrate pom dependencies to come from  the SpringSource Enterprise Bundle Repository
> ------------------------------------------------------------------------------------
>
>                 Key: RCP-624
>                 URL: https://jira.springsource.org/browse/RCP-624
>             Project: Spring Rich Client Project
>          Issue Type: Refactoring
>          Components: Build System
>    Affects Versions: 1.1.1
>            Reporter: Ryan Ovrevik
>            Assignee: Lieven Doclo
>            Priority: Minor
>         Attachments: conflictive classes.zip, spring-richclient-poms.patch
>
>
> Update all poms to retrieve dependencies from the SpringSource Enterprise Bundle Repository. This seems like a reasonable precondition for updating the project(s) to utilize spring3.

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