The scm api supports both add and remove. I think you will need to add your
own plugin though, as the preparation goals and completion goals do not
provide a means to specify properties, and, more importantly, the property
includes is shared with a number of plugins, so you really only want scm:add
Ok, but I don't see a delete operation in the scm plugin. Any idea on how to
do the removal without that?
OTOH, my first instinct was to think that the release plugin should be able to
generate the release notes on its own.
Ralph
On Dec 21, 2010, at 7:57 PM, Stephen Connolly wrote:
> The nex
The next release of the release plugin will have the completionGoals
parameter which you will want to hook in the remove of the release notes
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type
Apache Commons has a policy (which is in alignment with
http://incubator.apache.org/guides/releasemanagement.html#best-practice) to
include release notes in the source distribution. I would like to generate the
release notes using the changes plugin during release:prepare and have them
committe
Hi
I have been trying to upgrade Maven Changes Plugin to use a newer
version of Modello Maven Plugin. Currently it uses version 1.0.1. When I
upgrade to version 1.0.2 (or newer) I start getting all sorts of weird
test failures that I don't know how to fix. The errors occur for
elements that have
Hello,
The vote has passed with the following result:
+1 (binding): Kristian Rosenvold, Benjamin Bentmann, Olivier Lamy,
Stephen Connolly, Lukas Theussl, Emmanuel Venisse, Dennis Lundberg
+1 (non binding): Baptiste Mathus, Tony Chemit, Karl Heinz Marbaise
I have added an issue in JIRA to track i
+1
On 2010-12-15 20:25, Dennis Lundberg wrote:
> Hi
>
> I have some features I'd like to work on for the Changes Plugin. To
> simplify the work I would like to start using Java 5 features, such as
> generics for collections.
>
> The last release was version 2.3 and after that no issues have been
Dennis Lundberg wrote:
One comment I would make is if the plugin moves to another forge (hence different
groupId) a relocation pom should be created at the "old" location - not just an
update to the SCM.
This would mean that we (the Maven project) would have to deploy
relocation POMs everyti
I've done most of the requested changes on the wiki:
* Clarify that reitrement must be announced on the plugin's site
* Add apache-extras.org as a possible forge
* Remove creation of new plugins from the plan
* We can't change the SCM URL for the final release, so we fix the
reports on the site in
On 2010-12-16 11:44, Nord, James wrote:
> +0 (non-binding)
>
> One comment I would make is if the plugin moves to another forge (hence
> different groupId) a relocation pom should be created at the "old" location -
> not just an update to the SCM.
This would mean that we (the Maven project) wou
Hello,
I will have a look.
2010/12/21 lukewpatterson :
>
> Hi,
>
> I created two issues for maven-invoker-plugin:
>
> "duplicate script classpath entries are not filtered out, can cause
> ClassCastException" - http://jira.codehaus.org/browse/MINVOKER-112
>
> and
>
> "update to Groovy 1.7.5 (from 1
The Maven team is pleased to announce the release of the Maven Project
Info Reports Plugin, version 2.3.1
This plugin is used to generate reports information about the project.
http://maven.apache.org/plugins/maven-project-info-reports-plugin/
You should specify the version in your project's plug
Hi,
I created two issues for maven-invoker-plugin:
"duplicate script classpath entries are not filtered out, can cause
ClassCastException" - http://jira.codehaus.org/browse/MINVOKER-112
and
"update to Groovy 1.7.5 (from 1.5.6)" -
http://jira.codehaus.org/browse/MINVOKER-113
The first issue i
The vote has passed with the following result :
+1 (binding): Hervé Boutemy, Lukas Theussl, Olivier Lamy, Benjamin
Bentmann, Vincent Siveton
I will promote the artifacts to the central repo.
2010/12/18 Vincent Siveton :
> Hi,
>
> This is a maintenance release. We solved 5 issues:
> http://jira.c
It seems like this issue + the mockito problem
(http://jira.codehaus.org/browse/SUREFIRE-673) will make 2.7.1 happen
sooner rather than later. Sticking to your previous favourite version
is always an option.
-
To unsubscribe, e-ma
Hi,
Sorry for not taking the time to test this while the vote was in progress.
However, I think I've found a regression causing the failsafe plugin v2.7 to
report builds with broken integration tests as successful. I've created [1]
already - hope I got my reasoning correct in the description. Just
Mark,
I now have a second report of this and a test-project (via twitter ;).
I will track the problem from there.
I have been planning to do a 2.7.1 maintenance release in 2-4 weeks
time, so whatever it is will be fixed for 2.7.1
Kristian
> Looks like I had a rogue debugger process left around
he Maven team is pleased to announce the release of the Maven
Surefire Plugin, version 2.7
This release includes the maven-surefire-plugin, which executes the
unit tests of an application, the maven-surefire-report-plugin, which
parses surefire/failsafe test results and renders them to DOXIA
creat
18 matches
Mail list logo
