https://bender.vaadin.com/viewLog.html?buildId=146749&buildTypeId=Flow_StarterTests_FlowStartersItPlatform141Snapshot_PortletStarterIt

/opt/agent/work/54d731b39d1e6698/src/main/java/com/vaadin/starter/portlet/MyPortlet.java:[5,8] cannot access com.vaadin.flow.component.WebComponentExporterFactory
[10:45:35][Step 3/6]   class file for com.vaadin.flow.component.WebComponentExporterFactory not found
[10:45:35][Step 3/6] [ERROR] /opt/agent/work/54d731b39d1e6698/src/main/java/com/vaadin/starter/portlet/MyPortlet.java:[7,5] method does not override or implement a method from a supertype
[10:45:35][Step 3/6] [INFO] 2 errors 

Hello.

Thanks for your examples. Can you give me some advice, please, why when I place portlet from this example on liferay portal - portlet content is empty?

Requirements

• User can build and deploy a Vaadin portlet to Pluto using this starter
  • documentation has copy-pasteable steps to follow
  • uses latest portlet-support snapshot

• Add a new branch with Liferay example
• Update vaadin-portal to final version once it is out

I am not sure where best to ask about this.

I want to create a Vaadin (if possible) portlet (I had a couple of version 7 portlets running on Liferay 6.x some time ago).

Looking at Liferay 7.x, it seems an OSGi portlet is a no go as it is part of the commercial Vaadin offering (which is not an option in this case). The documentation talked about using a non OSGi Portlet 3.0 alternative, so this is the track that led me here.

I have cloned this repo, and in the pom.xml changed the dependancy to vaadin-core as suggested by the comment:

 <!-- Replace artifactId with vaadin-core to use only free components -->
            <artifactId>vaadin</artifactId>

So I changed the above to vaadin-core, and managed to compile and deply to pluto, but it seems to still want to go off to Vaadin servers and validate my developer pro licence. I got a trial which solved the problem, for two weeks I am guessing.

So the behaviour seems to imply that, although the comment indicates you can use the Vaadin free version, in fact you can't.

Is this correct behaviour?

Thanks.

To reproduce:

1. Clone base-starter-flow-portlet
2. Run mvn package cargo:run -Pdemo
3. Go to http://localhost:8080/pluto, log in, and add the base portlet to a page
4. Open browser console and go to the page
5. Browser console contains an error window.Vaadin is undefined