[RESULT] [DISCUSS] Leave Apache and the Incubator

2020-01-19 Thread Javi Roman
The community has voted retired Myriad project from Apache Incubator:

+1 6 votes
-1 0 votes.

We will start the retirement process accordingly with IPMC guidelines.
--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman


[DISCUSS] Leave Apache and the Incubator

2020-01-02 Thread Javi Roman
Please vote to retire Myriad from the ASF Incubator. My take is that
Myriad has failed to get adequate community traction in the ASF
Incubator and the administrative work of the ASF is more of a burden
than a benefit to the project. Exiting incubation right now seems like
the obvious benefit to everyone -- the decision to return can always be
made later and should be easier to execute the second time around.

[ ] +1 to retire
[ ] -1 Not retiring because..

Here's my +1

This will be open for at least 72 hours and is a Majority vote.
--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman


Re: Multiple versions of Apache Hadoop YARN as a Service

2019-09-24 Thread Javi Roman
Honestly your opinion is welcome, this kind of discussions are great
in this small traffic dev list ;-)
--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman

On Tue, Sep 24, 2019 at 8:55 PM yuliya Feldman
 wrote:
>
>  I am not saying it's crazy. I was voicing my opinion. Isn't it what was the 
> purpose of the discussion?
> It's definitely great to have UI that manages all the YARN clusters, but it's 
> not like UI/Web service has to be coupled/collocated with any of the Myriad 
> particular YARN version daemons.
> It's great if you would provide write up with pros and cons for your approach 
> or any alternative approaches.
>
>
> On Tuesday, September 24, 2019, 11:38:13 AM PDT, Javi Roman 
>  wrote:
>
>  On Tue, Sep 24, 2019 at 7:58 PM yuliya Feldman
>  wrote:
> >
> >  Hello,
> > Again I apologize for the late reply.
> > I think I replied to the thread, but will add more direct notes here
> > What you are proposing is to have yet another daemon that would start Yarn 
> > Clusters on demand within Mesos framework.
> > Meaning - it would be another layer of abstraction.  In this case that new 
> > layer would need to behave as second level scheduler and deal with third 
> > level scheduler(s) (RMs) to propagate offers from Mesos and keep track, etc.
> > I am sure you can somehow use concept of Capacity and/or FairShare 
> > scheduler in your new layer to do the job. I am just not very much 
> > convinced that 3 layers of scheduling will be easy to 
> > maintain/reconcile/etc.
> > Again - if I understand your design correctly.
> > Would be great if you do a small write up with the proposal and have some 
> > simple diagram of services interactions.
> > Just my 2c.
> > Thanks,Yuliya
>
> Great, I wil do a diagram!
>
> Only for clarify:
>
> Myriad is registered as framework in Mesos master. The same thread
> start the API server and the user interface. By means the user
> interface you select the YARN version to run, and the scheduler get
> resources from master for running RM and NMs. So you con manage as
> many YARN schedulers you want. YARN as a Service.
>
> Maybe I am missing the point, bu I don't feel this is something so
> strange, or so crazy!
>
>
> >On Wednesday, September 11, 2019, 11:55:07 PM PDT, Oscar Fernandez 
> >  wrote:
> >
> >  Hi,
> >
> > I've started working on https://issues.apache.org/jira/browse/MYRIAD-295 -
> > Multiple versions of Apache Hadoop YARN as a Service.
> >
> > In order to implement this, we should avoid starting the Myriad framework
> > from Yarn and instead starting Yarn(s) from Myriad on demand.
> >
> > I wanted to ask the Myriad community if this design was intended for a
> > reason or if you think it's a good idea to decouple the execution of Myriad
> > from the Yarn RM. With the new design, the Myriad Framework would register
> > on Mesos, and then, start on demand the RM and NM that the user wants,
> > allowing several Yarn clusters to run in he same Mesos, even with different
> > versions.
> >
> > Thank you
> >
>


Re: Multiple versions of Apache Hadoop YARN as a Service

2019-09-24 Thread Javi Roman
On Tue, Sep 24, 2019 at 7:58 PM yuliya Feldman
 wrote:
>
>  Hello,
> Again I apologize for the late reply.
> I think I replied to the thread, but will add more direct notes here
> What you are proposing is to have yet another daemon that would start Yarn 
> Clusters on demand within Mesos framework.
> Meaning - it would be another layer of abstraction.  In this case that new 
> layer would need to behave as second level scheduler and deal with third 
> level scheduler(s) (RMs) to propagate offers from Mesos and keep track, etc.
> I am sure you can somehow use concept of Capacity and/or FairShare scheduler 
> in your new layer to do the job. I am just not very much convinced that 3 
> layers of scheduling will be easy to maintain/reconcile/etc.
> Again - if I understand your design correctly.
> Would be great if you do a small write up with the proposal and have some 
> simple diagram of services interactions.
> Just my 2c.
> Thanks,Yuliya

Great, I wil do a diagram!

Only for clarify:

Myriad is registered as framework in Mesos master. The same thread
start the API server and the user interface. By means the user
interface you select the YARN version to run, and the scheduler get
resources from master for running RM and NMs. So you con manage as
many YARN schedulers you want. YARN as a Service.

Maybe I am missing the point, bu I don't feel this is something so
strange, or so crazy!


> On Wednesday, September 11, 2019, 11:55:07 PM PDT, Oscar Fernandez 
>  wrote:
>
>  Hi,
>
> I've started working on https://issues.apache.org/jira/browse/MYRIAD-295 -
> Multiple versions of Apache Hadoop YARN as a Service.
>
> In order to implement this, we should avoid starting the Myriad framework
> from Yarn and instead starting Yarn(s) from Myriad on demand.
>
> I wanted to ask the Myriad community if this design was intended for a
> reason or if you think it's a good idea to decouple the execution of Myriad
> from the Yarn RM. With the new design, the Myriad Framework would register
> on Mesos, and then, start on demand the RM and NM that the user wants,
> allowing several Yarn clusters to run in he same Mesos, even with different
> versions.
>
> Thank you
>


Re: Multiple versions of Apache Hadoop YARN as a Service

2019-09-24 Thread Javi Roman
On Tue, Sep 24, 2019 at 7:48 PM yuliya Feldman
 wrote:
>
>  >>> I guess we are talking about the concept of multi-service scheduler

Are you proposing to have a multi service scheduler? I thought that's
what Mesos is for?What am I missing here?

Yes is common in Mesos (IMHO): Marathon is a multi-service scheduler,
Apache Aurora too. Please take a look here:

https://mesosphere.github.io/dcos-commons/multi-service/


> On Tue, Sep 24, 2019 at 5:40 PM Yuliya  wrote:
> >
> > Hello there,
> >
> > Sorry for late reply.
> >
> > Frankly speaking I don’t know original motivation , I would probably say 
> > that it started organically as a need.
> >
> > What do you mean by starting yarn from myriad? I believe myriad daemons 
> > encompass some functionality of yarn daemons, namely rm and nm, so it’s not 
> > yarn that starts myriad, but myriad daemons that play role of yarn daemons.
> >  Unless I am missing something here.
> >
> > Are you proposing to have the same myriad daemons starting different 
> > versions of yarn?
> >  I would consider different set of docker containers built with different 
> > versions of yarn would be better decoupling. I am open for discussion 
> > though.
> >
> > Thanks,
> > Yuliya
> >
> >
> >
> > > On Sep 15, 2019, at 10:35 PM, Javi Roman  wrote:
> > >
> > > Hi Oscar,
> > >
> > > I have to say I don't know the initial motivation of this design. You
> > > are right the way of starting Myriad, strongly coupled to YARN is a
> > > little bit weird.
> > > Because of lack of activity of the initial committers, this is a
> > > question that probably we never get a clear answer.
> > >
> > > By the way, your proposal, according with MYRIAD-295 is, from my
> > > understanding, the right way to go ahead with the project.
> > >
> > > This new design is totally aligned with the further Myriad UI design
> > > (https://issues.apache.org/jira/browse/MYRIAD-279).
> > >
> > > The document design of this new UI here:
> > > https://docs.google.com/document/d/16gA67RXoPK24OIxDMNNhuYS8ioScI1eOBR-XMMPjWQE/edit?usp=sharing
> > > --
> > > Javi Roman
> > >
> > > Twitter: @javiromanrh
> > > GitHub: github.com/javiroman
> > > Linkedin: es.linkedin.com/in/javiroman
> > > Big Data Blog: dataintensive.info
> > > Apache Id: javiroman
> > >
> > >> On Thu, Sep 12, 2019 at 8:55 AM Oscar Fernandez  
> > >> wrote:
> > >>
> > >> Hi,
> > >>
> > >> I've started working on https://issues.apache.org/jira/browse/MYRIAD-295 
> > >> -
> > >> Multiple versions of Apache Hadoop YARN as a Service.
> > >>
> > >> In order to implement this, we should avoid starting the Myriad framework
> > >> from Yarn and instead starting Yarn(s) from Myriad on demand.
> > >>
> > >> I wanted to ask the Myriad community if this design was intended for a
> > >> reason or if you think it's a good idea to decouple the execution of 
> > >> Myriad
> > >> from the Yarn RM. With the new design, the Myriad Framework would 
> > >> register
> > >> on Mesos, and then, start on demand the RM and NM that the user wants,
> > >> allowing several Yarn clusters to run in he same Mesos, even with 
> > >> different
> > >> versions.
> > >>
> > >> Thank you
> >


Re: Multiple versions of Apache Hadoop YARN as a Service

2019-09-24 Thread Javi Roman
I guess we are talking about the concept of multi-service scheduler, or one
framework for multiple services, in our case multiple YARN services
(different versions, and so on).

Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman
On Tue, Sep 24, 2019 at 5:40 PM Yuliya  wrote:
>
> Hello there,
>
> Sorry for late reply.
>
> Frankly speaking I don’t know original motivation , I would probably say that 
> it started organically as a need.
>
> What do you mean by starting yarn from myriad? I believe myriad daemons 
> encompass some functionality of yarn daemons, namely rm and nm, so it’s not 
> yarn that starts myriad, but myriad daemons that play role of yarn daemons.
>  Unless I am missing something here.
>
> Are you proposing to have the same myriad daemons starting different versions 
> of yarn?
>  I would consider different set of docker containers built with different 
> versions of yarn would be better decoupling. I am open for discussion though.
>
> Thanks,
> Yuliya
>
>
>
> > On Sep 15, 2019, at 10:35 PM, Javi Roman  wrote:
> >
> > Hi Oscar,
> >
> > I have to say I don't know the initial motivation of this design. You
> > are right the way of starting Myriad, strongly coupled to YARN is a
> > little bit weird.
> > Because of lack of activity of the initial committers, this is a
> > question that probably we never get a clear answer.
> >
> > By the way, your proposal, according with MYRIAD-295 is, from my
> > understanding, the right way to go ahead with the project.
> >
> > This new design is totally aligned with the further Myriad UI design
> > (https://issues.apache.org/jira/browse/MYRIAD-279).
> >
> > The document design of this new UI here:
> > https://docs.google.com/document/d/16gA67RXoPK24OIxDMNNhuYS8ioScI1eOBR-XMMPjWQE/edit?usp=sharing
> > --
> > Javi Roman
> >
> > Twitter: @javiromanrh
> > GitHub: github.com/javiroman
> > Linkedin: es.linkedin.com/in/javiroman
> > Big Data Blog: dataintensive.info
> > Apache Id: javiroman
> >
> >> On Thu, Sep 12, 2019 at 8:55 AM Oscar Fernandez  
> >> wrote:
> >>
> >> Hi,
> >>
> >> I've started working on https://issues.apache.org/jira/browse/MYRIAD-295 -
> >> Multiple versions of Apache Hadoop YARN as a Service.
> >>
> >> In order to implement this, we should avoid starting the Myriad framework
> >> from Yarn and instead starting Yarn(s) from Myriad on demand.
> >>
> >> I wanted to ask the Myriad community if this design was intended for a
> >> reason or if you think it's a good idea to decouple the execution of Myriad
> >> from the Yarn RM. With the new design, the Myriad Framework would register
> >> on Mesos, and then, start on demand the RM and NM that the user wants,
> >> allowing several Yarn clusters to run in he same Mesos, even with different
> >> versions.
> >>
> >> Thank you
>


[jira] [Assigned] (MYRIAD-279) Reworking a new UI design

2019-09-15 Thread Javi Roman (Jira)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reassigned MYRIAD-279:
-

Assignee: Javi Roman

> Reworking a new UI design
> -
>
> Key: MYRIAD-279
> URL: https://issues.apache.org/jira/browse/MYRIAD-279
> Project: Myriad
>  Issue Type: New Feature
>  Components: User Interface
>Affects Versions: Myriad 0.5.0
>    Reporter: Javi Roman
>Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.5.0
>
>
> We should enhance the whole look and feel of Myriad UI, to add a dashboard, 
> new controls, metrics about YARN and HDFS and so forth.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


Re: Multiple versions of Apache Hadoop YARN as a Service

2019-09-15 Thread Javi Roman
Hi Oscar,

I have to say I don't know the initial motivation of this design. You
are right the way of starting Myriad, strongly coupled to YARN is a
little bit weird.
Because of lack of activity of the initial committers, this is a
question that probably we never get a clear answer.

By the way, your proposal, according with MYRIAD-295 is, from my
understanding, the right way to go ahead with the project.

This new design is totally aligned with the further Myriad UI design
(https://issues.apache.org/jira/browse/MYRIAD-279).

The document design of this new UI here:
https://docs.google.com/document/d/16gA67RXoPK24OIxDMNNhuYS8ioScI1eOBR-XMMPjWQE/edit?usp=sharing
--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman

On Thu, Sep 12, 2019 at 8:55 AM Oscar Fernandez  wrote:
>
> Hi,
>
> I've started working on https://issues.apache.org/jira/browse/MYRIAD-295 -
> Multiple versions of Apache Hadoop YARN as a Service.
>
> In order to implement this, we should avoid starting the Myriad framework
> from Yarn and instead starting Yarn(s) from Myriad on demand.
>
> I wanted to ask the Myriad community if this design was intended for a
> reason or if you think it's a good idea to decouple the execution of Myriad
> from the Yarn RM. With the new design, the Myriad Framework would register
> on Mesos, and then, start on demand the RM and NM that the user wants,
> allowing several Yarn clusters to run in he same Mesos, even with different
> versions.
>
> Thank you


Re: Podling Report Reminder - September 2019

2019-09-06 Thread Javi Roman
Done  I hope is a little bit improved right now.
--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman

On Fri, Sep 6, 2019 at 10:02 AM Justin Mclean  wrote:
>
> Hi,
>
> > Do we have the opportunity of improving right now, or we are out of time?
>
> You can improve it now.
>
> Thanks,
> Justin


Re: Podling Report Reminder - September 2019

2019-09-06 Thread Javi Roman
Do we have the opportunity of improving right now, or we are out of time?
--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman

On Fri, Sep 6, 2019 at 9:25 AM Justin Mclean  wrote:
>
> Hi,
>
> Thanks for submitting the reports, but unless it is improved, it's going to 
> be rejected and I'll ask for you to report next month. The item listed under 
> graduation have nothing to do with graduation. The issues should be about 
> moving towards doing things how Apache project work and community, not 
> functionality. I's also like to see some more detail and less stats, it 
> doesn't;t really matter how many twitter followers you have and that number 
> on it own doesn't tell anyone outside the project about community growth.
>
> Thanks,
> Justin


[jira] [Updated] (MYRIAD-295) Multiple versions of Apache Hadoop YARN as a Service

2019-08-31 Thread Javi Roman (Jira)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman updated MYRIAD-295:
--
Summary: Multiple versions of Apache Hadoop YARN as a Service  (was: Allow 
multiple versions of Apache Hadoop to run on the same physical infrastructure)

> Multiple versions of Apache Hadoop YARN as a Service
> 
>
> Key: MYRIAD-295
> URL: https://issues.apache.org/jira/browse/MYRIAD-295
> Project: Myriad
>  Issue Type: Improvement
>Affects Versions: Myriad 0.5.0
>    Reporter: Javi Roman
>Assignee: Oscar Fernandez
>Priority: Major
> Fix For: Myriad 0.5.0
>
>
> One of the most interesting features listed in the original Apache Myriad 
> Incubator Proposal [1], was:
>  * Allow multiple versions of Apache Hadoop to run on the same physical 
> infrastructure
> From my point of view this is one of the major advantages of Apache Mesos in 
> the context of framework development. Apache Myriad could be modified in 
> order to create a robust Apache YARN as a Services application. Multiple 
> YARNs running in the same infrastructure is a major goal for the project.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Resolved] (MYRIAD-303) Prepare for 0.4.0 release

2019-08-26 Thread Javi Roman (Jira)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-303.
---
Resolution: Done

> Prepare for 0.4.0 release
> -
>
> Key: MYRIAD-303
> URL: https://issues.apache.org/jira/browse/MYRIAD-303
> Project: Myriad
>  Issue Type: Task
>Affects Versions: Myriad 0.4.0
>Reporter: Oscar Fernandez
>Assignee: Oscar Fernandez
>Priority: Major
>  Labels: releasegeneration
> Fix For: Myriad 0.4.0
>
>
> Umbrella task for 0.4.0 version releasing.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Closed] (MYRIAD-322) Add version 0.5.0 in Apache Myriad Jira

2019-08-26 Thread Javi Roman (Jira)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-322.
-

> Add version 0.5.0 in Apache Myriad Jira
> ---
>
> Key: MYRIAD-322
> URL: https://issues.apache.org/jira/browse/MYRIAD-322
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.4.0
>Reporter: Oscar Fernandez
>Assignee: Oscar Fernandez
>Priority: Major
> Fix For: Myriad 0.4.0
>
>
> Create new version to assign tasks in Jira



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Closed] (MYRIAD-303) Prepare for 0.4.0 release

2019-08-26 Thread Javi Roman (Jira)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-303.
-

> Prepare for 0.4.0 release
> -
>
> Key: MYRIAD-303
> URL: https://issues.apache.org/jira/browse/MYRIAD-303
> Project: Myriad
>  Issue Type: Task
>Affects Versions: Myriad 0.4.0
>Reporter: Oscar Fernandez
>Assignee: Oscar Fernandez
>Priority: Major
>  Labels: releasegeneration
> Fix For: Myriad 0.4.0
>
>
> Umbrella task for 0.4.0 version releasing.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Resolved] (MYRIAD-322) Add version 0.5.0 in Apache Myriad Jira

2019-08-26 Thread Javi Roman (Jira)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-322.
---
Resolution: Done

> Add version 0.5.0 in Apache Myriad Jira
> ---
>
> Key: MYRIAD-322
> URL: https://issues.apache.org/jira/browse/MYRIAD-322
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.4.0
>Reporter: Oscar Fernandez
>Assignee: Oscar Fernandez
>Priority: Major
> Fix For: Myriad 0.4.0
>
>
> Create new version to assign tasks in Jira



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Closed] (MYRIAD-324) Send ANNOUNCE email

2019-08-26 Thread Javi Roman (Jira)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-324.
-

