[
https://issues.apache.org/jira/browse/POLYGENE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin reassigned POLYGENE-200:
Assignee: Paul Merlin
> Redirect zest.apache.org to polygene.apache.
[
https://issues.apache.org/jira/browse/POLYGENE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15789600#comment-15789600
]
Paul Merlin commented on POLYGENE-210:
--
The website is now in the `polygene-website` GIT repository
[
https://issues.apache.org/jira/browse/POLYGENE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated POLYGENE-129:
-
Summary: @PreDestroy and @PostConstruct in lieu of initializable and
service activation
[
https://issues.apache.org/jira/browse/POLYGENE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated POLYGENE-129:
-
Issue Type: Improvement (was: Bug)
Summary: @PreDestroy and @PostConstruct in lieu
[
https://issues.apache.org/jira/browse/POLYGENE-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin resolved POLYGENE-212.
--
Resolution: Fixed
> Require new groupId for Maven repositories from IN
Hi Niclas,
I second Stanislav, we need a new logo.
But we can get polygene.apache.org up online without it, simply reusing
the old logo for now.
The logo we display on the home page is comprised of two images:
http://zest.apache.org/graphics/Qi4j-Logo-Symbol.png
[
https://issues.apache.org/jira/browse/POLYGENE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin resolved POLYGENE-154.
--
Resolution: Won't Fix
The DCI-Cargo sample was removed as part of POLYGENE-180
> Ch
[
https://issues.apache.org/jira/browse/POLYGENE-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated POLYGENE-182:
-
Assignee: Paul Merlin
Fix Version/s: 3.0
Issue Type: Improvement (was: New
[
https://issues.apache.org/jira/browse/POLYGENE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15785746#comment-15785746
]
Paul Merlin commented on POLYGENE-209:
--
> if/once LDAP has been modified, you can use ht
[
https://issues.apache.org/jira/browse/POLYGENE-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin resolved POLYGENE-198.
--
Resolution: Fixed
> Rename Jira project
> ---
>
>
[
https://issues.apache.org/jira/browse/ZEST-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784854#comment-15784854
]
Paul Merlin commented on ZEST-209:
--
See INFRA-13191
> Request new domain name and gitpubsub from IN
[
https://issues.apache.org/jira/browse/ZEST-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-209:
-
Summary: Request new domain name and gitpubsub from INFRA (was: Request
new domain name and svnpubsub from
[
https://issues.apache.org/jira/browse/ZEST-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-209:
-
Description:
ASF now allows websites to be deployed from a dedicated GIT repository in lieu
of SVN.
Now
[
https://issues.apache.org/jira/browse/ZEST-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin resolved ZEST-201.
--
Resolution: Fixed
> Apply name change to code
> -
>
>
[
https://issues.apache.org/jira/browse/ZEST-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin resolved ZEST-205.
--
Resolution: Fixed
> Modify build system for new n
[
https://issues.apache.org/jira/browse/ZEST-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin resolved ZEST-202.
--
Resolution: Fixed
> Change Documentation to new Polygene n
Le 2016-12-13 11:26, Niclas Hedhman a écrit :
Our dear friend and VP Trademarks, Shane Curcuru, has approved[1]
"Apache
Polygene", so the race is on.
\o/
I will do a big stint tonight on the codebase and markdown
documentation.
Cool.
I'll start with CI view and job names.
I'll then
[
https://issues.apache.org/jira/browse/ZEST-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746167#comment-15746167
]
Paul Merlin commented on ZEST-214:
--
Is this issue a split of ZEST-201 ?
> Rename packages in codeb
n Thu, Dec 8, 2016 at 9:47 PM, Paul Merlin <paulmer...@apache.org> wrote:
>
>> Paul Merlin a écrit :
>>> Gang,
>>>
>>> I pushed a commit on the replace-io-by-stream branch that replace usage
>>> of core/io with Java 8 Streams:
>>> https://github
delegate all the nifty details to the
> corresponding services/factories". I prefer consistency.
Ok! +1
> Cheers
> Niclas
>
>
> On Thu, Dec 8, 2016 at 10:35 PM, Paul Merlin <paulmer...@apache.org> wrote:
>
>> Niclas Hedhman a écrit :
>>> Ok,
>>> shoul
Niclas Hedhman a écrit :
> Ok,
> should we then stop having Module extends XyzFactory, and they are obtained
> likewise? Just in case we in future want some other mechanism for the
> XyzFactory types, and not depend on the entire Module.
>
> I think so, as it then becomes more symmetrical and it
Niclas Hedhman a écrit :
> The org.apache.zest.spi.module.ModuleSpi contains access methods to a bunch
> of useful SPI internals, such as EntityStore, TypeLookup and more.
>
> Should we not just kill this class and provide that via @Structure
> injection, since that is what we do with factories
So, yes we should provide users a Gradle plugin to easily build a
Polygene library/extension/application.
About the changes I made to the SDK build. For now I just moved all
build logic to buildSrc so it's more manageable and easy to refactor.
>From a gigantic root build.gradle file we moved to
Niclas Hedhman a écrit :
> What happens is that src/perf and src/vhost-test are "Sources" (blue)
> directories instead of "Tests" (green) directories.
Yeah, I get that too. Not a big issue.
> Dependencies were incorrect, so that dnsjava was not seen.
But, dependencies are correct and I can
Niclas Hedhman a écrit :
> I also don't use the plugin, but open the build.gradle file directly.
>
> I am on Intellij 2016.2.4 UE
Using 2016.3 CE here, but it *should* work with 2016.2.4 UE.
What exactly is happening after import for the vhost and perf tests?
Dependencies are missing and source
To get the project into IDEA, I just import it directly from IDEA and I
don't get any dependency trouble.
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,
Niclas Hedhman a écrit :
> I didn't really notice all the nice things that Paul has done in the build
> system.
:)
> I particularly like the
>
> compile zest.extension( 'entitystore-jdbm' )
>
> Would it be possible to create and distribute a "Polygene plugin", which
> does this for
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.Exception is declared in the
interface,
as a convenience to the user implementing it. Unless really strong
reasons,
I think that should
Hey,
Le 2016-12-05 03:17, Niclas Hedhman a écrit :
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...
Thanks Niclas!
I added some more tasks.
We may still
[
https://issues.apache.org/jira/browse/ZEST-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin reassigned ZEST-213:
Assignee: Paul Merlin
> Apply name change to dist.apache.
[
https://issues.apache.org/jira/browse/ZEST-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin reassigned ZEST-212:
Assignee: Paul Merlin
> Require new groupId for Maven repositories from IN
[
https://issues.apache.org/jira/browse/ZEST-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin reassigned ZEST-205:
Assignee: Paul Merlin
> Modify build system for new n
[
https://issues.apache.org/jira/browse/ZEST-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-200:
-
Summary: Redirect zest.apache.org to polygene.apache.org (was: Rename/move
Subversion repository
Paul Merlin created ZEST-213:
Summary: Apply name change to dist.apache.org
Key: ZEST-213
URL: https://issues.apache.org/jira/browse/ZEST-213
Project: Zest
Issue Type: Sub-task
Paul Merlin created ZEST-210:
Summary: Deploy website with new branding under new domain name
Key: ZEST-210
URL: https://issues.apache.org/jira/browse/ZEST-210
Project: Zest
Issue Type: Sub-task
Paul Merlin created ZEST-208:
Summary: Apply name change to website content
Key: ZEST-208
URL: https://issues.apache.org/jira/browse/ZEST-208
Project: Zest
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/ZEST-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-199:
-
Description:
Two git repositories:
- {{zest-java}} to {{polygene-java}}
- {{zest-sandbox}} to {{polygene
Paul Merlin created ZEST-207:
Summary: Apply name change to CI
Key: ZEST-207
URL: https://issues.apache.org/jira/browse/ZEST-207
Project: Zest
Issue Type: Sub-task
Reporter: Paul
[
https://issues.apache.org/jira/browse/ZEST-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-201:
-
Environment: packages, types, identifiers names, string occurrences ...
Summary: Apply name change
[
https://issues.apache.org/jira/browse/ZEST-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-201:
-
Environment: (was: packages, types, identifiers names, string
occurrences ...)
Description
Paul Merlin created ZEST-206:
Summary: Apply name change to project doap file
Key: ZEST-206
URL: https://issues.apache.org/jira/browse/ZEST-206
Project: Zest
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/ZEST-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-200:
-
Description: If we want to keep {{zest.apache.org}} URLs to redirect to new
{{polygene.apache.org}} we need
[
https://issues.apache.org/jira/browse/ZEST-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-200:
-
Description:
If we want to keep {{zest.apache.org}} URLs to redirect to new
{{polygene.apache.org
[
https://issues.apache.org/jira/browse/ZEST-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-199:
-
Description: Two git repositories: {zest-java} and {zest-sandbox}
> Rename Git reposit
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
and merge into develop soon.
Cheers
/Paul
Paul Merlin a écrit :
> Niclas Hedhman a écrit :
>> Most (all?) Iterable
[x] Apache Polygenic/Polygene
Niclas Hedhman a écrit :
> 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
>
>
>
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 the code
> with Input/Output/Sender/Receiver is significantly more verbose and more
> complex than equivalent code using the Stream
Niclas Hedhman a écrit :
> Ok, so we need to figure out if a name is feasible before tossing it into
> the ring of names.
>
> Starting over, I would like to propose the following two names, that seem
> eligible;
>
> * Apache Aardworx
> (114 hits, but effectively only one Facebook profile)
I
My vote:
> [ ] Apache Accaly
> [X] Apache Akira
> [ ] Apache Zeno
> [ ] None of the above
Sorry to bring potentially bad news.
I've been quickly looking for projects already using one of those names.
Found some:
- https://github.com/Netflix/zeno
- https://github.com/joshuabarnes/zeno
-
[
https://issues.apache.org/jira/browse/ZEST-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681328#comment-15681328
]
Paul Merlin commented on ZEST-120:
--
Added unit test demonstrating actual behaviour
Paul Merlin created ZEST-194:
Summary: Support Java 9 Jigsaw
Key: ZEST-194
URL: https://issues.apache.org/jira/browse/ZEST-194
Project: Zest
Issue Type: Task
Reporter: Paul Merlin
[
https://issues.apache.org/jira/browse/ZEST-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-175:
-
Summary: Support Java 9 without Jigsaw (was: Java 9 Support)
> Support Java 9 without Jig
Paul Merlin created ZEST-193:
Summary: Fail when composite type has interface static method
Key: ZEST-193
URL: https://issues.apache.org/jira/browse/ZEST-193
Project: Zest
Issue Type: Bug
[
https://issues.apache.org/jira/browse/ZEST-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin resolved ZEST-177.
--
Resolution: Fixed
> Rework ElasticSearch Index/Query for ElasticSearc
[
https://issues.apache.org/jira/browse/ZEST-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin reopened ZEST-177:
--
Reopening as Elasticsearch 5.x is out.
Will change the goal of the issue to rework the Elasticsearch index
Throwing pseudo-random names in the air, again:
Animals:
- Apache Zebu
- Apache Puma
Native American tribe names, in echo to Apache:
- Apache Lipan
- Apache Kiowa
- Apache Piro
- Apache Navajo
- Apache Zuni
- Apache Zenu
- Apache Zamuko
Others:
- Apache Akira ("bright/clear" in Japanese)
-
[
https://issues.apache.org/jira/browse/ZEST-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin resolved ZEST-190.
--
Resolution: Fixed
Naming metrics is an application concern, the Metrics API now only require a
single
Paul Merlin created ZEST-191:
Summary: Remove org.json java library
Key: ZEST-191
URL: https://issues.apache.org/jira/browse/ZEST-191
Project: Zest
Issue Type: Task
Reporter: Paul
So, I ran integration tests and everything is stable except indexing-sql.
A lot of the query tests fail.
Something about mapping Identity to String is incomplete.
I've attached the tests result report to ZEST-180 and pointed to the
test setup instruction there.
Paul Merlin a écrit :
> Nic
[
https://issues.apache.org/jira/browse/ZEST-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-180:
-
Attachment: indexing-sql-test-report.zip
Test report for {{indexing-sql
[
https://issues.apache.org/jira/browse/ZEST-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15601726#comment-15601726
]
Paul Merlin commented on ZEST-180:
--
Most of the {{indexing-sql}} tests fail since the change.
It has
[
https://issues.apache.org/jira/browse/ZEST-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-180:
-
Assignee: Niclas Hedhman
> Replace String with Ident
Ahh lambdas :-)
Niclas Hedhman a écrit :
> Gang,
> while working on something else, an interesting pattern was "discovered",
> which I think minimizes the Factoty/Builder stuff quite a bit;
>
> public interface Amount
> {
> Property value();
> Property currency();
> }
>
>
> @Structure
>
Hey,
Niclas Hedhman a écrit :
> Gang,
> last time I brought up JPA, I think the consensus became; too complex to
> bother. But I think the need for "conventional persistence"
> interoperability is still an issue for us, and I think it should be tackled.
>
> Spring (and others?) are promoting a
Makes sense to me
Niclas Hedhman a écrit :
> Hi again,
> While looking into the feasibility of implementing a Repository EntityStore
> I realized that the current SPI seems flawed.
>
> The TYPE of an entity is stored with the entity and not the entity type
> that is being processed by the outside
[
https://issues.apache.org/jira/browse/ZEST-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin closed ZEST-178.
Resolution: Fixed
> Rework EhCache Cache for EhCach
Paul Merlin created ZEST-178:
Summary: Rework EhCache Cache for EhCache 3
Key: ZEST-178
URL: https://issues.apache.org/jira/browse/ZEST-178
Project: Zest
Issue Type: Task
Reporter
[
https://issues.apache.org/jira/browse/ZEST-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin closed ZEST-176.
Resolution: Fixed
> Rework Riak EntityStore for Ria
Le 2016-09-11 18:42, Paul Merlin a écrit :
I just disabled Xvfb on the develop branch builds.
IIRC this was needed for the integration tests of tools/entity-viewer
that we removed some time ago.
Let's see what the CI has to say..
Everything is back to blue except the Java 9 build as expected
[
https://issues.apache.org/jira/browse/ZEST-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483166#comment-15483166
]
Paul Merlin commented on ZEST-176:
--
The Riak EntityStore now works using a Riak 2 client.
Authentication
[
https://issues.apache.org/jira/browse/ZEST-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin closed ZEST-177.
Resolution: Fixed
> Rework ElasticSearch Index/Query for ElasticSearc
I just disabled Xvfb on the develop branch builds.
IIRC this was needed for the integration tests of tools/entity-viewer
that we removed some time ago.
Let's see what the CI has to say..
Le 2016-08-27 19:57, Niclas Hedhman a écrit :
Infra marked it as Duplicate, and I went digging for the
[
https://issues.apache.org/jira/browse/ZEST-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-176:
-
Issue Type: Task (was: Bug)
> Rework Riak EntityStore for Ria
[
https://issues.apache.org/jira/browse/ZEST-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-177:
-
Issue Type: Task (was: Bug)
> Rework ElasticSearch EntityStore for ElasticSearc
Paul Merlin created ZEST-177:
Summary: Rework ElasticSearch EntityStore for ElasticSearch 2
Key: ZEST-177
URL: https://issues.apache.org/jira/browse/ZEST-177
Project: Zest
Issue Type: Bug
[
https://issues.apache.org/jira/browse/ZEST-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-176:
-
Description:
Riak 2 Java Client only supports protocol buffer based communication, no more
HTTP. We
Paul Merlin created ZEST-176:
Summary: Rework Riak EntityStore for Riak 2
Key: ZEST-176
URL: https://issues.apache.org/jira/browse/ZEST-176
Project: Zest
Issue Type: Bug
Reporter
Gang,
Good news, Zest Core just works on Java 9!
Bad news, we can't just use it right now.
Some things in the build are failing with Java 9.
I created ZEST-175 to track the effort.
Code wise, only one test was failing with Java 9 because it uses
internal JDK apis.
It's the test for virtual
Paul Merlin created ZEST-175:
Summary: Java 9 Support
Key: ZEST-175
URL: https://issues.apache.org/jira/browse/ZEST-175
Project: Zest
Issue Type: Task
Reporter: Paul Merlin
Kent Sølvsten wrote:
This is a tough, but interesting question ..
[SNIP]
A few ideas:
(1)
If the persistence engines in the entitystores are XA capable (such as
for JDBC/NEO4J entitystores) it should not be too difficult.
The basic idea would be to inject a DataSource provided by the
Le 2016-09-03 18:27, Prince Arora a écrit :
I am not using scala. This happens when i use gradle to build zest but
working fine ./gradlew
Hey,
This must be caused by your local gradle installation being a different
version than the one we use for Zest.
Using ./gradlew enforce that you use
Le 2016-08-27 14:45, Prince Arora a écrit :
Hi Everyone,
And also we can make it easier if we add an option register these
composites with package name. Like for entity one can give a package
name
where we can scan all the entities and register them for that module.
It is
just a suggestion
[
https://issues.apache.org/jira/browse/ZEST-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370725#comment-15370725
]
Paul Merlin commented on ZEST-149:
--
There's basic support for chunked output in the Asciidoctor extensions
[
https://issues.apache.org/jira/browse/ZEST-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin resolved ZEST-139.
--
Resolution: Won't Fix
The thing is, dangling UoWs can be associated with several threads, not only
[
https://issues.apache.org/jira/browse/ZEST-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360574#comment-15360574
]
Paul Merlin commented on ZEST-122:
--
It turns out that parameter names are not included in bytecode
[
https://issues.apache.org/jira/browse/ZEST-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360573#comment-15360573
]
Paul Merlin commented on ZEST-121:
--
It turns out that parameter names are not included in bytecode
Niclas Hedhman a écrit :
> I am about halfway through a new implementation that only has the the
> "token"-level parsing (I think you call that "push"). It seems to simplify
> the design, although a lot more code for token checks, but I think it is
> the right thing to do.
Yep, push/token VS.
[
https://issues.apache.org/jira/browse/ZEST-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360552#comment-15360552
]
Paul Merlin commented on ZEST-138:
--
org.json ValueSerialization does not support "out of sequence v
[
https://issues.apache.org/jira/browse/ZEST-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360549#comment-15360549
]
Paul Merlin commented on ZEST-149:
--
One issue with asciidoctor is that cross-references in chunked HTML
Niclas Hedhman a écrit :
> Paul,
> What is the difference between the two Map deserialization methods in
> ValueDeserializationAdapter?
>
> One is parsing using tokens, and the other seems to be using JsonNode. One
> is has keyDeserializer in the arguments and the other don't use that. I am
> very
zhuangmz08 a ??crit :
> Hi,
> I've trying out elasticsearch index/query engine. However, I meet this
> exception: MaxBytesLengthExceededException[bytes can be at most 32766 in
> length; got 79504]
> I found an answer in stackoverflow
>
Paul Merlin a écrit :
> Another non-core approach we could use for Event Sourcing is to
> implement StateChangeListeners that generate and store state diffs (with
> e.g. json-patch). The same could be done for Timeseries, possibly with
> property/association value granularity. This
Niclas Hedhman a écrit :
> On Sat, Jul 2, 2016 at 11:18 PM, Paul Merlin <p...@nosphere.org> wrote:
>> On 2016-06-22 14:45 (+0200), Niclas Hedhman wrote:
>>> Entity == "Identity with Value property",
>>> versus DTO == "Value with Identity property
On 2016-06-22 14:45 (+0200), Niclas Hedhman wrote:
> Since I am struggling somewhat with "Entities", which I could view as
> "Identity with Value property", versus "Value with Identity property" (I
> use those as DTOs), I found this very basic, confusing and interesting
take
> on the subject...
>
Hey,
FWIW, community.zones.apache.org is down
Niclas Hedhman a écrit :
> Gang,
> Can someone broadcast a message to committers@, members@ or pmcs@ to
> promote the FOAF file that drives http://community.zones.apache.org/map.html
> ? Or is that too much noise?
Are you referring to the personal
Niice!
I updated the website to link to Pony Mail.
And sent the project a suggestion about moving the subscribe button to a
more prominent place, couldn't find it at first, it's down the list of
posts.
Par Niclas Hedhman a écrit :
> And one can "Subscribe" as well...
>
> On 2016-06-16 19:34
[
https://issues.apache.org/jira/browse/ZEST-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333717#comment-15333717
]
Paul Merlin commented on ZEST-157:
--
I'm not sure about this.
How would we then serialize a {{Map
tests now use a dynamically allowed free port.
This should prevent the CI builds to fail intermitently and send useless
emails to dev@.
Cheers
> On Jun 15, 2016 01:31, "Paul Merlin" <p...@nosphere.org> wrote
>> Gang,
>>
>> We have some flaky tests.
>>
Gang,
We have some flaky tests.
We know about Metrics and Scheduler tests.
Both are time-related.
For Metrics, maybe a simple retry strategy would do. WDYT Niclas?
The Scheduler library situation is not good.
I'm tempted to simply disable the tests until a rewrite occurs.
And the new kid on
Niclas Hedhman a écrit :
> I have spent a lot of time trying to fix
> https://issues.apache.org/jira/browse/ZEST-128, both chasing down the bug
> as well as integrating Zest persistence into Quartz, and both failed.
>
> I don't like having such a critical bug in the code, and knowing about it.
>
1 - 100 of 338 matches
Mail list logo
