Community
Participate
Working Groups
Mylar update site should link to companion update sites, such as Subclipse and Subversive integrations as well as other 3rd party connectors. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=165581#c22 PS: Mik, here is what Mike meant. I can't copy direct link to your comment from Bugzilla editor and I can only link to the web UI from here.
Do you have an update site for me to link to, e.g. a Subclipse one? I might also be able to try with the subversive one.
Hey! It takes several days to you to review and apply some tiny patches and I had only few hours since you resolved API issues in a team... I am not that fast. Anyways, I guess Subclipse update site is going to be at http://subclipse.tigris.org/update_1.2.x
Yes, sorry, was not meaning to imply that you could get this turned around instantly.
(In reply to comment #3) > Yes, sorry, was not meaning to imply that you could get this turned around > instantly. You don't have to be sorry. I am not as sensitive as you know who. Just being cheeky as usual. :-) Besides, you can still use subversive update site as a playground...
We can still try to have this for 1.0, or to update the site.xml file shortly thereafter, but first we need to ensure that the Subclipse and Subversive sites work standalone.
If Mylar links to other 3rd party connectors, we would like if our connector from update site: "http://www.trackplus.com/files/update-site/e3.2/trackplus-mylar" might be refered also.
Update sites for the beta version of Codebeamer repository connector is available: http://cbconnector.javaforge.com/update/codebeamer-3.2 http://cbconnector.javaforge.com/update/codebeamer-3.3
(In reply to comment #6) > If Mylar links to other 3rd party connectors, we would like if our connector > from update site: > "http://www.trackplus.com/files/update-site/e3.2/trackplus-mylar" > might be refered also. You may also want to add a note about your connector to http://wiki.eclipse.org/index.php?title=Mylar_Integrators .
This did not make into Friday's 2.0M1 update site because we need to give integrators a chance to move to the 2.0M1 APIs if they choose to do so (I plan on sending out the porting email by tomorrow). Adrian: please consider expanding on the Trac+ entry that Steffen added.
I added entries for each of the tools mentioned on the bug to following page, now linked from our navigation bar: http://wiki.eclipse.org/index.php/Mylar_Extensions Each contains an update site. Could everyone CC'd please make sure that their update site and description are correct or update as necessary?
Mik, we can probably maintain a separate aggregating update site that can link those external update sites together in one place.
Eugene: that sounds good to me, at least to start. Do you want to take a stab at creating it?
Here you are: <?xml version="1.0" encoding="UTF-8"?> <site associateSitesURL="http://download.eclipse.org/technology/mylar/extensions/associateSites.xml"> </site> and associateSites.xml look something like this: <?xml version="1.0" encoding="UTF-8"?> <associateSites> <associateSite label="Subclipse 1.2.x" url="http://subclipse.tigris.org/update_1.2.x/"/> <associateSite label="Subversive" url="http://www.polarion.org/projects/subversive/download/1.1/update-site/"/> <associateSite label="Maven Integration" url="http://m2eclipse.codehaus.org/update/"/> <associateSite label="Maven Integration (dev)" url="http://m2eclipse.codehaus.org/update-dev/"/> <associateSite label="PyDev" url="http://pydev.sourceforge.net/updates/site.xml"/> <associateSite label="CodeBeamer Repository Connector for Eclipse 3.2" url="http://cbconnector.javaforge.com/update/codebeamer-3.2/"/> <associateSite label="CodeBeamer Repository Connector for Eclipse 3.3" url="http://cbconnector.javaforge.com/update/codebeamer-3.3/"/> <associateSite label="Track+ Repository Connector" url="http://www.trackplus.com/files/update-site/e3.2/trackplus-mylar"/> </associateSites>
To do this effectively we will need to start a process similar to the Europa release train, where integrators are responsible for updating their associated sites to ensure that they support the corresponding version of Mylar. I plan on posting a proposal for this next week and would like to have the departure of the train be the 2.0 release.
It turns out that are legal implications to doing this on eclipse.org. We are exploring how best to do this, but might not have it resolved by June 29th. I'd like to do it as soon as possible after the 29th and if we can't make it happen on eclipse.org for that time it might make sense to prototype it on an external site until we can move it to eclipse.org.
For the time being we are supporting pointing to other update sites via the Mylyn Extensions page: http://wiki.eclipse.org/index.php/Mylyn_Extensions
As per comment#15, we have done what we can here via the Mylyn Extensions page, since we can't link non-eclipse.org content.
Interested parties should look into the new discovery UI: http://wiki.eclipse.org/Mylyn/Discovery Mylyn Discovery is included in Galileo.
