Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [higgins-dev] RE: IdAS automated build target

Replies inline


From: higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Jim Sermersheim
Sent: Wednesday, October 18, 2006 1:13 PM
To: 'Higgins (Trust Framework) Project developer discussions'
Subject: [higgins-dev] RE: IdAS automated build target

 

<resending to include higgins-dev>

 

My goals would include:

 

- The ability of a non-eclipse developer to get the source and build it.

- The ability for us to add whatever ant task we think we want to (right now, there's a javadoc target, using the javadoc ant task, in the future, we may want others).

- Not having to visit two build interfaces to keep things in sync

 

I agree that this would be great. We’ll see how close to this goal we can get.

 

(Note that some people like to get the source tree and just run "ant jar" or "ant test" or "ant javadoc" from the command line.)

 

Is full ant functionality surfaced through the IDE? 

 

Not in the way I think you mean. There are GUIs to configure eclipse plug-in projects that are pretty extensive. Eclipse folks just let the GUI create the internal Ant scripts for them. And I’m not sure what one would like to do *within the Eclipse way of doing things* that can’t be done with the GUI.

 

 Last time I used the internal IDE builders, I couldn't do what I wanted, but I'm not very experienced.  OTOH, I haven't yet seen an ant task which can produce an eclipse plugin either.

 

If one really wants to build an Eclipse plug-in externally using Ant, there is a feature in the IDE to export the build.xml for that plug-in. But folks hardly ever do it.

 

In the Bandit project, we've used an Ant script and made the eclipse IDE use that ant script (by using an external tool builder and turning off the Java builder). We have not, however built an eclipse plugin this way.

 

Yes, Eclipse has an Ant editor/parser and puts some GUI sugar around existing Ant scripts. Lets you run their various targets from the GUI in the same VM or in a separate one, etc.

 

Jim

>>> "Paul Trevithick" <paul@xxxxxxxxxxxxxxxxx> 10/17/06 2:39 PM >>>

 

Jim,

Once you have defined an Eclipse plug-in in the IDE's GUI, it generates and consumes Ant scripts internally to do its building. With one click you can also export the otherwise hidden build.xml, but that starts to defeat the whole IDE/GUI thing.

-Paul


From: Jim Sermersheim [mailto:jimse@xxxxxxxxxx]
Sent: Tuesday, October 17, 2006 4:31 PM
To: 'Valery Kokhan'; Paul Trevithick
Cc: 'Higgins (Trust Framework) Project developer discussions'
Subject: Re: IdAS automated build target

 

Yes, I recall similar goals.

 

The ant script  has these targets:

clean

compile

jar

javadoc

 

I would prefer if we could work it out so we retain the functionality of the ant script while also providing the eclipse plugin target.  In my mind, it would be ideal if this could be just another ant target.  Does anyone know if there's an ant task for building eclipse plugins?

 

Jim


>>> "Paul Trevithick" <paul@xxxxxxxxxxxxxxxxx> 10/17/06 12:39 PM >>>
Valery and Jim,

My recollection of last Thursday's conversation is that we want to start off
building two different targets for IdAS (not including javadoc and testing):

- vanilla JAR (Jim already has the Ant script for this)
- Eclipse plug-in

Is that right?

-Paul


Back to the top