You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Julien HENRY <he...@yahoo.fr> on 2009/03/10 17:54:50 UTC

Re : Re : [PLEASE TEST] Maven 2.1.0-RC1

Hi John,

I've submitted MNG-4079. Tell me if you need additional informations.

Thanks for the good job!

Julien



----- Message d'origine ----
De : John Casey <jd...@commonjava.org>
À : Maven Developers List <de...@maven.apache.org>
Envoyé le : Mardi, 10 Mars 2009, 17h15mn 49s
Objet : Re: Re : [PLEASE TEST] Maven 2.1.0-RC1

Could you file that in JIRA, and I'll take a look? If possible, please include the -e option so I can try to figure out where the different traces are being produced...it *might* be difficult to trace.

-john

Julien HENRY wrote:
> Works fine and quickly, but here is a small question. In case of error, is it possible to avoid duplication of the error message?
> 
> Example:
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Compilation failure
> Failure executing javac, but could not parse the error:
> javac: invalid target release: 1.5
> Usage: javac <options> <source files>
> where possible options include:
>   -g                        Generate all debugging info
>   -g:none                   Generate no debugging info
>   -g:{lines,vars,source}    Generate only some debugging info
>   -nowarn                   Generate no warnings
>   -verbose                  Output messages about what the compiler is doing
>   -deprecation              Output source locations where deprecated APIs are used
>   -classpath <path>         Specify where to find user class files
>   -sourcepath <path>        Specify where to find input source files
>   -bootclasspath <path>     Override location of bootstrap class files
>   -extdirs <dirs>           Override location of installed extensions
>   -d <directory>            Specify where to place generated class files
>   -encoding <encoding>      Specify character encoding used by source files
>   -source <release>         Provide source compatibility with specified release
>   -target <release>         Generate class files for specific VM version
>   -help                     Print a synopsis of standard options
> 
> 
> 
> 
> Failure executing javac, but could not parse the error:
> javac: invalid target release: 1.5
> Usage: javac <options> <source files>
> where possible options include:
>   -g                        Generate all debugging info
>   -g:none                   Generate no debugging info
>   -g:{lines,vars,source}    Generate only some debugging info
>   -nowarn                   Generate no warnings
>   -verbose                  Output messages about what the compiler is doing
>   -deprecation              Output source locations where deprecated APIs are used
>   -classpath <path>         Specify where to find user class files
>   -sourcepath <path>        Specify where to find input source files
>   -bootclasspath <path>     Override location of bootstrap class files
>   -extdirs <dirs>           Override location of installed extensions
>   -d <directory>            Specify where to place generated class files
>   -encoding <encoding>      Specify character encoding used by source files
>   -source <release>         Provide source compatibility with specified release
>   -target <release>         Generate class files for specific VM version
>   -help                     Print a synopsis of standard options
> 
> 
> 
> [INFO] ------------------------------------------------------------------------
> 
> 
> 
> 
> ----- Message d'origine ----
> De : John Casey <jd...@commonjava.org>
> À : Maven Developers List <de...@maven.apache.org>
> Envoyé le : Lundi, 9 Mars 2009, 17h00mn 13s
> Objet : [PLEASE TEST] Maven 2.1.0-RC1
> 
> Hi everyone,
> 
> I've rolled the first release candidate for Maven 2.1.0. It's available at:
> 
> http://tinyurl.com/maven-2-1-0-RC1
> (https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/)
> 
> The staging repository root is at:
> 
> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
> 
> If you have time, please take a look and see if you can break it!
> 
> BTW, the JIRA version notes for this release are at:
> 
> http://tinyurl..com/maven-2-1-0-jira
> (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587)
> 
> If we can't find anything wrong with this release candidate after maybe four or five days at most, I'll call the vote for a release. Hopefully we can coast in on the effort we put forth in the last release, at least to some extent! :-)
> 
> Thanks,
> 
> -john
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 
> 
>      
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


      


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Re : Re : [PLEASE TEST] Maven 2.1.0-RC1

Posted by John Casey <jd...@commonjava.org>.
FWIW, 2.1.0-RC* aren't releases, so we don't need them reflected in 
JIRA. We can set Affected Version == Fix-For Version == 2.1.0 for these 
issues.

Thanks,

-john

Julien HENRY wrote:
> Hi John,
> 
> I've submitted MNG-4079. Tell me if you need additional informations.
> 
> Thanks for the good job!
> 
> Julien
> 
> 
> 
> ----- Message d'origine ----
> De : John Casey <jd...@commonjava.org>
> À : Maven Developers List <de...@maven.apache.org>
> Envoyé le : Mardi, 10 Mars 2009, 17h15mn 49s
> Objet : Re: Re : [PLEASE TEST] Maven 2.1.0-RC1
> 
> Could you file that in JIRA, and I'll take a look? If possible, please include the -e option so I can try to figure out where the different traces are being produced...it *might* be difficult to trace.
> 
> -john
> 
> Julien HENRY wrote:
>> Works fine and quickly, but here is a small question. In case of error, is it possible to avoid duplication of the error message?
>>
>> Example:
>> [ERROR] BUILD FAILURE
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Compilation failure
>> Failure executing javac, but could not parse the error:
>> javac: invalid target release: 1.5
>> Usage: javac <options> <source files>
>> where possible options include:
>>   -g                        Generate all debugging info
>>   -g:none                   Generate no debugging info
>>   -g:{lines,vars,source}    Generate only some debugging info
>>   -nowarn                   Generate no warnings
>>   -verbose                  Output messages about what the compiler is doing
>>   -deprecation              Output source locations where deprecated APIs are used
>>   -classpath <path>         Specify where to find user class files
>>   -sourcepath <path>        Specify where to find input source files
>>   -bootclasspath <path>     Override location of bootstrap class files
>>   -extdirs <dirs>           Override location of installed extensions
>>   -d <directory>            Specify where to place generated class files
>>   -encoding <encoding>      Specify character encoding used by source files
>>   -source <release>         Provide source compatibility with specified release
>>   -target <release>         Generate class files for specific VM version
>>   -help                     Print a synopsis of standard options
>>
>>
>>
>>
>> Failure executing javac, but could not parse the error:
>> javac: invalid target release: 1.5
>> Usage: javac <options> <source files>
>> where possible options include:
>>   -g                        Generate all debugging info
>>   -g:none                   Generate no debugging info
>>   -g:{lines,vars,source}    Generate only some debugging info
>>   -nowarn                   Generate no warnings
>>   -verbose                  Output messages about what the compiler is doing
>>   -deprecation              Output source locations where deprecated APIs are used
>>   -classpath <path>         Specify where to find user class files
>>   -sourcepath <path>        Specify where to find input source files
>>   -bootclasspath <path>     Override location of bootstrap class files
>>   -extdirs <dirs>           Override location of installed extensions
>>   -d <directory>            Specify where to place generated class files
>>   -encoding <encoding>      Specify character encoding used by source files
>>   -source <release>         Provide source compatibility with specified release
>>   -target <release>         Generate class files for specific VM version
>>   -help                     Print a synopsis of standard options
>>
>>
>>
>> [INFO] ------------------------------------------------------------------------
>>
>>
>>
>>
>> ----- Message d'origine ----
>> De : John Casey <jd...@commonjava.org>
>> À : Maven Developers List <de...@maven.apache.org>
>> Envoyé le : Lundi, 9 Mars 2009, 17h00mn 13s
>> Objet : [PLEASE TEST] Maven 2.1.0-RC1
>>
>> Hi everyone,
>>
>> I've rolled the first release candidate for Maven 2.1.0. It's available at:
>>
>> http://tinyurl.com/maven-2-1-0-RC1
>> (https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/)
>>
>> The staging repository root is at:
>>
>> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>>
>> If you have time, please take a look and see if you can break it!
>>
>> BTW, the JIRA version notes for this release are at:
>>
>> http://tinyurl..com/maven-2-1-0-jira
>> (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587)
>>
>> If we can't find anything wrong with this release candidate after maybe four or five days at most, I'll call the vote for a release. Hopefully we can coast in on the effort we put forth in the last release, at least to some extent! :-)
>>
>> Thanks,
>>
>> -john
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>>      
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 
> 
>       
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org