Re: [Google Dataflow SDK] Build fails

[Kenneth Knowles]

Yup, I'm checking it out. I have not reproduced it yet.

On Mon, Mar 7, 2016 at 9:16 AM, Davor Bonaci  wrote:

> Minudika's issue is the following:
>
> [WARNING] Unused declared dependencies found:
> [...]
> [ERROR] Failed to execute
> goal org.apache.maven.plugins:maven-dependency-plugin:2.8:analyze-only
> (default) on project google-cloud-dataflow-java-sdk-all: Dependency
> problems found.
>
> It is possibly a real code issue. +Kenn, can you take a peek?
>
> On Mon, Mar 7, 2016 at 6:06 AM, Jean-Baptiste Onofré 
> wrote:
>
>> It could be related to the mistake in your .m2/settings.xml as it looks
>> like a  tag is missing.
>>
>> Can you check there ?
>>
>> Regards
>> JB
>>
>>
>> On 03/07/2016 02:57 PM, Minudika Malshan wrote:
>>
>>> Hi JB,
>>>
>>> Thanks a lot for your reply.
>>> I'm using maven 3.3.9.
>>>
>>> I tried to build apache-beam too. It also gives the same error.
>>>
>>> *[ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-dependency-plugin:2.8:analyze-only
>>> (default)
>>> on project google-cloud-dataflow-java-sdk-all: Dependency problems found
>>> ->
>>> [Help 1]*
>>>
>>> Perhaps it's because of something wrong with my internet connection.
>>> I will check with another connection.
>>>
>>> Please let me know if you have got anything. :)
>>>
>>> Best regards,
>>> Minudika
>>>
>>>
>>> Minudika Malshan
>>> Undergraduate
>>> Department of Computer Science and Engineering
>>> University of Moratuwa.
>>>
>>>
>>>
>>>
>>> On Mon, Mar 7, 2016 at 6:13 PM, Jean-Baptiste Onofré 
>>> wrote:
>>>
>>> Hi Minudika,

 You can now switch to Apache Beam repo, where it should build fine:

 [INFO] Google Cloud Dataflow Java SDK - Parent  SUCCESS [
 0.204 s]
 [INFO] Google Cloud Dataflow Java SDK - All ... SUCCESS
 [01:32
 min]
 [INFO] Beam Runners ... SUCCESS [
 0.005 s]
 [INFO] Flink Beam Runner .. SUCCESS
 [02:01
 min]
 [INFO] Google Cloud Dataflow Java Examples - All .. SUCCESS [
 11.960 s]
 [INFO] Google Cloud Dataflow Java SDK - Starter Archetype . SUCCESS [
 4.064 s]
 [INFO] Google Cloud Dataflow Java SDK - Examples Archetype  SUCCESS [
 7.178 s]
 [INFO]
 
 [INFO] BUILD SUCCESS
 [INFO]
 
 [INFO] Total time: 03:56 min
 [INFO] Finished at: 2016-03-07T13:38:58+01:00
 [INFO] Final Memory: 94M/1520M
 [INFO]
 

 I just tried on the Google DataFlowSDK github repo, and it works fine
 for
 me too:

 [INFO]
 
 [INFO] Reactor Summary:
 [INFO]
 [INFO] Google Cloud Dataflow Java SDK - Parent  SUCCESS [
 0.160 s]
 [INFO] Google Cloud Dataflow Java SDK - All ... SUCCESS
 [02:54
 min]
 [INFO] Google Cloud Dataflow Java Worker - All  SUCCESS [
 2.891 s]
 [INFO] Google Cloud Dataflow Java Examples - All .. SUCCESS [
 11.011 s]
 [INFO] Google Cloud Dataflow Java SDK - Starter Archetype . SUCCESS [
 3.125 s]
 [INFO] Google Cloud Dataflow Java SDK - Examples Archetype  SUCCESS [
 7.031 s]
 [INFO]
 
 [INFO] BUILD SUCCESS
 [INFO]
 
 [INFO] Total time: 03:19 min
 [INFO] Finished at: 2016-03-07T13:43:08+01:00
 [INFO] Final Memory: 76M/1403M
 [INFO]
 


 By the way, it seems you have a minor issue in your .m2/settings.xml
 where
 the  element is missing (not related to the project).

 What Java and Maven version do you use ?

 Thanks
 Regards
 JB

 On 03/07/2016 01:28 PM, Minudika Malshan wrote:

 Hi,
>
> I cloned the source of data flow SDK
>  and tried to
> build
>
> it.
> But build fails with the following stack trace.
> Please help me to get it resolved.
>
> Full stack trace :
>
> [WARNING]
> [WARNING] Some problems were encountered while building the effective
> settings
> [WARNING] Unrecognised tag: 'repositories' (position: START_TAG seen
> ... -->\n... @41:15)  @
> /home/minudika/.m2/settings.xml, line 41, column 15
> [WARNING]
> [INFO] Scanning for projects...
> [INFO]
>
> 
> [INFO] Reactor Build Order:

Re: [Google Dataflow SDK] Build fails

