Eclipse Community Forums: Virgo » Bundlor and 'static resources'

Home » Eclipse Projects » Virgo » Bundlor and 'static resources'

Bundlor and 'static resources' [message #1010903]

Mon, 18 February 2013 07:56

Eclipse User

I have a bunch of packages I wish to export from a MANIFEST, which do not contain any java classes and are not even compiled to target/classes. The documentation suggests that static resources can be included, but doesn't give any details on what it means by 'static resources', how they are detected or by what criteria.

So, if I have a structure like:

project
-> directory
--> subdirectory1
---> ...
--> subdirectory2
---> ...
--> subdirectory3
---> ...

is it possible to have bundler automatically detect all the 'packages' to export? There may be many of these directories.

Pre-thanks,
Dan.

Re: Bundlor and 'static resources' [message #1012908 is a reply to message #1010903]

Fri, 22 February 2013 07:49

Eclipse User

Hi, even any vague answer would likely help Smile

Thanks, Dan.

Re: Bundlor and 'static resources' [message #1016409 is a reply to message #1012908]

Wed, 06 March 2013 06:35

Eclipse User

I would suggest adding an Import-Package statement to your bundlor template.

Re: Bundlor and 'static resources' [message #1018801 is a reply to message #1016409]

Thu, 14 March 2013 09:44

Eclipse User

Static resources are usually located in the resource folder (src/main/resources with Maven).
My resources package exports are done for spring context located in src/main/resources/spring/...xml

Re: Bundlor and 'static resources' [message #1020407 is a reply to message #1018801]

Mon, 18 March 2013 01:16

Eclipse User

Thanks for the replies, when I come back to this problem I'll report back any success.

Re: Bundlor and 'static resources' [message #1431444 is a reply to message #1020407]

Thu, 25 September 2014 13:51

Eclipse User

hi,

at first have you solved that issue.

i run into the same problem. bundlor doesn't export static resources. so i downloaded the bundlor.zip to call it from the command line. And i find out that the generated manifest differs from the phase the project was.

if you call mvn package before calling the cli bunlor it generates all resources.

but i don't know how to fix this in the pom

Previous Topic:	Any owners of the #virgo IRC channel on Freenode around?
Next Topic:	Bundle Error:Import-package:xxxx can not be resovled

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jun 03 00:59:22 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter