| Re: [orbit-dev] Create CQs for new Orbit bundles |
Hi,
Ok I got that but what I don't get is why are you not simply moving
those 2 into your buildship project at Eclipse.org and publish them as
part of the your p2 repository.
This would also free the IP-Team to always review the stuff you want to
bring into orbit.
Tom
On 28.08.15 09:09, Donát Csikós wrote:
> I agree with you, becoming a committer would be a better option. Also,
> since the bundles we are talking about are developed by Gradle Inc, we'd
> be the best candidates to maintain. Consequently, I'd like to express my
> interest in becoming a committer on the Orbit project.
>
> To be more precise, there are two projects we'd like to contribute:
> - Gradle Tooling API: a library to interact with Gradle builds
> (https://docs.gradle.org/current/userguide/embedding.html).
> - Gradle Tooling Commons: abstraction layer over Tooling API. It hides
> the difference between different Gradle releases. It also provides an
> API to cache information describing Gradle builds and load/retrieve them
> in a concurrent manner (https://github.com/gradle/tooling-commons).
>
> Having said that, these libraries are very useful if somebody wants to
> implement an Eclipse plug-in or an RCP application which interacts with
> Gradle.
>
>
>
>
> 2015-08-27 21:56 GMT+02:00 Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx
> <mailto:tom.schindl@xxxxxxxxxxxxxxx>>:
>
> Ok then
> A) you need to be voted in as a orbit committer and you file the cq
> B) you need to convince a current committer to bring it there and
> file the cq
>
> A) is certainly the better way for the future
>
> Pushing something to orbit only makes sense if others are likely to
> reuse it.
>
> Tom
>
> Von meinem iPhone gesendet
>
> Am 27.08.2015 um 21:11 schrieb Donát Csikós <csdonat@xxxxxxxxx
> <mailto:csdonat@xxxxxxxxx>>:
>
>> No, the bundles are not in orbit yet.
>> To give you one example, the Gradle Tooling API is the one we'd
>> like to move there. The corresponding CQ is already approved:
>> https://dev.eclipse.org/ipzilla/show_bug.cgi?id=10008. Now I don't
>> know how - to quote the documentation - to raise a "piggy-back"
>> (PB) CQ for the Orbit project to re-use the library.
>>
>>
>>
>> 2015-08-27 20:41 GMT+02:00 Tom Schindl
>> <tom.schindl@xxxxxxxxxxxxxxx <mailto:tom.schindl@xxxxxxxxxxxxxxx>>:
>>
>> Just to understand: the bundles are in orbit? Then the piggy
>> back cqs are filed against the buildship project not against
>> orbit.
>>
>> Tom
>>
>> Von meinem iPhone gesendet
>>
>> Am 27.08.2015 um 18:20 schrieb Donát Csikós <csdonat@xxxxxxxxx
>> <mailto:csdonat@xxxxxxxxx>>:
>>
>>> Dear Orbit Developers,
>>>
>>> The Buildship project will participate in the Mars.1 update
>>> release. As part of the process we were asked to consume all
>>> of our dependencies from Orbit.
>>>
>>> The site
>>> https://wiki.eclipse.org/Adding_Bundles_to_Orbit#Before_You_Do_Anything
>>> states that we should create piggyback CQs assigned to the
>>> tools.orbit project which I am unable to do.
>>>
>>> When I try to create a CQ at https://dev.eclipse.org/ipzilla
>>> it redirects me to portal.eclipse.org
>>> <http://portal.eclipse.org> which seems disfunctional. On
>>> https://projects.eclipse.org/ I can create CQs but only for
>>> the Buildship project. Neither does it help because after a
>>> CQ is created I can't change the associated project.
>>>
>>> Can somebody help me on where and how to do this properly?
>>>
>>>
>>> Best regards,
>>>
>>>
>>> Donát Csikós
>>> Gradle Inc.
>>> _______________________________________________
>>> orbit-dev mailing list
>>> orbit-dev@xxxxxxxxxxx <mailto:orbit-dev@xxxxxxxxxxx>
>>> To change your delivery options, retrieve your password, or
>>> unsubscribe from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/orbit-dev
>>
>> _______________________________________________
>> orbit-dev mailing list
>> orbit-dev@xxxxxxxxxxx <mailto:orbit-dev@xxxxxxxxxxx>
>> To change your delivery options, retrieve your password, or
>> unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/orbit-dev
>>
>>
>> _______________________________________________
>> orbit-dev mailing list
>> orbit-dev@xxxxxxxxxxx <mailto:orbit-dev@xxxxxxxxxxx>
>> To change your delivery options, retrieve your password, or
>> unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/orbit-dev
>
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx <mailto:orbit-dev@xxxxxxxxxxx>
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/orbit-dev
>
>
>
>
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/orbit-dev
>
--
Thomas Schindl, CTO
BestSolution.at EDV Systemhaus GmbH
Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck
http://www.bestsolution.at/
Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/orbit-dev