Georg Kallidis
2017-09-30 20:25:50 UTC
Hi all,
- Fulcrum components are now in GitHub available (readonly)!
https://github.com/apache/turbine-fulcrum/tree/trunk
- Turbine Core might be mirrored soon into
https://github.com/apache/turbine-core/tree/trunk, but has
https://issues.apache.org/jira/browse/INFRA-15106 currently set to unresolved (GitHub Turbine Core trunk is truncated after the directory move from jakarta back in 2007). We may have to open another issue to get this done. On the other side ..
- if we decide to add a "next generation" Turbine with Java8 and servlet 3.x support, but still want to keep Turbine 4.x, we might do this by introducing a new branch as writable GitHub-Repo, while keeping the current Turbine Core trunk in svn (and do without the mirror). This might be convenient (for some developers). Of course, this could be discussed later, after the release of Turbine 4.0.
Best regards, Georg
BKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCBÈ [ÝXØÜXKK[XZ[]][ÝXØÜXP \[K\XÚKÜÃBÜY][Û[ÛÛ[X[ ËK[X
- Fulcrum components are now in GitHub available (readonly)!
https://github.com/apache/turbine-fulcrum/tree/trunk
- Turbine Core might be mirrored soon into
https://github.com/apache/turbine-core/tree/trunk, but has
https://issues.apache.org/jira/browse/INFRA-15106 currently set to unresolved (GitHub Turbine Core trunk is truncated after the directory move from jakarta back in 2007). We may have to open another issue to get this done. On the other side ..
- if we decide to add a "next generation" Turbine with Java8 and servlet 3.x support, but still want to keep Turbine 4.x, we might do this by introducing a new branch as writable GitHub-Repo, while keeping the current Turbine Core trunk in svn (and do without the mirror). This might be convenient (for some developers). Of course, this could be discussed later, after the release of Turbine 4.0.
Best regards, Georg
BKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCBÈ [ÝXØÜXKK[XZ[]][ÝXØÜXP \[K\XÚKÜÃBÜY][Û[ÛÛ[X[ ËK[X