You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Daniele Dellafiore <il...@gmail.com> on 2010/06/22 11:26:16 UTC

Re: [maven-release-plugin] problem with a multi-module project, perform phase

I fixed the last problem removing myProject inheritance from the company
pom.

Now I am stucked cause the release plugin is deploying the source artifact
two times and the second time Nexus give me a 400 cause it does not allow to
overwrite an artifact in the release repository, and it's right.

It install and then deploy the sources artifact two times.

Here is the execution for the source-plugin

          <execution>
            <id>attach-sources</id>
            <goals>
              <goal>jar-no-fork</goal>
            </goals>
          </execution>

And here is the log

[INFO] [INFO] [install:install {execution: default-install}]
[INFO] [INFO] Installing ..lcore-1.0.jar to ../lcore-1.0.jar
[INFO] [INFO] Installing ..lcore-1.0-sources.jar to ..lcore-1.0-sources.jar
[INFO] [INFO] Installing ..lcore-1.0-sources.jar to ..lcore-1.0-sources.jar
[INFO] [INFO] Installing ..lcore-1.0-javadoc.jar to ..lcore-1.0-javadoc.jar
[INFO] [INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Uploading:
http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0.jar
[INFO] 4/70K
[INFO] 8/70K
...
[INFO] 70/70K
[INFO] 70K uploaded  (lcore-1.0.jar)
[INFO] [INFO] Retrieving previous metadata from releases.company.it
[INFO] [INFO] repository metadata for: 'artifact lavazza.eshop:lcore' could
not be found on repository: releases.iconmedialab.it, so will be created
[INFO] [INFO] Uploading repository metadata for: 'artifact
lavazza.eshop:lcore'
[INFO] [INFO] Uploading project information for lcore 1.0
[INFO] Uploading:
http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0-sources.jar
[INFO] 4/61K
...
[INFO] 61/61K
[INFO] 61K uploaded  (lcore-1.0-sources.jar)
[INFO] Uploading:
http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0-sources.jar
[INFO] 4/61K
...
[INFO] 61/61K
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] [INFO] Error deploying artifact: Failed to transfer file:
http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0-sources.jar.
Return code is: 400

-- 
Daniele Dellafiore
http://danieledellafiore.net

Re: [maven-release-plugin] problem with a multi-module project, perform phase

Posted by Anders Hammar <an...@hammar.net>.
You can disable the use of the release profile. See the link Nick sent.

/Anders

On Tue, Jun 22, 2010 at 11:53, Daniele Dellafiore <il...@gmail.com> wrote:

> Ok, the problem here is that if this conflict with existent source and
> javadocs generation configuration, it causes the release to fail.
>
> On Tue, Jun 22, 2010 at 11:50 AM, Nick Stolwijk <nick.stolwijk@gmail.com
> >wrote:
>
> > M-R-P activates a release profile by default, which contains the
> > source and javadocs. See [1]
> >
> > [1]
> >
> http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#useReleaseProfile
> >
> > With regards,
> >
> > Nick Stolwijk
> > ~Java Developer~
> >
> > IPROFS BV.
> > Claus Sluterweg 125
> > 2012 WS Haarlem
> > http://www.iprofs.nl
> >
> >
> >
> > On Tue, Jun 22, 2010 at 11:46 AM, Daniele Dellafiore <il...@gmail.com>
> > wrote:
> > > ok, I changed executions goal from jar-no-fork to just "jar" and it
> works
> > > I think that m-r-p by default has the attach-sources on the goal jar
> > active
> > > and if I add a jar-no-fork executions, they are summed.
> > > In fact nowhere in my config I tell maven to make javadoc but the
> release
> > > plugin just make it.
> > >
> > > I think this is a little tricky, probably an issue to report, what do
> you
> > > think?
> > >
> > > On Tue, Jun 22, 2010 at 11:26 AM, Daniele Dellafiore <
> ildella@gmail.com
> > >wrote:
> > >
> > >> I fixed the last problem removing myProject inheritance from the
> company
> > >> pom.
> > >>
> > >> Now I am stucked cause the release plugin is deploying the source
> > artifact
> > >> two times and the second time Nexus give me a 400 cause it does not
> > allow to
> > >> overwrite an artifact in the release repository, and it's right.
> > >>
> > >> It install and then deploy the sources artifact two times.
> > >>
> > >> Here is the execution for the source-plugin
> > >>
> > >>           <execution>
> > >>             <id>attach-sources</id>
> > >>             <goals>
> > >>               <goal>jar-no-fork</goal>
> > >>             </goals>
> > >>           </execution>
> > >>
> > >> And here is the log
> > >>
> > >> [INFO] [INFO] [install:install {execution: default-install}]
> > >> [INFO] [INFO] Installing ..lcore-1.0.jar to ../lcore-1.0.jar
> > >> [INFO] [INFO] Installing ..lcore-1.0-sources.jar to
> > ..lcore-1.0-sources.jar
> > >> [INFO] [INFO] Installing ..lcore-1.0-sources.jar to
> > ..lcore-1.0-sources.jar
> > >> [INFO] [INFO] Installing ..lcore-1.0-javadoc.jar to
> > ..lcore-1.0-javadoc.jar
> > >> [INFO] [INFO] [deploy:deploy {execution: default-deploy}]
> > >> [INFO] Uploading:
> > >>
> >
> http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0.jar
> > >> [INFO] 4/70K
> > >> [INFO] 8/70K
> > >> ...
> > >> [INFO] 70/70K
> > >> [INFO] 70K uploaded  (lcore-1.0.jar)
> > >> [INFO] [INFO] Retrieving previous metadata from releases.company.it
> > >> [INFO] [INFO] repository metadata for: 'artifact lavazza.eshop:lcore'
> > could
> > >> not be found on repository: releases.iconmedialab.it, so will be
> > created
> > >> [INFO] [INFO] Uploading repository metadata for: 'artifact
> > >> lavazza.eshop:lcore'
> > >> [INFO] [INFO] Uploading project information for lcore 1.0
> > >> [INFO] Uploading:
> > >>
> >
> http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0-sources.jar
> > >> [INFO] 4/61K
> > >> ...
> > >> [INFO] 61/61K
> > >> [INFO] 61K uploaded  (lcore-1.0-sources.jar)
> > >> [INFO] Uploading:
> > >>
> >
> http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0-sources.jar
> > >> [INFO] 4/61K
> > >> ...
> > >> [INFO] 61/61K
> > >> [INFO] [INFO]
> > >>
> ------------------------------------------------------------------------
> > >> [INFO] [ERROR] BUILD ERROR
> > >> [INFO] [INFO]
> > >>
> ------------------------------------------------------------------------
> > >> [INFO] [INFO] Error deploying artifact: Failed to transfer file:
> > >>
> >
> http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0-sources.jar
> > .
> > >> Return code is: 400
> > >>
> > >>
> > >> --
> > >> Daniele Dellafiore
> > >> http://danieledellafiore.net
> > >>
> > >
> > >
> > >
> > > --
> > > Daniele Dellafiore
> > > http://danieledellafiore.net
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> Daniele Dellafiore
> http://danieledellafiore.net
>

Re: [maven-release-plugin] problem with a multi-module project, perform phase

Posted by Daniele Dellafiore <il...@gmail.com>.
Ok, the problem here is that if this conflict with existent source and
javadocs generation configuration, it causes the release to fail.

On Tue, Jun 22, 2010 at 11:50 AM, Nick Stolwijk <ni...@gmail.com>wrote:

> M-R-P activates a release profile by default, which contains the
> source and javadocs. See [1]
>
> [1]
> http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#useReleaseProfile
>
> With regards,
>
> Nick Stolwijk
> ~Java Developer~
>
> IPROFS BV.
> Claus Sluterweg 125
> 2012 WS Haarlem
> http://www.iprofs.nl
>
>
>
> On Tue, Jun 22, 2010 at 11:46 AM, Daniele Dellafiore <il...@gmail.com>
> wrote:
> > ok, I changed executions goal from jar-no-fork to just "jar" and it works
> > I think that m-r-p by default has the attach-sources on the goal jar
> active
> > and if I add a jar-no-fork executions, they are summed.
> > In fact nowhere in my config I tell maven to make javadoc but the release
> > plugin just make it.
> >
> > I think this is a little tricky, probably an issue to report, what do you
> > think?
> >
> > On Tue, Jun 22, 2010 at 11:26 AM, Daniele Dellafiore <ildella@gmail.com
> >wrote:
> >
> >> I fixed the last problem removing myProject inheritance from the company
> >> pom.
> >>
> >> Now I am stucked cause the release plugin is deploying the source
> artifact
> >> two times and the second time Nexus give me a 400 cause it does not
> allow to
> >> overwrite an artifact in the release repository, and it's right.
> >>
> >> It install and then deploy the sources artifact two times.
> >>
> >> Here is the execution for the source-plugin
> >>
> >>           <execution>
> >>             <id>attach-sources</id>
> >>             <goals>
> >>               <goal>jar-no-fork</goal>
> >>             </goals>
> >>           </execution>
> >>
> >> And here is the log
> >>
> >> [INFO] [INFO] [install:install {execution: default-install}]
> >> [INFO] [INFO] Installing ..lcore-1.0.jar to ../lcore-1.0.jar
> >> [INFO] [INFO] Installing ..lcore-1.0-sources.jar to
> ..lcore-1.0-sources.jar
> >> [INFO] [INFO] Installing ..lcore-1.0-sources.jar to
> ..lcore-1.0-sources.jar
> >> [INFO] [INFO] Installing ..lcore-1.0-javadoc.jar to
> ..lcore-1.0-javadoc.jar
> >> [INFO] [INFO] [deploy:deploy {execution: default-deploy}]
> >> [INFO] Uploading:
> >>
> http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0.jar
> >> [INFO] 4/70K
> >> [INFO] 8/70K
> >> ...
> >> [INFO] 70/70K
> >> [INFO] 70K uploaded  (lcore-1.0.jar)
> >> [INFO] [INFO] Retrieving previous metadata from releases.company.it
> >> [INFO] [INFO] repository metadata for: 'artifact lavazza.eshop:lcore'
> could
> >> not be found on repository: releases.iconmedialab.it, so will be
> created
> >> [INFO] [INFO] Uploading repository metadata for: 'artifact
> >> lavazza.eshop:lcore'
> >> [INFO] [INFO] Uploading project information for lcore 1.0
> >> [INFO] Uploading:
> >>
> http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0-sources.jar
> >> [INFO] 4/61K
> >> ...
> >> [INFO] 61/61K
> >> [INFO] 61K uploaded  (lcore-1.0-sources.jar)
> >> [INFO] Uploading:
> >>
> http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0-sources.jar
> >> [INFO] 4/61K
> >> ...
> >> [INFO] 61/61K
> >> [INFO] [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] [ERROR] BUILD ERROR
> >> [INFO] [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] [INFO] Error deploying artifact: Failed to transfer file:
> >>
> http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0-sources.jar
> .
> >> Return code is: 400
> >>
> >>
> >> --
> >> Daniele Dellafiore
> >> http://danieledellafiore.net
> >>
> >
> >
> >
> > --
> > Daniele Dellafiore
> > http://danieledellafiore.net
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Daniele Dellafiore
http://danieledellafiore.net

Re: [maven-release-plugin] problem with a multi-module project, perform phase

Posted by Nick Stolwijk <ni...@gmail.com>.
M-R-P activates a release profile by default, which contains the
source and javadocs. See [1]

[1] http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#useReleaseProfile

With regards,

Nick Stolwijk
~Java Developer~

IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl



