I just tried building jar collector against an empty repo with maven 2
and it succeeded - so the finger of suspicion points to maven 3 !
Michael
On 23 May 2012 15:47, Jody Garnett wrote:
> Could it be a Maven 3 problem ? Both FileUtils and Artifact are maven
> classes so should find their way to
> Could it be a Maven 3 problem ? Both FileUtils and Artifact are maven
> classes so should find their way to the repo with the rest of the
> plexus stuff.
>
> Michael
Good suggestion. Reverting back to my normal repository has me building fine
again (with maven 3).
So I am not sure what to make
The settings to control memory use for the javadoc executable is in
modules/pom.xml (it does not take into account the MAVEN_OPTS setting near as I
can tell.
--
Jody Garnett
On Wednesday, 23 May 2012 at 3:00 PM, Michael Bedward wrote:
> Jody,
>
> I've had this problem on my system for a whil
Could it be a Maven 3 problem ? Both FileUtils and Artifact are maven
classes so should find their way to the repo with the rest of the
plexus stuff.
Michael
On 23 May 2012 14:25, Jody Garnett wrote:
> And again with the "clean" build from bundled source code; against an empty
> maven reposito
Jody,
I've had this problem on my system for a while, and yet the Hudson
trunk javadocs job runs successfully with this config:
export MAVEN_OPTS="-Xmx512m" &&
mvn javadoc:aggregate
Michael
On 23 May 2012 13:25, Jody Garnett wrote:
> I have been unable to generate javadocs this time out (sigh
And again with the "clean" build from bundled source code; against an empty
maven repository.
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 18
A little hacking at the h2 console suggests that the result of a simple
"select * from tablename;" is sorted by primary key if no order by
clause is present. Nice behaviour, but no good for my test fixture. :~-(
Kind regards,
Ben.
On 23/05/12 11:37, Justin Deoliveira wrote:
> It could be that
On Tue, May 22, 2012 at 9:07 PM, Ben Caradoc-Davies <
[email protected]> wrote:
> Justin,
>
> I am attempting to use H2 to test sorting of features (in the context of
> GeoServer paging, i.e. WFS 2.0 GetFeaturePagingTest).
>
> When I add features to an H2 data store, they seem to always
I have been unable to generate javadocs this time out (sigh).
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:2.8.1:aggregate (default-cli) on
project modules: An error has occurred in JavaDocs report generation:
[ERROR] Exit code: 1 - javadoc: error - java.lang.OutO
Justin,
I am attempting to use H2 to test sorting of features (in the context of
GeoServer paging, i.e. WFS 2.0 GetFeaturePagingTest).
When I add features to an H2 data store, they seem to always come out
sorted by fid, even when I put them in intentionally unsorted (via
ListFeatureCollection)
On Tue, May 22, 2012 at 1:28 AM, Frank Gasdorf
wrote:
> 2012/5/22 Justin Deoliveira :
> > Hey Frank,
> >
> > On Mon, May 21, 2012 at 3:27 PM, Frank Gasdorf <
> [email protected]>
> > wrote:
> >>
> >> Thanks Justin,
> >>
> >> this is a good point to start! I've done something similar but
Adam Brow
Excellent !!! Thanks Justin.
I wonder if Jody was fiddling, I mean attempting to multi-task, too ?
Michael
On 22 May 2012 13:46, Justin Deoliveira wrote:
> Interesting. Nevermind... i take it back, the module builds now :) I think I
> see what is happening. The FEST stuff seems to take control
2012/5/22 Justin Deoliveira :
> Hey Frank,
>
> On Mon, May 21, 2012 at 3:27 PM, Frank Gasdorf
> wrote:
>>
>> Thanks Justin,
>>
>> this is a good point to start! I've done something similar but was nut
>> sure about the xmlcodgen configurations. The main difference
>> was the property "destination
14 matches
Mail list logo
