documentation module in a profile

Description

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.

Environment

None

Activity

Show:
Alexander Kostadinov
February 26, 2008, 12:27 PM

Attaching a patch file. Since docs are not buildable now I verified to get the same error with and without the patch.

you cam apply by "patch -p0 < docs.patch"

Steve Ebersole
February 28, 2008, 3:26 AM

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.

Alexander Kostadinov
February 28, 2008, 3:20 PM

Thanks! CI is now running fine. There is some issue with publishing and notification but that will be resolved soon.

Database builds are my next task.

Assignee

Steve Ebersole

Reporter

Alexander Kostadinov

Fix versions

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Affects versions

Priority

Major
Configure