Hi Georg, I tried moving testcontainer and factory to Junit5 - not too hard, but it will cause a cascade of changes that I think requires updating all related packages to Junit5 at the same time.... seems like a big effort and I don't have the time to invest on that right now :-( As soon as I updated testcontainer, yaafi started complaining, etc.
I took your lead on updates for yaafi-crypto pom changes and made them across all fulcrum modules. I also simplified a small bit of code in the yaafi-crypto hex conversion lib. I will try to package for release again and see how it goes! - Jeffery On 11/7/18 6:02 AM, Georg Kallidis wrote: > Hi Jeffery, > > thanks a lot for your efforts! I do my best to allow for enabling next > steps -I may be able to check middle of next week for the latest. > > Where to begin? Factory and Testcontainer? > > - I considered to allow for Junit5 (+ Junit 4) in Fulcrum testcontainer > release, may be we want this included or not? I think yes. > - minor version for Fulcrum Factory (code could be done more in Java 8 > syntax), check src/changes/changes.xml > > - Fulcrum Yaafi: Thomas mentioning "avalon" - yes it is "as it is", kind > of stable, but the code is in attic (excalibur). Thomas may come up with > some more helpful hints7suggestions (Spring?). Keeping this as it is for > now.. > > - For the atticable Fulcrums, we may move them to a dormant folder (like > commons) after a vote (list of candidates).. > > Best regards, Georg > > > > Von: Jeffery Painter <[email protected]> > An: [email protected] > Datum: 06.11.2018 19:19 > Betreff: Re: Fulcrum javadoc updates > > > > Hello all, > > I think I have mostly finished making the fulcrum javadoc updates :-) > > "mvn clean site" works for all of the following now: > > fulcrum-commonsemail (attic?) > fulcrum-configuration/impl (attic?) > fulcrum-crypto > fulcrum-factory > fulcrum-hsqldb (attic?) > fulcrum-intake > fulcrum-jetty > fulcrum-json (and all sub components) > fulcrum-localization > fulcrum-mimetype > fulcrum-parser > fulcrum-pbe (attic?) > fulcrum-pool > fulcrum-quartz > fulcrum-naming (attic?) > fulcrum-resourcemanager (attic?) > fulcrum-script (attic?) > fulcrum-security/api > fulcrum-security/dist > fulcrum-security/hibernate > fulcrum-security/memory > fulcrum-servicemanager > fulcrum-spring (attic?) > fulcrum-testcontainer > fulcrum-upload > fulcrum-xmlrpc (attic?) > fulcrum-xslt (attic?) > fulcrum-yaafi > fulcrum-yaafi-crypto > > Needs some help: > > fulcrum-security/torque > > The generated Torque.OM classes are the only ones left with offending > JavaDoc entries, I cleaned up the rest. I can run mvn javadoc:javadoc > and it plays nicely with the exclusions I put into the pom.xml, however > they are ignored when running full "mvn clean site". I haven't spent > any more time investigating this. > > Does not complete or maybe move to attic... > fulcrum-bsf (attic? no tests, site build does not work) > > Georg - whenever you are ready, I think we can start putting most of > these up for release and voting. Let me know how I can help :-) > > > Thanks! > Jeff > > > > On 11/5/18 12:51 PM, Jeffery Painter wrote: >> Progress update: >> >> "mvn clean package site" builds OK now for the following: >> >> fulcrum-crypto >> fulcrum-factory >> fulcrum-intake >> fulcrum-json (and all sub components) >> fulcrum-localization >> fulcrum-mimetype >> fulcrum-parser >> fulcrum-pbe >> fulcrum-pool >> fulcrum-quartz >> fulcrum-servicemanager >> fulcrum-testcontainer >> fulcrum-yaafi >> fulcrum-yaafi-crypto >> >> >> I still have to tackle fulcrum-security (lots of problems there) and >> fulcrum-upload. Haven't looked beyond that yet. >> >> -- >> Jeff >> >> > > [Anhang "signature.asc" gelöscht von Georg Kallidis/CeDiS/FU-Berlin/DE] >
signature.asc
Description: OpenPGP digital signature
