Hi Mirko, thanks for the feedback, issue and sample. I will have a look.@Robert: If you have any ideas (maybe my first guess is true) then please let me know. Debugging Mojos via M2E is still not working as expected for me...
Best regards Jörg Am 08.05.2014 21:25, schrieb Mirko Friedenhagen:
Jörg, I opened http://jira.codehaus.org/browse/MOJO-2030 and attached a small sample project. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Mon, May 5, 2014 at 10:25 AM, Mirko Friedenhagen <mfriedenha...@gmail.com> wrote:Hello Jörg, I have a living example: https://github.com/mfriedenhagen/trivia/tree/with-flatten-maven-plugin (please check out the with-flatten-maven-plugin branch), the java code is in the java directory ;-) My environment: Oracle JDK 1.7.0_55, Mac OS X 10.9.2 and tried Maven 3.0.5, Maven 3.1.1 and Maven 3.2.1. Preparation: ======== git clone https://github.com/mfriedenhagen/trivia.git cd trivia git checkout with-flatten-maven-plugin cd java Without flatten-maven-plugin: ------------------------------------------ mvn clean verify site | grep Rendering [INFO] Rendering site with org.apache.maven.skins:maven-fluido-skin:jar:1.3.1 skin. mvn clean verify site | grep Rendering With flatten-maven-plugin: -------------------------------------- mvn -Pwith-flatten-maven-plugin clean verify site | grep Rendering [INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0 skin. I firstly had this in the main build section and not in a profile, same result though. Of course running "mvn site" alone is not affected, as phase process-resources is never reached :-) Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Sat, May 3, 2014 at 10:15 PM, Jörg Hohwiller <jo...@j-hohwiller.de> wrote:Hi Mikro, are you saying that if flatten-maven-plugin is active in your build section then site generation is impacted negatively? Can you confirm that your site.xml problem goes away if you comment out flatten-maven-plugin? I have not yet observed this... The only reason if this is really happening could be that flatten-maven-plugin is chaning the Project.file. If some awkward mechanism is doing file lookups relative to Project.file - this would be possible. So far I would doubt it. Please double check first. In case it is really an error we should immediately file a JIRA bug. Of course this would not be an expected behaviour... Cheers Jörg Am 03.05.2014 21:22, schrieb Robert Scholte:Hi Mirko, Asking the question already answers it :) The plugin should only change the pom.xml, not the MavenProject instance. So you're saying that the maven-site-plugin has trouble finding the site.xml? This requires some extra investigation. thanks, Robert Op Sat, 03 May 2014 21:09:08 +0200 schreef Mirko Friedenhagen <mfriedenha...@gmail.com>:Hello, I now tried to use the plugin for the first time and observed, that src/site/site.xml was not working anymore, e.g. the skin was not taken correctly. Is this expected? Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
smime.p7s
Description: S/MIME Cryptographic Signature
