of course, we must use classifier per platform. see this link for other fundamental issues when not using non-unique snapshot
http://old.nabble.com/Multi-Platform-snapshots-td25295999.html -Dan On Mon, Nov 16, 2009 at 11:53 AM, Paul Benedict <[email protected]> wrote: > If you are creating artifacts for different environments, you can use > custom classifiers. I have done this. This will add a suffix to your > artifacts. > > Paul > > On Mon, Nov 16, 2009 at 1:50 PM, Dan Tran <[email protected]> wrote: >> How about an alternative solution to replace that feature? >> >> -D >> >> >> >> On Sun, Nov 15, 2009 at 11:26 AM, Dan Tran <[email protected]> wrote: >>> Hi >>> >>> According to >>> >>> http://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-NonuniqueSnapshotDeployments >>> >>> "The setting <uniqueVersion>false</uniqueVersion> for a distribution >>> repository has no effect in version 3.x, snapshot artifacts will >>> always be deployed using a timestamped version." >>> >>> This is a huge lost to those projects with multiple profile to build >>> per platform specific. see >>> http://old.nabble.com/Multi-Platform-snapshots-td25295999.html for >>> details >>> >>> For my case, we might be able to go forward with maven 3 ...... >>> >>> Can the dev team put it back? >>> >>> -Dan >>> >> >> --------------------------------------------------------------------- >> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
