I'm working on mavenizing the trunk of uPortal and have run into a few questions I'd like to pose to the group.
The big one is packaging. Using maven for build management really lends itself to generating an EAR since it allows multiple WARs (uPortal and each portlet app) and shared libraries. For uPortal 3 sandbox development we already have an EAR -> Tomcat deployer tool which puts the WARs and JARs in the correct locations. The problem with the EAR approach is it does not (as far as I can tell) allow for differentiation of what libraries are shared by just the WARs (pluto) and what libraries need to be shared with the servlet container (jdbc driver for JNDI datasource). I'm not quite sure what to do about this. We don't really need to use JNDI for the DataSource in the quickstart / out of the box configuration but providing a way to do it without having to come up with a custom development process would be very good. Discussion and suggestions are both welcome. -Eric
smime.p7s
Description: S/MIME Cryptographic Signature
