#436: feature request maven exclude dependency ------------------------------+----------------- Reporter: aruttenberg | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: (A)MOP | Version: Resolution: | Keywords: Parent Tickets: | ------------------------------+-----------------

Comment (by aruttenberg):

Here's a snippet that poc shows how one can do this at the direct dependent level. {{{ (let* ((node (#"getRoot" (#"collectDependencies" (ensure-repository- system) (ensure-session) collect-request)))) (let ((evil (find-if (lambda(e) (equal (#"getArtifactId" (#"getArtifact" e)) "org.protege.editor.owl")) (jss::j2list (#"getChildren" node))))) (#"remove" (#"getChildren" node) evil) (let ((dependency-request (jss:new 'DependencyRequest)) }}}

For deeper dependents I think you need to use pass a `DependencyFilter` in the constructor of the `DependencyRequest`. See `PatternExclusionsDependencyFilter` and `OrDependencyFilter`

For syntax I might suggest using the syntax that `PatternExclusionsDependencyFilter` uses, so it would be:

(:mvn "net.sourceforge.owlapi/owlapi-distribution/4.2.6" :exclude (":org.protege.editor.owl:" ..)) for my example case of exclusion by artifactID

The patterns apparently support version ranges.

The MVN URL Scheme doesn't seem to provide for exclusions. If you used them then they would be the form for both the dependency and the exclusions - you still need to specify the exclusions separately.

https://ops4j1.jira.com/wiki/display/paxurl/Mvn+Protocol

I vote for the pattern over the URL

-- Ticket URL: http://abcl.org/trac/ticket/436#comment:1 armedbear http://abcl.org armedbear

#436: feature request maven exclude dependency ------------------------------+---------------------- Reporter: aruttenberg | Owner: mevenson Type: enhancement | Status: accepted Priority: blocker | Milestone: Component: (A)MOP | Version: Resolution: | Keywords: Parent Tickets: | ------------------------------+---------------------- Changes (by mevenson):

* owner: => mevenson * status: new => accepted

Comment:

Not sure as to which syntax to specify exclusion.

{{{ (:mvn "net.sourceforge.owlapi/owlapi-distribution/4.2.6" :exclude (":org.protege.editor.owl:" ..)) }}}

What is syntax of the strings being passed to the `:exclude` clause here? Wouldn't it be simpler if they were regular mvn objects, i.e.

{{{ (:mvn "net.sourceforge.owlapi/owlapi-distribution/4.2.6" :exclude ((:mvn "group/artifact/version"))) }}}

-- Ticket URL: http://abcl.org/trac/ticket/436#comment:3 armedbear http://abcl.org armedbear

#436: feature request maven exclude dependency ------------------------------+---------------------- Reporter: aruttenberg | Owner: mevenson Type: enhancement | Status: accepted Priority: blocker | Milestone: Component: java | Version: Resolution: | Keywords: Parent Tickets: | ------------------------------+----------------------

Comment (by aruttenberg):

I think it should be as I wrote, a list of strings. The strings are groupid:artifactid:version as with the ones inside a (:mvn) component, but with any of the three components blank, meaning match anything.

Or, could take a lambda with args (groupid artifactid version why) of the dependency that might be loaded and if it returns nil it means skip it. The variable "why" is the path of dependencies that led to this one. The elements could be (:mvn blah) - that works here.

I just got bit by this again.

-- Ticket URL: http://abcl.org/trac/ticket/436#comment:5 armedbear http://abcl.org armedbear

#436: feature request maven exclude dependency ------------------------------+---------------------- Reporter: aruttenberg | Owner: mevenson Type: enhancement | Status: accepted Priority: blocker | Milestone: Component: java | Version: Resolution: | Keywords: Parent Tickets: | ------------------------------+----------------------

Comment (by mevenson):

ME: We should probably split into a subticket for the near term work of the current patch by Alan, but we document here the steps to longer term solution that involves re-using ASDF abstractions in a more concise way.

After conversation on asdf-devel, Faré has outlined a plan of attack around :before methods for the planning phase.

We need to code our generalization solution against https://gitlab.common- lisp.net/asdf/asdf/tree/plan

https://gitlab.common-lisp.net/mevenson/asdf/issues/1

-- Ticket URL: http://abcl.org/trac/ticket/436#comment:7 armedbear http://abcl.org armedbear

#436: feature request maven exclude dependency ------------------------------+-------------------------------------- Reporter: aruttenberg | Owner: mevenson Type: enhancement | Status: accepted Priority: blocker | Milestone: 1.6.0 Component: other | Version: 1.6.0-dev Resolution: | Keywords: aether abcl-asdf contrib Parent Tickets: | ------------------------------+-------------------------------------- Changes (by mevenson):

* keywords: => aether abcl-asdf contrib * version: => 1.6.0-dev * component: java => other * milestone: => 1.6.0

Comment:

Interim solution: abcl-1.5.0 ships with the ASDF:MVN-MODULE component which allows one to prune the subtree via exclusions exclusions.

TODO: "port" asdf-3.3, then push dependency resolution to its layer via suitable abstractions.

-- Ticket URL: http://abcl.org/trac/ticket/436#comment:9 armedbear http://abcl.org armedbear