pluginbuilder-development Mailing List for Plug-in Builder

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hello

Please note that I will be using my new email anu...@li... from now
on.

Kindly update your address book.

Rgds
Anu

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi, Hm, that should work. Anything useful in your log file? Search for "runAutoTests" and you will find something like the following.<div> </div><div>Markus <div><div> &nbsp;&nbsp;&nbsp;&nbsp;[java] -runAutoTests: &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;[mkdir] Created dir: /var/www/buildresults/self/nightly/0.8.0.201002190315NGT/testresults/xml &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] EMMA: collecting runtime coverage data ... &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Deleting directory /var/www/buildresults/self/nightly/0.8.0.201002190315NGT/testresults/xml &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] ~~~~~~~~~~~~ Searching for JUnit 3 test plug-ins. &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Using inclusion regular expression(s): .*(test|tests)$ &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Using exclusion regular expression(s): |^org.eclipse.test$ &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Bundle matches: org.pluginbuilder.core.test &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Found 1 plug-ins. &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] ~~~~~~ Searching for JUnit 3 test classes in org.pluginbuilder.core.test &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Using inclusion regular expression(s): .* &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Using exclusion regular expression(s): .*(WebDavSynchronize_Test|ServerCommunication_Test)$ &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Searching bundleentry://192.fwk873275301/coretest.jar for tests. &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Added test class: org.pluginbuilder.core.internal.BuildConfigPersistency_PDETest &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Added test class: org.pluginbuilder.core.internal.CopyMapFileWriter_PDETest &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] EMMA: collecting runtime coverage data ... &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Added test class: org.pluginbuilder.core.internal.templates.Template_PDETest &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Excluded test class: org.pluginbuilder.core.internal.webdav.WebDavSynchronize_Test &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Added test class: org.pluginbuilder.internal.core.creators.MapFileCreator_PDETest &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Added test class: org.pluginbuilder.internal.core.creators.SvnFetchAllFileWriter_PDETest &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Excluded test class: org.pluginbuilder.internal.core.serverconnection.ServerCommunication_Test &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Added test class: org.pluginbuilder.internal.core.smartproperties.SmartProperties_Test &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Scanned 25 Jar entries. &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Searching bundleentry://192.fwk873275301/lib/easymock.jar for tests. &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Scanned 37 Jar entries. &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Searching bundleentry://192.fwk873275301/lib/commons-io-1.3.1.jar for tests. &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Scanned 69 Jar entries. &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] Searching bundle directory for tests. &nbsp;&nbsp;&nbsp;&nbsp;[java] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[java] The bundle directory of org.pluginbuilder.core.test does not contain any class files. &nbsp;&nbsp;&nbsp;&nbsp;[java] On 19.02.2010, at 21:59, Hugo Corbucci wrote: <blockquote type="cite">Hello everyone, </blockquote><blockquote type="cite">I've been using plugin builder to build my app for about a year and a half. It works great but we're not using the test part since our continuous integration server is service on a windows machine and therefore cannot run plugin tests. </blockquote><blockquote type="cite">I've recently tried to run the build localy on my machine and discovered to my surprise that, although the test task is being run, autotestsuite is not finding any test. </blockquote><blockquote type="cite"> </blockquote><blockquote type="cite">I double checked my test feature to ensure it had all the test plugins for my app. I also double checked the inclusion and exclusion patters for both classes and plugin. </blockquote><blockquote type="cite">They are currently like this: </blockquote><blockquote type="cite">autotestsuite.plugin.inclusions=.*(test|tests)$ </blockquote><blockquote type="cite">autotestsuite.plugin.exclusions=org\.pluginbuilder\..* </blockquote><blockquote type="cite">autotestsuite.class.inclusions=.*Test$ </blockquote><blockquote type="cite">autotestsuite.class.exclusions= </blockquote><blockquote type="cite"> </blockquote><blockquote type="cite">And all our test classes use JUnit 4 and are named ending with 'Test'. Our plugins are all named with 'tests' at the end. </blockquote><blockquote type="cite"> </blockquote><blockquote type="cite">I've tried looking the .log of the testing running excution of eclipse but got nothing from that. It seems things are just fine there. </blockquote><blockquote type="cite">I'm using java 1.5.0 on an OS X machine, eclipse 3.5 and pluginbuilder 0.7. My app is an RCP app and it builds just fine with plugin builder. </blockquote><blockquote type="cite">Any ideas/tips? Any detail I forgot to mention but I should have mentioned? </blockquote><blockquote type="cite"> </blockquote><blockquote type="cite">Thanks, </blockquote><blockquote type="cite">-- </blockquote><blockquote type="cite">Hugo Corbucci </blockquote><blockquote type="cite">CS Grad from 2003 to 2006 </blockquote><blockquote type="cite">CS Master from 2007 to 2010 </blockquote><blockquote type="cite">Cel: (55) (11) 8636 9029 </blockquote><blockquote type="cite">Phone: (55) (11) 2649 8636 </blockquote><blockquote type="cite">Skype user: hugo.corbucci </blockquote><blockquote type="cite">------------------------------------------------------------------------------ </blockquote><blockquote type="cite">Download Intel&amp;#174; Parallel Studio Eval </blockquote><blockquote type="cite">Try the new software tools for yourself. Speed compiling, find bugs </blockquote><blockquote type="cite">proactively, and fine-tune applications for parallel performance. </blockquote><blockquote type="cite">See why Intel Parallel Studio got high marks during beta. </blockquote><blockquote type="cite">http://p.sf.net/sfu/intel-sw-dev_______________________________________________ </blockquote><blockquote type="cite">Pluginbuilder-development mailing list </blockquote><blockquote type="cite">Plu...@li... </blockquote><blockquote type="cite">https://lists.sourceforge.net/lists/listinfo/pluginbuilder-development </blockquote> </div></div></div></body></html>

Hey Markus,
Thanks a lot for trying!

On Sun, Feb 21, 2010 at 12:47 PM, mbarchfe <mba...@go...> wrote:

> No, you do not need a dependency from the autotest plug-in to your plug-in.
> I would suggest that you compare your set-up with the set-up of the example
> application ( http://www.pluginbuilder.org/documentation/example/), maybe
> that sheds some light.
>

I've tried that over and over. Weirdest part is that it was working fine.

> You can also try to start the test installation manually and thereby check
> if all dependencies of your plug-in (the one which contains the application)
> are available. In that case the log file should output more than just the
> "Failed to locate" message.
>

How can I start the test installation manually?
I've tried creating an autotestsuite run configuration on my eclipse also.
It runs the app fine but no tests are run. It just opens the app and stays
there until I close it. Any idea why? Should this be working? Can it be an
indication of why the build is not finding anything?

Thanks,
-- 
Hugo Corbucci
CS Grad from 2003 to 2006
CS Master from 2007 to 2010
Cel: (55) (11) 8636 9029
Phone: (55) (11) 2649 8636
Skype user: hugo.corbucci

Hi Hugo,

> I've tried that before. Used to be "com.o2filmes.storytouch.application" (considering my application extension is defined under my com.o2filmes.storytouch plugin and its id is application). The com.o2filmes.storytouch plugin is included in my core feature which is the first one on the list of features plugin builder should build.
> 
> The weirdest part is that it finds that application to build the product but not when running the tests. I thought about adding this plugin as a dependency for the test feature but it was useless. I keep getting that Failed to locate test application "com.o2filmes.storytouch.application" message.
No, you do not need a dependency from the autotest plug-in to your plug-in. I would suggest that you compare your set-up with the set-up of the example application ( http://www.pluginbuilder.org/documentation/example/), maybe that sheds some light.

You can also try to start the test installation manually and thereby check if all dependencies of your plug-in (the one which contains the application) are available. In that case the log file should output more than just the "Failed to locate" message.

More good luck
Markus

Hello Markus,

I've tried that before. Used to be "com.o2filmes.storytouch.application"
(considering my application extension is defined under my
com.o2filmes.storytouch plugin and its id is application). The
com.o2filmes.storytouch plugin is included in my core feature which is the
first one on the list of features plugin builder should build.

The weirdest part is that it finds that application to build the product but
not when running the tests. I thought about adding this plugin as a
dependency for the test feature but it was useless. I keep getting that
Failed to locate test application "com.o2filmes.storytouch.application"
message.

Out of ideas... :(

Hugo

On Sat, Feb 20, 2010 at 10:28 AM, mbarchfe <mba...@go...> wrote:

> Hi Hugo,
>
> The following line seems critical:
>
>  Failed to locate test application "org.eclipse.ide.ui.workbench"
>
> You should set your RCP application as test application. Just enter it on
> the Test tab of the pluginbuilder editor.
>
> Good luck ;-)
> Markus

-- 
Hugo Corbucci
CS Grad from 2003 to 2006
CS Master from 2007 to 2010
Cel: (55) (11) 8636 9029
Phone: (55) (11) 2649 8636
Skype user: hugo.corbucci

Hi Hugo,

The following line seems critical:

 Failed to locate test application "org.eclipse.ide.ui.workbench"

You should set your RCP application as test application. Just enter it on the Test tab of the pluginbuilder editor.

Good luck ;-)
Markus

[java] -runAutoTests:
     [java]     [mkdir] Created dir: /tmp/pluginbuilder/st/results/testresults/xml
     [java]      [java] Executing '/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/java' with arguments:
     [java]      [java] '-Demma.coverage.out.file=/tmp/pluginbuilder/st/coverage.ec'
     [java]      [java] '-XstartOnFirstThread'
     [java]      [java] '-Xmx512m'
     [java]      [java] '-Dautotestsuite.results.directory=/tmp/pluginbuilder/st/results/testresults/xml'
     [java]      [java] '-Dautotest.debug=true'
     [java]      [java] '-Dautotestsuite.headless=false'
     [java]      [java] '-Dautotestsuite.plugin.inclusions=.*(test|tests)$'
     [java]      [java] '-Dautotestsuite.plugin.exclusions=org\.pluginbuilder\..*|^org.eclipse.test$'
     [java]      [java] '-Dautotestsuite.class.inclusions=.*'
     [java]      [java] '-Dautotestsuite.class.exclusions='
     [java]      [java] '-classpath'
     [java]      [java] '/Users/night/Downloads/eclipse/plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar'
     [java]      [java] 'org.eclipse.core.launcher.Main'
     [java]      [java] '-application'
     [java]      [java] 'org.pluginbuilder.autotestsuite.application.autoTestApplication'
     [java]      [java] '-testApplication'
     [java]      [java] 'org.eclipse.ide.ui.workbench'
     [java]      [java] '-data'
     [java]      [java] '/tmp/pluginbuilder/st/test-workspace'
     [java]      [java] '-os'
     [java]      [java] 'macosx'
     [java]      [java] '-ws'
     [java]      [java] 'carbon'
     [java]      [java] '-arch'
     [java]      [java] 'x86'
     [java]      [java] '-clean'
     [java]      [java] '-consolelog'
     [java]      [java] '-dev'
     [java]      [java] '/Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests/emma.jar'
     [java]      [java] 
     [java]      [java] The ' characters around the executable and arguments are
     [java]      [java] not part of the command.
     [java]      [java] !SESSION 2010-02-19 20:36:02.250 -----------------------------------------------
     [java]      [java] eclipse.buildId=I20090611-1540
     [java]      [java] java.version=1.5.0_22
     [java]      [java] java.vendor=Apple Inc.
     [java]      [java] BootLoader constants: OS=macosx, ARCH=x86, WS=carbon, NL=en_US
     [java]      [java] Framework arguments:  -application org.pluginbuilder.autotestsuite.application.autoTestApplication -testApplication org.eclipse.ide.ui.workbench
     [java]      [java] Command-line arguments:  -application org.pluginbuilder.autotestsuite.application.autoTestApplication -testApplication org.eclipse.ide.ui.workbench -data /tmp/pluginbuilder/st/test-workspace -os macosx -ws carbon -arch x86 -clean -consolelog -dev /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests/emma.jar
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.435
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.gtk.solaris.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.436
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.gtk.linux.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.437
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.motif.aix.ppc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.437
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.motif.linux.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.444
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.cocoa.macosx.x86_64 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.444
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.motif.hpux.ia64_32 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.446
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.cocoa.macosx.ppc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.447
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.447
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.motif.hpux.PA_RISC is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.448
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.motif.solaris.sparc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.449
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.wpf.win32.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.449
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.win32.win32.ia64 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.450
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.carbon.macosx.ppc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.450
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.gtk.linux.ppc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.451
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.gtk.linux.x86_64 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.451
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.cocoa.macosx.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.452
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.photon.qnx.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.452
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.gtk.solaris.sparc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.452
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.carbon.macosx.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.453
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.win32.win32.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.453
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.win32.win32.x86_64 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.570
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.gtk.solaris.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.571
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.gtk.linux.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.572
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.motif.aix.ppc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.574
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.motif.linux.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.574
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.cocoa.macosx.x86_64 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.575
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.motif.hpux.ia64_32 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.575
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.cocoa.macosx.ppc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.575
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.576
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.motif.hpux.PA_RISC is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.576
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.motif.solaris.sparc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.576
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.wpf.win32.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.577
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.win32.win32.ia64 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.577
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.carbon.macosx.ppc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.577
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.gtk.linux.ppc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.578
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.gtk.linux.x86_64 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.579
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.cocoa.macosx.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.579
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.photon.qnx.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.597
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.gtk.solaris.sparc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.633
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.carbon.macosx.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.633
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.win32.win32.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.635
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.win32.win32.x86_64 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.715
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.gtk.solaris.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.716
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.gtk.linux.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.718
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.motif.aix.ppc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.718
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.motif.linux.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.719
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.cocoa.macosx.x86_64 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.719
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.motif.hpux.ia64_32 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.720
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.cocoa.macosx.ppc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.720
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.721
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.motif.hpux.PA_RISC is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.722
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.motif.solaris.sparc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.723
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.wpf.win32.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.723
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.win32.win32.ia64 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.724
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.carbon.macosx.ppc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.725
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.gtk.linux.ppc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.727
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.gtk.linux.x86_64 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.727
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.cocoa.macosx.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.729
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.photon.qnx.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.730
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.gtk.solaris.sparc is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.730
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.carbon.macosx.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.730
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.win32.win32.x86 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2010-02-19 20:36:10.732
     [java]      [java] !MESSAGE The installable unit org.eclipse.equinox.executable_root.win32.win32.x86_64 is missing the filename property.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.equinox.p2.engine 4 4 2010-02-19 20:36:12.080
     [java]      [java] !MESSAGE An error occurred while installing the items
     [java]      [java] !SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2010-02-19 20:36:12.080
     [java]      [java] !MESSAGE session context was:(profile=SDKProfile, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Install, operand=null --> [R]org.eclipse.equinox.executable_root 3.3.200.v20090521-1800-7M-Fm-FI3UouOe61h3BYGC, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.UnzipAction).
     [java]      [java] !SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.natives 4 0 2010-02-19 20:36:12.081
     [java]      [java] !MESSAGE The artifact for binary,org.eclipse.equinox.executable_root,3.3.200.v20090521-1800-7M-Fm-FI3UouOe61h3BYGC is not available.
     [java]      [java] 
     [java]      [java] !ENTRY org.eclipse.osgi 2 0 2010-02-19 20:36:12.139
     [java]      [java] !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
     [java]      [java] !SUBENTRY 1 org.eclipse.osgi 2 0 2010-02-19 20:36:12.139
     [java]      [java] !MESSAGE Bundle org.eclipse.jdt.apt.pluggable.core_1.0.200.v20090526-2130 [101] was not resolved.
     [java]      [java] !SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2010-02-19 20:36:12.139
     [java]      [java] !MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.tool_0.0.0.
     [java]      [java] !SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2010-02-19 20:36:12.140
     [java]      [java] !MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.apt.dispatch_0.0.0.
     [java]      [java] !SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2010-02-19 20:36:12.141
     [java]      [java] !MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.apt.model_0.0.0.
     [java]      [java] !SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2010-02-19 20:36:12.141
     [java]      [java] !MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.apt.util_0.0.0.
     [java]      [java] !SUBENTRY 1 org.eclipse.osgi 2 0 2010-02-19 20:36:12.141
     [java]      [java] !MESSAGE Bundle org.eclipse.jdt.compiler.apt_1.0.200.v20090528-1135 [103] was not resolved.
     [java]      [java] !SUBENTRY 2 org.eclipse.jdt.compiler.apt 2 0 2010-02-19 20:36:12.142
     [java]      [java] !MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.tool_0.0.0.
     [java]      [java] !SUBENTRY 1 org.eclipse.osgi 2 0 2010-02-19 20:36:12.142
     [java]      [java] !MESSAGE Bundle org.eclipse.jdt.compiler.tool_1.0.100.v_963 [104] was not resolved.
     [java]      [java] !SUBENTRY 2 org.eclipse.jdt.compiler.tool 2 0 2010-02-19 20:36:12.142
     [java]      [java] !MESSAGE Missing Constraint: Bundle-RequiredExecutionEnvironment: JavaSE-1.6
     [java]      [java] Failed to locate test application "org.eclipse.ide.ui.workbench"
     [java] Project base dir set to: /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests
     [java]   [antcall] calling target(s) [-markErrorOrFailure] in build file /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests/run-tests.xml
     [java] parsing buildfile /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests/run-tests.xml with URI = file:/Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests/run-tests.xml
     [java] Project base dir set to: /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests
     [java] Trying to override old definition of task BundleFileLocator
     [java] Trying to override old definition of task GetHostName
     [java] Trying to override old definition of task SetRegex
     [java] Trying to override old definition of datatype hasErrorOrFailure
     [java]  [property] Loading /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build_Nitim-2.local.properties
     [java]  [property] Unable to find property file: /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build_Nitim-2.local.properties
     [java]  [property] Loading /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build_local.properties
     [java] Override ignored for property "swt.fragment"
     [java] Override ignored for property "ws"
     [java] Override ignored for property "buildHome"
     [java] Override ignored for property "arch"
     [java] Override ignored for property "os"
     [java] Override ignored for property "eclipseDir"
     [java] Override ignored for property "buildDirectory"
     [java]  [property] Loading /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests/run-tests.properties
     [java] Override ignored for property "autotestsuite.plugin.exclusions"
     [java] Override ignored for property "test.library.xml"
     [java] Override ignored for property "test.aggregated.report"
     [java] Override ignored for property "autotestsuite.headless"
     [java] Override ignored for property "autotest.testapplication"
     [java] Override ignored for property "autotestsuite.class.inclusions"
     [java] Override ignored for property "pluginbuilder.coverage.exclusionfilter"
     [java] Override ignored for property "autotestsuite.plugin.inclusions"
     [java] Override ignored for property "autotestsuite.trace"
     [java] Override ignored for property "autotestsuite.class.exclusions"
     [java] Override ignored for property "test.result.dir"
     [java] Override ignored for property "test.eclipse.host"
     [java] Override ignored for property "emma.coverage.output"
     [java] Override ignored for property "test.workspace"
     [java] Override ignored for property "pluginbuilder.is.runcoverage"
     [java] Override ignored for property "test.eclipse.zip"
     [java] Override ignored for property "test.eclipseExtensionDirectory"
     [java] Override ignored for property "pluginbuilder.coverage.inclusionfilter"
     [java] Override ignored for property "test.eclipse.host.eclipse"
     [java] Importing file /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/build_shared.xml from /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests/run-tests.xml
     [java] parsing buildfile /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/build_shared.xml with URI = file:/Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/build_shared.xml
     [java] Trying to override old definition of task shellscript
     [java] Trying to override old definition of task propertycopy
     [java] Trying to override old definition of task pathtofileset
     [java] Trying to override old definition of task remoteant
     [java] Trying to override old definition of task runtarget
     [java] Trying to override old definition of task assert
     [java] Trying to override old definition of task propertyregex
     [java] Trying to override old definition of task math
     [java] Trying to override old definition of task trycatch
     [java] Trying to override old definition of task antserver
     [java] Trying to override old definition of task antcallback
     [java] Trying to override old definition of task compilewithwalls
     [java] Trying to override old definition of task outofdate
     [java] Trying to override old definition of task osfamily
     [java] Trying to override old definition of task stopwatch
     [java] Trying to override old definition of task throw
     [java] Trying to override old definition of task antclipse
     [java] Trying to override old definition of task urlencode
     [java] Trying to override old definition of task bool
     [java] Trying to override old definition of task timestampselector
     [java] Trying to override old definition of task foreach
     [java] Trying to override old definition of task if
     [java] Trying to override old definition of task propertyselector
     [java] Trying to override old definition of task sortlist
     [java] Trying to override old definition of task antfetch
     [java] Trying to override old definition of task post
     [java] Trying to override old definition of task forget
     [java] Trying to override old definition of task limit
     [java] Trying to override old definition of task switch
     [java] Trying to override old definition of task var
     [java] Trying to override old definition of task inifile
     [java] Trying to override old definition of task verifydesign
     [java] Override ignored for property "is.emma"
     [java] Build sequence for target(s) `-markErrorOrFailure' is [-markErrorOrFailure]
     [java] Complete build sequence is [-markErrorOrFailure, -set.archive.location, -set.eclipse.local.tar.server, -set.eclipse.local.tar.non.server, Shared build targets.-unpack.eclipse.windows, -unpack.eclipse.linux, -get.features, -unpack.features, -unpack.feature, Shared build targets.-set.archive.location, umListFeaturesSite, -unpack.eclipse.windows, -get.archive, test, unpack.eclipse, -emmaReport, updateManager, -runAutoTests, -emmaInit, -init, run, Shared build targets.-get.archive.ifnecessary, -installEclipseExtensionLocation, Shared build targets.-set.eclipse.local.tar.non.server, Shared build targets.-get.features, Shared build targets.test, Shared build targets.-unpack.features, Shared build targets.-unpack.eclipse.linux, Shared build targets.-unpack.feature, -emmaInstrument, umRemoveSite, Shared build targets.unpack.eclipse, umAddSite, Shared build targets.-unpack.eclipse.ifnecessary, Shared build targets.-set.eclipse.local.tar.server, -get.archive.ifnecessary, -checkTestResultFileForErrors, -unpackEclipse, Shared build targets.-get.archive, -unpack.eclipse.ifnecessary, ]
     [java]   [antcall] Entering /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests/run-tests.xml...
     [java] Build sequence for target(s) `-markErrorOrFailure' is [-markErrorOrFailure]
     [java] Complete build sequence is [-markErrorOrFailure, -set.archive.location, -set.eclipse.local.tar.server, -set.eclipse.local.tar.non.server, Shared build targets.-unpack.eclipse.windows, -unpack.eclipse.linux, -get.features, -unpack.features, -unpack.feature, Shared build targets.-set.archive.location, umListFeaturesSite, -unpack.eclipse.windows, -get.archive, test, unpack.eclipse, -emmaReport, updateManager, -runAutoTests, -emmaInit, -init, run, Shared build targets.-get.archive.ifnecessary, -installEclipseExtensionLocation, Shared build targets.-set.eclipse.local.tar.non.server, Shared build targets.-get.features, Shared build targets.test, Shared build targets.-unpack.features, Shared build targets.-unpack.eclipse.linux, Shared build targets.-unpack.feature, -emmaInstrument, umRemoveSite, Shared build targets.unpack.eclipse, umAddSite, Shared build targets.-unpack.eclipse.ifnecessary, Shared build targets.-set.eclipse.local.tar.server, -get.archive.ifnecessary, -checkTestResultFileForErrors, -unpackEclipse, Shared build targets.-get.archive, -unpack.eclipse.ifnecessary, ]
     [java] 
     [java] -markErrorOrFailure:
     [java]   [antcall] Exiting /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests/run-tests.xml.
     [java] 
     [java] -emmaReport:
     [java]     [mkdir] Created dir: /tmp/pluginbuilder/st/results/testresults/coverage
     [java]      [emma] [EMMA v2.0, build 5312 (2005/06/12 19:32:43)]
     [java]    [report] processing input files ...
     [java]    [report] 1 file(s) read and merged in 72 ms
     [java]    [report] nothing to do: no runtime coverage data found in any of the data files
     [java] 
     [java] run:
     [java] Project base dir set to: /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests
     [java]   [antcall] calling target(s) [umRemoveSite] in build file /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests/run-tests.xml
     [java] parsing buildfile /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests/run-tests.xml with URI = file:/Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests/run-tests.xml
     [java] Project base dir set to: /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests
     [java] Trying to override old definition of task BundleFileLocator
     [java] Trying to override old definition of task GetHostName
     [java] Trying to override old definition of task SetRegex
     [java] Trying to override old definition of datatype hasErrorOrFailure
     [java]  [property] Loading /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build_Nitim-2.local.properties
     [java]  [property] Unable to find property file: /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build_Nitim-2.local.properties
     [java]  [property] Loading /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build_local.properties
     [java] Override ignored for property "swt.fragment"
     [java] Override ignored for property "ws"
     [java] Override ignored for property "buildHome"
     [java] Override ignored for property "arch"
     [java] Override ignored for property "os"
     [java] Override ignored for property "eclipseDir"
     [java] Override ignored for property "buildDirectory"
     [java]  [property] Loading /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests/run-tests.properties
     [java] Override ignored for property "autotestsuite.plugin.exclusions"
     [java] Override ignored for property "test.library.xml"
     [java] Override ignored for property "test.aggregated.report"
     [java] Override ignored for property "autotestsuite.headless"
     [java] Override ignored for property "autotest.testapplication"
     [java] Override ignored for property "autotestsuite.class.inclusions"
     [java] Override ignored for property "pluginbuilder.coverage.exclusionfilter"
     [java] Override ignored for property "autotestsuite.plugin.inclusions"
     [java] Override ignored for property "autotestsuite.trace"
     [java] Override ignored for property "autotestsuite.class.exclusions"
     [java] Override ignored for property "test.result.dir"
     [java] Override ignored for property "test.eclipse.host"
     [java] Override ignored for property "emma.coverage.output"
     [java] Override ignored for property "test.workspace"
     [java] Override ignored for property "pluginbuilder.is.runcoverage"
     [java] Override ignored for property "test.eclipse.zip"
     [java] Override ignored for property "test.eclipseExtensionDirectory"
     [java] Override ignored for property "pluginbuilder.coverage.inclusionfilter"
     [java] Override ignored for property "test.eclipse.host.eclipse"
     [java] Importing file /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/build_shared.xml from /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests/run-tests.xml
     [java] parsing buildfile /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/build_shared.xml with URI = file:/Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/build_shared.xml
     [java] Trying to override old definition of task shellscript
     [java] Trying to override old definition of task propertycopy
     [java] Trying to override old definition of task pathtofileset
     [java] Trying to override old definition of task remoteant
     [java] Trying to override old definition of task runtarget
     [java] Trying to override old definition of task assert
     [java] Trying to override old definition of task propertyregex
     [java] Trying to override old definition of task math
     [java] Trying to override old definition of task trycatch
     [java] Trying to override old definition of task antserver
     [java] Trying to override old definition of task antcallback
     [java] Trying to override old definition of task compilewithwalls
     [java] Trying to override old definition of task outofdate
     [java] Trying to override old definition of task osfamily
     [java] Trying to override old definition of task stopwatch
     [java] Trying to override old definition of task throw
     [java] Trying to override old definition of task antclipse
     [java] Trying to override old definition of task urlencode
     [java] Trying to override old definition of task bool
     [java] Trying to override old definition of task timestampselector
     [java] Trying to override old definition of task foreach
     [java] Trying to override old definition of task if
     [java] Trying to override old definition of task propertyselector
     [java] Trying to override old definition of task sortlist
     [java] Trying to override old definition of task antfetch
     [java] Trying to override old definition of task post
     [java] Trying to override old definition of task forget
     [java] Trying to override old definition of task limit
     [java] Trying to override old definition of task switch
     [java] Trying to override old definition of task var
     [java] Trying to override old definition of task inifile
     [java] Trying to override old definition of task verifydesign
     [java] Override ignored for property "is.emma"
     [java] Build sequence for target(s) `umRemoveSite' is [umRemoveSite]
     [java] Complete build sequence is [umRemoveSite, -set.archive.location, -set.eclipse.local.tar.server, -set.eclipse.local.tar.non.server, Shared build targets.-unpack.eclipse.windows, -unpack.eclipse.linux, -get.features, -unpack.features, -unpack.feature, Shared build targets.-set.archive.location, umListFeaturesSite, -unpack.eclipse.windows, -get.archive, test, unpack.eclipse, -emmaReport, updateManager, -runAutoTests, -emmaInit, -init, run, Shared build targets.-get.archive.ifnecessary, -installEclipseExtensionLocation, Shared build targets.-set.eclipse.local.tar.non.server, -markErrorOrFailure, Shared build targets.-get.features, Shared build targets.test, Shared build targets.-unpack.features, Shared build targets.-unpack.eclipse.linux, Shared build targets.-unpack.feature, -emmaInstrument, Shared build targets.unpack.eclipse, umAddSite, Shared build targets.-unpack.eclipse.ifnecessary, Shared build targets.-set.eclipse.local.tar.server, -get.archive.ifnecessary, -checkTestResultFileForErrors, -unpackEclipse, Shared build targets.-get.archive, -unpack.eclipse.ifnecessary, ]
     [java]   [antcall] Entering /Users/night/Documents/Agilbits/Projetos/O2/workspace/StoryTouch-Builder/build-files/automatedTests/run-tests.xml...
     [java] Build sequence for target(s) `umRemoveSite' is [umRemoveSite]
     [java] Complete build sequence is [umRemoveSite, -set.archive.location, -set.eclipse.local.tar.server, -set.eclipse.local.tar.non.server, Shared build targets.-unpack.eclipse.windows, -unpack.eclipse.linux, -get.features, -unpack.features, -unpack.feature, Shared build targets.-set.archive.location, umListFeaturesSite, -unpack.eclipse.windows, -get.archive, test, unpack.eclipse, -emmaReport, updateManager, -runAutoTests, -emmaInit, -init, run, Shared build targets.-get.archive.ifnecessary, -installEclipseExtensionLocation, Shared build targets.-set.eclipse.local.tar.non.server, -markErrorOrFailure, Shared build targets.-get.features, Shared build targets.test, Shared build targets.-unpack.features, Shared build targets.-unpack.eclipse.linux, Shared build targets.-unpack.feature, -emmaInstrument, Shared build targets.unpack.eclipse, umAddSite, Shared build targets.-unpack.eclipse.ifnecessary, Shared build targets.-set.eclipse.local.tar.server, -get.archive.ifnecessary, -checkTestResultFileForErrors, -unpackEclipse, Shared build targets.-get.archive, -unpack.eclipse.ifnecessary, ]
Hi,

Hm, that should work. What does your log file mention?
For example,  if you look at http://self.pluginbuilder.org/latest/build.log.txt, there are entries similar to the ones below.
Markus

     [java] -runAutoTests:
     [java]     [mkdir] Created dir: /var/www/buildresults/self/nightly/0.8.0.201002190315NGT/testresults/xml
     [java]      [java] EMMA: collecting runtime coverage data ...
     [java]      [java] Deleting directory /var/www/buildresults/self/nightly/0.8.0.201002190315NGT/testresults/xml
     [java]      [java] ~~~~~~~~~~~~ Searching for JUnit 3 test plug-ins.
     [java]      [java] Using inclusion regular expression(s): .*(test|tests)$
     [java]      [java] Using exclusion regular expression(s): |^org.eclipse.test$
     [java]      [java] Bundle matches: org.pluginbuilder.core.test
     [java]      [java] Found 1 plug-ins.
     [java]      [java] ~~~~~~ Searching for JUnit 3 test classes in org.pluginbuilder.core.test
     [java]      [java] Using inclusion regular expression(s): .*
     [java]      [java] Using exclusion regular expression(s): .*(WebDavSynchronize_Test|ServerCommunication_Test)$
     [java]      [java] Searching bundleentry://192.fwk873275301/coretest.jar for tests.
     [java]      [java] Added test class: org.pluginbuilder.core.internal.BuildConfigPersistency_PDETest
     [java]      [java] Added test class: org.pluginbuilder.core.internal.CopyMapFileWriter_PDETest
     [java]      [java] EMMA: collecting runtime coverage data ...
     [java]      [java] Added test class: org.pluginbuilder.core.internal.templates.Template_PDETest
     [java]      [java] Excluded test class: org.pluginbuilder.core.internal.webdav.WebDavSynchronize_Test
     [java]      [java] Added test class: org.pluginbuilder.internal.core.creators.MapFileCreator_PDETest
     [java]      [java] Added test class: org.pluginbuilder.internal.core.creators.SvnFetchAllFileWriter_PDETest
     [java]      [java] Excluded test class: org.pluginbuilder.internal.core.serverconnection.ServerCommunication_Test
     [java]      [java] Added test class: org.pluginbuilder.internal.core.smartproperties.SmartProperties_Test
     [java]      [java] Scanned 25 Jar entries.
     [java]      [java] Searching bundleentry://192.fwk873275301/lib/easymock.jar for tests.
     [java]      [java] Scanned 37 Jar entries.
     [java]      [java] Searching bundleentry://192.fwk873275301/lib/commons-io-1.3.1.jar for tests.
     [java]      [java] Scanned 69 Jar entries.
     [java]      [java] Searching bundle directory for tests.
     [java]      [java] The bundle directory of org.pluginbuilder.core.test does not contain any class files.
     [java] 

On 19.02.2010, at 21:59, Hugo Corbucci wrote:

> Hello everyone,
> I've been using plugin builder to build my app for about a year and a half. It works great but we're not using the test part since our continuous integration server is service on a windows machine and therefore cannot run plugin tests.
> I've recently tried to run the build localy on my machine and discovered to my surprise that, although the test task is being run, autotestsuite is not finding any test.
> 
> I double checked my test feature to ensure it had all the test plugins for my app. I also double checked the inclusion and exclusion patters for both classes and plugin.
> They are currently like this:
> autotestsuite.plugin.inclusions=.*(test|tests)$
> autotestsuite.plugin.exclusions=org\.pluginbuilder\..*
> autotestsuite.class.inclusions=.*Test$
> autotestsuite.class.exclusions=
> 
> And all our test classes use JUnit 4 and are named ending with 'Test'. Our plugins are all named with 'tests' at the end.
> 
> I've tried looking the .log of the testing running excution of eclipse but got nothing from that. It seems things are just fine there.
> I'm using java 1.5.0 on an OS X machine, eclipse 3.5 and pluginbuilder 0.7. My app is an RCP app and it builds just fine with plugin builder.
> Any ideas/tips? Any detail I forgot to mention but I should have mentioned?
> 
> Thanks,
> -- 
> Hugo Corbucci
> CS Grad from 2003 to 2006
> CS Master from 2007 to 2010
> Cel: (55) (11) 8636 9029
> Phone: (55) (11) 2649 8636
> Skype user: hugo.corbucci
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev_______________________________________________
> Pluginbuilder-development mailing list
> Plu...@li...
> https://lists.sourceforge.net/lists/listinfo/pluginbuilder-development

Hello everyone,
I've been using plugin builder to build my app for about a year and a half.
It works great but we're not using the test part since our continuous
integration server is service on a windows machine and therefore cannot run
plugin tests.
I've recently tried to run the build localy on my machine and discovered to
my surprise that, although the test task is being run, autotestsuite is not
finding any test.

I double checked my test feature to ensure it had all the test plugins for
my app. I also double checked the inclusion and exclusion patters for both
classes and plugin.
They are currently like this:
autotestsuite.plugin.inclusions=.*(test|tests)$
autotestsuite.plugin.exclusions=org\.pluginbuilder\..*
autotestsuite.class.inclusions=.*Test$
autotestsuite.class.exclusions=

And all our test classes use JUnit 4 and are named ending with 'Test'. Our
plugins are all named with 'tests' at the end.

I've tried looking the .log of the testing running excution of eclipse but
got nothing from that. It seems things are just fine there.
I'm using java 1.5.0 on an OS X machine, eclipse 3.5 and pluginbuilder 0.7.
My app is an RCP app and it builds just fine with plugin builder.
Any ideas/tips? Any detail I forgot to mention but I should have mentioned?

Thanks,
-- 
Hugo Corbucci
CS Grad from 2003 to 2006
CS Master from 2007 to 2010
Cel: (55) (11) 8636 9029
Phone: (55) (11) 2649 8636
Skype user: hugo.corbucci

Hi,

I just want to give you a short update of the latest changes in trunk. The cause was to add categories to the p2 repository. Without categories the update manager of Eclipse 3.5 complains about "There are no categorized items" and the user has to uncheck "Group items by category" in order to see the features.

Categories can be added by enabling p2.gathering and by setting p2.category.definition to a category.xml file. That is easy, but there are ramifications. With p2.gathering the build does not create archives for features anymore. Instead, the features are published to the p2 repository. The problem: the archives are needed for deploying the features into the test host (with the standalone update manager). I pondered two solutions: 
1) extract the archives from the repository and go on with the update manager
2) install the features into the test host using the p2 director instead of the update manager

