Re: [morph-developer] getting involved

[Matt S. <Mat...@wh...>]

> Wanting Apache visibility won't, you can understand,
> be seen as a great reason for incubating.  ;)  The
> community and its experience might be better reasons. 
> Incubator guidelines seem to desire there be some
> level of community already in place; maybe we should
> continue to think about this but pursue other options
> in the meantime.
>   
Yeah, I don't think Morph meets the qualifications needed to make it as 
an Apache project.  I think our most viable options for the time being 
are to use SF or Spider Strategies.  I will do some investigating to 
determine what would be involved in doing some hosting on Spider 
Strategies servers.  I did some more research into my issue connecting 
to SF CVS, and I think it's just an issue with my workstation being 
configured incorrectly.  It seems to get SSH working I need to download 
3 or 4 software programs, generate public and private keys, publish 
public keys at SF, make sure my private keys are in the right place on 
my laptop, configure Eclipse properly, and offer up sacrifice to the IT 
gods.  I'll do some more research in the next couple days and get back 
to you with what I think the best solution is.
> I'm fine with all that.  In this case, the problem was
> the competing String vs. Object setters; the result
> was, in theory, random, however, so we might come back
> to this issue for discussion.
>   
Agreed.  This problem was pointed out to me some time ago, and I hadn't 
really focused on it too much since it's not relevant to the work I am 
doing right now.  There may be a bug report in the issue tracker on SF 
that covers this.  Another area where Morph falls down is it doesn't 
support all the options for manipulating collections that exist in the 
JavaBeans specification, namely methods like addChild(int index, Object 
value) or whatever the signature is.