[jira] Updated: (SCM-592) Error parsing blame for git
[ http://jira.codehaus.org/browse/SCM-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated SCM-592: - Fix Version/s: 1.5 Assignee: Olivier Lamy I would prefer a real patch file but I will try without :P > Error parsing blame for git > --- > > Key: SCM-592 > URL: http://jira.codehaus.org/browse/SCM-592 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git >Affects Versions: 1.4 >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.5 > > > Fixed version can be found here : > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/blame/ > And unit test : > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/blame/FixedGitBlameConsumerTest.java -- 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
[jira] Created: (MRELEASE-631) Use different file for non-interactive release configuration
Use different file for non-interactive release configuration Key: MRELEASE-631 URL: http://jira.codehaus.org/browse/MRELEASE-631 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.1 Reporter: Arno Wolter Priority: Minor It would be nice to use a configurable file for non-interactive release configuration instead of release.properties. One could commit that file with the sources in order to configure the upcoming release within his IDE. You cannot do that with the release.properties as is it modified by the release plugin and therefore prevents tagging. As a consequence you could just press a "release" button in your CI-server without touching any build plan configuration. Of course that makes only sense if release role and dev role are owned by the same person -- 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
[jira] Created: (MAVENUPLOAD-2811) upload new release 2.0.0 to org.mentaframework
upload new release 2.0.0 to org.mentaframework --- Key: MAVENUPLOAD-2811 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2811 Project: Maven Upload Requests Issue Type: Task Reporter: Fernando Boaglio The Mentawai goal is to be a simple, flexible, joyful and productive Java web framework. This is a new release with a lot of improvements . TIA -- 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
[jira] Commented: (MRELEASE-624) Performing a release with localCheckout fail on Windows
[
http://jira.codehaus.org/browse/MRELEASE-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249723#action_249723
]
Christian Holm commented on MRELEASE-624:
-
When specifying localCheckout the ":" in the path seems to be eaten. This is
required for the path to be valid on Windows.
> Performing a release with localCheckout fail on Windows
> ---
>
> Key: MRELEASE-624
> URL: http://jira.codehaus.org/browse/MRELEASE-624
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.1
> Environment: Windows Vista, msysgit, Maven 3.0.0
>Reporter: Daniel Spilker
>Priority: Minor
>
> When trying to perform a release on a Windows machine with localCheckout set
> to true, I get the following error message. The path
> 'C:\Users\daspilker\workspaces\myproject' is a git repository.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.1:perform (default-cli) on
> project warp:
> Unable to checkout from SCM
> [ERROR] Provider message:
> [ERROR] The git-clone command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'C\Users\daspilker\workspaces\myproject' does not appear to be
> a git repository
> [ERROR] fatal: The remote end hung up unexpectedly
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :myproject
> {code}
--
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
[jira] Commented: (SCM-592) Error parsing blame for git
[ http://jira.codehaus.org/browse/SCM-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249735#action_249735 ] Evgeny Mandrikov commented on SCM-592: -- I'll come back to you with patch today. In fact it would be much simpler for me to have commit access to Maven SCM ;) > Error parsing blame for git > --- > > Key: SCM-592 > URL: http://jira.codehaus.org/browse/SCM-592 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git >Affects Versions: 1.4 >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.5 > > > Fixed version can be found here : > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/blame/ > And unit test : > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/blame/FixedGitBlameConsumerTest.java -- 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
[jira] Closed: (MNG-4953) Issue a warning when a system-scope dependency refers to the project basedir
[
http://jira.codehaus.org/browse/MNG-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4953.
--
Resolution: Fixed
Fix Version/s: 3.0.2
Assignee: Benjamin Bentmann
Done in [r1053111|http://svn.apache.org/viewvc?view=revision&revision=1053111].
> Issue a warning when a system-scope dependency refers to the project basedir
>
>
> Key: MNG-4953
> URL: http://jira.codehaus.org/browse/MNG-4953
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Dependencies, POM
>Affects Versions: 3.0.1
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0.2
>
>
> This is an anti-pattern that asks for troubles as the declaring POM will be
> be unusable during dependency resolution (when accessed from a repository):
> {code:xml}
>
> ...
> system
> ${basedir}/lib/foo.jar
>
> {code}
> As such, usage of either {{basedir}} and {{project.basedir}} for the system
> path should emit a warning to help stopping this kind of bad practice.
--
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
[jira] Commented: (SUREFIRE-577) running only some method of a unit class (with -Dtest.method=myMethod)
[ http://jira.codehaus.org/browse/SUREFIRE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249749#action_249749 ] Kristian Rosenvold commented on SUREFIRE-577: - For junit you just use the Request.method method and the corresponding method on JunitCore that accepts a request on the 4.7 provider. I'm sure the same feature is available for 4.0. > running only some method of a unit class (with -Dtest.method=myMethod) > -- > > Key: SUREFIRE-577 > URL: http://jira.codehaus.org/browse/SUREFIRE-577 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Reporter: Olivier Lamy >Assignee: Olivier Lamy > > I definitely don't know if it's possible with junit. > But it's an idea, I have now :-). -- 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
[jira] Issue Comment Edited: (SUREFIRE-577) running only some method of a unit class (with -Dtest.method=myMethod)
[ http://jira.codehaus.org/browse/SUREFIRE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249748#action_249748 ] Kristian Rosenvold edited comment on SUREFIRE-577 at 12/27/10 1:13 PM: --- I think we should just use the single -Dtest=FooBar flag for all options. FooBar can be a test class, a test method (likely fooBar) or a JUnit Category. Since we scan the classpath and all classes we can just create the union if any disambiguity. Note that JUnit categories is the same as testNg groups, and we already have a parameter on the surefire mojo for TestNG groups. I Just think it's natural to be able to specify groups/categories using the same -Dtest parameter was (Author: krosenvold): I think we should just use the single -Dtest=FooBar flag for all options. FooBar can be a test class, a test method (likely fooBar) or a JUnit Category. Since we scan the classpath and all classes we can just create the union if any disambiguity. > running only some method of a unit class (with -Dtest.method=myMethod) > -- > > Key: SUREFIRE-577 > URL: http://jira.codehaus.org/browse/SUREFIRE-577 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Reporter: Olivier Lamy >Assignee: Olivier Lamy > > I definitely don't know if it's possible with junit. > But it's an idea, I have now :-). -- 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
[jira] Issue Comment Edited: (SUREFIRE-577) running only some method of a unit class (with -Dtest.method=myMethod)
[ http://jira.codehaus.org/browse/SUREFIRE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249748#action_249748 ] Kristian Rosenvold edited comment on SUREFIRE-577 at 12/27/10 1:16 PM: --- I think we should just use the single -Dtest=FooBar flag for all options. FooBar can be a test class, a test method (likely fooBar) or a JUnit Category. Since we scan the classpath and all classes we can just create the union if any ambiguity. Note that JUnit categories is the same as testNg groups, and we already have a parameter on the surefire mojo for TestNG groups. I Just think it's natural to be able to specify groups/categories using the same -Dtest parameter. Also note that interpreting these parameters is all the way down at the provider level; I am unsure if all the providers will provide the same level of features wrt this. was (Author: krosenvold): I think we should just use the single -Dtest=FooBar flag for all options. FooBar can be a test class, a test method (likely fooBar) or a JUnit Category. Since we scan the classpath and all classes we can just create the union if any disambiguity. Note that JUnit categories is the same as testNg groups, and we already have a parameter on the surefire mojo for TestNG groups. I Just think it's natural to be able to specify groups/categories using the same -Dtest parameter > running only some method of a unit class (with -Dtest.method=myMethod) > -- > > Key: SUREFIRE-577 > URL: http://jira.codehaus.org/browse/SUREFIRE-577 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Reporter: Olivier Lamy >Assignee: Olivier Lamy > > I definitely don't know if it's possible with junit. > But it's an idea, I have now :-). -- 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
[jira] Commented: (SUREFIRE-577) running only some method of a unit class (with -Dtest.method=myMethod)
[
http://jira.codehaus.org/browse/SUREFIRE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249753#action_249753
]
Olivier Lamy commented on SUREFIRE-577:
---
My goal is more to be able to execute only one test !
{code}
-Dtest=FooBar -DtestMethod=testNiceStuff.
{code}
In this case only FooBar#testNiceStuff will be executed.
BTW if -Dtest= is null and not -DtestMethod, we can execute method(s) from
scanned classes which match the parameter value.
WDYT ?
> running only some method of a unit class (with -Dtest.method=myMethod)
> --
>
> Key: SUREFIRE-577
> URL: http://jira.codehaus.org/browse/SUREFIRE-577
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Surefire Plugin
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>
> I definitely don't know if it's possible with junit.
> But it's an idea, I have now :-).
--
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
[jira] Commented: (SUREFIRE-577) running only some method of a unit class (with -Dtest.method=myMethod)
[ http://jira.codehaus.org/browse/SUREFIRE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249757#action_249757 ] Kristian Rosenvold commented on SUREFIRE-577: - I understand you want to run one specific test ;) I'm thinking we have all the information we need here, and can be more like google, you type something after -Dtest and we use that to resolve your request. If you're imprecise or lazy we might run a few more tests. If you're concise or have well named tests you get your single test. I'm not particularly worried about syntax here ; -Dtest=MyClass#myTest, -Dtest=MyClass.myTest, -Dtest=myTest, -Dtest=*.myTest or whatever. I just think we should keep the api simple from the user perspective. I'm interested in solving SUREFIRE-656 for 2.8, but regardless of that I think a unified -Dtest= syntax would be cool, and really user friendly. > running only some method of a unit class (with -Dtest.method=myMethod) > -- > > Key: SUREFIRE-577 > URL: http://jira.codehaus.org/browse/SUREFIRE-577 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Reporter: Olivier Lamy >Assignee: Olivier Lamy > > I definitely don't know if it's possible with junit. > But it's an idea, I have now :-). -- 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
[jira] Commented: (SUREFIRE-577) running only some method of a unit class (with -Dtest.method=myMethod)
[ http://jira.codehaus.org/browse/SUREFIRE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249759#action_249759 ] Olivier Lamy commented on SUREFIRE-577: --- ok I see your point. No problem for only one parameter ! I have a strong hesitation : -Dtest=Foo#mytest -DFoo.mytest . Will be probably the most long : find the correct syntax (or we can support both :-) ). > running only some method of a unit class (with -Dtest.method=myMethod) > -- > > Key: SUREFIRE-577 > URL: http://jira.codehaus.org/browse/SUREFIRE-577 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Reporter: Olivier Lamy >Assignee: Olivier Lamy > > I definitely don't know if it's possible with junit. > But it's an idea, I have now :-). -- 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
[jira] Updated: (SUREFIRE-577) running only some method of a unit class (with -Dtest=MyClass#myMethod)
[ http://jira.codehaus.org/browse/SUREFIRE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated SUREFIRE-577: -- Summary: running only some method of a unit class (with -Dtest=MyClass#myMethod) (was: running only some method of a unit class (with -Dtest.method=myMethod)) > running only some method of a unit class (with -Dtest=MyClass#myMethod) > --- > > Key: SUREFIRE-577 > URL: http://jira.codehaus.org/browse/SUREFIRE-577 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Reporter: Olivier Lamy >Assignee: Olivier Lamy > > I definitely don't know if it's possible with junit. > But it's an idea, I have now :-). -- 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
