The release plugin won’t let us release with a SNAPSHOT dependency.

Ralph

> On May 6, 2016, at 10:14 PM, Gary Gregory (JIRA) <j...@apache.org> wrote:
> 
> 
>    [ 
> https://issues.apache.org/jira/browse/LOG4J2-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275088#comment-15275088
>  ] 
> 
> Gary Gregory commented on LOG4J2-1295:
> --------------------------------------
> 
> So do we use a SNAPSHOT build or is there a release planned?
> 
>> Automated testing to verify no temporary objects allocated in gc-free 
>> configuration
>> -----------------------------------------------------------------------------------
>> 
>>                Key: LOG4J2-1295
>>                URL: https://issues.apache.org/jira/browse/LOG4J2-1295
>>            Project: Log4j 2
>>         Issue Type: New Feature
>>         Components: API, Configurators, Core, Layouts, Pattern Converters
>>   Affects Versions: 2.5
>>           Reporter: Remko Popma
>>           Assignee: Remko Popma
>>            Fix For: 2.6
>> 
>> 
>> LOG4J2-1270 proposes changes to support gc-free behaviour (no allocation of 
>> temporary objects) in certain configurations.
>> This ticket is about verifying that Log4j does not allocate in these 
>> configurations. It is not always obvious that some code creates objects, so 
>> it is easy for regressions to creep in during maintenance code changes.
>> Ideally this verification is packaged so it can run automatically during the 
>> test phase of the build, for example in a JUnit test.
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
> 
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Reply via email to