[
https://issues.apache.org/jira/browse/ZEST-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman updated ZEST-27:
---
Summary: Integrate RAT into Gradle build. (was: Integrat RAT into Gradle
build.)
> Integrate RAT into G
Niclas Hedhman created ZEST-27:
--
Summary: Integrat RAT into Gradle build.
Key: ZEST-27
URL: https://issues.apache.org/jira/browse/ZEST-27
Project: Zest
Issue Type: Sub-task
Reporter:
[
https://issues.apache.org/jira/browse/ZEST-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582889#comment-14582889
]
Niclas Hedhman commented on ZEST-17:
community/maturity.html has been created, but not ye
Hi,
I added a maturity.html page in "community" of the web site.
What do I need to do to 'enable' that? I guess only Paul knows...
Cheers
--
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java
Right... Create a Jira ticket for it.
On Fri, Jun 12, 2015 at 10:41 AM, Kent Sølvsten
wrote:
> Seems fair to toss these.
>
> Also I think in 3.0 we should consider moving the javascript library
> from rhino to nashorn (which is part of jdk8).
>
> /Kent
>
> Den 12-06-2015 kl. 04:13 skrev Niclas H
Seems fair to toss these.
Also I think in 3.0 we should consider moving the javascript library
from rhino to nashorn (which is part of jdk8).
/Kent
Den 12-06-2015 kl. 04:13 skrev Niclas Hedhman:
> Gang,
>
> I made a quick search for "GNU" in our source tree. Two components are
> refereing to LGP
[
https://issues.apache.org/jira/browse/ZEST-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman closed ZEST-14.
--
Resolution: Fixed
No other license restrictions on dependencies are know at this point.
> Ensure dependenc
[
https://issues.apache.org/jira/browse/ZEST-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582840#comment-14582840
]
Niclas Hedhman commented on ZEST-14:
I have removed lang/beanshell and lang/jruby from 'd
Gang,
I made a quick search for "GNU" in our source tree. Two components are
refereing to LGPL, namely
libraries/beanshell
libraries/lang-jruby
According to http://www.apache.org/legal/resolved.html, we are not allowed
to include LGPL works, nor depend on it.
I see no other choice than pull
[
https://issues.apache.org/jira/browse/ZEST-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582834#comment-14582834
]
Niclas Hedhman commented on ZEST-14:
libraries/lang-beanshell is depending on BeanShell w
[
https://issues.apache.org/jira/browse/ZEST-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582833#comment-14582833
]
Niclas Hedhman commented on ZEST-14:
libraries/lang-jruby is depending on JRuby which is
[
https://issues.apache.org/jira/browse/ZEST-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582827#comment-14582827
]
Niclas Hedhman commented on ZEST-14:
Google AppEngine support has been dropped, primarily
[
https://issues.apache.org/jira/browse/ZEST-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman closed ZEST-9.
-
Resolution: Fixed
Apache Zest shows up on site wide pages like http://www.apache.org
> Update Apache Navigati
[
https://issues.apache.org/jira/browse/ZEST-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582825#comment-14582825
]
Niclas Hedhman commented on ZEST-14:
Neo4j has been dropped, to ensure no GPLv3 entanglem
[
https://issues.apache.org/jira/browse/ZEST-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman updated ZEST-8:
--
Description:
It is not totally clear who needs to submit a Software Grant to ASF. Since Qi4j
was running wi
[
https://issues.apache.org/jira/browse/ZEST-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman closed ZEST-7.
-
Resolution: Fixed
Assignee: Niclas Hedhman
> IP Clearance
>
>
> Key: ZEST-7
[
https://issues.apache.org/jira/browse/ZEST-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman updated ZEST-6:
--
Description:
The following people has been invited as committers, and I need to track the
progress.
[C] Al
[
https://issues.apache.org/jira/browse/ZEST-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman updated ZEST-6:
--
Description:
The following people has been invited as committers, and I need to track the
progress.
[C] Al
Gang,
The following components are failing the Release Specification[1] check of
the build process;
org.qi4j.library.cxf(false) -> beta, none, some
org.qi4j.library.eventsourcing(false) -> beta, none, some
org.qi4j.library.eventsourcing-jdbm(false) -> beta, none, some
org.qi4j.library.eventsourci
[
https://issues.apache.org/jira/browse/ZEST-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman updated ZEST-26:
---
Description:
At the moment, the following compoinents (out of 104) are marked as not
fulfilling the Rele
Niclas Hedhman created ZEST-26:
--
Summary: Review the Release Specification failures
Key: ZEST-26
URL: https://issues.apache.org/jira/browse/ZEST-26
Project: Zest
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/ZEST-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman resolved ZEST-22.
Resolution: Fixed
Has been merged into 'develop'
> Add toValue() and toEntity() methods to the Qi4j AP
[
https://issues.apache.org/jira/browse/ZEST-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman closed ZEST-23.
--
> Strange Serialization exception
> ---
>
> Key: ZEST-23
>
[
https://issues.apache.org/jira/browse/ZEST-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman resolved ZEST-23.
Resolution: Fixed
The change in ValueComposite instantiation solved this issue.
> Strange Serializatio
Niclas Hedhman created ZEST-25:
--
Summary: Project -> Source SDK -> Binary SDK
Key: ZEST-25
URL: https://issues.apache.org/jira/browse/ZEST-25
Project: Zest
Issue Type: Sub-task
Repor
Gang,
as I mentioned else-thread, I would like to push a 2.1 release out the
door.
For this to be achievable, there are quite a lot of small tasks to be made,
and I have started to collect those on
https://issues.apache.org/jira/browse/ZEST-24
Please help add tasks, and if possible assist any w
Niclas Hedhman created ZEST-24:
--
Summary: Release 2.1
Key: ZEST-24
URL: https://issues.apache.org/jira/browse/ZEST-24
Project: Zest
Issue Type: Task
Reporter: Niclas Hedhman
This i
I think the consensus is; Let's not hold up the 2.1 release for GeoSpatial
Query support, as we seem to need more time to flesh out how to integrate
this efficiently, and possibly take into account the Java 8 benefits, that
we get with a 3.0 release.
So, I am trying to move forward with a 2.1 rele
Evtl. here the usage of the spatial extension :
https://github.com/apache/zest-qi4j/blob/ramtej-fb/spatial.queries/core/testsupport/src/main/java/org/qi4j/test/indexing/AbstractSpatialRegressionTest.java
Cheers,
jj
2015-06-11 13:39 GMT+02:00 Niclas Hedhman :
> Ah, I see... This would allow the
Ah, I see... This would allow the "Module" handling to be preserved if
necessary, and makes sense to me.
There is already a QueryBuilderSPI class, but not sure how it works (or is
not in use).
The Spatial Query stuff sits in a separate branch. See
https://github.com/apache/zest-qi4j/tree/ramtej
Actually I was not thinking of QueryBuilderFactory as a decoupled
service, but rather as a SPI like EntityFinder.
Something like
/public interface SolrQueryService extends EntityFinder,
StateChangeListener, QueryBuilderFactory, ServiceComposite//
//public interface SQLIndexingEngineService exte
Hi Kent,
"So a possible design could be to simply break out the querybuilder API's
form core. No more, no less."
Interesting approach.. Right now the Query Specifications are in the Core
and therefore
the spatial stuff is added there as well together with "custom" spatial
types that mimics
the g
Kent,
Nice to hear your refreshing input. Perhaps you have a very strong point.
Lng ago, the Query and Storage was more intertwined (days before
org.qi4j.api.property.Property and we tried to do pojo-style "properties")
than it is today, and perhaps we stopped that separation "too early" and
ev
While I agree that the goal of decoupling the query part from core is a
worthy one, I fail to see what UnitOfWorkFactory has to do with that.
Decoupling the UnitOfWork may or may not make sence, but I think that is
another discussion - which could make sense eg. if you wish to integrate
a Zest app
34 matches
Mail list logo
