Ron McLeod

Marshal
+ Follow
since Feb 12, 2013
Ron likes ...
Android Eclipse IDE TypeScript Redhat MicroProfile Quarkus Java Linux
Richmond, BC, Canada
Cows and Likes
Cows
Total received
512
In last 30 days
1
Total given
281
Likes
Total received
970
Received in last 30 days
2
Total given
1898
Given in last 30 days
7
Forums and Threads
Scavenger Hunt
expand Rancher Scavenger Hunt
expand Ranch Hand Scavenger Hunt Green check
expand Greenhorn Scavenger Hunt

Recent posts by Ron McLeod

Bob Matthews wrote:no "POM" required


Ok - which Derby jar are you using: derby-10.XXX.jar or derbyclient-10.XXX.jar?
Which dependency do you have in your POM: Derby Embedded or Derby Client?  You want the library for the embedded driver (and engine).

Bob Matthews wrote:
I am getting to 2 but not 3


We can't see what you are doing with exceptions.  Maybe getConnection() wasn't happy.   Are you catching and printing/logging them?
Is there a derby.log file in the working directory?  It may provide some clues.
Your database URL looks correct.

I just looked at an old project where I used embedded Derby, and these are the URLs that I used (first one in-memory for testing, second uses the file system):

Carey Brown wrote:I believe it's the database server that's responsible for knowing where a particular DB is kept. You should only need the DB name.


He is using the embedded driver (org.apache.derby.jdbc.EmbeddedDriver), so the path to the DB location needs to be specified.
I am trying to automate and simplify the process of building a service application and packaging it into a shippable form.

The application that I am building has a number of shared local dependencies:

The source code is checked-out in a flat structure:

Originally, the process was:
1. Build and install auth-interface
2. Build and install common
3. Build and install auth-common
4. Build auth-service
5. Create container image for auth-service
6. Transform container image to shippable form

I wanted to improve the process by:
- Eliminating the need to separately build dependencies
- Not storing dependencies in local Maven repository
- Having a single command to build and package container image

What I did:
- Created aggregation project with dependent projects as sub modules
- Created shell scripts for container image processing tasks
- Used maven-antrun-plugin to call the scripts (there may be a better plugin for this)

This works well, but I still have one issue - I want to tag the image and image file with the version in the auth-service project.
For example:
      image tag: auth-service:1.0.0
      shippable image file name: auth-service_1.0.0.gz

Currently, I am defining the image version in the builder POM adding a dependency for that specific version of auth-service, and then using that version property to tag the image.  If the version in the builder POM does not match the version in the auth-service POM, the build will fail, triggering me to manually update the version in the builder POM to match the version in the auth-service POM.

What I would really like is that the builder POM is not the authority for the auth-service version, but could discover/use the version defined in the auth-service POM.

3 days ago
Is there any way to reference the version property of a module POM from the parent POM?  Ideally something like: ${project.modules[0].version}
4 days ago
Their website states that they have two offices: one in New York, and the other in Ontario.

I don't know anything about the company, but I did notice that they are selling products on Amazon Canada - mostly scientific/industrial measurement equipment.
5 days ago
Actual code review takes only a few minutes; follow-on survey around 5 minutes.
5 days ago

Tim Holloway wrote:... Although porting the results to actual Docker on my CentOS 7 servers was a problem. Mainly because the Docker "export" format drops key metadata (not a problem specific to PodMan).


Out of interest, I did try move an image from Podman to Docker using podman save and docker load and it worked fine, but attempting to export a container from Podman and import into Docker failed.  I didn't bother to try and understand what the issue was since I won't be using Docker anyway; Podman + systemd fulfill my needs.
2 weeks ago

Tim Holloway wrote:... Although porting the results to actual Docker on my CentOS 7 servers was a problem. Mainly because the Docker "export" format drops key metadata (not a problem specific to PodMan).


Out of interest, I did try move an image from Podman to Docker using podman save and docker load and it worked fine, but attempting to export a container from Podman and import into Docker failed.  I didn't bother to try and understand what the issue was since I won't be using Docker anyway; Podman + systemd fulfill my needs.
2 weeks ago
I'm testing Rocky Linux (RHEL 8.4 equivalent) in a dev environment and all is well.  The distribution includes Podman 3.X - a daemonless replacement for Docker which supports rootless pods/containers, and has good integration with systemd.
2 weeks ago
When you say Vulnerability Scanner do you mean a penetration tester like Metasploit, or a static code analysis tool/plugin like SonarQube or FindBugs?
3 weeks ago