I decided to go for the second option. One reason being that the director will replace the update manager sooner or later anyway.

I think that p2.gathering has further potential to simplify the build with pluginbuilder. At the time being there are two build runs: the first run creates the feature archives (and the old style update site) whereas the second (optional) run creates the RCP configurations. With p2.gathering the RCP configurations can also be published into a repository. I guess this would make the first run useless. However, an additional task is necessary to export the archives from the repository.

I won't touch this in the near future. Just an idea.

cheers
Markus

Hi Anu,

There was a discussion about using fragments for tests in the past:
http://sourceforge.net/projects/pluginbuilder/forums/forum/660094/topic/2102194

It is difficult for me to guess about problems in your environment. I would recommend that you first set up the rcpsample with a test fragment and once this runs you can double-check the set-up of your application.

Here you find more about building the rcpsample with pluginbuilder: http://www.pluginbuilder.org/documentation/example/

cheers
Markus

On Jan 12, 2010, at 10:48 AM, Anu Anand wrote:

> Hi 
> I'm using plugin builde for builing a very complex application.
> I have few plugin tests written as fragments. 
> The plugin builder cannot run these tests as it cannot find the dependencies which fragments get from host plugin.
> I feel it cannot recogonize fragments.
> Any help?
> 
> Anu.
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev _______________________________________________
> Pluginbuilder-development mailing list
> Plu...@li...
> https://lists.sourceforge.net/lists/listinfo/pluginbuilder-development

