Re: [epsilon-dev] Update site now includes all dependencies!

[Sina Madani <sinadoom@xxxxxxxxxxxxxx>]

Hi Antonio,

 

Good point! At the time I was trying so many things and most of them didn’t work, so I presumed the same would be true for sites added to category.xml. I’ve also referenced some sites in feature.xml of some projects: presumably this is redundant? I’ll give it a go anyway. However for the Oomph setup I think they still need to be explicitly declared, so at a minimum we need to maintain setup file and category.xml for users, and the target platform for developers.

 

Thanks,

Sina

 

From: Antonio Garcia-Dominguez
Sent: 18 April 2020 09:01
To: Epislon Project developer discussions
Subject: Re: [epsilon-dev] Update site now includes all dependencies!

 

Hi Sina,

 

I was going to suggest using the "Repository Properties" tab of the category.xml editor, adding "Additional Repositories" entries. In fact, we already do that for Emfatic.

 

Those sites will be automatically added when the user loads our update site for the first time - the user has the convenience of getting everything working in one go, and our update sites will take up less space in download.eclipse.org. Users will also be able to get updates of those third-party projects without us having to rebuild the update site.

 

Best,

Antonio

 

On Thu, 9 Apr 2020 at 17:28, Sina Madani <sinadoom@xxxxxxxxxxxxxx> wrote:

Hi everyone,

 

I’ve recently been spending a lot of time to get the update site in good shape – specifically, to resolve dependencies without the user having to manually add repositories or install them. After a lot of headscratching and scouring mailing lists, forums and Bugzilla, the solution was actually relatively simple. https://download.eclipse.org/epsilon/interim/ is now a P2 repository, built using the eclipse-repository Tycho packaging in org.eclipse.epsilon.updatesite.interim’s pom.xml. So, we don’t need to ask users to add update sites to their list.

I propose that we update the website to remove links to dependencies to simplify maintenance and keeping things up to date.

There are now “only” two places we need to declare external dependencies: in the target platform and in epsilonUse.setup.

 

Thanks,

Sina

 

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

 

--

Antonio Garcia-Dominguez