From: | Kartik Ohri <kartikohri13(at)gmail(dot)com> |
---|---|
To: | Chapman Flack <chap(at)anastigmatix(dot)net> |
Cc: | pljava-dev(at)lists(dot)postgresql(dot)org |
Subject: | Re: PL/Java new build plugin |
Date: | 2020-07-09 18:52:08 |
Message-ID: | CAASLQ4PU1gKHvHfDHnaipLsJ+-YUexkkrOUwTTtUX5v_QgZFCw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pljava-dev |
>
> Meanwhile, I tried to eliminate the properties file and encountered the
> include path not found issue in nar-maven plugin. It took some time to find
> the issue but I was able to find the issue. It was that the pg_config
> appended a newline character to its output which was being added to the
> property value causing a path error. I have fixed it now and eliminated the
> need of the pgxs.properties file.
>
While debugging this issue, I took a look at properties-maven-plugin and
found that it writes the properties to the project instead of session. So,
I am writing the properties to project as well instead of the session.
Also, I read about the difference between getUserProperties provided by the
session and the getProperties provided by the session. I grasped that
getUserProperties is used for the properties the user passes to the maven
command using -D. It is possible to obtain project properties using a
session but directly using a project is more straightforward. The current
implementation using project properties compiles and works for me.
From | Date | Subject | |
---|---|---|---|
Next Message | Chapman Flack | 2020-07-09 20:08:06 | Re: PL/Java new build plugin |
Previous Message | Kartik Ohri | 2020-07-09 18:45:13 | Re: PL/Java new build plugin |