I am able to solve the problem in my maven project with any Java-8+ version and Lombok 1.18.2 version <dependency> <groupId>org.projectlombok</groupId> <artifactId>lombok</artifactId> <version>1.18.2</version> <scope>provided</scope> </dependency>
The reason is that the Sonar Maven Plugin is hosted at the Codehaus Mojo project and benefits from the groupId “org.codehaus.mojo”. This allows to use the shortcut “sonar:sonar” instead of “org.codehaus.mojo:sonar-maven-plugin::sonar” (see the section “Configuring Maven to Search for Plugins” of the Maven documentation)
Maybe this is related to a unresolved issue in Maven: https://issues.apache.org/jira/browse/MNG-5346 For my plugin projects, i could workaround by adding an explicit execution of the maven-plugin-plugin: <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-plugin-plugin</artifactId> <version>3.2</version> <configuration> <!– see http://jira.codehaus.org/browse/MNG-5346 –> <skipErrorNoDescriptorsFound>true</skipErrorNoDescriptorsFound> </configuration> <executions> <execution> <id>mojo-descriptor</id> <goals> <goal>descriptor</goal> </goals> </execution> </executions> </plugin> </plugins> </build> But see the comments in … Read more
Try mvn -help -l,–log-file <arg> Log file to where all build output will go. mvn <your parameters> –log-file log.txt
I highly recommend the maven-nar-plugin. I find it superior in many ways to the alternatives. It doesn’t require listing out source files, handles multiple OSes and architectures, handles unit and integration tests, and generally follows “the maven way”. It introduces a new kind of packaging – the NAR, or “native archive”, that contains the artifact … Read more
I have a doubt about what you are trying to do but but I’ll assume you want to reuse the tests that you have created for a project (module1) in another. As explained in the note at the bottom of the Guide to using attached tests: Note that previous editions of this guide suggested to … Read more
Eclipse artifact searching depends on repository’s index file. It seems you did not download the index file. Go to Window -> Prefrences -> Maven and check “Download repository index updates on start”. Restart Eclipse and then look at the progress view. An index file should be downloading. After downloading completely, artifact searching will be ready … Read more
As noted in How to execute maven plugin execution directly from command line?, this functionality has been implemented as MNG-5768, and is available in Maven 3.3.1. The change will: extend direct plugin invocation syntax to allow optional @execution-id parameter, e.g., org.apache.maven.plugins:maven-remote-resources-plugin:1.0:process@executionId. So, as long as you give your execution an id: mvn sql:execute@specific-execution-id uses the … Read more
I face this problem too when making new project from android studio. I’ve been able to resolve this by downgrading buildToolsVersion in app gradle setting: change {module-name}/build.gradle line buildToolsVersion “24.0.0 rc1” to buildToolsVersion “23.0.3” @Edit: In Android Studio 2.1 Go to File-> Project Structure->App -> Build Tool Version. Change it to 23.0.3 Do the method … Read more
Let’s summarize. We have/had: the maven-jaxb2-plugin (https://github.com/highsource/maven-jaxb2-plugin) the maven-jaxb-plugin (https://jaxb.dev.java.net/jaxb-maven2-plugin/) the jaxb2-maven-plugin (https://github.com/mojohaus/jaxb2-maven-plugin) Based on the comments of this thread, I’ve always used the maven-jaxb2-plugin (i.e. plugin #1): Concerning the org.jvnet.jaxb2.maven2:maven-jaxb2-plugin versus com.sun.tools.xjc.maven2:maven-jaxb-plugin, from my point of view it’s definitely the first one (http://maven-jaxb2-plugin.java.net/). This plugin has much more features than com.sun.tools.xjc.maven2:maven-jaxb-plugin, the development is … Read more