2012/6/6 David M Williams david_willi...@us.ibm.com
Admittedly, there is one day left for Juno RC3, but I can't help but point
out several (27) missing about.html files.
http://build.eclipse.org/juno/simrel/reporeports/reports/layoutCheck.txt
Plus, according to another report,
Hi,
The “missing about.html” is fixed in Libra plugins:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=381816.
The next run of the Juno aggregation build should see the fix.
Greetings,
Kaloyan
From: cross-project-issues-dev-boun...@eclipse.org
Hey folks. I'm going through the layout and licenses reports today.
I've already opened a couple of bugs regarding missing about files and
am just starting into the licenses. These issues need to be addressed
before any reviews can be declared successful. Note that these are very
basic
Frankly, that one was only on my just curious list. We have a long and
distinguished list of fair exceptions.
One of the things that I'm going to add into the new project management
stuff is the ability to specify bundle names (and patterns) owned by a
project.
Wayne
On 06/06/2012 09:23 AM,
I don't know anything about why gemini.jpa or gef3d are getting added to
the repo, but this made me think about your question:
If these bundles are in the repository, shouldn't the owning projects be
Juno particpants?
I don't know the correct answer, but it strikes me as odd that we allow
Fixed for the Linux Tools plugins. Linux Tools b3aggrcon updated to
point to the new build.
-- Jeff J.
On 06/06/2012 12:09 AM, David M Williams wrote:
Admittedly, there is one day left for Juno RC3, but I can't help but
point out several (27) missing about.html files.
Hi,
out several (27) missing about.html files.
http://build.eclipse.org/juno/simrel/reporeports/reports/layoutCheck.txt
Linux Tools apologizes for these missing files and will get them fixed
ASAP (for RC4).
https://bugs.eclipse.org/bugs/show_bug.cgi?id=381880
Hi,
Just to shed some lights into the issue. Gyrex requires Gemini JPA for
its EclipseLink JPA integration. Gemini JPA does not provide a p2
repository. Thus, it's in the Gyrex repo which is part of Juno.
Any ideas how to proceed?
Migrating to some external library just because Gemini isn't
Hi
Surely a release consists of on-train projects + Orbit, so if they're
not on-train they should frozen be in Orbit.
Regards
Ed Willink
On 06/06/2012 17:13, Gunnar Wagenknecht wrote:
Hi,
Just to shed some lights into the issue. Gyrex requires Gemini JPA for
its EclipseLink
Copying to cross project.
Wayne
On 06/06/2012 12:39 PM, Wayne Beaton wrote:
Sorry Gunnar. False alarm. As long as you're using released Gemini JPA
bits, you're good-to-go.
This was clarified on the Planning Council call today.
Wayne
On 06/06/2012 12:13 PM, Gunnar Wagenknecht wrote:
Hi,
FYI, would be nice if committers can help test to catch any last minute
issues.
-- Forwarded message --
From: Matthias Sohn matthias.s...@googlemail.com
Date: Wed, Jun 6, 2012 at 7:19 AM
Subject: [egit-dev] test RC3
To: JGit Developers list jgit-...@eclipse.org, EGit developer
AMP must be the cause for GEF3D, but I'm not sure why that is happening. AMP as
a stand-alone project includes GEF3D, but we created a non-GEF3D feature for
Indigo/Juno specifically because GEF3D isn't on release train and because
GEF3Ds 3D lib dependencies all live in IP hell. The feature we
This question has come up before if an Eclipse Project can release,
while it depends on something that is not released. And there are two
flavors: a) the dependency has never released at all, and b) the
dependency has been released before, but the project is not participating
in current
... and as a result org.eclipse.equinox.concurrent no longer part of
Eclipse Platform runtime as of RC4.
The greediness report is looking much better; thanks to all for paying
attention to details and making the common repo better.
Thanks for the clarification, David.
Wayne
On 06/06/2012 12:34 PM, David M Williams wrote:
This question has come up before if
an Eclipse Project can release, while it depends on something that
is not
released. And there are
My understanding was the the aggregator pulled the feature -- and only
the feature -- dependencies it needed from the aggregated site(s). Is that
not correct?
That is pretty much the case ... but ... it can get complicated. Do you
have any optional dependencies on it and do you publish
Hmm… I assumed that Buckminster would not be greedy. This reply seems to imply
that it *will* be, but perhaps wasn't.
http://dev.eclipse.org/mhonarc/lists/buckminster-dev/msg01320.html
Looking at the report, I have some that are there because they're defined via
xtext settings, as well as the
One of the items on the Juno Final Daze doc [1] is to clean up old builds.
I'd like to thank everyone for chipping in:
May 4Downloads: 599G Archives: 982G
June 6Downloads: 542GArchives: 987G
Downloads are down a whopping 55G, and we're down 5G overall. Many thanks!
Denis
http://download.eclipse.org/releases/staging/
One more to go!
Test well!
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
19 matches
Mail list logo
