When I create a war module with pax (maven packaging war + enabling maven-war-plugin + modifying bnd plugin to support war extension), and run this project with mvn pax:provision, the corresponding bundle located into $
{basedir}
/runner/bundles as a .jar extension (while the one located in my local repo has the .war one). It forbids me to be fully RFC66 compliant, so using jetty 8 (without pax-web) and gemini web 2.0 is just impossible.
CharlieM created PAXCONSTRUCT-138
When I create a war module with pax (maven packaging war + enabling maven-war-plugin + modifying bnd plugin to support war extension), and run this project with mvn pax:provision, the corresponding bundle located into $
{basedir}
/runner/bundles as a .jar extension (while the one located in my local repo has the .war one).
It forbids me to be fully RFC66 compliant, so using jetty 8 (without pax-web) and gemini web 2.0 is just impossible.
Can you do something to correct this?
Best regards for your wonderful framework,
Charlie
Votes: 0, Watches: 1