Hi Olivier and thanks for your fast reply. I need the validation to work with most tools and without any special configuration/programming. Therefore the first solution, accessing the schema in an archive, is not suitable.
The other solution seems suitable at first sight. But what about the version information? After all, we use Maven also because of the central artifact repository, in which artifacts are stored in a versioned manner. Putting the schema files in the site, makes them unversioned entities and this is not true. Schema files change from time to time and backwards compatibility cannot be always preserved -- therefore we need the versioning stuff. Is it possible to write an M2 plugin to do the "directory" packaging? Adrian. LAMY Olivier wrote: > Hi, > Workarounds for this : > I have done this with putting schema in src/main/resources. > The result is an artifact which contains only the schemas. > For validation : add the artifact in dependencies and load the schema with a > getResource and use your favorite parser. > > An other one is to put your schemas in src/site/resources and deploy your > site (the schemas will in the root folder of the web site). With this one, > you can use schemaLocation. > > -- > Olivier > > > -----Message d'origine----- > De : news [mailto:[EMAIL PROTECTED] De la part de Adrian Herscu > Envoyé : samedi 23 septembre 2006 13:54 > À : users@maven.apache.org > Objet : [m2] Packaging as directory > > Hi all, > > I have a project which contains only XML schema files. > Other project files depend on these XML schemas for validation, i.e. > there must be some fixed URL for the XML validator to find the appropriate > XML schema for each one of the validating XML files (this URL is contained by > the XML schemaLocation property). > > I would like to point the XML schemaLocation property to an URL in my M2 > repository where the XML schema files are deployed. The problem is that the > deployment artifact is archived as a WAR file and the repository server does > not know how to unpack the archive on demand and the schema files remain > unaccessible :-( > > I am thinking about a "directory" packaging type -- is it possible? > Any other solution? > > Thanks in advance, > Adrian. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > This e-mail, any attachments and the information contained therein ("this > message") are confidential and intended solely for the use of the > addressee(s). If you have received this message in error please send it back > to the sender and delete it. Unauthorized publication, use, dissemination or > disclosure of this message, either in whole or in part is strictly prohibited. > ********************************************************************** > Ce message électronique et tous les fichiers joints ainsi que les > informations contenues dans ce message ( ci après "le message" ), sont > confidentiels et destinés exclusivement à l'usage de la personne à laquelle > ils sont adressés. Si vous avez reçu ce message par erreur, merci de le > renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, > totale ou partielle ou divulgation sous quelque forme que se soit non > expressément autorisées de ce message, sont interdites. > ********************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
