Eclipse Community Forums: Rich Client Platform (RCP) » Problem with org.apache.commons.logging while exporting RCP product

Home » Eclipse Projects » Rich Client Platform (RCP) » Problem with org.apache.commons.logging while exporting RCP product

Show: Today's Messages :: Show Polls :: Message Navigator

Problem with org.apache.commons.logging while exporting RCP product [message #523751]

Mon, 29 March 2010 07:50

Armand

Messages: 4
Registered: March 2010

Junior Member

Hi,

I am trying to export my Eclipse RCP product with "Product Export Wizard" and I always have the following error:

Missing requirement: product requires 'org.apache.commons.logging [1.0.4.v200904062259]' but it could not be found

Of course I checked that org.apache.commons.logging was included in my plugin.xml dependencies and my product configuration, but I found out that there were two versions of org.apache.commons.logging: 1.0.4 and 1.1.1. Could the problem be there?

The only topic I found on the subject was http://www.eclipse.org/forums/index.php?t=tree&goto=3334 67& but it got no answer.

If you have any idea to solve my problem, that would be very kind of you.

Thanks in advance,

Armand

(I'm using Eclipse Platform 3.5.2)

Report message to a moderator

Re: Problem with org.apache.commons.logging while exporting RCP product [message #523772 is a reply to message #523751]

Mon, 29 March 2010 09:43

Bernd van Velsen

Messages: 19
Registered: November 2009

Junior Member

I guess this was done intentionally so you can choose the logging bundle for your application yourself. Because of this, you have to add org.apache.commons.logging as required plug-in. Otherwise you will get an error when starting the application:
Missing requirement: Apache Commons Httpclient 3.1.0.v20080605-1935
(org.apache.commons.httpclient 3.1.0.v20080605-1935) requires
'package org.apache.commons.logging [1.0.4,2.0.0)' but it could not be found

does this help you in any way?

Report message to a moderator

Re: Problem with org.apache.commons.logging while exporting RCP product [message #523998 is a reply to message #523772]

Tue, 30 March 2010 08:56

Armand

Messages: 4
Registered: March 2010

Junior Member

Thank you for your help. As a matter of fact, I had added it as a required plugin indeed, but it still couldn't find it.
At last I could solve my problem, and here is the solution if anyone encounters the same problem:

In the product configuration dependencies tab, you have to specify org.apache.commons.logging version with "Properties..." button, in my case 1.1.1, otherwise it will look for version 1.0.4.

I had already tried that, I don't understand why it works now but I won't complain!

Thanks again for your help,

Armand

Report message to a moderator

Re: Problem with org.apache.commons.logging while exporting RCP product [message #524276 is a reply to message #523772]

Wed, 31 March 2010 11:41

Ralf Ebert

Messages: 168
Registered: July 2009

Senior Member

Hi Armand,

you don't have to add it as dependency to a plug-in, instead add it to your product
(either directly if you have a plug-in based product or via a feature of your application).

btw, I guess this is caused by including the p2.user.ui feature, I opened a bug about the
missing bundle:
http://bugs.eclipse.org/306747

Greetings,

Ralf

--
http://www.ralfebert.de/blog/
http://twitter.com/ralfebert/

Report message to a moderator

Re: Problem with org.apache.commons.logging while exporting RCP product [message #528431 is a reply to message #524276]

Tue, 20 April 2010 13:56

Peter Lang

Messages: 153
Registered: July 2009

Senior Member

I am facing the same problem.

org.apache.commons.logging shows up in my Dependencies, but it has version
1.1.1.v200904062255 while org.eclipse.pde.core requires
1.0.4.v200904062259

I use eclipse-modeling-galileo-SR2-incubation-win32 (downloaded on 2010-04-14).

Am I doing something wrong or is this a bug?

Report message to a moderator

Re: Problem with org.apache.commons.logging while exporting RCP product [message #528438 is a reply to message #528431]

Tue, 20 April 2010 14:13

Ralf Ebert

Messages: 168
Registered: July 2009

Senior Member

Hi Peter,

you could just try to add the bundle to one of your application features so that it's
included into the exported product. But if you're building a RCP application, it would be
a strange thing to include "org.eclipse.pde.core" except if you're building an application
that includes a Plug-in Development Environment :)

Greetings,

Ralf

--
Learn how to contribute to Eclipse here: http://eclipse.org/contribute/
Read my Blog here: http://www.ralfebert.de/blog/
Follow me on Twitter here: http://twitter.com/ralfebert/

Report message to a moderator

Re: Problem with org.apache.commons.logging while exporting RCP product [message #528445 is a reply to message #528438]

Tue, 20 April 2010 14:38

Peter Lang

Messages: 153
Registered: July 2009

Senior Member

Thanks for your reply!

I'm not building an RCP-application - agreed that I wouldn't need it then :)

When I press "Add Required Plug-ins", org.apache.commons.logging is added to my dependencies, so that works fine.

The problem is that the versions do not match. The workaround suggested by Armand works for me too, but I think that something is wrong with either the Dependency or the bundle version.

Best regards, Peter

Report message to a moderator

Re: Problem with org.apache.commons.logging while exporting RCP product [message #538849 is a reply to message #523772]

Tue, 08 June 2010 19:09

Sairam Meghi

Messages: 1
Registered: June 2010

Junior Member

Select the org.apache.commons.logging and click on properties button where a dialog box will ask you for version number. Give the complete version number as 1.0.4.v200904062259.
And it will work... Very Happy

Report message to a moderator

Previous Topic:	How to implement CRUD operations in an RCP application
Next Topic:	Accessing the EditorInput in IdetailsPage

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 16 08:38:48 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter