Hello.

I am new to Shiro, so I tried importing the sample projects (quickstart,
web) into Eclipse (in which I am using m2e 1.3.1) on Windows 7.

These projects give the following build errors in their pom.xml files:
Description     Resource        Path    Location        Type
Plugin execution not covered by lifecycle configuration:
org.codehaus.gmaven:gmaven-plugin:1.3:compile (execution: default, phase:
compile)        pom.xml /web    line 23 Maven Project Build Lifecycle Mapping 
Problem
Plugin execution not covered by lifecycle configuration:
org.codehaus.gmaven:gmaven-plugin:1.3:testCompile (execution: default,
phase: test-compile)    pom.xml /web    line 23 Maven Project Build Lifecycle
Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.codehaus.gmaven:gmaven-plugin:1.3:testCompile (execution: default,
phase: test-compile)    pom.xml /quickstart     line 23 Maven Project Build
Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.codehaus.gmaven:gmaven-plugin:1.3:compile (execution: default, phase:
compile)        pom.xml /quickstart     line 23 Maven Project Build Lifecycle 
Mapping
Problem


I could fix the problem in the top-level (parent) pom.xml by removing the
indicated Groovy plugin entry under plugins (but not under
pluginManagement):
            <plugins>
                .....
                
                <plugin>
                    <groupId>org.codehaus.gmaven</groupId>
                    <artifactId>gmaven-plugin</artifactId>
                    <version>${gmaven.version}</version>
                    <executions>
                        <execution>
                            <goals>
                                <goal>compile</goal>
                                <goal>testCompile</goal>
                            </goals>
                        </execution>
                    </executions>
                </plugin>
            </plugins>

The tests still seem to run fine with this removal (using "mvn compile test"
as well as "mvn compile exec:java"), but as I am neither a Shiro nor a Maven
expert, I am reluctant to trust what I did.  Has anyone else observed these
errors, and is there a better fix?

I noticed a similar problem had been reported and fixed with SHIRO-299,
although no details are provided, so I am unclear if that may be related:
https://issues.apache.org/jira/browse/SHIRO-299

Thanks for any help.
+ Richard




--
View this message in context: 
http://shiro-user.582556.n2.nabble.com/Problem-with-Eclipse-m2e-with-sample-projects-tp7578573.html
Sent from the Shiro User mailing list archive at Nabble.com.

Reply via email to