Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    workquestions123
    @workquestions123
    @nedtwigg I see above that specifying the workspace directory within the goomph configuration was talked about. Did this ever get implemented? I would like to set the workspace directory based on the name of the git branch that is currently checked out. This is because the goomph configuration follows the branch but the branches might be using completely different configuration. And to provide a quick way for developers to switch between development on different branches, it would be nice to have the ability to specify the workspace directory. If they are using the same workspace directory then switching between branches has the potential to lead to o clashing in various ways.
    Ned Twigg
    @nedtwigg
    Is this what you mean? diffplug/goomph#60
    workquestions123
    @workquestions123
    So goomph will create a workspace folder within ~/.goomph/ide-workspace. The folder is automatically generated (as is the name). What I would like to know is it possible to change the name of the created folder? Is it possible to change the location of that created folder?
    Which seems to be the link that you posted. But looks like it is still not submitted.
    workquestions123
    @workquestions123
    Another question somewhat related: Is there a way to create multiple workspaces with the same configuration?
    Ned Twigg
    @nedtwigg
    Ahh, you mean workspace for interactive IDEs. The unmerged PR is only for headless tasks.
    That's why their location is weird. If you wanted to fiddle with the workspace location, you'd need to modify this code: https://github.com/diffplug/goomph/blob/3085877407a7b54781119edbc767ee5753d72eb3/src/main/java/com/diffplug/gradle/oomph/OomphIdeExtension.java#L230-L232
    anatolVasin
    @anatolVasin
    Hey Guys!
    Have a small question about oomph ide plugin
    Is there any section for defining update site or it's better to do it within setting properties mechanim?
    Ned Twigg
    @nedtwigg
    yes, you can add an update site with repo 'http://myurl'
    anatolVasin
    @anatolVasin
    yea, it's ok, but this repo won't be added to Update Sites list
    in running ide
    Ned Twigg
    @nedtwigg
    ahh
    yeah, I don't know if it gets added there or not
    happy to take a PR to make it do what you want
    anatolVasin
    @anatolVasin
    :) will look how can i help
    anatolVasin
    @anatolVasin
    ufff, eclipse update sites works like a magic, seems like it's modifications available only via api...
    @nedtwigg is there any examples of using SetupAction?
    Rey
    @reyman
    Hi @nedtwigg , i'm refactoring a new plugin which also use p2asmaven option, but i have one question. Is it possible to filter jar downloaded ?
    p2AsMaven {
        group 'p2', {
            repo 'http://updates.gama-platform.org'
            iu 'msi.gama.headless'
        }
    }
    Download bunch of jar, but there are some jar i want to exclude, is it possible using p2 some magic API method ?
    Ned Twigg
    @nedtwigg
    There is some filtering magic available
    Ned Twigg
    @nedtwigg
    group 'p2', {
      slicingOption('followStrict', 'true')
    }
    The available options come from here: https://wiki.eclipse.org/Equinox/p2/Ant_Tasks#SlicingOptions
    Rey
    @reyman
    Hi @nedtwigg thanks for reply. I'm not sure this is exactly what i want (follow strict = true), do you think it's possible for example to remove juste certain package, like excluding "org.eclipse.osgi.*"
    i say that because i load all the downloaded jar by mavenasp2 as osgi bundle into other software, and such package (org.eclipse.osgi*) create some trouble.
    Rey
    @reyman
    (ps : we use your lib for openmole-plugin : https://github.com/openmole/gama-plugin)
    Ned Twigg
    @nedtwigg
    There are a bunch of slicing options (see link). Maybe try slicingOption('filter', 'org.eclipse.osgi,org.eclipse.osgi.*'). I'm not sure what the exact syntax is that filter expects, but I bet a little fiddling can figure it out
    Rey
    @reyman
    oh, ok, i misunderstand the filter option when i read the doc because there are no example ...
    thx
    Mateusz Fryc
    @mateuszef
    hi, I am trying to make sources generated by annotationProcessor visible in eclipse, but it seems that putting apply plugin: 'com.diffplug.eclipse.apt' into build.gradle is not enough
    Eclipse IDE displays information that: Plugin with id 'com.diffplug.eclipse.apt' not found.
    Mateusz Fryc
    @mateuszef
    adding version to the end helped, still it seems that eclipse doesn't see sources generated by annotation processor
    I had to add:
    compileJava {
        options.annotationProcessorGeneratedSourcesDirectory = file("${projectDir}/src/main/generated")
    }
    and
    sourceSets {
        main {
            java {
                srcDirs += "${projectDir}/src/main/generated"
            }
        }
    }
    shouldn't eclipse see, with this apt plugin activated, sources generated by annotation processor (located in build dir) by default ?
    Ned Twigg
    @nedtwigg
    Gradle uses the JDK to compile .java to .class
    But Eclipse has its own compiler, ECJ
    So Gradle runs tests and makes jars out of the artifacts in build/
    But eclipse doesn't - it uses bin/
    For annotation processor, there's a similar split
    For me, Gradle puts them in build/generated/sources/annotationProcessor/java/main/
    And eclipse puts them in .apt_generated
    Those are the defaults, I just apply the plugin, add my annotation processors with dependencies { annotationProcessor and that's it.
    One bug that I've heard of before, but never actually encountered myself
    is that there are some differences between ECJ and JDK
    which can break some annotations processors
    I've used a bunch of processors and never had this problem
    Ned Twigg
    @nedtwigg
    so I don't know if eclipse fixed it, or if I just never used one of the problematic annotation processors