Thanks for the explanation. Feel free to update the "Javadocs" section, I think it deserves it (it was not completely clear to me) and just let me know if there is something remaining for me to finish the process release... Best, Jérôme
2014-05-21 15:17 GMT+02:00 Misagh Moayyed <[email protected]>: > Definitely relevant, although the title should be changed to say > “Documentation Site” rather than javadocs. This is what I had to do to get > the github pages site functional for 4.0.0. Javadocs are now auto-deployed > to the development folder for all commits, but upon release, there is still > a bit of copying stuff around, which isn’t that big of a deal I guess. > > > > As for source links, this is the work of the maven site plugin. I’ll take > a look and see if we can tweak the urls. > > > > *From:* Jérôme LELEU [mailto:[email protected]] > *Sent:* Wednesday, May 21, 2014 5:46 AM > *To:* [email protected] > *Subject:* Re: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > Hi, > > > > I updated the Jasig web site with the new 4.0.0 CAS release artifacts (in > the download section). > > > > I'm not sure what to do for the "Javadocs" part (in > http://jasig.github.io/cas/developer/Release-Process.html), looks like > the Javadoc has already been uploaded for 4.0.0: > http://jasig.github.io/cas/4.0.0/javadocs/index.html. > > > > @misagh: I know you have worked hard on automation: is the "Javadocs" part > still relevant? By the way, I noticed that the source links are wrong, like > this one: > http://jasig.github.io/cas/4.0.0/javadocs/cas-server-core/source-repository.html > . > > > > Thanks. > > Best regards, > > Jérôme > > > > > > > > 2014-05-07 20:51 GMT+02:00 Jérôme LELEU <[email protected]>: > > Hi, > > > > I finally finished the release. I encountered some troubles: slow or > stopped process, but it might be my computer... > > At least, I noticed the the check on NOTICE files is not disabled during > the release. I created a JIRA to fix that for the next release: > https://issues.jasig.org/browse/CAS-1450. > > > > The master has been upgraded to version 4.1.0-SNAPSHOT and I created a > 4.0.x branch (which is now at version 4.0.1-SNAPSHOT). > > > > I ran out of time to finish the release process and will perform the "Post > Release" tasks on Monday (I have a few days off). > > > > I will send an official announcement in a few minutes. > > > > Best regards, > > Jérôme > > > > > > 2014-05-07 9:06 GMT+02:00 Jérôme LELEU <[email protected]>: > > Hi, > > > > I'm about to merge: https://github.com/Jasig/cas/pull/430 and start the > release of CAS server 4.0.0. > > > > Raise your hand if you have any concern / problem... > > > > Best regards, > > Jérôme > > > > > > 2014-05-05 19:13 GMT+02:00 Misagh Moayyed <[email protected]>: > > Thanks. Just wanted to make sure that oauthwrapper components can still be > used in CAS4 for enabling Oauth server support. > > > > I am revising the documentation a bit and fixing a few formatting issues. > I’ll post back when things are near done so you can review and make > adjustments. > > > > *From:* Jérôme LELEU [mailto:[email protected]] > *Sent:* Monday, May 05, 2014 10:06 AM > *To:* [email protected] > *Subject:* Re: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > Hi, > > > > Yes, indeed, pac4j is only meant to be used as a client for different > protocols (OAuth, OpenID, CAS...) and everything should be explained > properly in "Delegate authentication" (from the client side point of view): > http://jasig.github.io/cas/current/integration/Delegate-Authentication.html > . > > Though, the OAuth server support remains and can still be used reading the > "OAuth protocol" documentation: > http://jasig.github.io/cas/current/protocol/OAuth-Protocol.html. > > > > It might not be clear enough, but I didn't find any better documentation > organization. > > Just let me know if you have a better idea... > > > > Best regards, > > Jérôme > > > > > > 2014-05-05 18:45 GMT+02:00 Misagh Moayyed <[email protected]>: > > Jérôme, > > I am reviewing the documentation for OAuth/OpenID and pac4j on the > existing wiki, and all references seem to indicate that CAS with pac4j will > act as an Oauth client only. Is that correct? Is the ability to have CAS > behave like an Oauth provider dropped, or do we have docs that explain what > needs to be done for CAS4? > > > > Misagh > > > > *From:* Jérôme LELEU [mailto:[email protected]] > *Sent:* Monday, May 05, 2014 8:19 AM > *To:* [email protected] > *Subject:* Re: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > Hi, > > > > I've struggled hard to find a fix. > > > > As I used Memcached locally, the setup was not easy and I discovered that > unmodifiable lists are not serializable: I think it's worth a JIRA for a > 4.0.x / 4.1, doesn't it? > > > > I was not able to make the JSTL stuffs completely work. The solution is > partly written in scriptlet in the JSP page. Here is the JIRA: > https://issues.jasig.org/browse/CAS-1448 and the pull: > https://github.com/Jasig/cas/pull/430. > > > > Feedbacks are welcome. > > Thanks. > > Best regards, > > Jérôme > > > > > > 2014-05-05 11:29 GMT+02:00 Jérôme LELEU <[email protected]>: > > Hi, > > > > OK. Noticed. > > Though, another test leads me to find a strange behaviour. If you have a > user attribute with commas (like "Jérôme, LELEU"), two attributes will be > returned instead of one. > > It comes from the fact that the success validation JSP page uses the > forEach (of the JSTL) where Strings delimited by commas are considered as > multiple elements. > > > > I will provide a fix before doing the release. > > Thanks. > > Best regards, > > Jérôme > > > > > > > > 2014-05-01 20:28 GMT+02:00 Robert Oschwald <[email protected] > >: > > ok with me. > > Whoever creates the release, please merge my PL in, first. > > > > Thanks, > > Robert > > Sent while mobile. > > > Am 01.05.2014 um 17:24 schrieb Misagh Moayyed <[email protected]>: > > Sounds good to me. Shall we put down Monday May 5th then? > > > > I’ll take care of javadocs, documentation, and stake a stab at updating > the protocol doc over at http://www.jasig.org/cas/protocol once v3 is > released. > > > > *From:* Robert Oschwald > [mailto:[email protected]<[email protected]>] > > *Sent:* Thursday, May 01, 2014 1:01 AM > *To:* [email protected] > *Subject:* Re: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > on monday, I will commit the spec as 3.0 release as well. > > Sent while mobile. > > > Am 01.05.2014 um 09:54 schrieb Jérôme LELEU <[email protected]>: > > Hi, > > > > Misagh has just merged the last fix for 4.0 ( > https://github.com/Jasig/cas/pull/427). > > I will cut the release next week: on Monday (4/5/14) or Wednesday (4/7/14) > if everyone is ok. > > Thanks. > > Best regards, > > Jérôme > > > > > > 2014-04-17 18:26 GMT+02:00 Misagh Moayyed <[email protected]>: > > Yes that’s the thought. 28th would also be fine. There has been some > discussion on #246, and so as soon as we are able to resolve that, we > should be ok to proceed with GA, if the timing is acceptable. > > > > *From:* Jérôme LELEU [mailto:[email protected]] > *Sent:* Thursday, April 17, 2014 1:17 AM > *To:* [email protected] > *Subject:* Re: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > Hi, > > > > Are you proposing to cut the final release (GA) on April, the 25th? I > agree, it's time to release the 4.0, even if it could be done one or two > weeks later... > > > > BTW, I'm willing to do the release, but as I'm in holidays, I can only > handle that from April, the 28th. > > > > Thanks. > > Best regards, > > Jérôme > > > > > > 2014-04-16 19:22 GMT+02:00 Misagh Moayyed <[email protected]>: > > Team, > I suppose the last change that we need to review and take action on is the > following pull: > https://github.com/Jasig/cas/pull/426 > > May I suggest that once the fate of this pull is decided, we'd take action > to proceed with the GA? And with that, could we perhaps agree on a > timeline, or say, Friday the 25th? This would give us 3 weeks before the > last RC which should be enough time to weed out issues. > > Misagh > > > -----Original Message----- > > From: Misagh Moayyed [mailto:[email protected]] > > Sent: Wednesday, April 02, 2014 12:06 PM > > To: '[email protected]' > > Subject: RE: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > Also, I realize now it makes better sense for the build to check for > commit > > messages and adherence to other conventions *after* it's been able to > > successfully build and test the pull. We would have been able to capture > the > > failure in advance. > > > > > -----Original Message----- > > > From: Misagh Moayyed [mailto:[email protected]] > > > Sent: Wednesday, April 02, 2014 12:02 PM > > > To: [email protected] > > > Subject: RE: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > > > Another issue; pull #415 [1] broke the following test in > cas-server-core: > > > MultifactorAuthenticationTests#testAllowsAccessToHighSecurityServiceWi > > > thPa > > > sswordAndOTPViaRenew() > > > > > > This is where the test failure comes from: > > > > > > if (!(current.getPrincipal().equals(original.getPrincipal()) > > > && current.getAttributes().equals(original.getAttributes()))) { > > > throw new MixedPrincipalException(current, > > > current.getPrincipal(), original.getPrincipal()); } > > > > > > The comparison on authentication attribute fails. What is the > intention > > here? > > > Should the principal attributes be compared if we are checking for > > > mixed principal conditions? If so, should that just be captured inside > > > the > > > equals() of SimplePrincipal? > > > > > > [1] https://github.com/Jasig/cas/pull/415 > > > > > > > -----Original Message----- > > > > From: Misagh Moayyed [mailto:[email protected]] > > > > Sent: Wednesday, April 02, 2014 10:10 AM > > > > To: '[email protected]' > > > > Subject: RE: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > > > > > Excellent. I'll get going. > > > > > > > > > -----Original Message----- > > > > > From: Marvin Addison [mailto:[email protected]] > > > > > Sent: Wednesday, April 02, 2014 10:04 AM > > > > > To: [email protected] > > > > > Subject: Re: [cas-dev] [cas-user] Schedule for CAS 4.0 > > > > > > > > > > > Thanks. Keep us posted on the progress please. > > > > > > > > > > Ldaptive 1.0.3 has been released and is available in Maven Central > > > > > [1], so we should be good to bump the version and move forward. > > > > > > > > > > M > > > > > > > > > > http://search.maven.org/#artifactdetails%7Corg.ldaptive%7Cldaptive > > > > > %7 > > > > > C1 > > > > > .0.3%7C > > > > > jar > > > > > > > > > > -- > > > > > You are currently subscribed to [email protected] as: > > > > > [email protected] To unsubscribe, change settings or access > > > > > archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > > > > -- > > > You are currently subscribed to [email protected] as: > > > [email protected] To unsubscribe, change settings or access > > > archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > > > > -- > > You are currently subscribed to [email protected] as: > [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > > You are currently subscribed to [email protected] as: [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > > -- > > You are currently subscribed to [email protected] as: > [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > > -- > > You are currently subscribed to [email protected] as: > [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > > > > -- > > You are currently subscribed to [email protected] as: > [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > > You are currently subscribed to [email protected] as: [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > > > > > > -- > > You are currently subscribed to [email protected] as: > [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > > You are currently subscribed to [email protected] as: [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > > > > -- > > You are currently subscribed to [email protected] as: > [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > > You are currently subscribed to [email protected] as: [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > > > > > > > > -- > > You are currently subscribed to [email protected] as: > [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > You are currently subscribed to [email protected] as: [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
