Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
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.
- Loading branch information
Showing
11 changed files
with
24 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 changes: 1 addition & 1 deletion
2
...id.designer.crypto.dummy.feature/.project → ...g.teiid.designer.library.feature/.project
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters