+1
About time this came out as a 1.0!
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[
https://jira.codehaus.org/browse/MCASSANDRA-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296119#comment-296119
]
Andrew Swan commented on MCASSANDRA-15:
---
Mikhail, your change fixes the problem with {{log
[
https://jira.codehaus.org/browse/MNBMODULE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296116#comment-296116
]
Jesse Glick commented on MNBMODULE-163:
---
Yes of course; will review & apply before making
Hello Robert,
thanks for coming up with this.
What about renaming "developers" to "requiredDeveloperRoles" and
"contributors" to "requiredContributorRoles"?
I still have the same problem as with the RequirePropertyDiverges
rule: when the roles are defined in the company parent pom *for* the
comp
[
https://jira.codehaus.org/browse/MOJO-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296115#comment-296115
]
Mirko Friedenhagen commented on MOJO-1828:
--
Implemented in branch
https://svn.codehaus.org
[
https://jira.codehaus.org/browse/MOJO-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296114#comment-296114
]
Mirko Friedenhagen commented on MOJO-1829:
--
Implemented in branch
https://svn.codehaus.org
Hi Mirko When I was reading the xml for the first time I'd expected something
else.When looking at abc
i would read it like:who require roles? developers.*which*
developers? abc.but what you are actually configuring are the *expected* roles.
IMO the naming is not strong/self-explaining e
[
https://jira.codehaus.org/browse/MOJO-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirko Friedenhagen reassigned MOJO-1829:
Assignee: Mirko Friedenhagen
> New rule to check that certain roles are defined in a
Mirko Friedenhagen created MOJO-1829:
Summary: New rule to check that certain roles are defined in a
project.
Key: MOJO-1829
URL: https://jira.codehaus.org/browse/MOJO-1829
Project: Mojo
[
https://jira.codehaus.org/browse/MOJO-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirko Friedenhagen reassigned MOJO-1828:
Assignee: Mirko Friedenhagen
> New rule to check that a property in a project diverge
Mirko Friedenhagen created MOJO-1828:
Summary: New rule to check that a property in a project diverges
from one given in another project, e.g. the parent.
Key: MOJO-1828
URL: https://jira.codehaus.org/browse/M
Hello,
while we are at this, it would come quit handy when the cobertura
report would render XML as well, so CI systems are able to pick up the
values :-).
In regards to changes from JIRA: Every non trivial change should come
with a corresponding JIRA issue then, right? My only concern here
wou
Robert Scholte created MOJO-1827:
Summary: More elements of site.xml need to be merged
Key: MOJO-1827
URL: https://jira.codehaus.org/browse/MOJO-1827
Project: Mojo
Issue Type: Improvement
[
https://jira.codehaus.org/browse/MOJO-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MOJO-1819.
Resolution: Fixed
Fixed in [rev. 16308|http://fisheye.codehaus.org/changelog/mojo/?cs=16308]
Hi,
I'd like to release version 1.2 of the Maven Keytool Plugin.
In this new release, we have now all the keytool-api commands available
via maven goals (MKEYTOOL-19).
We solved 7 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11706&version=14051
There are no more issues
[
https://jira.codehaus.org/browse/MLICENSE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit closed MLICENSE-33.
---
Resolution: Fixed
Fix Version/s: 1.1
Done in [rev. 16301|http://fisheye.codehaus.org/changelog/moj
[
https://jira.codehaus.org/browse/MLICENSE-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit closed MLICENSE-35.
---
Resolution: Fixed
Fix Version/s: 1.1
Done in rev. 16301
> Clean code
> --
Tony Chemit created MLICENSE-35:
---
Summary: Clean code
Key: MLICENSE-35
URL: https://jira.codehaus.org/browse/MLICENSE-35
Project: Mojo's License Maven Plugin
Issue Type: Improvement
Affects
After applying a the new fluido skin to a few plugins I see that out
plugins use quite a different set of reports. I realized that I filed
a ticket about this some time ago, but as we all know filing a ticket
doesn't fix a problem but actually acting on it does. So, here goes:
I think that we shou
[
https://jira.codehaus.org/browse/MFINDBUGS-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garvin LeClaire closed MFINDBUGS-162.
-
Resolution: Cannot Reproduce
> Generated FindBugs report does not pay attention to excl
[
https://jira.codehaus.org/browse/MFINDBUGS-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garvin LeClaire closed MFINDBUGS-165.
-
Resolution: Not A Bug
The Default effort is min as the Default Threshold is medium.
Hello
I would like to cut the 4 beta release of wagon-maven-plugin 1.0
The new site has just been deployed here:
http://mojo.codehaus.org/wagon-maven-plugin
Staging Repository
https://nexus.codehaus.org/content/repositories/orgcodehausmojo-042/
Change log is at
http://mojo.codehaus.org/wag
[
https://jira.codehaus.org/browse/MFINDBUGS-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garvin LeClaire closed MFINDBUGS-166.
-
Resolution: Fixed
Fix Version/s: 2.4.1
> Add support for excluding Baseline Bugs
[
https://jira.codehaus.org/browse/MFINDBUGS-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296100#comment-296100
]
Garvin LeClaire commented on MFINDBUGS-166:
---
Just creating test to go with it.
[
https://jira.codehaus.org/browse/MGWT-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296098#comment-296098
]
Constantino Cronemberger commented on MGWT-259:
---
Hi,
I have just sent a pull request w
[
https://jira.codehaus.org/browse/MGWT-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296097#comment-296097
]
Constantino Cronemberger commented on MGWT-293:
---
I have just sent a pull request with t
[
https://jira.codehaus.org/browse/MOJO-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MOJO-1825.
Resolution: Fixed
Fixed in [rev. 16287|http://fisheye.codehaus.org/changelog/mojo/?cs=16287]
In the pom of the build-helper plugin it states that the license is
MIT and there is a header.txt in the root with license text. But in
site.xml is states Apache License, Version 2.0.
How does it work, can there be a different license of a single file in
the source tree for a plugin or should it be
Anders Hammar created MOJO-1826:
---
Summary: NoClassDefFoundError when using with Maven 3.0.3 and 3.0.4
Key: MOJO-1826
URL: https://jira.codehaus.org/browse/MOJO-1826
Project: Mojo
Issue Type: Bu
Robert Scholte created MOJO-1825:
Summary: SiteSkinner should verify if versions of Maven and
maven-site-plugin match
Key: MOJO-1825
URL: https://jira.codehaus.org/browse/MOJO-1825
Project: Mojo
[
https://jira.codehaus.org/browse/MOJO-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MOJO-1800.
Resolution: Fixed
Assignee: Robert Scholte
> Create new logo for Mojo
> ---
[
https://jira.codehaus.org/browse/MLICENSE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit closed MLICENSE-26.
---
Resolution: Won't Fix
Fix Version/s: 1.1
This is not a problem I can solve (MSITE-616 will)
[
https://jira.codehaus.org/browse/MLICENSE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit closed MLICENSE-27.
---
Resolution: Fixed
Fix Version/s: 1.1
Done in r16283.
> How to configure start and
[
https://jira.codehaus.org/browse/MLICENSE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296085#comment-296085
]
Tony Chemit commented on MLICENSE-27:
-
Ok, I just have a second look at the code, and this is
34 matches
Mail list logo