Good day,
I wonder if this community can provide some hints on handling the following.
At a few last projects I was asked to set (or clean) automated builds up,
so they can get (at least) deployable software package(s) after code
changes in a minimum time. Starting from the final desirable
Hi Viktor,
Do you actually consider this situation as a problem or is it just a
perfectionist talking to me? ;-)
I would say it is a very real challenge of managing projects with many
components.
how would you approach determining those, which are required for final
deliveries, and those,
Hi Curtis,
Thank you very much for your thoughtful reply. I'll review your links... very
curious
Thanks,
Viktor
--- Sent on go
On 13/2/2015, at 17:33, Curtis Rueden ctrue...@wisc.edu wrote:
Hi Viktor,
Do you actually consider this situation as a problem or is it just a
perfectionist
Hello,
I'm using Maven 3.2.5 and I would like to use the Checkstyle plugin in the
newest version (6.3).
The default installation is 5.8, so how can I add the 6.3 version of the plugin
at my pom.xml and
use it on the check goal at the validate phase?
I don’t found the correct pom entries to do
Hello everyone
I thought I knew how maven did dependency conflict resolution: always go with
the version that's closest to the base pom
However, it seems that is not the case. Here is my scenario
I have a pom of packaging=pom, call it A, which is the base where I execute
maven.
So this is my
Provide a sample project with what you expect as the result for a given project.
The dependency plugin does its own weird resolution and M2Eclipse also has its
own resolver (which is closer to what Maven actually does vs the dependency
plugin) and I don't really want to think about your
Hi,
apply
http://maven.apache.org/plugins/maven-checkstyle-plugin/usage.html#Checking_for_Violations_as_Part_of_the_Build
and
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html
Vincent
2015-02-13 21:28 GMT+01:00 Philipp Kraus philipp.kr...@flashpixx.de:
Thanks I have read these instructions, but check style uses the sun_checks.xml
I have add to my build section:
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-checkstyle-plugin/artifactId
version2.14/version
Hello,
I'm using Maven 3.2.5 and I would like to use the Checkstyle plugin in the
newest version (6.3).
The default installation is 5.8, so how can I add the 6.3 version of the plugin
at my pom.xml and
use it on the check goal at the validate phase?
Thanks a lot
Phil
Hi.
We are prototyping following combination for our web site generation:
* maven-site-plugin 3.4
* doxia-module-markdown 1.6
* maven-fluido-skin 1.3.1
According to fluido documentation it has nice source code prettify
feature with line numbers. Alas, I didn't get it to work. Then I found
this
10 matches
Mail list logo