Re: FW: [eclipselink-dev] Why need to change build pathofeclipselink.sdo

[Tom Ware <tom.ware@xxxxxxxxxx>]

There is not currently one.

When we have completed the Orbit move, there will be several more automated ways 
to get the bundled files from Orbit.

1. Ant will download the jar files for the dependencies
2. An update site will be available to get the dependencies
3. With Eclipse Galileo, nearly all dependencies will be available as part of 
your Eclipse Install.

If you do not want all the projects for dependencies in your workspace, you 
should be able to get the jars from our "plugins" download and put them in your 
Eclipse dropins directory.  (I have not tried this, but can see no reason why it 
would not work)

Sebastien Tardif wrote:
> Do we have an Ant or Maven task to get most of the Orbit bundles needed?
> Should we?
>
> -----Original Message-----
> From: eclipselink-dev-bounces@xxxxxxxxxxx
> [mailto:eclipselink-dev-bounces@xxxxxxxxxxx] On Behalf Of Sebastien
> Tardif
> Sent: Thursday, April 30, 2009 1:10 PM
> To: Dev mailing list for Eclipse Persistence Services
> Subject: RE: [eclipselink-dev] Why need to change build
> pathofeclipselink.sdo.testfrom [javax.activation] to[javax.activation
> 1.1.0] ?
>
> I get it. I was confused by seeing a project in the workspace named
> [javax.activation] but eclipselink.sdo.test depending instead on
> [javax.activation 1.1.0].
>
> The answer seems to be this sentence from
> http://wiki.eclipse.org/EclipseLink/Building:
>
> ->>Note: The above libraries will eventually be removed from our SVN
> repository and only available from Orbit<<-
>
>
> -----Original Message-----
> From: eclipselink-dev-bounces@xxxxxxxxxxx
> [mailto:eclipselink-dev-bounces@xxxxxxxxxxx] On Behalf Of Tom Ware
> Sent: Thursday, April 30, 2009 10:36 AM
> To: Dev mailing list for Eclipse Persistence Services
> Subject: Re: [eclipselink-dev] Why need to change build path
> ofeclipselink.sdo.testfrom [javax.activation] to [javax.activation
> 1.1.0] ?
>
> Hi Sebastien,
>
>    Are you getting javax.activation from our SVN repository or from
> Orbit?
>
>    We are in the middle of a transition to use Orbit to get all the
> dependencies 
> we share with other Eclipse projects.  There is some info here:
>
> http://wiki.eclipse.org/EclipseLink/Building
>
>    The projects are set up to work with the projects from Orbit.
>
>    We have seen some issues where Eclipse itself does not pick up name
> changes 
> like the one above in some versions on refresh.
>
> -Tom
>
> Sebastien Tardif wrote:
> > I'm learning slowly how to compile and run tests of EclipseLink.
> >
> > I have recent code and by default, project eclipselink.sdo.test is
> > complaining that the build path is not right, not finding
> > [javax.activation], so I had to change the "Projects" in "Java Build
> > Path" from [javax.activation] to [javax.activation 1.1.0] to get it to
> > work. 
> >
> > Is it really the step needed? That doesn't sound right.
> > _______________________________________________
> > eclipselink-dev mailing list
> > eclipselink-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev