> Will you upload the bundles in our google repository as well? Or do you
> want me to do this?
>
I'm not sure what you are referring too. I don't need to upload anything
to code google to make my workbench setup work because I'm fetching
stuff using HTTP from various locations.
I was referring to the eclipse core, SWT and runtime (probably others) bundles. They need to be in some maven repository (like the one we currently host on code.google), so maven is able to retrieve them.
Another way to do this is maybe create an ant-script that fetches the bundles from a local Eclipse RCP target and moves this to a local maven repository (default <home>/.m2/repository). This is probably better, what do you think?
>
>
> The only part of our project that needs a patched version of databinding
> is the GWT stuff because some parts don't compile.
>
> That's what I was thinking.
>
>
>
> When repacking stuff for maven please use our code-google repo and don't
> submit any external code to our Eclipse-Repo. Ideally we consume
> packages from Eclipse-Orbit.
>
> That's what we always did, right?
> Orbit is cool, I guess. But I wonder if we can use this as a maven
> repository. Given its structure, I guess not :( Or do you have any ideas
> on this?
>
When we want to ship something we only have approval for the stuff in
Orbit and so we should not fetch the stuff from somewhere but reuse
what's there already.
I guess the only thing missing to use the orbit stuff is to write the
pom.xml to fetch it but I might be mistaken.
True, but currently we repackage our dependencies ourselves using felix, which is a good strategy, I think, since not all our dependencies are available in Orbit (like miglayout, swingx, ...)
