Home » Eclipse Projects » Buckminster dev » Re: [buckminster-dev] CSPEC Location
| Re: [buckminster-dev] CSPEC Location [message #4684] |
Mon, 18 February 2008 16:22 |
|
Hi Evan,
I think what you're describing sounds like a good match for what
Buckminster is targeted to help with. While Buckminster certainly knows
how to use plug-ins and features, it is not limited to that.
We don't generate .classpath and .project files since these are normally
checked in to a project. We don't do that for any type of project. So my
recommendation would be to create these files with desired settings for
JRE, project natures, etc. and then check them into CVS.
The difference between plug-ins and normal Java project is simply that
the plug-in contains more information that we can make use of. As you
have already discovered, this information must be entered manually when
it's not obtainable form other sources.
A good start for you is probably to add a buckminster.cspec file to each
project and declare all the dependencies there. Once you have that, and
one top-level project that can serve as the root of things, a query can
check everything out in one go. Next step would be to add the actions
that build each project and then finally the actions that tie the things
together.
Regards,
Thomas Hallgren
Evan Broderick wrote:
> Hi Thomas,
>
> Thanks for the reply. The project I'm trying to "buckminsterize" is not
> an eclipse plugin or a feature, so I guess I'll have to use the
> buckminster.cpec for my meta-data.
>
> I was wondering if I could describe to you what I would like to
> accomplish with buckminster and get your opinion on how feasible it is
> (and maybe get some advice on how to move forward)...
>
> Basically, we have a large java project in cvs which is pretty difficult
> to set up in eclipse, especially for new hires. No .classpath files,
> .project files, or jar dependencies are checked in with the source. When
> a developer wants to work on the project in eclipse, it obviously takes
> a while to find all these dependencies in order to configure the build
> path correctly.
>
> So really, all I would like to do with Buckminster right now would be to
> checkout the project, set up the source directories, and set up the
> build path in one step. I'm starting to think that Buckminster is really
> more of a tool for eclipse features/plugins, so would it be able to help
> me out with my situation?
>
> Thanks,
> Evan
>
> -----Original Message-----
> From: buckminster-dev-bounces@eclipse.org
> [mailto:buckminster-dev-bounces@eclipse.org] On Behalf Of Thomas
> Hallgren
> Sent: Monday, February 11, 2008 5:27 PM
> To: Buckminster developer discussions
> Subject: Re: [buckminster-dev] CSPEC Location
>
> Hi Evan,
> The 'componentTypes' attribute tells Buckminster what the provider
> should expect in the components that it finds. In your case, you have
> specificed three possible types:
> "osgi.bundle,eclipse.feature,buckminster"
>
> The 'osgi.bundle' component type assumes that meta-data can be found in
> files like META-INF/MANIFEST.MF, plugin.xml, or fragment.xml. The
> eclipse.feature will look for the 'eclipse.xml' file. The 'buckminster'
> type looks for the 'buckminster.cspec.
>
> If none of these files are present in the component, a provider with
> your setting for the 'componentTypes' attribute will fail.
>
> If you don't have any meta-data at all and if you are happy using the
> project name as the component name, then you can use
>
> componentTypes="unknown"
>
> How are your components structured? Do they have any meta-data that
> describes things like name, version, and dependencies? If it does, and
> if Buckminster has no component type that recognizes it, such a type is
> fairly easy to add.
>
> Regards,
> Thomas Hallgren
>
>
> brodericke wrote:
>
>> Hi All,
>>
>> I just started playing around with buckminster today and I was
>>
> wondering if
>
>> someone could answer a couple questions for me.
>>
>> I've been trying to create a cquery and rmap for a project which lives
>>
> in
>
>> our cvs repository. Here's my provider configuration:
>>
>> <provider
>> readerType="cvs"
>> componentTypes="osgi.bundle,eclipse.feature,buckminster"
>> source="true" mutable="false">
>> <uri
>>
> format=":pserver:brodericke:*****@********:/opt/cvsroot,{0} ">
>
>> <bc:propertyRef key="buckminster.component" />
>> </uri>
>> </provider>
>>
>> It seems to me like I'm only able to materialize my cquery when there
>>
> is a
>
>> cspec file in the root of my project in cvs. When I take out the cspec
>>
> file,
>
>> I see errors like:
>>
>> ERROR [0001] : No suitable provider for component
>> buckminster_project:buckminster was found in searchPath default
>> ERROR [0001] : Provider
>>
>>
> cvs(:pserver:brodericke:*****@********:/opt/cvsroot,buckmins ter_project)
> : No
>
>> match found for component buckminster_project
>>
>> Is this observation correct or am I just missing something? Do I need
>>
> to
>
>> have a cspec file checked in under the root of my project in cvs? If
>>
> that's
>
>> true, is there any way to point buckminster to a cspec file that's
>>
> located
>
>> somewhere else?
>>
>> Thanks,
>> Evan
>>
>>
>>
>
> _______________________________________________
> buckminster-dev mailing list
> buckminster-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
> _______________________________________________
> buckminster-dev mailing list
> buckminster-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>
|
|
|
Goto Forum:
Current Time: Thu Sep 26 15:44:59 GMT 2024
Powered by FUDForum. Page generated in 0.03110 seconds |
] 
Search
Help
Register
Login
Home
