Re: Maven deploy does not respect finalName

2014-09-26 Thread John Casey 

This question belongs on the users list.

Setting that aside, finalName is only meant as a convenience for use 
during the build process, and as such it only affects the filenames 
local to the build.


You're better off if you regard the repositories (local and remote) as 
databases (or catalogs), where the content has to be addressable in a 
predictable way if it's going to be retrieved.


If you're trying to set the name of a file in a particular way, chances 
are good that you're trying to use the repository as more than an 
artifact database / catalog.


HTH,

-john

On 09/26/2014 01:34 AM, VicBi wrote:

Hi,

Thanks for responding, I saw that I could use the plugin assembly. I'll try
to do it with this plugin :).

Thanks and regards



--
View this message in context: 
http://maven.40175.n5.nabble.com/Maven-deploy-does-not-respect-finalName-tp5806549p5806658.html
Sent from the Maven Developers mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



--
John Casey
---
GitHub:  https://github.com/jdcasey/
Twitter: http://twitter.com/buildchimp

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven deploy does not respect finalName

2014-09-25 Thread VicBi 
Hi,

Thanks for responding, I saw that I could use the plugin assembly. I'll try
to do it with this plugin :). 

Thanks and regards 



--
View this message in context: 
http://maven.40175.n5.nabble.com/Maven-deploy-does-not-respect-finalName-tp5806549p5806658.html
Sent from the Maven Developers mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven deploy does not respect finalName

2014-09-25 Thread Bernd Eckenfels 
Hello,

I dont think you can (or should) use arbitrary file names for artifacts
in a maven-style repository. They have to follow the
artifactid-classifier-version.type pattern.

It is usually the best to pack those files in an archive *-bin.zip or
similiar to keep their folder structure and file names in a maven-repo
compliant way.

This is btw better asked in the maven-users mailing list.

Gruss
Bernd

- Am Thu, 25 Sep 2014 06:51:21
-0700 (PDT) schrieb Victor :

> Hi,
> 
> When you run the maven deploy phase, maven upload to nexus the final
> file with the name ${artifactId}-${version}, and does not respect the
>  set in the build. 
> 
> How could I indicate to maven deploy plugin to upload to nexus with
> the name, for example PREFIX_${artifactId}-${version}
> 
> Does anyone know how to do?
> 
> 
> Thanks and regards.
> 
> 
> 
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Maven-deploy-does-not-respect-finalName-tp5806549.html
> Sent from the Maven Developers mailing list archive at Nabble.com.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Maven deploy does not respect finalName

2014-09-25 Thread Victor 
Hi,

When you run the maven deploy phase, maven upload to nexus the final file
with the name ${artifactId}-${version}, and does not respect the 
set in the build. 

How could I indicate to maven deploy plugin to upload to nexus with the
name, for example PREFIX_${artifactId}-${version}

Does anyone know how to do?


Thanks and regards.



--
View this message in context: 
http://maven.40175.n5.nabble.com/Maven-deploy-does-not-respect-finalName-tp5806549.html
Sent from the Maven Developers mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org