Hi, 

the reason was the following:

In my (parent) pom.xml I had:
<build>
        <plugins>
                ...
                        <plugin>
 <groupId>org.apache.maven.plugins</groupId>
 <artifactId>maven-changes-plugin</artifactId>
                                <executions>
                                        <execution>
                                                <goals>
 <goal>announcement-generate</goal>
                                                </goals>
 <id>announcement-generate</id>
                                        </execution>
                                        <execution>
                                                <goals>
 <goal>announcement-mail</goal>
                                                </goals>
                                                <id>announcement-mail</id>
                                        </execution>
                                </executions>
                                <configuration>
                                        <smtpHost>xxxxxxxx</smtpHost>
                                        <smtpPort 
implementation="java.lang.Integer">xx</smtpPort>
                                        <toAddresses>
                                                <toAddress 
implementation="java.lang.String">[EMAIL PROTECTED]</toAddress>
                                        </toAddresses>
                                </configuration>
                        </plugin>
                ...

=> the execution section wasn´t bound to a phase. That seems to break the 
build lifecycle and execution of the "generate-sources" phase......

After fixing that, I now run only into 

javax.xml.parsers.FactoryConfigurationError: Provider 
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found
        at 
javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:104)
        at 
com.sun.tools.xjc.reader.internalizer.DOMForest.<init>(DOMForest.java:137)
        at 
com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.resetSchema(SchemaCompilerImpl.java:188)
        at 
com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.<init>(SchemaCompilerImpl.java:88)
        at com.sun.tools.xjc.api.XJC.createSchemaCompiler(XJC.java:51)
        at 
com.sun.tools.ws.wscompile.WsimportOptions.<init>(WsimportOptions.java:77)
        at 
com.sun.tools.ws.wscompile.WsimportTool.<init>(WsimportTool.java:61)
        at 
com.sun.tools.ws.wscompile.WsimportTool.<init>(WsimportTool.java:64)
        at 
org.codehaus.mojo.jaxws.WsImportMojo.wsImport(WsImportMojo.java:266)
        at 
org.codehaus.mojo.jaxws.WsImportMojo.processLocalWsdlFiles(WsImportMojo.java:229)
        at 
org.codehaus.mojo.jaxws.WsImportMojo.execute(WsImportMojo.java:184)
        at 
org.codehaus.mojo.jaxws.MainWsImportMojo.execute(MainWsImportMojo.java:15)
        at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
        at 
org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
        at 
org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
        at 
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
        at 
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
        at 
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
        at 
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl$MavenExecutor.execute(MavenProjectManagerImpl.java:1007)
        at 
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl$1.execute(MavenProjectManagerImpl.java:1034)
        at 
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.execute(MavenProjectManagerImpl.java:963)
        at 
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.execute(MavenProjectManagerImpl.java:1031)
        at 
org.maven.ide.eclipse.project.MavenProjectFacade.execute(MavenProjectFacade.java:280)
        at 
org.maven.ide.eclipse.container.MavenBuilder.executePostBuild(MavenBuilder.java:135)
        at 
org.maven.ide.eclipse.container.MavenBuilder.build(MavenBuilder.java:72)
        at 
org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:624)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
        at 
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:166)
        at 
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:197)
        at 
org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:246)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
        at 
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:249)
        at 
org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:302)
        at 
org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:334)
        at 
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:137)
        at 
org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)





Eugene Kuleshov <[EMAIL PROTECTED]> 
15.07.2008 17:55
Bitte antworten an
[email protected]


An
[email protected]
Kopie

Thema
Re: [m2eclipse-user] Goals to invoke after project clean arent´t invoked






Torsten,

  Please submit a bug report and attach test project that would allow to 
reproduce this issue. See the following wiki page for more hints. 
http://docs.codehaus.org/display/M2ECLIPSE/Reporting+Issues

  Thanks

  Eugene


[EMAIL PROTECTED] wrote:
>
> Hi,
>
> i´m using 0.9.5 Version of m2eclipse.
> At the (Maven)properties of my project, i configured "package" as the 
> goal that should be invoked, when cleaning the project,
> as described in
>
> 
http://docs.codehaus.org/display/M2ECLIPSE/Project+FAQ#ProjectFAQ-HowtoconfigureMavenprojecttouseseparateoutputfoldersinEclipse
 

>
>
> In my pom.xml I have
>
>                         <plugin>
> 
> <groupId>com.sun.tools.xjc.maven2</groupId>
> 
> <artifactId>maven-jaxb-plugin</artifactId>
> 
>                                 <executions>
>                                         <execution>
>                                                 <id>test</id>
> 
> <phase>generate-test-sources</phase>
>                                                 <goals>
> 
> <goal>generate</goal>
>                                                 </goals>
>                                                 <configuration>
> 
> 
<schemaDirectory>src/test/resources/schemas/com/gide/common/jaxb/</schemaDirectory>
 

>
>                                                         <includeSchemas>
> 
> <includeSchema>test.xsd</includeSchema>
> </includeSchemas>
> 
> <generatePackage>com.gide.common.jaxb</generatePackage>
> 
> 
<generateDirectory>${project.basedir}/${target.dir}/generated-test-sources/java</generateDirectory>
 

>
>                                                 </configuration>
>                                         </execution>
>
>                                 </executions>
>                         </plugin>
>
> I´m now waiting for Maven to generate-test-sources, when cleaning in 
> Eclipse.
> But nothing happens......which results into a compile error, because 
> the generated-sources are missing.
>
> Any idea?
>
> Thanx, Torsten


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



Reply via email to