Creating a new release branch in preparation for the new release

Hi all, I think it is the right time to create a new release branch out of the trunk. According to our naming conventions the release will be named "release16.09". Any objections or concerns? If not, I will create the branch later today/tomorrow. After that we will start, in a separate thread,

Re: Creating a new release branch in preparation for the new release

+1 On Wed, Sep 7, 2016 at 2:07 PM, Sharan Foga wrote: > That's great news ! +1 > > Thanks > Sharan > > > On 07/09/16 12:06, Jacopo Cappellato wrote: > >> Hi all, >> >> I think it is the right time to create a new release branch out of the >> trunk. >> >> According to our

Re: Taking a decision on remaining Jars in OFBiz

On Sat, Aug 20, 2016 at 8:29 AM, Jacopo Cappellato < jacopo.cappell...@hotwaxsystems.com> wrote: > > On Sat, Aug 20, 2016 at 7:57 AM, jler...@apache.org > wrote: > >> ... >> IMO we can delete the cmssite component jars they are only used in >> extensions of Dockbook and AFAIK

Re: Taking a decision on remaining Jars in OFBiz

Yes I see no problems with that. I just need to add directions for users before. I'll then remove the jars... very soon... Jacques Le 07/09/2016 à 13:09, Jacopo Cappellato a écrit : Jacques, any news from notsoserial? If not, I think we can proceed by (temporarily) removing the jars until

Re: Taking a decision on remaining Jars in OFBiz

Jacques, any news from notsoserial? If not, I think we can proceed by (temporarily) removing the jars until they will publish the jar. Regards, Jacopo On Sat, Aug 20, 2016 at 11:12 AM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Yes that's what I proposed also, I will try that

Re: svn commit: r1759457 - in /ofbiz/trunk/framework/webtools: config/webtools.properties src/main/java/org/apache/ofbiz/webtools/labelmanager/LabelReferences.java widget/LabelManagerScreens.xml

On Wed, Sep 7, 2016 at 9:23 AM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > ... > 2. So I created a private static final String: private static final String > getResourceRegex = "ServiceUtil\\.getResource\\(\\)" >But this did not work. I got > >2016-09-07 08:27:32,489

Re: svn commit: r1759457 - in /ofbiz/trunk/framework/webtools: config/webtools.properties src/main/java/org/apache/ofbiz/webtools/labelmanager/LabelReferences.java widget/LabelManagerScreens.xml

OK no problems with me, I'll change that. I must say I did no like the property either. Jacques Le 07/09/2016 à 09:56, Jacopo Cappellato a écrit : On Wed, Sep 7, 2016 at 9:23 AM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: ... 2. So I created a private static final String:

Re: Proposal for a more unified commit message format

BTW, when we initially spoke about "that" with Michael (before this thread while working on the monthly blog post) I thought that an easier way to generate the detailed Jira issues notes would be to use Jira itself. Unfortunately if this works well for releases, you can't filter dates on the

Re: Creating a new release branch in preparation for the new release

That's great news ! +1 Thanks Sharan On 07/09/16 12:06, Jacopo Cappellato wrote: Hi all, I think it is the right time to create a new release branch out of the trunk. According to our naming conventions the release will be named "release16.09". Any objections or concerns? If not, I will

Re: Taking a decision on remaining Jars in OFBiz

On Sat, Aug 20, 2016 at 11:10 AM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Le 20/08/2016 à 08:28, Jacopo Cappellato a écrit : > >> On Sat, Aug 20, 2016 at 7:57 AM, jler...@apache.org >> wrote: >> >> ... >>> ebaystore component we need to put in Attic? >>> >>>

Re: Taking a decision on remaining Jars in OFBiz

