I've been adding the overlays folders to the ignore folder list for the portlet projects I've been creating releases in. I suggest doing the same for uPortal.
----- Original Message ----- From: "Andrew Petro" <[email protected]> To: [email protected] Sent: Tuesday, December 30, 2014 12:19:33 PM Subject: Re:[uportal-dev] uPortal release choking on missing headers in CSS files from overlay Aha! Those are IntelliJ helpfully generated source paths rather than real source paths. Working against a clean checkout without ever pointing IntelliJ at it may be fruitful... On Tue Dec 30 2014 at 1:04:16 PM Andrew Petro < [email protected] > wrote: So, I'm trying to cut that 4.2.0-M1 release. On mvn release:prepare, I get a bunch of errors like this: [INFO] Missing header in: /Users/apetro/code/github_jasig/uPortal/uportal-portlets-overlay/jasig-widget-portlets/overlays/org.jasig.portlet.jasig-widget-portlets-2.1.5/rs/fluid/1.5.0/fss/css/fss-theme-lgdg.min.css [INFO] Missing header in: /Users/apetro/code/github_jasig/uPortal/uportal-portlets-overlay/jasig-widget-portlets/overlays/org.jasig.portlet.jasig-widget-portlets-2.1.5/rs/fluid/1.5.0/fss/css/fss-theme-rust.css So, it seems unhappy about missing headers in CSS files that it's getting via overlay. Hints on how to resolve that? Bumping jasig-parent to the same version as that in jasig-widget-portlets didn't help. Andrew On Mon Dec 29 2014 at 11:28:52 AM James Wennmacher < [email protected] > wrote: <blockquote> Did a quick query. Looks like 62 issues resolved in 4.2.0 and not in 4.0.x or 4.1.x. This might be missing a few. I recall a few pull requests were processed without marking the Jira issues resolved (the release process should manually go back and look for those). Quick glance is that I see primary changes include: * transient layout portlet changes * lightbox config for portlets in regions * hover chrome for portlets without chrome * marketplace improvements * some changes to dynamic skin in Respondr * Tin Can API * Client-side session timeout pop-up * Groovy compilation improvements in build (though nothing takes advantage of this yet) * Legal footer from JSP to Simple Content Portlet * REST API enhancements, primarily driven by Marketplace portlet * Upgrading of internal and bundled portlets to use newer jQuery versions (also picks up some nicer UI changes in some portlets) https://issues.jasig.org/ browse/UP-4360?jql=resolution% 20%3D%20Fixed%20and% 20fixVersion%20%3D%204.2.0% 20and%20fixVersion%20not%20in% 20(4.0.14%2C%204.0.15%2C%204. 0.16%2C%204.1.0%2C%204.1.1%2C% 204.1.2%2C%204.1.3) One note is to do a release I think the license header change from Jasig to Apereo will pop up (it has in the portlet project releases). That means we'll have a change to most files as part of the release milestone unless we decide to push that off. From: "Andrew Petro" < [email protected] > To: [email protected] Sent: Monday, December 29, 2014 7:11:05 AM Subject: [uportal-dev] uPortal 4.2 release march I'd like to cut a 4.2.0-M1 milestone release in the next 24 hours or so, see if master is feeling like enough progress since 4.1 to be worth releasing. Andrew <blockquote> -- 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/uportal-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/uportal-dev </blockquote> </blockquote> -- 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/uportal-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/uportal-dev