> Send ANNOUNCE email
> ---
>
> Key: MYRIAD-324
> URL: https://issues.apache.org/jira/browse/MYRIAD-324
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.4.0
>Reporter: Oscar Fernandez
>Assignee: Oscar Fernandez
>Priority: Major
> Fix For: Myriad 0.4.0
>
>
> Send mail to [annou...@apache.org|mailto:annou...@apache.org]
> Example: 
> [http://mail-archives.apache.org/mod_mbox/www-announce/201904.mbox/%3ccacwqdqbovzouubxoeyfd0pd9wbthp9-jg1wmzxbcukkugw-...@mail.gmail.com%3E]



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (MYRIAD-317) Upgrade to Gradle 6

2019-08-21 Thread Javi Roman (Jira)
Javi Roman created MYRIAD-317:
-

 Summary: Upgrade to Gradle 6
 Key: MYRIAD-317
 URL: https://issues.apache.org/jira/browse/MYRIAD-317
 Project: Myriad
  Issue Type: Improvement
Reporter: Javi Roman


Deprecated Gradle features were used in this build, making it incompatible with 
Gradle 6.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See 
https://docs.gradle.org/5.5/userguide/command_line_interface.html#sec:command_line_warnings



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (MYRIAD-316) Upgrade to PDM 7

2019-08-21 Thread Javi Roman (Jira)
Javi Roman created MYRIAD-316:
-

 Summary: Upgrade to PDM 7
 Key: MYRIAD-316
 URL: https://issues.apache.org/jira/browse/MYRIAD-316
 Project: Myriad
  Issue Type: Improvement
Reporter: Javi Roman


Task :myriad-scheduler:pmdMain 
Discontinue using Rule name category/java/codestyle.xml/ForLoopsMustUseBraces 
as it is scheduled for removal from PMD. PMD 7.0.0 will remove support for this 
Rule. 
Use Rule name category/java/codestyle.xml/ForLoopsMustUseBraces instead of the 
deprecated Rule name rulesets/java/braces.xml/ForLoopsMustUseBraces. PMD 7.0.0 
will remove sup
port for this deprecated Rule name usage.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


Re: [VOTE] Release apache-myriad-0.4.0-incubating (release candidate 1)

2019-08-14 Thread Javi Roman
+1 (binding)

Steps for release review:

1. Download the RC1 release:
$ wget -e robots=off -r -nH --cut-dirs=5 --no-parent -R "index.html*"
https://dist.apache.org/repos/dist/dev/incubator/myriad/myriad-0.4.0-incubating-rc1/
$ cd myriad-0.4.0-incubating-rc1/
$ wget https://dist.apache.org/repos/dist/dev/incubator/myriad/KEYS

2. Signatures checking:
$ gpg --import KEYS
$ gpg --verify myriad-0.4.0-incubating-rc1.tar.gz.asc
myriad-0.4.0-incubating-rc1.tar.gz

3. Checksum checking:
$ gpg --print-md SHA512 myriad-0.4.0-incubating-rc1.tar.gz | diff -
myriad-0.4.0-incubating-rc1.tar.gz.sha512

4. Disclaimer and Notice files:
Verify the incubator disclaimer is in a separate file called DISCLAIMER,
residing inside the top-level distribution folder, along with the LICENSE and
NOTICE files.

5. All source files have license headers, where appropriate:
$ wget 
http://central.maven.org/maven2/org/apache/rat/apache-rat/0.13/apache-rat-0.13.jar
$ cat rat-excludes
.*\.txt(?:)
.*\.md(?:)
.npmrc
slaves
workers
package.json
roles/common/vars/main.yml
.*\.service(?:)
main.yml
package-lock.json
.babelrc

$ java -jar apache-rat-0.13.jar -E rat-excludes -d
myriad-0.4.0-incubating-rc1 > report

6. Release consists of source code only, no binaries:
$ find . -name *.jar

7. Build is successful, including automated tests:
$ gradle wrapper --gradle-version 5.5
$ ./gradlew build
$ find . -name *.jar

Review summary

Checked PGP signatures
Checked Checksums
DISCLAIMER checked
LICENSE checked
NOTICE checked
RAT Check passes
Source code only checked
Build and unitary tests checked
Functional testing checked with Apache Mesos 1.8.0 with success.

Some minor issue:

$ find . -name *.jar | grep 0.3.0
./docker/build/libs/docker-0.3.0.jar
./myriad-scheduler/build/libs/myriad-scheduler-0.3.0.jar
./myriad-scheduler/build/libs/myriad-commons-0.3.0.jar
./myriad-executor/build/libs/myriad-executor-0.3.0.jar
./myriad-commons/build/libs/myriad-commons-0.3.0.jar

The binary has the wrong version number (right now is 0.4.0), this is
something to fix in the
next version.

--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman

On Wed, Aug 14, 2019 at 2:20 PM Oscar Fernandez  wrote:
>
> Hi All,
>
> I would like to start the voting process of a new release of Apache Myriad
> (Incubator).
>
> I have created a source tar ball for Apache Myriad 0.4.0-incubating,
> release candidate 1.
>
> 1. Release notes:
> https://github.com/apache/incubator-myriad/blob/master/CHANGELOG.md
>
> 2. The commit to be voted upon is tagged with "myriad-0.4.0-incubating-rc1"
> and is available here:
> https://gitbox.apache.org/repos/asf?p=incubator-myriad.git;a=commit;h=019fba2be3e310302cd60a25d7d71f1310c9d5a5
>
> 3. The artifacts to be voted upon are located below. Please note that this
> is a Source Release:
> https://dist.apache.org/repos/dist/dev/incubator/myriad/myriad-0.4.0-incubating-rc1/
>
> 4. Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/oscarfmdc.asc
>
> 5. Please note that the release tar ball does not include the gradlew
> script to build. You need to generate one in order to build:
> $ gradle wrapper --gradle-version 5.5
> $ ./gradlew build
>
> Please try out the release candidate and vote. The vote is open for a
> minimum of 72 hours or until the necessary number of votes (3 binding +1s)
> is reached.
>
> Note: We have a lot of warnings in the build related with deprecated
> features in Gradle 6.0, Findbugs, and PDM plugins. This will fixed in the
> next versions.
>
> If/when this vote succeeds, I will call for a vote with IPMC seeking
> permission to release RC1 as Apache Myriad 0.4.0 (incubating).
>
> [ ] +1 Release this package as Apache Myriad 0.4.0-incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Many thanks!!!
>
> Note: We need  at least 3 +1 binding votes (included PPMCs and Mentors).


[jira] [Closed] (MYRIAD-166) Add Webapp and Website JIRA components

2019-08-09 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-166.
-

Current components:
[Confluence|https://issues.apache.org/jira/issues/?jql=project+%3D+MYRIAD+AND+component+%3D+Confluence]
[Website|https://issues.apache.org/jira/issues/?jql=project+%3D+MYRIAD+AND+component+%3D+Website]
[Executor|https://issues.apache.org/jira/issues/?jql=project+%3D+MYRIAD+AND+component+%3D+Executor]
[Scheduler|https://issues.apache.org/jira/issues/?jql=project+%3D+MYRIAD+AND+component+%3D+Scheduler]
[User 
Interface|https://issues.apache.org/jira/issues/?jql=project+%3D+MYRIAD+AND+component+%3D+%22User+Interface%22]
[Vagrant|https://issues.apache.org/jira/issues/?jql=project+%3D+MYRIAD+AND+component+%3D+Vagrant]

> Add Webapp and Website JIRA components
> --
>
> Key: MYRIAD-166
> URL: https://issues.apache.org/jira/browse/MYRIAD-166
> Project: Myriad
>  Issue Type: Task
>Reporter: Jim Klucar
>    Assignee: Javi Roman
>Priority: Trivial
>
> Our JIRA components are currently Executor and Scheduler. I would be nice to 
> have Webapp, Website, and possibly Wiki components to be able to organize 
> issues better. This just requires a JIRA admin to add them.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (MYRIAD-166) Add Webapp and Website JIRA components

2019-08-09 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-166.
---
Resolution: Fixed

done.

> Add Webapp and Website JIRA components
> --
>
> Key: MYRIAD-166
> URL: https://issues.apache.org/jira/browse/MYRIAD-166
> Project: Myriad
>  Issue Type: Task
>Reporter: Jim Klucar
>    Assignee: Javi Roman
>Priority: Trivial
>
> Our JIRA components are currently Executor and Scheduler. I would be nice to 
> have Webapp, Website, and possibly Wiki components to be able to organize 
> issues better. This just requires a JIRA admin to add them.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Assigned] (MYRIAD-166) Add Webapp and Website JIRA components

2019-08-09 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reassigned MYRIAD-166:
-

Assignee: Javi Roman

> Add Webapp and Website JIRA components
> --
>
> Key: MYRIAD-166
> URL: https://issues.apache.org/jira/browse/MYRIAD-166
> Project: Myriad
>  Issue Type: Task
>Reporter: Jim Klucar
>    Assignee: Javi Roman
>Priority: Trivial
>
> Our JIRA components are currently Executor and Scheduler. I would be nice to 
> have Webapp, Website, and possibly Wiki components to be able to organize 
> issues better. This just requires a JIRA admin to add them.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (MYRIAD-308) md5 checksums are deprecated "prepare_rc.sh" script need update

2019-08-06 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-308.
---
Resolution: Fixed

> md5 checksums are deprecated "prepare_rc.sh" script need update
> ---
>
> Key: MYRIAD-308
> URL: https://issues.apache.org/jira/browse/MYRIAD-308
> Project: Myriad
>  Issue Type: Bug
>Reporter: Javi Roman
>Assignee: Oscar Fernandez
>Priority: Minor
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> we have to elminate the md5 checksu creation in the support script.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Closed] (MYRIAD-308) md5 checksums are deprecated "prepare_rc.sh" script need update

2019-08-06 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-308.
-

> md5 checksums are deprecated "prepare_rc.sh" script need update
> ---
>
> Key: MYRIAD-308
> URL: https://issues.apache.org/jira/browse/MYRIAD-308
> Project: Myriad
>  Issue Type: Bug
>Reporter: Javi Roman
>Assignee: Oscar Fernandez
>Priority: Minor
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> we have to elminate the md5 checksu creation in the support script.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Created] (MYRIAD-308) md5 checksums are deprecated "prepare_rc.sh" script need update

2019-08-06 Thread Javi Roman (JIRA)
Javi Roman created MYRIAD-308:
-

 Summary: md5 checksums are deprecated "prepare_rc.sh" script need 
update
 Key: MYRIAD-308
 URL: https://issues.apache.org/jira/browse/MYRIAD-308
 Project: Myriad
  Issue Type: Bug
Reporter: Javi Roman


we have to elminate the md5 checksu creation in the support script.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Assigned] (MYRIAD-302) Renaming artifacts with correct version

2019-07-25 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reassigned MYRIAD-302:
-

Assignee: Oscar Fernandez  (was: Javi Roman)

> Renaming artifacts with correct version
> ---
>
> Key: MYRIAD-302
> URL: https://issues.apache.org/jira/browse/MYRIAD-302
> Project: Myriad
>  Issue Type: Improvement
>  Components: Executor, Scheduler
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Assignee: Oscar Fernandez
>Priority: Major
> Fix For: Myriad 0.4.0
>
>
> The build system create myriad artifacts with the incorrect version number:
>  
> {noformat}
> ./myriad-commons/build/libs/myriad-commons-0.2.0.jar
> ./myriad-executor/build/libs/myriad-executor-0.2.0.jar
> ./myriad-scheduler/build/libs/myriad-scheduler-0.2.0.jar
> {noformat}
>  
> The current version is v0.3.0
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Assigned] (MYRIAD-180) Build should not pollute sources

2019-07-25 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reassigned MYRIAD-180:
-

Assignee: Oscar Fernandez  (was: Javi Roman)

> Build should not pollute sources
> 
>
> Key: MYRIAD-180
> URL: https://issues.apache.org/jira/browse/MYRIAD-180
> Project: Myriad
>  Issue Type: Bug
>Affects Versions: Myriad 0.4.0
>Reporter: Santosh Marella
>Assignee: Oscar Fernandez
>Priority: Major
> Fix For: Myriad 0.4.0
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-general/201512.mbox/%3CCAPmHmDTM4T37wJj6sPZniiU0mwm7qC4P9VCEHaOxhwWAvr%2Be_g%40mail.gmail.com%3E
> Myriad scheduler build generates the node_modules  directory 
> (myriad-scheduler/src/main/resources/webapp/node_modules). Ideally, any files 
> downloaded/generated by build should be outside of "src".



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Closed] (MYRIAD-23) when i flexdown a running instance ,it does not work

2019-07-25 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-23.

   Resolution: Cannot Reproduce
Fix Version/s: Myriad 0.4.0

> when i flexdown a running instance ,it does not work
> 
>
> Key: MYRIAD-23
> URL: https://issues.apache.org/jira/browse/MYRIAD-23
> Project: Myriad
>  Issue Type: Bug
>  Components: User Interface
>Reporter: pengyunli
>    Assignee: Javi Roman
> Fix For: Myriad 0.4.0
>
>
> there are 3 instances,when i call flexdown api,i found that it can not 
> flexdown a running instance,there is still 3 running instanec,below is 
> resourcemanager.log
> uler.Rebalancer: Active 3, Pending 0
> 2015-02-09 01:11:21,831 INFO com.ebay.myriad.scheduler.MyriadOperations: 
> About to flex down 1 instances
> 2015-02-09 01:11:21,831 INFO com.ebay.myriad.scheduler.MyriadOperations: 
> Flexed down 0 of 1 instances including 0 staging instances, and 0 pending 
> instances.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Assigned] (MYRIAD-23) when i flexdown a running instance ,it does not work

2019-07-25 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reassigned MYRIAD-23:


Assignee: Javi Roman

> when i flexdown a running instance ,it does not work
> 
>
> Key: MYRIAD-23
> URL: https://issues.apache.org/jira/browse/MYRIAD-23
> Project: Myriad
>  Issue Type: Bug
>  Components: User Interface
>Reporter: pengyunli
>    Assignee: Javi Roman
>
> there are 3 instances,when i call flexdown api,i found that it can not 
> flexdown a running instance,there is still 3 running instanec,below is 
> resourcemanager.log
> uler.Rebalancer: Active 3, Pending 0
> 2015-02-09 01:11:21,831 INFO com.ebay.myriad.scheduler.MyriadOperations: 
> About to flex down 1 instances
> 2015-02-09 01:11:21,831 INFO com.ebay.myriad.scheduler.MyriadOperations: 
> Flexed down 0 of 1 instances including 0 staging instances, and 0 pending 
> instances.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (MYRIAD-302) Renaming artifacts with correct version

2019-07-19 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman updated MYRIAD-302:
--
Description: 
The build system create myriad artifacts with the incorrect version number:

 
{noformat}
./myriad-commons/build/libs/myriad-commons-0.2.0.jar
./myriad-executor/build/libs/myriad-executor-0.2.0.jar
./myriad-scheduler/build/libs/myriad-scheduler-0.2.0.jar

{noformat}
 

The current version is v0.3.0

 

 

 

  was:
The build system create myriad artifacts with the incorrect version number:

 

./myriad-commons/build/libs/myriad-commons-0.2.0.jar

./myriad-executor/build/libs/myriad-executor-0.2.0.jar

 

 


> Renaming artifacts with correct version
> ---
>
> Key: MYRIAD-302
> URL: https://issues.apache.org/jira/browse/MYRIAD-302
> Project: Myriad
>  Issue Type: Improvement
>  Components: Executor, Scheduler
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.4.0
>
>
> The build system create myriad artifacts with the incorrect version number:
>  
> {noformat}
> ./myriad-commons/build/libs/myriad-commons-0.2.0.jar
> ./myriad-executor/build/libs/myriad-executor-0.2.0.jar
> ./myriad-scheduler/build/libs/myriad-scheduler-0.2.0.jar
> {noformat}
>  
> The current version is v0.3.0
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Created] (MYRIAD-302) Renaming artifacts with correct version

2019-07-19 Thread Javi Roman (JIRA)
Javi Roman created MYRIAD-302:
-

 Summary: Renaming artifacts with correct version
 Key: MYRIAD-302
 URL: https://issues.apache.org/jira/browse/MYRIAD-302
 Project: Myriad
  Issue Type: Improvement
  Components: Executor, Scheduler
Affects Versions: Myriad 0.4.0
Reporter: Javi Roman
Assignee: Javi Roman
 Fix For: Myriad 0.4.0


The build system create myriad artifacts with the incorrect version number:

 

./myriad-commons/build/libs/myriad-commons-0.2.0.jar

./myriad-executor/build/libs/myriad-executor-0.2.0.jar

 

 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (MYRIAD-298) Upgrade Mesos API to 1.8.x

2019-07-18 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-298.
---
Resolution: Fixed

Done:

 

[https://github.com/apache/incubator-myriad/commit/d87b00d189e4580c5a376b3d3cebe41e1693ed5c]

> Upgrade Mesos API to 1.8.x
> --
>
> Key: MYRIAD-298
> URL: https://issues.apache.org/jira/browse/MYRIAD-298
> Project: Myriad
>  Issue Type: Task
>Affects Versions: Myriad 0.4.0
>Reporter: Oscar Fernandez
>Assignee: Oscar Fernandez
>Priority: Major
> Fix For: Myriad 0.4.0
>
>
> Apache Myriad should be upgraded to work with Mesos 1.8



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Closed] (MYRIAD-298) Upgrade Mesos API to 1.8.x

2019-07-18 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-298.
-

> Upgrade Mesos API to 1.8.x
> --
>
> Key: MYRIAD-298
> URL: https://issues.apache.org/jira/browse/MYRIAD-298
> Project: Myriad
>  Issue Type: Task
>Affects Versions: Myriad 0.4.0
>Reporter: Oscar Fernandez
>Assignee: Oscar Fernandez
>Priority: Major
> Fix For: Myriad 0.4.0
>
>
> Apache Myriad should be upgraded to work with Mesos 1.8



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Created] (MYRIAD-299) Create CHANGELOG file

2019-07-16 Thread Javi Roman (JIRA)
Javi Roman created MYRIAD-299:
-

 Summary: Create CHANGELOG file
 Key: MYRIAD-299
 URL: https://issues.apache.org/jira/browse/MYRIAD-299
 Project: Myriad
  Issue Type: Improvement
Affects Versions: Myriad 0.4.0
Reporter: Javi Roman
Assignee: Javi Roman
 Fix For: Myriad 0.4.0


It would be fine to create a Changelog file for tracking the release features.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (MYRIAD-298) Upgrade Mesos API to 1.7.x

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman updated MYRIAD-298:
--
Fix Version/s: Myriad 0.4.0

> Upgrade Mesos API to 1.7.x
> --
>
> Key: MYRIAD-298
> URL: https://issues.apache.org/jira/browse/MYRIAD-298
> Project: Myriad
>  Issue Type: Task
>Affects Versions: Myriad 0.4.0
>Reporter: Oscar Fernandez
>Assignee: Oscar Fernandez
>Priority: Major
> Fix For: Myriad 0.4.0
>
>
> Apache Myriad should be upgraded to work with Mesos 1.7



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (MYRIAD-298) Upgrade Mesos API to 1.7.x

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman updated MYRIAD-298:
--
Affects Version/s: Myriad 0.4.0

> Upgrade Mesos API to 1.7.x
> --
>
> Key: MYRIAD-298
> URL: https://issues.apache.org/jira/browse/MYRIAD-298
> Project: Myriad
>  Issue Type: Task
>Affects Versions: Myriad 0.4.0
>Reporter: Oscar Fernandez
>Assignee: Oscar Fernandez
>Priority: Major
>
> Apache Myriad should be upgraded to work with Mesos 1.7



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Assigned] (MYRIAD-298) Upgrade Mesos API to 1.7.x

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reassigned MYRIAD-298:
-

Assignee: Oscar Fernandez

