I think it should work. WHat is Maven complaining about? /Anders
On Fri, Mar 16, 2012 at 21:51, Maven User <[email protected]> wrote: > Ok, now getting a bit pissed. > > Maven deploy:deploy-file is NOT liking my url to my snapshot repository. > > Is there some magic or can I just use -Durl=http://<server>/<path>/snapshots > > On Fri, Mar 16, 2012 at 4:10 PM, Maven User <[email protected]> wrote: > >> Preaching to the choir my friend. >> >> I tried hacking up the build helper plugin as suggested above, but the >> ArtifactId (understandably) can't be changed. >> >> Thanks all! >> >> >> On Fri, Mar 16, 2012 at 3:57 PM, <[email protected]> wrote: >> >>> >>> >>> > Well, kinda - that only allows you to adjust extension and classifier. >>> > >>> > I _know_, we're swimming up stream here a bit. >>> > >>> > I'm pulling down the code for the buildhelper - I'd like to be able to >>> control >>> > final name or artifactId at least :-/ >>> >>> I would suggest that controlling the name of the artifact is flagrant >>> violation of the maven way. I just did a bunch of this work and >>> I used the classifier to clearly identify the purpose of the attached >>> artifact. Assuming your .doc file was something like "release notes", you >>> could use a classifier of "releaseNotes". I assume your desire to use a >>> different name comes from other elements of your ecosystem wanting/ needing >>> a different name . . . ? I suggest changing those things if possible. >>> >>> If they really have to be named something else, perhaps they should be >>> attached to another project with that name. Or even deployed ad hoc via >>> the deploy:deploy-file mojo? >>> >>> >>> --------------------------------------------------------------------- >>> 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]
