[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-386) Review: Devs to review Maven Tools content spec

[Fred Bricon (JIRA)]

    [ https://issues.jboss.org/browse/TOOLSDOC-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804251#comment-12804251 ] 

Fred Bricon commented on TOOLSDOC-386:
--------------------------------------

{quote}...for building and managing Java-based projects;{quote}
No, maven is not restricted to building java projects. It can actually build any kind of project (flex, groovy, docs ...)

{quote}• What Maven support is already in eclipse? m2e, m2e-wtp{quote}
m2e provides Java support, Dependency management, a POM editor and most importantly is a platform for other eclipse plugins to provide support for  different maven plugins and technologies (android, groovy, ...).
m2e-wtp aims at providing a bridge between m2e and Eclipse WTP, in other words, provide easy configuration for JavaEE projects.

{quote}
• Convert Java classpaths to Maven dependencies when convert to Maven project
{quote}
actually, it converts java dependencies (classpath entries for java projects, component references for EARs) to Maven dependencies

{quote}• Ease of specifying Maven profiles on per project basis
{quote}
It's all about profile selection, through a new UI over the existing m2e functionality. We don't add anything to specify/create new profiles.

{quote}
• Ease of specifying Maven profiles on per project basis
• Maven integration for JBoss-specific technologies (Hibernate, Portlet, ...)
{quote}
• Maven integration for JBoss-specific (Hibernate, CDI, Portlet, Seam, JBoss SAR) or 3rd party technologies (GWT)

{quote}• JBoss Maven repository identification
{quote}
• Easy Maven repository management in settings.xml, using a specific UI in the preferences
Also can define new maven repositories to be used for dependency identification or source lookup

Other features (can be filed under Enhanced Maven integration for Java technologies) :
- quick fixes for missing JBoss (project or product) dependencies
- provides support for Endorsed Libraries (libraries that must be declared before other JDK or maven jars. http://docs.jboss.org/tools/whatsnew/maven/maven-news-3.3.0.CR1.html) 
- add support for annotation processing (disabled by default http://docs.jboss.org/tools/whatsnew/maven/maven-news-3.3.0.Beta3.html#itemname1)

Although not related to maven directly (but using m2e's infrastructure) and applicable to any non-maven java projects :
- source lookup for any jar in a project classpath
- source lookup for any jar while debugging, at runtime



{quote}
• Use: Add Maven (M2) capabilities to a Java project, so makes pom.xml and sets up file system structure
for designated output type (JAR, WAR, ...)
{quote}
I wouldn't promote that approach, as it's largely been superceded (but not completely) by m2e's "Convert to Maven" menu. It might still be relevant for Seam projects though. Other use case where the M2 Facet is still relevant is when using maven-based Library providers (JSF, Hibernate).But I personally don't find this approach reliable as it references quickly outdated libraries (hardcoded in JBDS).

Another feature you could mention (though not directly a Maven tool): the ability to materialize _any_ library, as described in http://docs.jboss.org/tools/whatsnew/core/core-news-3.3.0.M4.html, useful if you want to drop maven (or gradle or ivy...)


As for the rest, I believe you're gonna add more details based on existing N&N. Ping me if you need more explanations as you progress.
                
> Review: Devs to review Maven Tools content spec
> -----------------------------------------------
>
>                 Key: TOOLSDOC-386
>                 URL: https://issues.jboss.org/browse/TOOLSDOC-386
>             Project: Documentation for JBoss Tools and Developer Studio
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: User Guide - Maven Tools
>    Affects Versions: 4.1.0
>            Reporter: Michelle Murray
>            Assignee: Fred Bricon
>             Fix For: 4.2.0
>
>         Attachments: MavenTools_contentspec.pdf
>
>
> Please review the content spec of the Maven Tools chapter from a technical viewpoint:
> 1) Is the info about features correct?
> 2) Are any features missing?
> The content spec will be used to write the Maven Tools chapter in the JBDS User Guide. It is important that any issues are resolved before writing starts.
> For ease of tracking by docs, please give feedback as comments in this JIRA. Estimated page and graphics counts will be added by docs later.
> The content spec is available here as a pdf. Alternatively, the content spec is also available at:
> https://mojo.redhat.com/docs/DOC-19224

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira