Re: Fwd: .sha Release Distribution Policy

Le 16 août 2017 11:00:31 GMT+02:00, Niclas Hedhman a écrit : >Relevant? >-- Forwarded message -- >From: "Henk P. Penning" >Date: Aug 16, 2017 10:56 >Subject: .sha Release Distribution Policy >To: >Cc: > >Hi PMC, > > The Release Distribution Policy[1] changed regarding .sha file

[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&focusedCommentId=16112252#comment-16112252 ] Paul Merlin commented on POLYGENE-204: -- I'm a bit concerned with the

Re: API change suggestion

Niclas Hedhman a écrit : > I have found a small annoying discrepancy; > > interface PropertyDescriptor > interface AssociationDescriptor > > shares a whole bunch of methods, which are in fact the same thing; > > > QualifiedName qualifiedName(); > > Type type(); > > AccessibleObject acce

Re: Logo Contest

Niclas Hedhman a écrit : > I have tried to make myself an opinion... not easy. > > But, I would like to see > > https://issues.apache.org/jira/secure/attachment/12879468/63_3.png > https://issues.apache.org/jira/secure/attachment/12879296/63_3.png > > with the RED color. Possibly a little bit "thic

[jira] [Updated] (POLYGENE-222) Remove Indexing-SQL from 3.0

[ https://issues.apache.org/jira/browse/POLYGENE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin updated POLYGENE-222: - Summary: Remove Indexing-SQL from 3.0 (was: Indexing-SQL is broken) > Remove Indexing-SQL f

[jira] [Resolved] (POLYGENE-222) Indexing-SQL is broken

[ https://issues.apache.org/jira/browse/POLYGENE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin resolved POLYGENE-222. -- Resolution: Won't Fix This was not fixed in 3.0 but the {{indexing-sql}} module was s

[jira] [Reopened] (POLYGENE-222) Indexing-SQL is broken

[ https://issues.apache.org/jira/browse/POLYGENE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin reopened POLYGENE-222: -- > Indexing-SQL is broken > -- > > Key:

[jira] [Resolved] (POLYGENE-143) Command line tool to quickly create skeletal Zest applications

[ https://issues.apache.org/jira/browse/POLYGENE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin resolved POLYGENE-143. -- Resolution: Won't Fix > Command line tool to quickly create skeletal Zest appl

[jira] [Updated] (POLYGENE-143) Command line tool to quickly create skeletal Zest applications

[ https://issues.apache.org/jira/browse/POLYGENE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin updated POLYGENE-143: - Fix Version/s: (was: 3.0.0) 3.1.0 > Command line tool to quickly cre

[jira] [Reopened] (POLYGENE-143) Command line tool to quickly create skeletal Zest applications

[ https://issues.apache.org/jira/browse/POLYGENE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin reopened POLYGENE-143: -- Reopening to change resolution from Fixed to Won't fix to reflect reality. > Command l

[jira] [Reopened] (POLYGENE-158) Yeoman-power Project Creator

[ https://issues.apache.org/jira/browse/POLYGENE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin reopened POLYGENE-158: -- Let's reopen this as it is now effectively targeted at 3.1 > Yeoman-power Project

[jira] [Updated] (POLYGENE-158) Yeoman-power Project Creator

[ https://issues.apache.org/jira/browse/POLYGENE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin updated POLYGENE-158: - Fix Version/s: (was: 3.0.0) 3.1.0 > Yeoman-power Project Crea

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

That's sweet! To make a final decision on the logo I think we should have variations on light and dark backgrounds. The color scheme should work on both. Niclas, could you ask this to Bijal? Cheers Bijal (JIRA) a écrit : > [ > https://issues.apache.org/jira/browse/POLYGENE-204?page=com.a

Re: 3.0.0 release notes and press release

e representative), and maybe with a better >> English than mine 😆 ... >> >> Bye, >> Sandro >> >> >> >> Il 26/Lug/2017 20:36, "Paul Merlin" ha scritto: >> >> Gang, >> >> I'd need a hand to close the 3.0.0 release. >&g

Re: Build failed in Jenkins: Polygene-develop-java8-checkDists #267

See The Cassandra tests timed out waiting for the docker container to be ready. I triggered another build.

3.0.0 release notes and press release

Gang, I'd need a hand to close the 3.0.0 release. I'll handle the release registration on reporter.a.o, updating the website with the 3.0.0 documentation and so on. But I'm running short on time before going afk for two weeks. I'd be very glad if someone would step up to help with: 1/ Releas

Re: [VOTE][RESULT] Release Polygene (Java Edition) version 3.0.0 - Take 4

Paul Merlin a écrit : > I will copy this release to the Apache Polygene dist directory, > and promote the artifacts to the central Maven repository. Done. I'll now wait 24 hours for mirrors to pick up the new bits and update the website. Cheers

[VOTE][RESULT] Release Polygene (Java Edition) version 3.0.0 - Take 4

Hi all, The vote [1] has passed with the following results: +1 (binding): Niclas Hedhman, Sandro Martini, Paul Merlin I will copy this release to the Apache Polygene dist directory, and promote the artifacts to the central Maven repository. Cheers /Paul [1] http://mail-archives.apache.org

Re: Logo Contest

Hi all, tl;dr: I prefer #63 (and #83) Yeah, both #40 and #63 are very close to the finish line. But the vote was somewhat useful by making these two stand out. Personally, I have a preference with the simplicity of #63 (and #83). I don't know how the gradients on #40 would render stitched. So

Re: [VOTE] Release Polygene (Java Edition) version 3.0.0 - Take 4

+ Downloaded source distro + Built from source distro + Validated source distro and convenience artifacts signature + Consumed Maven convenience artifacts from staged repository +1 (binding) Cheers Le 2017-07-21 13:38, Paul Merlin a écrit : Dear community, Once again, I am happy to start

[jira] [Updated] (POLYGENE-149) Migrate documentation to AsciiDoctor

[ https://issues.apache.org/jira/browse/POLYGENE-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin updated POLYGENE-149: - Attachment: core.html I've been doing some experiments with Asciidoctor. It definitely

[VOTE] Release Polygene (Java Edition) version 3.0.0 - Take 4

Dear community, Once again, I am happy to start the VOTE thread for Apache Polygene (Java Edition) 3.0.0! The changelog for this release can be found here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12332998&projectId=12316820 Tag: https://git-wip-us.apache.org/repos/asf?p=po

Re: [VOTE] Release Polygene (Java Edition) version 3.0.0 - Take 3

a new VOTE thread soon. Cheers /Paul Le 2017-07-17 16:48, Paul Merlin a écrit : Dear community, I am happy to start again the VOTE thread for Apache Polygene (Java Edition) 3.0.0! The changelog for this release can be found here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?versio

[jira] [Resolved] (POLYGENE-271) Windows CI job

[ https://issues.apache.org/jira/browse/POLYGENE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin resolved POLYGENE-271. -- Resolution: Fixed And this is DONE! https://builds.apache.org/view/P/view/Polygene/job

[jira] [Commented] (POLYGENE-34) Create Jenkins job for develop SNAPSHOTs publication to Nexus

[ https://issues.apache.org/jira/browse/POLYGENE-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095980#comment-16095980 ] Paul Merlin commented on POLYGENE-34: - Looks like Jenkins nodes now have Gr

[jira] [Updated] (POLYGENE-271) Windows CI job

[ https://issues.apache.org/jira/browse/POLYGENE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin updated POLYGENE-271: - Fix Version/s: (was: 3.1.0) 3.0.0 > Windows CI

[jira] [Assigned] (POLYGENE-271) Windows CI job

[ https://issues.apache.org/jira/browse/POLYGENE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin reassigned POLYGENE-271: Assignee: Paul Merlin > Windows CI job > -- > >

[jira] [Commented] (POLYGENE-270) Build errors with Oracle JDK 8 in Windows

[ https://issues.apache.org/jira/browse/POLYGENE-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095945#comment-16095945 ] Paul Merlin commented on POLYGENE-270: -- These issues are now fixed on {{dev

Re: [VOTE] Release Polygene (Java Edition) version 3.0.0 - Take 3

distribution archived is more appealing to me than having a warning dedicated to a single release somewhere on the website, away from the distribution itself. On Fri, Jul 21, 2017 at 6:43 AM, Paul Merlin wrote: So, the build failures from the source distribution on Windows are

Re: [VOTE] Release Polygene (Java Edition) version 3.0.0 - Take 3

Merlin a écrit : Given the issues discovered on Windows, I take back my +1 vote and: -1 from me! Le 2017-07-17 16:48, Paul Merlin a écrit : Dear community, I am happy to start again the VOTE thread for Apache Polygene (Java Edition) 3.0.0! The changelog for this release can be found here: https

[jira] [Commented] (POLYGENE-270) Build errors with Oracle JDK 8 in Windows

[ https://issues.apache.org/jira/browse/POLYGENE-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095489#comment-16095489 ] Paul Merlin commented on POLYGENE-270: -- I was able to reproduce the failures

[jira] [Commented] (POLYGENE-270) Build errors with Oracle JDK 8 in Windows

[ https://issues.apache.org/jira/browse/POLYGENE-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094993#comment-16094993 ] Paul Merlin commented on POLYGENE-270: -- [~smartini], thanks, looks like it

Re: [VOTE] Release Polygene (Java Edition) version 3.0.0 - Take 3

Given the issues discovered on Windows, I take back my +1 vote and: -1 from me! Le 2017-07-17 16:48, Paul Merlin a écrit : Dear community, I am happy to start again the VOTE thread for Apache Polygene (Java Edition) 3.0.0! The changelog for this release can be found here: https

[jira] [Created] (POLYGENE-271) Windows CI job

Paul Merlin created POLYGENE-271: Summary: Windows CI job Key: POLYGENE-271 URL: https://issues.apache.org/jira/browse/POLYGENE-271 Project: Polygene Issue Type: Wish Reporter

[jira] [Commented] (POLYGENE-270) Build errors with Oracle JDK 8 in Windows

[ https://issues.apache.org/jira/browse/POLYGENE-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094595#comment-16094595 ] Paul Merlin commented on POLYGENE-270: -- [~smartini], could you run `./gradlew

[jira] [Commented] (POLYGENE-270) Build errors with Oracle JDK 8 in Windows

[ https://issues.apache.org/jira/browse/POLYGENE-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094593#comment-16094593 ] Paul Merlin commented on POLYGENE-270: -- Can't reproduce on Mac or Linux.

Re: [VOTE] Release Polygene (Java Edition) version 3.0.0 - Take 3

+ Downloaded source distro + Validated source distro signature (well, it's mine so that was easy) + Built from source distro + Consumed Maven convenience artifacts from staged repository +1 (binding) Cheers Le 2017-07-17 16:48, Paul Merlin a écrit : Dear community, I am happy to start

Re: Logo contest

Le 2017-07-19 10:36, Niclas Hedhman a écrit : My previous experience, SVG is delivered, I asked for font file as well and the designer accommodated additional small changes. I doubt that an .ico file will be a problem. Color; My instructions has been such that it should be suitable to stitch

Re: Logo contest

Le 2017-07-19 07:21, Niclas Hedhman a écrit : Heads-up, I have been running a design contest on 99designs.com and as usual received a lot of good contributions. 46 designs from 16 designers around the world. In a couple of hours, I need to select finalists, and they get the idea is that the

Re: Time flies and Fun begins

Le 2017-07-11 02:14, Niclas Hedhman a écrit : 2. On Monday it is the *3rd Monday* and time for a *hangout* again. Last one feels like yesterday... Expecting everyone showing up It's now Monday July the 17th, 15:00 UTC Anybody available? https://appear.in/polygene

[VOTE] Release Polygene (Java Edition) version 3.0.0 - Take 3

Dear community, I am happy to start again the VOTE thread for Apache Polygene (Java Edition) 3.0.0! The changelog for this release can be found here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12332998&projectId=12316820 Tag: https://git-wip-us.apache.org/repos/asf?p=polyg

Re: [VOTE] Release Polygene (Java Edition) version 3.0.0

happen to have some time right now, you can still look at the release bits and report any issue you find. This will be useful anyway. I'm sorry for the noise. Cheers /Paul Paul Merlin a écrit : > Dear community, > > I am happy to start the VOTE thread for Apache Polygene

[VOTE] Release Polygene (Java Edition) version 3.0.0

Dear community, I am happy to start the VOTE thread for Apache Polygene (Java Edition) 3.0.0! The changelog for this release can be found here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12332998&projectId=12316820 Tag: https://git-wip-us.apache.org/repos/asf?p=polygene-ja

Re: Time flies and Fun begins

14, 2017 at 12:13 AM, Paul Merlin >wrote: > >> Niclas Hedhman a écrit : >> > 1. Most of the commits that I pushed is actually private branches >pushed >> by >> > accident. Check GitHub network graph for what is modified in >'develop', >> &

Re: Thoughts on Release 3.0

Le 2017-07-14 02:19, Niclas Hedhman a écrit : 3.1 - a suite of Gradle plugins: polygene-library, polygene-extension, polygene-application .. to make it damn easy to setup the build of Polygene apps Ok, that would simply fold into the generator? Or is it something to be published separately?

Re: Thoughts on Release 3.0

Hey folks, Niclas Hedhman a écrit : > 1. Polygene generator doesn't produce functioning projects. It is quite > close, but there are issues in security and perhaps in Configuration > handling. I get indexer complaining on restarts that Configuration type is > not visible and other odd things. Part

Re: Time flies and Fun begins

Niclas Hedhman a écrit : > 1. Most of the commits that I pushed is actually private branches pushed by > accident. Check GitHub network graph for what is modified in 'develop', > primarily SQL Indexing fix and Generator stuff. The git history was a bit weird, with commits of yours that were intend

Re: [2/3] polygene-java git commit: Fixed bug that caused some polygene generator build failures.. Is those disabled in Jenkins, or why didn't it show up in the CI?

nic...@apache.org a écrit : > Fixed bug that caused some polygene generator build failures.. Is those > disabled in Jenkins, or why didn't it show up in the CI? Yes they are disabled on CI for now as they just fail to run. Didn't have time to investigate. See: https://github.com/apache/polygene-

[jira] [Created] (POLYGENE-267) Model extensions capabilities in tooling

Paul Merlin created POLYGENE-267: Summary: Model extensions capabilities in tooling Key: POLYGENE-267 URL: https://issues.apache.org/jira/browse/POLYGENE-267 Project: Polygene Issue Type

Re: Hangout on Monday 19 June

Thanks a ton for the summary Niclas! Niclas Hedhman a écrit : > Gang, > Should have done this earlier, but been quite busy. > > First of all, remarkably the time was almost right. Tibor pointed out that > CET is the non-DST timezone name. I should probably used Europe/Berlin or > Europe/Paris. Fr

Re: UnitOfWork closed inconsistently

Niclas Hedhman a écrit : > Finally, the inconsistency was to the fact that the Entity properties were > accessible after the UnitOfWork is closed. And to restore "consistency" I > suggest that this would result in the same Exception as when accessing the > Associations, to force people to a "do the

[jira] [Commented] (POLYGENE-253) Default interface methods support broken on JDK 9b139

[ https://issues.apache.org/jira/browse/POLYGENE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072711#comment-16072711 ] Paul Merlin commented on POLYGENE-253: -- Right, CI history is not preserved.

[jira] [Commented] (POLYGENE-266) Investigate if JDK internal ASM can be used instead of external dependency

[ https://issues.apache.org/jira/browse/POLYGENE-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072704#comment-16072704 ] Paul Merlin commented on POLYGENE-266: -- Before considering doing this we

Re: EntityReference in ValueComposite 'side effect'

Niclas Hedhman a écrit : > Gang, > > the new EntityStoreTestSuite is once again finding "interesting" behavior > that is not documented. > > If an Value composite has an Association to an Entity, but that entity is > not visible to the Value, deserialization will fail. > > It is quite straight forw

[jira] [Updated] (POLYGENE-255) The project generator produces broken projects

[ https://issues.apache.org/jira/browse/POLYGENE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin updated POLYGENE-255: - Attachment: jmx-breakage-1.png jmx-breakage-2.png [~niclas], I don't hav

Re: Releasing 3.0 ?

12, 2017 at 10:37 PM, Paul Merlin wrote: > >> Gang, >> >> The 3.0 release is still blocked on >> https://issues.apache.org/jira/browse/POLYGENE-255 >> >> Basically, when enabling the `jmx` feature, the generated projects can't >> compile. Thi

Re: Releasing 3.0 ?

Gang, The 3.0 release is still blocked on https://issues.apache.org/jira/browse/POLYGENE-255 Basically, when enabling the `jmx` feature, the generated projects can't compile. This needs to be fixed before running the second 3.0 release candidate. I've been busy this week, I'll be mostly off in t

[jira] [Commented] (POLYGENE-255) The project generator produces broken projects

[ https://issues.apache.org/jira/browse/POLYGENE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046624#comment-16046624 ] Paul Merlin commented on POLYGENE-255: -- I ran the whole generator test suite

Re: JOOQ EntityStore

Hi Niclas, Yep, looks good. > Interestingly enough, the current design (without history) preserves state > of sub-types, which I think is no longer supported in other ES > implementations. This is just a side-effect of how the storage is > structured. IIRC, all JSONMapEntityStore support this,

Re: yeoman-work back to develop

So, :tools:generator:npmTestAll eventually finished. BUILD FAILED Total time: 12 hrs 39 mins 22.934 secs 6530 tests 1115 failures The JMX library assemblies do not compile! 252 timeouts Some tests are rather fast, <5sec, a few are are rather long, >30sec. Offenders use Cassandra ES, MongoDB ES

Re: ServiceActivation

Niclas Hedhman a écrit : > So there is an initial question to be answered first; > > Is 3.0 really releasable? I could argue that "instantiateOnStartup()" might > have to go. It is too fragile, and I think we can provide a "service > worker" and "deferred" solution for services that are suitable fo

Stanislav Muhametsin invited to join the PMC

Stanislav, The PMC is pleased to invite you to the Project Management Committee of the Apache Polygene project. The current list of PMC Members are; Alex Karasulu James Carman Jeff Genender Marcel Offermanns Chris Mattmann Niclas Hedhman Paul Merlin Roman

Re: yeoman-work back to develop

inary serialization. I would remove the choice of serialization from the generator for 3.0 and assemble default JSON serialization where appropriate instead. Any objections ? /Paul Le 2017-06-04 11:09, Paul Merlin a écrit : Le 2017-06-04 02:54, Niclas Hedhman a écrit : As for Docker; Don&#

Re: yeoman-work back to develop

ion. I would remove the choice of serialization from the generator for 3.0 and assemble default JSON serialization where appropriate instead. Any objections ? /Paul Le 2017-06-04 11:09, Paul Merlin a écrit : Le 2017-06-04 02:54, Niclas Hedhman a écrit : As for Docker; Don't forge

Re: Configuration structure

anced deployments. All in all I'd be in favor of not adding any magic to 3.0 and think about a more holistic solution for 3.1. WDYT? Cheers /Paul On Sun, Jun 4, 2017 at 8:37 PM, Paul Merlin wrote: Le 2017-06-04 13:23, Niclas Hedhman a écrit : initialValueProvider should

Re: Configuration structure

Le 2017-06-04 13:23, Niclas Hedhman a écrit : initialValueProvider should be marked "incomplete" or something. I'd rather simply remove it from the api for now. I'll do that if no one yell :) For the rest, not so sure I like it. I think I would prefer something more composite-like, but not

Re: Configuration structure

Maybe a silly idea, don't know, totally different, but ... interface MyConfig { @UseDefaults( value = "user.home", source = DefaultsSource.SYSTEM_PROPERTIES ) Property homeDirectoryPath(); @UseDefaults( value = "SOME_PORT", source = DefaultsSource.ENVIRONMENT ) Property thePortWeWa

Re: Configuration structure

Le 2017-06-04 12:21, Niclas Hedhman a écrit : Well, I implemented the simple/hacky way now. public interface MyConfig { Property osName(); Property home(); Property path(); } will now read "os.name" from System Properties and $HOME and $PATH/%PATH% of Environment variables. Ad

Re: yeoman-work back to develop

Le 2017-06-04 02:54, Niclas Hedhman a écrit : As for Docker; Don't forget that this is code generation and it is EXPECTED that people tailor it to their needs. I chose ":latest" so that we don't have to constantly maintain the version as those dependencies are likely to upgrade faster than we

Re: yeoman-work back to develop

Hey, I took a quick look at the project generator integration tests. First thing, I just tried on a computer where I don't have docker installed and the tests present in generated projects simply fail with a not so obvious error. We should not require docker for a successful build of generated p

Re: Adding stack trace element ??

I like the idea. I tried to put the trace into IntelliJ stacktrace analyser and it didn't choke. But we should assert that StackTraceElement[] and Java 9 StackWalker don't choke either. Another thing is that I'll go the other way around when describing where the error did happen. From the layer to

Re: Dependencies

Hey Niclas, Niclas Hedhman a écrit : > Paul, > I think you are probably the only one who can answers this. This surfaces > in the Yeoman generator with BootstrapTest, and most tests fail because of > this (maybe other things). > > In a generated project, I have a dependency on, say entitystore-lev

[jira] [Assigned] (POLYGENE-255) The project generator produces broken projects

[ https://issues.apache.org/jira/browse/POLYGENE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin reassigned POLYGENE-255: Assignee: Niclas Hedhman (was: Paul Merlin) > The project generator produces bro

[jira] [Assigned] (POLYGENE-172) MongoDB configuration is not friendly.

[ https://issues.apache.org/jira/browse/POLYGENE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin reassigned POLYGENE-172: Assignee: Niclas Hedhman (was: Paul Merlin) > MongoDB configuration is not frien

[jira] [Resolved] (POLYGENE-257) Custom IdentityGenerator or Serialization hidden by default assemblers

[ https://issues.apache.org/jira/browse/POLYGENE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin resolved POLYGENE-257. -- Resolution: Fixed {code} moduleAssembly.defaultServices() .visibleIn

[jira] [Assigned] (POLYGENE-172) MongoDB configuration is not friendly.

[ https://issues.apache.org/jira/browse/POLYGENE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin reassigned POLYGENE-172: Assignee: Paul Merlin (was: Niclas Hedhman) > MongoDB configuration is not frien

[jira] [Assigned] (POLYGENE-255) The project generator produces broken projects

[ https://issues.apache.org/jira/browse/POLYGENE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin reassigned POLYGENE-255: Assignee: Paul Merlin (was: Niclas Hedhman) > The project generator produces bro

Re: Default assemblers (Re: Issue with null association)

Hi Tibor, Tibor Mlynarik a écrit : > Paul, > > I did workaround with commenting out > //ModuleAssemblyImpl:127 > //defaultAssemblers.put( IdentityGenerator.class, new > DefaultIdentityGeneratorAssembler() ); > > that one line change helped me, so I am continuing with porting to 3.0 ( > currently

Re: npmTests

Niclas Hedhman a écrit : > I think you are saying; if Polygene hasn't been built from source, the > generated project will not have the Docker image available to use. Right?? Yep! That and that on the yeoman-work branch, building from source don't work anymore with an empty docker service as there

Re: npmTests

Niclas Hedhman a écrit : > The memcache example test works here, just as everything else does. > > niclas@devdesk:~/dev/polygene/java$ git branch > New_LookFeel > POLYGENE-191 > develop > entitystore_sqlng > master > serialization-3.0 > support/2.1 > * yeoman-work > niclas@devdesk:~/d

Re: npmTests

I can reproduce locally: ./gradlew :tools:generator:check But, I also get different errors depending on the generated project... I tried to look at the changes around the docker machinery but see my other email about promoting docker testing machinery to core.testsupport. And direct docker bas

Re: polygene-java git commit: :tools:generator Add empty test to generated rest-api application

Niclas Hedhman a écrit : > To support this, we really need the internal Docker support to become > official. So, I am removing the "internals" as it only contains the > DockerRule stuff, and that I am moving to core/testsupport. > > With that in testsupport, I am adding testcases to Yeoman generato

[jira] [Commented] (POLYGENE-257) Custom IdentityGenerator or Serialization hidden by default assemblers

[ https://issues.apache.org/jira/browse/POLYGENE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026368#comment-16026368 ] Paul Merlin commented on POLYGENE-257: -- Yeah, the added magic layer is not a

Re: Removing cruft

Niclas Hedhman a écrit : > * The ValueTypeFactory is different than the others, in that it is used > prior to model activation and can not really be a service straight up as it > is now. Can't it be an imported service then?

[jira] [Created] (POLYGENE-257) Custom IdentityGenerator or Serialization hidden by default assemblers

Paul Merlin created POLYGENE-257: Summary: Custom IdentityGenerator or Serialization hidden by default assemblers Key: POLYGENE-257 URL: https://issues.apache.org/jira/browse/POLYGENE-257 Project

Re: Default assemblers (Re: Issue with null association)

Addendum: - s/polygene-runtime/polygene-support - Tibor, you could try the branch with your application, I hope it'll fix your IdentityGenerator issue Le 2017-05-22 17:38, Paul Merlin a écrit : Gang, Le 2017-05-21 19:45, Tibor Mlynarik a écrit : I have another one. Is it ok to report

Default assemblers (Re: Issue with null association)

Gang, Le 2017-05-21 19:45, Tibor Mlynarik a écrit : I have another one. Is it ok to report here or better create JIRA issue ? What Niclas said, JIRAs are better. Keep them coming Tibor! My custom IdentityGenerator ( inherited from layer hierarchy ) is probably overwritten with default one.

Re: Issue with null association

Le 2017-05-21 17:45, Paul Merlin a écrit : Hi Tibor, Le 2017-05-21 17:11, Tibor Mlynarik a écrit : Hi , I am trying to port my 2.0 based application to latest 3.0 develop branch. It seems that Association.set() is not allowing null. ( quick look at AssociationInstance.set() shows possible

[jira] [Created] (POLYGENE-256) Cassandra EntityStore do not clear Many/Named Associations

Paul Merlin created POLYGENE-256: Summary: Cassandra EntityStore do not clear Many/Named Associations Key: POLYGENE-256 URL: https://issues.apache.org/jira/browse/POLYGENE-256 Project: Polygene

Re: Issue with null association

Hi Tibor, Le 2017-05-21 17:11, Tibor Mlynarik a écrit : Hi , I am trying to port my 2.0 based application to latest 3.0 develop branch. It seems that Association.set() is not allowing null. ( quick look at AssociationInstance.set() shows possible NPE at line 67 ) Thank you! Looks like this

Re: polygene-java git commit: :tools:generator Add empty test to generated rest-api application

FYI Niclas Le 2017-05-21 17:29, paulmer...@apache.org a écrit : Repository: polygene-java Updated Branches: refs/heads/develop 779cffbc6 -> 84a794d29 :tools:generator Add empty test to generated rest-api application See tools/generator-polygene/app/templates/RestAPIApplication/bootstrap-tes

Re: library/http

Also, HTTPS should be opt-in. If I intend to deploy my app in some managed environment where TLS is handled by a proxy I may not want to expose an HTTPS service. With my 3.0 release manager hat on: - HTTPS out of the box in generated projects could go into 3.1 if that's too much hassle for no

Re: library/http

Le 2017-05-21 14:59, Niclas Hedhman a écrit : I am trying to generate certs and stuff so that a dev environment is operational out of the box. I'm getting curious :) At what time do you generate the server certificate? So, the generated projects will include a generated server certificate. Lo

[jira] [Created] (POLYGENE-255) The project generator produces broken projects

Paul Merlin created POLYGENE-255: Summary: The project generator produces broken projects Key: POLYGENE-255 URL: https://issues.apache.org/jira/browse/POLYGENE-255 Project: Polygene Issue

Re: library/http

Le 2017-05-21 14:59, Niclas Hedhman a écrit : Thanks, I am trying to generate certs and stuff so that a dev environment is operational out of the box. Great Broken; The model isn't instantiated until a request is issued to the Restlet API, so it fails assembly in various ways, I think. No ide

[jira] [Resolved] (POLYGENE-254) Source distribution contains Gradle wrapper files including JARs

[ https://issues.apache.org/jira/browse/POLYGENE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin resolved POLYGENE-254. -- Resolution: Fixed All Gradle wrapper files have been removed from the source distribution

Re: library/http

Le 2017-05-21 08:02, Niclas Hedhman a écrit : Hi, I am changing the library/restlet to use the internal Jetty server instead of war deployment. Mainly to better tailor for "spring boot"-style of generation in Polygene Generator. Cool Now, the library/http looks on paper to support HTTPS, b

[jira] [Assigned] (POLYGENE-254) Source distribution contains Gradle wrapper files including JARs

[ https://issues.apache.org/jira/browse/POLYGENE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin reassigned POLYGENE-254: Assignee: Paul Merlin > Source distribution contains Gradle wrapper files including J

[jira] [Created] (POLYGENE-254) Source distribution contains Gradle wrapper files including JARs

Paul Merlin created POLYGENE-254: Summary: Source distribution contains Gradle wrapper files including JARs Key: POLYGENE-254 URL: https://issues.apache.org/jira/browse/POLYGENE-254 Project: Polygene

Re: [VOTE] [CANCEL] Release Polygene (Java Edition) version 3.0.0

Niclas Hedhman a écrit : > Also, I get a second Gradle download during the build, although 3.5 has > been downloaded before. It may be because one is using the -bin Gradle dist where the other one is using the -all Gradle dist. > :tools:generator-polygene:setsCurrentVersionToPackageJson > :tools:

  1   2   3   >