Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Great, I'll continue discussion over there referring to this conversation. On Thu, Jul 28, 2016 at 10:03 AM, Sharan Foga wrote: > Hi > > If we are talking about Jira and ways to handle or improve it for the > project then I did start a discussion thread a few days ago (link below) > > > https://

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Hi If we are talking about Jira and ways to handle or improve it for the project then I did start a discussion thread a few days ago (link below) https://lists.apache.org/thread.html/61d310a85759c89ca2aa2a18bdca945a9868caf5a1bff2fb72a774d8@%3Cdev.ofbiz.apache.org%3E It might be good to take t

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Hi Pierre and Everyone, I gather you might be currently preoccupied to work on this JIRA. If my understanding is correct, then may I suggest to close this JIRA and other similar JIRAs and allow those interested in implementing the work to create their own JIRAs for the following reasons: 1- It is

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

An issue regarding the move of data up the stack already exists: https://issues.apache.org/jira/browse/OFBIZ-7016 Best regards, Pierre Smits ORRTIZ.COM OFBiz based solutions & services OFBiz Extensions Marketplace http://oem.ofbizci.net/oci-2/ On Wed, Jul 27, 2016 at 5:

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Would you be willing to take care of that task Pierre? On Jul 27, 2016 6:36 PM, "Pierre Smits" wrote: > An issue regarding the move of data up the stack already exists: > https://issues.apache.org/jira/browse/OFBIZ-7016 > > Best regards, > > Pierre Smits > > ORRTIZ.COM >

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

