[maven-compiler-plugin] Possibly bug: annotationProcessorPath assuming classifier=processor

the project website. > [ERROR] > [ERROR]   Then, install it using the command: > [ERROR]   mvn install:install-file -DgroupId=io.dekorate > -DartifactId=kubernetes-annotations -Dversion=0.9-SNAPSHOT > -Dclassifier=processor -Dpackaging=jar -Dfile=/path/to/file Am I missing something or is it a bug? thanks, Cristiano

Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

le with it. Would not use it if I have a choice. best regards, Cristiano  On 08/06/2019 05:29, Tibor Digana wrote: > Why you use Eclipse. Use InteliJ IDEA. It is professional tool. Every > company has money to buy enterprise IDEA, the company wouln'd say no > because it is price

Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

Thanks all, I've confirmed that upgrading this mavenarchiver connector and also m2e (thanks Mickael) resolved my issue. best regards, Cristiano On 10/06/2019 04:11, Anders Hammar wrote: > Please read the bug report [1], which was reference in the first reply to > this thread.

Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

oject that has it as its parent POM. The error has no description and its title is "Unknown". It took some time to track the culprit down and after I have downgraded the maven-jar-plugin to 3.1.1 the error was gone. I'm curious about this... best

Re: Possible bug in the ProjectBuilder (3.5.4) ?

= session.getProjectBuildingRequest(); best regards, Cristiano On 24/09/2018 21:17, Cristiano wrote: Hello, I need some assistance in order to identify whether the issue I'm facing is a bug or a missing feature. I'm adding a goal to my plugin that must read a POM project from a repository and get details

Possible bug in the ProjectBuilder (3.5.4) ?

unknown-version], /home/cvgaviao/.m2/repository/br/com/c8tech/releng/fpom-deps-felix/2.1/fpom-deps-felix-2.1.pom, line 337, column 21 could someone tell me if its a missing feature, a bug or maybe am I missing something ? thanks a lot, Cristiano

AbstractArtifactMetadata deprecation?

t way to create and attach a pom to an artifact ? thanks, Cristiano - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: Strange problem with custom ArtifactHandler

After having lost many hours I finally found where the problem is likely to be... :-( maven is using aether for dependency resolution, but aether has not a concept of packaging and extension as maven has. it only has extension. as a workaround maven is saving the packaging type inside the aet

Re: Strange problem with custom ArtifactHandler

Well, is not the dot the culprit... I tried with another packaging name and I got the same result. I still don't know who injects the ArtifactHandler in the dependency... any idea ? - To unsubscribe, e-mail: dev-unsubscr...@

Strange problem with custom ArtifactHandler

"bundle": [WARN] CONVERTING:org.lunifera.maven.lib.mojo.handlers.BundleArtifactHandler | org.apache.felix.scr I want to investigate if the dot is the culprit. Could someone tell me which class is responsible to set the ArtifactHandler for a dependency object ? thanks, Cristiano

Re: Would be possible to inject com.google.inject.Injector in a mojo or other component?

Hi Stuart, thanks for the explanation ! the map solution also have fit well in my case. many thanks and best regards, Cristiano On 06-01-2016 19:50, Stuart McCulloch wrote: Hi Cristiano, Maven core doesn’t expose the “com.google.inject” package to plugins, which means the Injector class

Would be possible to inject com.google.inject.Injector in a mojo or other component?

@Inject private Injector injector; Its not allowed or am I missing something? thanks, Cristiano

Re: found some errors running takari-lifecycle build with java 1.8

ok, done: https://github.com/takari/takari-lifecycle/issues/11 regards, Cristiano On 22-02-2015 00:22, Igor Fedorenko wrote: Looks like takari plugin test harness can't talk to one of your project's repositories. Can you please open issue at github so we don't spam th

Re: found some errors running takari-lifecycle build with java 1.8

the takari-lifecycle tests again. It seems that exists some issue related to downloading this apache-maven archive. regards, Cristiano On 21-02-2015 20:40, Cristiano Gavião wrote: Hi Igor, That is strange... I deleted all versions of apache-maven from local my repo. Then I built (package)

Re: found some errors running takari-lifecycle build with java 1.8

r you. If not, file github issue like Jason suggested. -- Regards, Igor On 2015-02-21 16:08, Cristiano Gavião wrote: Hello, I'm trying to learn how to use the new testing tools provided by takari. Started by the tests in takari-lifecycle-plugin-its from github master branch. but I'm

found some errors running takari-lifecycle build with java 1.8

ForkedBooter.java:203) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) would be these errors caused by java 8 ? regards, Cristiano

POM mixins ?

Hi, couple years ago I read an interview from Jason where he talk about pom mixins [1]. But I couldn't find any information about it since then. Was this feature already implemented ? thanks [1] - http://blog.sonatype.com/2010/03/eclipsemagazine-interview-with-jason-van-zyl ---