[jira] [Commented] (EDGENT-179) console: oplet coloring gradients "too close"

[Queenie Ma (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524187#comment-15524187
 ] 

Queenie Ma commented on EDGENT-179:
---

I think that's a good idea, and I'll work on implementing it. Thank you for 
your input!

> console: oplet coloring gradients "too close"
> -
>
> Key: EDGENT-179
> URL: https://issues.apache.org/jira/browse/EDGENT-179
> Project: Edgent
>  Issue Type: Bug
>  Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
> Attachments: EDGENT-179_oplet_colors.png, Screen Shot 2016-09-19 at 
> 2.22.00 PM.png
>
>
> The oplet color generator ends up yielding two light purple-ish colors for 
> two different kinds of (adjacent) oplets and one can't tell them apart.  One 
> is a Sink the other is a subtype of Peek - a StreamScope.
> I was seeing this in a ParallelBalancedRecipe app of mine.  I can provide it 
> if really necessary to repro/improve this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-178) console: stream hover should report "alias" in addition to tags; maybe oplet hover too

[Queenie Ma (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524184#comment-15524184
 ] 

Queenie Ma commented on EDGENT-178:
---

[~dlaboss], would you mind giving me an idea of what you think should be 
displayed for oplet hovers? Perhaps what is mentioned in the previous comment? 
Thanks!

> console: stream hover should report "alias" in addition to tags; maybe oplet 
> hover too
> --
>
> Key: EDGENT-178
> URL: https://issues.apache.org/jira/browse/EDGENT-178
> Project: Edgent
>  Issue Type: Improvement
>  Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
>  Labels: newbie
> Attachments: alias_stream_hover.png
>
>
> TStream.alias("someAlias") manifests itself in graph.Connector similar to 
> tags. I'm pretty sure the graph json captures the alias already.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EDGENT-34) Work on License and Notices files for Quarks

[Dale LaBossiere (JIRA)]

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

Dale LaBossiere updated EDGENT-34:
--
Description: 
Update the notices file with the IBM copyright so the source file copyrights 
can be changed.  Review the included software and update the license or notices 
as appropriate.
http://www.apache.org/dev/licensing-howto.html
http://apache.org/legal/resolved.html#criteria
http://www.apache.org/legal/src-headers.html

Status:
- the Edgent source files headers contain the correct ASF info
- the gradle work includes corrected info in the Edgent jars (EDGENT-133)
- the LICENSE and NOTICE file in the repository are accurate once 
3rd-party-jars are removed from the repo
- the top-level LICENSE and/or NOTICE in the ant and gradle generated "release" 
build tgz file needs work as the tgz continues to include various 3rd party 
jars.  Use this issue to address this.  *Need to identify exactly what needs to 
be done here.*

  was:
Update the notices file with the IBM copyright so the source file copyrights 
can be changed.  Review the included software and update the license or notices 
as appropriate.
http://www.apache.org/dev/licensing-howto.html
http://apache.org/legal/resolved.html#criteria
http://www.apache.org/legal/src-headers.html


> Work on License and Notices files for Quarks
> 
>
> Key: EDGENT-34
> URL: https://issues.apache.org/jira/browse/EDGENT-34
> Project: Edgent
>  Issue Type: Task
>  Components: Miscellaneous
>Reporter: Kathy Saunders
>Assignee: Kathy Saunders
>  Labels: legal
>
> Update the notices file with the IBM copyright so the source file copyrights 
> can be changed.  Review the included software and update the license or 
> notices as appropriate.
> http://www.apache.org/dev/licensing-howto.html
> http://apache.org/legal/resolved.html#criteria
> http://www.apache.org/legal/src-headers.html
> Status:
> - the Edgent source files headers contain the correct ASF info
> - the gradle work includes corrected info in the Edgent jars (EDGENT-133)
> - the LICENSE and NOTICE file in the repository are accurate once 
> 3rd-party-jars are removed from the repo
> - the top-level LICENSE and/or NOTICE in the ant and gradle generated 
> "release" build tgz file needs work as the tgz continues to include various 
> 3rd party jars.  Use this issue to address this.  *Need to identify exactly 
> what needs to be done here.*



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EDGENT-34) Work on License and Notices files for Edgent "tgz"

[Dale LaBossiere (JIRA)]

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

Dale LaBossiere updated EDGENT-34:
--
Summary: Work on License and Notices files for Edgent "tgz"  (was: Work on 
License and Notices files for Quarks)

> Work on License and Notices files for Edgent "tgz"
> --
>
> Key: EDGENT-34
> URL: https://issues.apache.org/jira/browse/EDGENT-34
> Project: Edgent
>  Issue Type: Task
>  Components: Miscellaneous
>Reporter: Kathy Saunders
>Assignee: Dale LaBossiere
>  Labels: legal
>
> Update the notices file with the IBM copyright so the source file copyrights 
> can be changed.  Review the included software and update the license or 
> notices as appropriate.
> http://www.apache.org/dev/licensing-howto.html
> http://apache.org/legal/resolved.html#criteria
> http://www.apache.org/legal/src-headers.html
> Status:
> - the Edgent source files headers contain the correct ASF info
> - the gradle work includes corrected info in the Edgent jars (EDGENT-133)
> - the LICENSE and NOTICE file in the repository are accurate once 
> 3rd-party-jars are removed from the repo
> - the top-level LICENSE and/or NOTICE in the ant and gradle generated 
> "release" build tgz file needs work as the tgz continues to include various 
> 3rd party jars.  Use this issue to address this.  *Need to identify exactly 
> what needs to be done here.*



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (EDGENT-34) Work on License and Notices files for Quarks

[Dale LaBossiere (JIRA)]

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

Dale LaBossiere reassigned EDGENT-34:
-

Assignee: Dale LaBossiere  (was: Kathy Saunders)

> Work on License and Notices files for Quarks
> 
>
> Key: EDGENT-34
> URL: https://issues.apache.org/jira/browse/EDGENT-34
> Project: Edgent
>  Issue Type: Task
>  Components: Miscellaneous
>Reporter: Kathy Saunders
>Assignee: Dale LaBossiere
>  Labels: legal
>
> Update the notices file with the IBM copyright so the source file copyrights 
> can be changed.  Review the included software and update the license or 
> notices as appropriate.
> http://www.apache.org/dev/licensing-howto.html
> http://apache.org/legal/resolved.html#criteria
> http://www.apache.org/legal/src-headers.html
> Status:
> - the Edgent source files headers contain the correct ASF info
> - the gradle work includes corrected info in the Edgent jars (EDGENT-133)
> - the LICENSE and NOTICE file in the repository are accurate once 
> 3rd-party-jars are removed from the repo
> - the top-level LICENSE and/or NOTICE in the ant and gradle generated 
> "release" build tgz file needs work as the tgz continues to include various 
> 3rd party jars.  Use this issue to address this.  *Need to identify exactly 
> what needs to be done here.*



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EDGENT-87) Create first incubating release

[Dale LaBossiere (JIRA)]

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

Dale LaBossiere updated EDGENT-87:
--
Description: 
Create first Apache Quarks incubating release.

Currently just a placeholder to act as a place to put issues that must be 
completed first;

Depends on (list will get bigger):

QUARKS-34 (Work on licensing and notices)
QUARKS-89 (Add License in  Edgent jars)
EDGENT-133 (License in Edgent jars)
QUARKS-62 (Replace IBM copywrite in headers)
QUARKS-65 (possibly web site and doc to follow ASF guidelines)
QUARKS-88 (Add Apache license headers)
PODLINGNAMESEARCH-98 (I assume)
QUARKS-139 (Adopt gradle)

Others should feel free to create issues and add them to this list.


  was:
Create first Apache Quarks incubating release.

Currently just a placeholder to act as a place to put issues that must be 
completed first;

Depends on (list will get bigger):

QUARKS-34
QUARKS-62
QUARKS-65 (possibly)
QUARKS-88
QUARKS-89
PODLINGNAMESEARCH-98 (I assume)
QUARKS-139

Others should feel free to create issues and add them to this list.



> Create first incubating release
> ---
>
> Key: EDGENT-87
> URL: https://issues.apache.org/jira/browse/EDGENT-87
> Project: Edgent
>  Issue Type: Task
>Reporter: Daniel John Debrunner
>
> Create first Apache Quarks incubating release.
> Currently just a placeholder to act as a place to put issues that must be 
> completed first;
> Depends on (list will get bigger):
> QUARKS-34 (Work on licensing and notices)
> QUARKS-89 (Add License in  Edgent jars)
> EDGENT-133 (License in Edgent jars)
> QUARKS-62 (Replace IBM copywrite in headers)
> QUARKS-65 (possibly web site and doc to follow ASF guidelines)
> QUARKS-88 (Add Apache license headers)
> PODLINGNAMESEARCH-98 (I assume)
> QUARKS-139 (Adopt gradle)
> Others should feel free to create issues and add them to this list.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EDGENT-239) [gradle] need tests that run against distribution tree/jars

[Dale LaBossiere (JIRA)]

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

Dale LaBossiere resolved EDGENT-239.

Resolution: Fixed

The work for this task was covered in EDGENT-240 and in particular its PR 
https://github.com/apache/incubator-edgent/pull/190

> [gradle] need tests that run against distribution tree/jars
> ---
>
> Key: EDGENT-239
> URL: https://issues.apache.org/jira/browse/EDGENT-239
> Project: Edgent
>  Issue Type: Bug
>  Components: Miscellaneous
>Reporter: Dale LaBossiere
>
> "gradle test" ("build") runs the tests against the class files in the build 
> tree, it does NOT run them against the jars in distribution tree ("ant test" 
> did).  The net is that we don't seem to have anything validating the 
> distribution tree/jars.
> Seems like we need a new task that causes tests to be run against the 
> distribution tree/jars.  I don't think we want to warp the std "test" task to 
> do that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EDGENT-139) Adopt a build system, such as gradle, that supports transitive dependency management

[Dale LaBossiere (JIRA)]

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

Dale LaBossiere updated EDGENT-139:
---
Description: 
By moving to a build system that supports transitive dependency management, the 
repository size can be decreased and users can more easily integrate quarks 
with their own applications by allowing the version of a dependency to float 
within an acceptable range, assuming proper semantic versioning of the 
dependencies.

[~bjhargrave] has created the initial set of gradle files with PR-131.  The 
gradle work is still WIP.  The existing build mechanisms are still in place and 
are to be used.

TODOs
- Add license headers to gradle files - QUARKS-203
- Update build doc EDGENT-240 [TODO final updates when flipping the switch]
- Java7 build support EDGENT-240
- Android build support EDGENT-240
- add manifest classpath entries  EDGENT-240
- Release target, creating the target/… structure - QUARKS-204, EDGENT-240
- Junit parity - QUARKS-223, QUARKS-237, QUARKS-239
  - need top level aggregating report
- Javadoc parity - QUARKS-205
- Jacoco parity - QUARKS-237
- building from Eclipse - EDGENT-251
  - .classpath files have refs to ext jars that will be removed from the 
repo
- switch travis-ci to gradle - EDGENT-252 (mostly done)
- cleanup
  - remove ext jars from repo.  
Question: ext contains LICENSE/NOTICE/README files.  
  Note needed anymore as Quarks repo won’t contain the jars?
  Just want something in README.md or such to list the dependencies?
  - remove the ant build related files

