Skip to content

Conversation

@pmoerenhout
Copy link
Contributor

After maven-artifact-transfer 0.13.0 has been released, the PR will use the new functions from the maven-artifact-transfer to resolve the used repositories, and in verbose mode, also show the (local) location where this repository is defined.

<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-lang3</artifactId>
<version>3.6</version>
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this related to the functionality that you've implemented?

<dependency>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-http-lightweight</artifactId>
<version>3.3.4</version>
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this related to the functionality that you've implemented?

* Sets whether the plugin runs in verbose mode. As of plugin version 2.3, the default value is derived from Maven's
* global debug flag (compare command line switch <code>-X</code>). <br/>
*
* @since 3.1.2
Copy link
Contributor

Choose a reason for hiding this comment

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

The @since contradicts the first line of the Javadoc.


private boolean isVerbose()
{
return ( verbose || getLog().isDebugEnabled() );
Copy link
Contributor

Choose a reason for hiding this comment

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

It's a bit strange that isVerbose checks for log.isDebugEnabled(), while there is a verbose flag already which is triggered (according to its Javadoc) by the -X flag in the CLI.

this.getLog().info( repo.toString() );
String artifactKey =
ArtifactUtils.key( parent.getGroupId(), parent.getArtifactId(), parent.getVersion() );
MavenProject parentPom = getMavenProject( artifactKey );
Copy link
Contributor

@mthmulders mthmulders May 7, 2020

Choose a reason for hiding this comment

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

It seems to me as if you first concatenate groupId, artifactId and version into an artifactKey (line 326), only to pass it to getMavenProject(String) which then uses getArtifactCoordinate to disassemble then into their original values. Why is that?

@elharo elharo changed the title MDEP-648: Add location of listed repository. [MDEP-648] Add location of listed repository. Oct 31, 2022
@slawekjaranowski
Copy link
Member

@pmoerenhout thanks also for efforts on it ... we should not use maven-artifact-transfer at all
It should be reimplemented with using direct resolver API like I did in #301

So I close it now.

@jira-importer
Copy link

Resolve #1081

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants