[Building Sakai] Eclipse Ganymede 3.4.2 - Anybody Using This For Sakai? ( the real post )

[Steve Swinsburg]

Hi Charlie,

Thats the way I do it and it works well for me. Saves having a billion
projects in Eclipse. As for classpaths, your standard mvn eclipse:clean
eclipse:eclipse -DdownloadJavadocs=true inside a project's directory should
do the trick. Sometimes it's necessary to manually resolve some dependencies
to keep Eclipse happy, which just means going Build Path > Configure Build
Path > Add Variable > choose M2_REPO > Extend > Find the jar in your repo.

cheers,
Steve

On Wed, Nov 18, 2009 at 2:37 PM, Charlie Macchia
<cmacchia at brainovision.com>wrote:

>  Thanks Steve!
>
> It never dawned on me that I could just leave stuff out of eclipse that I
> didn’t want to mess around with, and only import the things I do! (have
> maven do the full build if necessary)
>
> So that’s a good one.
>
> I’m not sure how to regenerate the Eclipse metadata to set the appropriate
> classpaths – the web suggests something like this:
>
> eclipse -application
> org.eclipse.equinox.p2.metadata.generator.EclipseGenerator <insert your args
> here >
>
> Wondering what args I should typically be sticking in there for sakai?
>
> Thanks
> Charlie
>
>
>
>
>
>
> On 11/17/09 8:01 PM, "Steve Swinsburg" <steve.swinsburg at gmail.com> wrote:
>
> Hi Charlie,
>
> I use Ganymede and all is well. Galileo is not compatible with some plugins
> I use. However, I don't import all source into Sakai, I've no need for that
> and just pull in what I do need. It's not essential to developing. Have you
> regenerated the Eclipse metadata to set the classpaths? Also, they'll be
> pointing to your M2_REPO so you'll need to have built Sakai in order for it
> to find the artifacts there.
>
> cheers,
> Steve
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20091118/61dbec16/attachment.html