Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Patrick Warnecke
How to update portlet automatically without marketplace?
February 21, 2013 12:20 AM
Answer

Patrick Warnecke

Rank: New Member

Posts: 20

Join Date: November 30, 2012

Recent Posts

Hi,
my company is planning to switch with our product to a portal system. One of our concerns, wich I am currently evaluating, is if there is a possibility to update our portlet automatically without the marketplace. (The first deployment will most likely be always done by ourselves, cause chances are high that the product needs certain customer specific configuration, but after the first deployment we want the portlets to check themselves if the need an update or not and do it.)
We're not entirly sure as of yet, but the chances are high that out product will be split up into mutliple portlets and we don't want to publish these portlet in the marketplace.
Firstly would be the cost to hight (the 20% fee) and secondly you still need a certain setup of our portlet to actually use them. (I hope everybody gets my point, I'm a trainee and english isn't my first language.)
The software catalog and update manager are out of the question, at least to my understanding, because they will be removed or no longer supported in the near future.

In the server logs I can always see following two lines:
1[PluginPackageUtil:1421] Checking for available updates
2[PluginPackageUtil:1465] Finished checking for available updates in 1 ms

I thought this might be the kind of thing we want. Will this PluginPackageutil be supported in the future? Can it do automatic updates? And the most importan part, how do I hook into that thing?
A link to an instruction or something like that would be nice, I couldn't find anything until now.

Thanks in advance
regards
Hitoshi Ozawa
RE: How to update portlet automatically without marketplace?
February 21, 2013 3:15 AM
Answer

Hitoshi Ozawa

Rank: Liferay Legend

Posts: 7949

Join Date: March 23, 2010

Recent Posts

Check the following properties in portal-ext.properties

#
# Input a list of Liferay plugin repositories separated by \n characters.
#
plugin.repositories.trusted=http://plugins.liferay.com/official
plugin.repositories.untrusted=http://plugins.liferay.com/community
Patrick Warnecke
RE: How to update portlet automatically without marketplace?
February 28, 2013 2:26 AM
Answer

Patrick Warnecke

Rank: New Member

Posts: 20

Join Date: November 30, 2012

Recent Posts

Thanks for the reply, but that didn't help.
I added my local test repository, but it doesn't seem to have any effect at all??
Hitoshi Ozawa
RE: How to update portlet automatically without marketplace?
February 28, 2013 5:47 AM
Answer

Hitoshi Ozawa

Rank: Liferay Legend

Posts: 7949

Join Date: March 23, 2010

Recent Posts

Have you followed the steps in liferay's online documentation?

http://www.liferay.com/documentation/liferay-portal/6.1/user-guide/-/ai/lp-6-1-ugen15-creating-your-own-plugin-repository-0
Patrick Warnecke
RE: How to update portlet automatically without marketplace?
February 28, 2013 6:20 AM
Answer

Patrick Warnecke

Rank: New Member

Posts: 20

Join Date: November 30, 2012

Recent Posts

I just stumbled upon this plugin: http://www.liferay.com/marketplace/-/mp/application/15474932
With this I can now finally check my local repository (and yeah I followed the "steps" you mentioned already, but that didn't help). So this is a big step in the right direction. But now I face the problem that my repository or something seems to be misconfigured or the structure is not as needed, cause I see the two versions of my test portlet as different portlets and after I install any of the versions it isn't displayed as "installed".

My liferay-plugin-repository.xml in the root of the repository looks like:
 1<?xml version="1.0"?>
 2<!DOCTYPE plugin-repository PUBLIC "-//Liferay//DTD Plugin Repository 6.1.0//EN" "http://www.liferay.com/dtd/liferay-plugin-repository_6_1_0.dtd">
 3
 4<plugin-repository>
 5    <settings>
 6        <setting name="use-download-url" value="true"></setting>
 7    </settings>
 8
 9    <plugin-package>
10        <name>ObjectEditor</name>
11        <module-id>incony-ag/pf-objecteditor-portlet/6.1.1.1/war</module-id>
12        <types>
13            <type>portlet</type>
14        </types>
15        <short-description>Meine Kurzbeschreibung</short-description>
16        <change-log>Nothing major happened!</change-log>
17        <page-url>http://localhost/repository/</page-url>
18        <download-url>http://localhost/repository/incony-ag/pf-objecteditor-portlet/6.1.1.1/PF-ObjectEditor-portlet-6.1.1.1.war</download-url>
19        <author>Patrick W.</author>
20        <licenses>
21            <license osi-approved="true">LGPL</license>
22        </licenses>
23        <liferay-versions>
24            <liferay-version>6.1.1+</liferay-version>
25        </liferay-versions>
26    </plugin-package>
27    <plugin-package>
28        <name>ObjectEditor</name>
29        <module-id>incony-ag/pf-objecteditor-portlet/6.1.1.2/war</module-id>
30        <types>
31            <type>portlet</type>
32        </types>
33        <short-description>Meine Kurzbeschreibung</short-description>
34        <change-log>Nothing major happened!</change-log>
35        <page-url>http://localhost/repository/</page-url>
36        <download-url>http://localhost/repository/incony-ag/pf-objecteditor-portlet/6.1.1.2/PF-ObjectEditor-portlet-6.1.1.1.war</download-url>
37        <author>Patrick W.</author>
38        <licenses>
39            <license osi-approved="true">LGPL</license>
40        </licenses>
41        <liferay-versions>
42            <liferay-version>6.1.1+</liferay-version>
43        </liferay-versions>
44    </plugin-package>
45    <plugin-package>
46        <name>ObjectEditor</name>
47        <module-id>incony-ag/pf-objecteditor-portlet/6.1.1.3/war</module-id>
48        <types>
49            <type>portlet</type>
50        </types>
51        <short-description>Meine Kurzbeschreibung</short-description>
52        <change-log>Nothing major happened!</change-log>
53        <page-url>http://localhost/repository/</page-url>
54        <download-url>http://localhost/repository/incony-ag/pf-objecteditor-portlet/6.1.1.3/PF-ObjectEditor-portlet-6.1.1.1.war</download-url>
55        <author>Patrick W.</author>
56        <licenses>
57            <license osi-approved="true">LGPL</license>
58        </licenses>
59        <liferay-versions>
60            <liferay-version>6.1.1+</liferay-version>
61        </liferay-versions>
62    </plugin-package>
63</plugin-repository>


The folder structure in the repo is then:
./incony-ag/pf-objecteditor-portlet/6.1.1.1/PF-ObjectEditor-portlet-6.1.1.1.war
./incony-ag/pf-objecteditor-portlet/6.1.1.2/PF-ObjectEditor-portlet-6.1.1.1.war
./incony-ag/pf-objecteditor-portlet/6.1.1.3/PF-ObjectEditor-portlet-6.1.1.1.war

In every of the mentioned .war-Files I've got a WEB-INF/lifer-plugin-repository.xml with the same content as the .xml above. Besides that the portlet is basically a default portlet created by the SDK.
Is the problem maybe that I need a pom.xml somewhere? Do I have to lay out the repo structure differently?

Thanks in advance again!