> Upgrade Mesos API to 1.7.x
> --
>
> Key: MYRIAD-298
> URL: https://issues.apache.org/jira/browse/MYRIAD-298
> Project: Myriad
>  Issue Type: Task
>Reporter: Oscar Fernandez
>Assignee: Oscar Fernandez
>Priority: Major
>
> Apache Myriad should be upgraded to work with Mesos 1.7



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (MYRIAD-187) Update npm dependencies.

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman updated MYRIAD-187:
--
Fix Version/s: Myriad 0.4.0

> Update npm dependencies.
> 
>
> Key: MYRIAD-187
> URL: https://issues.apache.org/jira/browse/MYRIAD-187
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler
>Affects Versions: Myriad 0.1.0
>Reporter: DarinJ
>Assignee: Oscar Fernandez
>Priority: Minor
> Fix For: Myriad 0.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Reopened] (MYRIAD-187) Update npm dependencies.

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reopened MYRIAD-187:
---

> Update npm dependencies.
> 
>
> Key: MYRIAD-187
> URL: https://issues.apache.org/jira/browse/MYRIAD-187
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler
>Affects Versions: Myriad 0.1.0
>Reporter: DarinJ
>Assignee: Oscar Fernandez
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (MYRIAD-187) Update npm dependencies.

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-187.
---
Resolution: Fixed

> Update npm dependencies.
> 
>
> Key: MYRIAD-187
> URL: https://issues.apache.org/jira/browse/MYRIAD-187
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler
>Affects Versions: Myriad 0.1.0
>Reporter: DarinJ
>Assignee: Oscar Fernandez
>Priority: Minor
> Fix For: Myriad 0.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Closed] (MYRIAD-187) Update npm dependencies.

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-187.
-

> Update npm dependencies.
> 
>
> Key: MYRIAD-187
> URL: https://issues.apache.org/jira/browse/MYRIAD-187
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler
>Affects Versions: Myriad 0.1.0
>Reporter: DarinJ
>Assignee: Oscar Fernandez
>Priority: Minor
> Fix For: Myriad 0.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Closed] (MYRIAD-296) Build broken by Gulp Error

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-296.
-

> Build broken by Gulp Error
> --
>
> Key: MYRIAD-296
> URL: https://issues.apache.org/jira/browse/MYRIAD-296
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler, User Interface
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Assignee: Oscar Fernandez
>Priority: Major
>  Labels: build
> Fix For: Myriad 0.4.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> {noformat}
> $ ./gradlew gulp_build
> Parallel execution is an incubating feature.
> :myriad-scheduler:nodeSetup UP-TO-DATE
> :myriad-scheduler:installGulp UP-TO-DATE
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstallnpm WARN deprecated gulp-util@3.0.8: gulp-util is 
> deprecated - replace it, following the guidelines at 
> https://medium.com/gulpjs/gulp-util-ca3b1f
> 9f9ac5
> npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals 
> and will break at some point. Do not use it, and update to graceful-fs@4.x.
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN engine atob@2.1.2: wanted: {"node":">= 4.5.0"} (current: 
> {"node":"4.2.1","npm":"2.14.7"}) 
> gulp@3.8.11 node_modules/gulp
> ├── pretty-hrtime@0.2.2
> ├── interpret@0.3.10
> ├── deprecated@0.0.1
> ├── archy@1.0.0
> ├── tildify@1.2.0 (os-homedir@1.0.2)
> ├── minimist@1.2.0
> ├── v8flags@2.1.1 (user-home@1.1.1)
> ├── semver@4.3.6
> ├── chalk@0.5.1 (ansi-styles@1.1.0, escape-string-regexp@1.0.5, 
> supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
> ├── orchestrator@0.3.8 (stream-consume@0.1.1, sequencify@0.0.7, 
> end-of-stream@0.1.5)
> ├── gulp-util@3.0.8 (array-differ@1.0.0, beeper@1.1.1, 
> lodash._reescape@3.0.0, array-uniq@1.0.3, lodash._reevaluate@3.0.0, 
> object-assign@3.0.0, lodash._reinterpolate@3.0.0,
> replace-ext@0.0.1, dateformat@2.2.0, has-gulplog@0.1.0, vinyl@0.5.3, 
> chalk@1.1.3, gulplog@1.0.0, fancy-log@1.3.3, lodash.template@3.6.2, 
> multipipe@0.1.2, through2@2.0.5)
> ├── vinyl-fs@0.3.14 (strip-bom@1.0.0, defaults@1.0.3, vinyl@0.4.6, 
> graceful-fs@3.0.11, mkdirp@0.5.1, through2@0.6.5, glob-stream@3.1.18, 
> glob-watcher@0.0.6)
> └── liftoff@2.5.0 (flagged-respawn@1.0.1, rechoir@0.6.2, extend@3.0.2, 
> is-plain-object@2.0.4, object.map@1.0.1, fined@1.2.0, resolve@1.11.1, 
> findup-sync@2.0.0)
> :myriad-scheduler:gulp_build
> [20:04:49] Using gulpfile 
> ~/incubator-myriad/myriad-scheduler/src/main/resources/webapp/gulpfile.js
> [20:04:49] Starting 'clean'...
> [20:04:49] Finished 'clean' after 15 ms
> [20:04:49] Starting 'js'...
> [20:04:49] Finished 'js' after 29 ms
> [20:04:49] Starting 'html'...
> [20:04:49] Starting 'css'...
> [20:04:49] Starting 'img'...
> [20:04:49] Finished 'html' after 46 ms
> [20:04:49] Finished 'css' after 42 ms
> [20:04:50] Finished 'img' after 591 ms
> [20:04:50] Starting 'default'...
> [20:04:50] Finished 'default' after 17 μs
> [20:04:50] Starting 'build'...
> [20:04:50] Finished 'build' after 32 μs
> events.js:141
> throw er; // Unhandled 'error' event
> ^
> ReferenceError: Invalid left-hand side in assignment
> at module.exports 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/syntax-error/index.js:11:52)
> at DestroyableTransform._transform 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/index.js:613:19)
> at DestroyableTransform.Transform._read 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/l
> ib/_stream_transform.js:184:10)
> at DestroyableTransform.Transform._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/
> lib/_stream_transform.js:172:12)
> at Labeled.Pipeline._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resour

[jira] [Resolved] (MYRIAD-296) Build broken by Gulp Error

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-296.
---
Resolution: Fixed

> Build broken by Gulp Error
> --
>
> Key: MYRIAD-296
> URL: https://issues.apache.org/jira/browse/MYRIAD-296
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler, User Interface
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Assignee: Oscar Fernandez
>Priority: Major
>  Labels: build
> Fix For: Myriad 0.4.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> {noformat}
> $ ./gradlew gulp_build
> Parallel execution is an incubating feature.
> :myriad-scheduler:nodeSetup UP-TO-DATE
> :myriad-scheduler:installGulp UP-TO-DATE
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstallnpm WARN deprecated gulp-util@3.0.8: gulp-util is 
> deprecated - replace it, following the guidelines at 
> https://medium.com/gulpjs/gulp-util-ca3b1f
> 9f9ac5
> npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals 
> and will break at some point. Do not use it, and update to graceful-fs@4.x.
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN engine atob@2.1.2: wanted: {"node":">= 4.5.0"} (current: 
> {"node":"4.2.1","npm":"2.14.7"}) 
> gulp@3.8.11 node_modules/gulp
> ├── pretty-hrtime@0.2.2
> ├── interpret@0.3.10
> ├── deprecated@0.0.1
> ├── archy@1.0.0
> ├── tildify@1.2.0 (os-homedir@1.0.2)
> ├── minimist@1.2.0
> ├── v8flags@2.1.1 (user-home@1.1.1)
> ├── semver@4.3.6
> ├── chalk@0.5.1 (ansi-styles@1.1.0, escape-string-regexp@1.0.5, 
> supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
> ├── orchestrator@0.3.8 (stream-consume@0.1.1, sequencify@0.0.7, 
> end-of-stream@0.1.5)
> ├── gulp-util@3.0.8 (array-differ@1.0.0, beeper@1.1.1, 
> lodash._reescape@3.0.0, array-uniq@1.0.3, lodash._reevaluate@3.0.0, 
> object-assign@3.0.0, lodash._reinterpolate@3.0.0,
> replace-ext@0.0.1, dateformat@2.2.0, has-gulplog@0.1.0, vinyl@0.5.3, 
> chalk@1.1.3, gulplog@1.0.0, fancy-log@1.3.3, lodash.template@3.6.2, 
> multipipe@0.1.2, through2@2.0.5)
> ├── vinyl-fs@0.3.14 (strip-bom@1.0.0, defaults@1.0.3, vinyl@0.4.6, 
> graceful-fs@3.0.11, mkdirp@0.5.1, through2@0.6.5, glob-stream@3.1.18, 
> glob-watcher@0.0.6)
> └── liftoff@2.5.0 (flagged-respawn@1.0.1, rechoir@0.6.2, extend@3.0.2, 
> is-plain-object@2.0.4, object.map@1.0.1, fined@1.2.0, resolve@1.11.1, 
> findup-sync@2.0.0)
> :myriad-scheduler:gulp_build
> [20:04:49] Using gulpfile 
> ~/incubator-myriad/myriad-scheduler/src/main/resources/webapp/gulpfile.js
> [20:04:49] Starting 'clean'...
> [20:04:49] Finished 'clean' after 15 ms
> [20:04:49] Starting 'js'...
> [20:04:49] Finished 'js' after 29 ms
> [20:04:49] Starting 'html'...
> [20:04:49] Starting 'css'...
> [20:04:49] Starting 'img'...
> [20:04:49] Finished 'html' after 46 ms
> [20:04:49] Finished 'css' after 42 ms
> [20:04:50] Finished 'img' after 591 ms
> [20:04:50] Starting 'default'...
> [20:04:50] Finished 'default' after 17 μs
> [20:04:50] Starting 'build'...
> [20:04:50] Finished 'build' after 32 μs
> events.js:141
> throw er; // Unhandled 'error' event
> ^
> ReferenceError: Invalid left-hand side in assignment
> at module.exports 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/syntax-error/index.js:11:52)
> at DestroyableTransform._transform 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/index.js:613:19)
> at DestroyableTransform.Transform._read 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/l
> ib/_stream_transform.js:184:10)
> at DestroyableTransform.Transform._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/
> lib/_stream_transform.js:172:12)
> at Labeled.Pipeline._write 
> (/home/vagrant/incubator-myriad/myriad-s

[jira] [Reopened] (MYRIAD-296) Build broken by Gulp Error

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reopened MYRIAD-296:
---

> Build broken by Gulp Error
> --
>
> Key: MYRIAD-296
> URL: https://issues.apache.org/jira/browse/MYRIAD-296
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler, User Interface
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Assignee: Oscar Fernandez
>Priority: Major
>  Labels: build
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> {noformat}
> $ ./gradlew gulp_build
> Parallel execution is an incubating feature.
> :myriad-scheduler:nodeSetup UP-TO-DATE
> :myriad-scheduler:installGulp UP-TO-DATE
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstallnpm WARN deprecated gulp-util@3.0.8: gulp-util is 
> deprecated - replace it, following the guidelines at 
> https://medium.com/gulpjs/gulp-util-ca3b1f
> 9f9ac5
> npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals 
> and will break at some point. Do not use it, and update to graceful-fs@4.x.
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN engine atob@2.1.2: wanted: {"node":">= 4.5.0"} (current: 
> {"node":"4.2.1","npm":"2.14.7"}) 
> gulp@3.8.11 node_modules/gulp
> ├── pretty-hrtime@0.2.2
> ├── interpret@0.3.10
> ├── deprecated@0.0.1
> ├── archy@1.0.0
> ├── tildify@1.2.0 (os-homedir@1.0.2)
> ├── minimist@1.2.0
> ├── v8flags@2.1.1 (user-home@1.1.1)
> ├── semver@4.3.6
> ├── chalk@0.5.1 (ansi-styles@1.1.0, escape-string-regexp@1.0.5, 
> supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
> ├── orchestrator@0.3.8 (stream-consume@0.1.1, sequencify@0.0.7, 
> end-of-stream@0.1.5)
> ├── gulp-util@3.0.8 (array-differ@1.0.0, beeper@1.1.1, 
> lodash._reescape@3.0.0, array-uniq@1.0.3, lodash._reevaluate@3.0.0, 
> object-assign@3.0.0, lodash._reinterpolate@3.0.0,
> replace-ext@0.0.1, dateformat@2.2.0, has-gulplog@0.1.0, vinyl@0.5.3, 
> chalk@1.1.3, gulplog@1.0.0, fancy-log@1.3.3, lodash.template@3.6.2, 
> multipipe@0.1.2, through2@2.0.5)
> ├── vinyl-fs@0.3.14 (strip-bom@1.0.0, defaults@1.0.3, vinyl@0.4.6, 
> graceful-fs@3.0.11, mkdirp@0.5.1, through2@0.6.5, glob-stream@3.1.18, 
> glob-watcher@0.0.6)
> └── liftoff@2.5.0 (flagged-respawn@1.0.1, rechoir@0.6.2, extend@3.0.2, 
> is-plain-object@2.0.4, object.map@1.0.1, fined@1.2.0, resolve@1.11.1, 
> findup-sync@2.0.0)
> :myriad-scheduler:gulp_build
> [20:04:49] Using gulpfile 
> ~/incubator-myriad/myriad-scheduler/src/main/resources/webapp/gulpfile.js
> [20:04:49] Starting 'clean'...
> [20:04:49] Finished 'clean' after 15 ms
> [20:04:49] Starting 'js'...
> [20:04:49] Finished 'js' after 29 ms
> [20:04:49] Starting 'html'...
> [20:04:49] Starting 'css'...
> [20:04:49] Starting 'img'...
> [20:04:49] Finished 'html' after 46 ms
> [20:04:49] Finished 'css' after 42 ms
> [20:04:50] Finished 'img' after 591 ms
> [20:04:50] Starting 'default'...
> [20:04:50] Finished 'default' after 17 μs
> [20:04:50] Starting 'build'...
> [20:04:50] Finished 'build' after 32 μs
> events.js:141
> throw er; // Unhandled 'error' event
> ^
> ReferenceError: Invalid left-hand side in assignment
> at module.exports 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/syntax-error/index.js:11:52)
> at DestroyableTransform._transform 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/index.js:613:19)
> at DestroyableTransform.Transform._read 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/l
> ib/_stream_transform.js:184:10)
> at DestroyableTransform.Transform._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/
> lib/_stream_transform.js:172:12)
> at Labeled.Pipeline._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_mo

[jira] [Reopened] (MYRIAD-275) Upgrade front dependencies

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reopened MYRIAD-275:
---
  Assignee: Oscar Fernandez

> Upgrade front dependencies
> --
>
> Key: MYRIAD-275
> URL: https://issues.apache.org/jira/browse/MYRIAD-275
> Project: Myriad
>  Issue Type: Task
>  Components: User Interface
>Affects Versions: Myriad 0.4.0
>Reporter: Juan Pedro
>Assignee: Oscar Fernandez
>Priority: Major
>  Labels: build
> Fix For: Myriad 0.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (MYRIAD-275) Upgrade front dependencies

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-275.
---
Resolution: Fixed

> Upgrade front dependencies
> --
>
> Key: MYRIAD-275
> URL: https://issues.apache.org/jira/browse/MYRIAD-275
> Project: Myriad
>  Issue Type: Task
>  Components: User Interface
>Affects Versions: Myriad 0.4.0
>Reporter: Juan Pedro
>Assignee: Oscar Fernandez
>Priority: Major
>  Labels: build
> Fix For: Myriad 0.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Closed] (MYRIAD-275) Upgrade front dependencies

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-275.
-

> Upgrade front dependencies
> --
>
> Key: MYRIAD-275
> URL: https://issues.apache.org/jira/browse/MYRIAD-275
> Project: Myriad
>  Issue Type: Task
>  Components: User Interface
>Affects Versions: Myriad 0.4.0
>Reporter: Juan Pedro
>Assignee: Oscar Fernandez
>Priority: Major
>  Labels: build
> Fix For: Myriad 0.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (MYRIAD-273) upgrade gradle version

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-273.
---
Resolution: Fixed

[https://github.com/apache/incubator-myriad/commit/a73acb4ad2faecedb8e00bcf05d6c477565cd99b]

> upgrade gradle version
> --
>
> Key: MYRIAD-273
> URL: https://issues.apache.org/jira/browse/MYRIAD-273
> Project: Myriad
>  Issue Type: Wish
>Affects Versions: Myriad 0.4.0
>Reporter: Juan Pedro
>Assignee: Oscar Fernandez
>Priority: Minor
> Fix For: Myriad 0.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Closed] (MYRIAD-187) Update npm dependencies.

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-187.
-

> Update npm dependencies.
> 
>
> Key: MYRIAD-187
> URL: https://issues.apache.org/jira/browse/MYRIAD-187
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler
>Affects Versions: Myriad 0.1.0
>Reporter: DarinJ
>Assignee: Oscar Fernandez
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (MYRIAD-187) Update npm dependencies.

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-187.
---
Resolution: Fixed

[https://github.com/apache/incubator-myriad/commit/a73acb4ad2faecedb8e00bcf05d6c477565cd99b]

> Update npm dependencies.
> 
>
> Key: MYRIAD-187
> URL: https://issues.apache.org/jira/browse/MYRIAD-187
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler
>Affects Versions: Myriad 0.1.0
>Reporter: DarinJ
>Assignee: Oscar Fernandez
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Assigned] (MYRIAD-273) upgrade gradle version

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reassigned MYRIAD-273:
-

Assignee: Oscar Fernandez

> upgrade gradle version
> --
>
> Key: MYRIAD-273
> URL: https://issues.apache.org/jira/browse/MYRIAD-273
> Project: Myriad
>  Issue Type: Wish
>Affects Versions: Myriad 0.4.0
>Reporter: Juan Pedro
>Assignee: Oscar Fernandez
>Priority: Minor
> Fix For: Myriad 0.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Closed] (MYRIAD-273) upgrade gradle version

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-273.
-

> upgrade gradle version
> --
>
> Key: MYRIAD-273
> URL: https://issues.apache.org/jira/browse/MYRIAD-273
> Project: Myriad
>  Issue Type: Wish
>Affects Versions: Myriad 0.4.0
>Reporter: Juan Pedro
>Assignee: Oscar Fernandez
>Priority: Minor
> Fix For: Myriad 0.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (MYRIAD-275) Upgrade front dependencies

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-275.
---
Resolution: Fixed

[https://github.com/apache/incubator-myriad/commit/a73acb4ad2faecedb8e00bcf05d6c477565cd99b]

> Upgrade front dependencies
> --
>
> Key: MYRIAD-275
> URL: https://issues.apache.org/jira/browse/MYRIAD-275
> Project: Myriad
>  Issue Type: Task
>  Components: User Interface
>Affects Versions: Myriad 0.4.0
>Reporter: Juan Pedro
>Priority: Major
>  Labels: build
> Fix For: Myriad 0.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (MYRIAD-296) Build broken by Gulp Error

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-296.
---
Resolution: Fixed

[https://github.com/apache/incubator-myriad/commit/a73acb4ad2faecedb8e00bcf05d6c477565cd99b]

> Build broken by Gulp Error
> --
>
> Key: MYRIAD-296
> URL: https://issues.apache.org/jira/browse/MYRIAD-296
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler, User Interface
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Assignee: Oscar Fernandez
>Priority: Major
>  Labels: build
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> {noformat}
> $ ./gradlew gulp_build
> Parallel execution is an incubating feature.
> :myriad-scheduler:nodeSetup UP-TO-DATE
> :myriad-scheduler:installGulp UP-TO-DATE
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstallnpm WARN deprecated gulp-util@3.0.8: gulp-util is 
> deprecated - replace it, following the guidelines at 
> https://medium.com/gulpjs/gulp-util-ca3b1f
> 9f9ac5
> npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals 
> and will break at some point. Do not use it, and update to graceful-fs@4.x.
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN engine atob@2.1.2: wanted: {"node":">= 4.5.0"} (current: 
> {"node":"4.2.1","npm":"2.14.7"}) 
> gulp@3.8.11 node_modules/gulp
> ├── pretty-hrtime@0.2.2
> ├── interpret@0.3.10
> ├── deprecated@0.0.1
> ├── archy@1.0.0
> ├── tildify@1.2.0 (os-homedir@1.0.2)
> ├── minimist@1.2.0
> ├── v8flags@2.1.1 (user-home@1.1.1)
> ├── semver@4.3.6
> ├── chalk@0.5.1 (ansi-styles@1.1.0, escape-string-regexp@1.0.5, 
> supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
> ├── orchestrator@0.3.8 (stream-consume@0.1.1, sequencify@0.0.7, 
> end-of-stream@0.1.5)
> ├── gulp-util@3.0.8 (array-differ@1.0.0, beeper@1.1.1, 
> lodash._reescape@3.0.0, array-uniq@1.0.3, lodash._reevaluate@3.0.0, 
> object-assign@3.0.0, lodash._reinterpolate@3.0.0,
> replace-ext@0.0.1, dateformat@2.2.0, has-gulplog@0.1.0, vinyl@0.5.3, 
> chalk@1.1.3, gulplog@1.0.0, fancy-log@1.3.3, lodash.template@3.6.2, 
> multipipe@0.1.2, through2@2.0.5)
> ├── vinyl-fs@0.3.14 (strip-bom@1.0.0, defaults@1.0.3, vinyl@0.4.6, 
> graceful-fs@3.0.11, mkdirp@0.5.1, through2@0.6.5, glob-stream@3.1.18, 
> glob-watcher@0.0.6)
> └── liftoff@2.5.0 (flagged-respawn@1.0.1, rechoir@0.6.2, extend@3.0.2, 
> is-plain-object@2.0.4, object.map@1.0.1, fined@1.2.0, resolve@1.11.1, 
> findup-sync@2.0.0)
> :myriad-scheduler:gulp_build
> [20:04:49] Using gulpfile 
> ~/incubator-myriad/myriad-scheduler/src/main/resources/webapp/gulpfile.js
> [20:04:49] Starting 'clean'...
> [20:04:49] Finished 'clean' after 15 ms
> [20:04:49] Starting 'js'...
> [20:04:49] Finished 'js' after 29 ms
> [20:04:49] Starting 'html'...
> [20:04:49] Starting 'css'...
> [20:04:49] Starting 'img'...
> [20:04:49] Finished 'html' after 46 ms
> [20:04:49] Finished 'css' after 42 ms
> [20:04:50] Finished 'img' after 591 ms
> [20:04:50] Starting 'default'...
> [20:04:50] Finished 'default' after 17 μs
> [20:04:50] Starting 'build'...
> [20:04:50] Finished 'build' after 32 μs
> events.js:141
> throw er; // Unhandled 'error' event
> ^
> ReferenceError: Invalid left-hand side in assignment
> at module.exports 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/syntax-error/index.js:11:52)
> at DestroyableTransform._transform 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/index.js:613:19)
> at DestroyableTransform.Transform._read 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/l
> ib/_stream_transform.js:184:10)
> at DestroyableTransform.Transform._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/
> lib/_stream_transform.js:172:12)
> at Labeled.

[jira] [Closed] (MYRIAD-296) Build broken by Gulp Error

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-296.
-

> Build broken by Gulp Error
> --
>
> Key: MYRIAD-296
> URL: https://issues.apache.org/jira/browse/MYRIAD-296
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler, User Interface
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Assignee: Oscar Fernandez
>Priority: Major
>  Labels: build
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> {noformat}
> $ ./gradlew gulp_build
> Parallel execution is an incubating feature.
> :myriad-scheduler:nodeSetup UP-TO-DATE
> :myriad-scheduler:installGulp UP-TO-DATE
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstallnpm WARN deprecated gulp-util@3.0.8: gulp-util is 
> deprecated - replace it, following the guidelines at 
> https://medium.com/gulpjs/gulp-util-ca3b1f
> 9f9ac5
> npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals 
> and will break at some point. Do not use it, and update to graceful-fs@4.x.
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN engine atob@2.1.2: wanted: {"node":">= 4.5.0"} (current: 
> {"node":"4.2.1","npm":"2.14.7"}) 
> gulp@3.8.11 node_modules/gulp
> ├── pretty-hrtime@0.2.2
> ├── interpret@0.3.10
> ├── deprecated@0.0.1
> ├── archy@1.0.0
> ├── tildify@1.2.0 (os-homedir@1.0.2)
> ├── minimist@1.2.0
> ├── v8flags@2.1.1 (user-home@1.1.1)
> ├── semver@4.3.6
> ├── chalk@0.5.1 (ansi-styles@1.1.0, escape-string-regexp@1.0.5, 
> supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
> ├── orchestrator@0.3.8 (stream-consume@0.1.1, sequencify@0.0.7, 
> end-of-stream@0.1.5)
> ├── gulp-util@3.0.8 (array-differ@1.0.0, beeper@1.1.1, 
> lodash._reescape@3.0.0, array-uniq@1.0.3, lodash._reevaluate@3.0.0, 
> object-assign@3.0.0, lodash._reinterpolate@3.0.0,
> replace-ext@0.0.1, dateformat@2.2.0, has-gulplog@0.1.0, vinyl@0.5.3, 
> chalk@1.1.3, gulplog@1.0.0, fancy-log@1.3.3, lodash.template@3.6.2, 
> multipipe@0.1.2, through2@2.0.5)
> ├── vinyl-fs@0.3.14 (strip-bom@1.0.0, defaults@1.0.3, vinyl@0.4.6, 
> graceful-fs@3.0.11, mkdirp@0.5.1, through2@0.6.5, glob-stream@3.1.18, 
> glob-watcher@0.0.6)
> └── liftoff@2.5.0 (flagged-respawn@1.0.1, rechoir@0.6.2, extend@3.0.2, 
> is-plain-object@2.0.4, object.map@1.0.1, fined@1.2.0, resolve@1.11.1, 
> findup-sync@2.0.0)
> :myriad-scheduler:gulp_build
> [20:04:49] Using gulpfile 
> ~/incubator-myriad/myriad-scheduler/src/main/resources/webapp/gulpfile.js
> [20:04:49] Starting 'clean'...
> [20:04:49] Finished 'clean' after 15 ms
> [20:04:49] Starting 'js'...
> [20:04:49] Finished 'js' after 29 ms
> [20:04:49] Starting 'html'...
> [20:04:49] Starting 'css'...
> [20:04:49] Starting 'img'...
> [20:04:49] Finished 'html' after 46 ms
> [20:04:49] Finished 'css' after 42 ms
> [20:04:50] Finished 'img' after 591 ms
> [20:04:50] Starting 'default'...
> [20:04:50] Finished 'default' after 17 μs
> [20:04:50] Starting 'build'...
> [20:04:50] Finished 'build' after 32 μs
> events.js:141
> throw er; // Unhandled 'error' event
> ^
> ReferenceError: Invalid left-hand side in assignment
> at module.exports 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/syntax-error/index.js:11:52)
> at DestroyableTransform._transform 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/index.js:613:19)
> at DestroyableTransform.Transform._read 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/l
> ib/_stream_transform.js:184:10)
> at DestroyableTransform.Transform._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/
> lib/_stream_transform.js:172:12)
> at Labeled.Pipeline._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_mo

[jira] [Closed] (MYRIAD-275) Upgrade front dependencies

2019-07-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-275.
-

> Upgrade front dependencies
> --
>
> Key: MYRIAD-275
> URL: https://issues.apache.org/jira/browse/MYRIAD-275
> Project: Myriad
>  Issue Type: Task
>  Components: User Interface
>Affects Versions: Myriad 0.4.0
>Reporter: Juan Pedro
>Priority: Major
>  Labels: build
> Fix For: Myriad 0.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (MYRIAD-296) Build broken by Gulp Error

2019-07-15 Thread Javi Roman (JIRA)


[ 
https://issues.apache.org/jira/browse/MYRIAD-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885249#comment-16885249
 ] 

Javi Roman commented on MYRIAD-296:
---

And:
 * react-bootstrap 0.16.1 -> 0.32.4

It's not a minor change ;)

> Build broken by Gulp Error
> --
>
> Key: MYRIAD-296
> URL: https://issues.apache.org/jira/browse/MYRIAD-296
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler, User Interface
>Affects Versions: Myriad 0.4.0
>Reporter: Javi Roman
>Assignee: Oscar Fernandez
>Priority: Major
>  Labels: build
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> {noformat}
> $ ./gradlew gulp_build
> Parallel execution is an incubating feature.
> :myriad-scheduler:nodeSetup UP-TO-DATE
> :myriad-scheduler:installGulp UP-TO-DATE
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstallnpm WARN deprecated gulp-util@3.0.8: gulp-util is 
> deprecated - replace it, following the guidelines at 
> https://medium.com/gulpjs/gulp-util-ca3b1f
> 9f9ac5
> npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals 
> and will break at some point. Do not use it, and update to graceful-fs@4.x.
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN engine atob@2.1.2: wanted: {"node":">= 4.5.0"} (current: 
> {"node":"4.2.1","npm":"2.14.7"}) 
> gulp@3.8.11 node_modules/gulp
> ├── pretty-hrtime@0.2.2
> ├── interpret@0.3.10
> ├── deprecated@0.0.1
> ├── archy@1.0.0
> ├── tildify@1.2.0 (os-homedir@1.0.2)
> ├── minimist@1.2.0
> ├── v8flags@2.1.1 (user-home@1.1.1)
> ├── semver@4.3.6
> ├── chalk@0.5.1 (ansi-styles@1.1.0, escape-string-regexp@1.0.5, 
> supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
> ├── orchestrator@0.3.8 (stream-consume@0.1.1, sequencify@0.0.7, 
> end-of-stream@0.1.5)
> ├── gulp-util@3.0.8 (array-differ@1.0.0, beeper@1.1.1, 
> lodash._reescape@3.0.0, array-uniq@1.0.3, lodash._reevaluate@3.0.0, 
> object-assign@3.0.0, lodash._reinterpolate@3.0.0,
> replace-ext@0.0.1, dateformat@2.2.0, has-gulplog@0.1.0, vinyl@0.5.3, 
> chalk@1.1.3, gulplog@1.0.0, fancy-log@1.3.3, lodash.template@3.6.2, 
> multipipe@0.1.2, through2@2.0.5)
> ├── vinyl-fs@0.3.14 (strip-bom@1.0.0, defaults@1.0.3, vinyl@0.4.6, 
> graceful-fs@3.0.11, mkdirp@0.5.1, through2@0.6.5, glob-stream@3.1.18, 
> glob-watcher@0.0.6)
> └── liftoff@2.5.0 (flagged-respawn@1.0.1, rechoir@0.6.2, extend@3.0.2, 
> is-plain-object@2.0.4, object.map@1.0.1, fined@1.2.0, resolve@1.11.1, 
> findup-sync@2.0.0)
> :myriad-scheduler:gulp_build
> [20:04:49] Using gulpfile 
> ~/incubator-myriad/myriad-scheduler/src/main/resources/webapp/gulpfile.js
> [20:04:49] Starting 'clean'...
> [20:04:49] Finished 'clean' after 15 ms
> [20:04:49] Starting 'js'...
> [20:04:49] Finished 'js' after 29 ms
> [20:04:49] Starting 'html'...
> [20:04:49] Starting 'css'...
> [20:04:49] Starting 'img'...
> [20:04:49] Finished 'html' after 46 ms
> [20:04:49] Finished 'css' after 42 ms
> [20:04:50] Finished 'img' after 591 ms
> [20:04:50] Starting 'default'...
> [20:04:50] Finished 'default' after 17 μs
> [20:04:50] Starting 'build'...
> [20:04:50] Finished 'build' after 32 μs
> events.js:141
> throw er; // Unhandled 'error' event
> ^
> ReferenceError: Invalid left-hand side in assignment
> at module.exports 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/syntax-error/index.js:11:52)
> at DestroyableTransform._transform 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/index.js:613:19)
> at DestroyableTransform.Transform._read 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/l
> ib/_stream_transform.js:184:10)
> at DestroyableTransform.Transform._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/
> lib/_stream_transform.js:172:12)
> at Labeled.Pipeline._write 
> (/

[jira] [Assigned] (MYRIAD-296) Build broken by Gulp Error

2019-07-15 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reassigned MYRIAD-296:
-

Assignee: Javi Roman  (was: Oscar Fernandez)

> Build broken by Gulp Error
> --
>
> Key: MYRIAD-296
> URL: https://issues.apache.org/jira/browse/MYRIAD-296
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler, User Interface
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Assignee: Javi Roman
>Priority: Major
>  Labels: build
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> {noformat}
> $ ./gradlew gulp_build
> Parallel execution is an incubating feature.
> :myriad-scheduler:nodeSetup UP-TO-DATE
> :myriad-scheduler:installGulp UP-TO-DATE
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstallnpm WARN deprecated gulp-util@3.0.8: gulp-util is 
> deprecated - replace it, following the guidelines at 
> https://medium.com/gulpjs/gulp-util-ca3b1f
> 9f9ac5
> npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals 
> and will break at some point. Do not use it, and update to graceful-fs@4.x.
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN engine atob@2.1.2: wanted: {"node":">= 4.5.0"} (current: 
> {"node":"4.2.1","npm":"2.14.7"}) 
> gulp@3.8.11 node_modules/gulp
> ├── pretty-hrtime@0.2.2
> ├── interpret@0.3.10
> ├── deprecated@0.0.1
> ├── archy@1.0.0
> ├── tildify@1.2.0 (os-homedir@1.0.2)
> ├── minimist@1.2.0
> ├── v8flags@2.1.1 (user-home@1.1.1)
> ├── semver@4.3.6
> ├── chalk@0.5.1 (ansi-styles@1.1.0, escape-string-regexp@1.0.5, 
> supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
> ├── orchestrator@0.3.8 (stream-consume@0.1.1, sequencify@0.0.7, 
> end-of-stream@0.1.5)
> ├── gulp-util@3.0.8 (array-differ@1.0.0, beeper@1.1.1, 
> lodash._reescape@3.0.0, array-uniq@1.0.3, lodash._reevaluate@3.0.0, 
> object-assign@3.0.0, lodash._reinterpolate@3.0.0,
> replace-ext@0.0.1, dateformat@2.2.0, has-gulplog@0.1.0, vinyl@0.5.3, 
> chalk@1.1.3, gulplog@1.0.0, fancy-log@1.3.3, lodash.template@3.6.2, 
> multipipe@0.1.2, through2@2.0.5)
> ├── vinyl-fs@0.3.14 (strip-bom@1.0.0, defaults@1.0.3, vinyl@0.4.6, 
> graceful-fs@3.0.11, mkdirp@0.5.1, through2@0.6.5, glob-stream@3.1.18, 
> glob-watcher@0.0.6)
> └── liftoff@2.5.0 (flagged-respawn@1.0.1, rechoir@0.6.2, extend@3.0.2, 
> is-plain-object@2.0.4, object.map@1.0.1, fined@1.2.0, resolve@1.11.1, 
> findup-sync@2.0.0)
> :myriad-scheduler:gulp_build
> [20:04:49] Using gulpfile 
> ~/incubator-myriad/myriad-scheduler/src/main/resources/webapp/gulpfile.js
> [20:04:49] Starting 'clean'...
> [20:04:49] Finished 'clean' after 15 ms
> [20:04:49] Starting 'js'...
> [20:04:49] Finished 'js' after 29 ms
> [20:04:49] Starting 'html'...
> [20:04:49] Starting 'css'...
> [20:04:49] Starting 'img'...
> [20:04:49] Finished 'html' after 46 ms
> [20:04:49] Finished 'css' after 42 ms
> [20:04:50] Finished 'img' after 591 ms
> [20:04:50] Starting 'default'...
> [20:04:50] Finished 'default' after 17 μs
> [20:04:50] Starting 'build'...
> [20:04:50] Finished 'build' after 32 μs
> events.js:141
> throw er; // Unhandled 'error' event
> ^
> ReferenceError: Invalid left-hand side in assignment
> at module.exports 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/syntax-error/index.js:11:52)
> at DestroyableTransform._transform 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/index.js:613:19)
> at DestroyableTransform.Transform._read 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/l
> ib/_stream_transform.js:184:10)
> at DestroyableTransform.Transform._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/
> lib/_stream_transform.js:172:12)
> at Labeled.Pipeline._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resou

[jira] [Assigned] (MYRIAD-296) Build broken by Gulp Error

2019-07-15 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reassigned MYRIAD-296:
-

Assignee: Oscar Fernandez  (was: Javi Roman)

> Build broken by Gulp Error
> --
>
> Key: MYRIAD-296
> URL: https://issues.apache.org/jira/browse/MYRIAD-296
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler, User Interface
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Assignee: Oscar Fernandez
>Priority: Major
>  Labels: build
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> {noformat}
> $ ./gradlew gulp_build
> Parallel execution is an incubating feature.
> :myriad-scheduler:nodeSetup UP-TO-DATE
> :myriad-scheduler:installGulp UP-TO-DATE
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstallnpm WARN deprecated gulp-util@3.0.8: gulp-util is 
> deprecated - replace it, following the guidelines at 
> https://medium.com/gulpjs/gulp-util-ca3b1f
> 9f9ac5
> npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals 
> and will break at some point. Do not use it, and update to graceful-fs@4.x.
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN engine atob@2.1.2: wanted: {"node":">= 4.5.0"} (current: 
> {"node":"4.2.1","npm":"2.14.7"}) 
> gulp@3.8.11 node_modules/gulp
> ├── pretty-hrtime@0.2.2
> ├── interpret@0.3.10
> ├── deprecated@0.0.1
> ├── archy@1.0.0
> ├── tildify@1.2.0 (os-homedir@1.0.2)
> ├── minimist@1.2.0
> ├── v8flags@2.1.1 (user-home@1.1.1)
> ├── semver@4.3.6
> ├── chalk@0.5.1 (ansi-styles@1.1.0, escape-string-regexp@1.0.5, 
> supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
> ├── orchestrator@0.3.8 (stream-consume@0.1.1, sequencify@0.0.7, 
> end-of-stream@0.1.5)
> ├── gulp-util@3.0.8 (array-differ@1.0.0, beeper@1.1.1, 
> lodash._reescape@3.0.0, array-uniq@1.0.3, lodash._reevaluate@3.0.0, 
> object-assign@3.0.0, lodash._reinterpolate@3.0.0,
> replace-ext@0.0.1, dateformat@2.2.0, has-gulplog@0.1.0, vinyl@0.5.3, 
> chalk@1.1.3, gulplog@1.0.0, fancy-log@1.3.3, lodash.template@3.6.2, 
> multipipe@0.1.2, through2@2.0.5)
> ├── vinyl-fs@0.3.14 (strip-bom@1.0.0, defaults@1.0.3, vinyl@0.4.6, 
> graceful-fs@3.0.11, mkdirp@0.5.1, through2@0.6.5, glob-stream@3.1.18, 
> glob-watcher@0.0.6)
> └── liftoff@2.5.0 (flagged-respawn@1.0.1, rechoir@0.6.2, extend@3.0.2, 
> is-plain-object@2.0.4, object.map@1.0.1, fined@1.2.0, resolve@1.11.1, 
> findup-sync@2.0.0)
> :myriad-scheduler:gulp_build
> [20:04:49] Using gulpfile 
> ~/incubator-myriad/myriad-scheduler/src/main/resources/webapp/gulpfile.js
> [20:04:49] Starting 'clean'...
> [20:04:49] Finished 'clean' after 15 ms
> [20:04:49] Starting 'js'...
> [20:04:49] Finished 'js' after 29 ms
> [20:04:49] Starting 'html'...
> [20:04:49] Starting 'css'...
> [20:04:49] Starting 'img'...
> [20:04:49] Finished 'html' after 46 ms
> [20:04:49] Finished 'css' after 42 ms
> [20:04:50] Finished 'img' after 591 ms
> [20:04:50] Starting 'default'...
> [20:04:50] Finished 'default' after 17 μs
> [20:04:50] Starting 'build'...
> [20:04:50] Finished 'build' after 32 μs
> events.js:141
> throw er; // Unhandled 'error' event
> ^
> ReferenceError: Invalid left-hand side in assignment
> at module.exports 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/syntax-error/index.js:11:52)
> at DestroyableTransform._transform 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/index.js:613:19)
> at DestroyableTransform.Transform._read 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/l
> ib/_stream_transform.js:184:10)
> at DestroyableTransform.Transform._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/
> lib/_stream_transform.js:172:12)
> at Labeled.Pipeline._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/mai

[jira] [Comment Edited] (MYRIAD-296) Build broken by Gulp Error

2019-07-04 Thread Javi Roman (JIRA)


[ 
https://issues.apache.org/jira/browse/MYRIAD-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878524#comment-16878524
 ] 

Javi Roman edited comment on MYRIAD-296 at 7/4/19 11:30 AM:


This issue is related with:

 

https://issues.apache.org/jira/browse/MYRIAD-275

https://issues.apache.org/jira/browse/MYRIAD-273

https://issues.apache.org/jira/browse/MYRIAD-187

 

Closing this issue, it will close all of them.


was (Author: javiroman):
This issue is related with:

 

https://issues.apache.org/jira/browse/MYRIAD-275

https://issues.apache.org/jira/browse/MYRIAD-273

https://issues.apache.org/jira/browse/MYRIAD-187

 

Closing this issue, it will close them.

> Build broken by Gulp Error
> --
>
> Key: MYRIAD-296
> URL: https://issues.apache.org/jira/browse/MYRIAD-296
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler, User Interface
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Assignee: Oscar Fernandez
>Priority: Major
>  Labels: build
>
> {noformat}
> $ ./gradlew gulp_build
> Parallel execution is an incubating feature.
> :myriad-scheduler:nodeSetup UP-TO-DATE
> :myriad-scheduler:installGulp UP-TO-DATE
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstallnpm WARN deprecated gulp-util@3.0.8: gulp-util is 
> deprecated - replace it, following the guidelines at 
> https://medium.com/gulpjs/gulp-util-ca3b1f
> 9f9ac5
> npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals 
> and will break at some point. Do not use it, and update to graceful-fs@4.x.
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN engine atob@2.1.2: wanted: {"node":">= 4.5.0"} (current: 
> {"node":"4.2.1","npm":"2.14.7"}) 
> gulp@3.8.11 node_modules/gulp
> ├── pretty-hrtime@0.2.2
> ├── interpret@0.3.10
> ├── deprecated@0.0.1
> ├── archy@1.0.0
> ├── tildify@1.2.0 (os-homedir@1.0.2)
> ├── minimist@1.2.0
> ├── v8flags@2.1.1 (user-home@1.1.1)
> ├── semver@4.3.6
> ├── chalk@0.5.1 (ansi-styles@1.1.0, escape-string-regexp@1.0.5, 
> supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
> ├── orchestrator@0.3.8 (stream-consume@0.1.1, sequencify@0.0.7, 
> end-of-stream@0.1.5)
> ├── gulp-util@3.0.8 (array-differ@1.0.0, beeper@1.1.1, 
> lodash._reescape@3.0.0, array-uniq@1.0.3, lodash._reevaluate@3.0.0, 
> object-assign@3.0.0, lodash._reinterpolate@3.0.0,
> replace-ext@0.0.1, dateformat@2.2.0, has-gulplog@0.1.0, vinyl@0.5.3, 
> chalk@1.1.3, gulplog@1.0.0, fancy-log@1.3.3, lodash.template@3.6.2, 
> multipipe@0.1.2, through2@2.0.5)
> ├── vinyl-fs@0.3.14 (strip-bom@1.0.0, defaults@1.0.3, vinyl@0.4.6, 
> graceful-fs@3.0.11, mkdirp@0.5.1, through2@0.6.5, glob-stream@3.1.18, 
> glob-watcher@0.0.6)
> └── liftoff@2.5.0 (flagged-respawn@1.0.1, rechoir@0.6.2, extend@3.0.2, 
> is-plain-object@2.0.4, object.map@1.0.1, fined@1.2.0, resolve@1.11.1, 
> findup-sync@2.0.0)
> :myriad-scheduler:gulp_build
> [20:04:49] Using gulpfile 
> ~/incubator-myriad/myriad-scheduler/src/main/resources/webapp/gulpfile.js
> [20:04:49] Starting 'clean'...
> [20:04:49] Finished 'clean' after 15 ms
> [20:04:49] Starting 'js'...
> [20:04:49] Finished 'js' after 29 ms
> [20:04:49] Starting 'html'...
> [20:04:49] Starting 'css'...
> [20:04:49] Starting 'img'...
> [20:04:49] Finished 'html' after 46 ms
> [20:04:49] Finished 'css' after 42 ms
> [20:04:50] Finished 'img' after 591 ms
> [20:04:50] Starting 'default'...
> [20:04:50] Finished 'default' after 17 μs
> [20:04:50] Starting 'build'...
> [20:04:50] Finished 'build' after 32 μs
> events.js:141
> throw er; // Unhandled 'error' event
> ^
> ReferenceError: Invalid left-hand side in assignment
> at module.exports 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/syntax-error/index.js:11:52)
> at DestroyableTransform._transform 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/index.js:613:19)
> at DestroyableTransform.Transform._read 
> (/home/vagrant/in

[jira] [Commented] (MYRIAD-296) Build broken by Gulp Error

2019-07-04 Thread Javi Roman (JIRA)


[ 
https://issues.apache.org/jira/browse/MYRIAD-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878524#comment-16878524
 ] 

Javi Roman commented on MYRIAD-296:
---

This issue is related with:

 

https://issues.apache.org/jira/browse/MYRIAD-275

https://issues.apache.org/jira/browse/MYRIAD-273

https://issues.apache.org/jira/browse/MYRIAD-187

 

Closing this issue, it will close them.

> Build broken by Gulp Error
> --
>
> Key: MYRIAD-296
> URL: https://issues.apache.org/jira/browse/MYRIAD-296
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler, User Interface
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Assignee: Oscar Fernandez
>Priority: Major
>  Labels: build
>
> {noformat}
> $ ./gradlew gulp_build
> Parallel execution is an incubating feature.
> :myriad-scheduler:nodeSetup UP-TO-DATE
> :myriad-scheduler:installGulp UP-TO-DATE
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstallnpm WARN deprecated gulp-util@3.0.8: gulp-util is 
> deprecated - replace it, following the guidelines at 
> https://medium.com/gulpjs/gulp-util-ca3b1f
> 9f9ac5
> npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals 
> and will break at some point. Do not use it, and update to graceful-fs@4.x.
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN engine atob@2.1.2: wanted: {"node":">= 4.5.0"} (current: 
> {"node":"4.2.1","npm":"2.14.7"}) 
> gulp@3.8.11 node_modules/gulp
> ├── pretty-hrtime@0.2.2
> ├── interpret@0.3.10
> ├── deprecated@0.0.1
> ├── archy@1.0.0
> ├── tildify@1.2.0 (os-homedir@1.0.2)
> ├── minimist@1.2.0
> ├── v8flags@2.1.1 (user-home@1.1.1)
> ├── semver@4.3.6
> ├── chalk@0.5.1 (ansi-styles@1.1.0, escape-string-regexp@1.0.5, 
> supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
> ├── orchestrator@0.3.8 (stream-consume@0.1.1, sequencify@0.0.7, 
> end-of-stream@0.1.5)
> ├── gulp-util@3.0.8 (array-differ@1.0.0, beeper@1.1.1, 
> lodash._reescape@3.0.0, array-uniq@1.0.3, lodash._reevaluate@3.0.0, 
> object-assign@3.0.0, lodash._reinterpolate@3.0.0,
> replace-ext@0.0.1, dateformat@2.2.0, has-gulplog@0.1.0, vinyl@0.5.3, 
> chalk@1.1.3, gulplog@1.0.0, fancy-log@1.3.3, lodash.template@3.6.2, 
> multipipe@0.1.2, through2@2.0.5)
> ├── vinyl-fs@0.3.14 (strip-bom@1.0.0, defaults@1.0.3, vinyl@0.4.6, 
> graceful-fs@3.0.11, mkdirp@0.5.1, through2@0.6.5, glob-stream@3.1.18, 
> glob-watcher@0.0.6)
> └── liftoff@2.5.0 (flagged-respawn@1.0.1, rechoir@0.6.2, extend@3.0.2, 
> is-plain-object@2.0.4, object.map@1.0.1, fined@1.2.0, resolve@1.11.1, 
> findup-sync@2.0.0)
> :myriad-scheduler:gulp_build
> [20:04:49] Using gulpfile 
> ~/incubator-myriad/myriad-scheduler/src/main/resources/webapp/gulpfile.js
> [20:04:49] Starting 'clean'...
> [20:04:49] Finished 'clean' after 15 ms
> [20:04:49] Starting 'js'...
> [20:04:49] Finished 'js' after 29 ms
> [20:04:49] Starting 'html'...
> [20:04:49] Starting 'css'...
> [20:04:49] Starting 'img'...
> [20:04:49] Finished 'html' after 46 ms
> [20:04:49] Finished 'css' after 42 ms
> [20:04:50] Finished 'img' after 591 ms
> [20:04:50] Starting 'default'...
> [20:04:50] Finished 'default' after 17 μs
> [20:04:50] Starting 'build'...
> [20:04:50] Finished 'build' after 32 μs
> events.js:141
> throw er; // Unhandled 'error' event
> ^
> ReferenceError: Invalid left-hand side in assignment
> at module.exports 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/syntax-error/index.js:11:52)
> at DestroyableTransform._transform 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/index.js:613:19)
> at DestroyableTransform.Transform._read 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/l
> ib/_stream_transform.js:184:10)
> at DestroyableTransform.Transform._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_module

[jira] [Updated] (MYRIAD-296) Build broken by Gulp Error

2019-07-04 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman updated MYRIAD-296:
--
Component/s: User Interface

> Build broken by Gulp Error
> --
>
> Key: MYRIAD-296
> URL: https://issues.apache.org/jira/browse/MYRIAD-296
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler, User Interface
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Assignee: Oscar Fernandez
>Priority: Major
>  Labels: build
>
> {noformat}
> $ ./gradlew gulp_build
> Parallel execution is an incubating feature.
> :myriad-scheduler:nodeSetup UP-TO-DATE
> :myriad-scheduler:installGulp UP-TO-DATE
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstallnpm WARN deprecated gulp-util@3.0.8: gulp-util is 
> deprecated - replace it, following the guidelines at 
> https://medium.com/gulpjs/gulp-util-ca3b1f
> 9f9ac5
> npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals 
> and will break at some point. Do not use it, and update to graceful-fs@4.x.
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN engine atob@2.1.2: wanted: {"node":">= 4.5.0"} (current: 
> {"node":"4.2.1","npm":"2.14.7"}) 
> gulp@3.8.11 node_modules/gulp
> ├── pretty-hrtime@0.2.2
> ├── interpret@0.3.10
> ├── deprecated@0.0.1
> ├── archy@1.0.0
> ├── tildify@1.2.0 (os-homedir@1.0.2)
> ├── minimist@1.2.0
> ├── v8flags@2.1.1 (user-home@1.1.1)
> ├── semver@4.3.6
> ├── chalk@0.5.1 (ansi-styles@1.1.0, escape-string-regexp@1.0.5, 
> supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
> ├── orchestrator@0.3.8 (stream-consume@0.1.1, sequencify@0.0.7, 
> end-of-stream@0.1.5)
> ├── gulp-util@3.0.8 (array-differ@1.0.0, beeper@1.1.1, 
> lodash._reescape@3.0.0, array-uniq@1.0.3, lodash._reevaluate@3.0.0, 
> object-assign@3.0.0, lodash._reinterpolate@3.0.0,
> replace-ext@0.0.1, dateformat@2.2.0, has-gulplog@0.1.0, vinyl@0.5.3, 
> chalk@1.1.3, gulplog@1.0.0, fancy-log@1.3.3, lodash.template@3.6.2, 
> multipipe@0.1.2, through2@2.0.5)
> ├── vinyl-fs@0.3.14 (strip-bom@1.0.0, defaults@1.0.3, vinyl@0.4.6, 
> graceful-fs@3.0.11, mkdirp@0.5.1, through2@0.6.5, glob-stream@3.1.18, 
> glob-watcher@0.0.6)
> └── liftoff@2.5.0 (flagged-respawn@1.0.1, rechoir@0.6.2, extend@3.0.2, 
> is-plain-object@2.0.4, object.map@1.0.1, fined@1.2.0, resolve@1.11.1, 
> findup-sync@2.0.0)
> :myriad-scheduler:gulp_build
> [20:04:49] Using gulpfile 
> ~/incubator-myriad/myriad-scheduler/src/main/resources/webapp/gulpfile.js
> [20:04:49] Starting 'clean'...
> [20:04:49] Finished 'clean' after 15 ms
> [20:04:49] Starting 'js'...
> [20:04:49] Finished 'js' after 29 ms
> [20:04:49] Starting 'html'...
> [20:04:49] Starting 'css'...
> [20:04:49] Starting 'img'...
> [20:04:49] Finished 'html' after 46 ms
> [20:04:49] Finished 'css' after 42 ms
> [20:04:50] Finished 'img' after 591 ms
> [20:04:50] Starting 'default'...
> [20:04:50] Finished 'default' after 17 μs
> [20:04:50] Starting 'build'...
> [20:04:50] Finished 'build' after 32 μs
> events.js:141
> throw er; // Unhandled 'error' event
> ^
> ReferenceError: Invalid left-hand side in assignment
> at module.exports 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/syntax-error/index.js:11:52)
> at DestroyableTransform._transform 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/index.js:613:19)
> at DestroyableTransform.Transform._read 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/l
> ib/_stream_transform.js:184:10)
> at DestroyableTransform.Transform._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/
> lib/_stream_transform.js:172:12)
> at Labeled.Pipeline._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/labeled-stream-splicer/n

[jira] [Assigned] (MYRIAD-296) Build broken by Gulp Error

2019-07-04 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reassigned MYRIAD-296:
-

Assignee: Oscar Fernandez

> Build broken by Gulp Error
> --
>
> Key: MYRIAD-296
> URL: https://issues.apache.org/jira/browse/MYRIAD-296
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Assignee: Oscar Fernandez
>Priority: Major
>  Labels: build
>
> {noformat}
> $ ./gradlew gulp_build
> Parallel execution is an incubating feature.
> :myriad-scheduler:nodeSetup UP-TO-DATE
> :myriad-scheduler:installGulp UP-TO-DATE
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstallnpm WARN deprecated gulp-util@3.0.8: gulp-util is 
> deprecated - replace it, following the guidelines at 
> https://medium.com/gulpjs/gulp-util-ca3b1f
> 9f9ac5
> npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals 
> and will break at some point. Do not use it, and update to graceful-fs@4.x.
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN engine atob@2.1.2: wanted: {"node":">= 4.5.0"} (current: 
> {"node":"4.2.1","npm":"2.14.7"}) 
> gulp@3.8.11 node_modules/gulp
> ├── pretty-hrtime@0.2.2
> ├── interpret@0.3.10
> ├── deprecated@0.0.1
> ├── archy@1.0.0
> ├── tildify@1.2.0 (os-homedir@1.0.2)
> ├── minimist@1.2.0
> ├── v8flags@2.1.1 (user-home@1.1.1)
> ├── semver@4.3.6
> ├── chalk@0.5.1 (ansi-styles@1.1.0, escape-string-regexp@1.0.5, 
> supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
> ├── orchestrator@0.3.8 (stream-consume@0.1.1, sequencify@0.0.7, 
> end-of-stream@0.1.5)
> ├── gulp-util@3.0.8 (array-differ@1.0.0, beeper@1.1.1, 
> lodash._reescape@3.0.0, array-uniq@1.0.3, lodash._reevaluate@3.0.0, 
> object-assign@3.0.0, lodash._reinterpolate@3.0.0,
> replace-ext@0.0.1, dateformat@2.2.0, has-gulplog@0.1.0, vinyl@0.5.3, 
> chalk@1.1.3, gulplog@1.0.0, fancy-log@1.3.3, lodash.template@3.6.2, 
> multipipe@0.1.2, through2@2.0.5)
> ├── vinyl-fs@0.3.14 (strip-bom@1.0.0, defaults@1.0.3, vinyl@0.4.6, 
> graceful-fs@3.0.11, mkdirp@0.5.1, through2@0.6.5, glob-stream@3.1.18, 
> glob-watcher@0.0.6)
> └── liftoff@2.5.0 (flagged-respawn@1.0.1, rechoir@0.6.2, extend@3.0.2, 
> is-plain-object@2.0.4, object.map@1.0.1, fined@1.2.0, resolve@1.11.1, 
> findup-sync@2.0.0)
> :myriad-scheduler:gulp_build
> [20:04:49] Using gulpfile 
> ~/incubator-myriad/myriad-scheduler/src/main/resources/webapp/gulpfile.js
> [20:04:49] Starting 'clean'...
> [20:04:49] Finished 'clean' after 15 ms
> [20:04:49] Starting 'js'...
> [20:04:49] Finished 'js' after 29 ms
> [20:04:49] Starting 'html'...
> [20:04:49] Starting 'css'...
> [20:04:49] Starting 'img'...
> [20:04:49] Finished 'html' after 46 ms
> [20:04:49] Finished 'css' after 42 ms
> [20:04:50] Finished 'img' after 591 ms
> [20:04:50] Starting 'default'...
> [20:04:50] Finished 'default' after 17 μs
> [20:04:50] Starting 'build'...
> [20:04:50] Finished 'build' after 32 μs
> events.js:141
> throw er; // Unhandled 'error' event
> ^
> ReferenceError: Invalid left-hand side in assignment
> at module.exports 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/syntax-error/index.js:11:52)
> at DestroyableTransform._transform 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/index.js:613:19)
> at DestroyableTransform.Transform._read 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/l
> ib/_stream_transform.js:184:10)
> at DestroyableTransform.Transform._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/
> lib/_stream_transform.js:172:12)
> at Labeled.Pipeline._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/labeled-stream-splicer/node_mo
> d

[jira] [Updated] (MYRIAD-296) Build broken by Gulp Error

2019-07-01 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman updated MYRIAD-296:
--
Labels: build  (was: )

