[jira] [Resolved] (AVRO-1420) C# documentation is completely empty/wiped out

[Brian Lachniet (JIRA)]

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

Brian Lachniet resolved AVRO-1420.
--
Resolution: Fixed

It appears that this issue was resolved some time ago. The documentation is 
available at 
[http://avro.apache.org/docs/current/api/csharp/html/.|http://avro.apache.org/docs/current/api/csharp/html/]
 I'm marking this issue as resolved. Let me know if you think more needs to be 
done.

> C# documentation is completely empty/wiped out
> --
>
> Key: AVRO-1420
> URL: https://issues.apache.org/jira/browse/AVRO-1420
> Project: Apache Avro
>  Issue Type: Bug
>  Components: csharp, doc
>Affects Versions: 1.7.5
>Reporter: Sid S
>Priority: Major
>
> 1. Go to http://avro.apache.org/docs/current/api/csharp/index.html
> 2. Find blank page
> Note that this is the root page for C# documentation, went there looking for 
> basic hello world style documentation to get started.



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

[jira] [Assigned] (AVRO-1381) Publish C# artifacts to NuGet

[Brian Lachniet (JIRA)]

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

Brian Lachniet reassigned AVRO-1381:


Assignee: Brian Lachniet

> Publish C# artifacts to NuGet
> -
>
> Key: AVRO-1381
> URL: https://issues.apache.org/jira/browse/AVRO-1381
> Project: Apache Avro
>  Issue Type: New Feature
>  Components: csharp
>Affects Versions: 1.7.5
>Reporter: Mark Lamley
>Assignee: Brian Lachniet
>Priority: Major
> Fix For: 1.9.0
>
>
> Currently referencing Avro requires manually downloading, compiling and 
> referencing the compiled library. It would be nice to simply reference the 
> compiled library from http://www.nuget.org/ instead.



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

Re: Status of 1.9....

[Brian Lachniet]

That resolved my issue. I'm now able to assign issues to myself. Thank you!

On Mon, Jan 21, 2019 at 3:15 PM Driesprong, Fokko 
wrote:

> Brian, I recently added you as a contributor to the Jira. Could you try
> again to assign the ticket?
>
> I'm happy to help with the 1.9 release.
>
> Cheers, Fokko
>
> Op vr 18 jan. 2019 om 00:10 schreef Brian Lachniet :
>
> > It appears that I don't have permissions to edit or assign issues to
> > myself. Is that something I should have permissions for, or should I ask
> > someone to assign specific issues to me?
> >
> > On Thu, Jan 17, 2019, 8:19 AM Daniel Kulp  >
> > >
> > >
> > > > On Jan 16, 2019, at 9:29 PM, Thiruvalluvan MG
> > 
> > > wrote:
> > > >
> > > > To get a sense of what needs to be done, can you please review the
> > > pending issues for 1.9.0? According to JIRA, there are 43 unresolved
> > issues
> > > with Fix Version 1.9.0. Issue Navigator - ASF JIRA
> > > >
> > >
> > > https://issues.apache.org/jira/projects/AVRO/versions/1294
> > >
> > >
> > >
> > > > Please add the fix version to the issues outside the list that should
> > be
> > > resolved for the release and remove the fix version if some of the
> issues
> > > in the list need not be or cannot be resolved for 1.9.0. Also if you
> > intend
> > > to resolve it in the near future, please assign the issues to yourself.
> > > Thank you.
> > > > I've done the exercise for C++. There are three C++ issues unresolved
> > > and I'll address them before the weekend.
> > > > Thank you,
> > >
> > > Well, the main point is that not all of those 43 issues are going to
> get
> > > done for 1.9.  If someone is not actively working on it to be done in
> the
> > > next week or so, I’m going to remove them from 1.9.  I don’t see the
> > point
> > > in holding up a release that fixes 180 issues waiting for stuff that
> may
> > or
> > > may not ever get complete.   Thus, everyone, please take a look at the
> > list
> > > and if you aren’t working on something that is assigned to you, remove
> it
> > > from 1.9.
> > >
> > > That said, I’ll try and take a look at the 17 that have “Patch
> > > Available”.   If it’s just a matter of reviewing and applying a patch,
> > that
> > > shouldn’t be too hard.
> > >
> > > Dan
> > >
> > >
> > >
> > >
> > > > ThiruOn Thursday, 17 January, 2019, 6:51:39 AM IST, Brian
> Lachniet
> > <
> > > blachn...@gmail.com> wrote:
> > > >
> > > > I'd really like to get the changes to deploy C# NuGet packages in (
> > > > https://github.com/apache/avro/pull/428). Other than that, I think
> > > anything
> > > > else in the C# realm can wait for later releases.
> > > >
> > > > On Wed, Jan 16, 2019, 1:12 PM Daniel Kulp  > > >
> > > >> Just a quick question:
> > > >>
> > > >> What’s the status of the things people are working for 1.9?I
> think
> > > >> we’re getting really close to having something that would be a good
> > 1.9
> > > >> release.  We’ve accomplished a LOT with well over 100 PR’s merged
> and
> > > tons
> > > >> of JIRA’s closed and such and I’d like to get a release out.  Can
> > > anything
> > > >> left be postponed to 1.10 or 1.9.1?
> > > >>
> > > >> Thanks!
> > > >>
> > > >> --
> > > >> Daniel Kulp
> > > >> dk...@apache.org  -
> http://dankulp.com/blog
> > <
> > > >> http://dankulp.com/blog>
> > > >> Talend Community Coder - http://talend.com <
> http://coders.talend.com/
> > >
> > >
> > > --
> > > Daniel Kulp
> > > dk...@apache.org  - http://dankulp.com/blog <
> > > http://dankulp.com/blog>
> > > Talend Community Coder - http://talend.com 
> > >
> >
>


-- 

[image: 51b630b05e01a6d5134ccfd520f547c4.png]

Brian Lachniet

Software Engineer

E: blachn...@gmail.com | blachniet.com 

 

[jira] [Updated] (AVRO-1381) Publish C# artifacts to NuGet

[Brian Lachniet (JIRA)]

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

Brian Lachniet updated AVRO-1381:
-
Release Note: Configured C# project to generate NuGet packages for 
deploying to nuget.org.
  Status: Patch Available  (was: Open)

Patch available in GitHub [PR #428|https://github.com/apache/avro/pull/428]

> Publish C# artifacts to NuGet
> -
>
> Key: AVRO-1381
> URL: https://issues.apache.org/jira/browse/AVRO-1381
> Project: Apache Avro
>  Issue Type: New Feature
>  Components: csharp
>Affects Versions: 1.7.5
>Reporter: Mark Lamley
>Assignee: Brian Lachniet
>Priority: Major
> Fix For: 1.9.0
>
>
> Currently referencing Avro requires manually downloading, compiling and 
> referencing the compiled library. It would be nice to simply reference the 
> compiled library from http://www.nuget.org/ instead.



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

Jenkins build is back to normal : AvroJava #589

[Apache Jenkins Server]

See 

[jira] [Commented] (AVRO-2238) Update Docker image from java to openjdk

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748256#comment-16748256
 ] 

Hudson commented on AVRO-2238:
--

SUCCESS: Integrated in Jenkins build AvroJava #589 (See 
[https://builds.apache.org/job/AvroJava/589/])
AVRO-2238 Update Dockerfile base image from java to openjdk Fix the PHP 
(iemejia: 
[https://github.com/apache/avro/commit/5896f1a1bdcbc2f7450b09b1dbbdeb4ad0cb13b6])
* (edit) lang/java/ipc/src/test/java/org/apache/avro/TestBulkData.java
* (edit) lang/js/lib/utils.js
* (edit) BUILD.md
* (edit) share/test/interop/bin/test_rpc_interop.sh
* (edit) lang/perl/t/04_datafile.t
* (edit) share/docker/Dockerfile
* (edit) lang/java/tools/src/main/java/org/apache/avro/tool/RpcSendTool.java
* (edit) lang/php/test/SchemaTest.php
* (edit) lang/ruby/test/tool.rb


> Update Docker image from java to openjdk
> 
>
> Key: AVRO-2238
> URL: https://issues.apache.org/jira/browse/AVRO-2238
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: docker
>Reporter: Fokko Driesprong
>Assignee: Fokko Driesprong
>Priority: Major
> Fix For: 1.9.0
>
>
> Currently the docker image to run the tests is still using java which is 
> deprecated: https://hub.docker.com/_/java/
> Therefore we should move to openjdk (https://hub.docker.com/_/openjdk/). 
> Starting with version 8, and also adding 10 and 11 to it to make sure that 
> Avro is compatible with future version of Java.



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

[jira] [Resolved] (AVRO-2238) Update Docker image from java to openjdk

[JIRA]

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

Ismaël Mejía resolved AVRO-2238.

   Resolution: Fixed
Fix Version/s: 1.9.0

> Update Docker image from java to openjdk
> 
>
> Key: AVRO-2238
> URL: https://issues.apache.org/jira/browse/AVRO-2238
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: docker
>Reporter: Fokko Driesprong
>Assignee: Fokko Driesprong
>Priority: Major
> Fix For: 1.9.0
>
>
> Currently the docker image to run the tests is still using java which is 
> deprecated: https://hub.docker.com/_/java/
> Therefore we should move to openjdk (https://hub.docker.com/_/openjdk/). 
> Starting with version 8, and also adding 10 and 11 to it to make sure that 
> Avro is compatible with future version of Java.



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

[jira] [Commented] (AVRO-2238) Update Docker image from java to openjdk

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748247#comment-16748247
 ] 

ASF subversion and git services commented on AVRO-2238:
---

Commit 5896f1a1bdcbc2f7450b09b1dbbdeb4ad0cb13b6 in avro's branch 
refs/heads/master from Fokko Driesprong
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=5896f1a ]

AVRO-2238 Update Dockerfile base image from java to openjdk
Fix the PHP error due increased json_decode strictness
with PHP 5.6

For more information:
http://php.net/manual/en/migration56.incompatible.php#migration56.incompatible.json-decode

Changed the import of Perl to first do system imports, and then Avro imports

Updated Build,md with the latest versions which are also used in the CI

Removed the explicit stopping of the Ruby server after the first request,
because it would throw an error on the Java client


> Update Docker image from java to openjdk
> 
>
> Key: AVRO-2238
> URL: https://issues.apache.org/jira/browse/AVRO-2238
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: docker
>Reporter: Fokko Driesprong
>Assignee: Fokko Driesprong
>Priority: Major
>
> Currently the docker image to run the tests is still using java which is 
> deprecated: https://hub.docker.com/_/java/
> Therefore we should move to openjdk (https://hub.docker.com/_/openjdk/). 
> Starting with version 8, and also adding 10 and 11 to it to make sure that 
> Avro is compatible with future version of Java.



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

Re: Status of 1.9....

[Driesprong, Fokko]

Brian, I recently added you as a contributor to the Jira. Could you try
again to assign the ticket?

I'm happy to help with the 1.9 release.

Cheers, Fokko

Op vr 18 jan. 2019 om 00:10 schreef Brian Lachniet :

> It appears that I don't have permissions to edit or assign issues to
> myself. Is that something I should have permissions for, or should I ask
> someone to assign specific issues to me?
>
> On Thu, Jan 17, 2019, 8:19 AM Daniel Kulp 
> >
> >
> > > On Jan 16, 2019, at 9:29 PM, Thiruvalluvan MG
> 
> > wrote:
> > >
> > > To get a sense of what needs to be done, can you please review the
> > pending issues for 1.9.0? According to JIRA, there are 43 unresolved
> issues
> > with Fix Version 1.9.0. Issue Navigator - ASF JIRA
> > >
> >
> > https://issues.apache.org/jira/projects/AVRO/versions/1294
> >
> >
> >
> > > Please add the fix version to the issues outside the list that should
> be
> > resolved for the release and remove the fix version if some of the issues
> > in the list need not be or cannot be resolved for 1.9.0. Also if you
> intend
> > to resolve it in the near future, please assign the issues to yourself.
> > Thank you.
> > > I've done the exercise for C++. There are three C++ issues unresolved
> > and I'll address them before the weekend.
> > > Thank you,
> >
> > Well, the main point is that not all of those 43 issues are going to get
> > done for 1.9.  If someone is not actively working on it to be done in the
> > next week or so, I’m going to remove them from 1.9.  I don’t see the
> point
> > in holding up a release that fixes 180 issues waiting for stuff that may
> or
> > may not ever get complete.   Thus, everyone, please take a look at the
> list
> > and if you aren’t working on something that is assigned to you, remove it
> > from 1.9.
> >
> > That said, I’ll try and take a look at the 17 that have “Patch
> > Available”.   If it’s just a matter of reviewing and applying a patch,
> that
> > shouldn’t be too hard.
> >
> > Dan
> >
> >
> >
> >
> > > ThiruOn Thursday, 17 January, 2019, 6:51:39 AM IST, Brian Lachniet
> <
> > blachn...@gmail.com> wrote:
> > >
> > > I'd really like to get the changes to deploy C# NuGet packages in (
> > > https://github.com/apache/avro/pull/428). Other than that, I think
> > anything
> > > else in the C# realm can wait for later releases.
> > >
> > > On Wed, Jan 16, 2019, 1:12 PM Daniel Kulp  > >
> > >> Just a quick question:
> > >>
> > >> What’s the status of the things people are working for 1.9?I think
> > >> we’re getting really close to having something that would be a good
> 1.9
> > >> release.  We’ve accomplished a LOT with well over 100 PR’s merged and
> > tons
> > >> of JIRA’s closed and such and I’d like to get a release out.  Can
> > anything
> > >> left be postponed to 1.10 or 1.9.1?
> > >>
> > >> Thanks!
> > >>
> > >> --
> > >> Daniel Kulp
> > >> dk...@apache.org  - http://dankulp.com/blog
> <
> > >> http://dankulp.com/blog>
> > >> Talend Community Coder - http://talend.com  >
> >
> > --
> > Daniel Kulp
> > dk...@apache.org  - http://dankulp.com/blog <
> > http://dankulp.com/blog>
> > Talend Community Coder - http://talend.com 
> >
>