Hi Jesse,
Just looking over the preference module and a couple of things I notice
that the "repository" and "build" configurations seems to have been
copied from the root pom.xml. I am guessing this was just a result of
using the root pom as a starting point? Commenting them out the module
still seems to compile.
Mind if I kill them, or is there an actualy specific configuration needed?
-Justin
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
I have already. I just haven't committed yet.
Jesse
On 16-Jun-06, at 10:27 AM, Justin Deoliveira wrote:
Hi Jesse,
Just looking over the preference module and a couple of things I notice
that the "repository" and "build" configurations seems to have been
copied from the root pom.xml. I am guessing this was just a result of
using the root pom as a starting point? Commenting them out the module
still seems to compile.Mind if I kill them, or is there an actualy specific configuration needed?
-Justin
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Sorry read your email wrong.
It only build correctly because you have everything in your local repository. It breaks if you don't have a local repo.
Only the preferences_web depends on geoserver. The rest can be used with no geoserver dependencies. So the pom has to have the repositories and everything. It is mainly because geoserver itself has so many dependencies that preferences doesn't need and makes it harder to reuse because of the dependencies.
the preferences_web module is the sub-module that can be used by geoserver. The preference_core uses spring remoting and so doesn't have to be bundled with geoserver.
Jesse
On 16-Jun-06, at 1:20 PM, Jesse Eichar wrote:
I have already. I just haven't committed yet.
Jesse
On 16-Jun-06, at 10:27 AM, Justin Deoliveira wrote:Hi Jesse,
Just looking over the preference module and a couple of things I
notice
that the "repository" and "build" configurations seems to have been
copied from the root pom.xml. I am guessing this was just a result of
using the root pom as a starting point? Commenting them out the module
still seems to compile.Mind if I kill them, or is there an actualy specific configuration
needed?-Justin
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Jesse Eichar wrote:
Sorry read your email wrong.
It only build correctly because you have everything in your local
repository. It breaks if you don't have a local repo.
Not sure I understand?
Only the preferences_web depends on geoserver. The rest can be used
with no geoserver dependencies. So the pom has to have the
repositories and everything. It is mainly because geoserver itself
has so many dependencies that preferences doesn't need and makes it
harder to reuse because of the dependencies.
Unless I am mistaken you can still extend the root geoserver pom and not
pick up any actual dependencies. Every library in that pom is just
dependencyManagement.
the preferences_web module is the sub-module that can be used by
geoserver. The preference_core uses spring remoting and so doesn't
have to be bundled with geoserver.
Both modules require the core spring support. Ideally what I would like
to see if that the root community pom declares a dependency on the
"platform" geoserver module, which transitivley brings in the "core"
spring jars (not remoting). Then preferences_web can bring in the
additional dependencies on the main module, and preferences_core could
just declare an additional spring dependency on remoting.
Whadda think?
Jesse
On 16-Jun-06, at 1:20 PM, Jesse Eichar wrote:
I have already. I just haven't committed yet.
Jesse
On 16-Jun-06, at 10:27 AM, Justin Deoliveira wrote:Hi Jesse,
Just looking over the preference module and a couple of things I
notice
that the "repository" and "build" configurations seems to have been
copied from the root pom.xml. I am guessing this was just a result of
using the root pom as a starting point? Commenting them out the
module
still seems to compile.Mind if I kill them, or is there an actualy specific configuration
needed?-Justin
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:1004,44931c9755558365517736!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com