Re: [VOTE] Move OODT to Attic?

[Imesha Sudasingha]

Hi All,

Thanks all for voting! OODT was my first considerable ASF contribution and
it was a great opportunity for me to learn, and was an honour to work with
you all. Special thanks to Chris, Tom and Lewis.

@Bertrand,
Should anything else be done from the PMC side?

Thanks,
Imesha




On Mon, 17 Apr 2023 at 20:59, Bertrand Delacretaz 
wrote:

> Dear OODT PMC,
>
> On 2023/04/03 01:02:01 Imesha Sudasingha wrote:
> > Due to inactivity, Apache OODT is considering moving to the Attic [1]
>
> The next Board meeting is this Wednesday April 19th - if you have more
> information on the status of this move please let us know.
>
> -Bertrand, for the ASF Board of Directors
>

[VOTE] Move OODT to Attic?

[Imesha Sudasingha]

Hello everyone:

Due to inactivity, Apache OODT is considering moving to the Attic [1]. This
email serves as a call to all PMC members to vote whether to retire OODT to
the attic, or not.  Note that three -1 votes will be sufficient to cancel
retirement to the attic no matter how many +1 votes there are.

PMC members, please reply to this email with your vote:

+1 [ ] I wish for Apache OODT to be retired to the Apache Attic
+0 [ ] I do not care
-1 [ ] Apache OODT should not be retired to the Attic

Here's my +1.

Thanks,
Imesha

[1] https://attic.apache.org/

[REPORT] OODT - October 2022

[Imesha Sudasingha]

## Description:
Apache OODT is a software framework as well as an architectural style for
the
rapid construction of scientific data systems. It provides components for
data
capture, curation, metadata extraction, workflow management, resource
management, and data processing.

## Issues:
Regarding the following comment by the board in June, "Not being able to
release because of lack of activity is a bit problematic. Is there reason to
believe this will change in the near future?":

I don't think the situation will improve in the future

## Membership Data:
Apache OODT was founded 2010-11-17 (12 years ago)
There are currently 47 committers and 46 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Nadeeshan Gimhana on 2021-04-25.
- No new committers. Last addition was Nadeeshan Gimhana on 2021-04-06.

## Project Activity:
- Last release (1.9.1) was in October 2021
- Still we couldn't get OODT 2.0 released due to contributors being busy
with
  their own work

## Community Health:
Community health is low due to no new development being done around OODT and
the number of active OODT users is very low (and they will not upgrade to
newer versions).

[REPORT] OODT - June 2022

[Imesha Sudasingha]

## Description:
Apache OODT is a software framework as well as an architectural style for
the
rapid construction of scientific data systems. It provides components for
data
capture, curation, metadata extraction, workflow management, resource
management, and data processing.

## Issues:
No issues persist that require board's attention.

## Membership Data:
Apache OODT was founded 2010-11-17 (12 years ago)
There are currently 47 committers and 46 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Nadeeshan Gimhana on 2021-04-25.
- No new committers. Last addition was Nadeeshan Gimhana on 2021-04-06.

## Project Activity:
- Last release (1.9.1) was in October 2021

We have finished required feature developments for OODT 2.0, but couldn't
get
it released yet due to all the active contributors being busy. The plan is
to
get it released during the reporting period.

## Community Health:
Community health was low due to no new development being done around OODT.
It may increase a bit with the release work of OODT 2.0.

[REPORT] OODT - February 2022

[Imesha Sudasingha]

## Description:
Apache OODT is a software framework as well as an architectural style for the
rapid construction of scientific data systems. It provides components for data
capture, curation, metadata extraction, workflow management, resource
management, and data processing.

## Issues:
No issues persist that require board's attention.

## Membership Data:
Apache OODT was founded 2010-11-17 (11 years ago)
There are currently 47 committers and 46 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Nadeeshan Gimhana on 2021-04-25.
- No new committers. Last addition was Nadeeshan Gimhana on 2021-04-06.

## Project Activity:
- Last release was in October 2021

As mentioned in the last report (September 2021), we released 1.9.1 patch
release. Then we have merged the changes queued for 2.0 that was in the
development branch into master branch. Plan is to release 2.0 as soon as
several contributors become available.

## Community Health:
Community health was low due to no new development being done around OODT.
Work for 2.0 has already been completed. Project activity may pickup when we
start the discussion around 2.0 release.

[ANNOUNCE] Apache OODT 1.9.1 released

[Imesha Sudasingha]

The Apache OODT project is pleased to announce the release of Apache OODT
1.9.1. The release contents have been pushed out to the main Apache release
site and to the Maven Central sync, so the releases should be available as
soon as the mirrors get the syncs.

Apache OODT is a software framework as well as an architectural style for
the rapid construction of scientific data systems.  It provides components
for data capture, curation, metadata extraction, workflow management,
resource management, and data processing.

Apache OODT 1.9.1 contains a number of improvements and bug fixes. Details
can be found in the changes file:
http://www.apache.org/dist/oodt/CHANGES-1.9.1.txt

Apache OODT is available in source form from the following download page:
http://www.apache.org/dist/oodt/apache-oodt-1.9.1-src.zip

Apache OODT is also available in binary form or for use using Maven 2 from
the Central Repository: https://repo1.maven.org/maven2/org/apache/oodt/

In the initial 48 hours, the release may not be available on all mirrors.
When downloading from a mirror site, please remember to verify the
downloads using signatures found on the Apache site:
http://www.apache.org/dist/oodt/KEYS
For more information on Apache OODT, visit the project home page:
http://oodt.apache.org/

-- Imesha Sudasingha, on behalf of the Apache OODT community

Re: [EXTERNAL] Re: [VOTE] OODT 1.9.1 RC1

[Imesha Sudasingha]

Thanks a lot everyone for the votes.
We have 4 votes in favor and 0 against.
I will proceed with the release.


On Tue, 28 Sept 2021 at 18:29, Rajith Siriwardana 
wrote:

> +1
>
> On Tue, Sep 28, 2021 at 7:55 AM Chris Mattmann 
> wrote:
>
> > +1 from me on the release. Great job!
> >
> >
> >
> > Cheers,
> >
> > Chris
> >
> >
> >
> > On Sun, 26 Sept 2021 at 00:11, Imesha Sudasingha 
> > wrote:
> >
> > Hi Folks,
> >
> >
> >
> > I have posted a release candidate for the Apache OODT 1.9.1 release. The
> >
> > source code is at:
> >
> >
> >
> > https://dist.apache.org/repos/dist/dev/oodt/
> >
> >
> >
> > For more detailed information, see the included CHANGES.txt file for
> > details on
> >
> > release contents and latest changes. The release was made using the OODT
> >
> > release process, documented on the Wiki here:
> >
> >
> >
> > https://cwiki.apache.org/confluence/display/OODT/Release+Process
> >
> >
> >
> > The release was made from the OODT 1.9.1 tag (98b6a8a) at:
> >
> >
> >
> > https://github.com/apache/oodt/tree/1.9.1
> >
> >
> >
> > A staged Maven repository is available at:
> >
> >
> >
> > https://repository.apache.org/content/repositories/orgapacheoodt-1025
> >
> >
> >
> > Please vote on releasing these packages as Apache OODT 1.9.1. The vote is
> >
> > open for at least the next 72 hours.
> >
> >
> >
> > Only votes from OODT PMC are binding, but folks are welcome to check the
> >
> > release candidate and voice their approval or disapproval. The vote
> passes
> >
> > if at least three binding +1 votes are cast.
> >
> >
> >
> > [ ] +1 Release the packages as Apache OODT 
> >
> >
> >
> > [ ] -1 Do not release the packages because...
> >
> >
> >
> > Thanks!
> >
> >
> >
> > Imesha
> >
> >
> >
> > P.S. Here is my +1.
> >
> >
>

[VOTE] OODT 1.9.1 RC1

[Imesha Sudasingha]

Hi Folks,

I have posted a release candidate for the Apache OODT 1.9.1 release. The
source code is at:

https://dist.apache.org/repos/dist/dev/oodt/

For more detailed information, see the included CHANGES.txt file for
details on
release contents and latest changes. The release was made using the OODT
release process, documented on the Wiki here:

https://cwiki.apache.org/confluence/display/OODT/Release+Process

The release was made from the OODT 1.9.1 tag (98b6a8a) at:

https://github.com/apache/oodt/tree/1.9.1

A staged Maven repository is available at:

https://repository.apache.org/content/repositories/orgapacheoodt-1025

Please vote on releasing these packages as Apache OODT 1.9.1. The vote is
open for at least the next 72 hours.

Only votes from OODT PMC are binding, but folks are welcome to check the
release candidate and voice their approval or disapproval. The vote passes
if at least three binding +1 votes are cast.

[ ] +1 Release the packages as Apache OODT 

[ ] -1 Do not release the packages because...

Thanks!

Imesha

P.S. Here is my +1.

[REPORT] OODT - September 2021

[Imesha Sudasingha]

## Description:
Apache OODT is a software framework as well as an architectural style for
the
rapid construction of scientific data systems. It provides components for
data
capture, curation, metadata extraction, workflow management, resource
management, and data processing.

## Issues:
No issues persist that require board's attention

## Membership Data:
Apache OODT was founded 2010-11-17 (11 years ago)
There are currently 47 committers and 46 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
- Nadeeshan Gimhana was added to the PMC on 2021-04-25
- No new committers. Last addition was Nadeeshan Gimhana on 2021-04-06.

## Project Activity:
- Last release was in October 2019.

With the conclusion of GSoC 2021, we have completed the new React.js based
OPSUI implementation. Additionally, we have introduced a docker deployment
to
deploy OODT components with docker-compose with zero configuration. We plan
to
release 1.9.1 patch release in the next quarter and then 2.0 with a bunch of
new features.

## Community Health:
Community health was really good, mainly due to the GSoC 2021 project
activity
and several contributors working alongside to add different features. As a
result email activity, commits and PR counts were high compared to last
quarter.

Re: Alert-Verify-Sender: RE: [EXT] Re: [IMPORTANT] PMCs/pPMCs: Apache Project visibility and promotion (please read)

[Imesha Sudasingha]

Hi Valerie,

Can you try sending an email to "dev-unsubscr...@oodt.apache.org" [1]

[1]
http://www.apache.org/foundation/mailinglists.html#request-addresses-for-unsubscribing

Imesha


On Sun, 29 Aug 2021 at 03:54, Mallder, Valerie 
wrote:

> Hello,
>
> How do I unsubscribe from this mailing list? I am no longer involved with
> any projects that use OODT and would like to unsubscribe.
>
> Thanks,
> Valerie
>
>
> Sent with BlackBerry Work
> (www.blackberry.com)
>
>
> From: Mallder, Valerie  valerie.mall...@jhuapl.edu>>
> Date: Saturday, Aug 28, 2021, 6:22 PM
> To: dev@oodt.apache.org mailto:dev@oodt.apache.org>>
> Subject: Alert-Verify-Sender: RE: [EXT] Re: [IMPORTANT] PMCs/pPMCs: Apache
> Project visibility and promotion (please read)
>
> APL external email warning: Verify sender dev-return-9139-Valerie.Mallder=
> jhuapl@oodt.apache.org before clicking links or attachments
>
> Unsubscribe
>
>
> Sent with BlackBerry Work
> (www.blackberry.com<http://www.blackberry.com>)
>
>
> From: Pavindu Lakshan  pavindulaks...@gmail.com>>
> Date: Saturday, Aug 28, 2021, 4:09 PM
> To: dev@oodt.apache.org mailto:dev@oodt.apache.org>>
> Subject: [EXT] Re: [IMPORTANT] PMCs/pPMCs: Apache Project visibility and
> promotion (please read)
>
> APL external email warning: Verify sender dev-return-9138-Valerie.Mallder=
> jhuapl@oodt.apache.org before clicking links or attachments
>
> Hi Imesha,
>
> Opened a PR.
> https://github.com/apache/oodt/pull/129
>
> Thanks
> Pavindu
>
> On Sun, 29 Aug 2021, 00:16 Imesha Sudasingha,  >
> wrote:
>
> > Can you send a PR to asf-site branch? And I can add my changed on top of
> > that.
> >
> >
> > On Sat, 28 Aug 2021 at 15:53, Pavindu Lakshan 
> > wrote:
> >
> > > Hi Imesha,
> > >
> > > Thanks for the feedback.
> > >
> > > Yes, I have committed these changes to asf-site branch of my OODT fork,
> > so
> > > that I could deploy it on Github pages for the demo.
> > >
> > > Thanks and regards
> > > Pavindu
> > >
> > > On Sat, 28 Aug 2021, 15:27 Imesha Sudasingha, <
> > imesha.sudasin...@gmail.com
> > > >
> > > wrote:
> > >
> > > > Hi Pavindu,
> > > >
> > > > This is great! The page structure is fine. Need to decide how we are
> > > going
> > > > to name those sections. Do you have these committed somewhere?
> > > >
> > > > Imesha
> > > >
> > > >
> > > > On Sat, 28 Aug 2021 at 09:03, Pavindu Lakshan <
> > pavindulaks...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Imesha,
> > > > >
> > > > > I created a new page for use cases and redesigned the community
> page,
> > > as
> > > > a
> > > > > simple demo. You can view them on the following links.
> > > > > (please note that the styles of the other pages in this demo are
> > > broken)
> > > > >
> > > > > Community page: https://pavindulakshan.ml/oodt/community.html
> > > > > Usecases page: https://pavindulakshan.ml/oodt/use-cases.html
> > > > >
> > > > > I'd like to know your opinion on the design. If you are okay with
> > it, I
> > > > > will make a PR.
> > > > >
> > > > > Thanks and regards
> > > > > Pavindu
> > > > >
> > > >
> > >
> >
>

Re: [IMPORTANT] PMCs/pPMCs: Apache Project visibility and promotion (please read)

[Imesha Sudasingha]

Hi Pavindu,

This is great! The page structure is fine. Need to decide how we are going
to name those sections. Do you have these committed somewhere?

Imesha


On Sat, 28 Aug 2021 at 09:03, Pavindu Lakshan 
wrote:

> Hi Imesha,
>
> I created a new page for use cases and redesigned the community page, as a
> simple demo. You can view them on the following links.
> (please note that the styles of the other pages in this demo are broken)
>
> Community page: https://pavindulakshan.ml/oodt/community.html
> Usecases page: https://pavindulakshan.ml/oodt/use-cases.html
>
> I'd like to know your opinion on the design. If you are okay with it, I
> will make a PR.
>
> Thanks and regards
> Pavindu
>

Re: [IMPORTANT] PMCs/pPMCs: Apache Project visibility and promotion (please read)

[Imesha Sudasingha]

Hi Pavindu,

Thanks and +1. But we will have to make that page a bit responsive and
adjust the alignments.

On Fri, 27 Aug 2021 at 09:31, Pavindu Lakshan 
wrote:

> Hi all,
>
> Is it okay to move that content to [community. html](
> https://github.com/apache/oodt/blob/asf-site/community.html)? Some of the
> use cases of OODT are already listed there.
>
> If that's OK, I'd be happy to make a PR for that.
>
> Thanks and best regards
> Pavindu
>
> On Thu, 26 Aug 2021, 11:29 Imesha Sudasingha,  >
> wrote:
>
> > Hi Lewis,
> >
> > You are correct. Looks like we have to create a separate page for who use
> > OODT.
> > I think if we modify the `asf-site` branch, it should get synced
> > automatically right?
> >
> > Thanks,
> > Imesha
> >
> >
> >
> >
> > On Thu, 26 Aug 2021 at 09:28, lewis john mcgibbney 
> > wrote:
> >
> > > Hi Folks,
> > > It looks like we need to move the company logos off of the OODT website
> > > homepage.
> > > I have no idea how to do this. Do we have a Website update HOWTO?
> > > Thanks
> > > lewismc
> > >
> > > -- Forwarded message -
> > > From: Sally Khudairi 
> > > Date: Wed, Aug 25, 2021 at 8:41 PM
> > > Subject: [IMPORTANT] PMCs/pPMCs: Apache Project visibility and
> promotion
> > > (please read)
> > > To: ASF Marketing & Publicity 
> > > ...
> > > V-a. Website branding compliance
> > >
> > > IMPORTANT: PMCs who list "powered by" companies on their Project sites
> > > (organizations that are using your project --in their
> products/solutions
> > or
> > > otherwise) MUST NOT BE DOING SO ON THE PROJECT HOME PAGE.
> > >
> > > WHY: the ASF is strictly vendor-neutral. Listing company names and/or
> > logos
> > > on a project's home page is disallowed as it can imply "ownership" or
> > > preferred status or otherwise imbalanced relationship. Whether this is
> > the
> > > case or not, it is not acceptable. The policy is the same as "thanking"
> > > companies for their support of a project
> > > http://apache.org/foundation/marks/linking#projectthanks
> > >
> > > WHAT WE'RE NOT SAYING: please don't misunderstand the "no third party
> > logos
> > > on your homepage" policy. We *love* projects promoting their users!
> Many
> > of
> > > you have commented that we always include user organizations in our
> press
> > > releases --one of the first things that members of the media and
> analyst
> > > community ask is, "who uses you?". We're proud of all our projects and
> > your
> > > collective efforts: we want to ensure that everyone is being fairly
> > > represented and considered.
> > >
> > > Some projects that are in violation are recent graduates from the
> > Incubator
> > > and may not have ever been aware of this policy. Others are
> long-standing
> > > TLPs with refreshed Websites: perhaps there are new contributors who
> > helped
> > > with the redesign and weren't aware. We understand that this action has
> > > likely been done in error, but needs to be rectified. Your "Powered By"
> > > listings can be on any page within your Project site but NOT the home
> > page.
> > >
> > > There are different ways you can recognize organizations that are
> Powered
> > > By Apache (YourProjectName) --here are some good examples:
> > >
> > > 1) Full logo -- Airflow -- http://airflow.apache.org/use-cases/
> > > 2) Shown with screenshots -- Flex --
> > > http://flex.apache.org/community-showcase.html
> > > 3) Named list -- CloudStack -- http://cloudstack.apache.org/users.html
> > >
> > > To that end ...now that you know...
> > >
> > > ALERT: the following projects need to change their homepages --
> > > ...
> > >  - OODT http://oodt.apache.org/
> > > ...
> > >
> > > Thank you in advance for your attention and help where applicable. As
> > > always, do let me know if you need assistance or further information. I
> > > hope this helps :-)
> > >
> > > Best,
> > > Sally
> > >
> > > - - -
> > > Vice President Sponsor Relations
> > > The Apache Software Foundation
> > >
> > > Tel +1 617 921 8656 | s...@apache.org
> > >
> > >
> > > --
> > > http://home.apache.org/~lewismc/
> > > http://people.apache.org/keys/committer/lewismc
> > >
> >
>

Re: [IMPORTANT] PMCs/pPMCs: Apache Project visibility and promotion (please read)

[Imesha Sudasingha]

Hi Lewis,

You are correct. Looks like we have to create a separate page for who use
OODT.
I think if we modify the `asf-site` branch, it should get synced
automatically right?

Thanks,
Imesha




On Thu, 26 Aug 2021 at 09:28, lewis john mcgibbney 
wrote:

> Hi Folks,
> It looks like we need to move the company logos off of the OODT website
> homepage.
> I have no idea how to do this. Do we have a Website update HOWTO?
> Thanks
> lewismc
>
> -- Forwarded message -
> From: Sally Khudairi 
> Date: Wed, Aug 25, 2021 at 8:41 PM
> Subject: [IMPORTANT] PMCs/pPMCs: Apache Project visibility and promotion
> (please read)
> To: ASF Marketing & Publicity 
> ...
> V-a. Website branding compliance
>
> IMPORTANT: PMCs who list "powered by" companies on their Project sites
> (organizations that are using your project --in their products/solutions or
> otherwise) MUST NOT BE DOING SO ON THE PROJECT HOME PAGE.
>
> WHY: the ASF is strictly vendor-neutral. Listing company names and/or logos
> on a project's home page is disallowed as it can imply "ownership" or
> preferred status or otherwise imbalanced relationship. Whether this is the
> case or not, it is not acceptable. The policy is the same as "thanking"
> companies for their support of a project
> http://apache.org/foundation/marks/linking#projectthanks
>
> WHAT WE'RE NOT SAYING: please don't misunderstand the "no third party logos
> on your homepage" policy. We *love* projects promoting their users! Many of
> you have commented that we always include user organizations in our press
> releases --one of the first things that members of the media and analyst
> community ask is, "who uses you?". We're proud of all our projects and your
> collective efforts: we want to ensure that everyone is being fairly
> represented and considered.
>
> Some projects that are in violation are recent graduates from the Incubator
> and may not have ever been aware of this policy. Others are long-standing
> TLPs with refreshed Websites: perhaps there are new contributors who helped
> with the redesign and weren't aware. We understand that this action has
> likely been done in error, but needs to be rectified. Your "Powered By"
> listings can be on any page within your Project site but NOT the home page.
>
> There are different ways you can recognize organizations that are Powered
> By Apache (YourProjectName) --here are some good examples:
>
> 1) Full logo -- Airflow -- http://airflow.apache.org/use-cases/
> 2) Shown with screenshots -- Flex --
> http://flex.apache.org/community-showcase.html
> 3) Named list -- CloudStack -- http://cloudstack.apache.org/users.html
>
> To that end ...now that you know...
>
> ALERT: the following projects need to change their homepages --
> ...
>  - OODT http://oodt.apache.org/
> ...
>
> Thank you in advance for your attention and help where applicable. As
> always, do let me know if you need assistance or further information. I
> hope this helps :-)
>
> Best,
> Sally
>
> - - -
> Vice President Sponsor Relations
> The Apache Software Foundation
>
> Tel +1 617 921 8656 | s...@apache.org
>
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>

Re: Requesting feedback on the work product blog

[Imesha Sudasingha]

Hi Pavindu,

Had a chance to go through it and it looks good. When you have some time,
let's put a mail in this list explaining the new features/look of the OPSUI.

Same as you, I was even thinking of hosting a sample deployment on a VM.
With the new docker-compose deployment, it can be done easily. Will try to
do that.

Imesha


On Sun, 22 Aug 2021 at 19:24, Pavindu Lakshan 
wrote:

