[jira] (MRESOURCES-99) ${project.baseUri} and ${maven.build.timestamp} are not expanded by resource filtering
[
https://jira.codehaus.org/browse/MRESOURCES-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=307359#comment-307359
]
Karl Pietrzak commented on MRESOURCES-99:
-
@Aaron/@Evgeny: Yeah, I revise what I said. You guys are right: this should
stay open.
> ${project.baseUri} and ${maven.build.timestamp} are not expanded by resource
> filtering
> ---
>
> Key: MRESOURCES-99
> URL: https://jira.codehaus.org/browse/MRESOURCES-99
> Project: Maven 2.x Resources Plugin
> Issue Type: Improvement
> Components: interpolation
>Affects Versions: 2.3, 2.4
>Reporter: Thomas Champagne
>
> When filtering resources, ${project.baseUri} and ${maven.build.timestamp} are
> not expanded (remains unchanged in the output file).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-711) request for scm:info goal
Karl Pietrzak created SCM-711:
-
Summary: request for scm:info goal
Key: SCM-711
URL: https://jira.codehaus.org/browse/SCM-711
Project: Maven SCM
Issue Type: Wish
Components: maven-scm-api
Reporter: Karl Pietrzak
Priority: Minor
h4. What
I would like to request the addition of a {{scm:info}} goal.
h4. Why
I would like to use the properties of {{scm:info}} in the rest of my Maven
build process, especially put SVN info properties into my manifest.
h4. How
Most (all?) of the providers have some kind of {{info}} method already, so it
shouldn't be a big deal.
I can submit a patch, if this sounds OK to folks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-711) request for scm:info goal
[
https://jira.codehaus.org/browse/SCM-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317387#comment-317387
]
Karl Pietrzak commented on SCM-711:
---
Thank you, Olivier, but I feel like using the {{buildnumber-maven-plugin}} to
get the SVN rev or Git changeset is just a workaround around the fact that I
can't get it from {{scm}} plugin. I feel this is ironic, IMHO, because I can
branch using the {{scm}} plugin, but I can't get the revision.
Also {{buildnumber:create}} seems to be [only supported for
Subversion|http://mojo.codehaus.org/buildnumber-maven-plugin/create-mojo.html],
as compared to the plethora of SCMs that the Maven SCM plugin supports, most of
which already have some kind {{getInfo()}} method.
I'm not complaining: I'm offering to write a patch, if folks think this is
worthwhile.
Thanks!
> request for scm:info goal
> -
>
> Key: SCM-711
> URL: https://jira.codehaus.org/browse/SCM-711
> Project: Maven SCM
> Issue Type: Wish
> Components: maven-scm-api
>Reporter: Karl Pietrzak
>Priority: Minor
>
> h4. What
> I would like to request the addition of a {{scm:info}} goal.
> h4. Why
> I would like to use the properties of {{scm:info}} in the rest of my Maven
> build process, especially put SVN info properties into my manifest.
> h4. How
> Most (all?) of the providers have some kind of {{info}} method already, so it
> shouldn't be a big deal.
> I can submit a patch, if this sounds OK to folks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-949) Create forkCount parameter
[
https://jira.codehaus.org/browse/SUREFIRE-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318483#comment-318483
]
Karl Pietrzak commented on SUREFIRE-949:
@[~agudian]: I like the idea of deprecating {{forkMode}} and instead using
{{fork}}, {{reuseForks}}, and {{forkCount}}. The use of thread and fork
vocabulary together was a tad confusing to the untrained eye.
> Create forkCount parameter
> --
>
> Key: SUREFIRE-949
> URL: https://jira.codehaus.org/browse/SUREFIRE-949
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Surefire Plugin
>Reporter: Kristian Rosenvold
>Assignee: Kristian Rosenvold
> Fix For: 2.14
>
>
> The "threadCount" parameter is overloaded to the extent that it is becoming
> problematic. A forkCount parameter would be nice, maybe supporting the same
> style as maven-core "1.5C" for 1.5 x number of cores.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
