I will be committing the Mavenized version in the next few days. I did
not use GWT since I am not that familiar with it. But migrating could be
a community effort.
Regards,
Eric MacAdie
On 05/14/2010 01:47 AM, Manuel Carrasco Moñino wrote:
Is it the mavenized version available?, it seems you have not commit
the changes to the git repo and I'd like to take a look to it.
About the technology to use, if I can choose, I'd rather GWT :-)
because of many reasons but the main ones are: testability, and we are
already using it at Hupa.
Cheers
Manolo
On Wed, May 12, 2010 at 6:31 PM, David Jencks<david_jen...@yahoo.com> wrote:
I know almost nothing about struts2 or jsf but unless there is a significantly
better experience with struts2 I would hope you would stay with the standards
based solution.
david jencks
On May 12, 2010, at 9:23 AM, Eric MacAdie wrote:
I Maven-ized it, but now I may re-do it in Struts2 since there seems to be more
demand for Struts2 in the marketplace than JSF.
Regards,
Eric MacAdie
On 05/07/2010 02:53 PM, Eric MacAdie wrote:
Let me figure out a bit more about how Maven works before I get back to you.
Regards,
Eric MacAdie
On 05/07/2010 01:08 PM, Manuel Carrasco Moñino wrote:
On Fri, May 7, 2010 at 7:54 PM, Eric MacAdie<e...@macadie.net> wrote:
Would Maven be better? That way I do not have to distribute Hibernate or
other libraries, and people would not have to edit the build file.
Yes, maven is better.
If I do that, I will try to take the build.xml out of the tree. I am still
learning git. I know just enough to update files and push them to github.
Regards,
Eric MacAdie
On 05/07/2010 12:06 PM, Eric MacAdie wrote:
Sure. Give me a little bit to figure that out.
Thanks for taking a look.
Regards,
Eric MacAdie
On 05/07/2010 11:51 AM, Manuel Carrasco Mońino wrote:
Hi,
Eric, could you provide a working way to compile, test, and package
the application in command line?
Right now the build.xml depends on the Netbeans installation and I do
not use it.
Thanks
Manolo
On Thu, May 6, 2010 at 1:49 PM, Eric MacAdie<e...@macadie.net> wrote:
I started a project on GitHub that is a web project that people can use
to
perform some administrative tasks on a James web server.
The URL is http://github.com/emacadie/James-Admin-Web-App
It works with the James 2.3 schema. It does not work with James servers
that
store messages and user info on the filesystem. There have been some
requests/complaints for an easier way to perform some admin tasks in
James.
I found a link to something on sourceforge on the James wiki, but that
project was abandoned.
It is still a bit rough, but right now, you can add, delete and list the
users, as well as get a count of messages in the deadletter table,
delete
the messages in the deadletter table and get a count of the messages for
each account in the inbox.
I use Hibernate and MySQL. I assume it would work with other databases,
but
I have not tried to set up another database with my James server.
I am starting to look into the code for James 3. Perhaps James 3 makes
this
obsolete. Right now the documentation is pretty sparse. Anyway, try it
out
and let me know what you think.
Regards,
Eric MacAdie
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
