+1 for moving to git from me as well. We. use Maven in about 1000 inhouse
projects (95% still using SVN) and Maven adding artifactId out of the blue
at free will in inheriting projects is a pain in the neck for SVN as well,
while trying out releases completely locally with git is really helpful
IMO
Hello all,
I have pondered a tad about the usability, applicability and underpinnings
of Maven's current way to release artifacts [including source and javadoc
JARs] and sites. I feel that a lot of the confusion posted to diverse
mailing lists and forums originates in the release plugin, the site
Totally fair! :-)
I don't have the time or wrist-strength to go through JIRA and dig out all
of the examples, however anyone can do that. I don't use SCM except during
release, either.
I'd argue that it's not good enough for m-rel-p use, however it may well be
good enough for MOJO use cases of th
I do get the feeling that you refer to the general Git functionality as
implemented by the Maven SCM for Git.
In that case, I agree completely with your statement.
Do you feel that the (relatively limited) SCM feature set used within the
normal operation of the maven-release-plugin is also inferio
Sylvain Veyrie
+0
Wayne
On Tue, Jul 23, 2013 at 8:19 AM, Baptiste Mathus wrote:
> Hi,
>
> The following vote is a first (baby) step to keep us moving after our recent
> discussion about this.
>
> *Just checking here nobody is against moving mojo to git, whatever be the
> path.*
>
> (So, this *vote is NOT* abou
Sylvain V
Petter L. H. Eide
Petter L. H. Eide
edite
Petter L.
Petter L.
Petter L. H. Eide
Petter L. H. Eide
Angelina Velinska
Petter L.
Garvin L
Garvin LeClaire
No, it was a contraction. The full form was "Git functionality in Maven
doesn't work "well" at all.". Both Maven and Git work wonderfully, while
not in the same terminal :-p
On Wed, Jul 24, 2013 at 5:12 AM, Lee Thompson wrote:
> Think you have it backwards. Didn't you reverse "git" and "maven"
18 matches
Mail list logo
