Edit SVN commit message

I made a mistake in a commit message for a recent commit, and I wanted
to edit the svn log.  I've done this once or twice in the Apache SVN,
but it doesn't seem to be working correctly in the Mojo SVN repo.  Can
someone with admin rights check if this is set up?  Below is the error
message I received.

Thanks!

svn: DAV request failed; it's possible that the repository's
pre-revprop-change hook either failed or is non-existent
svn: At least one property change failed; repository is unchanged
svn: Error setting property 'log':
Repository has not been enabled to accept revision propchanges;
ask the administrator to create a pre-revprop-change hook

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

    http://xircles.codehaus.org/manage_email

[jira] Commented: (MOJO-1436) ClassCastException when using Mercurial

    [
http://jira.codehaus.org/browse/MOJO-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258081#action_258081
] 

perriman commented on MOJO-1436:
--------------------------------

It doesn't work for me....

> ClassCastException when using Mercurial
> ---------------------------------------
>
>                 Key: MOJO-1436
>                 URL: http://jira.codehaus.org/browse/MOJO-1436
>             Project: Mojo
>          Issue Type: Bug
>          Components: buildnumber
>    Affects Versions: buildnumber-maven-plugin-1.0-beta-4
>         Environment: MacOS 10.6.1
> Apache Maven 2.2.1 (r801777; 2009-08-06 23:16:01+0400)
> Java version: 1.6.0_15
>            Reporter: Max Matveev
>            Assignee: Olivier Lamy
>             Fix For: buildnumber-maven-plugin-1.0-beta-5
>
>
> When using HG as SCM provider i getting following stacktrace (mvn was executed with -X key)
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR

