As I somewhat expected. As you have the issue at hands, could you please
file a jira for the mave-deploy-plugin about this description being wrong?
/Anders
On Wed, Oct 6, 2010 at 11:48, NickDeGraeve wrote:
>
>
> Anders Hammar wrote:
> >
> > You might be able to solve this by setting generatePom
Doubt that. I've run into exactly the same thing when trying to script
deployments which use the deploy-file goal and includes sources/javadocs. My
solution was to just ignore any error for the javadoc and sources
deployment, as the jar was actually uploaded.
You could enable redeployments, but yo
Did you have a look at nexus logs to see what is wrong on its side ??
This is perhaps a problem of repository target settings
On Oct 6, 2010, at 11:23 AM, NickDeGraeve wrote:
>
> I'm trying to get a legacy project to build with Maven. I'm not allowed to do
> a complete makeover because of time c
So the problem is that I need to do 3 seperate deploys for the client and the
POM is added at the first invocation
It's unfortunate that the 'depoy-file' goal doesn't provide the
functionality to add the sources and Javadocs in one go like the
'install-file' goal does.
Nick
--
View this messag
Anders Hammar wrote:
>
> You might be able to solve this by setting generatePom to false:
> http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#generatePom
> I haven't tried this personally, but the text indicates this should work.
> However, the name of the param kind of i
This is expected as a release repo is set to not allow redeploys by default.
What happens is that first the primary artifact (the jar) and the pom gets
uploaded. The you try to uploaded sources jar and the pom again, which isn't
allowed.
A snapshot repo doesn't have this restriction normally and th
