Re: JavaSrc
Davanum Srinivas wrote: Team, Here's the latest output - http://nagoya.apache.org/~dims/maven/ running against maven's source code. this was so that we could compare with maven's jxr generated code - http://maven.apache.org/xref/index.html. Awesome! How do you think to make Gump run it? If we launch Gump adding -Dgump.merge=/.../merge.xml, we get a merged view of all the workspace, and can use that info to drive it all. Right now i need help from anyone who knows ANTLR and can handle grammars with ease. I'm a bit ignorant too... some info to get started http://www.antlr.org/doc/getting-started.html http://microprogrammers.150m.com/COMPILER/Writing%20basic%20expression%20parser%20in%20Antlr-article.htm http://www.bearcave.com/software/antlr/antlr_examples.html we need to update the grammer and clean up some cross referencing stuff. Can anyone help me? I'm game. What's to do? alternatively, does anyone know others who may have knowledge and might be willing to help? Stephan Michels. He wrote http://chaperon.sourceforge.net/ and is a Cocoon committer. I'm sure that in need he can give us a hand. In any case, here is the latest version of the Java grammer (Public domain): http://www.antlr.org/grammar/java/java.g http://www.antlr.org/grammar/java/java.tree.g There should be other places where we get 1.4 stuff like: http://groups.yahoo.com/group/antlr-interest/message/4968 http://groups.yahoo.com/group/antlr-interest/message/7776 -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [JAVASRC] Ready... set... ?!? What to do with current CVS?
[snip] Next I want to host Centipede Cents and Maven plugins. My best bet is a jakarta-alexandria/plugins dir with jakarta-alexandria/plugins/cents jakarta-alexandria/plugins/maven I'm -1 on this. If Alexandria is to be a commons like place, I'd rather not host other projects plugins here, I'd prefer the code behind the plugins to be in alexandria and the plugins be in their own projects. As well, not all maven plugins are about documenting and analysing source code, so I don't think it's appropriate they all be hosted here. I'd much rather: a) Maven was a top-level project (jakarta-maven) b) Maven's plugins were a top-level project (jakarta-maven-plugins) But that's a discussion for turbine-maven-dev. Jason has access to CVS here, and he can take care of making/committing the MAven plugins in the jakarta-alexandria/plugins/maven dir. These are the main points, any suggestions? AFAIK, there's be no discussion about moving plugins to alexandria on the turbine-maven-dev list. And personally, since it's about moving source code from one project to another, I'd expect the developers on that project to agree first. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [JAVASRC] Ready... set... ?!? What to do with current CVS?
[EMAIL PROTECTED] wrote: [snip] Next I want to host Centipede Cents and Maven plugins. My best bet is a jakarta-alexandria/plugins dir with jakarta-alexandria/plugins/cents jakarta-alexandria/plugins/maven I'm -1 on this. If Alexandria is to be a commons like place, I'd rather not host other projects plugins here, I'd prefer the code behind the plugins to be in alexandria and the plugins be in their own projects. I don't think so; Tomcat hosts the Ant task about himself, not Ant. This is common practice. But if I the project that will use the plugin wants to keep control of it, it's fine for me. As well, not all maven plugins are about documenting and analysing source code, so I don't think it's appropriate they all be hosted here. ? Oh, maybe I wasn't clear. I want to host the Maven plugins *about* the Alexandria project here. Just as Ant tries to make the projects keep their tasks instead of submitting them to Ant tp be included in optional.jar. I'd much rather: a) Maven was a top-level project (jakarta-maven) b) Maven's plugins were a top-level project (jakarta-maven-plugins) But that's a discussion for turbine-maven-dev. yup. Jason has access to CVS here, and he can take care of making/committing the MAven plugins in the jakarta-alexandria/plugins/maven dir. These are the main points, any suggestions? AFAIK, there's be no discussion about moving plugins to alexandria on the turbine-maven-dev list. Heck, no. Never thought that! I'm *never* gonna move plugins :-O And personally, since it's about moving source code from one project to another, I'd expect the developers on that project to agree first. Sorry again for not being clear :-/ This post is *only* about Alexandria, not Maven or Centipede. Just as Cocoon creates war files to be used in Tomcat, I want to make Alexandria create plugins of the Alexandria projects for Ant, Centipede and Maven. Of course, if Maven prefers to host the plugin about alexandria itself, no problem at all, less to worry about ;-) -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]