Results 1 to 2 of 2

Thread: FatalParseException for Export-Package

  1. Aug 20th, 2008, 06:57 AM #1
    Beta User
    Beta User is offline Junior Member
    Join Date
    Oct 2008
    Posts
    0

    Default FatalParseException for Export-Package

    While unusual, and probably not a good idea, the following manifest entry is fine within Eclipse, but not with S2AP (it gives a FatalParseException).
    Export-Package: .,
    another.package

    Surely S2AP should be able to handle the same Manifest entries as Eclipse happily does.
  2. Aug 20th, 2008, 07:09 AM #2
    robh
    robh is offline Senior Member Spring Modules TeamSpring Team
    Join Date
    Aug 2004
    Location
    Southampton, UK
    Posts
    826

    Default FatalParseException for Export-Package

    Eclipse is actually in error there - there is no package '.'. OSGi has no way of representing the default package, and . is certainly not valid.

    You can see this described in the BNF in section 1.3.2 of the OSGi R4 spec.

    Hope this helps.

    Regards, Rob
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules