[
https://issues.apache.org/jira/browse/OFBIZ-9832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196849#comment-16196849 ]
Jacques Le Roux commented on OFBIZ-9832:
----------------------------------------
Great news Taher,
I think that when the Gradle part will be done we should have an entry in Buildbot to automatically update a plugin on Maven when changed, or simpler always update all, less efficient but easier.
Looking forward :)
*Note: *better to use INFRA-13924 than \[INFRA-13924|
https://issues.apache.org/jira/browse/INFRA-13924\] because then Jira handles the link and shows it striken out if closed (which by and large reduces time to check if really closed). I just did it for you :)
> Provide ability for OFBiz to publish plugins to Nexus maven repository
> ----------------------------------------------------------------------
>
> Key: OFBIZ-9832
> URL:
https://issues.apache.org/jira/browse/OFBIZ-9832> Project: OFBiz
> Issue Type: Improvement
> Affects Versions: Upcoming Release
> Reporter: Taher Alkhateeb
> Priority: Minor
>
> This JIRA has reference to the [discussion|
http://markmail.org/message/bjvqu23ofwzuk57y] in the community regarding separating plugins into a separate project.
> I have requested from Infra the creation of a maven repository for OFBiz in INFRA-13924 which they accomplished very quickly.
> Now we need to upgrade the plugin manager in build.gradle to provide the ability to publish all plugins to this remote maven repository.
> I am not sure, but this might be a good chance to remove all plugin management logic from build.gradle and perhaps move it into a gradle-plugin or another gradle file to reduce the size of build.gradle
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Locked
