Linda,
I just started the test round of integration build on CruiseControl,
so we'll get the notification from build system and will see if
everything's ok or not.
Bests,
Max
Linda Damus wrote:
I just double-checked all of the
runtime
plugin manifests and caught a few more mistakes. Hopefully Max started
the build after I delivered the fixes, or that these particular
mistakes
won't cause the build to fail. The main one was:
org.eclipse.ui.console;bundle-version="[3.1.0,4.0.0)"
--Linda
Thanks, Linda! Max has started a
new I-build run.
Best,
Rich
On 4/7/06 8:56 AM, "Linda Damus" <ldamus@xxxxxxxxxx> wrote:
Hi Richard,
Yes, this was my mistake. I used a tool to update the manifest files,
and I suppose that was the version that I had in my environment. I
have delivered a fix for:
org.eclipse.core.runtime.compatibility;bundle-version="[3.1.0,4.0.0)",
org.junit;bundle-version="[3.8.0,4.0.0)"
I presume this is what caused the continuous build to fail, too.
Very sorry for the inconvenience,
Linda
Richard Gronback <richard.gronback@xxxxxxxxxxx>
Sent by: gmf-dev-bounces@xxxxxxxxxxx
04/07/2006 08:43 AM
Please respond to
"GMF Project developer discussions."
"GMF Project developer discussions."
<gmf-dev@xxxxxxxxxxx>
Re: [gmf-dev] Listing all our
plug-in dependencies
accurately
Hi All,
Some of the runtime plug-ins are now expressing in Require-Bundle:
org.eclipse.core.runtime.compatibility;bundle-version="[3.1.100,4.0.0)"
(which causes errors in my workspace). Looking at the platform, they
are using:
org.eclipse.core.runtime.compatibility;bundle-version="[3.1.0,4.0.0)"
This does not cause a workspace error, and I believe it’s what we
should
be using. Or, have I missed something?
Thanks,
Rich
On 4/5/06 3:17 PM, "Anthony Hunter" <anthonyh@xxxxxxxxxx>
wrote:
Hi Team,
As part of the plug-in versioning, http://www.eclipse.org/equinox/documents/plugin-versioning.html
<http://www.eclipse.org/equinox/documents/plugin-versioning.html>
we have a requirement that we list all our plug-in dependencies
accurately.
For example if the 'Require-Bundle' section looks like this initially:
Require-Bundle:
org.eclipse.core.runtime,
org.eclipse.ui.ide,
org.eclipse.jface,
org.eclipse.jface.text,
org.eclipse.xsd
It will get changed to this:
Require-Bundle:
org.eclipse.core.runtime;bundle-version="[3.2.0,4.0.0)",
org.eclipse.ui.ide;bundle-version="[3.2.0,4.0.0)",
org.eclipse.jface;bundle-version="[3.2.0,4.0.0)",
org.eclipse.jface.text;bundle-version="[3.2.0,4.0.0)",
org.eclipse.xsd;bundle-version="[2.2.0,3.0.0)"
We (Richard) already has added the .qualifier to the Bundle-Version for
our GMF plug-ins, we need to sweep the Require-Bundle next.
The runtime team will get the runtime plug-ins done for this weeks
milestone
build.
Cheers...
Anthony
--
Anthony Hunter mailto:anthonyh@xxxxxxxxxx
<mailto:anthonyh@xxxxxxxxxx>
Manager - Software Developer,
IBM Rational Software: Aurora Core Common / Modeling Tools
Phone: 613-591-7037
_______________________________________________
gmf-dev mailing list
gmf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gmf-dev
Sent using the Microsoft Entourage 2004 for Mac Test Drive._______________________________________________
gmf-dev mailing list
gmf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gmf-dev
_______________________________________________
gmf-dev mailing list
gmf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gmf-dev
Sent using the Microsoft Entourage 2004 for Mac Test Drive._______________________________________________
gmf-dev mailing list
gmf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gmf-dev
_______________________________________________
gmf-dev mailing list
gmf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gmf-dev
|