> Hi all,
>
> As GSoC '21 is coming to end tomorrow, I created the following blog post as
> the work product, including my work and the future developments.
>
>
> https://medium.com/@pavindulakshan/gsoc-2021-improving-apache-oodt-opsui-react-js-ui-with-advanced-functionalities-8d1a8b080c8a
>
> It will be a great help if you can provide me with feedback on it.
>
> Thanks and best regards
> Pavindu
>

[jira] [Closed] (OODT-1036) build failed on AArch64, Fedora 33

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha closed OODT-1036.
---

> build failed on AArch64, Fedora 33 
> ---
>
> Key: OODT-1036
> URL: https://issues.apache.org/jira/browse/OODT-1036
> Project: OODT
>  Issue Type: Bug
>Reporter: Lutz Weischer
>    Assignee: Imesha Sudasingha
>Priority: Major
> Fix For: 1.9.1
>
>
> {code}
> [jw@cn05 oodt]$ mvn install -DskipTests
>  [INFO] — maven-assembly-plugin:2.6:single (default) @ cas-resource —
>  [INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
>  [INFO] Building tar: 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.tar.gz
>  [INFO] Building zip: 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.zip
>  [INFO]
>  [INFO] — maven-install-plugin:2.5.2:install (default-install) @ cas-resource 
> —
>  [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT.jar to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT.jar
>  [INFO] Installing /home/jw/apache/oodt/resource/pom.xml to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT.pom
>  [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.tar.gz 
> to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT-dist.tar.gz
>  [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.zip to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT-dist.zip
>  [INFO]
>  [INFO] < org.apache.oodt:cas-workflow 
> >
>  [INFO] Building Catalog and Archive Workflow Management Component 
> 1.10-SNAPSHOT [9/27]
>  [INFO] [ jar 
> ]-
>  [INFO]
>  [INFO] — maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
> cas-workflow —
>  [INFO]
>  [INFO] — avro-maven-plugin:1.8.2:schema (schemas) @ cas-workflow —
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowCondition.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowTask.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflow.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowInstance.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowInstancePage.avsc
>  [INFO]
>  [INFO] — avro-maven-plugin:1.8.2:idl-protocol (protocol) @ cas-workflow —
>  [INFO] Importing Directory: /home/jw/apache/oodt/workflow/src/main/avro/types
>  [INFO]
>  [INFO] — maven-remote-resources-plugin:1.5:process 
> (process-resource-bundles) @ cas-workflow —
>  [INFO]
>  [INFO] — maven-resources-plugin:3.1.0:resources (default-resources) @ 
> cas-workflow —
>  [INFO] Using 'UTF-8' encoding to copy filtered resources.
>  [INFO] Copying 27 resources
>  [INFO] Copying 3 resources
>  [INFO]
>  [INFO] — maven-compiler-plugin:3.7.0:compile (default-compile) @ 
> cas-workflow —
>  [INFO] Changes detected - recompiling the module!
>  [INFO] Compiling 151 source files to 
> /home/jw/apache/oodt/workflow/target/classes
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/examples/ResmgrJobCondition.java:
>  Some input files use or override a deprecated API.
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/examples/ResmgrJobCondition.java:
>  Recompile with -Xlint:deprecation for details.
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/structs/WorkflowTask.java:
>  Some input files use unchecked or unsafe operations.
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/structs/WorkflowTask.java:
>  Recompile with -Xlint:unchecked for details.
>  [INFO] -
>  [ERROR] COMPILATION ERROR :
>  [INFO] -
>  [ERROR] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/engine/runner/AsynchronousLocalEngineRunner.java:[114,13]
>  cannot find symbol
>  symbol: method destroy()
>  [INFO] 1 error
>  [INFO] -

[jira] [Resolved] (OODT-1036) build failed on AArch64, Fedora 33

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha resolved OODT-1036.
-
Fix Version/s: 1.9.1
   Resolution: Fixed

This build failure is now fixed

> build failed on AArch64, Fedora 33 
> ---
>
> Key: OODT-1036
> URL: https://issues.apache.org/jira/browse/OODT-1036
> Project: OODT
>  Issue Type: Bug
>Reporter: Lutz Weischer
>    Assignee: Imesha Sudasingha
>Priority: Major
> Fix For: 1.9.1
>
>
> {code}
> [jw@cn05 oodt]$ mvn install -DskipTests
>  [INFO] — maven-assembly-plugin:2.6:single (default) @ cas-resource —
>  [INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
>  [INFO] Building tar: 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.tar.gz
>  [INFO] Building zip: 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.zip
>  [INFO]
>  [INFO] — maven-install-plugin:2.5.2:install (default-install) @ cas-resource 
> —
>  [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT.jar to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT.jar
>  [INFO] Installing /home/jw/apache/oodt/resource/pom.xml to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT.pom
>  [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.tar.gz 
> to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT-dist.tar.gz
>  [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.zip to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT-dist.zip
>  [INFO]
>  [INFO] < org.apache.oodt:cas-workflow 
> >
>  [INFO] Building Catalog and Archive Workflow Management Component 
> 1.10-SNAPSHOT [9/27]
>  [INFO] [ jar 
> ]-
>  [INFO]
>  [INFO] — maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
> cas-workflow —
>  [INFO]
>  [INFO] — avro-maven-plugin:1.8.2:schema (schemas) @ cas-workflow —
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowCondition.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowTask.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflow.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowInstance.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowInstancePage.avsc
>  [INFO]
>  [INFO] — avro-maven-plugin:1.8.2:idl-protocol (protocol) @ cas-workflow —
>  [INFO] Importing Directory: /home/jw/apache/oodt/workflow/src/main/avro/types
>  [INFO]
>  [INFO] — maven-remote-resources-plugin:1.5:process 
> (process-resource-bundles) @ cas-workflow —
>  [INFO]
>  [INFO] — maven-resources-plugin:3.1.0:resources (default-resources) @ 
> cas-workflow —
>  [INFO] Using 'UTF-8' encoding to copy filtered resources.
>  [INFO] Copying 27 resources
>  [INFO] Copying 3 resources
>  [INFO]
>  [INFO] — maven-compiler-plugin:3.7.0:compile (default-compile) @ 
> cas-workflow —
>  [INFO] Changes detected - recompiling the module!
>  [INFO] Compiling 151 source files to 
> /home/jw/apache/oodt/workflow/target/classes
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/examples/ResmgrJobCondition.java:
>  Some input files use or override a deprecated API.
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/examples/ResmgrJobCondition.java:
>  Recompile with -Xlint:deprecation for details.
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/structs/WorkflowTask.java:
>  Some input files use unchecked or unsafe operations.
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/structs/WorkflowTask.java:
>  Recompile with -Xlint:unchecked for details.
>  [INFO] -
>  [ERROR] COMPILATION ERROR :
>  [INFO] -
>  [ERROR] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/engine/runner/AsynchronousLocalEngineRunner.java:[114,13]
>  cannot find symbol
&g

[jira] [Assigned] (OODT-1036) build failed on AArch64, Fedora 33

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha reassigned OODT-1036:
---

Assignee: Imesha Sudasingha

> build failed on AArch64, Fedora 33 
> ---
>
> Key: OODT-1036
> URL: https://issues.apache.org/jira/browse/OODT-1036
> Project: OODT
>  Issue Type: Bug
>Reporter: Lutz Weischer
>    Assignee: Imesha Sudasingha
>Priority: Major
>
> {code}
> [jw@cn05 oodt]$ mvn install -DskipTests
>  [INFO] — maven-assembly-plugin:2.6:single (default) @ cas-resource —
>  [INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
>  [INFO] Building tar: 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.tar.gz
>  [INFO] Building zip: 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.zip
>  [INFO]
>  [INFO] — maven-install-plugin:2.5.2:install (default-install) @ cas-resource 
> —
>  [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT.jar to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT.jar
>  [INFO] Installing /home/jw/apache/oodt/resource/pom.xml to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT.pom
>  [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.tar.gz 
> to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT-dist.tar.gz
>  [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.zip to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT-dist.zip
>  [INFO]
>  [INFO] < org.apache.oodt:cas-workflow 
> >
>  [INFO] Building Catalog and Archive Workflow Management Component 
> 1.10-SNAPSHOT [9/27]
>  [INFO] [ jar 
> ]-
>  [INFO]
>  [INFO] — maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
> cas-workflow —
>  [INFO]
>  [INFO] — avro-maven-plugin:1.8.2:schema (schemas) @ cas-workflow —
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowCondition.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowTask.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflow.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowInstance.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowInstancePage.avsc
>  [INFO]
>  [INFO] — avro-maven-plugin:1.8.2:idl-protocol (protocol) @ cas-workflow —
>  [INFO] Importing Directory: /home/jw/apache/oodt/workflow/src/main/avro/types
>  [INFO]
>  [INFO] — maven-remote-resources-plugin:1.5:process 
> (process-resource-bundles) @ cas-workflow —
>  [INFO]
>  [INFO] — maven-resources-plugin:3.1.0:resources (default-resources) @ 
> cas-workflow —
>  [INFO] Using 'UTF-8' encoding to copy filtered resources.
>  [INFO] Copying 27 resources
>  [INFO] Copying 3 resources
>  [INFO]
>  [INFO] — maven-compiler-plugin:3.7.0:compile (default-compile) @ 
> cas-workflow —
>  [INFO] Changes detected - recompiling the module!
>  [INFO] Compiling 151 source files to 
> /home/jw/apache/oodt/workflow/target/classes
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/examples/ResmgrJobCondition.java:
>  Some input files use or override a deprecated API.
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/examples/ResmgrJobCondition.java:
>  Recompile with -Xlint:deprecation for details.
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/structs/WorkflowTask.java:
>  Some input files use unchecked or unsafe operations.
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/structs/WorkflowTask.java:
>  Recompile with -Xlint:unchecked for details.
>  [INFO] -
>  [ERROR] COMPILATION ERROR :
>  [INFO] -
>  [ERROR] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/engine/runner/AsynchronousLocalEngineRunner.java:[114,13]
>  cannot find symbol
>  symbol: method destroy()
>  [INFO] 1 error
>  [INFO] ---

[jira] [Updated] (OODT-1037) React.js OPSUI file browser and workflow browser pages are not shown when there's no ingested files/workflows

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-1037:

Description: 
In the new React.js based OPSUI, when there are no products ingested, product 
browser page is not loaded (blank page and an error printed in console).

Similarly, workflow browser page is not loaded when there are no workflows.

And both UIs do not show anything if there's only one workflow or product.

  was:
In the new React.js based OPSUI, when there are no products ingested, product 
browser page is not loaded (blank page and an error printed in console).

Similarly, workflow browser page is not loaded when there are no workflows.


> React.js OPSUI file browser and workflow browser pages are not shown when 
> there's no ingested files/workflows
> -
>
> Key: OODT-1037
> URL: https://issues.apache.org/jira/browse/OODT-1037
> Project: OODT
>  Issue Type: Bug
>  Components: opsui
>    Reporter: Imesha Sudasingha
>Priority: Blocker
>
> In the new React.js based OPSUI, when there are no products ingested, product 
> browser page is not loaded (blank page and an error printed in console).
> Similarly, workflow browser page is not loaded when there are no workflows.
> And both UIs do not show anything if there's only one workflow or product.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (OODT-1037) React.js OPSUI file browser and workflow browser pages are not shown when there's no ingested files/workflows

[Imesha Sudasingha (Jira)]

Imesha Sudasingha created OODT-1037:
---

 Summary: React.js OPSUI file browser and workflow browser pages 
are not shown when there's no ingested files/workflows
 Key: OODT-1037
 URL: https://issues.apache.org/jira/browse/OODT-1037
 Project: OODT
  Issue Type: Bug
  Components: opsui
Reporter: Imesha Sudasingha


In the new React.js based OPSUI, when there are no products ingested, product 
browser page is not loaded (blank page and an error printed in console).

Similarly, workflow browser page is not loaded when there are no workflows.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Build failed in Jenkins: OODT » OODT Development Continuous #3

[Imesha Sudasingha]

Thanks! Merged.


On Sun, 8 Aug 2021 at 11:33, Nadeeshan  wrote:

> Hi Imesha,
>
> Send another PR [1] for fixing unit test failures.
> Will update the JDK 11 migration PR [2] soon.
>
> Thanks and regards,
> Nadeeshan
>
>
>
> [1] https://github.com/apache/oodt/pull/124
> [2] https://github.com/apache/oodt/pull/118
>
> On Sat, 7 Aug 2021 at 11:43, Imesha Sudasingha  wrote:
>
> > Hi Nadeeshan,
> >
> > Will you be able to extract the test failure fixes from your JDK 11 PR
> [1]
> > and send a separate PR?
> > Let's keep the JDK 11 migration for later.
> >
> > [1] https://github.com/apache/oodt/pull/118
> >
> > On Fri, 30 Jul 2021 at 23:37, Apache Jenkins Server <
> > jenk...@builds.apache.org> wrote:
> >
> > > See <
> > >
> >
> https://ci-builds.apache.org/job/OODT/job/OODT%20Development%20Continuous/3/display/redirect?page=changes
> > > >
> > >
> > > Changes:
> > >
> > > [174084F] add more select input to search bar
> > >
> > > [174084F] move product search UI to searchbar component
> > >
> > > [174084F] remove unused imports and state varaible references
> > >
> > > [174084F] add progress bar ui and remove unused code
> > >
> > > [174084F] add product ingesting progress calculation logic and format
> > code
> > >
> > > [174084F] get all product types
> > >
> > > [174084F] fix pagination in fm product browser
> > >
> > > [174084F] move file mager api call functions to a separate file
> > >
> > > [174084F] use ml prop to apply margin
> > >
> > > [github] add javadoc comment to getTotalNumOfProducts method
> > >
> > > [github] add javadoc comment to totalProducts getter and setter
> > >
> > > [Imesha Sudasingha] Add docker builds to relevant pom files
> > >
> > > [Imesha Sudasingha] Dockerized workflow manager
> > >
> > >
> > > --
> > > [...truncated 24.66 KB...]
> > > [INFO] Catalog and Archive Crawling Framework . SKIPPED
> > > [INFO] OODT CAS Curator Single Sign On Security Package ... SKIPPED
> > > [INFO] CAS Curation Web Services .. SKIPPED
> > > [INFO] Process Control System Core Package  SKIPPED
> > > [INFO] OODT Webapps ... SKIPPED
> > > [INFO] OODT Wicket Web Components . SKIPPED
> > > [INFO] CAS Curation Interface . SKIPPED
> > > [INFO] CAS PGE Adaptor Framework .. SKIPPED
> > > [INFO] CAS Installer Maven Mojo ... SKIPPED
> > > [INFO] OODT :: Archetypes :: OpsUI  SKIPPED
> > > [INFO] OODT :: Archetypes :: RADiX  SKIPPED
> > > [INFO] OODT :: Archetypes . SKIPPED
> > > [INFO] CAS File Manager Browser Web App ... SKIPPED
> > > [INFO] CAS Product Server Web Application . SKIPPED
> > > [INFO] CAS Workflow Manager Monitor Web App ... SKIPPED
> > > [INFO] CAS Workflow REST Services . SKIPPED
> > > [INFO] Process Control System Operator Interface Webapp ... SKIPPED
> > > [INFO] OODT Process Control System JAX-RS service layer ... SKIPPED
> > > [INFO] OODT ReactJs OPSUI . SKIPPED
> > > [INFO] OODT Deployment  SKIPPED
> > > [INFO] Apache OODT  SKIPPED
> > > [INFO]
> > >
> 
> > > [INFO] BUILD FAILURE
> > > [INFO]
> > >
> 
> > > [INFO] Total time:  58.370 s
> > > [INFO] Finished at: 2021-07-30T18:06:50Z
> > > [INFO]
> > >
> 
> > > ERROR: Asynchronous execution failure
> > > java.util.concurrent.ExecutionException: java.io.IOException:
> Unexpected
> > > Fingerprint type. Expected class hudson.model.Fingerprint or subclass
> but
> > > got class hudson.model.Fingerprint$RangeSet
> > > at hudson.remoting.Channel$2.adapt(Channel.java:1039)
> > > at hudson.remoting.Channel$2.adapt(Channel.java:1033)
> &g

Re: Build failed in Jenkins: OODT » OODT Development Continuous #3

[Imesha Sudasingha]

Hi Nadeeshan,

Will you be able to extract the test failure fixes from your JDK 11 PR [1]
and send a separate PR?
Let's keep the JDK 11 migration for later.

[1] https://github.com/apache/oodt/pull/118

On Fri, 30 Jul 2021 at 23:37, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> See <
> https://ci-builds.apache.org/job/OODT/job/OODT%20Development%20Continuous/3/display/redirect?page=changes
> >
>
> Changes:
>
> [174084F] add more select input to search bar
>
> [174084F] move product search UI to searchbar component
>
> [174084F] remove unused imports and state varaible references
>
> [174084F] add progress bar ui and remove unused code
>
> [174084F] add product ingesting progress calculation logic and format code
>
> [174084F] get all product types
>
> [174084F] fix pagination in fm product browser
>
> [174084F] move file mager api call functions to a separate file
>
> [174084F] use ml prop to apply margin
>
> [github] add javadoc comment to getTotalNumOfProducts method
>
> [github] add javadoc comment to totalProducts getter and setter
>
> [Imesha Sudasingha] Add docker builds to relevant pom files
>
> [Imesha Sudasingha] Dockerized workflow manager
>
>
> --
> [...truncated 24.66 KB...]
> [INFO] Catalog and Archive Crawling Framework . SKIPPED
> [INFO] OODT CAS Curator Single Sign On Security Package ... SKIPPED
> [INFO] CAS Curation Web Services .. SKIPPED
> [INFO] Process Control System Core Package  SKIPPED
> [INFO] OODT Webapps ... SKIPPED
> [INFO] OODT Wicket Web Components . SKIPPED
> [INFO] CAS Curation Interface . SKIPPED
> [INFO] CAS PGE Adaptor Framework .. SKIPPED
> [INFO] CAS Installer Maven Mojo ... SKIPPED
> [INFO] OODT :: Archetypes :: OpsUI  SKIPPED
> [INFO] OODT :: Archetypes :: RADiX  SKIPPED
> [INFO] OODT :: Archetypes . SKIPPED
> [INFO] CAS File Manager Browser Web App ... SKIPPED
> [INFO] CAS Product Server Web Application . SKIPPED
> [INFO] CAS Workflow Manager Monitor Web App ... SKIPPED
> [INFO] CAS Workflow REST Services . SKIPPED
> [INFO] Process Control System Operator Interface Webapp ... SKIPPED
> [INFO] OODT Process Control System JAX-RS service layer ... SKIPPED
> [INFO] OODT ReactJs OPSUI . SKIPPED
> [INFO] OODT Deployment  SKIPPED
> [INFO] Apache OODT  SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time:  58.370 s
> [INFO] Finished at: 2021-07-30T18:06:50Z
> [INFO]
> 
> ERROR: Asynchronous execution failure
> java.util.concurrent.ExecutionException: java.io.IOException: Unexpected
> Fingerprint type. Expected class hudson.model.Fingerprint or subclass but
> got class hudson.model.Fingerprint$RangeSet
> at hudson.remoting.Channel$2.adapt(Channel.java:1039)
> at hudson.remoting.Channel$2.adapt(Channel.java:1033)
> at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)
> at
> hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:186)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:144)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
> at hudson.remoting.UserRequest.perform(UserRequest.java:211)
> at hudson.remoting.UserRequest.perform(UserRequest.java:54)
> at hudson.remoting.Request$2.run(Request.java:375)
> at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:73)
> at
> java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by: java.io.IOException: Unexpected Fingerprint type. Expected
> class hudson.model.Fingerprint or subclass but got class
> hudson.model.Fingerprint$RangeSet
> at
> jenkins.fingerprints.FileFingerprintStorage.load(FileFingerprintStorage.java:98)
> 

Re: Where's OODT Jenkins Jobs

[Imesha Sudasingha]

Jenkins jobs are now available at https://ci-builds.apache.org/job/OODT/.
There are some failing tests which need attention.


On Tue, 13 Jul 2021 at 13:53, Imesha Sudasingha 
wrote:

> Created https://issues.apache.org/jira/browse/INFRA-22104 to get this
> resolved.
>
>
> On Fri, 25 Jun 2021 at 19:34, Imesha Sudasingha <
> imesha.sudasin...@gmail.com> wrote:
>
>> Hi Lewis,
>>
>> I don't have write access in Jenkins. How can I get that?
>>
>>
>> On Thu, 22 Apr 2021 at 10:27, Imesha Sudasingha <
>> imesha.sudasin...@gmail.com> wrote:
>>
>>> Hi Lewis,
>>>
>>> Seems like that's the case. I will create a new jenkins job. We can ask
>>> jenkins to poll a git repo for changes and build when a change happens.
>>>
>>> Thanks,
>>> Imesha
>>>
>>> On Wed, 21 Apr 2021 at 18:49, lewis john mcgibbney 
>>> wrote:
>>>
>>>> Hi Imesha,
>>>> The jobs may have been wiped when the Jenkins server move from
>>>> builds.a.o
>>>> to ci-builds.a.o.
>>>> If that is the case, then I would just create a Jenkinsfile pipeline
>>>> which
>>>> can be monitored in GitSCM from within the Jenkins job.
>>>> You can look at the Apache Gora project for an example of how to do
>>>> this...
>>>> lewismc
>>>>
>>>> On Wed, Apr 21, 2021 at 00:54  wrote:
>>>>
>>>> >
>>>> > dev Digest 21 Apr 2021 07:54:11 - Issue 1507
>>>> >
>>>> > Topics (messages 9034 through 9034)
>>>> >
>>>> > Where's OODT Jenkins Jobs
>>>> > 9034 by: Imesha Sudasingha
>>>> >
>>>> > Administrivia:
>>>> >
>>>> > -
>>>> > To post to the list, e-mail: dev@oodt.apache.org
>>>> > To unsubscribe, e-mail: dev-digest-unsubscr...@oodt.apache.org
>>>> > For additional commands, e-mail: dev-digest-h...@oodt.apache.org
>>>> >
>>>> > --
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > -- Forwarded message --
>>>> > From: Imesha Sudasingha 
>>>> > To: dev 
>>>> > Cc:
>>>> > Bcc:
>>>> > Date: Mon, 19 Apr 2021 13:01:50 +0530
>>>> > Subject: Where's OODT Jenkins Jobs
>>>> > Hi all,
>>>> >
>>>> > Couldn't find OODT jenkins jobs in https://ci-builds.apache.org. Any
>>>> idea
>>>> > where they are?
>>>> > Couldn't find at:
>>>> > 1. https://builds.apache.org/job/oodt-trunk/
>>>> > 2. https://ci-builds.apache.org
>>>> >
>>>> > Imesha
>>>> >
>>>> --
>>>> http://home.apache.org/~lewismc/
>>>> http://people.apache.org/keys/committer/lewismc
>>>>
>>>

[REPORT] OODT - July 2021

[Imesha Sudasingha]

## Description:
Apache OODT is a software framework as well as an architectural style for
the
rapid construction of scientific data systems. It provides components for
data
capture, curation, metadata extraction, workflow management, resource
management, and data processing.

## Issues:
No issues persist that require board's attention

## Membership Data:
Apache OODT was founded 2010-11-17 (11 years ago)
There are currently 47 committers and 46 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
- Nadeeshan Gimhana was added to the PMC on 2021-04-25
- No new committers. Last addition was Nadeeshan Gimhana on 2021-04-06.

## Project Activity:
- Last release was in October 2019.

Project activity has been high due to the ongoing GSoC 2021 project to
finalize the features of the ReactJS based OPSUI (dashboard). Along with
that,
we are working on minor improvements in other aspects of the project as
well.
Once this is completed, we plan on releasing OODT 2.0.

## Community Health:
Nadeeshan was added to PMC during the last reporting period. This is the 1st
addition to the PMC in around 3 years. Overall, community health is
satisfactory.

Re: Where's OODT Jenkins Jobs

[Imesha Sudasingha]

Created https://issues.apache.org/jira/browse/INFRA-22104 to get this
resolved.


On Fri, 25 Jun 2021 at 19:34, Imesha Sudasingha 
wrote:

> Hi Lewis,
>
> I don't have write access in Jenkins. How can I get that?
>
>
> On Thu, 22 Apr 2021 at 10:27, Imesha Sudasingha <
> imesha.sudasin...@gmail.com> wrote:
>
>> Hi Lewis,
>>
>> Seems like that's the case. I will create a new jenkins job. We can ask
>> jenkins to poll a git repo for changes and build when a change happens.
>>
>> Thanks,
>> Imesha
>>
>> On Wed, 21 Apr 2021 at 18:49, lewis john mcgibbney 
>> wrote:
>>
>>> Hi Imesha,
>>> The jobs may have been wiped when the Jenkins server move from builds.a.o
>>> to ci-builds.a.o.
>>> If that is the case, then I would just create a Jenkinsfile pipeline
>>> which
>>> can be monitored in GitSCM from within the Jenkins job.
>>> You can look at the Apache Gora project for an example of how to do
>>> this...
>>> lewismc
>>>
>>> On Wed, Apr 21, 2021 at 00:54  wrote:
>>>
>>> >
>>> > dev Digest 21 Apr 2021 07:54:11 - Issue 1507
>>> >
>>> > Topics (messages 9034 through 9034)
>>> >
>>> > Where's OODT Jenkins Jobs
>>> > 9034 by: Imesha Sudasingha
>>> >
>>> > Administrivia:
>>> >
>>> > -
>>> > To post to the list, e-mail: dev@oodt.apache.org
>>> > To unsubscribe, e-mail: dev-digest-unsubscr...@oodt.apache.org
>>> > For additional commands, e-mail: dev-digest-h...@oodt.apache.org
>>> >
>>> > --
>>> >
>>> >
>>> >
>>> >
>>> > -- Forwarded message --
>>> > From: Imesha Sudasingha 
>>> > To: dev 
>>> > Cc:
>>> > Bcc:
>>> > Date: Mon, 19 Apr 2021 13:01:50 +0530
>>> > Subject: Where's OODT Jenkins Jobs
>>> > Hi all,
>>> >
>>> > Couldn't find OODT jenkins jobs in https://ci-builds.apache.org. Any
>>> idea
>>> > where they are?
>>> > Couldn't find at:
>>> > 1. https://builds.apache.org/job/oodt-trunk/
>>> > 2. https://ci-builds.apache.org
>>> >
>>> > Imesha
>>> >
>>> --
>>> http://home.apache.org/~lewismc/
>>> http://people.apache.org/keys/committer/lewismc
>>>
>>

Re: Where's OODT Jenkins Jobs

[Imesha Sudasingha]

Hi Lewis,

I don't have write access in Jenkins. How can I get that?


On Thu, 22 Apr 2021 at 10:27, Imesha Sudasingha 
wrote:

> Hi Lewis,
>
> Seems like that's the case. I will create a new jenkins job. We can ask
> jenkins to poll a git repo for changes and build when a change happens.
>
> Thanks,
> Imesha
>
> On Wed, 21 Apr 2021 at 18:49, lewis john mcgibbney 
> wrote:
>
>> Hi Imesha,
>> The jobs may have been wiped when the Jenkins server move from builds.a.o
>> to ci-builds.a.o.
>> If that is the case, then I would just create a Jenkinsfile pipeline which
>> can be monitored in GitSCM from within the Jenkins job.
>> You can look at the Apache Gora project for an example of how to do
>> this...
>> lewismc
>>
>> On Wed, Apr 21, 2021 at 00:54  wrote:
>>
>> >
>> > dev Digest 21 Apr 2021 07:54:11 -0000 Issue 1507
>> >
>> > Topics (messages 9034 through 9034)
>> >
>> > Where's OODT Jenkins Jobs
>> > 9034 by: Imesha Sudasingha
>> >
>> > Administrivia:
>> >
>> > -
>> > To post to the list, e-mail: dev@oodt.apache.org
>> > To unsubscribe, e-mail: dev-digest-unsubscr...@oodt.apache.org
>> > For additional commands, e-mail: dev-digest-h...@oodt.apache.org
>> >
>> > --
>> >
>> >
>> >
>> >
>> > -- Forwarded message --
>> > From: Imesha Sudasingha 
>> > To: dev 
>> > Cc:
>> > Bcc:
>> > Date: Mon, 19 Apr 2021 13:01:50 +0530
>> > Subject: Where's OODT Jenkins Jobs
>> > Hi all,
>> >
>> > Couldn't find OODT jenkins jobs in https://ci-builds.apache.org. Any
>> idea
>> > where they are?
>> > Couldn't find at:
>> > 1. https://builds.apache.org/job/oodt-trunk/
>> > 2. https://ci-builds.apache.org
>> >
>> > Imesha
>> >
>> --
>> http://home.apache.org/~lewismc/
>> http://people.apache.org/keys/committer/lewismc
>>
>

Re: React OPSUI: oodt_fm_plugin breaks OPSUI web app layout styles

[Imesha Sudasingha]

Let's proceed with this. I have merged it to the development branch.

On Wed, 23 Jun 2021 at 18:10, Pavindu Lakshan 
wrote:

> Hi Imesha,
>
> I too tried different workarounds but nothing worked. The only way it
> worked was when the components in the plugin are implemented inside the
> sample app itself. Therefore, your change seems like the only
> viable solution for now.
>
> Thanks and regards,
> Pavindu
>
>
> On Wed, Jun 23, 2021 at 1:20 PM Imesha Sudasingha <
> imesha.sudasin...@gmail.com> wrote:
>
> > Hi Pavindu,
> >
> > I went through the code and couldn't find an easy solution for this.
> Tried
> > using npm workspaces, etc. The amount of work (writing separate types,
> etc)
> > required to get that to a developer friendly state is high.
> > Therefore, decided to make everything a single project and sent the PR
> [1].
> > I will merge it later today if there's no objections.
> >
> > [1] https://github.com/apache/oodt/pull/119
> >
> > Thanks,
> > Imesha
> >
>

Re: React OPSUI: oodt_fm_plugin breaks OPSUI web app layout styles

[Imesha Sudasingha]

Hi Pavindu,

I went through the code and couldn't find an easy solution for this. Tried
using npm workspaces, etc. The amount of work (writing separate types, etc)
required to get that to a developer friendly state is high.
Therefore, decided to make everything a single project and sent the PR [1].
I will merge it later today if there's no objections.

[1] https://github.com/apache/oodt/pull/119

Thanks,
Imesha

Re: cannot resolve avrotypes in oodt filemgr

[Imesha Sudasingha]

Thanks Lewis for the explanation. It sums up everything you need to know
about AvroRPC.

@Pavindu, you were running the file manager using Intellij IDEA right?
Before running that, make sure you have built the file manager project with
`mvn clean install -DskipTests`.


On Thu, 10 Jun 2021 at 05:33, lewis john mcgibbney 
wrote:

> Hi Pavindu,
>
> Avro provides:
> * Rich data structures.
> * A compact, fast, binary data format.
> * A container file, to store persistent data.
> * Remote procedure call (RPC).
> * Simple integration with dynamic languages. Code generation is not
> required to read or write data files nor to use or implement RPC protocols.
> Code generation as an optional optimization, only worth implementing for
> statically typed languages.
>
> The Avro specification (https://avro.apache.org/docs/current/spec.html)
> states "A Schema is represented in JSON by one of..."
>
> In OODT, this means that all objects are modeled as Avro schemas. In the
> case of Filemgr, all of the Avro schemas live in source code management in
> https://github.com/apache/oodt/tree/master/filemgr/src/main/avro/types
> and are compiled into the OODT POJOs at compile time courtesy of the
> avro-maven-plugin
> https://github.com/apache/oodt/blob/master/filemgr/pom.xml#L247-L295
>
> Please let me know if you have any questions.
> lewismc
>
> On Tue, Jun 8, 2021 at 9:15 PM  wrote:
>
> >
> > dev Digest 9 Jun 2021 04:15:16 - Issue 1518
> >
> > Topics (messages 9049 through 9049)
> >
> > cannot resolve avrotypes in oodt filemgr
> > 9049 by: Pavindu Lakshan
> >
> > Administrivia:
> >
> > -
> > To post to the list, e-mail: dev@oodt.apache.org
> > To unsubscribe, e-mail: dev-digest-unsubscr...@oodt.apache.org
> > For additional commands, e-mail: dev-digest-h...@oodt.apache.org
> >
> > --
> >
> >
> >
> >
> > -- Forwarded message --
> > From: Pavindu Lakshan 
> > To: dev@oodt.apache.org
> > Cc:
> > Bcc:
> > Date: Wed, 9 Jun 2021 09:45:04 +0530
> > Subject: cannot resolve avrotypes in oodt filemgr
> > Hi all,
> >
> > When I'm trying to ingest a product, I'm getting the following error.
> >
> > *NullPointerException: null of
> > org.apache.oodt.cas.filemgr.structs.avrotypes.AvroProductType*
> >
> > Also in the IntelliJ IDE, I am getting the error *Cannot resolve symbol
> > 'avrotypes'*
> >
> > Turns out, there is no avrotypes struct
> > in filemgr/src/main/java/org/apache/oodt/cas/filemgr/structs. But they
> are
> > imported in AvroFileManagerClient.java[1].
> >
> > Can someone point me out a way to fix this error? Sorry if I'm missing
> > something obvious.
> >
> > Thanks and regards,
> > Pavindu
> >
> >  [1]
> >
> >
> https://github.com/apache/oodt/blob/master/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/AvroFileManagerClient.java
> >
>
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>

Re: Starting working on the React dashboard

[Imesha Sudasingha]

Hi Pavindu,

Yes, we need to start on that. But first, let's get the setup correct and
get everything working properly.
And we can kick off the dev work after the next synup.

Imesha


On Mon, 7 Jun 2021 at 06:49, Pavindu Lakshan 
wrote:

> Hi Imesha and Nadeeshan,
>
> Since the coding period begins today, shall I start working on the React
> dashboard from now on? or is there anything that I should start working on
> instead? The planned work for the first month is as follows.
>
>- Refactor existing class components in the oodt_fm_plugin and
>oodt_wm_plugin
>- Implement searching products by product ID in the product search page
>- Implement progress indicator UI components for showing the progress of
>the workflows and file ingestion processes
>
> Looking forward to your feedback.
>
> Thanks and regards,
> Pavindu
>

Welcome Nadeeshan to OODT PMC/Committers

[Imesha Sudasingha]

Hi all,

Nadeeshan had been contributing continuously to OODT over the last 2 years.
Starting from GSoC 2019, Nadeeshan worked on ReactJs based novel OPSUI and
JDK 11 support as the key contributions.

As an appreciation for the selfless contributions and continuous efforts to
make OODT better, I'm pleased to welcome Nadeeshan as an OODT committer and
a PMC member.

Nadeeshan, congratulations and welcome! See you around.

Imesha

Re: Where's OODT Jenkins Jobs

[Imesha Sudasingha]

Hi Lewis,

Seems like that's the case. I will create a new jenkins job. We can ask
jenkins to poll a git repo for changes and build when a change happens.

Thanks,
Imesha

On Wed, 21 Apr 2021 at 18:49, lewis john mcgibbney 
wrote:

> Hi Imesha,
> The jobs may have been wiped when the Jenkins server move from builds.a.o
> to ci-builds.a.o.
> If that is the case, then I would just create a Jenkinsfile pipeline which
> can be monitored in GitSCM from within the Jenkins job.
> You can look at the Apache Gora project for an example of how to do this...
> lewismc
>
> On Wed, Apr 21, 2021 at 00:54  wrote:
>
> >
> > dev Digest 21 Apr 2021 07:54:11 - Issue 1507
> >
> > Topics (messages 9034 through 9034)
> >
> > Where's OODT Jenkins Jobs
> > 9034 by: Imesha Sudasingha
> >
> > Administrivia:
> >
> > -
> > To post to the list, e-mail: dev@oodt.apache.org
> > To unsubscribe, e-mail: dev-digest-unsubscr...@oodt.apache.org
> > For additional commands, e-mail: dev-digest-h...@oodt.apache.org
> >
> > ----------
> >
> >
> >
> >
> > -- Forwarded message --
> > From: Imesha Sudasingha 
> > To: dev 
> > Cc:
> > Bcc:
> > Date: Mon, 19 Apr 2021 13:01:50 +0530
> > Subject: Where's OODT Jenkins Jobs
> > Hi all,
> >
> > Couldn't find OODT jenkins jobs in https://ci-builds.apache.org. Any
> idea
> > where they are?
> > Couldn't find at:
> > 1. https://builds.apache.org/job/oodt-trunk/
> > 2. https://ci-builds.apache.org
> >
> > Imesha
> >
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>

Where's OODT Jenkins Jobs

[Imesha Sudasingha]

Hi all,

Couldn't find OODT jenkins jobs in https://ci-builds.apache.org. Any idea
where they are?
Couldn't find at:
1. https://builds.apache.org/job/oodt-trunk/
2. https://ci-builds.apache.org

Imesha

[jira] [Commented] (OODT-1036) build failed on AArch64, Fedora 33

[Imesha Sudasingha (Jira)]

[ 
https://issues.apache.org/jira/browse/OODT-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17324784#comment-17324784
 ] 

Imesha Sudasingha commented on OODT-1036:
-

I could reproduce the test failure. Need to have a look. I was wondering why 
jenkins build did not complain about this.

> build failed on AArch64, Fedora 33 
> ---
>
> Key: OODT-1036
> URL: https://issues.apache.org/jira/browse/OODT-1036
> Project: OODT
>  Issue Type: Bug
>Reporter: Lutz Weischer
>Priority: Major
>
> {code}
> [jw@cn05 oodt]$ mvn install -DskipTests
>  [INFO] — maven-assembly-plugin:2.6:single (default) @ cas-resource —
>  [INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
>  [INFO] Building tar: 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.tar.gz
>  [INFO] Building zip: 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.zip
>  [INFO]
>  [INFO] — maven-install-plugin:2.5.2:install (default-install) @ cas-resource 
> —
>  [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT.jar to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT.jar
>  [INFO] Installing /home/jw/apache/oodt/resource/pom.xml to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT.pom
>  [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.tar.gz 
> to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT-dist.tar.gz
>  [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.zip to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT-dist.zip
>  [INFO]
>  [INFO] < org.apache.oodt:cas-workflow 
> >
>  [INFO] Building Catalog and Archive Workflow Management Component 
> 1.10-SNAPSHOT [9/27]
>  [INFO] [ jar 
> ]-
>  [INFO]
>  [INFO] — maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
> cas-workflow —
>  [INFO]
>  [INFO] — avro-maven-plugin:1.8.2:schema (schemas) @ cas-workflow —
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowCondition.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowTask.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflow.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowInstance.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowInstancePage.avsc
>  [INFO]
>  [INFO] — avro-maven-plugin:1.8.2:idl-protocol (protocol) @ cas-workflow —
>  [INFO] Importing Directory: /home/jw/apache/oodt/workflow/src/main/avro/types
>  [INFO]
>  [INFO] — maven-remote-resources-plugin:1.5:process 
> (process-resource-bundles) @ cas-workflow —
>  [INFO]
>  [INFO] — maven-resources-plugin:3.1.0:resources (default-resources) @ 
> cas-workflow —
>  [INFO] Using 'UTF-8' encoding to copy filtered resources.
>  [INFO] Copying 27 resources
>  [INFO] Copying 3 resources
>  [INFO]
>  [INFO] — maven-compiler-plugin:3.7.0:compile (default-compile) @ 
> cas-workflow —
>  [INFO] Changes detected - recompiling the module!
>  [INFO] Compiling 151 source files to 
> /home/jw/apache/oodt/workflow/target/classes
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/examples/ResmgrJobCondition.java:
>  Some input files use or override a deprecated API.
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/examples/ResmgrJobCondition.java:
>  Recompile with -Xlint:deprecation for details.
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/structs/WorkflowTask.java:
>  Some input files use unchecked or unsafe operations.
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/structs/WorkflowTask.java:
>  Recompile with -Xlint:unchecked for details.
>  [INFO] -
>  [ERROR] COMPILATION ERROR :
>  [INFO] -
>  [ERROR] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/engine/runner/AsynchronousLocalEngineRunner.java:[114,13]
>  cannot find symbol
>  symbo

[jira] [Commented] (OODT-1036) build failed on AArch64, Fedora 33

[Imesha Sudasingha (Jira)]

[ 
https://issues.apache.org/jira/browse/OODT-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17321875#comment-17321875
 ] 

Imesha Sudasingha commented on OODT-1036:
-

[~LutzWeischerFujitsu] I cloned a new copy and built with java 8 (AdoptOpenJDK) 
and it was built successfully. Can you try with *mvn clean install -DskipTests* 
instead?

> build failed on AArch64, Fedora 33 
> ---
>
> Key: OODT-1036
> URL: https://issues.apache.org/jira/browse/OODT-1036
> Project: OODT
>  Issue Type: Bug
>Reporter: Lutz Weischer
>Priority: Major
>
> {code}
> [jw@cn05 oodt]$ mvn install -DskipTests
>  [INFO] — maven-assembly-plugin:2.6:single (default) @ cas-resource —
>  [INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
>  [INFO] Building tar: 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.tar.gz
>  [INFO] Building zip: 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.zip
>  [INFO]
>  [INFO] — maven-install-plugin:2.5.2:install (default-install) @ cas-resource 
> —
>  [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT.jar to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT.jar
>  [INFO] Installing /home/jw/apache/oodt/resource/pom.xml to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT.pom
>  [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.tar.gz 
> to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT-dist.tar.gz
>  [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.zip to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT-dist.zip
>  [INFO]
>  [INFO] < org.apache.oodt:cas-workflow 
> >
>  [INFO] Building Catalog and Archive Workflow Management Component 
> 1.10-SNAPSHOT [9/27]
>  [INFO] [ jar 
> ]-
>  [INFO]
>  [INFO] — maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
> cas-workflow —
>  [INFO]
>  [INFO] — avro-maven-plugin:1.8.2:schema (schemas) @ cas-workflow —
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowCondition.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowTask.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflow.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowInstance.avsc
>  [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowInstancePage.avsc
>  [INFO]
>  [INFO] — avro-maven-plugin:1.8.2:idl-protocol (protocol) @ cas-workflow —
>  [INFO] Importing Directory: /home/jw/apache/oodt/workflow/src/main/avro/types
>  [INFO]
>  [INFO] — maven-remote-resources-plugin:1.5:process 
> (process-resource-bundles) @ cas-workflow —
>  [INFO]
>  [INFO] — maven-resources-plugin:3.1.0:resources (default-resources) @ 
> cas-workflow —
>  [INFO] Using 'UTF-8' encoding to copy filtered resources.
>  [INFO] Copying 27 resources
>  [INFO] Copying 3 resources
>  [INFO]
>  [INFO] — maven-compiler-plugin:3.7.0:compile (default-compile) @ 
> cas-workflow —
>  [INFO] Changes detected - recompiling the module!
>  [INFO] Compiling 151 source files to 
> /home/jw/apache/oodt/workflow/target/classes
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/examples/ResmgrJobCondition.java:
>  Some input files use or override a deprecated API.
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/examples/ResmgrJobCondition.java:
>  Recompile with -Xlint:deprecation for details.
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/structs/WorkflowTask.java:
>  Some input files use unchecked or unsafe operations.
>  [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/structs/WorkflowTask.java:
>  Recompile with -Xlint:unchecked for details.
>  [INFO] -
>  [ERROR] COMPILATION ERROR :
>  [INFO] -
>  [ERROR] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/engine/runner/AsynchronousLocalEngineRunner.java:[114,13]
>  cannot fi

Re: GSoC 2021 - Requesting feedback on the proposal for OODT - 1035

[Imesha Sudasingha]

Hi Pavindu,

Had a look at the proposal and it looks good to me. Added 2 minor comments,
one to the timeline and another to the deliverables.

If time permits, can you add some screenshots of the existing OPSUI
(ReactJs version), which you will be improving for completeness.

Thanks,
Imesha

On Tue, 13 Apr 2021 at 09:33, Nadeeshan  wrote:

> Hi Pavindu,
>
> Great progress!!
>
> 1) I couldn't still find where the REST API s for the file manager
> > component is implemented in the repository. Can you point me to that?
> >
>
> You can find the REST APIs used in the React app from [1] in the Github
> repo.
>
> 2) With that error being fixed, I could view the existing implementation of
> > the React.js OPSUI and almost completed the proposal. I also shared the
> > proposal through the GSoC dashboard.
> >
>
> Cool !!. Imesha will look into this and it is better if you can share the
> proposal here also, in the dev list for getting a wider reach of the
> community.
>
> Thanks and regards,
> Nadeeshan
>
> [1]
>
> https://github.com/apache/oodt/blob/development/webapp/fmprod/src/main/java/org/apache/oodt/cas/product/jaxrs/services/FileManagerJaxrsServiceV2.java
>
>
> On Mon, 12 Apr 2021, 08:06 Pavindu Lakshan, 
> wrote:
>
> > Hi Imesha and Nadeeshan,
> >
> > After trying for several days, I was able to fix the issue that I
> mentioned
> > in the last email. I also published the solution
> >  under the question I
> posted
> > on StackOverflow. However, I still have a few questions to clarify.
> >
> > 1) I couldn't still find where the REST API s for the file manager
> > component is implemented in the repository. Can you point me to that?
> >
> > 2) With that error being fixed, I could view the existing implementation
> of
> > the React.js OPSUI and almost completed the proposal. I also shared the
> > proposal through the GSoC dashboard.
> >
> > I know it's been too close to the deadline, but I couldn't work much on
> the
> > project due to my university exams held in the last week. It will be a
> > great help if you can view my proposal and give me feedback on that.
> >
> > Thanks and best regards
> > Pavindu
> >
>

[jira] [Updated] (OODT-1036) build failed on AArch64, Fedora 33

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-1036:

Description: 
{code}
[jw@cn05 oodt]$ mvn install -DskipTests
 [INFO] — maven-assembly-plugin:2.6:single (default) @ cas-resource —
 [INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
 [INFO] Building tar: 
/home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.tar.gz
 [INFO] Building zip: 
/home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.zip
 [INFO]
 [INFO] — maven-install-plugin:2.5.2:install (default-install) @ cas-resource —
 [INFO] Installing 
/home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT.jar to 
/home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT.jar
 [INFO] Installing /home/jw/apache/oodt/resource/pom.xml to 
/home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT.pom
 [INFO] Installing 
/home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.tar.gz to 
/home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT-dist.tar.gz
 [INFO] Installing 
/home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.zip to 
/home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT-dist.zip
 [INFO]
 [INFO] < org.apache.oodt:cas-workflow >
 [INFO] Building Catalog and Archive Workflow Management Component 
1.10-SNAPSHOT [9/27]
 [INFO] [ jar ]-
 [INFO]
 [INFO] — maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
cas-workflow —
 [INFO]
 [INFO] — avro-maven-plugin:1.8.2:schema (schemas) @ cas-workflow —
 [INFO] Importing File: 
/home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowCondition.avsc
 [INFO] Importing File: 
/home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowTask.avsc
 [INFO] Importing File: 
/home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflow.avsc
 [INFO] Importing File: 
/home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowInstance.avsc
 [INFO] Importing File: 
/home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowInstancePage.avsc
 [INFO]
 [INFO] — avro-maven-plugin:1.8.2:idl-protocol (protocol) @ cas-workflow —
 [INFO] Importing Directory: /home/jw/apache/oodt/workflow/src/main/avro/types
 [INFO]
 [INFO] — maven-remote-resources-plugin:1.5:process (process-resource-bundles) 
@ cas-workflow —
 [INFO]
 [INFO] — maven-resources-plugin:3.1.0:resources (default-resources) @ 
cas-workflow —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] Copying 27 resources
 [INFO] Copying 3 resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.7.0:compile (default-compile) @ cas-workflow —
 [INFO] Changes detected - recompiling the module!
 [INFO] Compiling 151 source files to 
/home/jw/apache/oodt/workflow/target/classes
 [INFO] 
/home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/examples/ResmgrJobCondition.java:
 Some input files use or override a deprecated API.
 [INFO] 
/home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/examples/ResmgrJobCondition.java:
 Recompile with -Xlint:deprecation for details.
 [INFO] 
/home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/structs/WorkflowTask.java:
 Some input files use unchecked or unsafe operations.
 [INFO] 
/home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/structs/WorkflowTask.java:
 Recompile with -Xlint:unchecked for details.
 [INFO] -
 [ERROR] COMPILATION ERROR :
 [INFO] -
 [ERROR] 
/home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/engine/runner/AsynchronousLocalEngineRunner.java:[114,13]
 cannot find symbol
 symbol: method destroy()
 [INFO] 1 error
 [INFO] -
 [INFO] 
 [INFO] Reactor Summary for Apache OODT 1.10-SNAPSHOT:
 [INFO]
 [INFO] OODT Core .. SUCCESS [ 6.290 s]
 [INFO] Common Utilities ... SUCCESS [ 14.864 s]
 [INFO] CAS Command Line Interface . SUCCESS [ 14.411 s]
 [INFO] OODT - Configuration Management  SUCCESS [ 13.700 s]
 [INFO] Process Control System Input Data Package .. SUCCESS [ 8.088 s]
 [INFO] Catalog and Archive Service Generic Multi-valued Metadata Container 
SUCCESS [ 11.297 s]
 [INFO] Catalog and Archive File Management Component .. SUCCESS [01:31 min]
 [INFO] Catalog and Archive Resource Management Component .. SUCCESS [ 28.155 s]
 [INFO] C

[jira] [Commented] (OODT-1036) build failed on AArch64, Fedora 33

[Imesha Sudasingha (Jira)]

[ 
https://issues.apache.org/jira/browse/OODT-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319885#comment-17319885
 ] 

Imesha Sudasingha commented on OODT-1036:
-

[~LutzWeischerFujitsu]: What is the Java version you were using? I assume you 
were using a Java version higher than 8.

> build failed on AArch64, Fedora 33 
> ---
>
> Key: OODT-1036
> URL: https://issues.apache.org/jira/browse/OODT-1036
> Project: OODT
>  Issue Type: Bug
>Reporter: Lutz Weischer
>Priority: Major
>
> [jw@cn05 oodt]$ mvn install -DskipTests
> ... 
> [INFO] --- maven-assembly-plugin:2.6:single (default) @ cas-resource ---
> [INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
> [INFO] Building tar: 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.tar.gz
> [INFO] Building zip: 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.zip
> [INFO]
> [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ 
> cas-resource ---
> [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT.jar to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT.jar
> [INFO] Installing /home/jw/apache/oodt/resource/pom.xml to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT.pom
> [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.tar.gz 
> to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT-dist.tar.gz
> [INFO] Installing 
> /home/jw/apache/oodt/resource/target/cas-resource-1.10-SNAPSHOT-dist.zip to 
> /home/jw/.m2/repository/org/apache/oodt/cas-resource/1.10-SNAPSHOT/cas-resource-1.10-SNAPSHOT-dist.zip
> [INFO]
> [INFO] < org.apache.oodt:cas-workflow 
> >
> [INFO] Building Catalog and Archive Workflow Management Component 
> 1.10-SNAPSHOT [9/27]
> [INFO] [ jar 
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
> cas-workflow ---
> [INFO]
> [INFO] --- avro-maven-plugin:1.8.2:schema (schemas) @ cas-workflow ---
> [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowCondition.avsc
> [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowTask.avsc
> [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflow.avsc
> [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowInstance.avsc
> [INFO] Importing File: 
> /home/jw/apache/oodt/workflow/src/main/avro/types/AvroWorkflowInstancePage.avsc
> [INFO]
> [INFO] --- avro-maven-plugin:1.8.2:idl-protocol (protocol) @ cas-workflow ---
> [INFO] Importing Directory: /home/jw/apache/oodt/workflow/src/main/avro/types
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.5:process 
> (process-resource-bundles) @ cas-workflow ---
> [INFO]
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> cas-workflow ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 27 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ 
> cas-workflow ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 151 source files to 
> /home/jw/apache/oodt/workflow/target/classes
> [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/examples/ResmgrJobCondition.java:
>  Some input files use or override a deprecated API.
> [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/examples/ResmgrJobCondition.java:
>  Recompile with -Xlint:deprecation for details.
> [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/structs/WorkflowTask.java:
>  Some input files use unchecked or unsafe operations.
> [INFO] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/structs/WorkflowTask.java:
>  Recompile with -Xlint:unchecked for details.
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR] 
> /home/jw/apache/oodt/workflow/src/main/java/org/apache/oodt/cas/workflow/engine/runner/AsynchronousLocalEngineRunner.java:[114,13]
>  cannot find symbol
>   symbol: method destroy()
> [INFO] 1 error
> 

Re: GSoC 2021 - OODT React components are broken

[Imesha Sudasingha]

Hi Pavindu,

The attached image is not available. Probably because the emails going
through the Apache mail servers don't support them. Can you host the image
somewhere else and put a link instead?

Regarding the error you are facing, Nadeeshan who did the initial
implementation of the UI will be able to help. I will have a look at it as
well. Been busy these few days.

Imesha

On Fri, 2 Apr 2021 at 23:15, Pavindu Lakshan 
wrote:

> Hi Imesha,
>
> By following the instructions in the last email, I was able to view the
> React.js dashboard homepage without any CORS errors. However, when
> navigating to the `/product`, `/products` and `/productIngest` pages, the
> dashboard fails to render the correct pages as expected. Instead, I see an
> error like follows.
> [image: oodt_react_mui_style_isssue.PNG]
>
> This error doesn't occur when "withStyle" HOC is removed from the exported
> components, but then it affects the styles. I also opened a question on
> StackOverflow <https://stackoverflow.com/q/66922317/8810941> asking for a
> solution for this issue and still trying to fix that issue, because it's
> essential to fix this issue in order to view what has already been done in
> the OPSUI React.js dashboard.
>
> Regarding the proposal, there does exist such a functionality in the GSoC
> dashboard as you mentioned. I will share the proposal soon once I am able
> to solve the above-mentioned problem and fully view the existing features
> in the React.js OPSUI dashboard.
>
> Thank you and best regards
> Pavindu
>
> On Wed, Mar 31, 2021 at 7:43 AM Imesha Sudasingha 
> wrote:
>
>> Hi Pavindu,
>>
>> Great progress. This CORS issue is expected because we run React.Js on a
>> separate port than the port where the REST APIs are running. Therefore,
>> for
>> the moment, try with using a CORS plugin for your browser. In the future,
>> we have to support adding CORS configuration to the REST APIs.
>>
>> Regarding the proposal, around 2,3 years back, GSoC dashboard allowed
>> uploading a link to your proposal and sharing it as a draft. Does that
>> functionality exist now?
>>
>> Imesha
>>
>> On Tue, 30 Mar 2021 at 11:28, Pavindu Lakshan 
>> wrote:
>>
>> > Hi Imesha,
>> >
>> > I was able to solve the issues mentioned in the last email. The issues
>> in
>> > the wifi driver of my computer had caused those. Managed to get the
>> > React.js dashboard up and running as well, but still getting CORS issues
>> > therefore OODT ingested files are not shown in the dashboard.
>> >
>> > I also hope to share my project proposal with you, as a Google doc, to
>> get
>> > your feedback on it. Can you let me know if it is okay to share it with
>> > your personal Gmail address, or what process I should follow?
>> >
>> > Thank you
>> >
>> > Best regards
>> > Pavindu Lakshan
>> >
>> > On Sat, Mar 27, 2021 at 9:08 PM Pavindu Lakshan <
>> pavindulaks...@gmail.com>
>> > wrote:
>> >
>> > > Hi Imesha,
>> > >
>> > > It took me several days to respond because of my university exams.
>> > > However, I went through the articles you mentioned and they helped me
>> to
>> > > broaden my understanding of what Apache OODT is and its use cases.
>> Thank
>> > > you for that.
>> > >
>> > > Also, I cloned the repository, was able to get it up and running with
>> > > Docker on a Windows machine and visited the existing OPS UI dashboard.
>> > > Nevertheless, I faced the following problems and wasn't able to solve
>> > them
>> > > on my own.
>> > >
>> > > 1. When trying to ingest a txt file as mentioned in this medium
>> article
>> > > <https://faun.pub/apache-oodt-with-docker-84d32525c798>, I get the
>> > > following error.
>> > >
>> > > *error:** ERROR: Failed to ingest product 'test.txt' :
>> > > java.net.ConnectException: Connection refused (Connection refused)*
>> > > *what I have tried up to now:* searched for a solution but none was
>> > > found. Does this happen because I'm on Windows OS?
>> > > *steps to reproduce:* Follow the medium article from the beginning and
>> > > this error appears when trying out step 9.
>> > >
>> > > 2. I tried to view the React.js app by checking out to
>> /react-components
>> > > of the development branch. But when I tried to install NPM
>> dependencies
>> > in
>> > > plug

Re: GSoC 2021

[Imesha Sudasingha]

Hi Pavindu,

Great progress. This CORS issue is expected because we run React.Js on a
separate port than the port where the REST APIs are running. Therefore, for
the moment, try with using a CORS plugin for your browser. In the future,
we have to support adding CORS configuration to the REST APIs.

Regarding the proposal, around 2,3 years back, GSoC dashboard allowed
uploading a link to your proposal and sharing it as a draft. Does that
functionality exist now?

Imesha

On Tue, 30 Mar 2021 at 11:28, Pavindu Lakshan 
wrote:

> Hi Imesha,
>
> I was able to solve the issues mentioned in the last email. The issues in
> the wifi driver of my computer had caused those. Managed to get the
> React.js dashboard up and running as well, but still getting CORS issues
> therefore OODT ingested files are not shown in the dashboard.
>
> I also hope to share my project proposal with you, as a Google doc, to get
> your feedback on it. Can you let me know if it is okay to share it with
> your personal Gmail address, or what process I should follow?
>
> Thank you
>
> Best regards
> Pavindu Lakshan
>
> On Sat, Mar 27, 2021 at 9:08 PM Pavindu Lakshan 
> wrote:
>
> > Hi Imesha,
> >
> > It took me several days to respond because of my university exams.
> > However, I went through the articles you mentioned and they helped me to
> > broaden my understanding of what Apache OODT is and its use cases. Thank
> > you for that.
> >
> > Also, I cloned the repository, was able to get it up and running with
> > Docker on a Windows machine and visited the existing OPS UI dashboard.
> > Nevertheless, I faced the following problems and wasn't able to solve
> them
> > on my own.
> >
> > 1. When trying to ingest a txt file as mentioned in this medium article
> > <https://faun.pub/apache-oodt-with-docker-84d32525c798>, I get the
> > following error.
> >
> > *error:** ERROR: Failed to ingest product 'test.txt' :
> > java.net.ConnectException: Connection refused (Connection refused)*
> > *what I have tried up to now:* searched for a solution but none was
> > found. Does this happen because I'm on Windows OS?
> > *steps to reproduce:* Follow the medium article from the beginning and
> > this error appears when trying out step 9.
> >
> > 2. I tried to view the React.js app by checking out to /react-components
> > of the development branch. But when I tried to install NPM dependencies
> in
> > plugins, I get the below errors.
> >
> > *errors:*
> > In OPSUI sample app: invalid json response body at
> > https://registry.npmjs.org/@material-ui%2fstyles reason: Unexpected end
> > of JSON input
> > In oodt_wm_plugin: invalid json response body at
> > https://registry.npmjs.org/@babel%2fpreset-env reason: Unexpected end of
> > JSON input
> > *what I have tried up to now:* clean npm cache, use --force and
> > --legacy-peer-deps arguments, update dependencies in package.json to the
> > latest.
> > *steps to reproduce:* Clone the repo, switch to the development branch,
> > move to react-components folder and try to install dependencies in each
> > plugin with *npm install*.
> >
> > It would be a great help if you can provide me with suggestions to
> > overcome these issues.
> >
> > Thanks and best regards
> > Pavindu
> >
> > On Mon, Mar 22, 2021 at 12:12 PM Imesha Sudasingha <
> > imesha.sudasin...@gmail.com> wrote:
> >
> >> Hi Pavindu,
> >>
> >> Thanks for your interest. In order to get started with OODT, you can
> refer
> >> to this [1] [2] article to get it up and running with Docker.
> >> First, you will have to get some overall understanding of OODT.
> Basically,
> >>
> >> 1. File manager - File ingestion and meta data extraction
> >> 2. Workflow manager - Schedule and run workflows
> >> 3. Crawler - Used to crawl directories and ingest files with file
> manager
> >> in bulk
> >> 4. Resource Manager - Execute, monitor and track jobs, resources as a
> >> whole
> >> 5. OPSUI - OPSUI is like the management dashboard which shows status and
> >> data of all those components.
> >>
> >> It's better if you have a look at the existing OPSUI (mentioned in
> almost
> >> all the docs) and then have a look at the React.js based novel UI.
> >> Let us know if you have any questions.
> >>
> >> [1] https://medium.com/faun/apache-oodt-with-docker-84d32525c798
> >> [2] https://cwiki.apache.org/confluence/display/OODT/Getting+Started
> >>
> >> Cheers,
> >> Imesha
> >&g

Re: GSoC 2021

[Imesha Sudasingha]

Hi Pavindu,

Thanks for your interest. In order to get started with OODT, you can refer
to this [1] [2] article to get it up and running with Docker.
First, you will have to get some overall understanding of OODT. Basically,

1. File manager - File ingestion and meta data extraction
2. Workflow manager - Schedule and run workflows
3. Crawler - Used to crawl directories and ingest files with file manager
in bulk
4. Resource Manager - Execute, monitor and track jobs, resources as a whole
5. OPSUI - OPSUI is like the management dashboard which shows status and
data of all those components.

It's better if you have a look at the existing OPSUI (mentioned in almost
all the docs) and then have a look at the React.js based novel UI.
Let us know if you have any questions.

[1] https://medium.com/faun/apache-oodt-with-docker-84d32525c798
[2] https://cwiki.apache.org/confluence/display/OODT/Getting+Started

Cheers,
Imesha

On Mon, 22 Mar 2021 at 07:22, Pavindu Lakshan 
wrote:

> Hello all,
>
> I'm Pavindu Lakshan, a final year undergraduate of the University of
> Moratuwa, who has working experience in Node.js and React.js. I would like
> to work on this issue, Improving OPSUI React.js UI with advanced
> functionalities , for
> GSoC
> 2021 since this involves the technologies that I'm most familiar with.
>
> For now, I have a very basic understanding of what OODT does, Also, I'm
> going through the medium articles that Imesha had posted on the issue and
> going to follow the official tutorial
> .
>
> Feedback and suggestions on my current learning path and future steps that
> I should follow are highly appreciated.
>
> Thank you
>
> Best regards
> Pavindu Lakshan
>

[jira] [Updated] (OODT-1035) Improve OPSUI React.js UI with advanced functionalities

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-1035:

Description: 
In GSoC 2019, we implemented a new OPSUI UI based on React.js. See the related 
blog posts [1] [2]. Several advanced features require to be implemented 
including.
 * Implement querying functionality at OPSUI side (scope can be determined)
 * Show progress of workflows and file ingestions
 * Introduce a proper REST API for resource manager component
 * Introduce proper packaging (with configurable external REST API URLs) and 
deployment mechanism (as a docker deployment or an npm package)

In this project, the student will have to work on the UI with React.js and will 
have to implement several REST APIs using JAX-RS. Furthermore, will have to 
work on making OPSUI easy to deploy.

The existing wicket based OPSUI will be replaced by the new React.js based 
OPSUI at the end of this project. And the linked blog posts will be a good 
start to understand what the new React.js based OPSUI is capable of doing.

[1] 
[https://medium.com/faun/gsoc-2019-apache-oodt-react-based-opsui-dashboard-d93a9083981c]
[2] 
[https://medium.com/faun/whats-new-in-apache-oodt-react-opsui-dashboard-4cc6701628a9]
[3] [https://medium.com/faun/apache-oodt-with-docker-84d32525c798]

  was:
In GSoC 2019, we implemented a new OPSUI UI based on React.js. See the related 
blog posts [1] [2]. Several advanced features require to be implemented 
including.

* Implement querying functionality at OPSUI side (scope can be determined)
* Show progress of workflows and file ingestions
* Introduce a proper REST API for resource manager component
* Introduce proper packaging (with configurable external REST API URLs) and 
deployment mechanism (as a docker deployment or an npm package)

In this project, the student will have to work on the UI with React.js and will 
have to implement several REST APIs using JAX-RS. Furthermore, will have to 
work on making OPSUI easy to deploy.

The existing wicket based OPSUI will be replaced by the new React.js based 
OPSUI at the end of this project. And the linked blog posts will be a good 
start to understand what the new React.js based OPSUI is capable of doing.

[1] 
[https://medium.com/faun/gsoc-2019-apache-oodt-react-based-opsui-dashboard-d93a9083981c]
[2] 
[https://medium.com/faun/whats-new-in-apache-oodt-react-opsui-dashboard-4cc6701628a9]


> Improve OPSUI React.js UI with advanced functionalities
> ---
>
> Key: OODT-1035
> URL: https://issues.apache.org/jira/browse/OODT-1035
> Project: OODT
>  Issue Type: Improvement
>  Components: file manager, opsui, resource manager
>    Reporter: Imesha Sudasingha
>Priority: Major
>  Labels: gsoc2021, mentor
>
> In GSoC 2019, we implemented a new OPSUI UI based on React.js. See the 
> related blog posts [1] [2]. Several advanced features require to be 
> implemented including.
>  * Implement querying functionality at OPSUI side (scope can be determined)
>  * Show progress of workflows and file ingestions
>  * Introduce a proper REST API for resource manager component
>  * Introduce proper packaging (with configurable external REST API URLs) and 
> deployment mechanism (as a docker deployment or an npm package)
> In this project, the student will have to work on the UI with React.js and 
> will have to implement several REST APIs using JAX-RS. Furthermore, will have 
> to work on making OPSUI easy to deploy.
> The existing wicket based OPSUI will be replaced by the new React.js based 
> OPSUI at the end of this project. And the linked blog posts will be a good 
> start to understand what the new React.js based OPSUI is capable of doing.
> [1] 
> [https://medium.com/faun/gsoc-2019-apache-oodt-react-based-opsui-dashboard-d93a9083981c]
> [2] 
> [https://medium.com/faun/whats-new-in-apache-oodt-react-opsui-dashboard-4cc6701628a9]
> [3] [https://medium.com/faun/apache-oodt-with-docker-84d32525c798]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-1035) Improve OPSUI React.js UI with advanced functionalities

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-1035:

Description: 
In GSoC 2019, we implemented a new OPSUI UI based on React.js. See the related 
blog posts [1] [2]. Several advanced features require to be implemented 
including.

* Implement querying functionality at OPSUI side (scope can be determined)
* Show progress of workflows and file ingestions
* Introduce a proper REST API for resource manager component
* Introduce proper packaging (with configurable external REST API URLs) and 
deployment mechanism (as a docker deployment or an npm package)

In this project, the student will have to work on the UI with React.js and will 
have to implement several REST APIs using JAX-RS. Furthermore, will have to 
work on making OPSUI easy to deploy.

The existing wicket based OPSUI will be replaced by the new React.js based 
OPSUI at the end of this project. And the linked blog posts will be a good 
start to understand what the new React.js based OPSUI is capable of doing.

[1] 
[https://medium.com/faun/gsoc-2019-apache-oodt-react-based-opsui-dashboard-d93a9083981c]
[2] 
[https://medium.com/faun/whats-new-in-apache-oodt-react-opsui-dashboard-4cc6701628a9]

  was:
In GSoC 2019, we implemented a new OPSUI UI based on React.js. See the related 
blog posts [1] [2]. Several advanced features require to be implemented 
including.

* Implement querying functionality at OPSUI side (scope can be determined)
* Show progress of workflows and file ingestions
* Introduce a proper REST API for resource manager component
* Introduce proper packaging (with configurable external REST API URLs) and 
deployment mechanism (as a docker deployment or an npm package)

In this project, the student will have to work on the UI with React.js and will 
have to implement several REST APIs using JAX-RS. Furthermore, will have to 
work on making OPSUI easy to deploy.

The existing wicket based OPSUI will be replaced by the new React.js based 
OPSUI at the end of this project. And the linked blog posts will be a good 
start to understand what the new React.js based OPSUI is capable of doing.



 
[1]https://medium.com/faun/gsoc-2019-apache-oodt-react-based-opsui-dashboard-d93a9083981c

[2]https://medium.com/faun/whats-new-in-apache-oodt-react-opsui-dashboard-4cc6701628a9


> Improve OPSUI React.js UI with advanced functionalities
> ---
>
> Key: OODT-1035
> URL: https://issues.apache.org/jira/browse/OODT-1035
> Project: OODT
>  Issue Type: Improvement
>  Components: file manager, opsui, resource manager
>    Reporter: Imesha Sudasingha
>Priority: Major
>  Labels: gsoc2021, mentor
>
> In GSoC 2019, we implemented a new OPSUI UI based on React.js. See the 
> related blog posts [1] [2]. Several advanced features require to be 
> implemented including.
> * Implement querying functionality at OPSUI side (scope can be determined)
> * Show progress of workflows and file ingestions
> * Introduce a proper REST API for resource manager component
> * Introduce proper packaging (with configurable external REST API URLs) and 
> deployment mechanism (as a docker deployment or an npm package)
> In this project, the student will have to work on the UI with React.js and 
> will have to implement several REST APIs using JAX-RS. Furthermore, will have 
> to work on making OPSUI easy to deploy.
> The existing wicket based OPSUI will be replaced by the new React.js based 
> OPSUI at the end of this project. And the linked blog posts will be a good 
> start to understand what the new React.js based OPSUI is capable of doing.
> [1] 
> [https://medium.com/faun/gsoc-2019-apache-oodt-react-based-opsui-dashboard-d93a9083981c]
> [2] 
> [https://medium.com/faun/whats-new-in-apache-oodt-react-opsui-dashboard-4cc6701628a9]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (OODT-1035) Improve OPSUI React.js UI with advanced functionalities

[Imesha Sudasingha (Jira)]

Imesha Sudasingha created OODT-1035:
---

 Summary: Improve OPSUI React.js UI with advanced functionalities
 Key: OODT-1035
 URL: https://issues.apache.org/jira/browse/OODT-1035
 Project: OODT
  Issue Type: Improvement
  Components: file manager, opsui, resource manager
Reporter: Imesha Sudasingha


In GSoC 2019, we implemented a new OPSUI UI based on React.js. See the related 
blog posts [1] [2]. Several advanced features require to be implemented 
including.

* Implement querying functionality at OPSUI side (scope can be determined)
* Show progress of workflows and file ingestions
* Introduce a proper REST API for resource manager component
* Introduce proper packaging (with configurable external REST API URLs) and 
deployment mechanism (as a docker deployment or an npm package)

In this project, the student will have to work on the UI with React.js and will 
have to implement several REST APIs using JAX-RS. Furthermore, will have to 
work on making OPSUI easy to deploy.

The existing wicket based OPSUI will be replaced by the new React.js based 
OPSUI at the end of this project. And the linked blog posts will be a good 
start to understand what the new React.js based OPSUI is capable of doing.



 
[1]https://medium.com/faun/gsoc-2019-apache-oodt-react-based-opsui-dashboard-d93a9083981c

[2]https://medium.com/faun/whats-new-in-apache-oodt-react-opsui-dashboard-4cc6701628a9



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [GSoC 2021] Status of OPSUI React UI

[Imesha Sudasingha]

Hi Nadeeshan,

Thanks for the input. Seems like we can put a project to finalize OPSUI
ReactJs based implementation.

Hi All,

Any other suggestions?

Thanks,
Imesha

On Sun, 14 Mar 2021 at 11:40, Gimhana Nadeeshan <
gimhanadesilva...@cse.mrt.ac.lk> wrote:

> Hi Imesha,
>
> *Update of the current OPSUI React UI Dashboard*
> File Manager Node JS React Component Capable of,
>
>- Ingesting a File with its corresponding Metadata File
>- Ingesting a File without giving its Metadata File. (capable of
>building the corresponding Metadata file according to a given product type
>and structure.
>- Listing the Ingested products.
>- Viewing an Ingested product (File Viewer).
>- Removing selected Ingested products.
>
> Workflow Manager Node JS React Component Capable of,
>
>- Listing running/finished/paused workflows.
>- Resuming/Stopping/Pausing workflows.
>
>
> Here are my thoughts on the identified remaining work.
>
>- Adding query support (like filters) and process progress ( like
>Indicating the current status of ingestions) in the UI for File Manager and
>Workflow Manager components.
>- As I believe there is no supported REST API s for Resources Manager
>at the moment, we can add REST APIs s for Resources Manager, use those in a
>reusable react component, and OPSUI integration.
>- Hosting the OPSUI React UI in a proper production server and publish
>Node modules in an open-source friendly, active package managing platform
>(like NPM).
>
> Those are my ideas regarding the remaining work and please correct me if I
> missed anything.
>
> Thanks and Best Regards,
> Gimhana
>
> On Fri, 12 Mar 2021 at 09:00, Imesha Sudasingha  wrote:
>
>> Hi Gimhana,
>>
>> As of where we finished, what's the status of OPSUI ReactJS UI? Can you
>> point out the remaining work required to be done?
>>
>> Since this time, the GSoC is around 2 months in length and the project
>> scopes are supposed to be reduced. Therefore, I'm planning to put a project
>> for GSoC 2021 [1] to get the remainder of the OPSUI done.
>>
>> Therefore, could you please let us know what remaining work we have to do?
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2021+Ideas+list
>>
>> Thanks,
>> Imesha
>>
>>
>
>
>
>
> * <http://www.linkedin.com/in/nadeeshangimhana/>*
>
>
> * <http://www.linkedin.com/in/nadeeshangimhana/>*
>
>
>

[GSoC 2021] Status of OPSUI React UI

[Imesha Sudasingha]

Hi Gimhana,

As of where we finished, what's the status of OPSUI ReactJS UI? Can you
point out the remaining work required to be done?

Since this time, the GSoC is around 2 months in length and the project
scopes are supposed to be reduced. Therefore, I'm planning to put a project
for GSoC 2021 [1] to get the remainder of the OPSUI done.

Therefore, could you please let us know what remaining work we have to do?

[1] https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2021+Ideas+list

Thanks,
Imesha

[REPORT] OODT - March 2021

[Imesha Sudasingha]

## Description:
Apache OODT is a software framework as well as an architectural style for
the
rapid construction of scientific data systems. It provides components for
data
capture, curation, metadata extraction, workflow management, resource
management, and data processing.

## Issues:
There are no issues requiring board attention.

## Membership Data:
Apache OODT was founded 2010-11-17 (10 years ago)
There are currently 46 committers and 45 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Imesha Sudasingha on 2017-08-28.
- No new committers. Last addition was Imesha Sudasingha on 2017-08-29.

## Project Activity:
We are currently working on JDK 11 support and removing XML RPC support.
There
have been very positive contributions during this quarter. Several PRs are
waiting to be reviewed for OODT 2.0 release. We are hopeful to get them
merged
in next quarter.

## Community Health:
Compared to last reporting period, project activity has been high due to
several contributors working on JDK 11 support, logging improvements for
OODT
and overall 2.0 release. We predict this trend will continue in the next
quarter as well.

Re: OODT 2.0 planning

[Imesha Sudasingha]

Seems like it was due to JDK 11. Got through using JDK 8.

On Wed, 6 Jan 2021 at 12:28, Imesha Sudasingha  wrote:

> Hi Gimhana,
>
> Thanks for the details. As per our offline conversation, did you manage to
> get the JDK 11 testing ongoing?
> Because I tried to build this on JDK 11 today and it failed with:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:javadoc
> (attach-javadocs) on project oodt-core: Execution attach-javadocs of goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:javadoc failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:javadoc:
> java.lang.ExceptionInInitializerError: null
> [ERROR] -
> [ERROR] realm =
> plugin>org.apache.maven.plugins:maven-javadoc-plugin:2.10.3
> [ERROR] strategy =
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/home/imesha/.m2/repository/org/apache/maven/plugins/maven-javadoc-plugin/2.10.3/maven-javadoc-plugin-2.10.3.jar
>
> Not sure if this was entirely due to JDK 11.
>
> Imesha
>
> On Tue, 17 Nov 2020 at 07:59, Gimhana Nadeeshan <
> gimhanadesilva...@cse.mrt.ac.lk> wrote:
>
>> Hi all,
>>
>> 2. About JDK 11 support, does anybody have any idea on how we can test
>> that
>> > or what issues do we have when running with JDK 11? I remember Lewis
>> trying
>> > to run OODT with JDK 10 sometime back [3] [4]
>> >
>>
>> As we discussed offline, here I'll put my suggestion regarding OpenJDK 11
>> migration.
>>
>> When migrating basically what we have to have to do is
>>
>>- Update all dependencies to the latest versions.
>>- Compile the project and resolve all issues related to unofficial
>>access, split packages and deprecated/removed Java EE modules.
>>
>> We use the official Oracle JDK 11 migration guide[1] as a head start.
>> However, we cannot guarantee that we will be able to update all the
>> dependencies without breaking stuff. Have to try and see!
>>
>> [1] https://docs.oracle.com/en/java/javase/11/migrate/migration-guide.pdf
>>
>> Thanks and Regards,
>> Gimhana
>>
>> On Thu, 12 Nov 2020 at 13:32, Imesha Sudasingha 
>> wrote:
>>
>> > Great! We have 2 action items then:
>> >
>> > 1. Making Avro RPC the default. We once did this for the 1.9 release and
>> > later reverted due to 1.x backward compatibility issues [1]. Therefore,
>> > this task can reuse some commits we had there (simply revert [2]).
>> >
>> > 2. About JDK 11 support, does anybody have any idea on how we can test
>> that
>> > or what issues do we have when running with JDK 11? I remember Lewis
>> trying
>> > to run OODT with JDK 10 sometime back [3] [4]
>> >
>> > [1] https://issues.apache.org/jira/browse/OODT-1031
>> > [2] https://github.com/apache/oodt/pull/116
>> > [3] https://github.com/apache/oodt/pull/71
>> > [4] https://issues.apache.org/jira/browse/OODT-990
>> >
>> >
>> > On Wed, 11 Nov 2020 at 22:20, Tom Barber  wrote:
>> >
>> > > I've officially marked all my email as read, so thats 3000 emails gone
>> > > forever... on the plus side, I should have some time now. I've got a
>> > couple
>> > > of projects I need to get off my plate so I shall setup my new laptop
>> > next
>> > > week and sort them out, then I'll get this code base stood back up and
>> > > figure out the best place to start.
>> > >
>> > > Tom
>> > >
>> > > On Wed, Nov 11, 2020 at 4:22 PM Chris Mattmann 
>> > > wrote:
>> > >
>> > > > +1 from me Imesha!
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > From: Imesha Sudasingha 
>> > > > Reply-To: 
>> > > > Date: Wednesday, November 11, 2020 at 7:49 AM
>> > > > To: dev 
>> > > > Subject: Re: OODT 2.0 planning
>> > > >
>> > > >
>> > > >
>> > > > Hi All,
>> > > >
>> > > >
>> > > >
>> > > > This is my suggestion, what if we include both Avro default support
>> and
>> > > JDK
>> > > >
>> > > > 11 support for OODT 2.0 as JDK 11 support seems to be critical as
&

Re: OODT 2.0 planning

[Imesha Sudasingha]

Hi Sean,

Regarding docker images, we haven't decided where to push them yet. Yasith
was the person who contributed to them for his GSoC.

Hi Yasith,

Your help is much appreciated and we will definitely need your help there.
Keep in touch with the mails in this list.

Thanks,
Imesha


On Tue, 3 Nov 2020 at 22:55, Jayawardana, Yasith  wrote:

> Hello all,
>
> I can make some time to help with the 2.3 release as well.
>
> Best Regards,
> Yasith
>
> > On Nov 3, 2020, at 10:23 AM, Sean Kelly  wrote:
> >
> > 
> >> 2.0 – first release where we remove all the Xml-RPC and we change
> nothing
> >> else. Avro is the default, and only
> >> comm option – though interface exists for anyone that wants to roll
> their
> >> own. We change nothing else*
> >
> > Sounds fine by me. XML-RPC was "fun while it lasted".
> >
> >>
> >> 2.1 – first release with newer JDK support (everyone is asking for this,
> >> and it screws up people like me with
> >> new Macs, or computers and newer JDKs by default). We also begin
> cleaning
> >> up dependencies and removing
> >> old ones, and pointing at new stuff.
> >
> > Oh my glob yes, yes, yes!
> >>
> >> 2.2 – OpsUi React with GSoC 2019 output.
> >
> > I can't comment on 2.2 since I've never used it.
> >>
> >> 2.3 – We integrate, test and demo the Docker builds. We also test and
> fully
> >> bake the ZK deployments and
> >> scaled up Docker.
> >
> > Are these the images owned by "oodthub" on hub.docker.com?
> >
> > Take care,
> > -SK
>

Re: OODT 2.0 planning

[Imesha Sudasingha]

Great. I had a discussion with Gimhana, who was the GSoC 2019 student and
contributed to developing the React based new OpsUI. He will also be able
to help us with this.

On Mon, 2 Nov 2020 at 07:06, Chris Mattmann  wrote:

> +1 from me
>
>
>
>
>
>
>
> From: Imesha Sudasingha 
> Reply-To: 
> Date: Thursday, October 29, 2020 at 6:56 PM
> To: dev 
> Subject: Re: OODT 2.0 planning
>
>
>
> Hi All,
>
>
>
> This is an old thread where we discussed the plan for next releases. In
>
> summary, following was the plan:
>
>
>
> 2.0 – first release where we remove all the Xml-RPC and we change nothing
>
> else. Avro is the default, and only
>
> comm option – though interface exists for anyone that wants to roll their
>
> own. We change nothing else*
>
>
>
> 2.1 – first release with newer JDK support (everyone is asking for this,
>
> and it screws up people like me with
>
> new Macs, or computers and newer JDKs by default). We also begin cleaning
>
> up dependencies and removing
>
> old ones, and pointing at new stuff.
>
>
>
> 2.2 – OpsUi React with GSoC 2019 output.
>
>
>
> 2.3 – We integrate, test and demo the Docker builds. We also test and fully
>
> bake the ZK deployments and
>
> scaled up Docker.
>
>
>
> Any changes/suggestions to the above plan?
>
> What if we release the OpsUI ahead of others?
>
>
>
> Thanks,
>
> Imesha
>
>
>
> On Sun, 6 Oct 2019 at 06:20, Tom Barber  wrote:
>
>
>
> Sounds good to me. Should also increase the release cadence as well.
>
>
>
>
>
> On 5 October 2019 at 09:06:35, Chris Mattmann (mattm...@apache.org) wrote:
>
>
>
> Here is my suggested Roadmap here:
>
>
>
>
>
>
>
> 2.0 – first release where we remove all the Xml-RPC and we change nothing
>
> else. Avro is the default, and only
>
> comm option – though interface exists for anyone that wants to roll their
>
> own. We change nothing else*
>
>
>
>
>
>
>
> 2.1 – first release with newer JDK support (everyone is asking for this,
>
> and it screws up people like me with
>
> new Macs, or computers and newer JDKs by default). We also begin cleaning
>
> up dependencies and removing
>
> old ones, and pointing at new stuff.
>
>
>
>
>
>
>
> 2.2 – OpsUi React with Breno’s stuff.
>
>
>
>
>
>
>
> 2.3 – We integrate, test and demo the Docker builds. We also test and fully
>
> bake the ZK deployments and
>
> scaled up Docker.
>
>
>
>
>
>
>
> 2.4+ … who knows
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: Tom Barber 
>
> Reply-To: 
>
> Date: Saturday, October 5, 2019 at 3:31 AM
>
> To: , Imesha Sudasingha 
>
> Subject: Re: OODT 2.0 planning
>
>
>
>
>
>
>
> On 5 October 2019 at 11:25:41, Imesha Sudasingha (ime...@apache.org)
>
> wrote:
>
>
>
>
>
>
>
> I think there was a plan to
>
>
>
> remove XML rpc support completely and use avro only in 2.0.
>
>
>
>
>
>
>
>
>
>
>
> That is true. XMLRPC needs to die.
>
>
>
>
>
>
>
> Not sure about Knative, but certainly a Kubernetes operator would be
>
>
>
> something interesting to look at if we could.
>
>
>
>
>
>
>
> --
>
>
>
>
>
>
>
>
>
>
>
> Spicule Limited is registered in England & Wales. Company Number:
>
>
>
> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
>
>
>
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> All engagements
>
>
>
> are subject to Spicule Terms and Conditions of Business. This email and its
>
>
>
> contents are intended solely for the individual to whom it is addressed and
>
>
>
> may contain information that is confidential, privileged or otherwise
>
>
>
> protected from disclosure, distributing or copying. Any views or opinions
>
>
>
> presented in this email are solely those of the author and do not
>
>
>
> necessarily represent those of Spicule Limited. The company accepts no
>
>
>
> liability for any damage caused by any virus transmitted by this email. If
>
>
>
> you have received this message in error, please notify us immediately by
>
>
>
> reply email before deleting it from your system. Service of legal notice
>
>
>
> cannot be effected on Spicule Limited by email.
>
>
>
> --
>
>
>
>
>
> S

Re: OODT 2.0 planning

[Imesha Sudasingha]

Hi All,

This is an old thread where we discussed the plan for next releases. In
summary, following was the plan:

2.0 – first release where we remove all the Xml-RPC and we change nothing
else. Avro is the default, and only
comm option – though interface exists for anyone that wants to roll their
own. We change nothing else*

2.1 – first release with newer JDK support (everyone is asking for this,
and it screws up people like me with
new Macs, or computers and newer JDKs by default). We also begin cleaning
up dependencies and removing
old ones, and pointing at new stuff.

2.2 – OpsUi React with GSoC 2019 output.

2.3 – We integrate, test and demo the Docker builds. We also test and fully
bake the ZK deployments and
scaled up Docker.

Any changes/suggestions to the above plan?
What if we release the OpsUI ahead of others?

Thanks,
Imesha

On Sun, 6 Oct 2019 at 06:20, Tom Barber  wrote:

> Sounds good to me. Should also increase the release cadence as well.
>
>
> On 5 October 2019 at 09:06:35, Chris Mattmann (mattm...@apache.org) wrote:
>
> Here is my suggested Roadmap here:
>
>
>
> 2.0 – first release where we remove all the Xml-RPC and we change nothing
> else. Avro is the default, and only
> comm option – though interface exists for anyone that wants to roll their
> own. We change nothing else*
>
>
>
> 2.1 – first release with newer JDK support (everyone is asking for this,
> and it screws up people like me with
> new Macs, or computers and newer JDKs by default). We also begin cleaning
> up dependencies and removing
> old ones, and pointing at new stuff.
>
>
>
> 2.2 – OpsUi React with Breno’s stuff.
>
>
>
> 2.3 – We integrate, test and demo the Docker builds. We also test and fully
> bake the ZK deployments and
> scaled up Docker.
>
>
>
> 2.4+ … who knows
>
>
>
>
>
>
>
> From: Tom Barber 
> Reply-To: 
> Date: Saturday, October 5, 2019 at 3:31 AM
> To: , Imesha Sudasingha 
> Subject: Re: OODT 2.0 planning
>
>
>
> On 5 October 2019 at 11:25:41, Imesha Sudasingha (ime...@apache.org)
> wrote:
>
>
>
> I think there was a plan to
>
> remove XML rpc support completely and use avro only in 2.0.
>
>
>
>
>
> That is true. XMLRPC needs to die.
>
>
>
> Not sure about Knative, but certainly a Kubernetes operator would be
>
> something interesting to look at if we could.
>
>
>
> --
>
>
>
>
>
> Spicule Limited is registered in England & Wales. Company Number:
>
> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
>
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
>
>
>
>
>
>
>
> All engagements
>
> are subject to Spicule Terms and Conditions of Business. This email and its
>
> contents are intended solely for the individual to whom it is addressed and
>
> may contain information that is confidential, privileged or otherwise
>
> protected from disclosure, distributing or copying. Any views or opinions
>
> presented in this email are solely those of the author and do not
>
> necessarily represent those of Spicule Limited. The company accepts no
>
> liability for any damage caused by any virus transmitted by this email. If
>
> you have received this message in error, please notify us immediately by
>
> reply email before deleting it from your system. Service of legal notice
>
> cannot be effected on Spicule Limited by email.
>
> --
>
>
> Spicule Limited is registered in England & Wales. Company Number:
> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
>
>
> All engagements
> are subject to Spicule Terms and Conditions of Business. This email and
> its
> contents are intended solely for the individual to whom it is addressed
> and
> may contain information that is confidential, privileged or otherwise
> protected from disclosure, distributing or copying. Any views or opinions
> presented in this email are solely those of the author and do not
> necessarily represent those of Spicule Limited. The company accepts no
> liability for any damage caused by any virus transmitted by this email. If
> you have received this message in error, please notify us immediately by
> reply email before deleting it from your system. Service of legal notice
> cannot be effected on Spicule Limited by email.
>

[REPORT] OODT - October 2020

[Imesha Sudasingha]

## Description:
Apache OODT is a software framework as well as an architectural style for
the
rapid construction of scientific data systems. It provides components for
data
capture, curation, metadata extraction, workflow management, resource
management, and data processing.

## Issues:
No issues persist that require board's attention

## Membership Data:
Apache OODT was founded 2010-11-17 (10 years ago)
There are currently 46 committers and 45 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Imesha Sudasingha on 2017-08-28.
- No new committers. Last addition was Imesha Sudasingha on 2017-08-29.

## Project Activity:
- Last release was in October 2019.

Project activity has been very low due to all the contributors being busy
and
no major features/bugs are in the backlog.

However, there's a plan to fully integrate the new OPSUI developed in the
GSoC 2019 into the next release. That will be a great step for OODT once
completed.

## Community Health:
Activity point of view, project health is not satisfactory. However, in a
roll
call initiated 2 terms back, 8 PMC members responded. I hope the health will
be better once we start working on OODT 2.0 as mentioned above.

[REPORT] OODT - April 2020

[Imesha Sudasingha]

## Description:
Apache OODT is a software framework as well as an architectural style for
the
rapid construction of scientific data systems. It provides components for
data capture, curation, metadata extraction, workflow management, resource
management, and data processing.

## Issues:
There are no issues requiring board attention

## Membership Data:
Apache OODT was founded 2010-11-17 (9 years ago) There are currently 46
committers and 45 PMC members in this project. The Committer-to-PMC ratio is
roughly 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Imesha Sudasingha on 2017-08-28.
- No new committers. Last addition was Imesha Sudasingha on 2017-08-29.

## Project Activity:
- Last release was 1.9 on 2019-10-03
- The features implemented through GSoC 2019 are yet to be finalized and
  released as OODT 2.0.
- Backward compatibility fix for OODT 1.9 was not released during this
  quarter due to lack of contributions to validate the changes.

## Community Health:
- The rise in number of emails is due to JIRA notifications and not due to
  contributions/discussions.
- Project activity was very low in this quarter since all the active
  contributors couldn't get involved enough.
- No project ideas were submitted for GSoC 2020

Re: [EXTERNAL] OODT 1.9.1 Release and DRAT

[Imesha Sudasingha]

That will be great. Thanks Chris!

CCing DRAT dev list.

On Sat, 8 Feb 2020 at 23:49, Chris Mattmann  wrote:

> Thanks Imesha, I’ll add it to my list of things to test ☺
>
> You ROCK would love to get a DRAT 1.0 out
>
>
>
>
>
>
>
> From: Imesha Sudasingha 
> Reply-To: "dev@oodt.apache.org" 
> Date: Saturday, February 8, 2020 at 10:18 AM
> To: dev 
> Subject: [EXTERNAL] OODT 1.9.1 Release and DRAT
>
>
>
> Hi All,
>
>
>
> When DRAT 1.0 RC which relied on OODT 1.9 was being tested, we encountered
>
> several issues [1]. I have fixed OODT related things under OODT-1031 and
>
> those fixes have now been committed. Now we need to release OODT 1.9.1 with
>
> those fixes.
>
>
>
> On DRAT side, I have sent a PR [2] containing updates required to be done
>
> to DRAT to be compatible with OODT 1.9.1 once released. If you can have a
>
> look at the PR and preferably test it locally, it will help expedite the
>
> release process.
>
>
>
> Thanks,
>
> Imesha
>
>
>
> [1] https://issues.apache.org/jira/projects/OODT/issues/OODT-1031
>
> [2] https://github.com/apache/drat/pull/204
>
>
>
>

OODT 1.9.1 Release and DRAT

[Imesha Sudasingha]

Hi All,

When DRAT 1.0 RC which relied on OODT 1.9 was being tested, we encountered
several issues [1]. I have fixed OODT related things under OODT-1031 and
those fixes have now been committed. Now we need to release OODT 1.9.1 with
those fixes.

On DRAT side, I have sent a PR [2] containing updates required to be done
to DRAT to be compatible with OODT 1.9.1 once released. If you can have a
look at the PR and preferably test it locally, it will help expedite the
release process.

Thanks,
Imesha

[1] https://issues.apache.org/jira/projects/OODT/issues/OODT-1031
[2] https://github.com/apache/drat/pull/204

[jira] [Updated] (OODT-1031) OODT 1.9 should default to XMLRpc versions of FM/RESMGR/WMGR instead of Avro versions

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-1031:

Fix Version/s: 1.9.1

> OODT 1.9 should default to XMLRpc versions of FM/RESMGR/WMGR instead of Avro 
> versions
> -
>
> Key: OODT-1031
> URL: https://issues.apache.org/jira/browse/OODT-1031
> Project: OODT
>  Issue Type: Task
>  Components: file manager, resource manager, workflow manager
>Affects Versions: 1.9
>    Reporter: Imesha Sudasingha
>Priority: Major
> Fix For: 1.9.1
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> We have made avro file manager, workflow manager and resource manager the 
> default in the new 1.9 release. Due to this change, if the XML Rpc versions 
> of those are not set explicitly, avro versions start causing incompatible 
> (ex: XML Rpc client with avro server) clients and servers to communicate.
> This should be changed to use XML Rpc versions as the default clients and 
> servers.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (OODT-1031) OODT 1.9 should default to XMLRpc versions of FM/RESMGR/WMGR instead of Avro versions

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha resolved OODT-1031.
-
Resolution: Fixed

> OODT 1.9 should default to XMLRpc versions of FM/RESMGR/WMGR instead of Avro 
> versions
> -
>
> Key: OODT-1031
> URL: https://issues.apache.org/jira/browse/OODT-1031
> Project: OODT
>  Issue Type: Task
>  Components: file manager, resource manager, workflow manager
>Affects Versions: 1.9
>    Reporter: Imesha Sudasingha
>Priority: Major
> Fix For: 1.9.1
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> We have made avro file manager, workflow manager and resource manager the 
> default in the new 1.9 release. Due to this change, if the XML Rpc versions 
> of those are not set explicitly, avro versions start causing incompatible 
> (ex: XML Rpc client with avro server) clients and servers to communicate.
> This should be changed to use XML Rpc versions as the default clients and 
> servers.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-995) ProductType is not serializable

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-995:
---
Fix Version/s: (was: 1.9)

> ProductType is not serializable 
> 
>
> Key: OODT-995
> URL: https://issues.apache.org/jira/browse/OODT-995
> Project: OODT
>  Issue Type: Bug
>  Components: file manager, opsui
>Affects Versions: 1.2.4
>Reporter: Lewis John McGibbney
>Priority: Major
> Fix For: 2.0
>
>
> In my COAL project, we are using the OPSUI Web Application for PCS. 
> When navigating to http://localhost:8080/opsui/types/, I regularly see stuff 
> like this
> {code}
> ERROR - Objects- Error serializing object class 
> org.apache.oodt.pcs.opsui.TypesPage [object=[Page class = 
> org.apache.oodt.pcs.opsui.TypesPage, id = 2, version = 0]]
> org.apache.wicket.util.io.SerializableChecker$WicketNotSerializableException: 
> Unable to serialize class: org.apache.oodt.cas.filemgr.structs.ProductType
> Field hierarchy is:
>   2 [class=org.apache.oodt.pcs.opsui.TypesPage, path=2]
> private java.lang.Object org.apache.wicket.MarkupContainer.children 
> [class=[Ljava.lang.Object;]
>   private org.apache.wicket.markup.html.link.PopupSettings 
> org.apache.wicket.markup.html.link.ExternalLink.popupSettings[8] 
> [class=org.apache.oodt.cas.webcomponents.filemgr.browser.types.Types, 
> path=2:types_component]
> private java.lang.Object org.apache.wicket.MarkupContainer.children 
> [class=org.apache.oodt.cas.webcomponents.filemgr.browser.types.Types$2, 
> path=2:types_component:cas_fm_browser_ptype_table_rows]
>   java.lang.Object org.apache.wicket.Component.data 
> [class=org.apache.wicket.model.util.WildcardListModel]
> private java.lang.Object 
> org.apache.wicket.model.util.GenericBaseModel.object [class=java.util.Vector]
>   private java.lang.Object 
> org.apache.wicket.model.util.GenericBaseModel.object[write:1] 
> [class=[Ljava.lang.Object;]
> private java.lang.Object 
> org.apache.wicket.model.util.GenericBaseModel.object[write:1][0] 
> [class=org.apache.oodt.cas.webcomponents.filemgr.browser.types.Types$TypeCountTuple]
>   private java.util.List 
> org.apache.oodt.cas.webcomponents.filemgr.browser.types.Types$TypeCountTuple.types
>  [class=java.util.Vector]
> private java.util.List 
> org.apache.oodt.cas.webcomponents.filemgr.browser.types.Types$TypeCountTuple.types[write:1]
>  [class=[Ljava.lang.Object;]
>   private java.util.List 
> org.apache.oodt.cas.webcomponents.filemgr.browser.types.Types$TypeCountTuple.types[write:1][0]
>  [class=org.apache.oodt.cas.filemgr.structs.ProductType] <- field that is 
> not serializable
>   at 
> org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:386)
>   at 
> org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:365)
>   at 
> org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:432)
>   at 
> org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:365)
>   at 
> org.apache.wicket.util.io.SerializableChecker.access$500(SerializableChecker.java:64)
>   at 
> org.apache.wicket.util.io.SerializableChecker$1InterceptingObjectOutputStream.replaceObject(SerializableChecker.java:535)
>   at 
> java.base/java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1145)
>   at 
> java.base/java.io.ObjectOutputStream.access$300(ObjectOutputStream.java:163)
>   at 
> java.base/java.io.ObjectOutputStream$PutFieldImpl.writeFields(ObjectOutputStream.java:1713)
>   at 
> java.base/java.io.ObjectOutputStream.writeFields(ObjectOutputStream.java:483)
>   at java.base/java.util.Vector.writeObject(Vector.java:1217)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.base/java.lang.reflect.Method.invoke(Method.java:564)
>   at 
> java.base/java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:1130)
>   at 
> java.base/java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1497)
>   at 
> java.base/java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav

[jira] [Updated] (OODT-1000) commons-pool and commons-dbcp need to be upgraded to commons-pool2 and commons-dbcp2 respectively

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-1000:

Fix Version/s: (was: 1.9)

> commons-pool and commons-dbcp need to be upgraded to commons-pool2 and 
> commons-dbcp2 respectively
> -
>
> Key: OODT-1000
> URL: https://issues.apache.org/jira/browse/OODT-1000
> Project: OODT
>  Issue Type: Task
>  Components: commons, core, file manager, resource manager, workflow 
> manager
>Affects Versions: 1.2.4
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 2.0
>
>
> In particular, when trying to launch a RADiX under JDK11, I run into an issue 
> with xerces:xercesImpl:2.0.2 which is inherited from commons:commons-dbcp 
> dependency.
> Every other instance of xercesImpl is pegged at 2.9.1 and hence we get a 
> ClassNotFoundException when attempting to launch, in particular, the workflow 
> and resource manager services. 
> The fix here is to upgrade to commons-pool2 and commons-dbcp2 respectively.
> I'll try and work a fix.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-484) Enhance Workflow Lifecycle to include state change logic

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-484:
---
Fix Version/s: (was: 1.9)

> Enhance Workflow Lifecycle to include state change logic
> 
>
> Key: OODT-484
> URL: https://issues.apache.org/jira/browse/OODT-484
> Project: OODT
>  Issue Type: Sub-task
>  Components: workflow manager
>Affects Versions: 0.4
> Environment: none
>Reporter: Brian Foster
>Assignee: Brian Foster
>Priority: Minor
> Fix For: 2.0
>
>
> Let's split up the lifecycle XML file into several files (kind have it look 
> like filemgr element and product-type XML files):
>   1) Define States XML file
>   2) Define Stages XML file
>   3) Mapping of States to Stages XML file
>   4) Mapping of States to next valid States
> I then propose we add a Priority to each Stage (its purpose will become 
> apparent)... Then we create a new Interface: StatePreCondition... These 
> preconditions would then be attached to a State... Then when the Workflow 
> Processor detects a sub-processor State change it would poll each next valid 
> State (determined by mapping in purposed XML file #4) for their PreConditions 
> and if any of the State's PreConditions pass then that State would become the 
> next State of that Workflow Processor (if multiple States pass as next State, 
> then the priority attached to the Stage each State belongs to is used to 
> determine which State becomes next State)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-983) Update Resource Manager to use SLF4J logging

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-983:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Update Resource Manager to use SLF4J logging
> 
>
> Key: OODT-983
> URL: https://issues.apache.org/jira/browse/OODT-983
> Project: OODT
>  Issue Type: Sub-task
>  Components: resource manager
>    Reporter: Imesha Sudasingha
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-956) Add connection checks to components

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-956:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Add connection checks to components
> ---
>
> Key: OODT-956
> URL: https://issues.apache.org/jira/browse/OODT-956
> Project: OODT
>  Issue Type: Bug
>Affects Versions: 1.1
>Reporter: Tom Barber
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-971) Default filemgr.properties is buggy in radix post AvroRPC

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-971:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Default filemgr.properties is buggy in radix post AvroRPC
> -
>
> Key: OODT-971
> URL: https://issues.apache.org/jira/browse/OODT-971
> Project: OODT
>  Issue Type: Bug
>  Components: file manager, radix
>Affects Versions: 1.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Major
>
> When a user creates and builds a new Radix distribution, the 
> filemgr.properties references such as 
> {code}
> # xml rpc client configuration
> org.apache.oodt.cas.filemgr.system.xmlrpc.connectionTimeout.minutes=20
> org.apache.oodt.cas.filemgr.system.xmlrpc.requestTimeout.minutes=60
> #org.apache.oodt.cas.filemgr.system.xmlrpc.connection.retries=0
> #org.apache.oodt.cas.filemgr.system.xmlrpc.connection.retry.interval.seconds=3
> {code}
> Although these are _fine_ e.g. they still work, the package naming is now off 
> as there is no package actually named 
> {code}
> org.apache.oodt.cas.filemgr.system.xmlrpc...
> {code}
> The only issue I have with changing this important configuration setting, is 
> that is would essentially be backwards non-compatible with EVERY OODT install 
> unless your new install was powered by Radix.
> Any comments as to what to do? I am happy to close this as *wont fix* due to 
> the backwards non-compatible nature of a proposed fix which would _correct_ 
> the package naming but I just wanted to post for consideration here folks. I 
> will open a new issue regarding adding AvroRPC filemgr configuration in a 
> separate issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-915) Forbidden APIs for Common Utilities

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-915:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Forbidden APIs for Common Utilities
> ---
>
> Key: OODT-915
> URL: https://issues.apache.org/jira/browse/OODT-915
> Project: OODT
>  Issue Type: Sub-task
>Affects Versions: 0.10
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Major
>
> {code}
> [INFO] --- forbiddenapis:2.0:check (default) @ oodt-commons ---
> [INFO] Scanning for classes to check...
> [INFO] Reading bundled API signatures: jdk-unsafe-1.7
> [INFO] Reading bundled API signatures: jdk-deprecated-1.7
> [INFO] Reading bundled API signatures: jdk-system-out
> [INFO] Loading classes to check...
> [INFO] Scanning classes for violations...
> [ERROR] Forbidden field access: java.lang.System#err [prints to System.err; 
> should only be used for debugging, not in production code]
> [ERROR]   in org.apache.oodt.commons.util.Utility (Utility.java:67)
> [ERROR] Forbidden field access: java.lang.System#err [prints to System.err; 
> should only be used for debugging, not in production code]
> [ERROR]   in org.apache.oodt.commons.util.Utility (Utility.java:146)
> [ERROR] Forbidden method invocation: 
> java.io.InputStreamReader#(java.io.InputStream) [Uses default charset]
> [ERROR]   in org.apache.oodt.commons.exec.ExecHelper (ExecHelper.java:346)
> [ERROR] Forbidden method invocation: 
> java.io.InputStreamReader#(java.io.InputStream) [Uses default charset]
> [ERROR]   in org.apache.oodt.commons.exec.ExecHelper (ExecHelper.java:347)
> [ERROR] Forbidden field access: java.lang.System#err [prints to System.err; 
> should only be used for debugging, not in production code]
> [ERROR]   in org.apache.oodt.commons.database.SqlScript (SqlScript.java:92)
> [ERROR] Forbidden class/interface use: java.io.FileReader [Uses default 
> charset]
> [ERROR]   in org.apache.oodt.commons.database.SqlScript (SqlScript.java:112)
> [ERROR] Forbidden field access: java.lang.System#out [prints to System.out; 
> should only be used for debugging, not in production code]
> [ERROR]   in org.apache.oodt.commons.database.SqlScript (SqlScript.java:190)
> [ERROR] Forbidden field access: java.lang.System#out [prints to System.out; 
> should only be used for debugging, not in production code]
> [ERROR]   in org.apache.oodt.commons.database.SqlScript (SqlScript.java:231)
> [ERROR] Forbidden method invocation: 
> java.util.Calendar#getInstance(java.util.TimeZone) [Uses default locale or 
> time zone]
> [ERROR]   in org.apache.oodt.commons.date.DateUtils (DateUtils.java:112)
> [ERROR] Forbidden method invocation: 
> java.util.Calendar#getInstance(java.util.TimeZone) [Uses default locale or 
> time zone]
> [ERROR]   in org.apache.oodt.commons.date.DateUtils (DateUtils.java:118)
> [ERROR] Forbidden method invocation: java.util.Calendar#getInstance() [Uses 
> default locale or time zone]
> [ERROR]   in org.apache.oodt.commons.date.DateUtils (DateUtils.java:131)
> [ERROR] Forbidden method invocation: 
> java.util.Calendar#getInstance(java.util.TimeZone) [Uses default locale or 
> time zone]
> [ERROR]   in org.apache.oodt.commons.date.DateUtils (DateUtils.java:141)
> [ERROR] Forbidden method invocation: java.util.Calendar#getInstance() [Uses 
> default locale or time zone]
> [ERROR]   in org.apache.oodt.commons.date.DateUtils (DateUtils.java:152)
> [ERROR] Forbidden method invocation: 
> java.text.SimpleDateFormat#(java.lang.String) [Uses default locale]
> [ERROR]   in org.apache.oodt.commons.date.DateUtils (DateUtils.java:160)
> [ERROR] Forbidden method invocation: java.util.Calendar#getInstance() [Uses 
> default locale or time zone]
> [ERROR]   in org.apache.oodt.commons.date.DateUtils (DateUtils.java:176)
> [ERROR] Forbidden method invocation: 
> java.text.SimpleDateFormat#(java.lang.String) [Uses default locale]
> [ERROR]   in org.apache.oodt.commons.date.DateUtils (DateUtils.java:177)
> [ERROR] Forbidden method invocation: java.util.Calendar#getInstance() [Uses 
> default locale or time zone]
> [ERROR]   in org.apache.oodt.commons.date.DateUtils (DateUtils.java:183)
> [ERROR] Forbidden method invocation: 
> java.text.DecimalFormat#(java.lang.String) [Uses default locale]
> [ERROR]   in org.apache.oodt.commons.date.DateUtils (DateUtils.java:209)
> [ERROR] Forbidden field access: java.lang.System#out [prints to System.out; 
> should only be used for debugging, not in production code]
> [ERROR]   in org.apache.oodt.commons.date.DateUtils (Dat

[jira] [Updated] (OODT-976) Upgrade Apache Tika to 1.19.1

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-976:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Upgrade Apache Tika to 1.19.1
> -
>
> Key: OODT-976
> URL: https://issues.apache.org/jira/browse/OODT-976
> Project: OODT
>  Issue Type: Improvement
>  Components: core, file manager, radix
>Affects Versions: 1.2.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Major
>
> tika-core and tika-parsers 1.13 dependencies are pretty outdated now. A 
> release is pending for Tika 1.19.1. We should upgrade when it is available. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-910) Create Skinny Dependencies for WARs

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-910:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Create Skinny Dependencies for WARs
> ---
>
> Key: OODT-910
> URL: https://issues.apache.org/jira/browse/OODT-910
> Project: OODT
>  Issue Type: Improvement
>  Components: opsui
>Reporter: Tom Barber
>Priority: Major
>
> Currently the OPSUI war files are huge because the drag in all of the OODT 
> component transient dependencies which to the best of my knowledge are 
> generally not required as the UI just sends commands to remote services.
> To combat this we should create some skinny components that dont' include all 
> the transient dependencies.
> The "easy" but not very maintainable way would probably be to "exclude" a big 
> list of transient dependencies in the pom files for the components you want 
> to slim down.
> An alternative approach which I would favour, would be to create an API 
> module, similar to OSGI design practices, that contain the various API 
> interfaces for the component, say the filemanager. Then OPSUI can implement 
> its required interfaces separately from the filemanager, which can also 
> implement the interfaces if required on its side.
> I'm sure there are alternatives, just dictating my thoughts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-914) Parent issue for implementing forbidden apis plugin

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-914:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Parent issue for implementing forbidden apis plugin
> ---
>
> Key: OODT-914
> URL: https://issues.apache.org/jira/browse/OODT-914
> Project: OODT
>  Issue Type: Improvement
>  Components: commons, crawler, file manager, resource manager, 
> workflow manager
>Affects Versions: 0.10
>Reporter: Lewis John McGibbney
>Priority: Major
>
> The [Forbidden API's|https://github.com/policeman-tools/forbidden-apis] 
> plugin is very useful for findimg invocations of method/class/field 
> signatures and failing builds based on violations of some safe guards.
> I think the best way to go at this is probably module-by-module as there are 
> a ton of errors. 
> This is a parent issue for managing codebase compliance.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-863) Tidy up dependencies

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-863:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Tidy up dependencies
> 
>
> Key: OODT-863
> URL: https://issues.apache.org/jira/browse/OODT-863
> Project: OODT
>  Issue Type: Sub-task
>Reporter: Tom Barber
>Priority: Major
>
> This is something me and Michael Starch debated at apachecon and I've been 
> wanting to do for a long time.
> Most multi module projects I work with have their dependency versions set at 
> the top level that way its easy to change the dependency version for the 
> project and keep everything in sync across the whole build rather than (as in 
> one case I found) have 4 different versions of the same dependency.
> I've moved them all to the core pom and ordered them alphabetically, if no 
> one is too unhappy with this I'll finish off the reordering in the other poms 
> and we can continue as usual. I've tried a local build nothing fails(although 
> who knows once it hits jenkins), and if there really is a need to override a 
> specific dependency version on a per module basis this can still be done.
> Personally I think its a useful tidy up and of benefit to the developers new 
> and old.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-868) Integrate Avro RPC with the pcs module

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-868:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Integrate Avro RPC with the pcs module
> --
>
> Key: OODT-868
> URL: https://issues.apache.org/jira/browse/OODT-868
> Project: OODT
>  Issue Type: Sub-task
>  Components: pcs
>Reporter: Radu Manole
>Assignee: Chris A. Mattmann
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-873) Update the scripts in RADIX to accomodate AvroRPC.

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-873:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Update the scripts in RADIX to accomodate AvroRPC.
> --
>
> Key: OODT-873
> URL: https://issues.apache.org/jira/browse/OODT-873
> Project: OODT
>  Issue Type: Sub-task
>  Components: avro rpc, radix
>Reporter: Lewis John McGibbney
>Priority: Major
>
> As per https://reviews.apache.org/r/36953/#comment151338 it is extremely 
> important that we update RADIX to accommodate the AvroRPC work. This can be 
> managed here as a separate issue. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-841) create restful impl of ops ui

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-841:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> create restful impl of ops ui
> -
>
> Key: OODT-841
> URL: https://issues.apache.org/jira/browse/OODT-841
> Project: OODT
>  Issue Type: Bug
>  Components: opsui
>Reporter: Tom Barber
>Assignee: Tom Barber
>Priority: Major
>
> create new ops ui rest interface so people can add 3rd party ui's easily to 
> the ops ui platform



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-692) Use lsof to stop Workflow/Resource Manager task/job PIDs

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-692:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Use lsof to stop Workflow/Resource Manager task/job PIDs 
> -
>
> Key: OODT-692
> URL: https://issues.apache.org/jira/browse/OODT-692
> Project: OODT
>  Issue Type: Bug
>  Components: pge wrapper framework, resource manager, workflow manager
>Reporter: Chris A. Mattmann
>Assignee: Chris A. Mattmann
>Priority: Major
>  Labels: killjob, manager, oodt, pid, resource, unix, workflow
>
> We can exploit a combination of LSOF, JobDir, and WorkflowInstanceId to 
> actually kill the process ID and fully stop a job kicked off by the resource 
> manager and workflow manager. I've been testing this process by hand on the 
> ASO process and it's totally useable by hand in practice, so we should 
> automate it. For example:
> {noformat}
> [snowdeploy@trango-private bin]$ lsof -p 37558
> COMMAND   PID   USER   FD   TYPE   DEVICE SIZE/OFF  NODE NAME
> idl 37558 snowdeploy  cwdDIR253,2 4096 488284165 
> /data/jobs/CASI/ISSP/20140511f1_184151_1399903013836
> ..
> {noformat}
> Reveals to use that the process ID 37558 (one of the IDL jobs running in ASO 
> for the ORTHO process) corresponds to _JobDir_ 
> {noformat}
> /data/jobs/CASI/ISSP/20140511f1_184151_1399903013836
> {noformat}
> We can also find out from WorklowInstanceMetadata that the _JobDir_ 
> corresponding to the line _184151_ is _726af17c-c131-4682-845e-4ef6b4a7_.
> So, from a Workflow Instance Id, we need:
> # the resolved JobDir by CAS-PGE. If it's not a CAS-PGE job, we need the 
> WorkflowTask to specify a JobDir, or else this functionality will simply 
> print out a message saying Kill without JobDir not supported.
> # a map for processes to interrogate with lsof e.g., PCS_JobKillProcessName
> # the use of lsof to interrogate the PID table, find the job corresponding 
> JobDir, and then kill. If PCS_JobKillProcessName is not specified, then 
> interrogate all jobs to determine the job to kill.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-658) Implement Apache Gora as suitable storage abstraction for Filemgr

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-658:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Implement Apache Gora as suitable storage abstraction for Filemgr 
> --
>
> Key: OODT-658
> URL: https://issues.apache.org/jira/browse/OODT-658
> Project: OODT
>  Issue Type: Improvement
>  Components: file manager
>Reporter: Lewis John McGibbney
>Priority: Major
>  Labels: gsoc2015, gsoc2017
> Attachments: OODT-658.patch
>
>
> As a framework, Apache Gora [0] provides an in-memory data model and 
> persistence for big data. It is my goal to build it in to the filemgr 
> component of OODT in the very near future. I will begin work on this now.
> Some history on the mailing lists can be found here
> [0] http://gora.apache.org
> [1] http://www.mail-archive.com/dev@oodt.apache.org/msg02500.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-833) Cyclic Dependency

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-833:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Cyclic Dependency
> -
>
> Key: OODT-833
> URL: https://issues.apache.org/jira/browse/OODT-833
> Project: OODT
>  Issue Type: Bug
>  Components: radix
>Reporter: Michael Starch
>Assignee: Michael Starch
>Priority: Major
> Attachments: evil-cycle.png, fixed.png
>
>
> Currently in the radix poms, there are a cyclic dependencies. This causes ALL 
> dependent libraries for all of radix to be pulled into each component.  This 
> is incorrect behavior for components that are supposed to be independent.
> Currently the cyclic dependency shows itself in the following way:
>  FileManager --> Extensions -->PCS Core --> FileManager, Workflow, Resource 
> 
> As can be seen, there is a cyclic dependency.
> It is recommended that the top level projects in radix for FileManager, 
> WorkflowManager, ResourceManager, etc should be broken down into two 
> projects: deployment and core.
> In this way, extensions can depend on core projects, and deployment can 
> depend on both extensions, and core.  Therefore, the cycle has disappeared.
> At this point, in-order to prevent pulling in dependencies from the 
> non-component cores, define the dependencies inside Extensions to "provided".



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-834) Improve Dependency Consistency

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-834:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Improve Dependency Consistency
> --
>
> Key: OODT-834
> URL: https://issues.apache.org/jira/browse/OODT-834
> Project: OODT
>  Issue Type: Bug
>  Components: build proces
>Reporter: Michael Starch
>Assignee: Tom Barber
>Priority: Major
>
> We have dependency version defined all over the system.  These dependencies 
> should be moved up to the top-level pom, and provided via variables to the 
> children poms so the same version of the dependencies are used across the 
> system



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-808) Replace OODT's XMLPRC with Avro's RPC

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-808:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Replace OODT's XMLPRC with Avro's RPC
> -
>
> Key: OODT-808
> URL: https://issues.apache.org/jira/browse/OODT-808
> Project: OODT
>  Issue Type: Epic
>  Components: xmlps
>Reporter: Lewis John McGibbney
>Assignee: Chris A. Mattmann
>Priority: Major
>  Labels: gsoc2015
> Attachments: OODT Avro RPC Project Proposal.docx, OODT Project 
> Proposal.pdf
>
>
> OODT relies on a legacy [Remote Procedure 
> Call|http://en.wikipedia.org/wiki/Remote_procedure_call] implementation, 
> namely [Apache XML-RPC|https://ws.apache.org/xmlrpc/]. Our version of this 
> library currently sits at 2.0.1, which was released on 28th December 2005.
> This issue proposes to replace the convoluted XML-RPC logic with [Apache 
> Avro's|http://avro.apache.org] [RPC 
> Protocol|http://avro.apache.org/docs/1.7.7/spec.html#Protocol+Declaration] 
> implementation.
> Right now xmlrpc implementation logic exists in the following OODT modules:
>  * catalog
>  * commons
>  * crawler
>  * filemgr
>  * mvn
>  * pcs
>  * protocol/api
>  * pushpull
>  * resource
>  * workflow



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-697) SolrCatalog needs a validation layer implemented

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-697:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> SolrCatalog needs a validation layer implemented
> 
>
> Key: OODT-697
> URL: https://issues.apache.org/jira/browse/OODT-697
> Project: OODT
>  Issue Type: Improvement
>  Components: file manager
>Affects Versions: 0.6
>Reporter: Thomas Bennett
>Assignee: Christopher
>Priority: Major
>  Labels: features
>
> SorlCatalog needs to have the ValidationLayer implemented.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-518) Get ResourceRunner working, submitting jobs, and updating state

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-518:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Get ResourceRunner working, submitting jobs, and updating state
> ---
>
> Key: OODT-518
> URL: https://issues.apache.org/jira/browse/OODT-518
> Project: OODT
>  Issue Type: Sub-task
>  Components: workflow manager
>Reporter: Chris A. Mattmann
>Assignee: Chris A. Mattmann
>Priority: Major
>
> We need to wrap up the ResourceRunner, unit test it, get it running and 
> updating state, and submitting jobs to the resource manager as part of the 
> Wengine finish line tasks.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-504) Support Parallel Processors in Model Repo

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-504:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Support Parallel Processors in Model Repo
> -
>
> Key: OODT-504
> URL: https://issues.apache.org/jira/browse/OODT-504
> Project: OODT
>  Issue Type: Sub-task
>  Components: workflow manager
>Reporter: Chris A. Mattmann
>Assignee: Chris A. Mattmann
>Priority: Major
>  Labels: expert, workflow, workflow2
>
> # Define a new property, 
> *org.apache.oodt.cas.workflow.wengine.packagedRepo.parallelProcessors*. If 
> set to true, then the PackagedWorkflowRepository will neglect to compile 
> additional event/workflow instance logic to deal with parallelism, and will
> leave it to the underlying engine to leverage its Graph to determine how to 
> run Parallel Processors
> # Test this property with both the ThreadPoolWorkflowEngine and the 
> PrioritizedQueueBasedWorkflowEngine



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-517) Create and expose getWorkflowInstanceByCategory

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-517:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Create and expose getWorkflowInstanceByCategory 
> 
>
> Key: OODT-517
> URL: https://issues.apache.org/jira/browse/OODT-517
> Project: OODT
>  Issue Type: Sub-task
>  Components: workflow manager
>Reporter: Chris A. Mattmann
>Assignee: Chris A. Mattmann
>Priority: Major
>
> Need to expose a method to allow the WorkflowInstanceRepository to return 
> back workflow instances that have (or that do not have) a particular category 
> or set of categories. This will be used by the TaskQuerier to only retrieve 
> back workflow instances which are not in the "done" category.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-519) Fix calculation and computation of Wall Clock Time for Task and Workflow Level, and Current Task

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-519:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Fix calculation and computation of Wall Clock Time for Task and Workflow 
> Level, and Current Task
> 
>
> Key: OODT-519
> URL: https://issues.apache.org/jira/browse/OODT-519
> Project: OODT
>  Issue Type: Sub-task
>  Components: workflow manager
>Reporter: Chris A. Mattmann
>Assignee: Chris A. Mattmann
>Priority: Major
>
> Currently there is a bug in the computation of wall clock time for tasks and 
> workflows, and the current task isn't being calculated correctly. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-940) Upgrade Solr to Solr6 for lots of fun new stuff

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-940:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Upgrade Solr to Solr6 for lots of fun new stuff
> ---
>
> Key: OODT-940
> URL: https://issues.apache.org/jira/browse/OODT-940
> Project: OODT
>  Issue Type: Improvement
>Reporter: Tom Barber
>Assignee: Tom Barber
>Priority: Major
>
> We ship with Solr4 by default in the solr maven profile this should be 6 
> these days as 4 is from the ice age.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-936) Update SLF4J

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-936:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Update SLF4J
> 
>
> Key: OODT-936
> URL: https://issues.apache.org/jira/browse/OODT-936
> Project: OODT
>  Issue Type: Improvement
>Reporter: Tom Barber
>Assignee: Tom Barber
>Priority: Major
>
> The old SLF4J Api is ancient and not compatible with newer libraries



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-491) Finish line tasks for Wengine integration

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-491:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Finish line tasks for Wengine integration
> -
>
> Key: OODT-491
> URL: https://issues.apache.org/jira/browse/OODT-491
> Project: OODT
>  Issue Type: Umbrella
>  Components: workflow manager
>Reporter: Chris A. Mattmann
>Assignee: Chris A. Mattmann
>Priority: Major
> Attachments: NewWorkflowModel.patch.txt
>
>
> The final tasks to wrap up wengine integration into trunk.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-434) Finish config pages in PCS Operator Interface

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-434:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Finish config pages in PCS Operator Interface
> -
>
> Key: OODT-434
> URL: https://issues.apache.org/jira/browse/OODT-434
> Project: OODT
>  Issue Type: Improvement
>  Components: pcs
>Reporter: Chris A. Mattmann
>Assignee: Chris A. Mattmann
>Priority: Major
>  Labels: config, interface, operator, pages, pcs
>
> After OODT-157, we now have a configurable, functioning PCS Operator 
> Interface. I didn't get to finish the config pages part for 0.4 though. So 
> I'll track those updates here.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-503) Support ParentChildWorkflows and Graph structure in XMLWorkflowRepository

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-503:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Support ParentChildWorkflows and Graph structure in XMLWorkflowRepository
> -
>
> Key: OODT-503
> URL: https://issues.apache.org/jira/browse/OODT-503
> Project: OODT
>  Issue Type: Sub-task
>  Components: workflow manager
>Reporter: Chris A. Mattmann
>Assignee: Chris A. Mattmann
>Priority: Major
>  Labels: wengine, workflow2
>
> Make XMLWorkflowRepository generate ParentChildWorkflows and Graphs, so that 
> WorkflowProcessorQueue can unravel this information and convert into Workflow 
> Processors independent of underlying model repo.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-499) Document PackagedWorkflowRepository

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-499:
---
Fix Version/s: (was: 2.0)
   (was: 1.9)

> Document PackagedWorkflowRepository
> ---
>
> Key: OODT-499
> URL: https://issues.apache.org/jira/browse/OODT-499
> Project: OODT
>  Issue Type: Sub-task
>  Components: workflow manager
>Reporter: Chris A. Mattmann
>Assignee: Chris A. Mattmann
>Priority: Major
>
> The PackagedWorkflowRepository needs documentation, a wiki page, and 
> architectural diagram will do nicely. This is critical because the repo is a 
> major part of Workflow Engine, including the Graph structure and blurs the 
> line between PackagedWorkflowRepository and the whole WorkflowProcessor 
> infrastructure to support PrioritizedQueueBasedWorkflowEngine.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-990) Enable OODT to build under JDK 10.X

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-990:
---
Fix Version/s: (was: 1.9)

> Enable OODT to build under JDK 10.X
> ---
>
> Key: OODT-990
> URL: https://issues.apache.org/jira/browse/OODT-990
> Project: OODT
>  Issue Type: Improvement
>  Components: build proces
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Critical
> Fix For: 2.0
>
>
> When reviewing the 1.2.4 RC, I decided to build under JDK 10.X. This issue 
> will document and contain a fix for any deprecation and code improvements 
> required to build and test master branch under JDK 10.X.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-949) Various issues with RADiX

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-949:
---
Fix Version/s: (was: 1.9)

