On Wed, Oct 5, 2011 at 12:27 AM, Scott Deboy scott.de...@gmail.com wrote:
There are a number of people looking for resolution on the code signing cert
question (Eclipse plugins, maven artifacts, etc). I'll file a Jira issue.
Our case is relatively straightforward - hopefully infra can automate
Since we never had offiical release of receivers or component, is it ok to
nuke them from subversion now?
Christian, do you mind doing site-related stuff?
I'll update wording on the Chainsaw page and update the screenshots...and I
think we could be ready soon to vote on a release..
Not sure
On Tue, Oct 4, 2011 at 6:17 PM, Scott Deboy scott.de...@gmail.com wrote:
Since we never had offiical release of receivers or component, is it ok to
nuke them from subversion now?
Probably we should make a new mail thread with [ANN] in the subject to
make sure everybody reads, give 72h and then
OK, I'll send out an announcement email and delete after 72 hours if there
are no objections.
Thanks for the help on the web site.
Regarding Web Start, the old old old version of Chainsaw is currently
available via Web Start, signed by Paul Smith a long time ago..available
from the 'download
http://logging.apache.org/chainsaw/download.html - by clicking on the 'Java
Web Start' link, Chainsaw will download, install and run..
To update the version of Chainsaw we provide via Web Start, we need to sign
the jars, since Chainsaw writes to the local file system, can initiate
socket
We need a code signing certificate that is trusted by a root cert auth, and
use that cert to sign the jars - I would prefer the ASF handle this.
See
http://download.oracle.com/javase/6/docs/technotes/guides/javaws/developersguide/faq.html
Scott
On Tue, Oct 4, 2011 at 10:32 AM, Christian
OK understood.
Not sure were do ask, but maybe infra has an idea if such a thing
exists. If not, we might ask the board if we can buy something like
that
On Tue, Oct 4, 2011 at 7:44 PM, Scott Deboy scott.de...@gmail.com wrote:
We need a code signing certificate that is trusted by a root cert
There are a number of people looking for resolution on the code signing cert
question (Eclipse plugins, maven artifacts, etc). I'll file a Jira issue.
Our case is relatively straightforward - hopefully infra can automate it so
we can send them binaries/drop binaries into a folder, along with a
OK, I pulled receivers and component companion sources into Chainsaw in svn
1178304. Is deleting the entire component and receivers companions
hierarchy from svn sufficient or do I need to do something else?
There is also the question of 'companions' only being one now (extras) - not
sure what
On Mon, Oct 3, 2011 at 8:17 AM, Scott Deboy scott.de...@gmail.com wrote:
OK, I pulled receivers and component companion sources into Chainsaw in svn
1178304. Is deleting the entire component and receivers companions
hierarchy from svn sufficient or do I need to do something else?
we need to
Thanks Christian,
Extras are useful and should be kept around as is, unless we choose to pull
them back in to core...
I agree, replacing companions with just extras seems to be a good choice.
Scott
On Sun, Oct 2, 2011 at 11:41 PM, Christian Grobmeier grobme...@gmail.comwrote:
On Mon, Oct 3,
ok, I'll nuke component and receivers and pull the useful bits in to
chainsaw...does that mean we should remove the parent maven project then?
Scott
On Fri, Sep 2, 2011 at 6:55 AM, Curt Arnold carn...@apache.org wrote:
Forget the packaging renaming bit. No need to make Chainsaw an OSGi package
On Fri, Sep 30, 2011 at 2:27 PM, Scott Deboy scott.de...@gmail.com wrote:
ok, I'll nuke component and receivers and pull the useful bits in to
chainsaw...does that mean we should remove the parent maven project then?
If you speak of the parent for Companions: yes.
I think we can remove the
ok, moving ahead with removal then
On Fri, Sep 30, 2011 at 5:29 AM, Christian Grobmeier grobme...@gmail.comwrote:
On Fri, Sep 30, 2011 at 2:27 PM, Scott Deboy scott.de...@gmail.com
wrote:
ok, I'll nuke component and receivers and pull the useful bits in to
chainsaw...does that mean we
On Fri, Sep 30, 2011 at 2:36 PM, Scott Deboy scott.de...@gmail.com wrote:
ok, moving ahead with removal then
Thanks, and have fun - removing old stuff makes me always feel good,
hope it is the same feeling for you :-)
On Fri, Sep 30, 2011 at 5:29 AM, Christian Grobmeier grobme...@gmail.com
Definitely!
Anything to simplify things and get this out the door!
Thanks for all your help Christian,
Scott
On Fri, Sep 30, 2011 at 5:38 AM, Christian Grobmeier grobme...@gmail.comwrote:
On Fri, Sep 30, 2011 at 2:36 PM, Scott Deboy scott.de...@gmail.com
wrote:
ok, moving ahead with
I need to use some of the classes that were copied to core from receivers in
1165491 (rewriteappender, utillogginglevel)...
Will there be a log4j release soon or should I duplicate these classes in
Chainsaw? I don't want a log4j release to hold up a Chainsaw release.
Scott
On Fri, Sep 30, 2011
On Fri, Sep 30, 2011 at 4:26 PM, Scott Deboy scott.de...@gmail.com wrote:
I need to use some of the classes that were copied to core from receivers in
1165491 (rewriteappender, utillogginglevel)...
Will there be a log4j release soon or should I duplicate these classes in
Chainsaw? I don't
I'm leaning toward keeping them in the same package location - when log4j is
released, I can remove the classes from Chainsaw and everything will still
work.
Scott
On Fri, Sep 30, 2011 at 7:35 AM, Christian Grobmeier grobme...@gmail.comwrote:
On Fri, Sep 30, 2011 at 4:26 PM, Scott Deboy
On Fri, Sep 30, 2011 at 4:46 PM, Scott Deboy scott.de...@gmail.com wrote:
I'm leaning toward keeping them in the same package location - when log4j is
released, I can remove the classes from Chainsaw and everything will still
work.
But you need to make a new release of chainsaw together with
I would need to make a new release of Chainsaw after the log4j release at
some point, assuming I needed other things from the updated version of
log4j, but right now Chainsaw depends on 1.2.16 and bundles it in the
standalone and DMG builds...so I think I'm ok.. (?)
Scott
On Fri, Sep 30, 2011 at
On Fri, Sep 30, 2011 at 5:53 PM, Scott Deboy scott.de...@gmail.com wrote:
I would need to make a new release of Chainsaw after the log4j release at
some point, assuming I needed other things from the updated version of
log4j, but right now Chainsaw depends on 1.2.16 and bundles it in the
Forget the packaging renaming bit. No need to make Chainsaw an OSGi package and
no need to add additional work.
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail:
Scott,
Curt had an interesting idea lately, he mentioned it might make sense
to move the companions code into chainsaw.
What do you think on that?
I like the idea - less releases, and no other interested parties in
having companions.
Please comment, when you can :-)
Cheers
Christian
At this point I'm only focusing only on 2.0. I've been wondering if I should
create a subproject for chainsaw or if it should remain separate. I already
moved a large part of extras in as a core part of the functionality.
Ralph
On Sep 1, 2011, at 4:13 AM, Christian Grobmeier wrote:
Scott,
On Thu, Sep 1, 2011 at 6:15 PM, Scott Deboy scott.de...@gmail.com wrote:
I think pulling in component would make sense...no one else probably uses
it. Receivers? I suppose if they were built as a separate jar that'd be
fine too, I have no idea who uses them if anyone.
We can always cut them
On Thu, Sep 1, 2011 at 4:09 PM, Ralph Goers ralph.go...@dslextreme.com wrote:
At this point I'm only focusing only on 2.0. I've been wondering if I should
create a subproject for chainsaw or if it should remain separate. I already
moved a large part of extras in as a core part of the
On Sep 1, 2011, at 6:13 AM, Christian Grobmeier wrote:
Scott,
Curt had an interesting idea lately, he mentioned it might make sense
to move the companions code into chainsaw.
What do you think on that?
I like the idea - less releases, and no other interested parties in
having
28 matches
Mail list logo
