Discuss package structure change

[Husterknupp]

Problem Description
We have only one main package cc.commandmanager.core that contains all of our 14 classes. These classes are

• exceptions as well as
• those who do the main work (e.g., CommandManager, CommandGraph) and some
• kind of helper classes (e.g., Optional or ResultState).

This variety might be confusing.

@FRosner, @hinneburg do you think it would be reasonable to seperate the classes into more than just the core package? Or would it produce too much overhead? What criteria make sense to split the classes with respect to further extension?

[FRosner]

I moved this into 2.0. The structure is fine for now as we don't offer much functionality.

What does cc stand for anyway?

[Husterknupp]

It might stand for creative common and emphasizes the open character of this project. But I'm not totally sure on that.

[FRosner]

Very open indeed...

[FRosner]

@hinneburg do you want to publish the command manager under creative commons? If not, we should change the package name, I believe.