-
1. Re: Common assembly and module folder names
starksm64 Mar 10, 2007 5:34 AM (in response to pgier)I suppose. I guess the only issue is what are we going to do if we do make minor independent releases of the underlying projects. Say we do a 2.0.1 release of common, and then do 2.0.2 and 2.0.3 release of jboss-common-logging-log4j for whatever reason.
Are there going to be jboss-common-2.0.2 and 2.0.3 releases as well, or will we release 2.0.2 and 2.0.3 versions of everything even without changes?
We just need a plan on how this is going to be managed. -
2. Re: Common assembly and module folder names
pgier Mar 12, 2007 9:22 AM (in response to pgier)We will still be able to do independent releases. So we could do a 2.0.1 release of the combined common, and then do a 2.0.2 release of just common-logging-log4j, and then 2.0.2 of just common-core, etc.
Or we could have just the separate releases. Is it even useful to have a combined jar file in addition to the individual releases? Maybe it would be better to just keep the releases separate?