The package task runs fine, and by modifying the pom to use jgit as SCM
server, files are created with build number (ie
OpenJUMP-20210119-rcaccfa1928f1bdc1205965d08cf431c50bfb5559-PLUS.zip)

Nicolas

On Tue, 19 Jan 2021 at 11:02, Nicolas Ribot <nicolas.ri...@gmail.com> wrote:

> Hi,
> That's a good news.
>
> I gave it a try, by cloning git repo, then switching to master branch.
> I use IntelliJ IDEA for devs. When running the Maven deploy task, I get
> the error:
> Failed to execute goal
> org.codehaus.mojo:buildnumber-maven-plugin:1.4:create
> (generate-buildnumber) on project OpenJUMP: Cannot get the revision
> information from the scm repository :
> Exception while executing SCM command.
>
> By commenting out the providerImplementations in the
> buildnumber-maven-plugin (pom.xml), the task runs, zip and jar files are
> created (ie: OpenJUMP-20210119-r${version.revision}.jar).
> There is still an error:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on
> project OpenJUMP: Deployment failed: repository element was not specified
> in the POM inside distributionManagement element or in
> -DaltDeploymentRepository=id::layout::url parameter -> [Help 1]
>
> Nicolas
>
>
> On Tue, 19 Jan 2021 at 09:19, Michaud Michael <m.michael.mich...@orange.fr>
> wrote:
>
>> Hi Jumpers
>>
>> Thanks to Eric's guide, I could initialize openjump project on gitub
>> (openjump-gis/openjump) and convert it to jts 1.18.
>>
>> It is not perfect (I could not convert 1.5 post_release
>> <https://sourceforge.net/p/jump-pilot/code/HEAD/tree/core/tags/1.5%20post_release>
>>  tag
>> because of the whitespace in the name :-(), but all in all, I think it is
>> OK.
>>
>> Please, have a look and let me know if you think so.
>>
>> I could compile but I still have a problem to run maven.
>>
>> I did not migrate plugins at all (not sure how we must proceed yet, some
>> options must be discussed)
>>
>> There are probably plenty of things to improve and fix before we start
>> again to add new code.
>>
>> I'll try to list some more precise points to discuss in a future mail.
>>
>> Michaƫl
>> _______________________________________________
>> Jump-pilot-devel mailing list
>> Jump-pilot-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>
>
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to