Eclipse Community Forums: Buckminster » Is there support form properties in an Aggregator model?

Help

Home

Home » Archived » Buckminster » Is there support form properties in an Aggregator model?

Show: Today's Messages :: Show Polls :: Message Navigator

Is there support form properties in an Aggregator model? [message #515376]

Thu, 18 February 2010 15:39

John

Messages: 107
Registered: July 2009

Senior Member

Actually I guess the answer is no. But I would really like it.

It's generally supported in various Buckminster files (although not completely) and it really makes it a lot simpler to make the various files, since they can be used in different situations just by setting e few properties.

Like in this case where I want to aggregate a number of sites and use one validation site. Here's the model:

<?xml version="1.0" encoding="UTF-8"?>
<aggregator:Aggregator xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:aggregator="http://www.eclipse.org/buckminster/2009/aggregator" description="The aggregated update site for NBD" label="NBD">
<configurations/>
<contributions label="NBD">
<repositories location="${my.company.bd.build.c.site}" mirrorArtifacts="false" categoryPrefix="C">
<metadataRepository href="p2:${my.company.bd.build.c.site}#//@metadataRepository "/>
</repositories>
<repositories location="${my.company.bd.build.p.site}" mirrorArtifacts="false" categoryPrefix="P">
<metadataRepository href="p2:${my.company.bd.build.p.site}#//@metadataRepository "/>
</repositories>
<repositories location="${my.company.bd.build.pn.site}" mirrorArtifacts="false" categoryPrefix="PN">
<metadataRepository href="p2:${my.company.bd.build.pn.site}#//@metadataRepository "/>
</repositories>
</contributions>
<validationRepositories location="${my.company.bd.build.eclipse.site}">
<metadataRepository href=" p2:${my.company.bd.build.eclipse.site}#//@metadataRepository "/>
</validationRepositories>
</aggregator:Aggregator>

Unfortunately it doesn't work and I get the error below if I try to use a property for the validation repository.

I need to sometimes aggregate our release sites and sometimes mix release sites with development sites.

Say, typically developers will work off of release sites for dependencies, but sometimes they need to evaluate/use a development version of a plugin, which is published on a development site. Instead of making a new model file, we could just change the value of a property to do this.

Can this be accomplished in some way?

Thanks.

/John.

INFO: aggregate '--buildModel' './aggregate-site.build' '--action' 'CLEAN_BUILD' '--buildRoot' 'C:/temp/nbd/aggregate-site/aggregate-site-root'
ERROR: The feature 'metadataRepository' of 'org.eclipse.buckminster.aggregator.impl.MetadataRepositoryR eferenceImpl @1022de4 {file:/C:/ccviews/psd_build_main_latest/NTP_NCD/build/script /./aggregate-site.build#//@validationRepositories.0}' contains an unresolved proxy 'org.eclipse.buckminster.aggregator.p2.impl.MetadataReposito ryImpl @130998 {p2:${my.company.bd.build.eclipse.site.dir}#//@metadataRepos itory}'
ERROR: Build failed! Exception was org.eclipse.core.runtime.CoreException: Build model validation failed: Diagnosis of org.eclipse.buckminster.aggregator.impl.AggregatorImpl@1265109 {file:/C:/ccviews/psd_build_main_latest/NTP_NCD/build/script /./aggregate-site.build#/}
org.eclipse.core.runtime.CoreException: Build model validation failed: Diagnosis of org.eclipse.buckminster.aggregator.impl.AggregatorImpl@1265109 {file:/C:/ccviews/psd_build_main_latest/NTP_NCD/build/script /./aggregate-site.build#/}
at org.eclipse.buckminster.runtime.BuckminsterException.fromMes sage(BuckminsterException.java:64)
at org.eclipse.buckminster.runtime.BuckminsterException.fromMes sage(BuckminsterException.java:59)
at org.eclipse.buckminster.aggregator.engine.Builder.runTransfo rmation(Builder.java:1241)
at org.eclipse.buckminster.aggregator.engine.Builder.run(Builde r.java:635)
at org.eclipse.buckminster.aggregator.engine.Builder.run(Builde r.java:1059)
at org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:155)
at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 41)
at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 35)
at org.eclipse.buckminster.cmdline.Headless.start(Headless.java :189)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)

Report message to a moderator

