My understanding is the same as Wendy and Stephen's. Put incubating in the version (required), not the groupId or artifactId.
Yoav On 11/11/06, Stephen Duncan <[EMAIL PROTECTED]> wrote:
Right. But if they specify org.apache.wicket:wicket:1.0, and some dependency they have has a dependency on org.apache.incubator.wicket:wicket:1.0-incubating, they'll end up with both. If the groupId is the same, they'll just the dependency they specified. -Stephen On 11/11/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > On 11/11/06, Stephen Duncan <[EMAIL PROTECTED]> wrote: > > On 11/11/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > > <groupId>org.apache.incubator.wicket</groupid> > > > <artifactId>wicket-parent</artifactId> > > > <version>1.3-incubating-SNAPSHOT</version> > > > > I think that's a bad thing, as upon the first release after > > graduation, the groupId will change, and therefore your pre-post & > > graduation artifacts will be considered to be totally different. This > > will expose problems to users of your artifacts because Maven can't > > prevent them from getting two different versions of wicket. > > But that is the same as for changing the version. Either way people > *have* to change their pom's to reflect the new release. > > Martijn > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Stephen Duncan Jr www.stephenduncanjr.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
