pantsbuild #general

Channels

welcome

github-notifications

announce

ancient-stone-50795

10/18/2016, 2:28 PM

Ah, well, after adding debugging it started to work...

fast-megabyte-33579

10/18/2016, 2:44 PM

yay 🙂

ancient-stone-50795

10/18/2016, 3:09 PM

Well, it turns out it was not really working. The jars got uploaded to nexus and I was able to publish them, but the changes to

build-support/ivy/pushdb/org.pantsbuild/junit-runner-annotations/publish.properties

did not get made for all of the artifacts published. We have an artifact to depend on for now but the next publish may be broken.

ancient-stone-50795

10/18/2016, 3:11 PM

Well, they did get updated, the commit just looks funny because it includes some local debugging that I added:

Copy code

commit 755d8400703a5536cdf4d29645c6c383c901f97f
Author: Eric Ayers <zundel@squareup.com>
Date:   Tue Oct 18 07:27:34 2016 -0400

    debug file lock

Running

git diff 755d8400703a5536cdf4d29645c6c383c901f97f~1 755d8400703a5536cdf4d29645c6c383c901f97f

shows how those changes got merged in with my commit that I made to print out the pid in the error message I was getting.

thankful-library-32113

10/18/2016, 3:29 PM

if i'm building a resources() target, is there a way for me to change the path that the file in the build artifact lives in (e.g. strip off some parts of the path)

thankful-library-32113

10/18/2016, 3:30 PM

is the fact that i'm asking this question betraying some deeper misunderstanding of resources vs bundles

thankful-library-32113

10/18/2016, 3:31 PM

the reason i ask is that akka-http expects a

application.conf

at the root level of a jar on the classpath, but i can't figure out how to get pants to build such an artifact without completely screwing up my source tree

witty-crayon-22786

10/18/2016, 5:03 PM

@thankful-library-32113 : the path is relative to the source root for the resources target

witty-crayon-22786

10/18/2016, 5:03 PM

http://www.pantsbuild.org/setup_repo.html#source-roots

witty-crayon-22786

10/18/2016, 5:04 PM

so,

src/resources/this/is/the/path

src/main/resources/this/is/the/path

, by default

thankful-library-32113

10/18/2016, 5:04 PM

sure, but let's say i have multiple services each with a unique application.conf

witty-crayon-22786

10/18/2016, 5:04 PM

(nested under any other path)

thankful-library-32113

10/18/2016, 5:04 PM

and i want each of them to be like src/resources/servicea/application.conf

thankful-library-32113

10/18/2016, 5:04 PM

but i need that resulting conf to live at the root of the jar

thankful-library-32113

10/18/2016, 5:04 PM

in the resulting artifact

thankful-library-32113

10/18/2016, 5:05 PM

happy to try to solve this problem in a non-resources way if this is the wrong hammer to use

witty-crayon-22786

10/18/2016, 5:05 PM

i'll start by saying: it's a good idea to avoid collisions

witty-crayon-22786

10/18/2016, 5:05 PM

so namespacing them as

servicea/application.conf

is a good thing

witty-crayon-22786

10/18/2016, 5:05 PM

but failing that, just invert it:

witty-crayon-22786

10/18/2016, 5:05 PM

servicea/src/resources/application.conf

thankful-library-32113

10/18/2016, 5:06 PM

and have a series of folders like serviceA, serviceB, etc in my git root?

witty-crayon-22786

10/18/2016, 5:06 PM

yea.

thankful-library-32113

10/18/2016, 5:06 PM

😬

witty-crayon-22786

10/18/2016, 5:06 PM

the price you pay for skipping namespacing! 😃

witty-crayon-22786

10/18/2016, 5:07 PM

but i mean, alternatively:

config/servicea/src/resources

witty-crayon-22786

10/18/2016, 5:07 PM

twitter has project directories at the root

witty-crayon-22786

10/18/2016, 5:07 PM

useful for readmes, etc.

fast-megabyte-33579

10/18/2016, 5:07 PM

we have

resources/[service]/application.conf

fwiw

fast-megabyte-33579

10/18/2016, 5:08 PM

with the BUILD file next to the application.conf

witty-crayon-22786

10/18/2016, 5:08 PM

if a target isn't under a source root, its definition location becomes a source root