One problem we're going to have with resolving dependencies via bytecode is
discussed here - http://importscrubber.sourceforge.net/limitations.html.  I
definitely think that checking bytecode for dependencies is very useful,
but it's going to miss things occasionally....

Maybe we can try it for a while and see how it works out.  Maybe there are
other mechanisms which can catch these inlined constants....

Yours,

Tom Copeland
[EMAIL PROTECTED]
703-317-5193


                                                                                       
                                                       
                    Jason van Zyl                                                      
                                                       
                    <jvanzyl@zenp        To:     [EMAIL PROTECTED]        
                                                       
                    lex.com>             cc:                                           
                                                       
                                         Subject:     [maven] update/todo              
                                                       
                    02/22/2002                                                         
                                                       
                    09:40 AM                                                           
                                                       
                    Please                                                             
                                                       
                    respond to                                                         
                                                       
                    "Turbine                                                           
                                                       
                    Developers                                                         
                                                       
                    List"                                                              
                                                       
                                                                                       
                                                       
                                                                                       
                                                       




Hi,

The bootstrap process is working for Maven now. What does that mean? The
basic maven classes needed to generate a build system from a project
descriptor are compiled, then the build system is generated and the
generated build system is used to build all of Maven. Jeff helped clean
this up yesterday and it's working now. It could still use some cleaning
up so if anyone wants to try it out it would be interesting to get some
feedback.

Here's some very short term things I would like to do:

- Refactor importscrubber to make it a general dependency resolver using
bytecode. Tom your input here is crucial. What I would like to do is
take an existing body of source and generate the project descriptor for
it. I want to be able to quickly absorb the other Turbine projects into
the Maven process. I want to automate this as much as possible so that
iterations will be easy. I also want it to be easy for other projects to
use Maven, it should only take them a few minutes to try Maven.

- Get some docs on how to use the CVS ,v parser. Jaunco do you think you
could pop together a tiny howto? I would like to look at how to do
something like CruiseControl (cruisecontrol.sourceforge.net) using your
parser, Tim Endres CVS client library and a scheduler.

Pete and I are currently working on getting the documentation system
fully working and Geir is making a slight change to dvsl to allow for
embedded CDATA elements.


--
jvz.

Jason van Zyl
[EMAIL PROTECTED]

http://tambora.zenplex.org


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


                                                                            
                                                                            
 -------------------------------------------------------------------------- 


This email may contain confidential and proprietary information which is
for the sole use of the intended recipient.  If you received this email in
error, please notify the sender and delete this email from your computer.
Any review, distribution or retransmission of or reliance on this email by
anyone other than the intended recipient is forbidden.




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to