Thanks, I am aware of that plugin and have used it before. It sure seems like
the compiler plugin should provide this capability without the need for yet
another plugin to fill the functionality gaps...don't you think?
-Original Message-
From: Curtis Rueden [mailto:ctrue...@wisc.edu]
You can add source directories using the build-helper-maven-plugin.
On Oct 22, 2016 4:39 PM, "Robert Patrick" wrote:
> I am using the section of the POM, not my own plugin, to
> populate some tokens in a Java source file that we use to get build
> information (version, git commit/branch info, b
I am using the section of the POM, not my own plugin, to populate
some tokens in a Java source file that we use to get build information
(version, git commit/branch info, build timestamp, etc).
src/main/resources/templates
hi robert,
what is the plugin that creates files and puts them into the
generated-sources/annotations directory
as from how i understand it works, the plugin should on execution
dynamically register that new extra directory into the list of source
directories that the maven-compiler-plugin will l
This is not a bug, it's a bug fix! Bug introduced in 3.2, fixed in 3.5.1
(see release notes for that version).
Your plugin should use its own output directory and add it as a source root.
Le sam. 22 oct. 2016 23:18, Robert Patrick a
écrit :
> Periodically, I update the versions of the Maven plu
Periodically, I update the versions of the Maven plugins for my projects.
Today was one of those days. What I found is that the maven-compiler-plugin
3.5.1's compile goal no longer seems to not be including the
${project.build.directory}/generated-sources/annotations
directory in the compile.
Yep, I am on windows 7 and get the same thing. It seems to have calmed
down with Nano.1
On 10/22/2016 2:44 PM, Robert Patrick wrote:
> Hi,
>
>
>
> I am seeing a periodic error when running our builds on Windows. When
> running "mvn clean verify" I occasionally see errors like the following:
>
Hi,
I am seeing a periodic error when running our builds on Windows. When running
"mvn clean verify" I occasionally see errors like the following:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.5.1:testCompile (test-compile)
on project single-application
You could write a custom enforcer rule to check the classifier of projects
with particular groupIds:
http://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html
Then configure the enforcer plugin to apply that rule in your corporate pom
or wherever you want to enforce it...
On 22 Oc
Short answer: no
On phone, so can't give long answer
On Friday 21 October 2016, Rémy Saissy wrote:
> Hi,
> is there a Maven plugin that allows to automatically append a classifier
> given a groupId?
>
> I would do something like that:
>
>
> org.apache.maven.plugins
> maven
10 matches
Mail list logo
