Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [higgins-dev] fixing the component row templates

Peter, that looks good, but it does still require the user to download and interface with the auto project, as well as add the jars in step 5.


I was hoping that a user could simply download a package (whether it's a component or a deployment) and do this:


ant configure

ant build


Is it possible to get to this point?  I tried doing something like this at one point, but got derailed when we were trying to decide whether to use Orbit or not.


Jim



>>> Peter Kimlach <pkimlach@xxxxxxxxxxxxxx> 11/19/07 6:46 AM >>>
Hi Jim,
I wrote ant script that fetch project and its all dependencies into some
specified folder on local machine. After that script complete its work
projects simply may be added into eclipse workspace (new or existent).
How to use it you may find on this page
http://wiki.eclipse.org/SAML2_IdP_Deployment#Check_out_sources_automatically
. I think it can help you with fetching.
Peter

Paul Trevithick wrote:
>
> Jim wrote:
>
> I had hoped we'd have some kind of configure target in build.xml by
> now that would fetch the dependencies for a project. Do you know if
> anyone is working on that? If we had that, then I don't think we'd
> need the dep links/pages anymore.
>
> Jim, I think Peter will start work on this as soon as he completes the
> new download pages (pages that will include not just nightly builds
> but the stable build for 1.0M9, etc. as I mentioned below). See the
> one and only task here
> <http://wiki.eclipse.org/Build_Enhancements#Eclipse_Developer_Builds>
> -- I think is Peter’s highest priority.
>
> *Peter*,
>
> Please edit this task description and elaborate on it as necessary and
> then copy the corrected/elaborated task description in a new bugzilla
> item for this task.
>
> -Paul
>
> Jim
>
>
> >>> "Paul Trevithick" <paul@xxxxxxxxxxxxxxxxx> 11/17/07 8:56 AM >>>
>
> Jim,
>
> First, I want to say thanks very much for doing this. Looks great.
> [BTW, a nit: as soon as Peter completes his work we’ll change your
> “nightly build” link to “download” or “builds” or something because
> the new page will contain the nightly build, the stable build, the
> release 1.0 build (!), etc.]
>
> What do you think we should do about the dep link and wiki pages?
>
> Valery or Peter
>
> I notice that iss and iss.cardspace’s “nightly build” links in the
> Downloads page don’t work. Any ideas?
>
> -Paul
>
> First, I want to say thanks very much for doing this. Looks great.
>
> What do you think we should do about the dep link and wiki pages?
>
> Val
>
> ------------------------------------------------------------------------
>
> *From: *
>
> higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx]
>
> *On Behalf Of *
>
> Jim Sermersheim
>
> *Sent: *
>
> Saturday, November 17, 2007 12:37 AM
>
> *To: *
>
> higgins-dev@xxxxxxxxxxx
>
> *Subject: *
>
> Re: [higgins-dev] fixing the component row templates
>
> I updated all the tables for y'all. Some of the dependency links are
> broken now. If you care, you can look at an old version of the page like
>
> /http://wiki.eclipse.org/index.php?title=Components&oldid=60587 /
>
> to find your old dependencies and copy them to the new dep page.
>
> Personally, I think the dep column should go away. I mean, the
> dependencies can be generated in a much easier and complete way.
>
>
>
> >>> "Jim Sermersheim" <jimse@xxxxxxxxxx> 11/16/07 7:09 PM >>>
>
> I did some very hacky stuff in the template using default params and
> got it to allow dir=<somedir at the root of the higgins tree>,
> appdir=<somedir under /app>, or plugindir=<somedir under /plugin>
>
> I think people can convert over to the templates now
>
>
>
> >>> "Jim Sermersheim" <jimse@xxxxxxxxxx> 11/16/07 2:17 PM >>>
>
> I took a stab at changing the template to do what we want, and it
> works in sort of a limping way.
>
> I really wanted to be able to have the viewcvs point at the proper
> place regardless of whether the project is under /api, /plugins, or at
> the root. To do that, we need the mediawiki extension ParserFunctions
> loaded.
>
> I logged a
>
> /bug /
>
> but it's one of 84 on the webmaster's plate, so I dont' know how long
> it will take for it to be addressed.
>
> Jim
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> higgins-dev mailing list
> higgins-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/higgins-dev
>  


Back to the top