On 25/03/2021 20:31, Mark Thomas wrote:
On 25/03/2021 13:50, Mladen Turk wrote:
On 25/03/2021 14:46, Mark Thomas wrote:
On 25/03/2021 12:21, Mladen Turk wrote:
I used to do releases couple of years back.
Since 1.2.5 is mostly fixing procrun issues, I'll try to make that
release
On 25/03/2021 14:46, Mark Thomas wrote:
On 25/03/2021 12:21, Mladen Turk wrote:
I used to do releases couple of years back.
Since 1.2.5 is mostly fixing procrun issues, I'll try to make that
release.
Is there some doc with new set of rules for creating a release?
HOW-TO-RELEASE.txt
I used to do releases couple of years back.
Since 1.2.5 is mostly fixing procrun issues, I'll try to make that release.
Is there some doc with new set of rules for creating a release?
On 18/03/2021 12:23, Gary Gregory wrote:
that would be the most effective path forward IMO
Regards
--
^TM
The Apache Commons Daemon team is pleased to announce the commons-daemon-1.0.15
release!
Version 1.0.15 is bug fix release fixing various issues and regressions
found in 1.0.14 and previous releases.
List of fixed issues can be seen on:
Hi,
There's been a discussion about not deploying certain type of artifacts
to Maven repository (upon which I totally agree).
However how can this be done. Except from manually cleaning up open staging
repo of course.
It would be nice to have some sort of list which types of artifact gets
On 04/03/2013 10:02 AM, Simone Tripodi wrote:
Hi Mladen!
artifacts produced by the assembly-plugin can be detached from the project
by setting to `false` the `attach`[1] property.
In that way, -(src|bin)\.(zip|tar\.gz) artifacts won't be deployed.
Seems exactly what I was looking for.
On 04/03/2013 11:48 AM, sebb wrote:
On 3 April 2013 06:56, Mladen Turk mt...@apache.org wrote:
So building from the tag should be equivalent to building from the source
archive.
Not necessary. Source distribution might have some pre-generated code.
Many projects work like that and some
On 04/03/2013 11:56 AM, sebb wrote:
On 3 April 2013 10:49, Mladen Turk mt...@apache.org wrote:
On 04/03/2013 10:02 AM, Simone Tripodi wrote:
Hi Mladen!
artifacts produced by the assembly-plugin can be detached from the project
by setting to `false` the `attach`[1] property.
In that way
On 04/03/2013 12:14 PM, Jörg Schaible wrote:
Hi Sebb,
This is the point: They cannot be identical, since the manifest contains
also stuff like build time, user name, JDK version (snipped):
== %
$ catmf commons-configuration-1.8.jar
Created-By: Apache Maven Bundle
On 04/03/2013 12:56 PM, Rainer Jung wrote:
From reading this thread my understanding is that the only *minor*
annoyance here is, that the current build procedure includes a metadata
(manifest) entry, that *looks* broken when building not from an svn
checkout but instead from an export or an
On 04/03/2013 08:29 PM, sebb wrote:
On 3 April 2013 11:19, Mladen Turk mt...@apache.org wrote:
Unfortunately that also detaches the archives from the hash generation
process.
So you need to add code (e.g. antrun) to create the hashes.
That's fine. I know how to use md5sum and gpg. No need
On 04/03/2013 08:29 PM, sebb wrote:
On 3 April 2013 11:19, Mladen Turk mt...@apache.org wrote:
Anyhow, gpg sign fails for commons-parent #28. #27 and earlier work.
First I've heard of that.
CP 28 has been used successfully elsewhere AFAIK.
It doesn't work in interactive mode. However
On 04/02/2013 09:49 AM, Jörg Schaible wrote:
Mladen Turk wrote:
On 03/30/2013 11:47 PM, sebb wrote:
On 30 March 2013 20:50, Mladen Turk mt...@apache.org wrote:
Not sure what would be the reason to have that (SVN) info in the
manifest at the first place.
It shows that the build was done
On 04/02/2013 03:30 PM, Jörg Schaible wrote:
Hi Mladen,
Mladen Turk wrote:
On 04/02/2013 09:49 AM, Jörg Schaible wrote:
Mladen Turk wrote:
On 03/30/2013 11:47 PM, sebb wrote:
On 30 March 2013 20:50, Mladen Turk mt...@apache.org wrote:
Not sure what would be the reason to have that (SVN
On 04/02/2013 05:06 PM, Jörg Schaible wrote:
Mladen Turk wrote:
And BTW, build number can use multiple sources and its primary usage
is with continuous integration. Our release version is build number in
this case.
We configured the build to take it from the current svn number to reflect
On 04/03/2013 02:21 AM, sebb wrote:
On 2 April 2013 16:25, Mladen Turk mt...@apache.org wrote:
On 04/02/2013 05:06 PM, Jörg Schaible wrote:
Mladen Turk wrote:
And BTW, build number can use multiple sources and its primary usage
is with continuous integration. Our release version is build
With 3 binding votes (Gary, Phil, Mladen) and one non-binding
vote (Ognjen) I declare this vote as passed.
On 03/28/2013 02:12 PM, Mladen Turk wrote:
Please vote (vote will remain open for at least 72 hours).
Regards
--
^TM
On 03/30/2013 11:47 PM, sebb wrote:
On 30 March 2013 20:50, Mladen Turk mt...@apache.org wrote:
Not sure what would be the reason to have that (SVN) info in the manifest
at the first place.
It shows that the build was done from the relevant tag.
mvn -DbuildNumber=1234 -DscmBranch=54678
On 03/30/2013 09:06 PM, Jörg Schaible wrote:
Jörg Schaible wrote:
And I cannot build the native part if an IBM JDK is the current JDK, because
it does not contain a jni_md.h file.
./configure --with-java=/opt/ibm-java-x86_64-70
or
export JAVA_HOME=/opt/ibm-java-x86_64-70
./configure
and
On 03/28/2013 02:12 PM, Mladen Turk wrote:
Apache Commons Daemon 1.0.15 is
[X] +1 Release
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
My vote FTR.
Regards
--
^TM
On 03/30/2013 09:06 PM, Jörg Schaible wrote:
Jörg Schaible wrote:
the manifest of the commons-daemon-1.0.15.jar contains a strange entry:
=== % =
Implementation-Build: UNKNOWN_BRANCH@r??; 2013-03-28 13:53:43+0100
=== % =
This contains normally the
On 03/30/2013 11:59 PM, Gary Gregory wrote:
On Mar 30, 2013, at 18:48, sebb seb...@gmail.com wrote:
On 30 March 2013 20:50, Mladen Turk mt...@apache.org wrote:
On 03/30/2013 09:06 PM, Jörg Schaible wrote:
Jörg Schaible wrote:
the manifest of the commons-daemon-1.0.15.jar contains
Hi,
We have couple of regressions in 1.0.14 and few other bugs fixed
like (now functional) windows JVM thread dumps, so I plan to tag
and start RM later today.
Comments, objections?
Regards
--
^TM
-
To unsubscribe, e-mail:
On 03/28/2013 11:46 AM, sebb wrote:
On 28 March 2013 07:38, Mladen Turk mt...@apache.org wrote:
Hi,
We have couple of regressions in 1.0.14 and few other bugs fixed
like (now functional) windows JVM thread dumps, so I plan to tag
and start RM later today.
Comments, objections?
OK by me
Apache Commons Daemon 1.0.15 based on RC1 is ready.
This is bug fix release fixing both bugs and regressions
found in previous release(s).
Binaries and sources for testing are at [1], dist layout is at [2],
generated site can be found at [3]. Tag is [4] which will be renamed to
On 03/28/2013 03:33 PM, Simone Tripodi wrote:
I don't think we can speak about standard practices, but Maven
itself[1] publishes -src and -bin artifacts on the central repo.
+1 on NOT publishing them on central repo, but we should find an
automated way to deploy them on SvnPubSub along the
On 03/28/2013 05:24 PM, Emmanuel Bourg wrote:
But binary packages including the jars, the sources, the compiled tests,
the dependencies and the javadoc are just redundant with the other Maven
artifacts.
Agreed.
Those could/should be part of standard distribution method.
Some times we just
On 03/19/2013 01:23 PM, sebb wrote:
https://dist.apache.org/repos/dist/release/commons/daemon/
Done.
Thanks
--
^TM
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail:
The Apache Commons Daemon team is pleased to announce the commons-daemon-1.0.14
release!
Version 1.0.14 is bug fix release fixing various issues
ound in 1.0.13 and previous releases.
Source and binary distributions are available for download
from the Apache Commons download site:
On 03/15/2013 08:12 AM, Mladen Turk wrote:
Apache Commons Daemon 1.0.14 is
[x] +1 Release
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
My vote FTR.
Regards
--
^TM
With 3 binding +1 votes (Luc, Gary and Mladen) and no
other votes I declare this vote as passed.
I'll copy the artefacts and create ANN message after mirrors pick up
the release (within 24 hrs).
On 03/15/2013 08:12 AM, Mladen Turk wrote:
Please vote (vote will remain open for at least 72
On 03/18/2013 10:00 PM, sebb wrote:
On 18 March 2013 13:14, Mladen Turk mt...@apache.org wrote:
With 3 binding +1 votes (Luc, Gary and Mladen) and no
other votes I declare this vote as passed.
I'll copy the artefacts and create ANN message after mirrors pick up
the release (within 24 hrs
Apache Commons Daemon 1.0.14 based on RC1 is ready.
This is bug fix release fixing both bugs and regressions
found in previous release(s).
Binaries and sources for testing are at [1], dist layout is at [2],
generated site can be found at [3]. Tag is [4] which will be renamed to
Hi,
We have few bugs fixed that require a speedy release, so I'll tag
1.0.14 later today and push for a release process.
Regards
--
^TM
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands,
On 02/14/2013 05:30 PM, Sangjin Lee wrote:
Hi,
Is there any information on incompatibilities between 1.0.3 and 1.0.13?
Hadoop is still using 1.0.3 with the known group id issue, and it needs to
be upgraded to a later version. We got this information:
The Apache Commons Daemon team is pleased to announce the
commons-daemon-1.0.13 release!
Version 1.0.13 is bug fix release fixing various issues
found in 1.0.12 and previous releases.
Source and binary distributions are available for download
from the Apache Commons download site:
With 3 binding votes from Luc, Garry and Mladen this vote passes!
I'll copy the artefacts to dist site later today and create ANN
message once that mirrors pick up.
On 02/07/2013 06:37 AM, Mladen Turk wrote:
Apache Commons Daemon 1.0.13 based on RC1 is ready.
It contains a fix for regression
On 02/07/2013 06:37 AM, Mladen Turk wrote:
Apache Commons Daemon 1.0.13 is
[X] +1 Release
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
My vote FTR.
Regards
--
^TM
On 02/07/2013 12:04 PM, sebb wrote:
On 7 February 2013 05:24, Mladen Turk mt...@apache.org wrote:
OK, I was able to upload using .zip file made manually from
my local ~/.m2.
So given all seems there are some serious infra problems with nexus.
Well, I had no problems uploading a SNAPSHOT
Hi,
Exactly the same config as couple of weeks back now gives:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project commons-daemon: Failed to deploy artifacts: Could not transfer artifact commons-daemon:commons-daemon:jar:1.0.13
On 02/06/2013 07:26 PM, Mladen Turk wrote:
I have everything set up in maven config file as before when this operation was
successful.
Crap I have deleted my ~/.m2 directory together
with security-settings.xml. Sorry for the noise :)
Regards
--
^TM
On 02/06/2013 07:26 PM, Mladen Turk wrote:
I have everything set up in maven config file as before when this operation was
successful.
Now I have different problem.
deploy constantly times out. It uploads few files but then it just sits for
a minute a so and fails with timeout.
I have tried
On 02/06/2013 09:38 PM, sebb wrote:
On 6 February 2013 20:15, Mladen Turk mt...@apache.org wrote:
On 02/06/2013 07:26 PM, Mladen Turk wrote:
Perhaps you managed to lock out your account?
OK, I was able to upload using .zip file made manually from
my local ~/.m2.
So given all seems
Apache Commons Daemon 1.0.13 based on RC1 is ready.
It contains a fix for regression found in previous release(s).
Binaries and sources for testing are at [1], dist layout is at [2],
generated site can be found at [3]. Tag is [4] which will be renamed to
COMMONS_DAEMON_1_0_13 if voted.
Please
Hi,
I plan to tag and push for a release Daemon 1.0.13 later today.
We have some regression, or better to say an old problem
which manifested with new version which requires a new release.
The fix was already confirmed by Tomcat folks.
Regards
--
^TM
The Apache Commons Daemon team is pleased to announce the
commons-daemon-1.0.12 release!
Version 1.0.12 is bug fix release fixing various issues
found in 1.0.11 release.
Source and binary distributions are available for download
from the Apache Commons download site:
On 01/15/2013 12:21 PM, Mladen Turk wrote:
Please vote (vote will remain open for at least 72 hours).
Apache Commons Daemon 1.0.12 is
[X] +1 Release
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
[1] http://repository.apache.org
With four +1 binding (Gary, Luc, Phil and Mladen) votes
and no other votes I declare this vote as passed.
I'll move the artefacts to dist site and create ANN once
the mirrors sync up.
[1] http://repository.apache.org/content/repositories/orgapachecommons-128/
[2]
On 01/15/2013 12:21 PM, Mladen Turk wrote:
Apache Commons Daemon 1.0.12 based on RC1 is ready.
It contains several fixes for regressions found in previous release(s).
Binaries and sources for testing are at [1], dist layout is at [2],
generated site can be found at [3]. Tag is [4] which
On 01/16/2013 03:38 PM, sebb wrote:
New signing key needs to be added to LDAP please so it appears under
https://people.apache.org/keys/
Added new fingerprint so it should sync at some point in time.
Regards
--
^TM
-
To
Apache Commons Daemon 1.0.12 based on RC1 is ready.
It contains several fixes for regressions found in previous release(s).
Binaries and sources for testing are at [1], dist layout is at [2],
generated site can be found at [3]. Tag is [4] which will be renamed to
COMMONS_DAEMON_1_0_12 if voted.
Hi,
Had to generate a new key file cause after 10 years my old one expired ;)
I updated KEYS file in svn but don't know how to publish that to a site.
Anyone willing to push that file online?
Regards
--
^TM
-
To unsubscribe,
On 01/14/2013 11:36 AM, Thomas Neidhart wrote:
On Mon, Jan 14, 2013 at 11:27 AM, Mladen Turk mt...@apache.org wrote:
Hi,
Had to generate a new key file cause after 10 years my old one expired ;)
I updated KEYS file in svn but don't know how to publish that to a site.
Anyone willing to push
The Apache Commons Daemon team is pleased to announce the
commons-daemon-1.0.11 release!
Version 1.0.11 is bug fix release fixing various issues
found in 1.0.10 release.
Source and binary distributions are available for download
from the Apache Commons download site:
The Apache Commons Daemon team is pleased to announce the
commons-daemon-1.0.11 release!
Version 1.0.11 is bug fix release fixing various issues
found in 1.0.10 release.
Source and binary distributions are available for download
from the Apache Commons download site:
Huh, obviously a typo in the @subject :(
It should have been '[ANN] Apache Commons Daemon 1.0.11 released'
Should I post another one with the correct @subject?
Regards
--
^TM
-
To unsubscribe, e-mail:
On 11/22/2012 02:22 PM, Mladen Turk wrote:
Apache Commons Daemon 1.0.11 is
[X] +1 Release
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
Just my vote FTR.
--
^TM
With 4 binding votes (Gary, Luc, Mladen and Sebastian)
this vote has been passed!
I'll copy the artefacts to dist site and create ANN
message after the mirrors pick up.
Regards
--
^TM
-
To unsubscribe, e-mail:
On 11/27/2012 03:32 PM, Gary Gregory wrote:
The process creates all you need in nexus. You have to move the -bin
and -src files out before you release to maven central though.
Hmm,
I did mvn -Prelease deploy -DskipTests
So suppose -bin and -src went away.
Can I revert that?
Regards
--
^TM
On 11/27/2012 04:12 PM, sebb wrote:
Can I revert that?
Yes, provided that you have not published the Nexus staging dir (and
I've not seem the commit messages).
I can delete it if you like.
Sure, please do.
Regards
--
^TM
On 11/27/2012 05:00 PM, sebb wrote:
On 27 November 2012 15:31, Mladen Turk mt...@apache.org wrote:
On 11/27/2012 04:12 PM, sebb wrote:
I can delete it if you like.
Sure, please do.
OK, done.
Do you also want me to upload the files from
http://people.apache.org/~mturk/daemon-1.0.11
On 11/25/2012 09:42 PM, Gary Gregory wrote:
Is this something to worry about:
Nope.
.\..\..\apps\prunsrv\prunsrv.c(317) : warning C4996: '_wfopen': This
function or variable may be unsafe. Consider using _wfopen_s instead. To
disable deprecatio
n, use _CRT_SECURE_NO_WARNINGS. See online
Apache Commons Daemon 1.0.11 based on RC1 is ready.
Binaries and sources for testing are at [1], site can be
found at [2]. Tag is [3] which will be renamed to COMMONS_DAEMON_1_0_11 if
voted.
Please vote (vote will remain open for at least 72 hours).
Apache Commons Daemon 1.0.11 is
[ ] +1
Hi,
I plan to tag 1_0_11_RC1 later today and prepare the binaries
for testing and voting. Since there were may fixes I'd like to
give users reporting the bugs a chance to check the candidate
since many of them don't have native development environment
so we unable to check the binaries as bugs
The Apache Commons Daemon team is pleased to announce the
commons-daemon-1.0.10 release!
Version 1.0.10 is bug fix release fixing regression on Linux
platforms introduced with 1.0.9 in case the user does not have
libcap headers at build time and wrongly reported versions
on most platforms.
With required 3 binding +1's from Luc, Jörg and I
and one -0 from Garry I declare this vote as passed.
Will copy the artefacts to dist site and make ANN tomorrow
after the mirrors pick up.
On 02/24/2012 12:41 AM, Mladen Turk wrote:
Fixed a typo in RC1 which caused compile failure in case
On 02/27/2012 06:14 PM, sebb wrote:
Can you also release the jar to Maven please?
Sure, already did steps described at
http://commons.apache.org/releases/release.html
files are already inside
/x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/commons/commons-daemon
and
On 02/27/2012 11:45 PM, sebb wrote:
On 27 February 2012 17:57, Mladen Turkmt...@apache.org wrote:
According to the release.html this should sync to repo1.maven.org
(if the instructions are valid of course)
They are out of date for Nexus-enabled components, which Daemon is.
Not sure how you
On 02/24/2012 12:41 AM, Mladen Turk wrote:
Apache Commons Daemon 1.0.10 is
[X] +1 Release
Just my vote for the record
Regards
--
^TM
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e
On 02/24/2012 02:34 PM, Gary Gregory wrote:
[X] -0 OK, but really should fix...
The Clirr reports compares against 1.0.8 instead of 1.0.9.
http://people.apache.org/~mturk/daemon-1.0.10-site/clirr-report.html
says: The following document contains the results of Clirr.
Current Version:
On 02/24/2012 04:17 PM, Gary Gregory wrote:
On Fri, Feb 24, 2012 at 8:41 AM, Mladen Turkmt...@apache.org wrote:
I downloaded
http://people.apache.org/~mturk/daemon-1.0.10/source/commons-daemon-1.0.10-src.zip
The ran: mvn clean site
and I see:
- Current Version: 1.0.10
- Comparison
... release early, release often.
We have a regression in recently released 1.0.9 which can cause
problems on some linux distributions which don't have libcap.so symlink
like Debian and probably few others (DAEMON-242)
Also this release contains site in src dist (which should make sebb happy :)
On 02/23/2012 07:54 PM, sebb wrote:
On 23 February 2012 10:00, Mladen Turkmt...@apache.org wrote:
[1] http://people.apache.org/~mturk/daemon-1.0.10/
I'm not sure why there is a jar file under:
http://people.apache.org/~mturk/daemon-1.0.10/binaries/
It's already in the binary archives.
Not
On 02/23/2012 09:19 PM, Luc Maisonobe wrote:
Le 23/02/2012 11:00, Mladen Turk a écrit :
I have checked again the exact same commands on commons-daemon-1.0.9 and
compilation went smoothly.
Right, different test and actual commit.
Fixed the typo. Will do RC2 tomorrow and call for another vote
Cancelled due to bug when libcap is not present on the system
Already tagged RC2, so will call for another vote when the artifacts gets
prepared
Regards
--
^TM
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For
On 02/24/2012 12:08 AM, sebb wrote:
On 23 February 2012 22:51,mt...@apache.org wrote:
Author: mturk
Date: Thu Feb 23 22:51:38 2012
New Revision: 1293004
URL: http://svn.apache.org/viewvc?rev=1293004view=rev
Log:
Oh well, hope no one will change that again untill we pass the release process
On 02/14/2012 11:03 PM, sebb wrote:
This is a vote to release Apache Commons NET 3.1 based on RC2.
[X] +1 release it
Looks good.
Regards
--
^TM
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional
The Apache Commons Daemon team is pleased to announce the
commons-daemon-1.0.9 release!
Version 1.0.9 is bug fix release fixing few minor issues.
Source and binary distributions are available for download
from the Apache Commons download site:
We have 3 +1's from Mark, Luc and Mladen
Thus the vote passed. I'll push the sources
and create an ANN later today.
Regards
--
^TM
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail:
On 02/07/2012 01:52 PM, Mladen Turk wrote:
Votes, please. This vote will close in 72 hours
[X] +1 Release Daemon 1.0.9
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
Just to record my vote.
Since 72 hour period exceeded, suppose I'll just
On 02/06/2012 09:10 PM, sebb wrote:
On 6 February 2012 17:45, Mladen Turkmt...@apache.org wrote:
Hmm, right. I'll revert the patch. There should be no surprises
or new features with 1.0.x branch.
Think that --foo=a ++foo=b ++foo=c should behave like
If there was foo set, set to a b c, not add
On 02/07/2012 12:59 PM, sebb wrote:
On 7 February 2012 10:37, Mladen Turkmt...@apache.org wrote:
I'll tag and prepare 1.0.9 RC later today.
Can you also do the Maven jars?
Sure, but have no idea how to do that.
Regards
--
^TM
Hi,
Version 1.0.9 is bug fix release.
Daemon 1.0.9 RC1 is available for review at:
http://people.apache.org/~mturk/daemon-1.0.9/
It is based on the svn tag
https://svn.apache.org/repos/asf/commons/proper/daemon/tags/COMMONS_DAEMON_1_0_9_RC1
which if voted will be renamed to
On 02/07/2012 02:46 PM, Gary Gregory wrote:
Hi All:
I am not sure how much of an issue this is but I get the following warnings
on Windows 7 64-bit and Microsoft Visual Studio 10.0:
cd src\native\windows\apps
cd prunsrv
nmake CPU=X64
cl -c -nologo -DWIN32 -D_WIN32 -D_WINDOWS
On 02/07/2012 07:23 PM, sebb wrote:
On 7 February 2012 12:52, Mladen Turkmt...@apache.org wrote:
Maven arifacts are at:
http://people.apache.org/~mturk/daemon-1.0.9/maven/
note that starting with this release, the windows binaries
are in the maven repo, finally :)
For some reason the
On 02/07/2012 08:16 PM, Gary Gregory wrote:
On the topic of Maven: it seems of odd to have EXEs in a ZIP file, the
EXEs, like JAR files, should just be there, ready to be downloaded and used
as-is. Unless I am missing something.
Please do not hijack vote thread for technical discussions.
On 02/07/2012 08:46 PM, sebb wrote:
On 7 February 2012 19:17, Mladen Turkmt...@apache.org wrote:
On 02/07/2012 07:23 PM, sebb wrote:
I would move the zip and tar.gz archives out of /maven (but copy the
windows one)
Also copy the binary jar from /maven to /binaries
OK, I'll just rerun the
On 02/07/2012 09:31 PM, Mladen Turk wrote:
On 02/07/2012 08:46 PM, sebb wrote:
On 7 February 2012 19:17, Mladen Turkmt...@apache.org wrote:
On 02/07/2012 07:23 PM, sebb wrote:
I would move the zip and tar.gz archives out of /maven (but copy the
windows one)
Also copy the binary jar from
On 02/07/2012 10:20 PM, Gary Gregory wrote:
On Feb 7, 2012, at 15:03, Mladen Turkmt...@apache.org wrote:
On 02/07/2012 08:16 PM, Gary Gregory wrote:
On the topic of Maven: it seems of odd to have EXEs in a ZIP file, the
EXEs, like JAR files, should just be there, ready to be downloaded and
Hi,
There are few important bug fixes for 1.0.8 so I plan to push
for a 1.0.9 bugfix release later this week.
Is there anything else we should consider before doing that?
sebb, you always have something to say at vote time, so here is
the chance to do that before ;)
Regards
--
^TM
On 02/06/2012 09:30 AM, Mladen Turk wrote:
Is there anything else we should consider before doing that?
Please note that the sources are inside branches/1.0.x not trunk!
(Just in case someone forgot that we are going to release 1.0.x
versions from 1.0.x branch from now on)
Regards
--
^TM
On 02/06/2012 12:48 PM, sebb wrote:
On 6 February 2012 10:12, Mladen Turkmt...@apache.org wrote:
On 02/06/2012 09:30 AM, Mladen Turk wrote:
Is there anything else we should consider before doing that?
I've just raised DAEMON-240; it would be good if the docs could be
updated accordingly
On 02/06/2012 03:55 PM, sebb wrote:
Sure, but the docs can always be updated at any time.
We don't have to wait for a release or something to update our web site.
That particular JIRA could involve code changes as well.
Also, we include the site source in the archive.
Right, this is
On 02/06/2012 04:15 PM, sebb wrote:
On 6 February 2012 15:06, Mladen Turkmt...@apache.org wrote:
On 02/06/2012 03:55 PM, sebb wrote:
Sure, but the docs can always be updated at any time.
We don't have to wait for a release or something to update our web site.
That particular JIRA could
On 02/06/2012 05:02 PM, sebb wrote:
On 6 February 2012 15:25, Mladen Turkmt...@apache.org wrote:
I don't, but since its there, so be it.
OK, in that case what's needed is to decide whether the current
behaviour should be fixed and documented or just documented.
You mean with DAEMON-240?
On 02/06/2012 05:16 PM, sebb wrote:
On 6 February 2012 16:05, Mladen Turkmt...@apache.org wrote:
On 02/06/2012 05:02 PM, sebb wrote:
On 6 February 2012 15:25, Mladen Turkmt...@apache.orgwrote:
I don't, but since its there, so be it.
OK, in that case what's needed is to decide
On 11/24/2011 07:36 PM, Gary Gregory wrote:
I think commons stuff no longer carry the Jakarta prefix. It's Apache
Commons now. Not Apache Jakatra Commons.
Sure, that's old stuff I moved from branches to tags so it doesn't
pollute the branches dir. Its purely for archive purposes.
There are
On 11/24/2011 08:12 PM, sebb wrote:
+
+We assume, that you checked out
+https://svn.apache.org/repos/asf/commons/proper/daemon/trunk
Would it not be better to tag first and then check out the tag?
Sure that is one of the options.
Anyhow here I try to explain (work-in-progress) what
has to
Sebastian,
Could you push the maven artifacts?
The one we voted are in the
http://people.apache.org/~mturk/daemon-1.0.8/.deploy/
On 11/23/2011 12:32 PM, Mladen Turk wrote:
With my implicit +1 we have
+1 Simone, Phil, Luc, Jörg, Gary, James, Mladen
-1 Sebastian
Commons daemon 1.0.8 has been
The Apache Commons Daemon team is pleased to announce the
commons-daemon-1.0.8 release!
Version 1.0.8 is both a bug fix and feature update release.
Source and binary distributions are available for download
from the Apache Commons download site:
1 - 100 of 230 matches
Mail list logo