> Build broken by Gulp Error
> --
>
> Key: MYRIAD-296
> URL: https://issues.apache.org/jira/browse/MYRIAD-296
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Priority: Major
>  Labels: build
>
> {noformat}
> $ ./gradlew gulp_build
> Parallel execution is an incubating feature.
> :myriad-scheduler:nodeSetup UP-TO-DATE
> :myriad-scheduler:installGulp UP-TO-DATE
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstallnpm WARN deprecated gulp-util@3.0.8: gulp-util is 
> deprecated - replace it, following the guidelines at 
> https://medium.com/gulpjs/gulp-util-ca3b1f
> 9f9ac5
> npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals 
> and will break at some point. Do not use it, and update to graceful-fs@4.x.
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN engine atob@2.1.2: wanted: {"node":">= 4.5.0"} (current: 
> {"node":"4.2.1","npm":"2.14.7"}) 
> gulp@3.8.11 node_modules/gulp
> ├── pretty-hrtime@0.2.2
> ├── interpret@0.3.10
> ├── deprecated@0.0.1
> ├── archy@1.0.0
> ├── tildify@1.2.0 (os-homedir@1.0.2)
> ├── minimist@1.2.0
> ├── v8flags@2.1.1 (user-home@1.1.1)
> ├── semver@4.3.6
> ├── chalk@0.5.1 (ansi-styles@1.1.0, escape-string-regexp@1.0.5, 
> supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
> ├── orchestrator@0.3.8 (stream-consume@0.1.1, sequencify@0.0.7, 
> end-of-stream@0.1.5)
> ├── gulp-util@3.0.8 (array-differ@1.0.0, beeper@1.1.1, 
> lodash._reescape@3.0.0, array-uniq@1.0.3, lodash._reevaluate@3.0.0, 
> object-assign@3.0.0, lodash._reinterpolate@3.0.0,
> replace-ext@0.0.1, dateformat@2.2.0, has-gulplog@0.1.0, vinyl@0.5.3, 
> chalk@1.1.3, gulplog@1.0.0, fancy-log@1.3.3, lodash.template@3.6.2, 
> multipipe@0.1.2, through2@2.0.5)
> ├── vinyl-fs@0.3.14 (strip-bom@1.0.0, defaults@1.0.3, vinyl@0.4.6, 
> graceful-fs@3.0.11, mkdirp@0.5.1, through2@0.6.5, glob-stream@3.1.18, 
> glob-watcher@0.0.6)
> └── liftoff@2.5.0 (flagged-respawn@1.0.1, rechoir@0.6.2, extend@3.0.2, 
> is-plain-object@2.0.4, object.map@1.0.1, fined@1.2.0, resolve@1.11.1, 
> findup-sync@2.0.0)
> :myriad-scheduler:gulp_build
> [20:04:49] Using gulpfile 
> ~/incubator-myriad/myriad-scheduler/src/main/resources/webapp/gulpfile.js
> [20:04:49] Starting 'clean'...
> [20:04:49] Finished 'clean' after 15 ms
> [20:04:49] Starting 'js'...
> [20:04:49] Finished 'js' after 29 ms
> [20:04:49] Starting 'html'...
> [20:04:49] Starting 'css'...
> [20:04:49] Starting 'img'...
> [20:04:49] Finished 'html' after 46 ms
> [20:04:49] Finished 'css' after 42 ms
> [20:04:50] Finished 'img' after 591 ms
> [20:04:50] Starting 'default'...
> [20:04:50] Finished 'default' after 17 μs
> [20:04:50] Starting 'build'...
> [20:04:50] Finished 'build' after 32 μs
> events.js:141
> throw er; // Unhandled 'error' event
> ^
> ReferenceError: Invalid left-hand side in assignment
> at module.exports 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/syntax-error/index.js:11:52)
> at DestroyableTransform._transform 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/index.js:613:19)
> at DestroyableTransform.Transform._read 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/l
> ib/_stream_transform.js:184:10)
> at DestroyableTransform.Transform._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/
> lib/_stream_transform.js:172:12)
> at Labeled.Pipeline._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/labeled-stream-splicer/node_mo
> dules/stream-splicer/index.js:73:22)
> at doWrite 

[jira] [Updated] (MYRIAD-296) Build broken by Gulp Error

2019-07-01 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman updated MYRIAD-296:
--
Component/s: Scheduler

> Build broken by Gulp Error
> --
>
> Key: MYRIAD-296
> URL: https://issues.apache.org/jira/browse/MYRIAD-296
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Priority: Major
>
> {noformat}
> $ ./gradlew gulp_build
> Parallel execution is an incubating feature.
> :myriad-scheduler:nodeSetup UP-TO-DATE
> :myriad-scheduler:installGulp UP-TO-DATE
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstallnpm WARN deprecated gulp-util@3.0.8: gulp-util is 
> deprecated - replace it, following the guidelines at 
> https://medium.com/gulpjs/gulp-util-ca3b1f
> 9f9ac5
> npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals 
> and will break at some point. Do not use it, and update to graceful-fs@4.x.
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm WARN engine atob@2.1.2: wanted: {"node":">= 4.5.0"} (current: 
> {"node":"4.2.1","npm":"2.14.7"}) 
> gulp@3.8.11 node_modules/gulp
> ├── pretty-hrtime@0.2.2
> ├── interpret@0.3.10
> ├── deprecated@0.0.1
> ├── archy@1.0.0
> ├── tildify@1.2.0 (os-homedir@1.0.2)
> ├── minimist@1.2.0
> ├── v8flags@2.1.1 (user-home@1.1.1)
> ├── semver@4.3.6
> ├── chalk@0.5.1 (ansi-styles@1.1.0, escape-string-regexp@1.0.5, 
> supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
> ├── orchestrator@0.3.8 (stream-consume@0.1.1, sequencify@0.0.7, 
> end-of-stream@0.1.5)
> ├── gulp-util@3.0.8 (array-differ@1.0.0, beeper@1.1.1, 
> lodash._reescape@3.0.0, array-uniq@1.0.3, lodash._reevaluate@3.0.0, 
> object-assign@3.0.0, lodash._reinterpolate@3.0.0,
> replace-ext@0.0.1, dateformat@2.2.0, has-gulplog@0.1.0, vinyl@0.5.3, 
> chalk@1.1.3, gulplog@1.0.0, fancy-log@1.3.3, lodash.template@3.6.2, 
> multipipe@0.1.2, through2@2.0.5)
> ├── vinyl-fs@0.3.14 (strip-bom@1.0.0, defaults@1.0.3, vinyl@0.4.6, 
> graceful-fs@3.0.11, mkdirp@0.5.1, through2@0.6.5, glob-stream@3.1.18, 
> glob-watcher@0.0.6)
> └── liftoff@2.5.0 (flagged-respawn@1.0.1, rechoir@0.6.2, extend@3.0.2, 
> is-plain-object@2.0.4, object.map@1.0.1, fined@1.2.0, resolve@1.11.1, 
> findup-sync@2.0.0)
> :myriad-scheduler:gulp_build
> [20:04:49] Using gulpfile 
> ~/incubator-myriad/myriad-scheduler/src/main/resources/webapp/gulpfile.js
> [20:04:49] Starting 'clean'...
> [20:04:49] Finished 'clean' after 15 ms
> [20:04:49] Starting 'js'...
> [20:04:49] Finished 'js' after 29 ms
> [20:04:49] Starting 'html'...
> [20:04:49] Starting 'css'...
> [20:04:49] Starting 'img'...
> [20:04:49] Finished 'html' after 46 ms
> [20:04:49] Finished 'css' after 42 ms
> [20:04:50] Finished 'img' after 591 ms
> [20:04:50] Starting 'default'...
> [20:04:50] Finished 'default' after 17 μs
> [20:04:50] Starting 'build'...
> [20:04:50] Finished 'build' after 32 μs
> events.js:141
> throw er; // Unhandled 'error' event
> ^
> ReferenceError: Invalid left-hand side in assignment
> at module.exports 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/syntax-error/index.js:11:52)
> at DestroyableTransform._transform 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/index.js:613:19)
> at DestroyableTransform.Transform._read 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/l
> ib/_stream_transform.js:184:10)
> at DestroyableTransform.Transform._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/
> lib/_stream_transform.js:172:12)
> at Labeled.Pipeline._write 
> (/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/labeled-stream-splicer/node_mo
> dules/stream-splicer/index.js:73:22)
> at doWrite 
> (/home/vagrant/incubator-m

[jira] [Created] (MYRIAD-296) Build broken by Gulp Error

2019-07-01 Thread Javi Roman (JIRA)
Javi Roman created MYRIAD-296:
-

 Summary: Build broken by Gulp Error
 Key: MYRIAD-296
 URL: https://issues.apache.org/jira/browse/MYRIAD-296
 Project: Myriad
  Issue Type: Bug
Affects Versions: Myriad 0.4.0
Reporter: Javi Roman


{noformat}
$ ./gradlew gulp_build
Parallel execution is an incubating feature.
:myriad-scheduler:nodeSetup UP-TO-DATE
:myriad-scheduler:installGulp UP-TO-DATE
:myriad-scheduler:npmSetup SKIPPED
:myriad-scheduler:npmInstallnpm WARN deprecated gulp-util@3.0.8: gulp-util is 
deprecated - replace it, following the guidelines at 
https://medium.com/gulpjs/gulp-util-ca3b1f
9f9ac5
npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for 
compatibility with current and future versions of Node.js
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or 
higher to avoid a RegExp DoS issue
npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals 
and will break at some point. Do not use it, and update to graceful-fs@4.x.
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or 
higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for 
compatibility with current and future versions of Node.js
npm WARN engine atob@2.1.2: wanted: {"node":">= 4.5.0"} (current: 
{"node":"4.2.1","npm":"2.14.7"}) 

gulp@3.8.11 node_modules/gulp
├── pretty-hrtime@0.2.2
├── interpret@0.3.10
├── deprecated@0.0.1
├── archy@1.0.0
├── tildify@1.2.0 (os-homedir@1.0.2)
├── minimist@1.2.0
├── v8flags@2.1.1 (user-home@1.1.1)
├── semver@4.3.6
├── chalk@0.5.1 (ansi-styles@1.1.0, escape-string-regexp@1.0.5, 
supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
├── orchestrator@0.3.8 (stream-consume@0.1.1, sequencify@0.0.7, 
end-of-stream@0.1.5)
├── gulp-util@3.0.8 (array-differ@1.0.0, beeper@1.1.1, lodash._reescape@3.0.0, 
array-uniq@1.0.3, lodash._reevaluate@3.0.0, object-assign@3.0.0, 
lodash._reinterpolate@3.0.0,
replace-ext@0.0.1, dateformat@2.2.0, has-gulplog@0.1.0, vinyl@0.5.3, 
chalk@1.1.3, gulplog@1.0.0, fancy-log@1.3.3, lodash.template@3.6.2, 
multipipe@0.1.2, through2@2.0.5)
├── vinyl-fs@0.3.14 (strip-bom@1.0.0, defaults@1.0.3, vinyl@0.4.6, 
graceful-fs@3.0.11, mkdirp@0.5.1, through2@0.6.5, glob-stream@3.1.18, 
glob-watcher@0.0.6)
└── liftoff@2.5.0 (flagged-respawn@1.0.1, rechoir@0.6.2, extend@3.0.2, 
is-plain-object@2.0.4, object.map@1.0.1, fined@1.2.0, resolve@1.11.1, 
findup-sync@2.0.0)
:myriad-scheduler:gulp_build
[20:04:49] Using gulpfile 
~/incubator-myriad/myriad-scheduler/src/main/resources/webapp/gulpfile.js
[20:04:49] Starting 'clean'...
[20:04:49] Finished 'clean' after 15 ms
[20:04:49] Starting 'js'...
[20:04:49] Finished 'js' after 29 ms
[20:04:49] Starting 'html'...
[20:04:49] Starting 'css'...
[20:04:49] Starting 'img'...
[20:04:49] Finished 'html' after 46 ms
[20:04:49] Finished 'css' after 42 ms
[20:04:50] Finished 'img' after 591 ms
[20:04:50] Starting 'default'...
[20:04:50] Finished 'default' after 17 μs
[20:04:50] Starting 'build'...
[20:04:50] Finished 'build' after 32 μs

events.js:141
throw er; // Unhandled 'error' event
^

ReferenceError: Invalid left-hand side in assignment
at module.exports 
(/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/syntax-error/index.js:11:52)
at DestroyableTransform._transform 
(/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/index.js:613:19)
at DestroyableTransform.Transform._read 
(/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/l
ib/_stream_transform.js:184:10)
at DestroyableTransform.Transform._write 
(/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/
lib/_stream_transform.js:172:12)
at Labeled.Pipeline._write 
(/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/labeled-stream-splicer/node_mo
dules/stream-splicer/index.js:73:22)
at doWrite 
(/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/lib/_stream_writable.js:279:12
)
at writeOrBuffer 
(/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/lib/_stream_writable.js:
266:5)
at Labeled.Writable.write 
(/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/lib/_stream_wri
table.js:211:11)
at Labeled.ondata 
(/home/vagrant/incubator-myriad/myriad-scheduler/src/main/resources/webapp/node_modules/browserify/node_modules/readable-stream/lib/_stream_readable.js
:572:20

Re: The way towards TLP promotion

2019-06-29 Thread Javi Roman
Following up this thread I'd like add this new issue:

https://issues.apache.org/jira/browse/MYRIAD-295

as a major issue towards an hypothetical TLP graduation.
--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman

On Mon, Nov 26, 2018 at 7:17 PM Javi Roman  wrote:
>
> I have been thinking about some goals/roadmap to reach a possible TLP
> promotion of Myriad. I've just created three JIRA issues, a sort of
> umbrella issues in order to focus our effort on that direction:
>
> 1. https://issues.apache.org/jira/browse/MYRIAD-280: Improve overall stability
> 2. https://issues.apache.org/jira/browse/MYRIAD-279: Reworking a new UI design
> 3. https://issues.apache.org/jira/browse/MYRIAD-278: Create test-suit
> for acceptance test driven development
>
> The former and second issues are focuses in an overall improvement of
> the project, we can create sub-tasks under those umbrella-tickets. The
> third one, is a helper task for the other ones, we can create
> specialized test for Myriad taking into advance the capabilities of
> Vagrant as cluster foundation.
>
> Please, feel free of comment this idea!
>
> --
> Javi Roman
>
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
> Apache Id: javiroman


[jira] [Created] (MYRIAD-295) Allow multiple versions of Apache Hadoop to run on the same physical infrastructure

2019-06-29 Thread Javi Roman (JIRA)
Javi Roman created MYRIAD-295:
-

 Summary: Allow multiple versions of Apache Hadoop to run on the 
same physical infrastructure
 Key: MYRIAD-295
 URL: https://issues.apache.org/jira/browse/MYRIAD-295
 Project: Myriad
  Issue Type: Improvement
Affects Versions: Myriad 0.4.0
Reporter: Javi Roman
 Fix For: Myriad 0.4.0


One of the most interesting features listed in the original Apache Myriad 
Incubator Proposal [1], was:
 * Allow multiple versions of Apache Hadoop to run on the same physical 
infrastructure

>From my point of view this is one of the major advantages of Apache Mesos in 
>the context of framework development. Apache Myriad could be modified in order 
>to create a robust Apache YARN as a Services application. Multiple YARNs 
>running in the same infrastructure is a major goal for the project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MYRIAD-279) Reworking a new UI design

2019-06-29 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman updated MYRIAD-279:
--
Affects Version/s: (was: Myriad 0.3.0)
   Myriad 0.4.0

> Reworking a new UI design
> -
>
> Key: MYRIAD-279
> URL: https://issues.apache.org/jira/browse/MYRIAD-279
> Project: Myriad
>  Issue Type: New Feature
>  Components: User Interface
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Priority: Major
>
> We should enhance the whole look and feel of Myriad UI, to add a dashboard, 
> new controls, metrics about YARN and HDFS and so forth.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (MYRIAD-180) Build should not pollute sources

2019-06-29 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reassigned MYRIAD-180:
-

Assignee: Javi Roman

> Build should not pollute sources
> 
>
> Key: MYRIAD-180
> URL: https://issues.apache.org/jira/browse/MYRIAD-180
> Project: Myriad
>  Issue Type: Bug
>Affects Versions: Myriad 0.1.0
>Reporter: Santosh Marella
>    Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.4.0
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-general/201512.mbox/%3CCAPmHmDTM4T37wJj6sPZniiU0mwm7qC4P9VCEHaOxhwWAvr%2Be_g%40mail.gmail.com%3E
> Myriad scheduler build generates the node_modules  directory 
> (myriad-scheduler/src/main/resources/webapp/node_modules). Ideally, any files 
> downloaded/generated by build should be outside of "src".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MYRIAD-180) Build should not pollute sources

2019-06-29 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman updated MYRIAD-180:
--
Affects Version/s: (was: Myriad 0.1.0)
   Myriad 0.4.0

> Build should not pollute sources
> 
>
> Key: MYRIAD-180
> URL: https://issues.apache.org/jira/browse/MYRIAD-180
> Project: Myriad
>  Issue Type: Bug
>Affects Versions: Myriad 0.4.0
>Reporter: Santosh Marella
>    Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.4.0
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-general/201512.mbox/%3CCAPmHmDTM4T37wJj6sPZniiU0mwm7qC4P9VCEHaOxhwWAvr%2Be_g%40mail.gmail.com%3E
> Myriad scheduler build generates the node_modules  directory 
> (myriad-scheduler/src/main/resources/webapp/node_modules). Ideally, any files 
> downloaded/generated by build should be outside of "src".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MYRIAD-278) Create test-suit for acceptance test driven development

2019-06-29 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman updated MYRIAD-278:
--
Affects Version/s: (was: Myriad 0.3.0)
   Myriad 0.4.0

> Create test-suit for acceptance test driven development 
> 
>
> Key: MYRIAD-278
> URL: https://issues.apache.org/jira/browse/MYRIAD-278
> Project: Myriad
>  Issue Type: New Feature
>  Components: Vagrant
>Affects Versions: Myriad 0.4.0
>    Reporter: Javi Roman
>Priority: Major
>  Labels: test
>
> We need a strong test suit for getting confidence about our code, for example 
> following the concept of Acceptance Test Driven Development (ATDD) involves 
> team members with different perspectives (customer, development, testing) 
> collaborating to write acceptance tests. These acceptance tests represent the 
> user's point of view and act as a form of requirements to describe how the 
> system will function, as well as serve as a way of verifying that the system 
> functions as intended.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MYRIAD-280) Improve overall stability

2019-06-29 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman updated MYRIAD-280:
--
Fix Version/s: Myriad 0.4.0

> Improve overall stability
> -
>
> Key: MYRIAD-280
> URL: https://issues.apache.org/jira/browse/MYRIAD-280
> Project: Myriad
>  Issue Type: Improvement
>  Components: Executor, Scheduler, User Interface
>    Reporter: Javi Roman
>Priority: Major
> Fix For: Myriad 0.4.0
>
>
> This is an umbrella task for enhancing the overall stability of Apache 
> Myriad. The idea is to create sub-tasks focuses into improve the product. 
> This will be a key issue in order to get an MVP for promotion to top level 
> project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (MYRIAD-185) Incubator Myriad 0.1.0 Build Takes Long

2019-06-29 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-185.
---
Resolution: Not A Bug

