profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/slipset/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Erik Assum slipset @ardoq Oslo, Norway

jonase/eastwood 1025

Clojure lint tool

borkdude/speculative 177

Unofficial community-driven specs for clojure.core

clj-commons/infra 2

Infrastructure for clj-commons

clj-commons/CLJ-2253 1

A workaround for https://dev.clojure.org/jira/browse/CLJ-2253

slipset/account-manager 0

a simple account manager based on a sencha tutorial. a work in progress

issue closedslipset/deps-deploy

Remove the need to specify jar file

Leverage the data read from the pom file to locate the Jar file. Current solution is a bit fragile as it requires specifying the same info (like version) twice.

closed time in a day

jeluard

issue closedslipset/deps-deploy

The short & medium term future of library packaging in the tools.deps ecosystem

Hi @slipset I started writing a slack message to you, but figured I should probably open a public issue to discuss it instead. This isn't so much a single issue though, it involves how we should organise and arrange a variety of libraries in the tools.deps tools eco system to better support packaging and deploying libraries (and applications).

In the microcosm the problems are motivated by where to put the code in my PR #21. My feeling is that it doesn't currently belong in deps-deploy because the pom should really be created prior to it being packaged in the jar in the first place.

My initial reaction was then to push it into depstar, however after speaking to @seancorfield he thought that would be complecting things, and that he's essentially of the opinion that tools.build will eventually better solve these problems, so he's not willing to invest much time fixing things in this area.

My view here is slightly different to sean's in that depstar is already complected, but along the wrong axis. i.e. it complects uberjarring (an application concern) with library making, and that most of the constraints about how depstar needs to be managed are to ensure no 3rd party deps are included on the classpath when uberjarring.

So I think there are a few ways to try and resolve this:

  1. Do the simple decomplected thing, and move my PR for updating the pom into a separate project. Users wishing to deploy libraries then need to complect (tie) the pom generation, library generation and deployment together themselves in their own code.
  2. Do the easy complected thing that I suspect most of the community would like, which is to complect library-making concerns together, in a way that is untangled from uberjarring. i.e. create a new "lib-maker" project that can update a pom, generate a library jar containing the appropriate assets, and deploy it to either clojars or a private s3 bucket.

My feeling is that it might be best to persue 1 first and either leave enough signposts for others or our future selves to fill in the gaps and implement 2. Hopefully by then tools.build will be done, but if it's not the community might have a better option than the current state of affairs.

Anyway I thought I'd write this up incase you or others have useful things to say on the matter.

Many thanks.

closed time in a day

RickMoynihan

issue commentslipset/deps-deploy

The short & medium term future of library packaging in the tools.deps ecosystem

Let's track this in discussion

RickMoynihan

comment created time in a day

issue closedslipset/deps-deploy

Track releases in GitHub

Would be great to have release tags in GitHub that correspond to release versions. I recently was tracking down the source of an error I was seeing, and the line numbers didn't match up w/ the latest unreleased code. I had to track down the git SHA of the latest release from Clojars and then switch to that. If the release had been in GitHub, I could have gone straight to that.

closed time in a day

cap10morgan

issue commentslipset/deps-deploy

Track releases in GitHub

I believe the latest version is tagged. Will continue doing so

cap10morgan

comment created time in a day

created tagslipset/deps-deploy

tagRelease-0.2.0

deploy your stuff

created time in a day

issue closedslipset/deps-deploy

Release new version w/ alias lookup support

I ran into the lack of b4359c5d67ca002d9ed0c4b41b710d7e5a82e3bf in the latest version released to Clojars. I switched to pulling in deps-deploy via git, but it would be great to have this in a released version. Thanks!

closed time in a day

cap10morgan

issue commentslipset/deps-deploy

Release new version w/ alias lookup support

There is now a 0.2.0 release

cap10morgan

comment created time in a day

pull request commentslipset/deps-deploy

