[Geoserver-devel] Adding another repository reference

Hi,
as per http://jira.codehaus.org/browse/GEOS-3063
I would like to add a XHTML validation check in our
unit tests using
http://github.com/dashorst/wicket-stuff-markup-validator/tree/master
which is hosted in a repository here:
http://wicketstuff.org/maven/repository/org/wicketstuff/htmlvalidator/1.2/

However, adding another repo reference is going to slow down builds.
Not that much if I specify not to check it for snapshots, but still,
it may be annoying.

What do you think, worth it?
Alternatives:
- don't make xhtml compliance checks
- push this jar to the opengeo repo

Let me know

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

Andrea Aime wrote:

Hi,
as per http://jira.codehaus.org/browse/GEOS-3063
I would like to add a XHTML validation check in our
unit tests using
http://github.com/dashorst/wicket-stuff-markup-validator/tree/master
which is hosted in a repository here:
http://wicketstuff.org/maven/repository/org/wicketstuff/htmlvalidator/1.2/

However, adding another repo reference is going to slow down builds.
Not that much if I specify not to check it for snapshots, but still,
it may be annoying.

What do you think, worth it?
Alternatives:
- don't make xhtml compliance checks
- push this jar to the opengeo repo

I think putting into our repo should be fine right? After you have the jar locally it should be one liner with mvn install:install-file to put into the repo.

Let me know

Cheers
Andrea

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

I'd be for pushing to OpenGeo. I'm already doing that for H2.

-Arne

Andrea Aime wrote:

Hi,
as per http://jira.codehaus.org/browse/GEOS-3063
I would like to add a XHTML validation check in our
unit tests using
http://github.com/dashorst/wicket-stuff-markup-validator/tree/master
which is hosted in a repository here:
http://wicketstuff.org/maven/repository/org/wicketstuff/htmlvalidator/1.2/

However, adding another repo reference is going to slow down builds.
Not that much if I specify not to check it for snapshots, but still,
it may be annoying.

What do you think, worth it?
Alternatives:
- don't make xhtml compliance checks
- push this jar to the opengeo repo

Let me know

Cheers
Andrea

--
Arne Kepp
OpenGeo - http://opengeo.org
Expert service straight from the developers