Links

  • 1. Sogeti
  • 2. JBoss
  • 3. IBM
  • 4. Oracle
  • 5. SpringSource
  • 6. NL-JUG
  • 7. Java

Archives

Syndication  RSS 2.0

RSS 1.0
RSS 2.0

Bookmark this site

Add 'JCN Blog' site to delicious  Add 'JCN Blog' site to technorati  Add 'JCN Blog' site to digg  Add 'JCN Blog' site to dzone

Posted by Ron Lievens at 13:59 on Wednesday 2 December    Add 'Mijn standaard Jave/Eclipse ontwikkel omgeving' site to delicious  Add 'Mijn standaard Jave/Eclipse ontwikkel omgeving' site to technorati  Add 'Mijn standaard Jave/Eclipse ontwikkel omgeving' site to digg  Add 'Mijn standaard Jave/Eclipse ontwikkel omgeving' site to dzone

Na aanleiding van verschillede discussies over hoe de Java/Eclipse ontwikkel omgeving er uit moet zien, heb ik een voorstel voor een standaard Java/Eclipse ontwikkel omgeving gemaakt.

Mijn voorstel maakt volledig gebruik van open source tooling en is toegespitst op code kwalitie. Mijn voorstel bevat Apache Ant, Apache Maven2, Subversion, CheckStyle en Findbugs intergratie met Eclipse. Verder maakt mijn voorstel gebruik van de EclEmma eclipse plugin voor code dekking en uiteraard maak ik gebruik van de JCN Style Guide in Eclispe.

Read the rest of this entry »

Posted by Rene de Groot at 9:05 on Thursday 1 October    Add 'Portable Optional Tasks with Library Dependencies' site to delicious  Add 'Portable Optional Tasks with Library Dependencies' site to technorati  Add 'Portable Optional Tasks with Library Dependencies' site to digg  Add 'Portable Optional Tasks with Library Dependencies' site to dzone

Many tasks in Ant are portable. The task <javac> is a portable way to compile code, it works on every install of Ant. Non-standard tasks are easily added by the <taskdef> task. Using a taskdef an <svn> task can be added to use Subversion.[1] The <taskdef> has a classpath attribute that allows the loading of (3rd party) libraries. These libraries can be distributed alongside the Ant script.

Some Ant optional tasks require 3rd party library installations on the host executing the ant command.[2] This breaks portability, because these libraries are required separately from the build script. One means of using optional task with 3rd party library dependencies is to exend the classpath of the existing classloader.[3,4]

For example:
The optional ant task <scp > exists, but does not work, in a default Ant install. This example shows how to avoid the “Before running the build script, copy the jsch.jar into your %ANT_HOME%/lib” step.

<taskdef
  resource="net/jtools/classloadertask/antlib.xml"
  classpath="lib/ant-classloadertask.jar"/>
<classloader
  loader="project"
  classpath="lib/jsch.jar"/>

<scp
  file="service.ear"
  todir="deploy@stagingmachine.local:${hostdir}"
  keyfile="${user.home}/.ssh/id_dsa"
  passphrase="secretpassphrase" />

A 3rd party library can be added without abiding by the classpath rules of ant.

[1]http://subclipse.tigris.org/svnant/svn.html
[2]http://ant.apache.org/manual/install.html#librarydependencies
[2]http://www.acrhodes.com/2009/08/ants-scp-task/
[3]http://enitsys.sourceforge.net/ant-classloadertask/

Posted by Barend Garvelink at 11:45 on Thursday 10 August    Add 'Ant 1.7: antlibs' site to delicious  Add 'Ant 1.7: antlibs' site to technorati  Add 'Ant 1.7: antlibs' site to digg  Add 'Ant 1.7: antlibs' site to dzone

Op onjava staat een artikeltje over antlibs, een nieuwe feature van Ant 1.7. Antlibs zijn een verbeterde manier om 3rd-party ant tasks te distribueren, waarbij alle benodigde gegevens en instellingen in één enkele jar worden verpakt.

So, what was wrong with normal taskdefs that desperately needed to be fixed?

  • Classpath lookups for taskdef classes–people still have problems getting JUnit to work properly with Ant.
  • No standard way to distribute custom tasks.
  • Optional tasks are tightly coupled to Ant core.

Het artikel beschrijft wat antlibs zijn, hoe je ze kunt gebruiken, hoe je ze zelf kunt maken, en wat je moet doen om een bestaande taskdef om te zetten in een antlib. Lees Ant 1.7: Using antlibs op OnJava.com.

Posted by Hans-Jürgen Jacobs at 14:06 on Monday 7 November    Add 'Incremental and fast builds using Ant' site to delicious  Add 'Incremental and fast builds using Ant' site to technorati  Add 'Incremental and fast builds using Ant' site to digg  Add 'Incremental and fast builds using Ant' site to dzone

Build scripts or files, created and developed during a software development project, are important artifacts for development teams; their quality and speed significantly affect a team’s productivity. As a project’s size grows, the build process also grows and becomes more complex. Long builds waste a developer’s time and amplify the time required to view the results of the changes made to the system. In addition, the XP (extreme programming) practice of continuous integration grows more difficult as developers’ working sessions increase because of the long builds that do needless work every time they execute. Ultimately, these negative consequences of long builds impair the project’s progress. In this article, Arin Ghazarian describes the concepts of incremental builds, dependency checking, and other related concepts in build processes, then proposes some techniques and guidelines to optimize and quicken builds written in Apache Ant. [javaworld.com]

Posted by Barend Garvelink at 10:27 on Friday 3 June    Add 'Ant 1.6.5' site to delicious  Add 'Ant 1.6.5' site to technorati  Add 'Ant 1.6.5' site to digg  Add 'Ant 1.6.5' site to dzone

Zojuist is Ant versie 1.6.5 gereleased. Dit is een bugfix release die een drietal problemen oplost:

* <move> was unable to replace existing files or write into existing directories. Bugzilla report 34962.
* <macrodef> with redefined default values was incorrect. (Fix for 31215 had a bug). Bugzilla report 35109.
* <javadoc> will convert backslashes to forwardslashes when generating file list by useexternalfile. Bugzilla report 27814.

[Ant 1.6.5 download page]

Posted by Hans-Jürgen Jacobs at 11:37 on Friday 14 January    Add 'Introduction to Code Coverage' site to delicious  Add 'Introduction to Code Coverage' site to technorati  Add 'Introduction to Code Coverage' site to digg  Add 'Introduction to Code Coverage' site to dzone

Lasse Koskela heeft voor de JavaRanch nieuwsbrief een verhaaltje geschreven over Code Coverage Analysis. Dit artikel begint met een introductie over Code Coverage Analysis en geeft daarna voorbeelden voor het gebruik van Clover, JCoverage en GroboCoverage in Ant builds. De diepgang is niet enorm, maar het is verder wel goed geschreven.

http://www.javaranch.com/newsletter/200401/IntroToCodeCoverage.html

Printed: 15 pagina’s A4


© 2020 Java Competence Network. All Rights Reserved.