[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-1066) Exclude maven-jdocbook-plugin from Eclipse m2

Hardy Ferentschik (JIRA) noreply at atlassian.com
Mon Mar 19 04:49:48 EDT 2012


    [ https://hibernate.onjira.com/browse/HSEARCH-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46009#comment-46009 ] 

Hardy Ferentschik commented on HSEARCH-1066:
--------------------------------------------

I hear you and we discussed this before. IMO it is flawed. This information has no business in the pom. It is just bloating already overly verbose maven poms. If they need meta information it should come from IDE specific files.  

> Some Maven plugins really need extensions: like creating a WAR enabled the webapp tooling and "one click deploy" tools, including JBoss. Quite cool

This should be configured via Eclipse and end up in some Eclipse/M2 config file.

> Exclude maven-jdocbook-plugin from Eclipse m2
> ---------------------------------------------
>
>                 Key: HSEARCH-1066
>                 URL: https://hibernate.onjira.com/browse/HSEARCH-1066
>             Project: Hibernate Search
>          Issue Type: Task
>          Components: build
>            Reporter: Sanne Grinovero
>            Assignee: Sanne Grinovero
>            Priority: Trivial
>             Fix For: 4.1.0.Final
>
>
> Eclipse's M2 is not able to deal with the maven-jdocbook-plugin, this generates project import errors on Eclipse when the documentation module is imported.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the hibernate-issues mailing list