date:20160714


[ 
https://issues.apache.org/jira/browse/OFBIZ-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378884#comment-15378884
 ] 

Taher Alkhateeb commented on OFBIZ-7534:


Hi Jacques,

no I just wanted to break it into newlines. Now that you mentioned it maybe it 
is better to actually generate html instead? I did it quickly and did not think 
too much about formatting.

> Migrate OFBiz from Apache Ant to Gradle build system
> 
>
> Key: OFBIZ-7534
> URL: https://issues.apache.org/jira/browse/OFBIZ-7534
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Affects Versions: Upcoming Branch
>Reporter: Taher Alkhateeb
>Assignee: Taher Alkhateeb
>  Labels: ant, build-tools, gradle
> Attachments: ANT_GRADLE_COMPARISON.txt, OFBIZ-7534.patch, 
> OFBIZ-7534.patch, OFBIZ-7534.patch, OFBIZ-7534.patch, OFBizRemoteJarList.csv, 
> OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, 
> gradle-wrapper.jar
>
>
> This is a major refactoring task referring to the [email 
> thread|http://ofbiz.markmail.org/message/vstt3wxuubmjgmqj?q=Important+Changes+to+Trunk+and+Use+of+Ant+%26+Gradle]
>  in which the community voted for the switch after a proposal from the PMC
> The purpose of this JIRA is to achieve the following objectives
> - Fully implement a working compiling system in Gradle that passes all tests
> - Remove all ant and maven build scripts from the system
> - update the documentation of the system to reflect these changes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7798) Translate the svn and git info footers


 [ 
https://issues.apache.org/jira/browse/OFBIZ-7798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux updated OFBIZ-7798:
---
Summary: Translate the svn and git info footers  (was: Translated th svn 
and git info footers)

> Translate the svn and git info footers
> --
>
> Key: OFBIZ-7798
> URL: https://issues.apache.org/jira/browse/OFBIZ-7798
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Trivial
> Fix For: Upcoming Branch
>
>
> We slightly changed the old format of the footer. The old format used only 
> the translated words _uiLabelMap.CommonBuiltOn_ and _uiLabelMap.CommonWith_. 
> On the other hand, the new format contains the words Branch, Revision, Built 
> On and Java Version.
> We need to translate all four words in the CommonUiLabels.xml and then 
> incorporate them
> old version:
> {code}
> " - Release-revision : ${releasePath}-r${info.entry.commit(revision)},  
> ${uiLabelMap.CommonBuiltOn} ${dateTime} ${uiLabelMap.CommonWith} Java 
> ${java.version}
> {code}
> new version:
> {code}
> "Branch: ${info.entry.url.text()}" + System.lineSeparator()
> "Revision: ${info.entry.commit.@revision}" + System.lineSeparator()
> "Built on: ${timestamp}" + System.lineSeparator()
> "Java Version: ${org.gradle.internal.jvm.Jvm.current()}"
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7798) Translated th svn and git info footers

Jacques Le Roux created OFBIZ-7798:
--

 Summary: Translated th svn and git info footers
 Key: OFBIZ-7798
 URL: https://issues.apache.org/jira/browse/OFBIZ-7798
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: Trunk
Reporter: Jacques Le Roux
Priority: Trivial
 Fix For: Upcoming Branch


We slightly changed the old format of the footer. The old format used only the 
translated words _uiLabelMap.CommonBuiltOn_ and _uiLabelMap.CommonWith_. On the 
other hand, the new format contains the words Branch, Revision, Built On and 
Java Version.

We need to translate all four words in the CommonUiLabels.xml and then 
incorporate them

old version:
{code}
" - Release-revision : ${releasePath}-r${info.entry.commit(revision)},  
${uiLabelMap.CommonBuiltOn} ${dateTime} ${uiLabelMap.CommonWith} Java 
${java.version}
{code}

new version:
{code}
"Branch: ${info.entry.url.text()}" + System.lineSeparator()
"Revision: ${info.entry.commit.@revision}" + System.lineSeparator()
"Built on: ${timestamp}" + System.lineSeparator()
"Java Version: ${org.gradle.internal.jvm.Jvm.current()}"
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7534) Migrate OFBiz from Apache Ant to Gradle build system


[ 
https://issues.apache.org/jira/browse/OFBIZ-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378880#comment-15378880
 ] 

Jacques Le Roux commented on OFBIZ-7534:


Hi Taher, yes I think so, but why do we have + System.lineSeparator()? Is that 
needed for the file construction?

> Migrate OFBiz from Apache Ant to Gradle build system
> 
>
> Key: OFBIZ-7534
> URL: https://issues.apache.org/jira/browse/OFBIZ-7534
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Affects Versions: Upcoming Branch
>Reporter: Taher Alkhateeb
>Assignee: Taher Alkhateeb
>  Labels: ant, build-tools, gradle
> Attachments: ANT_GRADLE_COMPARISON.txt, OFBIZ-7534.patch, 
> OFBIZ-7534.patch, OFBIZ-7534.patch, OFBIZ-7534.patch, OFBizRemoteJarList.csv, 
> OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, 
> gradle-wrapper.jar
>
>
> This is a major refactoring task referring to the [email 
> thread|http://ofbiz.markmail.org/message/vstt3wxuubmjgmqj?q=Important+Changes+to+Trunk+and+Use+of+Ant+%26+Gradle]
>  in which the community voted for the switch after a proposal from the PMC
> The purpose of this JIRA is to achieve the following objectives
> - Fully implement a working compiling system in Gradle that passes all tests
> - Remove all ant and maven build scripts from the system
> - update the documentation of the system to reflect these changes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5840) Create bootstrap theme

2016-07-14 Thread Derek Lew (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378875#comment-15378875
 ] 

Derek Lew commented on OFBIZ-5840:
--

May I know the direction on this bootstrap theme?

> Create bootstrap theme
> --
>
> Key: OFBIZ-5840
> URL: https://issues.apache.org/jira/browse/OFBIZ-5840
> Project: OFBiz
>  Issue Type: New Feature
>  Components: framework, themes
>Affects Versions: Bootstrap theme
>Reporter: Julien NICOLAS
>Assignee: Jacques Le Roux
>  Labels: bootstrap, theme
> Attachments: Facility.PNG, FindAgreement..png, Footer.jpg, 
> GlobalDecorator.patch, ImprovedFooter.patch, MacroMenuRenderer.patch, 
> OFBIZ-5840-Menufactory.patch, OFBIZ-5840-Menufactory.patch, 
> appbar_menu_ftl.patch, bootified.js, bootified_js_screentrans.patch, 
> bootstrap-theme.zip, bootstrap.zip, bootstrapThemeToTrunk.patch, 
> calendar.PNG, catalog.png, glyphicons-halflings-regular.zip, 
> htmlMenuMacroLibrary.patch, lookupField_patch.patch, 
> pagination_htmlFormMacroLibrary.patch, 
> panelCollapse_htmlSreenMacroLibrary.patch, party menu tab bar.PNG, 
> preferences.png, styling_issue_1.png, styling_issue_2.png, 
> styling_issue_3.png, styling_issue_4.png, styling_issue_5.png, 
> styling_issue_6.png, styling_issue_7.png, styling_issue_8.png, 
> styling_issue_9.png, tab-bar.png, workeffort.PNG
>
>
> 1- create a sub-directory called bootstrap under the image webapp to put
> the resources over there (js, css and fonts) as indicated earlier by Gavin.
> (Julien : not sure about location)
> 2- check to make sure that the current version of jQuery is compatible with
> the installed version or upgrade it accordingly
> 3- Create a new theme based on one of the existing themes as suggested by
> Julien and Gavin
> 4- Test the theme by switching to it and handle major bugs / issues.
> 5- Start to make a few test screens utilizing Bootstrap



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Which versions on new demo VM?


It seems nobody disagreed so I will apply this KISS plan, thanks Taher

Jacques


Le 10/07/2016 à 06:53, Jacques Le Roux a écrit :

Thanks Taher,

I finally see no reasons to not send this message to the dev ML. I forward your 
answer.

Jacques


Le 09/07/2016 à 19:00, Taher Alkhateeb a écrit :

Hi Jacques,

I suggest that we keep only two demo VMs instead of three. One for old /
stable (13) and one for trunk and that's it. Once we branch out 16 and
stabilize it into a release then we reshuffle things again.

Under the exceptional transformational conditions we are going through, I
think I would not bother with having too many demos up and running

Regards,

Taher Alkhateeb

On Sat, Jul 9, 2016 at 3:48 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


Hi,

I have promised to Gavin to put in place the demos on the new VM this
weekend.

I think I can easily do it with the current setting. But I wonder if we
could not benefit from this change to also change the versioned demos.

On the other hand it's a bold decision because it would mean that we
switch R13 to old and use R14 or even R15 as "stable", which does not make
sense. But finally how long will we demos with so old stuff?

Opinions?

Later I will also put a letsencrypt script to automatically generate the
certificates (must be done each 3 months)

Jacques

[jira] [Commented] (OFBIZ-7795) Clean the tools directory


[ 
https://issues.apache.org/jira/browse/OFBIZ-7795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378870#comment-15378870
 ] 

Jacques Le Roux commented on OFBIZ-7795:


Partly done at revision: 1752771 , WIP...


> Clean the tools directory
> -
>
> Key: OFBIZ-7795
> URL: https://issues.apache.org/jira/browse/OFBIZ-7795
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: tools
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
> Fix For: Upcoming Branch
>
>
> Some scripts, at least, are meaningless after the Gradel move. They need to 
> be amended or removed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7797) Bug in OfbizSetup Create Customer Step

2016-07-14 Thread Derek Lew (JIRA)

Derek Lew created OFBIZ-7797:


 Summary: Bug in OfbizSetup Create Customer Step
 Key: OFBIZ-7797
 URL: https://issues.apache.org/jira/browse/OFBIZ-7797
 Project: OFBiz
  Issue Type: Bug
  Components: commonext/setup
Affects Versions: Release Branch 15.12, Trunk, Release Branch 14.12
 Environment: Windows 10
Reporter: Derek Lew


When running the OFBiz Setup Application, the following exception was thrown.


The Following Errors Occurred:
ERROR: Could not complete the Create Customer 
[file:/E:/OfBiz14.12/applications/commonext/script/org/ofbiz/setup/SetupEvents.xml#createOrganization]
 process [problem invoking the [createCustomTimePeriod] service with the map 
named [customTimePeriodCtx] containing [{fromDate=2016-01-01, periodNum=1, 
userLogin=[GenericEntity:UserLogin][createdStamp,2016-07-13 
18:19:01.72(java.sql.Timestamp)][createdTxStamp,2016-07-13 
18:19:01.608(java.sql.Timestamp)][currentPassword,$SHA$wN7vvoeHKomFb$fhBdrGDkWvhPdxOX3PW8g1ucPP4(java.lang.String)][disabledDateTime,null()][enabled,Y(java.lang.String)][externalAuthId,null()][hasLoggedOut,null()][isSystem,null()][lastCurrencyUom,null()][lastLocale,null()][lastTimeZone,null()][lastUpdatedStamp,2016-07-13
 18:19:52.017(java.sql.Timestamp)][lastUpdatedTxStamp,2016-07-13 
18:19:51.994(java.sql.Timestamp)][partyId,null()][passwordHint,null()][requirePasswordChange,N(java.lang.String)][successiveFailedLogins,0(java.lang.Long)][userLdapDn,null()][userLoginId,admin(java.lang.String)],
 isClosed=N, periodTypeId=FISCAL_YEAR, organizationPartyId=10006, 
periodName=2016, locale=en_US, thruDate=2016-12-31}]: Type check failed for 
field [createCustomTimePeriod.fromDate]; expected type is [java.sql.Timestamp]; 
actual type is [java.sql.Date]Type check failed for field 
[createCustomTimePeriod.thruDate]; expected type is [java.sql.Timestamp]; 
actual type is [java.sql.Date]]
•   

In \applications\commonext\script\org\ofbiz\setup\SetupEvents.xml

250   
251   

Need to change to:

250
251





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7796) Running OFBiz as a service fails


 [ 
https://issues.apache.org/jira/browse/OFBIZ-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-7796:

Affects Version/s: Trunk

> Running OFBiz as a service fails
> 
>
> Key: OFBIZ-7796
> URL: https://issues.apache.org/jira/browse/OFBIZ-7796
> Project: OFBiz
>  Issue Type: Bug
>Affects Versions: Trunk
> Environment: Ubuntu 16.04, openjdk-8-jdk
>Reporter: Pierre Smits
>Priority: Blocker
>
> In a new ubuntu environment I performed a checkout  from trunk and ran the 
> loadDefault build script.
> After this had completed, I moved the ofbiz directory from my user folder to 
> the /opt folder, and configured the Ubuntu environment to be able to run 
> OFBiz as a service.
> This entails:
> * deploy a script in /etc/init.d
> * set the correct permissions of the service script
> * create the service user 
> * changed the owner and ownergroup of the files and folders in /opt/ofbiz
> and then fire the service:
> sudo /etc/init.d/ofbiz start
> This normally starts the proces java -jar ofbiz.jar
> But now nothing happens.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7796) Running OFBiz as a service fails

Pierre Smits created OFBIZ-7796:
---

 Summary: Running OFBiz as a service fails
 Key: OFBIZ-7796
 URL: https://issues.apache.org/jira/browse/OFBIZ-7796
 Project: OFBiz
  Issue Type: Bug
 Environment: Ubuntu 16.04, openjdk-8-jdk
Reporter: Pierre Smits
Priority: Blocker


In a new ubuntu environment I performed a checkout  from trunk and ran the 
loadDefault build script.

After this had completed, I moved the ofbiz directory from my user folder to 
the /opt folder, and configured the Ubuntu environment to be able to run OFBiz 
as a service.
This entails:
* deploy a script in /etc/init.d
* set the correct permissions of the service script
* create the service user 
* changed the owner and ownergroup of the files and folders in /opt/ofbiz

and then fire the service:
sudo /etc/init.d/ofbiz start

This normally starts the proces java -jar ofbiz.jar

But now nothing happens.






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7795) Clean the tools directory

Jacques Le Roux created OFBIZ-7795:
--

 Summary: Clean the tools directory
 Key: OFBIZ-7795
 URL: https://issues.apache.org/jira/browse/OFBIZ-7795
 Project: OFBiz
  Issue Type: Sub-task
  Components: tools
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
 Fix For: Upcoming Branch


Some scripts, at least, are meaningless after the Gradel move. They need to be 
amended or removed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7754) The big problem when load seed.


[ 
https://issues.apache.org/jira/browse/OFBIZ-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378849#comment-15378849
 ] 

Jacques Le Roux commented on OFBIZ-7754:


I agree Pierre, that sounds like the best solution, thanks!

> The big problem when load seed.
> ---
>
> Key: OFBIZ-7754
> URL: https://issues.apache.org/jira/browse/OFBIZ-7754
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Kongrath Suankaewmanee
>Assignee: Jacques Le Roux
> Attachments: OFBIZ-7754.patch
>
>
> Hi All,
> Regarding, [OFBIZ-7112|https://issues.apache.org/jira/browse/OFBIZ-7112]
> That's good for who start on use the ofbiz with initial setup, but not for 
> the site that already online and has to update the OFBiz core. Because when 
> has update OFBiz core they will use command load-seed for update.
> The problem is if we use load-seed mean the configuration data that's already 
> exists will be replaced by the data from this file,
> *CommonSystemPropertyData.xml*
> So, for my suggestion should change the reader from *seed* to *seed-initial*  
> or remove systemPropertyValue from the data file.
> Thank you,
> Kongrath



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Clean up XSD on ofbiz/site/dtds/


Thanks Deepak,

Done at revision: 1752764

Jacques


Le 21/06/2016 à 15:24, Deepak Dixit a écrit :

I think we can remove them as well, currently we are doing major
refactoring in trunk and all are not backward compatible. So its good idea
to clean xsd as well.

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Tue, Jun 21, 2016 at 6:16 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


Hi All,

At r1749490, I wondered about removing simple-methods-v2.xsd and
regions.xsd which are no longer used, and for a moment, but could be that
old custom projects still need them.

What do you hinkt about that and about all XSD files actually?

Thanks

Jacques

[jira] [Commented] (OFBIZ-7534) Migrate OFBiz from Apache Ant to Gradle build system


[ 
https://issues.apache.org/jira/browse/OFBIZ-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378816#comment-15378816
 ] 

Jacques Le Roux commented on OFBIZ-7534:


Hi Taher, OK thanks. I will begin by removing this one.

> Migrate OFBiz from Apache Ant to Gradle build system
> 
>
> Key: OFBIZ-7534
> URL: https://issues.apache.org/jira/browse/OFBIZ-7534
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Affects Versions: Upcoming Branch
>Reporter: Taher Alkhateeb
>Assignee: Taher Alkhateeb
>  Labels: ant, build-tools, gradle
> Attachments: ANT_GRADLE_COMPARISON.txt, OFBIZ-7534.patch, 
> OFBIZ-7534.patch, OFBIZ-7534.patch, OFBIZ-7534.patch, OFBizRemoteJarList.csv, 
> OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, 
> gradle-wrapper.jar
>
>
> This is a major refactoring task referring to the [email 
> thread|http://ofbiz.markmail.org/message/vstt3wxuubmjgmqj?q=Important+Changes+to+Trunk+and+Use+of+Ant+%26+Gradle]
>  in which the community voted for the switch after a proposal from the PMC
> The purpose of this JIRA is to achieve the following objectives
> - Fully implement a working compiling system in Gradle that passes all tests
> - Remove all ant and maven build scripts from the system
> - update the documentation of the system to reflect these changes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7534) Migrate OFBiz from Apache Ant to Gradle build system


[ 
https://issues.apache.org/jira/browse/OFBIZ-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378809#comment-15378809
 ] 

Taher Alkhateeb commented on OFBIZ-7534:


Hi Jacques,

I believe we definitely have more cases like this one. Now you can go to each 
library and set the exclusions by hand. However I think the original 
dependencies and libraries were not properly setup because they were scattered 
among different components and hand picked by different individuals. Having 
automatic dependency resolution means you don't worry about what gets pulled.

Also the dependencies graph because of the huge number of libraries in OFBiz is 
very complex. So I would recommend instead of trying to replicate what we had 
before dependency management we instead focus on actually removing as many 
libraries as we can. 229 libraries is a number I don't recall seeing in any 
other project.

> Migrate OFBiz from Apache Ant to Gradle build system
> 
>
> Key: OFBIZ-7534
> URL: https://issues.apache.org/jira/browse/OFBIZ-7534
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Affects Versions: Upcoming Branch
>Reporter: Taher Alkhateeb
>Assignee: Taher Alkhateeb
>  Labels: ant, build-tools, gradle
> Attachments: ANT_GRADLE_COMPARISON.txt, OFBIZ-7534.patch, 
> OFBIZ-7534.patch, OFBIZ-7534.patch, OFBIZ-7534.patch, OFBizRemoteJarList.csv, 
> OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, 
> gradle-wrapper.jar
>
>
> This is a major refactoring task referring to the [email 
> thread|http://ofbiz.markmail.org/message/vstt3wxuubmjgmqj?q=Important+Changes+to+Trunk+and+Use+of+Ant+%26+Gradle]
>  in which the community voted for the switch after a proposal from the PMC
> The purpose of this JIRA is to achieve the following objectives
> - Fully implement a working compiling system in Gradle that passes all tests
> - Remove all ant and maven build scripts from the system
> - update the documentation of the system to reflect these changes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[RESOLVED]Re: Editing comments in Jira


I came to the conclusion that nobody longer cares

Jacques


Le 06/07/2016 à 11:25, Jacques Le Roux a écrit :

Hi,

Long ago we decided about this policy which is written as an info block at 
https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Contributors+Best+Practices


>


It has been lost for some time. I know some committers (Scott for instance) really wanted this way of doing. I wonder know if we should continue to 
advice to respect it or if we should discard it.


Opininons?

Jacques

[jira] [Comment Edited] (OFBIZ-7793) Add download definition for drivers of commonly used open source rdbms to build gradle


[ 
https://issues.apache.org/jira/browse/OFBIZ-7793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378403#comment-15378403
 ] 

Jacques Le Roux edited comment on OFBIZ-7793 at 7/14/16 9:32 PM:
-

I'm not strongly against this solution, and we could live with it temporarily 
but I think for this issue as for OFBIZ-7773 we should follow the Apache Groovy 
team recommendation which is to use 
https://github.com/tkruse/gradle-groovysh-plugin. We could then ask users for 
their preference, it's here a bit more difficult so maybe best to forget it and 
let users completly decide about it.

Globally for static downloads, one issue I'm thinking about is possible 
vulnerabilities. Here see eg 
https://www.cvedetails.com/google-search-results.php?q=jdbc=Search
The beauty of a tool like Gradle is it should automatically prevent 
vulnerabilities. We can of course cross compilation issues with automatic 
updates but it's orders of magnitude less dangerous than an hidden 
vulnerability...


was (Author: jacques.le.roux):
I'm not strongly against this solution, and we could live with it temporarily 
but I think for this issue as for OFBIZ-7773 we should follow the Apache Groovy 
team recommendation which is to use 
https://github.com/tkruse/gradle-groovysh-plugin. We could then ask users for 
their preference, it's here a bit more difficult do maybe best to forget it and 
let users completly decide about it.

Globally for static downloads, one issue I'm thinking about is possible 
vulnerabilities. Here see eg 
https://www.cvedetails.com/google-search-results.php?q=jdbc=Search
The beauty of a tool like Gradle is it should automatically prevent 
vulnerabilities. We can of course cross compilation issues with automatic 
updates but it's orders of magnitude less dangerous than an hidden 
vulnerability...

> Add download definition for drivers of commonly used open source rdbms to 
> build gradle
> --
>
> Key: OFBIZ-7793
> URL: https://issues.apache.org/jira/browse/OFBIZ-7793
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
> Attachments: OFBIZ-7793-build.gradle.patch
>
>
> With the move to dependency mgt through gradle/gradlew the download 
> definitions for the drivers of the most commonly used rdbms solutions were 
> removed.
> Adding these to the build.gradle file will deliver a great pleasure adoption 
> wise through a small effort.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7534) Migrate OFBiz from Apache Ant to Gradle build system


[ 
https://issues.apache.org/jira/browse/OFBIZ-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378424#comment-15378424
 ] 

Jacques Le Roux commented on OFBIZ-7534:


I was wondering why we have commons-httpclient:3.1 in the dependencies? It's 
not in the list above and was removed with OFBIZ-6755. I checked with "gradlew 
dependencies" and see it comes from external dependency which still relies on 
it. But does that means that we should have it as a lib? It was absent in trunk 
before the Gradle changes. I'll check if we have such other cases...

> Migrate OFBiz from Apache Ant to Gradle build system
> 
>
> Key: OFBIZ-7534
> URL: https://issues.apache.org/jira/browse/OFBIZ-7534
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Affects Versions: Upcoming Branch
>Reporter: Taher Alkhateeb
>Assignee: Taher Alkhateeb
>  Labels: ant, build-tools, gradle
> Attachments: ANT_GRADLE_COMPARISON.txt, OFBIZ-7534.patch, 
> OFBIZ-7534.patch, OFBIZ-7534.patch, OFBIZ-7534.patch, OFBizRemoteJarList.csv, 
> OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, 
> gradle-wrapper.jar
>
>
> This is a major refactoring task referring to the [email 
> thread|http://ofbiz.markmail.org/message/vstt3wxuubmjgmqj?q=Important+Changes+to+Trunk+and+Use+of+Ant+%26+Gradle]
>  in which the community voted for the switch after a proposal from the PMC
> The purpose of this JIRA is to achieve the following objectives
> - Fully implement a working compiling system in Gradle that passes all tests
> - Remove all ant and maven build scripts from the system
> - update the documentation of the system to reflect these changes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7793) Add download definition for drivers of commonly used open source rdbms to build gradle


[ 
https://issues.apache.org/jira/browse/OFBIZ-7793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378403#comment-15378403
 ] 

Jacques Le Roux commented on OFBIZ-7793:


I'm not strongly against this solution, and we could live with it temporarily 
but I think for this issue as for OFBIZ-7773 we should follow the Apache Groovy 
team recommendation which is to use 
https://github.com/tkruse/gradle-groovysh-plugin. We could then ask users for 
their preference, it's here a bit more difficult do maybe best to forget it and 
let users completly decide about it.

Globally for static downloads, one issue I'm thinking about is possible 
vulnerabilities. Here see eg 
https://www.cvedetails.com/google-search-results.php?q=jdbc=Search
The beauty of a tool like Gradle is it should automatically prevent 
vulnerabilities. We can of course cross compilation issues with automatic 
updates but it's orders of magnitude less dangerous than an hidden 
vulnerability...

> Add download definition for drivers of commonly used open source rdbms to 
> build gradle
> --
>
> Key: OFBIZ-7793
> URL: https://issues.apache.org/jira/browse/OFBIZ-7793
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
> Attachments: OFBIZ-7793-build.gradle.patch
>
>
> With the move to dependency mgt through gradle/gradlew the download 
> definitions for the drivers of the most commonly used rdbms solutions were 
> removed.
> Adding these to the build.gradle file will deliver a great pleasure adoption 
> wise through a small effort.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Should few Gradle tasks be interactive has were similars in Ant?

Thanks Gavin,

I made some research since and came with a conclusion we should try to use https://github.com/tkruse/gradle-groovysh-plugin as recommended by Apache
Groovy team

I'll investigate this in the context of OFBIZ-7773 and possibly OFBIZ-7793

Jacques

Le 14/07/2016 à 20:08, Gavin Mabie a écrit :

Not using interactive tasks would be going against the very philosophy
behind Gradle. "Unlike the build file formats of Ant and Maven,
Gradle’s Groovy-based build files allow you to do general-purpose
programming tasks in your build file. This relieves much of the
frustration developers have faced in lacking control flow in Ant
or being forced into plug-in development in Maven to accomplish
nonstandard tasks."

Lower level build tasks may require little user interaction typically those
tasks linked to building the system and it's components. Higher level
tasks will definitely involve user-interaction which is where Groovy comes
into the equation. In fact, it makes Gradle’s use of Ant simpler
than directly using Ant, partly by leveraging Groovy’s AntBuilder
functionality. I have used Ant builder before for tasks such as:
1. Creating a charts of accounts;
2. Building a catalogue;
3. Building a webstore;
4. Building a theme.

These are some examples of build tasks that are on a higher level with less
generic application.

My 2 cents.

Gavin
On 10 Jul 2016 1:02 PM, "Jacques Le Roux"
wrote:

Le 10/07/2016 à 12:48, Jacques Le Roux a écrit :

Hi,

See https://issues.apache.org/jira/browse/OFBIZ-7773 and
https://issues.apache.org/jira/browse/OFBIZ-7772

Opinions (about the question in title: "Should we?")

Thanks

Jacques

This could help
https://mrhaki.blogspot.fr/2010/09/gradle-goodness-get-user-input-values.html

Jacques

[jira] [Updated] (OFBIZ-7790) Change the Java Directory Structure to Main and Test


 [ 
https://issues.apache.org/jira/browse/OFBIZ-7790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharan Foga updated OFBIZ-7790:
---
Description: 
Change of the directory 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 wew directory structure will be as follows:

   componentname/src/main/java
   componentname/src/test/java

This JIRA will we used for the migration of all compoenents

  was:
Change of the directory 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 wew directory structure will be as follows:

   componentname/src/main/java
   componentname/src/test/java*

This JIRA will we used for the migration of all compoenents


> Change the Java Directory Structure to Main and Test
> 
>
> Key: OFBIZ-7790
> URL: https://issues.apache.org/jira/browse/OFBIZ-7790
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Sharan Foga
>
> Change of the directory 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 wew directory structure will be as follows:
>componentname/src/main/java
>componentname/src/test/java
> This JIRA will we used for the migration of all compoenents



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7793) Add download definition for drivers of commonly used open source rdbms to build gradle


[ 
https://issues.apache.org/jira/browse/OFBIZ-7793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378098#comment-15378098
 ] 

Pierre Smits commented on OFBIZ-7793:
-

Is not everything temporary? 

Do you see any adopter posting issues about the drivers selecting not working 
with their (production) environments? If that happens, we'll deal with then. 
Let us not jump the fence here, and just help potential adopters, reviewers and 
contributors.

A little deed goes a long way. And reputations break easily.

> Add download definition for drivers of commonly used open source rdbms to 
> build gradle
> --
>
> Key: OFBIZ-7793
> URL: https://issues.apache.org/jira/browse/OFBIZ-7793
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
> Attachments: OFBIZ-7793-build.gradle.patch
>
>
> With the move to dependency mgt through gradle/gradlew the download 
> definitions for the drivers of the most commonly used rdbms solutions were 
> removed.
> Adding these to the build.gradle file will deliver a great pleasure adoption 
> wise through a small effort.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7793) Add download definition for drivers of commonly used open source rdbms to build gradle


