If you can get us a stable and free of charge public Jenkins compute where we could setup and run automated JAX-RS build jobs, that would be great.
Otherwise I will continue using our Oracle internal infrastructure for these builds and there is no way you could help there unless you switch sides :)
Marek
> On 16 Aug 2016, at 12:15, Sergey Beryozkin <sberyozkin_at_talend.com> wrote:
>
> Hi Marek
>
> Sounds good, thanks, let me know please if you'd like me to help somehow
>
> Cheers, Sergey
> On 16/08/16 09:31, Marek Potociar wrote:
>> Hi Sergey,
>>
>> I understand your concern, I will try to spend some time on setting up automated release job sometime next week.
>>
>> Cheers,
>> Marek
>>
>>> On 15 Aug 2016, at 17:50, Sergey Beryozkin <sberyozkin_at_talend.com <mailto:sberyozkin_at_talend.com>> wrote:
>>>
>>> Hi Marek
>>>
>>> Yes, but it was a 2.1-SNAPSHOT in
>>> https://maven.java.net/content/repositories/snapshots/ <https://maven.java.net/content/repositories/snapshots/>
>>>
>>> (https://maven.java.net/#nexus-search;quick~javax.ws.rs <https://maven.java.net/#nexus-search;quick%7Ejavax.ws.rs>)
>>>
>>> CXF master-jaxrs21 branch depends on it, it helped, but we can not start merging master-jaxrs21 branch
>>> into CXF master until a non-SNAPSHOT API release is available. The concern is that if we do it
>>> then we can block the master release due to a SNAPSHOT dependency.
>>>
>>> We understand that if such a release were made then it would not represent the final API.
>>>
>>> Cheers, Sergey
>>>
>>>
>>>
>>>
>>> On 15/08/16 16:18, Marek Potociar wrote:
>>>> Hi Sergey,
>>>>
>>>> We did release some preliminary bits earlier based on your request, didn’t we? I would prefer waiting with more releases until we have some new content to justify the effort.
>>>>
>>>> Marek
>>>>
>>>>> On 15 Aug 2016, at 14:19, Sergey Beryozkin <sberyozkin_at_talend.com <mailto:sberyozkin_at_talend.com>> wrote:
>>>>>
>>>>> Hi Marek
>>>>>
>>>>> Seeing you replying in other threads makes me feel JAX-RS 2.1 has a very bright future :-)
>>>>>
>>>>> So what do you think about cutting out the current early draft release for it to make it to Central ?
>>>>> As I said, at this stage it would not be about meeting certain spec deadlines but rather supporting
>>>>> the implementation projects to do the early adoption and releases. Not only for CXF.
>>>>>
>>>>> By the way I should have a write access to a JAX-RS git repo. So if it can help I can do the release
>>>>> (I'd only need some guidance on how to reflect the early draft status in the artifact name, ex, 2.1-early-draft-m1, etc).
>>>>> Think about it please if it can work.
>>>>>
>>>>> Thanks, Sergey
>>>>>
>>>>> On 26/07/16 13:33, Sergey Beryozkin wrote:
>>>>>> Hi Marek, Santiago
>>>>>>
>>>>>> Hope you are doing well.
>>>>>>
>>>>>> We'd like in CXF to start merging our JAX-RS 2.1 branch to the main CXF 3.2.0-SNAPSHOT.
>>>>>>
>>>>>> My colleague had implemented SSE (server only so far) but it is a start and interesting, today, we've had a user
>>>>>> asking for this SSE code.
>>>>>>
>>>>>> For us to merge the branch code to the CXF master an early draft non-SNAPSHOT 2.1 API would need to be available
>>>>>> in Central. This is so that we can release CXF 3.2.0 eventually, knowing that we do not have SNAPSHOT deps.
>>>>>> It will also help us to go ahead and implement the NIO experiment and CompletableFuture client code directly on the master.
>>>>>>
>>>>>> Marek, can you please support it and do the very first API release ? (add some qualifier like early_draft, etc, to make it obvious that
>>>>>> it is far from being complete) ?
>>>>>>
>>>>>> a demand for JAX-RS is still very strong. If CXF manages to ship an early draft implementation, alongside with RI, it would be easier for
>>>>>> the community at large to continue working toward 2.1 being eventually completed. Depending on how things go I might consider submitting
>>>>>> a talk to JaveOne to raise the awareness of JAX-RS being implemented in ASF.
>>>>>>
>>>>>> Many thanks, Sergey
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>