Re: release failing, help needed

2021-05-27 Thread Ben M.
OK, let's start with updating some gpg 
instructions: https://github.com/mojohaus/mojohaus.github.io/pull/38

Unless I do a release, I probably cannot help you any further. Sorry! :( 
BUT… I noticed slow upload/download speeds from Germany as well. In case 
you are a Deutsche Telekom customer as I am, just open a ticket. You will 
get a refund on each month this happens. According to press it is a peering 
problem on the part of Deutsche Telekom.

Ben M. schrieb am Donnerstag, 27. Mai 2021 um 22:41:21 UTC+2:

> Wow, the "how to release" page is extremely outdated.
>
> DSA keys… they are deprecated for years now and we are moving from RSA to 
> ECC now.
>
> About the run time… I did a dry run of release:prepare and found:
> [INFO] [prepare dry-run] 17/17 end-release 
> [INFO] Release preparation simulation complete. 
> [INFO] 
>  
> [INFO] BUILD SUCCESS 
> [INFO] 
>  
> [INFO] Total time:  32.543 s 
> [INFO] Finished at: 2021-05-27T22:39:41+02:00 
> [INFO] 
> 
>
> I will ping some other committers and ask about what to do in your case.
>
> joerg.h...@googlemail.com schrieb am Donnerstag, 27. Mai 2021 um 21:50:04 
> UTC+2:
>
>> Hi Bean,
>>
>> thanks for your response and your suggestion.
>> I updated parent to the latest release 61:
>>
>> https://github.com/mojohaus/servicedocgen-maven-plugin/commit/ca831c4821200ea162174533cf7293d433b03c53
>>
>> After rerunning the release process I ended up with the exact same 
>> behaviour.
>>
>> BTW:
>> [INFO] BUILD SUCCESS
>> [INFO] 
>> 
>> [INFO] Total time:  01:25 h
>> [INFO] Finished at: 2021-05-27T21:38:28+02:00
>>
>> IMHO almost 1,5h is extraordinary slow for the release of a simple mojo.
>> Something wrong with OSSRH nexus?
>>
>> It seems that release plugins hates me as I hat it.
>> Is mojohaus still following the manifesto or have we changed to a 
>> collaboration of agile sub-projects where only the results count?
>> So if nobody forces me to follow the official process and to use 
>> release-maven-plugin, I can do the release with "devon release" from 
>> devonfw-ide or I can also try to automate it via github actions.
>>
>> Kind regards
>>   Jörg
>> Ben M. schrieb am Donnerstag, 27. Mai 2021 um 19:22:54 UTC+2:
>>
>>> Have you tried updating the parent pom?
>>> I think you will need more recent versions of some plugins, especially 
>>> the deploy and gpg plugins.
>>>
>>> joerg.h...@googlemail.com schrieb am Donnerstag, 27. Mai 2021 um 
>>> 16:48:39 UTC+2:
>>>
 Dear mojohaus experts,

 after a long while I want to build a release of one of my mojos.
 I tried to exactly follow the instructions:
 https://www.mojohaus.org/development/performing-a-release.html

 Whilst running mvn release:perform I saw log message like this:
 Uploading to ossrh-staging: 
 http://oss.sonatype.org/service/local/staging/deploy/maven2/org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar
 [WARNING] Failed to upload checksum 
 org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha1:
  
 null
 [WARNING] Failed to upload checksum 
 org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.md5:
  
 null

 However, build gave me SUCCESS so I closed the repo in OSSRH.
 That now failed with this error:
 Requires one-of SHA-1: 
 /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha1,
  
 MD5: 
 /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.md5,
  
 SHA-256: 
 /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha256,
  
 SHA-512: 
 /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha512

 Can someone give me a hint what I might be doing wrong?

 Thanks & cheers
   Jörg

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mojohaus-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mojohaus-dev/d8f470ec-8e9e-460c-8d94-c9a2172529a0n%40googlegroups.com.


Re: release failing, help needed

2021-05-27 Thread Ben M.
Wow, the "how to release" page is extremely outdated.

DSA keys… they are deprecated for years now and we are moving from RSA to 
ECC now.

About the run time… I did a dry run of release:prepare and found:
[INFO] [prepare dry-run] 17/17 end-release 
[INFO] Release preparation simulation complete. 
[INFO] 
 
[INFO] BUILD SUCCESS 
[INFO] 
 
[INFO] Total time:  32.543 s 
[INFO] Finished at: 2021-05-27T22:39:41+02:00 
[INFO] 


I will ping some other committers and ask about what to do in your case.

joerg.h...@googlemail.com schrieb am Donnerstag, 27. Mai 2021 um 21:50:04 
UTC+2:

> Hi Bean,
>
> thanks for your response and your suggestion.
> I updated parent to the latest release 61:
>
> https://github.com/mojohaus/servicedocgen-maven-plugin/commit/ca831c4821200ea162174533cf7293d433b03c53
>
> After rerunning the release process I ended up with the exact same 
> behaviour.
>
> BTW:
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time:  01:25 h
> [INFO] Finished at: 2021-05-27T21:38:28+02:00
>
> IMHO almost 1,5h is extraordinary slow for the release of a simple mojo.
> Something wrong with OSSRH nexus?
>
> It seems that release plugins hates me as I hat it.
> Is mojohaus still following the manifesto or have we changed to a 
> collaboration of agile sub-projects where only the results count?
> So if nobody forces me to follow the official process and to use 
> release-maven-plugin, I can do the release with "devon release" from 
> devonfw-ide or I can also try to automate it via github actions.
>
> Kind regards
>   Jörg
> Ben M. schrieb am Donnerstag, 27. Mai 2021 um 19:22:54 UTC+2:
>
>> Have you tried updating the parent pom?
>> I think you will need more recent versions of some plugins, especially 
>> the deploy and gpg plugins.
>>
>> joerg.h...@googlemail.com schrieb am Donnerstag, 27. Mai 2021 um 
>> 16:48:39 UTC+2:
>>
>>> Dear mojohaus experts,
>>>
>>> after a long while I want to build a release of one of my mojos.
>>> I tried to exactly follow the instructions:
>>> https://www.mojohaus.org/development/performing-a-release.html
>>>
>>> Whilst running mvn release:perform I saw log message like this:
>>> Uploading to ossrh-staging: 
>>> http://oss.sonatype.org/service/local/staging/deploy/maven2/org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar
>>> [WARNING] Failed to upload checksum 
>>> org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha1:
>>>  
>>> null
>>> [WARNING] Failed to upload checksum 
>>> org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.md5:
>>>  
>>> null
>>>
>>> However, build gave me SUCCESS so I closed the repo in OSSRH.
>>> That now failed with this error:
>>> Requires one-of SHA-1: 
>>> /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha1,
>>>  
>>> MD5: 
>>> /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.md5,
>>>  
>>> SHA-256: 
>>> /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha256,
>>>  
>>> SHA-512: 
>>> /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha512
>>>
>>> Can someone give me a hint what I might be doing wrong?
>>>
>>> Thanks & cheers
>>>   Jörg
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mojohaus-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mojohaus-dev/e14a7602-2eed-4142-bbb4-7b050192ada1n%40googlegroups.com.


Re: release failing, help needed

2021-05-27 Thread 'joerg.h...@googlemail.com' via mojohaus-dev
Hi Bean,

thanks for your response and your suggestion.
I updated parent to the latest release 61:
https://github.com/mojohaus/servicedocgen-maven-plugin/commit/ca831c4821200ea162174533cf7293d433b03c53

After rerunning the release process I ended up with the exact same 
behaviour.

BTW:
[INFO] BUILD SUCCESS
[INFO] 

[INFO] Total time:  01:25 h
[INFO] Finished at: 2021-05-27T21:38:28+02:00

IMHO almost 1,5h is extraordinary slow for the release of a simple mojo.
Something wrong with OSSRH nexus?

It seems that release plugins hates me as I hat it.
Is mojohaus still following the manifesto or have we changed to a 
collaboration of agile sub-projects where only the results count?
So if nobody forces me to follow the official process and to use 
release-maven-plugin, I can do the release with "devon release" from 
devonfw-ide or I can also try to automate it via github actions.

Kind regards
  Jörg
Ben M. schrieb am Donnerstag, 27. Mai 2021 um 19:22:54 UTC+2:

> Have you tried updating the parent pom?
> I think you will need more recent versions of some plugins, especially the 
> deploy and gpg plugins.
>
> joerg.h...@googlemail.com schrieb am Donnerstag, 27. Mai 2021 um 16:48:39 
> UTC+2:
>
>> Dear mojohaus experts,
>>
>> after a long while I want to build a release of one of my mojos.
>> I tried to exactly follow the instructions:
>> https://www.mojohaus.org/development/performing-a-release.html
>>
>> Whilst running mvn release:perform I saw log message like this:
>> Uploading to ossrh-staging: 
>> http://oss.sonatype.org/service/local/staging/deploy/maven2/org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar
>> [WARNING] Failed to upload checksum 
>> org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha1:
>>  
>> null
>> [WARNING] Failed to upload checksum 
>> org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.md5:
>>  
>> null
>>
>> However, build gave me SUCCESS so I closed the repo in OSSRH.
>> That now failed with this error:
>> Requires one-of SHA-1: 
>> /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha1,
>>  
>> MD5: 
>> /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.md5,
>>  
>> SHA-256: 
>> /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha256,
>>  
>> SHA-512: 
>> /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha512
>>
>> Can someone give me a hint what I might be doing wrong?
>>
>> Thanks & cheers
>>   Jörg
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mojohaus-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mojohaus-dev/aa19308c-e7d9-4343-81ad-fd7801864255n%40googlegroups.com.


Re: release failing, help needed

2021-05-27 Thread Ben M.
Have you tried updating the parent pom?
I think you will need more recent versions of some plugins, especially the 
deploy and gpg plugins.

joerg.h...@googlemail.com schrieb am Donnerstag, 27. Mai 2021 um 16:48:39 
UTC+2:

> Dear mojohaus experts,
>
> after a long while I want to build a release of one of my mojos.
> I tried to exactly follow the instructions:
> https://www.mojohaus.org/development/performing-a-release.html
>
> Whilst running mvn release:perform I saw log message like this:
> Uploading to ossrh-staging: 
> http://oss.sonatype.org/service/local/staging/deploy/maven2/org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar
> [WARNING] Failed to upload checksum 
> org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha1:
>  
> null
> [WARNING] Failed to upload checksum 
> org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.md5:
>  
> null
>
> However, build gave me SUCCESS so I closed the repo in OSSRH.
> That now failed with this error:
> Requires one-of SHA-1: 
> /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha1,
>  
> MD5: 
> /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.md5,
>  
> SHA-256: 
> /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha256,
>  
> SHA-512: 
> /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha512
>
> Can someone give me a hint what I might be doing wrong?
>
> Thanks & cheers
>   Jörg
>

-- 
You received this message because you are subscribed to the Google Groups 
"mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mojohaus-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mojohaus-dev/41c9f562-8681-4783-8f27-17f7d7d5dc10n%40googlegroups.com.


release failing, help needed

2021-05-27 Thread 'joerg.h...@googlemail.com' via mojohaus-dev
Dear mojohaus experts,

after a long while I want to build a release of one of my mojos.
I tried to exactly follow the instructions:
https://www.mojohaus.org/development/performing-a-release.html

Whilst running mvn release:perform I saw log message like this:
Uploading to ossrh-staging: 
http://oss.sonatype.org/service/local/staging/deploy/maven2/org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar
[WARNING] Failed to upload checksum 
org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha1:
 
null
[WARNING] Failed to upload checksum 
org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.md5:
 
null

However, build gave me SUCCESS so I closed the repo in OSSRH.
That now failed with this error:
Requires one-of SHA-1: 
/org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha1,
 
MD5: 
/org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.md5,
 
SHA-256: 
/org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha256,
 
SHA-512: 
/org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha512

Can someone give me a hint what I might be doing wrong?

Thanks & cheers
  Jörg

-- 
You received this message because you are subscribed to the Google Groups 
"mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mojohaus-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mojohaus-dev/ceff6bbe-fcbb-440f-b305-fb72fa6bdc82n%40googlegroups.com.


Re: Make dev-aspectj the new upstream for the aspectj-maven-plugin

2021-05-27 Thread Olivier Lamy
Hi Ben
Good to see people interested in maintaining the project.
Sorry I do not read every github issue etc (too much of of spamming
these days with too many notifications)
Asking on the mailing list is definitely the best option (or ping directly
people)
You should have received an invite.
welcome
cheers
Olivier


On Thu, 27 May 2021 at 15:55, Ben M.  wrote:

> Hello everyone,
>
> looking at [1] and these forums, I see that mojohaus failed to invite new
> committers which (sadly) led to a fork and then yet another fork.
> Since no other action has been taken, I suggest giving up (i.e. archiving)
> the aspectj-maven-plugin from mojohaus after doing a relocation.
>
> If you do have concerns, please respond with an appropriate message. I do
> understand that the process of forking a project twice without receiving an
> invitation must have been an exhausting process.
>
> - Ben
>
>
> [1]: https://github.com/dev-aspectj/aspectj-maven-plugin/issues/1
>
> --
> You received this message because you are subscribed to the Google Groups
> "mojohaus-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mojohaus-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mojohaus-dev/76ff29c2-ef89-42e9-98d2-ed34db42f3ecn%40googlegroups.com
> 
> .
>


-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

-- 
You received this message because you are subscribed to the Google Groups 
"mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mojohaus-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mojohaus-dev/CAPoyBqTOUxkYqNMvii_-zzbN6uvDPHra5GewT%2BAmnOB2Ej8jLQ%40mail.gmail.com.