Look at the enforcer plugin. As each rule is a component that gets
configured.
On 10-Aug-09, at 8:54 PM, Jochen Wiedmann wrote:
Hi, Jason,
thanks for your reply. That will at least help me to get a working
solution. However, I am not quite sure whether I expressed myself
right. Sorry, if not
Hi, Jason,
thanks for your reply. That will at least help me to get a working
solution. However, I am not quite sure whether I expressed myself
right. Sorry, if not.
My ideal solution would be to have something like
myPlugin
On 10-Aug-09, at 1:32 PM, Jochen Wiedmann wrote:
Hi,
in a plugin, I'd like to select a component dynamically. Basically,
I'd like to have something along these lines:
...
The idea is to use the hint for looking up the "myComponent" bean and
use the XML fragment be
The cobertura one yes because it would be produced potentially by the
tests. The others probably have less harm.
On Mon, Aug 10, 2009 at 4:41 PM, Brett Porter wrote:
>
> On 07/08/2009, at 4:11 PM, jdca...@apache.org wrote:
>
>> +
>> **/cobertura.ser
>> + **/*.bak
>> +
On 07/08/2009, at 4:11 PM, jdca...@apache.org wrote:
+
**/cobertura.ser
+**/*.bak
+**/*.diff
+**/*.patch
+**/*.log
I feel like these could start knocking out legitimate files.
Are they really necessary since it is usually built from a clean
c
Hi,
in a plugin, I'd like to select a component dynamically. Basically,
I'd like to have something along these lines:
...
The idea is to use the hint for looking up the "myComponent" bean and
use the XML fragment between and to
configure the bean.
Is that poss
This vote has passed with the following:
+1: John, Benjamin, Arnaud
I'll release the artifacts and deploy the site.
Thanks,
-john
John Casey wrote:
Hi,
We solved 2 issues, and none remain in JIRA:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11250&styleName=Text&version=14414
If I do that, we'll have to redo this vote. I'm hoping to get 2.2.1 out
to fix some problems in 2.2.0 that make it nearly unusable for deployment.
Is this issue important enough to push the release off by another week?
If not, can we just push it out as part of 2.2.2 or 2.3.0 or whatever
$NEXT
Before we push this, I'd like to add a requirement to include the scm
url and project url in the pom that is bundled. This information is
currently required in Jira, but it should be in the pom.
On Fri, Aug 7, 2009 at 10:10 AM, John Casey wrote:
> Oops, forgot to record my own +1.
>
> -john
>
> Jo
+1
But I hope that you will bump to latest modello to fix MNG-4289.
Cheers,
Vincent
2009/8/6, John Casey :
> Hi,
>
> It looks like we've got a stable release candidate that addresses the major
> regressions that resulted from the Maven 2.2.0 release.
>
> The artifacts we're voting on for the
+1
Stéphane
On Thu, Aug 6, 2009 at 9:36 PM, John Casey wrote:
> Hi,
>
> It looks like we've got a stable release candidate that addresses the major
> regressions that resulted from the Maven 2.2.0 release.
>
> The artifacts we're voting on for the 2.2.1 release are here:
>
> https://repository.a
Hi,
in order to avoid reinventing the wheel: I need to implement name
transformation in a plugin. For example, the plugin would need to
convert
a.xml -> a.html
b.xml -> b.html
but would be configurable to create
a.xml -> a-13.html
b.xml -> b-13.html
instead. Is there any exampl
12 matches
Mail list logo