[ 
https://issues.apache.org/jira/browse/OFBIZ-7793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378067#comment-15378067
 ] 

Pierre Smits commented on OFBIZ-7793:
-

Through community effort and collaboration

Like I did in 2015 with OFBIZ-6582 and in 2012 with OFBIZ-4800

> Add download definition for drivers of commonly used open source rdbms to 
> build gradle
> --
>
> Key: OFBIZ-7793
> URL: https://issues.apache.org/jira/browse/OFBIZ-7793
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
> Attachments: OFBIZ-7793-build.gradle.patch
>
>
> With the move to dependency mgt through gradle/gradlew the download 
> definitions for the drivers of the most commonly used rdbms solutions were 
> removed.
> Adding these to the build.gradle file will deliver a great pleasure adoption 
> wise through a small effort.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Should few Gradle tasks be interactive has were similars in Ant?

2016-07-14 Thread Gavin Mabie

Not using interactive tasks would be going against the very philosophy
behind Gradle. "Unlike the  build  file  formats  of  Ant  and  Maven,
Gradle’s  Groovy-based  build  files  allow  you to  do  general-purpose
programming  tasks  in  your  build  file.  This  relieves  much  of  the
frustration  developers  have  faced  in  lacking  control  flow  in  Ant
or  being  forced  into plug-in development in Maven to accomplish
nonstandard tasks."

Lower level build tasks may require little user interaction typically those
tasks linked to  building the system and it's components. Higher level
tasks will definitely involve user-interaction which is where Groovy comes
into the equation. In  fact,  it  makes  Gradle’s  use  of  Ant simpler
than  directly  using  Ant,  partly  by  leveraging  Groovy’s  AntBuilder
functionality. I have used Ant builder before for tasks such as:
1. Creating a charts of accounts;
2. Building a catalogue;
3. Building a webstore;
4. Building a theme.

These are some examples of build tasks that are on a higher level with less
generic application.

My 2 cents.

Gavin
On 10 Jul 2016 1:02 PM, "Jacques Le Roux" 
wrote:

> Le 10/07/2016 à 12:48, Jacques Le Roux a écrit :
>
>> Hi,
>>
>> See https://issues.apache.org/jira/browse/OFBIZ-7773 and
>> https://issues.apache.org/jira/browse/OFBIZ-7772
>>
>> Opinions (about the question in title: "Should we?")
>>
>> Thanks
>>
>> Jacques
>>
>>
>>
> This could help
> https://mrhaki.blogspot.fr/2010/09/gradle-goodness-get-user-input-values.html
>
> Jacques
>
>

[jira] [Commented] (OFBIZ-7779) Update wiki Eclipse pages regarding Gradle


[ 
https://issues.apache.org/jira/browse/OFBIZ-7779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377893#comment-15377893
 ] 

Jacques Le Roux commented on OFBIZ-7779:


Thanks Taher
All is totally clean from Gradle path issue at my end, congrats! 
It must have been a tedious work when you did not see this elsewhere, I can't 
help, I still prefer Windows :)

I have thought about updating the wiki pages. We need to keep the current 
version because we will support the current branches for a year. I see an easy 
way to do that, a link like that at the top of changed pages: 
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=7045138 it's 
the actual page versionned. So I will begin to update the pages thanks to 
Confluence versionning almost nothing more is required :)

> Update wiki Eclipse pages regarding Gradle
> --
>
> Key: OFBIZ-7779
> URL: https://issues.apache.org/jira/browse/OFBIZ-7779
> Project: OFBiz
>  Issue Type: Task
>  Components: Confluence
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
> Attachments: Image 007.png, OFBIZ-7779.patch, OFBIZ-7779.patch, 
> compile.error, neon.error
>
>
> I wanted to update the 2 wiki Eclipse pages regarding Gradle. But so far got 
> some issues in my environment (still Windows 7).
> I use both Eclipse Luna and Mars (Mars at 98%).  Luna does not support Gradle.
> First I must say my Mars instance works perfectly, but for few months I'm 
> unable to update. I did not try yet to create another Mars instance because I 
> guess it will anyway screws its update mechanism later :/
> Mars comes with the embedded ["Gradle Buildship" 
> plugin|https://gradle.org/eclipse/], I have the 1.0.5 version from 
> 2015-09-22. I found this tuto 
> http://www.vogella.com/tutorials/EclipseGradle/article.html (with a 6/7 
> clone/redundant section).
> Few remarks: I see no Gradle context menu entrie, maybe due to my unability 
> to update Mars, so I'm unable to "add Gradle support to existing Eclipse 
> project ". So I created a Gradle "trunk" side project following , but, though 
> all work well in command line, in Eclipse building with Gradle does not work. 
> I always get (see compile.error)
> Of course I tried (4th) to install Eclipse Neon, to no avail, so far the best 
> I got (at least I eventually got something) is in neon.error
> I'll continue later...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7793) Add download definition for drivers of commonly used open source rdbms to build gradle


[ 
https://issues.apache.org/jira/browse/OFBIZ-7793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377358#comment-15377358
 ] 

Jacques Le Roux commented on OFBIZ-7793:


How to maintain this? Is it only temporary (then OK)?

> Add download definition for drivers of commonly used open source rdbms to 
> build gradle
> --
>
> Key: OFBIZ-7793
> URL: https://issues.apache.org/jira/browse/OFBIZ-7793
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
> Attachments: OFBIZ-7793-build.gradle.patch
>
>
> With the move to dependency mgt through gradle/gradlew the download 
> definitions for the drivers of the most commonly used rdbms solutions were 
> removed.
> Adding these to the build.gradle file will deliver a great pleasure adoption 
> wise through a small effort.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7794) Error when updating file in CMS

2016-07-14 Thread Ingo Wolfmayr (JIRA)

Ingo Wolfmayr created OFBIZ-7794:


 Summary: Error when updating file in CMS
 Key: OFBIZ-7794
 URL: https://issues.apache.org/jira/browse/OFBIZ-7794
 Project: OFBiz
  Issue Type: Bug
  Components: content
Affects Versions: Trunk
Reporter: Ingo Wolfmayr


In-Parameter missing: 
updateContentAndUploadedFile.partyContentTypeId
updateContentAndUploadedFile.partyId

I guess it has been introduced by jira-7374 as service 
updateContentAndUploadedFile has been changed:

-
+

