Thanks a lot Andrea ...
Andrea Aime escribió:
> On Mon, Jun 20, 2011 at 5:40 PM, Jose Macchi wrote:
>
>> ok, just asking. Since task is done by a team, we need to coordinate "rules
>> & criteria" when adding native libraries, or documents, or testing files, or
>> whatever.
>>
>> I will be
On Mon, Jun 20, 2011 at 5:40 PM, Jose Macchi wrote:
> ok, just asking. Since task is done by a team, we need to coordinate "rules
> & criteria" when adding native libraries, or documents, or testing files, or
> whatever.
>
> I will be placing all this information on a doc, then you will decide if
Great
Since task is done by a team, we need to coordinate "rules & criteria"
when adding native libraries, or documents, or testing files, or
whatever. While team work, i can organize this kind of information (so
we can progress on both sides).
I will be placing all this information on a doc,
Native lib dependencies are tricky just for this reason. Another way to
solve this would be just at packaging time. As Andrea states host the native
libs somewhere external and when it comes time to build the extension at
release time then we download the appropriate native libs just when we
packag
What we do for Geotools app-schema test data and schema bundles is to
(1) package them into maven artifacts and then
(2) deploy them to the osgeo maven repository.
The advantage of using Maven artifacts is that they are downloaded only
when needed and are cached on the build platform. Builds not
On Sun, Jun 19, 2011 at 2:58 AM, Jose Macchi wrote:
> I guess the easiest approach is to follow the imageio-ext lead:
> you just have to find some site that would host your files.
> Sourceforge could be a hosting platform for the natives for example.
>
>
> About sourceforge, i'm agree to use it a
Hi Andrea,
Andrea Aime escribió:
On Sat, Jun 18, 2011 at 9:57 PM, Jose Macchi wrote:
Hi Andrea, first at all, sorry for causing this trouble.
We should ask Justin before proceeding, on how to manage compiled version of
dlls/libraries.
As you know we are working on an integration with spati
Hi peoplei were out of office all friday. Just today i was able to
check mails. We should remove that, but we also need to define where to
place binaries (inside jars, or in a repository, or..dont know. You
would determine which is your preference on that).
Jar files for specific OS on a
On Sat, Jun 18, 2011 at 9:57 PM, Jose Macchi wrote:
> Hi Andrea, first at all, sorry for causing this trouble.
> We should ask Justin before proceeding, on how to manage compiled version of
> dlls/libraries.
>
> As you know we are working on an integration with spatialite. We have worked
> on comp
On Sat, Jun 18, 2011 at 8:02 PM, Frank Gasdorf
wrote:
> Maybe you already heard about pre commit hooks in SVN where you can check
> project relevant content or general project rules :
> Have a look at this
> : http://wordaligned.org/articles/a-subversion-pre-commit-hook
> svnbook 1.4 "Create Hooks
Hi Andrea, first at all, sorry for causing this trouble.
We should ask Justin before proceeding, on how to manage compiled
version of dlls/libraries.
As you know we are working on an integration with spatialite. We have
worked on compiling sqlite and spatialite to work on all platforms, and
m
I tried to send him a private email but i have yet to hear back. So let's
roll back the commit for now. Or at least remove all the binary libs.
On Sat, Jun 18, 2011 at 11:14 AM, Andrea Aime
wrote:
> On Fri, Jun 17, 2011 at 3:44 PM, Justin Deoliveira
> wrote:
> > In an attempt to prevent this fro
Maybe you already heard about pre commit hooks in SVN where you can check
project relevant content or general project rules :
Have a look at this :
http://wordaligned.org/articles/a-subversion-pre-commit-hook
svnbook 1.4 "Create Hooks" :
http://svnbook.red-bean.com/en/1.4/svn.reposadmin.create.htm
On Fri, Jun 17, 2011 at 3:44 PM, Justin Deoliveira wrote:
> In an attempt to prevent this from occurring again in the future i just
> updated the developer guide to include some basic commit guidelines for the
> project:
>
> http://docs.geoserver.org/latest/en/developer/policies/comitting.html#com
In an attempt to prevent this from occurring again in the future i just
updated the developer guide to include some basic commit guidelines for the
project:
http://docs.geoserver.org/latest/en/developer/policies/comitting.html#commit-guidelines
Please add anything you deem appropriate.
-Justin
Hi,
tonight a large batch of native libraries was committed to the
community/spatialite section:
/devel/git-gs/src/community/spatialite/lib$ du -csh *
50M native
50M total
This is unprecedented, I think we got mad at people for less than 1MB binary
commits
in svn in the past.
Now, I understand J
16 matches
Mail list logo