On Tue, Jun 19, 2012 at 10:34 AM, Vincent Massol <[email protected]> wrote:
On Jun 15, 2012, at 12:26 PM, Thomas Mortagne wrote:
Hi devs,
Since I got some veto on http://markmail.org/message/feavtmfokcsaalpo lets cut all that in small peaces.
The today's episode is about finding what is the war we are running it at runtime to list it in the core extensions (among other things it allows to check for available updates).
Like the JAR packages, a WAR contains pom.xml file, problem is that this pom.xml file is not in a "stable" location (META-INF/<groupId>/<artifactId>/pom.xml) and I can't find any generic way to scan a WAR like Reflection allows to scan jars files from the classpath.
So as a last resort solution I propose to include the extension identifier in the METAINF.MF at build time. This will give me the entry point I need to find the pom.xml and gather more detailed informations about the war to put it as core extension.
WDYT ?
So this means that we put our extension ids in META-INF/MANIFEST.MF to have self-describing extensions.
That seems a good idea to me. It also allows to recognize if a given artifact is a xwiki extension or not.
Yes I tough it was a nice information to add to the META-INF/MANIFEST.MF for all sort of uses cases anyway.
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne