[dna-issues] [JBoss JIRA] Created: (DNA-600) mvn eclipse:clean eclipse:eclipse doesn't work on dna-connector-store-jpa

[Serge Emmanuel Pagop (JIRA)]

mvn eclipse:clean eclipse:eclipse doesn't work on dna-connector-store-jpa
-------------------------------------------------------------------------

                 Key: DNA-600
                 URL: https://jira.jboss.org/jira/browse/DNA-600
             Project: DNA
          Issue Type: Bug
          Components: Development Environment
    Affects Versions: 0.7, 1.0, 1.1, Future Releases
         Environment: MAC OS X 10.6.2, java version "1.6.0_17", Apache Maven 2.2.0 
            Reporter: Serge Emmanuel Pagop
            Assignee: Serge Emmanuel Pagop
            Priority: Critical
             Fix For: 0.7


During building the DNA modules with mvn clean install eclipse:clean eclipse:eclipse I got this error:

------ Start Error Trace
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Request to merge when 'filtering' is not identical. Original=resource src/test/resources: output=target/test-classes, include=[*|**/*], exclude=[database.properties|**/*.java], test=true, filtering=false, merging with=resource src/test/resources: output=target/test-classes, include=[database.properties], exclude=[**/*.java], test=true, filtering=true
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
        at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Request to merge when 'filtering' is not identical. Original=resource src/test/resources: output=target/test-classes, include=[*|**/*], exclude=[database.properties|**/*.java], test=true, filtering=false, merging with=resource src/test/resources: output=target/test-classes, include=[database.properties], exclude=[**/*.java], test=true, filtering=true

------ End Error Trace

Because this is a bug in the maven eclipse plugin version 2.7, this link "http://stackoverflow.com/questions/1397903/setting-project-for-eclipse-using-maven" gives more information about

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira