I've been thinking about this and would like to sum up:
- need multiple branches as well. Something for later, but in the same way
id is unique by groupId:artifactId:type, I think it actually gets added to
version along the lines of version:branch:snapshot.
- I don't think editing currentVersion
> I am trying to find about the best practices related to
> SNAPSHOT dependencies. More and more I think about them I
> find that some things are rather not clear and quite inconsistent.
>
> There is one misleading thing: We often find in POMs (maven,
> maven plugins do that):
>
>
> 3
> m
On Wed, 2004-01-07 at 10:32, John Casey wrote:
> Is it a little naive to assume that active development can only take
> place on one branch at a time?
I'm not assuming that at all, I'm telling you what a SNAPSHOT was
originally defined as. I said before that the notion of a SNAPSHOT may
need to be
> > maven jar:install (will put maven-1.1-SNAPSHOT to repository)
>
> That should probably be altered. That really shouldn't go into the
> repository.
>
[...]
> > Maybe indeed it is reasonable to lock usage of snapshot to
> one branch (like
> > 1.0-SNAPSHOT, 1.1-SNAPSHOT)?
>
> This was al
Is it a little naive to assume that active development can only take
place on one branch at a time? It seems to me that this is what we
assume when we dictate that we can only have a single SNAPSHOT version
of code out there. In fact, I have worked on projects wherein we were
testing bugfixes on o
On Wed, 2004-01-07 at 09:29, Maczka Michal wrote:
> I am trying to find about the best practices related to SNAPSHOT
> dependencies.
> More and more I think about them I find that some things are rather not
> clear and quite inconsistent.
>
> There is one misleading thing: We often find in POMs (m
