Skip to content
This repository has been archived by the owner on Mar 19, 2024. It is now read-only.

Build sample app successful #297

Merged
merged 7 commits into from
Jan 30, 2020
Merged

Build sample app successful #297

merged 7 commits into from
Jan 30, 2020

Conversation

hannesa2
Copy link
Contributor

@hannesa2 hannesa2 commented Jan 16, 2020

Now you can do a successful ./gradlew clean build

I did

  • update to Android Studio 3.5.3
  • fix lint issues
  • remove Log_OC
  • move Log.x() to Timber.x()
  • cleanup .gitignore
  • remove relicts

It will be referenced in the app via owncloud/android#2792

@hannesa2
Copy link
Contributor Author

hannesa2 commented Jan 16, 2020

This synk runs into an issue
image

You can remove this commit git revert a05e2dd9891e1 but the file is not needs (in my point of view).
And only keep this file because of synk ? I don't know. For me its only noise, but it's your decision

.gitignore Show resolved Hide resolved
@@ -3,4 +3,4 @@ distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-5.6.4-all.zip
distributionUrl=https\://services.gradle.org/distributions/gradle-6.0.1-all.zip
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a new Gradle version => 6.1

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I created this PR 5 days ago, there was no 6.1
What prevents me to have a 6.0.1 when this will be reviewed again ?

That's why I vote to approve and merge this, to go ahead.
And for sure I will create a follow up new PR with 6.1

Copy link
Contributor

@davigonz davigonz Jan 21, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, not really, 6.1 was released one day before this PR was created. https://gradle.org/releases/ , that's why I have suggested this change

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reality is always faster: there is a 6.1.1
But it's pointless to block this PR because of this

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

6.1.1 has been released after this PR creation while 6.1 was released before this PR creation, as I said in my comment above. That's why I suggested to use directly 6.1 instead of 6.0.1. I already applied the change yesterday (here and in owncloud/android#2792) and the PRs are ready to QA since then.

@davigonz
Copy link
Contributor

@hannesa2 just a couple of changes here

@hannesa2
Copy link
Contributor Author

This synk runs into an issue
image

You can remove this commit git revert a05e2dd9891e1 but the file is not needs (in my point of view).
And only keep this file because of synk ? I don't know. For me its only noise, but it's your decision

@davigonz With this message I've bigger doubts, instead of a more recent version Gradle

@davigonz
Copy link
Contributor

davigonz commented Jan 21, 2020

With this message I've bigger doubts, instead of a more recent version Gradle

@hannesa2 do not worry, we are aware of it

@DeepDiver1975 could you remove pom.xml file from snyk checks? Thanks

@jesmrec
Copy link
Collaborator

jesmrec commented Jan 29, 2020

No much to test here beyond the basic checks.

Approved.

@davigonz davigonz merged commit 015011b into master Jan 30, 2020
@delete-merged-branch delete-merged-branch bot deleted the BuildSampleApp branch January 30, 2020 13:40
@jesmrec jesmrec removed the Sprint label May 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants