https://pantsbuild.org/ logo
Powered by
#general
  • e

    enough-sundown-78166

    04/03/2017, 5:02 PM
    Hey y'all. Got a question on publishing artifacts (jars, specifically). Given package 
    foo
    that depends on package 
    bar
    , is there any way to publish a jar that includes both packages? It seems that pants requires both packages to have a 
    provides
    with a separate artifact id, which seems to indicate that it would publish them as separate jars
  • e

    enough-sundown-78166

    04/03/2017, 5:04 PM
    I'd like to have multiple packages just within the one jar. Should I be publishing a jvm_binary instead? How are the semantics different?
  • w

    witty-crayon-22786

    04/03/2017, 5:49 PM
    there is not, no
  • w

    witty-crayon-22786

    04/03/2017, 5:49 PM
    if you want a "fat" deploy jar, jvm_binary is one approach
  • w

    witty-crayon-22786

    04/03/2017, 5:50 PM
    but there isn't support for publishing merged packages.
  • w

    witty-crayon-22786

    04/03/2017, 5:50 PM
    why do you need them merged?
  • e

    enough-sundown-78166

    04/03/2017, 6:23 PM
    I guess I don't need them merged, it just seemed preferable since both packages are part of the same library. If I were using an older build system, I couldn't have the dependency without publishing both 
    foo
    and 
    bar
    . I just thought that perhaps pants had a different way.
  • e

    enough-sundown-78166

    04/03/2017, 6:25 PM
    Perhaps the way to go about this would be to just have a higher-level build file and treat the packages as sources instead of dependencies. In a sense, pants' opinion seems to be that the two packages are observed either as a single unit or separate, but not both
  • h

    high-advantage-47550

    04/03/2017, 6:55 PM
    is it possible to generate something like a 
    build.properties
    file and include it in resources? i have a 
    prep_command
    as a dependent of a 
    resources
    but it doesn’t seem to be making it in
  • h

    high-advantage-47550

    04/03/2017, 7:10 PM
    should that be working? (aka am I just doing something wrong somewhere? 😛 )
  • h

    high-advantage-47550

    04/03/2017, 7:36 PM
    i’m guessing 
    rglobs(’*’)
    is executed before the dependency runs..
  • w

    witty-crayon-22786

    04/03/2017, 7:39 PM
    prep_command doesn't capture its output, no.
  • w

    witty-crayon-22786

    04/03/2017, 7:39 PM
    there are previous threads about BuildPropertiesTask type extensions if you look in "All Threads"
  • h

    high-advantage-47550

    04/03/2017, 7:47 PM
    thanks! and oh, looks like i should use 
    bundle
    instead of just 
    binary
  • h

    high-advantage-47550

    04/03/2017, 7:51 PM
    scratch that
  • h

    high-advantage-47550

    04/03/2017, 8:12 PM
    wow i just wrote a working pants task plugin in like 15 minutes
  • h

    high-advantage-47550

    04/03/2017, 8:12 PM
    that was so easy — thanks pants team 😂
  • w

    witty-crayon-22786

    04/03/2017, 8:19 PM
    hah, nice.
  • h

    high-advantage-47550

    04/03/2017, 8:24 PM
    is it possible to say “this task should never be cached”? or is that the default?
  • w

    witty-crayon-22786

    04/03/2017, 8:24 PM
    that's the default for a task written from scratch, yea
  • h

    high-advantage-47550

    04/03/2017, 8:24 PM
    ah cool, just saw "Enabling Artifact Caching For Tasks"
  • w

    witty-crayon-22786

    04/03/2017, 8:24 PM
    if you extended some other base task, it might use caching
  • h

    high-advantage-47550

    04/03/2017, 8:25 PM
    ah — that’s why
  • w

    witty-crayon-22786

    04/03/2017, 8:26 PM
    can disable via options.
  • h

    high-advantage-47550

    04/03/2017, 8:26 PM
    presumably
    Copy code
    def cache_target_dirs(self):
        return False
    ?
  • w

    witty-crayon-22786

    04/03/2017, 8:30 PM
    that should work too, yea.
  • w

    witty-crayon-22786

    04/03/2017, 8:30 PM
    ... uh, depending on what you're extending.
  • w

    witty-crayon-22786

    04/03/2017, 8:31 PM
    if your base task uses the recommended/"automatic" caching, that will work: http://www.pantsbuild.org/dev_tasks.html#enabling-artifact-caching-for-tasks
  • h

    high-advantage-47550

    04/03/2017, 8:35 PM
    yeah, i’m extending 
    ResourcesTask
    — and registering with 
    task(name='generate-build-properties', action=PrepareBuildProperties).install(‘resources’)
  • h

    high-advantage-47550

    04/03/2017, 8:36 PM
    oh, hmm, does that override the existing 
    prepare_resources
    task?
1...168916901691...2420Latest