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

[Lieven D. (JIRA) <no...@sp...>]

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

Lieven Doclo commented on RCP-624:
----------------------------------

Geoffrey, while I agree with the fact that moving to Spring's repo would be a bad idea at the moment (I know some people who really wouldn't appreciate the fact that they need to rewrite their POMs just because we're using the Spring OSGi-fied repo), your solution to both problems may (I repeat, may) cause problems. It could be possible that some RCP code is depending on jars that are pulled in transitively. When Spring would just copy our POM's and change the dependencies, it is possible due to their dependency rewiring, some dependencies will be missing. While this is our fault, it is something to take into account.

That said, I am totally in agreement to use logback. Unfortunately, we still don't have a unified logging mechanism when it comes to open source projects. We'd be obliged to include just about every slf4j adapter (java.util Logger, Log4J, commons-logging, ...) to get every working consistently.

> 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