-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implementing possibility for reprojection Coordinates #1044
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @flomickl
just had a quick look on your PR. Could you please specify/describe to which issue this PR relates to?
It doesn't have to belong to one but I think the issue you mentioned in the title is not realy related to the changes in your PR or am I wrong?
More than that, I am bit curious why you have this empty SQL scripts in the PR. Will they be filled in an upcoming PR?
Lastly, you indicated in the PR description that this PR indtroduces deprecations but I couldn't find any @deprecation
annotation somewhere. Could you please add them together with a short discpription in the PR/issue?
That would be awesome.
Thanks a lot already
@bossenti The empty SQL Scripts are correct. This is for a clean startup in the corresponding docker-compose file. This way the processor does not run in any time out, which takes longer anyway from the user perspective. Instead, there is a check in the onInvocation method if the database is set up with data. If not, an SpRuntime Exception is thrown. There are some follow-up tickets related to this issue: Mainly the processor does some coordinate reprojection so transform some WGS84 coordinates (lat long) to an UTM projection. |
i don't understand the validate-pr / run-rat-plugin check and why it failed?
|
@flomickl thanks a lot for your explanation 🙏🏼 With regard to the failing build: Maven complains here that it found four files without an Apache header. tldr; these are the four SQL files |
@bossenti What to do with this kind of files? In
EPSG_FINISH.sql is Apache conform and therefore the following could be added:
What do you think? |
The suggested header looks fine to me
@flomickl I don't really get why we cannot add our header here? 🙈 These are just empty files, right? |
@bossenti Hm if you mention it. Nothing prevent it to include the license text to an empty script that reference to another file. |
@bossenti added and style check complete. Anything else to do before merge? |
@flomickl that's great It would be great if you could rebase your branch once but then I think you are ready to go |
rebase done :) |
@flomickl there seems to be something wrong... |
oh man, why? what to do now? @bossenti |
@flomickl it's hard to tell from the sidelines, so I took a quick look locally |
@@ -63,7 +63,17 @@ | |||
<dependency> | |||
<groupId>org.locationtech.jts</groupId> | |||
<artifactId>jts-core</artifactId> | |||
<version>1.16.1</version> | |||
<version>1.19.0</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @flomickl can you please add the dependencies to the tag in the parent pom.
Then you don't need the version number in this pom.
In the parent pom you can also create a variable like it is done for other dependencies.
If you have any questions, just let me know.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tenthe You mean here?
https://github.com/apache/streampipes/blob/dev/pom.xml ?
What is the difference between these two pom files?
The change should look something like:
...
<jts.version>1.19.0</jts.version>
...
<dependency>
<groupId>org.locationtech.jts<</groupId>
<artifactId>jts-core</artifactId>
<version>${jts.version}</version>
</dependency>
Should I do it for these entries?
- jts
- postgresql -> pretty sure that this entry already exist sin the parent pom
- sis
- com.squareup.okhttp
I did not add
<dependency>
<groupId>com.squareup.okhttp3</groupId>
<artifactId>okhttp</artifactId>
<version>3.13.1</version>
</dependency>
The entry in the geo.jvm pom should also be changed to following entry?
<dependency>
<groupId>org.locationtech.jts<</groupId>
<artifactId>jts-core</artifactId>
<version>${jts.version}</version>
</dependency>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @flomickl,
the parent pom ensures that we use the same version of a dependency within the whole project.
Therefore, the dependency must be added to the <dependencyManagement>
tag with the version in the parent pom.xml.
To use this dependency you can add it the to the pom.xml in the module that requires the dependency to the <dependencies>
tag. The version should only be defined in the parent pom.xml and not in the module pom.xml.
The only exception are the StreamPipes dependencies.
Does this help?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tenthe I updated the pom files.
I also run manual tests again. Everything as expected.
I left this inside, but sure that this could be removed in another ticket. The version is also outdated in both pom files.
<dependency>
<groupId>com.squareup.okhttp3</groupId>
<artifactId>okhttp</artifactId>
<version>3.13.1</version>
</dependency>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The parent pom would also need new code format process in an extra commit!
Did not want to add this here as well
@flomickl I just gave it another rebase to keep up with recent changes 🙂 |
@bossenti btw I found out what happened. Somehow, the rebase command was setup with the --onto flag in my git configs |
@dominikriemer can you check the code as well please? O:-) |
@bossenti there was a conflict in the pom file, so I fixed it here on the web IDE. Is it correct that the dev branch should be merged here? Is this a default behavior of GitHub and the web IDE or should it be a rebased? I didn't want to make it as complicated as last time.... |
@flomickl I don't think we have a preference for rebasing or merge commits in this project |
Purpose
Implement #797
Remarks
I created some follow-up tickets like #1041 #1042 and #1043 to split this big change into separate tasks.
Last time it took so long that the issue was too old to be merged.
PR introduces (a) deprecation(s): no
Implemented the Apache SIS maven package.