Details
-
New Feature
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
Description
The "Detect modules" currently only support maven 'modules'. It would be nice if it also would support OSGi Bundles.
An OSGi Bundle consists of a manifest files describing the bundle in the META-INF directory (see here for example http://www.javaworld.com/javaworld/jw-03-2008/jw-03-osgi1.html?page=2 a little down the page).
If the warnings could be grouped based on these bundles it would be a great help.
Attachments
Activity
Code changed in jenkins
User: Ulli Hafner
Path:
src/main/java/hudson/plugins/analysis/util/ModuleDetector.java
src/test/java/hudson/plugins/analysis/util/ModuleDetectorTest.java
src/test/resources/hudson/plugins/analysis/util/MANIFEST-NAME.MF
src/test/resources/hudson/plugins/analysis/util/MANIFEST.MF
src/test/resources/hudson/plugins/analysis/util/l10n.properties
http://jenkins-ci.org/commit/analysis-core-plugin/5704f5571c662d874e710102634d14c21c888071
Log:
[FIXED JENKINS-10681] Added support for localized MANIFEST files.
Code changed in jenkins
User: Ulli Hafner
Path:
src/main/java/hudson/plugins/analysis/util/ModuleDetector.java
http://jenkins-ci.org/commit/analysis-core-plugin/9a77f974fe8ea4c6d86cc99fffb97390e6be8924
Log:
JENKINS-10681 Added support for OSGi modules when mapping warnings
to modules. If a module is an OSGi bundle then the content of pom or
build.xml will not be used.
No, the mapping contains just the root folders:
/a/b/c/pom.xml ->
put("/a/b/c", "module name");
In your case:
/a/b/bundle-root/META-INF/MANIFEST.MF ->
put("/a/b/bundle-root", "module name");
All Files that share the same prefix use the value of the map.
Integrated in
plugins_analysis-core #161
[FIXED JENKINS-10681] Added support for localized MANIFEST files.
Ulli Hafner :
Files :