[
https://issues.apache.org/jira/browse/TOMEE-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willes Reis updated TOMEE-2559:
-------------------------------
Labels: documentation (was: docuentation)
> TomEE dependency matrix
> -----------------------
>
> Key: TOMEE-2559
> URL: https://issues.apache.org/jira/browse/TOMEE-2559
> Project: TomEE
> Issue Type: Documentation
> Reporter: Cesar Hernandez
> Priority: Major
> Labels: documentation
>
> The current project Dev oriented documentation
> [http://tomee.apache.org/community/sources.html] can be improved with an
> automated procedure that generates the following:
>
> # We could have in TomEE site, further information about
> the target for each project version", I meant tomee versions between 7.0,
> 7.1 and 8.0. Would be the same page
> http://tomee.apache.org/comparison.html showing
> implementations by version. Eg. tomee-7.0 (JSP v1, JSF v2, ...) / tomee-7.1
> (JSP v2, JSF v3, ...) / tomee-8.0 (JSP v3, JSF v4, ...).
> # Current strategy for control version (semantic version) of the
> maven project, changing of major/minor version when is a fix or
> enhancements and who does it (responsibility).
> # While working on an issue with MP rest client on current TomEE master, I
> invested a couple of hours understanding how the relationship
> betweenMicroProfile boom, rest-client jar and cxf versions worked all
> together.From Tomee pom file [1] I was able to quickly identify how current
> masteris structured, but then the journey to check releases and
> correlationsstarted and I was navigating around CXF release notes, JIRA, MP
> githubrelease pages, rest-client releases etc.I think it would be nice to
> have a dev-oriented documentation that can saveus time in the future.
> [1][https://github.com/apache/tomee/blob/master/pom.xml#L200-L218]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
