Re: [JXTA discuss] JXTA/NetBeans

Hey Tim -

  W/ MyJXTA (http://myjxta2.jxta.org) we included a NB project file w/in the
  CVS repository. As such, all folks need to is "bootstrap" thier dev env:

    http://wiki.java.net/bin/view/Jxta/HowCanIObtainMyJXTAsSource

    read: 2 Ant commands

  And you are ready to edit, compile and run MyJXTA w/in NB. Quite enabling.

  Now, to your question. I'd start in one project and refactor across multiple
  repositories as needed. Before spanning across more then one repository I
  would expect a typical project structural change to include multiple "modules"
  w/in one repository before spilling out to multiple repositories. Just a
  gut feel on my part.

  hth,

- james

--
James Todd :: blogs.sun.com/gonzo | weblogs.java.net/blog/gonzo 

MyJXTA :: use it - learn it - do it

Java == platform independence
XML  == application independence
JXTA == network independence

Secure End-to-End Computing 


Tim Bray wrote:
> I'm building a project in NetBeans and I'm going to use JXTA.  It's a 
> really typical JXTA thing, not unlike the canonical RestoPeer/HungryPeer 
> example from the O'Reilly book, only with four classes of peers.
> 
> Here's the question: what's a good way to organize the NetBeans project 
> structure for this?  Is anyone else doing this?  Would you use a 
> separate project for each class of peer, or do it all in one big 
> project? -Tim
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>