On Mar 13, 2007, at 4:51 AM, Rupert Smith wrote:
Hi Jason, I suppose you could take some feedback from people
experiences in using it? Not exactly a repeatable automated test suite
I know. So far its worked fine for me and I've retrotranslated tests
and run them under 1.4 and it all went well...

Yup, I will continue to do that, but I'd like to make something automated too.


Anyway, the real reason I'm mailing is because I think you might have
introduced a problem in the new snapshot. Either that or the examples
on the site or just wrong. I got a new SNAPSHOT after this weekend and
it broke the build. I notices that the <jarfileset> is now wrapped
inside a <jarfilesets> element in the example. I did this to mine (as
it was saying no sources), but now the <jarfileset> won't accept a
<basedire>.

The docs are wrong, its <directory> not <basedir> now... will update the site docs. Thanks for pointing this out.


The only reason I was using jarfileset was because I was doing that
jar translation and then using build-helper to attach and classify the
results, as per the old alpha-1 release. I upgraded everything to use
the new translate-project goal and it all worked fine (and I could get
rid of the build-helper plugin from the pom too).
You might like to check that the jar translation is all working right
or update the example. Thought I'd let you know.

I'm fairly sure its just the example is wrong. Please let me know if you find that its still broken even when using <directory>.

--jason


Rupert

On 3/13/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
I've been trying to think of ways to make integration tests for the
retrotranslator-maven-plugin which actually test something useful and
validate the plugin works.  But so far I'm not sure how to do it.

I think I need to compile some stuff with Java 5, then try to run it
with Java 1.4 and see if it works or not.  But to do that I think I
need to have the tests know about 2 different JVM's which is a PITA.

Or I could compile with Java 5, translate and then inspect the byte-
code of the translated bits to see if its major/minor versions are
correct.  Though that doesn't really test it fully.

Anyways... anyone have any ideas on how to make useful integration
tests for this plugin?

--jason

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

Reply via email to