directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot">
Subject Re: [Studio] Mavenization status - Remaning issues
Date Wed, 30 Jan 2008 13:04:41 GMT

I posted the mail on the maven ML, but there's no real answer at the moment.
I'll keep you informed...

I finally found out what why our application was not launching correctly.
The renaming of the RCP plugin as '' was the
I fixed it.

I have created a new branch in SVN (
where we are going to mavenize the current trunk (and its eventual updates).
Felix's sandbox is now getting out of date from the trunk, and with the
reorganization of the folder that has been made, i would be very difficult
to port the commits done after the last update.
Now that we have a build working (except for the location of the final maven
repository and the repackaging issue), I thought it would be easier to try
to mavenize the trunk than to try to update the mavenized version we have in
Felix's sandbox.


On Jan 29, 2008 5:09 PM, Felix Knecht <> wrote:

> Pierre-Arnaud Marcelot schrieb:
> > In a recent talk with Emmanuel, we've come to the conclusion that the
> > use of the <> server to store
> > our Studio Maven Repository is not the appropriate solution.
> > Emmanuel thinks, and I think he's right, that
> > <> is not prepared to handle the load of a Maven
> > repository.
> > We need to find a correct place for it.
> Yes.
> >
> > I'm going to prepare a little summary of what we're doing to mavenize
> > Studio and send it to the Maven users' mailing list to ask their help on
> > where to store this repository.
> Thanks. They do already have something there, but it's only for eclipse
> 3.2 and we want to use eclipse 3.3.
> Good luck :-)
> Felix

View raw message