IvyDE and Ivy share styles. These are not necessary for builds (at least, from what I saw with IvyDE), but it sure helps to be able to get the look and feel.
It seems sensible to me to have separate repos for site sources, one per project, and another repo for publishing which would aggregate built sites and all releases for all projects (that's how IvyDE builds work, AFAICS). Gintas 2016-12-19 12:41 GMT+01:00 Stefan Bodewig <bode...@apache.org>: > On 2016-12-15, Gintautas Grigelionis wrote: > > >> 2016-12-15 8:43 GMT+01:00 Stefan Bodewig <bode...@apache.org>: > > >> https://github.com/apache/ant-ivy-site-styles is a very curious case as > >> it claims to mirror a repository that doesn't exist (I wanted to > >> manually push the svn files there but fail to find the repository). > > >> It would be good if anybody could ask INFRA in order to figure out what > >> exactly the repo is mirroring as I don't see anything matching at > >> https://git-wip-us.apache.org/repos/asf - I'll do so myself at the > >> weekend, if nobody else finds time before that. > > > Great! May I suggest adding repos ant-site-sources, ant-ivy-site-sources, > > ant-ivyde-site-sources and ant-site (for publishing using the git > workflow)? > > Not exactly weekend anymore :-) > > https://github.com/apache/ant-ivy-site-styles and > https://github.com/apache/any-ivy-site-styles > > seem to be the same and neither has ever been requested by us AFAICT. > > Assuming we wanted to restructure the site stuff, what would it look > like? > > Do we want to move to git? All of it or just parts? How many repos do we > want to use (a single one as we do right now, or one for Ant+antlibs and > several for Ivy and IvyDE)? I'm not familiar with how the Ivy and IvyDE > sites get built. > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > >
