galder zamarreño <> in Escalante

ESC-33 Play module missing dependency making standard Lift apps crash

Update to 0.4.0-SNAPSHOT

    • -2
    • +2
    • -2
    • +2
    • -2
    • +2
Release script adjustments

* Make sure pom.xml files in target/ folders are not included

Release script adjustments

* Adjust location of Version.scala file.

ESC-29 Fix Scala resolution for non-main Scala versions

Enable Play/Lift integration build output to go to console

ESC-28 Add Play module to distribution

    • -1
    • +0
ESC-28 Download and unzip Play distro for testing

ESC-25 Updated to Lift 2.5-RC4

ESC-17 Upgrade to Play applications to version 2.1.1

ESC-18 Update to Scala 2.10.1

ESC-17 Add support for Play 2 applications to persist to database

* This is not using application data sources yet, more work needed.

* Try to use more for comprehensions to cleaner code base and avoid

touching Option methods directly, and code in a more monadic style.

* Since Play! applications remove logging handlers when starting up

(great!), add some logic to cache current log handlers when starting

Play applications and restore them right after.

* Switch to Dev mode for applications so that multiple applications

can be deployed one after the one and avoid previous application

configuration to be cached.

  1. … 32 more files in changeset.
ESC-17 Add basic Play integration layer

* Basic HelloWorld application works.

* To have Play logging, it needs -Dlogger.file= passed as system prop.

* A lot of TODOs, including on-the-fly compilation, custom Netty server

to avoid logging issue and enable plugging in AS provided Executors...

  1. … 53 more files in changeset.
ESC-18 Upgrade to Scala 2.10.0

* Sorted out VerifyError which was the result of duplicate

commons-codec jars with different versions in deployment war.

* Switched to String interpolation for the majority of cases.

* Force invoker plugin to avoid running tests if the user passes

a system property to skip tests when invoking its parent.

* Remove any references to escalante-build project which was

removed in an earlier commit.

  1. … 4 more files in changeset.
ESC-13 Remove build/ project and unzip base app server from code

* Use same code to unzip base app server when building distribution.

* Adjust arquillian listeners to that they unzip the base server

before test set up if necessary.

    • -0
    • +7
    • -1
    • +8
ESC-13 Provide TRACE logging for io.escalante in testing

ESC-13 Add extension and subsystem XML fragments programmatically

* Makes it easier to deal with changes to underlying AS standalone


* Update root README file with new structure.

    • -0
    • +6
    • -0
    • +6
ESC-13 Split assembly to separate project to reduce dist dependencies

* Update Version information.

* Update roadmap.

ESC-13 Use embedded container for testing

* Define pluginManagement section to centralize configuration of

Maven plugins.

    • -22
    • +6
    • -105
    • +11
ESC-13 Add Artifact extension which deals with artifact resolution

* It also deals with artifact attachment to deployments (i.e. Lift jars)

* This new extension will be reused by other extensions.

* Restructured entire Arquillian testsuite to be stored in each module

and be executed via the Maven Invoker plugin. This makes it easier for

the future when you wanna test the same code with different Scala


    • -127
    • +0
  1. … 167 more files in changeset.
ESC-1 Fix release script to log correct version on startup

ESC-10 Support Lift JPA applications

* Adds support for Lift applications deploying JPA EntityManagers.

* Requires EntityManagerFactory to be bound to JNDI.

* Future support for CDI-style injection of persistence context

and units is planned.

    • -0
    • +1
    • -105
    • +119
  1. … 34 more files in changeset.
ESC-2 Support any Lift version and optional modules

* By resolving any Lift version, we make an attempt to use a Lift

version even if it's unknown to the Lift subsystem.

* Optional modules can now be defined per deployment so that

other modules such as mapper, record...etc can be resolved and

added to deployment classpath.

    • -1
    • +20
    • -0
    • +64
  1. … 8 more files in changeset.
Fix core test classes that were located in wrong package

ESC-8 Switch to escalante.yml for metadata provision

* lift.xml was too limited since it only covered the lift use case.

* With escalante.yml we can now add more libraries more easily.

    • -0
    • +31
    • -0
    • +63
    • -0
    • +90
ESC-6 Upgrade base application server to a version supporting embedded

ESC-5 Fix thirdparty modules repo absolute path resolution

* Path allows now for expressions which is crucial for running in

cloudy environments such as OpenShift.

* Added unit tests to verify that expression resolution happens.

Update to 0.2.0-SNAPSHOT

    • -1
    • +1
ESC-3 Remove duplicate jars for Lift module

To solve the issue, it adds filter options for Maven artifact classes.

    • -1
    • +1
Force source jars to be generated by Maven

    • -0
    • +1
    • -0
    • +1