Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [embed-cdt-dev] Prepare for first incubation release
Hi Liviu,

That is a great update. This combined with some progress on CQs is a step in the right direction.

Answers below.
~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Tue, 7 Apr 2020 at 10:10, Liviu Ionescu <ilg@xxxxxxxxxx> wrote:
I managed to update the eclipse-plugin.git repo to include both the changes that were performed on the embed-cdt branch (mainly license updates) and the few bugs that were fixed in the latest release.

Unfortunately, since the changes in embed-cdt included a major folder rename, and in these folders there were some submodules, that was probably a a bit too much for git, so that regular merges, and even cherry picking, failed with weird errors, so I had to manually re-do the bug fix commits.

Anyway, now the develop branch is again up to date, and I was able to run a successful maven build.

The result, after installing on a fresh 2020-03 Eclipse CDT, looks like this:


That looks good in the install details.

 


I already added the '(incubation)' notice; I hope that it is ok.

Yes, very good.
 

Next I'll try to update the few JARs that need to match the versions available in Orbis.

OK. Let me know if you need help in this area, especially if you want/need new JARs in Orbit itself to consume. Using Orbit is great because it is one of the conditions of joining simrel.
 

---

Then we need to decide on the location where to publish the plug-ins.

Here is where you publish to: https://download.eclipse.org/embed-cdt/ - indeed Project Handbook says:

"[...] where technically sensible—the Eclipse Foundation-provided infrastructure must be considered the primary source of project downloads."

But you can publish (in addition) to whereever you want as the first part of the above quote is:

"Project artifacts (e.g. downloads) can be distributed via third party services (e.g. Maven Central)" 

Once again, to join SimRel (I believe) it needs to be on https://download.eclipse.org/embed-cdt/.
 

The current URLs for the p2 sites are:

http://gnu-mcu-eclipse.netlify.com/v4-neon-updates-experimental/

The archives with all previous releases are available from:


And the EPP packages are available from:



I would continue to publish the individual archives in the same eclipse-embed-cdt/eclipse-plugins/releases/ location, since I never had issues with it.

For the EPP releases, since I have no idea yet how much effort would be to join the simrel program, I would transfer the existing org.eclipse.epp.packages to eclipse-embed-cdt and continue to publish the releases there, at least for a while.

The only obvious change is the url of the p2 site, which I'd like to move somewhere to eclipse.com/embed-cdt.

Current https://eclipse.org/embed-cdt points to https://projects.eclipse.org/projects/iot.embed-cdt which has a standard Downloads page you can add links, etc to. Either way, the link can/should be to https://download.eclipse.org/embed-cdt/

(Note your link said eclipse.com which I assume was a typo)
 

Since the structure with 3 separate folders (main + test + experimental) proved useful, I'd like to preserve it.

The 'v4-neon' prefix was added when v4 was released, to make explicit that the plug-ins run only on neon and up.

Now the version was bumped to v5.x, and the plug-ins still run on neon and up. Since I understood that Eclipse will move to Java 11, and there will probably be several more updates, possible incompatible, perhaps we should prepare for multiple download urls.

---

Jonah, since you have a thorough knowledge how these things work within Eclipse, could you suggest how to proceed?

I hope I have answered the open questions - please follow up if not.
 



Regards,

Liviu




_______________________________________________
embed-cdt-dev mailing list
embed-cdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/embed-cdt-dev

Back to the top