> Various issues with RADiX
> -
>
> Key: OODT-949
> URL: https://issues.apache.org/jira/browse/OODT-949
> Project: OODT
>  Issue Type: Bug
>  Components: radix
>Affects Versions: 1.0
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Critical
> Fix For: 2.0
>
>
> I recently started a new OODT RADiX deployment and I noticed several issues 
> whilst building the data system. I will augment on them here and submit a 
> patch to fix them.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-966) agility broken syntax under Python 3.X

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-966:
---
Fix Version/s: (was: 1.9)

> agility broken syntax under Python 3.X
> --
>
> Key: OODT-966
> URL: https://issues.apache.org/jira/browse/OODT-966
> Project: OODT
>  Issue Type: Bug
>  Components: agility
>Affects Versions: 1.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Critical
> Fix For: 2.0
>
>
> Using OODT master branch, python setup.py install results in the following
> {code}
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/webgrid.py to 
> webgrid.cpython-36.pyc
>   File "build/bdist.macosx-10.7-x86_64/egg/oodt/webgrid.py", line 51
> except Exception, e:
> ^
> SyntaxError: invalid syntax
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/workflow.py to 
> workflow.cpython-36.pyc
>   File "build/bdist.macosx-10.7-x86_64/egg/oodt/workflow.py", line 129
> print 'available events:', events
> ^
> SyntaxError: Missing parentheses in call to 'print'
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/xmlutils.py to 
> xmlutils.cpython-36.pyc
> creating build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/PKG-INFO -> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/SOURCES.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/dependency_links.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/entry_points.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/namespace_packages.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/top_level.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/zip-safe -> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> creating dist
> creating 'dist/oodt-1.2.dev_r0-py3.6.egg' and adding 
> 'build/bdist.macosx-10.7-x86_64/egg' to it
> removing 'build/bdist.macosx-10.7-x86_64/egg' (and everything under it)
> Processing oodt-1.2.dev_r0-py3.6.egg
> Copying oodt-1.2.dev_r0-py3.6.egg to 
> /Users/lmcgibbn/miniconda3/lib/python3.6/site-packages
> Adding oodt 1.2.dev-r0 to easy-install.pth file
> Installing webgrid script to /Users/lmcgibbn/miniconda3/bin
> Installed 
> /Users/lmcgibbn/miniconda3/lib/python3.6/site-packages/oodt-1.2.dev_r0-py3.6.egg
> Processing dependencies for oodt===1.2.dev-r0
> Finished processing dependencies for oodt===1.2.dev-r0
> {code}
> Fix coming up



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OODT-994) Replace deprecated -Djava.ext.dirs with -classpath

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha updated OODT-994:
---
Fix Version/s: (was: 1.9)

> Replace deprecated -Djava.ext.dirs with -classpath
> --
>
> Key: OODT-994
> URL: https://issues.apache.org/jira/browse/OODT-994
> Project: OODT
>  Issue Type: Improvement
>  Components: radix
> Environment: Apache Maven 3.5.4 
> (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T11:33:14-07:00)
> Maven home: /usr/local/Cellar/maven/3.5.4/libexec
> Java version: 10.0.2, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk-10.0.2.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "Mac"
> OODT master branch
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Blocker
> Fix For: 2.0
>
>
> I'm back working with [coal-sds|https://github.com/capstone-coal/coal-sds] 
> and will be running it under JDK 10 if possible. Immediately upon launching 
> the RADiX deployment, all hell breaks loose
> {code}
> Resource Manager started PID file 
> (/usr/local/coal-sds-deploy/resmgr/run/cas.resmgr.pid).
> Workflow Manager started PID file 
> (/usr/local/coal-sds-deploy/workflow/run/cas.workflow.pid).
> -Djava.ext.dirs=/usr/local/coal-sds-deploy/filemgr/lib is not supported.  Use 
> -classpath instead.
> -Djava.ext.dirs=/usr/local/coal-sds-deploy/workflow/lib is not supported.  
> Use -classpath instead.
> -Djava.ext.dirs=/usr/local/coal-sds-deploy/resmgr/lib is not supported.  Use 
> -classpath instead.
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.Error: Could not 
> create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> On my macOS Sierra v10.12.6 the following statement does a find and replace 
> for all instances of '-Djava.ext.dirs', replacing with '-classpath'
> {code}
> git grep -lz '\-Djava.ext.dirs' | xargs -0 perl -i'' -pE 
> "s/-Djava.ext.dirs/-classpath/g"
> {code}
> PR coming up.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (OODT-1033) Update workflow and resource manager to not use properties files shipped within the jars

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha resolved OODT-1033.
-
Fix Version/s: 1.9.1
   Resolution: Fixed

