Yes, I fixed the release target, its building now. But it seems to get the same error as I get locally
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 > On Nov 9, 2016, at 8:21 AM, Werner Keil <[email protected]> wrote: > > At least that one sounds rather trivial: > > [ERROR] javac: invalid target release: 1.7 > Usage: javac <options> <source files> > use -help for a list of possible options > > > Maybe that is not the only reason it fails, but now that Portlet 3 targets > Java SE/EE 7, the Jenkins build must be adjusted to run on Java SE 7. > > Werner > > > On Wed, Nov 9, 2016 at 4:59 PM, David S Taylor <[email protected] > <mailto:[email protected]>> wrote: > 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 <[email protected] > > <mailto:[email protected]>> 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 <[email protected] > >> <mailto:[email protected]>> 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] > > > >
