[Geoserver-users] eclipse integration with partial failures

I'm not sure but either the maven poms, dependencies, remote repositories
have
been improved since the last two weeks or the invocation of 'mvn install' in
advance
of 'mvn eclipse:eclipse' is resposible for the better results. I'm now able
to import
most of the eclipse projects without errors only two projects remain with
errors.
These are "net.opengis.ows" and "net.opengis.wfs". The reported errors are
attached
below. The last time I tried to import the projects into eclipse allmost all
had erros. As I wrote, this time I called 'mvn install' in advance. If this
is mandatory,
it would be worth to be mentioned in the documentation.

For non maven experts it might also be helpfull to mention the
'mvn -DdownloadSources=true eclipse:eclipse' command, which forces the
download
of source code attachements and provides better debugging capabilities.

-------------------------------------------------------------------------------------------------------

Eclipse SDK
Version: 3.2.2
Build id: M20070212-1330

Severity and Description Path Resource Location Creation Time Id
Bundle 'org.eclipse.emf.ecore' cannot be resolved net.opengis.ows/META-INF
MANIFEST.MF line 12 1180527498453 1194
Bundle 'org.eclipse.emf.ecore' cannot be resolved net.opengis.wfs/META-INF
MANIFEST.MF line 12 1180527499562 1199
Unknown extension point: 'org.eclipse.emf.ecore.generated_package'
net.opengis.ows plugin.xml line 13 1180527498422 1193
Unknown extension point: 'org.eclipse.emf.ecore.generated_package'
net.opengis.wfs plugin.xml line 13 1180527499562 1198

--
View this message in context: http://www.nabble.com/eclipse-integration-with-partial-failures-tf3840118.html#a10872857
Sent from the GeoServer - User mailing list archive at Nabble.com.

w2y4m ha scritto:

I'm not sure but either the maven poms, dependencies, remote repositories
have
been improved since the last two weeks or the invocation of 'mvn install' in
advance
of 'mvn eclipse:eclipse' is resposible for the better results. I'm now able
to import
most of the eclipse projects without errors only two projects remain with
errors.
These are "net.opengis.ows" and "net.opengis.wfs". The reported errors are
attached
below. The last time I tried to import the projects into eclipse allmost all
had erros. As I wrote, this time I called 'mvn install' in advance. If this
is mandatory,
it would be worth to be mentioned in the documentation.

Yeah, it's mandatory but just the first time you try to set up thing, or
when new dependencies are introduced. mvn eclipse:eclipse does not force
jars to be downloaded. The guide in fact says:

.........................................................................
Before building GeoServer with your Eclipse IDE you must:

    1. Setup your Eclipse IDE
    2. Build all GeoServer modules
.........................................................................

(the two sentences have links to pages with more explainations)
Anyways, I made this more explicit now.

For non maven experts it might also be helpfull to mention the 'mvn -DdownloadSources=true eclipse:eclipse' command, which forces the
download
of source code attachements and provides better debugging capabilities.

Indeed, good idea, merged it.

-------------------------------------------------------------------------------------------------------

Eclipse SDK
Version: 3.2.2
Build id: M20070212-1330

Severity and Description Path Resource Location Creation Time Id
Bundle 'org.eclipse.emf.ecore' cannot be resolved net.opengis.ows/META-INF
MANIFEST.MF line 12 1180527498453 1194
Bundle 'org.eclipse.emf.ecore' cannot be resolved net.opengis.wfs/META-INF
MANIFEST.MF line 12 1180527499562 1199
Unknown extension point: 'org.eclipse.emf.ecore.generated_package'
net.opengis.ows plugin.xml line 13 1180527498422 1193
Unknown extension point: 'org.eclipse.emf.ecore.generated_package'
net.opengis.wfs plugin.xml line 13 1180527499562 1198

I think you can largerly ignore these errors, it should not affect
Geoserver in any way. You probably won't be able to regenerated the
classes in these packages from the annotated interfaces, but this
is something you're expected to do unless you're hacking the WFS
xml bindings. If you really can't stand these errors, I think installing
EMF in Eclipse should solve the problem.

Cheers
Andrea