[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] [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=15369512#comment-15369512 ] Pierre Smits edited comment on OFBIZ-7534 at 7/10/16 9:20 AM: -- I am all for discussion first. But when the discussion is nothing more than expressions of viewpoints, and where participants aren't collaborating towards an agreement of sorts, it is a waste of time and effort. The consensus should lead to something actionable, that - for tracking and reporting - is captured in a JIRA issue. So that results show up in release notes, etc. This way we ensure that our adopters stay on the page. was (Author: pfm.smits): I am all for discussion first. But when the discussion is nothing more than expressions of viewpoints, and where participants aren't collaborating towards an agreement of sorts, it is a waste of time and effort. The consensus should lead to something actionable, that - for tracking and reporting - is captured in JIRA issues. So that results show up in release notes, etc. This way we ensure that our adopters stay on the page. > 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] [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=15369442#comment-15369442
]
Taher Alkhateeb edited comment on OFBIZ-7534 at 7/10/16 6:45 AM:
-
Ok Jacques, after further checking 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.
Should we 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}
was (Author: taher):
Ok Jacques, after further checking 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.
Should we translate all four words in the CommonUiLabels.xml and then
incorporate them?
old version:
" - Release-revision : ${releasePath}-r${info.entry.commit(revision)},
${uiLabelMap.CommonBuiltOn} ${dateTime} ${uiLabelMap.CommonWith} Java
${java.version}
new version:
"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()}"
> 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] [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=15369266#comment-15369266 ] Pierre Smits edited comment on OFBIZ-7534 at 7/9/16 7:47 PM: - I believe it is a bad thing to remove the ant tasks at this moment in time. Without the ant tasks in the code base no real comparison can be made anymore. Please restore the ant tasks. They can be removed afterwards, when everything is migrated and found acceptable. was (Author: pfm.smits): I believe it is a bad thing to remove the ant tasks at this moment in time. Without the ant tasks in the code base no real comparison can be made anymore. Please store the ant tasks. > 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] [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=15363861#comment-15363861 ] Jacques Le Roux edited comment on OFBIZ-7534 at 7/6/16 7:32 AM: Hi Jacques, In feedback to your comments: # agreed with .gradle ans build directories hiding in root as well as ofbiz.jar # It's okay but not very necessary to modify the commit saying we will remove .classpath and .project. Many other files will go away, maybe we should mention it in its own commit? # I hesitate about the build directory in each component. Under the current design each component is a gradle subproject. If any of these subprojects applies the Java plugin for whatever reason a build directory will be created. I am not sure we will use it but a little delay on this point would be better until the picture is clear. Cheers! was (Author: taher): Hi Jacques, In feedback to your comments: - agreed with .gradle ans build directories hiding in root as well as ofbiz.jar - It's okay but not very necessary to modify the commit saying we will remove .classpath and .project. Many other files will go away, maybe we should mention it in its own commit? - I hesitate about the build directory in each component. Under the current design each component is a gradle subproject. If any of these subprojects applies the Java plugin for whatever reason a build directory will be created. I am not sure we will use it but a little delay on this point would be better until the picture is clear. Cheers! > 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, build.gradle, > 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] [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=15361063#comment-15361063 ] Jacques Le Roux edited comment on OFBIZ-7534 at 7/4/16 9:19 AM: Hi Pierre, I understand your concerns, reverting and removing and reaplying a such patch is not easy at 1st glance. But as long as you keep the .gradle part (so you don't need to manipulate the Gradle wrapper), and (for me at least) keep the .gradle and build svn:ignore properties, it's not so hard as well since, in Eclipse, you can also exclude keeped files when patching (like gradle-wrapper.properties). I know what I'm talking about, I just did it with the last patch, all works perfectly, even stuff like "gradlew svnInfoFooter" I also don't think a branch is required. Apart few minor changes in Java code, it's mostly adds. Ant will still be in place with no Ant related changes (in builds, etc.) Also there are some good changes, for instance see the NOTICE file. One thing is the removing of Eclipsthe .classpath and .project file. But it's a breeze to recreate them using "gradlew eclipse". README.MD is better than README but we will maybe need to remove it later rather than now. I have no ideas about "mvnrepository vs jcenter" (ie did not look at it). I guess Taher picked jcenter because it's in relation with Gradle. was (Author: jacques.le.roux): Hi Pierre, I understand your concerns, reverting and removing and reaplying a such patch is not easy at 1st glance. But as long as you keep the .gradle part (so you don't need to manipulate the Gradle wrapper), and (for me at least) keep the .gradle and build svn:ignore properties, it's not so hard as well since, in Eclipse, you can also exclude keeped files when patching. I know what I'm talking about, I just did it with the last patch, all works perfectly, even stuff like "gradlew svnInfoFooter" I also don't think a branch is required. Apart few minor changes in Java code, it's mostly adds. Ant will still be in place with no Ant related changes (in builds, etc.) Also there are some good changes, for instance see the NOTICE file. One thing is the removing of Eclipsthe .classpath and .project file. But it's a breeze to recreate them using "gradlew eclipse". README.MD is better than README but we will maybe need to remove it later rather than now. I have no ideas about "mvnrepository vs jcenter" (ie did not look at it). I guess Taher picked jcenter because it's in relation with Gradle. > 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, build.gradle, > 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] [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=15360484#comment-15360484 ] Gil Portenseigne edited comment on OFBIZ-7534 at 7/3/16 9:38 AM: - All help is welcome, we need to find a get the correct jcenter URL ( bintray.com/bintray/jcenter ) for each jar mentionned in the post. The goal is to replace the jar in OFBiz by the corresponding remote one. For that purpose we created a framacalc to store the references for each jar : https://framacalc.org/OFBizRemoteJarList Feel free to edit it to add the corresponding remote you found and for each be sure to get the right lib, if uncertain : # delete the local lib # download the remote lib to the same location # compile The syntax to follow is : Syntax: '::' Example: 'org.apache.commons:commons-dbcp2:2.1.1' was (Author: gil portenseigne): All help is welcome, we need to find a get the correct jcenter URL ( bintray.com/bintray/jcenter ) for each jar mentionned in the post. The goal is to replace the jar in OFBiz by the corresponding remote one. For that purpose we created a framacalc to store the references for each jar : https://framacalc.org/OFBizRemoteJarList Feel free to edit it to add the corresponding remote you found and for each be sure to get the right lib, if uncertain : # delete the local lib # download the remote lib to the same location # compile > 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, build.gradle, > 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] [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=15356955#comment-15356955 ] Taher Alkhateeb edited comment on OFBIZ-7534 at 6/30/16 11:55 AM: -- Okay, doing a bit of research, the listing of the JARs and their count in each component is listed below. I would appreciate it if you can save me some time by pointing out which ones are not necessary and the code would compile without them. ||Component||Count of Jars|| |base|94| |solr|43| |birt|34| |catalina|13| |service|10| |cmssite|6| |pos|5| |ebaystore|4| |lucene|3| |webapp|3| |testtools|2| |entity|2| |content|2| |product|2| |start|1| |demo-backup|1| |ldap|1| |geronimo|1| |security|1| |googlecheckout|1| |*Total*|*229*| The detailed listing of the Jars: ||component_group||component_name||JarFile|| |applications|content|./applications/content/lib/dom4j-1.6.1.jar| |applications|content|./applications/content/lib/poi-3.13-20150929.jar| |applications|product|./applications/product/lib/watermarker-0.0.4.jar| |applications|product|./applications/product/lib/dozer-4.2.1.jar| |framework|base|./framework/base/lib/scripting/bsh-2.0b4.jar| |framework|base|./framework/base/lib/scripting/antlr-2.7.6.jar| |framework|base|./framework/base/lib/scripting/jython-nooro.jar| |framework|base|./framework/base/lib/scripting/jakarta-oro-2.0.8.jar| |framework|base|./framework/base/lib/scripting/bsf-2.4.0.jar| |framework|base|./framework/base/lib/scripting/asm-3.2.jar| |framework|base|./framework/base/lib/scripting/groovy-all-2.4.5.jar| |framework|base|./framework/base/lib/batik-all-1.8.jar| |framework|base|./framework/base/lib/jdom-1.1.jar| |framework|base|./framework/base/lib/ant-1.9.0-ant.jar| |framework|base|./framework/base/lib/fop-2.1.jar| |framework|base|./framework/base/lib/juel-impl-2.2.7.jar| |framework|base|./framework/base/lib/log4j-nosql-2.3.jar| |framework|base|./framework/base/lib/ant/ant-1.9.0-ant-apache-bsf.jar| |framework|base|./framework/base/lib/ant/ant-contrib-1.0b3.jar| |framework|base|./framework/base/lib/commons/commons-io-2.4.jar| |framework|base|./framework/base/lib/commons/commons-logging-1.2.jar| |framework|base|./framework/base/lib/commons/commons-lang-2.6.jar| |framework|base|./framework/base/lib/commons/commons-compress-1.11.jar| |framework|base|./framework/base/lib/commons/commons-pool2-2.3.jar| |framework|base|./framework/base/lib/commons/commons-el-1.0.jar| |framework|base|./framework/base/lib/commons/commons-codec-1.10.jar| |framework|base|./framework/base/lib/commons/commons-fileupload-1.3.1.jar| |framework|base|./framework/base/lib/commons/commons-csv-1.1.jar| |framework|base|./framework/base/lib/commons/commons-net-3.3.jar| |framework|base|./framework/base/lib/commons/commons-collections4-4.1.jar| |framework|base|./framework/base/lib/commons/commons-beanutils-core-1.8.3.jar| |framework|base|./framework/base/lib/commons/commons-validator-1.4.1.jar| |framework|base|./framework/base/lib/xml-apis-ext-1.3.04.jar| |framework|base|./framework/base/lib/xml-apis-1.4.01.jar| |framework|base|./framework/base/lib/log4j-1.2-api-2.3.jar| |framework|base|./framework/base/lib/log4j-slf4j-impl-2.3.jar| |framework|base|./framework/base/lib/ant-1.9.0-ant-junit.jar| |framework|base|./framework/base/lib/icu4j-57_1.jar| |framework|base|./framework/base/lib/resolver-2.9.1.jar| |framework|base|./framework/base/lib/barcode4j-2.1-barcode4j-fop-ext-complete.jar| |framework|base|./framework/base/lib/xpp3-1.1.4c.jar| |framework|base|./framework/base/lib/log4j-core-2.3.jar| |framework|base|./framework/base/lib/junit-dep-4.10.jar| |framework|base|./framework/base/lib/freemarker-2.3.24.jar| |framework|base|./framework/base/lib/tika-parsers-1.12.jar| |framework|base|./framework/base/lib/xmlrpc-client-3.1.2.jar| |framework|base|./framework/base/lib/clhm-release-1.0-lru.jar| |framework|base|./framework/base/lib/jpim-0.1.jar| |framework|base|./framework/base/lib/xalan-2.7.2.jar| |framework|base|./framework/base/lib/shiro-core-1.2.5.jar| |framework|base|./framework/base/lib/mail-1.5.1.jar| |framework|base|./framework/base/lib/pdfbox-1.8.12.jar| |framework|base|./framework/base/lib/xmlrpc-common-3.1.2.jar| |framework|base|./framework/base/lib/avalon-framework-4.2.0.jar| |framework|base|./framework/base/lib/jempbox-1.8.11.jar| |framework|base|./framework/base/lib/nekohtml-1.9.16.jar| |framework|base|./framework/base/lib/jackson-core-2.4.2.jar| |framework|base|./framework/base/lib/owasp-java-html-sanitizer-r239.jar| |framework|base|./framework/base/lib/serializer-2.9.1.jar| |framework|base|./framework/base/lib/httpclient-cache-4.4.1.jar| |framework|base|./framework/base/lib/ical4j-1.0-rc2.jar| |framework|base|./framework/base/lib/ws-commons-java5-1.0.1.jar| |framework|base|./framework/base/lib/fontbox-1.8.11.jar| |framework|base|./framework/base/lib/esapi-2.1.0.jar| |framework|base|./framework/base/lib/xercesImpl-2.11.0.jar|
[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=15355345#comment-15355345 ] Pierre Smits edited comment on OFBIZ-7534 at 6/29/16 3:03 PM: -- So there is a chicken-egg situation here (triggered by this permissions aspect): no one can assess the impact of the change without some kind of extra work in their test environments and you can't preserve permissions with patches. I would say that is a fail.. The way to get around this, and save you (and others) a lot of work, is to commit your changes to a separate dev branch. The impact is large enough. And you - as a privileged contributor - have the mandate to create one. Those who want to test your changes then just have to execute an update of the check-out to get the latest revision. On the plus side there is then also the aspect of being able to reference revisions when it comes to reporting findings. was (Author: pfm.smits): So there is a chicken-egg situation here (with respect to permissions): no one can assess the impact of the change without some kind of extra work in their test environments and you can't preserve permissions with patches. I would say that is a fail.. The way to get around this, and save you (and others) a lot of work, is to commit your changes to a separate dev branch. The impact is large enough. And you - as a privileged contributor - have the mandate to create one. Those who want to test your changes then just have to execute an update of the check-out to get the latest revision. On the plus side there is then also the aspect of being able to reference revisions when it comes to reporting findings. > 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, build.gradle, 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] [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=15355345#comment-15355345 ] Pierre Smits edited comment on OFBIZ-7534 at 6/29/16 2:43 PM: -- So there is a chicken-egg situation here (with respect to permissions): no one can assess the impact of the change without some kind of extra work in their test environments and you can't preserve permissions with patches. I would say that is a fail.. The way to get around this, and save you (and others) a lot of work, is to commit your changes to a separate dev branch. The impact is large enough. And you - as a privileged contributor - have the mandate to create one. Those who want to test your changes then just have to execute an update of the check-out to get the latest revision. On the plus side there is then also the aspect of being able to reference revisions when it comes to reporting findings. was (Author: pfm.smits): So there is a chicken-egg situation here (with respect to permissions): no one can assess the impact of the change without some kind of extra work in their test environments and you can't preserve permissions with patches. I would say that is a fail.. The way to get around this, and save you (and others) a lot of work, is to commit your changes to a separate dev branch. The impact is large enough. And you - as a privileged contributor - have the mandate to create one. Those who want to test your changes then just have to execute and update to get the latest revision. On the plus side there is then also the aspect of being able to reference revisions when it comes to reporting findings. > 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, build.gradle, 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] [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=15355345#comment-15355345 ] Pierre Smits edited comment on OFBIZ-7534 at 6/29/16 2:43 PM: -- So there is a chicken-egg situation here (with respect to permissions): no one can assess the impact of the change without some kind of extra work in their test environments and you can't preserve permissions with patches. I would say that is a fail.. The way to get around this, and save you (and others) a lot of work, is to commit your changes to a separate dev branch. The impact is large enough. And you - as a privileged contributor - have the mandate to create one. Those who want to test your changes then just have to execute and update to get the latest revision. On the plus side there is then also the aspect of being able to reference revisions when it comes to reporting findings. was (Author: pfm.smits): So there is a chicken-egg situation here (with respect to permissions): no one can assess the impact of the change without some kind of extra work in their test environments and you can't preserve permissions with patches. I would say that is a fail.. The way to get around this, and save you (and others) a lot of work, is to commit your changes to a separate dev branch. The impact is large enough. And you - as a privileged contributor have the mandate to create one. Those who want to test your changes then just have to execute and update to get the latest revision. On the plus side there is then also the aspect of being able to reference revisions when it comes to reporting findings. > 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, build.gradle, 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)