Hi
I'm using plugin builde for builing a very complex application.
I have few plugin tests written as fragments.
The plugin builder cannot run these tests as it cannot find the dependencies
which fragments get from host plugin.
I feel it cannot recogonize fragments.
Any help?

Anu.

Hi all,

I just wanted to let you know there was a release of pluginbuilder and 
get your input for the further development.

The release 0.7.0 
(http://www.pluginbuilder.org/news/article/released-070) does not 
support any of the new Eclipse 3.5 features yet with one exception: the 
autotestsuite is compatible with Junit 4.5. Is there anything which 
would be particularly important for you?

With Eclipse 3.5 there have been some changes concerning the target 
platform. For example there are target definitions. I still have not 
figured out the easiest way how to get a target platform for the PDE 
headless build from a target definition. For example, if the target 
definition contains references to update sites, how would I create a 
local directory which I could zip und make available on the build 
server? Any suggestions? BTW, I have tried to describe a way to build 
the target platform automatically 
(http://www.markusbarchfeld.de/blog/article/2009/02/23/build_automation_for_your_target_platform.html) 
but this seems cumbersome and I wonder if target definitions could 
simplify the approach.

Another change with Eclipse 3.5 concerns the RCP delta pack: it can not 
be copied over the Eclipse installation anymore. Instead it must be part 
of the target platform. So, for RCP builds you must define a target 
platform which includes the delta pack. If you copy the RCP delta pack 
over an Eclipse installation, it can not be started up anymore.

Unfortunately this affects the current approach of using the same host 
as build and test host: currently we just create one Eclipse 
installation which includes everything to build and test, i.e. the JDT 
and PDE, the prerequisites of the application to be built, any test 
dependencies and - the delta pack. After the build has finished the 
resulting features will be added to the build/test host via the update 
manager API.

Now, by using a target platform, the prerequisites do not have to be 
added to the build host anymore, but they must be made available to the 
test host. It is not possible to just add the target platform to the 
test host in the same way as the resulting feature because it also 
includes the RCP delta pack.

So, I guess we have to change the way how RCP apps are tested. We 
probably have to reverse the process: instead of adding the resulting 
features to the test host the necessary plugins for running the tests 
should be added to the RCP app. Do you have experience with that 
process? Any suggestions are welcome.

Thanks
Markus

The contents of the plugin directory:
br.org.archimedes.batik
br.org.archimedes.core
br.org.archimedes.opengl
br.org.archimedes.opengl.linux.x86
br.org.archimedes.opengl.linux.x86_64
br.org.archimedes.opengl.macosx
br.org.archimedes.opengl.win32.x86

The only dependency that the OpenGL plugin has is for 'org.eclipse.ui' which
is in my target platform.
I've checked each plugin. The only thing that is in those directories are
the MANIFEST.MF file and plugin.xml (or fragment.xml). That sounds weird.
Is this ok?

Thank you very much,
Hugo

On Tue, Feb 17, 2009 at 11:36 AM, Markus Barchfeld
<Mar...@gm...>wrote:

> Hi Hugo,
>
> Can you confirm that the source for br.org.archimedes.opengl was
> copied (or checked out from svn) correctly? Does the
> $buildDirectory/plugins folder look alright? if not, was the map file
> generated correctly?
> Since br.org.archimedes.opengl does not have many dependencies, we can
> probably exclude a missing dependency as the reason.
>
> cheers
> Markus
>
> 2009/2/16 Hugo Corbucci <hug...@gm...>:
> > Hello everyone,
> > I've been using Plug-in Builder to build a commercial application and
> I've
> > had no big problems surrounding that.
> > Recently, I decided to use it to build my open source project. It is a
> CAD
> > RCP application aimed for architects.
> >
> > I used to build it manually through Eclipse with the exporting wizard and
> > then package it with IzPack.
> > I am now struggling to understand what might be stopping me from building
> it
> > with Plug-in Builder.
> > I've attached my workspace log file which states:
> >
> /Users/night/Downloads/eclipse/plugins/org.eclipse.pde.build_3.4.0.v20080604/scripts/genericTargets.xml:91:
> > Bundle br.org.archimedes.core_0.0.0 failed to resolve.:
> >     Missing required plug-in br.org.archimedes.opengl_0.0.0.
> >
> >     at
> >
> org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:541)
> > ...
> >
> > I do have this plugin in my list and it has no special problems being
> built
> > (it's a pre-compiled library).
> > Anyone got any idea on why this might be happening?
> >
> > The whole source code can be found at:
> > http://svn.archimedes.org.br/public/mainarchimedes/rcparchimedes/
> <project-name>/trunk
> >
> > Thanks for your help,
> > --
> > Hugo Corbucci
> > CS Grad from 2003 to 2006
> > CS Master from 2007 to 2009
> > Cel: (55) (11) 8636 9029
> > Phone: (55) (11) 5539 3500
> > Skype user: hugo.corbucci
> >
> >
> ------------------------------------------------------------------------------
> > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco,
> CA
> > -OSBC tackles the biggest issue in open source: Open Sourcing the
> Enterprise
> > -Strategies to boost innovation and cut costs with open source
> participation
> > -Receive a $600 discount off the registration fee with the source code:
> SFAD
> > http://p.sf.net/sfu/XcvMzF8H
> > _______________________________________________
> > Pluginbuilder-development mailing list
> > Plu...@li...
> > https://lists.sourceforge.net/lists/listinfo/pluginbuilder-development
> >
> >
>

-- 
Hugo Corbucci
CS Grad from 2003 to 2006
CS Master from 2007 to 2009
Cel: (55) (11) 8636 9029
Phone: (55) (11) 5539 3500
Skype user: hugo.corbucci

Hi Hugo,

Can you confirm that the source for br.org.archimedes.opengl was
copied (or checked out from svn) correctly? Does the
$buildDirectory/plugins folder look alright? if not, was the map file
generated correctly?
Since br.org.archimedes.opengl does not have many dependencies, we can
probably exclude a missing dependency as the reason.

cheers
Markus

2009/2/16 Hugo Corbucci <hug...@gm...>:
> Hello everyone,
> I've been using Plug-in Builder to build a commercial application and I've
> had no big problems surrounding that.
> Recently, I decided to use it to build my open source project. It is a CAD
> RCP application aimed for architects.
>
> I used to build it manually through Eclipse with the exporting wizard and
> then package it with IzPack.
> I am now struggling to understand what might be stopping me from building it
> with Plug-in Builder.
> I've attached my workspace log file which states:
> /Users/night/Downloads/eclipse/plugins/org.eclipse.pde.build_3.4.0.v20080604/scripts/genericTargets.xml:91:
> Bundle br.org.archimedes.core_0.0.0 failed to resolve.:
>     Missing required plug-in br.org.archimedes.opengl_0.0.0.
>
>     at
> org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:541)
> ...
>
> I do have this plugin in my list and it has no special problems being built
> (it's a pre-compiled library).
> Anyone got any idea on why this might be happening?
>
> The whole source code can be found at:
> http://svn.archimedes.org.br/public/mainarchimedes/rcparchimedes/<project-name>/trunk
>
> Thanks for your help,
> --
> Hugo Corbucci
> CS Grad from 2003 to 2006
> CS Master from 2007 to 2009
> Cel: (55) (11) 8636 9029
> Phone: (55) (11) 5539 3500
> Skype user: hugo.corbucci
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Pluginbuilder-development mailing list
> Plu...@li...
> https://lists.sourceforge.net/lists/listinfo/pluginbuilder-development
>
>

>> The properties are already included in the Pluginbuilder nightly and
>> can be set via the Properties tab of the Pluginbuilder Editor.
>>
> Have there been changes in the nightlies? I was watching the CVS for a
> while but there didn't seem to be significant modifications since 0.6?
> (Just wondering if I should move to a nightly update site).
Not many. Apart from the p2 properties the emma.jar has been replaced
due to a bug on 64 Bit Linux (IndexOutOufBoundException).
And the usual smaller fixes. I should release it anyway.

Markus

Markus Barchfeld wrote:
>
> hm, as far is I remember the deletion of postBuild.xml was related to
> the pre-p2 update site. 
Ah yes (from the 0.6 release notes):
"The target of this release is Eclipse 3.3. A user has reported that 
building  with Eclipse 3.4 also works but postBuild.xml must be disabled 
(e.g. by renaming or deleting it)."

> The properties are already included in the Pluginbuilder nightly and
> can be set via the Properties tab of the Pluginbuilder Editor.
>   
Have there been changes in the nightlies? I was watching the CVS for a 
while but there didn't seem to be significant modifications since 0.6? 
(Just wondering if I should move to a nightly update site).

> Have a look at 
> http://rcpsample-3-4.pluginbuilder.org/nightly/p2-updateSite/
> which has been set up with the pluginbuilder nightly.
> Still unclear: how to set a category,
> https://sourceforge.net/forum/message.php?msg_id=6025032.
>   
Yeah - I know.  I sampled code from this and some other blogs, eg
http://aniefer.blogspot.com/2008/06/example-headless-build-for-rcp-product.html
helped me along, mostly by pointing out all the bugs that one needs to 
know about when dealing with p2 (eg. which config option not to use 
because it's broken, etc).

But still - a tool that sets up all the different string identifiers and 
version numbers and whatnot in exactly the way p2 & friends expect would 
be great.
(I spent ages on it - but any kind of approach of working with the PDE 
Build system (when working with a non-trivial RCP product) is marked by 
trying one combination,
waiting 10 minutes for the build to grind to a halt and fails with "Java 
exited with error code -13" - or the alternative of watching the build 
unfold in the debugger, which isn't much more fun.

I know the best way to do this would be to read and fully grok the PDE 
Build system, but I'd like to avoid a mind numbing task like that as 
long as I can.  Mostly because I can't believe that's really the _only_ 
way to build plugins.

>> (I tried for ages to get this right - but apparently one needs to be a
>> Mensa member and infinite patience to get even the most trivial things
>> to work with the PDE Build).
>>     
> I would not blame PDE for that. I think it is intrinsic to all build
> related development because it takes so long to get feedback. 
Weeeeell... the patience bit wasn't so much about the time it take to 
run the builds, but the patience it takes to even find out where to get 
started with the PDE Build system config.

Imagine if there were no PDE editors/tools support and you had to figure 
out all the OSGi/plugin/extension/etc stuff on your own - or figure out 
that your plugin doesn't work because you haven't set up the right 
import statement here or there.  These are all trivial with the PDE 
tools - but setting up a PDE Build means grokking every little 
nook/cranny of the system.

Eg. Alex Blewitt's EclipseCon talk/slides gave me the first light bulb 
moment by explaining the architecture of the PDE Build system (ie. 
basically a kind of OOP/Module/Polymorphism built on Ant callback files).
http://www.eclipsecon.org/2006/Sub.do?id=18
Etc.

murphee

> One question is: what's the level of p2 support in PluginBuilder 0.6.0?
> The release notes state that it's supported, but it's necessary to
> delete postBuild.xml.
hm, as far is I remember the deletion of postBuild.xml was related to
the pre-p2 update site. Pluginbuilder 0.6.0 does not support p2. But
it is quite easy to create a p2 repository since the PDE provides a
couple of p2 related properties:
http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_metadata_generator.html
The properties are already included in the Pluginbuilder nightly and
can be set via the Properties tab of the Pluginbuilder Editor.
>
> Also: as I understand p2, it's necessary to run the p2 Director task.
> Having PluginBuilder (or something - dare I suggest the PDE...) set up
> something that works would be great.
Have a look at http://rcpsample-3-4.pluginbuilder.org/nightly/p2-updateSite/
which has been set up with the pluginbuilder nightly.
Still unclear: how to set a category,
https://sourceforge.net/forum/message.php?msg_id=6025032.

> (I tried for ages to get this right - but apparently one needs to be a
> Mensa member and infinite patience to get even the most trivial things
> to work with the PDE Build).
I would not blame PDE for that. I think it is intrinsic to all build
related development because it takes so long to get feedback. That is
the difference between developing code where you get immediate
feedback from your test suites as opposed to developing build scripts
where you have to wait minutes or even hours to see results. So, one
of the principles of writing build scripts should be to make them as
modular as possible and reduce time to feedback. For example it should
be possible to re-run the tests without doing all the compilation
steps before.

Markus

Markus Barchfeld wrote:
>> We have not managed to use pluginbuilder for an
>> RCP build (based on the p2 system for eclipse 3.4).
>> Would this be a good list to send questions to?
>>     
> If you stumbled upon a specific issue a bug report would suite better I guess.
> If it is something more general, let's go on and discuss it here.
>   

One question is: what's the level of p2 support in PluginBuilder 0.6.0?
The release notes state that it's supported, but it's necessary to 
delete postBuild.xml.

Also: as I understand p2, it's necessary to run the p2 Director task. 
Having PluginBuilder (or something - dare I suggest the PDE...) set up 
something that works would be great.
(I tried for ages to get this right - but apparently one needs to be a 
Mensa member and infinite patience to get even the most trivial things 
to work with the PDE Build).

murphee

PS: I'd like to second the opinions already stated: PluginBuilder is a 
life saver - Thanks Markus B.,  also thanks for your old Developer Works 
Article on the PDE Build system which permitted me to get started with 
PDE Build before the age of PluginBuilder.
Also: I'm surprised the PDE team would spoil their otherwise excellent 
tools with a mindblowingly ghastly blemish such as the undocumented 
torture instrument that is the PDE Build system (or at least it's 
configuration).

> We have not managed to use pluginbuilder for an
> RCP build (based on the p2 system for eclipse 3.4).
> Would this be a good list to send questions to?
If you stumbled upon a specific issue a bug report would suite better I guess.
If it is something more general, let's go on and discuss it here.

Thanks
Markus

Hi

We build a collection of eclipse plugins to add
development support for Mathematica.  We also
ship an RCP version of this, one that is very
close to eclipse.

eclipse is a great platform, but I have
always found its build system/tools to be
complicated, confusing, and hard to work with.
This is in enormous contrast to just about
everything else in eclipse.

Last year we switched to use pluginbuilder
to create the build system for our plugins,
and it works very nicely. It helps enormously,
for example it is good at preventing organic
drift of build files.  We have our own build
system that kicks of nightly builds and handles
configuration management tracking etc...

We have not managed to use pluginbuilder for an
RCP build (based on the p2 system for eclipse 3.4).
Would this be a good list to send questions to?

 From what I can see of Buckminster,  I don't
think it would be useful for us.

Anyway,  pluginbuilder is great!

Tom Wickham-Jones

Hello everyone,
I'm writing to fulfill my duties towards Markus who did a great job with
Plug-in Builder.
I am currently using it to automatically build and deploy an RCP application
with TeamCity.
TeamCity keeps track of repository (Subversion) changes and hourly (if there
is a change) triggers Plug-in Builder to build, run the tests (though this
is not working so well) and produce the executable files of an RCP
application.
I've just reported a few problems I'm having with it but it has so far
helped me a lot.

I don't believe Buckminster overlaps with Plug-in builder. I honestly
couldn't make it out with the build.xml files that eclipse generated to
build my rcp application. Plug-in builder made it amazingly easier to handle
and track my build system and problems. I am willing to help improve
anything needed and so far am struggling with the problems I reported on
sourceforge.

Thank you for your work.

Yours,
-- 
Hugo Corbucci
CS Grad from 2003 to 2006
CS Master from 2007 to 2009
Cel: (55) (11) 8636 9029
Phone: (55) (11) 5539 3500
Skype user: hugo.corbucci

>From what I read about Buckminster it looks more like a dependency
resolution tool.
I don't think there is much overlapping with Pluginbuilder but I might
have misinterpreted what Buckminster is.

Concerning the PDE, it could be a good idea but it would require to be
able to build on another server than pluginbuilder.org
By the way it would be a good idea to enable private companies to
adopt the Pluginbuilder by letting them deploy build servers.
I think it would boost the Pluginbuilder adoption to open-source the
server as well, let other build server infrastructure and let the
plugin connect to any server. It could even enable business to develop
around this.
At the end may be even the Eclipse Foundation would finally adopt it
for its build infrastructure.

C.

On Fri, Jan 23, 2009 at 12:54 PM, Markus Barchfeld
<Mar...@gm...> wrote:
> I have created this list to discuss the development of Pluginbuilder.
> In particular the project has reached a point where the future
> direction of Pluginbuilder is not clear to me and I would be glad to
> receive some feedback from the people who have tried or used
> pluginbuilder so far. I have already added some feature requests
> (https://sourceforge.net/tracker/?group_id=188226&atid=924464) which
> would improve Pluginbuilder from my point of view.
>
> I would like people to comment on the existing requests or add new
> requests. They will be a base for the decision if/how to proceed with
> Pluginbuilder.
>
> I would also like to pose the following questions:
> 1) Do Buckminster and Pluginbuilder overlap? Should further efforts be
> invested into Buckminster instead of Pluginbuilder?
> 2) Is there still need to add some of pluginbuilder's functionality
> into PDE? There was an attempt to add Pluginbuilder as PDE Incubator
> project but there was not much interest, see
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=205384
>
> cheers
> Markus
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Pluginbuilder-development mailing list
> Plu...@li...
> https://lists.sourceforge.net/lists/listinfo/pluginbuilder-development
>

I have created this list to discuss the development of Pluginbuilder.
In particular the project has reached a point where the future
direction of Pluginbuilder is not clear to me and I would be glad to
receive some feedback from the people who have tried or used
pluginbuilder so far. I have already added some feature requests
(https://sourceforge.net/tracker/?group_id=188226&atid=924464) which
would improve Pluginbuilder from my point of view.

I would like people to comment on the existing requests or add new
requests. They will be a base for the decision if/how to proceed with
Pluginbuilder.

I would also like to pose the following questions:
1) Do Buckminster and Pluginbuilder overlap? Should further efforts be
invested into Buckminster instead of Pluginbuilder?
2) Is there still need to add some of pluginbuilder's functionality
into PDE? There was an attempt to add Pluginbuilder as PDE Incubator
project but there was not much interest, see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=205384

cheers
Markus

Hi All,

To follow-up on Markus request here is what I have to say :)

To me Pluginbuilder is a great tool and is doing just well, its role
is clearly defined and is well done, I guess that's one of the reasons
why there's not much to say about it, that's like a commodity, you
don't talk about it until there's no more of it  :)

If I were to ask for new features this would be my list:
- solve the problem with changing SSL certificates. when sourceforge
changes the ssl certificates for svn then the Pluginbuilder server
fails
- have an option for builds to be triggered when something has changed
on the repository (integration builds vs nightly builds)
- possibility to have several builds running (like HEAD and
maintenance for various releases)

Regards,
Claude Vedovini
---
Software Consulting & Development
+41 78 617 86 98
http://vedovini.net/
http://www.dita-op.org/

---------- Forwarded message ----------
From: Markus Barchfeld <Mar...@gm...>
Date: Fri, Jan 23, 2009 at 1:26 PM
Subject: Future of Pluginbuilder
To:

Hello,

I am writing you because you have been in touch with the Pluginbuilder
project in the past.

The project has reached a point where the future direction of
Pluginbuilder is not clear to me and I would be glad to receive some
feedback from the people who have tried or used pluginbuilder so far.

If you are interested there are two ways for you to give feedback.
Subscribe (and write to!) the newly created mailing list
"pluginbuilder-development"
(https://sourceforge.net/mail/?group_id=188226) or add your feature
requests to pluginbuilder's Feature tracker at sourceforge
(https://sourceforge.net/tracker/?group_id=188226&atid=924464). Your
comments to existing Feature Requests would also be appreciated.

On the mailing list I would also like to discuss the following questions:

1) Do Buckminster and Pluginbuilder overlap? Should further efforts be
invested into Buckminster instead of Pluginbuilder?

2) Is there still need to add some of pluginbuilder's functionality
into PDE? There was an attempt to add Pluginbuilder as PDE Incubator
project but there was not much interest, see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=205384

And of course I am also curious about your experience with
Pluginbuilder: Why have you (not) used Pluginbuilder in your Project?
What extensions did you have to create yourself in order to get the
build results you wanted? Would it be worth to share them with others?

I am looking forward to your response on the mailing list.
cheers
Markus

2009	Jan (9)	Feb (4)	Mar (1)	Apr	May	Jun	Jul (1)	Aug	Sep	Oct	Nov	Dec
2010	Jan (3)	Feb (7)	Mar	Apr	May	Jun	Jul	Aug (1)	Sep	Oct	Nov	Dec
2011	Jan	Feb	Mar	Apr	May (1)	Jun	Jul	Aug	Sep	Oct	Nov	Dec

pluginbuilder-development Mailing List for Plug-in Builder

pluginbuilder-development — Discussing the development of pluginbuilder