Problems starting Infra services with new build

[Phillip Rhodes <mo...@gmail.com>]

Team:

This is probably as much a side effect of my own ignorance as
anything, but working with the build artifacts from the "new build",
I'm having some issues running things. I think it's related to some
changes in jar file names, and locations of classes, etc., but I don't
fully understand the startup process yet. Maybe one of you folks can
point me in the right direction?

Basically, I amu using the trivial "hello world" example stuff from
the examples project, but I changed all the dependencies to use the
-3.0-SNAPSHOT artifacts, and I replaced the lib/ and lib-dl/
directories in my project-home directory with the ones from
dist/target/apache-river-3.0-SNAPSHOT from where I did my build.

Right away I can see that there are some differences. There are, for
example, more files in lib/ now than before, and not all of them have
corresponding entries in the infra.config file. There are some
differences in the lib-dl/ directory as well.

I assume I need to make compensating changes to infra.config to match
the new structure... does this sound right? If so, does *every* jar in
lib/ need to be mentioned in the .config? If not, how do I tell which
ones do need such a mention?

Also, can anyone explain what the relationship is between the  lines
that look like e this in the confile file:

"http://" + host + ":" + port + "/reggie-dl.jar" + jskdl,

and the files physically contained in the lib-dl/ folder (which seem
to mostly end in -dl.jar)? Or is there any relation?

Sorry, I know this is a lot of questions, but any help would be
greatly appreciated.


Phil


This message optimized for indexing by NSA PRISM