Not able to extend portlet from existing portlet.

[9年前 に Dhanwan S Ramasane によって更新されました。]

I tried this https://www.liferay.com/documentation/liferay-portal/6.2/development/-/ai/creating-plugins-to-extend-plugins-liferay-portal-6-2-dev-guide-03-en
But still merge target is not properly working please give some solution.

[9年前 に Vishal Patel によって更新されました。]

What issue exactly you are facing ? Any error Log ?

[9年前 に Dhanwan S Ramasane によって更新されました。]

No error log when i run the merge target it is not creating tmp folder and all...

[9年前 に Olaf Kock によって更新されました。]

It would help more if you'd describe what you did, what kind of messages you see and what you expect to see, rather than asking for the solution to a problem that you don't describe. Logs, Ant output, anything more than "it doesn't work" helps if you expect someone to be able to help you solve your problem.

[9年前 に Dhanwan S Ramasane によって更新されました。]

Thanks for your reply !!

I am trying to extend existing notifications-portlet plugins in Liferay 6.2 refered this Link

I followed all the steps
1. Created new notifications-portlet portlet.
2. Removed everything excepts dockroot and build.xml.
3. added these entry in build.xml
<?xml version="1.0"?>
<!DOCTYPE project>

<project name="notifications-portlet" basedir="." default="deploy">
<import file="../build-common-portlet.xml" />
<property
name="original.war.file"
value="notifications-portlet-6.2.0.3-ce-ga1-20140210151141114.war"
/>
</project>
4. Added above notifications-portlet-6.2.0.3-ce-ga1-20140210151141114.war in root folder.
5. Run ant target merge.

So here i am getting this console
[Console output redirected to file:\liferay\setup\workspace\.metadata\.plugins\com.liferay.ide.sdk.core\sdk.log]
Buildfile: D:\liferay\setup\liferay-plugins-sdk-6.2\portlets\notifications-portlet\build.xml
merge:
BUILD SUCCESSFUL
Total time: 2 seconds

So here i m expecting tmp folder should be there in root folder and it should contains all the content from war file.
But I am not seeing any tmp folder over here.

I tried to explore merge target in build-common.xml <isset property="set-build-xml-var.return" /> property something is missing.
your help is needed !!

[9年前 に Olaf Kock によって更新されました。]

Hm - I've tried it once (loooong time ago) and it worked then. You don't mention that you add any code to override the original plugin - did you try what happens when you do?

[9年前 に Dhanwan S Ramasane によって更新されました。]

I tried to change /docroot/notifications/view.jsp, added the same location as in the war. But still i am not getting proper result.
In console when i run ant target merge:

[Console output redirected to file:\liferay\setup\workspace\.metadata\.plugins\com.liferay.ide.sdk.core\sdk.log]
Buildfile: D:\liferay\setup\liferay-plugins-sdk-6.2\portlets\notifications-portlet\build.xml
merge:
BUILD SUCCESSFUL
Total time: 2 seconds

Thanks !!

[9年前 に David H Nebinger によって更新されました。]

The merge target only merges your changes. Complete with "ant war" to build your war file in the SDK dist directory.

[9年前 に Dhanwan S Ramasane によって更新されました。]

Hi David,

I think before running "ant war" , "ant merge" require to run for extending any plugins. So when first time we run target merge it will merge the modified and existing content and put into tmp folder but for me tmp is not creating. Even i tried running target war but generated war file is empty.

I checked, the problem is somewhere <macrodef name="merge"> in build-common.xml there "<isset property="set-build-xml-var.return" /> " is cooming false, i dont know what configuration is missing?

Thanks !!

[9年前 に David H Nebinger によって更新されました。]

I would check that you have a good 1.6 or 1.7 sun jdk, latest version of maven, check build.xml to ensure that the filename matches that of the real file, ...

I have verified that it does still work, but there's something environmental on your end that is blocking it.

[9年前 に Olivier Spieser によって更新されました。]

The issue comes from a change in "build-common-plugin.xml" in liferay plugin sdk 6.2.

The value for the field "original.war.file" is parsed with a string parser, so you have to be very careful about the format.

You have to replace :

<property name="original.war.file" value="original-portal-6.2.0.3.war" />

With (remove all extra endlines and spaces) :

<property name="original.war.file" value="marketplace-portlet-6.2.0.3.war" />

Then it will work as expected.

[9年前 に David H Nebinger によって更新されました。]

XML is not supposed to be sensitive to whitespace and newlines

[9年前 に Dhanwan S Ramasane によって更新されました。]

Hi Olivier Spieser / David,

Its working
Thanks for both of you.

Thanks,
Dhanwan

[7年前 に Reddeppa Kollu によって更新されました。]

Issue: Getting Identified too long when i try to browse for notification on home page.

Running on Tomcat, Oracle DB

Root Cause: Table length

Somebody mentioned that it was fixed, but i couldn't find where it was fixed or version?

the Plug-in i am talking is about notification-portlet :

i thought of trying to extend by changing myself, but i couldn't find the war file for notification-portlet, trying for last 24 hrs, finally writing here to get some help

[7年前 に David H Nebinger によって更新されました。]

Notification portlet is not shipped separately, it's actually in the bundle distribution.

You can manufacture a war file by zipping up the notifications folder contents from the webapps dir and name it notifications.war to use as a starting point.

Yes it was supposed to be fixed at some point, not sure why it wasn't in the latest bundle release.

[7年前 に Reddeppa Kollu によって更新されました。]

Thanks you David for Quick response!! let me try!!

Really appreciate that!!

Regards
Naidu

[7年前 に David H Nebinger によって更新されました。]

oops, my bad, it is available in the marketplace:

https://web.liferay.com/marketplace/-/mp/application/31718422

The 2.0.5 version is still there that has the identifier problem w/ Oracle, but at least it will give you the war to start from.