Hi, @Vincent : I agree with all your points, my feedback was more on that these points may not be clear for contributors at first (at least, it wasn't for me). My only little worry is that maybe it does not require the same level of knowledge to merely create and publish a simple extension on xwiki.org, and to develop a maven module for it and release it to Nexus staging from github, though it'd be better to have all extensions in a maven repository (for flavors/bundles for example). Additionnally, it seems that with the sample pom provided (for xar), I always get the following error when trying to release: [INFO] --- maven-enforcer-plugin:1.1:enforce (enforce-javadoc-exists) @ xwiki-macro-tabs --- [WARNING] Rule 0: org.apache.maven.plugins.enforcer.EvaluateBeanshell failed with message: Couldn't evaluate condition: ("xar" != "jar") || ("xar" == "jar" && new java.io.File("C:\PRIVATE\tabs-macro\target\checkout\target/xwiki-macro-tabs-1.0.1-SNAPSHOT-javadoc.jar") .exists()) I think maybe it's because of being on Windows (as show by the paths), that would explain why you seem not to have this problem ;-) It's easily workaround by skiping that enforcer rule, but it's kind of a dirty workaround. BR, Jeremie 2013/3/3 Vincent Massol <vincent(a)massol.net>

Hi Vincent, 2013/3/7 Vincent Massol &lt;vincent(a)massol.net&gt; That does not work either ("Failed to evaluate condition..."). I think problem is with '\' and not '/', and that I'm stuck on an enforcer issue [1] I tried to do some string replacements, without success. Then I also checked with a string literal, replacing the condition as follows: <condition>("${project.packaging}" != "jar") || ("${project.packaging}" == "jar" &amp;&amp; "test with a \ character" != "test without it")</condition> That also fails. I think trying to do replacements in beanshell is already too late, it seems to me that it's enforcer that fails to evaluate the beanshell syntax because of non-escaped '\'. Going a little further, the problem is that the path must already be correct before putting the property in the evaluateBeanshell condition. So I've come out with the following solution, that works correctly now. I checked it both for failure and success conditions (missing or existing javadoc jar) : <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>build-helper-maven-plugin</artifactId> <version>1.7</version> <executions> <execution> <id>create-javadoc-filename-property</id> <phase>verify</phase> <goals><goal>regex-property</goal></goals> <configuration> <name>javadoc-filename</name> <value>${project.build.directory}/${project.build.finalName}-javadoc.jar</value> <regex>\\</regex> <replacement>/</replacement> <failIfNoMatch>false</failIfNoMatch> </configuration> </execution> </executions> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-enforcer-plugin</artifactId> <executions> <execution> <id>enforce-javadoc-exists</id> <phase>verify</phase> <goals> <goal>enforce</goal> </goals> <configuration> <rules> <evaluateBeanshell> <condition>("${project.packaging}" != "jar") || ("${project.packaging}" == "jar" &amp;&amp; new java.io.File("${javadoc-filename}").exists())</condition> <message>Missing Javadoc JAR</message> </evaluateBeanshell> </rules> <fail>true</fail> </configuration> </execution> </executions> </plugin> Seems like a hack, and it is, but works nicely, and as long as [1] is not fixed you might want to get inspiration to fix it in commons pom for windows users, I think now I'll use that to avoid skipping the enforcer rule completely. BR, Jeremie [1] - http://jira.codehaus.org/browse/MENFORCER-100

2013/3/7 Eduard Moraru &lt;enygma2002(a)gmail.com&gt; Main problem is that maven exposes system paths inside properties without caring about them being later used from java or other language, which is understandable though pretty annoying sometimes. For sure, I should replace "${file.separator}" by '/' to be sure. But as separator that causes problems in java is 100% of time single backslash '\', I'm not sure it would bring anything better. What is wrong in my configurations above, is that I replace all '\' by '/', though I should take care to only replace single '\' by '/' (in regex above, "\\" would be replaced by "//"). This is likely to never cause any problem though, as I don't think "\\" is a path separator on any system.