Re: Build failed

Ahhh I see the tests were dependant on the remote dtds. Weird design On Mon, Oct 1, 2018, 11:18 PM Deepak Dixit wrote: > I am sure that this is due to the changes done in the ofbiz website, After > updating the redirect rule condition it's fixed. > http to https redirect affect all the older

Re: Build failed

I am sure that this is due to the changes done in the ofbiz website, After updating the redirect rule condition it's fixed. http to https redirect affect all the older version as well, all the ofbiz versions usinging http://ofbiz.apache.org/dtds/* as a namespace. Thanks Benjamin Jugl and Pierre

Re: Build failed

I have a feeling this has nothing to do with this commit, I have an older working copy that is also crashing. This could mean that the problem is somewhere in the gradle dependencies, something corrupted or wrong in JCenter perhaps? On Mon, Oct 1, 2018 at 4:42 PM Deepak Dixit wrote: > > This

Re: Build failed

This should be fixed at r#1842499 Here is the ticket for further work as mentioned by Michale. https://issues.apache.org/jira/browse/OFBIZ-10590 Thanks & Regards -- Deepak Dixit On Mon, Oct 1, 2018 at 5:59 PM, Pierre Smits wrote: > Upgrading the references in the code base to >

Re: Build failed

Upgrading the references in the code base to https://ofbiz.apache.org/dtds/entity-config.xsd should do the trick, correct? Best regards, Pierre Smits *Apache Trafodion , Vice President* *Apache Directory , PMC Member* Apache Incubator

Re: Build failed

Yes, you are right, Deepak. Renaming only works for coming releases. So wee need exceptional conditions for the https redirect. Better file a Jira and collect what we have to serve on the http port, there might be other resources as well (no time to check now). Thanks, Michael Am

Re: Build failed

+1 Thanks, Michale, We can do for newer releases/trunk. But for older releases, we need to have backward compatibility as well. Thanks & Regards -- Deepak Dixit On Mon, Oct 1, 2018 at 5:23 PM, Michael Brohl wrote: > I think we should consequently rename the schema location and any other >

Re: Build failed

I think we should consequently rename the schema location and any other resources depending on the official website to the https address. Regards, Michael Am 01.10.18 um 13:41 schrieb Deepak Dixit: I think its due to changes done at r#1842437 While build using debug mode found following

Re: Build failed

Or use, what we have and disable tests via gradle:  ./gradlew ofbiz -x test Am 01.10.18 um 13:43 schrieb Hannes Geist: Ok, easy solution: rename framework/entity/src/test to framework/entity/src/test_ for now. -Original Message- From: Hannes Geist Reply-to: h...@hgeist.com

Re: Build failed

Ok, easy solution: rename  framework/entity/src/test  to  framework/entity/src/test_  for now. -Original Message- From: Hannes Geist Reply-to: h...@hgeist.com To: dev@ofbiz.apache.org Subject: Re: Build failed Date: Mon, 01 Oct 2018 13:39:21 +0200 Same. Is there any way to disable

Re: Build failed

I think its due to changes done at r#1842437 While build using debug mode found following warning 17:04:57.839 [DEBUG] [TestEventLogger] 2018-10-01 17:04:57,839 |Test worker |UtilXml |W| [UtilXml.LocalResolver.resolveEntity] could not find

Re: Build failed

Same. Is there any way to disable the Test system for now? I tried commenting out all test-suite entries in components already, doesnt work. I need the system urgently for a customer demo. Best regards Hannes Geist -Original Message- From: Pritam Kute Reply-to: dev@ofbiz.apache.org

Re: Build failed

Same here. About to write an email. :) Thanks and Regards -- Pritam Kute On Mon, Oct 1, 2018 at 4:43 PM Suraj Khurana < suraj.khur...@hotwaxsystems.com> wrote: > Hello team, > > I am getting this exception after re-starting OFBiz server. I used > ./gradlew cleanAll ofbiz and got this exception:

Build failed

Hello team, I am getting this exception after re-starting OFBiz server. I used ./gradlew cleanAll ofbiz and got this exception: === :test org.apache.ofbiz.entity.util.EntitySaxReaderTests > parse FAILED java.lang.IllegalStateException at

Re: "Not Secure" in the Google Chrome browser

Hi All, Verified 'https://ofbiz.apache.org', it is working fine. Thanks & Regards -- Deepak Nigam HotWax System Pvt. Ltd On Mon, Oct 1, 2018 at 2:35 PM Michael Brohl wrote: > Thank you, Deepak! > > Regards, > > Michael > > > Am 01.10.18 um 10:25 schrieb Deepak Dixit: > > Thanks Michael, > >

Re: "Not Secure" in the Google Chrome browser

Thank you, Deepak! Regards, Michael Am 01.10.18 um 10:25 schrieb Deepak Dixit: Thanks Michael, I just discuss this with our sysadmin, and he suggests the same as your solution :) Let me commit this. Thanks & Regards -- Deepak Dixit On Mon, Oct 1, 2018 at 1:45 PM, Michael Brohl wrote:

Re: "Not Secure" in the Google Chrome browser

This has been done at r#1842437, and it's working fine. Thanks & Regards -- Deepak Dixit On Mon, Oct 1, 2018 at 1:55 PM, Deepak Dixit wrote: > Thanks Michael, > > I just discuss this with our sysadmin, and he suggests the same as your > solution :) > > Let me commit this. > > > Thanks &

Re: "Not Secure" in the Google Chrome browser

Thanks Michael, I just discuss this with our sysadmin, and he suggests the same as your solution :) Let me commit this. Thanks & Regards -- Deepak Dixit On Mon, Oct 1, 2018 at 1:45 PM, Michael Brohl wrote: > Hi Deepak, > > I would suggest > > === > > RewriteCond %{HTTPS} off > RewriteRule

Re: "Not Secure" in the Google Chrome browser

Hi Deepak, I would suggest === RewriteCond %{HTTPS} off RewriteRule ^\/?(.*)$ https://%{HTTP_HOST}/$1 [R=301,L] === 1st statement just checks if https is not active, independent of the ports used. 2nd statement does a 301 redirect telling Google that it is permanent. Regards, Michael

Re: "Not Secure" in the Google Chrome browser

Thanks Deepak, +1 Jacques Le 01/10/2018 à 08:32, Deepak Dixit a écrit : Thanks Jacques, Following rule should work. = RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://ofbiz.apache.org/$1 [R,L] = Please confirm if it looks good. Thanks & Regards -- Deepak

Re: "Not Secure" in the Google Chrome browser

Thanks Jacques, Following rule should work. = RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://ofbiz.apache.org/$1 [R,L] = Please confirm if it looks good. Thanks & Regards -- Deepak Dixit On Mon, Oct 1, 2018 at 11:45 AM, Jacques Le Roux <

Re: "Not Secure" in the Google Chrome browser

That's quite a  good idea Deepak Jacques Le 01/10/2018 à 07:30, Deepak Dixit a écrit : We have .htaccess file, we can write redirect rule in this file. Thanks & Regards -- Deepak Dixit On Sun, Sep 30, 2018 at 3:51 PM, Ashish Vijaywargiya < ashish.vijaywarg...@hotwaxsystems.com> wrote: