a note regarding net.shibboleth:parent-v3:2
Tom Zeller
tzeller at dragonacea.biz
Tue Nov 5 13:35:30 EST 2013
>>The whole idea makes me uncomfortable enough to suggest that we should
>>resolve it by *not* having such circular dependency management. That
>>would mean taking spring-extensions and java-support out of the parent
>>project and moving them down into the parent POMs for the individual
>>projects.
>>
>>Is this worth discussing on the next dev call?
>
> Yeah, and FWIW I think that's a simple enough fix to make. It also will
> decouple our parent POM from being tied to specific versions of our own
> utilities, thus reducing the number of times we would need to change it. I
> think we should stick to managing only external dependency versions and
> not our own.
>
> It's really up to a given IdP POM what version of OpenSAML to pull in,
> IMHO.
Sounds like a good idea. Maybe I should have done that instead, oh well.
Added as a Discussion to the next dev call wiki page.
Someone should work through this idea, hopefully it will be trivial. I
will unless someone else is already there, just let me know to avoid
duplication of effort.
>>I am not, personally, very fond of the tag-from-workspace way of doing
>>things, although that's what we document as our procedures. I think
>>that's mainly a svn-specific convention and I come from the "check it in
>>and then tag it" generation (although that's obviously how Git works,
>>too, so everything old is new again).
I feel the same way.
> Not sure I see the difference, though with svn you can do a direct cp of a
> particular revision to become the tag.
The difference, to me, is the loss of history on the thing copied from.
>>I'm a bit surprised that you seem to be losing history, though.
>
> It's that the cp doesn't create a history on the original trunk/branch.
> The tag knows its history, but there's no record of the tag in the history
> of the revisions the tag was created from.
>
> So if you look at a given source file's history from a branch, for
> example, there's no log of which revisions became which tags.
Which is what I consider to be a loss of history. Not really, not
technically, but I just wanted the history of trunk to include "Tag as
version X", so that history is "linear", meaning you only have to look
in one place, one thread, by which I mean trunk. The "Tag as version
X" comment should exist both on the thing copied from and to, IMHO,
for sanity.
As an aside : I hope to work through the release process again,
avoiding manipulating a local working copy too much, and preferring
mvn commands to emacs|vi.
More information about the dev
mailing list