Hi all, So, what is the way forward? Is that till we have the feature Graham is working on (downloading eclipse jars from links like http://download.eclipse.org/eclipse/downloads/drops/R-3.2.1-200609210945/) we have to download those jars seperately from those urls and may be put in the project's lib dir and then bundle our RCP apps for distribution?
For things like eclipse plugin jars, who is supposed to be taking care of having updates jars in the maven repo? - is it the specific project team (like eclipse project people), who should take care of it or - it the maven team or - projects which need to use them should follow some process to get it in the maven. I don't this is the option as it will make things messy and inconsistent versions in the repo. Regards, Bhupendra On 12/19/06, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
On 12/19/06, Graham Leggett <[EMAIL PROTECTED]> wrote: > On Tue, December 19, 2006 10:24 am, [EMAIL PROTECTED] wrote: > > > =8*O I beg your pardon? I looked in JIRA but couldn't find a report about > > this. Is there? If not, I'd open one. ;-) > > > > The idea that you'll never have to fix a broken POM/JAR/whatever is just > > ridiculous. :-) As I understand it, the repo admins are just very > > reluctant to modify already published artefacts. > > That's what I meant, yes. > > As it turns out, someone has already published the full eclipse tree to > repo1, so all this is moot :) > No it's not - the Eclipse artifacts are published to a separate repository and are not yet integrated into the main repository. > Regards, > Graham > -- > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