[Davor Bonaci]

Minudika's issue is the following:

[WARNING] Unused declared dependencies found:
[...]
[ERROR] Failed to execute
goal org.apache.maven.plugins:maven-dependency-plugin:2.8:analyze-only
(default) on project google-cloud-dataflow-java-sdk-all: Dependency
problems found.

It is possibly a real code issue. +Kenn, can you take a peek?

On Mon, Mar 7, 2016 at 6:06 AM, Jean-Baptiste Onofré 
wrote:

> It could be related to the mistake in your .m2/settings.xml as it looks
> like a  tag is missing.
>
> Can you check there ?
>
> Regards
> JB
>
>
> On 03/07/2016 02:57 PM, Minudika Malshan wrote:
>
>> Hi JB,
>>
>> Thanks a lot for your reply.
>> I'm using maven 3.3.9.
>>
>> I tried to build apache-beam too. It also gives the same error.
>>
>> *[ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-dependency-plugin:2.8:analyze-only
>> (default)
>> on project google-cloud-dataflow-java-sdk-all: Dependency problems found
>> ->
>> [Help 1]*
>>
>> Perhaps it's because of something wrong with my internet connection.
>> I will check with another connection.
>>
>> Please let me know if you have got anything. :)
>>
>> Best regards,
>> Minudika
>>
>>
>> Minudika Malshan
>> Undergraduate
>> Department of Computer Science and Engineering
>> University of Moratuwa.
>>
>>
>>
>>
>> On Mon, Mar 7, 2016 at 6:13 PM, Jean-Baptiste Onofré 
>> wrote:
>>
>> Hi Minudika,
>>>
>>> You can now switch to Apache Beam repo, where it should build fine:
>>>
>>> [INFO] Google Cloud Dataflow Java SDK - Parent  SUCCESS [
>>> 0.204 s]
>>> [INFO] Google Cloud Dataflow Java SDK - All ... SUCCESS
>>> [01:32
>>> min]
>>> [INFO] Beam Runners ... SUCCESS [
>>> 0.005 s]
>>> [INFO] Flink Beam Runner .. SUCCESS
>>> [02:01
>>> min]
>>> [INFO] Google Cloud Dataflow Java Examples - All .. SUCCESS [
>>> 11.960 s]
>>> [INFO] Google Cloud Dataflow Java SDK - Starter Archetype . SUCCESS [
>>> 4.064 s]
>>> [INFO] Google Cloud Dataflow Java SDK - Examples Archetype  SUCCESS [
>>> 7.178 s]
>>> [INFO]
>>> 
>>> [INFO] BUILD SUCCESS
>>> [INFO]
>>> 
>>> [INFO] Total time: 03:56 min
>>> [INFO] Finished at: 2016-03-07T13:38:58+01:00
>>> [INFO] Final Memory: 94M/1520M
>>> [INFO]
>>> 
>>>
>>> I just tried on the Google DataFlowSDK github repo, and it works fine for
>>> me too:
>>>
>>> [INFO]
>>> 
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] Google Cloud Dataflow Java SDK - Parent  SUCCESS [
>>> 0.160 s]
>>> [INFO] Google Cloud Dataflow Java SDK - All ... SUCCESS
>>> [02:54
>>> min]
>>> [INFO] Google Cloud Dataflow Java Worker - All  SUCCESS [
>>> 2.891 s]
>>> [INFO] Google Cloud Dataflow Java Examples - All .. SUCCESS [
>>> 11.011 s]
>>> [INFO] Google Cloud Dataflow Java SDK - Starter Archetype . SUCCESS [
>>> 3.125 s]
>>> [INFO] Google Cloud Dataflow Java SDK - Examples Archetype  SUCCESS [
>>> 7.031 s]
>>> [INFO]
>>> 
>>> [INFO] BUILD SUCCESS
>>> [INFO]
>>> 
>>> [INFO] Total time: 03:19 min
>>> [INFO] Finished at: 2016-03-07T13:43:08+01:00
>>> [INFO] Final Memory: 76M/1403M
>>> [INFO]
>>> 
>>>
>>>
>>> By the way, it seems you have a minor issue in your .m2/settings.xml
>>> where
>>> the  element is missing (not related to the project).
>>>
>>> What Java and Maven version do you use ?
>>>
>>> Thanks
>>> Regards
>>> JB
>>>
>>> On 03/07/2016 01:28 PM, Minudika Malshan wrote:
>>>
>>> Hi,

 I cloned the source of data flow SDK
  and tried to
 build

 it.
 But build fails with the following stack trace.
 Please help me to get it resolved.

 Full stack trace :

 [WARNING]
 [WARNING] Some problems were encountered while building the effective
 settings
 [WARNING] Unrecognised tag: 'repositories' (position: START_TAG seen
 ... -->\n... @41:15)  @
 /home/minudika/.m2/settings.xml, line 41, column 15
 [WARNING]
 [INFO] Scanning for projects...
 [INFO]
 
 [INFO] Reactor Build Order:
 [INFO]
 [INFO] Google Cloud Dataflow Java SDK - Parent
 [INFO] Google Cloud Dataflow Java SDK - All
 [INFO] Google Cloud Dataflow Java Examples - All
 [INFO] Google Cloud Dataflow Java SDK - Starter Archetype
 [INFO] Google Cloud Dataflow Java SDK - Examples Archetype
 [INFO]