[ Original from [~lfeagan]
I have an initial set of work for this effort completed using gradle. Nearly 
all sub-projects build at this time--the notable exception being the 
android-dependent sub-projects. The other notable missing element is the 
integration of JaCoCo. In both cases, these should be simple additions. ]

  was:
By moving to a build system that supports transitive dependency management, the 
repository size can be decreased and users can more easily integrate quarks 
with their own applications by allowing the version of a dependency to float 
within an acceptable range, assuming proper semantic versioning of the 
dependencies.

[~bjhargrave] has created the initial set of gradle files with PR-131.  The 
gradle work is still WIP.  The existing build mechanisms are still in place and 
are to be used.

TODOs
- Add license headers to gradle files - QUARKS-203
- Update build doc EDGENT-240
- Java7 build support EDGENT-240
- Android build support EDGENT-240
- add manifest classpath entries  EDGENT-240
- Release target, creating the target/… structure - QUARKS-204, EDGENT-240
- Junit parity - QUARKS-223, QUARKS-237, QUARKS-239
  - need top level aggregating report
- Javadoc parity - QUARKS-205
- Jacoco parity - QUARKS-237
- building from Eclipse
  - .classpath files have refs to ext jars that will be removed from the repo
- switch travis-ci to gradle
- cleanup
  - remove ext jars from repo.  
Question: ext contains LICENSE/NOTICE/README files.  
  Note needed anymore as Quarks repo won’t contain the jars?
  Just want something in README.md or such to list the dependencies?
  - remove the ant build related files

[ Original from [~lfeagan]
I have an initial set of work for this effort completed using gradle. Nearly 
all sub-projects build at this time--the notable exception being the 
android-dependent sub-projects. The other notable missing element is the 
integration of JaCoCo. In both cases, these should be simple additions. ]


> Adopt a build system, such as gradle, that supports transitive dependency 
> management
> 
>
> Key: EDGENT-139
> URL: https://issues.apache.org/jira/browse/EDGENT-139
> Project: Edgent
>  Issue Type: Improvement
>  Components: Analytics, API, Applications, Connectors, Console, 
> Documentation, Miscellaneous, Runtime, Samples, Test, Utils
>Reporter: Lance Feagan
>Assignee: Dale LaBossiere
>  Labels: build
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> By moving to a build system that supports transitive dependency management, 
> the repository size can be decreased and users can more easily integrate 
> quarks with their own applications by allowing the version of a dependency to 
> float within an acceptable range, assuming proper semantic versioning of the 
> dependencies.
> [~bjhargrave] has created the initial set of gradle files with PR-131.  The 
> gradle work is still WIP.  The existing build mechanisms are still in place 
> and are to be used.
> TODOs
> - Add license headers to gradle files - QUARKS-203
> - Update build doc EDGENT-240 [TODO final updates when flipping the switch]
> - Java7 build support EDGENT-240
> - Android build support 

[jira] [Created] (EDGENT-252) use gradle build from travis-ci

[Dale LaBossiere (JIRA)]

Dale LaBossiere created EDGENT-252:
--

 Summary: use gradle build from travis-ci
 Key: EDGENT-252
 URL: https://issues.apache.org/jira/browse/EDGENT-252
 Project: Edgent
  Issue Type: Task
Reporter: Dale LaBossiere
Assignee: Dale LaBossiere


The work is included in PR https://github.com/apache/incubator-edgent/pull/194

Need to decide when to flip the switch and cease using the ant build env in 
travis-ci.  May do that soon / before the full switch over occurs to exercise 
it more.

TODO need to look at how the ant build tweaked the output/config of some tasks 
when running in ci mode.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EDGENT-205) Create gradle Javadoc task

[Dale LaBossiere (JIRA)]

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

Dale LaBossiere resolved EDGENT-205.

Resolution: Fixed

> Create gradle Javadoc task
> --
>
> Key: EDGENT-205
> URL: https://issues.apache.org/jira/browse/EDGENT-205
> Project: Edgent
>  Issue Type: Task
>Reporter: Cazen Lee
>Assignee: Cazen Lee
>Priority: Minor
>  Labels: build, newbie
>
> Javadoc parity with ant javadoc task



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EDGENT-240) [gradle] add task to create a release tgz

[Dale LaBossiere (JIRA)]

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

Dale LaBossiere resolved EDGENT-240.

Resolution: Fixed

> [gradle] add task to create a release tgz
> -
>
> Key: EDGENT-240
> URL: https://issues.apache.org/jira/browse/EDGENT-240
> Project: Edgent
>  Issue Type: Task
>  Components: Miscellaneous
>Reporter: Dale LaBossiere
>Assignee: Dale LaBossiere
>
> This issue is being used to cover gradle work for:
> - populating the "target dir" with the appropriate project and external jars, 
> for java8, java7, and android targets
> - adding manifest classpaths to our project jars
> - "gradlew release" (including full android support jars when 
> ANDROID_SDK_PLATFORM is set)
> - updating the build doc



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EDGENT-251) [gradle] initial work for developing Edgent runtime with gradle in Eclipse

[Dale LaBossiere (JIRA)]

Dale LaBossiere created EDGENT-251:
--

 Summary: [gradle] initial work for developing Edgent runtime with 
gradle in Eclipse
 Key: EDGENT-251
 URL: https://issues.apache.org/jira/browse/EDGENT-251
 Project: Edgent
  Issue Type: Task
Reporter: Dale LaBossiere
Assignee: Dale LaBossiere


An Eclipse-based Edgent runtime development enviroment depends on the 3rd party 
jars currently present in the Edgent repository (the Eclipse .classpath files 
present in the repository depend on them)

Those jars will be removed, replaced by a gradle based build environment, when 
all of the pieces are in place  - EDGENT-139.

This issue is for working towards getting an Eclipse based development 
environment working in the absence of 3rd-party jars in the repo, utilizing the 
integration with gradle to achieve that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-240) [gradle] add task to create a release tgz

[Dale LaBossiere (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15523700#comment-15523700
 ] 

Dale LaBossiere commented on EDGENT-240:


Added some gradle script cleanup in PR 
https://github.com/apache/incubator-edgent/pull/196

> [gradle] add task to create a release tgz
> -
>
> Key: EDGENT-240
> URL: https://issues.apache.org/jira/browse/EDGENT-240
> Project: Edgent
>  Issue Type: Task
>  Components: Miscellaneous
>Reporter: Dale LaBossiere
>Assignee: Dale LaBossiere
>
> This issue is being used to cover gradle work for:
> - populating the "target dir" with the appropriate project and external jars, 
> for java8, java7, and android targets
> - adding manifest classpaths to our project jars
> - "gradlew release" (including full android support jars when 
> ANDROID_SDK_PLATFORM is set)
> - updating the build doc



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-edgent pull request #196: Edgent-240 [gradle] script cleanup

[dlaboss]

GitHub user dlaboss reopened a pull request:

https://github.com/apache/incubator-edgent/pull/196

Edgent-240 [gradle] script cleanup



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dlaboss/incubator-edgent gradleHygiene

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-edgent/pull/196.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #196


commit d5d6e1558f604b5fba8dad687b6af1231f4ee857
Author: Dale LaBossiere 
Date:   2016-09-26T15:42:42Z

Edgent-240 [gradle] script cleanup




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-edgent pull request #196: Edgent-240 [gradle] script cleanup

[dlaboss]

GitHub user dlaboss opened a pull request:

https://github.com/apache/incubator-edgent/pull/196

Edgent-240 [gradle] script cleanup



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dlaboss/incubator-edgent gradleHygiene

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-edgent/pull/196.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #196


commit d5d6e1558f604b5fba8dad687b6af1231f4ee857
Author: Dale LaBossiere 
Date:   2016-09-26T15:42:42Z

Edgent-240 [gradle] script cleanup




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---