[jira] [Updated] (OFBIZ-5165) Broken renderLabel functionality of screenfop view handler
[ https://issues.apache.org/jira/browse/OFBIZ-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit updated OFBIZ-5165: Attachment: OFBIZ-5165-R10.04.patch OFBIZ-5165.patch Here is the patch for this issue. - Corrected the conditions for label rendering. - Also replaced fo:inline with fo:block as fo:inline can't render directly. -- A contribution from HotWax media Broken renderLabel functionality of screenfop view handler -- Key: OFBIZ-5165 URL: https://issues.apache.org/jira/browse/OFBIZ-5165 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release Branch 10.04, Release 10.04, SVN trunk, Release Branch 12.04 Reporter: Deepak Dixit Priority: Minor Fix For: Release Branch 10.04, Release Branch 11.04, SVN trunk, Release Branch 12.04 Attachments: OFBIZ-5165.patch, OFBIZ-5165-R10.04.patch If we use label inside widget tag then renderLabel macro skip the label rendering due to wrong condition check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] [RELEASE] Apache OFBiz 12.04.01
+1. -- Thanks And Regards Sumit Pandit Tata Consultancy Services Cell:- 917503046188 - Original Message - | From: Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com | To: dev@ofbiz.apache.org | Sent: Tuesday, March 26, 2013 10:02:35 PM | Subject: [VOTE] [RELEASE] Apache OFBiz 12.04.01 | This is the vote thread to approve the first release for the 12.04 | branch. This new release, Apache OFBiz 12.04.01 (major release | number: 12.04; minor release number: 01) is the first release of | the 12.04 series and contains all the features of the trunk up to | April 2012 and since then has been stabilized with bug fixes. It | will become the OFBiz current stable release and users of the | 11.04 series will be encouraged to migrate to this release. | The candidate release files can be downloaded from here: | https://dist.apache.org/repos/dist/dev/ofbiz/ | (committers only) or from here: | http://people.apache.org/~jacopoc/dist/ | (everyone else) | and are: | * apache-ofbiz-12.04.01.zip: the release package, based on the 12.04 | branch at revision 1461136 (latest as of now) | * KEYS: text file with keys | * apache-ofbiz-12.04.01.zip.asc: the detached signature file | * apache-ofbiz-12.04.01.zip.md5, apache-ofbiz-12.04.01.zip.sha: | hashes | Please download the zip file and check its signatures (for | instructions on testing the signatures see | http://www.apache.org/info/verification.html), then test the | release. | Vote: | [ +1] release as Apache OFBiz 12.04.01 | [ -1] do not release | This vote will be closed in Monday, 1st of April. | For more details about this process please read | http://www.apache.org/foundation/voting.html | The following text is quoted from the above url: | Votes on whether a package is ready to be released use majority | approval -- i.e. at least three PMC members must vote affirmatively | for release, and there must be more positive than negative votes. | Releases may not be vetoed. Generally the community will cancel the | release vote if anyone identifies serious problems, but in most | cases the ultimate decision, lies with the individual serving as | release manager. | Jacopo Cappellato =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
Re: svn commit: r1461709 - in /ofbiz/trunk: ./ framework/base/lib/ framework/base/lib/ant/
Hi Jacques, I don't think we discussed this specifically, and I am actually not even sure this naming convention is the best approach we could adopt: all I know it works well for Tomcat (now upgrading Tomcat is rather simple while in the past it was a pain... but this is also a consequence of the switch I did some time ago to the embedded distribution, available in the new releases) and so I decided to use it while I was upgrading Ant (because its jar files were missing any release information) The new format is nice because from the first part of the jar name you can understand from which release file we got it, while the second part is the original name of the jar (as found in the release file). We can see how it works in the next months and see if we like it, before discussing and making it a rule; or if you want we can discuss it now and see if the community can come up with a solution. Another important reason I have adopted it for Ant is that there are other jar files for Ant that don't come from the Ant distribution (e.g. ant-contrib*, ant-nodeps*) and they currently have a different release number as suffix: now it is easier to distinguish between them and the jars in the core distribution (because the jars from the core distribution now have the prefix ant-1.9.0-) I hope I was able to explain my reasonings adequately. Jacopo On Mar 27, 2013, at 10:55 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi Jacopo, I'm not against this new way of naming jars (I'm even for it) but where did we discuss this? Thanks Jacques From: jaco...@apache.org Author: jacopoc Date: Wed Mar 27 17:01:12 2013 New Revision: 1461709 URL: http://svn.apache.org/r1461709 Log: Upgrade from Ant 1.8.4 to Ant 1.9.0: in the process I have also switched the naming convention of jars to the new one we are adopting for example for Tomcat jars that is NAME-OF-THE-EXTERNAL-PROJECT-RELEASE-NUMBER-ORIGINAL-NAME-OF-JAR-FILE. For example, in in the release package apache-ant-1.9.0.zip we have the jar ant-launcher.jar, the name of the jar in OFBiz is: ant-1.9.0-ant-launcher.jar Added: ofbiz/trunk/framework/base/lib/ant-1.9.0-ant-junit.jar (with props) ofbiz/trunk/framework/base/lib/ant-1.9.0-ant-launcher.jar (with props) ofbiz/trunk/framework/base/lib/ant-1.9.0-ant.jar (with props) ofbiz/trunk/framework/base/lib/ant/ant-1.9.0-ant-apache-bsf.jar (with props) Removed: ofbiz/trunk/framework/base/lib/ant-1.8.4.jar ofbiz/trunk/framework/base/lib/ant-junit-1.8.4.jar ofbiz/trunk/framework/base/lib/ant-launcher-1.8.4.jar ofbiz/trunk/framework/base/lib/ant/ant-apache-bsf-1.8.4.jar Modified: ofbiz/trunk/.classpath ofbiz/trunk/LICENSE ofbiz/trunk/ant Modified: ofbiz/trunk/.classpath URL: http://svn.apache.org/viewvc/ofbiz/trunk/.classpath?rev=1461709r1=1461708r2=1461709view=diff == --- ofbiz/trunk/.classpath (original) +++ ofbiz/trunk/.classpath Wed Mar 27 17:01:12 2013 @@ -17,10 +17,10 @@ classpathentry kind=lib path=applications/content/lib/tika-parsers-1.0.jar/ classpathentry kind=lib path=applications/product/lib/watermarker-0.0.4.jar/ classpathentry kind=lib path=applications/product/lib/dozer-4.2.1.jar/ -classpathentry kind=lib path=framework/base/lib/ant-1.8.4.jar/ -classpathentry kind=lib path=framework/base/lib/ant-junit-1.8.4.jar/ -classpathentry kind=lib path=framework/base/lib/ant-launcher-1.8.4.jar/ -classpathentry kind=lib path=framework/base/lib/ant/ant-apache-bsf-1.8.4.jar/ +classpathentry kind=lib path=framework/base/lib/ant-1.9.0-ant.jar/ +classpathentry kind=lib path=framework/base/lib/ant-1.9.0-ant-junit.jar/ +classpathentry kind=lib path=framework/base/lib/ant-1.9.0-ant-launcher.jar/ +classpathentry kind=lib path=framework/base/lib/ant/ant-1.9.0-ant-apache-bsf.jar/ classpathentry kind=lib path=framework/base/lib/ant/ant-nodeps-1.8.1.jar/ classpathentry kind=lib path=framework/base/lib/antisamy-bin.1.2.jar/ classpathentry kind=lib path=framework/base/lib/avalon-framework-4.2.0.jar/ Modified: ofbiz/trunk/LICENSE URL: http://svn.apache.org/viewvc/ofbiz/trunk/LICENSE?rev=1461709r1=1461708r2=1461709view=diff == --- ofbiz/trunk/LICENSE (original) +++ ofbiz/trunk/LICENSE Wed Mar 27 17:01:12 2013 @@ -10,10 +10,10 @@ OFBiz and the full text of the license u For additional details, see the NOTICE file. = The following libraries are licensed under the Apache License Version 2.0: -ofbiz/trunk/framework/base/lib/ant-launcher-1.8.4.jar -ofbiz/trunk/framework/base/lib/ant-1.8.4.jar -ofbiz/trunk/framework/base/lib/ant-junit-1.8.4.jar -ofbiz/trunk/framework/base/lib/ant/ant-apache-bsf-1.8.4.jar
Re: [VOTE] [RELEASE] Apache OFBiz 12.04.01
+1 Thanks!! Regards, Ratnesh Upadhyay Hotwax Media | www.hotwaxmedia.com On Tue, Mar 26, 2013 at 10:02 PM, Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com wrote: This is the vote thread to approve the first release for the 12.04 branch. This new release, Apache OFBiz 12.04.01 (major release number: 12.04; minor release number: 01) is the first release of the 12.04 series and contains all the features of the trunk up to April 2012 and since then has been stabilized with bug fixes. It will become the OFBiz current stable release and users of the 11.04 series will be encouraged to migrate to this release. The candidate release files can be downloaded from here: https://dist.apache.org/repos/dist/dev/ofbiz/ (committers only) or from here: http://people.apache.org/~jacopoc/dist/ (everyone else) and are: * apache-ofbiz-12.04.01.zip: the release package, based on the 12.04 branch at revision 1461136 (latest as of now) * KEYS: text file with keys * apache-ofbiz-12.04.01.zip.asc: the detached signature file * apache-ofbiz-12.04.01.zip.md5, apache-ofbiz-12.04.01.zip.sha: hashes Please download the zip file and check its signatures (for instructions on testing the signatures see http://www.apache.org/info/verification.html), then test the release. Vote: [ +1] release as Apache OFBiz 12.04.01 [ -1] do not release This vote will be closed in Monday, 1st of April. For more details about this process please read http://www.apache.org/foundation/voting.html The following text is quoted from the above url: Votes on whether a package is ready to be released use majority approval -- i.e. at least three PMC members must vote affirmatively for release, and there must be more positive than negative votes. Releases may not be vetoed. Generally the community will cancel the release vote if anyone identifies serious problems, but in most cases the ultimate decision, lies with the individual serving as release manager. Jacopo Cappellato
Re: svn commit: r1461709 - in /ofbiz/trunk: ./ framework/base/lib/ framework/base/lib/ant/
Deal Thanks! Jacques From: Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com Hi Jacques, I don't think we discussed this specifically, and I am actually not even sure this naming convention is the best approach we could adopt: all I know it works well for Tomcat (now upgrading Tomcat is rather simple while in the past it was a pain... but this is also a consequence of the switch I did some time ago to the embedded distribution, available in the new releases) and so I decided to use it while I was upgrading Ant (because its jar files were missing any release information) The new format is nice because from the first part of the jar name you can understand from which release file we got it, while the second part is the original name of the jar (as found in the release file). We can see how it works in the next months and see if we like it, before discussing and making it a rule; or if you want we can discuss it now and see if the community can come up with a solution. Another important reason I have adopted it for Ant is that there are other jar files for Ant that don't come from the Ant distribution (e.g. ant-contrib*, ant-nodeps*) and they currently have a different release number as suffix: now it is easier to distinguish between them and the jars in the core distribution (because the jars from the core distribution now have the prefix ant-1.9.0-) I hope I was able to explain my reasonings adequately. Jacopo On Mar 27, 2013, at 10:55 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi Jacopo, I'm not against this new way of naming jars (I'm even for it) but where did we discuss this? Thanks Jacques From: jaco...@apache.org Author: jacopoc Date: Wed Mar 27 17:01:12 2013 New Revision: 1461709 URL: http://svn.apache.org/r1461709 Log: Upgrade from Ant 1.8.4 to Ant 1.9.0: in the process I have also switched the naming convention of jars to the new one we are adopting for example for Tomcat jars that is NAME-OF-THE-EXTERNAL-PROJECT-RELEASE-NUMBER-ORIGINAL-NAME-OF-JAR-FILE. For example, in in the release package apache-ant-1.9.0.zip we have the jar ant-launcher.jar, the name of the jar in OFBiz is: ant-1.9.0-ant-launcher.jar Added: ofbiz/trunk/framework/base/lib/ant-1.9.0-ant-junit.jar (with props) ofbiz/trunk/framework/base/lib/ant-1.9.0-ant-launcher.jar (with props) ofbiz/trunk/framework/base/lib/ant-1.9.0-ant.jar (with props) ofbiz/trunk/framework/base/lib/ant/ant-1.9.0-ant-apache-bsf.jar (with props) Removed: ofbiz/trunk/framework/base/lib/ant-1.8.4.jar ofbiz/trunk/framework/base/lib/ant-junit-1.8.4.jar ofbiz/trunk/framework/base/lib/ant-launcher-1.8.4.jar ofbiz/trunk/framework/base/lib/ant/ant-apache-bsf-1.8.4.jar Modified: ofbiz/trunk/.classpath ofbiz/trunk/LICENSE ofbiz/trunk/ant Modified: ofbiz/trunk/.classpath URL: http://svn.apache.org/viewvc/ofbiz/trunk/.classpath?rev=1461709r1=1461708r2=1461709view=diff == --- ofbiz/trunk/.classpath (original) +++ ofbiz/trunk/.classpath Wed Mar 27 17:01:12 2013 @@ -17,10 +17,10 @@ classpathentry kind=lib path=applications/content/lib/tika-parsers-1.0.jar/ classpathentry kind=lib path=applications/product/lib/watermarker-0.0.4.jar/ classpathentry kind=lib path=applications/product/lib/dozer-4.2.1.jar/ -classpathentry kind=lib path=framework/base/lib/ant-1.8.4.jar/ -classpathentry kind=lib path=framework/base/lib/ant-junit-1.8.4.jar/ -classpathentry kind=lib path=framework/base/lib/ant-launcher-1.8.4.jar/ -classpathentry kind=lib path=framework/base/lib/ant/ant-apache-bsf-1.8.4.jar/ +classpathentry kind=lib path=framework/base/lib/ant-1.9.0-ant.jar/ +classpathentry kind=lib path=framework/base/lib/ant-1.9.0-ant-junit.jar/ +classpathentry kind=lib path=framework/base/lib/ant-1.9.0-ant-launcher.jar/ +classpathentry kind=lib path=framework/base/lib/ant/ant-1.9.0-ant-apache-bsf.jar/ classpathentry kind=lib path=framework/base/lib/ant/ant-nodeps-1.8.1.jar/ classpathentry kind=lib path=framework/base/lib/antisamy-bin.1.2.jar/ classpathentry kind=lib path=framework/base/lib/avalon-framework-4.2.0.jar/ Modified: ofbiz/trunk/LICENSE URL: http://svn.apache.org/viewvc/ofbiz/trunk/LICENSE?rev=1461709r1=1461708r2=1461709view=diff == --- ofbiz/trunk/LICENSE (original) +++ ofbiz/trunk/LICENSE Wed Mar 27 17:01:12 2013 @@ -10,10 +10,10 @@ OFBiz and the full text of the license u For additional details, see the NOTICE file. = The following libraries are licensed under the Apache License Version 2.0: -ofbiz/trunk/framework/base/lib/ant-launcher-1.8.4.jar -ofbiz/trunk/framework/base/lib/ant-1.8.4.jar
Re: svn commit: r1461709 - in /ofbiz/trunk: ./ framework/base/lib/ framework/base/lib/ant/
Jacques, as a side note, I know that you have recently worked at cleaning up some jars etc... if in the process you have put together some notes about jars dependencies, jar status etc... I'd love to get that as I am reviewing the jars we distribute to see if we need to upgrade them. Thanks, Jacopo On Mar 28, 2013, at 9:31 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Deal Thanks! Jacques From: Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com Hi Jacques, I don't think we discussed this specifically, and I am actually not even sure this naming convention is the best approach we could adopt: all I know it works well for Tomcat (now upgrading Tomcat is rather simple while in the past it was a pain... but this is also a consequence of the switch I did some time ago to the embedded distribution, available in the new releases) and so I decided to use it while I was upgrading Ant (because its jar files were missing any release information) The new format is nice because from the first part of the jar name you can understand from which release file we got it, while the second part is the original name of the jar (as found in the release file). We can see how it works in the next months and see if we like it, before discussing and making it a rule; or if you want we can discuss it now and see if the community can come up with a solution. Another important reason I have adopted it for Ant is that there are other jar files for Ant that don't come from the Ant distribution (e.g. ant-contrib*, ant-nodeps*) and they currently have a different release number as suffix: now it is easier to distinguish between them and the jars in the core distribution (because the jars from the core distribution now have the prefix ant-1.9.0-) I hope I was able to explain my reasonings adequately. Jacopo On Mar 27, 2013, at 10:55 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi Jacopo, I'm not against this new way of naming jars (I'm even for it) but where did we discuss this? Thanks Jacques From: jaco...@apache.org Author: jacopoc Date: Wed Mar 27 17:01:12 2013 New Revision: 1461709 URL: http://svn.apache.org/r1461709 Log: Upgrade from Ant 1.8.4 to Ant 1.9.0: in the process I have also switched the naming convention of jars to the new one we are adopting for example for Tomcat jars that is NAME-OF-THE-EXTERNAL-PROJECT-RELEASE-NUMBER-ORIGINAL-NAME-OF-JAR-FILE. For example, in in the release package apache-ant-1.9.0.zip we have the jar ant-launcher.jar, the name of the jar in OFBiz is: ant-1.9.0-ant-launcher.jar Added: ofbiz/trunk/framework/base/lib/ant-1.9.0-ant-junit.jar (with props) ofbiz/trunk/framework/base/lib/ant-1.9.0-ant-launcher.jar (with props) ofbiz/trunk/framework/base/lib/ant-1.9.0-ant.jar (with props) ofbiz/trunk/framework/base/lib/ant/ant-1.9.0-ant-apache-bsf.jar (with props) Removed: ofbiz/trunk/framework/base/lib/ant-1.8.4.jar ofbiz/trunk/framework/base/lib/ant-junit-1.8.4.jar ofbiz/trunk/framework/base/lib/ant-launcher-1.8.4.jar ofbiz/trunk/framework/base/lib/ant/ant-apache-bsf-1.8.4.jar Modified: ofbiz/trunk/.classpath ofbiz/trunk/LICENSE ofbiz/trunk/ant Modified: ofbiz/trunk/.classpath URL: http://svn.apache.org/viewvc/ofbiz/trunk/.classpath?rev=1461709r1=1461708r2=1461709view=diff == --- ofbiz/trunk/.classpath (original) +++ ofbiz/trunk/.classpath Wed Mar 27 17:01:12 2013 @@ -17,10 +17,10 @@ classpathentry kind=lib path=applications/content/lib/tika-parsers-1.0.jar/ classpathentry kind=lib path=applications/product/lib/watermarker-0.0.4.jar/ classpathentry kind=lib path=applications/product/lib/dozer-4.2.1.jar/ -classpathentry kind=lib path=framework/base/lib/ant-1.8.4.jar/ -classpathentry kind=lib path=framework/base/lib/ant-junit-1.8.4.jar/ -classpathentry kind=lib path=framework/base/lib/ant-launcher-1.8.4.jar/ -classpathentry kind=lib path=framework/base/lib/ant/ant-apache-bsf-1.8.4.jar/ +classpathentry kind=lib path=framework/base/lib/ant-1.9.0-ant.jar/ +classpathentry kind=lib path=framework/base/lib/ant-1.9.0-ant-junit.jar/ +classpathentry kind=lib path=framework/base/lib/ant-1.9.0-ant-launcher.jar/ +classpathentry kind=lib path=framework/base/lib/ant/ant-1.9.0-ant-apache-bsf.jar/ classpathentry kind=lib path=framework/base/lib/ant/ant-nodeps-1.8.1.jar/ classpathentry kind=lib path=framework/base/lib/antisamy-bin.1.2.jar/ classpathentry kind=lib path=framework/base/lib/avalon-framework-4.2.0.jar/ Modified: ofbiz/trunk/LICENSE URL: http://svn.apache.org/viewvc/ofbiz/trunk/LICENSE?rev=1461709r1=1461708r2=1461709view=diff == --- ofbiz/trunk/LICENSE (original) +++ ofbiz/trunk/LICENSE Wed Mar 27
Re: [VOTE] [RELEASE] Apache OFBiz 12.04.01
+1 -- From: Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com Sent: Wednesday, March 27, 2013 12:32 AM To: dev@ofbiz.apache.org Subject: [VOTE] [RELEASE] Apache OFBiz 12.04.01 This is the vote thread to approve the first release for the 12.04 branch. This new release, Apache OFBiz 12.04.01 (major release number: 12.04; minor release number: 01) is the first release of the 12.04 series and contains all the features of the trunk up to April 2012 and since then has been stabilized with bug fixes. It will become the OFBiz current stable release and users of the 11.04 series will be encouraged to migrate to this release. The candidate release files can be downloaded from here: https://dist.apache.org/repos/dist/dev/ofbiz/ (committers only) or from here: http://people.apache.org/~jacopoc/dist/ (everyone else) and are: * apache-ofbiz-12.04.01.zip: the release package, based on the 12.04 branch at revision 1461136 (latest as of now) * KEYS: text file with keys * apache-ofbiz-12.04.01.zip.asc: the detached signature file * apache-ofbiz-12.04.01.zip.md5, apache-ofbiz-12.04.01.zip.sha: hashes Please download the zip file and check its signatures (for instructions on testing the signatures see http://www.apache.org/info/verification.html), then test the release. Vote: [ +1] release as Apache OFBiz 12.04.01 [ -1] do not release This vote will be closed in Monday, 1st of April. For more details about this process please read http://www.apache.org/foundation/voting.html The following text is quoted from the above url: Votes on whether a package is ready to be released use majority approval -- i.e. at least three PMC members must vote affirmatively for release, and there must be more positive than negative votes. Releases may not be vetoed. Generally the community will cancel the release vote if anyone identifies serious problems, but in most cases the ultimate decision, lies with the individual serving as release manager. Jacopo Cappellato
Re: [VOTE] [RELEASE] Apache OFBiz 12.04.01
Am 26.03.2013 17:32, schrieb Jacopo Cappellato: This is the vote thread to approve the first release for the 12.04 branch. This new release, Apache OFBiz 12.04.01 (major release number: 12.04; minor release number: 01) is the first release of the 12.04 series and contains all the features of the trunk up to April 2012 and since then has been stabilized with bug fixes. It will become the OFBiz current stable release and users of the 11.04 series will be encouraged to migrate to this release. [..] Please download the zip file and check its signatures (for instructions on testing the signatures see http://www.apache.org/info/verification.html), then test the release. Vote: +1 Checksums/signature ok, tests are running without failure (Yay!), no showstoppers found. Christian
Re: [VOTE] [RELEASE] Apache OFBiz 12.04.01
+1 for the release, GPG Key and checksum SHA512 and MD5 ok I never use gpg to generate my checksum, I needed some time to understant d why md5sum -c didn't works :) thks Jacopo Nicolas Le 26/03/2013 17:32, Jacopo Cappellato a écrit : This is the vote thread to approve the first release for the 12.04 branch. This new release, Apache OFBiz 12.04.01 (major release number: 12.04; minor release number: 01) is the first release of the 12.04 series and contains all the features of the trunk up to April 2012 and since then has been stabilized with bug fixes. It will become the OFBiz current stable release and users of the 11.04 series will be encouraged to migrate to this release. The candidate release files can be downloaded from here: https://dist.apache.org/repos/dist/dev/ofbiz/ (committers only) or from here: http://people.apache.org/~jacopoc/dist/ (everyone else) and are: * apache-ofbiz-12.04.01.zip: the release package, based on the 12.04 branch at revision 1461136 (latest as of now) * KEYS: text file with keys * apache-ofbiz-12.04.01.zip.asc: the detached signature file * apache-ofbiz-12.04.01.zip.md5, apache-ofbiz-12.04.01.zip.sha: hashes Please download the zip file and check its signatures (for instructions on testing the signatures see http://www.apache.org/info/verification.html), then test the release. Vote: [ +1] release as Apache OFBiz 12.04.01 [ -1] do not release This vote will be closed in Monday, 1st of April. For more details about this process please read http://www.apache.org/foundation/voting.html The following text is quoted from the above url: Votes on whether a package is ready to be released use majority approval -- i.e. at least three PMC members must vote affirmatively for release, and there must be more positive than negative votes. Releases may not be vetoed. Generally the community will cancel the release vote if anyone identifies serious problems, but in most cases the ultimate decision, lies with the individual serving as release manager. Jacopo Cappellato -- Nicolas MALIN Consultant Tél : 06.17.66.40.06 Site projet : http://www.neogia.org/ --- Société LibrenBerry Tél : 02.48.02.56.12 Site : http://www.librenberry.net/
Re: Some ideas for the future of the OFBiz
Sound good, it was mentioned on the last thread to replace mini-lang CRUD by entity-auto service, I have been started an issue. Is this still valid ? Nicolas Le 21/03/2013 11:57, Jacopo Cappellato a écrit : Hi all, this is just intended to brainstorm some ideas for the future OFBiz (let's say for the 14.04 branch) and to get the community feedback... I don't have concrete plans at the moment for most of them Some of the ideas below are intended to renew some core parts of the OFBiz Framework, replacing custom code (some of getting old) with Open Source alternatives; some of them are just cleanups. * Replace the OFBiz TX Manager and the Database Connection Pool (Geronimo TX and DBCP, well... they actually can stay as optional components) with: http://www.atomikos.com/Main/TransactionsEssentials (see initial work on https://issues.apache.org/jira/browse/OFBIZ-5129 ) * Refactor the OFBiz Security (authentication/authorization/cryptography) with (a session I attended during ApacheCon@Portland inspired me for this): http://shiro.apache.org * Replace Javolution (this has been already discussed in the past) * Replace the OFBiz cache system with: http://ehcache.org * Replace the OFBiz job scheduler with: http://quartz-scheduler.org * Reorganize the screen data preparation Groovy scripts into bigger files with methods (they are now individual files); for example, instead of having: applications/product/webapp/catalog/WEB-INF/actions/product/EditProductAssoc.groovy applications/product/webapp/catalog/WEB-INF/actions/product/EditProductContent.groovy applications/product/webapp/catalog/WEB-INF/actions/product/EditProductContentContent.groovy applications/product/webapp/catalog/WEB-INF/actions/product/EditProductFeatures.groovy ... we could have one file: applications/product/webapp/catalog/WEB-INF/actions/EditProduct.groovy with methods: editProductAssoc, editProductContent, editProductContentContent, editProductFeatures... (note: this switch is possible since the enhancements we did one year ago); this could make our code more readable and organized without loosing the ability to override individual scripts from hot-deploy components; in the process, we could also review the scripts and clean them or improve (some of them are pretty old) * (in the process) we could also refactor the code of the Groovy scripts to use the (now experimental and to be tested/expanded) DSL methods we implemented one year ago Kind regards, Jacopo -- Nicolas MALIN Consultant Tél : 06.17.66.40.06 Site projet : http://www.neogia.org/ --- Société LibrenBerry Tél : 02.48.02.56.12 Site : http://www.librenberry.net/
Re: Some ideas for the future of the OFBiz
Any effort to reduce the amount of code is worthwhile. -Adrian On 3/28/2013 5:14 PM, Nicolas Malin wrote: Sound good, it was mentioned on the last thread to replace mini-lang CRUD by entity-auto service, I have been started an issue. Is this still valid ? Nicolas Le 21/03/2013 11:57, Jacopo Cappellato a écrit : Hi all, this is just intended to brainstorm some ideas for the future OFBiz (let's say for the 14.04 branch) and to get the community feedback... I don't have concrete plans at the moment for most of them Some of the ideas below are intended to renew some core parts of the OFBiz Framework, replacing custom code (some of getting old) with Open Source alternatives; some of them are just cleanups. * Replace the OFBiz TX Manager and the Database Connection Pool (Geronimo TX and DBCP, well... they actually can stay as optional components) with: http://www.atomikos.com/Main/TransactionsEssentials (see initial work on https://issues.apache.org/jira/browse/OFBIZ-5129 ) * Refactor the OFBiz Security (authentication/authorization/cryptography) with (a session I attended during ApacheCon@Portland inspired me for this): http://shiro.apache.org * Replace Javolution (this has been already discussed in the past) * Replace the OFBiz cache system with: http://ehcache.org * Replace the OFBiz job scheduler with: http://quartz-scheduler.org * Reorganize the screen data preparation Groovy scripts into bigger files with methods (they are now individual files); for example, instead of having: applications/product/webapp/catalog/WEB-INF/actions/product/EditProductAssoc.groovy applications/product/webapp/catalog/WEB-INF/actions/product/EditProductContent.groovy applications/product/webapp/catalog/WEB-INF/actions/product/EditProductContentContent.groovy applications/product/webapp/catalog/WEB-INF/actions/product/EditProductFeatures.groovy ... we could have one file: applications/product/webapp/catalog/WEB-INF/actions/EditProduct.groovy with methods: editProductAssoc, editProductContent, editProductContentContent, editProductFeatures... (note: this switch is possible since the enhancements we did one year ago); this could make our code more readable and organized without loosing the ability to override individual scripts from hot-deploy components; in the process, we could also review the scripts and clean them or improve (some of them are pretty old) * (in the process) we could also refactor the code of the Groovy scripts to use the (now experimental and to be tested/expanded) DSL methods we implemented one year ago Kind regards, Jacopo
Re: Some ideas for the future of the OFBiz
+1 On Mar 28, 2013, at 6:22 PM, Adrian Crum adrian.c...@sandglass-software.com wrote: Any effort to reduce the amount of code is worthwhile. -Adrian On 3/28/2013 5:14 PM, Nicolas Malin wrote: Sound good, it was mentioned on the last thread to replace mini-lang CRUD by entity-auto service, I have been started an issue. Is this still valid ? Nicolas Le 21/03/2013 11:57, Jacopo Cappellato a écrit : Hi all, this is just intended to brainstorm some ideas for the future OFBiz (let's say for the 14.04 branch) and to get the community feedback... I don't have concrete plans at the moment for most of them Some of the ideas below are intended to renew some core parts of the OFBiz Framework, replacing custom code (some of getting old) with Open Source alternatives; some of them are just cleanups. * Replace the OFBiz TX Manager and the Database Connection Pool (Geronimo TX and DBCP, well... they actually can stay as optional components) with: http://www.atomikos.com/Main/TransactionsEssentials (see initial work on https://issues.apache.org/jira/browse/OFBIZ-5129 ) * Refactor the OFBiz Security (authentication/authorization/cryptography) with (a session I attended during ApacheCon@Portland inspired me for this): http://shiro.apache.org * Replace Javolution (this has been already discussed in the past) * Replace the OFBiz cache system with: http://ehcache.org * Replace the OFBiz job scheduler with: http://quartz-scheduler.org * Reorganize the screen data preparation Groovy scripts into bigger files with methods (they are now individual files); for example, instead of having: applications/product/webapp/catalog/WEB-INF/actions/product/EditProductAssoc.groovy applications/product/webapp/catalog/WEB-INF/actions/product/EditProductContent.groovy applications/product/webapp/catalog/WEB-INF/actions/product/EditProductContentContent.groovy applications/product/webapp/catalog/WEB-INF/actions/product/EditProductFeatures.groovy ... we could have one file: applications/product/webapp/catalog/WEB-INF/actions/EditProduct.groovy with methods: editProductAssoc, editProductContent, editProductContentContent, editProductFeatures... (note: this switch is possible since the enhancements we did one year ago); this could make our code more readable and organized without loosing the ability to override individual scripts from hot-deploy components; in the process, we could also review the scripts and clean them or improve (some of them are pretty old) * (in the process) we could also refactor the code of the Groovy scripts to use the (now experimental and to be tested/expanded) DSL methods we implemented one year ago Kind regards, Jacopo
Re: Some ideas for the future of the OFBiz
I'm not so much suggesting a beginner mode as I am suggesting that controls be scoped to the role of the logged in user. It just doesn't make sense to show controls that link to screens that the user does not have access to. A side-effect of this would be that an order entry user would have greatly simplified screens. - Paul Foxworthy wrote: Hi Ean, I am absolutely 100% in agreement that the user experience is a big barrier to entry for OFBiz. I am comfortable with Javascript being part of the primary user interface, provided there is architectural provision for alternatives. I do not think that a limited beginner mode is the answer. See the thread at http://ofbiz.135035.n4.nabble.com/hiding-functionality-in-ofbiz-td3473417.html for some discussion on this. Cheers Paul Foxworthy -- Ean Schuessler, CTO e...@brainfood.com 214-720-0700 x 315 Brainfood, Inc. http://www.brainfood.com
Re: In preparation for the 13.04 branch
Le 22/03/2013 17:19, Jacopo Cappellato a écrit : Of course we can still decide to issue a release of specialpurpose components separately. I worked on it, unit tests failed because specialpurpose components load some data needing. I continued the investigation but by lack of time I didn't solve the problem. I hope good, Nicolas -- Nicolas MALIN Consultant Tél : 06.17.66.40.06 Site projet : http://www.neogia.org/ --- Société LibrenBerry Tél : 02.48.02.56.12 Site : http://www.librenberry.net/
Re: Some ideas for the future of the OFBiz
Hi Jacopo, +1 I hope there is a vote for prioritizing the implementation sequence of these amazing Ideas. Regards, Medhat -- View this message in context: http://ofbiz.135035.n4.nabble.com/Some-ideas-for-the-future-of-the-OFBiz-tp4639965p4640208.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
Re: In preparation for the 13.04 branch
I am going to commit a fix for this soon, I am working on it right now. Jacopo On Mar 28, 2013, at 6:43 PM, Nicolas Malin malin.nico...@librenberry.net wrote: Le 22/03/2013 17:19, Jacopo Cappellato a écrit : Of course we can still decide to issue a release of specialpurpose components separately. I worked on it, unit tests failed because specialpurpose components load some data needing. I continued the investigation but by lack of time I didn't solve the problem. I hope good, Nicolas -- Nicolas MALIN Consultant Tél : 06.17.66.40.06 Site projet : http://www.neogia.org/ --- Société LibrenBerry Tél : 02.48.02.56.12 Site : http://www.librenberry.net/
[jira] [Assigned] (OFBIZ-5165) Broken renderLabel functionality of screenfop view handler
[ https://issues.apache.org/jira/browse/OFBIZ-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Vijaywargiya reassigned OFBIZ-5165: -- Assignee: Ashish Vijaywargiya Broken renderLabel functionality of screenfop view handler -- Key: OFBIZ-5165 URL: https://issues.apache.org/jira/browse/OFBIZ-5165 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release Branch 10.04, Release 10.04, SVN trunk, Release Branch 12.04 Reporter: Deepak Dixit Assignee: Ashish Vijaywargiya Priority: Minor Fix For: Release Branch 10.04, Release Branch 11.04, SVN trunk, Release Branch 12.04 Attachments: OFBIZ-5165.patch, OFBIZ-5165-R10.04.patch If we use label inside widget tag then renderLabel macro skip the label rendering due to wrong condition check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: svn commit: r1461709 - in /ofbiz/trunk: ./ framework/base/lib/ framework/base/lib/ant/
Hi Jacopo, All the notes I put were in the Jira https://issues.apache.org/jira/browse/OFBIZ-4833 HTH Jacques From: Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com Jacques, as a side note, I know that you have recently worked at cleaning up some jars etc... if in the process you have put together some notes about jars dependencies, jar status etc... I'd love to get that as I am reviewing the jars we distribute to see if we need to upgrade them. Thanks, Jacopo On Mar 28, 2013, at 9:31 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Deal Thanks! Jacques From: Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com Hi Jacques, I don't think we discussed this specifically, and I am actually not even sure this naming convention is the best approach we could adopt: all I know it works well for Tomcat (now upgrading Tomcat is rather simple while in the past it was a pain... but this is also a consequence of the switch I did some time ago to the embedded distribution, available in the new releases) and so I decided to use it while I was upgrading Ant (because its jar files were missing any release information) The new format is nice because from the first part of the jar name you can understand from which release file we got it, while the second part is the original name of the jar (as found in the release file). We can see how it works in the next months and see if we like it, before discussing and making it a rule; or if you want we can discuss it now and see if the community can come up with a solution. Another important reason I have adopted it for Ant is that there are other jar files for Ant that don't come from the Ant distribution (e.g. ant-contrib*, ant-nodeps*) and they currently have a different release number as suffix: now it is easier to distinguish between them and the jars in the core distribution (because the jars from the core distribution now have the prefix ant-1.9.0-) I hope I was able to explain my reasonings adequately. Jacopo On Mar 27, 2013, at 10:55 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi Jacopo, I'm not against this new way of naming jars (I'm even for it) but where did we discuss this? Thanks Jacques From: jaco...@apache.org Author: jacopoc Date: Wed Mar 27 17:01:12 2013 New Revision: 1461709 URL: http://svn.apache.org/r1461709 Log: Upgrade from Ant 1.8.4 to Ant 1.9.0: in the process I have also switched the naming convention of jars to the new one we are adopting for example for Tomcat jars that is NAME-OF-THE-EXTERNAL-PROJECT-RELEASE-NUMBER-ORIGINAL-NAME-OF-JAR-FILE. For example, in in the release package apache-ant-1.9.0.zip we have the jar ant-launcher.jar, the name of the jar in OFBiz is: ant-1.9.0-ant-launcher.jar Added: ofbiz/trunk/framework/base/lib/ant-1.9.0-ant-junit.jar (with props) ofbiz/trunk/framework/base/lib/ant-1.9.0-ant-launcher.jar (with props) ofbiz/trunk/framework/base/lib/ant-1.9.0-ant.jar (with props) ofbiz/trunk/framework/base/lib/ant/ant-1.9.0-ant-apache-bsf.jar (with props) Removed: ofbiz/trunk/framework/base/lib/ant-1.8.4.jar ofbiz/trunk/framework/base/lib/ant-junit-1.8.4.jar ofbiz/trunk/framework/base/lib/ant-launcher-1.8.4.jar ofbiz/trunk/framework/base/lib/ant/ant-apache-bsf-1.8.4.jar Modified: ofbiz/trunk/.classpath ofbiz/trunk/LICENSE ofbiz/trunk/ant Modified: ofbiz/trunk/.classpath URL: http://svn.apache.org/viewvc/ofbiz/trunk/.classpath?rev=1461709r1=1461708r2=1461709view=diff == --- ofbiz/trunk/.classpath (original) +++ ofbiz/trunk/.classpath Wed Mar 27 17:01:12 2013 @@ -17,10 +17,10 @@ classpathentry kind=lib path=applications/content/lib/tika-parsers-1.0.jar/ classpathentry kind=lib path=applications/product/lib/watermarker-0.0.4.jar/ classpathentry kind=lib path=applications/product/lib/dozer-4.2.1.jar/ -classpathentry kind=lib path=framework/base/lib/ant-1.8.4.jar/ -classpathentry kind=lib path=framework/base/lib/ant-junit-1.8.4.jar/ -classpathentry kind=lib path=framework/base/lib/ant-launcher-1.8.4.jar/ -classpathentry kind=lib path=framework/base/lib/ant/ant-apache-bsf-1.8.4.jar/ +classpathentry kind=lib path=framework/base/lib/ant-1.9.0-ant.jar/ +classpathentry kind=lib path=framework/base/lib/ant-1.9.0-ant-junit.jar/ +classpathentry kind=lib path=framework/base/lib/ant-1.9.0-ant-launcher.jar/ +classpathentry kind=lib path=framework/base/lib/ant/ant-1.9.0-ant-apache-bsf.jar/ classpathentry kind=lib path=framework/base/lib/ant/ant-nodeps-1.8.1.jar/ classpathentry kind=lib path=framework/base/lib/antisamy-bin.1.2.jar/ classpathentry kind=lib path=framework/base/lib/avalon-framework-4.2.0.jar/ Modified: ofbiz/trunk/LICENSE URL:
[jira] [Closed] (OFBIZ-5165) Broken renderLabel functionality of screenfop view handler
[ https://issues.apache.org/jira/browse/OFBIZ-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Vijaywargiya closed OFBIZ-5165. -- Resolution: Fixed Committed patch in trunk and all the branches. Please check commit notifications. Thanks Deepak. -- Kind Regards Ashish Vijaywargiya Broken renderLabel functionality of screenfop view handler -- Key: OFBIZ-5165 URL: https://issues.apache.org/jira/browse/OFBIZ-5165 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release Branch 10.04, Release 10.04, SVN trunk, Release Branch 12.04 Reporter: Deepak Dixit Assignee: Ashish Vijaywargiya Priority: Minor Fix For: Release Branch 10.04, Release Branch 11.04, SVN trunk, Release Branch 12.04 Attachments: OFBIZ-5165.patch, OFBIZ-5165-R10.04.patch If we use label inside widget tag then renderLabel macro skip the label rendering due to wrong condition check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
buildbot success in ASF Buildbot on ofbiz-branch10
The Buildbot has detected a restored build on builder ofbiz-branch10 while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/ofbiz-branch10/builds/61 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: portunus_ubuntu Build Reason: scheduler Build Source Stamp: [branch ofbiz/branches/release10.04] 1462253 Blamelist: ashish Build succeeded! sincerely, -The Buildbot
[jira] [Commented] (OFBIZ-5165) Broken renderLabel functionality of screenfop view handler
[ https://issues.apache.org/jira/browse/OFBIZ-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13617032#comment-13617032 ] Deepak Dixit commented on OFBIZ-5165: - Thanks Ashish -- Deepak Dixit Broken renderLabel functionality of screenfop view handler -- Key: OFBIZ-5165 URL: https://issues.apache.org/jira/browse/OFBIZ-5165 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release Branch 10.04, Release 10.04, SVN trunk, Release Branch 12.04 Reporter: Deepak Dixit Assignee: Ashish Vijaywargiya Priority: Minor Fix For: Release Branch 10.04, Release Branch 11.04, SVN trunk, Release Branch 12.04 Attachments: OFBIZ-5165.patch, OFBIZ-5165-R10.04.patch If we use label inside widget tag then renderLabel macro skip the label rendering due to wrong condition check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
