[antlr-interest] New Maven artifacts, some fixes, buidlable source

[Tilman Bender]

Hi list, Hi Jim,

I really like the gunit plugin and the fact, that it gives me a good  
feedback on what went wrong with my gunit-tests,
but it would also be cool to have a goal (maybe one that can only be  
called by explicitly stating so in the execution-element in the plugin  
section)
that also does the conversion of gunit to JUnit tests.

Why would you want that? Simple Answer: Reporting:

1. The results get included into the project website as all the other  
JUnit results do.
2. Using tools like corbertura or clover you can keep an eye on your  
test-coverage and see where your recognizer lacks proper unit tests.

I can get along very well with the plugin as it is, but this feature  
would really be the cherry  on top of the cake ;-)

kind regards
Tilman Bender
Student des Software Engineering
Hochschule Heilbronn
tbender at stud.hs-heilbronn.de



Am 02.05.2009 um 00:31 schrieb Jim Idle:

> Hi,
>
> We have a new Maven artifact available: maven-gunit-plugin, this  
> automates the running of gunit tests as part of a Maven build.  
> Documentation to follow, but it is fairly easy to work out if you  
> already know ANTLR and gUnit. It can be used as:
>
> <plugin>
>    <groupId>org.antlr</groupId>
>        <artifactId>maven-gunit-plugin</artifactId>
>        <version>3.1.3</version>
>        <configuration>
> ...
>        </configuration>
> </plugin>
>
>  - - - - - -
>
> I have also fixed the issue with the ANTLR 3.1.3 whereby the -make  
> option (which the Maven plugin relies on) was not detecting changes  
> in .g files correctly and was assuming that everything was up to  
> date. If this was bugging you enough that you want to use the  
> current snapshot of antlr, then configure your pom.xml file like this:
>
> 1) Add a reference to the ANTLR snapshot repository at the <project>  
> level:
>
>     <!--
>
>     Inform Maven of the ANTLR snapshot repository, which it will
>     need to consult to get the latest snapshot build of the runtime  
> and tool
>     if it was not built and installed locally.
>     -->
>     <repositories>
>
>       <!--
>         This is the ANTLR repository.
>         -->
>         <repository>
>             <id>antlr-snapshot</id>
>             <name>ANTLR Testing Snapshot Repository</name>
>             <url>http://antlr.org/antlr-snapshot</url>
>             <snapshots>
>                 <enabled>true</enabled>
>                 <updatePolicy>always</updatePolicy>
>             </snapshots>
>
>             <releases>
>                 <enabled>false</enabled>
>             </releases>
>
>         </repository>
>
>     </repositories>
>
> 2) Change the version number of the antlr3-maven-plugin to  
> <version>3.1.4-SNAPSHOT</version>
>
> - - - - - -
> Finally today, I have corrected the build of the source code  
> collection jars. You can always find the latest executable jar of  
> ANTLR (java -jar xxx.jar t.g) and the latest buildable source code  
> at this permalink:
>
> http://antlr.org/hudson/job/ANTLR_Tool_Daily/lastSuccessfulBuild/org.antlr$antlr-master/
>
> Similarly these artifacts are copied in to: http://antlr.org/download
>
> antlr-master-3.1.4-SNAPSHOT-completejar.jar
> antlr-master-3.1.4-SNAPSHOT-src.jar
>
>
> Jim
>
> List: http://www.antlr.org/mailman/listinfo/antlr-interest
> Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-email-address

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.antlr.org/pipermail/antlr-interest/attachments/20090505/2fd5a672/attachment.html