In the .psf file, it looks like the svn plugin is specified in the provider element. Can a .psf file contain multiple provider sections (one for each plugin that people use)?
>>> Valery Kokhan <vkokhan@xxxxxxxxxxxxxx> 12/11/07 4:36 PM >>>
It is not a problem to add .psf autogen capabilities to higgins2ant. The problem is that there is no standard Eclipse plugin to work with svn repository and in case we need .psf files we have to agree which plugin we all using to access svn because content of .psf files depends on that directly.
Another way to get all required sub-projects is to generate 'configure' target to our build scripts as it was proposed by Jim earlier but in this case we also need to make sure that everyone who want use this target has the same svn ant task installed.
From my point we should have both .psf and 'configure' target in build scripts because this will allow people to get what they need regardless of their preferred working environment.
Valery
Wednesday, December 12, 2007, 1:08:40 AM, you wrote:
> I will remove all of the old .psf files this week. Let?s see if folks start > asking for them again. If they do, let?s have higgins2ant autogen them as > you suggest.
> -Paul
> ________________________________________ > From: higgins-dev-bounces@xxxxxxxxxxx > [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Jim Sermersheim > Sent: Tuesday, December 11, 2007 6:04 PM > To: Higgins ((Trust Framework)) Project developer discussions > Subject: Re: [higgins-dev] Updating .psf to SVC locations
> I think we need to update any .psf files we have for deployments (I've done > this for the idas simple deployment), and that maybe we need a master .psf > for all current higgins projects.
> Aside from that, should we remove the old .psf files? I think many people > directly checkout projects from the SVN repository now that our project > names are the same as the leaf directory names in the repository.
> If we do want to keep .psf files for each project, maybe Valery can update > higgins2ant to make it auto-gen them. That way each .psf can include all of > its dependency projects as well.
> Jim
>>>> Phil Hunt <phil.hunt@xxxxxxxxxx> 12/08/07 3:44 PM >>> > I notice many, if not all, of the psf files are referring back to the CVS > repository. Will this be updated to the new SVN locations? > Phil Hunt > Oracle
> _______________________________________________ > 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
|