Andrea Aime wrote: > Jody Garnett ha scritto: >> Quick update; the "simple" example only works if the geoserver >> community has been deployed; currently that is not part of the >> release process (making these instructions useless). > This sounds like an exaggeration. If they were really useless we > wouldn't have been able to release geoserver. Do you believe that > developers know how to make releases by heart? Sorry andrea? Not sure I understand ... the instructions on making a simple application did not work as provided because an artifact (community pom.xml) was not deployed. >> Ideas: >> - make a formal "framework" pom.xml for community modules (and others >> to) use as their parent pom.xml > Not sure what you mean here. don't use community pom.xml; make a separate module (called geoserver/framework) that community modules can use as their parent pom.xml. >> - include community in the build; and make the -Pcommunity profile >> just control if the community plug-ins are build (probably the >> original intention of the profile?) > Hmmm... that pom is about to gain some profiles already when I'm done > with the csv module (java5 profile), this would probably make it a mess? Then perhaps we should consider a different name for a profile controlling the various community modules -Ppending or -Pexperiments or something? Jody
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
