I know maven is quite java centric, but I assume there should be some strategy for handling this type of problem in the "maven way"? What would be the proper way for accomplishing this in maven?
2009/3/12 Wayne Fay <[email protected]> > > As you can see, the file group-project-2.3.0.1-16287.noarch.rpm is > > installed as project-2.3.0-1.rpm. Is there a way to prevent this, ie. > > keep the original file name? > > I'm not aware of any way to force Maven to install into a repo using > the "finalName" you've defined. There are a lot of good reasons for > this. > > If you require this naming you've suggested above, the -16287 part > belongs in your version tag, and the noarch bit belongs in the > classifier. Then Maven will install this file as: > ${project.artifactId}-${project.version}-${project.classifier}.rpm > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [email protected] www.seamless.se
