mailto:chamik...@google.com>>
> Date: 6/6/18 2:09 PM (GMT-08:00)
> To: dev@beam.apache.org
> <mailto:dev@beam.apache.org>,
> u...@beam.apache.org
>
>>>>
>>>>> On Wed, Jun 6, 2018 at 8:29 PM Kenneth Knowles wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> Definitely a good opportunity to decouple your build tools from your
>>>>>> dependenci
tools.
>>>>>
>>>>> On Wed, Jun 6, 2018 at 2:42 PM Ted Yu wrote:
>>>>>
>>>>>> +1 on this effort
>>>>>>
>>>>>> Original message
>>>>>> From: Chamikara Jayalath
>>>
d tools.
>>>>
>>>> On Wed, Jun 6, 2018 at 2:42 PM Ted Yu wrote:
>>>>
>>>>> +1 on this effort
>>>>>
>>>>> ---- Original message
>>>>> From: Chamikara Jayalath
>>>>> Date: 6/6/18
this effort
>>>>
>>>> Original message ----
>>>> From: Chamikara Jayalath
>>>> Date: 6/6/18 2:09 PM (GMT-08:00)
>>>> To: dev@beam.apache.org, u...@beam.apache.org
>>>> Subject: Re: [DISCUSS] [BEAM-4126] Deleti
>>
>>> Original message
>>> From: Chamikara Jayalath
>>> Date: 6/6/18 2:09 PM (GMT-08:00)
>>> To: dev@beam.apache.org, u...@beam.apache.org
>>> Subject: Re: [DISCUSS] [BEAM-4126] Deleting Maven build files (pom.xml)
>>>
dev@beam.apache.org, u...@beam.apache.org
>> Subject: Re: [DISCUSS] [BEAM-4126] Deleting Maven build files (pom.xml)
>> grace period?
>>
>> +1 for the overall effort. As Pablo mentioned, we need some time to
>> migrate internal Dataflow build off of Maven build files. I cr
dev@beam.apache.org, u...@beam.apache.org
> Subject: Re: [DISCUSS] [BEAM-4126] Deleting Maven build files (pom.xml)
> grace period?
>
> +1 for the overall effort. As Pablo mentioned, we need some time to
> migrate internal Dataflow build off of Maven build files. I created
> h
+1 on this effort
Original message From: Chamikara Jayalath
Date: 6/6/18 2:09 PM (GMT-08:00) To:
dev@beam.apache.org, u...@beam.apache.org Subject: Re: [DISCUSS] [BEAM-4126]
Deleting Maven build files (pom.xml) grace period?
+1 for the overall effort. As Pablo mentioned, we
+1 for the overall effort. As Pablo mentioned, we need some time to migrate
internal Dataflow build off of Maven build files. I created
https://issues.apache.org/jira/browse/BEAM-4512 for this.
Thanks,
Cham
On Wed, Jun 6, 2018 at 1:30 PM Eugene Kirpichov
wrote:
> Is it possible for Dataflow to
Is it possible for Dataflow to just keep a copy of the pom.xmls and delete
it as soon as Dataflow is migrated?
Overall +1, I've been using Gradle without issues for a while and almost
forgot pom.xml's still existed.
On Wed, Jun 6, 2018, 1:13 PM Pablo Estrada wrote:
> I agree that we should dele
I agree that we should delete the pom.xml files soon, as they create a
burden for maintainers.
I'd like to be able to extend the grace period by a bit, to allow the
internal build systems at Google to move away from using the Beam poms.
We use these pom files to build Dataflow workers, and thus i
Note: Apache Beam will still provide pom.xml for each release it produces.
This is only about people using Maven to build Apache Beam themselves and
not relying on the released artifacts in Maven Central.
With the first release using Gradle as the build system is underway, I
wanted to start this t
13 matches
Mail list logo
