This vote is cancelled and is superseded by the vote for 2.0.0-rc2.
On 20 January 2018 at 11:40, Scott Deboy wrote:
> Sure
>
> On Jan 20, 2018 9:04 AM, "Matt Sicker" wrote:
>
> > Wouldn't it be 2.0.0-rc2? Also, good timing: I can cut a new RC in the
> next
> > few hours.
> >
> > On 20 January 2
Sure
On Jan 20, 2018 9:04 AM, "Matt Sicker" wrote:
> Wouldn't it be 2.0.0-rc2? Also, good timing: I can cut a new RC in the next
> few hours.
>
> On 20 January 2018 at 09:47, Scott Deboy wrote:
>
> > Matt, would you mind re-spinning a new build at 2.1.0-rc1?
> >
> > On 1/19/18, Scott Deboy wro
Wouldn't it be 2.0.0-rc2? Also, good timing: I can cut a new RC in the next
few hours.
On 20 January 2018 at 09:47, Scott Deboy wrote:
> Matt, would you mind re-spinning a new build at 2.1.0-rc1?
>
> On 1/19/18, Scott Deboy wrote:
> > I finally looked at this. I pushed a change to app assemble
Matt, would you mind re-spinning a new build at 2.1.0-rc1?
On 1/19/18, Scott Deboy wrote:
> I finally looked at this. I pushed a change to app assembler config
> to make the bin directory executable, and updated HOWTOBUILD to
> mention you need to run mvn site:site first.
>
> Can we resin?
>
> O
I finally looked at this. I pushed a change to app assembler config
to make the bin directory executable, and updated HOWTOBUILD to
mention you need to run mvn site:site first.
Can we resin?
On 11/13/17, Matt Sicker wrote:
> Another thing I noticed is that the downloads page needs to be updated
Another thing I noticed is that the downloads page needs to be updated to
link to the (future) dist URLs instead of ones in the site's directory (no
proper mirroring in the old links).
On 12 November 2017 at 19:25, Scott Deboy wrote:
> I don't recall why - it was a while back :)
>
> Yes, I think
I don't recall why - it was a while back :)
Yes, I think 2.1.0-rc1 would make sense, once we fix the /bin directory issue.
On 11/12/17, Matt Sicker wrote:
> On 12 November 2017 at 13:53, Scott Deboy wrote:
>
>> That's right -forgot we rev'd to 2.1 internally (info.plist, release
>> notes, coupl
On 12 November 2017 at 13:53, Scott Deboy wrote:
> That's right -forgot we rev'd to 2.1 internally (info.plist, release
> notes, couple other places).
>
Any particular reason?
> Would it be easiest to release the new version as 2.1.0.0 instead of
> 2.0.0-rc1? Otherwise I could downgrade 2.1 r
When starting Chainsaw, I see this warning in the log:
menu 'Connect to' was NOT added because the 'Help' menu could not be located
There is a "Connect to" menu though, and the "Learn more about ZeroConf"
works.
On 2017-11-10 20:00, Matt Sicker wrote:
This is a vote to release Apache Chains
That's right -forgot we rev'd to 2.1 internally (info.plist, release
notes, couple other places).
Would it be easiest to release the new version as 2.1.0.0 instead of
2.0.0-rc1? Otherwise I could downgrade 2.1 refs, we never had an
official release with that rev.
Scott
On 11/12/17, Mikael Ståld
I think we can either fix or remove that menu item from the menu after
the release - I don't know how useful it is.
Scott
On 11/12/17, Mikael Ståldal wrote:
> When starting Chainsaw, I see this warning:
>
> Could not find any local JavaDocs, you might want to consider running
> 'ant javadoc'. Th
Would be nice to be able to load that as a plugin in a more dynamic
fashion. But we can keep that for a future version, not blocking this
release.
On 2017-11-12 20:45, Scott Deboy wrote:
That's right - we don't bundle in a JMS jar, although users can add
one to the classpath to use the JMSRec
Fixed.
On 11/12/17, Mikael Ståldal wrote:
> In the About text, it says:
>
> Please send questions, bug reports and/or feature requests to
> log4j-...@logging.apache.org
>
> which is obsolete.
>
>
> On 2017-11-10 20:00, Matt Sicker wrote:
>> This is a vote to release Apache Chainsaw 2.0.0-rc1.
>>
That's right - we don't bundle in a JMS jar, although users can add
one to the classpath to use the JMSReceiver.
On 11/12/17, Mikael Ståldal wrote:
> When running Chainsaw, I see this error message:
>
> Failed to locate Receiver class:org.apache.log4j.net.JMSReceiver, looks
> like a dependent cla
In release notes in the app, it says version 2.1.
On 2017-11-10 20:00, Matt Sicker wrote:
This is a vote to release Apache Chainsaw 2.0.0-rc1.
(Note: I've created release instructions on the new wiki: <
https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>)
Artifacts:
ht
When starting Chainsaw, I see this warning:
Could not find any local JavaDocs, you might want to consider running
'ant javadoc'. The release version will be able to access Javadocs from
the Apache website.
And accessing Javadocs from the Help menu does not work.
On 2017-11-10 20:00, Matt S
In the About text, it says:
Please send questions, bug reports and/or feature requests to
log4j-...@logging.apache.org
which is obsolete.
On 2017-11-10 20:00, Matt Sicker wrote:
This is a vote to release Apache Chainsaw 2.0.0-rc1.
(Note: I've created release instructions on the new wiki: <
h
When running Chainsaw, I see this error message:
Failed to locate Receiver class:org.apache.log4j.net.JMSReceiver, looks
like a dependent class is missing from the classpath
java.lang.NoClassDefFoundError: javax/jms/MessageListener
It seems to work anyway (without JMX support I suppose) though
Ah I see the same issue in the standalone tar.gz file. The bin directory is
set to 000 for some reason.
As for the user/group names, I'm not exactly sure how those got there
unless the assembly plugin or whatever is simply calling whatever version
of tar is on the PATH.
Those errors in the distri
The apache-chainsaw-2.0.0-standalone.tar.gz artifact has wrong
permissions set on the bin directory:
$ tar -tvzf apache-chainsaw-2.0.0-standalone.tar.gz
d- 0/0 0 2017-11-10 19:24 apache-chainsaw/2.0.0/bin/
after extracting:
$ cd apache-chainsaw-2.0.0/
$ ls
bin repo
$ cd bin/
bash:
On 11 November 2017 at 14:44, Mikael Ståldal wrote:
> On 2017-11-10 20:00, Matt Sicker wrote:
>
>> Artifacts:
>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>> svn revision 23048
>>
>
> When I look at that URL, it says: Revision 23059
>
I gave a specific revision so that, if necessa
Ah yes, I didn't note that correctly in the release wiki page. I've updated
the wiki.
On 11 November 2017 at 15:38, Mikael Ståldal wrote:
> Yes, that worked.
>
>
>
> On 2017-11-11 22:22, Scott Deboy wrote:
>
>> I had ran mvn clean site:site install and it worked.
>>
>>
>> On 11/11/17, Mikael Stå
Yes, that worked.
On 2017-11-11 22:22, Scott Deboy wrote:
I had ran mvn clean site:site install and it worked.
On 11/11/17, Mikael Ståldal wrote:
On 2017-11-10 20:00, Matt Sicker wrote:
Artifacts:
https://dist.apache.org/repos/dist/dev/logging/chainsaw/
svn revision 23048
When I look at
I had ran mvn clean site:site install and it worked.
On 11/11/17, Mikael Ståldal wrote:
> On 2017-11-10 20:00, Matt Sicker wrote:
>> Artifacts:
>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>> svn revision 23048
>
> When I look at that URL, it says: Revision 23059
>
On 2017-11-10 20:00, Matt Sicker wrote:
Artifacts:
https://dist.apache.org/repos/dist/dev/logging/chainsaw/
svn revision 23048
When I look at that URL, it says: Revision 23059
Same issue on master branch.
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T17:41:47+01:00)
Java version: 1.8.0_144, vendor: Oracle Corporation
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", arch: "amd64", family: "unix"
On 2017-11-11 21:40, Mikael
$ git checkout chainsaw-2.0.0-rc1
$ mvn clean install
[...]
[INFO] --- maven-assembly-plugin:2.4:single (make-assembly) @
apache-chainsaw ---
Downloading:
https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6/wagon-provider-api-1.0-alpha-6.jar
Downloaded:
I can certainly update the screenshot for the site, though if it's embedded
in the bin archive, then that won't get updated. Thanks for verifying!
On 10 November 2017 at 14:43, Scott Deboy wrote:
> Here's my +1.
>
> Site looks good, and it builds and runs.
>
> Thanks Matt
>
> On 11/10/17, Scott
Here's my +1.
Site looks good, and it builds and runs.
Thanks Matt
On 11/10/17, Scott Deboy wrote:
> Updated screenshot.
>
> On 11/10/17, Scott Deboy wrote:
>> Awesome..I'll commit a new screenshot then.
>>
>> On 11/10/17, Ralph Goers wrote:
>>> The web site doesn’t have to be locked into the
Updated screenshot.
On 11/10/17, Scott Deboy wrote:
> Awesome..I'll commit a new screenshot then.
>
> On 11/10/17, Ralph Goers wrote:
>> The web site doesn’t have to be locked into the release. An image can be
>> updated after the release pretty easily.
>>
>> Ralph
>>
>>
>>> On Nov 10, 2017, at
Awesome..I'll commit a new screenshot then.
On 11/10/17, Ralph Goers wrote:
> The web site doesn’t have to be locked into the release. An image can be
> updated after the release pretty easily.
>
> Ralph
>
>
>> On Nov 10, 2017, at 1:03 PM, Scott Deboy wrote:
>>
>> Would it be possible for me to
The web site doesn’t have to be locked into the release. An image can be
updated after the release pretty easily.
Ralph
> On Nov 10, 2017, at 1:03 PM, Scott Deboy wrote:
>
> Would it be possible for me to push an updated screenshot and re-spin?
>
> On 11/10/17, Scott Deboy wrote:
>> Wow th
Would it be possible for me to push an updated screenshot and re-spin?
On 11/10/17, Scott Deboy wrote:
> Wow that screen shot looks ancient and ugly. I should pull up
> something on the Mac with updated default colors - it looks much
> better.
>
> Scott
>
> On 11/10/17, Matt Sicker wrote:
>> Oh
Wow that screen shot looks ancient and ugly. I should pull up
something on the Mac with updated default colors - it looks much
better.
Scott
On 11/10/17, Matt Sicker wrote:
> Oh, and in case it isn't obvious how to test this, you can extract from
> either the zip or tar.gz files and run the cha
Oh, and in case it isn't obvious how to test this, you can extract from
either the zip or tar.gz files and run the chainsaw script in bin/
corresponding to your operating system. Note that this crashes when using
Java 9 for some reason, so make sure to use Java 6, 7, or 8.
I built this using Java
Quick note: using the maven-release-plugin doesn't seem to work in this
project. Also, sources and documentation are included in the bin.* files
while the standalone.* files are just the jars and startup scripts.
On 10 November 2017 at 13:00, Matt Sicker wrote:
> This is a vote to release Apache
This is a vote to release Apache Chainsaw 2.0.0-rc1.
(Note: I've created release instructions on the new wiki: <
https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>)
Artifacts:
https://dist.apache.org/repos/dist/dev/logging/chainsaw/
svn revision 23048
Site:
http://musigm
37 matches
Mail list logo
