Rejecting for now.
Please create a new request once the information/planning is ready.
Thanks!
Jess
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
On Mon Apr 30 18:33:09 2018, frank.obr...@amdocs.com wrote:
> I was ok with moving code between the repos
>
> Sounds good, Having a hard time with the mixed python and java code
> from the single root pom.xml that is picked up by Jenkins jobs - It
> may not have been a good idea to mix the 2 techn
I was ok with moving code between the repos
Sounds good, Having a hard time with the mixed python and java code from the
single root pom.xml that is picked up by Jenkins jobs - It may not have been a
good idea to mix the 2 technologies in a single repo.
I'll work through the issues as I try to g
I was ok with moving code between the repos
Sounds good, Having a hard time with the mixed python and java code from the
single root pom.xml that is picked up by Jenkins jobs - It may not have been a
good idea to mix the 2 technologies in a single repo.
I'll work through the issues as I try to g
Hi Michael,
Currently for logging there is 1 repo labelled "logging-analytics". This repo
can't be renamed.
LF will need to create 2 new repo
> Logging-analytics/java
> Logging-analytics/python
And you will need to move the code appropriately, then LF will need to lock the
" logging-analytics"
Hi Michael,
Currently for logging there is 1 repo labelled "logging-analytics". This repo
can't be renamed.
LF will need to create 2 new repo
> Logging-analytics/java
> Logging-analytics/python
And you will need to move the code appropriately, then LF will need to lock the
" logging-analytics"
Yes, both issues are ok
We can have just 2 top level repos - like you propose
The history can be deleted if this makes it easier - if you can preserve it -
preserve it on the repo where all the existing code will go - the java one.
You can put everything on one side for now - as the python folder
Yes, both issues are ok
We can have just 2 top level repos - like you propose
The history can be deleted if this makes it easier - if you can preserve it -
preserve it on the repo where all the existing code will go - the java one.
You can put everything on one side for now - as the python folder
On Sun Apr 29 19:28:26 2018, frank.obr...@amdocs.com wrote:
> LF, Gildas,
>We would like to split the current logging-analytics repo into
> python and java. Currently the shared repo root pom.xml is causing
> issues running both technologies both offline and with jobs running on
> jenkins.
>
