Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

this is the embedded dependency in maven plugins #1803

Merged
merged 2 commits into from
Dec 9, 2016

Conversation

rotty3000
Copy link
Contributor

No description provided.

Signed-off-by: Christian Schneider <chris@die-schneider.net>
@@ -124,11 +124,6 @@
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>biz.aQute.bnd</groupId>
Copy link
Member

Choose a reason for hiding this comment

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

How is this delete related to adding the embedded repo to the plugns?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it's just cleanup from a previous change! Is that not ok?

Copy link
Member

Choose a reason for hiding this comment

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

OK, for some reason I thought #1794 removed the reference, but it was just in the project pom. So this is fine.

<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.10</version>
<configuration>
Copy link
Member

Choose a reason for hiding this comment

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

It is not clear to me that this configuration should be in the parent pom. It is shared by 2 of the plugins but if we need to use the dependency plugin in another plugin, that plugin may not need the embedded repo. This config should be in each project's pom.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ok..

@rotty3000 rotty3000 changed the title [maven] remove unused dependency this is the embedded dependency in maven plugins Dec 9, 2016
<version>${project.version}</version>
<type>jar</type>
<overWrite>false</overWrite>
<outputDirectory>${project.build.directory}/classes</outputDirectory>
Copy link
Member

@bjhargrave bjhargrave Dec 9, 2016

Choose a reason for hiding this comment

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

<outputDirectory>${project.build.outputDirectory}</outputDirectory>

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sorry, do you mean I should replace the entire string including /classes?

Copy link
Member

Choose a reason for hiding this comment

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

Yes. Using classes means failure if user uses a diff output folder.

<version>${project.version}</version>
<type>jar</type>
<overWrite>false</overWrite>
<outputDirectory>${project.build.directory}/classes</outputDirectory>
Copy link
Member

@bjhargrave bjhargrave Dec 9, 2016

Choose a reason for hiding this comment

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

<outputDirectory>${project.build.outputDirectory}</outputDirectory>

…s not present

The same issue exists with `bnd-testing-maven-plugin`

Signed-off-by: Raymond Auge <raymond.auge@liferay.com>
Copy link
Member

@bjhargrave bjhargrave left a comment

Choose a reason for hiding this comment

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

LGTM

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.

3 participants