possible release of the Maven 2.x FindBugs
> Plugin
> Based upon the inforrmation in Jira all issues scheduled for version 2.3.3
> of this plugin have been fixed.
> One of the fixed issues (http://jira.codehaus.org/browse/MFINDBUGS-146)
> applies to our environment and therefor I wo
Hello developers of maven,
I would like to inform about a possible release of the Maven 2.x FindBugs
Plugin
Based upon the inforrmation in Jira all issues scheduled for version 2.3.3
of this plugin have been fixed.
One of the fixed issues (http://jira.codehaus.org/browse/MFINDBUGS-146)
applies to
I think you have the wrong dev list
On Wed, Nov 11, 2009 at 7:53 PM, Garvin LeClaire
wrote:
>
> Hi,
>
> We solved 5 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11701&version=15548
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/I
Hi,
We solved 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11701&version=15548
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+MFINDBUGS+AND+resolution+%3D+Unresolved+ORDER+BY+
above)
The 5.1-PATCH version number referenced in the pom.xml of the findbugs
plugin.
If there is a dofferent or preferred way to reference and use unreleased
jars, please let me know.
> There is no Findbugs plugin for Mav
[ http://jira.codehaus.org/browse/MNG-1822?page=all ]
patrick OShea updated MNG-1822:
---
Attachment: bcel.zip
> There is no Findbugs plugin for Maven2
> --
>
> Key: MNG-1822
>
[ http://jira.codehaus.org/browse/MNG-1822?page=all ]
patrick OShea updated MNG-1822:
---
Attachment: maven-findbugs-plugin-1.0.jar
> There is no Findbugs plugin for Maven2
> --
>
> Key: MNG-1822
&g
[ http://jira.codehaus.org/browse/MNG-1822?page=all ]
patrick OShea updated MNG-1822:
---
Attachment: maven-findbugs-plugin-source.zip
> There is no Findbugs plugin for Maven2
> --
>
> Key: MNG-1822
&g
There is no Findbugs plugin for Maven2
--
Key: MNG-1822
URL: http://jira.codehaus.org/browse/MNG-1822
Project: Maven 2
Type: New Feature
Versions: 2.0.1
Reporter: patrick OShea
There is no findbugs plugin for maven2
updating it last, but I'm not aware of any of
the problems you've highlighted.
- Brett
Jeff Jensen wrote:
Hi,
Is anyone actually maintaining the FindBugs plugin?
I ask because the web pages don't match releases, the FindBugs
plugin source
in SourceForge CVS has needed fix
Is anyone actually maintaining the FindBugs plugin?
I ask because the web pages don't match releases, the FindBugs
plugin source
in SourceForge CVS has needed fixes, SourceForge has no FindBugs
plugin
downloads available, something called "1.0-SNAPSHOT" from ibiblio
maven-plu
ou've
highlighted.
- Brett
Jeff Jensen wrote:
Hi,
Is anyone actually maintaining the FindBugs plugin?
I ask because the web pages don't match releases, the FindBugs plugin source
in SourceForge CVS has needed fixes, SourceForge has no FindBugs plugin
downloads available, something called &quo
Hi,
Is anyone actually maintaining the FindBugs plugin?
I ask because the web pages don't match releases, the FindBugs plugin source
in SourceForge CVS has needed fixes, SourceForge has no FindBugs plugin
downloads available, something called "1.0-SNAPSHOT" from ibiblio
maven-p
[ http://jira.codehaus.org/browse/MAVEN-1618?page=all ]
Brett Porter closed MAVEN-1618:
---
Resolution: Won't Fix
please file this at maven-plugins.sf.net. The findbugs plugin is not developed
here. Thanks!
> maven-findbugs-plugin gets depe
[ http://jira.codehaus.org/browse/MAVEN-1618?page=all ]
Krystian Nowak updated MAVEN-1618:
--
Attachment: emptyExcludeFilter.xml
> maven-findbugs-plugin gets dependency's path in w
[ http://jira.codehaus.org/browse/MAVEN-1618?page=all ]
Krystian Nowak updated MAVEN-1618:
--
Attachment: project.properties
> maven-findbugs-plugin gets dependency's path in w
maven-findbugs-plugin gets dependency's path in wrong way
-
Key: MAVEN-1618
URL: http://jira.codehaus.org/browse/MAVEN-1618
Project: maven
Type: Bug
Versions: 1.0.2
Environment: Maven ver. 1.0.2,
dependencies. Issue: 1003083.
Changes:
o Use findbugs version 0.8.4.
To automatically install the plugin, type the following on a single line:
maven plugin:download
-DgroupId=maven-plugins
-DartifactId=maven-findbugs-plugin
-Dversion=0.8.4
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http
0.8.2.
To automatically install the plugin, type the following on a single line:
maven plugin:download
-DgroupId=maven-plugins
-DartifactId=maven-findbugs-plugin
-Dversion=0.8.2
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://maven-plugins.sour
ceforge.net/maven/
For a manual installatio
Does that mean that we are agreed to get rid of the findbugs plugin in maven
and go with the version in maven-plugins? I don't want to delete any hard
work :-)
Eric
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 04, 2003
> Also, what we need is some sort of plugin installer similar
> to how eclipse or jedit work to pull in plugins from every
> repo, maybe tied to a master list of possible repos...
> Dreaming outloud...
There is a plugin:download goal that is half finished, but the plugin
dependency mechanism w
wever,
they will let me know when the bcel catches up. Also an upload request for
the coreplugin to be versioned as well.
Dom4j-1.4 is fine however.
So, according to Brian, does that mean that we are agreed that the findbugs
plugin needs to live at maven-plugins? If you are happy with the chan
It is not a violation of the Apache license, nor of the LGPL; but it has
been ASF policy to not release software that requires the use of
non-BSD-licensed software. I suppose that is a fuzzy line - do we use
Linux-specific kernel calls, for example, or GCC-only macros? - but the
overall principle
lugin handling is simplified, it won't be an
issue, but
for now - core plugins have far more exposure than anything else.
I agree there should only be 1 findbugs plugin. I don't really care
which one dies / is folded into the other.
Cheers,
Ben
Eric Pugh wrote:
Ben,
I suggested a w
Hi there,
we have a script that uses an LGPL jar file during execution time.
To run the script, Maven will automatically download the LGPL jars, they
are not stored in CVS, or shipped with Maven.
Is it ok by ASF policy to include the above script as part of Maven?
- Forwarded by dIon Gilla
won't be an
> issue, but
> for now - core plugins have far more exposure than anything else.
>
>
> I agree there should only be 1 findbugs plugin. I don't really care
> which one dies / is folded into the other.
>
> Cheers,
>
> Ben
>
> Eric Pugh wrote:
>
>
Ben,
This looks cool. Well done, I will be trying this one out soon.
--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net
Ben Walding wrote:
I committed a FindBugs report plugin yesterday. Basically it is a
static class file checker that analyzes your class files for well
known bug patter
I committed a FindBugs report plugin yesterday. Basically it is a
static class file checker that analyzes your class files for well known
bug patterns.
For instance, here are the results from running it against Maven
M UCF: Useless control flow in
org.apache.maven.DefaultProjectUnmarshaller.p
28 matches
Mail list logo
