Re: release-plugin: execute at generate-sources phase
Sorry, i do not get it. My explict configuration in buildpluginsplugin overwrites the default config (or, that is what i expect). Where is the conflict? I thought that i just missed a configuration... Thanks Klaus On Tue, Sep 23, 2008 at 6:35 AM, Brett Porter [EMAIL PROTECTED]wrote: I think the plugin level configuration would conflict, overriding the section from the build section. - Brett 2008/9/19 Klaus H. [EMAIL PROTECTED]: Hi all, i need to filter a resource file before the generate-sources phase (input file for source-generator). So i bound the maven-resources-plugin to the generate-sources phase. The point is that filtering does not work anymore. Even the filtering in the default lifecycle-phase of the generator plugin does not work anymore. Seem as explicity naming the resource-plugin overwrites some default configuration. Any idea which one this could be? Or any other idea how this could be solved.. Thanks, Klaus --- build plugins plugin artifactIdmaven-resources-plugin/artifactId executions execution idfilterGeneratorInput/id phasegenerate-sources/phase goals goalresources/goal /goals configuration resources resource filteringtrue/filtering directorysrc/main/resources/directory includes includeGeneratorInput.xml/include /includes /resource /resources outputDirectorytarget\klaus/outputDirectory /configuration /execution /executions configuration resources resource filteringtrue/filtering directorysrc/main/resources/META-INF/directory /resource /resources /configuration /plugin !-- (Re-)Generate -- plugin artifactIdmyGeneratorPlugin/artifactId ... -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: release-plugin: execute at generate-sources phase
I would normally expect to see the resources in build, but you have a second configuration outside the execution attempting to override that. Is it your intent to copy the one filtered file from src/main/resources in process-sources and then only the files in src/main/resources/META-INF during the normal build? - Brett 2008/9/25 Klaus [EMAIL PROTECTED]: Sorry, i do not get it. My explict configuration in buildpluginsplugin overwrites the default config (or, that is what i expect). Where is the conflict? I thought that i just missed a configuration... Thanks Klaus On Tue, Sep 23, 2008 at 6:35 AM, Brett Porter [EMAIL PROTECTED]wrote: I think the plugin level configuration would conflict, overriding the section from the build section. - Brett 2008/9/19 Klaus H. [EMAIL PROTECTED]: Hi all, i need to filter a resource file before the generate-sources phase (input file for source-generator). So i bound the maven-resources-plugin to the generate-sources phase. The point is that filtering does not work anymore. Even the filtering in the default lifecycle-phase of the generator plugin does not work anymore. Seem as explicity naming the resource-plugin overwrites some default configuration. Any idea which one this could be? Or any other idea how this could be solved.. Thanks, Klaus --- build plugins plugin artifactIdmaven-resources-plugin/artifactId executions execution idfilterGeneratorInput/id phasegenerate-sources/phase goals goalresources/goal /goals configuration resources resource filteringtrue/filtering directorysrc/main/resources/directory includes includeGeneratorInput.xml/include /includes /resource /resources outputDirectorytarget\klaus/outputDirectory /configuration /execution /executions configuration resources resource filteringtrue/filtering directorysrc/main/resources/META-INF/directory /resource /resources /configuration /plugin !-- (Re-)Generate -- plugin artifactIdmyGeneratorPlugin/artifactId ... -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: release-plugin: execute at generate-sources phase
I think the plugin level configuration would conflict, overriding the section from the build section. - Brett 2008/9/19 Klaus H. [EMAIL PROTECTED]: Hi all, i need to filter a resource file before the generate-sources phase (input file for source-generator). So i bound the maven-resources-plugin to the generate-sources phase. The point is that filtering does not work anymore. Even the filtering in the default lifecycle-phase of the generator plugin does not work anymore. Seem as explicity naming the resource-plugin overwrites some default configuration. Any idea which one this could be? Or any other idea how this could be solved.. Thanks, Klaus --- build plugins plugin artifactIdmaven-resources-plugin/artifactId executions execution idfilterGeneratorInput/id phasegenerate-sources/phase goals goalresources/goal /goals configuration resources resource filteringtrue/filtering directorysrc/main/resources/directory includes includeGeneratorInput.xml/include /includes /resource /resources outputDirectorytarget\klaus/outputDirectory /configuration /execution /executions configuration resources resource filteringtrue/filtering directorysrc/main/resources/META-INF/directory /resource /resources /configuration /plugin !-- (Re-)Generate -- plugin artifactIdmyGeneratorPlugin/artifactId ... -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
