svn.relative.location

[Ian Young]

On 4 Mar 2013, at 21:18, Brent Putman <putmanb at georgetown.edu> wrote:

> So we should just pick one way or another.  I'd personally lean towards saying the leading
> '/' doesn't go in the svn.relative.location, but rather in the URL in
> the SCM section in the POM.

That seemed like the simplest alternative to me too.  It just involves changing the V3 parent POM to match the V2 parent POM in this area, and optionally removing the now surplus '/' in the svn.relative.location in the java-support POM.

> Of course, all of this is somewhat moot if we can't actually get the SCM
> part of the site generation to work per JPAR-12.  In terms of just the
> literal data in the POM itself, I don't think most people are going to
> derive a lot of value from having to look up the inheritance hierarchy
> across several POM's and manually interpolate it all into the actual
> repo URL.  They're more likely to just go to the website where we list
> all the repo names.

Just removing the SCM part of the POMs is obviously the other major option, if in fact we think it's not giving us anything.

	-- Ian



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4813 bytes
Desc: not available
Url : http://shibboleth.net/pipermail/dev/attachments/20130304/34e37f19/attachment.bin