Hi Sven!
Sven Homburg wrote: > > short hint how to configure this ? > If your library uses another library (e.g. t5components use tapestry-core) and you support with your version X a range of versions Y1-Y5 of the other library then you can tell maven that with version ranges. Here you can see how to specify them: http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges For example: if your version 0.5.4 supports Tapestry 5.0.6 - 5.0.9 (both including) then you could have: <properties> <tapestry-version>[5.0.6, 5.0.9]</tapestry-version> </properties> with: <dependency> <groupId>org.apache.tapestry</groupId> <artifactId>tapestry-core</artifactId> <version>${tapestry-version}</version> </dependency> Usually, as a library depending on another lib you should have at least something like this: ... <verision>[1.1,1.2)</version> Which means we support 1.1 and all Bugfix releases (1.1.1, 1.1.2, ...). That requires that the other library uses the versioning scheme correctly (major, minor, bugfix). Bugfix releases should not change interface and semantics. With Tapestry5 - this will need time until the first "real" release. But now, I think we're gliding too deep into Mavenish (maybe we should continue on the Maven mailing-list ;) ) -- Chris -- View this message in context: http://www.nabble.com/Need-help-with-pom.xml-for-my-tapestry-5-project-tp15166088p15207367.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
