You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juneau.apache.org by James Bognar <ja...@apache.org> on 2017/09/18 00:54:30 UTC
[VOTE] Release Apache Juneau 6.4.0-incubating RC2
I am pleased to be calling this vote for the source release of Apache
Juneau 6.4.0-incubating RC2.
This includes some fixes for bugs found in RC1 and some packaging changes
for the example and template projects.
The list of new features can be found here:
http://juneau.incubator.apache.org/site/apidocs/overview-summary.html#6.4.0
The binaries are available at:
https://dist.apache.org/repos/dist/dev/incubator/juneau/binaries/juneau-6.4.0-incubating-RC2/
The release candidate to be voted over is available at:
https://dist.apache.org/repos/dist/dev/incubator/juneau/source/juneau-6.4.0-incubating-RC2/
SHA-1 checksums:
aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
0-incubating-src.zip
c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
0-incubating-bin.zip
MD5 checksums:
e6ef05085093a5235cb9665c65a778fb apache-juneau-6.4.0-incubating-src.zip
4e96d5047c0e9f03f0def2d017521f13 apache-juneau-6.4.0-incubating-bin.zip
Build the release candidate using:
mvn clean install
The release candidate is signed with a GPG key available at:
https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS
A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachejuneau-1016/
The Git commit for this release is...
*https://git-wip-us.apache.org/repos/asf?p=incubator-juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
<https://git-wip-us.apache.org/repos/asf?p=incubator-juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37>*
Please vote on releasing this package as:
Apache Juneau 6.4.0-incubating
This vote will be open until 20-Sep-2017 9:00pm EST and passes if a
majority of at least three +1 Apache Juneau PPMC votes are cast.
[ ] +1 Release this package
[ ] 0 I don't feel strongly about it, but don't object
[ ] -1 Do not release this package because...
Anyone can participate in testing and voting, not just committers, please
feel free to try out the release candidate and provide your votes.
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by Steve Blackmon <sb...@apache.org>.
+1 (binding)
- confirmed SUCCESS from mvn clean install
- checked md5 and shasum for bin and src release artifacts
- verified gpg signatures
Steve
Sent from Astro <https://www.helloastro.com> for Mac
On Sep 17, 2017 at 7:54 PM, James Bognar <ja...@apache.org> wrote:
I am pleased to be calling this vote for the source release of Apache
Juneau 6.4.0-incubating RC2.
This includes some fixes for bugs found in RC1 and some packaging changes
for the example and template projects.
The list of new features can be found here:
http://juneau.incubator.apache.org/site/apidocs/overview-summary.html#6.4.0
The binaries are available at:
https://dist.apache.org/repos/dist/dev/incubator/juneau/binaries/juneau-6.4.0-incubating-RC2/
The release candidate to be voted over is available at:
https://dist.apache.org/repos/dist/dev/incubator/juneau/source/juneau-6.4.0-incubating-RC2/
SHA-1 checksums:
aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
0-incubating-src.zip
c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
0-incubating-bin.zip
MD5 checksums:
e6ef05085093a5235cb9665c65a778fb apache-juneau-6.4.0-incubating-src.zip
4e96d5047c0e9f03f0def2d017521f13 apache-juneau-6.4.0-incubating-bin.zip
Build the release candidate using:
mvn clean install
The release candidate is signed with a GPG key available at:
https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS
A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachejuneau-1016/
The Git commit for this release is...
*
https://git-wip-us.apache.org/repos/asf?p=incubator-juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
<
https://git-wip-us.apache.org/repos/asf?p=incubator-juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
>*
Please vote on releasing this package as:
Apache Juneau 6.4.0-incubating
This vote will be open until 20-Sep-2017 9:00pm EST and passes if a
majority of at least three +1 Apache Juneau PPMC votes are cast.
[ ] +1 Release this package
[ ] 0 I don't feel strongly about it, but don't object
[ ] -1 Do not release this package because...
Anyone can participate in testing and voting, not just committers, please
feel free to try out the release candidate and provide your votes.
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by Steve Blackmon <sb...@apache.org>.
Perusing
https://cwiki.apache.org/confluence/display/INFRA/Jenkins+node+labels
I see that that there are several generic windows server 12 nodes available
to builds.apache.org under the ‘Windows’ label.
We could probably configure jenkins to build on linux and windows targets
to help isolate the issue if it’s not as simple as line endings.
Steve
On Sep 21, 2017 at 7:55 AM, James Bognar <ja...@apache.org> wrote:
Hi David,
I don't have a Windows machine anymore :-(
It looks like a test issue. Is it only RDF tests that are failing?
Can you find line 484 in org.apache.juneau.TestUtils in juneau-core-tests...
String[] e = expected.trim().split("\n"), a = actual.trim().split("\n");
...and change it to this?...
String[] e = expected.trim().split("[\r\n]+"), a = actual.trim().split(
"[\r\n]+");
Background on this method: Since Jena does not guarantee the order of
entries in the generated RDF (it's pretty much random), it's difficult to
do simple comparison validation. So instead, we sort the expected and
actual lines and then check for comparison. It's not perfect (XML
attribute order can also be random), but generally good enough for what
we're testing.
On Thu, Sep 21, 2017 at 5:52 AM, David Goddard <go...@acm.org> wrote:
Thanks.
I'm seeting a whole load of test failures in juneau-core parsing (every
round trip test is failing for me). For example:
ByteArrayBase64SwapComboTest>ComboRoundTripTest.g32_parseRdf
XmlR:701->ComboRoundTripTest.testParse:205 ByteArray2d/parseRdfXmlR
parse-normal failed expected:<<rdf:RDF>[
<rdf:Seq>
<rdf:li>AQID</rdf:li>
<rdf:li>BAUG</rdf:li>
<rdf:li rdf:resource='http://www.w3.org/1999/02/22-rdf-syntax-ns#nil'/
</rdf:Seq>
</rdf:RDF>]
but was:<<rdf:RDF>[
<rdf:Seq>
<rdf:li>AQID</rdf:li>
<rdf:li>BAUG</rdf:li>
<rdf:li rdf:resource='http://www.w3.org/1999/02/22-rdf-syntax-ns#nil'/
</rdf:Seq>
</rdf:RDF>
]
The only consistent difference I see is that the final closing square
bracket is appearing on a new line. Perhaps this is a character encoding
issue (although I wouldn't rule out user error) - these tests fail on a
Windows platform, but work fine on a Mac.
David
On 20/09/2017 15:39, James Bognar wrote:
Indeed they are.
I've fixed them in Git. Thanks David!
On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <go...@acm.org> wrote:
I'm seeing a couple of issues with the Eclipse project names when
importing a fresh clone into a workspace.
juneau-microservice/.project has <name>juneau-rest</name>
juneau-doc/.project has <name>juneau-marshall</name>
I'm assuming these are copy/paste errors arising from the restructuring.
David
On 19/09/2017 18:26, Charles Mims wrote:
+1, with intermittent test failures in Apache Juneau Microservice Tests
MD5 (apache-juneau-6.4.0-incubating-src.zip) =
e6ef05085093a5235cb9665c65a778fb
For me it failed on the 1st and 2nd try, passed on the 3rd.
On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <ja...@apache.org>
wrote:
** At this time, I have met “Broken Pipe” issue too. I think we need to
handle this problem soon.
Darn.
I'm thinking it must be an issue with Jetty since we just upgraded it.
From the Jetty side, the connection is open waiting for data, but
that's
all I know.
I'll have to figure out how to use Fiddler and do some low-level
debugging. It's really hard to reproduce though :-(
On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <yi...@gmail.com>
wrote:
+1
SHA1, MD5 Checksum OK
Maven Build OK
** At this time, I have met “Broken Pipe” issue too. I think we need
to
handle this problem soon.
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Juneau (incubating) ......................... SUCCESS [
10.521 s]
[INFO] Apache Juneau - Core APIs .......................... SUCCESS [
0.737 s]
[INFO] Apache Juneau Marshall ............................. SUCCESS [
45.444 s]
[INFO] Apache Juneau Marshal RDF .......................... SUCCESS [
3.558 s]
[INFO] Apache Juneau Data Transfer Objects ................ SUCCESS [
6.813 s]
[INFO] Apache Juneau Core ................................. SUCCESS [
1.025 s]
[INFO] Apache Juneau Config File API ...................... SUCCESS [
1.928 s]
[INFO] Apache Juneau Core Tests ........................... SUCCESS
[01:04
min]
[INFO] Apache Juneau - REST APIs .......................... SUCCESS [
0.080 s]
[INFO] Apache Juneau REST Servlet API ..................... SUCCESS [
2.331 s]
[INFO] Apache Juneau REST JAX/RS API ...................... SUCCESS [
0.476 s]
[INFO] Apache Juneau REST Client API ...................... SUCCESS [
1.005 s]
[INFO] Apache Juneau - Microservice APIs .................. SUCCESS [
0.068 s]
[INFO] Apache Juneau Microservice Server .................. SUCCESS [
1.588 s]
[INFO] Apache Juneau Microservice Template ................ SUCCESS [
1.243 s]
[INFO] Apache Juneau - Examples ........................... SUCCESS [
0.183 s]
[INFO] Apache Juneau REST Examples ........................ SUCCESS [
8.512 s]
[INFO] Apache Juneau Microservice Tests ................... SUCCESS [
24.522 s]
[INFO] Apache Juneau Core Examples ........................ SUCCESS [
0.287 s]
[INFO] Apache Juneau Javadocs ............................. SUCCESS [
0.617 s]
[INFO] Apache Juneau - Release Engineering ................ SUCCESS [
0.040 s]
[INFO] Apache Juneau UberJar .............................. SUCCESS [
1.008 s]
[INFO] Apache Juneau Distribution ......................... SUCCESS [
0.768 s]
[INFO] ------------------------------------------------------------
------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------
------------
[INFO] Total time: 03:01 min
[INFO] Finished at: 2017-09-19T20:11:43+09:00
[INFO] Final Memory: 87M/773M
[INFO] ------------------------------------------------------------
------------
Raphi D Lee, yidonguk@gmail.com
2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org> 작성:
I am pleased to be calling this vote for the source release of Apache
Juneau 6.4.0-incubating RC2.
This includes some fixes for bugs found in RC1 and some packaging
changes
for the example and template projects.
The list of new features can be found here:
http://juneau.incubator.apache.org/site/apidocs/
overview-summary.html#6.4.0
The binaries are available at:
https://dist.apache.org/repos/dist/dev/incubator/juneau/
binaries/juneau-6.4.0-incubating-RC2/
The release candidate to be voted over is available at:
https://dist.apache.org/repos/dist/dev/incubator/juneau/
source/juneau-6.4.0-incubating-RC2/
SHA-1 checksums:
aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
0-incubating-src.zip
c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
0-incubating-bin.zip
MD5 checksums:
e6ef05085093a5235cb9665c65a778fb apache-juneau-6.4.0-incubating
-src.zip
4e96d5047c0e9f03f0def2d017521f13 apache-juneau-6.4.0-incubating
-bin.zip
Build the release candidate using:
mvn clean install
The release candidate is signed with a GPG key available at:
https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS
A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapache
juneau-1016/
The Git commit for this release is...
*https://git-wip-us.apache.org/repos/asf?p=incubator-
juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
<https://git-wip-us.apache.org/repos/asf?p=incubator-
juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37>*
Please vote on releasing this package as:
Apache Juneau 6.4.0-incubating
This vote will be open until 20-Sep-2017 9:00pm EST and passes if a
majority of at least three +1 Apache Juneau PPMC votes are cast.
[ ] +1 Release this package
[ ] 0 I don't feel strongly about it, but don't object
[ ] -1 Do not release this package because...
Anyone can participate in testing and voting, not just committers,
please
feel free to try out the release candidate and provide your votes.
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by James Bognar <ja...@apache.org>.
I'd like to cancel RC2 and try for an RC3 after we resolve David's latest
issue in BeanConfigTest.
I've added significant debugging support to the microservice to help us
track down the HTTP call issues being reported by some of the
contributors....
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=73639856
It's worthwhile to get these into 6.4.0.
On Sun, Sep 24, 2017 at 1:40 PM, James Bognar <ja...@apache.org>
wrote:
> Hi David,
>
> Is that really occurring on line 473? Could you catch the exception and
> print a longer stack trace?
>
> Thanks!
>
> On Sun, Sep 24, 2017 at 4:31 AM, David Goddard <go...@acm.org> wrote:
>
>> Hi,
>>
>> Yes, this code now works:
>>
>> @Test
>> public void test() {
>> BeanSession session = ps.getBeanContext()
>> .createSession(new BeanSessionArgs(null, sessionLocale,
>> sessionTimeZone, null));
>> String actual = session.convertToType(calendar, String.class);
>> if (expected.indexOf('(') == -1)
>> // Fix JVM-specific formatting difference
>> actual.replaceAll(" \\([^\\)]+\\)",
>> "").replaceAll("\\([^\\)]+\\) ", "");
>> assertEquals(expected, actual);
>> Object c2 = session.convertToType(actual, calendar.getClass());
>> String actual2 = session.convertToType(c2, String.class);
>> if (expected.indexOf('(') == -1)
>> // Fix JVM-specific formatting difference
>> actual2 = actual2.replaceAll("\\([^\\)]+\\) ", "");
>> assertEquals(expected, actual2);
>> }
>>
>> However, still one more error in my Windows environment though :(
>>
>> #############################
>> Tests run: 11, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.031
>> sec <<< FAILURE! - in org.apache.juneau.BeanConfigTest
>> testProxyHandler(org.apache.juneau.BeanConfigTest) Time elapsed: 0 sec
>> <<< ERROR!
>> org.apache.juneau.BeanRuntimeException: interface
>> org.apache.juneau.BeanConfigTest$A is not visible from class loader
>> at org.apache.juneau.BeanConfigTest.testProxyHandler(BeanConfig
>> Test.java:473)
>> Caused by: java.lang.IllegalArgumentException: interface
>> org.apache.juneau.BeanConfigTest$A is not visible from class loader
>> at org.apache.juneau.BeanConfigTest.testProxyHandler(BeanConfig
>> Test.java:473)
>> #############################
>>
>> I'm wondering if this is an issue specific to my setup. When I have a
>> chance (I am travelling at the moment), I'll set up an Oracle JVM in my
>> Windows test environment and try a build with that.
>>
>> David
>>
>> On 23/09/2017 21:35, James Bognar wrote:
>>
>>> Hi David,
>>>
>>> How about this?
>>> if (expected.indexOf('(') == -1)
>>> actual.replaceAll(" \\([^\\)]+\\)", "").replaceAll("\\([^\\)]+\\) ",
>>> "");
>>>
>>>
>>> On Fri, Sep 22, 2017 at 3:08 PM, David Goddard <go...@acm.org> wrote:
>>>
>>> Most things are in some way IBM's fault :)
>>>>
>>>> Trying both variants of your fix gives similar results. Better in both
>>>> cases, but not quite there. Details below.
>>>>
>>>> It looks to me on a quick read that those cases that now fail are
>>>> failing
>>>> because they *do* expect a value between the parentheses, and of course
>>>> the
>>>> fix strips that out. For example, here's test 205:
>>>>
>>>> { "205", testDate, CalendarSwap.DateTimeLong.class, "en_UK",
>>>> Locale.KOREA, null, null, "2001년 3월 3일 (토) 오전 10시 11분 12초" },
>>>>
>>>> I guess we could bend the test a little further by conditionally only
>>>> stripping out the parenthetical content if the expected value doesn't
>>>> contain values in parentheses itself, but that be regarded as a fix too
>>>> far...
>>>>
>>>> #######################
>>>>
>>>> actual = actual.replaceAll("\\([^\\)]+\\) ", "");
>>>> actual2 = actual2.replaceAll("\\([^\\)]+\\) ", "");
>>>>
>>>> ...leads to:
>>>>
>>>> Tests run: 460, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 19.485
>>>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
>>>> test[205](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>> elapsed:
>>>> 0.004 sec <<< FAILURE!
>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
>>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>>>> at org.apache.juneau.transforms.L
>>>> ocalizedDatesTest.test(Localiz
>>>> edDatesTest.java:660)
>>>>
>>>> test[435](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>> elapsed:
>>>> 0.001 sec <<< FAILURE!
>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
>>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>>>> at org.apache.juneau.transforms.L
>>>> ocalizedDatesTest.test(Localiz
>>>> edDatesTest.java:660)
>>>>
>>>> With the different location for the space in the regexp, I get a longer
>>>> list of failures:
>>>>
>>>> #######################
>>>>
>>>> actual = actual.replaceAll(" \\([^\\)]+\\)", "");
>>>> actual2 = actual2.replaceAll(" \\([^\\)]+\\)", "");
>>>>
>>>> ... leads to:
>>>>
>>>> Running org.apache.juneau.transforms.LocalizedDatesTest
>>>> Tests run: 460, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 0.189
>>>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
>>>> test[125](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>> elapsed:
>>>> 0.003 sec <<< FAILURE!
>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3?[ (?)]> but was:<2001?
>>>> 3? 3?[]>
>>>> at org.apache.juneau.transforms.L
>>>> ocalizedDatesTest.test(Localiz
>>>> edDatesTest.java:660)
>>>>
>>>> test[205](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>> elapsed:
>>>> 0 sec <<< FAILURE!
>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
>>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>>>> at org.apache.juneau.transforms.L
>>>> ocalizedDatesTest.test(Localiz
>>>> edDatesTest.java:660)
>>>>
>>>> test[355](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>> elapsed:
>>>> 0 sec <<< FAILURE!
>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3?[ (?)]> but was:<2001?
>>>> 3? 3?[]>
>>>> at org.apache.juneau.transforms.L
>>>> ocalizedDatesTest.test(Localiz
>>>> edDatesTest.java:660)
>>>>
>>>> test[435](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>> elapsed:
>>>> 0.001 sec <<< FAILURE!
>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
>>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>>>> at org.apache.juneau.transforms.L
>>>> ocalizedDatesTest.test(Localiz
>>>> edDatesTest.java:660)
>>>>
>>>> #######################
>>>>
>>>>
>>>>
>>>>
>>>> On 22/09/2017 00:05, James Bognar wrote:
>>>>
>>>> Ah...so we can blame IBM :-)
>>>>>
>>>>> Can you see if swapping the location of the space in the regular
>>>>> expressions fixes all the tests?
>>>>> actual = actual.replaceAll(" \\([^\\)]+\\)", "");
>>>>>
>>>>> On Thu, Sep 21, 2017 at 6:01 PM, David Goddard <go...@acm.org>
>>>>> wrote:
>>>>>
>>>>> Just to add:
>>>>>
>>>>>>
>>>>>> Maybe it's JVM vendor-specific behavior?
>>>>>>
>>>>>>>
>>>>>>>
>>>>>> Yes, I've now tested again after changing from an IBM JRE to an Oracle
>>>>>> JRE
>>>>>> - this resolves the problem. It looks like this is specific to the
>>>>>> IBM
>>>>>> JRE
>>>>>> then. My Mac testing was done with an Oracle JRE, so I think this is
>>>>>> probably JVM-specific rather than OS-specific.
>>>>>>
>>>>>>
>>>>>> On 21/09/2017 23:46, David Goddard wrote:
>>>>>>
>>>>>> Actual text is:
>>>>>>
>>>>>>>
>>>>>>> 2001年3月3日 (土曜日)
>>>>>>> (I've attached a copy as a text file also)
>>>>>>>
>>>>>>> In this case, I it looks like the value between the parenthesis is
>>>>>>> the
>>>>>>> day name, "Saturday". So the expected value is just the date
>>>>>>> (2001年3月
>>>>>>> 3日),
>>>>>>> but the day is being added in the process.
>>>>>>>
>>>>>>>
>>>>>>> On 21/09/2017 22:45, James Bognar wrote:
>>>>>>>
>>>>>>> Interesting. So the behavior of...
>>>>>>>
>>>>>>>>
>>>>>>>> DateFormat.getDateInstance(DateFormat.FULL, locale).format(date);
>>>>>>>> DateFormat.getDateTimeInstance(DateFormat.FULL, DateFormat.FULL,
>>>>>>>> locale
>>>>>>>> ).format(date);
>>>>>>>>
>>>>>>>> ...returns different formats depending on the OS. Lovely.
>>>>>>>>
>>>>>>>> Maybe it's JVM vendor-specific behavior?
>>>>>>>>
>>>>>>>> I'm curious to know what's in those parentheses...
>>>>>>>> 2001?3?3? [*(???)* ]10?11?12? GMT
>>>>>>>>
>>>>>>>> Might give me something to google for.
>>>>>>>>
>>>>>>>> It's technically a test-only issue. We can probably 'fix' the
>>>>>>>> testcase
>>>>>>>> by
>>>>>>>> just stripping out the formatting difference...
>>>>>>>>
>>>>>>>> @Test
>>>>>>>> public void test() {
>>>>>>>> BeanSession session = ps.getBeanContext().createSession(new
>>>>>>>> BeanSessionArgs(null, sessionLocale, sessionTimeZone, null));
>>>>>>>> String actual = session.convertToType(calendar, String.class);
>>>>>>>> *actual = actual.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>>>>>>>> Windows-specific
>>>>>>>> formatting difference*
>>>>>>>> assertEquals(expected, actual);
>>>>>>>> Object c2 = session.convertToType(actual, calendar.getClass());
>>>>>>>> String actual2 = session.convertToType(c2, String.class);
>>>>>>>> *actual2 = actual2.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>>>>>>>> Windows-specific formatting difference*
>>>>>>>> assertEquals(expected, actual2);
>>>>>>>> }
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Sep 21, 2017 at 3:11 PM, David Goddard <go...@acm.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>>
>>>>>>>>> Yes, that fixed it, thanks. It also still tests OK on my Mac after
>>>>>>>>> the
>>>>>>>>> change.
>>>>>>>>>
>>>>>>>>> I'm now running into some further test issues, also on Windows
>>>>>>>>> only.
>>>>>>>>>
>>>>>>>>> ########################
>>>>>>>>>
>>>>>>>>> Tests run: 460, Failures: 16, Errors: 0, Skipped: 0, Time elapsed:
>>>>>>>>> 0.247
>>>>>>>>> sec <<< FAILURE! - in org.apache.juneau.transforms.L
>>>>>>>>> ocalizedDatesTest
>>>>>>>>> test[111](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>>>>> elapsed:
>>>>>>>>> 0.015 sec <<< FAILURE!
>>>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3?[]> but
>>>>>>>>> was:<2001?3?3?[
>>>>>>>>> (???)]>
>>>>>>>>> at org.apache.juneau.transforms.L
>>>>>>>>> ocalizedDatesTest.test(Localiz
>>>>>>>>> edDatesTest.java:645)
>>>>>>>>>
>>>>>>>>> [...]
>>>>>>>>> test[423](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>>>>> elapsed:
>>>>>>>>> 0 sec <<< FAILURE!
>>>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT>
>>>>>>>>> but
>>>>>>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>>>>>>>> at org.apache.juneau.transforms.L
>>>>>>>>> ocalizedDatesTest.test(Localiz
>>>>>>>>> edDatesTest.java:645)
>>>>>>>>>
>>>>>>>>> test[424](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>>>>> elapsed:
>>>>>>>>> 0 sec <<< FAILURE!
>>>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT>
>>>>>>>>> but
>>>>>>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>>>>>>>> at org.apache.juneau.transforms.L
>>>>>>>>> ocalizedDatesTest.test(Localiz
>>>>>>>>> edDatesTest.java:645)
>>>>>>>>>
>>>>>>>>> ########################
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> These are specific to date swap tests in Japanese & Korean:
>>>>>>>>>
>>>>>>>>> { "421", testDate.getTime(), DateSwap.DateTimeFull.class, "ja_JP",
>>>>>>>>> null,
>>>>>>>>> null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>>>> { "422", testDate.getTime(), DateSwap.DateTimeFull.class,
>>>>>>>>> Locale.JAPAN,
>>>>>>>>> null, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>>>> { "423", testDate.getTime(), DateSwap.DateTimeFull.class, null,
>>>>>>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>>>> { "424", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>>>>>>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>>>> { "425", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>>>>>>>>> Locale.KOREA, null, null, "2001ë…„ 3ì›” 3ì�¼ í† ìš”ì�¼ ì˜¤ì „ 10ì‹œ
>>>>>>>>> 11분
>>>>>>>>> 12ì´ˆ GMT" },
>>>>>>>>> etc.
>>>>>>>>>
>>>>>>>>> All the date swaps where the test date contains Japanese or Korean
>>>>>>>>> characters in the date part fail in this way. I initially thought
>>>>>>>>> it
>>>>>>>>> was
>>>>>>>>> the code page of the file, but I've changed to UTF-8 from the
>>>>>>>>> default
>>>>>>>>> and
>>>>>>>>> this didn't resolve this for me. Again, this is specific to my
>>>>>>>>> Windows
>>>>>>>>> platform - all is fine on Mac.
>>>>>>>>>
>>>>>>>>> Given that this is a build test error, and specific to one platform
>>>>>>>>> (and
>>>>>>>>> possibly one machine), I'm not sure that it is a fatal problem for
>>>>>>>>> the
>>>>>>>>> release.
>>>>>>>>>
>>>>>>>>> David
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 21/09/2017 14:55, James Bognar wrote:
>>>>>>>>>
>>>>>>>>> Hi David,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> I don't have a Windows machine anymore :-(
>>>>>>>>>>
>>>>>>>>>> It looks like a test issue. Is it only RDF tests that are
>>>>>>>>>> failing?
>>>>>>>>>>
>>>>>>>>>> Can you find line 484 in org.apache.juneau.TestUtils in
>>>>>>>>>> juneau-core-tests...
>>>>>>>>>>
>>>>>>>>>> String[] e = expected.trim().split("\n"), a =
>>>>>>>>>> actual.trim().split("\n");
>>>>>>>>>>
>>>>>>>>>> ...and change it to this?...
>>>>>>>>>>
>>>>>>>>>> String[] e = expected.trim().split("[\r\n]+"), a =
>>>>>>>>>> actual.trim().split(
>>>>>>>>>> "[\r\n]+");
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Background on this method: Since Jena does not guarantee the
>>>>>>>>>> order
>>>>>>>>>> of
>>>>>>>>>> entries in the generated RDF (it's pretty much random), it's
>>>>>>>>>> difficult
>>>>>>>>>> to
>>>>>>>>>> do simple comparison validation. So instead, we sort the expected
>>>>>>>>>> and
>>>>>>>>>> actual lines and then check for comparison. It's not perfect (XML
>>>>>>>>>> attribute order can also be random), but generally good enough for
>>>>>>>>>> what
>>>>>>>>>> we're testing.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, Sep 21, 2017 at 5:52 AM, David Goddard <go...@acm.org>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Thanks.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I'm seeting a whole load of test failures in juneau-core parsing
>>>>>>>>>>> (every
>>>>>>>>>>> round trip test is failing for me). For example:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ByteArrayBase64SwapComboTest>ComboRoundTripTest.g32_parseRdf
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> XmlR:701->ComboRoundTripTest.testParse:205
>>>>>>>>>>>>
>>>>>>>>>>> ByteArray2d/parseRdfXmlR
>>>>>>>>>>> parse-normal failed expected:<<rdf:RDF>[
>>>>>>>>>>> <rdf:Seq>
>>>>>>>>>>> <rdf:li>AQID</rdf:li>
>>>>>>>>>>> <rdf:li>BAUG</rdf:li>
>>>>>>>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>>>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> </rdf:Seq>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> </rdf:RDF>]
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> but was:<<rdf:RDF>[
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> <rdf:Seq>
>>>>>>>>>>>>
>>>>>>>>>>>> <rdf:li>AQID</rdf:li>
>>>>>>>>>>> <rdf:li>BAUG</rdf:li>
>>>>>>>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>>>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> </rdf:Seq>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> </rdf:RDF>
>>>>>>>>>>>>
>>>>>>>>>>> ]
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The only consistent difference I see is that the final closing
>>>>>>>>>>>> square
>>>>>>>>>>>>
>>>>>>>>>>>> bracket is appearing on a new line. Perhaps this is a character
>>>>>>>>>>> encoding
>>>>>>>>>>> issue (although I wouldn't rule out user error) - these tests
>>>>>>>>>>> fail
>>>>>>>>>>> on
>>>>>>>>>>> a
>>>>>>>>>>> Windows platform, but work fine on a Mac.
>>>>>>>>>>>
>>>>>>>>>>> David
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 20/09/2017 15:39, James Bognar wrote:
>>>>>>>>>>>
>>>>>>>>>>> Indeed they are.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I've fixed them in Git. Thanks David!
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <goddard@acm.org
>>>>>>>>>>>> >
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> I'm seeing a couple of issues with the Eclipse project names
>>>>>>>>>>>> when
>>>>>>>>>>>>
>>>>>>>>>>>> importing a fresh clone into a workspace.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> juneau-microservice/.project has <name>juneau-rest</name>
>>>>>>>>>>>>> juneau-doc/.project has <name>juneau-marshall</name>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I'm assuming these are copy/paste errors arising from the
>>>>>>>>>>>>> restructuring.
>>>>>>>>>>>>>
>>>>>>>>>>>>> David
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 19/09/2017 18:26, Charles Mims wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> +1, with intermittent test failures in Apache Juneau
>>>>>>>>>>>>> Microservice
>>>>>>>>>>>>> Tests
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> MD5 (apache-juneau-6.4.0-incubating-src.zip) =
>>>>>>>>>>>>>
>>>>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>>>>>>>>>> For me it failed on the 1st and 2nd try, passed on the 3rd.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <
>>>>>>>>>>>>>> jamesbognar@apache.org>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think
>>>>>>>>>>>>>> we
>>>>>>>>>>>>>> need
>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> handle this problem soon.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Darn.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I'm thinking it must be an issue with Jetty since we just
>>>>>>>>>>>>>>> upgraded
>>>>>>>>>>>>>>> it.
>>>>>>>>>>>>>>> From the Jetty side, the connection is open waiting for
>>>>>>>>>>>>>>> data,
>>>>>>>>>>>>>>> but
>>>>>>>>>>>>>>> that's
>>>>>>>>>>>>>>> all I know.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I'll have to figure out how to use Fiddler and do some
>>>>>>>>>>>>>>> low-level
>>>>>>>>>>>>>>> debugging. It's really hard to reproduce though :-(
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <
>>>>>>>>>>>>>>> yidonguk@gmail.com
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> SHA1, MD5 Checksum OK
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Maven Build OK
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I
>>>>>>>>>>>>>>>> think we
>>>>>>>>>>>>>>>> need
>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>> handle this problem soon.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [INFO] Reactor Summary:
>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau (incubating) .........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 10.521 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau - Core APIs ..........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.737 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Marshall .............................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 45.444 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Marshal RDF ..........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 3.558 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Data Transfer Objects ................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 6.813 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Core .................................
>>>>>>>>>>>>>>>> SUCCESS [
>>>>>>>>>>>>>>>> 1.025 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Config File API ......................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 1.928 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Core Tests ...........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [01:04
>>>>>>>>>>>>>>>> min]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau - REST APIs ..........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.080 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau REST Servlet API .....................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 2.331 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau REST JAX/RS API ......................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.476 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau REST Client API ......................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 1.005 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau - Microservice APIs ..................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.068 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Server ..................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 1.588 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Template ................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 1.243 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau - Examples ...........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.183 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau REST Examples ........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 8.512 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Tests ...................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 24.522 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Core Examples ........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.287 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Javadocs .............................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.617 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau - Release Engineering ................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.040 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau UberJar ..............................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 1.008 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Distribution .........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.768 s]
>>>>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>>>> ------------
>>>>>>>>>>>>>>>> [INFO] BUILD SUCCESS
>>>>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>>>> ------------
>>>>>>>>>>>>>>>> [INFO] Total time: 03:01 min
>>>>>>>>>>>>>>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>>>>>>>>>>>>>>>> [INFO] Final Memory: 87M/773M
>>>>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>>>> ------------
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Raphi D Lee, yidonguk@gmail.com
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org>
>>>>>>>>>>>>>>>> 작성:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I am pleased to be calling this vote for the source release
>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Apache
>>>>>>>>>>>>>>>>> Juneau 6.4.0-incubating RC2.
>>>>>>>>>>>>>>>>> This includes some fixes for bugs found in RC1 and some
>>>>>>>>>>>>>>>>> packaging
>>>>>>>>>>>>>>>>> changes
>>>>>>>>>>>>>>>>> for the example and template projects.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The list of new features can be found here:
>>>>>>>>>>>>>>>>> http://juneau.incubator.apache.org/site/apidocs/
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> overview-summary.html#6.4.0
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The binaries are available at:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> binaries/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The release candidate to be voted over is available at:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> source/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> SHA-1 checksums:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 0-incubating-src.zip
>>>>>>>>>>>>>>>>> c3d4a1d7c21142a4006876419729d9f0c352203e
>>>>>>>>>>>>>>>>> apache-juneau-6.4.
>>>>>>>>>>>>>>>>> 0-incubating-bin.zip
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> MD5 checksums:
>>>>>>>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>>>>>>>>>>>>> apache-juneau-6.4.0-incubating
>>>>>>>>>>>>>>>>> -src.zip
>>>>>>>>>>>>>>>>> 4e96d5047c0e9f03f0def2d017521f13
>>>>>>>>>>>>>>>>> apache-juneau-6.4.0-incubating
>>>>>>>>>>>>>>>>> -bin.zip
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Build the release candidate using:
>>>>>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The release candidate is signed with a GPG key available
>>>>>>>>>>>>>>>>> at:
>>>>>>>>>>>>>>>>> https://dist.apache.org/repos/
>>>>>>>>>>>>>>>>> dist/release/incubator/juneau/
>>>>>>>>>>>>>>>>> KEYS
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> A staged Maven repository is available for review at:
>>>>>>>>>>>>>>>>> https://repository.apache.org/
>>>>>>>>>>>>>>>>> content/repositories/orgapache
>>>>>>>>>>>>>>>>> juneau-1016/
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The Git commit for this release is...
>>>>>>>>>>>>>>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> juneau.git;a=commit;h=6de99819
>>>>>>>>>>>>>>>>> 3807eeec40e6f297f6b70222552f3b
>>>>>>>>>>>>>>>>> 37
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> juneau.git;a=commit;h=6de99819
>>>>>>>>>>>>>>>> 3807eeec40e6f297f6b70222552f3b
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 37>*
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Please vote on releasing this package as:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Apache Juneau 6.4.0-incubating
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> This vote will be open until 20-Sep-2017 9:00pm EST and
>>>>>>>>>>>>>>>>> passes
>>>>>>>>>>>>>>>>> if a
>>>>>>>>>>>>>>>>> majority of at least three +1 Apache Juneau PPMC votes are
>>>>>>>>>>>>>>>>> cast.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> [ ] +1 Release this package
>>>>>>>>>>>>>>>>> [ ] 0 I don't feel strongly about it, but don't object
>>>>>>>>>>>>>>>>> [ ] -1 Do not release this package because...
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Anyone can participate in testing and voting, not just
>>>>>>>>>>>>>>>>> committers,
>>>>>>>>>>>>>>>>> please
>>>>>>>>>>>>>>>>> feel free to try out the release candidate and provide your
>>>>>>>>>>>>>>>>> votes.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by David Goddard <go...@acm.org>.
Logged as JUNEAU-66 <https://issues.apache.org/jira/browse/JUNEAU-66>. Interestingly I also tested with an Oracle JVM when preparing the JIRA and that also had the same behaviour. I can’t rule out an issue with my Eclipse environment, but I can’t see anything obvious.
> On 26 Sep 2017, at 20:06, James Bognar <ja...@apache.org> wrote:
>
> Thanks David,
>
> The stack trace helps. Can you open a defect for this issue? IMHO, it's
> not serious enough to hold up release. I can fix it in 6.4.1.
>
> On Tue, Sep 26, 2017 at 2:28 PM, David Goddard <go...@acm.org> wrote:
>
>> Hi,
>>
>> Sorry for the delay, I’m travelling away from my Windows test platform so
>> had to knock up a VM. Definitely line 473. Here’s a stack trace:
>>
>> org.apache.juneau.BeanRuntimeException: interface org.apache.juneau.BeanConfigTest$A
>> is not visible from class loader
>> at org.apache.juneau.BeanSession.newBean(BeanSession.java:858)
>> at org.apache.juneau.BeanSession.newBeanMap(BeanSession.java:810)
>> at org.apache.juneau.BeanSession.newBeanMap(BeanSession.java:790)
>> at org.apache.juneau.BeanConfigTest.testProxyHandler(
>> BeanConfigTest.java:473)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(
>> NativeMethodAccessorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>> DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:497)
>> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(
>> FrameworkMethod.java:47)
>> at org.junit.internal.runners.model.ReflectiveCallable.run(
>> ReflectiveCallable.java:12)
>> at org.junit.runners.model.FrameworkMethod.invokeExplosively(
>> FrameworkMethod.java:44)
>> at org.junit.internal.runners.statements.InvokeMethod.
>> evaluate(InvokeMethod.java:17)
>> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
>> at org.junit.runners.BlockJUnit4ClassRunner.runChild(
>> BlockJUnit4ClassRunner.java:70)
>> at org.junit.runners.BlockJUnit4ClassRunner.runChild(
>> BlockJUnit4ClassRunner.java:50)
>> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>> at org.junit.runners.ParentRunner.runChildren(
>> ParentRunner.java:236)
>> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>> at org.junit.runners.ParentRunner$2.evaluate(
>> ParentRunner.java:229)
>> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(
>> JUnit4Provider.java:367)
>> at org.apache.maven.surefire.junit4.JUnit4Provider.
>> executeWithRerun(JUnit4Provider.java:274)
>> at org.apache.maven.surefire.junit4.JUnit4Provider.
>> executeTestSet(JUnit4Provider.java:238)
>> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(
>> JUnit4Provider.java:161)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(
>> NativeMethodAccessorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>> DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:497)
>> at org.apache.maven.surefire.util.ReflectionUtils.
>> invokeMethodWithArray2(ReflectionUtils.java:202)
>> at org.apache.maven.surefire.booter.ProviderFactory$
>> ProviderProxy.invoke(ProviderFactory.java:155)
>> at org.apache.maven.surefire.booter.ProviderFactory.
>> invokeProvider(ProviderFactory.java:81)
>> at org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.
>> runSuitesInProcess(InPluginVMSurefireStarter.java:82)
>> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.
>> executeProvider(AbstractSurefireMojo.java:1010)
>> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.
>> executeAfterPreconditionsChecked(AbstractSurefireMojo.java:862)
>> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.
>> execute(AbstractSurefireMojo.java:755)
>> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(
>> DefaultBuildPluginManager.java:134)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
>> MojoExecutor.java:207)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
>> MojoExecutor.java:153)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
>> MojoExecutor.java:145)
>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
>> buildProject(LifecycleModuleBuilder.java:116)
>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
>> buildProject(LifecycleModuleBuilder.java:80)
>> at org.apache.maven.lifecycle.internal.builder.singlethreaded.
>> SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>> at org.apache.maven.lifecycle.internal.LifecycleStarter.
>> execute(LifecycleStarter.java:128)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(
>> NativeMethodAccessorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>> DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:497)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.
>> launchEnhanced(Launcher.java:289)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.
>> launch(Launcher.java:229)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.
>> mainWithExitCode(Launcher.java:415)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.
>> main(Launcher.java:356)
>> Caused by: java.lang.IllegalArgumentException: interface
>> org.apache.juneau.BeanConfigTest$A is not visible from class loader
>> at java.lang.reflect.Proxy$ProxyClassFactory.apply(Proxy.java:581)
>> at java.lang.reflect.Proxy$ProxyClassFactory.apply(Proxy.java:557)
>> at java.lang.reflect.WeakCache$Factory.get(WeakCache.java:230)
>> at java.lang.reflect.WeakCache.get(WeakCache.java:127)
>> at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:419)
>> at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:719)
>> at org.apache.juneau.BeanMeta.newBean(BeanMeta.java:723)
>> at org.apache.juneau.BeanSession.newBean(BeanSession.java:851)
>> ... 57 more
>>
>>
>>
>>> On 24 Sep 2017, at 18:40, James Bognar <ja...@apache.org> wrote:
>>>
>>> Hi David,
>>>
>>> Is that really occurring on line 473? Could you catch the exception and
>>> print a longer stack trace?
>>>
>>> Thanks!
>>>
>>> On Sun, Sep 24, 2017 at 4:31 AM, David Goddard <go...@acm.org> wrote:
>>>
>>>> Hi,
>>>>
>>>> Yes, this code now works:
>>>>
>>>> @Test
>>>> public void test() {
>>>> BeanSession session = ps.getBeanContext()
>>>> .createSession(new BeanSessionArgs(null, sessionLocale,
>>>> sessionTimeZone, null));
>>>> String actual = session.convertToType(calendar, String.class);
>>>> if (expected.indexOf('(') == -1)
>>>> // Fix JVM-specific formatting difference
>>>> actual.replaceAll(" \\([^\\)]+\\)",
>>>> "").replaceAll("\\([^\\)]+\\) ", "");
>>>> assertEquals(expected, actual);
>>>> Object c2 = session.convertToType(actual, calendar.getClass());
>>>> String actual2 = session.convertToType(c2, String.class);
>>>> if (expected.indexOf('(') == -1)
>>>> // Fix JVM-specific formatting difference
>>>> actual2 = actual2.replaceAll("\\([^\\)]+\\) ", "");
>>>> assertEquals(expected, actual2);
>>>> }
>>>>
>>>> However, still one more error in my Windows environment though :(
>>>>
>>>> #############################
>>>> Tests run: 11, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.031
>> sec
>>>> <<< FAILURE! - in org.apache.juneau.BeanConfigTest
>>>> testProxyHandler(org.apache.juneau.BeanConfigTest) Time elapsed: 0 sec
>>>> <<< ERROR!
>>>> org.apache.juneau.BeanRuntimeException: interface
>>>> org.apache.juneau.BeanConfigTest$A is not visible from class loader
>>>> at org.apache.juneau.BeanConfigTest.testProxyHandler(BeanConfig
>>>> Test.java:473)
>>>> Caused by: java.lang.IllegalArgumentException: interface
>>>> org.apache.juneau.BeanConfigTest$A is not visible from class loader
>>>> at org.apache.juneau.BeanConfigTest.testProxyHandler(BeanConfig
>>>> Test.java:473)
>>>> #############################
>>>>
>>>> I'm wondering if this is an issue specific to my setup. When I have a
>>>> chance (I am travelling at the moment), I'll set up an Oracle JVM in my
>>>> Windows test environment and try a build with that.
>>>>
>>>> David
>>>>
>>>> On 23/09/2017 21:35, James Bognar wrote:
>>>>
>>>>> Hi David,
>>>>>
>>>>> How about this?
>>>>> if (expected.indexOf('(') == -1)
>>>>> actual.replaceAll(" \\([^\\)]+\\)", "").replaceAll("\\([^\\)]+\\) ",
>>>>> "");
>>>>>
>>>>>
>>>>> On Fri, Sep 22, 2017 at 3:08 PM, David Goddard <go...@acm.org>
>> wrote:
>>>>>
>>>>> Most things are in some way IBM's fault :)
>>>>>>
>>>>>> Trying both variants of your fix gives similar results. Better in
>> both
>>>>>> cases, but not quite there. Details below.
>>>>>>
>>>>>> It looks to me on a quick read that those cases that now fail are
>> failing
>>>>>> because they *do* expect a value between the parentheses, and of
>> course
>>>>>> the
>>>>>> fix strips that out. For example, here's test 205:
>>>>>>
>>>>>> { "205", testDate, CalendarSwap.DateTimeLong.class, "en_UK",
>>>>>> Locale.KOREA, null, null, "2001년 3월 3일 (토) 오전 10시 11분 12초" },
>>>>>>
>>>>>> I guess we could bend the test a little further by conditionally only
>>>>>> stripping out the parenthetical content if the expected value doesn't
>>>>>> contain values in parentheses itself, but that be regarded as a fix
>> too
>>>>>> far...
>>>>>>
>>>>>> #######################
>>>>>>
>>>>>> actual = actual.replaceAll("\\([^\\)]+\\) ", "");
>>>>>> actual2 = actual2.replaceAll("\\([^\\)]+\\) ", "");
>>>>>>
>>>>>> ...leads to:
>>>>>>
>>>>>> Tests run: 460, Failures: 2, Errors: 0, Skipped: 0, Time elapsed:
>> 19.485
>>>>>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
>>>>>> test[205](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>> elapsed:
>>>>>> 0.004 sec <<< FAILURE!
>>>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11?
>> 12?>
>>>>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>>>>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(
>> Localiz
>>>>>> edDatesTest.java:660)
>>>>>>
>>>>>> test[435](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>> elapsed:
>>>>>> 0.001 sec <<< FAILURE!
>>>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11?
>> 12?>
>>>>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>>>>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(
>> Localiz
>>>>>> edDatesTest.java:660)
>>>>>>
>>>>>> With the different location for the space in the regexp, I get a
>> longer
>>>>>> list of failures:
>>>>>>
>>>>>> #######################
>>>>>>
>>>>>> actual = actual.replaceAll(" \\([^\\)]+\\)", "");
>>>>>> actual2 = actual2.replaceAll(" \\([^\\)]+\\)", "");
>>>>>>
>>>>>> ... leads to:
>>>>>>
>>>>>> Running org.apache.juneau.transforms.LocalizedDatesTest
>>>>>> Tests run: 460, Failures: 4, Errors: 0, Skipped: 0, Time elapsed:
>> 0.189
>>>>>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
>>>>>> test[125](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>> elapsed:
>>>>>> 0.003 sec <<< FAILURE!
>>>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3?[ (?)]> but
>> was:<2001?
>>>>>> 3? 3?[]>
>>>>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(
>> Localiz
>>>>>> edDatesTest.java:660)
>>>>>>
>>>>>> test[205](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>> elapsed:
>>>>>> 0 sec <<< FAILURE!
>>>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11?
>> 12?>
>>>>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>>>>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(
>> Localiz
>>>>>> edDatesTest.java:660)
>>>>>>
>>>>>> test[355](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>> elapsed:
>>>>>> 0 sec <<< FAILURE!
>>>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3?[ (?)]> but
>> was:<2001?
>>>>>> 3? 3?[]>
>>>>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(
>> Localiz
>>>>>> edDatesTest.java:660)
>>>>>>
>>>>>> test[435](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>> elapsed:
>>>>>> 0.001 sec <<< FAILURE!
>>>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11?
>> 12?>
>>>>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>>>>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(
>> Localiz
>>>>>> edDatesTest.java:660)
>>>>>>
>>>>>> #######################
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 22/09/2017 00:05, James Bognar wrote:
>>>>>>
>>>>>> Ah...so we can blame IBM :-)
>>>>>>>
>>>>>>> Can you see if swapping the location of the space in the regular
>>>>>>> expressions fixes all the tests?
>>>>>>> actual = actual.replaceAll(" \\([^\\)]+\\)", "");
>>>>>>>
>>>>>>> On Thu, Sep 21, 2017 at 6:01 PM, David Goddard <go...@acm.org>
>> wrote:
>>>>>>>
>>>>>>> Just to add:
>>>>>>>
>>>>>>>>
>>>>>>>> Maybe it's JVM vendor-specific behavior?
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> Yes, I've now tested again after changing from an IBM JRE to an
>> Oracle
>>>>>>>> JRE
>>>>>>>> - this resolves the problem. It looks like this is specific to the
>> IBM
>>>>>>>> JRE
>>>>>>>> then. My Mac testing was done with an Oracle JRE, so I think this
>> is
>>>>>>>> probably JVM-specific rather than OS-specific.
>>>>>>>>
>>>>>>>>
>>>>>>>> On 21/09/2017 23:46, David Goddard wrote:
>>>>>>>>
>>>>>>>> Actual text is:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2001年3月3日 (土曜日)
>>>>>>>>> (I've attached a copy as a text file also)
>>>>>>>>>
>>>>>>>>> In this case, I it looks like the value between the parenthesis is
>> the
>>>>>>>>> day name, "Saturday". So the expected value is just the date
>> (2001年3月
>>>>>>>>> 3日),
>>>>>>>>> but the day is being added in the process.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 21/09/2017 22:45, James Bognar wrote:
>>>>>>>>>
>>>>>>>>> Interesting. So the behavior of...
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> DateFormat.getDateInstance(DateFormat.FULL, locale).format(date);
>>>>>>>>>> DateFormat.getDateTimeInstance(DateFormat.FULL, DateFormat.FULL,
>>>>>>>>>> locale
>>>>>>>>>> ).format(date);
>>>>>>>>>>
>>>>>>>>>> ...returns different formats depending on the OS. Lovely.
>>>>>>>>>>
>>>>>>>>>> Maybe it's JVM vendor-specific behavior?
>>>>>>>>>>
>>>>>>>>>> I'm curious to know what's in those parentheses...
>>>>>>>>>> 2001?3?3? [*(???)* ]10?11?12? GMT
>>>>>>>>>>
>>>>>>>>>> Might give me something to google for.
>>>>>>>>>>
>>>>>>>>>> It's technically a test-only issue. We can probably 'fix' the
>>>>>>>>>> testcase
>>>>>>>>>> by
>>>>>>>>>> just stripping out the formatting difference...
>>>>>>>>>>
>>>>>>>>>> @Test
>>>>>>>>>> public void test() {
>>>>>>>>>> BeanSession session = ps.getBeanContext().createSession(new
>>>>>>>>>> BeanSessionArgs(null, sessionLocale, sessionTimeZone, null));
>>>>>>>>>> String actual = session.convertToType(calendar, String.class);
>>>>>>>>>> *actual = actual.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>>>>>>>>>> Windows-specific
>>>>>>>>>> formatting difference*
>>>>>>>>>> assertEquals(expected, actual);
>>>>>>>>>> Object c2 = session.convertToType(actual, calendar.getClass());
>>>>>>>>>> String actual2 = session.convertToType(c2, String.class);
>>>>>>>>>> *actual2 = actual2.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>>>>>>>>>> Windows-specific formatting difference*
>>>>>>>>>> assertEquals(expected, actual2);
>>>>>>>>>> }
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, Sep 21, 2017 at 3:11 PM, David Goddard <go...@acm.org>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Yes, that fixed it, thanks. It also still tests OK on my Mac
>> after
>>>>>>>>>>> the
>>>>>>>>>>> change.
>>>>>>>>>>>
>>>>>>>>>>> I'm now running into some further test issues, also on Windows
>> only.
>>>>>>>>>>>
>>>>>>>>>>> ########################
>>>>>>>>>>>
>>>>>>>>>>> Tests run: 460, Failures: 16, Errors: 0, Skipped: 0, Time
>> elapsed:
>>>>>>>>>>> 0.247
>>>>>>>>>>> sec <<< FAILURE! - in org.apache.juneau.transforms.L
>>>>>>>>>>> ocalizedDatesTest
>>>>>>>>>>> test[111](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>>>>>>> elapsed:
>>>>>>>>>>> 0.015 sec <<< FAILURE!
>>>>>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3?[]> but
>>>>>>>>>>> was:<2001?3?3?[
>>>>>>>>>>> (???)]>
>>>>>>>>>>> at org.apache.juneau.transforms.L
>>>>>>>>>>> ocalizedDatesTest.test(Localiz
>>>>>>>>>>> edDatesTest.java:645)
>>>>>>>>>>>
>>>>>>>>>>> [...]
>>>>>>>>>>> test[423](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>>>>>>> elapsed:
>>>>>>>>>>> 0 sec <<< FAILURE!
>>>>>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT>
>>>>>>>>>>> but
>>>>>>>>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>>>>>>>>>> at org.apache.juneau.transforms.L
>>>>>>>>>>> ocalizedDatesTest.test(Localiz
>>>>>>>>>>> edDatesTest.java:645)
>>>>>>>>>>>
>>>>>>>>>>> test[424](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>>>>>>> elapsed:
>>>>>>>>>>> 0 sec <<< FAILURE!
>>>>>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT>
>>>>>>>>>>> but
>>>>>>>>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>>>>>>>>>> at org.apache.juneau.transforms.L
>>>>>>>>>>> ocalizedDatesTest.test(Localiz
>>>>>>>>>>> edDatesTest.java:645)
>>>>>>>>>>>
>>>>>>>>>>> ########################
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> These are specific to date swap tests in Japanese & Korean:
>>>>>>>>>>>
>>>>>>>>>>> { "421", testDate.getTime(), DateSwap.DateTimeFull.class,
>> "ja_JP",
>>>>>>>>>>> null,
>>>>>>>>>>> null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>>>>>> { "422", testDate.getTime(), DateSwap.DateTimeFull.class,
>>>>>>>>>>> Locale.JAPAN,
>>>>>>>>>>> null, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>>>>>> { "423", testDate.getTime(), DateSwap.DateTimeFull.class, null,
>>>>>>>>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT"
>> },
>>>>>>>>>>> { "424", testDate.getTime(), DateSwap.DateTimeFull.class,
>> "en_UK",
>>>>>>>>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT"
>> },
>>>>>>>>>>> { "425", testDate.getTime(), DateSwap.DateTimeFull.class,
>> "en_UK",
>>>>>>>>>>> Locale.KOREA, null, null, "2001ë…„ 3ì›” 3ì�¼ í† ìš”ì�¼ ì˜¤ì „
>> 10시
>>>>>>>>>>> 11분
>>>>>>>>>>> 12ì´ˆ GMT" },
>>>>>>>>>>> etc.
>>>>>>>>>>>
>>>>>>>>>>> All the date swaps where the test date contains Japanese or
>> Korean
>>>>>>>>>>> characters in the date part fail in this way. I initially
>> thought
>>>>>>>>>>> it
>>>>>>>>>>> was
>>>>>>>>>>> the code page of the file, but I've changed to UTF-8 from the
>>>>>>>>>>> default
>>>>>>>>>>> and
>>>>>>>>>>> this didn't resolve this for me. Again, this is specific to my
>>>>>>>>>>> Windows
>>>>>>>>>>> platform - all is fine on Mac.
>>>>>>>>>>>
>>>>>>>>>>> Given that this is a build test error, and specific to one
>> platform
>>>>>>>>>>> (and
>>>>>>>>>>> possibly one machine), I'm not sure that it is a fatal problem
>> for
>>>>>>>>>>> the
>>>>>>>>>>> release.
>>>>>>>>>>>
>>>>>>>>>>> David
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 21/09/2017 14:55, James Bognar wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi David,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> I don't have a Windows machine anymore :-(
>>>>>>>>>>>>
>>>>>>>>>>>> It looks like a test issue. Is it only RDF tests that are
>> failing?
>>>>>>>>>>>>
>>>>>>>>>>>> Can you find line 484 in org.apache.juneau.TestUtils in
>>>>>>>>>>>> juneau-core-tests...
>>>>>>>>>>>>
>>>>>>>>>>>> String[] e = expected.trim().split("\n"), a =
>>>>>>>>>>>> actual.trim().split("\n");
>>>>>>>>>>>>
>>>>>>>>>>>> ...and change it to this?...
>>>>>>>>>>>>
>>>>>>>>>>>> String[] e = expected.trim().split("[\r\n]+"), a =
>>>>>>>>>>>> actual.trim().split(
>>>>>>>>>>>> "[\r\n]+");
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Background on this method: Since Jena does not guarantee the
>> order
>>>>>>>>>>>> of
>>>>>>>>>>>> entries in the generated RDF (it's pretty much random), it's
>>>>>>>>>>>> difficult
>>>>>>>>>>>> to
>>>>>>>>>>>> do simple comparison validation. So instead, we sort the
>> expected
>>>>>>>>>>>> and
>>>>>>>>>>>> actual lines and then check for comparison. It's not perfect
>> (XML
>>>>>>>>>>>> attribute order can also be random), but generally good enough
>> for
>>>>>>>>>>>> what
>>>>>>>>>>>> we're testing.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Sep 21, 2017 at 5:52 AM, David Goddard <goddard@acm.org
>>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> I'm seeting a whole load of test failures in juneau-core parsing
>>>>>>>>>>>>> (every
>>>>>>>>>>>>> round trip test is failing for me). For example:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ByteArrayBase64SwapComboTest>ComboRoundTripTest.g32_parseRdf
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> XmlR:701->ComboRoundTripTest.testParse:205
>>>>>>>>>>>>>>
>>>>>>>>>>>>> ByteArray2d/parseRdfXmlR
>>>>>>>>>>>>> parse-normal failed expected:<<rdf:RDF>[
>>>>>>>>>>>>> <rdf:Seq>
>>>>>>>>>>>>> <rdf:li>AQID</rdf:li>
>>>>>>>>>>>>> <rdf:li>BAUG</rdf:li>
>>>>>>>>>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>>>>>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> </rdf:Seq>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> </rdf:RDF>]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> but was:<<rdf:RDF>[
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <rdf:Seq>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <rdf:li>AQID</rdf:li>
>>>>>>>>>>>>> <rdf:li>BAUG</rdf:li>
>>>>>>>>>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>>>>>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> </rdf:Seq>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> </rdf:RDF>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> ]
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> The only consistent difference I see is that the final closing
>>>>>>>>>>>>>> square
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> bracket is appearing on a new line. Perhaps this is a
>> character
>>>>>>>>>>>>> encoding
>>>>>>>>>>>>> issue (although I wouldn't rule out user error) - these tests
>> fail
>>>>>>>>>>>>> on
>>>>>>>>>>>>> a
>>>>>>>>>>>>> Windows platform, but work fine on a Mac.
>>>>>>>>>>>>>
>>>>>>>>>>>>> David
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 20/09/2017 15:39, James Bognar wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Indeed they are.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I've fixed them in Git. Thanks David!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <
>> goddard@acm.org>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I'm seeing a couple of issues with the Eclipse project names
>> when
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> importing a fresh clone into a workspace.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> juneau-microservice/.project has <name>juneau-rest</name>
>>>>>>>>>>>>>>> juneau-doc/.project has <name>juneau-marshall</name>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I'm assuming these are copy/paste errors arising from the
>>>>>>>>>>>>>>> restructuring.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> David
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 19/09/2017 18:26, Charles Mims wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> +1, with intermittent test failures in Apache Juneau
>>>>>>>>>>>>>>> Microservice
>>>>>>>>>>>>>>> Tests
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> MD5 (apache-juneau-6.4.0-incubating-src.zip) =
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>>>>>>>>>>>> For me it failed on the 1st and 2nd try, passed on the 3rd.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <
>>>>>>>>>>>>>>>> jamesbognar@apache.org>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I
>> think we
>>>>>>>>>>>>>>>> need
>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> handle this problem soon.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Darn.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I'm thinking it must be an issue with Jetty since we just
>>>>>>>>>>>>>>>>> upgraded
>>>>>>>>>>>>>>>>> it.
>>>>>>>>>>>>>>>>> From the Jetty side, the connection is open waiting
>> for
>>>>>>>>>>>>>>>>> data,
>>>>>>>>>>>>>>>>> but
>>>>>>>>>>>>>>>>> that's
>>>>>>>>>>>>>>>>> all I know.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I'll have to figure out how to use Fiddler and do some
>>>>>>>>>>>>>>>>> low-level
>>>>>>>>>>>>>>>>> debugging. It's really hard to reproduce though :-(
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <
>>>>>>>>>>>>>>>>> yidonguk@gmail.com
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> SHA1, MD5 Checksum OK
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Maven Build OK
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I
>> think
>>>>>>>>>>>>>>>>>> we
>>>>>>>>>>>>>>>>>> need
>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>> handle this problem soon.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [INFO] Reactor Summary:
>>>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau (incubating)
>> .........................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 10.521 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau - Core APIs
>> ..........................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 0.737 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau Marshall
>> .............................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 45.444 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau Marshal RDF
>> ..........................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 3.558 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau Data Transfer Objects
>> ................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 6.813 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau Core ..............................
>> ...
>>>>>>>>>>>>>>>>>> SUCCESS [
>>>>>>>>>>>>>>>>>> 1.025 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau Config File API
>> ......................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 1.928 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau Core Tests
>> ...........................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [01:04
>>>>>>>>>>>>>>>>>> min]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau - REST APIs
>> ..........................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 0.080 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau REST Servlet API
>> .....................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 2.331 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau REST JAX/RS API
>> ......................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 0.476 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau REST Client API
>> ......................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 1.005 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau - Microservice APIs
>> ..................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 0.068 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Server
>> ..................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 1.588 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Template
>> ................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 1.243 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau - Examples
>> ...........................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 0.183 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau REST Examples
>> ........................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 8.512 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Tests
>> ...................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 24.522 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau Core Examples
>> ........................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 0.287 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau Javadocs
>> .............................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 0.617 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau - Release Engineering
>> ................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 0.040 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau UberJar
>> ..............................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 1.008 s]
>>>>>>>>>>>>>>>>>> [INFO] Apache Juneau Distribution
>> .........................
>>>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>>>> 0.768 s]
>>>>>>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>>>>>> ------------
>>>>>>>>>>>>>>>>>> [INFO] BUILD SUCCESS
>>>>>>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>>>>>> ------------
>>>>>>>>>>>>>>>>>> [INFO] Total time: 03:01 min
>>>>>>>>>>>>>>>>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>>>>>>>>>>>>>>>>>> [INFO] Final Memory: 87M/773M
>>>>>>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>>>>>> ------------
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Raphi D Lee, yidonguk@gmail.com
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 2017. 9. 18. 오전 9:54, James Bognar <
>> jamesbognar@apache.org>
>>>>>>>>>>>>>>>>>> 작성:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I am pleased to be calling this vote for the source
>> release
>>>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Apache
>>>>>>>>>>>>>>>>>>> Juneau 6.4.0-incubating RC2.
>>>>>>>>>>>>>>>>>>> This includes some fixes for bugs found in RC1 and some
>>>>>>>>>>>>>>>>>>> packaging
>>>>>>>>>>>>>>>>>>> changes
>>>>>>>>>>>>>>>>>>> for the example and template projects.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> The list of new features can be found here:
>>>>>>>>>>>>>>>>>>> http://juneau.incubator.apache.org/site/apidocs/
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> overview-summary.html#6.4.0
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> The binaries are available at:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> binaries/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> The release candidate to be voted over is available at:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> source/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> SHA-1 checksums:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81
>> apache-juneau-6.4.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 0-incubating-src.zip
>>>>>>>>>>>>>>>>>>> c3d4a1d7c21142a4006876419729d9f0c352203e
>> apache-juneau-6.4.
>>>>>>>>>>>>>>>>>>> 0-incubating-bin.zip
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> MD5 checksums:
>>>>>>>>>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>>>>>>>>>>>>>>> apache-juneau-6.4.0-incubating
>>>>>>>>>>>>>>>>>>> -src.zip
>>>>>>>>>>>>>>>>>>> 4e96d5047c0e9f03f0def2d017521f13
>>>>>>>>>>>>>>>>>>> apache-juneau-6.4.0-incubating
>>>>>>>>>>>>>>>>>>> -bin.zip
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Build the release candidate using:
>>>>>>>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> The release candidate is signed with a GPG key available
>> at:
>>>>>>>>>>>>>>>>>>> https://dist.apache.org/repos/
>>>>>>>>>>>>>>>>>>> dist/release/incubator/juneau/
>>>>>>>>>>>>>>>>>>> KEYS
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> A staged Maven repository is available for review at:
>>>>>>>>>>>>>>>>>>> https://repository.apache.org/
>>>>>>>>>>>>>>>>>>> content/repositories/orgapache
>>>>>>>>>>>>>>>>>>> juneau-1016/
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> The Git commit for this release is...
>>>>>>>>>>>>>>>>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> juneau.git;a=commit;h=6de99819
>>>>>>>>>>>>>>>>>>> 3807eeec40e6f297f6b70222552f3b
>>>>>>>>>>>>>>>>>>> 37
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b702
>> 22552f3b
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 37>*
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Please vote on releasing this package as:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Apache Juneau 6.4.0-incubating
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> This vote will be open until 20-Sep-2017 9:00pm EST and
>>>>>>>>>>>>>>>>>>> passes
>>>>>>>>>>>>>>>>>>> if a
>>>>>>>>>>>>>>>>>>> majority of at least three +1 Apache Juneau PPMC votes
>> are
>>>>>>>>>>>>>>>>>>> cast.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> [ ] +1 Release this package
>>>>>>>>>>>>>>>>>>> [ ] 0 I don't feel strongly about it, but don't object
>>>>>>>>>>>>>>>>>>> [ ] -1 Do not release this package because...
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Anyone can participate in testing and voting, not just
>>>>>>>>>>>>>>>>>>> committers,
>>>>>>>>>>>>>>>>>>> please
>>>>>>>>>>>>>>>>>>> feel free to try out the release candidate and provide
>> your
>>>>>>>>>>>>>>>>>>> votes.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>
>>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by James Bognar <ja...@apache.org>.
Thanks David,
The stack trace helps. Can you open a defect for this issue? IMHO, it's
not serious enough to hold up release. I can fix it in 6.4.1.
On Tue, Sep 26, 2017 at 2:28 PM, David Goddard <go...@acm.org> wrote:
> Hi,
>
> Sorry for the delay, I’m travelling away from my Windows test platform so
> had to knock up a VM. Definitely line 473. Here’s a stack trace:
>
> org.apache.juneau.BeanRuntimeException: interface org.apache.juneau.BeanConfigTest$A
> is not visible from class loader
> at org.apache.juneau.BeanSession.newBean(BeanSession.java:858)
> at org.apache.juneau.BeanSession.newBeanMap(BeanSession.java:810)
> at org.apache.juneau.BeanSession.newBeanMap(BeanSession.java:790)
> at org.apache.juneau.BeanConfigTest.testProxyHandler(
> BeanConfigTest.java:473)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(
> FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(
> ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(
> FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.InvokeMethod.
> evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(
> BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(
> BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(
> ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(
> ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(
> JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.
> executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.
> executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(
> JUnit4Provider.java:161)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.apache.maven.surefire.util.ReflectionUtils.
> invokeMethodWithArray2(ReflectionUtils.java:202)
> at org.apache.maven.surefire.booter.ProviderFactory$
> ProviderProxy.invoke(ProviderFactory.java:155)
> at org.apache.maven.surefire.booter.ProviderFactory.
> invokeProvider(ProviderFactory.java:81)
> at org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.
> runSuitesInProcess(InPluginVMSurefireStarter.java:82)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.
> executeProvider(AbstractSurefireMojo.java:1010)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.
> executeAfterPreconditionsChecked(AbstractSurefireMojo.java:862)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.
> execute(AbstractSurefireMojo.java:755)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(
> DefaultBuildPluginManager.java:134)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:207)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
> buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
> buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.
> SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.
> execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> main(Launcher.java:356)
> Caused by: java.lang.IllegalArgumentException: interface
> org.apache.juneau.BeanConfigTest$A is not visible from class loader
> at java.lang.reflect.Proxy$ProxyClassFactory.apply(Proxy.java:581)
> at java.lang.reflect.Proxy$ProxyClassFactory.apply(Proxy.java:557)
> at java.lang.reflect.WeakCache$Factory.get(WeakCache.java:230)
> at java.lang.reflect.WeakCache.get(WeakCache.java:127)
> at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:419)
> at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:719)
> at org.apache.juneau.BeanMeta.newBean(BeanMeta.java:723)
> at org.apache.juneau.BeanSession.newBean(BeanSession.java:851)
> ... 57 more
>
>
>
> > On 24 Sep 2017, at 18:40, James Bognar <ja...@apache.org> wrote:
> >
> > Hi David,
> >
> > Is that really occurring on line 473? Could you catch the exception and
> > print a longer stack trace?
> >
> > Thanks!
> >
> > On Sun, Sep 24, 2017 at 4:31 AM, David Goddard <go...@acm.org> wrote:
> >
> >> Hi,
> >>
> >> Yes, this code now works:
> >>
> >> @Test
> >> public void test() {
> >> BeanSession session = ps.getBeanContext()
> >> .createSession(new BeanSessionArgs(null, sessionLocale,
> >> sessionTimeZone, null));
> >> String actual = session.convertToType(calendar, String.class);
> >> if (expected.indexOf('(') == -1)
> >> // Fix JVM-specific formatting difference
> >> actual.replaceAll(" \\([^\\)]+\\)",
> >> "").replaceAll("\\([^\\)]+\\) ", "");
> >> assertEquals(expected, actual);
> >> Object c2 = session.convertToType(actual, calendar.getClass());
> >> String actual2 = session.convertToType(c2, String.class);
> >> if (expected.indexOf('(') == -1)
> >> // Fix JVM-specific formatting difference
> >> actual2 = actual2.replaceAll("\\([^\\)]+\\) ", "");
> >> assertEquals(expected, actual2);
> >> }
> >>
> >> However, still one more error in my Windows environment though :(
> >>
> >> #############################
> >> Tests run: 11, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.031
> sec
> >> <<< FAILURE! - in org.apache.juneau.BeanConfigTest
> >> testProxyHandler(org.apache.juneau.BeanConfigTest) Time elapsed: 0 sec
> >> <<< ERROR!
> >> org.apache.juneau.BeanRuntimeException: interface
> >> org.apache.juneau.BeanConfigTest$A is not visible from class loader
> >> at org.apache.juneau.BeanConfigTest.testProxyHandler(BeanConfig
> >> Test.java:473)
> >> Caused by: java.lang.IllegalArgumentException: interface
> >> org.apache.juneau.BeanConfigTest$A is not visible from class loader
> >> at org.apache.juneau.BeanConfigTest.testProxyHandler(BeanConfig
> >> Test.java:473)
> >> #############################
> >>
> >> I'm wondering if this is an issue specific to my setup. When I have a
> >> chance (I am travelling at the moment), I'll set up an Oracle JVM in my
> >> Windows test environment and try a build with that.
> >>
> >> David
> >>
> >> On 23/09/2017 21:35, James Bognar wrote:
> >>
> >>> Hi David,
> >>>
> >>> How about this?
> >>> if (expected.indexOf('(') == -1)
> >>> actual.replaceAll(" \\([^\\)]+\\)", "").replaceAll("\\([^\\)]+\\) ",
> >>> "");
> >>>
> >>>
> >>> On Fri, Sep 22, 2017 at 3:08 PM, David Goddard <go...@acm.org>
> wrote:
> >>>
> >>> Most things are in some way IBM's fault :)
> >>>>
> >>>> Trying both variants of your fix gives similar results. Better in
> both
> >>>> cases, but not quite there. Details below.
> >>>>
> >>>> It looks to me on a quick read that those cases that now fail are
> failing
> >>>> because they *do* expect a value between the parentheses, and of
> course
> >>>> the
> >>>> fix strips that out. For example, here's test 205:
> >>>>
> >>>> { "205", testDate, CalendarSwap.DateTimeLong.class, "en_UK",
> >>>> Locale.KOREA, null, null, "2001년 3월 3일 (토) 오전 10시 11분 12초" },
> >>>>
> >>>> I guess we could bend the test a little further by conditionally only
> >>>> stripping out the parenthetical content if the expected value doesn't
> >>>> contain values in parentheses itself, but that be regarded as a fix
> too
> >>>> far...
> >>>>
> >>>> #######################
> >>>>
> >>>> actual = actual.replaceAll("\\([^\\)]+\\) ", "");
> >>>> actual2 = actual2.replaceAll("\\([^\\)]+\\) ", "");
> >>>>
> >>>> ...leads to:
> >>>>
> >>>> Tests run: 460, Failures: 2, Errors: 0, Skipped: 0, Time elapsed:
> 19.485
> >>>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
> >>>> test[205](org.apache.juneau.transforms.LocalizedDatesTest) Time
> >>>> elapsed:
> >>>> 0.004 sec <<< FAILURE!
> >>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11?
> 12?>
> >>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
> >>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(
> Localiz
> >>>> edDatesTest.java:660)
> >>>>
> >>>> test[435](org.apache.juneau.transforms.LocalizedDatesTest) Time
> >>>> elapsed:
> >>>> 0.001 sec <<< FAILURE!
> >>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11?
> 12?>
> >>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
> >>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(
> Localiz
> >>>> edDatesTest.java:660)
> >>>>
> >>>> With the different location for the space in the regexp, I get a
> longer
> >>>> list of failures:
> >>>>
> >>>> #######################
> >>>>
> >>>> actual = actual.replaceAll(" \\([^\\)]+\\)", "");
> >>>> actual2 = actual2.replaceAll(" \\([^\\)]+\\)", "");
> >>>>
> >>>> ... leads to:
> >>>>
> >>>> Running org.apache.juneau.transforms.LocalizedDatesTest
> >>>> Tests run: 460, Failures: 4, Errors: 0, Skipped: 0, Time elapsed:
> 0.189
> >>>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
> >>>> test[125](org.apache.juneau.transforms.LocalizedDatesTest) Time
> >>>> elapsed:
> >>>> 0.003 sec <<< FAILURE!
> >>>> org.junit.ComparisonFailure: expected:<2001? 3? 3?[ (?)]> but
> was:<2001?
> >>>> 3? 3?[]>
> >>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(
> Localiz
> >>>> edDatesTest.java:660)
> >>>>
> >>>> test[205](org.apache.juneau.transforms.LocalizedDatesTest) Time
> >>>> elapsed:
> >>>> 0 sec <<< FAILURE!
> >>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11?
> 12?>
> >>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
> >>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(
> Localiz
> >>>> edDatesTest.java:660)
> >>>>
> >>>> test[355](org.apache.juneau.transforms.LocalizedDatesTest) Time
> >>>> elapsed:
> >>>> 0 sec <<< FAILURE!
> >>>> org.junit.ComparisonFailure: expected:<2001? 3? 3?[ (?)]> but
> was:<2001?
> >>>> 3? 3?[]>
> >>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(
> Localiz
> >>>> edDatesTest.java:660)
> >>>>
> >>>> test[435](org.apache.juneau.transforms.LocalizedDatesTest) Time
> >>>> elapsed:
> >>>> 0.001 sec <<< FAILURE!
> >>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11?
> 12?>
> >>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
> >>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(
> Localiz
> >>>> edDatesTest.java:660)
> >>>>
> >>>> #######################
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On 22/09/2017 00:05, James Bognar wrote:
> >>>>
> >>>> Ah...so we can blame IBM :-)
> >>>>>
> >>>>> Can you see if swapping the location of the space in the regular
> >>>>> expressions fixes all the tests?
> >>>>> actual = actual.replaceAll(" \\([^\\)]+\\)", "");
> >>>>>
> >>>>> On Thu, Sep 21, 2017 at 6:01 PM, David Goddard <go...@acm.org>
> wrote:
> >>>>>
> >>>>> Just to add:
> >>>>>
> >>>>>>
> >>>>>> Maybe it's JVM vendor-specific behavior?
> >>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>> Yes, I've now tested again after changing from an IBM JRE to an
> Oracle
> >>>>>> JRE
> >>>>>> - this resolves the problem. It looks like this is specific to the
> IBM
> >>>>>> JRE
> >>>>>> then. My Mac testing was done with an Oracle JRE, so I think this
> is
> >>>>>> probably JVM-specific rather than OS-specific.
> >>>>>>
> >>>>>>
> >>>>>> On 21/09/2017 23:46, David Goddard wrote:
> >>>>>>
> >>>>>> Actual text is:
> >>>>>>
> >>>>>>>
> >>>>>>> 2001年3月3日 (土曜日)
> >>>>>>> (I've attached a copy as a text file also)
> >>>>>>>
> >>>>>>> In this case, I it looks like the value between the parenthesis is
> the
> >>>>>>> day name, "Saturday". So the expected value is just the date
> (2001年3月
> >>>>>>> 3日),
> >>>>>>> but the day is being added in the process.
> >>>>>>>
> >>>>>>>
> >>>>>>> On 21/09/2017 22:45, James Bognar wrote:
> >>>>>>>
> >>>>>>> Interesting. So the behavior of...
> >>>>>>>
> >>>>>>>>
> >>>>>>>> DateFormat.getDateInstance(DateFormat.FULL, locale).format(date);
> >>>>>>>> DateFormat.getDateTimeInstance(DateFormat.FULL, DateFormat.FULL,
> >>>>>>>> locale
> >>>>>>>> ).format(date);
> >>>>>>>>
> >>>>>>>> ...returns different formats depending on the OS. Lovely.
> >>>>>>>>
> >>>>>>>> Maybe it's JVM vendor-specific behavior?
> >>>>>>>>
> >>>>>>>> I'm curious to know what's in those parentheses...
> >>>>>>>> 2001?3?3? [*(???)* ]10?11?12? GMT
> >>>>>>>>
> >>>>>>>> Might give me something to google for.
> >>>>>>>>
> >>>>>>>> It's technically a test-only issue. We can probably 'fix' the
> >>>>>>>> testcase
> >>>>>>>> by
> >>>>>>>> just stripping out the formatting difference...
> >>>>>>>>
> >>>>>>>> @Test
> >>>>>>>> public void test() {
> >>>>>>>> BeanSession session = ps.getBeanContext().createSession(new
> >>>>>>>> BeanSessionArgs(null, sessionLocale, sessionTimeZone, null));
> >>>>>>>> String actual = session.convertToType(calendar, String.class);
> >>>>>>>> *actual = actual.replaceAll("\\([^\\)]+\\) ", ""); // Fix
> >>>>>>>> Windows-specific
> >>>>>>>> formatting difference*
> >>>>>>>> assertEquals(expected, actual);
> >>>>>>>> Object c2 = session.convertToType(actual, calendar.getClass());
> >>>>>>>> String actual2 = session.convertToType(c2, String.class);
> >>>>>>>> *actual2 = actual2.replaceAll("\\([^\\)]+\\) ", ""); // Fix
> >>>>>>>> Windows-specific formatting difference*
> >>>>>>>> assertEquals(expected, actual2);
> >>>>>>>> }
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Thu, Sep 21, 2017 at 3:11 PM, David Goddard <go...@acm.org>
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>> Hi,
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> Yes, that fixed it, thanks. It also still tests OK on my Mac
> after
> >>>>>>>>> the
> >>>>>>>>> change.
> >>>>>>>>>
> >>>>>>>>> I'm now running into some further test issues, also on Windows
> only.
> >>>>>>>>>
> >>>>>>>>> ########################
> >>>>>>>>>
> >>>>>>>>> Tests run: 460, Failures: 16, Errors: 0, Skipped: 0, Time
> elapsed:
> >>>>>>>>> 0.247
> >>>>>>>>> sec <<< FAILURE! - in org.apache.juneau.transforms.L
> >>>>>>>>> ocalizedDatesTest
> >>>>>>>>> test[111](org.apache.juneau.transforms.LocalizedDatesTest) Time
> >>>>>>>>> elapsed:
> >>>>>>>>> 0.015 sec <<< FAILURE!
> >>>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3?[]> but
> >>>>>>>>> was:<2001?3?3?[
> >>>>>>>>> (???)]>
> >>>>>>>>> at org.apache.juneau.transforms.L
> >>>>>>>>> ocalizedDatesTest.test(Localiz
> >>>>>>>>> edDatesTest.java:645)
> >>>>>>>>>
> >>>>>>>>> [...]
> >>>>>>>>> test[423](org.apache.juneau.transforms.LocalizedDatesTest) Time
> >>>>>>>>> elapsed:
> >>>>>>>>> 0 sec <<< FAILURE!
> >>>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT>
> >>>>>>>>> but
> >>>>>>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
> >>>>>>>>> at org.apache.juneau.transforms.L
> >>>>>>>>> ocalizedDatesTest.test(Localiz
> >>>>>>>>> edDatesTest.java:645)
> >>>>>>>>>
> >>>>>>>>> test[424](org.apache.juneau.transforms.LocalizedDatesTest) Time
> >>>>>>>>> elapsed:
> >>>>>>>>> 0 sec <<< FAILURE!
> >>>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT>
> >>>>>>>>> but
> >>>>>>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
> >>>>>>>>> at org.apache.juneau.transforms.L
> >>>>>>>>> ocalizedDatesTest.test(Localiz
> >>>>>>>>> edDatesTest.java:645)
> >>>>>>>>>
> >>>>>>>>> ########################
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> These are specific to date swap tests in Japanese & Korean:
> >>>>>>>>>
> >>>>>>>>> { "421", testDate.getTime(), DateSwap.DateTimeFull.class,
> "ja_JP",
> >>>>>>>>> null,
> >>>>>>>>> null, null, "2001年3月3日 10時11分12秒 GMT" },
> >>>>>>>>> { "422", testDate.getTime(), DateSwap.DateTimeFull.class,
> >>>>>>>>> Locale.JAPAN,
> >>>>>>>>> null, null, null, "2001年3月3日 10時11分12秒 GMT" },
> >>>>>>>>> { "423", testDate.getTime(), DateSwap.DateTimeFull.class, null,
> >>>>>>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT"
> },
> >>>>>>>>> { "424", testDate.getTime(), DateSwap.DateTimeFull.class,
> "en_UK",
> >>>>>>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT"
> },
> >>>>>>>>> { "425", testDate.getTime(), DateSwap.DateTimeFull.class,
> "en_UK",
> >>>>>>>>> Locale.KOREA, null, null, "2001ë…„ 3ì›” 3ì�¼ í† ìš”ì�¼ ì˜¤ì „
> 10시
> >>>>>>>>> 11분
> >>>>>>>>> 12ì´ˆ GMT" },
> >>>>>>>>> etc.
> >>>>>>>>>
> >>>>>>>>> All the date swaps where the test date contains Japanese or
> Korean
> >>>>>>>>> characters in the date part fail in this way. I initially
> thought
> >>>>>>>>> it
> >>>>>>>>> was
> >>>>>>>>> the code page of the file, but I've changed to UTF-8 from the
> >>>>>>>>> default
> >>>>>>>>> and
> >>>>>>>>> this didn't resolve this for me. Again, this is specific to my
> >>>>>>>>> Windows
> >>>>>>>>> platform - all is fine on Mac.
> >>>>>>>>>
> >>>>>>>>> Given that this is a build test error, and specific to one
> platform
> >>>>>>>>> (and
> >>>>>>>>> possibly one machine), I'm not sure that it is a fatal problem
> for
> >>>>>>>>> the
> >>>>>>>>> release.
> >>>>>>>>>
> >>>>>>>>> David
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On 21/09/2017 14:55, James Bognar wrote:
> >>>>>>>>>
> >>>>>>>>> Hi David,
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> I don't have a Windows machine anymore :-(
> >>>>>>>>>>
> >>>>>>>>>> It looks like a test issue. Is it only RDF tests that are
> failing?
> >>>>>>>>>>
> >>>>>>>>>> Can you find line 484 in org.apache.juneau.TestUtils in
> >>>>>>>>>> juneau-core-tests...
> >>>>>>>>>>
> >>>>>>>>>> String[] e = expected.trim().split("\n"), a =
> >>>>>>>>>> actual.trim().split("\n");
> >>>>>>>>>>
> >>>>>>>>>> ...and change it to this?...
> >>>>>>>>>>
> >>>>>>>>>> String[] e = expected.trim().split("[\r\n]+"), a =
> >>>>>>>>>> actual.trim().split(
> >>>>>>>>>> "[\r\n]+");
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Background on this method: Since Jena does not guarantee the
> order
> >>>>>>>>>> of
> >>>>>>>>>> entries in the generated RDF (it's pretty much random), it's
> >>>>>>>>>> difficult
> >>>>>>>>>> to
> >>>>>>>>>> do simple comparison validation. So instead, we sort the
> expected
> >>>>>>>>>> and
> >>>>>>>>>> actual lines and then check for comparison. It's not perfect
> (XML
> >>>>>>>>>> attribute order can also be random), but generally good enough
> for
> >>>>>>>>>> what
> >>>>>>>>>> we're testing.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Thu, Sep 21, 2017 at 5:52 AM, David Goddard <goddard@acm.org
> >
> >>>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Thanks.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> I'm seeting a whole load of test failures in juneau-core parsing
> >>>>>>>>>>> (every
> >>>>>>>>>>> round trip test is failing for me). For example:
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> ByteArrayBase64SwapComboTest>ComboRoundTripTest.g32_parseRdf
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> XmlR:701->ComboRoundTripTest.testParse:205
> >>>>>>>>>>>>
> >>>>>>>>>>> ByteArray2d/parseRdfXmlR
> >>>>>>>>>>> parse-normal failed expected:<<rdf:RDF>[
> >>>>>>>>>>> <rdf:Seq>
> >>>>>>>>>>> <rdf:li>AQID</rdf:li>
> >>>>>>>>>>> <rdf:li>BAUG</rdf:li>
> >>>>>>>>>>> <rdf:li rdf:resource='http://www.w3.or
> >>>>>>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> </rdf:Seq>
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> </rdf:RDF>]
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> but was:<<rdf:RDF>[
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> <rdf:Seq>
> >>>>>>>>>>>>
> >>>>>>>>>>>> <rdf:li>AQID</rdf:li>
> >>>>>>>>>>> <rdf:li>BAUG</rdf:li>
> >>>>>>>>>>> <rdf:li rdf:resource='http://www.w3.or
> >>>>>>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> </rdf:Seq>
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> </rdf:RDF>
> >>>>>>>>>>>>
> >>>>>>>>>>> ]
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> The only consistent difference I see is that the final closing
> >>>>>>>>>>>> square
> >>>>>>>>>>>>
> >>>>>>>>>>>> bracket is appearing on a new line. Perhaps this is a
> character
> >>>>>>>>>>> encoding
> >>>>>>>>>>> issue (although I wouldn't rule out user error) - these tests
> fail
> >>>>>>>>>>> on
> >>>>>>>>>>> a
> >>>>>>>>>>> Windows platform, but work fine on a Mac.
> >>>>>>>>>>>
> >>>>>>>>>>> David
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On 20/09/2017 15:39, James Bognar wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> Indeed they are.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> I've fixed them in Git. Thanks David!
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <
> goddard@acm.org>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> I'm seeing a couple of issues with the Eclipse project names
> when
> >>>>>>>>>>>>
> >>>>>>>>>>>> importing a fresh clone into a workspace.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>> juneau-microservice/.project has <name>juneau-rest</name>
> >>>>>>>>>>>>> juneau-doc/.project has <name>juneau-marshall</name>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I'm assuming these are copy/paste errors arising from the
> >>>>>>>>>>>>> restructuring.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> David
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On 19/09/2017 18:26, Charles Mims wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> +1, with intermittent test failures in Apache Juneau
> >>>>>>>>>>>>> Microservice
> >>>>>>>>>>>>> Tests
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> MD5 (apache-juneau-6.4.0-incubating-src.zip) =
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb
> >>>>>>>>>>>>>> For me it failed on the 1st and 2nd try, passed on the 3rd.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <
> >>>>>>>>>>>>>> jamesbognar@apache.org>
> >>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I
> think we
> >>>>>>>>>>>>>> need
> >>>>>>>>>>>>>> to
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> handle this problem soon.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Darn.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> I'm thinking it must be an issue with Jetty since we just
> >>>>>>>>>>>>>>> upgraded
> >>>>>>>>>>>>>>> it.
> >>>>>>>>>>>>>>> From the Jetty side, the connection is open waiting
> for
> >>>>>>>>>>>>>>> data,
> >>>>>>>>>>>>>>> but
> >>>>>>>>>>>>>>> that's
> >>>>>>>>>>>>>>> all I know.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> I'll have to figure out how to use Fiddler and do some
> >>>>>>>>>>>>>>> low-level
> >>>>>>>>>>>>>>> debugging. It's really hard to reproduce though :-(
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <
> >>>>>>>>>>>>>>> yidonguk@gmail.com
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> +1
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> SHA1, MD5 Checksum OK
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Maven Build OK
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I
> think
> >>>>>>>>>>>>>>>> we
> >>>>>>>>>>>>>>>> need
> >>>>>>>>>>>>>>>> to
> >>>>>>>>>>>>>>>> handle this problem soon.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> [INFO] Reactor Summary:
> >>>>>>>>>>>>>>>> [INFO]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau (incubating)
> .........................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 10.521 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau - Core APIs
> ..........................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 0.737 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau Marshall
> .............................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 45.444 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau Marshal RDF
> ..........................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 3.558 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau Data Transfer Objects
> ................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 6.813 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau Core ..............................
> ...
> >>>>>>>>>>>>>>>> SUCCESS [
> >>>>>>>>>>>>>>>> 1.025 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau Config File API
> ......................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 1.928 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau Core Tests
> ...........................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [01:04
> >>>>>>>>>>>>>>>> min]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau - REST APIs
> ..........................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 0.080 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau REST Servlet API
> .....................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 2.331 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau REST JAX/RS API
> ......................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 0.476 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau REST Client API
> ......................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 1.005 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau - Microservice APIs
> ..................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 0.068 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Server
> ..................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 1.588 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Template
> ................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 1.243 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau - Examples
> ...........................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 0.183 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau REST Examples
> ........................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 8.512 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Tests
> ...................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 24.522 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau Core Examples
> ........................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 0.287 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau Javadocs
> .............................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 0.617 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau - Release Engineering
> ................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 0.040 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau UberJar
> ..............................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 1.008 s]
> >>>>>>>>>>>>>>>> [INFO] Apache Juneau Distribution
> .........................
> >>>>>>>>>>>>>>>> SUCCESS
> >>>>>>>>>>>>>>>> [
> >>>>>>>>>>>>>>>> 0.768 s]
> >>>>>>>>>>>>>>>> [INFO] ------------------------------
> >>>>>>>>>>>>>>>> ------------------------------
> >>>>>>>>>>>>>>>> ------------
> >>>>>>>>>>>>>>>> [INFO] BUILD SUCCESS
> >>>>>>>>>>>>>>>> [INFO] ------------------------------
> >>>>>>>>>>>>>>>> ------------------------------
> >>>>>>>>>>>>>>>> ------------
> >>>>>>>>>>>>>>>> [INFO] Total time: 03:01 min
> >>>>>>>>>>>>>>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
> >>>>>>>>>>>>>>>> [INFO] Final Memory: 87M/773M
> >>>>>>>>>>>>>>>> [INFO] ------------------------------
> >>>>>>>>>>>>>>>> ------------------------------
> >>>>>>>>>>>>>>>> ------------
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Raphi D Lee, yidonguk@gmail.com
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> 2017. 9. 18. 오전 9:54, James Bognar <
> jamesbognar@apache.org>
> >>>>>>>>>>>>>>>> 작성:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I am pleased to be calling this vote for the source
> release
> >>>>>>>>>>>>>>>> of
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Apache
> >>>>>>>>>>>>>>>>> Juneau 6.4.0-incubating RC2.
> >>>>>>>>>>>>>>>>> This includes some fixes for bugs found in RC1 and some
> >>>>>>>>>>>>>>>>> packaging
> >>>>>>>>>>>>>>>>> changes
> >>>>>>>>>>>>>>>>> for the example and template projects.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> The list of new features can be found here:
> >>>>>>>>>>>>>>>>> http://juneau.incubator.apache.org/site/apidocs/
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> overview-summary.html#6.4.0
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> The binaries are available at:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> binaries/juneau-6.4.0-incubating-RC2/
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> The release candidate to be voted over is available at:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> source/juneau-6.4.0-incubating-RC2/
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> SHA-1 checksums:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81
> apache-juneau-6.4.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> 0-incubating-src.zip
> >>>>>>>>>>>>>>>>> c3d4a1d7c21142a4006876419729d9f0c352203e
> apache-juneau-6.4.
> >>>>>>>>>>>>>>>>> 0-incubating-bin.zip
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> MD5 checksums:
> >>>>>>>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb
> >>>>>>>>>>>>>>>>> apache-juneau-6.4.0-incubating
> >>>>>>>>>>>>>>>>> -src.zip
> >>>>>>>>>>>>>>>>> 4e96d5047c0e9f03f0def2d017521f13
> >>>>>>>>>>>>>>>>> apache-juneau-6.4.0-incubating
> >>>>>>>>>>>>>>>>> -bin.zip
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Build the release candidate using:
> >>>>>>>>>>>>>>>>> mvn clean install
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> The release candidate is signed with a GPG key available
> at:
> >>>>>>>>>>>>>>>>> https://dist.apache.org/repos/
> >>>>>>>>>>>>>>>>> dist/release/incubator/juneau/
> >>>>>>>>>>>>>>>>> KEYS
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> A staged Maven repository is available for review at:
> >>>>>>>>>>>>>>>>> https://repository.apache.org/
> >>>>>>>>>>>>>>>>> content/repositories/orgapache
> >>>>>>>>>>>>>>>>> juneau-1016/
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> The Git commit for this release is...
> >>>>>>>>>>>>>>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> juneau.git;a=commit;h=6de99819
> >>>>>>>>>>>>>>>>> 3807eeec40e6f297f6b70222552f3b
> >>>>>>>>>>>>>>>>> 37
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b702
> 22552f3b
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> 37>*
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Please vote on releasing this package as:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Apache Juneau 6.4.0-incubating
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> This vote will be open until 20-Sep-2017 9:00pm EST and
> >>>>>>>>>>>>>>>>> passes
> >>>>>>>>>>>>>>>>> if a
> >>>>>>>>>>>>>>>>> majority of at least three +1 Apache Juneau PPMC votes
> are
> >>>>>>>>>>>>>>>>> cast.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> [ ] +1 Release this package
> >>>>>>>>>>>>>>>>> [ ] 0 I don't feel strongly about it, but don't object
> >>>>>>>>>>>>>>>>> [ ] -1 Do not release this package because...
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Anyone can participate in testing and voting, not just
> >>>>>>>>>>>>>>>>> committers,
> >>>>>>>>>>>>>>>>> please
> >>>>>>>>>>>>>>>>> feel free to try out the release candidate and provide
> your
> >>>>>>>>>>>>>>>>> votes.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
>
>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by David Goddard <go...@acm.org>.
Hi,
Sorry for the delay, I’m travelling away from my Windows test platform so had to knock up a VM. Definitely line 473. Here’s a stack trace:
org.apache.juneau.BeanRuntimeException: interface org.apache.juneau.BeanConfigTest$A is not visible from class loader
at org.apache.juneau.BeanSession.newBean(BeanSession.java:858)
at org.apache.juneau.BeanSession.newBeanMap(BeanSession.java:810)
at org.apache.juneau.BeanSession.newBeanMap(BeanSession.java:790)
at org.apache.juneau.BeanConfigTest.testProxyHandler(BeanConfigTest.java:473)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:202)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:155)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:81)
at org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.runSuitesInProcess(InPluginVMSurefireStarter.java:82)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1010)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:862)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:755)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: java.lang.IllegalArgumentException: interface org.apache.juneau.BeanConfigTest$A is not visible from class loader
at java.lang.reflect.Proxy$ProxyClassFactory.apply(Proxy.java:581)
at java.lang.reflect.Proxy$ProxyClassFactory.apply(Proxy.java:557)
at java.lang.reflect.WeakCache$Factory.get(WeakCache.java:230)
at java.lang.reflect.WeakCache.get(WeakCache.java:127)
at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:419)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:719)
at org.apache.juneau.BeanMeta.newBean(BeanMeta.java:723)
at org.apache.juneau.BeanSession.newBean(BeanSession.java:851)
... 57 more
> On 24 Sep 2017, at 18:40, James Bognar <ja...@apache.org> wrote:
>
> Hi David,
>
> Is that really occurring on line 473? Could you catch the exception and
> print a longer stack trace?
>
> Thanks!
>
> On Sun, Sep 24, 2017 at 4:31 AM, David Goddard <go...@acm.org> wrote:
>
>> Hi,
>>
>> Yes, this code now works:
>>
>> @Test
>> public void test() {
>> BeanSession session = ps.getBeanContext()
>> .createSession(new BeanSessionArgs(null, sessionLocale,
>> sessionTimeZone, null));
>> String actual = session.convertToType(calendar, String.class);
>> if (expected.indexOf('(') == -1)
>> // Fix JVM-specific formatting difference
>> actual.replaceAll(" \\([^\\)]+\\)",
>> "").replaceAll("\\([^\\)]+\\) ", "");
>> assertEquals(expected, actual);
>> Object c2 = session.convertToType(actual, calendar.getClass());
>> String actual2 = session.convertToType(c2, String.class);
>> if (expected.indexOf('(') == -1)
>> // Fix JVM-specific formatting difference
>> actual2 = actual2.replaceAll("\\([^\\)]+\\) ", "");
>> assertEquals(expected, actual2);
>> }
>>
>> However, still one more error in my Windows environment though :(
>>
>> #############################
>> Tests run: 11, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.031 sec
>> <<< FAILURE! - in org.apache.juneau.BeanConfigTest
>> testProxyHandler(org.apache.juneau.BeanConfigTest) Time elapsed: 0 sec
>> <<< ERROR!
>> org.apache.juneau.BeanRuntimeException: interface
>> org.apache.juneau.BeanConfigTest$A is not visible from class loader
>> at org.apache.juneau.BeanConfigTest.testProxyHandler(BeanConfig
>> Test.java:473)
>> Caused by: java.lang.IllegalArgumentException: interface
>> org.apache.juneau.BeanConfigTest$A is not visible from class loader
>> at org.apache.juneau.BeanConfigTest.testProxyHandler(BeanConfig
>> Test.java:473)
>> #############################
>>
>> I'm wondering if this is an issue specific to my setup. When I have a
>> chance (I am travelling at the moment), I'll set up an Oracle JVM in my
>> Windows test environment and try a build with that.
>>
>> David
>>
>> On 23/09/2017 21:35, James Bognar wrote:
>>
>>> Hi David,
>>>
>>> How about this?
>>> if (expected.indexOf('(') == -1)
>>> actual.replaceAll(" \\([^\\)]+\\)", "").replaceAll("\\([^\\)]+\\) ",
>>> "");
>>>
>>>
>>> On Fri, Sep 22, 2017 at 3:08 PM, David Goddard <go...@acm.org> wrote:
>>>
>>> Most things are in some way IBM's fault :)
>>>>
>>>> Trying both variants of your fix gives similar results. Better in both
>>>> cases, but not quite there. Details below.
>>>>
>>>> It looks to me on a quick read that those cases that now fail are failing
>>>> because they *do* expect a value between the parentheses, and of course
>>>> the
>>>> fix strips that out. For example, here's test 205:
>>>>
>>>> { "205", testDate, CalendarSwap.DateTimeLong.class, "en_UK",
>>>> Locale.KOREA, null, null, "2001년 3월 3일 (토) 오전 10시 11분 12초" },
>>>>
>>>> I guess we could bend the test a little further by conditionally only
>>>> stripping out the parenthetical content if the expected value doesn't
>>>> contain values in parentheses itself, but that be regarded as a fix too
>>>> far...
>>>>
>>>> #######################
>>>>
>>>> actual = actual.replaceAll("\\([^\\)]+\\) ", "");
>>>> actual2 = actual2.replaceAll("\\([^\\)]+\\) ", "");
>>>>
>>>> ...leads to:
>>>>
>>>> Tests run: 460, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 19.485
>>>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
>>>> test[205](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>> elapsed:
>>>> 0.004 sec <<< FAILURE!
>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
>>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>>>> edDatesTest.java:660)
>>>>
>>>> test[435](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>> elapsed:
>>>> 0.001 sec <<< FAILURE!
>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
>>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>>>> edDatesTest.java:660)
>>>>
>>>> With the different location for the space in the regexp, I get a longer
>>>> list of failures:
>>>>
>>>> #######################
>>>>
>>>> actual = actual.replaceAll(" \\([^\\)]+\\)", "");
>>>> actual2 = actual2.replaceAll(" \\([^\\)]+\\)", "");
>>>>
>>>> ... leads to:
>>>>
>>>> Running org.apache.juneau.transforms.LocalizedDatesTest
>>>> Tests run: 460, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 0.189
>>>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
>>>> test[125](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>> elapsed:
>>>> 0.003 sec <<< FAILURE!
>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3?[ (?)]> but was:<2001?
>>>> 3? 3?[]>
>>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>>>> edDatesTest.java:660)
>>>>
>>>> test[205](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>> elapsed:
>>>> 0 sec <<< FAILURE!
>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
>>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>>>> edDatesTest.java:660)
>>>>
>>>> test[355](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>> elapsed:
>>>> 0 sec <<< FAILURE!
>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3?[ (?)]> but was:<2001?
>>>> 3? 3?[]>
>>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>>>> edDatesTest.java:660)
>>>>
>>>> test[435](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>> elapsed:
>>>> 0.001 sec <<< FAILURE!
>>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
>>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>>>> edDatesTest.java:660)
>>>>
>>>> #######################
>>>>
>>>>
>>>>
>>>>
>>>> On 22/09/2017 00:05, James Bognar wrote:
>>>>
>>>> Ah...so we can blame IBM :-)
>>>>>
>>>>> Can you see if swapping the location of the space in the regular
>>>>> expressions fixes all the tests?
>>>>> actual = actual.replaceAll(" \\([^\\)]+\\)", "");
>>>>>
>>>>> On Thu, Sep 21, 2017 at 6:01 PM, David Goddard <go...@acm.org> wrote:
>>>>>
>>>>> Just to add:
>>>>>
>>>>>>
>>>>>> Maybe it's JVM vendor-specific behavior?
>>>>>>
>>>>>>>
>>>>>>>
>>>>>> Yes, I've now tested again after changing from an IBM JRE to an Oracle
>>>>>> JRE
>>>>>> - this resolves the problem. It looks like this is specific to the IBM
>>>>>> JRE
>>>>>> then. My Mac testing was done with an Oracle JRE, so I think this is
>>>>>> probably JVM-specific rather than OS-specific.
>>>>>>
>>>>>>
>>>>>> On 21/09/2017 23:46, David Goddard wrote:
>>>>>>
>>>>>> Actual text is:
>>>>>>
>>>>>>>
>>>>>>> 2001年3月3日 (土曜日)
>>>>>>> (I've attached a copy as a text file also)
>>>>>>>
>>>>>>> In this case, I it looks like the value between the parenthesis is the
>>>>>>> day name, "Saturday". So the expected value is just the date (2001年3月
>>>>>>> 3日),
>>>>>>> but the day is being added in the process.
>>>>>>>
>>>>>>>
>>>>>>> On 21/09/2017 22:45, James Bognar wrote:
>>>>>>>
>>>>>>> Interesting. So the behavior of...
>>>>>>>
>>>>>>>>
>>>>>>>> DateFormat.getDateInstance(DateFormat.FULL, locale).format(date);
>>>>>>>> DateFormat.getDateTimeInstance(DateFormat.FULL, DateFormat.FULL,
>>>>>>>> locale
>>>>>>>> ).format(date);
>>>>>>>>
>>>>>>>> ...returns different formats depending on the OS. Lovely.
>>>>>>>>
>>>>>>>> Maybe it's JVM vendor-specific behavior?
>>>>>>>>
>>>>>>>> I'm curious to know what's in those parentheses...
>>>>>>>> 2001?3?3? [*(???)* ]10?11?12? GMT
>>>>>>>>
>>>>>>>> Might give me something to google for.
>>>>>>>>
>>>>>>>> It's technically a test-only issue. We can probably 'fix' the
>>>>>>>> testcase
>>>>>>>> by
>>>>>>>> just stripping out the formatting difference...
>>>>>>>>
>>>>>>>> @Test
>>>>>>>> public void test() {
>>>>>>>> BeanSession session = ps.getBeanContext().createSession(new
>>>>>>>> BeanSessionArgs(null, sessionLocale, sessionTimeZone, null));
>>>>>>>> String actual = session.convertToType(calendar, String.class);
>>>>>>>> *actual = actual.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>>>>>>>> Windows-specific
>>>>>>>> formatting difference*
>>>>>>>> assertEquals(expected, actual);
>>>>>>>> Object c2 = session.convertToType(actual, calendar.getClass());
>>>>>>>> String actual2 = session.convertToType(c2, String.class);
>>>>>>>> *actual2 = actual2.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>>>>>>>> Windows-specific formatting difference*
>>>>>>>> assertEquals(expected, actual2);
>>>>>>>> }
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Sep 21, 2017 at 3:11 PM, David Goddard <go...@acm.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>>
>>>>>>>>> Yes, that fixed it, thanks. It also still tests OK on my Mac after
>>>>>>>>> the
>>>>>>>>> change.
>>>>>>>>>
>>>>>>>>> I'm now running into some further test issues, also on Windows only.
>>>>>>>>>
>>>>>>>>> ########################
>>>>>>>>>
>>>>>>>>> Tests run: 460, Failures: 16, Errors: 0, Skipped: 0, Time elapsed:
>>>>>>>>> 0.247
>>>>>>>>> sec <<< FAILURE! - in org.apache.juneau.transforms.L
>>>>>>>>> ocalizedDatesTest
>>>>>>>>> test[111](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>>>>> elapsed:
>>>>>>>>> 0.015 sec <<< FAILURE!
>>>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3?[]> but
>>>>>>>>> was:<2001?3?3?[
>>>>>>>>> (???)]>
>>>>>>>>> at org.apache.juneau.transforms.L
>>>>>>>>> ocalizedDatesTest.test(Localiz
>>>>>>>>> edDatesTest.java:645)
>>>>>>>>>
>>>>>>>>> [...]
>>>>>>>>> test[423](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>>>>> elapsed:
>>>>>>>>> 0 sec <<< FAILURE!
>>>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT>
>>>>>>>>> but
>>>>>>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>>>>>>>> at org.apache.juneau.transforms.L
>>>>>>>>> ocalizedDatesTest.test(Localiz
>>>>>>>>> edDatesTest.java:645)
>>>>>>>>>
>>>>>>>>> test[424](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>>>>> elapsed:
>>>>>>>>> 0 sec <<< FAILURE!
>>>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT>
>>>>>>>>> but
>>>>>>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>>>>>>>> at org.apache.juneau.transforms.L
>>>>>>>>> ocalizedDatesTest.test(Localiz
>>>>>>>>> edDatesTest.java:645)
>>>>>>>>>
>>>>>>>>> ########################
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> These are specific to date swap tests in Japanese & Korean:
>>>>>>>>>
>>>>>>>>> { "421", testDate.getTime(), DateSwap.DateTimeFull.class, "ja_JP",
>>>>>>>>> null,
>>>>>>>>> null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>>>> { "422", testDate.getTime(), DateSwap.DateTimeFull.class,
>>>>>>>>> Locale.JAPAN,
>>>>>>>>> null, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>>>> { "423", testDate.getTime(), DateSwap.DateTimeFull.class, null,
>>>>>>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>>>> { "424", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>>>>>>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>>>> { "425", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>>>>>>>>> Locale.KOREA, null, null, "2001ë…„ 3ì›” 3ì�¼ í† ìš”ì�¼ ì˜¤ì „ 10ì‹œ
>>>>>>>>> 11분
>>>>>>>>> 12ì´ˆ GMT" },
>>>>>>>>> etc.
>>>>>>>>>
>>>>>>>>> All the date swaps where the test date contains Japanese or Korean
>>>>>>>>> characters in the date part fail in this way. I initially thought
>>>>>>>>> it
>>>>>>>>> was
>>>>>>>>> the code page of the file, but I've changed to UTF-8 from the
>>>>>>>>> default
>>>>>>>>> and
>>>>>>>>> this didn't resolve this for me. Again, this is specific to my
>>>>>>>>> Windows
>>>>>>>>> platform - all is fine on Mac.
>>>>>>>>>
>>>>>>>>> Given that this is a build test error, and specific to one platform
>>>>>>>>> (and
>>>>>>>>> possibly one machine), I'm not sure that it is a fatal problem for
>>>>>>>>> the
>>>>>>>>> release.
>>>>>>>>>
>>>>>>>>> David
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 21/09/2017 14:55, James Bognar wrote:
>>>>>>>>>
>>>>>>>>> Hi David,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> I don't have a Windows machine anymore :-(
>>>>>>>>>>
>>>>>>>>>> It looks like a test issue. Is it only RDF tests that are failing?
>>>>>>>>>>
>>>>>>>>>> Can you find line 484 in org.apache.juneau.TestUtils in
>>>>>>>>>> juneau-core-tests...
>>>>>>>>>>
>>>>>>>>>> String[] e = expected.trim().split("\n"), a =
>>>>>>>>>> actual.trim().split("\n");
>>>>>>>>>>
>>>>>>>>>> ...and change it to this?...
>>>>>>>>>>
>>>>>>>>>> String[] e = expected.trim().split("[\r\n]+"), a =
>>>>>>>>>> actual.trim().split(
>>>>>>>>>> "[\r\n]+");
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Background on this method: Since Jena does not guarantee the order
>>>>>>>>>> of
>>>>>>>>>> entries in the generated RDF (it's pretty much random), it's
>>>>>>>>>> difficult
>>>>>>>>>> to
>>>>>>>>>> do simple comparison validation. So instead, we sort the expected
>>>>>>>>>> and
>>>>>>>>>> actual lines and then check for comparison. It's not perfect (XML
>>>>>>>>>> attribute order can also be random), but generally good enough for
>>>>>>>>>> what
>>>>>>>>>> we're testing.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, Sep 21, 2017 at 5:52 AM, David Goddard <go...@acm.org>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Thanks.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I'm seeting a whole load of test failures in juneau-core parsing
>>>>>>>>>>> (every
>>>>>>>>>>> round trip test is failing for me). For example:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ByteArrayBase64SwapComboTest>ComboRoundTripTest.g32_parseRdf
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> XmlR:701->ComboRoundTripTest.testParse:205
>>>>>>>>>>>>
>>>>>>>>>>> ByteArray2d/parseRdfXmlR
>>>>>>>>>>> parse-normal failed expected:<<rdf:RDF>[
>>>>>>>>>>> <rdf:Seq>
>>>>>>>>>>> <rdf:li>AQID</rdf:li>
>>>>>>>>>>> <rdf:li>BAUG</rdf:li>
>>>>>>>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>>>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> </rdf:Seq>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> </rdf:RDF>]
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> but was:<<rdf:RDF>[
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> <rdf:Seq>
>>>>>>>>>>>>
>>>>>>>>>>>> <rdf:li>AQID</rdf:li>
>>>>>>>>>>> <rdf:li>BAUG</rdf:li>
>>>>>>>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>>>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> </rdf:Seq>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> </rdf:RDF>
>>>>>>>>>>>>
>>>>>>>>>>> ]
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The only consistent difference I see is that the final closing
>>>>>>>>>>>> square
>>>>>>>>>>>>
>>>>>>>>>>>> bracket is appearing on a new line. Perhaps this is a character
>>>>>>>>>>> encoding
>>>>>>>>>>> issue (although I wouldn't rule out user error) - these tests fail
>>>>>>>>>>> on
>>>>>>>>>>> a
>>>>>>>>>>> Windows platform, but work fine on a Mac.
>>>>>>>>>>>
>>>>>>>>>>> David
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 20/09/2017 15:39, James Bognar wrote:
>>>>>>>>>>>
>>>>>>>>>>> Indeed they are.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I've fixed them in Git. Thanks David!
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <go...@acm.org>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> I'm seeing a couple of issues with the Eclipse project names when
>>>>>>>>>>>>
>>>>>>>>>>>> importing a fresh clone into a workspace.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> juneau-microservice/.project has <name>juneau-rest</name>
>>>>>>>>>>>>> juneau-doc/.project has <name>juneau-marshall</name>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I'm assuming these are copy/paste errors arising from the
>>>>>>>>>>>>> restructuring.
>>>>>>>>>>>>>
>>>>>>>>>>>>> David
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 19/09/2017 18:26, Charles Mims wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> +1, with intermittent test failures in Apache Juneau
>>>>>>>>>>>>> Microservice
>>>>>>>>>>>>> Tests
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> MD5 (apache-juneau-6.4.0-incubating-src.zip) =
>>>>>>>>>>>>>
>>>>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>>>>>>>>>> For me it failed on the 1st and 2nd try, passed on the 3rd.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <
>>>>>>>>>>>>>> jamesbognar@apache.org>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we
>>>>>>>>>>>>>> need
>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> handle this problem soon.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Darn.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I'm thinking it must be an issue with Jetty since we just
>>>>>>>>>>>>>>> upgraded
>>>>>>>>>>>>>>> it.
>>>>>>>>>>>>>>> From the Jetty side, the connection is open waiting for
>>>>>>>>>>>>>>> data,
>>>>>>>>>>>>>>> but
>>>>>>>>>>>>>>> that's
>>>>>>>>>>>>>>> all I know.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I'll have to figure out how to use Fiddler and do some
>>>>>>>>>>>>>>> low-level
>>>>>>>>>>>>>>> debugging. It's really hard to reproduce though :-(
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <
>>>>>>>>>>>>>>> yidonguk@gmail.com
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> SHA1, MD5 Checksum OK
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Maven Build OK
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think
>>>>>>>>>>>>>>>> we
>>>>>>>>>>>>>>>> need
>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>> handle this problem soon.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [INFO] Reactor Summary:
>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau (incubating) .........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 10.521 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau - Core APIs ..........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.737 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Marshall .............................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 45.444 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Marshal RDF ..........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 3.558 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Data Transfer Objects ................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 6.813 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Core .................................
>>>>>>>>>>>>>>>> SUCCESS [
>>>>>>>>>>>>>>>> 1.025 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Config File API ......................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 1.928 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Core Tests ...........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [01:04
>>>>>>>>>>>>>>>> min]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau - REST APIs ..........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.080 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau REST Servlet API .....................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 2.331 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau REST JAX/RS API ......................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.476 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau REST Client API ......................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 1.005 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau - Microservice APIs ..................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.068 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Server ..................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 1.588 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Template ................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 1.243 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau - Examples ...........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.183 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau REST Examples ........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 8.512 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Tests ...................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 24.522 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Core Examples ........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.287 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Javadocs .............................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.617 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau - Release Engineering ................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.040 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau UberJar ..............................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 1.008 s]
>>>>>>>>>>>>>>>> [INFO] Apache Juneau Distribution .........................
>>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>>> 0.768 s]
>>>>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>>>> ------------
>>>>>>>>>>>>>>>> [INFO] BUILD SUCCESS
>>>>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>>>> ------------
>>>>>>>>>>>>>>>> [INFO] Total time: 03:01 min
>>>>>>>>>>>>>>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>>>>>>>>>>>>>>>> [INFO] Final Memory: 87M/773M
>>>>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>>>> ------------
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Raphi D Lee, yidonguk@gmail.com
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org>
>>>>>>>>>>>>>>>> 작성:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I am pleased to be calling this vote for the source release
>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Apache
>>>>>>>>>>>>>>>>> Juneau 6.4.0-incubating RC2.
>>>>>>>>>>>>>>>>> This includes some fixes for bugs found in RC1 and some
>>>>>>>>>>>>>>>>> packaging
>>>>>>>>>>>>>>>>> changes
>>>>>>>>>>>>>>>>> for the example and template projects.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The list of new features can be found here:
>>>>>>>>>>>>>>>>> http://juneau.incubator.apache.org/site/apidocs/
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> overview-summary.html#6.4.0
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The binaries are available at:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> binaries/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The release candidate to be voted over is available at:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> source/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> SHA-1 checksums:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 0-incubating-src.zip
>>>>>>>>>>>>>>>>> c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
>>>>>>>>>>>>>>>>> 0-incubating-bin.zip
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> MD5 checksums:
>>>>>>>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>>>>>>>>>>>>> apache-juneau-6.4.0-incubating
>>>>>>>>>>>>>>>>> -src.zip
>>>>>>>>>>>>>>>>> 4e96d5047c0e9f03f0def2d017521f13
>>>>>>>>>>>>>>>>> apache-juneau-6.4.0-incubating
>>>>>>>>>>>>>>>>> -bin.zip
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Build the release candidate using:
>>>>>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The release candidate is signed with a GPG key available at:
>>>>>>>>>>>>>>>>> https://dist.apache.org/repos/
>>>>>>>>>>>>>>>>> dist/release/incubator/juneau/
>>>>>>>>>>>>>>>>> KEYS
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> A staged Maven repository is available for review at:
>>>>>>>>>>>>>>>>> https://repository.apache.org/
>>>>>>>>>>>>>>>>> content/repositories/orgapache
>>>>>>>>>>>>>>>>> juneau-1016/
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The Git commit for this release is...
>>>>>>>>>>>>>>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> juneau.git;a=commit;h=6de99819
>>>>>>>>>>>>>>>>> 3807eeec40e6f297f6b70222552f3b
>>>>>>>>>>>>>>>>> 37
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 37>*
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Please vote on releasing this package as:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Apache Juneau 6.4.0-incubating
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> This vote will be open until 20-Sep-2017 9:00pm EST and
>>>>>>>>>>>>>>>>> passes
>>>>>>>>>>>>>>>>> if a
>>>>>>>>>>>>>>>>> majority of at least three +1 Apache Juneau PPMC votes are
>>>>>>>>>>>>>>>>> cast.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> [ ] +1 Release this package
>>>>>>>>>>>>>>>>> [ ] 0 I don't feel strongly about it, but don't object
>>>>>>>>>>>>>>>>> [ ] -1 Do not release this package because...
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Anyone can participate in testing and voting, not just
>>>>>>>>>>>>>>>>> committers,
>>>>>>>>>>>>>>>>> please
>>>>>>>>>>>>>>>>> feel free to try out the release candidate and provide your
>>>>>>>>>>>>>>>>> votes.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by James Bognar <ja...@apache.org>.
Hi David,
Is that really occurring on line 473? Could you catch the exception and
print a longer stack trace?
Thanks!
On Sun, Sep 24, 2017 at 4:31 AM, David Goddard <go...@acm.org> wrote:
> Hi,
>
> Yes, this code now works:
>
> @Test
> public void test() {
> BeanSession session = ps.getBeanContext()
> .createSession(new BeanSessionArgs(null, sessionLocale,
> sessionTimeZone, null));
> String actual = session.convertToType(calendar, String.class);
> if (expected.indexOf('(') == -1)
> // Fix JVM-specific formatting difference
> actual.replaceAll(" \\([^\\)]+\\)",
> "").replaceAll("\\([^\\)]+\\) ", "");
> assertEquals(expected, actual);
> Object c2 = session.convertToType(actual, calendar.getClass());
> String actual2 = session.convertToType(c2, String.class);
> if (expected.indexOf('(') == -1)
> // Fix JVM-specific formatting difference
> actual2 = actual2.replaceAll("\\([^\\)]+\\) ", "");
> assertEquals(expected, actual2);
> }
>
> However, still one more error in my Windows environment though :(
>
> #############################
> Tests run: 11, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.031 sec
> <<< FAILURE! - in org.apache.juneau.BeanConfigTest
> testProxyHandler(org.apache.juneau.BeanConfigTest) Time elapsed: 0 sec
> <<< ERROR!
> org.apache.juneau.BeanRuntimeException: interface
> org.apache.juneau.BeanConfigTest$A is not visible from class loader
> at org.apache.juneau.BeanConfigTest.testProxyHandler(BeanConfig
> Test.java:473)
> Caused by: java.lang.IllegalArgumentException: interface
> org.apache.juneau.BeanConfigTest$A is not visible from class loader
> at org.apache.juneau.BeanConfigTest.testProxyHandler(BeanConfig
> Test.java:473)
> #############################
>
> I'm wondering if this is an issue specific to my setup. When I have a
> chance (I am travelling at the moment), I'll set up an Oracle JVM in my
> Windows test environment and try a build with that.
>
> David
>
> On 23/09/2017 21:35, James Bognar wrote:
>
>> Hi David,
>>
>> How about this?
>> if (expected.indexOf('(') == -1)
>> actual.replaceAll(" \\([^\\)]+\\)", "").replaceAll("\\([^\\)]+\\) ",
>> "");
>>
>>
>> On Fri, Sep 22, 2017 at 3:08 PM, David Goddard <go...@acm.org> wrote:
>>
>> Most things are in some way IBM's fault :)
>>>
>>> Trying both variants of your fix gives similar results. Better in both
>>> cases, but not quite there. Details below.
>>>
>>> It looks to me on a quick read that those cases that now fail are failing
>>> because they *do* expect a value between the parentheses, and of course
>>> the
>>> fix strips that out. For example, here's test 205:
>>>
>>> { "205", testDate, CalendarSwap.DateTimeLong.class, "en_UK",
>>> Locale.KOREA, null, null, "2001년 3월 3일 (토) 오전 10시 11분 12초" },
>>>
>>> I guess we could bend the test a little further by conditionally only
>>> stripping out the parenthetical content if the expected value doesn't
>>> contain values in parentheses itself, but that be regarded as a fix too
>>> far...
>>>
>>> #######################
>>>
>>> actual = actual.replaceAll("\\([^\\)]+\\) ", "");
>>> actual2 = actual2.replaceAll("\\([^\\)]+\\) ", "");
>>>
>>> ...leads to:
>>>
>>> Tests run: 460, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 19.485
>>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
>>> test[205](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>> elapsed:
>>> 0.004 sec <<< FAILURE!
>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>>> edDatesTest.java:660)
>>>
>>> test[435](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>> elapsed:
>>> 0.001 sec <<< FAILURE!
>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>>> edDatesTest.java:660)
>>>
>>> With the different location for the space in the regexp, I get a longer
>>> list of failures:
>>>
>>> #######################
>>>
>>> actual = actual.replaceAll(" \\([^\\)]+\\)", "");
>>> actual2 = actual2.replaceAll(" \\([^\\)]+\\)", "");
>>>
>>> ... leads to:
>>>
>>> Running org.apache.juneau.transforms.LocalizedDatesTest
>>> Tests run: 460, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 0.189
>>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
>>> test[125](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>> elapsed:
>>> 0.003 sec <<< FAILURE!
>>> org.junit.ComparisonFailure: expected:<2001? 3? 3?[ (?)]> but was:<2001?
>>> 3? 3?[]>
>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>>> edDatesTest.java:660)
>>>
>>> test[205](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>> elapsed:
>>> 0 sec <<< FAILURE!
>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>>> edDatesTest.java:660)
>>>
>>> test[355](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>> elapsed:
>>> 0 sec <<< FAILURE!
>>> org.junit.ComparisonFailure: expected:<2001? 3? 3?[ (?)]> but was:<2001?
>>> 3? 3?[]>
>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>>> edDatesTest.java:660)
>>>
>>> test[435](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>> elapsed:
>>> 0.001 sec <<< FAILURE!
>>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
>>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>>> edDatesTest.java:660)
>>>
>>> #######################
>>>
>>>
>>>
>>>
>>> On 22/09/2017 00:05, James Bognar wrote:
>>>
>>> Ah...so we can blame IBM :-)
>>>>
>>>> Can you see if swapping the location of the space in the regular
>>>> expressions fixes all the tests?
>>>> actual = actual.replaceAll(" \\([^\\)]+\\)", "");
>>>>
>>>> On Thu, Sep 21, 2017 at 6:01 PM, David Goddard <go...@acm.org> wrote:
>>>>
>>>> Just to add:
>>>>
>>>>>
>>>>> Maybe it's JVM vendor-specific behavior?
>>>>>
>>>>>>
>>>>>>
>>>>> Yes, I've now tested again after changing from an IBM JRE to an Oracle
>>>>> JRE
>>>>> - this resolves the problem. It looks like this is specific to the IBM
>>>>> JRE
>>>>> then. My Mac testing was done with an Oracle JRE, so I think this is
>>>>> probably JVM-specific rather than OS-specific.
>>>>>
>>>>>
>>>>> On 21/09/2017 23:46, David Goddard wrote:
>>>>>
>>>>> Actual text is:
>>>>>
>>>>>>
>>>>>> 2001年3月3日 (土曜日)
>>>>>> (I've attached a copy as a text file also)
>>>>>>
>>>>>> In this case, I it looks like the value between the parenthesis is the
>>>>>> day name, "Saturday". So the expected value is just the date (2001年3月
>>>>>> 3日),
>>>>>> but the day is being added in the process.
>>>>>>
>>>>>>
>>>>>> On 21/09/2017 22:45, James Bognar wrote:
>>>>>>
>>>>>> Interesting. So the behavior of...
>>>>>>
>>>>>>>
>>>>>>> DateFormat.getDateInstance(DateFormat.FULL, locale).format(date);
>>>>>>> DateFormat.getDateTimeInstance(DateFormat.FULL, DateFormat.FULL,
>>>>>>> locale
>>>>>>> ).format(date);
>>>>>>>
>>>>>>> ...returns different formats depending on the OS. Lovely.
>>>>>>>
>>>>>>> Maybe it's JVM vendor-specific behavior?
>>>>>>>
>>>>>>> I'm curious to know what's in those parentheses...
>>>>>>> 2001?3?3? [*(???)* ]10?11?12? GMT
>>>>>>>
>>>>>>> Might give me something to google for.
>>>>>>>
>>>>>>> It's technically a test-only issue. We can probably 'fix' the
>>>>>>> testcase
>>>>>>> by
>>>>>>> just stripping out the formatting difference...
>>>>>>>
>>>>>>> @Test
>>>>>>> public void test() {
>>>>>>> BeanSession session = ps.getBeanContext().createSession(new
>>>>>>> BeanSessionArgs(null, sessionLocale, sessionTimeZone, null));
>>>>>>> String actual = session.convertToType(calendar, String.class);
>>>>>>> *actual = actual.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>>>>>>> Windows-specific
>>>>>>> formatting difference*
>>>>>>> assertEquals(expected, actual);
>>>>>>> Object c2 = session.convertToType(actual, calendar.getClass());
>>>>>>> String actual2 = session.convertToType(c2, String.class);
>>>>>>> *actual2 = actual2.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>>>>>>> Windows-specific formatting difference*
>>>>>>> assertEquals(expected, actual2);
>>>>>>> }
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Sep 21, 2017 at 3:11 PM, David Goddard <go...@acm.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>>
>>>>>>>> Yes, that fixed it, thanks. It also still tests OK on my Mac after
>>>>>>>> the
>>>>>>>> change.
>>>>>>>>
>>>>>>>> I'm now running into some further test issues, also on Windows only.
>>>>>>>>
>>>>>>>> ########################
>>>>>>>>
>>>>>>>> Tests run: 460, Failures: 16, Errors: 0, Skipped: 0, Time elapsed:
>>>>>>>> 0.247
>>>>>>>> sec <<< FAILURE! - in org.apache.juneau.transforms.L
>>>>>>>> ocalizedDatesTest
>>>>>>>> test[111](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>>>> elapsed:
>>>>>>>> 0.015 sec <<< FAILURE!
>>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3?[]> but
>>>>>>>> was:<2001?3?3?[
>>>>>>>> (???)]>
>>>>>>>> at org.apache.juneau.transforms.L
>>>>>>>> ocalizedDatesTest.test(Localiz
>>>>>>>> edDatesTest.java:645)
>>>>>>>>
>>>>>>>> [...]
>>>>>>>> test[423](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>>>> elapsed:
>>>>>>>> 0 sec <<< FAILURE!
>>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT>
>>>>>>>> but
>>>>>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>>>>>>> at org.apache.juneau.transforms.L
>>>>>>>> ocalizedDatesTest.test(Localiz
>>>>>>>> edDatesTest.java:645)
>>>>>>>>
>>>>>>>> test[424](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>>>> elapsed:
>>>>>>>> 0 sec <<< FAILURE!
>>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT>
>>>>>>>> but
>>>>>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>>>>>>> at org.apache.juneau.transforms.L
>>>>>>>> ocalizedDatesTest.test(Localiz
>>>>>>>> edDatesTest.java:645)
>>>>>>>>
>>>>>>>> ########################
>>>>>>>>
>>>>>>>>
>>>>>>>> These are specific to date swap tests in Japanese & Korean:
>>>>>>>>
>>>>>>>> { "421", testDate.getTime(), DateSwap.DateTimeFull.class, "ja_JP",
>>>>>>>> null,
>>>>>>>> null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>>> { "422", testDate.getTime(), DateSwap.DateTimeFull.class,
>>>>>>>> Locale.JAPAN,
>>>>>>>> null, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>>> { "423", testDate.getTime(), DateSwap.DateTimeFull.class, null,
>>>>>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>>> { "424", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>>>>>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>>> { "425", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>>>>>>>> Locale.KOREA, null, null, "2001ë…„ 3ì›” 3ì�¼ í† ìš”ì�¼ ì˜¤ì „ 10ì‹œ
>>>>>>>> 11분
>>>>>>>> 12ì´ˆ GMT" },
>>>>>>>> etc.
>>>>>>>>
>>>>>>>> All the date swaps where the test date contains Japanese or Korean
>>>>>>>> characters in the date part fail in this way. I initially thought
>>>>>>>> it
>>>>>>>> was
>>>>>>>> the code page of the file, but I've changed to UTF-8 from the
>>>>>>>> default
>>>>>>>> and
>>>>>>>> this didn't resolve this for me. Again, this is specific to my
>>>>>>>> Windows
>>>>>>>> platform - all is fine on Mac.
>>>>>>>>
>>>>>>>> Given that this is a build test error, and specific to one platform
>>>>>>>> (and
>>>>>>>> possibly one machine), I'm not sure that it is a fatal problem for
>>>>>>>> the
>>>>>>>> release.
>>>>>>>>
>>>>>>>> David
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 21/09/2017 14:55, James Bognar wrote:
>>>>>>>>
>>>>>>>> Hi David,
>>>>>>>>
>>>>>>>>
>>>>>>>>> I don't have a Windows machine anymore :-(
>>>>>>>>>
>>>>>>>>> It looks like a test issue. Is it only RDF tests that are failing?
>>>>>>>>>
>>>>>>>>> Can you find line 484 in org.apache.juneau.TestUtils in
>>>>>>>>> juneau-core-tests...
>>>>>>>>>
>>>>>>>>> String[] e = expected.trim().split("\n"), a =
>>>>>>>>> actual.trim().split("\n");
>>>>>>>>>
>>>>>>>>> ...and change it to this?...
>>>>>>>>>
>>>>>>>>> String[] e = expected.trim().split("[\r\n]+"), a =
>>>>>>>>> actual.trim().split(
>>>>>>>>> "[\r\n]+");
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Background on this method: Since Jena does not guarantee the order
>>>>>>>>> of
>>>>>>>>> entries in the generated RDF (it's pretty much random), it's
>>>>>>>>> difficult
>>>>>>>>> to
>>>>>>>>> do simple comparison validation. So instead, we sort the expected
>>>>>>>>> and
>>>>>>>>> actual lines and then check for comparison. It's not perfect (XML
>>>>>>>>> attribute order can also be random), but generally good enough for
>>>>>>>>> what
>>>>>>>>> we're testing.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Sep 21, 2017 at 5:52 AM, David Goddard <go...@acm.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Thanks.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I'm seeting a whole load of test failures in juneau-core parsing
>>>>>>>>>> (every
>>>>>>>>>> round trip test is failing for me). For example:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ByteArrayBase64SwapComboTest>ComboRoundTripTest.g32_parseRdf
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> XmlR:701->ComboRoundTripTest.testParse:205
>>>>>>>>>>>
>>>>>>>>>> ByteArray2d/parseRdfXmlR
>>>>>>>>>> parse-normal failed expected:<<rdf:RDF>[
>>>>>>>>>> <rdf:Seq>
>>>>>>>>>> <rdf:li>AQID</rdf:li>
>>>>>>>>>> <rdf:li>BAUG</rdf:li>
>>>>>>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> </rdf:Seq>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> </rdf:RDF>]
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> but was:<<rdf:RDF>[
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> <rdf:Seq>
>>>>>>>>>>>
>>>>>>>>>>> <rdf:li>AQID</rdf:li>
>>>>>>>>>> <rdf:li>BAUG</rdf:li>
>>>>>>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> </rdf:Seq>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> </rdf:RDF>
>>>>>>>>>>>
>>>>>>>>>> ]
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> The only consistent difference I see is that the final closing
>>>>>>>>>>> square
>>>>>>>>>>>
>>>>>>>>>>> bracket is appearing on a new line. Perhaps this is a character
>>>>>>>>>> encoding
>>>>>>>>>> issue (although I wouldn't rule out user error) - these tests fail
>>>>>>>>>> on
>>>>>>>>>> a
>>>>>>>>>> Windows platform, but work fine on a Mac.
>>>>>>>>>>
>>>>>>>>>> David
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 20/09/2017 15:39, James Bognar wrote:
>>>>>>>>>>
>>>>>>>>>> Indeed they are.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I've fixed them in Git. Thanks David!
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <go...@acm.org>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> I'm seeing a couple of issues with the Eclipse project names when
>>>>>>>>>>>
>>>>>>>>>>> importing a fresh clone into a workspace.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> juneau-microservice/.project has <name>juneau-rest</name>
>>>>>>>>>>>> juneau-doc/.project has <name>juneau-marshall</name>
>>>>>>>>>>>>
>>>>>>>>>>>> I'm assuming these are copy/paste errors arising from the
>>>>>>>>>>>> restructuring.
>>>>>>>>>>>>
>>>>>>>>>>>> David
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 19/09/2017 18:26, Charles Mims wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> +1, with intermittent test failures in Apache Juneau
>>>>>>>>>>>> Microservice
>>>>>>>>>>>> Tests
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> MD5 (apache-juneau-6.4.0-incubating-src.zip) =
>>>>>>>>>>>>
>>>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>>>>>>>>> For me it failed on the 1st and 2nd try, passed on the 3rd.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <
>>>>>>>>>>>>> jamesbognar@apache.org>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we
>>>>>>>>>>>>> need
>>>>>>>>>>>>> to
>>>>>>>>>>>>>
>>>>>>>>>>>>> handle this problem soon.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Darn.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I'm thinking it must be an issue with Jetty since we just
>>>>>>>>>>>>>> upgraded
>>>>>>>>>>>>>> it.
>>>>>>>>>>>>>> From the Jetty side, the connection is open waiting for
>>>>>>>>>>>>>> data,
>>>>>>>>>>>>>> but
>>>>>>>>>>>>>> that's
>>>>>>>>>>>>>> all I know.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I'll have to figure out how to use Fiddler and do some
>>>>>>>>>>>>>> low-level
>>>>>>>>>>>>>> debugging. It's really hard to reproduce though :-(
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <
>>>>>>>>>>>>>> yidonguk@gmail.com
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> SHA1, MD5 Checksum OK
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Maven Build OK
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think
>>>>>>>>>>>>>>> we
>>>>>>>>>>>>>>> need
>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>> handle this problem soon.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [INFO] Reactor Summary:
>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>> [INFO] Apache Juneau (incubating) .........................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 10.521 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau - Core APIs ..........................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 0.737 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau Marshall .............................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 45.444 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau Marshal RDF ..........................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 3.558 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau Data Transfer Objects ................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 6.813 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau Core .................................
>>>>>>>>>>>>>>> SUCCESS [
>>>>>>>>>>>>>>> 1.025 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau Config File API ......................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 1.928 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau Core Tests ...........................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [01:04
>>>>>>>>>>>>>>> min]
>>>>>>>>>>>>>>> [INFO] Apache Juneau - REST APIs ..........................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 0.080 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau REST Servlet API .....................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 2.331 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau REST JAX/RS API ......................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 0.476 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau REST Client API ......................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 1.005 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau - Microservice APIs ..................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 0.068 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Server ..................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 1.588 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Template ................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 1.243 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau - Examples ...........................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 0.183 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau REST Examples ........................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 8.512 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Tests ...................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 24.522 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau Core Examples ........................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 0.287 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau Javadocs .............................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 0.617 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau - Release Engineering ................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 0.040 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau UberJar ..............................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 1.008 s]
>>>>>>>>>>>>>>> [INFO] Apache Juneau Distribution .........................
>>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>> 0.768 s]
>>>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>>> ------------
>>>>>>>>>>>>>>> [INFO] BUILD SUCCESS
>>>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>>> ------------
>>>>>>>>>>>>>>> [INFO] Total time: 03:01 min
>>>>>>>>>>>>>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>>>>>>>>>>>>>>> [INFO] Final Memory: 87M/773M
>>>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>>> ------------
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Raphi D Lee, yidonguk@gmail.com
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org>
>>>>>>>>>>>>>>> 작성:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I am pleased to be calling this vote for the source release
>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Apache
>>>>>>>>>>>>>>>> Juneau 6.4.0-incubating RC2.
>>>>>>>>>>>>>>>> This includes some fixes for bugs found in RC1 and some
>>>>>>>>>>>>>>>> packaging
>>>>>>>>>>>>>>>> changes
>>>>>>>>>>>>>>>> for the example and template projects.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The list of new features can be found here:
>>>>>>>>>>>>>>>> http://juneau.incubator.apache.org/site/apidocs/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> overview-summary.html#6.4.0
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The binaries are available at:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> binaries/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The release candidate to be voted over is available at:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> source/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> SHA-1 checksums:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 0-incubating-src.zip
>>>>>>>>>>>>>>>> c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
>>>>>>>>>>>>>>>> 0-incubating-bin.zip
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> MD5 checksums:
>>>>>>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>>>>>>>>>>>> apache-juneau-6.4.0-incubating
>>>>>>>>>>>>>>>> -src.zip
>>>>>>>>>>>>>>>> 4e96d5047c0e9f03f0def2d017521f13
>>>>>>>>>>>>>>>> apache-juneau-6.4.0-incubating
>>>>>>>>>>>>>>>> -bin.zip
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Build the release candidate using:
>>>>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The release candidate is signed with a GPG key available at:
>>>>>>>>>>>>>>>> https://dist.apache.org/repos/
>>>>>>>>>>>>>>>> dist/release/incubator/juneau/
>>>>>>>>>>>>>>>> KEYS
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> A staged Maven repository is available for review at:
>>>>>>>>>>>>>>>> https://repository.apache.org/
>>>>>>>>>>>>>>>> content/repositories/orgapache
>>>>>>>>>>>>>>>> juneau-1016/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The Git commit for this release is...
>>>>>>>>>>>>>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> juneau.git;a=commit;h=6de99819
>>>>>>>>>>>>>>>> 3807eeec40e6f297f6b70222552f3b
>>>>>>>>>>>>>>>> 37
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 37>*
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Please vote on releasing this package as:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Apache Juneau 6.4.0-incubating
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> This vote will be open until 20-Sep-2017 9:00pm EST and
>>>>>>>>>>>>>>>> passes
>>>>>>>>>>>>>>>> if a
>>>>>>>>>>>>>>>> majority of at least three +1 Apache Juneau PPMC votes are
>>>>>>>>>>>>>>>> cast.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [ ] +1 Release this package
>>>>>>>>>>>>>>>> [ ] 0 I don't feel strongly about it, but don't object
>>>>>>>>>>>>>>>> [ ] -1 Do not release this package because...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Anyone can participate in testing and voting, not just
>>>>>>>>>>>>>>>> committers,
>>>>>>>>>>>>>>>> please
>>>>>>>>>>>>>>>> feel free to try out the release candidate and provide your
>>>>>>>>>>>>>>>> votes.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by David Goddard <go...@acm.org>.
Hi,
Yes, this code now works:
@Test
public void test() {
BeanSession session = ps.getBeanContext()
.createSession(new BeanSessionArgs(null, sessionLocale,
sessionTimeZone, null));
String actual = session.convertToType(calendar, String.class);
if (expected.indexOf('(') == -1)
// Fix JVM-specific formatting difference
actual.replaceAll(" \\([^\\)]+\\)", "").replaceAll("\\([^\\)]+\\) ",
"");
assertEquals(expected, actual);
Object c2 = session.convertToType(actual, calendar.getClass());
String actual2 = session.convertToType(c2, String.class);
if (expected.indexOf('(') == -1)
// Fix JVM-specific formatting difference
actual2 = actual2.replaceAll("\\([^\\)]+\\) ", "");
assertEquals(expected, actual2);
}
However, still one more error in my Windows environment though :(
#############################
Tests run: 11, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.031
sec <<< FAILURE! - in org.apache.juneau.BeanConfigTest
testProxyHandler(org.apache.juneau.BeanConfigTest) Time elapsed: 0 sec
<<< ERROR!
org.apache.juneau.BeanRuntimeException: interface
org.apache.juneau.BeanConfigTest$A is not visible from class loader
at
org.apache.juneau.BeanConfigTest.testProxyHandler(BeanConfigTest.java:473)
Caused by: java.lang.IllegalArgumentException: interface
org.apache.juneau.BeanConfigTest$A is not visible from class loader
at
org.apache.juneau.BeanConfigTest.testProxyHandler(BeanConfigTest.java:473)
#############################
I'm wondering if this is an issue specific to my setup. When I have a
chance (I am travelling at the moment), I'll set up an Oracle JVM in my
Windows test environment and try a build with that.
David
On 23/09/2017 21:35, James Bognar wrote:
> Hi David,
>
> How about this?
> if (expected.indexOf('(') == -1)
> actual.replaceAll(" \\([^\\)]+\\)", "").replaceAll("\\([^\\)]+\\) ", "");
>
>
> On Fri, Sep 22, 2017 at 3:08 PM, David Goddard <go...@acm.org> wrote:
>
>> Most things are in some way IBM's fault :)
>>
>> Trying both variants of your fix gives similar results. Better in both
>> cases, but not quite there. Details below.
>>
>> It looks to me on a quick read that those cases that now fail are failing
>> because they *do* expect a value between the parentheses, and of course the
>> fix strips that out. For example, here's test 205:
>>
>> { "205", testDate, CalendarSwap.DateTimeLong.class, "en_UK",
>> Locale.KOREA, null, null, "2001년 3월 3일 (토) 오전 10시 11분 12초" },
>>
>> I guess we could bend the test a little further by conditionally only
>> stripping out the parenthetical content if the expected value doesn't
>> contain values in parentheses itself, but that be regarded as a fix too
>> far...
>>
>> #######################
>>
>> actual = actual.replaceAll("\\([^\\)]+\\) ", "");
>> actual2 = actual2.replaceAll("\\([^\\)]+\\) ", "");
>>
>> ...leads to:
>>
>> Tests run: 460, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 19.485
>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
>> test[205](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
>> 0.004 sec <<< FAILURE!
>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>> edDatesTest.java:660)
>>
>> test[435](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
>> 0.001 sec <<< FAILURE!
>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>> edDatesTest.java:660)
>>
>> With the different location for the space in the regexp, I get a longer
>> list of failures:
>>
>> #######################
>>
>> actual = actual.replaceAll(" \\([^\\)]+\\)", "");
>> actual2 = actual2.replaceAll(" \\([^\\)]+\\)", "");
>>
>> ... leads to:
>>
>> Running org.apache.juneau.transforms.LocalizedDatesTest
>> Tests run: 460, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 0.189
>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
>> test[125](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
>> 0.003 sec <<< FAILURE!
>> org.junit.ComparisonFailure: expected:<2001? 3? 3?[ (?)]> but was:<2001?
>> 3? 3?[]>
>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>> edDatesTest.java:660)
>>
>> test[205](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
>> 0 sec <<< FAILURE!
>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>> edDatesTest.java:660)
>>
>> test[355](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
>> 0 sec <<< FAILURE!
>> org.junit.ComparisonFailure: expected:<2001? 3? 3?[ (?)]> but was:<2001?
>> 3? 3?[]>
>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>> edDatesTest.java:660)
>>
>> test[435](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
>> 0.001 sec <<< FAILURE!
>> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
>> but was:<2001? 3? 3? []?? 10? 11? 12?>
>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>> edDatesTest.java:660)
>>
>> #######################
>>
>>
>>
>>
>> On 22/09/2017 00:05, James Bognar wrote:
>>
>>> Ah...so we can blame IBM :-)
>>>
>>> Can you see if swapping the location of the space in the regular
>>> expressions fixes all the tests?
>>> actual = actual.replaceAll(" \\([^\\)]+\\)", "");
>>>
>>> On Thu, Sep 21, 2017 at 6:01 PM, David Goddard <go...@acm.org> wrote:
>>>
>>> Just to add:
>>>>
>>>> Maybe it's JVM vendor-specific behavior?
>>>>>
>>>>
>>>> Yes, I've now tested again after changing from an IBM JRE to an Oracle
>>>> JRE
>>>> - this resolves the problem. It looks like this is specific to the IBM
>>>> JRE
>>>> then. My Mac testing was done with an Oracle JRE, so I think this is
>>>> probably JVM-specific rather than OS-specific.
>>>>
>>>>
>>>> On 21/09/2017 23:46, David Goddard wrote:
>>>>
>>>> Actual text is:
>>>>>
>>>>> 2001年3月3日 (土曜日)
>>>>> (I've attached a copy as a text file also)
>>>>>
>>>>> In this case, I it looks like the value between the parenthesis is the
>>>>> day name, "Saturday". So the expected value is just the date (2001年3月
>>>>> 3日),
>>>>> but the day is being added in the process.
>>>>>
>>>>>
>>>>> On 21/09/2017 22:45, James Bognar wrote:
>>>>>
>>>>> Interesting. So the behavior of...
>>>>>>
>>>>>> DateFormat.getDateInstance(DateFormat.FULL, locale).format(date);
>>>>>> DateFormat.getDateTimeInstance(DateFormat.FULL, DateFormat.FULL,
>>>>>> locale
>>>>>> ).format(date);
>>>>>>
>>>>>> ...returns different formats depending on the OS. Lovely.
>>>>>>
>>>>>> Maybe it's JVM vendor-specific behavior?
>>>>>>
>>>>>> I'm curious to know what's in those parentheses...
>>>>>> 2001?3?3? [*(???)* ]10?11?12? GMT
>>>>>>
>>>>>> Might give me something to google for.
>>>>>>
>>>>>> It's technically a test-only issue. We can probably 'fix' the testcase
>>>>>> by
>>>>>> just stripping out the formatting difference...
>>>>>>
>>>>>> @Test
>>>>>> public void test() {
>>>>>> BeanSession session = ps.getBeanContext().createSession(new
>>>>>> BeanSessionArgs(null, sessionLocale, sessionTimeZone, null));
>>>>>> String actual = session.convertToType(calendar, String.class);
>>>>>> *actual = actual.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>>>>>> Windows-specific
>>>>>> formatting difference*
>>>>>> assertEquals(expected, actual);
>>>>>> Object c2 = session.convertToType(actual, calendar.getClass());
>>>>>> String actual2 = session.convertToType(c2, String.class);
>>>>>> *actual2 = actual2.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>>>>>> Windows-specific formatting difference*
>>>>>> assertEquals(expected, actual2);
>>>>>> }
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Sep 21, 2017 at 3:11 PM, David Goddard <go...@acm.org>
>>>>>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>>
>>>>>>> Yes, that fixed it, thanks. It also still tests OK on my Mac after
>>>>>>> the
>>>>>>> change.
>>>>>>>
>>>>>>> I'm now running into some further test issues, also on Windows only.
>>>>>>>
>>>>>>> ########################
>>>>>>>
>>>>>>> Tests run: 460, Failures: 16, Errors: 0, Skipped: 0, Time elapsed:
>>>>>>> 0.247
>>>>>>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
>>>>>>> test[111](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>>> elapsed:
>>>>>>> 0.015 sec <<< FAILURE!
>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3?[]> but
>>>>>>> was:<2001?3?3?[
>>>>>>> (???)]>
>>>>>>> at org.apache.juneau.transforms.L
>>>>>>> ocalizedDatesTest.test(Localiz
>>>>>>> edDatesTest.java:645)
>>>>>>>
>>>>>>> [...]
>>>>>>> test[423](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>>> elapsed:
>>>>>>> 0 sec <<< FAILURE!
>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT> but
>>>>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>>>>>> at org.apache.juneau.transforms.L
>>>>>>> ocalizedDatesTest.test(Localiz
>>>>>>> edDatesTest.java:645)
>>>>>>>
>>>>>>> test[424](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>>> elapsed:
>>>>>>> 0 sec <<< FAILURE!
>>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT> but
>>>>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>>>>>> at org.apache.juneau.transforms.L
>>>>>>> ocalizedDatesTest.test(Localiz
>>>>>>> edDatesTest.java:645)
>>>>>>>
>>>>>>> ########################
>>>>>>>
>>>>>>>
>>>>>>> These are specific to date swap tests in Japanese & Korean:
>>>>>>>
>>>>>>> { "421", testDate.getTime(), DateSwap.DateTimeFull.class, "ja_JP",
>>>>>>> null,
>>>>>>> null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>> { "422", testDate.getTime(), DateSwap.DateTimeFull.class,
>>>>>>> Locale.JAPAN,
>>>>>>> null, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>> { "423", testDate.getTime(), DateSwap.DateTimeFull.class, null,
>>>>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>> { "424", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>>>>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>>> { "425", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>>>>>>> Locale.KOREA, null, null, "2001ë…„ 3ì›” 3ì�¼ í† ìš”ì�¼ ì˜¤ì „ 10ì‹œ
>>>>>>> 11분
>>>>>>> 12ì´ˆ GMT" },
>>>>>>> etc.
>>>>>>>
>>>>>>> All the date swaps where the test date contains Japanese or Korean
>>>>>>> characters in the date part fail in this way. I initially thought it
>>>>>>> was
>>>>>>> the code page of the file, but I've changed to UTF-8 from the default
>>>>>>> and
>>>>>>> this didn't resolve this for me. Again, this is specific to my
>>>>>>> Windows
>>>>>>> platform - all is fine on Mac.
>>>>>>>
>>>>>>> Given that this is a build test error, and specific to one platform
>>>>>>> (and
>>>>>>> possibly one machine), I'm not sure that it is a fatal problem for the
>>>>>>> release.
>>>>>>>
>>>>>>> David
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 21/09/2017 14:55, James Bognar wrote:
>>>>>>>
>>>>>>> Hi David,
>>>>>>>
>>>>>>>>
>>>>>>>> I don't have a Windows machine anymore :-(
>>>>>>>>
>>>>>>>> It looks like a test issue. Is it only RDF tests that are failing?
>>>>>>>>
>>>>>>>> Can you find line 484 in org.apache.juneau.TestUtils in
>>>>>>>> juneau-core-tests...
>>>>>>>>
>>>>>>>> String[] e = expected.trim().split("\n"), a =
>>>>>>>> actual.trim().split("\n");
>>>>>>>>
>>>>>>>> ...and change it to this?...
>>>>>>>>
>>>>>>>> String[] e = expected.trim().split("[\r\n]+"), a =
>>>>>>>> actual.trim().split(
>>>>>>>> "[\r\n]+");
>>>>>>>>
>>>>>>>>
>>>>>>>> Background on this method: Since Jena does not guarantee the order
>>>>>>>> of
>>>>>>>> entries in the generated RDF (it's pretty much random), it's
>>>>>>>> difficult
>>>>>>>> to
>>>>>>>> do simple comparison validation. So instead, we sort the expected
>>>>>>>> and
>>>>>>>> actual lines and then check for comparison. It's not perfect (XML
>>>>>>>> attribute order can also be random), but generally good enough for
>>>>>>>> what
>>>>>>>> we're testing.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Sep 21, 2017 at 5:52 AM, David Goddard <go...@acm.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>>
>>>>>>>>> I'm seeting a whole load of test failures in juneau-core parsing
>>>>>>>>> (every
>>>>>>>>> round trip test is failing for me). For example:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ByteArrayBase64SwapComboTest>ComboRoundTripTest.g32_parseRdf
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> XmlR:701->ComboRoundTripTest.testParse:205
>>>>>>>>> ByteArray2d/parseRdfXmlR
>>>>>>>>> parse-normal failed expected:<<rdf:RDF>[
>>>>>>>>> <rdf:Seq>
>>>>>>>>> <rdf:li>AQID</rdf:li>
>>>>>>>>> <rdf:li>BAUG</rdf:li>
>>>>>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> </rdf:Seq>
>>>>>>>>>>
>>>>>>>>>> </rdf:RDF>]
>>>>>>>>>
>>>>>>>>> but was:<<rdf:RDF>[
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> <rdf:Seq>
>>>>>>>>>>
>>>>>>>>> <rdf:li>AQID</rdf:li>
>>>>>>>>> <rdf:li>BAUG</rdf:li>
>>>>>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> </rdf:Seq>
>>>>>>>>>>
>>>>>>>>>> </rdf:RDF>
>>>>>>>>> ]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> The only consistent difference I see is that the final closing
>>>>>>>>>> square
>>>>>>>>>>
>>>>>>>>> bracket is appearing on a new line. Perhaps this is a character
>>>>>>>>> encoding
>>>>>>>>> issue (although I wouldn't rule out user error) - these tests fail
>>>>>>>>> on
>>>>>>>>> a
>>>>>>>>> Windows platform, but work fine on a Mac.
>>>>>>>>>
>>>>>>>>> David
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 20/09/2017 15:39, James Bognar wrote:
>>>>>>>>>
>>>>>>>>> Indeed they are.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> I've fixed them in Git. Thanks David!
>>>>>>>>>>
>>>>>>>>>> On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <go...@acm.org>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> I'm seeing a couple of issues with the Eclipse project names when
>>>>>>>>>>
>>>>>>>>>> importing a fresh clone into a workspace.
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> juneau-microservice/.project has <name>juneau-rest</name>
>>>>>>>>>>> juneau-doc/.project has <name>juneau-marshall</name>
>>>>>>>>>>>
>>>>>>>>>>> I'm assuming these are copy/paste errors arising from the
>>>>>>>>>>> restructuring.
>>>>>>>>>>>
>>>>>>>>>>> David
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 19/09/2017 18:26, Charles Mims wrote:
>>>>>>>>>>>
>>>>>>>>>>> +1, with intermittent test failures in Apache Juneau Microservice
>>>>>>>>>>> Tests
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> MD5 (apache-juneau-6.4.0-incubating-src.zip) =
>>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>>>>>>>> For me it failed on the 1st and 2nd try, passed on the 3rd.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <
>>>>>>>>>>>> jamesbognar@apache.org>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we
>>>>>>>>>>>> need
>>>>>>>>>>>> to
>>>>>>>>>>>>
>>>>>>>>>>>> handle this problem soon.
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Darn.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I'm thinking it must be an issue with Jetty since we just
>>>>>>>>>>>>> upgraded
>>>>>>>>>>>>> it.
>>>>>>>>>>>>> From the Jetty side, the connection is open waiting for
>>>>>>>>>>>>> data,
>>>>>>>>>>>>> but
>>>>>>>>>>>>> that's
>>>>>>>>>>>>> all I know.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I'll have to figure out how to use Fiddler and do some low-level
>>>>>>>>>>>>> debugging. It's really hard to reproduce though :-(
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <
>>>>>>>>>>>>> yidonguk@gmail.com
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> +1
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> SHA1, MD5 Checksum OK
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Maven Build OK
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we
>>>>>>>>>>>>>> need
>>>>>>>>>>>>>> to
>>>>>>>>>>>>>> handle this problem soon.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [INFO] Reactor Summary:
>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>> [INFO] Apache Juneau (incubating) .........................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 10.521 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau - Core APIs ..........................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 0.737 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau Marshall .............................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 45.444 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau Marshal RDF ..........................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 3.558 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau Data Transfer Objects ................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 6.813 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau Core .................................
>>>>>>>>>>>>>> SUCCESS [
>>>>>>>>>>>>>> 1.025 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau Config File API ......................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 1.928 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau Core Tests ...........................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [01:04
>>>>>>>>>>>>>> min]
>>>>>>>>>>>>>> [INFO] Apache Juneau - REST APIs ..........................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 0.080 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau REST Servlet API .....................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 2.331 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau REST JAX/RS API ......................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 0.476 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau REST Client API ......................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 1.005 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau - Microservice APIs ..................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 0.068 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Server ..................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 1.588 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Template ................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 1.243 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau - Examples ...........................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 0.183 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau REST Examples ........................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 8.512 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Tests ...................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 24.522 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau Core Examples ........................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 0.287 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau Javadocs .............................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 0.617 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau - Release Engineering ................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 0.040 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau UberJar ..............................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 1.008 s]
>>>>>>>>>>>>>> [INFO] Apache Juneau Distribution .........................
>>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>> 0.768 s]
>>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>> ------------
>>>>>>>>>>>>>> [INFO] BUILD SUCCESS
>>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>> ------------
>>>>>>>>>>>>>> [INFO] Total time: 03:01 min
>>>>>>>>>>>>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>>>>>>>>>>>>>> [INFO] Final Memory: 87M/773M
>>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>>> ------------
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Raphi D Lee, yidonguk@gmail.com
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org>
>>>>>>>>>>>>>> 작성:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I am pleased to be calling this vote for the source release of
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Apache
>>>>>>>>>>>>>>> Juneau 6.4.0-incubating RC2.
>>>>>>>>>>>>>>> This includes some fixes for bugs found in RC1 and some
>>>>>>>>>>>>>>> packaging
>>>>>>>>>>>>>>> changes
>>>>>>>>>>>>>>> for the example and template projects.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The list of new features can be found here:
>>>>>>>>>>>>>>> http://juneau.incubator.apache.org/site/apidocs/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> overview-summary.html#6.4.0
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The binaries are available at:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> binaries/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The release candidate to be voted over is available at:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> source/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> SHA-1 checksums:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
>>>>>>>>>>>>>>> 0-incubating-src.zip
>>>>>>>>>>>>>>> c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
>>>>>>>>>>>>>>> 0-incubating-bin.zip
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> MD5 checksums:
>>>>>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>>>>>>>>>>> apache-juneau-6.4.0-incubating
>>>>>>>>>>>>>>> -src.zip
>>>>>>>>>>>>>>> 4e96d5047c0e9f03f0def2d017521f13
>>>>>>>>>>>>>>> apache-juneau-6.4.0-incubating
>>>>>>>>>>>>>>> -bin.zip
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Build the release candidate using:
>>>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The release candidate is signed with a GPG key available at:
>>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/juneau/
>>>>>>>>>>>>>>> KEYS
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> A staged Maven repository is available for review at:
>>>>>>>>>>>>>>> https://repository.apache.org/content/repositories/orgapache
>>>>>>>>>>>>>>> juneau-1016/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The Git commit for this release is...
>>>>>>>>>>>>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b
>>>>>>>>>>>>>>> 37
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b
>>>>>>>>>>>>>>> 37>*
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Please vote on releasing this package as:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Apache Juneau 6.4.0-incubating
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> This vote will be open until 20-Sep-2017 9:00pm EST and passes
>>>>>>>>>>>>>>> if a
>>>>>>>>>>>>>>> majority of at least three +1 Apache Juneau PPMC votes are
>>>>>>>>>>>>>>> cast.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [ ] +1 Release this package
>>>>>>>>>>>>>>> [ ] 0 I don't feel strongly about it, but don't object
>>>>>>>>>>>>>>> [ ] -1 Do not release this package because...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Anyone can participate in testing and voting, not just
>>>>>>>>>>>>>>> committers,
>>>>>>>>>>>>>>> please
>>>>>>>>>>>>>>> feel free to try out the release candidate and provide your
>>>>>>>>>>>>>>> votes.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by James Bognar <ja...@apache.org>.
Hi David,
How about this?
if (expected.indexOf('(') == -1)
actual.replaceAll(" \\([^\\)]+\\)", "").replaceAll("\\([^\\)]+\\) ", "");
On Fri, Sep 22, 2017 at 3:08 PM, David Goddard <go...@acm.org> wrote:
> Most things are in some way IBM's fault :)
>
> Trying both variants of your fix gives similar results. Better in both
> cases, but not quite there. Details below.
>
> It looks to me on a quick read that those cases that now fail are failing
> because they *do* expect a value between the parentheses, and of course the
> fix strips that out. For example, here's test 205:
>
> { "205", testDate, CalendarSwap.DateTimeLong.class, "en_UK",
> Locale.KOREA, null, null, "2001년 3월 3일 (토) 오전 10시 11분 12초" },
>
> I guess we could bend the test a little further by conditionally only
> stripping out the parenthetical content if the expected value doesn't
> contain values in parentheses itself, but that be regarded as a fix too
> far...
>
> #######################
>
> actual = actual.replaceAll("\\([^\\)]+\\) ", "");
> actual2 = actual2.replaceAll("\\([^\\)]+\\) ", "");
>
> ...leads to:
>
> Tests run: 460, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 19.485
> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
> test[205](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
> 0.004 sec <<< FAILURE!
> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
> but was:<2001? 3? 3? []?? 10? 11? 12?>
> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
> edDatesTest.java:660)
>
> test[435](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
> 0.001 sec <<< FAILURE!
> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
> but was:<2001? 3? 3? []?? 10? 11? 12?>
> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
> edDatesTest.java:660)
>
> With the different location for the space in the regexp, I get a longer
> list of failures:
>
> #######################
>
> actual = actual.replaceAll(" \\([^\\)]+\\)", "");
> actual2 = actual2.replaceAll(" \\([^\\)]+\\)", "");
>
> ... leads to:
>
> Running org.apache.juneau.transforms.LocalizedDatesTest
> Tests run: 460, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 0.189
> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
> test[125](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
> 0.003 sec <<< FAILURE!
> org.junit.ComparisonFailure: expected:<2001? 3? 3?[ (?)]> but was:<2001?
> 3? 3?[]>
> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
> edDatesTest.java:660)
>
> test[205](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
> 0 sec <<< FAILURE!
> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
> but was:<2001? 3? 3? []?? 10? 11? 12?>
> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
> edDatesTest.java:660)
>
> test[355](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
> 0 sec <<< FAILURE!
> org.junit.ComparisonFailure: expected:<2001? 3? 3?[ (?)]> but was:<2001?
> 3? 3?[]>
> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
> edDatesTest.java:660)
>
> test[435](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
> 0.001 sec <<< FAILURE!
> org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
> but was:<2001? 3? 3? []?? 10? 11? 12?>
> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
> edDatesTest.java:660)
>
> #######################
>
>
>
>
> On 22/09/2017 00:05, James Bognar wrote:
>
>> Ah...so we can blame IBM :-)
>>
>> Can you see if swapping the location of the space in the regular
>> expressions fixes all the tests?
>> actual = actual.replaceAll(" \\([^\\)]+\\)", "");
>>
>> On Thu, Sep 21, 2017 at 6:01 PM, David Goddard <go...@acm.org> wrote:
>>
>> Just to add:
>>>
>>> Maybe it's JVM vendor-specific behavior?
>>>>
>>>
>>> Yes, I've now tested again after changing from an IBM JRE to an Oracle
>>> JRE
>>> - this resolves the problem. It looks like this is specific to the IBM
>>> JRE
>>> then. My Mac testing was done with an Oracle JRE, so I think this is
>>> probably JVM-specific rather than OS-specific.
>>>
>>>
>>> On 21/09/2017 23:46, David Goddard wrote:
>>>
>>> Actual text is:
>>>>
>>>> 2001年3月3日 (土曜日)
>>>> (I've attached a copy as a text file also)
>>>>
>>>> In this case, I it looks like the value between the parenthesis is the
>>>> day name, "Saturday". So the expected value is just the date (2001年3月
>>>> 3日),
>>>> but the day is being added in the process.
>>>>
>>>>
>>>> On 21/09/2017 22:45, James Bognar wrote:
>>>>
>>>> Interesting. So the behavior of...
>>>>>
>>>>> DateFormat.getDateInstance(DateFormat.FULL, locale).format(date);
>>>>> DateFormat.getDateTimeInstance(DateFormat.FULL, DateFormat.FULL,
>>>>> locale
>>>>> ).format(date);
>>>>>
>>>>> ...returns different formats depending on the OS. Lovely.
>>>>>
>>>>> Maybe it's JVM vendor-specific behavior?
>>>>>
>>>>> I'm curious to know what's in those parentheses...
>>>>> 2001?3?3? [*(???)* ]10?11?12? GMT
>>>>>
>>>>> Might give me something to google for.
>>>>>
>>>>> It's technically a test-only issue. We can probably 'fix' the testcase
>>>>> by
>>>>> just stripping out the formatting difference...
>>>>>
>>>>> @Test
>>>>> public void test() {
>>>>> BeanSession session = ps.getBeanContext().createSession(new
>>>>> BeanSessionArgs(null, sessionLocale, sessionTimeZone, null));
>>>>> String actual = session.convertToType(calendar, String.class);
>>>>> *actual = actual.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>>>>> Windows-specific
>>>>> formatting difference*
>>>>> assertEquals(expected, actual);
>>>>> Object c2 = session.convertToType(actual, calendar.getClass());
>>>>> String actual2 = session.convertToType(c2, String.class);
>>>>> *actual2 = actual2.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>>>>> Windows-specific formatting difference*
>>>>> assertEquals(expected, actual2);
>>>>> }
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Sep 21, 2017 at 3:11 PM, David Goddard <go...@acm.org>
>>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>>>
>>>>>> Yes, that fixed it, thanks. It also still tests OK on my Mac after
>>>>>> the
>>>>>> change.
>>>>>>
>>>>>> I'm now running into some further test issues, also on Windows only.
>>>>>>
>>>>>> ########################
>>>>>>
>>>>>> Tests run: 460, Failures: 16, Errors: 0, Skipped: 0, Time elapsed:
>>>>>> 0.247
>>>>>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
>>>>>> test[111](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>> elapsed:
>>>>>> 0.015 sec <<< FAILURE!
>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3?[]> but
>>>>>> was:<2001?3?3?[
>>>>>> (???)]>
>>>>>> at org.apache.juneau.transforms.L
>>>>>> ocalizedDatesTest.test(Localiz
>>>>>> edDatesTest.java:645)
>>>>>>
>>>>>> [...]
>>>>>> test[423](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>> elapsed:
>>>>>> 0 sec <<< FAILURE!
>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT> but
>>>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>>>>> at org.apache.juneau.transforms.L
>>>>>> ocalizedDatesTest.test(Localiz
>>>>>> edDatesTest.java:645)
>>>>>>
>>>>>> test[424](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>>> elapsed:
>>>>>> 0 sec <<< FAILURE!
>>>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT> but
>>>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>>>>> at org.apache.juneau.transforms.L
>>>>>> ocalizedDatesTest.test(Localiz
>>>>>> edDatesTest.java:645)
>>>>>>
>>>>>> ########################
>>>>>>
>>>>>>
>>>>>> These are specific to date swap tests in Japanese & Korean:
>>>>>>
>>>>>> { "421", testDate.getTime(), DateSwap.DateTimeFull.class, "ja_JP",
>>>>>> null,
>>>>>> null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>> { "422", testDate.getTime(), DateSwap.DateTimeFull.class,
>>>>>> Locale.JAPAN,
>>>>>> null, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>> { "423", testDate.getTime(), DateSwap.DateTimeFull.class, null,
>>>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>> { "424", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>>>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>>> { "425", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>>>>>> Locale.KOREA, null, null, "2001ë…„ 3ì›” 3ì�¼ í† ìš”ì�¼ ì˜¤ì „ 10ì‹œ
>>>>>> 11분
>>>>>> 12ì´ˆ GMT" },
>>>>>> etc.
>>>>>>
>>>>>> All the date swaps where the test date contains Japanese or Korean
>>>>>> characters in the date part fail in this way. I initially thought it
>>>>>> was
>>>>>> the code page of the file, but I've changed to UTF-8 from the default
>>>>>> and
>>>>>> this didn't resolve this for me. Again, this is specific to my
>>>>>> Windows
>>>>>> platform - all is fine on Mac.
>>>>>>
>>>>>> Given that this is a build test error, and specific to one platform
>>>>>> (and
>>>>>> possibly one machine), I'm not sure that it is a fatal problem for the
>>>>>> release.
>>>>>>
>>>>>> David
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 21/09/2017 14:55, James Bognar wrote:
>>>>>>
>>>>>> Hi David,
>>>>>>
>>>>>>>
>>>>>>> I don't have a Windows machine anymore :-(
>>>>>>>
>>>>>>> It looks like a test issue. Is it only RDF tests that are failing?
>>>>>>>
>>>>>>> Can you find line 484 in org.apache.juneau.TestUtils in
>>>>>>> juneau-core-tests...
>>>>>>>
>>>>>>> String[] e = expected.trim().split("\n"), a =
>>>>>>> actual.trim().split("\n");
>>>>>>>
>>>>>>> ...and change it to this?...
>>>>>>>
>>>>>>> String[] e = expected.trim().split("[\r\n]+"), a =
>>>>>>> actual.trim().split(
>>>>>>> "[\r\n]+");
>>>>>>>
>>>>>>>
>>>>>>> Background on this method: Since Jena does not guarantee the order
>>>>>>> of
>>>>>>> entries in the generated RDF (it's pretty much random), it's
>>>>>>> difficult
>>>>>>> to
>>>>>>> do simple comparison validation. So instead, we sort the expected
>>>>>>> and
>>>>>>> actual lines and then check for comparison. It's not perfect (XML
>>>>>>> attribute order can also be random), but generally good enough for
>>>>>>> what
>>>>>>> we're testing.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Sep 21, 2017 at 5:52 AM, David Goddard <go...@acm.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>>
>>>>>>>> I'm seeting a whole load of test failures in juneau-core parsing
>>>>>>>> (every
>>>>>>>> round trip test is failing for me). For example:
>>>>>>>>
>>>>>>>>
>>>>>>>> ByteArrayBase64SwapComboTest>ComboRoundTripTest.g32_parseRdf
>>>>>>>>
>>>>>>>>>
>>>>>>>>> XmlR:701->ComboRoundTripTest.testParse:205
>>>>>>>> ByteArray2d/parseRdfXmlR
>>>>>>>> parse-normal failed expected:<<rdf:RDF>[
>>>>>>>> <rdf:Seq>
>>>>>>>> <rdf:li>AQID</rdf:li>
>>>>>>>> <rdf:li>BAUG</rdf:li>
>>>>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>>>>
>>>>>>>>
>>>>>>>> </rdf:Seq>
>>>>>>>>>
>>>>>>>>> </rdf:RDF>]
>>>>>>>>
>>>>>>>> but was:<<rdf:RDF>[
>>>>>>>>
>>>>>>>>>
>>>>>>>>> <rdf:Seq>
>>>>>>>>>
>>>>>>>> <rdf:li>AQID</rdf:li>
>>>>>>>> <rdf:li>BAUG</rdf:li>
>>>>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>>>>
>>>>>>>>
>>>>>>>> </rdf:Seq>
>>>>>>>>>
>>>>>>>>> </rdf:RDF>
>>>>>>>> ]
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> The only consistent difference I see is that the final closing
>>>>>>>>> square
>>>>>>>>>
>>>>>>>> bracket is appearing on a new line. Perhaps this is a character
>>>>>>>> encoding
>>>>>>>> issue (although I wouldn't rule out user error) - these tests fail
>>>>>>>> on
>>>>>>>> a
>>>>>>>> Windows platform, but work fine on a Mac.
>>>>>>>>
>>>>>>>> David
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 20/09/2017 15:39, James Bognar wrote:
>>>>>>>>
>>>>>>>> Indeed they are.
>>>>>>>>
>>>>>>>>
>>>>>>>>> I've fixed them in Git. Thanks David!
>>>>>>>>>
>>>>>>>>> On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <go...@acm.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> I'm seeing a couple of issues with the Eclipse project names when
>>>>>>>>>
>>>>>>>>> importing a fresh clone into a workspace.
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> juneau-microservice/.project has <name>juneau-rest</name>
>>>>>>>>>> juneau-doc/.project has <name>juneau-marshall</name>
>>>>>>>>>>
>>>>>>>>>> I'm assuming these are copy/paste errors arising from the
>>>>>>>>>> restructuring.
>>>>>>>>>>
>>>>>>>>>> David
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 19/09/2017 18:26, Charles Mims wrote:
>>>>>>>>>>
>>>>>>>>>> +1, with intermittent test failures in Apache Juneau Microservice
>>>>>>>>>> Tests
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> MD5 (apache-juneau-6.4.0-incubating-src.zip) =
>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>>>>>>> For me it failed on the 1st and 2nd try, passed on the 3rd.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <
>>>>>>>>>>> jamesbognar@apache.org>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we
>>>>>>>>>>> need
>>>>>>>>>>> to
>>>>>>>>>>>
>>>>>>>>>>> handle this problem soon.
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Darn.
>>>>>>>>>>>>
>>>>>>>>>>>> I'm thinking it must be an issue with Jetty since we just
>>>>>>>>>>>> upgraded
>>>>>>>>>>>> it.
>>>>>>>>>>>> From the Jetty side, the connection is open waiting for
>>>>>>>>>>>> data,
>>>>>>>>>>>> but
>>>>>>>>>>>> that's
>>>>>>>>>>>> all I know.
>>>>>>>>>>>>
>>>>>>>>>>>> I'll have to figure out how to use Fiddler and do some low-level
>>>>>>>>>>>> debugging. It's really hard to reproduce though :-(
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <
>>>>>>>>>>>> yidonguk@gmail.com
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> +1
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> SHA1, MD5 Checksum OK
>>>>>>>>>>>>
>>>>>>>>>>>>> Maven Build OK
>>>>>>>>>>>>>
>>>>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we
>>>>>>>>>>>>> need
>>>>>>>>>>>>> to
>>>>>>>>>>>>> handle this problem soon.
>>>>>>>>>>>>>
>>>>>>>>>>>>> [INFO] Reactor Summary:
>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>> [INFO] Apache Juneau (incubating) .........................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 10.521 s]
>>>>>>>>>>>>> [INFO] Apache Juneau - Core APIs ..........................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 0.737 s]
>>>>>>>>>>>>> [INFO] Apache Juneau Marshall .............................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 45.444 s]
>>>>>>>>>>>>> [INFO] Apache Juneau Marshal RDF ..........................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 3.558 s]
>>>>>>>>>>>>> [INFO] Apache Juneau Data Transfer Objects ................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 6.813 s]
>>>>>>>>>>>>> [INFO] Apache Juneau Core .................................
>>>>>>>>>>>>> SUCCESS [
>>>>>>>>>>>>> 1.025 s]
>>>>>>>>>>>>> [INFO] Apache Juneau Config File API ......................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 1.928 s]
>>>>>>>>>>>>> [INFO] Apache Juneau Core Tests ...........................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [01:04
>>>>>>>>>>>>> min]
>>>>>>>>>>>>> [INFO] Apache Juneau - REST APIs ..........................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 0.080 s]
>>>>>>>>>>>>> [INFO] Apache Juneau REST Servlet API .....................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 2.331 s]
>>>>>>>>>>>>> [INFO] Apache Juneau REST JAX/RS API ......................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 0.476 s]
>>>>>>>>>>>>> [INFO] Apache Juneau REST Client API ......................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 1.005 s]
>>>>>>>>>>>>> [INFO] Apache Juneau - Microservice APIs ..................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 0.068 s]
>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Server ..................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 1.588 s]
>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Template ................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 1.243 s]
>>>>>>>>>>>>> [INFO] Apache Juneau - Examples ...........................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 0.183 s]
>>>>>>>>>>>>> [INFO] Apache Juneau REST Examples ........................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 8.512 s]
>>>>>>>>>>>>> [INFO] Apache Juneau Microservice Tests ...................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 24.522 s]
>>>>>>>>>>>>> [INFO] Apache Juneau Core Examples ........................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 0.287 s]
>>>>>>>>>>>>> [INFO] Apache Juneau Javadocs .............................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 0.617 s]
>>>>>>>>>>>>> [INFO] Apache Juneau - Release Engineering ................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 0.040 s]
>>>>>>>>>>>>> [INFO] Apache Juneau UberJar ..............................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 1.008 s]
>>>>>>>>>>>>> [INFO] Apache Juneau Distribution .........................
>>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>>> [
>>>>>>>>>>>>> 0.768 s]
>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>> ------------
>>>>>>>>>>>>> [INFO] BUILD SUCCESS
>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>> ------------
>>>>>>>>>>>>> [INFO] Total time: 03:01 min
>>>>>>>>>>>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>>>>>>>>>>>>> [INFO] Final Memory: 87M/773M
>>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>> ------------
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Raphi D Lee, yidonguk@gmail.com
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org>
>>>>>>>>>>>>> 작성:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I am pleased to be calling this vote for the source release of
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Apache
>>>>>>>>>>>>>> Juneau 6.4.0-incubating RC2.
>>>>>>>>>>>>>> This includes some fixes for bugs found in RC1 and some
>>>>>>>>>>>>>> packaging
>>>>>>>>>>>>>> changes
>>>>>>>>>>>>>> for the example and template projects.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The list of new features can be found here:
>>>>>>>>>>>>>> http://juneau.incubator.apache.org/site/apidocs/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> overview-summary.html#6.4.0
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> The binaries are available at:
>>>>>>>>>>>>>
>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> binaries/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> The release candidate to be voted over is available at:
>>>>>>>>>>>>>
>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> source/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> SHA-1 checksums:
>>>>>>>>>>>>>
>>>>>>>>>>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
>>>>>>>>>>>>>> 0-incubating-src.zip
>>>>>>>>>>>>>> c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
>>>>>>>>>>>>>> 0-incubating-bin.zip
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> MD5 checksums:
>>>>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>>>>>>>>>> apache-juneau-6.4.0-incubating
>>>>>>>>>>>>>> -src.zip
>>>>>>>>>>>>>> 4e96d5047c0e9f03f0def2d017521f13
>>>>>>>>>>>>>> apache-juneau-6.4.0-incubating
>>>>>>>>>>>>>> -bin.zip
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Build the release candidate using:
>>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The release candidate is signed with a GPG key available at:
>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/juneau/
>>>>>>>>>>>>>> KEYS
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> A staged Maven repository is available for review at:
>>>>>>>>>>>>>> https://repository.apache.org/content/repositories/orgapache
>>>>>>>>>>>>>> juneau-1016/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The Git commit for this release is...
>>>>>>>>>>>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b
>>>>>>>>>>>>>> 37
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b
>>>>>>>>>>>>>> 37>*
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> Please vote on releasing this package as:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Apache Juneau 6.4.0-incubating
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> This vote will be open until 20-Sep-2017 9:00pm EST and passes
>>>>>>>>>>>>>> if a
>>>>>>>>>>>>>> majority of at least three +1 Apache Juneau PPMC votes are
>>>>>>>>>>>>>> cast.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [ ] +1 Release this package
>>>>>>>>>>>>>> [ ] 0 I don't feel strongly about it, but don't object
>>>>>>>>>>>>>> [ ] -1 Do not release this package because...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Anyone can participate in testing and voting, not just
>>>>>>>>>>>>>> committers,
>>>>>>>>>>>>>> please
>>>>>>>>>>>>>> feel free to try out the release candidate and provide your
>>>>>>>>>>>>>> votes.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by David Goddard <go...@acm.org>.
Most things are in some way IBM's fault :)
Trying both variants of your fix gives similar results. Better in both
cases, but not quite there. Details below.
It looks to me on a quick read that those cases that now fail are
failing because they *do* expect a value between the parentheses, and of
course the fix strips that out. For example, here's test 205:
{ "205", testDate, CalendarSwap.DateTimeLong.class, "en_UK",
Locale.KOREA, null, null, "2001년 3월 3일 (토) 오전 10시 11분 12초" },
I guess we could bend the test a little further by conditionally only
stripping out the parenthetical content if the expected value doesn't
contain values in parentheses itself, but that be regarded as a fix too
far...
#######################
actual = actual.replaceAll("\\([^\\)]+\\) ", "");
actual2 = actual2.replaceAll("\\([^\\)]+\\) ", "");
...leads to:
Tests run: 460, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 19.485
sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
test[205](org.apache.juneau.transforms.LocalizedDatesTest) Time
elapsed: 0.004 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
but was:<2001? 3? 3? []?? 10? 11? 12?>
at
org.apache.juneau.transforms.LocalizedDatesTest.test(LocalizedDatesTest.java:660)
test[435](org.apache.juneau.transforms.LocalizedDatesTest) Time
elapsed: 0.001 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
but was:<2001? 3? 3? []?? 10? 11? 12?>
at
org.apache.juneau.transforms.LocalizedDatesTest.test(LocalizedDatesTest.java:660)
With the different location for the space in the regexp, I get a longer
list of failures:
#######################
actual = actual.replaceAll(" \\([^\\)]+\\)", "");
actual2 = actual2.replaceAll(" \\([^\\)]+\\)", "");
... leads to:
Running org.apache.juneau.transforms.LocalizedDatesTest
Tests run: 460, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 0.189
sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
test[125](org.apache.juneau.transforms.LocalizedDatesTest) Time
elapsed: 0.003 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<2001? 3? 3?[ (?)]> but was:<2001?
3? 3?[]>
at
org.apache.juneau.transforms.LocalizedDatesTest.test(LocalizedDatesTest.java:660)
test[205](org.apache.juneau.transforms.LocalizedDatesTest) Time
elapsed: 0 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
but was:<2001? 3? 3? []?? 10? 11? 12?>
at
org.apache.juneau.transforms.LocalizedDatesTest.test(LocalizedDatesTest.java:660)
test[355](org.apache.juneau.transforms.LocalizedDatesTest) Time
elapsed: 0 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<2001? 3? 3?[ (?)]> but was:<2001?
3? 3?[]>
at
org.apache.juneau.transforms.LocalizedDatesTest.test(LocalizedDatesTest.java:660)
test[435](org.apache.juneau.transforms.LocalizedDatesTest) Time
elapsed: 0.001 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<2001? 3? 3? [(?) ]?? 10? 11? 12?>
but was:<2001? 3? 3? []?? 10? 11? 12?>
at
org.apache.juneau.transforms.LocalizedDatesTest.test(LocalizedDatesTest.java:660)
#######################
On 22/09/2017 00:05, James Bognar wrote:
> Ah...so we can blame IBM :-)
>
> Can you see if swapping the location of the space in the regular
> expressions fixes all the tests?
> actual = actual.replaceAll(" \\([^\\)]+\\)", "");
>
> On Thu, Sep 21, 2017 at 6:01 PM, David Goddard <go...@acm.org> wrote:
>
>> Just to add:
>>
>>> Maybe it's JVM vendor-specific behavior?
>>
>> Yes, I've now tested again after changing from an IBM JRE to an Oracle JRE
>> - this resolves the problem. It looks like this is specific to the IBM JRE
>> then. My Mac testing was done with an Oracle JRE, so I think this is
>> probably JVM-specific rather than OS-specific.
>>
>>
>> On 21/09/2017 23:46, David Goddard wrote:
>>
>>> Actual text is:
>>>
>>> 2001年3月3日 (土曜日)
>>> (I've attached a copy as a text file also)
>>>
>>> In this case, I it looks like the value between the parenthesis is the
>>> day name, "Saturday". So the expected value is just the date (2001年3月 3日),
>>> but the day is being added in the process.
>>>
>>>
>>> On 21/09/2017 22:45, James Bognar wrote:
>>>
>>>> Interesting. So the behavior of...
>>>>
>>>> DateFormat.getDateInstance(DateFormat.FULL, locale).format(date);
>>>> DateFormat.getDateTimeInstance(DateFormat.FULL, DateFormat.FULL, locale
>>>> ).format(date);
>>>>
>>>> ...returns different formats depending on the OS. Lovely.
>>>>
>>>> Maybe it's JVM vendor-specific behavior?
>>>>
>>>> I'm curious to know what's in those parentheses...
>>>> 2001?3?3? [*(???)* ]10?11?12? GMT
>>>>
>>>> Might give me something to google for.
>>>>
>>>> It's technically a test-only issue. We can probably 'fix' the testcase
>>>> by
>>>> just stripping out the formatting difference...
>>>>
>>>> @Test
>>>> public void test() {
>>>> BeanSession session = ps.getBeanContext().createSession(new
>>>> BeanSessionArgs(null, sessionLocale, sessionTimeZone, null));
>>>> String actual = session.convertToType(calendar, String.class);
>>>> *actual = actual.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>>>> Windows-specific
>>>> formatting difference*
>>>> assertEquals(expected, actual);
>>>> Object c2 = session.convertToType(actual, calendar.getClass());
>>>> String actual2 = session.convertToType(c2, String.class);
>>>> *actual2 = actual2.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>>>> Windows-specific formatting difference*
>>>> assertEquals(expected, actual2);
>>>> }
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Sep 21, 2017 at 3:11 PM, David Goddard <go...@acm.org> wrote:
>>>>
>>>> Hi,
>>>>>
>>>>> Yes, that fixed it, thanks. It also still tests OK on my Mac after the
>>>>> change.
>>>>>
>>>>> I'm now running into some further test issues, also on Windows only.
>>>>>
>>>>> ########################
>>>>>
>>>>> Tests run: 460, Failures: 16, Errors: 0, Skipped: 0, Time elapsed: 0.247
>>>>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
>>>>> test[111](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>> elapsed:
>>>>> 0.015 sec <<< FAILURE!
>>>>> org.junit.ComparisonFailure: expected:<2001?3?3?[]> but was:<2001?3?3?[
>>>>> (???)]>
>>>>> at org.apache.juneau.transforms.L
>>>>> ocalizedDatesTest.test(Localiz
>>>>> edDatesTest.java:645)
>>>>>
>>>>> [...]
>>>>> test[423](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>> elapsed:
>>>>> 0 sec <<< FAILURE!
>>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT> but
>>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>>>> at org.apache.juneau.transforms.L
>>>>> ocalizedDatesTest.test(Localiz
>>>>> edDatesTest.java:645)
>>>>>
>>>>> test[424](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>>> elapsed:
>>>>> 0 sec <<< FAILURE!
>>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT> but
>>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>>>> at org.apache.juneau.transforms.L
>>>>> ocalizedDatesTest.test(Localiz
>>>>> edDatesTest.java:645)
>>>>>
>>>>> ########################
>>>>>
>>>>>
>>>>> These are specific to date swap tests in Japanese & Korean:
>>>>>
>>>>> { "421", testDate.getTime(), DateSwap.DateTimeFull.class, "ja_JP", null,
>>>>> null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>> { "422", testDate.getTime(), DateSwap.DateTimeFull.class, Locale.JAPAN,
>>>>> null, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>> { "423", testDate.getTime(), DateSwap.DateTimeFull.class, null,
>>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>> { "424", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>>> { "425", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>>>>> Locale.KOREA, null, null, "2001ë…„ 3ì›” 3ì�¼ í† ìš”ì�¼ ì˜¤ì „ 10ì‹œ
>>>>> 11분
>>>>> 12ì´ˆ GMT" },
>>>>> etc.
>>>>>
>>>>> All the date swaps where the test date contains Japanese or Korean
>>>>> characters in the date part fail in this way. I initially thought it
>>>>> was
>>>>> the code page of the file, but I've changed to UTF-8 from the default
>>>>> and
>>>>> this didn't resolve this for me. Again, this is specific to my Windows
>>>>> platform - all is fine on Mac.
>>>>>
>>>>> Given that this is a build test error, and specific to one platform (and
>>>>> possibly one machine), I'm not sure that it is a fatal problem for the
>>>>> release.
>>>>>
>>>>> David
>>>>>
>>>>>
>>>>>
>>>>> On 21/09/2017 14:55, James Bognar wrote:
>>>>>
>>>>> Hi David,
>>>>>>
>>>>>> I don't have a Windows machine anymore :-(
>>>>>>
>>>>>> It looks like a test issue. Is it only RDF tests that are failing?
>>>>>>
>>>>>> Can you find line 484 in org.apache.juneau.TestUtils in
>>>>>> juneau-core-tests...
>>>>>>
>>>>>> String[] e = expected.trim().split("\n"), a =
>>>>>> actual.trim().split("\n");
>>>>>>
>>>>>> ...and change it to this?...
>>>>>>
>>>>>> String[] e = expected.trim().split("[\r\n]+"), a =
>>>>>> actual.trim().split(
>>>>>> "[\r\n]+");
>>>>>>
>>>>>>
>>>>>> Background on this method: Since Jena does not guarantee the order of
>>>>>> entries in the generated RDF (it's pretty much random), it's difficult
>>>>>> to
>>>>>> do simple comparison validation. So instead, we sort the expected and
>>>>>> actual lines and then check for comparison. It's not perfect (XML
>>>>>> attribute order can also be random), but generally good enough for what
>>>>>> we're testing.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Sep 21, 2017 at 5:52 AM, David Goddard <go...@acm.org>
>>>>>> wrote:
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>>>
>>>>>>> I'm seeting a whole load of test failures in juneau-core parsing
>>>>>>> (every
>>>>>>> round trip test is failing for me). For example:
>>>>>>>
>>>>>>>
>>>>>>> ByteArrayBase64SwapComboTest>ComboRoundTripTest.g32_parseRdf
>>>>>>>>
>>>>>>> XmlR:701->ComboRoundTripTest.testParse:205 ByteArray2d/parseRdfXmlR
>>>>>>> parse-normal failed expected:<<rdf:RDF>[
>>>>>>> <rdf:Seq>
>>>>>>> <rdf:li>AQID</rdf:li>
>>>>>>> <rdf:li>BAUG</rdf:li>
>>>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>>>
>>>>>>>
>>>>>>>> </rdf:Seq>
>>>>>>>>
>>>>>>> </rdf:RDF>]
>>>>>>>
>>>>>>> but was:<<rdf:RDF>[
>>>>>>>>
>>>>>>>> <rdf:Seq>
>>>>>>> <rdf:li>AQID</rdf:li>
>>>>>>> <rdf:li>BAUG</rdf:li>
>>>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>>>
>>>>>>>
>>>>>>>> </rdf:Seq>
>>>>>>>>
>>>>>>> </rdf:RDF>
>>>>>>> ]
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> The only consistent difference I see is that the final closing square
>>>>>>> bracket is appearing on a new line. Perhaps this is a character
>>>>>>> encoding
>>>>>>> issue (although I wouldn't rule out user error) - these tests fail on
>>>>>>> a
>>>>>>> Windows platform, but work fine on a Mac.
>>>>>>>
>>>>>>> David
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 20/09/2017 15:39, James Bognar wrote:
>>>>>>>
>>>>>>> Indeed they are.
>>>>>>>
>>>>>>>>
>>>>>>>> I've fixed them in Git. Thanks David!
>>>>>>>>
>>>>>>>> On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <go...@acm.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> I'm seeing a couple of issues with the Eclipse project names when
>>>>>>>>
>>>>>>>> importing a fresh clone into a workspace.
>>>>>>>>>
>>>>>>>>> juneau-microservice/.project has <name>juneau-rest</name>
>>>>>>>>> juneau-doc/.project has <name>juneau-marshall</name>
>>>>>>>>>
>>>>>>>>> I'm assuming these are copy/paste errors arising from the
>>>>>>>>> restructuring.
>>>>>>>>>
>>>>>>>>> David
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 19/09/2017 18:26, Charles Mims wrote:
>>>>>>>>>
>>>>>>>>> +1, with intermittent test failures in Apache Juneau Microservice
>>>>>>>>> Tests
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> MD5 (apache-juneau-6.4.0-incubating-src.zip) =
>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>>>>>> For me it failed on the 1st and 2nd try, passed on the 3rd.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <
>>>>>>>>>> jamesbognar@apache.org>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we
>>>>>>>>>> need
>>>>>>>>>> to
>>>>>>>>>>
>>>>>>>>>> handle this problem soon.
>>>>>>>>>>>
>>>>>>>>>>> Darn.
>>>>>>>>>>>
>>>>>>>>>>> I'm thinking it must be an issue with Jetty since we just upgraded
>>>>>>>>>>> it.
>>>>>>>>>>> From the Jetty side, the connection is open waiting for data,
>>>>>>>>>>> but
>>>>>>>>>>> that's
>>>>>>>>>>> all I know.
>>>>>>>>>>>
>>>>>>>>>>> I'll have to figure out how to use Fiddler and do some low-level
>>>>>>>>>>> debugging. It's really hard to reproduce though :-(
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <yidonguk@gmail.com
>>>>>>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> +1
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> SHA1, MD5 Checksum OK
>>>>>>>>>>>> Maven Build OK
>>>>>>>>>>>>
>>>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we
>>>>>>>>>>>> need
>>>>>>>>>>>> to
>>>>>>>>>>>> handle this problem soon.
>>>>>>>>>>>>
>>>>>>>>>>>> [INFO] Reactor Summary:
>>>>>>>>>>>> [INFO]
>>>>>>>>>>>> [INFO] Apache Juneau (incubating) .........................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 10.521 s]
>>>>>>>>>>>> [INFO] Apache Juneau - Core APIs ..........................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 0.737 s]
>>>>>>>>>>>> [INFO] Apache Juneau Marshall .............................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 45.444 s]
>>>>>>>>>>>> [INFO] Apache Juneau Marshal RDF ..........................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 3.558 s]
>>>>>>>>>>>> [INFO] Apache Juneau Data Transfer Objects ................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 6.813 s]
>>>>>>>>>>>> [INFO] Apache Juneau Core .................................
>>>>>>>>>>>> SUCCESS [
>>>>>>>>>>>> 1.025 s]
>>>>>>>>>>>> [INFO] Apache Juneau Config File API ......................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 1.928 s]
>>>>>>>>>>>> [INFO] Apache Juneau Core Tests ...........................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [01:04
>>>>>>>>>>>> min]
>>>>>>>>>>>> [INFO] Apache Juneau - REST APIs ..........................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 0.080 s]
>>>>>>>>>>>> [INFO] Apache Juneau REST Servlet API .....................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 2.331 s]
>>>>>>>>>>>> [INFO] Apache Juneau REST JAX/RS API ......................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 0.476 s]
>>>>>>>>>>>> [INFO] Apache Juneau REST Client API ......................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 1.005 s]
>>>>>>>>>>>> [INFO] Apache Juneau - Microservice APIs ..................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 0.068 s]
>>>>>>>>>>>> [INFO] Apache Juneau Microservice Server ..................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 1.588 s]
>>>>>>>>>>>> [INFO] Apache Juneau Microservice Template ................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 1.243 s]
>>>>>>>>>>>> [INFO] Apache Juneau - Examples ...........................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 0.183 s]
>>>>>>>>>>>> [INFO] Apache Juneau REST Examples ........................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 8.512 s]
>>>>>>>>>>>> [INFO] Apache Juneau Microservice Tests ...................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 24.522 s]
>>>>>>>>>>>> [INFO] Apache Juneau Core Examples ........................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 0.287 s]
>>>>>>>>>>>> [INFO] Apache Juneau Javadocs .............................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 0.617 s]
>>>>>>>>>>>> [INFO] Apache Juneau - Release Engineering ................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 0.040 s]
>>>>>>>>>>>> [INFO] Apache Juneau UberJar ..............................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 1.008 s]
>>>>>>>>>>>> [INFO] Apache Juneau Distribution .........................
>>>>>>>>>>>> SUCCESS
>>>>>>>>>>>> [
>>>>>>>>>>>> 0.768 s]
>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>> ------------
>>>>>>>>>>>> [INFO] BUILD SUCCESS
>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>> ------------
>>>>>>>>>>>> [INFO] Total time: 03:01 min
>>>>>>>>>>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>>>>>>>>>>>> [INFO] Final Memory: 87M/773M
>>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>> ------------
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Raphi D Lee, yidonguk@gmail.com
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org> 작성:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> I am pleased to be calling this vote for the source release of
>>>>>>>>>>>>> Apache
>>>>>>>>>>>>> Juneau 6.4.0-incubating RC2.
>>>>>>>>>>>>> This includes some fixes for bugs found in RC1 and some
>>>>>>>>>>>>> packaging
>>>>>>>>>>>>> changes
>>>>>>>>>>>>> for the example and template projects.
>>>>>>>>>>>>>
>>>>>>>>>>>>> The list of new features can be found here:
>>>>>>>>>>>>> http://juneau.incubator.apache.org/site/apidocs/
>>>>>>>>>>>>>
>>>>>>>>>>>>> overview-summary.html#6.4.0
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> The binaries are available at:
>>>>>>>>>>>>
>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>>>
>>>>>>>>>>>>> binaries/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> The release candidate to be voted over is available at:
>>>>>>>>>>>>
>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>>>
>>>>>>>>>>>>> source/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> SHA-1 checksums:
>>>>>>>>>>>>
>>>>>>>>>>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
>>>>>>>>>>>>> 0-incubating-src.zip
>>>>>>>>>>>>> c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
>>>>>>>>>>>>> 0-incubating-bin.zip
>>>>>>>>>>>>>
>>>>>>>>>>>>> MD5 checksums:
>>>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb apache-juneau-6.4.0-incubating
>>>>>>>>>>>>> -src.zip
>>>>>>>>>>>>> 4e96d5047c0e9f03f0def2d017521f13 apache-juneau-6.4.0-incubating
>>>>>>>>>>>>> -bin.zip
>>>>>>>>>>>>>
>>>>>>>>>>>>> Build the release candidate using:
>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>
>>>>>>>>>>>>> The release candidate is signed with a GPG key available at:
>>>>>>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/juneau/
>>>>>>>>>>>>> KEYS
>>>>>>>>>>>>>
>>>>>>>>>>>>> A staged Maven repository is available for review at:
>>>>>>>>>>>>> https://repository.apache.org/content/repositories/orgapache
>>>>>>>>>>>>> juneau-1016/
>>>>>>>>>>>>>
>>>>>>>>>>>>> The Git commit for this release is...
>>>>>>>>>>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>>>
>>>>>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b
>>>>>>>>>>>>> 37>*
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Please vote on releasing this package as:
>>>>>>>>>>>>
>>>>>>>>>>>>> Apache Juneau 6.4.0-incubating
>>>>>>>>>>>>>
>>>>>>>>>>>>> This vote will be open until 20-Sep-2017 9:00pm EST and passes
>>>>>>>>>>>>> if a
>>>>>>>>>>>>> majority of at least three +1 Apache Juneau PPMC votes are cast.
>>>>>>>>>>>>>
>>>>>>>>>>>>> [ ] +1 Release this package
>>>>>>>>>>>>> [ ] 0 I don't feel strongly about it, but don't object
>>>>>>>>>>>>> [ ] -1 Do not release this package because...
>>>>>>>>>>>>>
>>>>>>>>>>>>> Anyone can participate in testing and voting, not just
>>>>>>>>>>>>> committers,
>>>>>>>>>>>>> please
>>>>>>>>>>>>> feel free to try out the release candidate and provide your
>>>>>>>>>>>>> votes.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by James Bognar <ja...@apache.org>.
Ah...so we can blame IBM :-)
Can you see if swapping the location of the space in the regular
expressions fixes all the tests?
actual = actual.replaceAll(" \\([^\\)]+\\)", "");
On Thu, Sep 21, 2017 at 6:01 PM, David Goddard <go...@acm.org> wrote:
> Just to add:
>
> > Maybe it's JVM vendor-specific behavior?
>
> Yes, I've now tested again after changing from an IBM JRE to an Oracle JRE
> - this resolves the problem. It looks like this is specific to the IBM JRE
> then. My Mac testing was done with an Oracle JRE, so I think this is
> probably JVM-specific rather than OS-specific.
>
>
> On 21/09/2017 23:46, David Goddard wrote:
>
>> Actual text is:
>>
>> 2001年3月3日 (土曜日)
>> (I've attached a copy as a text file also)
>>
>> In this case, I it looks like the value between the parenthesis is the
>> day name, "Saturday". So the expected value is just the date (2001年3月 3日),
>> but the day is being added in the process.
>>
>>
>> On 21/09/2017 22:45, James Bognar wrote:
>>
>>> Interesting. So the behavior of...
>>>
>>> DateFormat.getDateInstance(DateFormat.FULL, locale).format(date);
>>> DateFormat.getDateTimeInstance(DateFormat.FULL, DateFormat.FULL, locale
>>> ).format(date);
>>>
>>> ...returns different formats depending on the OS. Lovely.
>>>
>>> Maybe it's JVM vendor-specific behavior?
>>>
>>> I'm curious to know what's in those parentheses...
>>> 2001?3?3? [*(???)* ]10?11?12? GMT
>>>
>>> Might give me something to google for.
>>>
>>> It's technically a test-only issue. We can probably 'fix' the testcase
>>> by
>>> just stripping out the formatting difference...
>>>
>>> @Test
>>> public void test() {
>>> BeanSession session = ps.getBeanContext().createSession(new
>>> BeanSessionArgs(null, sessionLocale, sessionTimeZone, null));
>>> String actual = session.convertToType(calendar, String.class);
>>> *actual = actual.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>>> Windows-specific
>>> formatting difference*
>>> assertEquals(expected, actual);
>>> Object c2 = session.convertToType(actual, calendar.getClass());
>>> String actual2 = session.convertToType(c2, String.class);
>>> *actual2 = actual2.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>>> Windows-specific formatting difference*
>>> assertEquals(expected, actual2);
>>> }
>>>
>>>
>>>
>>>
>>>
>>> On Thu, Sep 21, 2017 at 3:11 PM, David Goddard <go...@acm.org> wrote:
>>>
>>> Hi,
>>>>
>>>> Yes, that fixed it, thanks. It also still tests OK on my Mac after the
>>>> change.
>>>>
>>>> I'm now running into some further test issues, also on Windows only.
>>>>
>>>> ########################
>>>>
>>>> Tests run: 460, Failures: 16, Errors: 0, Skipped: 0, Time elapsed: 0.247
>>>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
>>>> test[111](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>> elapsed:
>>>> 0.015 sec <<< FAILURE!
>>>> org.junit.ComparisonFailure: expected:<2001?3?3?[]> but was:<2001?3?3?[
>>>> (???)]>
>>>> at org.apache.juneau.transforms.L
>>>> ocalizedDatesTest.test(Localiz
>>>> edDatesTest.java:645)
>>>>
>>>> [...]
>>>> test[423](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>> elapsed:
>>>> 0 sec <<< FAILURE!
>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT> but
>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>>> at org.apache.juneau.transforms.L
>>>> ocalizedDatesTest.test(Localiz
>>>> edDatesTest.java:645)
>>>>
>>>> test[424](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>>> elapsed:
>>>> 0 sec <<< FAILURE!
>>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT> but
>>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>>> at org.apache.juneau.transforms.L
>>>> ocalizedDatesTest.test(Localiz
>>>> edDatesTest.java:645)
>>>>
>>>> ########################
>>>>
>>>>
>>>> These are specific to date swap tests in Japanese & Korean:
>>>>
>>>> { "421", testDate.getTime(), DateSwap.DateTimeFull.class, "ja_JP", null,
>>>> null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>> { "422", testDate.getTime(), DateSwap.DateTimeFull.class, Locale.JAPAN,
>>>> null, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>> { "423", testDate.getTime(), DateSwap.DateTimeFull.class, null,
>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>> { "424", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>>> { "425", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>>>> Locale.KOREA, null, null, "2001ë…„ 3ì›” 3ì�¼ í† ìš”ì�¼ ì˜¤ì „ 10ì‹œ
>>>> 11분
>>>> 12ì´ˆ GMT" },
>>>> etc.
>>>>
>>>> All the date swaps where the test date contains Japanese or Korean
>>>> characters in the date part fail in this way. I initially thought it
>>>> was
>>>> the code page of the file, but I've changed to UTF-8 from the default
>>>> and
>>>> this didn't resolve this for me. Again, this is specific to my Windows
>>>> platform - all is fine on Mac.
>>>>
>>>> Given that this is a build test error, and specific to one platform (and
>>>> possibly one machine), I'm not sure that it is a fatal problem for the
>>>> release.
>>>>
>>>> David
>>>>
>>>>
>>>>
>>>> On 21/09/2017 14:55, James Bognar wrote:
>>>>
>>>> Hi David,
>>>>>
>>>>> I don't have a Windows machine anymore :-(
>>>>>
>>>>> It looks like a test issue. Is it only RDF tests that are failing?
>>>>>
>>>>> Can you find line 484 in org.apache.juneau.TestUtils in
>>>>> juneau-core-tests...
>>>>>
>>>>> String[] e = expected.trim().split("\n"), a =
>>>>> actual.trim().split("\n");
>>>>>
>>>>> ...and change it to this?...
>>>>>
>>>>> String[] e = expected.trim().split("[\r\n]+"), a =
>>>>> actual.trim().split(
>>>>> "[\r\n]+");
>>>>>
>>>>>
>>>>> Background on this method: Since Jena does not guarantee the order of
>>>>> entries in the generated RDF (it's pretty much random), it's difficult
>>>>> to
>>>>> do simple comparison validation. So instead, we sort the expected and
>>>>> actual lines and then check for comparison. It's not perfect (XML
>>>>> attribute order can also be random), but generally good enough for what
>>>>> we're testing.
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Sep 21, 2017 at 5:52 AM, David Goddard <go...@acm.org>
>>>>> wrote:
>>>>>
>>>>> Thanks.
>>>>>
>>>>>>
>>>>>> I'm seeting a whole load of test failures in juneau-core parsing
>>>>>> (every
>>>>>> round trip test is failing for me). For example:
>>>>>>
>>>>>>
>>>>>> ByteArrayBase64SwapComboTest>ComboRoundTripTest.g32_parseRdf
>>>>>>>
>>>>>> XmlR:701->ComboRoundTripTest.testParse:205 ByteArray2d/parseRdfXmlR
>>>>>> parse-normal failed expected:<<rdf:RDF>[
>>>>>> <rdf:Seq>
>>>>>> <rdf:li>AQID</rdf:li>
>>>>>> <rdf:li>BAUG</rdf:li>
>>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>>
>>>>>>
>>>>>>> </rdf:Seq>
>>>>>>>
>>>>>> </rdf:RDF>]
>>>>>>
>>>>>> but was:<<rdf:RDF>[
>>>>>>>
>>>>>>> <rdf:Seq>
>>>>>> <rdf:li>AQID</rdf:li>
>>>>>> <rdf:li>BAUG</rdf:li>
>>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>>
>>>>>>
>>>>>>> </rdf:Seq>
>>>>>>>
>>>>>> </rdf:RDF>
>>>>>> ]
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> The only consistent difference I see is that the final closing square
>>>>>> bracket is appearing on a new line. Perhaps this is a character
>>>>>> encoding
>>>>>> issue (although I wouldn't rule out user error) - these tests fail on
>>>>>> a
>>>>>> Windows platform, but work fine on a Mac.
>>>>>>
>>>>>> David
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 20/09/2017 15:39, James Bognar wrote:
>>>>>>
>>>>>> Indeed they are.
>>>>>>
>>>>>>>
>>>>>>> I've fixed them in Git. Thanks David!
>>>>>>>
>>>>>>> On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <go...@acm.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>> I'm seeing a couple of issues with the Eclipse project names when
>>>>>>>
>>>>>>> importing a fresh clone into a workspace.
>>>>>>>>
>>>>>>>> juneau-microservice/.project has <name>juneau-rest</name>
>>>>>>>> juneau-doc/.project has <name>juneau-marshall</name>
>>>>>>>>
>>>>>>>> I'm assuming these are copy/paste errors arising from the
>>>>>>>> restructuring.
>>>>>>>>
>>>>>>>> David
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 19/09/2017 18:26, Charles Mims wrote:
>>>>>>>>
>>>>>>>> +1, with intermittent test failures in Apache Juneau Microservice
>>>>>>>> Tests
>>>>>>>>
>>>>>>>>
>>>>>>>>> MD5 (apache-juneau-6.4.0-incubating-src.zip) =
>>>>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>>>>> For me it failed on the 1st and 2nd try, passed on the 3rd.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <
>>>>>>>>> jamesbognar@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we
>>>>>>>>> need
>>>>>>>>> to
>>>>>>>>>
>>>>>>>>> handle this problem soon.
>>>>>>>>>>
>>>>>>>>>> Darn.
>>>>>>>>>>
>>>>>>>>>> I'm thinking it must be an issue with Jetty since we just upgraded
>>>>>>>>>> it.
>>>>>>>>>> From the Jetty side, the connection is open waiting for data,
>>>>>>>>>> but
>>>>>>>>>> that's
>>>>>>>>>> all I know.
>>>>>>>>>>
>>>>>>>>>> I'll have to figure out how to use Fiddler and do some low-level
>>>>>>>>>> debugging. It's really hard to reproduce though :-(
>>>>>>>>>>
>>>>>>>>>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <yidonguk@gmail.com
>>>>>>>>>> >
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> SHA1, MD5 Checksum OK
>>>>>>>>>>> Maven Build OK
>>>>>>>>>>>
>>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we
>>>>>>>>>>> need
>>>>>>>>>>> to
>>>>>>>>>>> handle this problem soon.
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Reactor Summary:
>>>>>>>>>>> [INFO]
>>>>>>>>>>> [INFO] Apache Juneau (incubating) .........................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 10.521 s]
>>>>>>>>>>> [INFO] Apache Juneau - Core APIs ..........................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 0.737 s]
>>>>>>>>>>> [INFO] Apache Juneau Marshall .............................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 45.444 s]
>>>>>>>>>>> [INFO] Apache Juneau Marshal RDF ..........................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 3.558 s]
>>>>>>>>>>> [INFO] Apache Juneau Data Transfer Objects ................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 6.813 s]
>>>>>>>>>>> [INFO] Apache Juneau Core .................................
>>>>>>>>>>> SUCCESS [
>>>>>>>>>>> 1.025 s]
>>>>>>>>>>> [INFO] Apache Juneau Config File API ......................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 1.928 s]
>>>>>>>>>>> [INFO] Apache Juneau Core Tests ...........................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [01:04
>>>>>>>>>>> min]
>>>>>>>>>>> [INFO] Apache Juneau - REST APIs ..........................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 0.080 s]
>>>>>>>>>>> [INFO] Apache Juneau REST Servlet API .....................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 2.331 s]
>>>>>>>>>>> [INFO] Apache Juneau REST JAX/RS API ......................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 0.476 s]
>>>>>>>>>>> [INFO] Apache Juneau REST Client API ......................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 1.005 s]
>>>>>>>>>>> [INFO] Apache Juneau - Microservice APIs ..................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 0.068 s]
>>>>>>>>>>> [INFO] Apache Juneau Microservice Server ..................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 1.588 s]
>>>>>>>>>>> [INFO] Apache Juneau Microservice Template ................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 1.243 s]
>>>>>>>>>>> [INFO] Apache Juneau - Examples ...........................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 0.183 s]
>>>>>>>>>>> [INFO] Apache Juneau REST Examples ........................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 8.512 s]
>>>>>>>>>>> [INFO] Apache Juneau Microservice Tests ...................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 24.522 s]
>>>>>>>>>>> [INFO] Apache Juneau Core Examples ........................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 0.287 s]
>>>>>>>>>>> [INFO] Apache Juneau Javadocs .............................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 0.617 s]
>>>>>>>>>>> [INFO] Apache Juneau - Release Engineering ................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 0.040 s]
>>>>>>>>>>> [INFO] Apache Juneau UberJar ..............................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 1.008 s]
>>>>>>>>>>> [INFO] Apache Juneau Distribution .........................
>>>>>>>>>>> SUCCESS
>>>>>>>>>>> [
>>>>>>>>>>> 0.768 s]
>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>> ------------------------------
>>>>>>>>>>> ------------
>>>>>>>>>>> [INFO] BUILD SUCCESS
>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>> ------------------------------
>>>>>>>>>>> ------------
>>>>>>>>>>> [INFO] Total time: 03:01 min
>>>>>>>>>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>>>>>>>>>>> [INFO] Final Memory: 87M/773M
>>>>>>>>>>> [INFO] ------------------------------
>>>>>>>>>>> ------------------------------
>>>>>>>>>>> ------------
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Raphi D Lee, yidonguk@gmail.com
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org> 작성:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I am pleased to be calling this vote for the source release of
>>>>>>>>>>>> Apache
>>>>>>>>>>>> Juneau 6.4.0-incubating RC2.
>>>>>>>>>>>> This includes some fixes for bugs found in RC1 and some
>>>>>>>>>>>> packaging
>>>>>>>>>>>> changes
>>>>>>>>>>>> for the example and template projects.
>>>>>>>>>>>>
>>>>>>>>>>>> The list of new features can be found here:
>>>>>>>>>>>> http://juneau.incubator.apache.org/site/apidocs/
>>>>>>>>>>>>
>>>>>>>>>>>> overview-summary.html#6.4.0
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The binaries are available at:
>>>>>>>>>>>
>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>>
>>>>>>>>>>>> binaries/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The release candidate to be voted over is available at:
>>>>>>>>>>>
>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>>
>>>>>>>>>>>> source/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> SHA-1 checksums:
>>>>>>>>>>>
>>>>>>>>>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
>>>>>>>>>>>> 0-incubating-src.zip
>>>>>>>>>>>> c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
>>>>>>>>>>>> 0-incubating-bin.zip
>>>>>>>>>>>>
>>>>>>>>>>>> MD5 checksums:
>>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb apache-juneau-6.4.0-incubating
>>>>>>>>>>>> -src.zip
>>>>>>>>>>>> 4e96d5047c0e9f03f0def2d017521f13 apache-juneau-6.4.0-incubating
>>>>>>>>>>>> -bin.zip
>>>>>>>>>>>>
>>>>>>>>>>>> Build the release candidate using:
>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>
>>>>>>>>>>>> The release candidate is signed with a GPG key available at:
>>>>>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/juneau/
>>>>>>>>>>>> KEYS
>>>>>>>>>>>>
>>>>>>>>>>>> A staged Maven repository is available for review at:
>>>>>>>>>>>> https://repository.apache.org/content/repositories/orgapache
>>>>>>>>>>>> juneau-1016/
>>>>>>>>>>>>
>>>>>>>>>>>> The Git commit for this release is...
>>>>>>>>>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>>
>>>>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b
>>>>>>>>>>>> 37>*
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Please vote on releasing this package as:
>>>>>>>>>>>
>>>>>>>>>>>> Apache Juneau 6.4.0-incubating
>>>>>>>>>>>>
>>>>>>>>>>>> This vote will be open until 20-Sep-2017 9:00pm EST and passes
>>>>>>>>>>>> if a
>>>>>>>>>>>> majority of at least three +1 Apache Juneau PPMC votes are cast.
>>>>>>>>>>>>
>>>>>>>>>>>> [ ] +1 Release this package
>>>>>>>>>>>> [ ] 0 I don't feel strongly about it, but don't object
>>>>>>>>>>>> [ ] -1 Do not release this package because...
>>>>>>>>>>>>
>>>>>>>>>>>> Anyone can participate in testing and voting, not just
>>>>>>>>>>>> committers,
>>>>>>>>>>>> please
>>>>>>>>>>>> feel free to try out the release candidate and provide your
>>>>>>>>>>>> votes.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by David Goddard <go...@acm.org>.
Just to add:
> Maybe it's JVM vendor-specific behavior?
Yes, I've now tested again after changing from an IBM JRE to an Oracle
JRE - this resolves the problem. It looks like this is specific to the
IBM JRE then. My Mac testing was done with an Oracle JRE, so I think
this is probably JVM-specific rather than OS-specific.
On 21/09/2017 23:46, David Goddard wrote:
> Actual text is:
>
> 2001年3月3日 (土曜日)
> (I've attached a copy as a text file also)
>
> In this case, I it looks like the value between the parenthesis is the
> day name, "Saturday". So the expected value is just the date (2001年3月
> 3日), but the day is being added in the process.
>
> On 21/09/2017 22:45, James Bognar wrote:
>> Interesting. So the behavior of...
>>
>> DateFormat.getDateInstance(DateFormat.FULL, locale).format(date);
>> DateFormat.getDateTimeInstance(DateFormat.FULL, DateFormat.FULL, locale
>> ).format(date);
>>
>> ...returns different formats depending on the OS. Lovely.
>>
>> Maybe it's JVM vendor-specific behavior?
>>
>> I'm curious to know what's in those parentheses...
>> 2001?3?3? [*(???)* ]10?11?12? GMT
>>
>> Might give me something to google for.
>>
>> It's technically a test-only issue. We can probably 'fix' the
>> testcase by
>> just stripping out the formatting difference...
>>
>> @Test
>> public void test() {
>> BeanSession session = ps.getBeanContext().createSession(new
>> BeanSessionArgs(null, sessionLocale, sessionTimeZone, null));
>> String actual = session.convertToType(calendar, String.class);
>> *actual = actual.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>> Windows-specific
>> formatting difference*
>> assertEquals(expected, actual);
>> Object c2 = session.convertToType(actual, calendar.getClass());
>> String actual2 = session.convertToType(c2, String.class);
>> *actual2 = actual2.replaceAll("\\([^\\)]+\\) ", ""); // Fix
>> Windows-specific formatting difference*
>> assertEquals(expected, actual2);
>> }
>>
>>
>>
>>
>>
>> On Thu, Sep 21, 2017 at 3:11 PM, David Goddard <go...@acm.org> wrote:
>>
>>> Hi,
>>>
>>> Yes, that fixed it, thanks. It also still tests OK on my Mac after the
>>> change.
>>>
>>> I'm now running into some further test issues, also on Windows only.
>>>
>>> ########################
>>>
>>> Tests run: 460, Failures: 16, Errors: 0, Skipped: 0, Time elapsed: 0.247
>>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
>>> test[111](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>> elapsed:
>>> 0.015 sec <<< FAILURE!
>>> org.junit.ComparisonFailure: expected:<2001?3?3?[]> but was:<2001?3?3?[
>>> (???)]>
>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>>> edDatesTest.java:645)
>>>
>>> [...]
>>> test[423](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>> elapsed:
>>> 0 sec <<< FAILURE!
>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT> but
>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>>> edDatesTest.java:645)
>>>
>>> test[424](org.apache.juneau.transforms.LocalizedDatesTest) Time
>>> elapsed:
>>> 0 sec <<< FAILURE!
>>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT> but
>>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>>> edDatesTest.java:645)
>>>
>>> ########################
>>>
>>>
>>> These are specific to date swap tests in Japanese & Korean:
>>>
>>> { "421", testDate.getTime(), DateSwap.DateTimeFull.class, "ja_JP", null,
>>> null, null, "2001年3月3日 10時11分12秒 GMT" },
>>> { "422", testDate.getTime(), DateSwap.DateTimeFull.class, Locale.JAPAN,
>>> null, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>> { "423", testDate.getTime(), DateSwap.DateTimeFull.class, null,
>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>> { "424", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>>> { "425", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>>> Locale.KOREA, null, null, "2001ë…„ 3ì›” 3ì�¼ í† ìš”ì�¼ ì˜¤ì „ 10ì‹œ
>>> 11분
>>> 12ì´ˆ GMT" },
>>> etc.
>>>
>>> All the date swaps where the test date contains Japanese or Korean
>>> characters in the date part fail in this way. I initially thought it
>>> was
>>> the code page of the file, but I've changed to UTF-8 from the default
>>> and
>>> this didn't resolve this for me. Again, this is specific to my Windows
>>> platform - all is fine on Mac.
>>>
>>> Given that this is a build test error, and specific to one platform (and
>>> possibly one machine), I'm not sure that it is a fatal problem for the
>>> release.
>>>
>>> David
>>>
>>>
>>>
>>> On 21/09/2017 14:55, James Bognar wrote:
>>>
>>>> Hi David,
>>>>
>>>> I don't have a Windows machine anymore :-(
>>>>
>>>> It looks like a test issue. Is it only RDF tests that are failing?
>>>>
>>>> Can you find line 484 in org.apache.juneau.TestUtils in
>>>> juneau-core-tests...
>>>>
>>>> String[] e = expected.trim().split("\n"), a =
>>>> actual.trim().split("\n");
>>>>
>>>> ...and change it to this?...
>>>>
>>>> String[] e = expected.trim().split("[\r\n]+"), a = actual.trim().split(
>>>> "[\r\n]+");
>>>>
>>>>
>>>> Background on this method: Since Jena does not guarantee the order of
>>>> entries in the generated RDF (it's pretty much random), it's
>>>> difficult to
>>>> do simple comparison validation. So instead, we sort the expected and
>>>> actual lines and then check for comparison. It's not perfect (XML
>>>> attribute order can also be random), but generally good enough for what
>>>> we're testing.
>>>>
>>>>
>>>>
>>>> On Thu, Sep 21, 2017 at 5:52 AM, David Goddard <go...@acm.org> wrote:
>>>>
>>>> Thanks.
>>>>>
>>>>> I'm seeting a whole load of test failures in juneau-core parsing
>>>>> (every
>>>>> round trip test is failing for me). For example:
>>>>>
>>>>>
>>>>>> ByteArrayBase64SwapComboTest>ComboRoundTripTest.g32_parseRdf
>>>>> XmlR:701->ComboRoundTripTest.testParse:205 ByteArray2d/parseRdfXmlR
>>>>> parse-normal failed expected:<<rdf:RDF>[
>>>>> <rdf:Seq>
>>>>> <rdf:li>AQID</rdf:li>
>>>>> <rdf:li>BAUG</rdf:li>
>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>
>>>>>>
>>>>>> </rdf:Seq>
>>>>> </rdf:RDF>]
>>>>>
>>>>>> but was:<<rdf:RDF>[
>>>>>>
>>>>> <rdf:Seq>
>>>>> <rdf:li>AQID</rdf:li>
>>>>> <rdf:li>BAUG</rdf:li>
>>>>> <rdf:li rdf:resource='http://www.w3.or
>>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>>
>>>>>>
>>>>>> </rdf:Seq>
>>>>> </rdf:RDF>
>>>>> ]
>>>>>
>>>>>>
>>>>>>
>>>>> The only consistent difference I see is that the final closing square
>>>>> bracket is appearing on a new line. Perhaps this is a character
>>>>> encoding
>>>>> issue (although I wouldn't rule out user error) - these tests fail
>>>>> on a
>>>>> Windows platform, but work fine on a Mac.
>>>>>
>>>>> David
>>>>>
>>>>>
>>>>>
>>>>> On 20/09/2017 15:39, James Bognar wrote:
>>>>>
>>>>> Indeed they are.
>>>>>>
>>>>>> I've fixed them in Git. Thanks David!
>>>>>>
>>>>>> On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <go...@acm.org>
>>>>>> wrote:
>>>>>>
>>>>>> I'm seeing a couple of issues with the Eclipse project names when
>>>>>>
>>>>>>> importing a fresh clone into a workspace.
>>>>>>>
>>>>>>> juneau-microservice/.project has <name>juneau-rest</name>
>>>>>>> juneau-doc/.project has <name>juneau-marshall</name>
>>>>>>>
>>>>>>> I'm assuming these are copy/paste errors arising from the
>>>>>>> restructuring.
>>>>>>>
>>>>>>> David
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 19/09/2017 18:26, Charles Mims wrote:
>>>>>>>
>>>>>>> +1, with intermittent test failures in Apache Juneau Microservice
>>>>>>> Tests
>>>>>>>
>>>>>>>>
>>>>>>>> MD5 (apache-juneau-6.4.0-incubating-src.zip) =
>>>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>>>> For me it failed on the 1st and 2nd try, passed on the 3rd.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <
>>>>>>>> jamesbognar@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we
>>>>>>>> need
>>>>>>>> to
>>>>>>>>
>>>>>>>>> handle this problem soon.
>>>>>>>>>
>>>>>>>>> Darn.
>>>>>>>>>
>>>>>>>>> I'm thinking it must be an issue with Jetty since we just upgraded
>>>>>>>>> it.
>>>>>>>>> From the Jetty side, the connection is open waiting for
>>>>>>>>> data, but
>>>>>>>>> that's
>>>>>>>>> all I know.
>>>>>>>>>
>>>>>>>>> I'll have to figure out how to use Fiddler and do some low-level
>>>>>>>>> debugging. It's really hard to reproduce though :-(
>>>>>>>>>
>>>>>>>>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <yi...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> SHA1, MD5 Checksum OK
>>>>>>>>>> Maven Build OK
>>>>>>>>>>
>>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think
>>>>>>>>>> we need
>>>>>>>>>> to
>>>>>>>>>> handle this problem soon.
>>>>>>>>>>
>>>>>>>>>> [INFO] Reactor Summary:
>>>>>>>>>> [INFO]
>>>>>>>>>> [INFO] Apache Juneau (incubating) .........................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 10.521 s]
>>>>>>>>>> [INFO] Apache Juneau - Core APIs ..........................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 0.737 s]
>>>>>>>>>> [INFO] Apache Juneau Marshall .............................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 45.444 s]
>>>>>>>>>> [INFO] Apache Juneau Marshal RDF ..........................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 3.558 s]
>>>>>>>>>> [INFO] Apache Juneau Data Transfer Objects ................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 6.813 s]
>>>>>>>>>> [INFO] Apache Juneau Core .................................
>>>>>>>>>> SUCCESS [
>>>>>>>>>> 1.025 s]
>>>>>>>>>> [INFO] Apache Juneau Config File API ......................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 1.928 s]
>>>>>>>>>> [INFO] Apache Juneau Core Tests ...........................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [01:04
>>>>>>>>>> min]
>>>>>>>>>> [INFO] Apache Juneau - REST APIs ..........................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 0.080 s]
>>>>>>>>>> [INFO] Apache Juneau REST Servlet API .....................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 2.331 s]
>>>>>>>>>> [INFO] Apache Juneau REST JAX/RS API ......................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 0.476 s]
>>>>>>>>>> [INFO] Apache Juneau REST Client API ......................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 1.005 s]
>>>>>>>>>> [INFO] Apache Juneau - Microservice APIs ..................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 0.068 s]
>>>>>>>>>> [INFO] Apache Juneau Microservice Server ..................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 1.588 s]
>>>>>>>>>> [INFO] Apache Juneau Microservice Template ................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 1.243 s]
>>>>>>>>>> [INFO] Apache Juneau - Examples ...........................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 0.183 s]
>>>>>>>>>> [INFO] Apache Juneau REST Examples ........................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 8.512 s]
>>>>>>>>>> [INFO] Apache Juneau Microservice Tests ...................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 24.522 s]
>>>>>>>>>> [INFO] Apache Juneau Core Examples ........................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 0.287 s]
>>>>>>>>>> [INFO] Apache Juneau Javadocs .............................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 0.617 s]
>>>>>>>>>> [INFO] Apache Juneau - Release Engineering ................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 0.040 s]
>>>>>>>>>> [INFO] Apache Juneau UberJar ..............................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 1.008 s]
>>>>>>>>>> [INFO] Apache Juneau Distribution .........................
>>>>>>>>>> SUCCESS
>>>>>>>>>> [
>>>>>>>>>> 0.768 s]
>>>>>>>>>> [INFO]
>>>>>>>>>> ------------------------------------------------------------
>>>>>>>>>> ------------
>>>>>>>>>> [INFO] BUILD SUCCESS
>>>>>>>>>> [INFO]
>>>>>>>>>> ------------------------------------------------------------
>>>>>>>>>> ------------
>>>>>>>>>> [INFO] Total time: 03:01 min
>>>>>>>>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>>>>>>>>>> [INFO] Final Memory: 87M/773M
>>>>>>>>>> [INFO]
>>>>>>>>>> ------------------------------------------------------------
>>>>>>>>>> ------------
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Raphi D Lee, yidonguk@gmail.com
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org>
>>>>>>>>>> 작성:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> I am pleased to be calling this vote for the source release of
>>>>>>>>>>> Apache
>>>>>>>>>>> Juneau 6.4.0-incubating RC2.
>>>>>>>>>>> This includes some fixes for bugs found in RC1 and some
>>>>>>>>>>> packaging
>>>>>>>>>>> changes
>>>>>>>>>>> for the example and template projects.
>>>>>>>>>>>
>>>>>>>>>>> The list of new features can be found here:
>>>>>>>>>>> http://juneau.incubator.apache.org/site/apidocs/
>>>>>>>>>>>
>>>>>>>>>>> overview-summary.html#6.4.0
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> The binaries are available at:
>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>
>>>>>>>>>>> binaries/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> The release candidate to be voted over is available at:
>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>>
>>>>>>>>>>> source/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> SHA-1 checksums:
>>>>>>>>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
>>>>>>>>>>> 0-incubating-src.zip
>>>>>>>>>>> c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
>>>>>>>>>>> 0-incubating-bin.zip
>>>>>>>>>>>
>>>>>>>>>>> MD5 checksums:
>>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb apache-juneau-6.4.0-incubating
>>>>>>>>>>> -src.zip
>>>>>>>>>>> 4e96d5047c0e9f03f0def2d017521f13 apache-juneau-6.4.0-incubating
>>>>>>>>>>> -bin.zip
>>>>>>>>>>>
>>>>>>>>>>> Build the release candidate using:
>>>>>>>>>>> mvn clean install
>>>>>>>>>>>
>>>>>>>>>>> The release candidate is signed with a GPG key available at:
>>>>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS
>>>>>>>>>>>
>>>>>>>>>>> A staged Maven repository is available for review at:
>>>>>>>>>>> https://repository.apache.org/content/repositories/orgapache
>>>>>>>>>>> juneau-1016/
>>>>>>>>>>>
>>>>>>>>>>> The Git commit for this release is...
>>>>>>>>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>>
>>>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37>*
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Please vote on releasing this package as:
>>>>>>>>>>> Apache Juneau 6.4.0-incubating
>>>>>>>>>>>
>>>>>>>>>>> This vote will be open until 20-Sep-2017 9:00pm EST and
>>>>>>>>>>> passes if a
>>>>>>>>>>> majority of at least three +1 Apache Juneau PPMC votes are cast.
>>>>>>>>>>>
>>>>>>>>>>> [ ] +1 Release this package
>>>>>>>>>>> [ ] 0 I don't feel strongly about it, but don't object
>>>>>>>>>>> [ ] -1 Do not release this package because...
>>>>>>>>>>>
>>>>>>>>>>> Anyone can participate in testing and voting, not just
>>>>>>>>>>> committers,
>>>>>>>>>>> please
>>>>>>>>>>> feel free to try out the release candidate and provide your
>>>>>>>>>>> votes.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by David Goddard <go...@acm.org>.
Actual text is:
2001年3月3日 (土曜日)
(I've attached a copy as a text file also)
In this case, I it looks like the value between the parenthesis is the
day name, "Saturday". So the expected value is just the date
(2001年3月3日), but the day is being added in the process.
On 21/09/2017 22:45, James Bognar wrote:
> Interesting. So the behavior of...
>
> DateFormat.getDateInstance(DateFormat.FULL, locale).format(date);
> DateFormat.getDateTimeInstance(DateFormat.FULL, DateFormat.FULL, locale
> ).format(date);
>
> ...returns different formats depending on the OS. Lovely.
>
> Maybe it's JVM vendor-specific behavior?
>
> I'm curious to know what's in those parentheses...
> 2001?3?3? [*(???)* ]10?11?12? GMT
>
> Might give me something to google for.
>
> It's technically a test-only issue. We can probably 'fix' the testcase by
> just stripping out the formatting difference...
>
> @Test
> public void test() {
> BeanSession session = ps.getBeanContext().createSession(new
> BeanSessionArgs(null, sessionLocale, sessionTimeZone, null));
> String actual = session.convertToType(calendar, String.class);
> *actual = actual.replaceAll("\\([^\\)]+\\) ", ""); // Fix Windows-specific
> formatting difference*
> assertEquals(expected, actual);
> Object c2 = session.convertToType(actual, calendar.getClass());
> String actual2 = session.convertToType(c2, String.class);
> *actual2 = actual2.replaceAll("\\([^\\)]+\\) ", ""); // Fix
> Windows-specific formatting difference*
> assertEquals(expected, actual2);
> }
>
>
>
>
>
> On Thu, Sep 21, 2017 at 3:11 PM, David Goddard <go...@acm.org> wrote:
>
>> Hi,
>>
>> Yes, that fixed it, thanks. It also still tests OK on my Mac after the
>> change.
>>
>> I'm now running into some further test issues, also on Windows only.
>>
>> ########################
>>
>> Tests run: 460, Failures: 16, Errors: 0, Skipped: 0, Time elapsed: 0.247
>> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
>> test[111](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
>> 0.015 sec <<< FAILURE!
>> org.junit.ComparisonFailure: expected:<2001?3?3?[]> but was:<2001?3?3?[
>> (???)]>
>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>> edDatesTest.java:645)
>>
>> [...]
>> test[423](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
>> 0 sec <<< FAILURE!
>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT> but
>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>> edDatesTest.java:645)
>>
>> test[424](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
>> 0 sec <<< FAILURE!
>> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT> but
>> was:<2001?3?3? [(???) ]10?11?12? GMT>
>> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
>> edDatesTest.java:645)
>>
>> ########################
>>
>>
>> These are specific to date swap tests in Japanese & Korean:
>>
>> { "421", testDate.getTime(), DateSwap.DateTimeFull.class, "ja_JP", null,
>> null, null, "2001年3月3日 10時11分12秒 GMT" },
>> { "422", testDate.getTime(), DateSwap.DateTimeFull.class, Locale.JAPAN,
>> null, null, null, "2001年3月3日 10時11分12秒 GMT" },
>> { "423", testDate.getTime(), DateSwap.DateTimeFull.class, null,
>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>> { "424", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
>> { "425", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
>> Locale.KOREA, null, null, "2001ë…„ 3ì›” 3ì�¼ í† ìš”ì�¼ ì˜¤ì „ 10ì‹œ 11분
>> 12ì´ˆ GMT" },
>> etc.
>>
>> All the date swaps where the test date contains Japanese or Korean
>> characters in the date part fail in this way. I initially thought it was
>> the code page of the file, but I've changed to UTF-8 from the default and
>> this didn't resolve this for me. Again, this is specific to my Windows
>> platform - all is fine on Mac.
>>
>> Given that this is a build test error, and specific to one platform (and
>> possibly one machine), I'm not sure that it is a fatal problem for the
>> release.
>>
>> David
>>
>>
>>
>> On 21/09/2017 14:55, James Bognar wrote:
>>
>>> Hi David,
>>>
>>> I don't have a Windows machine anymore :-(
>>>
>>> It looks like a test issue. Is it only RDF tests that are failing?
>>>
>>> Can you find line 484 in org.apache.juneau.TestUtils in
>>> juneau-core-tests...
>>>
>>> String[] e = expected.trim().split("\n"), a = actual.trim().split("\n");
>>>
>>> ...and change it to this?...
>>>
>>> String[] e = expected.trim().split("[\r\n]+"), a = actual.trim().split(
>>> "[\r\n]+");
>>>
>>>
>>> Background on this method: Since Jena does not guarantee the order of
>>> entries in the generated RDF (it's pretty much random), it's difficult to
>>> do simple comparison validation. So instead, we sort the expected and
>>> actual lines and then check for comparison. It's not perfect (XML
>>> attribute order can also be random), but generally good enough for what
>>> we're testing.
>>>
>>>
>>>
>>> On Thu, Sep 21, 2017 at 5:52 AM, David Goddard <go...@acm.org> wrote:
>>>
>>> Thanks.
>>>>
>>>> I'm seeting a whole load of test failures in juneau-core parsing (every
>>>> round trip test is failing for me). For example:
>>>>
>>>>
>>>>> ByteArrayBase64SwapComboTest>ComboRoundTripTest.g32_parseRdf
>>>> XmlR:701->ComboRoundTripTest.testParse:205 ByteArray2d/parseRdfXmlR
>>>> parse-normal failed expected:<<rdf:RDF>[
>>>> <rdf:Seq>
>>>> <rdf:li>AQID</rdf:li>
>>>> <rdf:li>BAUG</rdf:li>
>>>> <rdf:li rdf:resource='http://www.w3.or
>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>
>>>>>
>>>>> </rdf:Seq>
>>>> </rdf:RDF>]
>>>>
>>>>> but was:<<rdf:RDF>[
>>>>>
>>>> <rdf:Seq>
>>>> <rdf:li>AQID</rdf:li>
>>>> <rdf:li>BAUG</rdf:li>
>>>> <rdf:li rdf:resource='http://www.w3.or
>>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>>
>>>>>
>>>>> </rdf:Seq>
>>>> </rdf:RDF>
>>>> ]
>>>>
>>>>>
>>>>>
>>>> The only consistent difference I see is that the final closing square
>>>> bracket is appearing on a new line. Perhaps this is a character encoding
>>>> issue (although I wouldn't rule out user error) - these tests fail on a
>>>> Windows platform, but work fine on a Mac.
>>>>
>>>> David
>>>>
>>>>
>>>>
>>>> On 20/09/2017 15:39, James Bognar wrote:
>>>>
>>>> Indeed they are.
>>>>>
>>>>> I've fixed them in Git. Thanks David!
>>>>>
>>>>> On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <go...@acm.org> wrote:
>>>>>
>>>>> I'm seeing a couple of issues with the Eclipse project names when
>>>>>
>>>>>> importing a fresh clone into a workspace.
>>>>>>
>>>>>> juneau-microservice/.project has <name>juneau-rest</name>
>>>>>> juneau-doc/.project has <name>juneau-marshall</name>
>>>>>>
>>>>>> I'm assuming these are copy/paste errors arising from the
>>>>>> restructuring.
>>>>>>
>>>>>> David
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 19/09/2017 18:26, Charles Mims wrote:
>>>>>>
>>>>>> +1, with intermittent test failures in Apache Juneau Microservice Tests
>>>>>>
>>>>>>>
>>>>>>> MD5 (apache-juneau-6.4.0-incubating-src.zip) =
>>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>>> For me it failed on the 1st and 2nd try, passed on the 3rd.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <
>>>>>>> jamesbognar@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we need
>>>>>>> to
>>>>>>>
>>>>>>>> handle this problem soon.
>>>>>>>>
>>>>>>>> Darn.
>>>>>>>>
>>>>>>>> I'm thinking it must be an issue with Jetty since we just upgraded
>>>>>>>> it.
>>>>>>>> From the Jetty side, the connection is open waiting for data, but
>>>>>>>> that's
>>>>>>>> all I know.
>>>>>>>>
>>>>>>>> I'll have to figure out how to use Fiddler and do some low-level
>>>>>>>> debugging. It's really hard to reproduce though :-(
>>>>>>>>
>>>>>>>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <yi...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>>
>>>>>>>>> SHA1, MD5 Checksum OK
>>>>>>>>> Maven Build OK
>>>>>>>>>
>>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we need
>>>>>>>>> to
>>>>>>>>> handle this problem soon.
>>>>>>>>>
>>>>>>>>> [INFO] Reactor Summary:
>>>>>>>>> [INFO]
>>>>>>>>> [INFO] Apache Juneau (incubating) ......................... SUCCESS
>>>>>>>>> [
>>>>>>>>> 10.521 s]
>>>>>>>>> [INFO] Apache Juneau - Core APIs .......................... SUCCESS
>>>>>>>>> [
>>>>>>>>> 0.737 s]
>>>>>>>>> [INFO] Apache Juneau Marshall ............................. SUCCESS
>>>>>>>>> [
>>>>>>>>> 45.444 s]
>>>>>>>>> [INFO] Apache Juneau Marshal RDF .......................... SUCCESS
>>>>>>>>> [
>>>>>>>>> 3.558 s]
>>>>>>>>> [INFO] Apache Juneau Data Transfer Objects ................ SUCCESS
>>>>>>>>> [
>>>>>>>>> 6.813 s]
>>>>>>>>> [INFO] Apache Juneau Core .................................
>>>>>>>>> SUCCESS [
>>>>>>>>> 1.025 s]
>>>>>>>>> [INFO] Apache Juneau Config File API ...................... SUCCESS
>>>>>>>>> [
>>>>>>>>> 1.928 s]
>>>>>>>>> [INFO] Apache Juneau Core Tests ........................... SUCCESS
>>>>>>>>> [01:04
>>>>>>>>> min]
>>>>>>>>> [INFO] Apache Juneau - REST APIs .......................... SUCCESS
>>>>>>>>> [
>>>>>>>>> 0.080 s]
>>>>>>>>> [INFO] Apache Juneau REST Servlet API ..................... SUCCESS
>>>>>>>>> [
>>>>>>>>> 2.331 s]
>>>>>>>>> [INFO] Apache Juneau REST JAX/RS API ...................... SUCCESS
>>>>>>>>> [
>>>>>>>>> 0.476 s]
>>>>>>>>> [INFO] Apache Juneau REST Client API ...................... SUCCESS
>>>>>>>>> [
>>>>>>>>> 1.005 s]
>>>>>>>>> [INFO] Apache Juneau - Microservice APIs .................. SUCCESS
>>>>>>>>> [
>>>>>>>>> 0.068 s]
>>>>>>>>> [INFO] Apache Juneau Microservice Server .................. SUCCESS
>>>>>>>>> [
>>>>>>>>> 1.588 s]
>>>>>>>>> [INFO] Apache Juneau Microservice Template ................ SUCCESS
>>>>>>>>> [
>>>>>>>>> 1.243 s]
>>>>>>>>> [INFO] Apache Juneau - Examples ........................... SUCCESS
>>>>>>>>> [
>>>>>>>>> 0.183 s]
>>>>>>>>> [INFO] Apache Juneau REST Examples ........................ SUCCESS
>>>>>>>>> [
>>>>>>>>> 8.512 s]
>>>>>>>>> [INFO] Apache Juneau Microservice Tests ................... SUCCESS
>>>>>>>>> [
>>>>>>>>> 24.522 s]
>>>>>>>>> [INFO] Apache Juneau Core Examples ........................ SUCCESS
>>>>>>>>> [
>>>>>>>>> 0.287 s]
>>>>>>>>> [INFO] Apache Juneau Javadocs ............................. SUCCESS
>>>>>>>>> [
>>>>>>>>> 0.617 s]
>>>>>>>>> [INFO] Apache Juneau - Release Engineering ................ SUCCESS
>>>>>>>>> [
>>>>>>>>> 0.040 s]
>>>>>>>>> [INFO] Apache Juneau UberJar .............................. SUCCESS
>>>>>>>>> [
>>>>>>>>> 1.008 s]
>>>>>>>>> [INFO] Apache Juneau Distribution ......................... SUCCESS
>>>>>>>>> [
>>>>>>>>> 0.768 s]
>>>>>>>>> [INFO] ------------------------------------------------------------
>>>>>>>>> ------------
>>>>>>>>> [INFO] BUILD SUCCESS
>>>>>>>>> [INFO] ------------------------------------------------------------
>>>>>>>>> ------------
>>>>>>>>> [INFO] Total time: 03:01 min
>>>>>>>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>>>>>>>>> [INFO] Final Memory: 87M/773M
>>>>>>>>> [INFO] ------------------------------------------------------------
>>>>>>>>> ------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Raphi D Lee, yidonguk@gmail.com
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org> 작성:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> I am pleased to be calling this vote for the source release of
>>>>>>>>>> Apache
>>>>>>>>>> Juneau 6.4.0-incubating RC2.
>>>>>>>>>> This includes some fixes for bugs found in RC1 and some packaging
>>>>>>>>>> changes
>>>>>>>>>> for the example and template projects.
>>>>>>>>>>
>>>>>>>>>> The list of new features can be found here:
>>>>>>>>>> http://juneau.incubator.apache.org/site/apidocs/
>>>>>>>>>>
>>>>>>>>>> overview-summary.html#6.4.0
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> The binaries are available at:
>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>
>>>>>>>>>> binaries/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> The release candidate to be voted over is available at:
>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>>
>>>>>>>>>> source/juneau-6.4.0-incubating-RC2/
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> SHA-1 checksums:
>>>>>>>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
>>>>>>>>>> 0-incubating-src.zip
>>>>>>>>>> c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
>>>>>>>>>> 0-incubating-bin.zip
>>>>>>>>>>
>>>>>>>>>> MD5 checksums:
>>>>>>>>>> e6ef05085093a5235cb9665c65a778fb apache-juneau-6.4.0-incubating
>>>>>>>>>> -src.zip
>>>>>>>>>> 4e96d5047c0e9f03f0def2d017521f13 apache-juneau-6.4.0-incubating
>>>>>>>>>> -bin.zip
>>>>>>>>>>
>>>>>>>>>> Build the release candidate using:
>>>>>>>>>> mvn clean install
>>>>>>>>>>
>>>>>>>>>> The release candidate is signed with a GPG key available at:
>>>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS
>>>>>>>>>>
>>>>>>>>>> A staged Maven repository is available for review at:
>>>>>>>>>> https://repository.apache.org/content/repositories/orgapache
>>>>>>>>>> juneau-1016/
>>>>>>>>>>
>>>>>>>>>> The Git commit for this release is...
>>>>>>>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>>
>>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37>*
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Please vote on releasing this package as:
>>>>>>>>>> Apache Juneau 6.4.0-incubating
>>>>>>>>>>
>>>>>>>>>> This vote will be open until 20-Sep-2017 9:00pm EST and passes if a
>>>>>>>>>> majority of at least three +1 Apache Juneau PPMC votes are cast.
>>>>>>>>>>
>>>>>>>>>> [ ] +1 Release this package
>>>>>>>>>> [ ] 0 I don't feel strongly about it, but don't object
>>>>>>>>>> [ ] -1 Do not release this package because...
>>>>>>>>>>
>>>>>>>>>> Anyone can participate in testing and voting, not just committers,
>>>>>>>>>> please
>>>>>>>>>> feel free to try out the release candidate and provide your votes.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by James Bognar <ja...@apache.org>.
Interesting. So the behavior of...
DateFormat.getDateInstance(DateFormat.FULL, locale).format(date);
DateFormat.getDateTimeInstance(DateFormat.FULL, DateFormat.FULL, locale
).format(date);
...returns different formats depending on the OS. Lovely.
Maybe it's JVM vendor-specific behavior?
I'm curious to know what's in those parentheses...
2001?3?3? [*(???)* ]10?11?12? GMT
Might give me something to google for.
It's technically a test-only issue. We can probably 'fix' the testcase by
just stripping out the formatting difference...
@Test
public void test() {
BeanSession session = ps.getBeanContext().createSession(new
BeanSessionArgs(null, sessionLocale, sessionTimeZone, null));
String actual = session.convertToType(calendar, String.class);
*actual = actual.replaceAll("\\([^\\)]+\\) ", ""); // Fix Windows-specific
formatting difference*
assertEquals(expected, actual);
Object c2 = session.convertToType(actual, calendar.getClass());
String actual2 = session.convertToType(c2, String.class);
*actual2 = actual2.replaceAll("\\([^\\)]+\\) ", ""); // Fix
Windows-specific formatting difference*
assertEquals(expected, actual2);
}
On Thu, Sep 21, 2017 at 3:11 PM, David Goddard <go...@acm.org> wrote:
> Hi,
>
> Yes, that fixed it, thanks. It also still tests OK on my Mac after the
> change.
>
> I'm now running into some further test issues, also on Windows only.
>
> ########################
>
> Tests run: 460, Failures: 16, Errors: 0, Skipped: 0, Time elapsed: 0.247
> sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
> test[111](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
> 0.015 sec <<< FAILURE!
> org.junit.ComparisonFailure: expected:<2001?3?3?[]> but was:<2001?3?3?[
> (???)]>
> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
> edDatesTest.java:645)
>
> [...]
> test[423](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
> 0 sec <<< FAILURE!
> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT> but
> was:<2001?3?3? [(???) ]10?11?12? GMT>
> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
> edDatesTest.java:645)
>
> test[424](org.apache.juneau.transforms.LocalizedDatesTest) Time elapsed:
> 0 sec <<< FAILURE!
> org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT> but
> was:<2001?3?3? [(???) ]10?11?12? GMT>
> at org.apache.juneau.transforms.LocalizedDatesTest.test(Localiz
> edDatesTest.java:645)
>
> ########################
>
>
> These are specific to date swap tests in Japanese & Korean:
>
> { "421", testDate.getTime(), DateSwap.DateTimeFull.class, "ja_JP", null,
> null, null, "2001年3月3日 10時11分12秒 GMT" },
> { "422", testDate.getTime(), DateSwap.DateTimeFull.class, Locale.JAPAN,
> null, null, null, "2001年3月3日 10時11分12秒 GMT" },
> { "423", testDate.getTime(), DateSwap.DateTimeFull.class, null,
> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
> { "424", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
> Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
> { "425", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
> Locale.KOREA, null, null, "2001ë…„ 3ì›” 3ì�¼ í† ìš”ì�¼ ì˜¤ì „ 10ì‹œ 11분
> 12ì´ˆ GMT" },
> etc.
>
> All the date swaps where the test date contains Japanese or Korean
> characters in the date part fail in this way. I initially thought it was
> the code page of the file, but I've changed to UTF-8 from the default and
> this didn't resolve this for me. Again, this is specific to my Windows
> platform - all is fine on Mac.
>
> Given that this is a build test error, and specific to one platform (and
> possibly one machine), I'm not sure that it is a fatal problem for the
> release.
>
> David
>
>
>
> On 21/09/2017 14:55, James Bognar wrote:
>
>> Hi David,
>>
>> I don't have a Windows machine anymore :-(
>>
>> It looks like a test issue. Is it only RDF tests that are failing?
>>
>> Can you find line 484 in org.apache.juneau.TestUtils in
>> juneau-core-tests...
>>
>> String[] e = expected.trim().split("\n"), a = actual.trim().split("\n");
>>
>> ...and change it to this?...
>>
>> String[] e = expected.trim().split("[\r\n]+"), a = actual.trim().split(
>> "[\r\n]+");
>>
>>
>> Background on this method: Since Jena does not guarantee the order of
>> entries in the generated RDF (it's pretty much random), it's difficult to
>> do simple comparison validation. So instead, we sort the expected and
>> actual lines and then check for comparison. It's not perfect (XML
>> attribute order can also be random), but generally good enough for what
>> we're testing.
>>
>>
>>
>> On Thu, Sep 21, 2017 at 5:52 AM, David Goddard <go...@acm.org> wrote:
>>
>> Thanks.
>>>
>>> I'm seeting a whole load of test failures in juneau-core parsing (every
>>> round trip test is failing for me). For example:
>>>
>>>
>>>> ByteArrayBase64SwapComboTest>ComboRoundTripTest.g32_parseRdf
>>> XmlR:701->ComboRoundTripTest.testParse:205 ByteArray2d/parseRdfXmlR
>>> parse-normal failed expected:<<rdf:RDF>[
>>> <rdf:Seq>
>>> <rdf:li>AQID</rdf:li>
>>> <rdf:li>BAUG</rdf:li>
>>> <rdf:li rdf:resource='http://www.w3.or
>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>
>>>>
>>>> </rdf:Seq>
>>> </rdf:RDF>]
>>>
>>>> but was:<<rdf:RDF>[
>>>>
>>> <rdf:Seq>
>>> <rdf:li>AQID</rdf:li>
>>> <rdf:li>BAUG</rdf:li>
>>> <rdf:li rdf:resource='http://www.w3.or
>>> g/1999/02/22-rdf-syntax-ns#nil'/
>>>
>>>>
>>>> </rdf:Seq>
>>> </rdf:RDF>
>>> ]
>>>
>>>>
>>>>
>>> The only consistent difference I see is that the final closing square
>>> bracket is appearing on a new line. Perhaps this is a character encoding
>>> issue (although I wouldn't rule out user error) - these tests fail on a
>>> Windows platform, but work fine on a Mac.
>>>
>>> David
>>>
>>>
>>>
>>> On 20/09/2017 15:39, James Bognar wrote:
>>>
>>> Indeed they are.
>>>>
>>>> I've fixed them in Git. Thanks David!
>>>>
>>>> On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <go...@acm.org> wrote:
>>>>
>>>> I'm seeing a couple of issues with the Eclipse project names when
>>>>
>>>>> importing a fresh clone into a workspace.
>>>>>
>>>>> juneau-microservice/.project has <name>juneau-rest</name>
>>>>> juneau-doc/.project has <name>juneau-marshall</name>
>>>>>
>>>>> I'm assuming these are copy/paste errors arising from the
>>>>> restructuring.
>>>>>
>>>>> David
>>>>>
>>>>>
>>>>>
>>>>> On 19/09/2017 18:26, Charles Mims wrote:
>>>>>
>>>>> +1, with intermittent test failures in Apache Juneau Microservice Tests
>>>>>
>>>>>>
>>>>>> MD5 (apache-juneau-6.4.0-incubating-src.zip) =
>>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>>> For me it failed on the 1st and 2nd try, passed on the 3rd.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <
>>>>>> jamesbognar@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we need
>>>>>> to
>>>>>>
>>>>>>> handle this problem soon.
>>>>>>>
>>>>>>> Darn.
>>>>>>>
>>>>>>> I'm thinking it must be an issue with Jetty since we just upgraded
>>>>>>> it.
>>>>>>> From the Jetty side, the connection is open waiting for data, but
>>>>>>> that's
>>>>>>> all I know.
>>>>>>>
>>>>>>> I'll have to figure out how to use Fiddler and do some low-level
>>>>>>> debugging. It's really hard to reproduce though :-(
>>>>>>>
>>>>>>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <yi...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>>
>>>>>>>> SHA1, MD5 Checksum OK
>>>>>>>> Maven Build OK
>>>>>>>>
>>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we need
>>>>>>>> to
>>>>>>>> handle this problem soon.
>>>>>>>>
>>>>>>>> [INFO] Reactor Summary:
>>>>>>>> [INFO]
>>>>>>>> [INFO] Apache Juneau (incubating) ......................... SUCCESS
>>>>>>>> [
>>>>>>>> 10.521 s]
>>>>>>>> [INFO] Apache Juneau - Core APIs .......................... SUCCESS
>>>>>>>> [
>>>>>>>> 0.737 s]
>>>>>>>> [INFO] Apache Juneau Marshall ............................. SUCCESS
>>>>>>>> [
>>>>>>>> 45.444 s]
>>>>>>>> [INFO] Apache Juneau Marshal RDF .......................... SUCCESS
>>>>>>>> [
>>>>>>>> 3.558 s]
>>>>>>>> [INFO] Apache Juneau Data Transfer Objects ................ SUCCESS
>>>>>>>> [
>>>>>>>> 6.813 s]
>>>>>>>> [INFO] Apache Juneau Core .................................
>>>>>>>> SUCCESS [
>>>>>>>> 1.025 s]
>>>>>>>> [INFO] Apache Juneau Config File API ...................... SUCCESS
>>>>>>>> [
>>>>>>>> 1.928 s]
>>>>>>>> [INFO] Apache Juneau Core Tests ........................... SUCCESS
>>>>>>>> [01:04
>>>>>>>> min]
>>>>>>>> [INFO] Apache Juneau - REST APIs .......................... SUCCESS
>>>>>>>> [
>>>>>>>> 0.080 s]
>>>>>>>> [INFO] Apache Juneau REST Servlet API ..................... SUCCESS
>>>>>>>> [
>>>>>>>> 2.331 s]
>>>>>>>> [INFO] Apache Juneau REST JAX/RS API ...................... SUCCESS
>>>>>>>> [
>>>>>>>> 0.476 s]
>>>>>>>> [INFO] Apache Juneau REST Client API ...................... SUCCESS
>>>>>>>> [
>>>>>>>> 1.005 s]
>>>>>>>> [INFO] Apache Juneau - Microservice APIs .................. SUCCESS
>>>>>>>> [
>>>>>>>> 0.068 s]
>>>>>>>> [INFO] Apache Juneau Microservice Server .................. SUCCESS
>>>>>>>> [
>>>>>>>> 1.588 s]
>>>>>>>> [INFO] Apache Juneau Microservice Template ................ SUCCESS
>>>>>>>> [
>>>>>>>> 1.243 s]
>>>>>>>> [INFO] Apache Juneau - Examples ........................... SUCCESS
>>>>>>>> [
>>>>>>>> 0.183 s]
>>>>>>>> [INFO] Apache Juneau REST Examples ........................ SUCCESS
>>>>>>>> [
>>>>>>>> 8.512 s]
>>>>>>>> [INFO] Apache Juneau Microservice Tests ................... SUCCESS
>>>>>>>> [
>>>>>>>> 24.522 s]
>>>>>>>> [INFO] Apache Juneau Core Examples ........................ SUCCESS
>>>>>>>> [
>>>>>>>> 0.287 s]
>>>>>>>> [INFO] Apache Juneau Javadocs ............................. SUCCESS
>>>>>>>> [
>>>>>>>> 0.617 s]
>>>>>>>> [INFO] Apache Juneau - Release Engineering ................ SUCCESS
>>>>>>>> [
>>>>>>>> 0.040 s]
>>>>>>>> [INFO] Apache Juneau UberJar .............................. SUCCESS
>>>>>>>> [
>>>>>>>> 1.008 s]
>>>>>>>> [INFO] Apache Juneau Distribution ......................... SUCCESS
>>>>>>>> [
>>>>>>>> 0.768 s]
>>>>>>>> [INFO] ------------------------------------------------------------
>>>>>>>> ------------
>>>>>>>> [INFO] BUILD SUCCESS
>>>>>>>> [INFO] ------------------------------------------------------------
>>>>>>>> ------------
>>>>>>>> [INFO] Total time: 03:01 min
>>>>>>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>>>>>>>> [INFO] Final Memory: 87M/773M
>>>>>>>> [INFO] ------------------------------------------------------------
>>>>>>>> ------------
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Raphi D Lee, yidonguk@gmail.com
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org> 작성:
>>>>>>>>
>>>>>>>>
>>>>>>>>> I am pleased to be calling this vote for the source release of
>>>>>>>>> Apache
>>>>>>>>> Juneau 6.4.0-incubating RC2.
>>>>>>>>> This includes some fixes for bugs found in RC1 and some packaging
>>>>>>>>> changes
>>>>>>>>> for the example and template projects.
>>>>>>>>>
>>>>>>>>> The list of new features can be found here:
>>>>>>>>> http://juneau.incubator.apache.org/site/apidocs/
>>>>>>>>>
>>>>>>>>> overview-summary.html#6.4.0
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The binaries are available at:
>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>
>>>>>>>>> binaries/juneau-6.4.0-incubating-RC2/
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The release candidate to be voted over is available at:
>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>>
>>>>>>>>> source/juneau-6.4.0-incubating-RC2/
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> SHA-1 checksums:
>>>>>>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
>>>>>>>>> 0-incubating-src.zip
>>>>>>>>> c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
>>>>>>>>> 0-incubating-bin.zip
>>>>>>>>>
>>>>>>>>> MD5 checksums:
>>>>>>>>> e6ef05085093a5235cb9665c65a778fb apache-juneau-6.4.0-incubating
>>>>>>>>> -src.zip
>>>>>>>>> 4e96d5047c0e9f03f0def2d017521f13 apache-juneau-6.4.0-incubating
>>>>>>>>> -bin.zip
>>>>>>>>>
>>>>>>>>> Build the release candidate using:
>>>>>>>>> mvn clean install
>>>>>>>>>
>>>>>>>>> The release candidate is signed with a GPG key available at:
>>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS
>>>>>>>>>
>>>>>>>>> A staged Maven repository is available for review at:
>>>>>>>>> https://repository.apache.org/content/repositories/orgapache
>>>>>>>>> juneau-1016/
>>>>>>>>>
>>>>>>>>> The Git commit for this release is...
>>>>>>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>>
>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
>>>>>>>>>
>>>>>>>>
>>>>>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>
>>>>>>>>>
>>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37>*
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Please vote on releasing this package as:
>>>>>>>>> Apache Juneau 6.4.0-incubating
>>>>>>>>>
>>>>>>>>> This vote will be open until 20-Sep-2017 9:00pm EST and passes if a
>>>>>>>>> majority of at least three +1 Apache Juneau PPMC votes are cast.
>>>>>>>>>
>>>>>>>>> [ ] +1 Release this package
>>>>>>>>> [ ] 0 I don't feel strongly about it, but don't object
>>>>>>>>> [ ] -1 Do not release this package because...
>>>>>>>>>
>>>>>>>>> Anyone can participate in testing and voting, not just committers,
>>>>>>>>> please
>>>>>>>>> feel free to try out the release candidate and provide your votes.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by David Goddard <go...@acm.org>.
Hi,
Yes, that fixed it, thanks. It also still tests OK on my Mac after the
change.
I'm now running into some further test issues, also on Windows only.
########################
Tests run: 460, Failures: 16, Errors: 0, Skipped: 0, Time elapsed: 0.247
sec <<< FAILURE! - in org.apache.juneau.transforms.LocalizedDatesTest
test[111](org.apache.juneau.transforms.LocalizedDatesTest) Time
elapsed: 0.015 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<2001?3?3?[]> but was:<2001?3?3?[
(???)]>
at
org.apache.juneau.transforms.LocalizedDatesTest.test(LocalizedDatesTest.java:645)
[...]
test[423](org.apache.juneau.transforms.LocalizedDatesTest) Time
elapsed: 0 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT> but
was:<2001?3?3? [(???) ]10?11?12? GMT>
at
org.apache.juneau.transforms.LocalizedDatesTest.test(LocalizedDatesTest.java:645)
test[424](org.apache.juneau.transforms.LocalizedDatesTest) Time
elapsed: 0 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<2001?3?3? []10?11?12? GMT> but
was:<2001?3?3? [(???) ]10?11?12? GMT>
at
org.apache.juneau.transforms.LocalizedDatesTest.test(LocalizedDatesTest.java:645)
########################
These are specific to date swap tests in Japanese & Korean:
{ "421", testDate.getTime(), DateSwap.DateTimeFull.class, "ja_JP", null,
null, null, "2001年3月3日 10時11分12秒 GMT" },
{ "422", testDate.getTime(), DateSwap.DateTimeFull.class, Locale.JAPAN,
null, null, null, "2001年3月3日 10時11分12秒 GMT" },
{ "423", testDate.getTime(), DateSwap.DateTimeFull.class, null,
Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
{ "424", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
Locale.JAPAN, null, null, "2001年3月3日 10時11分12秒 GMT" },
{ "425", testDate.getTime(), DateSwap.DateTimeFull.class, "en_UK",
Locale.KOREA, null, null, "2001ë…„ 3ì›” 3ì�¼ í† ìš”ì�¼ ì˜¤ì „ 10ì‹œ
11분 12초 GMT" },
etc.
All the date swaps where the test date contains Japanese or Korean
characters in the date part fail in this way. I initially thought it
was the code page of the file, but I've changed to UTF-8 from the
default and this didn't resolve this for me. Again, this is specific to
my Windows platform - all is fine on Mac.
Given that this is a build test error, and specific to one platform (and
possibly one machine), I'm not sure that it is a fatal problem for the
release.
David
On 21/09/2017 14:55, James Bognar wrote:
> Hi David,
>
> I don't have a Windows machine anymore :-(
>
> It looks like a test issue. Is it only RDF tests that are failing?
>
> Can you find line 484 in org.apache.juneau.TestUtils in juneau-core-tests...
>
> String[] e = expected.trim().split("\n"), a = actual.trim().split("\n");
>
> ...and change it to this?...
>
> String[] e = expected.trim().split("[\r\n]+"), a = actual.trim().split(
> "[\r\n]+");
>
>
> Background on this method: Since Jena does not guarantee the order of
> entries in the generated RDF (it's pretty much random), it's difficult to
> do simple comparison validation. So instead, we sort the expected and
> actual lines and then check for comparison. It's not perfect (XML
> attribute order can also be random), but generally good enough for what
> we're testing.
>
>
>
> On Thu, Sep 21, 2017 at 5:52 AM, David Goddard <go...@acm.org> wrote:
>
>> Thanks.
>>
>> I'm seeting a whole load of test failures in juneau-core parsing (every
>> round trip test is failing for me). For example:
>>
>>>
>> ByteArrayBase64SwapComboTest>ComboRoundTripTest.g32_parseRdf
>> XmlR:701->ComboRoundTripTest.testParse:205 ByteArray2d/parseRdfXmlR
>> parse-normal failed expected:<<rdf:RDF>[
>> <rdf:Seq>
>> <rdf:li>AQID</rdf:li>
>> <rdf:li>BAUG</rdf:li>
>> <rdf:li rdf:resource='http://www.w3.org/1999/02/22-rdf-syntax-ns#nil'/
>>>
>> </rdf:Seq>
>> </rdf:RDF>]
>>> but was:<<rdf:RDF>[
>> <rdf:Seq>
>> <rdf:li>AQID</rdf:li>
>> <rdf:li>BAUG</rdf:li>
>> <rdf:li rdf:resource='http://www.w3.org/1999/02/22-rdf-syntax-ns#nil'/
>>>
>> </rdf:Seq>
>> </rdf:RDF>
>> ]
>>>
>>
>> The only consistent difference I see is that the final closing square
>> bracket is appearing on a new line. Perhaps this is a character encoding
>> issue (although I wouldn't rule out user error) - these tests fail on a
>> Windows platform, but work fine on a Mac.
>>
>> David
>>
>>
>>
>> On 20/09/2017 15:39, James Bognar wrote:
>>
>>> Indeed they are.
>>>
>>> I've fixed them in Git. Thanks David!
>>>
>>> On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <go...@acm.org> wrote:
>>>
>>> I'm seeing a couple of issues with the Eclipse project names when
>>>> importing a fresh clone into a workspace.
>>>>
>>>> juneau-microservice/.project has <name>juneau-rest</name>
>>>> juneau-doc/.project has <name>juneau-marshall</name>
>>>>
>>>> I'm assuming these are copy/paste errors arising from the restructuring.
>>>>
>>>> David
>>>>
>>>>
>>>>
>>>> On 19/09/2017 18:26, Charles Mims wrote:
>>>>
>>>> +1, with intermittent test failures in Apache Juneau Microservice Tests
>>>>>
>>>>> MD5 (apache-juneau-6.4.0-incubating-src.zip) =
>>>>> e6ef05085093a5235cb9665c65a778fb
>>>>> For me it failed on the 1st and 2nd try, passed on the 3rd.
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <ja...@apache.org>
>>>>> wrote:
>>>>>
>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we need to
>>>>>> handle this problem soon.
>>>>>>
>>>>>> Darn.
>>>>>>
>>>>>> I'm thinking it must be an issue with Jetty since we just upgraded it.
>>>>>> From the Jetty side, the connection is open waiting for data, but
>>>>>> that's
>>>>>> all I know.
>>>>>>
>>>>>> I'll have to figure out how to use Fiddler and do some low-level
>>>>>> debugging. It's really hard to reproduce though :-(
>>>>>>
>>>>>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <yi...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> +1
>>>>>>
>>>>>>>
>>>>>>> SHA1, MD5 Checksum OK
>>>>>>> Maven Build OK
>>>>>>>
>>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we need
>>>>>>> to
>>>>>>> handle this problem soon.
>>>>>>>
>>>>>>> [INFO] Reactor Summary:
>>>>>>> [INFO]
>>>>>>> [INFO] Apache Juneau (incubating) ......................... SUCCESS [
>>>>>>> 10.521 s]
>>>>>>> [INFO] Apache Juneau - Core APIs .......................... SUCCESS [
>>>>>>> 0.737 s]
>>>>>>> [INFO] Apache Juneau Marshall ............................. SUCCESS [
>>>>>>> 45.444 s]
>>>>>>> [INFO] Apache Juneau Marshal RDF .......................... SUCCESS [
>>>>>>> 3.558 s]
>>>>>>> [INFO] Apache Juneau Data Transfer Objects ................ SUCCESS [
>>>>>>> 6.813 s]
>>>>>>> [INFO] Apache Juneau Core ................................. SUCCESS [
>>>>>>> 1.025 s]
>>>>>>> [INFO] Apache Juneau Config File API ...................... SUCCESS [
>>>>>>> 1.928 s]
>>>>>>> [INFO] Apache Juneau Core Tests ........................... SUCCESS
>>>>>>> [01:04
>>>>>>> min]
>>>>>>> [INFO] Apache Juneau - REST APIs .......................... SUCCESS [
>>>>>>> 0.080 s]
>>>>>>> [INFO] Apache Juneau REST Servlet API ..................... SUCCESS [
>>>>>>> 2.331 s]
>>>>>>> [INFO] Apache Juneau REST JAX/RS API ...................... SUCCESS [
>>>>>>> 0.476 s]
>>>>>>> [INFO] Apache Juneau REST Client API ...................... SUCCESS [
>>>>>>> 1.005 s]
>>>>>>> [INFO] Apache Juneau - Microservice APIs .................. SUCCESS [
>>>>>>> 0.068 s]
>>>>>>> [INFO] Apache Juneau Microservice Server .................. SUCCESS [
>>>>>>> 1.588 s]
>>>>>>> [INFO] Apache Juneau Microservice Template ................ SUCCESS [
>>>>>>> 1.243 s]
>>>>>>> [INFO] Apache Juneau - Examples ........................... SUCCESS [
>>>>>>> 0.183 s]
>>>>>>> [INFO] Apache Juneau REST Examples ........................ SUCCESS [
>>>>>>> 8.512 s]
>>>>>>> [INFO] Apache Juneau Microservice Tests ................... SUCCESS [
>>>>>>> 24.522 s]
>>>>>>> [INFO] Apache Juneau Core Examples ........................ SUCCESS [
>>>>>>> 0.287 s]
>>>>>>> [INFO] Apache Juneau Javadocs ............................. SUCCESS [
>>>>>>> 0.617 s]
>>>>>>> [INFO] Apache Juneau - Release Engineering ................ SUCCESS [
>>>>>>> 0.040 s]
>>>>>>> [INFO] Apache Juneau UberJar .............................. SUCCESS [
>>>>>>> 1.008 s]
>>>>>>> [INFO] Apache Juneau Distribution ......................... SUCCESS [
>>>>>>> 0.768 s]
>>>>>>> [INFO] ------------------------------------------------------------
>>>>>>> ------------
>>>>>>> [INFO] BUILD SUCCESS
>>>>>>> [INFO] ------------------------------------------------------------
>>>>>>> ------------
>>>>>>> [INFO] Total time: 03:01 min
>>>>>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>>>>>>> [INFO] Final Memory: 87M/773M
>>>>>>> [INFO] ------------------------------------------------------------
>>>>>>> ------------
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Raphi D Lee, yidonguk@gmail.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org> 작성:
>>>>>>>
>>>>>>>>
>>>>>>>> I am pleased to be calling this vote for the source release of Apache
>>>>>>>> Juneau 6.4.0-incubating RC2.
>>>>>>>> This includes some fixes for bugs found in RC1 and some packaging
>>>>>>>> changes
>>>>>>>> for the example and template projects.
>>>>>>>>
>>>>>>>> The list of new features can be found here:
>>>>>>>> http://juneau.incubator.apache.org/site/apidocs/
>>>>>>>>
>>>>>>>> overview-summary.html#6.4.0
>>>>>>>
>>>>>>>
>>>>>>>> The binaries are available at:
>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>
>>>>>>>> binaries/juneau-6.4.0-incubating-RC2/
>>>>>>>
>>>>>>>
>>>>>>>> The release candidate to be voted over is available at:
>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>>
>>>>>>>> source/juneau-6.4.0-incubating-RC2/
>>>>>>>
>>>>>>>
>>>>>>>> SHA-1 checksums:
>>>>>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
>>>>>>>> 0-incubating-src.zip
>>>>>>>> c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
>>>>>>>> 0-incubating-bin.zip
>>>>>>>>
>>>>>>>> MD5 checksums:
>>>>>>>> e6ef05085093a5235cb9665c65a778fb apache-juneau-6.4.0-incubating
>>>>>>>> -src.zip
>>>>>>>> 4e96d5047c0e9f03f0def2d017521f13 apache-juneau-6.4.0-incubating
>>>>>>>> -bin.zip
>>>>>>>>
>>>>>>>> Build the release candidate using:
>>>>>>>> mvn clean install
>>>>>>>>
>>>>>>>> The release candidate is signed with a GPG key available at:
>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS
>>>>>>>>
>>>>>>>> A staged Maven repository is available for review at:
>>>>>>>> https://repository.apache.org/content/repositories/orgapache
>>>>>>>> juneau-1016/
>>>>>>>>
>>>>>>>> The Git commit for this release is...
>>>>>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>
>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
>>>>>>>
>>>>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>>
>>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37>*
>>>>>>>
>>>>>>>
>>>>>>>> Please vote on releasing this package as:
>>>>>>>> Apache Juneau 6.4.0-incubating
>>>>>>>>
>>>>>>>> This vote will be open until 20-Sep-2017 9:00pm EST and passes if a
>>>>>>>> majority of at least three +1 Apache Juneau PPMC votes are cast.
>>>>>>>>
>>>>>>>> [ ] +1 Release this package
>>>>>>>> [ ] 0 I don't feel strongly about it, but don't object
>>>>>>>> [ ] -1 Do not release this package because...
>>>>>>>>
>>>>>>>> Anyone can participate in testing and voting, not just committers,
>>>>>>>> please
>>>>>>>> feel free to try out the release candidate and provide your votes.
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by James Bognar <ja...@apache.org>.
Hi David,
I don't have a Windows machine anymore :-(
It looks like a test issue. Is it only RDF tests that are failing?
Can you find line 484 in org.apache.juneau.TestUtils in juneau-core-tests...
String[] e = expected.trim().split("\n"), a = actual.trim().split("\n");
...and change it to this?...
String[] e = expected.trim().split("[\r\n]+"), a = actual.trim().split(
"[\r\n]+");
Background on this method: Since Jena does not guarantee the order of
entries in the generated RDF (it's pretty much random), it's difficult to
do simple comparison validation. So instead, we sort the expected and
actual lines and then check for comparison. It's not perfect (XML
attribute order can also be random), but generally good enough for what
we're testing.
On Thu, Sep 21, 2017 at 5:52 AM, David Goddard <go...@acm.org> wrote:
> Thanks.
>
> I'm seeting a whole load of test failures in juneau-core parsing (every
> round trip test is failing for me). For example:
>
> >
> ByteArrayBase64SwapComboTest>ComboRoundTripTest.g32_parseRdf
> XmlR:701->ComboRoundTripTest.testParse:205 ByteArray2d/parseRdfXmlR
> parse-normal failed expected:<<rdf:RDF>[
> <rdf:Seq>
> <rdf:li>AQID</rdf:li>
> <rdf:li>BAUG</rdf:li>
> <rdf:li rdf:resource='http://www.w3.org/1999/02/22-rdf-syntax-ns#nil'/
> >
> </rdf:Seq>
> </rdf:RDF>]
> > but was:<<rdf:RDF>[
> <rdf:Seq>
> <rdf:li>AQID</rdf:li>
> <rdf:li>BAUG</rdf:li>
> <rdf:li rdf:resource='http://www.w3.org/1999/02/22-rdf-syntax-ns#nil'/
> >
> </rdf:Seq>
> </rdf:RDF>
> ]
> >
>
> The only consistent difference I see is that the final closing square
> bracket is appearing on a new line. Perhaps this is a character encoding
> issue (although I wouldn't rule out user error) - these tests fail on a
> Windows platform, but work fine on a Mac.
>
> David
>
>
>
> On 20/09/2017 15:39, James Bognar wrote:
>
>> Indeed they are.
>>
>> I've fixed them in Git. Thanks David!
>>
>> On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <go...@acm.org> wrote:
>>
>> I'm seeing a couple of issues with the Eclipse project names when
>>> importing a fresh clone into a workspace.
>>>
>>> juneau-microservice/.project has <name>juneau-rest</name>
>>> juneau-doc/.project has <name>juneau-marshall</name>
>>>
>>> I'm assuming these are copy/paste errors arising from the restructuring.
>>>
>>> David
>>>
>>>
>>>
>>> On 19/09/2017 18:26, Charles Mims wrote:
>>>
>>> +1, with intermittent test failures in Apache Juneau Microservice Tests
>>>>
>>>> MD5 (apache-juneau-6.4.0-incubating-src.zip) =
>>>> e6ef05085093a5235cb9665c65a778fb
>>>> For me it failed on the 1st and 2nd try, passed on the 3rd.
>>>>
>>>>
>>>>
>>>> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <ja...@apache.org>
>>>> wrote:
>>>>
>>>> ** At this time, I have met “Broken Pipe” issue too. I think we need to
>>>>> handle this problem soon.
>>>>>
>>>>> Darn.
>>>>>
>>>>> I'm thinking it must be an issue with Jetty since we just upgraded it.
>>>>> From the Jetty side, the connection is open waiting for data, but
>>>>> that's
>>>>> all I know.
>>>>>
>>>>> I'll have to figure out how to use Fiddler and do some low-level
>>>>> debugging. It's really hard to reproduce though :-(
>>>>>
>>>>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <yi...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> +1
>>>>>
>>>>>>
>>>>>> SHA1, MD5 Checksum OK
>>>>>> Maven Build OK
>>>>>>
>>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we need
>>>>>> to
>>>>>> handle this problem soon.
>>>>>>
>>>>>> [INFO] Reactor Summary:
>>>>>> [INFO]
>>>>>> [INFO] Apache Juneau (incubating) ......................... SUCCESS [
>>>>>> 10.521 s]
>>>>>> [INFO] Apache Juneau - Core APIs .......................... SUCCESS [
>>>>>> 0.737 s]
>>>>>> [INFO] Apache Juneau Marshall ............................. SUCCESS [
>>>>>> 45.444 s]
>>>>>> [INFO] Apache Juneau Marshal RDF .......................... SUCCESS [
>>>>>> 3.558 s]
>>>>>> [INFO] Apache Juneau Data Transfer Objects ................ SUCCESS [
>>>>>> 6.813 s]
>>>>>> [INFO] Apache Juneau Core ................................. SUCCESS [
>>>>>> 1.025 s]
>>>>>> [INFO] Apache Juneau Config File API ...................... SUCCESS [
>>>>>> 1.928 s]
>>>>>> [INFO] Apache Juneau Core Tests ........................... SUCCESS
>>>>>> [01:04
>>>>>> min]
>>>>>> [INFO] Apache Juneau - REST APIs .......................... SUCCESS [
>>>>>> 0.080 s]
>>>>>> [INFO] Apache Juneau REST Servlet API ..................... SUCCESS [
>>>>>> 2.331 s]
>>>>>> [INFO] Apache Juneau REST JAX/RS API ...................... SUCCESS [
>>>>>> 0.476 s]
>>>>>> [INFO] Apache Juneau REST Client API ...................... SUCCESS [
>>>>>> 1.005 s]
>>>>>> [INFO] Apache Juneau - Microservice APIs .................. SUCCESS [
>>>>>> 0.068 s]
>>>>>> [INFO] Apache Juneau Microservice Server .................. SUCCESS [
>>>>>> 1.588 s]
>>>>>> [INFO] Apache Juneau Microservice Template ................ SUCCESS [
>>>>>> 1.243 s]
>>>>>> [INFO] Apache Juneau - Examples ........................... SUCCESS [
>>>>>> 0.183 s]
>>>>>> [INFO] Apache Juneau REST Examples ........................ SUCCESS [
>>>>>> 8.512 s]
>>>>>> [INFO] Apache Juneau Microservice Tests ................... SUCCESS [
>>>>>> 24.522 s]
>>>>>> [INFO] Apache Juneau Core Examples ........................ SUCCESS [
>>>>>> 0.287 s]
>>>>>> [INFO] Apache Juneau Javadocs ............................. SUCCESS [
>>>>>> 0.617 s]
>>>>>> [INFO] Apache Juneau - Release Engineering ................ SUCCESS [
>>>>>> 0.040 s]
>>>>>> [INFO] Apache Juneau UberJar .............................. SUCCESS [
>>>>>> 1.008 s]
>>>>>> [INFO] Apache Juneau Distribution ......................... SUCCESS [
>>>>>> 0.768 s]
>>>>>> [INFO] ------------------------------------------------------------
>>>>>> ------------
>>>>>> [INFO] BUILD SUCCESS
>>>>>> [INFO] ------------------------------------------------------------
>>>>>> ------------
>>>>>> [INFO] Total time: 03:01 min
>>>>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>>>>>> [INFO] Final Memory: 87M/773M
>>>>>> [INFO] ------------------------------------------------------------
>>>>>> ------------
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Raphi D Lee, yidonguk@gmail.com
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org> 작성:
>>>>>>
>>>>>>>
>>>>>>> I am pleased to be calling this vote for the source release of Apache
>>>>>>> Juneau 6.4.0-incubating RC2.
>>>>>>> This includes some fixes for bugs found in RC1 and some packaging
>>>>>>> changes
>>>>>>> for the example and template projects.
>>>>>>>
>>>>>>> The list of new features can be found here:
>>>>>>> http://juneau.incubator.apache.org/site/apidocs/
>>>>>>>
>>>>>>> overview-summary.html#6.4.0
>>>>>>
>>>>>>
>>>>>>> The binaries are available at:
>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>
>>>>>>> binaries/juneau-6.4.0-incubating-RC2/
>>>>>>
>>>>>>
>>>>>>> The release candidate to be voted over is available at:
>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>>
>>>>>>> source/juneau-6.4.0-incubating-RC2/
>>>>>>
>>>>>>
>>>>>>> SHA-1 checksums:
>>>>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
>>>>>>> 0-incubating-src.zip
>>>>>>> c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
>>>>>>> 0-incubating-bin.zip
>>>>>>>
>>>>>>> MD5 checksums:
>>>>>>> e6ef05085093a5235cb9665c65a778fb apache-juneau-6.4.0-incubating
>>>>>>> -src.zip
>>>>>>> 4e96d5047c0e9f03f0def2d017521f13 apache-juneau-6.4.0-incubating
>>>>>>> -bin.zip
>>>>>>>
>>>>>>> Build the release candidate using:
>>>>>>> mvn clean install
>>>>>>>
>>>>>>> The release candidate is signed with a GPG key available at:
>>>>>>> https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS
>>>>>>>
>>>>>>> A staged Maven repository is available for review at:
>>>>>>> https://repository.apache.org/content/repositories/orgapache
>>>>>>> juneau-1016/
>>>>>>>
>>>>>>> The Git commit for this release is...
>>>>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>
>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
>>>>>>
>>>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>>
>>>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37>*
>>>>>>
>>>>>>
>>>>>>> Please vote on releasing this package as:
>>>>>>> Apache Juneau 6.4.0-incubating
>>>>>>>
>>>>>>> This vote will be open until 20-Sep-2017 9:00pm EST and passes if a
>>>>>>> majority of at least three +1 Apache Juneau PPMC votes are cast.
>>>>>>>
>>>>>>> [ ] +1 Release this package
>>>>>>> [ ] 0 I don't feel strongly about it, but don't object
>>>>>>> [ ] -1 Do not release this package because...
>>>>>>>
>>>>>>> Anyone can participate in testing and voting, not just committers,
>>>>>>> please
>>>>>>> feel free to try out the release candidate and provide your votes.
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by David Goddard <go...@acm.org>.
Thanks.
I'm seeting a whole load of test failures in juneau-core parsing (every
round trip test is failing for me). For example:
>
ByteArrayBase64SwapComboTest>ComboRoundTripTest.g32_parseRdfXmlR:701->ComboRoundTripTest.testParse:205
ByteArray2d/parseRdfXmlR parse-normal failed expected:<<rdf:RDF>[
<rdf:Seq>
<rdf:li>AQID</rdf:li>
<rdf:li>BAUG</rdf:li>
<rdf:li rdf:resource='http://www.w3.org/1999/02/22-rdf-syntax-ns#nil'/>
</rdf:Seq>
</rdf:RDF>]
> but was:<<rdf:RDF>[
<rdf:Seq>
<rdf:li>AQID</rdf:li>
<rdf:li>BAUG</rdf:li>
<rdf:li rdf:resource='http://www.w3.org/1999/02/22-rdf-syntax-ns#nil'/>
</rdf:Seq>
</rdf:RDF>
]
>
The only consistent difference I see is that the final closing square
bracket is appearing on a new line. Perhaps this is a character
encoding issue (although I wouldn't rule out user error) - these tests
fail on a Windows platform, but work fine on a Mac.
David
On 20/09/2017 15:39, James Bognar wrote:
> Indeed they are.
>
> I've fixed them in Git. Thanks David!
>
> On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <go...@acm.org> wrote:
>
>> I'm seeing a couple of issues with the Eclipse project names when
>> importing a fresh clone into a workspace.
>>
>> juneau-microservice/.project has <name>juneau-rest</name>
>> juneau-doc/.project has <name>juneau-marshall</name>
>>
>> I'm assuming these are copy/paste errors arising from the restructuring.
>>
>> David
>>
>>
>>
>> On 19/09/2017 18:26, Charles Mims wrote:
>>
>>> +1, with intermittent test failures in Apache Juneau Microservice Tests
>>>
>>> MD5 (apache-juneau-6.4.0-incubating-src.zip) =
>>> e6ef05085093a5235cb9665c65a778fb
>>> For me it failed on the 1st and 2nd try, passed on the 3rd.
>>>
>>>
>>>
>>> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <ja...@apache.org>
>>> wrote:
>>>
>>>> ** At this time, I have met “Broken Pipe” issue too. I think we need to
>>>> handle this problem soon.
>>>>
>>>> Darn.
>>>>
>>>> I'm thinking it must be an issue with Jetty since we just upgraded it.
>>>> From the Jetty side, the connection is open waiting for data, but that's
>>>> all I know.
>>>>
>>>> I'll have to figure out how to use Fiddler and do some low-level
>>>> debugging. It's really hard to reproduce though :-(
>>>>
>>>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <yi...@gmail.com>
>>>> wrote:
>>>>
>>>> +1
>>>>>
>>>>> SHA1, MD5 Checksum OK
>>>>> Maven Build OK
>>>>>
>>>>> ** At this time, I have met “Broken Pipe” issue too. I think we need to
>>>>> handle this problem soon.
>>>>>
>>>>> [INFO] Reactor Summary:
>>>>> [INFO]
>>>>> [INFO] Apache Juneau (incubating) ......................... SUCCESS [
>>>>> 10.521 s]
>>>>> [INFO] Apache Juneau - Core APIs .......................... SUCCESS [
>>>>> 0.737 s]
>>>>> [INFO] Apache Juneau Marshall ............................. SUCCESS [
>>>>> 45.444 s]
>>>>> [INFO] Apache Juneau Marshal RDF .......................... SUCCESS [
>>>>> 3.558 s]
>>>>> [INFO] Apache Juneau Data Transfer Objects ................ SUCCESS [
>>>>> 6.813 s]
>>>>> [INFO] Apache Juneau Core ................................. SUCCESS [
>>>>> 1.025 s]
>>>>> [INFO] Apache Juneau Config File API ...................... SUCCESS [
>>>>> 1.928 s]
>>>>> [INFO] Apache Juneau Core Tests ........................... SUCCESS
>>>>> [01:04
>>>>> min]
>>>>> [INFO] Apache Juneau - REST APIs .......................... SUCCESS [
>>>>> 0.080 s]
>>>>> [INFO] Apache Juneau REST Servlet API ..................... SUCCESS [
>>>>> 2.331 s]
>>>>> [INFO] Apache Juneau REST JAX/RS API ...................... SUCCESS [
>>>>> 0.476 s]
>>>>> [INFO] Apache Juneau REST Client API ...................... SUCCESS [
>>>>> 1.005 s]
>>>>> [INFO] Apache Juneau - Microservice APIs .................. SUCCESS [
>>>>> 0.068 s]
>>>>> [INFO] Apache Juneau Microservice Server .................. SUCCESS [
>>>>> 1.588 s]
>>>>> [INFO] Apache Juneau Microservice Template ................ SUCCESS [
>>>>> 1.243 s]
>>>>> [INFO] Apache Juneau - Examples ........................... SUCCESS [
>>>>> 0.183 s]
>>>>> [INFO] Apache Juneau REST Examples ........................ SUCCESS [
>>>>> 8.512 s]
>>>>> [INFO] Apache Juneau Microservice Tests ................... SUCCESS [
>>>>> 24.522 s]
>>>>> [INFO] Apache Juneau Core Examples ........................ SUCCESS [
>>>>> 0.287 s]
>>>>> [INFO] Apache Juneau Javadocs ............................. SUCCESS [
>>>>> 0.617 s]
>>>>> [INFO] Apache Juneau - Release Engineering ................ SUCCESS [
>>>>> 0.040 s]
>>>>> [INFO] Apache Juneau UberJar .............................. SUCCESS [
>>>>> 1.008 s]
>>>>> [INFO] Apache Juneau Distribution ......................... SUCCESS [
>>>>> 0.768 s]
>>>>> [INFO] ------------------------------------------------------------
>>>>> ------------
>>>>> [INFO] BUILD SUCCESS
>>>>> [INFO] ------------------------------------------------------------
>>>>> ------------
>>>>> [INFO] Total time: 03:01 min
>>>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>>>>> [INFO] Final Memory: 87M/773M
>>>>> [INFO] ------------------------------------------------------------
>>>>> ------------
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Raphi D Lee, yidonguk@gmail.com
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org> 작성:
>>>>>>
>>>>>> I am pleased to be calling this vote for the source release of Apache
>>>>>> Juneau 6.4.0-incubating RC2.
>>>>>> This includes some fixes for bugs found in RC1 and some packaging
>>>>>> changes
>>>>>> for the example and template projects.
>>>>>>
>>>>>> The list of new features can be found here:
>>>>>> http://juneau.incubator.apache.org/site/apidocs/
>>>>>>
>>>>> overview-summary.html#6.4.0
>>>>>
>>>>>>
>>>>>> The binaries are available at:
>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>
>>>>> binaries/juneau-6.4.0-incubating-RC2/
>>>>>
>>>>>>
>>>>>> The release candidate to be voted over is available at:
>>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>>
>>>>> source/juneau-6.4.0-incubating-RC2/
>>>>>
>>>>>>
>>>>>> SHA-1 checksums:
>>>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
>>>>>> 0-incubating-src.zip
>>>>>> c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
>>>>>> 0-incubating-bin.zip
>>>>>>
>>>>>> MD5 checksums:
>>>>>> e6ef05085093a5235cb9665c65a778fb apache-juneau-6.4.0-incubating
>>>>>> -src.zip
>>>>>> 4e96d5047c0e9f03f0def2d017521f13 apache-juneau-6.4.0-incubating
>>>>>> -bin.zip
>>>>>>
>>>>>> Build the release candidate using:
>>>>>> mvn clean install
>>>>>>
>>>>>> The release candidate is signed with a GPG key available at:
>>>>>> https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS
>>>>>>
>>>>>> A staged Maven repository is available for review at:
>>>>>> https://repository.apache.org/content/repositories/orgapache
>>>>>> juneau-1016/
>>>>>>
>>>>>> The Git commit for this release is...
>>>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>
>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
>>>>>
>>>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>>
>>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37>*
>>>>>
>>>>>>
>>>>>> Please vote on releasing this package as:
>>>>>> Apache Juneau 6.4.0-incubating
>>>>>>
>>>>>> This vote will be open until 20-Sep-2017 9:00pm EST and passes if a
>>>>>> majority of at least three +1 Apache Juneau PPMC votes are cast.
>>>>>>
>>>>>> [ ] +1 Release this package
>>>>>> [ ] 0 I don't feel strongly about it, but don't object
>>>>>> [ ] -1 Do not release this package because...
>>>>>>
>>>>>> Anyone can participate in testing and voting, not just committers,
>>>>>> please
>>>>>> feel free to try out the release candidate and provide your votes.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>
>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by James Bognar <ja...@gmail.com>.
Indeed they are.
I've fixed them in Git. Thanks David!
On Wed, Sep 20, 2017 at 8:25 AM, David Goddard <go...@acm.org> wrote:
> I'm seeing a couple of issues with the Eclipse project names when
> importing a fresh clone into a workspace.
>
> juneau-microservice/.project has <name>juneau-rest</name>
> juneau-doc/.project has <name>juneau-marshall</name>
>
> I'm assuming these are copy/paste errors arising from the restructuring.
>
> David
>
>
>
> On 19/09/2017 18:26, Charles Mims wrote:
>
>> +1, with intermittent test failures in Apache Juneau Microservice Tests
>>
>> MD5 (apache-juneau-6.4.0-incubating-src.zip) =
>> e6ef05085093a5235cb9665c65a778fb
>> For me it failed on the 1st and 2nd try, passed on the 3rd.
>>
>>
>>
>> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <ja...@apache.org>
>> wrote:
>>
>>> ** At this time, I have met “Broken Pipe” issue too. I think we need to
>>> handle this problem soon.
>>>
>>> Darn.
>>>
>>> I'm thinking it must be an issue with Jetty since we just upgraded it.
>>> From the Jetty side, the connection is open waiting for data, but that's
>>> all I know.
>>>
>>> I'll have to figure out how to use Fiddler and do some low-level
>>> debugging. It's really hard to reproduce though :-(
>>>
>>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <yi...@gmail.com>
>>> wrote:
>>>
>>> +1
>>>>
>>>> SHA1, MD5 Checksum OK
>>>> Maven Build OK
>>>>
>>>> ** At this time, I have met “Broken Pipe” issue too. I think we need to
>>>> handle this problem soon.
>>>>
>>>> [INFO] Reactor Summary:
>>>> [INFO]
>>>> [INFO] Apache Juneau (incubating) ......................... SUCCESS [
>>>> 10.521 s]
>>>> [INFO] Apache Juneau - Core APIs .......................... SUCCESS [
>>>> 0.737 s]
>>>> [INFO] Apache Juneau Marshall ............................. SUCCESS [
>>>> 45.444 s]
>>>> [INFO] Apache Juneau Marshal RDF .......................... SUCCESS [
>>>> 3.558 s]
>>>> [INFO] Apache Juneau Data Transfer Objects ................ SUCCESS [
>>>> 6.813 s]
>>>> [INFO] Apache Juneau Core ................................. SUCCESS [
>>>> 1.025 s]
>>>> [INFO] Apache Juneau Config File API ...................... SUCCESS [
>>>> 1.928 s]
>>>> [INFO] Apache Juneau Core Tests ........................... SUCCESS
>>>> [01:04
>>>> min]
>>>> [INFO] Apache Juneau - REST APIs .......................... SUCCESS [
>>>> 0.080 s]
>>>> [INFO] Apache Juneau REST Servlet API ..................... SUCCESS [
>>>> 2.331 s]
>>>> [INFO] Apache Juneau REST JAX/RS API ...................... SUCCESS [
>>>> 0.476 s]
>>>> [INFO] Apache Juneau REST Client API ...................... SUCCESS [
>>>> 1.005 s]
>>>> [INFO] Apache Juneau - Microservice APIs .................. SUCCESS [
>>>> 0.068 s]
>>>> [INFO] Apache Juneau Microservice Server .................. SUCCESS [
>>>> 1.588 s]
>>>> [INFO] Apache Juneau Microservice Template ................ SUCCESS [
>>>> 1.243 s]
>>>> [INFO] Apache Juneau - Examples ........................... SUCCESS [
>>>> 0.183 s]
>>>> [INFO] Apache Juneau REST Examples ........................ SUCCESS [
>>>> 8.512 s]
>>>> [INFO] Apache Juneau Microservice Tests ................... SUCCESS [
>>>> 24.522 s]
>>>> [INFO] Apache Juneau Core Examples ........................ SUCCESS [
>>>> 0.287 s]
>>>> [INFO] Apache Juneau Javadocs ............................. SUCCESS [
>>>> 0.617 s]
>>>> [INFO] Apache Juneau - Release Engineering ................ SUCCESS [
>>>> 0.040 s]
>>>> [INFO] Apache Juneau UberJar .............................. SUCCESS [
>>>> 1.008 s]
>>>> [INFO] Apache Juneau Distribution ......................... SUCCESS [
>>>> 0.768 s]
>>>> [INFO] ------------------------------------------------------------
>>>> ------------
>>>> [INFO] BUILD SUCCESS
>>>> [INFO] ------------------------------------------------------------
>>>> ------------
>>>> [INFO] Total time: 03:01 min
>>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>>>> [INFO] Final Memory: 87M/773M
>>>> [INFO] ------------------------------------------------------------
>>>> ------------
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Raphi D Lee, yidonguk@gmail.com
>>>>
>>>>
>>>>
>>>>
>>>> 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org> 작성:
>>>>>
>>>>> I am pleased to be calling this vote for the source release of Apache
>>>>> Juneau 6.4.0-incubating RC2.
>>>>> This includes some fixes for bugs found in RC1 and some packaging
>>>>> changes
>>>>> for the example and template projects.
>>>>>
>>>>> The list of new features can be found here:
>>>>> http://juneau.incubator.apache.org/site/apidocs/
>>>>>
>>>> overview-summary.html#6.4.0
>>>>
>>>>>
>>>>> The binaries are available at:
>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>
>>>> binaries/juneau-6.4.0-incubating-RC2/
>>>>
>>>>>
>>>>> The release candidate to be voted over is available at:
>>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>>>>
>>>> source/juneau-6.4.0-incubating-RC2/
>>>>
>>>>>
>>>>> SHA-1 checksums:
>>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
>>>>> 0-incubating-src.zip
>>>>> c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
>>>>> 0-incubating-bin.zip
>>>>>
>>>>> MD5 checksums:
>>>>> e6ef05085093a5235cb9665c65a778fb apache-juneau-6.4.0-incubating
>>>>> -src.zip
>>>>> 4e96d5047c0e9f03f0def2d017521f13 apache-juneau-6.4.0-incubating
>>>>> -bin.zip
>>>>>
>>>>> Build the release candidate using:
>>>>> mvn clean install
>>>>>
>>>>> The release candidate is signed with a GPG key available at:
>>>>> https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS
>>>>>
>>>>> A staged Maven repository is available for review at:
>>>>> https://repository.apache.org/content/repositories/orgapache
>>>>> juneau-1016/
>>>>>
>>>>> The Git commit for this release is...
>>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>
>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
>>>>
>>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>>>
>>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37>*
>>>>
>>>>>
>>>>> Please vote on releasing this package as:
>>>>> Apache Juneau 6.4.0-incubating
>>>>>
>>>>> This vote will be open until 20-Sep-2017 9:00pm EST and passes if a
>>>>> majority of at least three +1 Apache Juneau PPMC votes are cast.
>>>>>
>>>>> [ ] +1 Release this package
>>>>> [ ] 0 I don't feel strongly about it, but don't object
>>>>> [ ] -1 Do not release this package because...
>>>>>
>>>>> Anyone can participate in testing and voting, not just committers,
>>>>> please
>>>>> feel free to try out the release candidate and provide your votes.
>>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by David Goddard <go...@acm.org>.
I'm seeing a couple of issues with the Eclipse project names when
importing a fresh clone into a workspace.
juneau-microservice/.project has <name>juneau-rest</name>
juneau-doc/.project has <name>juneau-marshall</name>
I'm assuming these are copy/paste errors arising from the restructuring.
David
On 19/09/2017 18:26, Charles Mims wrote:
> +1, with intermittent test failures in Apache Juneau Microservice Tests
>
> MD5 (apache-juneau-6.4.0-incubating-src.zip) = e6ef05085093a5235cb9665c65a778fb
> For me it failed on the 1st and 2nd try, passed on the 3rd.
>
>
>
> On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <ja...@apache.org> wrote:
>> ** At this time, I have met “Broken Pipe” issue too. I think we need to
>> handle this problem soon.
>>
>> Darn.
>>
>> I'm thinking it must be an issue with Jetty since we just upgraded it.
>> From the Jetty side, the connection is open waiting for data, but that's
>> all I know.
>>
>> I'll have to figure out how to use Fiddler and do some low-level
>> debugging. It's really hard to reproduce though :-(
>>
>> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <yi...@gmail.com> wrote:
>>
>>> +1
>>>
>>> SHA1, MD5 Checksum OK
>>> Maven Build OK
>>>
>>> ** At this time, I have met “Broken Pipe” issue too. I think we need to
>>> handle this problem soon.
>>>
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] Apache Juneau (incubating) ......................... SUCCESS [
>>> 10.521 s]
>>> [INFO] Apache Juneau - Core APIs .......................... SUCCESS [
>>> 0.737 s]
>>> [INFO] Apache Juneau Marshall ............................. SUCCESS [
>>> 45.444 s]
>>> [INFO] Apache Juneau Marshal RDF .......................... SUCCESS [
>>> 3.558 s]
>>> [INFO] Apache Juneau Data Transfer Objects ................ SUCCESS [
>>> 6.813 s]
>>> [INFO] Apache Juneau Core ................................. SUCCESS [
>>> 1.025 s]
>>> [INFO] Apache Juneau Config File API ...................... SUCCESS [
>>> 1.928 s]
>>> [INFO] Apache Juneau Core Tests ........................... SUCCESS [01:04
>>> min]
>>> [INFO] Apache Juneau - REST APIs .......................... SUCCESS [
>>> 0.080 s]
>>> [INFO] Apache Juneau REST Servlet API ..................... SUCCESS [
>>> 2.331 s]
>>> [INFO] Apache Juneau REST JAX/RS API ...................... SUCCESS [
>>> 0.476 s]
>>> [INFO] Apache Juneau REST Client API ...................... SUCCESS [
>>> 1.005 s]
>>> [INFO] Apache Juneau - Microservice APIs .................. SUCCESS [
>>> 0.068 s]
>>> [INFO] Apache Juneau Microservice Server .................. SUCCESS [
>>> 1.588 s]
>>> [INFO] Apache Juneau Microservice Template ................ SUCCESS [
>>> 1.243 s]
>>> [INFO] Apache Juneau - Examples ........................... SUCCESS [
>>> 0.183 s]
>>> [INFO] Apache Juneau REST Examples ........................ SUCCESS [
>>> 8.512 s]
>>> [INFO] Apache Juneau Microservice Tests ................... SUCCESS [
>>> 24.522 s]
>>> [INFO] Apache Juneau Core Examples ........................ SUCCESS [
>>> 0.287 s]
>>> [INFO] Apache Juneau Javadocs ............................. SUCCESS [
>>> 0.617 s]
>>> [INFO] Apache Juneau - Release Engineering ................ SUCCESS [
>>> 0.040 s]
>>> [INFO] Apache Juneau UberJar .............................. SUCCESS [
>>> 1.008 s]
>>> [INFO] Apache Juneau Distribution ......................... SUCCESS [
>>> 0.768 s]
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>> [INFO] BUILD SUCCESS
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>> [INFO] Total time: 03:01 min
>>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>>> [INFO] Final Memory: 87M/773M
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Raphi D Lee, yidonguk@gmail.com
>>>
>>>
>>>
>>>
>>>> 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org> 작성:
>>>>
>>>> I am pleased to be calling this vote for the source release of Apache
>>>> Juneau 6.4.0-incubating RC2.
>>>> This includes some fixes for bugs found in RC1 and some packaging changes
>>>> for the example and template projects.
>>>>
>>>> The list of new features can be found here:
>>>> http://juneau.incubator.apache.org/site/apidocs/
>>> overview-summary.html#6.4.0
>>>>
>>>> The binaries are available at:
>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>> binaries/juneau-6.4.0-incubating-RC2/
>>>>
>>>> The release candidate to be voted over is available at:
>>>> https://dist.apache.org/repos/dist/dev/incubator/juneau/
>>> source/juneau-6.4.0-incubating-RC2/
>>>>
>>>> SHA-1 checksums:
>>>> aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
>>>> 0-incubating-src.zip
>>>> c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
>>>> 0-incubating-bin.zip
>>>>
>>>> MD5 checksums:
>>>> e6ef05085093a5235cb9665c65a778fb apache-juneau-6.4.0-incubating-src.zip
>>>> 4e96d5047c0e9f03f0def2d017521f13 apache-juneau-6.4.0-incubating-bin.zip
>>>>
>>>> Build the release candidate using:
>>>> mvn clean install
>>>>
>>>> The release candidate is signed with a GPG key available at:
>>>> https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS
>>>>
>>>> A staged Maven repository is available for review at:
>>>> https://repository.apache.org/content/repositories/orgapachejuneau-1016/
>>>>
>>>> The Git commit for this release is...
>>>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
>>>> <https://git-wip-us.apache.org/repos/asf?p=incubator-
>>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37>*
>>>>
>>>> Please vote on releasing this package as:
>>>> Apache Juneau 6.4.0-incubating
>>>>
>>>> This vote will be open until 20-Sep-2017 9:00pm EST and passes if a
>>>> majority of at least three +1 Apache Juneau PPMC votes are cast.
>>>>
>>>> [ ] +1 Release this package
>>>> [ ] 0 I don't feel strongly about it, but don't object
>>>> [ ] -1 Do not release this package because...
>>>>
>>>> Anyone can participate in testing and voting, not just committers, please
>>>> feel free to try out the release candidate and provide your votes.
>>>
>>>
>
>
>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by Charles Mims <ch...@mims.io>.
+1, with intermittent test failures in Apache Juneau Microservice Tests
MD5 (apache-juneau-6.4.0-incubating-src.zip) = e6ef05085093a5235cb9665c65a778fb
For me it failed on the 1st and 2nd try, passed on the 3rd.
On Tue, Sep 19, 2017 at 11:11 AM, James Bognar <ja...@apache.org> wrote:
> ** At this time, I have met “Broken Pipe” issue too. I think we need to
> handle this problem soon.
>
> Darn.
>
> I'm thinking it must be an issue with Jetty since we just upgraded it.
> From the Jetty side, the connection is open waiting for data, but that's
> all I know.
>
> I'll have to figure out how to use Fiddler and do some low-level
> debugging. It's really hard to reproduce though :-(
>
> On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <yi...@gmail.com> wrote:
>
>> +1
>>
>> SHA1, MD5 Checksum OK
>> Maven Build OK
>>
>> ** At this time, I have met “Broken Pipe” issue too. I think we need to
>> handle this problem soon.
>>
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache Juneau (incubating) ......................... SUCCESS [
>> 10.521 s]
>> [INFO] Apache Juneau - Core APIs .......................... SUCCESS [
>> 0.737 s]
>> [INFO] Apache Juneau Marshall ............................. SUCCESS [
>> 45.444 s]
>> [INFO] Apache Juneau Marshal RDF .......................... SUCCESS [
>> 3.558 s]
>> [INFO] Apache Juneau Data Transfer Objects ................ SUCCESS [
>> 6.813 s]
>> [INFO] Apache Juneau Core ................................. SUCCESS [
>> 1.025 s]
>> [INFO] Apache Juneau Config File API ...................... SUCCESS [
>> 1.928 s]
>> [INFO] Apache Juneau Core Tests ........................... SUCCESS [01:04
>> min]
>> [INFO] Apache Juneau - REST APIs .......................... SUCCESS [
>> 0.080 s]
>> [INFO] Apache Juneau REST Servlet API ..................... SUCCESS [
>> 2.331 s]
>> [INFO] Apache Juneau REST JAX/RS API ...................... SUCCESS [
>> 0.476 s]
>> [INFO] Apache Juneau REST Client API ...................... SUCCESS [
>> 1.005 s]
>> [INFO] Apache Juneau - Microservice APIs .................. SUCCESS [
>> 0.068 s]
>> [INFO] Apache Juneau Microservice Server .................. SUCCESS [
>> 1.588 s]
>> [INFO] Apache Juneau Microservice Template ................ SUCCESS [
>> 1.243 s]
>> [INFO] Apache Juneau - Examples ........................... SUCCESS [
>> 0.183 s]
>> [INFO] Apache Juneau REST Examples ........................ SUCCESS [
>> 8.512 s]
>> [INFO] Apache Juneau Microservice Tests ................... SUCCESS [
>> 24.522 s]
>> [INFO] Apache Juneau Core Examples ........................ SUCCESS [
>> 0.287 s]
>> [INFO] Apache Juneau Javadocs ............................. SUCCESS [
>> 0.617 s]
>> [INFO] Apache Juneau - Release Engineering ................ SUCCESS [
>> 0.040 s]
>> [INFO] Apache Juneau UberJar .............................. SUCCESS [
>> 1.008 s]
>> [INFO] Apache Juneau Distribution ......................... SUCCESS [
>> 0.768 s]
>> [INFO] ------------------------------------------------------------
>> ------------
>> [INFO] BUILD SUCCESS
>> [INFO] ------------------------------------------------------------
>> ------------
>> [INFO] Total time: 03:01 min
>> [INFO] Finished at: 2017-09-19T20:11:43+09:00
>> [INFO] Final Memory: 87M/773M
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>>
>>
>>
>>
>>
>>
>> Raphi D Lee, yidonguk@gmail.com
>>
>>
>>
>>
>> > 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org> 작성:
>> >
>> > I am pleased to be calling this vote for the source release of Apache
>> > Juneau 6.4.0-incubating RC2.
>> > This includes some fixes for bugs found in RC1 and some packaging changes
>> > for the example and template projects.
>> >
>> > The list of new features can be found here:
>> > http://juneau.incubator.apache.org/site/apidocs/
>> overview-summary.html#6.4.0
>> >
>> > The binaries are available at:
>> > https://dist.apache.org/repos/dist/dev/incubator/juneau/
>> binaries/juneau-6.4.0-incubating-RC2/
>> >
>> > The release candidate to be voted over is available at:
>> > https://dist.apache.org/repos/dist/dev/incubator/juneau/
>> source/juneau-6.4.0-incubating-RC2/
>> >
>> > SHA-1 checksums:
>> > aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
>> > 0-incubating-src.zip
>> > c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
>> > 0-incubating-bin.zip
>> >
>> > MD5 checksums:
>> > e6ef05085093a5235cb9665c65a778fb apache-juneau-6.4.0-incubating-src.zip
>> > 4e96d5047c0e9f03f0def2d017521f13 apache-juneau-6.4.0-incubating-bin.zip
>> >
>> > Build the release candidate using:
>> > mvn clean install
>> >
>> > The release candidate is signed with a GPG key available at:
>> > https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS
>> >
>> > A staged Maven repository is available for review at:
>> > https://repository.apache.org/content/repositories/orgapachejuneau-1016/
>> >
>> > The Git commit for this release is...
>> > *https://git-wip-us.apache.org/repos/asf?p=incubator-
>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
>> > <https://git-wip-us.apache.org/repos/asf?p=incubator-
>> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37>*
>> >
>> > Please vote on releasing this package as:
>> > Apache Juneau 6.4.0-incubating
>> >
>> > This vote will be open until 20-Sep-2017 9:00pm EST and passes if a
>> > majority of at least three +1 Apache Juneau PPMC votes are cast.
>> >
>> > [ ] +1 Release this package
>> > [ ] 0 I don't feel strongly about it, but don't object
>> > [ ] -1 Do not release this package because...
>> >
>> > Anyone can participate in testing and voting, not just committers, please
>> > feel free to try out the release candidate and provide your votes.
>>
>>
--
Charles Mims
pgp key: 81C62E56F930E099
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by James Bognar <ja...@apache.org>.
** At this time, I have met “Broken Pipe” issue too. I think we need to
handle this problem soon.
Darn.
I'm thinking it must be an issue with Jetty since we just upgraded it.
From the Jetty side, the connection is open waiting for data, but that's
all I know.
I'll have to figure out how to use Fiddler and do some low-level
debugging. It's really hard to reproduce though :-(
On Tue, Sep 19, 2017 at 11:32 AM, Raphi D Lee <yi...@gmail.com> wrote:
> +1
>
> SHA1, MD5 Checksum OK
> Maven Build OK
>
> ** At this time, I have met “Broken Pipe” issue too. I think we need to
> handle this problem soon.
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Juneau (incubating) ......................... SUCCESS [
> 10.521 s]
> [INFO] Apache Juneau - Core APIs .......................... SUCCESS [
> 0.737 s]
> [INFO] Apache Juneau Marshall ............................. SUCCESS [
> 45.444 s]
> [INFO] Apache Juneau Marshal RDF .......................... SUCCESS [
> 3.558 s]
> [INFO] Apache Juneau Data Transfer Objects ................ SUCCESS [
> 6.813 s]
> [INFO] Apache Juneau Core ................................. SUCCESS [
> 1.025 s]
> [INFO] Apache Juneau Config File API ...................... SUCCESS [
> 1.928 s]
> [INFO] Apache Juneau Core Tests ........................... SUCCESS [01:04
> min]
> [INFO] Apache Juneau - REST APIs .......................... SUCCESS [
> 0.080 s]
> [INFO] Apache Juneau REST Servlet API ..................... SUCCESS [
> 2.331 s]
> [INFO] Apache Juneau REST JAX/RS API ...................... SUCCESS [
> 0.476 s]
> [INFO] Apache Juneau REST Client API ...................... SUCCESS [
> 1.005 s]
> [INFO] Apache Juneau - Microservice APIs .................. SUCCESS [
> 0.068 s]
> [INFO] Apache Juneau Microservice Server .................. SUCCESS [
> 1.588 s]
> [INFO] Apache Juneau Microservice Template ................ SUCCESS [
> 1.243 s]
> [INFO] Apache Juneau - Examples ........................... SUCCESS [
> 0.183 s]
> [INFO] Apache Juneau REST Examples ........................ SUCCESS [
> 8.512 s]
> [INFO] Apache Juneau Microservice Tests ................... SUCCESS [
> 24.522 s]
> [INFO] Apache Juneau Core Examples ........................ SUCCESS [
> 0.287 s]
> [INFO] Apache Juneau Javadocs ............................. SUCCESS [
> 0.617 s]
> [INFO] Apache Juneau - Release Engineering ................ SUCCESS [
> 0.040 s]
> [INFO] Apache Juneau UberJar .............................. SUCCESS [
> 1.008 s]
> [INFO] Apache Juneau Distribution ......................... SUCCESS [
> 0.768 s]
> [INFO] ------------------------------------------------------------
> ------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------
> ------------
> [INFO] Total time: 03:01 min
> [INFO] Finished at: 2017-09-19T20:11:43+09:00
> [INFO] Final Memory: 87M/773M
> [INFO] ------------------------------------------------------------
> ------------
>
>
>
>
>
>
>
> Raphi D Lee, yidonguk@gmail.com
>
>
>
>
> > 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org> 작성:
> >
> > I am pleased to be calling this vote for the source release of Apache
> > Juneau 6.4.0-incubating RC2.
> > This includes some fixes for bugs found in RC1 and some packaging changes
> > for the example and template projects.
> >
> > The list of new features can be found here:
> > http://juneau.incubator.apache.org/site/apidocs/
> overview-summary.html#6.4.0
> >
> > The binaries are available at:
> > https://dist.apache.org/repos/dist/dev/incubator/juneau/
> binaries/juneau-6.4.0-incubating-RC2/
> >
> > The release candidate to be voted over is available at:
> > https://dist.apache.org/repos/dist/dev/incubator/juneau/
> source/juneau-6.4.0-incubating-RC2/
> >
> > SHA-1 checksums:
> > aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
> > 0-incubating-src.zip
> > c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
> > 0-incubating-bin.zip
> >
> > MD5 checksums:
> > e6ef05085093a5235cb9665c65a778fb apache-juneau-6.4.0-incubating-src.zip
> > 4e96d5047c0e9f03f0def2d017521f13 apache-juneau-6.4.0-incubating-bin.zip
> >
> > Build the release candidate using:
> > mvn clean install
> >
> > The release candidate is signed with a GPG key available at:
> > https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS
> >
> > A staged Maven repository is available for review at:
> > https://repository.apache.org/content/repositories/orgapachejuneau-1016/
> >
> > The Git commit for this release is...
> > *https://git-wip-us.apache.org/repos/asf?p=incubator-
> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
> > <https://git-wip-us.apache.org/repos/asf?p=incubator-
> juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37>*
> >
> > Please vote on releasing this package as:
> > Apache Juneau 6.4.0-incubating
> >
> > This vote will be open until 20-Sep-2017 9:00pm EST and passes if a
> > majority of at least three +1 Apache Juneau PPMC votes are cast.
> >
> > [ ] +1 Release this package
> > [ ] 0 I don't feel strongly about it, but don't object
> > [ ] -1 Do not release this package because...
> >
> > Anyone can participate in testing and voting, not just committers, please
> > feel free to try out the release candidate and provide your votes.
>
>
Re: [VOTE] Release Apache Juneau 6.4.0-incubating RC2
Posted by Raphi D Lee <yi...@gmail.com>.
+1
SHA1, MD5 Checksum OK
Maven Build OK
** At this time, I have met “Broken Pipe” issue too. I think we need to handle this problem soon.
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Juneau (incubating) ......................... SUCCESS [ 10.521 s]
[INFO] Apache Juneau - Core APIs .......................... SUCCESS [ 0.737 s]
[INFO] Apache Juneau Marshall ............................. SUCCESS [ 45.444 s]
[INFO] Apache Juneau Marshal RDF .......................... SUCCESS [ 3.558 s]
[INFO] Apache Juneau Data Transfer Objects ................ SUCCESS [ 6.813 s]
[INFO] Apache Juneau Core ................................. SUCCESS [ 1.025 s]
[INFO] Apache Juneau Config File API ...................... SUCCESS [ 1.928 s]
[INFO] Apache Juneau Core Tests ........................... SUCCESS [01:04 min]
[INFO] Apache Juneau - REST APIs .......................... SUCCESS [ 0.080 s]
[INFO] Apache Juneau REST Servlet API ..................... SUCCESS [ 2.331 s]
[INFO] Apache Juneau REST JAX/RS API ...................... SUCCESS [ 0.476 s]
[INFO] Apache Juneau REST Client API ...................... SUCCESS [ 1.005 s]
[INFO] Apache Juneau - Microservice APIs .................. SUCCESS [ 0.068 s]
[INFO] Apache Juneau Microservice Server .................. SUCCESS [ 1.588 s]
[INFO] Apache Juneau Microservice Template ................ SUCCESS [ 1.243 s]
[INFO] Apache Juneau - Examples ........................... SUCCESS [ 0.183 s]
[INFO] Apache Juneau REST Examples ........................ SUCCESS [ 8.512 s]
[INFO] Apache Juneau Microservice Tests ................... SUCCESS [ 24.522 s]
[INFO] Apache Juneau Core Examples ........................ SUCCESS [ 0.287 s]
[INFO] Apache Juneau Javadocs ............................. SUCCESS [ 0.617 s]
[INFO] Apache Juneau - Release Engineering ................ SUCCESS [ 0.040 s]
[INFO] Apache Juneau UberJar .............................. SUCCESS [ 1.008 s]
[INFO] Apache Juneau Distribution ......................... SUCCESS [ 0.768 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 03:01 min
[INFO] Finished at: 2017-09-19T20:11:43+09:00
[INFO] Final Memory: 87M/773M
[INFO] ------------------------------------------------------------------------
Raphi D Lee, yidonguk@gmail.com
> 2017. 9. 18. 오전 9:54, James Bognar <ja...@apache.org> 작성:
>
> I am pleased to be calling this vote for the source release of Apache
> Juneau 6.4.0-incubating RC2.
> This includes some fixes for bugs found in RC1 and some packaging changes
> for the example and template projects.
>
> The list of new features can be found here:
> http://juneau.incubator.apache.org/site/apidocs/overview-summary.html#6.4.0
>
> The binaries are available at:
> https://dist.apache.org/repos/dist/dev/incubator/juneau/binaries/juneau-6.4.0-incubating-RC2/
>
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/juneau/source/juneau-6.4.0-incubating-RC2/
>
> SHA-1 checksums:
> aeb89ecf6b0da5e8b594455a349f1f7efa483f81 apache-juneau-6.4.
> 0-incubating-src.zip
> c3d4a1d7c21142a4006876419729d9f0c352203e apache-juneau-6.4.
> 0-incubating-bin.zip
>
> MD5 checksums:
> e6ef05085093a5235cb9665c65a778fb apache-juneau-6.4.0-incubating-src.zip
> 4e96d5047c0e9f03f0def2d017521f13 apache-juneau-6.4.0-incubating-bin.zip
>
> Build the release candidate using:
> mvn clean install
>
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachejuneau-1016/
>
> The Git commit for this release is...
> *https://git-wip-us.apache.org/repos/asf?p=incubator-juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37
> <https://git-wip-us.apache.org/repos/asf?p=incubator-juneau.git;a=commit;h=6de998193807eeec40e6f297f6b70222552f3b37>*
>
> Please vote on releasing this package as:
> Apache Juneau 6.4.0-incubating
>
> This vote will be open until 20-Sep-2017 9:00pm EST and passes if a
> majority of at least three +1 Apache Juneau PPMC votes are cast.
>
> [ ] +1 Release this package
> [ ] 0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
> Anyone can participate in testing and voting, not just committers, please
> feel free to try out the release candidate and provide your votes.