b3-dev

On 2011-05-11 05:54, joerg@xxxxxxxxxxxxx wrote:

Category org.eclipse.emf.cdo includes a requirement for bundle org.eclipse.emf.ecore [2.4.0,3.0.0) that cannot be 
fulfilled
However what "requirement" is talked about?

Obviously a category in a contribution is referring to a bundle that cannot be found.
Why are such problems reported in the error log view and not in the problem view? Why is the problematic category not 
marked in the editor?
It really should be. Please enter a bugzilla for this for EMF/emft.b3
- thomas
Did you check the log? The errors should be printed in there during
validation.

The Error log view you mean?
Yes, there are actually many errors all of the form e.g.
"
eclipse.buildId=M20100909-0800
java.version=1.6.0_23
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Command-line arguments:  -os win32 -ws win32 -arch x86

Error

Wed May 11 12:56:31 EST 2011

Category org.eclipse.emf.cdo includes a requirement for bundle 
org.eclipse.emf.ecore [2.4.0,3.0.0) that cannot be fulfilled

"

However what "requirement" is talked about? Why are such problems 
reported in the error log view and not in the problem view? Why is the 
problematic category not marked in the editor?
Did you check the log? The errors should be printed in there during validation.
- thomas
On 2011-05-11 04:58, joerg@xxxxxxxxxxxxx wrote:

I get following validation error without a hint what feature is problematic:
publishing result
Features without repositories

The feature are also not marked red in the editor, so what is wrong?
_______________________________________________
b3-dev mailing list
b3-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/b3-dev

I get following validation error without a hint what feature is problematic:
publishing result
Features without repositories

The feature are also not marked red in the editor, so what is wrong?
Ed, Henrik,
Projects are required to keep meta data up to date using the MyFoundation
Portal (http://portal.eclipse.org/).  The following problems were found
with this project's meta-data:

* Project home page (projecturl = http://www.eclipse.org/modeling/emft/b3/)
does not have an "About ","About This Project" or "Information
about " link. Projects are required to provide that standard link
on their home page (see
http://www.eclipse.org/projects/standard-link-on-home-page.php) .
The 'About' link should point to this URL: 
http://www.eclipse.org/projects/project_summary.php?projectid=modeling.emft
.b3

On 2011-04-12 07:59, joerg@xxxxxxxxxxxxx wrote:

Can you please explain why only legacy sites are affected?

Legacy sites are transformed on the fly into p2 sites. It's p2 and not the aggregator that does this but obviously there 
is something in the correlation between the aggregator and p2 that causes this failure when that happens. That's all I 
know without investigating this further.
Then, maybe its better to get in contact with the ANTLR people, telling them they should rebuild their update site 
(http://antlreclipse.sourceforge.net/updates/).
Absolutely. It's always better to provide a proper p2 site with meta-data. When p2 encounters a legacy site, it must 
download all feature jars in order to build the p2 meta-data. That is a slow process.
The b3 aggregator deals solely with p2 or Maven artifacts. Not sure I
follow your line of reasoning when you talk about the b3 in concjunction
with SVN. Can you please elaborate?

When a Eclipse developer has to configure his Eclipse to get ready for developing, (1) he first has to install a bunch 
of upate sites required by the project, and after this (2) he often checks out a bunch of SVN projects where the code 
resides, maybe from different SVN repositories.
With b3, (1) can be automated very well, however (2) is not automated by now. It would be nice, if not only p2 
artifacts can be added and grouped with b3, but also SVN projects within a category. So you could put SVN projects 
(actually only the SVN URLs) into a category, and maybe the category also contains all required p2 dependencies 
required for the SVN projects to compile.
This is out of scope for the b3 aggregator. Partly because what you find in SVN is a moving target. It doesn't have 
fixed versions yet since it hasn't been built and therefore it can not participate in a p2 resolution.
We provide another tool, Buckminster, that will perform a resolution of both SVN repositories and p2 repositories and 
then divide the downloaded material into workspace projects and target platform binaries. Very special requirements, and 
a very special logic must be used when transitively resolve features and bundles in source form. Buckminster is also 
capable of building a p2 update site based on your workspace content. Might be worth looking at.
- thomas

Hi, this bug fixing is quite slow, can I fix
https://bugs.eclipse.org/bugs/show_bug.cgi?id=338405 on my own?

The reason this bug has somewhat low priority is that it only affects
legacy sites and therefore very few users get exposed to it.

Can you please explain why only legacy sites are affected? Then, maybe 
its better to get in contact with the ANTLR people, telling them they 
should rebuild their update site 
(http://antlreclipse.sourceforge.net/updates/).

Does anybody know a concept of how to configure a workspace
considering a set of checked out SVN projects using a b3 aggregator
model? I use b3 to configure all plugin dependencies for an Eclipse
developer IDE, however if the developer can checked out the SVN
projects automatically by choosing some categories of interest from
the update site, this would be much time-saving for him!
The b3 aggregator deals solely with p2 or Maven artifacts. Not sure I
follow your line of reasoning when you talk about the b3 in concjunction
with SVN. Can you please elaborate?

When a Eclipse developer has to configure his Eclipse to get ready for 
developing, (1) he first has to install a bunch of upate sites required 
by the project, and after this (2) he often checks out a bunch of SVN 
projects where the code resides, maybe from different SVN repositories.
With b3, (1) can be automated very well, however (2) is not automated by 
now. It would be nice, if not only p2 artifacts can be added and grouped 
with b3, but also SVN projects within a category. So you could put SVN 
projects (actually only the SVN URLs) into a category, and maybe the 
category also contains all required p2 dependencies required for the SVN 
projects to compile.
One way to do it is maybe to mark an added feature with a boolean 
property "asSource", so the feature is not installed into the Eclipse 
IDE but actually the SVN source projects are imported. A feature is made 
up of a bunch of plugins, so installing such a feature marked with 
"asSource" imports all those plugins from SVN repositoris into the 
workspace of the developer. b3 would need to know where to find the SVN 
location of a plugin, this could be done by defining a set of SVN parent 
directory URLs, and b3 checks each parent directory if the project is 
contained in the directory (assuming the plugin name has the same name 
as the directoy name of the SVN project, which belongs to the best 
pratices). Instead of using a feature, one could also use a product maybe.
Ok, actually p2 must implement this logic, however if this is not 
possible, have you any idea how to automatic the checking out of SVN 
projects?
Cheers,
Joerg
Hi Joerg,
On 2011-04-12 06:04, joerg@xxxxxxxxxxxxx wrote:

Hi, this bug fixing is quite slow, can I fix https://bugs.eclipse.org/bugs/show_bug.cgi?id=338405 on my own?

The reason this bug has somewhat low priority is that it only affects legacy sites and therefore very few users get 
exposed to it. And yes, you can help fixing this bug. Check out our source from SVN and debug, see if you can find the 
problem. Then either tell us in the bugzilla or, even better, submit a patch.

Does anybody know a concept of how to configure a workspace considering a set of checked out SVN projects using a b3 
aggregator model? I use b3 to configure all plugin dependencies for an Eclipse developer IDE, however if the developer 
can checked out the SVN projects automatically by choosing some categories of interest from the update site, this 
would be much time-saving for him!
The b3 aggregator deals solely with p2 or Maven artifacts. Not sure I follow your line of reasoning when you talk about 
the b3 in concjunction with SVN. Can you please elaborate?
- thomas
Hi, this bug fixing is quite slow, can I fix 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=338405 on my own?
Does anybody know a concept of how to configure a workspace considering 
a set of checked out SVN projects using a b3 aggregator model? I use b3 
to configure all plugin dependencies for an Eclipse developer IDE, 
however if the developer can checked out the SVN projects automatically 
by choosing some categories of interest from the update site, this would 
be much time-saving for him!
issue fixed, and there *is* a link on the home page !
Henrik Lindberg
henrik.lindberg@xxxxxxxxxxxxxx

On Apr 5, 2011, at 6:00 AM, portal on behalf of emo wrote:
Ed, Henrik,

Projects are required to keep meta data up to date using the  
MyFoundation

Portal (http://portal.eclipse.org/).  The following problems were  
found

with this project's meta-data:
* The date for release "0.3" is in the past, but the release is not  
marked

as completed. If it is completed, it should be marked as completed;  
if it

has been postponed, it should be given a new target date.

* There is no next/future release of this project. All Eclipse  
projects

must have a "next release" planned and scheduled.

* Project home page (projecturl = http://www.eclipse.org/modeling/emft/b3/)

does not have an "About ","About This Project" or  
"Information

about " link. Projects are required to provide that  
standard link

on their home page (see

http://www.eclipse.org/projects/standard-link-on-home-page.php) .

The 'About' link should point to this URL:

http://www.eclipse.org/projects/project_summary.php?projectid=modeling.emft

.b3
_______________________________________________
b3-dev mailing list
b3-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/b3-dev

b3-dev

Re: [b3-dev] what is that error?

Re: [b3-dev] what is that error?

Re: [b3-dev] what is that error?

[b3-dev] what is that error?

[b3-dev] Project meta data is out of date for modeling.emft.b3

Re: [b3-dev] try not to mirror antlr

Re: [b3-dev] try not to mirror antlr

Re: [b3-dev] try not to mirror antlr

Re: [b3-dev] try not to mirror antlr

Re: [b3-dev] Project meta data is out of date for modeling.emft.b3