RE: [higgins-dev] STS Build Instruction Notes

[Michael McIntosh <mikemci@xxxxxxxxxx>]

> > 1. We need an all encompassing psf file which gets all of the required 
STS
> > components at once.

I update the page with a single PSF, I'd thought Jim had done that in the 
F2F meeting.

> > 2. Complete the STS dependencies page so we know where to go to get 
the
> > dependant jars and the correct versions.  Not all dependencies are 
listed.
> > What other jars do we need and how do we get them?

Part of the build problems for STS are that there is no link anymore to 
download Axis 1.3. I've had to link to a planned but not ready Orbit Axis 
Package.
I've just converted and tested with Axis 1.4 so there is now a link I can 
point to to get the set of Axis 1.x libs. I'll update the component page 
with that information (Axis 1.4 libs and links).

> > 3. Actualize the instructions page.

I will also take care of this.

> > 4. Where do the dependant jars belong in the file system?

Agree with Paul, we should change from current variable based approach to 
putitng them under the project lib directory.
I'll take care of this.

I am splitting my time today between a meeting and doing these tasks. Will 
send notes to the list as each of these if finished.

Thanks,
Mike


higgins-dev-bounces@xxxxxxxxxxx wrote on 01/31/2007 06:49:43 PM:

> Sorry, Spanish brain cramp ...  actualizar == to update, bring up to
> date ... actualize == to realize in action or make real.  The latter
> could apply but I meant "bring up to date".  Sorry, still learning 
> English!  ;)
> 
> Tom
> 
> >>> "Paul Trevithick" <paul@xxxxxxxxxxxxxxxxx> 01/31/07 9:16 AM >>>
> 
> 
> Tom wrote:
> > 
> > Mike,
> > 
> > Mostly, my notes came down to dependencies, actualizing the 
instructions,
> > and creating a single psf file to get started.  I haven't tried an ant
> > build yet and there may be more notes there.  Also, do we have 
deployment
> > instructions?  That'll be next for me.
> > 
> > 1. We need an all encompassing psf file which gets all of the required 
STS
> > components at once.
> 
> Yes. I would say it this way: all sub-projects of the Higgins Token 
Service
> component. The Token Service now has a separate table here
> (http://wiki.eclipse.org/index.php/Components) that shows a total of 6
> projects. 
> 
> > 2. Complete the STS dependencies page so we know where to go to get 
the
> > dependant jars and the correct versions.  Not all dependencies are 
listed.
> > What other jars do we need and how do we get them?
> > 3. Actualize the instructions page.
> 
> I presume you mean the "ide" and "cli" links pages (and thereby getting 
rid
> of the current "instructions" link) shown here
> http://wiki.eclipse.org/index.php/Components 
> 
> > 4. Where do the dependant jars belong in the file system?
> 
> If they are third party and have been approved you have some choices: 
The
> easiest/quickest thing to do is to just copy them into the "libs" 
subfolder
> of each Higgins Eclipse project needs. (See better options in 5. below)
> 
> > 5. Easier ways to get dependant jars for any higgins project?  Is that
> > what Orbit is for?
> 
> In the long run we will probably want to wrap each separate third party
> lib/jar as a separate Eclipse plugin project. This is the "Eclipse Way"
> because it provides the power of the extra metadata in the project's
> manifest to help other projects that are dependent on this one manage
> version compatibility.
> 
> And in the long run for any third party lib/jars that are of interest to
> other projects (beyond Higgins). That is, the fairly generic ones, we
> should, as Mary said, check them into Orbit.
> 
> 
> _______________________________________________
> higgins-dev mailing list
> higgins-dev@xxxxxxxxxxx 
> https://dev.eclipse.org/mailman/listinfo/higgins-dev
> _______________________________________________
> higgins-dev mailing list
> higgins-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/higgins-dev