Announcement Announcement Module
Collapse
No announcement yet.
Maven managed dependency .Vs Bundle Classpath Container Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Maven managed dependency .Vs Bundle Classpath Container

    When a project depends on some other third party packages, we can use Maven, and we can also use Bundle Container.

    Using "Bundle Classpath Container" can make sure the dependent packages are the same as those at running time. But it does not have a benefit from Maven that is Maven will download those packages (no matter they are directly dependent or indirectly dependent), we have to download and copy them manually. And Maven managed dependency can't coexist with "Bundle Classpath Container".

    I found samples (e.g GreenPages) from springsource are using Maven. Which is the best practice?

  • #2
    I wouldn't say there is a clear best practice. Each approach has its advantages and drawbacks. You get to choose. ;-)

    Comment

    Working...
    X