I think we can proceed in the following way: 1) remove the jar and the dependent Gradle code and move on with the release branches and release publication workflow 2) continue the discussion about what, where, how we want to document about nososerial (e.g. a message in our download page would be

Re: Taking a decision on remaining Jars in OFBiz

Hi Jacques, First of all the ofbizSecure task is gone instead everything calls the correct jvm arguments by default to fetch notsoserial. The work to remove notsoserial is almost nothing. You just to remove a few jvm args and that's it. Even if you don't remove the jvm args nothing happens

Re: Taking a decision on remaining Jars in OFBiz

Thank you Jacques and Taher. So it seems we can move on and temporarily remove the jar. Jacopo On Wed, Sep 7, 2016 at 5:11 PM, Taher Alkhateeb wrote: > Hi Jacques, > > First of all the ofbizSecure task is gone instead everything calls the > correct jvm arguments

Re: Taking a decision on remaining Jars in OFBiz

Huho, I was too fast on this. Currently the Gradle "ofbizSecure" tasks depends on the notsoserial-1.0-SNAPSHOT.jar So this would need more work and w/o answers from them I suspect they will not publish the jar. Now it's a serious security but not OOTB. So I see 2 possibilities. 1. Ask the

Re: Taking a decision on remaining Jars in OFBiz

OK, since we have no issues OOTB that can be done. But IMO documenting the whole thing in our nososerial readme.txt is not enough. We need to make that more prominent. Not sure how yet... Jacques Le 07/09/2016 à 20:09, Taher Alkhateeb a écrit : Scratch that, actually only the -D arguments

Re: Creating a new release branch in preparation for the new release

+1 Jacopo! Thanks, Michael Am 07.09.16 um 12:06 schrieb Jacopo Cappellato: Hi all, I think it is the right time to create a new release branch out of the trunk. According to our naming conventions the release will be named "release16.09". Any objections or concerns? If not, I will create

Re: [Supplier-Product] - How can apply more than one price for a product and a supplier.

Thanks! We still use last_price in supplier_product as default price. The new entities only using for special cases and we need setting up some trigger before order to save time. About screens, i'll take options for end user choosing, inside price will be calculate automatic and not change logical

Re: [Supplier-Product] - How can apply more than one price for a product and a supplier.

Hi Jacopo , I think using Agreement is ok with my case. But in small business, the agreement sometime not enough flexibility, transaction between the seller and the buyer only base on invoice and payment. The agreements only contains some rules basically. I will try. Thanks! On Wed, Sep 7, 2016

Re: Taking a decision on remaining Jars in OFBiz

Scratch that, actually only the -D arguments are ignored, we must remove the -javaagent argument because it's not a classpath argument and would crash the VM But for consistency's sake, let's remove them all for now. So simply we apply: Index: build.gradle

Re: Taking a decision on remaining Jars in OFBiz

OK Cool, if the JVM arguments are simply ignored, then I will proceed with an addition in the readme and remove the jar, simple Jacques Le 07/09/2016 à 17:16, Jacopo Cappellato a écrit : Thank you Jacques and Taher. So it seems we can move on and temporarily remove the jar. Jacopo On

Re: [Supplier-Product] - How can apply more than one price for a product and a supplier.

I decided using minimumOrderQuantity to check and apply price for order_item. Thanks all! Cheers! On Wed, Sep 7, 2016 at 1:29 PM, thang nguyen wrote: > Hi Jacopo , > I think using Agreement is ok with my case. But in small business, the > agreement sometime not

Re: svn commit: r1759457 - in /ofbiz/trunk/framework/webtools: config/webtools.properties src/main/java/org/apache/ofbiz/webtools/labelmanager/LabelReferences.java widget/LabelManagerScreens.xml

Le 06/09/2016 à 19:03, Jacopo Cappellato a écrit : On Tue, Sep 6, 2016 at 6:38 PM, wrote: Author: jleroux Date: Tue Sep 6 16:38:14 2016 New Revision: 1759457 URL: http://svn.apache.org/viewvc?rev=1759457=rev Log: ... * Moreover the string can't be in the