[DEF4ALL-1] defense4all packaging is jar , not osgi bundle Created: 20/Oct/13  Updated: 19/Oct/17  Resolved: 19/Jan/14

Status: Resolved
Project: defense4all
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Alissa Bonas Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC

External issue ID: 117

 Description   

defense4all packaging is jar , not osgi bundles
Thus, it is not deployed correctly in the osgi container - there are no defense4all bundles there even though defense4all jars are brought correctly by the integration project.

to reproduce, take patch
https://git.opendaylight.org/gerrit/#/c/1937/1
that enables bringing of the defense4all dependencies,
build and run "run.sh" and then in osgi console type "ss"
there won't be any defense4all bundles even though the defense4all jars are in the plugins dir.

or just look at the poms in defense4all and see that packaging type is "jar" and not "bundle"...

 Comments   
Comment by Chris Wright [ 21/Oct/13 ]

Is there some kind of automation we can include to detect this?

Comment by Alissa Bonas [ 19/Jan/14 ]

(In reply to Chris Wright from comment #1)
> Is there some kind of automation we can include to detect this?

In which stage this automation should detect it?

Comment by Konstantin Pozdeev [ 19/Jan/14 ]

Defense4all process is not designed to be OSGI bundle and should not be run under run.sh scropt.

Generated at Wed Feb 07 19:57:22 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.