search

IgnoredAmbience / DoCitten

DoCitten: The Cutest IRC bot ever [citation needed]
Other
0 stars 0 forks source link

Maven: package target errors #6

Open javajawa opened 8 years ago

javajawa commented 8 years ago

When running mvn package from either edgemaster/DoCitten@23bc4db using edgemaster/InternetRelayCats@d6577c3, I receive the following error:

[ERROR] Failed to execute goal on project internetrelaycats:
Could not resolve dependencies for project uk.co.harcourtprogramming:internetrelaycats:jar:1.0-SNAPSHOT:
Could not find artifact uk.co.harcourtprogramming:mewler:jar:tests:1.0-SNAPSHOT

(line breaks added for readability).

The issue is not present for mvn compile or mvn test.

Debug log from mvn -e -X package: maven-output.txt

IgnoredAmbience commented 8 years ago

Yeah, I stopped once I got test and coveralls working. Packaging is the next job. On 11 May 2016 09:52, "Benedict Harcourt" notifications@github.com wrote:

When running mvn package from either edgemaster/DoCitten@23bc4db https://github.com/edgemaster/DoCitten/commit/23bc4db using edgemaster/InternetRelayCats@d6577c3 https://github.com/edgemaster/InternetRelayCats/commit/d6577c3, I receive the following error:

[ERROR] Failed to execute goal on project internetrelaycats: Could not resolve dependencies for project uk.co.harcourtprogramming:internetrelaycats:jar:1.0-SNAPSHOT: Could not find artifact uk.co.harcourtprogramming:mewler:jar:tests:1.0-SNAPSHOT

(line breaks added for readability).

The issue is not present for mvn compile or mvn test.

Debug log from mvn -e -X package: maven-output.txt https://github.com/edgemaster/DoCitten/files/258905/maven-output.txt

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/edgemaster/DoCitten/issues/6

javajawa commented 8 years ago

Oh, ok -- it looked to me like it should have worked, but there again my maven experience is pretty much non-existent.

IgnoredAmbience commented 8 years ago

I'm doing some less-than-standard stuff with it, the general structure of multi-package maven projects is not through submodule inclusion, but multiple separate projects that are release-version controlled and packaged into a repository for use by dependent projects. DoCitten doesn't fit that too well at the moment, so I was working around it.

On 11 May 2016 at 15:24, Benedict Harcourt notifications@github.com wrote:

Oh, ok -- it looked to me like it should have worked, but there again my maven experience is pretty much non-existant.

— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/edgemaster/DoCitten/issues/6#issuecomment-218475373