A bit of bio. I'm a middle-aged US resident of Lexington, MA, USA. My deep background is in, of all things, secure operating systems and object-oriented databases. I'm the CTO of a company (Basis Technology) that builds software components that analyze text, with an emphasis on non-English. I've had to learn a bit of machine learning over the last few years to keep up; a challenge given that I can barely count to 17.
Around the ASF, I started on CXF, which is where I met Maven for the first time. I'm also involved in the WS project, where I'm a caretaker of XmlSchema, and the Mahout project, where I seem to specialize in ... Maven. At the day job, a considerable part of the code base is java (with a parallel giant heap of C++ code and some JNI connections). Aside from using maven to build it, we're deployed Maven to drive processes like training machine-learning models. In some of these adventures, we've done some spelunking in the caves that connect 'the maven way', 'the the primrose path', and 'adventures in novel applications of maven.' There's nothing like 100MB of model file to lead to some cursing at the (lack of speed) of the dependency plugin unpacking or the assembly plugin packing. My colleagues have a few choice things to say about how easy or hard it is to explain certain 'events' in maven; you may see some patches to 'help:'. I expect to start out around here trimming hedges and pulling weeds in the plugins. I have some ideas and interests in the 'burning issues of the day' (technical and organizational) but I have a lot to learn before I'm prepared to try coding something 'inside the reactor (in more senses of the word than one)', however frustrated I might be from time to time with some aspects of the current design. Oh, and I love to fix doc. If I wanted to add some explanations to the core pom doc (http://maven.apache.org/pom.html), where does it live? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
