You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Oliver Kopp <ko...@gmail.com> on 2020/11/03 11:34:44 UTC
log4j 3.0.0-SNAHSOPT disappeared
Hi,
Due to https://issues.apache.org/jira/browse/LOG4J2-2690?focusedCommentId=16927936&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16927936
we are using 3.0.0-SNAPSHOT in our Java 15 project.
This morning, we noticed that maven-metadata.xml disappeared from
https://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-jcl/3.0.0-SNAPSHOT/
and all mirrors. This makes our software JabRef
(https://github.com/jabref/jabref/) non-buildadble.
Would it be possible to bring back 3.0.0-SNAPSHOT to the apache maven
repository?
Thank you in advance and greetings,
Oliver
--
https://github.com/koppor/
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: log4j 3.0.0-SNAHSOPT disappeared
Posted by Ralph Goers <ra...@dslextreme.com>.
Unfortunately, I don’t see 2.x as ever fully supporting the JPMS. I keep wanting to focus solely on 3.0 to get it released but there is still so much work to do that it is difficult since we can’t put everything on hold until then.
Ralph
> On Nov 3, 2020, at 8:57 AM, Oliver Kopp <ko...@gmail.com> wrote:
>
> Hi,
>
> Sure. I think, we thought, fixing snapshot usage issues (and possibly
> report back issues) would help log4j more than staying with a pinned
> snapshot.
>
> Surely, this will cause troubles when initiating a release for Debian.
> Maybe a 3.0.0 release happens before all other dependencies of our project
> are packaged for Debian 😅
>
> Cheers,
>
> Oliver
>
> Ralph Goers <ra...@dslextreme.com> schrieb am Di., 3. Nov. 2020,
> 16:52:
>
>> Snapshots are not releases and we don’t guarantee we won’t make breaking
>> changes. If you want to use 3.0.0 in a production environment you should
>> clone the repo locally and create a tag and create an internal release for
>> yourself. You should also use a version number that won’t conflict with
>> our releases by using a version number like 3.0.0-mycorp-1.
>>
>> Ralph
>>
>>> On Nov 3, 2020, at 4:34 AM, Oliver Kopp <ko...@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> Due to
>> https://issues.apache.org/jira/browse/LOG4J2-2690?focusedCommentId=16927936&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16927936
>>> we are using 3.0.0-SNAPSHOT in our Java 15 project.
>>>
>>> This morning, we noticed that maven-metadata.xml disappeared from
>>>
>> https://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-jcl/3.0.0-SNAPSHOT/
>>> and all mirrors. This makes our software JabRef
>>> (https://github.com/jabref/jabref/) non-buildadble.
>>>
>>> Would it be possible to bring back 3.0.0-SNAPSHOT to the apache maven
>>> repository?
>>>
>>> Thank you in advance and greetings,
>>>
>>> Oliver
>>> --
>>> https://github.com/koppor/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: log4j 3.0.0-SNAHSOPT disappeared
Posted by Oliver Kopp <ko...@gmail.com>.
Hi,
Sure. I think, we thought, fixing snapshot usage issues (and possibly
report back issues) would help log4j more than staying with a pinned
snapshot.
Surely, this will cause troubles when initiating a release for Debian.
Maybe a 3.0.0 release happens before all other dependencies of our project
are packaged for Debian 😅
Cheers,
Oliver
Ralph Goers <ra...@dslextreme.com> schrieb am Di., 3. Nov. 2020,
16:52:
> Snapshots are not releases and we don’t guarantee we won’t make breaking
> changes. If you want to use 3.0.0 in a production environment you should
> clone the repo locally and create a tag and create an internal release for
> yourself. You should also use a version number that won’t conflict with
> our releases by using a version number like 3.0.0-mycorp-1.
>
> Ralph
>
> > On Nov 3, 2020, at 4:34 AM, Oliver Kopp <ko...@gmail.com> wrote:
> >
> > Hi,
> >
> > Due to
> https://issues.apache.org/jira/browse/LOG4J2-2690?focusedCommentId=16927936&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16927936
> > we are using 3.0.0-SNAPSHOT in our Java 15 project.
> >
> > This morning, we noticed that maven-metadata.xml disappeared from
> >
> https://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-jcl/3.0.0-SNAPSHOT/
> > and all mirrors. This makes our software JabRef
> > (https://github.com/jabref/jabref/) non-buildadble.
> >
> > Would it be possible to bring back 3.0.0-SNAPSHOT to the apache maven
> > repository?
> >
> > Thank you in advance and greetings,
> >
> > Oliver
> > --
> > https://github.com/koppor/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-user-help@logging.apache.org
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
Re: log4j 3.0.0-SNAHSOPT disappeared
Posted by Ralph Goers <ra...@dslextreme.com>.
Snapshots are not releases and we don’t guarantee we won’t make breaking changes. If you want to use 3.0.0 in a production environment you should clone the repo locally and create a tag and create an internal release for yourself. You should also use a version number that won’t conflict with our releases by using a version number like 3.0.0-mycorp-1.
Ralph
> On Nov 3, 2020, at 4:34 AM, Oliver Kopp <ko...@gmail.com> wrote:
>
> Hi,
>
> Due to https://issues.apache.org/jira/browse/LOG4J2-2690?focusedCommentId=16927936&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16927936
> we are using 3.0.0-SNAPSHOT in our Java 15 project.
>
> This morning, we noticed that maven-metadata.xml disappeared from
> https://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-jcl/3.0.0-SNAPSHOT/
> and all mirrors. This makes our software JabRef
> (https://github.com/jabref/jabref/) non-buildadble.
>
> Would it be possible to bring back 3.0.0-SNAPSHOT to the apache maven
> repository?
>
> Thank you in advance and greetings,
>
> Oliver
> --
> https://github.com/koppor/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: log4j 3.0.0-SNAHSOPT disappeared
Posted by Matt Sicker <bo...@gmail.com>.
Oops, sent too soon. I see that’s a snapshot repo. I believe we need to run
CI again since we purged some old snapshots the other day.
On Tue, Nov 3, 2020 at 08:23 Matt Sicker <bo...@gmail.com> wrote:
> Snapshots aren’t meant to be in the release repository. While we do
> publish snapshots in our snapshots repo from CI, those aren’t releases, so
> we don’t directly advertise them except to users who want to test out
> future changes. I’m not particularly sure why you’ve chosen 3.x as that
> repo changes more drastically than the 2.x one (except for the API module).
>
> On Tue, Nov 3, 2020 at 05:35 Oliver Kopp <ko...@gmail.com> wrote:
>
>> Hi,
>>
>> Due to
>> https://issues.apache.org/jira/browse/LOG4J2-2690?focusedCommentId=16927936&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16927936
>> we are using 3.0.0-SNAPSHOT in our Java 15 project.
>>
>> This morning, we noticed that maven-metadata.xml disappeared from
>>
>> https://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-jcl/3.0.0-SNAPSHOT/
>> and all mirrors. This makes our software JabRef
>> (https://github.com/jabref/jabref/) non-buildadble.
>>
>> Would it be possible to bring back 3.0.0-SNAPSHOT to the apache maven
>> repository?
>>
>> Thank you in advance and greetings,
>>
>> Oliver
>> --
>> https://github.com/koppor/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>>
Re: log4j 3.0.0-SNAHSOPT disappeared
Posted by Oliver Kopp <ko...@gmail.com>.
Hi,
Matt Sicker <bo...@gmail.com> schrieb am Di., 3. Nov. 2020, 15:23:
I’m not particularly sure why you’ve chosen 3.x
Because our issue seems not to be solved for the 2.x release according to
the state of LOG4J2-2690 -
https://issues.apache.org/jira/browse/LOG4J2-2690?focusedCommentId=16927936&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16927936
.
Maybe I'm wrong and we should try the latest 2.x release.
Cheers,
Oliver
Re: log4j 3.0.0-SNAHSOPT disappeared
Posted by Matt Sicker <bo...@gmail.com>.
Snapshots aren’t meant to be in the release repository. While we do publish
snapshots in our snapshots repo from CI, those aren’t releases, so we don’t
directly advertise them except to users who want to test out future
changes. I’m not particularly sure why you’ve chosen 3.x as that repo
changes more drastically than the 2.x one (except for the API module).
On Tue, Nov 3, 2020 at 05:35 Oliver Kopp <ko...@gmail.com> wrote:
> Hi,
>
> Due to
> https://issues.apache.org/jira/browse/LOG4J2-2690?focusedCommentId=16927936&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16927936
> we are using 3.0.0-SNAPSHOT in our Java 15 project.
>
> This morning, we noticed that maven-metadata.xml disappeared from
>
> https://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-jcl/3.0.0-SNAPSHOT/
> and all mirrors. This makes our software JabRef
> (https://github.com/jabref/jabref/) non-buildadble.
>
> Would it be possible to bring back 3.0.0-SNAPSHOT to the apache maven
> repository?
>
> Thank you in advance and greetings,
>
> Oliver
> --
> https://github.com/koppor/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>