Hi Juhan, Thanks for the help. The updates you made on the documentation are well detailed, that was really helpful.
Best Regards, Courage. On Wed, Jun 12, 2019 at 4:11 AM Michael Vorburger <[email protected]> wrote: > On Wed, Jun 12, 2019 at 9:40 AM Juhan Aasaru <[email protected]> wrote: > >> Michael, >> >> thanks for starting up a discussion on this. I think it is an important >> topic that deserves attention. >> The truly correct way would be creating versions and use them instead. >> So if one would now tag fineract-cn-lang with version 0.0.0.1 in github >> then travis would build a version and >> upload it to Artifactory under libs-release and it would be available >> forever (since it is a version and not a snapshot). >> >> Using the latest snapshot doesn't guarantee anything - any funcitonality >> might still break at any point of time >> causing a lot of confusion and lots of lost hours in debugging. >> >> Since we have an automatic system in place to release versions (all that >> needs to be done is to tag the same version in github web >> for each fineract-cn-* repository) I propose we just start creating >> 0.0.0.x versions whenever we think it is required. >> In my opinion we don't need to perform time consuming release and testing >> for these releases as their idea is just to produce common ground for >> everyone. >> And ideally we could automate the release creating procedure so it would >> just require a few clicks. >> >> Regarding snapshots - then you are correct - eventually the old snapshots >> will be removed from the Artifactory. >> To clarify my idea - if anyone has trouble fetching the latest snapshot >> using "generic" url >> then the workaround would be always to perform two steps in a row: >> 1) get the unique url of the latest version >> 2) pull snapshot from that url. >> And not hard code the unique url anywhere. >> >> I hope we get a good discussion on the topic of just starting to create >> releases / versions. >> > > I'm totally in support of you/someone else/anyone creating an automated > process to release 0.0.0.x versions to JFrog artifactory whenever we think > it is required for developers! > > >> Juhan >> >> >> >> >> >> Kontakt Michael Vorburger (<[email protected]>) kirjutas kuupäeval K, >> 12. juuni 2019 kell 09:51: >> >>> Hello, >>> >>> On Wed, Jun 12, 2019 at 8:16 AM Juhan Aasaru <[email protected]> wrote: >>> >>>> Hi Courage, >>>> >>>> I checked, the artifact is there in the repository. But trying to get >>>> latest artifact just by generic url like: >>>> >>>> http://mifos.jfrog.io/mifos/libs-snapshot/org/apache/fineract/cn/lang/0.1.0-BUILD-SNAPSHOT/lang-0.1.0-BUILD-SNAPSHOT.jar >>>> can be unrelyiable as some old version could have been cached on the >>>> way. >>>> >>> >>> may I respectfully disagree with this? I would argue the opposite, and >>> suggest that it's better to use the "generic" URLs (those with the >>> -SNAPSHOT, without that timestamp). >>> >>> For me an e.g. "wget >>> http://mifos.jfrog.io/mifos/libs-snapshot/org/apache/fineract/cn/lang/0.1.0-BUILD-SNAPSHOT/lang-0.1.0-BUILD-SNAPSHOT.jar"; >>> seems to work just fine, so what's actually the issue? >>> >>> >>>> The best way would be to determine the unique filename of the latest >>>> version and then use that instead. >>>> You can find the unique filename of the latest artifact like this: >>>> >>>> https://mifos.jfrog.io/mifos/api/search/latestVersion?g=org.apache.fineract.cn&a=lang&v=0.1.0-BUILD-SNAPSHOT&repos=libs-snapshot-local >>>> currently returns "0.1.0-BUILD-20190607.052703-26" >>>> and then pull it like this (added "lang-" and ".jar" to the url): >>>> >>>> https://mifos.jfrog.io/mifos/libs-snapshot/org/apache/fineract/cn/lang/0.1.0-BUILD-SNAPSHOT/lang-0.1.0-BUILD-20190607.052703-26.jar >>>> >>> >>> For a one time manual use it's OK to use a URL like this. You wrote "I >>> am just want to manually download the artefact and run the jar file" so >>> it's probably all good. >>> >>> More for general background: If one were to hard code this into say some >>> script, you risk that it breaks soon. The reason is that Maven repository >>> manager software such as JFrog or Sonatype Nexus (same functionality) will >>> keep only a handful (configurable) number of timestamps for any given >>> SNAPSHOT version. So as new 0.1.0-BUILD-SNAPSHOT versions are deployed in >>> the future, the 20190607.052703-26 could well very get automatically >>> cleaned up and disappear again. >>> >>> I updated the documentation with troubleshooting section where I >>>> described the steps in more detail: >>>> >>>> https://cwiki.apache.org/confluence/display/FINERACT/Fineract-CN+Artifactory#Fineract-CNArtifactory-Troubleshooting >>>> >>>> I hope that helps. >>>> >>> >>> Very nice write up, thank you!! >>> >>> >>>> Kind regards >>>> Juhan >>>> >>>> >>>> Kontakt Courage Angeh (<[email protected]>) kirjutas kuupäeval T, >>>> 11. juuni 2019 kell 22:24: >>>> >>>>> Hi Cajetan, >>>>> >>>>> Thanks for the suggestion. But I am not running any fineract-cn >>>>> service so my question is not related to the .m2 directory. >>>>> >>>>> I am just want to manually download the artefact and run the jar file >>>>> so that I can generate some RSA keys for a deployment environment. >>>>> >>>>> Regards, >>>>> Courage. >>>>> >>>>> >>>>> On Tue, Jun 11, 2019 at 3:02 PM Cajetan Rodrigues < >>>>> [email protected]> wrote: >>>>> >>>>>> Also note that the .me repo is found in the users/<username> in C >>>>>> drive folder. >>>>>> >>>>>> M2 folder contains all your dependencies. >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Jun 12, 2019, 12:26 AM Cajetan Rodrigues < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> I have fallen into such issues before. >>>>>>> So if you are on windows, a folder known as *.m2* is auto-created. >>>>>>> Just delete that and restart STS (or other S/W). >>>>>>> It will take a long time, downloading the repositories, but it >>>>>>> should then work fine. >>>>>>> >>>>>>> Regards, >>>>>>> Cajetan Rodrigues. >>>>>>> >>>>>>> On Wed, 12 Jun 2019 at 00:16, Courage Angeh <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Juhan, >>>>>>>> >>>>>>>> Hope this email finds you well. >>>>>>>> >>>>>>>> I merged the recent changes you made to fineract-cn-lang but when I >>>>>>>> visit the online artefact, I see that the artefact was modified was >>>>>>>> 09-Apr-2019. >>>>>>>> >>>>>>>> Based on this documentation: >>>>>>>> https://cwiki.apache.org/confluence/display/FINERACT/Fineract-CN+Artifactory >>>>>>>> I presume that when a PR is merged, I should be able to get the >>>>>>>> updates via 0.1.0-BUILD-SNAPSHOT >>>>>>>> <https://mifos.jfrog.io/mifos/libs-snapshot/org/apache/fineract/cn/lang/0.1.0-BUILD-SNAPSHOT/>. >>>>>>>> However, when I visit the artifactory, it shows that the artefact was >>>>>>>> last >>>>>>>> updated on the 9th of April 2019. >>>>>>>> >>>>>>> >>> I can see a version which was deployed on 07-Jun-2019 05:27. >>> >>> >>>> Please, can you help me out? >>>>>>>> >>>>>>>> Regards, >>>>>>>> Courage. >>>>>>>> >>>>>>>
