Build failed in Jenkins: Polygene(JavaEdition)-develop-java8-checkDists #109

See Changes: [paulmerlin] build: unit test ModuleReleaseSpec [paulmerlin] build: fix xslt task inputs declaration -- [...truncated 6202 lines...]

Build failed in Jenkins: Polygene(JavaEdition)-develop-java8-check #242

See Changes: [niclas] Adding a METHOD_NAMED convenience function. [niclas] Improved the Constraints handling (better messages and removed static [niclas] ZEST-195 ; Replace all "Zest" with "Polygene"

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

[ 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 name. > - > >

[jira] [Resolved] (ZEST-202) Change Documentation to new Polygene name

[ 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 name > -

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

[ 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 > - > > Key:

Jenkins build is back to normal : Polygene(JavaEdition)-develop-java9-check #46

See

Apache Polygene - Future Directions

Hi Gang, now after the renaming activity is over (that is surely still ongoing, but at least we have a final name and a path), I think it is time to brainstorm about some future directions of Apache Polygene. >From my perspective Polygene is a DCI and COP oriented programming approach for Java