not sure what you saying. the demo-trunk is what I went to and got the message I included. so I assume, unless there is a script run after the svn command, that the certs in the svn have been changed. if a script is run after the svn to create the demo-trunk then that is where it needs to be changes.
I don't follow the svn much theses days, since nothing useful, to me, is being committed. the was meant as an FYI if someone wanted to research it. Jacques Le Roux sent the following on 5/21/2011 2:27 PM: > I also noticed that rmitrust.jks have been changed in trunk demo. svn st > ... > M framework/service/config/rmitrust.jks > ... > > I thought it has been purposely done by the infra team. You say that the > OOTB cert is good, or better right? > > Jacques > > From: "BJ Freeman" <bjf...@free-man.net> >> My guess is a committer has an old cert they committed. >> I think this is more an infra thing since they have the cert for >> apache.org >> so all committers should make sure they have the correct cert in their >> copy. >> >> Jacques Le Roux sent the following on 5/21/2011 9:14 AM: >>> HI BJ, >>> >>> Would you like to help on this? >>> >>> Jacques >>> >>> From: "BJ Freeman" <bjf...@free-man.net> >>>> demo-trunk.ofbiz.apache.org:8443 uses an invalid security certificate. >>>> >>>> The certificate is not trusted because the issuer certificate has >>>> expired. >>>> The certificate is only valid for ofbiz.apache.org >>>> The certificate expired on 7/6/2008 4:46 AM. >>>> >>>> >>>> >>>> ========================= >>>> BJ Freeman >>>> Strategic Power Office with Supplier Automation >>>> <http://www.businessesnetwork.com/automation/viewforum.php?f=52> >>>> Specialtymarket.com <http://www.specialtymarket.com/> >>>> Systems Integrator-- Glad to Assist >>>> >>>> Chat Y! messenger: bjfr33man >>>> >>> >>> > >
