: Sun, December 5, 2010 6:02:41 PM
> Subject: Re: API and VM compatibility verification
>
> On 12/05/2010 11:47 PM, Wade Chandler wrote:
> > They have Ant tasks, so you don't have to worry about trying to change the
> > underlying build system. Too, animal-sniffer
On 12/05/2010 11:47 PM, Wade Chandler wrote:
They have Ant tasks, so you don't have to worry about trying to change the
underlying build system. Too, animal-sniffer is a regular Java library if you
need something more elaborate than the Ant tasks provide. See:
I read about this. But i could
- Original Message
> From: Sim IJskes - QCG
> To: river-dev@incubator.apache.org
> Sent: Sun, December 5, 2010 5:06:17 PM
> Subject: Re: API and VM compatibility verification
>
> On 12/05/2010 02:18 PM, Michał Kłeczek wrote:
> > I know we're not us
On 12/05/2010 02:18 PM, Michał Kłeczek wrote:
I know we're not using Maven (yet?) but look at:
http://mojo.codehaus.org/animal-sniffer-maven-plugin
I've had a change to start maven and compile and verify the src
directory, but my lack of experience with maven is limiting to say the
least. Wou
- Original Message
> From: Peter Firmstone
> To: river-dev@incubator.apache.org
> Sent: Sun, December 5, 2010 3:56:30 PM
> Subject: Re: API and VM compatibility verification
>
> Sim IJskes - QCG wrote:
> > On 12/05/2010 02:18 PM, Michał Kłeczek wrote:
> >
Sim IJskes - QCG wrote:
On 12/05/2010 02:18 PM, Michał Kłeczek wrote:
I know we're not using Maven (yet?) but look at:
http://mojo.codehaus.org/animal-sniffer-maven-plugin
That looks really promising. Cool!
Gr. Sim
Certainly does.
Cheers,
Peter.
On 12/05/2010 02:18 PM, Michał Kłeczek wrote:
I know we're not using Maven (yet?) but look at:
http://mojo.codehaus.org/animal-sniffer-maven-plugin
That looks really promising. Cool!
Gr. Sim
I know we're not using Maven (yet?) but look at:
http://mojo.codehaus.org/animal-sniffer-maven-plugin
On Sat, Dec 4, 2010 at 5:00 PM, Sim IJskes - QCG wrote:
> Hello,
>
> Is there a tool that we can use to verify API compatibility? So we can make
> sure we do not call methods that do not exist?
On 04-12-10 20:54, Wade Chandler wrote:
I don't really know of any. One way would be to run binary tests against
different JREs/JDKs. Compile with the desired JDK. Then run other things with
the target. Depending on code coverage of the tests that would be very useful.
I've reconfigured the Riv
The JDO project does signature checking using reflection on a jar
file. The expected values of reflection are stored in a file that
looks a lot like the signature of the class itself.
Here's a snippet of the signature definition file:
public interface javax.jdo.datastore.JDOConnection {
On 04-12-10 20:54, Wade Chandler wrote:
I don't really know of any. One way would be to run binary tests against
different JREs/JDKs. Compile with the desired JDK. Then run other things with
the target. Depending on code coverage of the tests that would be very useful.
I've looked into compilin
On 05-12-10 02:24, Peter Firmstone wrote:
Sim IJskes - QCG wrote:
Is there a tool that we can use to verify API compatibility? So we can
make sure we do not call methods that do not exist?
I've been pondering bytecode analysis.
I think thats the only way to do it. Compile to jars and verify
Sim IJskes - QCG wrote:
Hello,
Is there a tool that we can use to verify API compatibility? So we can
make sure we do not call methods that do not exist?
Gr. SIm
I've been pondering bytecode analysis.
We have just such a tool, have a look at in com.sun.jini.tool.classdepend
It needs to
- Original Message
> From: Sim IJskes - QCG
> To: "river-dev@incubator.apache.org"
> Sent: Sat, December 4, 2010 11:00:10 AM
> Subject: API and VM compatibility verification
>
> Hello,
>
> Is there a tool that we can use to verify API compatibility? So we can make
>sure we do not ca
14 matches
Mail list logo
