Aha, we've been ignoring that error for ages!
On 18/11/10 14:27, Michael Bedward wrote:
> Ah... a glint of enlightenment...
>
> I just switched back to maven 2.2.1 and noticed when building the
> javadoc module it issues this warning:
>
>
> [WARNING] **
Ah... a glint of enlightenment...
I just switched back to maven 2.2.1 and noticed when building the
javadoc module it issues this warning:
[WARNING] ***
[WARNING] Deprecation Alert:
[WARNING] No mojo descriptors were found in this project whic
On 18 November 2010 06:14, Justin Deoliveira wrote:
> Ah ok. Yeah I agree. And yeah moving to maven 3 would be nice as it has some
> nice new features... if only there were more hours in the day :)
I just tried building with maven 3 (OSX, Java 1.6). It fell over when
trying to compile the build/j
+1 for updating the dev guide. Although it is a bit naughty forcing tool
upgrades on stable, we have to be pragmatic.
On 17/11/10 22:38, Justin Deoliveira wrote:
> So what do people prefer? Shall I just updated the developer guide? Or roll
> back the change?
--
Ben Caradoc-Davies
Software Eng
On Wed, Nov 17, 2010 at 10:41 AM, Andrea Aime
wrote:
> On Wed, Nov 17, 2010 at 5:09 PM, Justin Deoliveira
> wrote:
> >> Update the developer guide? Atm it would be better to try out Maven 3
> >> rather than trying to support an old maven version imho
> >
> > Not too sure what you mean here. The a
On Wed, Nov 17, 2010 at 5:09 PM, Justin Deoliveira wrote:
>> Update the developer guide? Atm it would be better to try out Maven 3
>> rather than trying to support an old maven version imho
>
> Not too sure what you mean here. The alternatives are either (a) update the
> developer guide stating t
On Wed, Nov 17, 2010 at 8:58 AM, Andrea Aime
wrote:
> On Wed, Nov 17, 2010 at 3:38 PM, Justin Deoliveira
> wrote:
> > Doh, I knew it was going to be too easy. I also made the changes on 2.6.x
> as
> > well for which it says 2.0.10 is supported.
> > So what do people prefer? Shall I just updated t
On Wed, Nov 17, 2010 at 3:38 PM, Justin Deoliveira wrote:
> Doh, I knew it was going to be too easy. I also made the changes on 2.6.x as
> well for which it says 2.0.10 is supported.
> So what do people prefer? Shall I just updated the developer guide? Or roll
> back the change?
Update the develo
+1 for updating the developer guide. Only professionals are concerned,
should not be a problem :-)
Quoting Justin Deoliveira :
> Doh, I knew it was going to be too easy. I also made the changes on 2.6.x as
> well for which it says 2.0.10 is supported.
>
> So what do people prefer? Shall I just
Doh, I knew it was going to be too easy. I also made the changes on 2.6.x as
well for which it says 2.0.10 is supported.
So what do people prefer? Shall I just updated the developer guide? Or roll
back the change?
On Tue, Nov 16, 2010 at 11:44 PM, Ben Caradoc-Davies
wrote:
> After Justin's chan
After Justin's change in r36337 "GEOT-3319, adding
version/revision/build info to build", the Geotools trunk build fails
with Maven 2.0.10 (on an old buildbot). The solution is to upgrade Maven
to 2.2.1.
The user manual does *not* say 2.0.10 is supported for trunk:
http://docs.codehaus.org/disp
11 matches
Mail list logo
