Updated: 10/3/2002; 2:02:36 PM.
P@'s Radio Weblog
Patrick Chanezon's Radio WebLog

Wednesday, September 11, 2002

Jelly and Maven: more good stuff from the Jakarta project !

Jelly or executable XML

Jelly is a tool for turning XML into executable code. So Jelly is a Java and XML based scripting and processing engine. Jelly can be used as a more flexible and powerful front end to Ant such as in the Maven project, as a testing framework such as JellyUnit, in an intergration or workflow system such as werkflow or as a page templating system inside engines like Cocoon.

Sounds real cool.

I need to play with this.

Jelly has a weblog.

Maven which uses Jelly is also a cool tool. It is one level of abstraction above ant.

In my team we used ant on our projects and after a while one of us standardized the project structure and ant targets so that we could run a set of standard ant targets with standard ant files.

Maven just does that in a more formalized way and I think this is an excellent initiative from the Jakarta project.

Maven formalizes the project structure and if you follow this structure, it makes your life really easier by automating lots of aspects of the development process.

Maven is a Java project management and project comprehension tool. Maven is based on the concept of a project object model (POM) in that all the artifacts produced by Maven are a result of consulting a well defined model for your project. Builds, documentation, source metrics, and source cross-references are all controlled by your POM. Look here to see the full list of Maven's features.

Maven has many goals, but in a nutshell Maven aims to make the developer's life easier by providing a well defined project structure, well defined development processes to follow, and a coherent body of documentation that keeps your developers and clients apprised of what's happening with your project. Maven alleviates a lot of what most developers consider drudgery and lets them get on with the task at hand. This is essential in OSS projects where there aren't many people dedicated to the task of documenting and propagating the critical information about your project which is necessary in order to attract potential new developers and clients.

8:24:37 PM Google It!      comment []

an interesting interview of the Mandrake cofounder

Looking Back, Looking Forward: Gaël Duval on Mandrake, an interesting interview of the Mandrake cofounder.

Open for Business's Timothy R. Butler talked with Mandrake co-founder Gaël Duval about the company's past, present, and future.

Working myself remotely, I work in Paris from my home over DSL/VPN with a team of 80 people located in California and India, I particularly liked the following comment:

Yes, I'm involved with MandrakeSoft's direction, and also a member of MandrakeSoft's board. But I'm not a real "executive". One reason is because I've worked at home since the beginning of the company. This was my only condition when creating MandrakeSoft! On the executive side, I'm very involved in everything that is related to Web and Internet here, including communication activities and new projects (MandrakeStore, MandrakeClub, etc.). My biggest regret is that I had to stop developing when our development team became so large. It's not easy to manage a team when you aren't located at the same place as everyone else.

8:02:20 PM Google It!      comment []

Grid computing meets Web Services

Grid Computing: Electrifying Web Services, from Web Services Journal is a good article about the new Open Grid Services Architecture (OGSA), where the grid uses web services.

The Open Grid Services Architecture (OGSA) combines technologies to unlock and exploit grid-attached resources. OGSA defines mechanisms to create, manage, and exchange information between Grid Services, a special type of Web service. The architecture uses WSDL extensively to describe the structure and behavior of a service. Service descriptions are located and discovered using Web Services Inspection Language (WSIL). By combining elements from grid computing and Web services technologies, OGSA establishes an extensible and interoperable design and development framework for Grid Services that includes details for service definition, discovery, and life-cycle management.

7:36:12 PM Google It!      comment []

© Copyright 2002 Patrick Chanezon.
September 2002
Sun Mon Tue Wed Thu Fri Sat
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30          
Aug   Oct

Click here to visit the Radio UserLand website.

Subscribe to "P@'s Radio Weblog" in Radio UserLand.

Click to see the XML version of this web page.

Click here to send an email to the editor of this weblog.