The artifacts by default are also the jar names, which is the thing I care most. They must be not too long, but also somewhat unique (in some cases, they could get into a common directory with other stuff and we need to avoid clashes). I've figured out three options:
fabriziogiudici added a comment - 21/Jul/09 03:25 PM The artifacts by default are also the jar names, which is the thing I care most. They must be not too long, but also somewhat unique (in some cases, they could get into a common directory with other stuff and we need to avoid clashes). I've figured out three options:
1.
betterbeansbinding-core.jar
betterbeansbinding-el.jar
betterbeansbinding-swingbinding.jar
2.
bbb-core.jar
bbb-el.jar
bbb-swingbinding.jar
3.
A "qualified name" solution (à la eclipse), such as it.tidalwave.betterbeansbinding-.jar or org.jdesktop.betterbeansbinding-.jar.
Improvement
Closed
Major
Decide final names for groupIds and artifactIds.
The artifacts by default are also the jar names, which is the thing I care most. They must be not too long, but also somewhat unique (in some cases, they could get into a common directory with other stuff and we need to avoid clashes). I've figured out three options:
1.
betterbeansbinding-core.jar
betterbeansbinding-el.jar
betterbeansbinding-swingbinding.jar
2.
bbb-core.jar
bbb-el.jar
bbb-swingbinding.jar
3.
A "qualified name" solution (à la eclipse), such as it.tidalwave.betterbeansbinding-.jar or org.jdesktop.betterbeansbinding-.jar.