Re: [uportal-dev] Idea for uportal-bundle

[Anthony Colebourne]

FYI this is exactly what I've done locally, I called mine 
manchetser-ear. It contains the same sub modules as yours!


I also use this project to store my quickstart_entities / 
manchester_entities.


... Once I've filtered my overlayed portlets and uPortal I either
1) don't want to leave then lying around in the .m2 directory
or
2) I do want them laying around in .m2 to save re-filtering next time 
when all I've done is update a single portlet version. In this case I 
need to ensure that artifacts filters for UAT do not accidentally get 
included in a bundle filtered for PROD.


... I'm not sure whether skip-deploy, skip-install on each portlet would 
break the overlay system?


... ultimately I want to move away from filtering completely and use 
paths to external properties files so I can truly have 1 build for all 
environments.


-- Anthony.

On 09/06/15 19:41, Tim Levett wrote:

Hi Devs,


One topic that came up during the uPortal BoF was moving bundled
portlets out of the portal project. We all recognized the benefit of the
bundle, but also realized this could be a separate project that pulled
in the needed dependencies.


I took a stab at pulling out the important bits of the bundling and
building of the EAR and put it up on github here:
https://github.com/timlevett/uportal-bundle .


What are your thoughts?  Should we move this project into Jasig and move
forward?


Thanks,


Tim Levett
tim.levettATwisc.edu
MyUW-Infrastructure

--

You are currently subscribed to uportal-dev@lists.ja-sig.org as: 
anthony.colebou...@manchester.ac.uk
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev



--
You are currently subscribed to uportal-dev@lists.ja-sig.org as: 
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Re:[uportal-dev] Idea for uportal-bundle

[Andrew W Petro]

Tim,


Thanks for this.


I'm hungry for a solution that:


1. Simplifies the GitHub project named uPortal

2. Makes it more feasible to fork / depend upon that simpler uPortal

3. Continues to also deliver a rich bundled offering, and

4. Makes maintaining both of these things feasible.


This uportal-bundle looks an awful lot like the heavy bundle that ought to 
accompany a much lighter base uPortal, and it looks like it would make 
meeting both use cases more cleanly than currently quite feasible.


Which is to say, I think you've hit upon a solution that does all of 1-4 of 
above.


So, yes, I'd favor moving this project into the Jasig GitHub ownership and 
moving forward with lightening the uPortal repo and ensuring that the 
uportal-bundle repo meets the use cases that uPortal stops meeting in that 
lightening.


Kind regards,


Andrew




From: bounce-41568595-81063...@lists.wisc.edu 
bounce-41568595-81063...@lists.wisc.edu on behalf of Tim Levett 
tim.lev...@wisc.edu
Sent: Tuesday, June 9, 2015 1:41 PM
To: uportal-dev@lists.ja-sig.org
Subject: [uportal-dev] Idea for uportal-bundle


Hi Devs,


One topic that came up during the uPortal BoF was moving bundled portlets out 
of the portal project. We all recognized the benefit of the bundle, but also 
realized this could be a separate project that pulled in the needed 
dependencies.


I took a stab at pulling out the important bits of the bundling and building of 
the EAR and put it up on github here: 
https://github.com/timlevett/uportal-bundle .


What are your thoughts?  Should we move this project into Jasig and move 
forward?


Thanks,


Tim Levett
tim.levettATwisc.edu
MyUW-Infrastructure


--

You are currently subscribed to uportal-dev@lists.ja-sig.org as: 
andrew.pe...@wisc.edu
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

-- 
You are currently subscribed to uportal-dev@lists.ja-sig.org as: 
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev