Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » COSMOS » How and what to check out from CVS?
How and what to check out from CVS? [message #9616] Tue, 04 December 2007 12:52 Go to next message
Michael Moser is currently offline Michael Moser
Messages: 914
Registered: July 2009
Senior Member
I am a bit lost re. the cosmos CVS organization and how to convert
(parts of) it into eclipse projects again.

When I look into the CVS then the content seems to be a load of *nested*
Eclipse projects (some actually doubly nested)!
But - at least to my knowledge - Eclipse doesn't support "nested"
projects - or am I missing something here?

So, if I check out the top-node (org.eclipse.cosmos) I end up with a
strange mess of things. There is ONE big project, that contains
everything but nothing is built in it, because it's .project contains no
"buildSpecs" and no "natures". Then there is a list of maybe 20 projects
which are partly put into my \JavaDevt-folder (where I usually save
things), partly in my .workspace folder (no idea, who/what controls what
ends up where). Most of these projects show build and/or compile errors
because they can't find libraries or references to other projects etc.

The same holds true, if I check out the the next "layer" of nodes (i.e.
only data-collection or data-reporting individually).

Is one really supposed to traverse the CVS and check out all the
leaf-projects individually? There are, I would roughly estimate, about
50 of them, so this would take quite some effort and at least an hour
just to check out the files from CVS. Tell me, that this is NOT what is
expected, please!

So, what is the correct approach to get all or a subset (like
"data-collection") out of the CVS and building in optimal time?

Michael
Re: How and what to check out from CVS? [message #9640 is a reply to message #9616] Tue, 04 December 2007 14:50 Go to previous messageGo to next message
Michael Moser is currently offline Michael Moser
Messages: 914
Registered: July 2009
Senior Member
I tried a trick to make eclipse iterate through the entire subtree and
regenerate all projects: I deleted (or rather renamed) all .project
files in higher layers (i.e. in ...cosmos, ...cosmos\data-collection,
....cosmos\resource-modeling, ...cosmos\test\data-collection, and
....cosmos\test\resource-modeling) and this made eclipse show me
ALL "leaf projects" when using "Import existing projects".

While doing so I had to learn, that two project-names "broker-server"
and "domain-server" exist twice, once in data-collection and once under
sandbox and test, resp.. BTW: it would be nice, if all projects would
stick to a common naming convention (org.eclipse.cosmos....) so that
they show up adjacent in the Package-Explorer. There are a few
"run-aways" (broker-server, domain-server, ...)

Other issues are: specific JREs listed as prereq's. E.g. does it REALLY
have to be 1.5.11? Wouldn't any 1.5 JRE do?

Furthermore:

I get 4 errors re. illegal wsdl:
Severity and Description Path Resource Location Creation Time Id
s4s-att-not-allowed: Attribute 'maxOccurs' cannot appear in element
'element'. broker-server/WebContent/WEB-INF/classes/wsdl MyService.wsdl
line 1298 1196779379492 2915
s4s-att-not-allowed: Attribute 'maxOccurs' cannot appear in element
'element'. domain-server/WebContent/WEB-INF/classes/wsdl MyService.wsdl
line 1273 1196775687555 992
s4s-att-not-allowed: Attribute 'maxOccurs' cannot appear in element
'element'. sandbox-broker-server/WebContent/WEB-INF/classes/wsdl
MyService.wsdl line 1297 1196775701320 1923
s4s-att-not-allowed: Attribute 'maxOccurs' cannot appear in element
'element'. sandbox-domain-server/WebContent/WEB-INF/classes/wsdl
MyService.wsdl line 1273 1196775701477 1924



....and another 4 errors re. unsatisfied javax.wsdl constraints:
Severity and Description Path Resource Location Creation Time Id
Unsatisfied constraint: 'Import-Package: javax.wsdl; version="1.6.1"'
org.eclipse.cosmos.dc.mgmt.wsdm/META-INF MANIFEST.MF line 11
1196779555164 3651
Unsatisfied constraint: 'Import-Package: javax.wsdl.factory;
version="1.6.1"' org.eclipse.cosmos.dc.dataManager/META-INF MANIFEST.MF
line 10 1196779536477 3039
Unsatisfied constraint: 'Import-Package: javax.wsdl.factory;
version="1.6.1"' org.eclipse.cosmos.rm.sml.mdr/META-INF MANIFEST.MF line
14 1196779545586 3319
Unsatisfied constraint: 'Import-Package: javax.wsdl.xml;
version="1.6.1"' org.eclipse.cosmos.dc.mgmt.wsdm/META-INF MANIFEST.MF
line 12 1196779555164 3652

What javax.wsdl package is needed for this?


and finally, there are a couple of errors re. a missing JSON-Outputter:
Severity and Description Path Resource Location Creation Time Id
IJSONOutputter cannot be resolved to a type
org.eclipse.cosmos.dr.tests/src/org/eclipse/cosmos/dr/drs/se rvice/handler/sml
JSONSMLOutputterTest.java line 124 1196779549383 3328
IJSONOutputter cannot be resolved to a type
org.eclipse.cosmos.dr.tests/src/org/eclipse/cosmos/dr/drs/se rvice/handler/sml
JSONSMLOutputterTest.java line 124 1196779549383 3329
JSONOutputterReader cannot be resolved to a type
org.eclipse.cosmos.dr.tests/src/org/eclipse/cosmos/dr/drs/se rvice/handler/sml
JSONSMLOutputterTest.java line 71 1196779549383 3322
JSONOutputterReader cannot be resolved to a type
org.eclipse.cosmos.dr.tests/src/org/eclipse/cosmos/dr/drs/se rvice/handler/sml
JSONSMLOutputterTest.java line 71 1196779549383 3323
NavigatorOutputter cannot be resolved to a type
org.eclipse.cosmos.dr.tests/src/org/eclipse/cosmos/dr/drs/se rvice/handler/sml
JSONSMLOutputterTest.java line 92 1196779549383 3326
NavigatorOutputter cannot be resolved to a type
org.eclipse.cosmos.dr.tests/src/org/eclipse/cosmos/dr/drs/se rvice/handler/sml
JSONSMLOutputterTest.java line 92 1196779549383 3327

Where's that JSON stuff supposed to come from?

Michael
Re: How and what to check out from CVS? [message #9663 is a reply to message #9616] Tue, 04 December 2007 15:50 Go to previous messageGo to next message
No real name is currently offline No real name
Messages: 404
Registered: July 2009
Senior Member
Hi Michael,

The CVS is structured based on COSMOS 4 subprojects:
1) data-collection
2) data-reporting
3) management-enablement
4) resource-modeling

The plug-ins under the subprojects are what gets regularly build.
In addition to the 4 root folders listed above, there are a few other
folders that are used for various reasons:

* doc - Used for documentations
* examples - Contains samples that illustrate the usage of the COSMOS
framework
* releng - Contains release engineering resources
* sandbox - Place holder for experimental code that is not yet ready to be
included as part of the build
* tests - Contains testing resources for plug-ins that belong to each
subproject

What you need really depends on what you intend to do with COSMOS. I
recommend reviewing the consumer documentations available on COSMOS website:

http://www.eclipse.org/cosmos/home/documents/

Good luck,

Ali Mehregani

"Michael Moser" <mmo@zurich.ibm.com> wrote in message
news:fj3ij1$oen$1@build.eclipse.org...
>I am a bit lost re. the cosmos CVS organization and how to convert (parts
>of) it into eclipse projects again.
>
> When I look into the CVS then the content seems to be a load of *nested*
> Eclipse projects (some actually doubly nested)!
> But - at least to my knowledge - Eclipse doesn't support "nested"
> rojects - or am I missing something here?
>
> So, if I check out the top-node (org.eclipse.cosmos) I end up with a
> strange mess of things. There is ONE big project, that contains everything
> but nothing is built in it, because it's .project contains no "buildSpecs"
> and no "natures". Then there is a list of maybe 20 projects which are
> partly put into my \JavaDevt-folder (where I usually save things), partly
> in my .workspace folder (no idea, who/what controls what ends up where).
> Most of these projects show build and/or compile errors because they can't
> find libraries or references to other projects etc.
>
> The same holds true, if I check out the the next "layer" of nodes (i.e.
> only data-collection or data-reporting individually).
>
> Is one really supposed to traverse the CVS and check out all the
> leaf-projects individually? There are, I would roughly estimate, about 50
> of them, so this would take quite some effort and at least an hour just to
> check out the files from CVS. Tell me, that this is NOT what is expected,
> please!
>
> So, what is the correct approach to get all or a subset (like
> "data-collection") out of the CVS and building in optimal time?
>
> Michael
>
>
>
>
Re: How and what to check out from CVS? [message #9684 is a reply to message #9640] Tue, 04 December 2007 16:26 Go to previous message
Eclipse User
Originally posted by: david_whiteman.us.ibm.com

Michael Moser wrote:

> Other issues are: specific JREs listed as prereq's. E.g. does it REALLY
> have to be 1.5.11? Wouldn't any 1.5 JRE do?

For IBM JREs., any 1.5 version will do. For Sun JREs, we specifically
mention a minimum level of 1.5.0_13 because some components that use SAX
parsing, such as the CMDBf toolkit and the SML-IF validator, fail to
operate correctly on previous Sun 1.5 implementations, due to an
apparent Sun bug. It appears that IBM fixed the bug in Sun source long
before Sun got around to it.

David
Re: How and what to check out from CVS? [message #570775 is a reply to message #9616] Tue, 04 December 2007 14:50 Go to previous message
Michael Moser is currently offline Michael Moser
Messages: 914
Registered: July 2009
Senior Member
I tried a trick to make eclipse iterate through the entire subtree and
regenerate all projects: I deleted (or rather renamed) all .project
files in higher layers (i.e. in ...cosmos, ...cosmos\data-collection,
....cosmos\resource-modeling, ...cosmos\test\data-collection, and
....cosmos\test\resource-modeling) and this made eclipse show me
ALL "leaf projects" when using "Import existing projects".

While doing so I had to learn, that two project-names "broker-server"
and "domain-server" exist twice, once in data-collection and once under
sandbox and test, resp.. BTW: it would be nice, if all projects would
stick to a common naming convention (org.eclipse.cosmos....) so that
they show up adjacent in the Package-Explorer. There are a few
"run-aways" (broker-server, domain-server, ...)

Other issues are: specific JREs listed as prereq's. E.g. does it REALLY
have to be 1.5.11? Wouldn't any 1.5 JRE do?

Furthermore:

I get 4 errors re. illegal wsdl:
Severity and Description Path Resource Location Creation Time Id
s4s-att-not-allowed: Attribute 'maxOccurs' cannot appear in element
'element'. broker-server/WebContent/WEB-INF/classes/wsdl MyService.wsdl
line 1298 1196779379492 2915
s4s-att-not-allowed: Attribute 'maxOccurs' cannot appear in element
'element'. domain-server/WebContent/WEB-INF/classes/wsdl MyService.wsdl
line 1273 1196775687555 992
s4s-att-not-allowed: Attribute 'maxOccurs' cannot appear in element
'element'. sandbox-broker-server/WebContent/WEB-INF/classes/wsdl
MyService.wsdl line 1297 1196775701320 1923
s4s-att-not-allowed: Attribute 'maxOccurs' cannot appear in element
'element'. sandbox-domain-server/WebContent/WEB-INF/classes/wsdl
MyService.wsdl line 1273 1196775701477 1924



....and another 4 errors re. unsatisfied javax.wsdl constraints:
Severity and Description Path Resource Location Creation Time Id
Unsatisfied constraint: 'Import-Package: javax.wsdl; version="1.6.1"'
org.eclipse.cosmos.dc.mgmt.wsdm/META-INF MANIFEST.MF line 11
1196779555164 3651
Unsatisfied constraint: 'Import-Package: javax.wsdl.factory;
version="1.6.1"' org.eclipse.cosmos.dc.dataManager/META-INF MANIFEST.MF
line 10 1196779536477 3039
Unsatisfied constraint: 'Import-Package: javax.wsdl.factory;
version="1.6.1"' org.eclipse.cosmos.rm.sml.mdr/META-INF MANIFEST.MF line
14 1196779545586 3319
Unsatisfied constraint: 'Import-Package: javax.wsdl.xml;
version="1.6.1"' org.eclipse.cosmos.dc.mgmt.wsdm/META-INF MANIFEST.MF
line 12 1196779555164 3652

What javax.wsdl package is needed for this?


and finally, there are a couple of errors re. a missing JSON-Outputter:
Severity and Description Path Resource Location Creation Time Id
IJSONOutputter cannot be resolved to a type
org.eclipse.cosmos.dr.tests/src/org/eclipse/cosmos/dr/drs/se rvice/handler/sml
JSONSMLOutputterTest.java line 124 1196779549383 3328
IJSONOutputter cannot be resolved to a type
org.eclipse.cosmos.dr.tests/src/org/eclipse/cosmos/dr/drs/se rvice/handler/sml
JSONSMLOutputterTest.java line 124 1196779549383 3329
JSONOutputterReader cannot be resolved to a type
org.eclipse.cosmos.dr.tests/src/org/eclipse/cosmos/dr/drs/se rvice/handler/sml
JSONSMLOutputterTest.java line 71 1196779549383 3322
JSONOutputterReader cannot be resolved to a type
org.eclipse.cosmos.dr.tests/src/org/eclipse/cosmos/dr/drs/se rvice/handler/sml
JSONSMLOutputterTest.java line 71 1196779549383 3323
NavigatorOutputter cannot be resolved to a type
org.eclipse.cosmos.dr.tests/src/org/eclipse/cosmos/dr/drs/se rvice/handler/sml
JSONSMLOutputterTest.java line 92 1196779549383 3326
NavigatorOutputter cannot be resolved to a type
org.eclipse.cosmos.dr.tests/src/org/eclipse/cosmos/dr/drs/se rvice/handler/sml
JSONSMLOutputterTest.java line 92 1196779549383 3327

Where's that JSON stuff supposed to come from?

Michael
Re: How and what to check out from CVS? [message #570808 is a reply to message #9616] Tue, 04 December 2007 15:50 Go to previous message
No real name is currently offline No real name
Messages: 404
Registered: July 2009
Senior Member
Hi Michael,

The CVS is structured based on COSMOS 4 subprojects:
1) data-collection
2) data-reporting
3) management-enablement
4) resource-modeling

The plug-ins under the subprojects are what gets regularly build.
In addition to the 4 root folders listed above, there are a few other
folders that are used for various reasons:

* doc - Used for documentations
* examples - Contains samples that illustrate the usage of the COSMOS
framework
* releng - Contains release engineering resources
* sandbox - Place holder for experimental code that is not yet ready to be
included as part of the build
* tests - Contains testing resources for plug-ins that belong to each
subproject

What you need really depends on what you intend to do with COSMOS. I
recommend reviewing the consumer documentations available on COSMOS website:

http://www.eclipse.org/cosmos/home/documents/

Good luck,

Ali Mehregani

"Michael Moser" <mmo@zurich.ibm.com> wrote in message
news:fj3ij1$oen$1@build.eclipse.org...
>I am a bit lost re. the cosmos CVS organization and how to convert (parts
>of) it into eclipse projects again.
>
> When I look into the CVS then the content seems to be a load of *nested*
> Eclipse projects (some actually doubly nested)!
> But - at least to my knowledge - Eclipse doesn't support "nested"
> rojects - or am I missing something here?
>
> So, if I check out the top-node (org.eclipse.cosmos) I end up with a
> strange mess of things. There is ONE big project, that contains everything
> but nothing is built in it, because it's .project contains no "buildSpecs"
> and no "natures". Then there is a list of maybe 20 projects which are
> partly put into my \JavaDevt-folder (where I usually save things), partly
> in my .workspace folder (no idea, who/what controls what ends up where).
> Most of these projects show build and/or compile errors because they can't
> find libraries or references to other projects etc.
>
> The same holds true, if I check out the the next "layer" of nodes (i.e.
> only data-collection or data-reporting individually).
>
> Is one really supposed to traverse the CVS and check out all the
> leaf-projects individually? There are, I would roughly estimate, about 50
> of them, so this would take quite some effort and at least an hour just to
> check out the files from CVS. Tell me, that this is NOT what is expected,
> please!
>
> So, what is the correct approach to get all or a subset (like
> "data-collection") out of the CVS and building in optimal time?
>
> Michael
>
>
>
>
Re: How and what to check out from CVS? [message #570843 is a reply to message #9640] Tue, 04 December 2007 16:26 Go to previous message
David Whiteman is currently offline David Whiteman
Messages: 166
Registered: July 2009
Senior Member
Michael Moser wrote:

> Other issues are: specific JREs listed as prereq's. E.g. does it REALLY
> have to be 1.5.11? Wouldn't any 1.5 JRE do?

For IBM JREs., any 1.5 version will do. For Sun JREs, we specifically
mention a minimum level of 1.5.0_13 because some components that use SAX
parsing, such as the CMDBf toolkit and the SML-IF validator, fail to
operate correctly on previous Sun 1.5 implementations, due to an
apparent Sun bug. It appears that IBM fixed the bug in Sun source long
before Sun got around to it.

David
Previous Topic:How and what to check out from CVS?
Next Topic:Hardware specification templates for Eclipse projects
Goto Forum:
  


Current Time: Tue Sep 23 08:34:14 GMT 2014

Powered by FUDForum. Page generated in 0.06099 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software