...
[12:36:14 CST(-0600)] <dmccallum54> the portlet deployment/installation process with SSP is going to be the same as for a vanilla uPortal. if you're not clear on aspects of the uPortal portlet deploy/install process you're probably going to find the most expert advice on the uportal-user mailing list or #jasig-uportal
[12:37:26 CST(-0600)] <dmccallum54> if you're having trouble with the sakai connector portlet itself i'd suggest contacting portlet-user or portlet-dev mailing lists. steve swinsburg was the main dev on that project i think. he's usually quite responsive
[12:40:46 CST(-0600)] <dearbin> okay.... I have deployed the portlet, but I would like to confirm its deployment with the contents on its web.xml, but I dont know how to verify that
[12:42:57 CST(-0600)] <dmccallum54> i dont think anyone here is familiar with the details of the sakai connector portlet
[12:43:33 CST(-0600)] <dearbin> am not asking to that specific portlet, in general how to check
[13:01:31 CST(-0600)] <dmccallum54> i see the problem i think. the skin is hiding the 'customize' layout link. can try unhiding it in the css or chrome dev tools. or adding your portlet by fname to one of the standard ssp fragment defs. e.g. ./uportal-war/src/main/data/ssp_entities/fragment-layout/ssp-lo.fragment-layout.xml
[15:37:52 CST(-0600)] <js70> that would be me :-$
[16:10:21 CST(-0600)] <TonyUnicon1> Jim, I still haven't gotten to the broken test cases.. The issue is with the test now and this EasyMock stuff, the tests I would expect to fail based on the changes I made
[16:10:44 CST(-0600)] <TonyUnicon1> so no real code needs to be fixed, just the tests adjust it, i should get to it this weekend
[16:10:53 CST(-0600)] <TonyUnicon1> adjusted*
[16:39:04 CST(-0600)] <JasonElwood> Tony- I'm going to move SSP-728 to the next iteration and give it an estimate of 8 days. any problems?
[17:22:43 CST(-0600)] <js70> np
[17:22:54 CST(-0600)] <js70> just wanted you to know.