[
https://issues.apache.org/jira/browse/SUREFIRE-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484124#comment-17484124
]
Markus Spann commented on SUREFIRE-1994:
----------------------------------------
How does this discovery in IntelliJ take place?
Does Idea make educated guesses or does it have explicit support for
javacc-maven-plugin?
I use Eclipse mostly, and I can tell you that *setting up surefire in Eclipse*
for development is quite a hazzle.
My two biggest stumbling blocks were:
# javacc-maven-plugin
# surefire-shared-utils
In Ecipse one needs to hand-configure the surefire-grouper module with an
additional source folder.
I wouldn't want this source folder to exist in the project's build directory.
Every time you do {{clean}} in Maven, the project has compile errors in
Eclipse. And Eclipse cannot rectify those by itself, as it does not know of
javacc.
> Upgrade and configure javacc-maven-plugin in module surefire-grouper
> --------------------------------------------------------------------
>
> Key: SUREFIRE-1994
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1994
> Project: Maven Surefire
> Issue Type: Improvement
> Affects Versions: 3.0.0-M5
> Reporter: Markus Spann
> Priority: Minor
>
> Maven module surefire-grouper uses *javacc-maven-plugin* to generate
> {{GroupMatcherParser}} and other Java sources.
> Upgrade the plugin to the new groupId (org.codehaus.mojo ->
> org.javacc.plugin) and latest version (2.6 -> 3.0.3).
> The plugin by default generates sources into
> {{{}target/generated-sources/javacc/{}}}. This location is inconvenient for
> the Eclipse IDE.
> Configure the plugin to write generated sources to {{src/generated/java}} (an
> often-used location for generated Java sources) and add this location as a
> source folder using {{{}build-helper-maven-plugin{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
