svn.relative.location

[Ian Young]

On 6 Mar 2013, at 22:32, Brent Putman <putmanb at georgetown.edu> wrote:

> On 3/4/13 6:18 PM, Ian Young wrote:
>> 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.
> 
> Ok, I did that.

Triffic, thanks.

> I also changed java-support's svn.relative.location to
> 'utilities/java-support' instead of just 'utilities'.  That's really the
> intention of how it's supposed to work.

Had a moment of panic there, but yes that's the way xmlsectool's POM looks.

> I think I'm inclined to say right now that we should leave the <scm>
> part in the POM, if for no other reason than internal documentation and
> just having the data available.  If we can't get the report stuff to
> work (JPAR-12), then we should just pull that report out of the report
> set, which is configurable in the POM. 

Seems reasonable to me.

	-- 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/20130306/53ce52cc/attachment.bin