On Wed, Jul 27, 2016 at 3:47 PM, Pierre Smits wrote: > ... > But when code is already available in the OFBiz repo - and made available > through releases - such an enabler/disabler is as much overkill to an > adopter as a convenience script to download JDBC libraries (to paraphrase another contr

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Initially ecommerce was part of the "core" applications, then it was moved to specialpurpose because as it it is a "template" for the implementation of an ecommerce store rather than a ready to be used application. I must admit that the same could apply to the other backend applications so there is

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Hi Jacopo, You got it 100% right, it was indeed the ecommerce component. Wow! This means one of two things should happen, either we move ecommerce as a core application, or we untangle this mess. I'm not very familiar with the history, is there a reason why ecommerce is a specialpurpose applicatio

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

The perception is growing that 2 different solutions are mixed into one... One solution is about jump starting development, the other is about on-boarding existing components into an OFBiz deployment. If this plugin API/solution was intended for components existing outside of the OFBiz repo (eith

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

I think that the core reason for the failure is that most of the tests need the demo data that is loaded with the ecommerce component; if you disable it the data is not loaded. Could you please try to enable ecommerce and run them again? Thanks, Jacopo On Wed, Jul 27, 2016 at 1:21 PM, Taher Alkh

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Hi everyone, In continuation with the above discussion, I just made a little experiment which gave me scary results. What did I do? 1 - Disabled all specialpurpose components (except example, to make it a valid XML file) in specialpurpose/component-load.xml 2 - Attempted ./gradlew cleanAll loadDe

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Hi Taher, Gil, Exactly my thoughts. Nothing (ethically and technically) should force an user to share his/her/its personal plugins. This assumption must be part of the specifications (assumption as in a theory) Thanks Taher! Le 23/07/2016 à 19:44, Taher Alkhateeb a écrit : Hi Gil, Thank yo

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Hi Gil, Thank you for sharing past experiences. It seems we are tackling something that was attempted multiple times before. I am a bit optimistic though because having the plugin system integrated into the build system is a different approach that solves multiple problems I think. I would like t

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Hi all, First, I like the idea of gradle being the plugin solution endebbed within OFBiz. This could allow OFBiz integrators to share their specific improvments with a easy to use, OOTB tool (thinking about OfbizExtra addons or Pierre's OEM initiatives to name a few). Then, from what i und

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Le 22/07/2016 à 15:31, Nicolas Malin a écrit : Hi, Taher I like you proposal, and I wish to add some complement :) hot-deploy is to manage specific customer site component with the business logic specific to each, Apache OFBiz can help to prepare this but do not more (I will like to have thi

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Taher, Nicolas, I like you plan Taher. I had a small discussion with Nicolas by phone on this subject before he wrote his answer. I told me that he prefers to separate the OOTB things (aka specialpurpose now) from the outside things (aka hot-deploy now) I still think that if we have real plug

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

This is a great step forward. Thanks Ron On 22/07/2016 11:49 AM, Taher Alkhateeb wrote: Oh I see Ron, this is already implemented. Every plugin can have a build.gradle file. This file declares the dependencies specific to that plugin (which actually points to jcenter). So that part is already

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Oh I see Ron, this is already implemented. Every plugin can have a build.gradle file. This file declares the dependencies specific to that plugin (which actually points to jcenter). So that part is already done for you :) now we need to figure out the plugin API which was being discussed in the la

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

I was thinking more about the 3rd party artifacts that can not be included in releases but need to be installed before OFBiz can run. I guess that I am assuming that eventually a user will get some sort of installer that will take all of the various components developed by OFBiz, find all of t

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Hi Ron, Maven and Jcenter are jar repositories. OFBiz components are not jars, so I am not sure but I think it would not fit, unless perhaps we can jar and unjar the folder not sure. On Friday, 22 July 2016, Ron Wheeler wrote: > For 3rd party libraries, would Maven Central be a good source? > E

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

For 3rd party libraries, would Maven Central be a good source? Everything is there that does not need a license to access There is a well defined and well supported service for getting artifacts. Ron On 22/07/2016 9:31 AM, Nicolas Malin wrote: Hi, Taher I like you proposal, and I wish to add s

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Hi Nicolas, Actually as I was discussing this with Jacques in one of the JIRAs he mentioned something which I found very interesting: If we create a full plugin API for creating a new plugin from templates and we provide everything necessary for updating then perhaps hot-deploy is even not that n

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Hi, Taher I like you proposal, and I wish to add some complement :) hot-deploy is to manage specific customer site component with the business logic specific to each, Apache OFBiz can help to prepare this but do not more (I will like to have this as best practice) I agree to add a new direct

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Hi Pierre, all, I think perhaps my proposal was short and therefore your understanding of it is a bit different than what I had in mind. So I list below more specifically what I mean about each point from the ones you mentioned above to further fine-tune the discussion. - The difference between c

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Le 19/07/2016 à 22:57, Jacques Le Roux a écrit : the graph needs to be checked/amended to possibly remove components dependencies only introduced by the data model Sorry, I have noticed I have the bad tendency of using the word "introduced" instead of "put" or "add" (due to "introduire" false fr

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

feel free to respond with your feedback and comments. Thanks Sharan -- View this message in context: http://ofbiz.135035.n4.nabble.com/DISCUSSION-Proposed-Task-List-for-Moving-Forward-with-Gradle-and-the-Trunk-tp4687808p4688257.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

--- We would like * to propose changing the name of the specialpurpose folder to 'plugins'* These are the 3 areas we would like to progress so please feel free to respond with your feedback and comments. T

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

s: > > >>> > > > > > >>> > > > Task 1 “Replace all the current jars in OFBiz with appropriate > > >>> remote > > >>> > > > libraries from a download repository > > >>> > > > > > >>> >

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

t; The work to replace the jars is ongoing and we have already > >>> removed 169 > >>> > > of > >>> > > > them. These libraries will now be automatically downloaded by > >>> Gradle. > >>> > > Work > >>> > > > wil

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

> > > are finding library migration issues with some of the >>> specialpurpose >>> > > > components so would like *to propose to deactivate all >>> specialpurpose >>> > > > components by default.* >>> > > > >>> &g

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

t tests in\u2002\u2002$component/src/test/java” >> > > > >> > > >> > >> -----------------------------------

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

y structure so that we can separate the Java files between > main > > > and > > > > test. This will help us simplify the implementation of a testing > > > framework. > > > > *The proposal for the directory structure is as follows: > > > > > > > >componentname/src/main/java > > > >componentname/src/test/java* > > > > > > > > > > > > Task 10. “Propose the renaming specialpurpose to plugins or such an > > > > appropriate name for clarity” > > > > > > > > > > - > > > > We would like * to propose changing the name of the specialpurpose > > > folder to > > > > 'plugins'* > > > > > > > > These are the 3 areas we would like to progress so please feel free > to > > > > respond with your feedback and comments. > > > > > > > > Thanks > > > > Sharan > > > > > > > > > > > > > > > > > > > > -- > > > > View this message in context: > > > > > > http://ofbiz.135035.n4.nabble.com/DISCUSSION-Proposed-Task-List-for-Moving-Forward-with-Gradle-and-the-Trunk-tp4687808p4688257.html > > > > Sent from the OFBiz - Dev mailing list archive at Nabble.com. > > > > > > > > > >

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

ponentname/src/main/java > > >componentname/src/test/java* > > > > > > > > > Task 10. “Propose the renaming specialpurpose to plugins or such an > > > appropriate name for clarity” > > > > > > - > > > We would like * to propose changing the name of the specialpurpose > > folder to > > > 'plugins'* > > > > > > These are the 3 areas we would like to progress so please feel free to > > > respond with your feedback and comments. > > > > > > Thanks > > > Sharan > > > > > > > > > > > > > > > -- > > > View this message in context: > > > http://ofbiz.135035.n4.nabble.com/DISCUSSION-Proposed-Task-List-for-Moving-Forward-with-Gradle-and-the-Trunk-tp4687808p4688257.html > > > Sent from the OFBiz - Dev mailing list archive at Nabble.com. > > > > > >

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

-- > > We would like * to propose changing the name of the specialpurpose > folder to > > 'plugins'* > > > > These are the 3 areas we would like to progress so please feel free to > > respond with your feedback and comments. > > > > Thanks > > Sharan > > > > > > > > > > -- > > View this message in context: > http://ofbiz.135035.n4.nabble.com/DISCUSSION-Proposed-Task-List-for-Moving-Forward-with-Gradle-and-the-Trunk-tp4687808p4688257.html > > Sent from the OFBiz - Dev mailing list archive at Nabble.com. > > >

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

folder to > 'plugins'* > > These are the 3 areas we would like to progress so please feel free to > respond with your feedback and comments. > > Thanks > Sharan > > > > > -- > View this message in context: > http://ofbiz.135035.n4.nabble.com/DISCUSSION-Proposed-Task-List-for-Moving-Forward-with-Gradle-and-the-Trunk-tp4687808p4688257.html > Sent from the OFBiz - Dev mailing list archive at Nabble.com. >

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

onentname/src/test/java* > > > > > > > > > Task 10. “Propose the renaming specialpurpose to plugins or such an > > > appropriate name for clarity” > > > > > > - > > > We would like * to propose changing the name of the specialpurpose > > folder to > > > 'plugins'* > > > > > > These are the 3 areas we would like to progress so please feel free to > > > respond with your feedback and comments. > > > > > > Thanks > > > Sharan > > > > > > > > > > > > > > > -- > > > View this message in context: > > > > > > http://ofbiz.135035.n4.nabble.com/DISCUSSION-Proposed-Task-List-for-Moving-Forward-with-Gradle-and-the-Trunk-tp4687808p4688257.html > > > Sent from the OFBiz - Dev mailing list archive at Nabble.com. > > > > > >

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

name for clarity” > > > --------- > > We would like * to propose changing the name of the specialpurpose > folder to > > 'plugins'* > > > > These are the 3 areas we would like to progress so please feel free to > > respond with your feedback and comments. > > > > Thanks > > Sharan > > > > > > > > > > -- > > View this message in context: > > > http://ofbiz.135035.n4.nabble.com/DISCUSSION-Proposed-Task-List-for-Moving-Forward-with-Gradle-and-the-Trunk-tp4687808p4688257.html > > Sent from the OFBiz - Dev mailing list archive at Nabble.com. > > >

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

ese are the 3 areas we would like to progress so please feel free to > respond with your feedback and comments. > > Thanks > Sharan > > > > > -- > View this message in context: > http://ofbiz.135035.n4.nabble.com/DISCUSSION-Proposed-Task-List-for-Moving-Forward-with-Gradle-and-the-Trunk-tp4687808p4688257.html > Sent from the OFBiz - Dev mailing list archive at Nabble.com. >

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

ran -- View this message in context: http://ofbiz.135035.n4.nabble.com/DISCUSSION-Proposed-Task-List-for-Moving-Forward-with-Gradle-and-the-Trunk-tp4687808p4688257.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

ugins'* These are the 3 areas we would like to progress so please feel free to respond with your feedback and comments. Thanks Sharan -- View this message in context: http://ofbiz.135035.n4.nabble.com/DISCUSSION-Proposed-Task-List-for-Moving-Forward-with-Gradle-and-the-Trunk-tp4687808p46

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Hi Sharan, Thank you for wonderfully coordinating and organizing this project. +1 for all points from my side. One more thing ! I suggest that we make the specialpurpose components (plugins!) deactivated by default! Those who are interested in a certain plugin would issue the appropriate gradle

[DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

Hi Everyone A brief update and also some ideas for moving forward with Gradle and the trunk. For those who missed it, the patch (OFBIZ-7534) to use Gradle in the trunk was committed to the trunk yesterday in revision 1751309. Huge thanks to Taher for working so hard and also co-ordinating it.