Hi,
I want to build geoserver 1.4x, which version of maven should I be using, I see there is a pom.xml file, should I be using Maven 2.0,
Thanks Again
Ok I have answered my own question, Geoserver used maven 1.02, since all hell breaks when you use version 2.02
Clint Lewis wrote:
Hi,
I want to build geoserver 1.4x, which version of maven should I be using, I see there is a pom.xml file, should I be using Maven 2.0,
Thanks Again
The pom files were just an experiment to try out maven 2.0, but i found it wasn't up to snuff yet. They really shouldn't be there because people will get odd behaviour when they try to use it.
However, just recently the eclipse support has gotten better, not sure about war support yet though. But worth trying again i think. However the pom.xml files are severley out of date. Does anyone know of any tools for converting 1.x poms to 2.x poms? That would be nice.
-Justin
Clint Lewis wrote:
Hi,
I want to build geoserver 1.4x, which version of maven should I be using, I see there is a pom.xml file, should I be using Maven 2.0,
Thanks Again
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Justin Deoliveira wrote:
The pom files were just an experiment to try out maven 2.0, but i found it wasn't up to snuff yet. They really shouldn't be there because people will get odd behaviour when they try to use it.
However, just recently the eclipse support has gotten better, not sure about war support yet though. But worth trying again i think. However the pom.xml files are severley out of date. Does anyone know of any tools for converting 1.x poms to 2.x poms? That would be nice.
If we could possibly go to maven 2 it would be great, I am not sure how much longer geotools will support maven 1.0.2. It comes down to an issue of time, and martin has put in the time to make maven 2 based builds releasable, and maven 1 is lagging behind.
I understand this may impact what build system you pursue in geoserver, and I recall you were taking over the maven build from James so I guess the tradeoffs are yours?
Jody
I agree, there is so much about maven 2 i like, and would love to migrate. But a new build system for geoserver is hard enough to sell to people without the bugs that I found with maven 2.0 when i tried it. I dont have the time to put into the geoserver that martin did for geotools. I would love if someone could volunteer on this one. Why dont we make it a topic at next IRC, and perhaps we can get the ball rolling.
-Justin
Jody Garnett wrote:
Justin Deoliveira wrote:
The pom files were just an experiment to try out maven 2.0, but i found it wasn't up to snuff yet. They really shouldn't be there because people will get odd behaviour when they try to use it.
However, just recently the eclipse support has gotten better, not sure about war support yet though. But worth trying again i think. However the pom.xml files are severley out of date. Does anyone know of any tools for converting 1.x poms to 2.x poms? That would be nice.
If we could possibly go to maven 2 it would be great, I am not sure how much longer geotools will support maven 1.0.2. It comes down to an issue of time, and martin has put in the time to make maven 2 based builds releasable, and maven 1 is lagging behind.
I understand this may impact what build system you pursue in geoserver, and I recall you were taking over the maven build from James so I guess the tradeoffs are yours?
Jody-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Justin Deoliveira wrote:
I agree, there is so much about maven 2 i like, and would love to migrate. But a new build system for geoserver is hard enough to sell to people without the bugs that I found with maven 2.0 when i tried it. I dont have the time to put into the geoserver that martin did for geotools. I would love if someone could volunteer on this one. Why dont we make it a topic at next IRC, and perhaps we can get the ball rolling.
Yep, but it may be a choice of doing maven 2 for geoserver, or doing maven 1 for both geotools and geoserver? Hense the tradeoff, sorry I don't got an easy answer.
How about an easy question: are they any remaining show stopping bugs in maven 2 (and by show stopping I mean war, eclipse, jetty).
Jody
-Justin
Jody Garnett wrote:
Justin Deoliveira wrote:
The pom files were just an experiment to try out maven 2.0, but i found it wasn't up to snuff yet. They really shouldn't be there because people will get odd behaviour when they try to use it.
However, just recently the eclipse support has gotten better, not sure about war support yet though. But worth trying again i think. However the pom.xml files are severley out of date. Does anyone know of any tools for converting 1.x poms to 2.x poms? That would be nice.
If we could possibly go to maven 2 it would be great, I am not sure how much longer geotools will support maven 1.0.2. It comes down to an issue of time, and martin has put in the time to make maven 2 based builds releasable, and maven 1 is lagging behind.
I understand this may impact what build system you pursue in geoserver, and I recall you were taking over the maven build from James so I guess the tradeoffs are yours?
Jody-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Jody Garnett wrote:
Justin Deoliveira wrote:
I agree, there is so much about maven 2 i like, and would love to migrate. But a new build system for geoserver is hard enough to sell to people without the bugs that I found with maven 2.0 when i tried it. I dont have the time to put into the geoserver that martin did for geotools. I would love if someone could volunteer on this one. Why dont we make it a topic at next IRC, and perhaps we can get the ball rolling.
Yep, but it may be a choice of doing maven 2 for geoserver, or doing maven 1 for both geotools and geoserver? Hense the tradeoff, sorry I don't got an easy answer.
How about an easy question: are they any remaining show stopping bugs in maven 2 (and by show stopping I mean war, eclipse, jetty).
Jody
Well after reading the documentation I think eclipse support is even smarter then before. Havent tried it though.
I just looked at war and it too looks like to have been improved.
Geoserver jetty support does use any of the maven support for jetty.
So there are defintley no show stoppers to make the move. Just need some time. If noone volunteers i can step up and start hacking out the scripts when i get spare time, if there is such a thing :).
-Justin
Jody Garnett wrote:
Justin Deoliveira wrote:
The pom files were just an experiment to try out maven 2.0, but i found it wasn't up to snuff yet. They really shouldn't be there because people will get odd behaviour when they try to use it.
However, just recently the eclipse support has gotten better, not sure about war support yet though. But worth trying again i think. However the pom.xml files are severley out of date. Does anyone know of any tools for converting 1.x poms to 2.x poms? That would be nice.
If we could possibly go to maven 2 it would be great, I am not sure how much longer geotools will support maven 1.0.2. It comes down to an issue of time, and martin has put in the time to make maven 2 based builds releasable, and maven 1 is lagging behind.
I understand this may impact what build system you pursue in geoserver, and I recall you were taking over the maven build from James so I guess the tradeoffs are yours?
Jody-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
why i can't BUILD my geoserver with maven?
Running
org.vfny.geoserver.wms.responses.map.legend.GetLegendGraphicKvpReaderTes
t
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.5 sec
Running org.vfny.geoserver.wms.responses.featureinfo.FeatureTemplateTest
Could not delete
D:\dev\geoserver\wms\.\target\mock7425data\sf\PrimitiveGeoFeatu
re.properties
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.532 sec
Running org.vfny.geoserver.wms.requests.DescribeLayerKvpRequestReaderTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.032 sec
Results :
Tests in error:
testVector(org.vfny.geoserver.wms.responses.map.kml.KMLTest)
testVectorWithFeatureId(org.vfny.geoserver.wms.responses.map.kml.KMLTest)
testOutput(org.vfny.geoserver.wms.responses.map.kml.GeoSearchKMLTest)
testDataRegionator(org.vfny.geoserver.wms.responses.map.kml.GeoSearchKMLTest)
testGeometryRegionator(org.vfny.geoserver.wms.responses.map.kml.GeoSearchKMLTe
st)
testRandomRegionator(org.vfny.geoserver.wms.responses.map.kml.GeoSearchKMLTest
)
testBigGeometries(org.vfny.geoserver.wms.responses.map.kml.GeoSearchKMLTest)
testStrategyChangesStuff(org.vfny.geoserver.wms.responses.map.kml.GeoSearchKML
Test)
Tests run: 129, Failures: 0, Errors: 8, Skipped: 0
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] There are test failures.
Please refer to D:\dev\geoserver\wms\target\surefire-reports for the
individual
test results.
--
View this message in context: http://www.nabble.com/Maven-build-tp3335366p20094221.html
Sent from the GeoServer - Dev mailing list archive at Nabble.com.