http://maven.apache.org/faq.html#unversioned-jars
you can do what you want in your project, but you must obey the rules in the local repository as that's Maven's private area. - Brett On 8/9/05, Sanjay Choudhary <[EMAIL PROTECTED]> wrote: > I wish to use maven.jar.final.name <http://maven.jar.final.name> property. I > want my jar file name to be different.(basiclly, don't want any version > appended to it, I know it is not in alignment with maven best practice but > life is not always straight). > If I use maven jar:install -Dmaven.jar.final.name=foo.jar > 1. It creates foo.jar in target directory. > 2. It copies foo.jar to foo-1.1.jar in maven local repository. ?? what is > the use of maven.jar.final.name <http://maven.jar.final.name>? > Let us assumt, I have another java project fred that is dependent on > project foo. fred and foo - both extend from same project.xml and share the > same pom-version. In fred project, project.xml is as below > <dependency> > <artifactId>foo</artifactId> > <groupId>${pom.groupId}</groupId> > <properties> > <jar.manifest.classpath>true</jar.manifest.classpath> > </properties> > <version>${pom.currentVersion}</version> > </dependency> > Is it possible to define dependecy of fred on foo in project.xml without > the version # ? so that when I use multiproject:goal -Djar:install it will > first build foo and then fred. > Please advice. > Thanks, > sanjay > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
