Re: [morph-developer] Help with build / Should we start a wiki?

[Matt B. <gud...@ya...>]

--- Matt Sgarlata
<Mat...@wh...> wrote:

> Hi Matt B-
> 
> I just downloaded the latest from Morph and all the
> changes you've 
> implemented look awesome.  It's good to see someone
> go through and fix 
> some of my blundering attempts at proper
> synchronization ;)  I noticed 
> the try/finally blocks you added to the
> SimpleDelegatingTransformer as 
> well -- I wish I had thought about that!

:)

> 
> One thing I'm having trouble with is getting the new
> build to work.  I 
> can keep blundering away with it, but if you have
> any pointers or things 
> you would recommend I read to understand Ivy, etc. I
> would greatly 
> appreciate it.
>

Yeah, I thought about that only after the fact--sorry.
 I decoupled the Ivy build from the Morph build,
making both old builds work as legacy-build as you
requested.  All you need to do is:

1) Get Ivy 1.4.1 and add to $ANT_HOME/lib (there are
other ways but that's the easiest).
2) Synch Composite, and run 'ant publish' against it
3) Synch Morph, and run e.g. 'ant rebuild-all' or some
such against it

Running Composite's publish target puts an
"integration version" of Composite into your local
repository for Morph to build against... the idea
being that we should release Composite 1.0.1 and
publish somewhere like iBiblio, then Morph could/would
build against that in the wild, see?
 
> This brings me to the other subject of the email,
> which is: should we 
> start a wiki?  I'm thinking it could be more
> effective to have our 
> documentation in a wiki so that anyone can modify it
> rather than 
> basically restricting documentation modification to
> developers of 
> Morph.  I know in theory a non-developer could
> download the source, 
> submit a patch, and hope it gets excepted, but I
> think most users would 
> be much more likely to contribute to a wiki than try
> to sync with SVN to 
> make sure you're working with the latest, figure out
> where the reference 
> document source is, figure out how to prepare a
> patch for it, submit the 
> patch and watch it sit for 6 months.  Off the top of
> my head, wikia 
> (for-profit wikipedia knockoff) has free wiki
> hosting that we could 
> leverage.  Another possibility is to investigate
> what wiki software 
> Apache is using in case we ever make the move over
> there (it would suck 
> if there wasn't an automatic way to transfer the
> wiki information).  
> Spider Strategies also recently started using wiki
> software so I might 
> be able to get us our own wiki hosted on Spider
> servers using that software.
> 

We definitely need to break down and work on Morph's
docs, so a wiki could be useful.  Apache uses MoinMoin
and Confluence, FWIW...

-Matt B

> Matt S
> 
>
-------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get
> the chance to share your
> opinions on IT & business topics through brief
> surveys-and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> morph-developer mailing list
> mor...@li...
>
https://lists.sourceforge.net/lists/listinfo/morph-developer
> 



 
____________________________________________________________________________________
Looking for earth-friendly autos? 
Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.
http://autos.yahoo.com/green_center/