[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [emf-dev] Publishing to Maven Central
|
Hi
Eclipse-SourceReferences is another thing I do not understand. I would
expect a standard Buckminster step to do it automatically. IIRC I found
settings that should configure it, but David's reports always list my
projects as non-compliant.
I'm not suggesting one standard account. However I am arging that e.g.
org.eclipse.ocl be initially created by EF IT so that they have a
password, and then they create additional users for releng committers.
Regards
Ed Willink
On 18/12/2016 00:57, Stephan Herrmann wrote:
On 12/16/2016 04:24 PM, Ed Willink wrote:
Hi Stephan
Once someone provides/advertises a ?CBI? wiki page that explains
exactly how to follow the "just one step", I will endeavour to
follow it for my projects. However migration from Buckminster to
Tycho is still on my to-do list.
Nothing of what I do requires tycho, currently.
Need a p2 repo as input plus calling cbi aggregator
+ a few shell scripts for preparation.
The final steps I cannot yet tell :)
Ah, you should set Eclipse-SourceReferences for easy processing,
but you should do that for SimRel anyway :)
If a standard account at OSSRH is required, then I could argue that
EF IT should create it, since EF IT should be able to step in
and maintain it in extremis. EF IT could create corresponding releng
accounts, perhaps requiring a first time password definition by
the true user.
The accounts must be per groupId (required by OSSRH)
- so one standard account won't cut it,
you'll need your own org.eclipse.ocl account or such.
Then the account will be tied to a HIPP
from where the actual publishing will happen.
Good to know there's s.o. who will proof read,
once we put our experience in the wiki :)
best,
Stephan
_______________________________________________
emf-dev mailing list
emf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/emf-dev
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