The change expects all content updated by updateContentAndUploadedFile  to be 
partyContent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7793) Add download definition for drivers of commonly used open source rdbms to build gradle


 [ 
https://issues.apache.org/jira/browse/OFBIZ-7793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-7793:

Attachment: OFBIZ-7793-build.gradle.patch

This patch addresses the issue.

> Add download definition for drivers of commonly used open source rdbms to 
> build gradle
> --
>
> Key: OFBIZ-7793
> URL: https://issues.apache.org/jira/browse/OFBIZ-7793
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
> Attachments: OFBIZ-7793-build.gradle.patch
>
>
> With the move to dependency mgt through gradle/gradlew the download 
> definitions for the drivers of the most commonly used rdbms solutions were 
> removed.
> Adding these to the build.gradle file will deliver a great pleasure adoption 
> wise through a small effort.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-7793) Add download definition for drivers of commonly used open source rdbms to build gradle


 [ 
https://issues.apache.org/jira/browse/OFBIZ-7793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits reassigned OFBIZ-7793:
---

Assignee: Pierre Smits

> Add download definition for drivers of commonly used open source rdbms to 
> build gradle
> --
>
> Key: OFBIZ-7793
> URL: https://issues.apache.org/jira/browse/OFBIZ-7793
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>
> With the move to dependency mgt through gradle/gradlew the download 
> definitions for the drivers of the most commonly used rdbms solutions were 
> removed.
> Adding these to the build.gradle file will deliver a great pleasure adoption 
> wise through a small effort.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7793) Add download definition for drivers of commonly used open source rdbms to build gradle


 [ 
https://issues.apache.org/jira/browse/OFBIZ-7793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-7793:

Description: 
With the move to dependency mgt through gradle/gradlew the download definitions 
for the drivers of the most commonly used rdbms solutions were removed.

Adding these to the build.gradle file will deliver a great pleasure adoption 
wise through a small effort.


  was:
With the move to dependency mgt through gradle/gradlew the download definition 
was removed.



> Add download definition for drivers of commonly used open source rdbms to 
> build gradle
> --
>
> Key: OFBIZ-7793
> URL: https://issues.apache.org/jira/browse/OFBIZ-7793
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Pierre Smits
>
> With the move to dependency mgt through gradle/gradlew the download 
> definitions for the drivers of the most commonly used rdbms solutions were 
> removed.
> Adding these to the build.gradle file will deliver a great pleasure adoption 
> wise through a small effort.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7793) Add download definition for drivers of commonly used open source rdbms to build gradle


 [ 
https://issues.apache.org/jira/browse/OFBIZ-7793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-7793:

Summary: Add download definition for drivers of commonly used open source 
rdbms to build gradle  (was: Add download definition for postgresql driver for 
build.gradle)

> Add download definition for drivers of commonly used open source rdbms to 
> build gradle
> --
>
> Key: OFBIZ-7793
> URL: https://issues.apache.org/jira/browse/OFBIZ-7793
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Pierre Smits
>
> With the move to dependency mgt through gradle/gradlew the download 
> definition was removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Ahh. I found where they were hidden in the component, with the help of [1].

[1]
https://issues.apache.org/jira/browse/OFBIZ-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356955#comment-15356955

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Thu, Jul 14, 2016 at 4:49 PM, Pierre Smits 
wrote:

> As I am a user of the cmssite I did have a look at what external libraries
> are included in that component. I have found none. Not in trunk, not in any
> of the older release branches.
>
> Are we sure that this then needs to be disabled?
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM 
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Thu, Jul 14, 2016 at 4:43 PM, Pierre Smits 
> wrote:
>
>> I can live with that.
>>
>> Best regards,
>>
>> Pierre Smits
>>
>> ORRTIZ.COM 
>> OFBiz based solutions & services
>>
>> OFBiz Extensions Marketplace
>> http://oem.ofbizci.net/oci-2/
>>
>> On Thu, Jul 14, 2016 at 4:30 PM, Jacopo Cappellato <
>> jacopo.cappell...@hotwaxsystems.com> wrote:
>>
>>> On Thu, Jul 14, 2016 at 1:35 PM, Pierre Smits 
>>> wrote:
>>>
>>> > Hi Sharan,
>>> >
>>> > I guess all accepted proposals can now be transformed into JIRA
>>> issues, for
>>> > follow-up and tracking purposes.
>>> >
>>> > Also, with respect to the failing components) I suggest that we
>>> postpone
>>> > the ultimate decision of activation/deactivation until the moment of
>>> > cutting a release. Until then, contributors can work on those issues,
>>> and
>>> > if they can't resolve the issues by the time the decision needs to be
>>> taken
>>> > we know what to deactivate precisely.
>>> >
>>>
>>> I suggest the opposite :-) if we disable them sooner than later
>>> contributors will be more aware of the work required and there be less
>>> surprises when they will be excluded from releases; disabling them sooner
>>> would probably increase the chances of fixing them because it will catch
>>> attention; if otherwise no one will care about them being disabled it
>>> could
>>> be an indicator that there is not enough interest.
>>>
>>> Jacopo
>>>
>>>
>>>
>>> > Best regards,
>>> >
>>> >
>>> > Pierre Smits
>>> >
>>> > ORRTIZ.COM 
>>> > OFBiz based solutions & services
>>> >
>>> > OFBiz Extensions Marketplace
>>> > http://oem.ofbizci.net/oci-2/
>>> >
>>> > On Thu, Jul 14, 2016 at 1:14 PM, Sharan Foga 
>>> > wrote:
>>> >
>>> > > Hi Everyone
>>> > >
>>> > > Thanks responding to these 3 proposals. Based on your feedback and
>>> > > comments we can move ahead with 2 of these for the changes to the
>>> > directory
>>> > > structure for java and the renaming of specialpurpose to 'plugins'
>>> > >
>>> > > For the third, Pierre highlighted that he was against this proposal
>>> so we
>>> > > won't be deactivating the all the specialpurpose components by
>>> default.
>>> > >
>>> > > However as mentioned previously, we are having library migration
>>> problems
>>> > > with some of the components so we can only activate the ones that
>>> don't
>>> > > have any issues; the others will not be activated and will need
>>> > additional
>>> > > work to manage the changeover to remote libraries and the resolution
>>> of
>>> > any
>>> > > startup conflicts.
>>> > >
>>> > > (Just for information the components with issues are BIRT, Ebaystore,
>>> > > ldap, POS and cmssite.)
>>> > >
>>> > > We are also looking for help with these migrations so if you would
>>> like
>>> > to
>>> > > help out fixing the issues with these specialpurpose components then
>>> > please
>>> > > let me know.
>>> > >
>>> > > Thanks
>>> > > Sharan
>>> > >
>>> > > On 2016-07-11 17:56 (+0200), Sharan-F  wrote:
>>> > > > Hi Everyone
>>> > > >
>>> > > > Another update on the task list for moving forward with Gradle and
>>> the
>>> > > > Trunk. We would also like to get community feedback and comments on
>>> > each
>>> > > of
>>> > > > the following 3 proposals:
>>> > > >
>>> > > > Task 1 “Replace all the current jars in OFBiz with appropriate
>>> remote
>>> > > > libraries from a download repository
>>> > > >
>>> > >
>>> >
>>> --
>>> > > > 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
>>> > > > will continue to remove the remaining files. As we are working
>>> through,
>>> > > we
>>> > > > are finding library migration issues with some of the
>>> specialpurpose
>>> > > > components so would like *to propose to deactivate all
>>> specialpurpose
>>> > > > components by

[jira] [Created] (OFBIZ-7793) Add download definition for postgresql driver for build.gradle

Pierre Smits created OFBIZ-7793:
---

 Summary: Add download definition for postgresql driver for 
build.gradle
 Key: OFBIZ-7793
 URL: https://issues.apache.org/jira/browse/OFBIZ-7793
 Project: OFBiz
  Issue Type: Improvement
Affects Versions: Trunk
Reporter: Pierre Smits


With the move to dependency mgt through gradle/gradlew the download definition 
was removed.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

As I am a user of the cmssite I did have a look at what external libraries
are included in that component. I have found none. Not in trunk, not in any
of the older release branches.

Are we sure that this then needs to be disabled?

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Thu, Jul 14, 2016 at 4:43 PM, Pierre Smits 
wrote:

> I can live with that.
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM 
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Thu, Jul 14, 2016 at 4:30 PM, Jacopo Cappellato <
> jacopo.cappell...@hotwaxsystems.com> wrote:
>
>> On Thu, Jul 14, 2016 at 1:35 PM, Pierre Smits 
>> wrote:
>>
>> > Hi Sharan,
>> >
>> > I guess all accepted proposals can now be transformed into JIRA issues,
>> for
>> > follow-up and tracking purposes.
>> >
>> > Also, with respect to the failing components) I suggest that we postpone
>> > the ultimate decision of activation/deactivation until the moment of
>> > cutting a release. Until then, contributors can work on those issues,
>> and
>> > if they can't resolve the issues by the time the decision needs to be
>> taken
>> > we know what to deactivate precisely.
>> >
>>
>> I suggest the opposite :-) if we disable them sooner than later
>> contributors will be more aware of the work required and there be less
>> surprises when they will be excluded from releases; disabling them sooner
>> would probably increase the chances of fixing them because it will catch
>> attention; if otherwise no one will care about them being disabled it
>> could
>> be an indicator that there is not enough interest.
>>
>> Jacopo
>>
>>
>>
>> > Best regards,
>> >
>> >
>> > Pierre Smits
>> >
>> > ORRTIZ.COM 
>> > OFBiz based solutions & services
>> >
>> > OFBiz Extensions Marketplace
>> > http://oem.ofbizci.net/oci-2/
>> >
>> > On Thu, Jul 14, 2016 at 1:14 PM, Sharan Foga 
>> > wrote:
>> >
>> > > Hi Everyone
>> > >
>> > > Thanks responding to these 3 proposals. Based on your feedback and
>> > > comments we can move ahead with 2 of these for the changes to the
>> > directory
>> > > structure for java and the renaming of specialpurpose to 'plugins'
>> > >
>> > > For the third, Pierre highlighted that he was against this proposal
>> so we
>> > > won't be deactivating the all the specialpurpose components by
>> default.
>> > >
>> > > However as mentioned previously, we are having library migration
>> problems
>> > > with some of the components so we can only activate the ones that
>> don't
>> > > have any issues; the others will not be activated and will need
>> > additional
>> > > work to manage the changeover to remote libraries and the resolution
>> of
>> > any
>> > > startup conflicts.
>> > >
>> > > (Just for information the components with issues are BIRT, Ebaystore,
>> > > ldap, POS and cmssite.)
>> > >
>> > > We are also looking for help with these migrations so if you would
>> like
>> > to
>> > > help out fixing the issues with these specialpurpose components then
>> > please
>> > > let me know.
>> > >
>> > > Thanks
>> > > Sharan
>> > >
>> > > On 2016-07-11 17:56 (+0200), Sharan-F  wrote:
>> > > > Hi Everyone
>> > > >
>> > > > Another update on the task list for moving forward with Gradle and
>> the
>> > > > Trunk. We would also like to get community feedback and comments on
>> > each
>> > > of
>> > > > the following 3 proposals:
>> > > >
>> > > > Task 1 “Replace all the current jars in OFBiz with appropriate
>> remote
>> > > > libraries from a download repository
>> > > >
>> > >
>> >
>> --
>> > > > 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
>> > > > will continue to remove the remaining files. As we are working
>> through,
>> > > we
>> > > > are finding library migration issues with some of the specialpurpose
>> > > > components so would like *to propose to deactivate all
>> specialpurpose
>> > > > components by default.*
>> > > >
>> > > >
>> > > > Task 4. “ Move all java source files
>> to\u2002$component/src/main/java
>> > and
>> > > > introduce all unit tests in\u2002\u2002$component/src/test/java”
>> > > >
>> > >
>> >
>> -
>> > > > Another area we need to progress is the re-design and changing of
>> the
>> > > > directory structure so that we can separate the Java files between
>> main
>> > > and
>> > > > test. This will help us

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

I can live with that.

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Thu, Jul 14, 2016 at 4:30 PM, Jacopo Cappellato <
jacopo.cappell...@hotwaxsystems.com> wrote:

> On Thu, Jul 14, 2016 at 1:35 PM, Pierre Smits 
> wrote:
>
> > Hi Sharan,
> >
> > I guess all accepted proposals can now be transformed into JIRA issues,
> for
> > follow-up and tracking purposes.
> >
> > Also, with respect to the failing components) I suggest that we postpone
> > the ultimate decision of activation/deactivation until the moment of
> > cutting a release. Until then, contributors can work on those issues, and
> > if they can't resolve the issues by the time the decision needs to be
> taken
> > we know what to deactivate precisely.
> >
>
> I suggest the opposite :-) if we disable them sooner than later
> contributors will be more aware of the work required and there be less
> surprises when they will be excluded from releases; disabling them sooner
> would probably increase the chances of fixing them because it will catch
> attention; if otherwise no one will care about them being disabled it could
> be an indicator that there is not enough interest.
>
> Jacopo
>
>
>
> > Best regards,
> >
> >
> > Pierre Smits
> >
> > ORRTIZ.COM 
> > OFBiz based solutions & services
> >
> > OFBiz Extensions Marketplace
> > http://oem.ofbizci.net/oci-2/
> >
> > On Thu, Jul 14, 2016 at 1:14 PM, Sharan Foga 
> > wrote:
> >
> > > Hi Everyone
> > >
> > > Thanks responding to these 3 proposals. Based on your feedback and
> > > comments we can move ahead with 2 of these for the changes to the
> > directory
> > > structure for java and the renaming of specialpurpose to 'plugins'
> > >
> > > For the third, Pierre highlighted that he was against this proposal so
> we
> > > won't be deactivating the all the specialpurpose components by default.
> > >
> > > However as mentioned previously, we are having library migration
> problems
> > > with some of the components so we can only activate the ones that don't
> > > have any issues; the others will not be activated and will need
> > additional
> > > work to manage the changeover to remote libraries and the resolution of
> > any
> > > startup conflicts.
> > >
> > > (Just for information the components with issues are BIRT, Ebaystore,
> > > ldap, POS and cmssite.)
> > >
> > > We are also looking for help with these migrations so if you would like
> > to
> > > help out fixing the issues with these specialpurpose components then
> > please
> > > let me know.
> > >
> > > Thanks
> > > Sharan
> > >
> > > On 2016-07-11 17:56 (+0200), Sharan-F  wrote:
> > > > Hi Everyone
> > > >
> > > > Another update on the task list for moving forward with Gradle and
> the
> > > > Trunk. We would also like to get community feedback and comments on
> > each
> > > of
> > > > the following 3 proposals:
> > > >
> > > > Task 1 “Replace all the current jars in OFBiz with appropriate remote
> > > > libraries from a download repository
> > > >
> > >
> >
> --
> > > > 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
> > > > will continue to remove the remaining files. As we are working
> through,
> > > we
> > > > are finding library migration issues with some of the specialpurpose
> > > > components so would like *to propose to deactivate all specialpurpose
> > > > components by default.*
> > > >
> > > >
> > > > Task 4. “ Move all java source files to\u2002$component/src/main/java
> > and
> > > > introduce all unit tests in\u2002\u2002$component/src/test/java”
> > > >
> > >
> >
> -
> > > > Another area we need to progress is the re-design and changing of the
> > > > directory 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

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

