Hi Scott, That fixed it, thanks. It now builds locally and on the Apache Jenkins Server:
https://builds.apache.org/job/portals-pluto-trunk/34/ <https://builds.apache.org/job/portals-pluto-trunk/34/> I just configured Jenkins to send build status emails to pluto-dev > On Nov 9, 2016, at 11:58 PM, Martin Scott Nicklous > <scott.nickl...@de.ibm.com> wrote: > > Hi David, > > interesting problem. I think I found it - check my latest commit. The test > fixture IncompletePortlet.java was mistakenly using the portlet name > "Portlet4" for the init and destroy methods rather than the correct name > "IncompletePortlet". This led to duplicate init and destroy methods for > "Portlet4" to be found, and which one was used depended on the order in which > the class scanner found the files, which in turn depended on the order that > the file system read the class files from a certain directory. On my system I > was lucky I guess and it worked, while on your system, the wrong class file > was found first. > > Anyway, if that was it, it should be fixed now. > > (Note that this should not happen with real portlets, since the configuration > reconciliation process that combines the bean portlet configuration with the > portlet.xml configuration will not take the portlet into service if duplicate > init and destroy methods are found. This checking is ignored in the test > code, since some of the tests handle edge cases that require a check to fail.) > > > Mit freundlichen Grüßen, / Kind regards, > Scott Nicklous > > WebSphere Portal Standardization Lead & Technology Consultant > Specification Lead, JSR 362 Portlet Specification 3.0 > IBM Commerce, Digital Experience Development > IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: > Martina Koederitz / Geschäftsführung: Dirk Wittkopp > Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, > HRB 243294 > > > <graycol.gif>David S Taylor ---09.11.2016 16:59:43---Well, I pulled the > master branch clean, same problem. Running Java java version "1.7.0_60" > > From: David S Taylor <da...@bluesunrise.com> > To: pluto-dev@portals.apache.org > Date: 09.11.2016 16:59 > Subject: Re: build errors > > > > > Well, I pulled the master branch clean, same problem. Running Java > > java version "1.7.0_60" > Java(TM) SE Runtime Environment (build 1.7.0_60-b19) > Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode) > > Seems that one of my methods in the AnnotatedMethodStore is not initialized > correctly, it points to: > > class org.apache.pluto.container.reconcile.fixtures.IncompletePortlet > > and not the expected Portlet4 > > "Portlet name='Portlet4', Method type='INIT', Dispatch ID=''" -> " size = 1" > > > On Nov 9, 2016, at 6:55 AM, Neil Griffin <neil.grif...@portletfaces.org> > > wrote: > > > > Hi David, > > > > The Liferay Faces team performing builds of Pluto, but we're not seeing the > > error you mentioned below. > > > > Best Regards, > > > > Neil > > > >> On Nov 8, 2016, at 10:49 AM, DavidSeanTaylor <da...@bluesunrise.com> wrote: > >> > >> Im seeing these errors with my latest pull today. I ran ‘mvn clean install’ > >> anyone else seeing the errors below? > >> > >> Running org.apache.pluto.container.util.ArgumentUtilityTest > >> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec > >> - in org.apache.pluto.container.util.ArgumentUtilityTest > >> > >> Results : > >> > >> Failed tests: > >> PortletInvokeTest.test4destroy:266 null > >> PortletInvokeTest.test4init:259 null > >> PortletInvokeTest.test4resource:306 null > >> PortletInvokeTest.test4action:274 null > >> PortletInvokeTest.test4event1:282 null > >> PortletInvokeTest.test4event2:290 null > >> PortletInvokeTest.test4render:298 null > >> > >> Tests run: 1003, Failures: 7, Errors: 0, Skipped: 0 > >> > >> [INFO] > >> ------------------------------------------------------------------------ > >> [INFO] Reactor Summary: > >> [INFO] > >> [INFO] Apache Pluto ....................................... SUCCESS [ > >> 1.669 s] > >> [INFO] Java Portlet API V3.0 .............................. SUCCESS [ > >> 19.451 s] > >> [INFO] Apache Pluto Container API ......................... SUCCESS [ > >> 0.695 s] > >> [INFO] Apache Pluto Portlet Container ..................... FAILURE [ > >> 18.080 s] > > > > > >
