HI,
The Mojo team is pleased to announce the release of the CodeNarc Maven Plugin
version 0.17-1 .
CodeNarc scans Groovy source code, looking for violations of predefined or
custom rules and generates an HTML report of the results. These rules include
checks for coding standards, or searching
We started by changing the versions of everything but as we got to 70
modules for the application we stopped.
We stepped back and started to look at our code in the same way that we
looked at third party (Apache, Spring, etc.) libraries that we used.
We were perfectly able to use the same version
True .. personally i am also not in favor of bumping version of all
artifacts when only one artifacts has changed in the project. This also
leads to addition of extra space in artifactory or any repo manager as the
same artifact will be stored with just diff version number without any
need. Consume
Am 08.04.2012 07:15 schrieb "Domingo José González Cabrera" <
doming...@gmrcanarias.com>:
>
> Hi, How I can do for set Passive mode to false with maven3
What kind of "passive mode" are you referring to? Please give some more
context regarding what you are trying to achieve.
Regards,
Ansgar
Thanks Wayne, It now works.
--
View this message in context:
http://maven.40175.n5.nabble.com/Error-running-Maven-tp5622633p5625692.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail:
Your described scenario is the common scenario for Maven. You should
never change (or delete) a release. Your repo manager should always be
configured to deny that.
You're describing the two possible solutions. Either bump the version
on all artifacts produced, or just deploy the artifact that has
