[
https://issues.apache.org/jira/browse/OFBIZ-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17371694#comment-17371694
]
Ioan Eugen Stan commented on OFBIZ-3500:
----------------------------------------
I think this would be much simpler to see components if ofbiz used a
build.gradle file (subproject) per component.
Right now activateComponent scans the classpath and creates gradle projects
dynamically.
Why not use actual build.gradle configurations for the framework and
applications ?
Projects can use common dependencies:
[https://stackoverflow.com/questions/9547170/in-gradle-how-do-i-declare-common-dependencies-in-a-single-place]
:
{code:java}
libraries = [
spring: [ // Groovy list literal
"org.springframework:spring-core:3.1",
"org.springframework:spring-jdbc:3.1"
]
]
dependencies { compile libraries.spring }
{code}
By using real projects we could also publish a jar per component and those
could be used as libraries.
I would love to use OFBiz framework as a library (the entity layer is very
useful).
> Umbrella issue for components dependency
> ----------------------------------------
>
> Key: OFBIZ-3500
> URL: https://issues.apache.org/jira/browse/OFBIZ-3500
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
> Affects Versions: Trunk
> Reporter: Jacques Le Roux
> Priority: Major
> Attachments: dependencyCheck.groovy
>
>
> This issue is dedicated to group components dependency related issues.
> Chris Snow created [this related Wiki
> page|http://cwiki.apache.org/confluence/x/eIOJ]
> There is now a
> https://cwiki.apache.org/confluence/display/OFBIZ/Component+and+Component+Set+Dependencies
> wiki page which is more up to data (still small things to clean)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