> Incubator Myriad 0.1.0 Build Takes Long
> ---
>
> Key: MYRIAD-185
> URL: https://issues.apache.org/jira/browse/MYRIAD-185
> Project: Myriad
>  Issue Type: Bug
>Affects Versions: Myriad 0.4.0
> Environment: OS: Ubuntu 14.04
> Kernel: 3.13.0-66-generic
>Reporter: Miguel Bernadin
>Assignee: Javi Roman
>Priority: Minor
> Fix For: Myriad 0.4.0
>
>
> Hello guys,
> I've noticed that the build for incubator-0.1.0 took 28 mins to complete.
> I performed, git clone https://github.com/apache/incubator-myriad and 
> ./gradlew build and here are the logs below.
> As you can see below it hangs at > Building 65% for 18 mins or so. It throws 
> an error then runs for about 3 mins more minutes and says it finishes 
> successfully. 
> Any thoughts?
> ---
> LOGS
> Starting a new Gradle Daemon for this build (subsequent builds will be 
> faster).
> Parallel execution is an incubating feature.
> :myriad-commons:compileJava
> :myriad-scheduler:nodeSetup
> :myriad-executor:processResources UP-TO-DATE
> :myriad-executor:processTestResources UP-TO-DATE
> warning: [options] bootstrap class path not set in conjunction with -source 
> 1.7
> 1 warning
> :myriad-commons:compileGroovy UP-TO-DATE
> :myriad-commons:processResources UP-TO-DATE
> :myriad-commons:classes
> :myriad-commons:jar
> :myriad-commons:startScripts
> :myriad-executor:compileJava
> :myriad-scheduler:compileJava
> warning: [options] bootstrap class path not set in conjunction with -source 
> 1.7
> 1 warning
> :myriad-commons:distTar
> :myriad-executor:compileGroovy UP-TO-DATE
> :myriad-executor:classes
> :myriad-executor:jar
> :myriad-executor:startScripts
> warning: [options] bootstrap class path not set in conjunction with -source 
> 1.7
> :myriad-executor:distTar
> :myriad-commons:distZip
> :myriad-commons:assemble
> :myriad-executor:distZip
> :myriad-commons:checkstyleMain
> :myriad-commons:compileTestJava UP-TO-DATE
> :myriad-commons:compileTestGroovy UP-TO-DATE
> :myriad-commons:processTestResources UP-TO-DATE
> :myriad-commons:testClasses UP-TO-DATE
> :myriad-commons:checkstyleTest UP-TO-DATE
> :myriad-commons:findbugsMain
> 1 warning
> :myriad-scheduler:compileGroovy UP-TO-DATE
> :myriad-scheduler:installGulp
> :myriad-executor:assemble
> :myriad-executor:capsule
> :myriad-executor:checkstyleMain
> :myriad-executor:compileTestJava UP-TO-DATE
> :myriad-executor:compileTestGroovy UP-TO-DATE
> :myriad-executor:testClasses UP-TO-DATE
> :myriad-executor:checkstyleTest UP-TO-DATE
> :myriad-executor:findbugsMain
> :myriad-commons:findbugsTest UP-TO-DATE
> :myriad-commons:pmdMain
> Scanning archives (68 / 68)
> 2 analysis passes to perform
> :myriad-commons:pmdTest UP-TO-DATE
> :myriad-commons:test UP-TO-DATE
> :myriad-commons:check
> :myriad-commons:build
> Pass 1: Analyzing classes (39 / 67) - 58% complete
>   
>   
>   
>   Pass 1: Analyzing classes (67 / 67) - 100% complete
> Pass 2: Analyzing classes (3 / 3) - 100% complete
> Done with analysis
> :myriad-executor:findbugsTest UP-TO-DATE
> :myriad-executor:pmdMain
> :myriad-executor:pmdTest UP-TO-DATE
> :myriad-executor:test UP-TO-DATE
> :myriad-executor:check
> :myriad-executor:build
> > Building 65%
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstall
> npm WARN peerDependencies The peer dependency stream-browserify@* included 
> from bl will no
> npm WARN peerDependencies longer be automatically installed to fulfill the 
> peerDependency 
> npm WARN peerDependencies in npm 3+. Your application will need to depend on 
> it explicitly.
> npm WARN deprecated lodash@2.4.2: lodash@<3.0.0 is no longer maintained. 
> Upgrade to lodash@^3.0.0.
> npm WARN optional dep failed, continuing fsevents@0.3.8
> npm WARN deprecated lodash@1.0.2: lodash@<3.0.0 is no longer maintained. 
> Upgrade to lodash@^3.0.0.
> > jpegtran-bin@3.0.6 postinstall 
> > /root/.dsh/mesos-configurator/incubator-myriad-0.1.0/myriad-scheduler/src/main/resources/webapp/node_modules/gulp-imagemin/node_modules/imagemin/node_modules/imagemin-jpegtran/node_modules/jpegtran

[jira] [Assigned] (MYRIAD-185) Incubator Myriad 0.1.0 Build Takes Long

2019-06-29 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reassigned MYRIAD-185:
-

Assignee: Javi Roman

> Incubator Myriad 0.1.0 Build Takes Long
> ---
>
> Key: MYRIAD-185
> URL: https://issues.apache.org/jira/browse/MYRIAD-185
> Project: Myriad
>  Issue Type: Bug
>Affects Versions: Myriad 0.4.0
> Environment: OS: Ubuntu 14.04
> Kernel: 3.13.0-66-generic
>Reporter: Miguel Bernadin
>Assignee: Javi Roman
>Priority: Minor
> Fix For: Myriad 0.4.0
>
>
> Hello guys,
> I've noticed that the build for incubator-0.1.0 took 28 mins to complete.
> I performed, git clone https://github.com/apache/incubator-myriad and 
> ./gradlew build and here are the logs below.
> As you can see below it hangs at > Building 65% for 18 mins or so. It throws 
> an error then runs for about 3 mins more minutes and says it finishes 
> successfully. 
> Any thoughts?
> ---
> LOGS
> Starting a new Gradle Daemon for this build (subsequent builds will be 
> faster).
> Parallel execution is an incubating feature.
> :myriad-commons:compileJava
> :myriad-scheduler:nodeSetup
> :myriad-executor:processResources UP-TO-DATE
> :myriad-executor:processTestResources UP-TO-DATE
> warning: [options] bootstrap class path not set in conjunction with -source 
> 1.7
> 1 warning
> :myriad-commons:compileGroovy UP-TO-DATE
> :myriad-commons:processResources UP-TO-DATE
> :myriad-commons:classes
> :myriad-commons:jar
> :myriad-commons:startScripts
> :myriad-executor:compileJava
> :myriad-scheduler:compileJava
> warning: [options] bootstrap class path not set in conjunction with -source 
> 1.7
> 1 warning
> :myriad-commons:distTar
> :myriad-executor:compileGroovy UP-TO-DATE
> :myriad-executor:classes
> :myriad-executor:jar
> :myriad-executor:startScripts
> warning: [options] bootstrap class path not set in conjunction with -source 
> 1.7
> :myriad-executor:distTar
> :myriad-commons:distZip
> :myriad-commons:assemble
> :myriad-executor:distZip
> :myriad-commons:checkstyleMain
> :myriad-commons:compileTestJava UP-TO-DATE
> :myriad-commons:compileTestGroovy UP-TO-DATE
> :myriad-commons:processTestResources UP-TO-DATE
> :myriad-commons:testClasses UP-TO-DATE
> :myriad-commons:checkstyleTest UP-TO-DATE
> :myriad-commons:findbugsMain
> 1 warning
> :myriad-scheduler:compileGroovy UP-TO-DATE
> :myriad-scheduler:installGulp
> :myriad-executor:assemble
> :myriad-executor:capsule
> :myriad-executor:checkstyleMain
> :myriad-executor:compileTestJava UP-TO-DATE
> :myriad-executor:compileTestGroovy UP-TO-DATE
> :myriad-executor:testClasses UP-TO-DATE
> :myriad-executor:checkstyleTest UP-TO-DATE
> :myriad-executor:findbugsMain
> :myriad-commons:findbugsTest UP-TO-DATE
> :myriad-commons:pmdMain
> Scanning archives (68 / 68)
> 2 analysis passes to perform
> :myriad-commons:pmdTest UP-TO-DATE
> :myriad-commons:test UP-TO-DATE
> :myriad-commons:check
> :myriad-commons:build
> Pass 1: Analyzing classes (39 / 67) - 58% complete
>   
>   
>   
>   Pass 1: Analyzing classes (67 / 67) - 100% complete
> Pass 2: Analyzing classes (3 / 3) - 100% complete
> Done with analysis
> :myriad-executor:findbugsTest UP-TO-DATE
> :myriad-executor:pmdMain
> :myriad-executor:pmdTest UP-TO-DATE
> :myriad-executor:test UP-TO-DATE
> :myriad-executor:check
> :myriad-executor:build
> > Building 65%
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstall
> npm WARN peerDependencies The peer dependency stream-browserify@* included 
> from bl will no
> npm WARN peerDependencies longer be automatically installed to fulfill the 
> peerDependency 
> npm WARN peerDependencies in npm 3+. Your application will need to depend on 
> it explicitly.
> npm WARN deprecated lodash@2.4.2: lodash@<3.0.0 is no longer maintained. 
> Upgrade to lodash@^3.0.0.
> npm WARN optional dep failed, continuing fsevents@0.3.8
> npm WARN deprecated lodash@1.0.2: lodash@<3.0.0 is no longer maintained. 
> Upgrade to lodash@^3.0.0.
> > jpegtran-bin@3.0.6 postinstall 
> > /root/.dsh/mesos-configurator/incubator-myriad-0.1.0/myriad-scheduler/src/main/resources/webapp/node_modules/gulp-imagemin/node_modules/imagemin/node_modules/imagemin-jpegtran/node_modules/jpegtran

[jira] [Updated] (MYRIAD-185) Incubator Myriad 0.1.0 Build Takes Long

2019-06-29 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman updated MYRIAD-185:
--
Fix Version/s: Myriad 0.4.0

> Incubator Myriad 0.1.0 Build Takes Long
> ---
>
> Key: MYRIAD-185
> URL: https://issues.apache.org/jira/browse/MYRIAD-185
> Project: Myriad
>  Issue Type: Bug
>Affects Versions: Myriad 0.4.0
> Environment: OS: Ubuntu 14.04
> Kernel: 3.13.0-66-generic
>Reporter: Miguel Bernadin
>Priority: Minor
> Fix For: Myriad 0.4.0
>
>
> Hello guys,
> I've noticed that the build for incubator-0.1.0 took 28 mins to complete.
> I performed, git clone https://github.com/apache/incubator-myriad and 
> ./gradlew build and here are the logs below.
> As you can see below it hangs at > Building 65% for 18 mins or so. It throws 
> an error then runs for about 3 mins more minutes and says it finishes 
> successfully. 
> Any thoughts?
> ---
> LOGS
> Starting a new Gradle Daemon for this build (subsequent builds will be 
> faster).
> Parallel execution is an incubating feature.
> :myriad-commons:compileJava
> :myriad-scheduler:nodeSetup
> :myriad-executor:processResources UP-TO-DATE
> :myriad-executor:processTestResources UP-TO-DATE
> warning: [options] bootstrap class path not set in conjunction with -source 
> 1.7
> 1 warning
> :myriad-commons:compileGroovy UP-TO-DATE
> :myriad-commons:processResources UP-TO-DATE
> :myriad-commons:classes
> :myriad-commons:jar
> :myriad-commons:startScripts
> :myriad-executor:compileJava
> :myriad-scheduler:compileJava
> warning: [options] bootstrap class path not set in conjunction with -source 
> 1.7
> 1 warning
> :myriad-commons:distTar
> :myriad-executor:compileGroovy UP-TO-DATE
> :myriad-executor:classes
> :myriad-executor:jar
> :myriad-executor:startScripts
> warning: [options] bootstrap class path not set in conjunction with -source 
> 1.7
> :myriad-executor:distTar
> :myriad-commons:distZip
> :myriad-commons:assemble
> :myriad-executor:distZip
> :myriad-commons:checkstyleMain
> :myriad-commons:compileTestJava UP-TO-DATE
> :myriad-commons:compileTestGroovy UP-TO-DATE
> :myriad-commons:processTestResources UP-TO-DATE
> :myriad-commons:testClasses UP-TO-DATE
> :myriad-commons:checkstyleTest UP-TO-DATE
> :myriad-commons:findbugsMain
> 1 warning
> :myriad-scheduler:compileGroovy UP-TO-DATE
> :myriad-scheduler:installGulp
> :myriad-executor:assemble
> :myriad-executor:capsule
> :myriad-executor:checkstyleMain
> :myriad-executor:compileTestJava UP-TO-DATE
> :myriad-executor:compileTestGroovy UP-TO-DATE
> :myriad-executor:testClasses UP-TO-DATE
> :myriad-executor:checkstyleTest UP-TO-DATE
> :myriad-executor:findbugsMain
> :myriad-commons:findbugsTest UP-TO-DATE
> :myriad-commons:pmdMain
> Scanning archives (68 / 68)
> 2 analysis passes to perform
> :myriad-commons:pmdTest UP-TO-DATE
> :myriad-commons:test UP-TO-DATE
> :myriad-commons:check
> :myriad-commons:build
> Pass 1: Analyzing classes (39 / 67) - 58% complete
>   
>   
>   
>   Pass 1: Analyzing classes (67 / 67) - 100% complete
> Pass 2: Analyzing classes (3 / 3) - 100% complete
> Done with analysis
> :myriad-executor:findbugsTest UP-TO-DATE
> :myriad-executor:pmdMain
> :myriad-executor:pmdTest UP-TO-DATE
> :myriad-executor:test UP-TO-DATE
> :myriad-executor:check
> :myriad-executor:build
> > Building 65%
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstall
> npm WARN peerDependencies The peer dependency stream-browserify@* included 
> from bl will no
> npm WARN peerDependencies longer be automatically installed to fulfill the 
> peerDependency 
> npm WARN peerDependencies in npm 3+. Your application will need to depend on 
> it explicitly.
> npm WARN deprecated lodash@2.4.2: lodash@<3.0.0 is no longer maintained. 
> Upgrade to lodash@^3.0.0.
> npm WARN optional dep failed, continuing fsevents@0.3.8
> npm WARN deprecated lodash@1.0.2: lodash@<3.0.0 is no longer maintained. 
> Upgrade to lodash@^3.0.0.
> > jpegtran-bin@3.0.6 postinstall 
> > /root/.dsh/mesos-configurator/incubator-myriad-0.1.0/myriad-scheduler/src/main/resources/webapp/node_modules/gulp-imagemin/node_modules/imagemin/node_modules/imagemin-jpegtran/node_modules/jpegtran-bin
> > node lib/install.js
&

[jira] [Commented] (MYRIAD-185) Incubator Myriad 0.1.0 Build Takes Long

2019-06-29 Thread Javi Roman (JIRA)


[ 
https://issues.apache.org/jira/browse/MYRIAD-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875452#comment-16875452
 ] 

Javi Roman commented on MYRIAD-185:
---

