EP6SP2 - Empty jar warning when deploying pars from Eclipse

[Former Member]

Hi there,

I've made modifications to the com.sap.portal.navigation.masthead and com.customer.portal.runtime.logon par files using Eclipse version 2.1.3 and the SAP Plug-ins version 1.2.0.

I use Eclipse to modify and deploy the files to the Portal. After I've deployed the par files and I've restarted the Portal, I'm getting the following warnings in the console log files:

warning: Jar is empty: /usr/sap/EPQA/j2ee/j2ee_07/cluster/server/services/servlet_jsp/work/jspTe

mp/irj/root/WEB-INF/portal/portalapps/com.customer.portal.runtime.logon/lib/api.jar

warning: Jar is empty: /usr/sap/EPQA/j2ee/j2ee_07/cluster/server/services/servlet_jsp/work/jspTe

mp/irj/root/WEB-INF/portal/portalapps/com.customer.portal.runtime.logon/private/lib/core.jar

warning: Jar is empty: /usr/sap/EPQA/j2ee/j2ee_07/cluster/server/services/servlet_jsp/work/jspTe

mp/irj/root/WEB-INF/portal/portalapps/com.sap.portal.navigation.masthead/lib/api.jar

warning: Jar is empty: /usr/sap/EPQA/j2ee/j2ee_07/cluster/server/services/servlet_jsp/work/jspTe

mp/irj/root/WEB-INF/portal/portalapps/com.sap.portal.navigation.masthead/private/lib/core.jar

Now, under the "Window -> Preferences -> SAP Portal Plugin Settings" in Eclipse there are three checkboxes. The third one (Yes, I want short jar names into the archive) is the one that seems to control whether the core.jar and api.jar files are created.

The problem is that if I click this checkbox ON it creates these two empty files and I get the warnings in the logs because it creates the empty core.jar and api.jar files in the par.

If I click this checkbox OFF then I get the following empty files created in the par:

com.customer.portal.runtime.logonapi.jar

com.customer.portal.runtime.logoncore.jar

and

com.sap.portal.navigation.mastheadapi.jar

com.sap.portal.navigation.mastheadcore.jar

This causes me to get the warnings in the console logs for these files instead of the api.jar and core.jar files.

So, my question is: Do I ignore these warnings and not worry about them?

Or, is there a way to get Eclipse to not create these blank files when creating/exporting a par file?

Thanks in advance for any help.

Regards,

Robin Schmidt.

[Former Member]

Thanks guys for the quick response, much appreciated.

Regards,

Robin.

[Former Member]

Hi Robin,

I think with Patch 4 the Eclipse plugin-version produced an error. With Patch 5 this error was reduced to a warning. We opened a OSS note with SAP because of that and were told that we shouldn't mind.

If these warning bother you, just delete the file like Detlev said.

Regards,

Holger.

[detlev_beutner]

Hi Robin,

the switch "Yes, I want short jar names into the archive" is, as you have realized more or less, to create only one JAR with the common name api.jar / core.jar for the public / private part of the portal app.

So, if there are no classes within the public and/or private part of the app, the corresponding JARs are created but empty.

As you have realized, the problem just appears in another kind if you don't mark the switch.

Anyhow, you can ignore the warnings; if they bother you, just delete the empty JARs. There is no automatism to get rid of them.

As far as I remember, these warning have appeared since some certain PatchLevel and haven't been there before (not quite sure).

Hope it helps

Detlev