I'm curious if anybody else has seen the following? Is this new and expected behavior?
Scott From: Leschke, Scott [mailto:slesc...@medline.com] Sent: Friday, November 16, 2018 3:46 PM To: user@karaf.apache.org Subject: Hmm, that's new. Felix Fileinstall Question. I've been running v 4.2.1 under Java 10.0.2 for a while in my test environment and everything has been working as expected. Recently though, it appeared that fileinstall wasn't picking up that .jar and .cfg files we being changed via hot deploy. I tried various things to get it to work but finally thought I'd do a fresh install of 4.2.1 to see if that might clear things up. To install, I run a PowerShell script that unzips the apache-karaf-4.2.1.zip file, installs the features I need and then I change where Karaf's hot deploy folder is by replacing etc/org.apache.felix.fileinstall-deploy.cfg with my own file, org.apache.felix.fileinstall-bam.cfg. My application deploy folder is a hierarchy rooted at the folder "BAM" (Business Activity Monitoring) that has 3 subfolders in it, runtime (for bundles (jars) the app is dependent on), datasources (where I keep the .cfgs that contain the org.ops4j.datasource-*.cfg files the app needs), and systems which is another folder hierarchy containing .cfg files and subfolders containing files associated with a system. After the install, I'm seeing some "pseudo" bundles with the names and versions shown below. C__BAM_runtime 0.0.0 C__BAM_datasources 0.0.0 Wrap_jardir_C__BAM_systems 0 I've rerun the install a few times with some varying results. In one case, the last name was in line with the others and was shown as C__BAM_systems. In another case, none of those bundles existed at all? Thoughts? Windows Server 2016 BTW. Sorry for the copius detail but I'm trying to be clear as to what I'm seeing. Scott