Re: Is there support form properties in an Aggregator model? [message #515410 is a reply to message #515376]

Thu, 18 February 2010 12:12

Filip Hrbek

Messages: 233
Registered: July 2009

Senior Member

Hi John,

this sounds good. Please enter a bugzilla.

Note: I don't think we should merge this change into the Buckminster Aggregator 3.5, but we can include this functionality in the new b3 aggregator.

John napsal(a):
> Actually I guess the answer is no. But I would really like it.
>
> It's generally supported in various Buckminster files (although not
> completely) and it really makes it a lot simpler to make the various
> files, since they can be used in different situations just by setting e
> few properties.
>
> Like in this case where I want to aggregate a number of sites and use
> one validation site. Here's the model:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <aggregator:Aggregator xmi:version="2.0"
> xmlns:xmi="http://www.omg.org/XMI"
> xmlns:aggregator="http://www.eclipse.org/buckminster/2009/aggregator"
> description="The aggregated update site for NBD" label="NBD">
> <configurations/>
> <contributions label="NBD">
> <repositories location="${my.company.bd.build.c.site}"
> mirrorArtifacts="false" categoryPrefix="C">
> <metadataRepository
> href="p2:${my.company.bd.build.c.site}#//@metadataRepository "/>
> </repositories>
> <repositories location="${my.company.bd.build.p.site}"
> mirrorArtifacts="false" categoryPrefix="P">
> <metadataRepository
> href="p2:${my.company.bd.build.p.site}#//@metadataRepository "/>
> </repositories>
> <repositories location="${my.company.bd.build.pn.site}"
> mirrorArtifacts="false" categoryPrefix="PN">
> <metadataRepository
> href="p2:${my.company.bd.build.pn.site}#//@metadataRepository "/>
> </repositories>
> </contributions>
> <validationRepositories location="${my.company.bd.build.eclipse.site}">
> <metadataRepository href="
> p2:${my.company.bd.build.eclipse.site}#//@metadataRepository "/>
> </validationRepositories>
> </aggregator:Aggregator>
>
> Unfortunately it doesn't work and I get the error below if I try to use
> a property for the validation repository.
>
> I need to sometimes aggregate our release sites and sometimes mix
> release sites with development sites.
>
> Say, typically developers will work off of release sites for
> dependencies, but sometimes they need to evaluate/use a development
> version of a plugin, which is published on a development site. Instead
> of making a new model file, we could just change the value of a
> property to do this.
>
> Can this be accomplished in some way?
>
> Thanks.
>
> /John.
>
> INFO: aggregate '--buildModel' './aggregate-site.build' '--action'
> 'CLEAN_BUILD' '--buildRoot'
> 'C:/temp/nbd/aggregate-site/aggregate-site-root'
> ERROR: The feature 'metadataRepository' of
> mailto: 'org.eclipse.buckminster.aggregator.impl.MetadataRepositoryR eferenceImpl @1022de4
> {file:/C:/ccviews/psd_build_main_latest/NTP_NCD/build/script
> /./aggregate-site.build#//@validationRepositories.0}' contains an
> unresolved proxy
> mailto: 'org.eclipse.buckminster.aggregator.p2.impl.MetadataReposito ryImpl @130998
> {p2:${my.company.bd.build.eclipse.site.dir}#//@metadataRepos itory}'
> ERROR: Build failed! Exception was
> org.eclipse.core.runtime.CoreException: Build model validation failed:
> Diagnosis of
> mailto:org.eclipse.buckminster.aggregator.impl.AggregatorImpl@1265109
> {file:/C:/ccviews/psd_build_main_latest/NTP_NCD/build/script
> /./aggregate-site.build#/}
> org.eclipse.core.runtime.CoreException: Build model validation failed:
> Diagnosis of
> mailto:org.eclipse.buckminster.aggregator.impl.AggregatorImpl@1265109
> {file:/C:/ccviews/psd_build_main_latest/NTP_NCD/build/script
> /./aggregate-site.build#/}
> at org.eclipse.buckminster.runtime.BuckminsterException.fromMes
> sage(BuckminsterException.java:64)
> at org.eclipse.buckminster.runtime.BuckminsterException.fromMes
> sage(BuckminsterException.java:59)
> at org.eclipse.buckminster.aggregator.engine.Builder.runTransfo
> rmation(Builder.java:1241)
> at org.eclipse.buckminster.aggregator.engine.Builder.run(Builde
> r.java:635)
> at org.eclipse.buckminster.aggregator.engine.Builder.run(Builde
> r.java:1059)
> at org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs
> tractCommand.java:155)
> at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 41)
> at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 35)
> at org.eclipse.buckminster.cmdline.Headless.start(Headless.java
> :189)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips
> eAppHandle.java:194)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher
> .runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher
> .start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS
> tarter.java:368)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS
> tarter.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:
> 559)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1287)

Report message to a moderator

Re: Is there support form properties in an Aggregator model? [message #515534 is a reply to message #515410]

Fri, 19 February 2010 10:04

John

Messages: 107
Registered: July 2009

Senior Member

Added as

https://bugs.eclipse.org/bugs/show_bug.cgi?id=303289

Report message to a moderator

Previous Topic:	How to prevent: JRE container on the classpath is not a perfect match to the 'J2SE-1.5'
Next Topic:	variables not replaced in generator.buildTimestamp.format

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed Apr 24 17:00:35 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter