The target platform that they use simply
references folders on disk and provides the appropriate plugins to support
JSP's etc. I am in the process of turning that target definition and directory
structure into a p2 repository (anoyingly the eclipse export target platform
wizard builds a repository with no plugins in the artifacts.xml!).
Igor Fedorenko <igor@xxxxxxxxxxxxxx>
Support for non-standard Manifest location?
No, Tycho still requires OSGi bundle manifest to be
Out of curiosity, can you explain tools involved in development of such
webapps? I assume all webapps' dependencies are available from P2
repositories, how are these repositories get populated?
On 2/17/2014, 10:23, Stephen Rowles wrote:
> Hi all,
> I have some web application bundles, which are valid OSGi bundles
> have their META-INF/MANIFEST.MF is not under the bundle root they
> within a top level folder of BundleContent, so
> I found this old tycho bug:
> However that was back in 2010, there are lots more OSGi based web
> application servers now, so I was wondering if this has moved on and
> been dealt with? I've done LOTS of googling but cannot find any way
> telling tycho how to use a custom location for the manifest. This
> shame as it's the last step in the chain to making these work.
> Any suggestions?
> *Stephen Rowles*
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
> tycho-user mailing list
tycho-user mailing list
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6