Hi, Chris,
I thought I would answer based on what I recall to be the original purpose of
splitting them into a ‘server’ and ‘servlet’ directory.
It was written in a way to allow other servlet containers to run the ‘servlet’
code without making them dependent on each other.
With that said,
Christofer, can you create a [WIP] PR for this work? Then I’ll have a context
from which I can review / ask stupid nubie questions :-)
Also, what’s the executive summary for running maven to build a release (or at
least all of the jars) using this work? And to run the tests? I’d like to
Yeah, this is a ~confusing and an under doc’d area.
Glad you’re back on track.
There has been some improvement in recent time - e.g., [1][2][3] all post 1.1.0.
Any concrete suggestions regarding that would be appreciated.
Please consider contributing doc improvements, a new sample or recipe,
[
https://issues.apache.org/jira/browse/EDGENT-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale LaBossiere resolved EDGENT-359.
Resolution: Fixed
> CLONE - Review release process / documentation
>
I’m not really familiar with that part of Edgent. I’m hoping Susan Cline will
notice this and respond.
— Dale
> On May 31, 2017, at 3:51 AM, Christofer Dutz
> wrote:
> ...
> While finishing the Maven migration of the last missing tests and finding a
> way to get
Hi all,
After more digging I was able to figure out the issue. In my first jar (
cputemptopology-1.0.0.jar) which contains the TopologyBuilder
implementation, I haven't registered the service provider and hence the
ServiceLoader was unable to pick up the service. After fixing this I was
able to
Hi guys,
While finishing the Maven migration of the last missing tests and finding a way
to get rid of the one or the other monster while at it, I noticed the two
modules console/server and console/servlets.
It seems as if “servlets” contain the real servlets for the server module and
the