Can't do this as each table is processed as it found in the metadata and relationships are created to other tables which are required to be present. Compile errors will result if I exclude tables. I already experimented with this.

it can be left at the user discretion. we have schema with tons of tables, while only couple of them need to be involved into project. So, it would be nice for the user to be able to pick up set of tables manually. anyway it is gonna be optional parameter, so should be no harm.

Deferred to Roo 1.2, as the Roo command line does not support arrays of values for options at the moment

--excludeTables option added to database reverse engineer command in Git ID 7ea831201b44d2ede83307feb06682aede6e866c. The way to specify tables to exclude follows the normal Roo format ie for a single table:
database reverse engineer --excludeTables PET or database reverse engineer --excludeTables "PET"

For multiple tables, the table names must be enclosed by pairs of double quotes and be separated by spaces, eg
database reverse engineer --excludeTables "PET VET"

Subsequents executions of the database reverse engineer do not need to specify --excludeOptions to exclude the same tables, similar to the --schema and --package options. To un-exclude tables specify an empty string, eg
database reverse engineer --excludeTables

It would be great to use this:
--excludeTables "SOME_PREFIX* SOME_POSTFIX *SOME_PART_OF_TABLE_NAME_"

• - means any characters.

Sorry, forgot to escape:

--excludeTables "SOME_PREFIX* *SOME_POSTFIX *SOME_PART_OF_TABLE_NAME*"

Added wildcard searching in Git ID b8f4040d7c1958102019a786abc30aadf1c8bf1b. One can specify * to match many characters or ? to match a singe character. Example:

database reverse engineer --excludeTables "foo* ?bar* com*bar"