[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3134?page=c...
]
Steve Ebersole closed HHH-3134.
-------------------------------
Assignee: Steve Ebersole
Resolution: Fixed
Fix Version/s: 3.3
Moved documentation module definition in main pom to 2 separate profiles:
1) the 'release' profile used by the release plugin
2) profile named 'docs' intended to be able to activate inclusion of
documentation
So essentially documentation is now not activated by default. Instead, for non-release
processes one must activate that profile explicitly. My only real concern with that is
how that will play with IDE integrations. By I am pretty sure for IntelliJ at least this
will be fine; really no clue about Eclipse. We can revisit if that becomes an issue.
documentation module in a profile
---------------------------------
Key: HHH-3134
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3134
Project: Hibernate3
Issue Type: Sub-task
Components: core, documentation
Affects Versions: 3.3
Reporter: Aleksandar Kostadinov
Assignee: Steve Ebersole
Fix For: 3.3
Attachments: docs.patch
Can we have the documentation module of the core project in a profile so it can be
disabled if needed? It still has issues building as well depends on native tools not
universally present. It will be an issue for a CI system to ensure these tools present on
all build hosts as well in some other cases.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira