[ANN] XSpec Tests Maven Plugin

[Adam Retter]

Hi everyone,

Just to let you know that we needed to execute XSpec tests as part of our Maven builds (as part of our larger Continuous Integration effort). Whilst this is possible using the xml-maven-plugin, any test failures would not cause the build to fail. There is a Maven archetype mentioned on the XSpec homepage as part of the 'jxsl' project, but a closer look showed that this does not really do anything practical yet.

As such we have built the xspec-maven-plugin - https://github.com/adamretter/xspec-maven-plugin

Our plugin utilises the latest XSpec implementation (0.4.0.rc1) and is released under the permissive BSD Licence.

The plugin is quite configurable as you will see in the details linked above, but typically we place our XSLTs under test into src/main/resources and our XSpec tests into src/test/xspec, and then just add the plugin configuration to the build part of our pom.xml. The plugin has been published to Maven Central and as such just including its definition in your pom.xml file should be enough and you should not have to download anything else.

Note - An XSpec test in src/test/xspec must of course then use the relative path "../../main/resources/something.xslt" in its 'description/@stylesheet' attribute to reference its stylesheet.

I hope this will be of use for others too. If you are so inclined we welcome issue/feature requests and pull-requests through the GitHub page linked above.

Thanks Adam.

[Romain Deltour]

Oh, we developed one too (as mentioned previously in another thread):

https://github.com/daisy-consortium/xspec-maven-plugin

Unfortunate duplication of effort… but well, two (or more) is better than none :)

What about trying to merge the code bases and move it to an "xspec" github organization ?

Romain.

--
You received this message because you are subscribed to the Google Groups "XSpec" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xspec-users...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Adam Retter]

Hi Romain,

That is indeed unfortunate, I did Google quite a bit before starting
and searched through Maven Central also. I note your plugin does not
seem to be in Maven Central?

I would be happy of course to remove duplication and work together on
this. I think we can only improve this by merging code and ideas :-)

An XSpec GitHub organisation would be excellent, however there is one
on GoogleCode already, and I do not like to duplicate organisations
either! Perhaps Jeni and Florent could be persuaded to migrate from
GoogleCode to GitHub? I would be happy to assist with the migration...

Cheers Adam.

--
Adam Retter

skype: adam.retter
tweet: adamretter
http://www.adamretter.org.uk

[Romain Deltour]

On 28 sept. 2013, at 14:14, Adam Retter <adam....@googlemail.com> wrote:

> Hi Romain,
>
> That is indeed unfortunate, I did Google quite a bit before starting
> and searched through Maven Central also. I note your plugin does not
> seem to be in Maven Central?

No, it is still 1.0.0-SNAPSHOT, on Sonatype's OSS repository. The code is pretty stable though, and I was planning to "release" 1.0.0 on Maven Central soon. I should have done that several weeks ago and properly announce it, but well… time flies.

I also have local code for a Maven site for the plugin, I will polish it and push it.

> I would be happy of course to remove duplication and work together on
> this. I think we can only improve this by merging code and ideas :-)

Indeed :)

>
> An XSpec GitHub organisation would be excellent, however there is one
> on GoogleCode already, and I do not like to duplicate organisations
> either! Perhaps Jeni and Florent could be persuaded to migrate from

> GoogleCode to GitHub? I would be happy to assist with the migration…

I agree. I would personally be happy if everything was on GitHub, which I find much better at allowing external contributions (via forks + pull requests).

Florent, Jeni, thoughts ?

Romain.

[Florent Georges]

That is indeed part of my plans...  Let me think about it next week when I'm back (meaning: do not hesitate to remind me about it next week :-P)

Regards,