| It appears that when I simply execute > mvn install
then the attached custom.properties file is the result
I can simply overwrite this with an original version, but of course would prefer to fix the issue |
custom.properties
Description: Binary data
Any ideas of what is happening and how to prevent it? I’d like to avoid a time consuming ‘clean install’ every time I change a line of code
If I make a change to my code, shouldn’t I be able to build with > mvn install -DskipTests -nsu ?
Frank Sandoval
Principal - Pajarito Technologies LLC mobile: 720 338-1988
On Mar 13, 2017, at 9:42 AM, Robert Varga < n...@hq.sk> wrote:
On 03/13/2017 04:37 PM, Michael Vorburger wrote: You would need to find out what truncates etc/custom.properties like
that... Out of curiosity, I did try to start, check, Ctrl-D a Karaf I've
just built today (from netvirt/vpnservice/distribution/karaf), and
feature:install odl-netvirt-openstack into, and can't repro this.
(Obviously.. otherwise everything would be broken.)
It's possible there is some.. rogue (?) code somewhere in some feature
you install which is causing this... you should try to find some
reliable way to reproduce it, if you can at all.
Definitely rogue, custom.properties is logically owned by odlparent. It contains critical platform setup and we cannot have anyone (aside from operator, who knows what she's doing) mucking with it -- otherwise this sort of thing is bound to happen. Regards, Robert
|
_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev
