And I'm referring to the posts back from October.
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-in-5-minutes-doesn-t-work-tp510820p5553793.html
Sent from the Maven - Users mailing list archive at Nabble.com.
--
I have all my proxies turned off under 'System Preferences' (I'm on mac OSX).
But I get the error Wasi getting before he disabled his proxies.
Any advice?
Thanks
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-in-5-minutes-doesn-t-work-tp510820p5553789.html
Sent from the
Mike,
I'm with you fully.
This thread is a suggestion I made based on tying versioning to concepts
within the SCM very tightly.
In short, I was trying to provide three types of versioning:
* I want the latest official build, *of a branch*, for a particular
dependency (say, master-SNAPSHOT, o
Could you be a bit more concrete, give a few examples where you feel
restricted, describe the workflow you'd like to implement... things like
that.
Regards,
Ansgar
Am 10.03.2012 18:43 schrieb "Mike Power" :
> Has there been any thought to changing the design maven uses for
> versioning? I often
Has there been any thought to changing the design maven uses for
versioning? I often find that the versioning system is too constrictive
and really does not fit well with the actual work flows of software
development.
I was wondering if there was a general consensus that software
development
2012/3/10 Seth Call
>
> There seem to be a good deal of issues open related directly to this.
>
> http://jira.codehaus.org/browse/MNG-2971
>
> I'll link to this thread in the JIRA bug as a use-case for fixing it.
Very good.
That issue depends on http://jira.codehaus.org/browse/MINSTALL-50,
which
