Here is a patch to fix the bug in 0.5RC1.  I managed to get this to
work eventually.

Mark.


### Eclipse Workspace Patch 1.0
#P ant4eclipse
Index: source/net/sf/ant4eclipse/ant/task/pde/BuildFeatureTask.java
===================================================================
RCS file: 
/cvsroot/ant4eclipse/ant4eclipse/source/net/sf/ant4eclipse/ant/task/pde/BuildFeatureTask.java,v
retrieving revision 1.17.2.3
diff -u -r1.17.2.3 BuildFeatureTask.java
--- source/net/sf/ant4eclipse/ant/task/pde/BuildFeatureTask.java        19
Dec 2007 22:57:06 -0000 1.17.2.3
+++ source/net/sf/ant4eclipse/ant/task/pde/BuildFeatureTask.java        11
Sep 2008 18:29:41 -0000
@@ -217,7 +217,7 @@
    * @see org.apache.tools.ant.Task#execute()
    */
   public void execute() throws BuildException {
-    if (isFeatureSet()) {
+    if (!isProjectSet() && isFeatureSet()) {
       requireWorkspaceSet();
       requireFeatureSet();
     } else {




On Thu, Sep 11, 2008 at 1:03 PM, Mark Melvin <[EMAIL PROTECTED]> wrote:
> Also - is the HEAD revision of the project supposed to build?  I was
> going to see if this was fixed in the latest code, but checking out
> all the source results in compilation errors due to missing methods on
> the Workspace interface.
>
> m.
>
> On Thu, Sep 11, 2008 at 12:49 PM, Mark Melvin <[EMAIL PROTECTED]> wrote:
>> Hi there,
>>
>> I am trying to get the buildFeature task to work with an automated
>> build system.  It is failing with the message "workspace has to be
>> set!", even though I am calling it with the "project" attribute set.
>> Looking at the source I believe this is because I don't have an
>> "actual" workspace in the location specified, but I shouldn't need on,
>> should I (I don't seem to need it for the buildProject task to work)?
>> Otherwise I don't see how this will ever work in command line mode
>> outside of Eclipse where you do not have a workspace.
>>
>> On a related note - I have tried everything I can think of to turn on
>> "tracing" in ant4eclipse.  Based on other posts I have read, I thought
>> you just had to set the magical properties ant4eclipse.trace and/or
>> ant4eclipse.debug and run Ant with -debug or -verbose, but none of
>> that appears to work.
>>
>> Thanks for the help,
>> Mark.
>>
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Ant4eclipse-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ant4eclipse-user

Reply via email to