[jira] Reopened: (MOJO-1436) ClassCastException when using Mercurial

     [
http://jira.codehaus.org/browse/MOJO-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy reopened MOJO-1436:
--------------------------------

reopen as user comment

> ClassCastException when using Mercurial
> ---------------------------------------
>
>                 Key: MOJO-1436
>                 URL: http://jira.codehaus.org/browse/MOJO-1436
>             Project: Mojo
>          Issue Type: Bug
>          Components: buildnumber
>    Affects Versions: buildnumber-maven-plugin-1.0-beta-4
>         Environment: MacOS 10.6.1
> Apache Maven 2.2.1 (r801777; 2009-08-06 23:16:01+0400)
> Java version: 1.6.0_15
>            Reporter: Max Matveev
>            Assignee: Olivier Lamy
>             Fix For: buildnumber-maven-plugin-1.0-beta-5
>
>
> When using HG as SCM provider i getting following stacktrace (mvn was executed with -X key)
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------

[jira] Commented: (MOJO-1436) ClassCastException when using Mercurial

    [
http://jira.codehaus.org/browse/MOJO-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258084#action_258084
] 

Olivier Lamy commented on MOJO-1436:
------------------------------------

can you give us more details ?? (stack trace, logs).
Difficult to fix something without informations.
Thanks !

> ClassCastException when using Mercurial
> ---------------------------------------
>
>                 Key: MOJO-1436
>                 URL: http://jira.codehaus.org/browse/MOJO-1436
>             Project: Mojo
>          Issue Type: Bug
>          Components: buildnumber
>    Affects Versions: buildnumber-maven-plugin-1.0-beta-4
>         Environment: MacOS 10.6.1
> Apache Maven 2.2.1 (r801777; 2009-08-06 23:16:01+0400)
> Java version: 1.6.0_15
>            Reporter: Max Matveev
>            Assignee: Olivier Lamy
>             Fix For: buildnumber-maven-plugin-1.0-beta-5
>
>
> When using HG as SCM provider i getting following stacktrace (mvn was executed with -X key)

[jira] Commented: (MOJO-1436) ClassCastException when using Mercurial

    [
http://jira.codehaus.org/browse/MOJO-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258089#action_258089
] 

perriman commented on MOJO-1436:
--------------------------------

It is the same maven version and the same error but:

* java 1.5 (I have tried with 1.6 and I have the same problem)
* Ubuntu 10.10

The plugin version is buildnumber-maven-plugin-1.0-beta-5

Can I provide you more information?

> ClassCastException when using Mercurial
> ---------------------------------------
>
>                 Key: MOJO-1436
>                 URL: http://jira.codehaus.org/browse/MOJO-1436
>             Project: Mojo
>          Issue Type: Bug
>          Components: buildnumber
>    Affects Versions: buildnumber-maven-plugin-1.0-beta-4
>         Environment: MacOS 10.6.1
> Apache Maven 2.2.1 (r801777; 2009-08-06 23:16:01+0400)
> Java version: 1.6.0_15
>            Reporter: Max Matveev

[jira] Commented: (MOJO-1436) ClassCastException when using Mercurial

    [
http://jira.codehaus.org/browse/MOJO-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258097#action_258097
] 

Olivier Lamy commented on MOJO-1436:
------------------------------------

yes run : mvn -e -X and paste the maven output please.
And the best is to provide a sample which reproduce the issue.
Thanks

> ClassCastException when using Mercurial
> ---------------------------------------
>
>                 Key: MOJO-1436
>                 URL: http://jira.codehaus.org/browse/MOJO-1436
>             Project: Mojo
>          Issue Type: Bug
>          Components: buildnumber
>    Affects Versions: buildnumber-maven-plugin-1.0-beta-4
>         Environment: MacOS 10.6.1
> Apache Maven 2.2.1 (r801777; 2009-08-06 23:16:01+0400)
> Java version: 1.6.0_15
>            Reporter: Max Matveev
>            Assignee: Olivier Lamy
>             Fix For: buildnumber-maven-plugin-1.0-beta-5
>
>
> When using HG as SCM provider i getting following stacktrace (mvn was executed with -X key)

Re: [RESULT] [VOTE] Release gwt-maven-plugin 2.2.0

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

    http://xircles.codehaus.org/manage_email

Re: Re: [RESULT] [VOTE] Release gwt-maven-plugin 2.2.0

[jira] Updated: (MGWT-175) Warnings from tests that are excluded during gwt:test

     [
http://jira.codehaus.org/browse/MGWT-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nicolas de loof updated MGWT-175:
---------------------------------

    Fix Version/s:     (was: 2.2.0)

> Warnings from tests that are excluded during gwt:test
> -----------------------------------------------------
>
>                 Key: MGWT-175
>                 URL: http://jira.codehaus.org/browse/MGWT-175
>             Project: Maven 2.x GWT Plugin
>          Issue Type: Bug
>    Affects Versions: 1.2
>            Reporter: Micah Whitacre
>            Priority: Minor
>         Attachments: example-project.tar.gz
>
>
> I currently have a project setup that combines standard JUnit 4 tests along with the GWTTestCase tests.  I
have it configured[1] based on the testing guide for how to separate the tests.  The build works however I
get warning for tests that are supposed be excluded from being ran during the gwt:test goal.
> [INFO] [surefire:test {execution: default-test}]
> [INFO] Surefire report directory: /home/mw010351/workspaces/preferences/example-project/target/surefire-reports
> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> Running com.example.project.client.SimpleTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.022 sec
> Results :
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> [INFO] [gwt:test {execution: test}]
> [INFO] using GWT jars for specified version 2.0.0
> [INFO] establishing classpath list (scope = test)
> [INFO] 
> [INFO] -------------------------------------------------------
> [INFO]  T E S T S
> [INFO] -------------------------------------------------------
> [INFO] Running junit.framework.TestSuite <at> 11975b59
> [INFO] Validating newly compiled units
> [INFO]    [ERROR] Errors in 'file:/home/mw010351/workspaces/preferences/example-project/src/test/java/com/example/project/client/SimpleTest.java'
> [INFO]       [ERROR] Line 10: No source code is available for type org.junit.Assert; did you forget to inherit a
required module?
> [INFO] Validating newly compiled units
> [INFO]    [ERROR] Errors in 'file:/home/mw010351/workspaces/preferences/example-project/src/test/java/com/example/project/client/SimpleTest.java'
> [INFO]       [ERROR] Line 10: No source code is available for type org.junit.Assert; did you forget to inherit a
required module?
> [INFO] Hello World
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.818 sec
> [INFO] 
> [INFO] Results :
> [INFO] 
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> [INFO] 
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO] ------------------------------------------------------------------------
> [1] - http://mojo.codehaus.org/gwt-maven-plugin/user-guide/testing.html

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

    http://xircles.codehaus.org/manage_email

[jira] Reopened: (MOJO-1644) Buildnumber plugin doesn't fail on doCheck if file is modified

     [
http://jira.codehaus.org/browse/MOJO-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ackermann reopened MOJO-1644:
------------------------------------

Thank you for checking. Please correct "mvn -U buildnumber:create" to "mvn -X verify" in my description
above. I just rechecked with "mvn -X verify": With modified file, the build doesn't fail - with deleted
file the build fails.

> Buildnumber plugin doesn't fail on doCheck if file is modified
> --------------------------------------------------------------
>
>                 Key: MOJO-1644
>                 URL: http://jira.codehaus.org/browse/MOJO-1644
>             Project: Mojo
>          Issue Type: Bug
>    Affects Versions: buildnumber-maven-plugin-1.0-beta-4
>         Environment: Windows XP SP3, Maven 3.0.1, Subversion 1.6.15, JDK 1.6_11
>            Reporter: Martin Ackermann
>            Assignee: Olivier Lamy
>
> I use the following configuration in my pom.xml:
> <build>
>   <plugins>
>     <plugin>
>       <groupId>org.codehaus.mojo</groupId>
>       <artifactId>buildnumber-maven-plugin</artifactId>
>       <version>1.0-beta-4</version>
>       <executions>
>          <execution>
>            <phase>verify</phase>
>            <goals>
>              <goal>create</goal>
>            </goals>
>          </execution>
>        </executions>
>        <configuration>
>        <doCheck>true</doCheck>
>        <doUpdate>false</doUpdate>
>      </configuration>
>    </plugin>
> </plugins>
> Steps to reproduce:
> 1. Check out the project.
> 2. Modify a .java file that is under version control, e.g. add a method to my-package\MyClass.java. The
file gets the dirty icon in Eclipse.
> 3. Run "mvn -U buildnumber:create". The build succeeds, but it should fail.
> Interestingly, the log says:
> [DEBUG] M       src\main\java\mypackage\MyClass.java
> So, the SVN client correctly identified the modified file, but the buildnumber plugin didn't react on
this result.
> If I delete my-package\MyClass.java, it works as expected: 
> [ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-4:create
(default-cli) on project trial-maven: Cannot create the build number because you have local
modifications :
> [ERROR] [ src\main\java\my-package\MyClass.java:deleted]

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

    http://xircles.codehaus.org/manage_email