[Fix #33] Don't ask for password when running headless

@kwladyka could I ask you to take this for a spin?

slipset

comment created time in a day

PR opened slipset/deps-deploy

[Fix #33] Don't ask for password when running headless

Also, don't supply password to gpg when no password is supplied

+6 -4

0 comment

1 changed file

pr created time in a day

push eventslipset/deps-deploy

Erik Assum

commit sha abc7a76b0263e6b70e056710aaa91ef3bc29a0fc

Remove reflection warnings

view details

push time in a day

push eventslipset/deps-deploy

Erik Assum

commit sha e0db587d29b1b23ebdbb3da65a56a1df6a905115

Add fn to sign with a specific key

view details

push time in a day

push eventslipset/deps-deploy

Erik Assum

commit sha dff94d0a7c1ce62e4e5899a0687201c01bd19db1

Update version

view details

push time in a day

push eventslipset/deps-deploy

Erik Assum

commit sha 3d20d0ee86c35c431e4fcf5b0830a3785e8116c0

Bump version

view details

push time in 2 days

push eventslipset/deps-deploy

Eugen Stan

commit sha db1efb9cd0d13c54330982535680516ad27ab71b

Convenience function to get repo by id from settings (#36)

view details

push time in 2 days

PR merged slipset/deps-deploy

Convenience function to get repo by id from settings
  • For use by deps-deploy/deploy
+17 -0

0 comment

2 changed files

ieugen

pr closed time in 2 days

PullRequestReviewEvent

issue closedslipset/deps-deploy

Prints out a `nil` if no username is set.

For deployments, if no username is set for the repository (especially for those that use role based authentication to AWS), the library prints out this:

Deploying foo.bar/worker-0.3.45 to repository releases as nil

If there is no username, it shouldn't print out a nil.

-=david=-

closed time in 2 days

dharrigan

push eventslipset/deps-deploy

David Harrigan

commit sha 49ebc481652be78883e603237bb7f780d2bde73e

[Fix #39] Refrain from printing out the username, if no username. (#40) Fixes #39 -=david=-

view details

push time in 2 days

delete branch slipset/deps-deploy

delete branch : 37-up-deps

delete time in 2 days

push eventslipset/deps-deploy

Erik Assum

commit sha 7406a23db5b52bb264fa7a05c63df545daa6e66c

[Fix #37] Upgrade dependencies (#38)

view details

push time in 2 days

issue closedslipset/deps-deploy

Dependencies are getting out of date

I noticed the recent Maven settings stuff brings in an old version of tools.deps.alpha so I ran antq on your repo and this is what it reported:

|    :file |                             :name |                                 :current |                                  :latest |
|----------+-----------------------------------+------------------------------------------+------------------------------------------|
| deps.edn |         com.cognitect/test-runner | 76568540e7f40268ad2b646110f237a60295fa3c | dd6da11611eeb87f08780a30ac8ea6012d4c05ce |
|          |   com.github.seancorfield/depstar |                                  2.0.211 |                                  2.1.297 |
|          |              org.clojure/data.xml |                             0.2.0-alpha5 |                             0.2.0-alpha6 |
|          |      org.clojure/tools.deps.alpha |                                  0.9.863 |                                0.12.1036 |
|          | s3-wagon-private/s3-wagon-private |                                    1.3.2 |                                    1.3.4 |
|  pom.xml |              org.clojure/data.xml |                             0.2.0-alpha5 |                             0.2.0-alpha6 |
|          |      org.clojure/tools.deps.alpha |                                  0.9.863 |                                0.12.1036 |
|          | s3-wagon-private/s3-wagon-private |                                    1.3.2 |                                    1.3.4 |

Available diffs:
  • https://github.com/cognitect-labs/test-runner/compare/76568540e7f40268ad2b646110f237a60295fa3c...dd6da11611eeb87f08780a30ac8ea6012d4c05ce
  • https://github.com/seancorfield/depstar/compare/v2.0.211...v2.1.297
  • https://github.com/clojure/data.xml/compare/data.xml-0.2.0-alpha5...data.xml-0.2.0-alpha6
  • https://github.com/clojure/tools.deps.alpha/compare/tools.deps.alpha-0.9.863...v0.12.1036
  • https://github.com/technomancy/s3-wagon-private/compare/v1.3.2...v1.3.4

closed time in 2 days

seancorfield

PR merged slipset/deps-deploy

[Fix #37] Upgrade dependencies
+57 -45

0 comment

2 changed files

slipset

pr closed time in 2 days

PR opened slipset/deps-deploy

[Fix #37] Upgrade dependencies
+57 -45

0 comment

2 changed files

pr created time in 2 days

create barnchslipset/deps-deploy

branch : 37-up-deps

created branch time in 2 days

issue commentseancorfield/depstar

depstar `2.1.297` doesn't seem to pick up jar-name from aliases:

Tested via git deps, and works.

Thanks for the super quick turn around!

slipset

comment created time in 4 days

issue commentseancorfield/depstar

depstar `2.1.297` doesn't seem to pick up jar-name from aliases:

Seems to break between 2.0.216 (which works) and 2.1.245 (which doesn't) No need to apologise, stranger things have gone worse

slipset

comment created time in 4 days

issue openedseancorfield/depstar

depstar `2.1.297` doesn't seem to pick up jar-name from aliases:

https://github.com/slipset/deps-deploy/blob/master/deps.edn#L29 works as expected with depstar version 2.0.211, ie it produces a jar file named deps-deploy.jar

When upgrading to depstar version 2.1.297, it produces a directory named :jar which contains file-name

✔ ~/Documents/github.com/deps-deploy [37-up-deps L|✚ 2]
08:27 $ ls -ltr
total 56
-rw-r--r--  1 erik  staff  11218 Mar 16  2020 LICENSE
drwxr-xr-x  3 erik  staff     96 Mar 16  2020 src
drwxr-xr-x  3 erik  staff     96 Mar 16  2020 test
-rw-r--r--  1 erik  staff    888 Oct 22  2020 CHANGELOG.md
-rw-r--r--  1 erik  staff   3439 Sep 15 07:56 README.md
drwxr-xr-x  3 erik  staff     96 Sep 15 07:56 doc
-rw-r--r--  1 erik  staff   2064 Sep 15 08:20 deps.edn
-rw-r--r--  1 erik  staff   2060 Sep 15 08:27 pom.xml
✔ ~/Documents/github.com/deps-deploy [37-up-deps L|✚ 2]
08:27 $ clj -X:depstar
:group-id should probably be a reverse domain name, not just slipset
Synchronizing pom.xml
Updating pom.xml file to {slipset/deps-deploy {:mvn/version "0.1.5"}}
Building thin jar: :jar/file-name
Processing pom.xml for {slipset/deps-deploy {:mvn/version "0.1.5"}}
✔ ~/Documents/github.com/deps-deploy [37-up-deps L|✚ 2…1]
08:27 $ ls -ltr
total 56
-rw-r--r--  1 erik  staff  11218 Mar 16  2020 LICENSE
drwxr-xr-x  3 erik  staff     96 Mar 16  2020 src
drwxr-xr-x  3 erik  staff     96 Mar 16  2020 test
-rw-r--r--  1 erik  staff    888 Oct 22  2020 CHANGELOG.md
-rw-r--r--  1 erik  staff   3439 Sep 15 07:56 README.md
drwxr-xr-x  3 erik  staff     96 Sep 15 07:56 doc
-rw-r--r--  1 erik  staff   2064 Sep 15 08:20 deps.edn
-rw-r--r--  1 erik  staff   2060 Sep 15 08:27 pom.xml
drwxr-xr-x  3 erik  staff     96 Sep 15 08:27 :jar
✔ ~/Documents/github.com/deps-deploy [37-up-deps L|✚ 2…1]
08:27 $ ls -l :jar
total 16
-rw-r--r--  1 erik  staff  7918 Sep 15 08:27 file-name
✔ ~/Documents/github.com/deps-deploy [37-up-deps L|✚ 2…1]
08:29 $ jar -tf ':jar/file-name'
META-INF/MANIFEST.MF
deps_deploy/
deps_deploy/deps_deploy.clj
deps_deploy/maven_settings.clj
deps_deploy/gpg.clj
META-INF/
META-INF/maven/
META-INF/maven/slipset/
META-INF/maven/slipset/deps-deploy/
META-INF/maven/slipset/deps-deploy/pom.properties
META-INF/maven/slipset/deps-deploy/pom.xml
✔ ~/Documents/github.com/deps-deploy [37-up-deps L|✚ 2…1]
08:29 $

created time in 4 days