Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 314502

Summary:	Remove unnecessary Version constraints on Require-Bundle- / Package-Import-Statements
Product:	[Modeling] EMFT	Reporter:	Jochen Schmich <jochen.schmich>
Component:	MWE	Assignee:	Project Inbox <emft-mwe-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	sven.efftinge
Version:	unspecified	Flags:	sven.efftinge: helios+
Target Milestone:	RC3
Hardware:	PC
OS:	All
Whiteboard:

Description Jochen Schmich

2010-05-26 12:24:43 EDT

There are version constraints on the imports of every of the following bundles:
org.eclipse.emf.mwe.core -> org.apache.commons.logging (1.1.1)
org.eclipse.emf.mwe.utils -> org.apache.commons.logging (1.1.1)
org.eclipse.emf.mwe2.runtime -> org.apache.log4j (1.2.15)

It's not absolutely necessary to remove them -> but I sometimes had strange effects while running different versions of Commons Logging in an OSGi-Environment (can't really predict of which bundles this environment will consist on each machine) -> those effects especially occurred while running the M2T Xpand Workflow Components inside the same environment - they don't define version constraints and sometimes happened to use a different Commons Logging bundle -> a different Logger!

Comment 1 Sven Efftinge

2010-05-28 01:08:49 EDT

fixed in HEAD

Comment 2 Sven Efftinge

2010-05-28 01:09:43 EDT

Note that the org.apache.log4j is needed in 1.2.15 because it provides features we use, which are not available in previous versions.