On Tue, Jun 22, 2010 at 11:46 AM, Daniele Dellafiore <il...@gmail.com> wrote:
> ok, I changed executions goal from jar-no-fork to just "jar" and it works
> I think that m-r-p by default has the attach-sources on the goal jar active
> and if I add a jar-no-fork executions, they are summed.
> In fact nowhere in my config I tell maven to make javadoc but the release
> plugin just make it.
>
> I think this is a little tricky, probably an issue to report, what do you
> think?
>
> On Tue, Jun 22, 2010 at 11:26 AM, Daniele Dellafiore <il...@gmail.com>wrote:
>
>> I fixed the last problem removing myProject inheritance from the company
>> pom.
>>
>> Now I am stucked cause the release plugin is deploying the source artifact
>> two times and the second time Nexus give me a 400 cause it does not allow to
>> overwrite an artifact in the release repository, and it's right.
>>
>> It install and then deploy the sources artifact two times.
>>
>> Here is the execution for the source-plugin
>>
>>           <execution>
>>             <id>attach-sources</id>
>>             <goals>
>>               <goal>jar-no-fork</goal>
>>             </goals>
>>           </execution>
>>
>> And here is the log
>>
>> [INFO] [INFO] [install:install {execution: default-install}]
>> [INFO] [INFO] Installing ..lcore-1.0.jar to ../lcore-1.0.jar
>> [INFO] [INFO] Installing ..lcore-1.0-sources.jar to ..lcore-1.0-sources.jar
>> [INFO] [INFO] Installing ..lcore-1.0-sources.jar to ..lcore-1.0-sources.jar
>> [INFO] [INFO] Installing ..lcore-1.0-javadoc.jar to ..lcore-1.0-javadoc.jar
>> [INFO] [INFO] [deploy:deploy {execution: default-deploy}]
>> [INFO] Uploading:
>> http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0.jar
>> [INFO] 4/70K
>> [INFO] 8/70K
>> ...
>> [INFO] 70/70K
>> [INFO] 70K uploaded  (lcore-1.0.jar)
>> [INFO] [INFO] Retrieving previous metadata from releases.company.it
>> [INFO] [INFO] repository metadata for: 'artifact lavazza.eshop:lcore' could
>> not be found on repository: releases.iconmedialab.it, so will be created
>> [INFO] [INFO] Uploading repository metadata for: 'artifact
>> lavazza.eshop:lcore'
>> [INFO] [INFO] Uploading project information for lcore 1.0
>> [INFO] Uploading:
>> http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0-sources.jar
>> [INFO] 4/61K
>> ...
>> [INFO] 61/61K
>> [INFO] 61K uploaded  (lcore-1.0-sources.jar)
>> [INFO] Uploading:
>> http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0-sources.jar
>> [INFO] 4/61K
>> ...
>> [INFO] 61/61K
>> [INFO] [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [ERROR] BUILD ERROR
>> [INFO] [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [INFO] Error deploying artifact: Failed to transfer file:
>> http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0-sources.jar.
>> Return code is: 400
>>
>>
>> --
>> Daniele Dellafiore
>> http://danieledellafiore.net
>>
>
>
>
> --
> Daniele Dellafiore
> http://danieledellafiore.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [maven-release-plugin] problem with a multi-module project, perform phase

Posted by Daniele Dellafiore <il...@gmail.com>.
ok, I changed executions goal from jar-no-fork to just "jar" and it works
I think that m-r-p by default has the attach-sources on the goal jar active
and if I add a jar-no-fork executions, they are summed.
In fact nowhere in my config I tell maven to make javadoc but the release
plugin just make it.

I think this is a little tricky, probably an issue to report, what do you
think?

On Tue, Jun 22, 2010 at 11:26 AM, Daniele Dellafiore <il...@gmail.com>wrote:

> I fixed the last problem removing myProject inheritance from the company
> pom.
>
> Now I am stucked cause the release plugin is deploying the source artifact
> two times and the second time Nexus give me a 400 cause it does not allow to
> overwrite an artifact in the release repository, and it's right.
>
> It install and then deploy the sources artifact two times.
>
> Here is the execution for the source-plugin
>
>           <execution>
>             <id>attach-sources</id>
>             <goals>
>               <goal>jar-no-fork</goal>
>             </goals>
>           </execution>
>
> And here is the log
>
> [INFO] [INFO] [install:install {execution: default-install}]
> [INFO] [INFO] Installing ..lcore-1.0.jar to ../lcore-1.0.jar
> [INFO] [INFO] Installing ..lcore-1.0-sources.jar to ..lcore-1.0-sources.jar
> [INFO] [INFO] Installing ..lcore-1.0-sources.jar to ..lcore-1.0-sources.jar
> [INFO] [INFO] Installing ..lcore-1.0-javadoc.jar to ..lcore-1.0-javadoc.jar
> [INFO] [INFO] [deploy:deploy {execution: default-deploy}]
> [INFO] Uploading:
> http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0.jar
> [INFO] 4/70K
> [INFO] 8/70K
> ...
> [INFO] 70/70K
> [INFO] 70K uploaded  (lcore-1.0.jar)
> [INFO] [INFO] Retrieving previous metadata from releases.company.it
> [INFO] [INFO] repository metadata for: 'artifact lavazza.eshop:lcore' could
> not be found on repository: releases.iconmedialab.it, so will be created
> [INFO] [INFO] Uploading repository metadata for: 'artifact
> lavazza.eshop:lcore'
> [INFO] [INFO] Uploading project information for lcore 1.0
> [INFO] Uploading:
> http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0-sources.jar
> [INFO] 4/61K
> ...
> [INFO] 61/61K
> [INFO] 61K uploaded  (lcore-1.0-sources.jar)
> [INFO] Uploading:
> http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0-sources.jar
> [INFO] 4/61K
> ...
> [INFO] 61/61K
> [INFO] [INFO]
> ------------------------------------------------------------------------
> [INFO] [ERROR] BUILD ERROR
> [INFO] [INFO]
> ------------------------------------------------------------------------
> [INFO] [INFO] Error deploying artifact: Failed to transfer file:
> http://10.10.20.128:8080/nexus/content/repositories/releases/../1.0/lcore-1.0-sources.jar.
> Return code is: 400
>
>
> --
> Daniele Dellafiore
> http://danieledellafiore.net
>



-- 
Daniele Dellafiore
http://danieledellafiore.net