Comments (7)
Hmmm. This will be an interesting one.
While this project must support 2.x to be useful, I don't think I want to drop support for 1.3.x. Being able to do this in the same codebase would be very tough, and and likely result in some monumental hackery.
I will need to have a look around for examples of working projects that maintain two active branches, specifically how that works with Maven. For example, would there be two different artifacts, or a single artifact with two classifiers, or perhaps two artifacts versioned to match FindBugs, e.g. tdd4fb-1.3.9.1 and tdd4fb-2.0.1.1?
Do you have any suggestions/preferences?
Thanks for the bug report!
from test-driven-detectors4findbugs.
I think perhaps an artifact per major findbugs release. So perhaps a new
tdd4b2 to support findbugs 2.x. Most new minor or bug fix versions of
findbugs will not require changes to the testing framework.
On Jul 4, 2013 3:25 AM, "Graham Allan" [email protected] wrote:
Hmmm. This will be an interesting one.
While this project must support 2.x to be useful, I don't think I want to
drop support for 1.3.x. Being able to do this in the same codebase would be
very tough, and and likely result in some monumental hackery.I will need to have a look around for examples of working projects that
maintain two active branches, specifically how that works with Maven. For
example, would there be two different artifacts, or a single artifact with
two classifiers, or perhaps two artifacts versioned to match FindBugs, e.g.
tdd4fb-1.3.9.1 and tdd4fb-2.0.1.1?Do you have any suggestions/preferences?
Thanks for the bug report!
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-20464915
.
from test-driven-detectors4findbugs.
Hi @bokken,
I have tried something a little more... inventive (shall we say ...)
That is, to use a Java proxy interface to simulate an interface that will work from 1.3.7 to 2.0.1 (I also just discovered that 2.0.1 removed as well as added methods). If this works, it means that we don't need to worry about multiple artifacts. I still need to be reactive to interface changes in later versions, but they need a source level change anyway.
Would you be able to try it and let me know if it works?
from test-driven-detectors4findbugs.
Sorry, I know it's a pain, but could you clone the repo to test? There's a lot of hurdles for both of us to jump if we want it available from Maven snapshot repositories. Let me know if that's a problem.
from test-driven-detectors4findbugs.
Hi @bokken,
I plan to do perform another release to Maven Central once this issue is confirmed. If you think you will be unable to find the time to test (which is fine) then please let me know and I'll take the risk, and go by my own personal testing.
Thanks.
from test-driven-detectors4findbugs.
I am out of the office right now. I should be able to take a look at your
changes next week sometime.
On Jul 4, 2013 2:40 PM, "Graham Allan" [email protected] wrote:
Hi,
I plan to do perform another release to Maven Central once this issue is
confirmed. If you think you will be unable to find the time to test (which
is fine) then please let me know and I'll take the risk, and go by my own
personal testing.Thanks.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-20491314
.
from test-driven-detectors4findbugs.
I'm going to assume this change fixes the problem, and begin preparing for a new release to nexus.
from test-driven-detectors4findbugs.
Related Issues (17)
- NullPointerException when initializing a BugAccumulator in the detector's constructor HOT 6
- Test "createsFileSystemCodeBaseLocatorForEachJarPathGiven" is failed on Windows HOT 5
- Exception/error messages of DetectorAssert is not informative HOT 1
- missing XFactory interning in test driver HOT 4
- BugMatcher not propagated by Detector --> Detector2 delegation method HOT 2
- DetectorAssert usability problem for multiple matchers HOT 1
- DetectorAssert.addRegistrar(...) has no effect HOT 3
- Compatibility with Findbugs 3 HOT 3
- PluginDoesntContainMetadataException because the wrong findbugs.xml is found when looking for the core plugin HOT 3
- Using Java 8 lambdas as tested classes
- Make available from Maven Central HOT 3
- Possibly incorrect license listed HOT 1
- RuntimeException: Failed to setup FindBugs dependencies for testing caused by FileNotFoundException HOT 6
- jdk 1.6 HOT 1
- java.lang.ExceptionInitializerError will thrown many times HOT 3
- Support Detector2 interface HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from test-driven-detectors4findbugs.