[teiid-designer-dev] [Teiid-Designer/teiid-designer] 630acb: Fixes apache logging fragment problem
Branch: refs/heads/master
Home: https://github.com/Teiid-Designer/teiid-designer
Commit: 630acb9d754f5a84aa28bf3d4d7f2ee3102ba1d0
https://github.com/Teiid-Designer/teiid-designer/commit/630acb9d754f5a84a...
Author: Paul Richardson <p.g.richardson(a)redhat.com>
Date: 2015-10-16 (Fri, 16 Oct 2015)
Changed paths:
R features/org.teiid.designer.crypto.dummy.feature/.project
R features/org.teiid.designer.crypto.dummy.feature/AUTHORS.txt
R features/org.teiid.designer.crypto.dummy.feature/LEGAL.txt
R features/org.teiid.designer.crypto.dummy.feature/build.properties
R features/org.teiid.designer.crypto.dummy.feature/feature.properties
R features/org.teiid.designer.crypto.dummy.feature/feature.xml
R features/org.teiid.designer.crypto.dummy.feature/license.html
R features/org.teiid.designer.crypto.dummy.feature/pom.xml
M features/org.teiid.designer.feature/feature.xml
A features/org.teiid.designer.library.feature/.project
A features/org.teiid.designer.library.feature/AUTHORS.txt
A features/org.teiid.designer.library.feature/LEGAL.txt
A features/org.teiid.designer.library.feature/build.properties
A features/org.teiid.designer.library.feature/feature.properties
A features/org.teiid.designer.library.feature/feature.xml
A features/org.teiid.designer.library.feature/license.html
A features/org.teiid.designer.library.feature/pom.xml
M features/pom.xml
M site/category.xml
Log Message:
-----------
Fixes apache logging fragment problem
* apache.directory's slf4j.api plugin requires a fragment that exports
the
org.slf4j package. In JBDS, no fragment is resident, thus the
org.apache.directory.studio.slf4j.eclipselog fragment is installed.
* In Eclipse Luna SR2, the ch.qos.logback.classic fragment is already
resident hence apache's slf4j plugin latches onto it. However, its
host
is an older version of slf4j.api and this causes a 'Uses Constraint'
violation when installing Designer.
* To avoid this, Designer needs to ensure that the eclipselog fragment
is
always installed as part of its dependencies. The seeming only way to
do
this is by including it in a feature.
* Renames the 'crypto.dummy' feature to 'library' and adds the
eclipselog
fragment to it. This does mean that the fragment is carried by the
feature but there is not a lot that can be done about that since we
need
to force its install and the apache.directory plugins/features cannot
be
changed.