Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [buckminster-dev] Passing javac parameter 
Hey,

I do execute the following subsequent steps within Hudson:

  + rm -Rf .metadata/
[After checking in the Repo, which is necessary, I do entirely remove the .metadata]

  + [workspace] $ java -Dbuckminster.output.root=/var/lib/hudson/jobs/Elexis_2.1_Core_Build/workspace/buckminster.output -Dbuckminster.temp.root=/var/lib/hudson/jobs/Elexis_2.1_Core_Build/workspace/buckminster.temp -DtargetPlatformPath=/var/lib/hudson/jobs/Elexis_2.1_Core_Build/workspace/targetPlatform -jar /usr/local/bin/buckminster-headless/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar -application org.eclipse.buckminster.cmdline.headless -data /var/lib/hudson/jobs/Elexis_2.1_Core_Build/workspace --loglevel info -S /var/lib/hudson/jobs/Elexis_2.1_Core_Build/workspace/commands.txt
  I
NFO:  import '--template' '/home/marco/templateWorkspace.zip' '/var/lib/hudson/jobs/Elexis_2.1_Core_Build/workspace/site.core.elexis/site.cquery'
  Workspace at /var/lib/hudson/jobs/Elexis_2.1_Core_Build/workspace is not empty

So there definitely is no .metadata within the workspace. The only things located in there is the cloned mercurial repository! 

Is there a way to have more output on what files the templateworkspace actually bangs on? Or is there a way to force the template into existence?

thx,
marco



Am 23.11.2010 um 14:09 schrieb Thomas Hallgren:

> On 2010-11-23 11:51, Marco Descher wrote:
>> Hey Thomas and List,
>> 
>> thanks for your help, there are however the following problems:
>> 
>> According to the bucky book, the respective option should be -t, this however results in
>> 
>> INFO:  import '-t' '/home/marco/templateWorkspace.zip' '/var/lib/hudson/jobs/Elexis_Trunk_Core_Build/workspace/site.core.elexis/org.eclipse.platform.mspec'
>> org.eclipse.buckminster.cmdline.parser.InvalidOptionException: The option '-t' is invalid
> 
> I think you can use either -T  or --template so the documentation is wrong.
> 
>> A successive use of --template results in
>> INFO:  import '--template' '/home/marco/templateWorkspace.zip' '/var/lib/hudson/jobs/Elexis_Trunk_Core_Build/workspace/site.core.elexis/org.eclipse.platform.mspec'
>> Workspace at /var/lib/hudson/jobs/Elexis_Trunk_Core_Build/workspace is not empty
>> I think I've seen this one before, but don't have a clue!
>> 
> It means that the workspace that you are trying to import to already exists and has some content (a .metadata folder most likely). That's not permitted when you start with a template.
> 
> - thomas
> _______________________________________________
> buckminster-dev mailing list
> buckminster-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/buckminster-dev

Back to the top