|
|
| Re: Gradle integation? [message #1714355 is a reply to message #1714350] |
Thu, 12 November 2015 02:08   |
Eclipse User |
|
|
|
If I understand your end goal, I think there are two routes to accomplish it.
1) Oomph master - the user runs Oomph, it checks out their code, and creates their projects (in which case you need GradleImportTask)
2) Gradle master - the user runs Gradle, it uses Oomph to provision a workspace and create their projects (in which case you still need something like GradleImportTask, but now you've got Gradle's scripting language to build a quick shortcut in the meantime).
In the same way that documentation and code-quality warnings are a build artifact, I think a working IDE should be a build artifact, and Oomph gives us the power to do that. The other nice thing about Gradle master is that it's a viral mechanism for the Eclipse ecosystem. If your project happens to be open source, your contributors could use whatever IDE they wanted, but Eclipse would be very easy to get started with.
For the immediate future, there's no way to do Gradle master fully (but I'm working on it here, so you can watch and/or contribute if you'd like. I'm knowledgeable about Gradle plugins and the various OSGi/P2 workarounds people are using in Gradle right now, but I'm a total noob w.r.t. Oomph. I'm hoping to find a collaborator who is knowledgeable about Oomph and wants to have a hack day to get Goomph started. Drop me a line if you're interested 
|
|
|
| Re: Gradle integation? [message #1714569 is a reply to message #1714350] |
Fri, 13 November 2015 10:40 |
| Eclipse User |
|
|
|
Hi Axel,
i had the same problem: you can try my import task at
https://github.com/herkne/buildship-import-4-oomph - its in a "works
for me" state and maybe still has some bugs.
Best regards,
Hermann
> Hi Axel,
>
> No, we don't ship a GradleImportTask, yet. Ned Twigg asked
> Gradle-related questions on our dev mailing list
> (https://dev.eclipse.org/mhonarc/lists/oomph-dev/msg00064.html ). I
> think he was actually asking for advice to implement the opposite
> direction, i.e., use Oomph's resolver and bundle pool in Gradle. But
> he's essentially building up Oomph+Gradle knowledge. So I'm going to
> ask him to join this discussion and share his thoughts...
>
> Cheers
> /Eike
>
> ----
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>
>
> Am 11.11.2015 um 20:53 schrieb Axel von Engel:
>> Hello everyone :)
>>
>> I just recently discovered Oomph and tried to setup a project model for
>> a project which consists of <10 gradle projects hosted on an enterprise
>> github server.
>> I figured out how to install the eclipse gradle integration plugin I
>> want (buildship) using the P2 director task. Since we did not check the
>> .project & .classpath files into our git repository, I would now have
>> to run the Gradle import wizard via Oomph.
>>
>> Is this possible, yet? I did not see any such task in the project model
>> editor and also could not find anything related on the net.
>>
>> Cheers
>> Axel
|
|
|
| Re: Gradle integation? [message #1714719 is a reply to message #1714569] |
Mon, 16 November 2015 03:34 |
| Eclipse User |
|
|
|
Hey everyone,
thanks for your replies. While I agree to some degree with Ned that a fully setup IDE should be a build artifact, I have a different way to accomplish this in mind: create virtual machines for developers to use. I took a look at Vagrant and found that while it's possible to provision a VM with almost everything, one of the difficult things is Eclipse.
Anyway - I'll take a closer look at both your projects in the coming days and may even pitch in a commit or two. Since this is one of my pet-projects on the job, I can't put in too much time, though :/
Regards
Axel
|
|
|
Powered by
FUDForum. Page generated in 0.04015 seconds
Home