[09:05:54 CDT(-0500)] <brandon> hello
[09:08:10 CDT(-0500)] <brandon> why don't the edit links for my portlets show up in the default uportal
[09:59:25 CDT(-0500)] <EricDalquist> good morning
[12:00:39 CDT(-0500)] <brandon> hello
[12:00:49 CDT(-0500)] <EricDalquist> hello
[12:00:52 CDT(-0500)] <brandon> i'm having a problem deploying the weather portlet
[12:01:07 CDT(-0500)] <EricDalquist> ok
[12:01:27 CDT(-0500)] <brandon> i removed the default one and setup the recent one from the trunk: https://source.jasig.org/portlets/WeatherPortlet
[12:02:04 CDT(-0500)] <brandon> then i want to deploy it by adding it to uportal's portlet overlay
[12:02:27 CDT(-0500)] <brandon> it's in there but when i run a ant clean deploy-ear it looks like it is deploying the old one
[12:02:49 CDT(-0500)] <brandon> but if i do a regular ant deployPortletApp, it deploys the (correct) updated one
[12:03:14 CDT(-0500)] <EricDalquist> how exactly did you add it to the portlet overlay?
[12:04:39 CDT(-0500)] <brandon> followed these steps: https://wiki.jasig.org/display/UPM32/Deploying+Portlets+to+uPortal
[12:05:11 CDT(-0500)] <brandon> created a WeatherPortlet folder and put the files from the svn trunk into it
[12:05:20 CDT(-0500)] <brandon> didn't create a pom.xml because it came with one
[12:05:54 CDT(-0500)] <EricDalquist> so an overlay is meant for deploying a portlet that exists as a maven artifact somewhere already
[12:06:02 CDT(-0500)] <EricDalquist> since uPortal already comes with a bookmarks portlet overlay
[12:06:16 CDT(-0500)] <EricDalquist> to use the trunk version you need to check out the weather portlet trunk into its own projecty
[12:06:36 CDT(-0500)] <EricDalquist> run "mvn clean install" to install the portlet artifact into your local maven repo
[12:06:47 CDT(-0500)] <EricDalquist> then update the version number for the bookmarks portlet in the root uPortal pom.xml
[12:06:54 CDT(-0500)] <EricDalquist> NOTE that this will only be effective on one machine
[12:07:13 CDT(-0500)] <brandon> run it from the root of the uportal src folder?
[12:07:45 CDT(-0500)] <EricDalquist> run "mvn clean install" from the root of the WeatherPortlet's code that you checked out into its own project (completely unrelated to uPortal)
[12:07:54 CDT(-0500)] <brandon> ok
[12:07:58 CDT(-0500)] <EricDalquist> if you want to use the trunk version of the weather portlet on other machines you'll either need to do the same svn checkout/mvn clean install
[12:08:05 CDT(-0500)] <EricDalquist> or setup a maven repository such as Nexus
[12:08:15 CDT(-0500)] <EricDalquist> to use for hosting locally built maven artifacts
[12:08:36 CDT(-0500)] <EricDalquist> and then configure your uPortal build to look at that maven repository when resolving artifacts
[12:12:33 CDT(-0500)] <brandon> hmm
[12:12:53 CDT(-0500)] <brandon> so what if i wanted to go back and use 1.0.7 of the weather portlet?
[12:13:06 CDT(-0500)] <EricDalquist> the other solution would be to jump on the portlet-dev list and bug folks there for a new release of the weather portlet
[12:13:14 CDT(-0500)] <EricDalquist> you're using uPortal 3.2.4 right?
[12:13:18 CDT(-0500)] <brandon> yeah
[12:13:31 CDT(-0500)] <brandon> the one i checked out is 1.0.9
[12:13:49 CDT(-0500)] <EricDalquist> so in the uPortal pom: https://source.jasig.org/uPortal/tags/rel-3-2-4/pom.xml
[12:13:52 CDT(-0500)] <brandon> i rather not have to worry about local artifacts
[12:14:00 CDT(-0500)] <EricDalquist> there are a bunch of properties under <!-- WAR Dependency Version Properties -->
[12:14:11 CDT(-0500)] <brandon> change it to 1.0.7?
[12:14:15 CDT(-0500)] <EricDalquist> you can simply change the version number of <WeatherPortlet.version>1.0.6</WeatherPortlet.version> to 1.0.7
[12:14:28 CDT(-0500)] <EricDalquist> yup
[12:14:32 CDT(-0500)] <EricDalquist> that property gets used here: https://source.jasig.org/uPortal/tags/rel-3-2-4/uportal-portlets-overlay/WeatherPortlet/pom.xml
[12:14:43 CDT(-0500)] <brandon> do i need to delete the WeatherPortlet folder I created under uportal-portlets-overlay ?
[12:14:45 CDT(-0500)] <EricDalquist> to determine the WeatherPortlet artifact to include
[12:14:58 CDT(-0500)] <EricDalquist> there should have been one that came with the 3.2.4 release
[12:15:02 CDT(-0500)] <EricDalquist> so just revert it to that
[12:15:26 CDT(-0500)] <brandon> ok, i mainly wanted to change the data source
[12:15:45 CDT(-0500)] <brandon> so if i revert, will i be able to enable Yahoo in the context file?
[12:16:12 CDT(-0500)] <EricDalquist> yes, I believe so, you'll need to have just that one context file in the correct location under /uportal-portlets-overlay/WeatherPortlet/
[12:17:31 CDT(-0500)] <EricDalquist> so it looks like you would put it in /src/main/webapp/WEB-INF/context/overlay/overlayContext.xml
[12:17:35 CDT(-0500)] <EricDalquist> see: https://source.jasig.org/portlets/WeatherPortlet/tags/WeatherPortlet-1.0.8/src/main/webapp/WEB-INF/context/overlay/overlayContext.xml
[12:17:41 CDT(-0500)] <EricDalquist> also version 1.0.8 is out
[12:17:53 CDT(-0500)] <EricDalquist> you can use this site to search for maven artifacts of projects: http://search.maven.org/#artifactdetails%7Corg.jasig.portlet%7CWeatherPortlet%7C1.0.8%7Cwar
[12:20:36 CDT(-0500)] <brandon> ok
[12:20:47 CDT(-0500)] <brandon> so i would put 1.0.8 in the uportal pom.xml
[12:21:09 CDT(-0500)] <EricDalquist> yes
[12:21:39 CDT(-0500)] <EricDalquist> and then create uPortal-3.2.4/uportal-portlet-overlay/WeatherPortlet/src/main/webapp/WEB-INF/context/overlay/overlayContext.xml
[12:21:47 CDT(-0500)] <EricDalquist> I'd recommend copying the one from: https://source.jasig.org/portlets/WeatherPortlet/tags/WeatherPortlet-1.0.8/src/main/webapp/WEB-INF/context/overlay/overlayContext.xml
[12:21:53 CDT(-0500)] <EricDalquist> and then editing it as needed
[12:22:24 CDT(-0500)] <brandon> ok, yeah i was wondering where that was. i reverted to the copy that came with uportal 3.2.4 and it wasn't there
[12:22:26 CDT(-0500)] <EricDalquist> what happens at build time is that overlayContext.xml file that you've created & modified replaces the one that ships with the portlet
[12:22:40 CDT(-0500)] <EricDalquist> injecting your config
[13:08:16 CDT(-0500)] <brandon> thanks eric
[13:08:19 CDT(-0500)] <brandon> working now
[13:08:35 CDT(-0500)] <EricDalquist> great
[13:09:27 CDT(-0500)] <brandon> so if i wanted to deploy a portlet that doesn't come with uportal by default but i wanted to manage through portlet overlay, would i just add it to the uportal pom.xml?
[13:09:37 CDT(-0500)] <EricDalquist> if there are things you think could use clarifying or additional details in the manual please just email it to either the uportal-user list or the uportal-steering-committee@lists.ja-sig.org
[13:10:01 CDT(-0500)] <EricDalquist> you would add a new overlay project (like the WeatherPortlet) folder
[13:10:17 CDT(-0500)] <EricDalquist> and then add the overlay project's maven info to the uportal-ear project
[13:11:03 CDT(-0500)] <brandon> ok, so basically follow this guide https://wiki.jasig.org/display/UPM32/Deploying+Portlets+to+uPortal
[13:11:10 CDT(-0500)] <EricDalquist> yup
[13:11:20 CDT(-0500)] <brandon> great
[13:11:31 CDT(-0500)] <EricDalquist> note that the overlay projects don't actually have code for the portlets in them
[13:11:48 CDT(-0500)] <EricDalquist> they are just a way to have maven customize already published portlet applications to get them to work in uPortal
[13:15:22 CDT(-0500)] <brandon> ah, ok
[13:15:35 CDT(-0500)] <brandon> make sense now