Re: New beam website!

[Maximilian Michels]

Hi JB,

I've pushed the web site to the empty repository and I'll tell Infra
to switch to the new repository.

Cheers,
Max


On Fri, Mar 4, 2016 at 5:00 PM, Jean-Baptiste Onofré  wrote:
> Hi Max,
>
> fair enough.
>
> Regards
> JB
>
>
> On 03/04/2016 03:52 PM, Maximilian Michels wrote:
>>
>> Hi JB,
>>
>> Good question. I didn't create the page but one problem about relative
>> URLs is changing the root directory or switching to https. So instead
>> of relative URLs which should use {{ site.baseurl }}/resource for all
>> links. That way, we can simply change baseurl in the _config.yml and
>> we're good to go. For local testing, we set jekyll --baseurl "". That
>> approach has worked well for the Flink website which is also built
>> with Jekyll.
>>
>> Cheers,
>> Max
>>
>> On Fri, Mar 4, 2016 at 1:48 PM, Jean-Baptiste Onofré 
>> wrote:
>>>
>>> Hi Max,
>>>
>>> I just cloned your repo and built using jekyll.
>>>
>>> I just wonder why not using relative URL (for images and js location)
>>> instead of absolute ? It would allow us to directly open the website in a
>>> browser. WDYT ?
>>>
>>> Regards
>>> JB
>>>
>>> On 03/01/2016 01:59 PM, Maximilian Michels wrote:


 As a summary from
 https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11318
 it would work as follows:

 We use the 'asf-site' branch of the repository. When we change the
 website, we execute "jekyll build" followed by "jekyll serve" to
 preview the site. Everything is generated in the 'content' directory.
 We then push the changes and they are deployed.

 I've prepared everything in my fork:
 https://github.com/mxm/beam-site/tree/asf-site

 Unfortunately, I couldn't push the changes to the new repository. The
 permissions don't seem to be set up correctly.

 On Tue, Mar 1, 2016 at 10:24 AM, Maximilian Michels 
 wrote:
>
>
> Quick update. The Git repository is ready under
> https://git-wip-us.apache.org/repos/asf/incubator-beam-site.git
>
> I'm sorting out the last things and will push the website thereafter.
> Infra can then proceed to do the pubsub switch to deploy the website
> from there.
>
> On Thu, Feb 25, 2016 at 11:31 PM, Maximilian Michels 
> wrote:
>>
>>
>> Hi JB,
>>
>> Greetings to Mexico! I was using Infra's "SVN to Git migration"
>> service desk. That seems like a standard way for migration to me. It
>> has also worked fine in the past.
>>
>> Could you explain the role of the SCM-Publish Maven plugin? What would
>> be different from just committing the changes of the website to the
>> Git/SVN repository? Is it necessary that people use another wrapper
>> around a version control system?
>>
>> After all, what counts is that we can use a Git repository to check in
>> website changes and use the GitHub mirror. That is not only much
>> faster (pushing in SVN takes a long time and there is no local
>> repository) but also more convenient for most people that use Git on a
>> daily basis. How the actual website is served, shouldn't matter to the
>> developer.
>>
>> Cheers,
>> Max
>>
>> On Thu, Feb 25, 2016 at 11:23 PM, Jean-Baptiste Onofré
>> 
>> wrote:
>>>
>>>
>>>
>>>
>>> I agree and it's what we have: the website sources are on my github
>>> and
>>> we will move it on apache git. Anyway the source is not where you
>>> promote
>>> with the scm-publish. The PR or patches are not created based on the
>>> "resulting" location (on svn now) but on the sources (on my github
>>> now).
>>> That's why I didn't understand the jira.
>>> I don't mind to move the "resulting/promotion" location from svn to
>>> git, but I don't see how it changes for the devs. It would be exactly
>>> the
>>> same workflow  (using the scm-publish plugin).
>>> Regards JB
>>>
>>>
>>> Sent from my Samsung device
>>>
>>>  Original message 
>>> From: James Malone 
>>> Date: 25/02/2016  21:38  (GMT+01:00)
>>> To: dev@beam.incubator.apache.org
>>> Subject: Re: New beam website!
>>>
>>> I'll chime in here - I'd greatly prefer a git-based repo for the
>>> website.
>>> If nothing else, it's what many of the committers on our side are
>>> familiar
>>> with.
>>>
>>> Cheers!
>>>
>>> James
>>>
>>> On Thu, Feb 25, 2016 at 10:49 AM, Henry Saputra
>>> 
>>> wrote:
>>>
 Hi JB,

 ASF infra now offer Git pubsub to support website source code [1]

 I think this is what Max was trying to enable so instead of using
 svn
 for
 website it will be using Git that also allow pubsub to