2016-07-14 Thread Jacopo Cappellato

On Thu, Jul 14, 2016 at 1:35 PM, Pierre Smits 
wrote:

> Hi Sharan,
>
> I guess all accepted proposals can now be transformed into JIRA issues, for
> follow-up and tracking purposes.
>
> Also, with respect to the failing components) I suggest that we postpone
> the ultimate decision of activation/deactivation until the moment of
> cutting a release. Until then, contributors can work on those issues, and
> if they can't resolve the issues by the time the decision needs to be taken
> we know what to deactivate precisely.
>

I suggest the opposite :-) if we disable them sooner than later
contributors will be more aware of the work required and there be less
surprises when they will be excluded from releases; disabling them sooner
would probably increase the chances of fixing them because it will catch
attention; if otherwise no one will care about them being disabled it could
be an indicator that there is not enough interest.

Jacopo



> Best regards,
>
>
> Pierre Smits
>
> ORRTIZ.COM 
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Thu, Jul 14, 2016 at 1:14 PM, Sharan Foga 
> wrote:
>
> > Hi Everyone
> >
> > Thanks responding to these 3 proposals. Based on your feedback and
> > comments we can move ahead with 2 of these for the changes to the
> directory
> > structure for java and the renaming of specialpurpose to 'plugins'
> >
> > For the third, Pierre highlighted that he was against this proposal so we
> > won't be deactivating the all the specialpurpose components by default.
> >
> > However as mentioned previously, we are having library migration problems
> > with some of the components so we can only activate the ones that don't
> > have any issues; the others will not be activated and will need
> additional
> > work to manage the changeover to remote libraries and the resolution of
> any
> > startup conflicts.
> >
> > (Just for information the components with issues are BIRT, Ebaystore,
> > ldap, POS and cmssite.)
> >
> > We are also looking for help with these migrations so if you would like
> to
> > help out fixing the issues with these specialpurpose components then
> please
> > let me know.
> >
> > Thanks
> > Sharan
> >
> > On 2016-07-11 17:56 (+0200), Sharan-F  wrote:
> > > Hi Everyone
> > >
> > > Another update on the task list for moving forward with Gradle and the
> > > Trunk. We would also like to get community feedback and comments on
> each
> > of
> > > the following 3 proposals:
> > >
> > > Task 1 “Replace all the current jars in OFBiz with appropriate remote
> > > libraries from a download repository
> > >
> >
> --
> > > 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
> > > will continue to remove the remaining files. As we are working through,
> > we
> > > are finding library migration issues with some of the specialpurpose
> > > components so would like *to propose to deactivate all specialpurpose
> > > components by default.*
> > >
> > >
> > > Task 4. “ Move all java source files to\u2002$component/src/main/java
> and
> > > introduce all unit tests in\u2002\u2002$component/src/test/java”
> > >
> >
> -
> > > Another area we need to progress is the re-design and changing of the
> > > directory 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.
> > >
> >
>

[jira] [Commented] (OFBIZ-6870) Mismatch between time entry field display and persisted data


[ 
https://issues.apache.org/jira/browse/OFBIZ-6870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376892#comment-15376892
 ] 

Pierre Smits commented on OFBIZ-6870:
-

I can go with that.

[~rahul.kushwah] Can you provide a patch that takes the suggestion made by 
[~jacques.le.roux] into account? If you can, then we have something to assess 
the impact.

> Mismatch between time entry field display and persisted data
> 
>
> Key: OFBIZ-6870
> URL: https://issues.apache.org/jira/browse/OFBIZ-6870
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/projectmgr
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Pierre Smits
>
> When a new time sheet is created, the fields for entering the time spent 
> starts on Monday and end on Sunday, however the date range start on Sunday 
> and ends on Saturday. And the latter range is used to persist the data. 
> So when a time entry is done in the field for Monday it is persisted on the 
> Sunday.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7779) Update wiki Eclipse pages regarding Gradle


[ 
https://issues.apache.org/jira/browse/OFBIZ-7779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376885#comment-15376885
 ] 

Taher Alkhateeb commented on OFBIZ-7779:


What I thought would be a quick fix took me a while and I uncovered a lot of 
problems in the build script.

Anyway, now it is working perfectly on both Windows and Linux after the commit 
r1752658 with all tests passing.

Cheers :)

> Update wiki Eclipse pages regarding Gradle
> --
>
> Key: OFBIZ-7779
> URL: https://issues.apache.org/jira/browse/OFBIZ-7779
> Project: OFBiz
>  Issue Type: Task
>  Components: Confluence
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
> Attachments: Image 007.png, OFBIZ-7779.patch, OFBIZ-7779.patch, 
> compile.error, neon.error
>
>
> I wanted to update the 2 wiki Eclipse pages regarding Gradle. But so far got 
> some issues in my environment (still Windows 7).
> I use both Eclipse Luna and Mars (Mars at 98%).  Luna does not support Gradle.
> First I must say my Mars instance works perfectly, but for few months I'm 
> unable to update. I did not try yet to create another Mars instance because I 
> guess it will anyway screws its update mechanism later :/
> Mars comes with the embedded ["Gradle Buildship" 
> plugin|https://gradle.org/eclipse/], I have the 1.0.5 version from 
> 2015-09-22. I found this tuto 
> http://www.vogella.com/tutorials/EclipseGradle/article.html (with a 6/7 
> clone/redundant section).
> Few remarks: I see no Gradle context menu entrie, maybe due to my unability 
> to update Mars, so I'm unable to "add Gradle support to existing Eclipse 
> project ". So I created a Gradle "trunk" side project following , but, though 
> all work well in command line, in Eclipse building with Gradle does not work. 
> I always get (see compile.error)
> Of course I tried (4th) to install Eclipse Neon, to no avail, so far the best 
> I got (at least I eventually got something) is in neon.error
> I'll continue later...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-5838) Have a descriptive WEB page per application


[ 
https://issues.apache.org/jira/browse/OFBIZ-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376811#comment-15376811
 ] 

Sharan Foga edited comment on OFBIZ-5838 at 7/14/16 12:20 PM:
--

The draft website has summaries of the applications but will not dedicate a 
complete page per application. A possibility could be to do a some linking 
between the website and the wiki so that people can get more detail if 
necessary.


was (Author: sharan ):
The draft website has summaries of the applications but will not dedicate a 
complete page per application. A possibility could be to do a some linking 
between the two so that people can get more detail if necessary.

> Have a descriptive WEB page per application
> ---
>
> Key: OFBIZ-5838
> URL: https://issues.apache.org/jira/browse/OFBIZ-5838
> Project: OFBiz
>  Issue Type: Improvement
>  Components: site
>Reporter: Pierre Smits
>
> Each application should have a page describing (briefly) what it is about in 
> the website/wiki



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5838) Have a descriptive WEB page per application


[ 
https://issues.apache.org/jira/browse/OFBIZ-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376811#comment-15376811
 ] 

Sharan Foga commented on OFBIZ-5838:


The draft website has summaries of the applications but will not dedicate a 
complete page per application. A possibility could be to do a some linking 
between the two so that people can get more detail if necessary.

> Have a descriptive WEB page per application
> ---
>
> Key: OFBIZ-5838
> URL: https://issues.apache.org/jira/browse/OFBIZ-5838
> Project: OFBiz
>  Issue Type: Improvement
>  Components: site
>Reporter: Pierre Smits
>
> Each application should have a page describing (briefly) what it is about in 
> the website/wiki



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-5838) Have a descriptive WEB page per application


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharan Foga updated OFBIZ-5838:
---
Assignee: (was: Sharan Foga)

> Have a descriptive WEB page per application
> ---
>
> Key: OFBIZ-5838
> URL: https://issues.apache.org/jira/browse/OFBIZ-5838
> Project: OFBiz
>  Issue Type: Improvement
>  Components: site
>Reporter: Pierre Smits
>
> Each application should have a page describing (briefly) what it is about in 
> the website/wiki



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-5836) Integrate web analytics into the website


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharan Foga updated OFBIZ-5836:
---
Priority: Minor  (was: Major)

> Integrate web analytics into the website
> 
>
> Key: OFBIZ-5836
> URL: https://issues.apache.org/jira/browse/OFBIZ-5836
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: site
>Reporter: Pierre Smits
>Assignee: Sharan Foga
>Priority: Minor
>
> Have some kind of web analytics integrated in the website to be able to some 
> kind analysis on visits, traffic etc.
> Refereces:
> * http://en.wikipedia.org/wiki/Web_analytics
> * http://en.wikipedia.org/wiki/List_of_web_analytics_software



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-5836) Integrate web analytics into the website


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharan Foga updated OFBIZ-5836:
---
Issue Type: Sub-task  (was: Improvement)
Parent: OFBIZ-7792

> Integrate web analytics into the website
> 
>
> Key: OFBIZ-5836
> URL: https://issues.apache.org/jira/browse/OFBIZ-5836
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: site
>Reporter: Pierre Smits
>Assignee: Sharan Foga
>
> Have some kind of web analytics integrated in the website to be able to some 
> kind analysis on visits, traffic etc.
> Refereces:
> * http://en.wikipedia.org/wiki/Web_analytics
> * http://en.wikipedia.org/wiki/List_of_web_analytics_software



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7792) Update OFBiz Website

Sharan Foga created OFBIZ-7792:
--

 Summary: Update OFBiz Website
 Key: OFBIZ-7792
 URL: https://issues.apache.org/jira/browse/OFBIZ-7792
 Project: OFBiz
  Issue Type: Improvement
Reporter: Sharan Foga
Priority: Minor


The current OFBiz website needs to be updated. This JIRA covers updates 
required to the complete site.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7791) Rename specialpurpose to plugins

Sharan Foga created OFBIZ-7791:
--

 Summary: Rename specialpurpose to plugins 
 Key: OFBIZ-7791
 URL: https://issues.apache.org/jira/browse/OFBIZ-7791
 Project: OFBiz
  Issue Type: Improvement
Reporter: Sharan Foga
Priority: Minor


Rename specialpurpose to plugins

Decision thread link 
https://lists.apache.org/thread.html/258dbd86cff87bc9294f4507dec60655e386c7b0eb5a8edb406bcfd4@%3Cdev.ofbiz.apache.org%3E

This JIRA covers changes to all the required components



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7790) Change the Java Directory Structure to Main and Test

Sharan Foga created OFBIZ-7790:
--

 Summary: Change the Java Directory Structure to Main and Test
 Key: OFBIZ-7790
 URL: https://issues.apache.org/jira/browse/OFBIZ-7790
 Project: OFBiz
  Issue Type: Improvement
Reporter: Sharan Foga


Change of the directory 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 wew directory structure will be as follows:

   componentname/src/main/java
   componentname/src/test/java*

This JIRA will we used for the migration of all compoenents



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Hi Sharan,

I guess all accepted proposals can now be transformed into JIRA issues, for
follow-up and tracking purposes.

Also, with respect to the failing components) I suggest that we postpone
the ultimate decision of activation/deactivation until the moment of
cutting a release. Until then, contributors can work on those issues, and
if they can't resolve the issues by the time the decision needs to be taken
we know what to deactivate precisely.

Best regards,


Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Thu, Jul 14, 2016 at 1:14 PM, Sharan Foga  wrote:

