[
https://issues.apache.org/jira/browse/IVY-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829307#action_12829307
]
Maarten Coene commented on IVY-1166:
------------------------------------
It's very hard to see what's going wrong.
My guess at the moment is that there is a problem with the patterns in your ssh
resolver, more in specific, I think the patterns containing the [branch] token
are causing the problem. When searching for the buildnumber, these first 2
patterns won't give any results because of a branch-mismatch (the listing shows
you don't have a branch for this module). The other patterns don't seem to
match with the listing you provided.
So to solve your problem, could you try adding following patterns to your ssh
resolver?
<artifact
pattern="${dest.repo.dir}/[organisation]/[module]/jars/[artifact]-[revision].[ext]"/>
<ivy
pattern="${dest.repo.dir}/[organisation]/[module]/ivys/ivy-[revision].xml"/>
> ivy unable to increment revision correctly
> ------------------------------------------
>
> Key: IVY-1166
> URL: https://issues.apache.org/jira/browse/IVY-1166
> Project: Ivy
> Issue Type: Bug
> Components: Ant
> Affects Versions: 2.1.0-RC1, 2.1.0
> Environment: client(s): windowsxp and linux
> server repository: linux
> Reporter: Amir
> Priority: Blocker
> Attachments: -build-base.xml, appwebserviceclient.files.list.txt,
> ivysettings-basic.xml
>
>
> ivy unable to increment revision correctly
> when buildnumber and publish task finish it keeps publishing version 1.0.2
> using ivy 2.0.0 works fine.
> using :
> <target name="publish.release" depends="client.deploy" description="Publishes
> a library to the corporate Ivy repository">
> <!-- asks to ivy an available version number -->
>
> <!-- auto-increment the next release number -->
> <ivy:buildnumber
> organisation="uk.co.company"
> module="AppWebServiceClient"
> />
> <echo message="Ivy repository says that the current ivy.revision is
> : ${ivy.revision}" />
> <echo message="Ivy repository says that the current
> ivy.new.revision is : ${ivy.new.revision}" />
> <echo message="Ivy repository says that the current
> ivy.build.number is : ${ivy.build.number}" />
> <echo message="Ivy repository says that the current
> ivy.new.build.number is : ${ivy.new.build.number}" />
>
> <ivy:publish
> settingsRef="basic.settings"
> artifactspattern="${dist.dir}/[artifact].[ext]"
> resolver="vm-repository"
> status="release"
> conf="unversioned.jar"
> forcedeliver="true"
> overwrite="true"
> pubrevision="${ivy.new.revision}"
> />
> <echo message="project ${ivy.module} released with version
> ${ivy.new.revision}" />
> </target>
> -----------------------------------
> Client ant output:
> publish.release:
> [ivy:buildnumber] DEPRECATED: 'ivy.conf.file' is deprecated, use
> 'ivy.settings.file' instead
> [ivy:buildnumber] :: loading settings :: file =
> C:\dev\eclipse.workspace\AppClient\ivy\ivysettings-basic.xml
> [echo] Ivy repository says that the current ivy.revision is : 1.0.1
> [echo] Ivy repository says that the current ivy.new.revision is : 1.0.2
> [echo] Ivy repository says that the current ivy.build.number is : 1
> [echo] Ivy repository says that the current ivy.new.build.number is : 2
> :: delivering :: uk.co.company#AppWebServiceClient;work...@z953831w :: 1.0.2
> :: release :: Mon Feb 01 17:16:03 GMT 2010
> delivering ivy file to C:\dev\eclipse.workspace\AppClient\dist\ivy.xml
> :: publishing :: uk.co.company#AppWebServiceClient
> published AppWebServiceClient to
> /opt/ivy-repository-2.1.0/myrepositoryNoDeps/no-namespace/uk.co.company/AppWebServiceClient//jars/AppWebServiceClient-1.0.2.jar
> published ivy to
> /opt/ivy-repository-2.1.0/myrepositoryNoDeps/no-namespace/uk.co.company/AppWebServiceClient//ivys/ivy-1.0.2.xml
> [echo] project AppWebServiceClient released with version 1.0.2
> ########################################################
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
