ESOE Development Google Group

Recent spam emails

2009-09-20T05:58:54Z

Hi All,
Due to recent spam emails, I've changed the list settings so that email from
new members will be moderated. This means there will be a delay the first
time you post to either list, but will hopefully eliminate the spam we've
been seeing lately.
Regards,
Shaun

ESOE Project News - Releases, Git

2009-08-11T06:08:56Z

Hi All,
After a long period of quiet, mostly due to the shifted priorities of our
development team, I'm glad to announce that the ESOE Project is back in
active development. We have some updates:
New site, new source control
In preparation for the move to Git source control, we migrated the ESOE
Project site to Redmine ([link]) back in April. We've now moved

Re: [esoe-dev] Status of Apache SPEP for Mac OS X

2009-07-15T23:46:00Z

Hi Tim,

The site is back up, I restarted to correct a config error and it didn't
come up cleanly for some reason.

The status of the SPEP code update is that it's in progress currently. It
was delayed due to workload constraints, but is now back in active
development. I've completed a large number of changes, including the upgrade

Status of Apache SPEP for Mac OS X

2009-07-15T23:31:11Z

Hi
I was wondering what is the current status of Apache SPEP for Mac OS X Server on 64 bit Intel or PowerPC. I understand it was being upgraded to use Xerces 3.0 to be 64 bit compatible.
BTW, I am having trouble connecting to [link]
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Re: [esoe-dev] Re: ESOE Project on git?

2009-06-18T23:45:57Z

Nice one!

Re: [esoe-dev] Re: ESOE Project on git?

2009-06-18T23:37:05Z

After reading this reply, it occurred to me that it's not really unusual to
want multiple source repos, so I went digging through the Redmine issue
tracker. Somebody has already solved this problem and helpfully uploaded a
patch.
From testing this patch, it looks like we'll be able to do everything we

Re: [esoe-dev] Re: ESOE Project on git?

2009-06-18T10:36:48Z

Re branching/tagging:

What if you need to issue an urgent patch release of spepcppdaemon?
You shouldn't be forced to release all components. Separate issue
though I guess.

Re tooling:

If the tooling works better with a monolithic repository then that is
probably the way to go. It seems strange that redmine can't handle

Re: [esoe-dev] Re: ESOE Project on git?

2009-06-18T08:41:05Z

2009/6/18 Luke Daley <lda...@gmail.com>
Good point here, though certain projects are coupled tightly enough that
they should be in sync - for example:
esoecore + esoemanager + esoedeployer
spepjava + spepjavafilter
spepcpp + modspep + spepcppdaemon
Putting some effort into decoupling them might lessen the impact, but the

Re: [esoe-dev] Re: ESOE Project on git?

2009-06-18T04:58:46Z

I prefer smaller repositories.
This does cause issues with branching/tagging etc, but it may be a
good opportunity to investigate whether all of the modules need to be
bound to the same version number and release cycle.
If a monolithic repository can be avoided, I think that should be the
path.

Re: [esoe-dev] ESOE Project on git?

2009-06-18T00:41:24Z

Hi Shaun,

My experience with other large projects and Git has been the single
repository approach with top level directories for each sub component.
I've used a couple that have gone the other way. Overall there are
positives and negatives to both.

What I find does really get painful with the single repository

ESOE Project on git?

2009-06-17T11:23:39Z

Hi All,
It's come time again to revisit the idea of using git for development of the
ESOE project. A few things have changed since this was last discussed, not
the least of which is the transition to Redmine ([link]) for
managing the project.
With the revamped project site, we can now use (almost) any VCS we want. The

Re: [esoe-dev] "True Single Sign On" for Unix-based OS

2009-04-16T21:39:47Z

Hi,
It's not quite true to say that it doesn't support Unix-based OS, because it
is platform agnostic. Authentication is achieved using a Kerberos ticket
which is issued by Active Directory.
LDAP authentication, at least in the context of ESOE, is simple
username/password verification. Storing the state would just be saving your

"True Single Sign On" for Unix-based OS

2009-04-16T17:04:33Z

Hi,
Just to ensure what I understand at this moment. The cool feature like
"True Single Sign On" which automatically authenticate user after login
to Windows OS by Active Directory, is still not implemented for the
Unix-based OS authenticated using LDAP. Am I right? (I haven't tested it
yet, just read the sourcecode)

Re: [esoe-dev] Re: git, future directions

2009-03-05T08:34:55Z

If it's going to be git then the issue tracker needs to change. Take a
look at lighthouse. I am not a huge fan but it's integration with
github is tight. I don't know if there is a solution for lighthouse
that links CI builds with tickets like Jira+Bamboo but I would think
there would be something.

Re: [esoe-dev] Re: git, future directions

2009-03-05T00:49:15Z

Hudson is a good example here. Where possible I'd like to stick to
other open source solutions to support the project. We've been using
Hudson in the past with great success and flexibility.

Hudson at least seems to have pretty decent GIT support
[link]