Fixed with OODT-1031

> Update workflow and resource manager to not use properties files shipped 
> within the jars
> 
>
> Key: OODT-1033
> URL: https://issues.apache.org/jira/browse/OODT-1033
> Project: OODT
>  Issue Type: Sub-task
>  Components: resource manager, workflow manager
>    Reporter: Imesha Sudasingha
>Priority: Major
> Fix For: 1.9.1
>
>
> Update Workflow and Resource manager to not automatically use their internal 
> /workflow.properties and /resource.properties shipped within the jar.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (OODT-1032) Make XmlRpc the default if the system properties aren’t read correctly

[Imesha Sudasingha (Jira)]

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

Imesha Sudasingha resolved OODT-1032.
-
Fix Version/s: 1.9.1
   Resolution: Fixed

> Make XmlRpc the default if the system properties aren’t read correctly
> --
>
> Key: OODT-1032
> URL: https://issues.apache.org/jira/browse/OODT-1032
> Project: OODT
>  Issue Type: Sub-task
>  Components: file manager, resource manager, workflow manager
>Affects Versions: 1.9
>    Reporter: Imesha Sudasingha
>Priority: Major
> Fix For: 1.9.1
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (OODT-1034) Update XmlRpcResourceManager to function correctly with the call to the main() method

[Imesha Sudasingha (Jira)]

Imesha Sudasingha created OODT-1034:
---

 Summary: Update XmlRpcResourceManager to function correctly with 
the call to the main() method
 Key: OODT-1034
 URL: https://issues.apache.org/jira/browse/OODT-1034
 Project: OODT
  Issue Type: Sub-task
  Components: resource manager
Affects Versions: 1.9
Reporter: Imesha Sudasingha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [ANNOUNCE] Apache OODT 1.9 released

[Imesha Sudasingha]

Great work Tom!

On Thu, 3 Oct 2019 at 14:27, Tom Barber  wrote:

> The Apache OODT project is pleased to announce the release of Apache OODT
> 1.9. The release contents have been pushed out to the main Apache release
> site and to the Maven Central sync, so the releases should be available as
> soon as the mirrors get the syncs.
>
> Apache OODT is a software framework as well as an architectural style for
> the rapid construction of scientific data systems.  It provides components
> for data capture, curation, metadata extraction, workflow management,
> resource management, and data processing.
>
> Apache OODT 1.9 contains a number of improvements and bug fixes. Details
> can be found in the changes file:
> http://www.apache.org/dist/oodt/CHANGES-1.9.txt
>
> Apache OODT is available in source form from the following download page:
> http://www-us.apache.org/dist/oodt/apache-oodt-1.9-src.zip
>
> Apache OODT is also available in binary form or for use using Maven 2 from
> the Central Repository: http://repo1.maven.org/maven2/org/apache/oodt/
>
> In the initial 48 hours, the release may not be available on all mirrors.
> When downloading from a mirror site, please remember to verify the
> downloads using signatures found on the Apache site:
> https://people.apache.org/keys/group/oodt.asc
> For more information on Apache OODT, visit the project home page:
> http://oodt.apache.org/
>
> -- Tom Barber, on behalf of the Apache OODT community
>
> --
>
>
> Spicule Limited is registered in England & Wales. Company Number:
> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
>
>
> All engagements
> are subject to Spicule Terms and Conditions of Business. This email and
> its
> contents are intended solely for the individual to whom it is addressed
> and
> may contain information that is confidential, privileged or otherwise
> protected from disclosure, distributing or copying. Any views or opinions
> presented in this email are solely those of the author and do not
> necessarily represent those of Spicule Limited. The company accepts no
> liability for any damage caused by any virus transmitted by this email. If
> you have received this message in error, please notify us immediately by
> reply email before deleting it from your system. Service of legal notice
> cannot be effected on Spicule Limited by email.
>

Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4