The most of the time these delays are related with "npm install" and 
dependencies, this is not a bug, only a poor performance of this tool. The 
solution could be change to [https://yarnpkg.com/en/]. This is something we 
have to take into account further.

We can open a issue for this change, meanwhile I'm going to close this issue.

> Incubator Myriad 0.1.0 Build Takes Long
> ---
>
> Key: MYRIAD-185
> URL: https://issues.apache.org/jira/browse/MYRIAD-185
> Project: Myriad
>  Issue Type: Bug
>Affects Versions: Myriad 0.1.0
> Environment: OS: Ubuntu 14.04
> Kernel: 3.13.0-66-generic
>Reporter: Miguel Bernadin
>Priority: Minor
>
> Hello guys,
> I've noticed that the build for incubator-0.1.0 took 28 mins to complete.
> I performed, git clone https://github.com/apache/incubator-myriad and 
> ./gradlew build and here are the logs below.
> As you can see below it hangs at > Building 65% for 18 mins or so. It throws 
> an error then runs for about 3 mins more minutes and says it finishes 
> successfully. 
> Any thoughts?
> ---
> LOGS
> Starting a new Gradle Daemon for this build (subsequent builds will be 
> faster).
> Parallel execution is an incubating feature.
> :myriad-commons:compileJava
> :myriad-scheduler:nodeSetup
> :myriad-executor:processResources UP-TO-DATE
> :myriad-executor:processTestResources UP-TO-DATE
> warning: [options] bootstrap class path not set in conjunction with -source 
> 1.7
> 1 warning
> :myriad-commons:compileGroovy UP-TO-DATE
> :myriad-commons:processResources UP-TO-DATE
> :myriad-commons:classes
> :myriad-commons:jar
> :myriad-commons:startScripts
> :myriad-executor:compileJava
> :myriad-scheduler:compileJava
> warning: [options] bootstrap class path not set in conjunction with -source 
> 1.7
> 1 warning
> :myriad-commons:distTar
> :myriad-executor:compileGroovy UP-TO-DATE
> :myriad-executor:classes
> :myriad-executor:jar
> :myriad-executor:startScripts
> warning: [options] bootstrap class path not set in conjunction with -source 
> 1.7
> :myriad-executor:distTar
> :myriad-commons:distZip
> :myriad-commons:assemble
> :myriad-executor:distZip
> :myriad-commons:checkstyleMain
> :myriad-commons:compileTestJava UP-TO-DATE
> :myriad-commons:compileTestGroovy UP-TO-DATE
> :myriad-commons:processTestResources UP-TO-DATE
> :myriad-commons:testClasses UP-TO-DATE
> :myriad-commons:checkstyleTest UP-TO-DATE
> :myriad-commons:findbugsMain
> 1 warning
> :myriad-scheduler:compileGroovy UP-TO-DATE
> :myriad-scheduler:installGulp
> :myriad-executor:assemble
> :myriad-executor:capsule
> :myriad-executor:checkstyleMain
> :myriad-executor:compileTestJava UP-TO-DATE
> :myriad-executor:compileTestGroovy UP-TO-DATE
> :myriad-executor:testClasses UP-TO-DATE
> :myriad-executor:checkstyleTest UP-TO-DATE
> :myriad-executor:findbugsMain
> :myriad-commons:findbugsTest UP-TO-DATE
> :myriad-commons:pmdMain
> Scanning archives (68 / 68)
> 2 analysis passes to perform
> :myriad-commons:pmdTest UP-TO-DATE
> :myriad-commons:test UP-TO-DATE
> :myriad-commons:check
> :myriad-commons:build
> Pass 1: Analyzing classes (39 / 67) - 58% complete
>   
>   
>   
>   Pass 1: Analyzing classes (67 / 67) - 100% complete
> Pass 2: Analyzing classes (3 / 3) - 100% complete
> Done with analysis
> :myriad-executor:findbugsTest UP-TO-DATE
> :myriad-executor:pmdMain
> :myriad-executor:pmdTest UP-TO-DATE
> :myriad-executor:test UP-TO-DATE
> :myriad-executor:check
> :myriad-executor:build
> > Building 65%
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstall
> npm WARN peerDependencies The peer dependency stream-browserify@* included 
> from bl will no
> npm WARN peerDependencies longer be automatically installed to fulfill the 
> peerDependency 
> npm WARN peerDependencies in npm 3+. Your application will need to depend on 
> it explicitly.
> npm WARN deprecated lodash@2.4.2: lodash@<3.0.0 is no longer maintained. 
> Upgrade to lodash@^3.0.0.
> npm WARN optional dep failed, continuing fsevents@0.3.8
> npm WARN deprecated lodash@1.0.2: lodash@<3.0.0 is no longer maintained. 
&g

[jira] [Updated] (MYRIAD-185) Incubator Myriad 0.1.0 Build Takes Long

2019-06-29 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman updated MYRIAD-185:
--
Affects Version/s: (was: Myriad 0.1.0)
   Myriad 0.4.0

> Incubator Myriad 0.1.0 Build Takes Long
> ---
>
> Key: MYRIAD-185
> URL: https://issues.apache.org/jira/browse/MYRIAD-185
> Project: Myriad
>  Issue Type: Bug
>Affects Versions: Myriad 0.4.0
> Environment: OS: Ubuntu 14.04
> Kernel: 3.13.0-66-generic
>Reporter: Miguel Bernadin
>Priority: Minor
>
> Hello guys,
> I've noticed that the build for incubator-0.1.0 took 28 mins to complete.
> I performed, git clone https://github.com/apache/incubator-myriad and 
> ./gradlew build and here are the logs below.
> As you can see below it hangs at > Building 65% for 18 mins or so. It throws 
> an error then runs for about 3 mins more minutes and says it finishes 
> successfully. 
> Any thoughts?
> ---
> LOGS
> Starting a new Gradle Daemon for this build (subsequent builds will be 
> faster).
> Parallel execution is an incubating feature.
> :myriad-commons:compileJava
> :myriad-scheduler:nodeSetup
> :myriad-executor:processResources UP-TO-DATE
> :myriad-executor:processTestResources UP-TO-DATE
> warning: [options] bootstrap class path not set in conjunction with -source 
> 1.7
> 1 warning
> :myriad-commons:compileGroovy UP-TO-DATE
> :myriad-commons:processResources UP-TO-DATE
> :myriad-commons:classes
> :myriad-commons:jar
> :myriad-commons:startScripts
> :myriad-executor:compileJava
> :myriad-scheduler:compileJava
> warning: [options] bootstrap class path not set in conjunction with -source 
> 1.7
> 1 warning
> :myriad-commons:distTar
> :myriad-executor:compileGroovy UP-TO-DATE
> :myriad-executor:classes
> :myriad-executor:jar
> :myriad-executor:startScripts
> warning: [options] bootstrap class path not set in conjunction with -source 
> 1.7
> :myriad-executor:distTar
> :myriad-commons:distZip
> :myriad-commons:assemble
> :myriad-executor:distZip
> :myriad-commons:checkstyleMain
> :myriad-commons:compileTestJava UP-TO-DATE
> :myriad-commons:compileTestGroovy UP-TO-DATE
> :myriad-commons:processTestResources UP-TO-DATE
> :myriad-commons:testClasses UP-TO-DATE
> :myriad-commons:checkstyleTest UP-TO-DATE
> :myriad-commons:findbugsMain
> 1 warning
> :myriad-scheduler:compileGroovy UP-TO-DATE
> :myriad-scheduler:installGulp
> :myriad-executor:assemble
> :myriad-executor:capsule
> :myriad-executor:checkstyleMain
> :myriad-executor:compileTestJava UP-TO-DATE
> :myriad-executor:compileTestGroovy UP-TO-DATE
> :myriad-executor:testClasses UP-TO-DATE
> :myriad-executor:checkstyleTest UP-TO-DATE
> :myriad-executor:findbugsMain
> :myriad-commons:findbugsTest UP-TO-DATE
> :myriad-commons:pmdMain
> Scanning archives (68 / 68)
> 2 analysis passes to perform
> :myriad-commons:pmdTest UP-TO-DATE
> :myriad-commons:test UP-TO-DATE
> :myriad-commons:check
> :myriad-commons:build
> Pass 1: Analyzing classes (39 / 67) - 58% complete
>   
>   
>   
>   Pass 1: Analyzing classes (67 / 67) - 100% complete
> Pass 2: Analyzing classes (3 / 3) - 100% complete
> Done with analysis
> :myriad-executor:findbugsTest UP-TO-DATE
> :myriad-executor:pmdMain
> :myriad-executor:pmdTest UP-TO-DATE
> :myriad-executor:test UP-TO-DATE
> :myriad-executor:check
> :myriad-executor:build
> > Building 65%
> :myriad-scheduler:npmSetup SKIPPED
> :myriad-scheduler:npmInstall
> npm WARN peerDependencies The peer dependency stream-browserify@* included 
> from bl will no
> npm WARN peerDependencies longer be automatically installed to fulfill the 
> peerDependency 
> npm WARN peerDependencies in npm 3+. Your application will need to depend on 
> it explicitly.
> npm WARN deprecated lodash@2.4.2: lodash@<3.0.0 is no longer maintained. 
> Upgrade to lodash@^3.0.0.
> npm WARN optional dep failed, continuing fsevents@0.3.8
> npm WARN deprecated lodash@1.0.2: lodash@<3.0.0 is no longer maintained. 
> Upgrade to lodash@^3.0.0.
> > jpegtran-bin@3.0.6 postinstall 
> > /root/.dsh/mesos-configurator/incubator-myriad-0.1.0/myriad-scheduler/src/main/resources/webapp/node_modules/gulp-imagemin/node_modules/imagemin/node_modules/imagemin-jpegtran/node_modules/jpegtran-bin
> > node l

Slack channel (again)

2019-06-29 Thread Javi Roman
Taking advantage of the new activity in the list and issues (many
thanks @oscarfmdc for your contribution). I would like share with all
a new slack workspace for Apache Myriad [1].

We have been using Gitter (https://gitter.im/apache-myriad/dev) for
chatting, however the Gitter platform is far away from Slack, in terms
of features. So I purpose to use Slack for that.

Please click this link in order to self-invite to the channel [2].

[1] https://apache-myriad.slack.com/
[2] 
https://join.slack.com/t/apache-myriad/shared_invite/enQtNjc5NTE0OTQwNTEyLTkwYjVkYzJkZDc4ZWQ2OWQ3NjQ5YzNmMTcxM2JjYjYyNGU2ZGRkZTA1NDUxZjA1OWYxYjkxY2JjMjk2MDQxYjI

--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman


[jira] [Assigned] (MYRIAD-294) Add license footers to a few markdown readmes that currently don't have it

2019-06-29 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reassigned MYRIAD-294:
-

Assignee: Oscar Fernandez  (was: Javi Roman)

> Add license footers to a few markdown readmes that currently don't have it
> --
>
> Key: MYRIAD-294
> URL: https://issues.apache.org/jira/browse/MYRIAD-294
> Project: Myriad
>  Issue Type: Task
>Reporter: Oscar Fernandez
>Assignee: Oscar Fernandez
>Priority: Minor
>  Time Spent: 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (MYRIAD-294) Add license footers to a few markdown readmes that currently don't have it

2019-06-29 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reassigned MYRIAD-294:
-

Assignee: Javi Roman

> Add license footers to a few markdown readmes that currently don't have it
> --
>
> Key: MYRIAD-294
> URL: https://issues.apache.org/jira/browse/MYRIAD-294
> Project: Myriad
>  Issue Type: Task
>Reporter: Oscar Fernandez
>    Assignee: Javi Roman
>Priority: Minor
>  Time Spent: 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[ANNOUNCE] Apache Myriad 0.3.0 released

2019-04-16 Thread Javi Roman
The Apache Myriad (Incubator) community is very happy to announce the
release of Apache Myriad 0.3.0.

The release is available for download at:
https://myriad.apache.org/downloads

Please check out the release blog post for an overview of the
improvements for this release:
https://myriad.apache.org/blogs/2019/03/25/myriad-0.3.0-release-announcement.html

The last version (0.2.0) was released at 2016-06-29. The release of
this new version is an effort made for rebooting the project with new
strength and with the hope of continuing the development with renewed
strength. New contributors are welcome!

--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman


[jira] [Resolved] (MYRIAD-288) Update Project Site (News, and more)

2019-04-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-288.
---
Resolution: Fixed

> Update Project Site (News, and more)
> 
>
> Key: MYRIAD-288
> URL: https://issues.apache.org/jira/browse/MYRIAD-288
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.3.0
>    Reporter: Javi Roman
>    Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.3.0
>
>
> Update  [http://myriad.incubator.apache.org/]
> And [https://incubator.apache.org/projects/myriad.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (MYRIAD-283) Prepare for 0.3.0 release

2019-04-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-283.
---
Resolution: Fixed

> Prepare for 0.3.0 release
> -
>
> Key: MYRIAD-283
> URL: https://issues.apache.org/jira/browse/MYRIAD-283
> Project: Myriad
>  Issue Type: Task
>Affects Versions: Myriad 0.3.0
>    Reporter: Javi Roman
>    Assignee: Javi Roman
>Priority: Major
>  Labels: releasegeneration
> Fix For: Myriad 0.3.0
>
>
> Umbrella task for 0.3.0 version releasing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (MYRIAD-283) Prepare for 0.3.0 release

2019-04-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-283.
-

> Prepare for 0.3.0 release
> -
>
> Key: MYRIAD-283
> URL: https://issues.apache.org/jira/browse/MYRIAD-283
> Project: Myriad
>  Issue Type: Task
>Affects Versions: Myriad 0.3.0
>    Reporter: Javi Roman
>    Assignee: Javi Roman
>Priority: Major
>  Labels: releasegeneration
> Fix For: Myriad 0.3.0
>
>
> Umbrella task for 0.3.0 version releasing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (MYRIAD-288) Update Project Site (News, and more)

2019-04-16 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-288.
-

> Update Project Site (News, and more)
> 
>
> Key: MYRIAD-288
> URL: https://issues.apache.org/jira/browse/MYRIAD-288
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.3.0
>    Reporter: Javi Roman
>    Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.3.0
>
>
> Update  [http://myriad.incubator.apache.org/]
> And [https://incubator.apache.org/projects/myriad.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MYRIAD-288) Update Project Site (News, and more)

2019-03-30 Thread Javi Roman (JIRA)


[ 
https://issues.apache.org/jira/browse/MYRIAD-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805793#comment-16805793
 ] 

Javi Roman commented on MYRIAD-288:
---

Status page with NEWs secton updated: Done.

> Update Project Site (News, and more)
> 
>
> Key: MYRIAD-288
> URL: https://issues.apache.org/jira/browse/MYRIAD-288
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.3.0
>    Reporter: Javi Roman
>    Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.3.0
>
>
> Update  [http://myriad.incubator.apache.org/]
> And [https://incubator.apache.org/projects/myriad.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MYRIAD-288) Update Project Site (News, and more)

2019-03-30 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman updated MYRIAD-288:
--
Description: 
Update  [http://myriad.incubator.apache.org/]

And [https://incubator.apache.org/projects/myriad.html]

  was:Update  http://myriad.incubator.apache.org/


> Update Project Site (News, and more)
> 
>
> Key: MYRIAD-288
> URL: https://issues.apache.org/jira/browse/MYRIAD-288
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.3.0
>    Reporter: Javi Roman
>    Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.3.0
>
>
> Update  [http://myriad.incubator.apache.org/]
> And [https://incubator.apache.org/projects/myriad.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (MYRIAD-293) Post Voting Action: create release with "release.sh" script

2019-03-30 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-293.
-

> Post Voting Action: create release with  "release.sh" script 
> -
>
> Key: MYRIAD-293
> URL: https://issues.apache.org/jira/browse/MYRIAD-293
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.3.0
>Reporter: Javi Roman
>Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.3.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> # Run the "release.sh" script to tag the successfully voted RC "as the 
> release". This script
>  ## Creates a new github tag for the release. Removes the "RC" tags that were 
> added during voting.
>  ## Uploads the "release" artifacts to release SVN: 
> [https://dist.apache.org/repos/dist/release/incubator/myriad/] 
>  ## Deletes the "RC" artifacts from dev SVN: 
> [https://dist.apache.org/repos/dist/dev/incubator/myriad/]
>  # Make all the JIRAs marked for this release are resolved. Add the "release 
> date" against the released version.
>  # Make sure the release is available for download from 
> http://myriad.incubator.apache.org/downloads/.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (MYRIAD-287) Update Release Notes (doc site - Confluence)

2019-03-30 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-287.
-

> Update Release Notes (doc site - Confluence)
> 
>
> Key: MYRIAD-287
> URL: https://issues.apache.org/jira/browse/MYRIAD-287
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.3.0
>    Reporter: Javi Roman
>    Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.3.0
>
>
> Release notes page:
>  
> https://cwiki.apache.org/confluence/display/MYRIAD/Release+Notes



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (MYRIAD-286) Call for voting to PPMC (e-mail)

2019-03-30 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-286.
-

> Call for voting to PPMC (e-mail)
> 
>
> Key: MYRIAD-286
> URL: https://issues.apache.org/jira/browse/MYRIAD-286
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.3.0
>    Reporter: Javi Roman
>    Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.3.0
>
>
> The Apache Myriad PPMC should approve a release candidate.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (MYRIAD-293) Post Voting Action: create release with "release.sh" script

2019-03-26 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-293.
---
Resolution: Fixed

> Post Voting Action: create release with  "release.sh" script 
> -
>
> Key: MYRIAD-293
> URL: https://issues.apache.org/jira/browse/MYRIAD-293
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.3.0
>Reporter: Javi Roman
>Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.3.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> # Run the "release.sh" script to tag the successfully voted RC "as the 
> release". This script
>  ## Creates a new github tag for the release. Removes the "RC" tags that were 
> added during voting.
>  ## Uploads the "release" artifacts to release SVN: 
> [https://dist.apache.org/repos/dist/release/incubator/myriad/] 
>  ## Deletes the "RC" artifacts from dev SVN: 
> [https://dist.apache.org/repos/dist/dev/incubator/myriad/]
>  # Make all the JIRAs marked for this release are resolved. Add the "release 
> date" against the released version.
>  # Make sure the release is available for download from 
> http://myriad.incubator.apache.org/downloads/.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MYRIAD-287) Update Release Notes (doc site - Confluence)

2019-03-26 Thread Javi Roman (JIRA)


[ 
https://issues.apache.org/jira/browse/MYRIAD-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801482#comment-16801482
 ] 

Javi Roman commented on MYRIAD-287:
---

Done: [https://cwiki.apache.org/confluence/display/MYRIAD/Release+Notes]

> Update Release Notes (doc site - Confluence)
> 
>
> Key: MYRIAD-287
> URL: https://issues.apache.org/jira/browse/MYRIAD-287
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.3.0
>    Reporter: Javi Roman
>    Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.3.0
>
>
> Release notes page:
>  
> https://cwiki.apache.org/confluence/display/MYRIAD/Release+Notes



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MYRIAD-293) Post Voting Action: create release with "release.sh" script

2019-03-25 Thread Javi Roman (JIRA)


[ 
https://issues.apache.org/jira/browse/MYRIAD-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16800434#comment-16800434
 ] 

Javi Roman commented on MYRIAD-293:
---

Released at:

[https://dist.apache.org/repos/dist/release/incubator/myriad/]

 

Cleanup of temporary dev folder (old RC's):

[https://dist.apache.org/repos/dist/dev/incubator/myriad/]

> Post Voting Action: create release with  "release.sh" script 
> -
>
> Key: MYRIAD-293
> URL: https://issues.apache.org/jira/browse/MYRIAD-293
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.3.0
>Reporter: Javi Roman
>Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.3.0
>
>
> # Run the "release.sh" script to tag the successfully voted RC "as the 
> release". This script
>  ## Creates a new github tag for the release. Removes the "RC" tags that were 
> added during voting.
>  ## Uploads the "release" artifacts to release SVN: 
> [https://dist.apache.org/repos/dist/release/incubator/myriad/] 
>  ## Deletes the "RC" artifacts from dev SVN: 
> [https://dist.apache.org/repos/dist/dev/incubator/myriad/]
>  # Make all the JIRAs marked for this release are resolved. Add the "release 
> date" against the released version.
>  # Make sure the release is available for download from 
> http://myriad.incubator.apache.org/downloads/.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MYRIAD-292) Call for voting to IPMC (e-mail)

2019-03-18 Thread Javi Roman (JIRA)


[ 
https://issues.apache.org/jira/browse/MYRIAD-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794871#comment-16794871
 ] 

Javi Roman commented on MYRIAD-292:
---

The vote was successful: 
[https://lists.apache.org/thread.html/8314190d529d785e08903d7ce92be5add34c54ac16d972d4acf299c9@%3Cgeneral.incubator.apache.org%3E]
 

> Call for voting to IPMC (e-mail)
> 
>
> Key: MYRIAD-292
> URL: https://issues.apache.org/jira/browse/MYRIAD-292
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.3.0
>    Reporter: Javi Roman
>    Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.3.0
>
>
> E-mail calling for voting to Incubator PMCs and final Result vote.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (MYRIAD-293) Post Voting Action: create release with "release.sh" script

2019-03-18 Thread Javi Roman (JIRA)
Javi Roman created MYRIAD-293:
-

 Summary: Post Voting Action: create release with  "release.sh" 
script 
 Key: MYRIAD-293
 URL: https://issues.apache.org/jira/browse/MYRIAD-293
 Project: Myriad
  Issue Type: Sub-task
Affects Versions: Myriad 0.3.0
Reporter: Javi Roman
Assignee: Javi Roman
 Fix For: Myriad 0.3.0


# Run the "release.sh" script to tag the successfully voted RC "as the 
release". This script
 ## Creates a new github tag for the release. Removes the "RC" tags that were 
added during voting.
 ## Uploads the "release" artifacts to release SVN: 
[https://dist.apache.org/repos/dist/release/incubator/myriad/] 
 ## Deletes the "RC" artifacts from dev SVN: 
[https://dist.apache.org/repos/dist/dev/incubator/myriad/]
 # Make all the JIRAs marked for this release are resolved. Add the "release 
date" against the released version.
 # Make sure the release is available for download from 
http://myriad.incubator.apache.org/downloads/.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (MYRIAD-292) Call for voting to IPMC (e-mail)

2019-03-18 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman closed MYRIAD-292.
-

> Call for voting to IPMC (e-mail)
> 
>
> Key: MYRIAD-292
> URL: https://issues.apache.org/jira/browse/MYRIAD-292
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.3.0
>    Reporter: Javi Roman
>    Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.3.0
>
>
> E-mail calling for voting to Incubator PMCs and final Result vote.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (MYRIAD-292) Call for voting to IPMC (e-mail)

2019-03-18 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman resolved MYRIAD-292.
---
Resolution: Fixed

> Call for voting to IPMC (e-mail)
> 
>
> Key: MYRIAD-292
> URL: https://issues.apache.org/jira/browse/MYRIAD-292
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.3.0
>    Reporter: Javi Roman
>    Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.3.0
>
>
> E-mail calling for voting to Incubator PMCs and final Result vote.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[RESULT][VOTE] Release Apache Myriad 0.3.0 (incubating) [rc1]

2019-03-18 Thread Javi Roman
Hi everyone,

The vote for releasing Apache Myriad 0.3.0-RC1 (incubating) is closed,
now. And I’m happy to announce that we have unanimously approved this
release candidate (RC1) to be the Apache Myriad 0.3.0 release.

Vote result:
3 (+1 binding) (lresende, jmclean,  ningjiang)
0 (0 binding)
0 (-1 binding)

And no non-binding votes.

Thank you everyone for taking the time to review the release and help us.

--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman


[jira] [Updated] (MYRIAD-292) Call for voting to IPMC (e-mail)

2019-03-09 Thread Javi Roman (JIRA)


 [ 
https://issues.apache.org/jira/browse/MYRIAD-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman updated MYRIAD-292:
--
Fix Version/s: Myriad 0.3.0

> Call for voting to IPMC (e-mail)
> 
>
> Key: MYRIAD-292
> URL: https://issues.apache.org/jira/browse/MYRIAD-292
> Project: Myriad
>  Issue Type: Sub-task
>Affects Versions: Myriad 0.3.0
>    Reporter: Javi Roman
>    Assignee: Javi Roman
>Priority: Major
> Fix For: Myriad 0.3.0
>
>
> E-mail calling for voting to Incubator PMCs and final Result vote.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


  1   2   3   4   >