Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » B3 » Dont aggregate to a 'final' catalog
Dont aggregate to a 'final' catalog [message #854093] Mon, 23 April 2012 12:58 Go to next message
Fredrik Lindqvist is currently offline Fredrik Lindqvist
Messages: 11
Registered: November 2009
Junior Member
Small question; Is it possible to define a aggregate so that its output isnt to a "final" folder? Currently I set the build root to (for example) "c:\tmp" and the update site ends up in "c:\tmp\final", is that configurable?
I can of course do some copy&paste magic, but I'd like to be able to use the result as is.

Report message to a moderator

Re: Dont aggregate to a 'final' catalog [message #885105 is a reply to message #854093] Tue, 12 June 2012 09:24 Go to previous message
Pavel Tarasenko is currently offline Pavel Tarasenko
Messages: 5
Registered: June 2012
Junior Member
Yes, it would be nice to have output location completely configurable.

We have b3 aggregated repository served via Apache web server and want to have a concise URL like http :// SERVER/eclipse/updates.
Currently this is achieved by symlinking a eclipse/final -> eclipse/updates.

Report message to a moderator

Previous Topic:Compressed build results?
Next Topic:Aggregated repository - allow updates of mapped features
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Tue May 28 09:02:31 EDT 2013

Powered by FUDForum. Page generated in 0.01556 seconds