Re: Apache Polygene - Future Directions

et's look at SQL DB as an example. Tables of rows with relationships are fairly easy to model. One could even imagine a client tool where the relations are described and that generates a Polygene model from it. Ideally interactively (graphical even), but even a some description language (SQL?) sh

Re: New logos

helix. I >> had a similar thought, >> to just replace the two red strokes (the vapour) with a double-helix in >> the current logo. >> >> Georg >> >> I'm not found of it but it shows that it's easy to make sense of the >>> name visually. We could find an illustration

[jira] [Updated] (POLYGENE-204) Change of Logo to reflect new name

[ https://issues.apache.org/jira/browse/POLYGENE-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman updated POLYGENE-204: Attachment: Screenshot_20161230_090035.png > Change of Logo to reflect new n

[jira] [Commented] (POLYGENE-204) Change of Logo to reflect new name

[ https://issues.apache.org/jira/browse/POLYGENE-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15786546#comment-15786546 ] Niclas Hedhman commented on POLYGENE-204: - Also attached my PoweredBy logo proposal. > Cha

[jira] [Commented] (POLYGENE-204) Change of Logo to reflect new name

[ https://issues.apache.org/jira/browse/POLYGENE-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15786533#comment-15786533 ] Niclas Hedhman commented on POLYGENE-204: - Attached first attempt at a Apache Polygene logo

[jira] [Updated] (POLYGENE-204) Change of Logo to reflect new name

[ https://issues.apache.org/jira/browse/POLYGENE-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman updated POLYGENE-204: Attachment: polygene1.png > Change of Logo to reflect new n

[jira] [Resolved] (POLYGENE-211) Apply name change to apache.org navigation

[ https://issues.apache.org/jira/browse/POLYGENE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman resolved POLYGENE-211. - Resolution: Fixed This was done prematurely, as the site is not up yet, since

Race is ON!

the issue with gitpubsub or svnpubsub before the site can be up. Grrr -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

[jira] [Commented] (POLYGENE-209) Request new domain name and gitpubsub from INFRA

[ https://issues.apache.org/jira/browse/POLYGENE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15786491#comment-15786491 ] Niclas Hedhman commented on POLYGENE-209: - Whimsy relies on batch job, and that has now been

[jira] [Closed] (ZEST-216) Change name in Board Report Schedule

[ https://issues.apache.org/jira/browse/ZEST-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman closed ZEST-216. --- Resolution: Fixed > Change name in Board Report Sched

[jira] [Commented] (ZEST-211) Apply name change to apache.org navigation

[ https://issues.apache.org/jira/browse/ZEST-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15772193#comment-15772193 ] Niclas Hedhman commented on ZEST-211: - We can't publish to navigation until the new site is up on https

[jira] [Assigned] (ZEST-219) Update committers/board/committee-info.txt

[ https://issues.apache.org/jira/browse/ZEST-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman reassigned ZEST-219: --- Assignee: Niclas Hedhman > Update committers/board/committee-info.

[jira] [Assigned] (ZEST-216) Change name in Board Report Schedule

[ https://issues.apache.org/jira/browse/ZEST-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman reassigned ZEST-216: --- Assignee: Niclas Hedhman > Change name in Board Report Sched

[jira] [Assigned] (ZEST-210) Deploy website with new branding under new domain name

[ https://issues.apache.org/jira/browse/ZEST-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman reassigned ZEST-210: --- Assignee: Paul Merlin > Deploy website with new branding under new domain n

[jira] [Assigned] (ZEST-211) Apply name change to apache.org navigation

[ https://issues.apache.org/jira/browse/ZEST-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman reassigned ZEST-211: --- Assignee: Niclas Hedhman > Apply name change to apache.org navigat

[jira] [Resolved] (ZEST-208) Apply name change to website content

[ https://issues.apache.org/jira/browse/ZEST-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman resolved ZEST-208. - Resolution: Fixed Changes commited to https://svn.apache.org/repos/asf/zest/site/src

[jira] [Assigned] (ZEST-208) Apply name change to website content

[ https://issues.apache.org/jira/browse/ZEST-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman reassigned ZEST-208: --- Assignee: Niclas Hedhman > Apply name change to website cont

[jira] [Created] (ZEST-220) Board Resolution

Niclas Hedhman created ZEST-220: --- Summary: Board Resolution Key: ZEST-220 URL: https://issues.apache.org/jira/browse/ZEST-220 Project: Zest Issue Type: Sub-task Reporter: Niclas

[jira] [Created] (ZEST-219) Update committers/board/committee-info.txt

Niclas Hedhman created ZEST-219: --- Summary: Update committers/board/committee-info.txt Key: ZEST-219 URL: https://issues.apache.org/jira/browse/ZEST-219 Project: Zest Issue Type: Sub-task

[jira] [Closed] (ZEST-218) Change affiliations.txt

[ https://issues.apache.org/jira/browse/ZEST-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman closed ZEST-218. --- Resolution: Fixed > Change affiliations.txt > --- > > K

[jira] [Closed] (ZEST-217) Change in irs-disclosures.txt

[ https://issues.apache.org/jira/browse/ZEST-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman closed ZEST-217. --- > Change in irs-disclosures.txt > - > > K

[jira] [Created] (ZEST-218) Change affiliations.txt

Niclas Hedhman created ZEST-218: --- Summary: Change affiliations.txt Key: ZEST-218 URL: https://issues.apache.org/jira/browse/ZEST-218 Project: Zest Issue Type: Sub-task Reporter

[jira] [Created] (ZEST-217) Change in irs-disclosures.txt

Niclas Hedhman created ZEST-217: --- Summary: Change in irs-disclosures.txt Key: ZEST-217 URL: https://issues.apache.org/jira/browse/ZEST-217 Project: Zest Issue Type: Sub-task

[jira] [Created] (ZEST-216) Change name in Board Report Schedule

Niclas Hedhman created ZEST-216: --- Summary: Change name in Board Report Schedule Key: ZEST-216 URL: https://issues.apache.org/jira/browse/ZEST-216 Project: Zest Issue Type: Sub-task

Re: Apache Polygene - Future Directions

If I understand your intention (Christmas Wish) correctly, you want to marry our pink unicorn with the green monster, or? I am not a Spring addict, and don't want to see a hard dependency on it. Work to strengthen the spring integration is most welcome, but I think need to be handled by someone

[jira] [Assigned] (ZEST-199) Rename Git repositories

[ https://issues.apache.org/jira/browse/ZEST-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman reassigned ZEST-199: --- Assignee: Niclas Hedhman > Rename Git repositor

[jira] [Assigned] (ZEST-198) Rename Jira project

[ https://issues.apache.org/jira/browse/ZEST-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman reassigned ZEST-198: --- Assignee: Niclas Hedhman > Rename Jira project > --- > >

[jira] [Assigned] (ZEST-197) Rename mailing lists

[ https://issues.apache.org/jira/browse/ZEST-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman reassigned ZEST-197: --- Assignee: Niclas Hedhman > Rename mailing lists > > >

[jira] [Commented] (ZEST-197) Rename mailing lists

[ https://issues.apache.org/jira/browse/ZEST-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15756172#comment-15756172 ] Niclas Hedhman commented on ZEST-197: - See INFRA-13127 > Rename mailing li

[jira] [Commented] (ZEST-199) Rename Git repositories

[ https://issues.apache.org/jira/browse/ZEST-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15756173#comment-15756173 ] Niclas Hedhman commented on ZEST-199: - See INFRA-13126 > Rename Git repositor

[jira] [Commented] (ZEST-198) Rename Jira project

[ https://issues.apache.org/jira/browse/ZEST-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15756168#comment-15756168 ] Niclas Hedhman commented on ZEST-198: - See INFRA-13125 > Rename Jira proj

[jira] [Commented] (ZEST-195) Project Name Change

[ https://issues.apache.org/jira/browse/ZEST-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15756169#comment-15756169 ] Niclas Hedhman commented on ZEST-195: - See INFRA-13124 > Project Name Cha

Fwd: [NOTICE] - analysis.apache.org closing down 14th January

st. Thanks and good luck, enjoy the new service. Gav… (ASF Infra) -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

[jira] [Assigned] (ZEST-201) Apply name change to code

[ https://issues.apache.org/jira/browse/ZEST-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman reassigned ZEST-201: --- Assignee: Niclas Hedhman > Apply name change to c

[jira] [Closed] (ZEST-214) Rename packages in codebase

[ https://issues.apache.org/jira/browse/ZEST-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman closed ZEST-214. --- Resolution: Duplicate Duplicate ZEST-201 > Rename packages in codeb

Re: TLP Name Change - How?

Uhhh The https://reference.apache.org/infra/tlpreq is protected "Infra Team only", and not available to members. On Tue, Dec 13, 2016 at 6:49 PM, Greg Stein <gst...@gmail.com> wrote: > > > On Tue, Dec 13, 2016 at 4:41 AM, Niclas Hedhman <nic...@hedhman.org>

Re: TLP Name Change - How?

2016 at 4:41 AM, Niclas Hedhman <nic...@hedhman.org> > wrote: > >> Dear Infra Heroes, >> >> Apache Zest PMC has seen it be necessary[1] to change name and Trademarks >> has just approved the proposed name of "Apache Polygene". >> >> TLP na

[jira] [Created] (ZEST-215) Create JDK8 and JDK9 specific test modules

Niclas Hedhman created ZEST-215: --- Summary: Create JDK8 and JDK9 specific test modules Key: ZEST-215 URL: https://issues.apache.org/jira/browse/ZEST-215 Project: Zest Issue Type: Bug

[jira] [Created] (ZEST-214) Rename packages in codebase

Niclas Hedhman created ZEST-214: --- Summary: Rename packages in codebase Key: ZEST-214 URL: https://issues.apache.org/jira/browse/ZEST-214 Project: Zest Issue Type: Sub-task Reporter

TLP Name Change - How?

from Infra, or is there a better/easier way for you? [1] Enough technical overlap of an Eclipse Foundation subproject called Zest, to potentially create confusion. Thanks. -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

[jira] [Resolved] (ZEST-196) Name Search

[ https://issues.apache.org/jira/browse/ZEST-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman resolved ZEST-196. - Resolution: Fixed Assignee: Niclas Hedhman Approved by Shane Curcuru in PODLINGNAMESEARCH-115

Polygene is approved

g/jira/browse/PODLINGNAMESEARCH-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel> Cheers -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

Re: JDK 9 b148 including a refresh of the module system is available on java.net

permail/jdk9-dev/2016-Novembe > r/005276.html <http://mail.openjdk.java.net/pipermail/jpms-spec-experts/20 > 16-October/000430.html> > > [2] http://openjdk.java.net/projects/jigsaw/spec/issues/#Awkward > StrongEncapsulation > > -- > Rgds,Rory O'Donnell > Quality Engineering Manager > Oracle EMEA , Dublin, Ireland > > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

Re: org.apache.zest.io an org.apache.zest.functional

ommit, core/io is completely unused across the whole SDK. > > > > The code is much simpler even if in some cases it's still quite > > convoluted to map the underlying stores APIs to Streams. > > > > Please review and comment so I can move forward, address your comments &g

Re: SPI or @Structure

s/factories". I prefer consistency. Cheers Niclas On Thu, Dec 8, 2016 at 10:35 PM, Paul Merlin <paulmer...@apache.org> wrote: > Niclas Hedhman a écrit : > > Ok, > > should we then stop having Module extends XyzFactory, and they are > obtained > > likewise? J

Re: SPI or @Structure

implements ValueBuilderFactory at the moment. Niclas On Thu, Dec 8, 2016 at 7:00 PM, Paul Merlin <paulmer...@apache.org> wrote: > Niclas Hedhman a écrit : > > The org.apache.zest.spi.module.ModuleSpi contains access methods to a > bunch > > of useful SPI internals, such as

IntelliJ Ultimate Edition

est. State that it is for Apache Software Foundation, and the Apache Zest project with link to http://zest.apache.org Cheers -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

Re: vhostTest is not detected as a Test dir

What happens is that src/perf and src/vhost-test are "Sources" (blue) directories instead of "Tests" (green) directories. Dependencies were incorrect, so that dnsjava was not seen. On Wed, Dec 7, 2016 at 7:30 PM, Paul Merlin <paulmer...@apache.org> wrote: > Niclas

Re: vhostTest is not detected as a Test dir

Also, instead of a vhost-test, why not have tests/jdk8 and tests/jdk9 which are specific tests for each platform? On Wed, Dec 7, 2016 at 7:22 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > I also don't use the plugin, but open the build.gradle file directly. > > I am on Intel

Re: vhostTest is not detected as a Test dir

ble. > > I'm not using ./gradlew idea anymore. > > > Niclas Hedhman a écrit : > > The same problem exists for src/perf/java in tests/performance. > > > > Could we name this back to src/test? > > > > And if so, should we move the vhostTest stuff to a tes

Re: Gradle Build support

Actually, more like; apply plugin: 'polygene' // also sets the repositories needed. > dependencies { > polygene.core() // sets up compile, runtime, testCompile > > if possible... On Wed, Dec 7, 2016 at 6:58 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > I did

Re: vhostTest is not detected as a Test dir

ec 7, 2016 at 5:22 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > Paul, > isn't it cool that we have a Gradle expert in the team :-) > > Your very elaborate handling of JDK 9 in libraries/http creates a problem > in the IDEA-Gradle integration. > > The vhostTest so

SPI or @Structure

?) If not, shouldn't then everything be moved to the Module or ModuleSpi as methods, instead of injectable types? WDYT? Cheers -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

vhostTest is not detected as a Test dir

bring in the dnsjava dependency, so even if I change it manualy to a "test/java" it is not resolved, and as soon as the dependencies are recomputed, we are back to "src/java". Any ideas? Cheers -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

Re: Checked Exceptions

Sounds good. On Tue, Dec 6, 2016 at 5:44 PM, Paul Merlin <paulmer...@apache.org> wrote: > Le 2016-12-05 13:04, Niclas Hedhman a écrit : > >> I am also "kind of" ok with removing the checked exceptions. But there are >> a couple of places where java.lang.Exce

Fwd: [REPORT]{DRAFT] Apache Zest Report

It is reporting season, and I am proposing the following updated draft to be submitted; The previous draft was incorrectly submitted to private@; Sorry about that. If no objections, I will submit this to board by tomorrow. -o-o-o-o- Report from the Apache Zest committee [Niclas Hedhman

Re: Checked Exceptions

way, like checked exceptions do, when writing lambdas. > > The most annoying one is AssemblyException, it prevent us from writing > > concise application assemblies. > > > > I'd be in favor of changing these to non-checked exceptions. > > > > WDYT? > > > > /Paul > > > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

Re: Checked Exceptions

n > > > > They get in the way, like checked exceptions do, when writing lambdas. > > The most annoying one is AssemblyException, it prevent us from writing > > concise application assemblies. > > > > I'd be in favor of changing these to non-checked exceptions. > > > > WDYT? > > > > /Paul > > > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

Name change consequences

Gang, as you can see from the many created Jira issues, the name change has a lot of consequences. If you can think of anything else, please add. If you can help out, please do so... Cheers -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

[jira] [Created] (ZEST-205) Modify build system for new name.

Niclas Hedhman created ZEST-205: --- Summary: Modify build system for new name. Key: ZEST-205 URL: https://issues.apache.org/jira/browse/ZEST-205 Project: Zest Issue Type: Sub-task

[jira] [Created] (ZEST-203) Issue press release about name change.

Niclas Hedhman created ZEST-203: --- Summary: Issue press release about name change. Key: ZEST-203 URL: https://issues.apache.org/jira/browse/ZEST-203 Project: Zest Issue Type: Sub-task

[jira] [Created] (ZEST-199) Rename Git repository

Niclas Hedhman created ZEST-199: --- Summary: Rename Git repository Key: ZEST-199 URL: https://issues.apache.org/jira/browse/ZEST-199 Project: Zest Issue Type: Sub-task Reporter

[jira] [Created] (ZEST-198) Rename Jira project

Niclas Hedhman created ZEST-198: --- Summary: Rename Jira project Key: ZEST-198 URL: https://issues.apache.org/jira/browse/ZEST-198 Project: Zest Issue Type: Sub-task Reporter: Niclas

[jira] [Commented] (ZEST-195) Project Name Change

[ https://issues.apache.org/jira/browse/ZEST-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15720942#comment-15720942 ] Niclas Hedhman commented on ZEST-195: - The winning candidate is; APACHE POLYGENE/POLYGENIC

Re: [RESULT][VOTE] New name

*Apache Polygene* it is. On Mon, Dec 5, 2016 at 2:04 AM, Jiri Jetmar <juergen.jet...@gmail.com> wrote: > same here - Polygene > > 2016-12-04 18:51 GMT+01:00 Paul Merlin <paulmer...@apache.org>: > > > Le 2016-12-04 11:12, Niclas Hedhman a écrit : > > > &

[RESULT][VOTE] New name

Any other opinions on this? Meanwhile, I will start the process of name change. Cheers -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

[jira] [Commented] (ZEST-195) Project Name Change

[ https://issues.apache.org/jira/browse/ZEST-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15719492#comment-15719492 ] Niclas Hedhman commented on ZEST-195: - Vote thread; https://lists.apache.org/thread.html

[jira] [Created] (ZEST-195) Project Name Change

Niclas Hedhman created ZEST-195: --- Summary: Project Name Change Key: ZEST-195 URL: https://issues.apache.org/jira/browse/ZEST-195 Project: Zest Issue Type: Task Reporter: Niclas

Re: [VOTE] New name

[ ] Apache Aardworx [ ] Apache Accaly [x] Apache Polygenic/Polygene (decide later) [ ] Apache Vorticity On Thu, Dec 1, 2016 at 4:11 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > Sorry to bother about this again... > > Restarting the vote on name change, as no more suggestio

[VOTE] New name

Sorry to bother about this again... Restarting the vote on name change, as no more suggestions have arrived; [ ] Apache Aardworx [ ] Apache Accaly [ ] Apache Polygenic/Polygene (decide later) [ ] Apache Vorticity Thanks -- Niclas Hedhman, Software Developer http://zest.apache.org - New

Re: Name finding... Again..

I will throw in one more proposed name; * Apache Dexteros Derived from Dexterity or Dexterous, but I recommend emphasis on "te" [deks'teros], as if it is a Greek word. 17,500 hits on Google,mostly user names on various social media. Cheers On Wed, Nov 23, 2016 at 10:35 AM, Niclas He

Re: org.apache.zest.io an org.apache.zest.functional

Paul, Great job done on the Iterables stuff... I didn't really anticipated a complete removal before the 3.0 release, but... On Tue, Nov 29, 2016 at 12:19 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > Most (all?) Iterables in Core was replaced before. > > For exceptions, &g

Re: org.apache.zest.io an org.apache.zest.functional

that in the caller. Niclas On Tue, Nov 29, 2016 at 12:41 AM, Paul Merlin <paulmer...@apache.org> wrote: > Niclas Hedhman a écrit : > > These two modules and their classes are largely replaced with the Java 8 > > Stream API already. I will try to get rid of the completely, as th

Name finding... Again..

(or family name) on Facebook and plenty of misspellings of "actually") -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

[VOTE CANCELLED] New name

Due to the conflicting name with Netflix Zeno (and others), I want to cancel this vote and find a new set of acceptable names to vote on. Sorry about the inconvenience. Cheers -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

Re: [VOTE] New name

:-( Yeah, I think all relationship to any mythology, science, philosophy, math, animals and more are kind of used up... Doing name search first, seems to be needed, yet it was quite a lot of effort for Zest when I did it. Niclas On Nov 22, 2016 16:42, "Paul Merlin"

Re: [VOTE] New name

My vote; [ ] Apache Accaly [ ] Apache Akira [x] Apache Zeno [ ] None of the above -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

[VOTE] New name

forwarded, and I have narrowed it down to these 3 + a choice to express dissatisfaction with the shortlist. Please cast your votes; [ ] Apache Accaly [ ] Apache Akira [ ] Apache Zeno [ ] None of the above I urge all participants in the community to express their wishes. Thank you -- Niclas

Re: Project name change

back are; 1. Apache Accaly 2. Apache Zeno 3. Apache Akira Anyone else with opinion? Niclas On Sun, Nov 13, 2016 at 8:01 AM, Niclas Hedhman <nic...@hedhman.org> wrote: > Two reasons as far as I remember; > 1. Pronunciation > 2. "Fresh start" > > > > On Sat

Re: Project name change

match better than the other > suggestions. > > So the other way round: Should we find a name which can be associated > easily > with the current logo, or is that irrelevant? I guess finding/creating a > new, > appealing logo isn't that easy. > > my 2 cents from outer space

Re: Project name change

0,000 - Qi = 161,000,000 - Zoe = 173,000,000 - Zen = 297,000,000 - Essence = 305,000,000 - COP = 306,000,000 - Aura = 324,000,000 - Zopper = 597,000,000 - Energy = 1,500,000,000 -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

Re: Project name change

ears ago, it was decided that ASF should avoid any more native American references, so let's drop these from the list. -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

[jira] [Commented] (ZEST-191) Remove org.json java library

[ https://issues.apache.org/jira/browse/ZEST-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15641012#comment-15641012 ] Niclas Hedhman commented on ZEST-191: - I am happy that we remove the dependency anyway. I want core

[jira] [Commented] (ZEST-191) Remove org.json java library

[ https://issues.apache.org/jira/browse/ZEST-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15641006#comment-15641006 ] Niclas Hedhman commented on ZEST-191: - I found the reason; https://lists.apache.org/thread.html

Re: Project name change

>From VP Trademarks, Shane Curcuru, we got an independent suggestion; - Apache Zop On Thu, Nov 3, 2016 at 11:41 AM, Niclas Hedhman <nic...@hedhman.org> wrote: > Gang, > We had an oversight when we chose name, almost 2 years ago. Eclipse Zest > is still an active project,

Project name change

this name change. [1] https://www.eclipse.org/gef/zest/ [2] https://groups.google.com/forum/#!topic/qi4j-dev/wXg2MdHU-oU -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

[jira] [Commented] (ZEST-190) Refine Metrics API/SPI

[ https://issues.apache.org/jira/browse/ZEST-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603733#comment-15603733 ] Niclas Hedhman commented on ZEST-190: - I agree. The original design was rushed together too quickly

Re: Postgresql indexing tests

Giving up for now... I think the general problem is that Identity is a missing type for the Indexing system, and not so much about the toString() conversion that seems to have been missed only once. Cheers Niclas On Mon, Oct 24, 2016 at 9:26 PM, Niclas Hedhman <nic...@hedhman.org>

Postgresql indexing tests

in org.apache.zest.index.sql.support.postgresql.PostgreSQLTypeHelper.SQLTypeHelperMixin#getSQLType(java.lang.reflect.Type) That fixed all the test org.apache.zest.index.sql.postgresql.PostgreSQLQueryTest,script34 Continuing -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

Re: [WARNING] Unstable 'develop' branch

Ii have figured it out... I missed the "reconnect to the jdbc_test_db as a superuser". My ltree addition happened outside the database "jdbc_test_db"... On my way now. On Mon, Oct 24, 2016 at 8:30 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > If I go back to

Re: [WARNING] Unstable 'develop' branch

If I go back to psql, I get this informative message postgres=# CREATE EXTENSION ltree; ERROR: extension "ltree" already exists On Mon, Oct 24, 2016 at 8:23 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > > Caused by: org.postgresql.util.PSQLException: ERROR: type l

Re: [WARNING] Unstable 'develop' branch

) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:286) Is there an easy way to test ltree presence with the psql command line? On Mon, Oct 24, 2016 at 8:20 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > Ah, I see... > > stmt.execute( this._ven

Re: [WARNING] Unstable 'develop' branch

t shown. Adding the root cause and running again. On Mon, Oct 24, 2016 at 8:16 PM, Stanislav Muhametsin < stanislav.muhamet...@zest.mail.kapsi.fi> wrote: > On 24.10.2016 15:05, Niclas Hedhman wrote: > >> I managed to install postgres locally and set up according to y

Re: [3/3] zest-java git commit: ZEST-180 Indexing-SQL uses the String form of Identity

if( value instanceof EntityComposite ) > { > value = uowf.currentUnitOfWork().get( > -(EntityComposite) value ).identity().get(); > + (EntityComposite) value > ).identity().get().toStrin

[jira] [Commented] (ZEST-180) Replace String with Identity

[ https://issues.apache.org/jira/browse/ZEST-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15601739#comment-15601739 ] Niclas Hedhman commented on ZEST-180: - I'll go through the test report now > Replace Str

[jira] [Resolved] (ZEST-189) Remove old UuidIdentityGeneratorService from Core SPI

[ https://issues.apache.org/jira/browse/ZEST-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman resolved ZEST-189. - Resolution: Fixed > Remove old UuidIdentityGeneratorService from Core

[jira] [Created] (ZEST-189) Remove old UuidIdentityGeneratorService from Core SPI

Niclas Hedhman created ZEST-189: --- Summary: Remove old UuidIdentityGeneratorService from Core SPI Key: ZEST-189 URL: https://issues.apache.org/jira/browse/ZEST-189 Project: Zest Issue Type

GitHub mirror not updated...

few minutes later. Cheers [1] https://git-wip-us.apache.org/repos/asf?p=zest-java.git;a=commit;h=103c59cbeb2907d0b3a132a1aa852e2e1b8585ae -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java

Re: [WARNING] Unstable 'develop' branch

It seems that something has gone wrong. The changes (the many commit emails confirms that) has not reached GitHub mirror, which is normally only seconds away. I will try to ping infra about it. Niclas On Sun, Oct 23, 2016 at 10:20 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > The

[jira] [Created] (ZEST-188) Remove Scala language support

Niclas Hedhman created ZEST-188: --- Summary: Remove Scala language support Key: ZEST-188 URL: https://issues.apache.org/jira/browse/ZEST-188 Project: Zest Issue Type: Task Reporter

  1   2   3   4   5   6   7   >