Ok, changes committed.
Martin Desruisseaux wrote:
> Justin Deoliveira a écrit :
>> On trunk some poms are referencing 2.3.0-RC1-SNAPSHOT as their parent:
>>
>> maven/jjtree-javacc/pom.xml
>> maven/javamaker/pom.xml
>> plugin/imagemosaic/pom.xml
>> demo/introduction/pom.xml
>> maven/javadoc/pom.xml
Justin Deoliveira a écrit :
> On trunk some poms are referencing 2.3.0-RC1-SNAPSHOT as their parent:
>
> maven/jjtree-javacc/pom.xml
> maven/javamaker/pom.xml
> plugin/imagemosaic/pom.xml
> demo/introduction/pom.xml
> maven/javadoc/pom.xml
>
> Are these just things that slipped in?
I guess so. A
Adrian Custer a écrit :
> One of the consequences of these poms, that I'm not sure how to get
> around is that a build results in lots of modifications compared to svn,
> even for a clean checkout. I had to prune the constructed filters and
> compiled files by hand. Not sure if this is a problem wi
Thanks Adrian for your pom cleaning!
Adrian Custer a écrit :
> Still to do:
> * Licenses
> All files are now simply LGPL. You (Jody?) have to add any
> other relevant licenses into the poms. Then we can see if maven
> can actually use the info.
We already know that Mave
Adrian Custer a écrit :
> The two ? I know about. However, all the reformatted and autogenerated
> code I don't. Is there a way to exclude this? Have I broken the pom.xml
> configures or my svn properties?
I modified the maven/build-configs/.../jalopy.settings file yesterday (pushed
the line leng
Simone Giannecchini a écrit :
> I think I already talked to Martin about this, I think having somehow
> access to this reader you are implementing (even to a snapshot of it)
> would be interesting for the both of us as well as for the
> geotools/geoserver community since Alex Petkov and Myself (wel
Ciao Cedric,
sorry for getting back to you with such a delay but it is a busy period.
See below...
On 10/11/06, Cédric Briançon <[EMAIL PROTECTED]> wrote:
> Dear Geoserver-users list,
>
> I'm developping a coverage store for geoserver to manage a netCDF file.
> In the implementation of this covera
On trunk some poms are referencing 2.3.0-RC1-SNAPSHOT as their parent:
maven/jjtree-javacc/pom.xml
maven/javamaker/pom.xml
plugin/imagemosaic/pom.xml
demo/introduction/pom.xml
maven/javadoc/pom.xml
Are these just things that slipped in?
-Justin
--
Justin Deoliveira
[EMAIL PROTECTED]
The Open P
Cory Horner wrote:
>We're changing the way uDig uses transactions -- so a transaction is
>AUTO_COMMIT until a modification occurs, and it remains open until the
>user commits the transaction:
>
>http://jira.codehaus.org/browse/UDIG-1051
>
>
On second though, this does seem to be needed for Pos
Adrian Custer wrote:
> After hours of painless, mind numbing, boring cut-and-pasting, I have
> committed the new poms to trunk and the 2.3.x branch.
>
Very cool, we should grab some of your email for the maven instructions
in the developers guide.
> Still to do:
> * Licenses
> All f
Hey All,
One of the consequences of these poms, that I'm not sure how to get
around is that a build results in lots of modifications compared to svn,
even for a clean checkout. I had to prune the constructed filters and
compiled files by hand. Not sure if this is a problem with my edited
poms or w
Hey All,
After hours of painless, mind numbing, boring cut-and-pasting, I have
committed the new poms to trunk and the 2.3.x branch.
Essentials:
* valid xml
* UTF-8 encoding
* No tabs
* Consistent unix eol style
* Standard layout (for better or worse)
Header
Bingo 15:22 CEST (utc+2) commit is slowing to a crawl.
--adrian
On Fri, 2006-10-13 at 14:47 -0700, Jesse Eichar wrote:
> Hi all,
>
> Our sys admin did a bunch of tests today and wasn't able to find any
> major bottle necks committing to svn. He even tried using a remote
> server in Amsterda
Hey all,
I've only modified pom files and then done lots of
mvn clean install
but when I do an svn st now, I get:
logipod:/soft/SVN/geotools/trunk/gt> svn st
? maven-v4_0_0.xsd
M demo/mappane/pom.xml
M demo/introduction/pom.xml
M demo/property/pom.xml
M demo/data/pom.x
hey all,
mysql tests are failing for me on 2.3.x. The module pom.xml has a
section to disable the tests so this is apparently not a new thing. I'm
committing the pom.xml files in a way that the test in this module is
disabled. Therefore,
TO RUN THE TESTS ON MYSQL IT WILL BE NECESSARY TO MODIFY
Hey all,
I'm about to check in my pom.xml changes. It's 11:11 current european
time (iirc, it's GMT+2 right now). Things may break or explode. Use at
your own risk.
--adrian
-
Using Tomcat but need to do more? Need to suppo
16 matches
Mail list logo