> Hi Everyone
>
> Thanks responding to these 3 proposals. Based on your feedback and
> comments we can move ahead with 2 of these for the changes to the directory
> structure for java and the renaming of specialpurpose to 'plugins'
>
> For the third, Pierre highlighted that he was against this proposal so we
> won't be deactivating the all the specialpurpose components by default.
>
> However as mentioned previously, we are having library migration problems
> with some of the components so we can only activate the ones that don't
> have any issues; the others will not be activated and will need additional
> work to manage the changeover to remote libraries and the resolution of any
> startup conflicts.
>
> (Just for information the components with issues are BIRT, Ebaystore,
> ldap, POS and cmssite.)
>
> We are also looking for help with these migrations so if you would like to
> help out fixing the issues with these specialpurpose components then please
> let me know.
>
> Thanks
> Sharan
>
> On 2016-07-11 17:56 (+0200), Sharan-F  wrote:
> > Hi Everyone
> >
> > Another update on the task list for moving forward with Gradle and the
> > Trunk. We would also like to get community feedback and comments on each
> of
> > the following 3 proposals:
> >
> > Task 1 “Replace all the current jars in OFBiz with appropriate remote
> > libraries from a download repository
> >
> --
> > 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
> > will continue to remove the remaining files. As we are working through,
> we
> > are finding library migration issues with some of the specialpurpose
> > components so would like *to propose to deactivate all specialpurpose
> > components by default.*
> >
> >
> > Task 4. “ Move all java source files to\u2002$component/src/main/java and
> > introduce all unit tests in\u2002\u2002$component/src/test/java”
> >
> -
> > Another area we need to progress is the re-design and changing of the
> > directory 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

2016-07-14 Thread Sharan Foga

Hi Everyone

Thanks responding to these 3 proposals. Based on your feedback and comments we 
can move ahead with 2 of these for the changes to the directory structure for 
java and the renaming of specialpurpose to 'plugins'

For the third, Pierre highlighted that he was against this proposal so we won't 
be deactivating the all the specialpurpose components by default. 

However as mentioned previously, we are having library migration problems with 
some of the components so we can only activate the ones that don't have any 
issues; the others will not be activated and will need additional work to 
manage the changeover to remote libraries and the resolution of any startup 
conflicts. 

(Just for information the components with issues are BIRT, Ebaystore, ldap, POS 
and cmssite.)

We are also looking for help with these migrations so if you would like to help 
out fixing the issues with these specialpurpose components then please let me 
know.

Thanks
Sharan

On 2016-07-11 17:56 (+0200), Sharan-F  wrote: 
> Hi Everyone
> 
> Another update on the task list for moving forward with Gradle and the
> Trunk. We would also like to get community feedback and comments on each of
> the following 3 proposals:
> 
> Task 1 âReplace all the current jars in OFBiz with appropriate remote
> libraries from a download repository
> --
> 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
> will continue to remove the remaining files. As we are working through, we
> are finding library migration issues with some of the specialpurpose
> components so would like *to propose to deactivate all specialpurpose
> components by default.*
> 
> 
> Task 4. â Move all java source files to\u2002$component/src/main/java and
> introduce all unit tests in\u2002\u2002$component/src/test/javaâ
> -
> Another area we need to progress is the re-design and changing of the
> directory 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.
>

[jira] [Commented] (OFBIZ-6711) Have configuration options regarding widgets


[ 
https://issues.apache.org/jira/browse/OFBIZ-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376770#comment-15376770
 ] 

Pierre Smits commented on OFBIZ-6711:
-

Thanks, [~jacques.le.roux], but you don't have to take on everything yourself. 
I was also soliciting the help of others.

> Have configuration options regarding widgets
> 
>
> Key: OFBIZ-6711
> URL: https://issues.apache.org/jira/browse/OFBIZ-6711
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL APPLICATIONS, ALL COMPONENTS
>Reporter: Pierre Smits
> Attachments: OFBIZ-6711-widget.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-7619) Add "changeByUserLoginId" field for BudgetStatus

2016-07-14 Thread Nicolas Malin (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Malin closed OFBIZ-7619.

   Resolution: Implemented
Fix Version/s: Upcoming Branch

Ok work for me, commited on trunk at revision 1752602

Thanks Nameet

> Add "changeByUserLoginId" field for BudgetStatus
> 
>
> Key: OFBIZ-7619
> URL: https://issues.apache.org/jira/browse/OFBIZ-7619
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Assignee: Nicolas Malin
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7619.patch, OFBIZ-7619.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-7619) Add "changeByUserLoginId" field for BudgetStatus

2016-07-14 Thread Nicolas Malin (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Malin reassigned OFBIZ-7619:


Assignee: Nicolas Malin

> Add "changeByUserLoginId" field for BudgetStatus
> 
>
> Key: OFBIZ-7619
> URL: https://issues.apache.org/jira/browse/OFBIZ-7619
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Assignee: Nicolas Malin
> Attachments: OFBIZ-7619.patch, OFBIZ-7619.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7781) Have a configurable solution with respect to the default fields of all entities

2016-07-14 Thread Nicolas Malin (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376571#comment-15376571
 ] 

Nicolas Malin commented on OFBIZ-7781:
--

+1, the advantage with track user on EntityStatus is the direct benefit to 
follow activity on sensible process. A good compromise between useful and 
resource.

Track all entities Oo sorry I can't believe it. A better way would be improve 
entity-audit-log engine, to enable it when you want at the fly and have a 
screen to analyse.

> Have a configurable solution with respect to the default fields of all 
> entities
> ---
>
> Key: OFBIZ-7781
> URL: https://issues.apache.org/jira/browse/OFBIZ-7781
> Project: OFBiz
>  Issue Type: Improvement
>  Components: datamodel
>Affects Versions: Trunk
>Reporter: Pierre Smits
>
> This issue follows up on comments posted in the  OFBIZ-7622 sub-task.
> Currently the fields to be added to all entities are defined in 
> ModelEntity.java. This is a limited list consisting of:
> * public static final String STAMP_FIELD = "lastUpdatedStamp";
> * public static final String STAMP_TX_FIELD = "lastUpdatedTxStamp";
> * public static final String CREATE_STAMP_FIELD = "createdStamp";
> * public static final String CREATE_STAMP_TX_FIELD = "createdTxStamp";
> After the implemented code change of the sub task mentioned above, a new 
> discussion evolved through postings of comments on the subject of how to get 
> more flexibility in.
> This issue is a starting point and potentially a place holder for sub 
> subtasks to get to a more flexible solution.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7754) The big problem when load seed.


[ 
https://issues.apache.org/jira/browse/OFBIZ-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376540#comment-15376540
 ] 

Pierre Smits commented on OFBIZ-7754:
-

I don't see  problems in changing the reader-name from *seed* to 
*seed-initial*, but I don't believe we should treat that as an exception for 
only this scenario. I don't mind if it would be applied to 
*SystemPropertyData.xml files in all components. If that can achieve consensus, 
I will work on providing one or more patch files.

> The big problem when load seed.
> ---
>
> Key: OFBIZ-7754
> URL: https://issues.apache.org/jira/browse/OFBIZ-7754
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Kongrath Suankaewmanee
>Assignee: Jacques Le Roux
> Attachments: OFBIZ-7754.patch
>
>
> Hi All,
> Regarding, [OFBIZ-7112|https://issues.apache.org/jira/browse/OFBIZ-7112]
> That's good for who start on use the ofbiz with initial setup, but not for 
> the site that already online and has to update the OFBiz core. Because when 
> has update OFBiz core they will use command load-seed for update.
> The problem is if we use load-seed mean the configuration data that's already 
> exists will be replaced by the data from this file,
> *CommonSystemPropertyData.xml*
> So, for my suggestion should change the reader from *seed* to *seed-initial*  
> or remove systemPropertyValue from the data file.
> Thank you,
> Kongrath



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7773) createTenant tasks does not ask for parameters


[ 
https://issues.apache.org/jira/browse/OFBIZ-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376527#comment-15376527
 ] 

Pierre Smits commented on OFBIZ-7773:
-

Like I said: I am done with the discussion of 'throwing the old shoes before we 
have the new shiny one'. 

Untill you and [~jacques.le.roux] have figured out how to do that and deliver 
the ultimate solution, an acceptable solution could be to have this in until 
then. But it seems you're not open to that suggestion as a compromise.

> createTenant tasks does not ask for parameters
> --
>
> Key: OFBIZ-7773
> URL: https://issues.apache.org/jira/browse/OFBIZ-7773
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Blocker
> Attachments: OFBIZ-7773-ofbiz.patch
>
>
> When executing the gradle createTenant tasks, the following error is thrown:
> {code}
> FAILURE: Build failed with an exception.
> * Where:
> Build file '/Users/pierre/dev/ofbiz/ofbiz-gradle/build.gradle' line: 328
> * What went wrong:
> Execution failed for task ':prepareAndValidateTenantArguments'.
> > Project property tenantId is missing
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output.
> BUILD FAILED
> {code}
> The function/process is missing the guided-through approach that ./ant 
> create-tenant has.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7754) The big problem when load seed.

2016-07-14 Thread Hans Bakker (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376506#comment-15376506
 ] 

Hans Bakker commented on OFBIZ-7754:


Can only repeat:
simply remove the framework/common/data/CommonSystemPropertyData.xml file from 
ofbiz-component is my suggestion.
then the file general.properties is active again.

> The big problem when load seed.
> ---
>
> Key: OFBIZ-7754
> URL: https://issues.apache.org/jira/browse/OFBIZ-7754
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Kongrath Suankaewmanee
>Assignee: Jacques Le Roux
> Attachments: OFBIZ-7754.patch
>
>
> Hi All,
> Regarding, [OFBIZ-7112|https://issues.apache.org/jira/browse/OFBIZ-7112]
> That's good for who start on use the ofbiz with initial setup, but not for 
> the site that already online and has to update the OFBiz core. Because when 
> has update OFBiz core they will use command load-seed for update.
> The problem is if we use load-seed mean the configuration data that's already 
> exists will be replaced by the data from this file,
> *CommonSystemPropertyData.xml*
> So, for my suggestion should change the reader from *seed* to *seed-initial*  
> or remove systemPropertyValue from the data file.
> Thank you,
> Kongrath



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7773) createTenant tasks does not ask for parameters


[ 
https://issues.apache.org/jira/browse/OFBIZ-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376505#comment-15376505
 ] 

Taher Alkhateeb commented on OFBIZ-7773:


Hi Pierre,

Sorry maybe I was not very clear. Perhaps the word I should have used is "more 
people". I did not hear from anyone else this request so I thought to at least 
delay the effort until we resolve the big problems (completing remote 
libraries, fixing the org.apache.ofbiz, fixing the directory structure)

I would also happily help Jacques where I can in his above initiatives (GUI or 
groovysh). Both solutions seem more appropriate than shell scripts. If you 
would like to take an initiative there I would also gladly help you out if you 
would like that.

> createTenant tasks does not ask for parameters
> --
>
> Key: OFBIZ-7773
> URL: https://issues.apache.org/jira/browse/OFBIZ-7773
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Blocker
> Attachments: OFBIZ-7773-ofbiz.patch
>
>
> When executing the gradle createTenant tasks, the following error is thrown:
> {code}
> FAILURE: Build failed with an exception.
> * Where:
> Build file '/Users/pierre/dev/ofbiz/ofbiz-gradle/build.gradle' line: 328
> * What went wrong:
> Execution failed for task ':prepareAndValidateTenantArguments'.
> > Project property tenantId is missing
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output.
> BUILD FAILED
> {code}
> The function/process is missing the guided-through approach that ./ant 
> create-tenant has.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7789) ReserveStoreInventory with insufficient inventory

2016-07-14 Thread Mirko Vogelsmeier (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mirko Vogelsmeier updated OFBIZ-7789:
-
Attachment: OFBIZ-7789.patch

I will provide a patch although I am not sure of the side effects to e. g. 
requirement processes.

> ReserveStoreInventory with insufficient inventory
> -
>
> Key: OFBIZ-7789
> URL: https://issues.apache.org/jira/browse/OFBIZ-7789
> Project: OFBiz
>  Issue Type: Bug
>Affects Versions: Release Branch 13.07, Trunk
>Reporter: Mirko Vogelsmeier
> Fix For: Trunk
>
> Attachments: OFBIZ-7789.patch
>
>
> When trying to reserve inventory for an item that does not have sufficient 
> amount of inventory ( ProductStoreServices#reserveStoreInventory ) no error 
> is thrown. This results in a successfully processed service.
> Following problem occured to us:
> We have a unique product (qoh 1) that is in the current order.
> Using the appendOrderItem on the exact product, does trigger 
> updateCartForUpdate which removes all reservations followed by 
> saveUpdatedCartToOrder that does store all orderItems to the order. Since no 
> error is being thrown due to the insufficient inventory, the product is added 
> to the order twice, although there is not enough inventory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7789) ReserveStoreInventory with insufficient inventory

2016-07-14 Thread Mirko Vogelsmeier (JIRA)

Mirko Vogelsmeier created OFBIZ-7789:


 Summary: ReserveStoreInventory with insufficient inventory
 Key: OFBIZ-7789
 URL: https://issues.apache.org/jira/browse/OFBIZ-7789
 Project: OFBiz
  Issue Type: Bug
Affects Versions: Trunk, Release Branch 13.07
Reporter: Mirko Vogelsmeier
 Fix For: Trunk


When trying to reserve inventory for an item that does not have sufficient 
amount of inventory ( ProductStoreServices#reserveStoreInventory ) no error is 
thrown. This results in a successfully processed service.

Following problem occured to us:
We have a unique product (qoh 1) that is in the current order.
Using the appendOrderItem on the exact product, does trigger 
updateCartForUpdate which removes all reservations followed by 
saveUpdatedCartToOrder that does store all orderItems to the order. Since no 
error is being thrown due to the insufficient inventory, the product is added 
to the order twice, although there is not enough inventory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7773) createTenant tasks does not ask for parameters


[ 
https://issues.apache.org/jira/browse/OFBIZ-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376492#comment-15376492
 ] 

Pierre Smits commented on OFBIZ-7773:
-

Well. He said it here: http://ofbiz.markmail.org/message/6m7ctc67bruxizc3

But I might have misunderstood him. He said 'If other people want to add 
interactive tasks I will happily volunteer to
implement them', which I took as *other people than him*.

But maybe he meant *other people than Pierre Smits*.

> createTenant tasks does not ask for parameters
> --
>
> Key: OFBIZ-7773
> URL: https://issues.apache.org/jira/browse/OFBIZ-7773
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Blocker
> Attachments: OFBIZ-7773-ofbiz.patch
>
>
> When executing the gradle createTenant tasks, the following error is thrown:
> {code}
> FAILURE: Build failed with an exception.
> * Where:
> Build file '/Users/pierre/dev/ofbiz/ofbiz-gradle/build.gradle' line: 328
> * What went wrong:
> Execution failed for task ':prepareAndValidateTenantArguments'.
> > Project property tenantId is missing
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output.
> BUILD FAILED
> {code}
> The function/process is missing the guided-through approach that ./ant 
> create-tenant has.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7754) The big problem when load seed.


[ 
https://issues.apache.org/jira/browse/OFBIZ-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376489#comment-15376489
 ] 

Jacques Le Roux commented on OFBIZ-7754:


That's my question to Hans, maybe it was not clear, thanks to repeat it.

> The big problem when load seed.
> ---
>
> Key: OFBIZ-7754
> URL: https://issues.apache.org/jira/browse/OFBIZ-7754
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Kongrath Suankaewmanee
>Assignee: Jacques Le Roux
> Attachments: OFBIZ-7754.patch
>
>
> Hi All,
> Regarding, [OFBIZ-7112|https://issues.apache.org/jira/browse/OFBIZ-7112]
> That's good for who start on use the ofbiz with initial setup, but not for 
> the site that already online and has to update the OFBiz core. Because when 
> has update OFBiz core they will use command load-seed for update.
> The problem is if we use load-seed mean the configuration data that's already 
> exists will be replaced by the data from this file,
> *CommonSystemPropertyData.xml*
> So, for my suggestion should change the reader from *seed* to *seed-initial*  
> or remove systemPropertyValue from the data file.
> Thank you,
> Kongrath



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7773) createTenant tasks does not ask for parameters


[ 
https://issues.apache.org/jira/browse/OFBIZ-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376484#comment-15376484
 ] 

Jacques Le Roux commented on OFBIZ-7773:


Bq. Luckily you don't have to. Taher said he would.
I doubt he will (at least in a visible horizon), where did he say that?


> createTenant tasks does not ask for parameters
> --
>
> Key: OFBIZ-7773
> URL: https://issues.apache.org/jira/browse/OFBIZ-7773
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Blocker
> Attachments: OFBIZ-7773-ofbiz.patch
>
>
> When executing the gradle createTenant tasks, the following error is thrown:
> {code}
> FAILURE: Build failed with an exception.
> * Where:
> Build file '/Users/pierre/dev/ofbiz/ofbiz-gradle/build.gradle' line: 328
> * What went wrong:
> Execution failed for task ':prepareAndValidateTenantArguments'.
> > Project property tenantId is missing
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output.
> BUILD FAILED
> {code}
> The function/process is missing the guided-through approach that ./ant 
> create-tenant has.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6448) Have configuration options regarding freemarkerImports.properties


[ 
https://issues.apache.org/jira/browse/OFBIZ-6448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376475#comment-15376475
 ] 

Jacques Le Roux commented on OFBIZ-6448:


Pierre, before continuing on such tasks I wait Hans's feedback on OFBIZ-7754. 
It will help clarify why he does not want to have that in his system...

> Have configuration options regarding freemarkerImports.properties
> -
>
> Key: OFBIZ-6448
> URL: https://issues.apache.org/jira/browse/OFBIZ-6448
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
> Attachments: OFBIZ-6448-FreeMarkerWorker.java.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-6946) Remove ftl dependency in order on ecommerce


[ 
https://issues.apache.org/jira/browse/OFBIZ-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15203232#comment-15203232
 ] 

Jacques Le Roux edited comment on OFBIZ-6946 at 7/14/16 7:17 AM:
-

Why to create a file in order if it's unused? If the community is OK I will get 
rif of the commented out line, et voilà. Or maybe the ideas was to keep a link? 
But this is pre-Apache era...


was (Author: jacques.le.roux):
Why to create a file in order if it's unused? If the community is OK I will get 
rif of the commented out line, et voilà. Or maybe the ideas was to keep a link? 
But this pre-Aapche era...

> Remove ftl dependency in order on ecommerce
> ---
>
> Key: OFBIZ-6946
> URL: https://issues.apache.org/jira/browse/OFBIZ-6946
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Minor
> Attachments: OFBIZ-6946-order-template-location.patch
>
>
> Currently there are dependencies in the order component on the ecommerce 
> component.
> Order management should work without the ecommerce component.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6711) Have configuration options regarding widgets


[ 
https://issues.apache.org/jira/browse/OFBIZ-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376463#comment-15376463
 ] 

Jacques Le Roux commented on OFBIZ-6711:


Just checked the patch still applies, other more urgent tasks pending...

> Have configuration options regarding widgets
> 
>
> Key: OFBIZ-6711
> URL: https://issues.apache.org/jira/browse/OFBIZ-6711
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL APPLICATIONS, ALL COMPONENTS
>Reporter: Pierre Smits
> Attachments: OFBIZ-6711-widget.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7754) The big problem when load seed.


[ 
https://issues.apache.org/jira/browse/OFBIZ-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376461#comment-15376461
 ] 

Pierre Smits commented on OFBIZ-7754:
-

Maybe it is an acceptable solution if Hans would to change the reader-name for 
loading CommonSystemPropertyData.xml in the ofbiz-component.xml file within his 
setup from: *seed* to *seed-initial*

See:
{code}

{code}

> The big problem when load seed.
> ---
>
> Key: OFBIZ-7754
> URL: https://issues.apache.org/jira/browse/OFBIZ-7754
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Kongrath Suankaewmanee
>Assignee: Jacques Le Roux
> Attachments: OFBIZ-7754.patch
>
>
> Hi All,
> Regarding, [OFBIZ-7112|https://issues.apache.org/jira/browse/OFBIZ-7112]
> That's good for who start on use the ofbiz with initial setup, but not for 
> the site that already online and has to update the OFBiz core. Because when 
> has update OFBiz core they will use command load-seed for update.
> The problem is if we use load-seed mean the configuration data that's already 
> exists will be replaced by the data from this file,
> *CommonSystemPropertyData.xml*
> So, for my suggestion should change the reader from *seed* to *seed-initial*  
> or remove systemPropertyValue from the data file.
> Thank you,
> Kongrath



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6125) Move SeoConfig.xml to e-commerce


[ 
https://issues.apache.org/jira/browse/OFBIZ-6125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376453#comment-15376453
 ] 

Pierre Smits commented on OFBIZ-6125:
-

Bump. Can we have this improvement in before the code grows stale?

> Move SeoConfig.xml to e-commerce
> 
>
> Key: OFBIZ-6125
> URL: https://issues.apache.org/jira/browse/OFBIZ-6125
> Project: OFBiz
>  Issue Type: Improvement
>  Components: product, specialpurpose/ecommerce
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Minor
>  Labels: seo
> Attachments: OFBIZ-6125-SeoConfigMove.patch
>
>
> Currently the configuration file (SeoConfig.xml) is incorporated in the 
> product component. However this is more related to how the e-commerce 
> operates than to the functions in the backend catalog and warehousing 
> applications. 
> The file should therefore be moved to its appropriate place.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6224) Rename search.properties in special purpose/lucene to lucene.properties


[ 
https://issues.apache.org/jira/browse/OFBIZ-6224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376451#comment-15376451
 ] 

Pierre Smits commented on OFBIZ-6224:
-

Bump. Can we implement this enhancement before the code grows stale?

> Rename search.properties in special purpose/lucene to lucene.properties
> ---
>
> Key: OFBIZ-6224
> URL: https://issues.apache.org/jira/browse/OFBIZ-6224
> Project: OFBiz
>  Issue Type: Improvement
>  Components: specialpurpose/lucene
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>  Labels: properties, rename
> Attachments: OFBIZ-6224-PropertiesRename.patch
>
>
> Currently many properties files in various components are named after the 
> component, i.e. the bi component has bi.properties.
> In order to have consistency from component to component the 
> search.properties file in the special purpose/lucene component must be 
> renamed to lucene.properties and all references in components should reflect 
> the change.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6302) Ftl to Widget: improve ViewCertificate to use widgets in stead of ftl


[ 
https://issues.apache.org/jira/browse/OFBIZ-6302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376450#comment-15376450
 ] 

Pierre Smits commented on OFBIZ-6302:
-

Bump. Can we have this implemented before the patch grows stale?

> Ftl to Widget: improve ViewCertificate to use widgets in stead of ftl
> -
>
> Key: OFBIZ-6302
> URL: https://issues.apache.org/jira/browse/OFBIZ-6302
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>  Labels: security
> Attachments: OFBIZ-6302-Certificate.patch
>
>
> Currently the screen ViewCertificate uses a widget to render the form(s). 
> This can be replaced by widgets



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6448) Have configuration options regarding freemarkerImports.properties


[ 
https://issues.apache.org/jira/browse/OFBIZ-6448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376448#comment-15376448
 ] 

Pierre Smits commented on OFBIZ-6448:
-

Bump. Before the patch grows stale also.

> Have configuration options regarding freemarkerImports.properties
> -
>
> Key: OFBIZ-6448
> URL: https://issues.apache.org/jira/browse/OFBIZ-6448
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
> Attachments: OFBIZ-6448-FreeMarkerWorker.java.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6711) Have configuration options regarding widgets


[ 
https://issues.apache.org/jira/browse/OFBIZ-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376447#comment-15376447
 ] 

Pierre Smits commented on OFBIZ-6711:
-

Bump. Before the patch grows stale also.

> Have configuration options regarding widgets
> 
>
> Key: OFBIZ-6711
> URL: https://issues.apache.org/jira/browse/OFBIZ-6711
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL APPLICATIONS, ALL COMPONENTS
>Reporter: Pierre Smits
> Attachments: OFBIZ-6711-widget.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6946) Remove ftl dependency in order on ecommerce


[ 
https://issues.apache.org/jira/browse/OFBIZ-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376446#comment-15376446
 ] 

Pierre Smits commented on OFBIZ-6946:
-

Bump! Before the patch grows stale also.

> Remove ftl dependency in order on ecommerce
> ---
>
> Key: OFBIZ-6946
> URL: https://issues.apache.org/jira/browse/OFBIZ-6946
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Minor
> Attachments: OFBIZ-6946-order-template-location.patch
>
>
> Currently there are dependencies in the order component on the ecommerce 
> component.
> Order management should work without the ecommerce component.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7754) The big problem when load seed.


[ 
https://issues.apache.org/jira/browse/OFBIZ-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376443#comment-15376443
 ] 

Jacques Le Roux commented on OFBIZ-7754:


Thanks for you feedback Hans. Why do you prefer to disable 
CommonSystemPropertyData.xml completely over using seed-initial. I ask this 
because you created CommonSystemPropertyData.xml so maybe I miss something?

> The big problem when load seed.
> ---
>
> Key: OFBIZ-7754
> URL: https://issues.apache.org/jira/browse/OFBIZ-7754
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Kongrath Suankaewmanee
>Assignee: Jacques Le Roux
> Attachments: OFBIZ-7754.patch
>
>
> Hi All,
> Regarding, [OFBIZ-7112|https://issues.apache.org/jira/browse/OFBIZ-7112]
> That's good for who start on use the ofbiz with initial setup, but not for 
> the site that already online and has to update the OFBiz core. Because when 
> has update OFBiz core they will use command load-seed for update.
> The problem is if we use load-seed mean the configuration data that's already 
> exists will be replaced by the data from this file,
> *CommonSystemPropertyData.xml*
> So, for my suggestion should change the reader from *seed* to *seed-initial*  
> or remove systemPropertyValue from the data file.
> Thank you,
> Kongrath



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7532) Form Display Field improvement to manage multiple number format


[ 
https://issues.apache.org/jira/browse/OFBIZ-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376437#comment-15376437
 ] 

Jacques Le Roux commented on OFBIZ-7532:


Hi PIerre, yes sure sounds interesting

Please Charles update your patch. I have removed widget-form-ns.xsd, we have 
only widget-form-xsd which contains both. Thanks!

> Form Display Field improvement to manage multiple number format
> ---
>
> Key: OFBIZ-7532
> URL: https://issues.apache.org/jira/browse/OFBIZ-7532
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Charles STELTZLEN
>Assignee: Jacques Le Roux
>Priority: Minor
> Attachments: OFBIZ-7532.patch
>
>
> On display field used in forms, there is a "type" "accounting-number" which 
> is used to format number like property configuration :  
> #,##0.;(#,##0.).
> This JIRA propose to extend this idea by using a "type" "number" and an 
> additional attribute called "format-pattern". This field will be used by form 
> renderer to get the good property. It use FlexibleString to manage variable 
> in this field and so allow to have different format for the same column 
> according to some conditions.
> example:  format-pattern="accounting"/>
> The "format-pattern" will be stored in arithmetic.properties.
> example:
> # the default number format 
> default.number.format = ##0.00
> accounting.number.format = #,##0.;(#,##0.)
> quantity.number.format = ##0.00
> integer-quantity.number.format = #0
> percentage.number.format = ##.##%
> export.number.format = #.00
> In ModelFormField.java, the system gets property using 
> EntityUtilProperties.getPropertyValue to ba able to quickly add a new format.
> I think that it will require a discussion on Dev mailing-list to validate the 
> choices.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-7532) Form Display Field improvement to manage multiple number format


 [ 
https://issues.apache.org/jira/browse/OFBIZ-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux reassigned OFBIZ-7532:
--

Assignee: Jacques Le Roux

> Form Display Field improvement to manage multiple number format
> ---
>
> Key: OFBIZ-7532
> URL: https://issues.apache.org/jira/browse/OFBIZ-7532
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Charles STELTZLEN
>Assignee: Jacques Le Roux
>Priority: Minor
> Attachments: OFBIZ-7532.patch
>
>
> On display field used in forms, there is a "type" "accounting-number" which 
> is used to format number like property configuration :  
> #,##0.;(#,##0.).
> This JIRA propose to extend this idea by using a "type" "number" and an 
> additional attribute called "format-pattern". This field will be used by form 
> renderer to get the good property. It use FlexibleString to manage variable 
> in this field and so allow to have different format for the same column 
> according to some conditions.
> example:  format-pattern="accounting"/>
> The "format-pattern" will be stored in arithmetic.properties.
> example:
> # the default number format 
> default.number.format = ##0.00
> accounting.number.format = #,##0.;(#,##0.)
> quantity.number.format = ##0.00
> integer-quantity.number.format = #0
> percentage.number.format = ##.##%
> export.number.format = #.00
> In ModelFormField.java, the system gets property using 
> EntityUtilProperties.getPropertyValue to ba able to quickly add a new format.
> I think that it will require a discussion on Dev mailing-list to validate the 
> choices.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7773) createTenant tasks does not ask for parameters


[ 
https://issues.apache.org/jira/browse/OFBIZ-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376433#comment-15376433
 ] 

Pierre Smits commented on OFBIZ-7773:
-

Luckily you don't have to. Taher said he would.

But I am done argueing over this 'throwing away the old shoes before the new 
ones arrive'. 

> createTenant tasks does not ask for parameters
> --
>
> Key: OFBIZ-7773
> URL: https://issues.apache.org/jira/browse/OFBIZ-7773
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Blocker
> Attachments: OFBIZ-7773-ofbiz.patch
>
>
> When executing the gradle createTenant tasks, the following error is thrown:
> {code}
> FAILURE: Build failed with an exception.
> * Where:
> Build file '/Users/pierre/dev/ofbiz/ofbiz-gradle/build.gradle' line: 328
> * What went wrong:
> Execution failed for task ':prepareAndValidateTenantArguments'.
> > Project property tenantId is missing
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output.
> BUILD FAILED
> {code}
> The function/process is missing the guided-through approach that ./ant 
> create-tenant has.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Permissions to Confluence - OFBIZADMIN

Hi Jacques,

Thank you for your explanation.

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Thu, Jul 14, 2016 at 8:27 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Hi Pierre,
>
> For now few people have an edit access to the OFBIZADMIN space. Almost all
> are PMC and not all PMC requested access. The (long term) plan is to merge
> this space to the OFBIZ space. In the meantime we don't intend to open it
> to other persons. So the conventional way is to propose (possibly
> formatted) changes in comment.
>
> Disclaimer: this is my own opinion, I assume the PMC wants the same, else
> please chime in...
>
> Thanks
>
> Jacques
>
>
> Le 13/07/2016 à 17:01, Pierre Smits a écrit :
>
>> Please grant me privileges to fix typos and erroneous links in the various
>> best practices/code-of conduct in the OFBIZADMIN space.
>>
>> Best regards,
>>
>> Pierre Smits
>>
>>
>> ORRTIZ.COM 
>> OFBiz based solutions & services
>>
>> OFBiz Extensions Marketplace
>> http://oem.ofbizci.net/oci-2/
>>
>>
>

[jira] [Commented] (OFBIZ-7534) Migrate OFBiz from Apache Ant to Gradle build system


[ 
https://issues.apache.org/jira/browse/OFBIZ-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376416#comment-15376416
 ] 

Pierre Smits commented on OFBIZ-7534:
-

Hi [~charlb] You can use both Intellij and git to work with OFBiz code. 

The project also has git mirrors and these are made available on GitHub, You 
can start from here: https://github.com/apache/ofbiz

Best regards,

Pierre

> Migrate OFBiz from Apache Ant to Gradle build system
> 
>
> Key: OFBIZ-7534
> URL: https://issues.apache.org/jira/browse/OFBIZ-7534
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Affects Versions: Upcoming Branch
>Reporter: Taher Alkhateeb
>Assignee: Taher Alkhateeb
>  Labels: ant, build-tools, gradle
> Attachments: ANT_GRADLE_COMPARISON.txt, OFBIZ-7534.patch, 
> OFBIZ-7534.patch, OFBIZ-7534.patch, OFBIZ-7534.patch, OFBizRemoteJarList.csv, 
> OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, 
> gradle-wrapper.jar
>
>
> This is a major refactoring task referring to the [email 
> thread|http://ofbiz.markmail.org/message/vstt3wxuubmjgmqj?q=Important+Changes+to+Trunk+and+Use+of+Ant+%26+Gradle]
>  in which the community voted for the switch after a proposal from the PMC
> The purpose of this JIRA is to achieve the following objectives
> - Fully implement a working compiling system in Gradle that passes all tests
> - Remove all ant and maven build scripts from the system
> - update the documentation of the system to reflect these changes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Permissions to Confluence - OFBIZADMIN


Hi Pierre,

For now few people have an edit access to the OFBIZADMIN space. Almost all are PMC and not all PMC requested access. The (long term) plan is to merge 
this space to the OFBIZ space. In the meantime we don't intend to open it to other persons. So the conventional way is to propose (possibly formatted) 
changes in comment.


Disclaimer: this is my own opinion, I assume the PMC wants the same, else 
please chime in...

Thanks

Jacques


Le 13/07/2016 à 17:01, Pierre Smits a écrit :

Please grant me privileges to fix typos and erroneous links in the various
best practices/code-of conduct in the OFBIZADMIN space.

Best regards,

Pierre Smits


ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

[jira] [Comment Edited] (OFBIZ-7534) Migrate OFBiz from Apache Ant to Gradle build system


[ 
https://issues.apache.org/jira/browse/OFBIZ-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376394#comment-15376394
 ] 

Jacques Le Roux edited comment on OFBIZ-7534 at 7/14/16 6:22 AM:
-

bq. I am assuming that exporting from the derby and importing to another Db 
procedure hasn't changed because of Gradle.
Right
bq. I will need the ability to compile and deploy to a custom directory
Actually the Ant+Ivy task did not deliver this sophistication and I don't think 
it's needed. Downloading the right driver is enough, then Devops can automate 
the rest with scripts
bq. I am also planning to use the the tenant system and only add the components 
that are required by them.
About that see my 
[comment|https://issues.apache.org/jira/browse/OFBIZ-7773?focusedCommentId=15376365]
 at OFBIZ-7773

I had an SA experience, it was about an hypotetical "Poultry Operating 
Company". It relied on government subsidy and never flyed. It was though very 
interesting and I remember the same kind of remarks, a high potential but 
issues to resolve while doing... If you need a contact in SA I know someone who 
works with OFBiz since 2007 and lives in Cape Town Area.

Ah, and we have also [~gavin.ma...@urbannex.co.za] who is a commiter, he lives 
in Johannesburg Area :)

Good luck :)


was (Author: jacques.le.roux):
bq. I am assuming that exporting from the derby and importing to another Db 
procedure hasn't changed because of Gradle.
Right
bq. I will need the ability to compile and deploy to a custom directory
Actually the Ant+Ivy task did not deliver this sophistication and I don't think 
it's needed. Downloading the right driver is enough, then Devops can automate 
the rest with scripts
bq. I am also planning to use the the tenant system and only add the components 
that are required by them.
About that see my 
[comment|https://issues.apache.org/jira/browse/OFBIZ-7773?focusedCommentId=15376365]
 at OFBIZ-7773

I had an SA experience, it was about an hypotetical "Poultry Operating 
Company". It relied on government subsidy and never flyed. It was though very 
interesting and I remember the same kind of remarks, a high potential but 
issues to resolve while doing... If you need a contact in SA I know someone who 
works with OFBiz since 2007 and lives in Cape Town Area.

> Migrate OFBiz from Apache Ant to Gradle build system
> 
>
> Key: OFBIZ-7534
> URL: https://issues.apache.org/jira/browse/OFBIZ-7534
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Affects Versions: Upcoming Branch
>Reporter: Taher Alkhateeb
>Assignee: Taher Alkhateeb
>  Labels: ant, build-tools, gradle
> Attachments: ANT_GRADLE_COMPARISON.txt, OFBIZ-7534.patch, 
> OFBIZ-7534.patch, OFBIZ-7534.patch, OFBIZ-7534.patch, OFBizRemoteJarList.csv, 
> OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, OFBizRemoteJarList.csv, 
> gradle-wrapper.jar
>
>
> This is a major refactoring task referring to the [email 
> thread|http://ofbiz.markmail.org/message/vstt3wxuubmjgmqj?q=Important+Changes+to+Trunk+and+Use+of+Ant+%26+Gradle]
>  in which the community voted for the switch after a proposal from the PMC
> The purpose of this JIRA is to achieve the following objectives
> - Fully implement a working compiling system in Gradle that passes all tests
> - Remove all ant and maven build scripts from the system
> - update the documentation of the system to reflect these changes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7534) Migrate OFBiz from Apache Ant to Gradle build system