Yes that would be easy to put in place, all that's really needed is a standard XML format to describe projects, components, etc... I'm starting to work on that first :)

J Aaron Farr wrote:
Quoting Yannick Menager <[EMAIL PROTECTED]>:


I was thinking of writing a GUI tool to help assemble merlin applications, and It would have been nice if it could just go to the repository and list retrieve a list of all available components.

Unless I'm wrong, at this moment that is not possible unless i was to do some screen scrapping of the index.htmls, which would be a huge PITA ( not to mention might not work if the remote repository customised those pages ).

It would be then nice to have a standard listing file, with details about all the components available in the remote repository.

What do you guys think ?


Additional tools like this are much needed.  It's been on my 'to do' list for
months.

On a related note, I've been thinking of putting together a cocoon web app that
would be a web front end to a maven-style repository.  It could parse the
directories and give you and easy way to see (and query) what's available in the
repository, what's the latest version, and short descriptions (using maven
POM's) of the projects.  If this were properly put together we could have it
communicate to any client GUI app like you're talking about very easily.  That
way you don't have to parse index.html-like files.  Instead, the web app could
send an XML representation of the repository.

Yeah, the more I think about this, the more I think it would be a good idea.  If
you're interested, I could work on this web-app back end and could provide what
you need for the GUI side.  What do you think?

---
  jaaron      <http://jadetower.org>



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



Reply via email to