Problem description:
We have a Jenkins job that runs a maven build that activates certain maven-profiles (maven Goals and options in my case: clean install -U -P all,runtime). The same job activates Sonar plugin as a post-build action. Running the Sonar on the job without pointing to a certain maven profiles assumes that there aren't any instead of passing the same profiles to the Sonar plugin.
While building with maven we often need to perform different kind of actions that were very simple with an old uncle Ant, but can become messy and complicated with Maven: copy files, directories, dependencies, filtering text, creating your "runtime' environment, and new tasks like attaching additional artifacts and etc.
I upload the following jar into Nexus using GAV parameters:
google-api-client-1.6.0-beta.jar
GAV:
Group:com.google.api-client
Artifact:google-api-client
Version:1.6.0-beta
Once i'm done, this is waht i have in the repository:
In Recent years Flex has become the ideal client solution for Java server based projects. Flex compliments Java in many ways and has many similarities to Java. These include, the syntax, the OOP approach and many other features of the two languages that are similar.
In this tutorial, I will demonstrate one aspect of the Flex Java integration by covering the earliest stage of the development process, which is the build and infrastructure creation. In future posts I will cover later stages of the development.
The information about the combination of these two goodies is to say the least scarce. I decided to create a minimal small POC project which
Full credit to Ittai who helped me out with this post.
1-Has a self contained Maven POM, which works out of the box without any major modifications.
2-Explicitly invokes AntInstaller via a configuration file while utilizing an antinstaller properties file
3-Is easy to understand and expand.
Have been wondering how to build your application that have both Java and Scala sources with Maven?
Here you can find a tutorial from http://mackaz.de:
Build a mixed Scala 2.8/Java application and Eclipse Settings for this project
Although I can't fully agree with all of the answers, but I definatelly agree with most of them - an answer to the blog post 'Top ten reasons why maven sucks' can be found here