I can rerun them this afternoon, but they will be a very long listing
to sift through. I am not really certain, but it appears that these
errors are a result of testing the code once it is compiled. If that
is the case, then maybe the binary is fine.

Thanks again, Niklas.

On 5/24/07, Niklas Gustavsson <[EMAIL PROTECTED]> wrote:
Errors are not a good thing with Maven (it would most likely end the
build after the errors). As I don't have a Mac to test on it would be
very interesting to see the error reports. In each module (ftplet-api,
core and so on) you will have a folder named target/surefire-reports.
Could you please zip that up and send to me off-list
([EMAIL PROTECTED])? Most likely, the problematic test cases are in core.

In the meantime, you can run the following command which will ignore the
tests and most likely produce a correct package for you:

mvn -Dmaven.test.skip=true package

/niklas

Mike McGonagle wrote:
> Alright, this is somewhat looking promising...
>
> This time everything compiled just fine, and all the tests ran, WITH 6
> errors... I wasn't quite sure how to identify exactly what was an
> error, as some of the things look like they were errors that were
> EXPECTED to happen...
>
> I also ran the "install" target under 'mvn', it also got six errors.
> Not sure if they are the same or not...
>
> It does appear that there is a 'distribution' folder. Should I assume
> that everything built correctly, dispite the errors?
>
> Thanks for all your help, Niklas. I hope it is as simple as building a
> new version from the sources...
>
>
> Mike M
>
> On 5/23/07, Niklas Gustavsson
> <[EMAIL PROTECTED]> wrote:
>> Mike McGonagle wrote:
>> > Hello all,
>> >
>> > After Niklas commented that I might have an old version, I figured
>> > that I could get current by just compiling from the method described
>> > on the 'building' web page...
>> >
>> > I got all the parts (Subversion and Maven), and everything is
>> > installed. I ran 'svn', and it completed. I then changed into the
>> > 'ftpserver' directory, then ran 'mvn test'. It starts to download a
>> > bunch of things, but then it goes to check for the version of maven
>> > that I am running, and claims it is incompatible with the required
>> > version... I got 2.0.6, and 2.0.6 appears on its list of valid
>> > version, and yet, NOTHING...
>> >
>> > Here is the trace after it gets the first error...
>> >
>> > [INFO] [enforcer:enforce {execution: default}]
>> > [WARNING] Rule 0: org.apache.maven.plugin.enforcer.RequireMavenVersion
>> > failed with message: Detected Maven Version: 2.0.6 is not in the
>> > allowed range [2.0.5,2.0.6).
>>
>> This syntax means that 2.0.5 is allowed, but 2.0.6 is not (due to a bug
>> in 2.0.6 that breaks the build). You need 2.0.5 at the moment.
>>
>> /niklas
>>
>>
>
>




--
Help the Environment, Plant a Bush back in Texas!

"I place economy among the first and most important republican
virtues, and public debt as the greatest of the dangers to be feared.
To preserve our independence, we must not let our rulers load us with
perpetual debt."
-- Thomas Jefferson, third US president, architect and author (1743-1826)

"Give Peace a Chance" -- John Lennon (9 October 1940 – 8 December 1980)

Peace may sound simple—one beautiful word— but it requires everything
we have, every quality, every strength, every dream, every high ideal.
—Yehudi Menuhin (1916–1999), musician

If you think you can, or you think you can't, you are probably right.
—Mark Twain

Reply via email to