Thanks for trying to help me this morning Gabriel; I was able to get a little further...
The instructions for building/running geoserver do not quite match what is going on on trunk; here is what I have been able to try thus far.
- upgrade to maven 2.0.10
- mvn clean install -Plegacy (this fails due to a compile error in legacy WMS)
- web/ - not to be used; since web2 is in use now
- community/web2 -could not start jetty - unable to find the correct version:
[INFO] Searching repository for plugin with prefix: 'jetty'.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist or no valid version could be found
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
I wonder if the jetty plugin is now in everyones local repository; and nobody has notice it go missing from the central repositories?
Thanks for trying to help me this morning Gabriel; I was able to get a little further...
The instructions for building/running geoserver do not quite match what is going on on trunk; here is what I have been able to try thus far.
- upgrade to maven 2.0.10
- mvn clean install -Plegacy (this fails due to a compile error in legacy WMS)
- web/ - not to be used; since web2 is in use now
- community/web2 -could not start jetty - unable to find the correct version:
The proper directory would have been community/web2/app, but
as you note below, there is another issue.
[INFO] Searching repository for plugin with prefix: 'jetty'.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist or no valid version could be found
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
I wonder if the jetty plugin is now in everyones local repository; and nobody has notice it go missing from the central repositories?
Thanks for trying to help me this morning Gabriel; I was able to get a little further...
The instructions for building/running geoserver do not quite match what is going on on trunk; here is what I have been able to try thus far.
- upgrade to maven 2.0.10
- mvn clean install -Plegacy (this fails due to a compile error in legacy WMS)
- web/ - not to be used; since web2 is in use now
- community/web2 -could not start jetty - unable to find the correct version:
The proper directory would have been community/web2/app, but
as you note below, there is another issue.
[INFO] Searching repository for plugin with prefix: 'jetty'.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist or no valid version could be found
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
I wonder if the jetty plugin is now in everyones local repository; and nobody has notice it go missing from the central repositories?
Ok, no, it's just the first issue. By running it from the wrong directory maven tries to guess the name of the plugin and comes up with
org.apache.maven.plugins:maven-jetty-plugin
Thanks for trying to help me this morning Gabriel; I was able to get a little further...
The instructions for building/running geoserver do not quite match what is going on on trunk;
Btw, the instructions have not been updated partly to the usual lazyness, partly because community/web2 is a temporary location,
once we reach feature parity web2 will be moved to the top and
renamed into web or something else.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Thanks for the help; making some progress now - changing the directory
helps. I am back to sorting out the compile error in legacy wms. Looks
to be WMS.setInterpoloation method has changed from a String to an
enum or something.
Jody
On Thu, Apr 2, 2009 at 5:28 PM, Andrea Aime <aaime@anonymised.com> wrote:
Jody Garnett ha scritto:
Thanks for trying to help me this morning Gabriel; I was able to get a
little further...
The instructions for building/running geoserver do not quite match what is
going on on trunk;
Btw, the instructions have not been updated partly to the usual lazyness,
partly because community/web2 is a temporary location,
once we reach feature parity web2 will be moved to the top and
renamed into web or something else.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Okay long story short; -Plegacy does not function; -Pweb2 is needed to
get web2 built obviously
The wiki now has a page on building geoserver 2.
Jody
On Thu, Apr 2, 2009 at 9:28 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Hi Andrea:
Thanks for the help; making some progress now - changing the directory
helps. I am back to sorting out the compile error in legacy wms. Looks
to be WMS.setInterpoloation method has changed from a String to an
enum or something.
Jody
On Thu, Apr 2, 2009 at 5:28 PM, Andrea Aime <aaime@anonymised.com> wrote:
Jody Garnett ha scritto:
Thanks for trying to help me this morning Gabriel; I was able to get a
little further...
The instructions for building/running geoserver do not quite match what is
going on on trunk;
Btw, the instructions have not been updated partly to the usual lazyness,
partly because community/web2 is a temporary location,
once we reach feature parity web2 will be moved to the top and
renamed into web or something else.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
