|
|
| Re: component type for eclipse projects [message #380028 is a reply to message #380027] |
Fri, 05 September 2008 08:56  |
Eclipse User |
|
|
|
I am currently using buckminster.cspec do define component dependencies.
It struck me however, that while doing that, I have (at least) 2 places
where my dependencies are declared - in eclipse project build path
settings and buckminster.cspec. (3, if you consider that build.xml also
needs to know those things)
It is no big problem to copy the dependencies from project classpath to
buckminster.cspec when initially defining the specifications, but it
becomes a nightmare to maintain with a host of developers banging away
at components. Everybody who is touching these projects may change the
dependencies and thus *must* remember to update the listing in cspec as
well. People being just people, tend to forget it.
Any way - I got my answer - there is no such component type at the
moment that would infer the dependencies from java project classpath...
Thomas Hallgren kirjutas mulle midagi seesugust:
> We have no generic 'eclipse.project' type so that depends on what you're
> doing instead. The best way is probably to add a buckminster.cspec to
> your project and then use the component type 'buckminster' but if you
> have a maven POM then using the maven component type might be a good idea.
>
> Regards,
> Thomas Hallgren
>
> Roland Tepp wrote:
>> Hi,
>>
>> I am wandering what is the preferred componentType of Eclipse projects
>> (not plug-in/osgi bundles).
>>
>>
--
Roland Tepp
|
|
|
Powered by
FUDForum. Page generated in 0.03085 seconds
Home