[jira] [Comment Edited] (TOMEE-2559) TomEE dependency matrix

["Willes Reis (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TOMEE-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147098#comment-17147098 ] 

Willes Reis edited comment on TOMEE-2559 at 6/27/20, 8:21 PM:
--------------------------------------------------------------

To keep tracked, I did search about tools that map dependencies as from pom files and I decided to try [pomParser|https://github.com/roclas/pomParser].

I think is not so good for tomee project because this tool analyses only:
 * direct pom tree *project:dependencies:dependency* tags;
 * literal values in *groupId* and *artifactId*.

As plenty of tomee's pom files are structured with different pom tree tags as:
 * *project:profiles:profile:dependencies*;
 * *project:dependencyManagement:dependencies*.

so the pomParser do not map all of correct dependencies.

Another point, there are some properties as *${project.groupId}* that do not parses to corresponding values in groupId and artifactId.

I am going to keep an attachment [^dependencies.html] that is the output of pomParser to anyone that wants to see.


was (Author: wsr):
To keep tracked, I did search about tools that map dependencies as from pom files and I decided to try [pomParser|https://github.com/roclas/pomParser].

I think is not so good for tomee project because this tool analyses only:
 * direct pom tree *project:dependencies:dependency* tags;
 * literal values in *groupId* and *artifactId*.

As plenty of tomee's pom files are structured with different pom tree tags as:
 * *project:profiles:profile:dependencies*;
 * *project:dependencyManagement:dependencies*.

so the pomParser do not map all of correct dependencies.

Another point, there are some properties as *${project.groupId}* that do not parses to corresponding values in groupId and artifactId.

I am going to keep an attachment (dependencies.html) that is the output of pomParser to anyone that wants to see.

> TomEE dependency matrix
> -----------------------
>
>                 Key: TOMEE-2559
>                 URL: https://issues.apache.org/jira/browse/TOMEE-2559
>             Project: TomEE
>          Issue Type: Documentation
>            Reporter: Cesar Hernandez
>            Assignee: Willes Reis
>            Priority: Major
>              Labels: documentation
>         Attachments: dependencies.html
>
>
> 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
(v8.3.4#803005)