[Imesha Sudasingha]

PPED
>
>
>
> [INFO] OODT Process Control System JAX-RS service layer ... SKIPPED
>
>
>
> [INFO] Apache OODT  SKIPPED
>
>
>
> [INFO]
>
> 
>
>
>
> [INFO] BUILD FAILURE
>
>
>
> [INFO]
>
> 
>
>
>
> [INFO] Total time: 06:43 min
>
>
>
> [INFO] Finished at: 2019-10-02T09:08:20-07:00
>
>
>
> [INFO]
>
> 
>
>
>
> [ERROR] Failed to execute goal
>
> org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test)
>
> on project cas-workflow: There are test failures.
>
>
>
> [ERROR]
>
>
>
> [ERROR] Please refer to
>
> /Users/mattmann/git/oodt/workflow/target/surefire-reports for the
>
> individual test results.
>
>
>
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
>
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
>
>
>
> [ERROR] -> [Help 1]
>
>
>
> [ERROR]
>
>
>
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
>
> switch.
>
>
>
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
>
>
> [ERROR]
>
>
>
> [ERROR] For more information about the errors and possible solutions,
>
> please read the following articles:
>
>
>
> [ERROR] [Help 1]
>
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
>
>
> [ERROR]
>
>
>
> [ERROR] After correcting the problems, you can resume the build with the
>
> command
>
>
>
> [ERROR] mvn  -rf :cas-workflow
>
>
>
> pomodoro:oodt mattmann$ git branch
>
>
>
> * (HEAD detached at 1.9)
>
>
>
> 0.12-release
>
>
>
> 1.2.1
>
>
>
> OODT-967
>
>
>
> OODT-972
>
>
>
> OODT-973
>
>
>
> OODT-978
>
>
>
> asf-site
>
>
>
> development
>
>
>
> feature/zookeeper-config
>
>
>
> master
>
>
>
> merge-avro-dynworkflow
>
>
>
> regex-exclude-merge
>
>
>
> release-1.2.3
>
>
>
> site-dev
>
>
>
>
>
>
>
> Is there a possibility Tom didn’t push Imesha’s fix and create a new tag?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: Chris Mattmann 
>
> Date: Wednesday, October 2, 2019 at 9:08 AM
>
> To: "dev@oodt.apache.org" 
>
> Cc: Chris Mattmann 
>
> Subject: Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4
>
>
>
>
>
>
>
> It is building further now and I already had brew cask. I am going to
>
> update the wiki with
>
> the export command to build b/c it is something we will want to capture.
>
>
>
>
>
>
>
> Speaking of which I don’t have perms to edit the wiki anymore. Imesha or
>
> Tom can you
>
> can me perms?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: Imesha Sudasingha 
>
> Reply-To: "dev@oodt.apache.org" 
>
> Date: Tuesday, October 1, 2019 at 6:42 PM
>
> To: dev 
>
> Cc: Chris Mattmann 
>
> Subject: Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4
>
>
>
>
>
>
>
> Hi Chris,
>
>
>
>
>
>
>
> I think from jdk 10 or 11, xml related libraries (jaxb) have been removed
>
>
>
> from default libraries. That's why you should be getting that error. By the
>
>
>
> look, it seems like an XML related issue.
>
>
>
>
>
>
>
> Thanks,
>
>
>
> Imesha
>
>
>
>
>
>
>
> On Wed, 2 Oct 2019, 3:21 am Tom Barber,  wrote:
>
>
>
>
>
>
>
> brew tap caskroom/versions
>
>
>
> brew cask install java8
>
>
>
>
>
>
>
>
>
>
>
> I think
>
>
>
>
>
>
>
>
>
>
>
> export JAVA_HOME=`/usr/libexec/java_home -v 1.8`
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On 1 October 2019 at 22:42:42, Mattmann, Chris A (US 1761) (
>
>
>
> chris.a.mattm...@jpl.nasa.gov.invalid) wrote:
>
>
>
>
>
>
>
> Any links to install one that old on mac?
>
>
>
>
>
>
>
> Sent from my iPhone
>
>
>
>
>
>
>
> On Oct 1, 2019, at 2:28 PM, Tom Barber  wrote:
>
>
>
>
>
>
>
> 8, 9 I think will be okay 10+ will be questionable due the change in API
>
>
>
> and jars that need upgrading for compatibility.
>
>

Re: [EXTERNAL] Re: [VOTE] OODT 1.9 RC 4

[Imesha Sudasingha]

Hi Chris,

I think from jdk 10 or 11, xml related libraries (jaxb) have been removed
from default libraries. That's why you should be getting that error. By the
look, it seems like an XML related issue.

Thanks,
Imesha

On Wed, 2 Oct 2019, 3:21 am Tom Barber,  wrote:

> brew tap caskroom/versions
> brew cask install java8
>
>
> I think
>
>
> export JAVA_HOME=`/usr/libexec/java_home -v 1.8`
>
>
>
> On 1 October 2019 at 22:42:42, Mattmann, Chris A (US 1761) (
> chris.a.mattm...@jpl.nasa.gov.invalid) wrote:
>
> Any links to install one that old on mac?
>
> Sent from my iPhone
>
> > On Oct 1, 2019, at 2:28 PM, Tom Barber  wrote:
> >
> > 8, 9 I think will be okay 10+ will be questionable due the change in API
> > and jars that need upgrading for compatibility.
> >
> >
> > On 1 October 2019 at 21:58:35, Chris Mattmann (mattm...@apache.org)
> wrote:
> >
> > OK so I need JDK8 to build, is that right?
> >
> >
> >
> >
> >
> >
> >
> > From: Tom Barber 
> > Reply-To: 
> > Date: Tuesday, October 1, 2019 at 1:57 PM
> > To: , Chris Mattmann , Imesha
> > Sudasingha 
> > Subject: Re: [VOTE] OODT 1.9 RC 4
> >
> >
> >
> > Yeah, I’m amazed you got that far through with 12. I know from other apps
> >
> > migrating from 8 through 12 is a right PITA and something we should look
> at
> >
> > for 2.0.
> >
> >
> >
> >
> >
> > On 1 October 2019 at 21:48:08, Chris Mattmann (mattm...@apache.org)
> wrote:
> >
> >
> >
> > Pom shouldn’t be a blocker.
> >
> >
> >
> >
> >
> >
> >
> > Here is my Java version am I using the right one?
> >
> >
> >
> >
> >
> >
> >
> > pomodoro:oodt mattmann$ java -version
> >
> >
> >
> > openjdk version "12.0.1" 2019-04-16
> >
> >
> >
> > OpenJDK Runtime Environment (build 12.0.1+12)
> >
> >
> >
> > OpenJDK 64-Bit Server VM (build 12.0.1+12, mixed mode, sharing)
> >
> >
> >
> > pomodoro:oodt mattmann$
> >
> >
> >
> >
> >
> >
> >
> > Should I switch?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Tom Barber 
> >
> > Reply-To: 
> >
> > Date: Tuesday, October 1, 2019 at 1:41 PM
> >
> > To: , Imesha Sudasingha 
> >
> > Subject: Re: [VOTE] OODT 1.9 RC 4
> >
> >
> >
> >
> >
> >
> >
> > Results :
> >
> >
> >
> >
> >
> >
> >
> > Tests run: 65, Failures: 0, Errors: 0, Skipped: 0
> >
> >
> >
> >
> >
> >
> >
> > [INFO]
> >
> >
> >
> > 
> >
> >
> >
> > [INFO] BUILD SUCCESS
> >
> >
> >
> > [INFO]
> >
> >
> >
> > --------
> >
> >
> >
> > [INFO] Total time: 14.723 s
> >
> >
> >
> > [INFO] Finished at: 2019-10-01T22:39:58+02:00
> >
> >
> >
> > [INFO] Final Memory: 15M/353M
> >
> >
> >
> > [INFO]
> >
> >
> >
> > 
> >
> >
> >
> > (superset) bugg@spicule-dev:~/oodt/commons>
> >
> >
> >
> >
> >
> >
> >
> > So I can’t replicate Chris’ test failure either, and you’re right Imesha
> >
> >
> >
> > the pom asc appears to be a copy of the pom, but I’ve not touched it so I
> >
> >
> >
> > don’t know why that would be.
> >
> >
> >
> >
> >
> >
> >
> > Does a missing pom asc mean a failed release? I’ve honestly no idea. It
> >
> >
> >
> > would be easier to fix these in 2.x.
> >
> >
> >
> >
> >
> >
> >
> > Tom
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On 1 October 2019 at 19:36:43, Imesha Sudasingha (ime...@apache.org)
> wrote:
> >
> >
> >
> >
> >
> >
> >
> > Hi Tom,
> >
> >
> >
> >
> >
> >
> >
> > Thanks for the release. Builds fine for me.
> >
> >
> >
> > One concern: o

Re: [VOTE] OODT 1.9 RC 4

[Imesha Sudasingha]

Hi Tom,

Thanks for the release. Builds fine for me.
One concern: oodt-1.9.pom.asc seems to be a copy of the pom itself. Not the
signature

Could you check that?

Thanks,
Imesha

On Tue, 1 Oct 2019 at 10:32, Chris Mattmann  wrote:

> Release checks out, but I get a test error:
>
> Running org.apache.oodt.commons.util.XMLTest
>
> Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.323 sec
> <<< FAILURE!
>
> Running org.apache.oodt.commons.io.FixedBufferOutputStreamTest
>
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec
>
> Running org.apache.oodt.commons.MultiServerTest
>
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.177 sec
>
> Running org.apache.oodt.commons.util.Base64Test
>
> Tests run: 1, Failures:
>
>
>
>
>
> Here is the RC verify checksums and MD5, and SIG:
>
> pomodoro:apache-oodt-1.9 mattmann$ /Users/mattmann/bin/stage_apache_rc
> apache-oodt 1.9-src https://dist.apache.org/repos/dist/dev/oodt/
>
>   % Total% Received % Xferd  Average Speed   TimeTime Time
> Current
>
>  Dload  Upload   Total   SpentLeft
> Speed
>
> 100 14.6M  100 14.6M0 0  1869k  0  0:00:08  0:00:08 --:--:--
> 1948k
>
>   % Total% Received % Xferd  Average Speed   TimeTime Time
> Current
>
>  Dload  Upload   Total   SpentLeft
> Speed
>
> 100   473  100   4730 0   2654  0 --:--:-- --:--:-- --:--:--
> 2657
>
> pomodoro:apache-oodt-1.9 mattmann$ ls
>
> apache-oodt-1.9-src.zipapache-oodt-1.9-src.zip.asc
>
> pomodoro:apache-oodt-1.9 mattmann$ $HOME/bin/verify_gpg_sigs
>
> Verifying Signature for file apache-oodt-1.9-src.zip.asc
>
> gpg: assuming signed data in 'apache-oodt-1.9-src.zip'
>
> gpg: Signature made Mon Sep 30 06:40:14 2019 PDT
>
> gpg:using RSA key AC57783AB30355CA
>
> gpg: Can't check signature: No public key
>
> pomodoro:apache-oodt-1.9 mattmann$ curl -O
> https://raw.githubusercontent.com/apache/oodt/master/KEYS
>
>   % Total% Received % Xferd  Average Speed   TimeTime Time
> Current
>
>  Dload  Upload   Total   SpentLeft
> Speed
>
> 100 26954  100 269540 0  68787  0 --:--:-- --:--:-- --:--:--
> 68936
>
> pomodoro:apache-oodt-1.9 mattmann$ gpg --import < KEY
>
> -bash: KEY: No such file or directory
>
> pomodoro:apache-oodt-1.9 mattmann$ gpg --import < KEYS
>
> gpg: key 70F09CC6B876884A: "Chris Mattmann (CODE SIGNING KEY) <
> mattm...@apache.org>" not changed
>
> gpg: key 170B657EF9D98BFA: public key "Sean Colin-Patrick Kelly (CODE
> SIGNING KEY) " imported
>
> gpg: key 11911679FF5B0BD5: public key "David Woollard (CODE SIGNING KEY) <
> wooll...@apache.org>" imported
>
> gpg: key A5DBC0182C47D568: public key "Paul Michael Ramirez (CODE SIGNING
> KEY) " imported
>
> gpg: key 7189700880EF652D: public key "Andrew Hart (CODE SIGNING KEY) <
> ah...@apache.org>" imported
>
> gpg: key D8167171783CE7BB: public key "Tom Barber (CODE SIGNING KEY) <
> magicaltr...@apache.org>" imported
>
> gpg: key 4EAAF8B60C1E654B: "Chris Mattmann (CODE SIGNING KEY - Apr 2016) <
> mattm...@apache.org>" not changed
>
> gpg: key 2B12271BFD01FEDB: "Chris Mattmann " not
> changed
>
> gpg: key AC57783AB30355CA: public key "Tom Barber "
> imported
>
> gpg: Total number processed: 9
>
> gpg:   imported: 6
>
> gpg:  unchanged: 3
>
> pomodoro:apache-oodt-1.9 mattmann$ ls
>
> KEYSapache-oodt-1.9-src.zip
> apache-oodt-1.9-src.zip.asc
>
> pomodoro:apache-oodt-1.9 mattmann$ $HOME/bin/verify_gpg_sigs
>
> Verifying Signature for file apache-oodt-1.9-src.zip.asc
>
> gpg: assuming signed data in 'apache-oodt-1.9-src.zip'
>
> gpg: Signature made Mon Sep 30 06:40:14 2019 PDT
>
> gpg:using RSA key AC57783AB30355CA
>
> gpg: Good signature from "Tom Barber " [unknown]
>
> gpg: WARNING: This key is not certified with a trusted signature!
>
> gpg:  There is no indication that the signature belongs to the
> owner.
>
> Primary key fingerprint: 65C4 6FC2 31C7 756A E60D  B307 AC57 783A B303 55CA
>
> pomodoro:apache-oodt-1.9 mattmann$ verify_md5_sigs
>
> -bash: verify_md5_sigs: command not found
>
> pomodoro:apache-oodt-1.9 mattmann$ verify_md5_checksums
>
> -bash: verify_md5_checksums: command not found
>
> pomodoro:apache-oodt-1.9 mattmann$ $HOME/bin/verify_md5_checksums
>
> md5sum: '*.tar.gz': No such file or directory
>
> md5sum: '*.bz2': No such file or directory
>
> md5sum: '*.tgz': No such file or directory
>
> apache-oodt-1.9-src.zip: OK
>
> pomodoro:apache-oodt-1.9 mattmann$
>
>
>
> Can you please recheck why the test is failing?
>
>
>
> pomodoro:oodt mattmann$ cat
> commons/target/surefire-reports/TEST-org.apache.oodt.commons.util.XMLTest.xml
>
>
> 
>
>  name="org.apache.oodt.commons.util.XMLTest" time="0.319" errors="0"
> skipped="0">
>
>   
>
> 
>
> 
>
>  

[jira] [Created] (OODT-1029) TestAvroRpcWorkflowManager.testGetWorkflowInstances() test failure

[Imesha Sudasingha (Jira)]

Imesha Sudasingha created OODT-1029:
---

 Summary: TestAvroRpcWorkflowManager.testGetWorkflowInstances() 
test failure
 Key: OODT-1029
 URL: https://issues.apache.org/jira/browse/OODT-1029
 Project: OODT
  Issue Type: Bug
  Components: workflow manager
Reporter: Imesha Sudasingha
Assignee: Imesha Sudasingha


{{org.apache.oodt.cas.workflow.system.TestAvroRpcWorkflowManager#testGetWorkflowInstances}}
 test case fails with the following error:
{code:java}
[INFO] 
[INFO] Results:
[INFO] 
[ERROR] Failures: 
[ERROR]   TestAvroRpcWorkflowManager.testGetWorkflowInstances:70 expected:<1> 
but was:<2>
[INFO] 
[ERROR] Tests run: 118, Failures: 1, Errors: 0, Skipped: 10 {code}
The cause seem to be, the exact number of workflow instances are actually 2, 
while we actually check for 1. The even fired ("long") creates 2 workflow 
instances according to the configuration.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [VOTE] OODT 1.9 RC3

[Imesha Sudasingha]

Hi Tom,

Finally :-D Thanks for taking the release. Signature is ok now.
+1 from me.

Should we add the pom to the release as well?

Thanks,
Imesha

On Fri, 27 Sep 2019 at 03:09, Tom Barber  wrote:

> Hi Folks,
>
> I have posted a 3rd release candidate for the Apache OODT 1.9 release. The
> source code is at:
>
> https://dist.apache.org/repos/dist/dev/oodt/
>
> For more detailed information, see the included CHANGES.txt file for
> details on
> release contents and latest changes. The release was made using the OODT
> release process, documented on the Wiki here:
>
> https://cwiki.apache.org/confluence/display/OODT/Release+Process
>
> The release was made from the OODT 1.9 tag (f9db54a) at:
>
> https://github.com/apache/oodt/tree/1.9
>
> A staged Maven repository is available at:
>
> https://repository.apache.org/content/repositories/orgapacheoodt-1022
>
> Please vote on releasing these packages as Apache OODT 1.9. The vote is
> open for at least the next 72 hours.
>
> Only votes from OODT PMC are binding, but folks are welcome to check the
> release candidate and voice their approval or disapproval. The vote passes
> if at least three binding +1 votes are cast.
>
> [ ] +1 Release the packages as Apache OODT 
>
> [ ] -1 Do not release the packages because...
>
> Thanks!
>
> Tom
>
> P.S. Here is my +1.
>
> --
>
>
> Spicule Limited is registered in England & Wales. Company Number:
> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
>
>
> All engagements
> are subject to Spicule Terms and Conditions of Business. This email and
> its
> contents are intended solely for the individual to whom it is addressed
> and
> may contain information that is confidential, privileged or otherwise
> protected from disclosure, distributing or copying. Any views or opinions
> presented in this email are solely those of the author and do not
> necessarily represent those of Spicule Limited. The company accepts no
> liability for any damage caused by any virus transmitted by this email. If
> you have received this message in error, please notify us immediately by
> reply email before deleting it from your system. Service of legal notice
> cannot be effected on Spicule Limited by email.
>

Re: [VOTE] OODT 1.9 RC1

[Imesha Sudasingha]

Hi Tom,

Great work proceeding with the release.
+1 from me.

I however could not verify the signature. I assume that is an issue on my
side. Can someone else verify that?

Thanks,
Imesha

On Tue, 24 Sep 2019 at 04:33, Tom Barber  wrote:

> Hi Folks,
>
> I have posted a 1st release candidate for the Apache OODT 1.9 release. The
> source code is at:
>
> https://dist.apache.org/repos/dist/dev/oodt/
>
> For more detailed information, see the included CHANGES.txt file for
> details on
> release contents and latest changes. The release was made using the OODT
> release process, documented on the Wiki here:
>
> https://cwiki.apache.org/confluence/display/OODT/Release+Process
>
> The release was made from the OODT 1.9 tag (re520827) at:
>
> https://github.com/apache/oodt/tree/1.9
>
> A staged Maven repository is available at:
>
> https://repository.apache.org/content/repositories/orgapacheoodt-1020
>
> Please vote on releasing these packages as Apache OODT 1.9. The vote is
> open for at least the next 72 hours.
>
> Only votes from OODT PMC are binding, but folks are welcome to check the
> release candidate and voice their approval or disapproval. The vote passes
> if at least three binding +1 votes are cast.
>
> [ ] +1 Release the packages as Apache OODT 1.9
>
> [ ] -1 Do not release the packages because...
>
> Thanks!
>
> Tom
>
> P.S. Here is my +1.
>
> --
>
>
> Spicule Limited is registered in England & Wales. Company Number:
> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
>
>
> All engagements
> are subject to Spicule Terms and Conditions of Business. This email and
> its
> contents are intended solely for the individual to whom it is addressed
> and
> may contain information that is confidential, privileged or otherwise
> protected from disclosure, distributing or copying. Any views or opinions
> presented in this email are solely those of the author and do not
> necessarily represent those of Spicule Limited. The company accepts no
> liability for any damage caused by any virus transmitted by this email. If
> you have received this message in error, please notify us immediately by
> reply email before deleting it from your system. Service of legal notice
> cannot be effected on Spicule Limited by email.
>