[mojo-dev] [jira] (MOJO-1840) Non-well-formed XML in sample project configuration on site

[ https://jira.codehaus.org/browse/MOJO-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirko Friedenhagen closed MOJO-1840. Resolution: Fixed Fix Version/s: extra-enforcer-rules-1.0-alpha-4 Fixed in r16488. https:/

[mojo-dev] [jira] (MOJO-1840) Non-well-formed XML in sample project configuration on site

[ https://jira.codehaus.org/browse/MOJO-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirko Friedenhagen updated MOJO-1840: - Remaining Estimate: 0 minutes Original Estimate: 0 minutes > Non-well-formed XML in sa

[mojo-dev] [jira] (MOJO-1840) Non-well-formed XML in sample project configuration on site

[ https://jira.codehaus.org/browse/MOJO-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirko Friedenhagen reassigned MOJO-1840: Assignee: Mirko Friedenhagen > Non-well-formed XML in sample project configuration on

Re: [mojo-dev] [VOTE] Release JDiff-maven-plugin version 1.0-beta-1

Hello Robert, I tried this on one of my pet projects (https://github.com/1and1/testlink-junit) and besides the MRELEASE-723 issue (I named the tags @groupId@-@version@ as this is a multimodule project and the artifactId does not make sense in this situation), I think the plugin will fail on multi-

[mojo-dev] [jira] (MOJO-1841) Contrary to documentation requiredRoles are not always valid

Andreas Sewe created MOJO-1841: -- Summary: Contrary to documentation requiredRoles are not always valid Key: MOJO-1841 URL: https://jira.codehaus.org/browse/MOJO-1841 Project: Mojo Issue Type: B

RE: [mojo-dev] [VOTE] Release JDiff-maven-plugin version 1.0-beta-1

Hi Karl Heinz, it should work out of the box.This seems to be a docletpath issue.Please run it again in debug-mode and check the commandline being executed. There are a few options: unescaped/unquoted path, invalid separators. Looks like I have to cancel this vote, once I know what to fix and h

[mojo-dev] [jira] (MOJO-1840) Non-well-formed XML in sample project configuration on site

Andreas Sewe created MOJO-1840: -- Summary: Non-well-formed XML in sample project configuration on site Key: MOJO-1840 URL: https://jira.codehaus.org/browse/MOJO-1840 Project: Mojo Issue Type: Bu

Re: [mojo-dev] [VOTE] Release JDiff-maven-plugin version 1.0-beta-1

Hi Robert, thanks for the hints .. I think you hit a MRELEASE-723 like problem. The plugin extracts the scm information of the released (or specified) version. apart from the above i would say there is an other problem in there... [INFO] Scanning for projects... [INFO] [INFO]

RE: [mojo-dev] [VOTE] Release JDiff-maven-plugin version 1.0-beta-1

hi Karl, I think you hit a MRELEASE-723 like problem.The plugin extracts the scm information of the released (or specified) version.For GIT this is not updated during the release, because you don't have that information.So I can imagine that this fails here. btw, the siteskinner borrowed this f

Re: [mojo-dev] [VOTE] Release JDiff-maven-plugin version 1.0-beta-1

Hi, i've just a small question: Does jdiff-maven-plugin support only a limited number of SCM's ? Or is there something special which i have to aware during the configuration for example for a Git project ? Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49

[mojo-dev] [jira] (MAPPASM-163) current directory is not the same in unix script and in windows script

[ https://jira.codehaus.org/browse/MAPPASM-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MAPPASM-163. --- Resolution: Not A Bug > current directory is not the same in unix script and in windo

[mojo-dev] [jira] (MAPPASM-163) current directory is not the same in unix script and in windows script

[ https://jira.codehaus.org/browse/MAPPASM-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297412#comment-297412 ] Karl Heinz Marbaise commented on MAPPASM-163: - Not *basename* *basedir* is the one whi

[mojo-dev] [jira] (MAPPASM-163) current directory is not the same in unix script and in windows script

[ https://jira.codehaus.org/browse/MAPPASM-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297411#comment-297411 ] Karl Heinz Marbaise commented on MAPPASM-163: - Ok that means the documentations needs

[mojo-dev] [jira] (MAPPASM-163) current directory is not the same in unix script and in windows script

[ https://jira.codehaus.org/browse/MAPPASM-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297410#comment-297410 ] Eric Vantillard commented on MAPPASM-163: - Exactly. Sorry I have miss understood the fact

[mojo-dev] [jira] (MAPPASM-163) current directory is not the same in unix script and in windows script

[ https://jira.codehaus.org/browse/MAPPASM-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297408#comment-297408 ] Karl Heinz Marbaise commented on MAPPASM-163: - Exactly one line above the excerpt you

[mojo-dev] [jira] (MAPPASM-163) current directory is not the same in unix script and in windows script

[ https://jira.codehaus.org/browse/MAPPASM-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297407#comment-297407 ] Eric Vantillard commented on MAPPASM-163: - good point, you are right. Thinking about it, m

[mojo-dev] [jira] (MAPPASM-163) current directory is not the same in unix script and in windows script

[ https://jira.codehaus.org/browse/MAPPASM-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297405#comment-297405 ] Karl Heinz Marbaise commented on MAPPASM-163: - In my opinion the scripts shouldn't cha