Am 24.09.2017 um 18:31 schrieb sebb:
The document is missing a step (just added).
Thanks!
I have added the same redirects for commons discovery.
Cheers,
Pascal
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For
On 24 September 2017 at 13:35, Pascal Schumacher
wrote:
> Am 24.09.2017 um 14:31 schrieb sebb:
>>>
>>> to:
>>> https://svn.apache.org/repos/asf/commons/dormant/launcher
>>>
>>> Synchronization of the git mirror
>>> (git://git.apache.or
Am 24.09.2017 um 14:31 schrieb sebb:
to:
https://svn.apache.org/repos/asf/commons/dormant/launcher
Synchronization of the git mirror
(git://git.apache.org/commons-launcher.git) has been deactivated.
The website has moved from:
http://commons.apache.org/proper/commons-launcher/
There ought to
On 24 September 2017 at 13:12, Pascal Schumacher
wrote:
> Hi,
>
> since no development has happened for a long while, the Apache Commons
> Launcher component
> has been moved to dormant. No further development is expected.
>
> The SVN location has changed from:
> https://
Hi,
since no development has happened for a long while, the Apache Commons
Launcher component
has been moved to dormant. No further development is expected.
The SVN location has changed from:
https://svn.apache.org/repos/asf/commons/proper/launcher
to:
https://svn.apache.org/repos/asf/commons
Time to wrap up. The following votes were cast (in order of appearance):
Rob Tompkins: +1
Gary Gregory: +1
Agustín Bernal Fernando: +1 (non-binding)
Amey Jadiye: +1 (non-binding)
Bernd Eckenfels: +1
Ralph Goers: +1
Benedikt Ritter: +1
Pascal Schumacher: +1
The vote has passed. Thanks to all the
+1
Am 21.08.2017 um 08:30 schrieb Benedikt Ritter:
+1
Am 20.08.2017 um 12:11 schrieb Pascal Schumacher :
Hi all,
as discussed, I'd like to propose to move Apache Commons Launcher to dormant.
Reasons:
- The last release is from 2007.
- No bugfix or feature addition commits since 2007
+1
> Am 20.08.2017 um 12:11 schrieb Pascal Schumacher :
>
> Hi all,
>
> as discussed, I'd like to propose to move Apache Commons Launcher to dormant.
>
> Reasons:
> - The last release is from 2007.
> - No bugfix or feature addition commits since 2007.
>
+1
Ralph
> On Aug 20, 2017, at 3:11 AM, Pascal Schumacher
> wrote:
>
> Hi all,
>
> as discussed, I'd like to propose to move Apache Commons Launcher to dormant.
>
> Reasons:
> - The last release is from 2007.
> - No bugfix or feature addition commits s
+1
Gruss
Bernd
--
http://bernd.eckenfels.net
On Sun, Aug 20, 2017 at 3:41 PM, Pascal Schumacher
mailto:pascalschumac...@gmx.net> wrote:
> Hi all,
>
> as discussed, I'd like to propose to move Apache Commons Launcher to
> dormant.
>
> Reasons:
> - The last release i
+1
On Sun, Aug 20, 2017 at 3:41 PM, Pascal Schumacher wrote:
> Hi all,
>
> as discussed, I'd like to propose to move Apache Commons Launcher to
> dormant.
>
> Reasons:
> - The last release is from 2007.
> - No bugfix or feature addition commits since 2007.
>
>
+1
On Sun, Aug 20, 2017, 6:44 AM Gary Gregory wrote:
> +1
>
> Gary
>
> On Aug 20, 2017 04:12, "Pascal Schumacher"
> wrote:
>
> > Hi all,
> >
> > as discussed, I'd like to propose to move Apache Commons Launcher to
> > dormant.
&g
+1
Gary
On Aug 20, 2017 04:12, "Pascal Schumacher" wrote:
> Hi all,
>
> as discussed, I'd like to propose to move Apache Commons Launcher to
> dormant.
>
> Reasons:
> - The last release is from 2007.
> - No bugfix or feature addition commits since 2007
+1
> On Aug 20, 2017, at 6:11 AM, Pascal Schumacher
> wrote:
>
> Hi all,
>
> as discussed, I'd like to propose to move Apache Commons Launcher to dormant.
>
> Reasons:
> - The last release is from 2007.
> - No bugfix or feature addition commits since 2
Hi all,
as discussed, I'd like to propose to move Apache Commons Launcher to
dormant.
Reasons:
- The last release is from 2007.
- No bugfix or feature addition commits since 2007.
So please cast your votes:
This vote will close no sooner that 72 hours from now,
i.e. after 13:00CET 23 A
Hello.
On Sun, 13 Aug 2017 20:42:34 +0200, Pascal Schumacher wrote:
Hello everybody,
an opinions on moving commons-launcher to dormant?
The last release is from 2007 and their have not been any bugfix or
feature addition commits since.
It might be interesting to know the reason for the
On 13 Aug 2017 7:43 pm, "Pascal Schumacher"
wrote:
Hello everybody,
an opinions on moving commons-launcher to dormant?
The last release is from 2007 and their have not been any bugfix or feature
addition commits since.
+1
Ok here.
Gary
On Aug 13, 2017 12:43, "Pascal Schumacher" wrote:
> Hello everybody,
>
> an opinions on moving commons-launcher to dormant?
>
> The last release is from 2007 and their have not been any bugfix or
> feature addition commits s
Hello everybody,
an opinions on moving commons-launcher to dormant?
The last release is from 2007 and their have not been any bugfix or
feature addition commits since.
Cheers,
Psacal
-
To unsubscribe, e-mail: dev-unsubscr
red guidance on migrating some of the more
common usage patterns of JDK-internal APIs
to supported public interfaces. The list is on the OpenJDK wiki [0], along with
instructions on how to run the jdeps analysis tool yourself .
I have prepared reports , attached to this email, for commons-jelly-1.
al APIs
>>> to supported public interfaces. The list is on the OpenJDK wiki [0], along
>>> with instructions on how to run the jdeps analysis tool yourself .
>>>
>>> I have prepared reports , attached to this email, for commons-jelly-1.0 &
>>> common
commons-launcher attached.
Rgds,Rory
On 17/10/2014 19:22, Paul Libbrecht wrote:
Rory,
I see no attachments here. Can you post it to some web-place please?
paul
On 17 oct. 2014, at 10:42, Rory O'Donnell wrote:
Hi Benedict,
As I already mentioned we have prepared guidance on migr
y-1.0 &
commons-launcher-1.1 based on the jdeps output.
For anything where your migration path is unclear, I would appreciate comments
on the JDK-internal API usage patterns in the attached jdeps reports - in
particular comments elaborating on the rationale for them - either to me or on
the
Is
> to supported public interfaces. The list is on the OpenJDK wiki [0], along
> with instructions on how to run the jdeps analysis tool yourself .
>
> I have prepared reports , attached to this email, for commons-jelly-1.0 &
> commons-launcher-1.1 based on the jdeps output.
&g
reports , attached to this email, for commons-jelly-1.0
& commons-launcher-1.1 based on the jdeps output.
For anything where your migration path is unclear, I would appreciate
comments on the JDK-internal API usage patterns in the attached jdeps
reports - in particular comments elaboratin
mentUtils.java
>
> commons/proper/exec/trunk/src/main/java/org/apache/commons/exec/environment/OpenVmsProcessingEnvironment.java
>
> commons/proper/exec/trunk/src/main/java/org/apache/commons/exec/launcher/CommandLauncher.java
>
> commons/proper/exec/trunk/src/main/java/org/apache/com
Le 16/06/2013 14:15, Ricardo Espírito Santo a écrit :
> Please let me know what you think so that I can start getting my hands onto
> the actual job itself.
-0
I don't find the [launcher] strategy for starting processes very
appealing and I fear this will just bring unnecessary blo
ed on his last message.
[Exec] is a broader project and it seems to make sense to integrate
[Launcher] into it. Even if we call the final product something else.
I thought that a good point for integration could be a non disruptive
approach by simply implementing the LauncherBootstrap ([Lau
Hi folks,
had a quick look
* similar functionality of both components
* launcher has some bells and whistles regarding launching Java
processes compared to commons-exec
* commons-launcher has Ant dependencies
IMHO retiring commons-launcher and moving it to commons-exec is a good idea
Hi folks,
there is actually "launcher" code in commons-exec - see
org.apache.commons.exec.launcher
I'm having a look "Launcher" code this evening
Cheers,
Siegfried Goeschl
On 10.06.13 12:07, Ricardo Espírito Santo wrote:
Hi Emmanuel,
Thank you for your comments.
ternal application from Java
> launcher: Start a Java application from the shell
>
> Besides launching something they don't look that similar to me.
>
That's a very good similarity! They both launch something and since that is
99% of what they do I'd say they do pretty m
Le 09/06/2013 22:03, Ricardo Espírito Santo a écrit :
> - Very similar objectives, features and aims
exec: Invoke an external application from Java
launcher: Start a Java application from the shell
Besides launching something they don't look that similar to me.
> - Simplifica
Hi all,
Following an initial idea of Gary Gregory, I have written a small proposal
regarding the merge of Launcher and Exec.
If this idea gains enough momentum I shall devise a plan and continue with
the rest of the required work.
Please comment and vote for merge +1 or no merge -1
ricardoespsa...@gmail.com>
> > > wrote:
> > > > Ok a bit more educated about the [exec] project now and yes I do
> > believe
> > > > [exec] is sort of too small to be left on its own.
> > > >
> > > > I liked the idea of merging it into
k a bit more educated about the [exec] project now and yes I do
> believe
> > > [exec] is sort of too small to be left on its own.
> > >
> > > I liked the idea of merging it into [launcher] or the other way around
> > but
> > > then I liked your next idea
On Wed, Jun 5, 2013 at 6:11 PM, sebb wrote:
> On 5 June 2013 22:53, Ricardo Espírito Santo
> wrote:
> > Ok a bit more educated about the [exec] project now and yes I do believe
> > [exec] is sort of too small to be left on its own.
> >
> > I liked the idea of mer
On 5 June 2013 22:53, Ricardo Espírito Santo wrote:
> Ok a bit more educated about the [exec] project now and yes I do believe
> [exec] is sort of too small to be left on its own.
>
> I liked the idea of merging it into [launcher] or the other way around but
> then I liked your
Ok a bit more educated about the [exec] project now and yes I do believe
[exec] is sort of too small to be left on its own.
I liked the idea of merging it into [launcher] or the other way around but
then I liked your next idea even better merging them both into [lang] ...
However, on a second
action since two years or
> so...
> >
> > So I guess my real question now is 'Is it possible to retake control of a
> > project which has been left semi-abandoned?'
> >
>
> Yes, development is based on contributions from the community.
>
> WRT [launc
action since two years or so...
>
> So I guess my real question now is 'Is it possible to retake control of a
> project which has been left semi-abandoned?'
>
Yes, development is based on contributions from the community.
WRT [launcher], I wonder if we could merge it with [e
Hi Gary,
Thanks for your reply!
I kinda was expecting that answer but I'm sort of curious as to what
happens to a project that gets no love from anyone for a long while?
The reason I'm asking this is that I have been buzzing around the commons
projects for a few days trying to find something I c
Hi,
No one is "in charge" of any Commons component. The community develops and
supports Commons as each participant and member sees fit.
Gary
On Tue, Jun 4, 2013 at 4:33 PM, Ricardo Espírito Santo <
ricardoespsa...@gmail.com> wrote:
> Is there anyone in charge of this project?
>
> Thanks,
> Ri
Is there anyone in charge of this project?
Thanks,
Ricardo Espírito Santo
Hi devs,
I like to know whether the $subject is possible with Apache Launcher ?
If I have a particular method I want to start as a separate child process of
my parent process how I am suppose to use Launcher class in apache Launcher.
I don't want to use any ant script or anything my requir
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-launcher has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-launcher has an issue affecting its community integration.
This issue
far. Anyway, the situation
I've described applies precisely for me in this
instance; I actually have looked at your patches, but
simply have not had the time to do more than that.
You should indeed feel free to nag the list
periodically in case someone has had some time open up
and forgot
On 12/28/07, Mark Horn <[EMAIL PROTECTED]> wrote:
> Rahul,
>
> Thanks for the links. I have reviewed them in the past, but will do so again.
>
I doubt anything has changed, if you've seen them, you're upto speed :-)
> I did attach a patch file w/ my requested change in JIRA and reviewing
> Lau
olkar <[EMAIL PROTECTED]> wrote:
> On 12/28/07, Mark Horn <[EMAIL PROTECTED]> wrote:
> > Is Commons-Launcher still active? The last release appears to be
> > quite some time ago ( Jan. 2005 ) and issues/feature requests have
> > been logged into JIRA (including one by
On 12/28/07, Mark Horn <[EMAIL PROTECTED]> wrote:
> Is Commons-Launcher still active? The last release appears to be
> quite some time ago ( Jan. 2005 ) and issues/feature requests have
> been logged into JIRA (including one by myself) but there does not
> seem to be any activ
Is Commons-Launcher still active? The last release appears to be
quite some time ago ( Jan. 2005 ) and issues/feature requests have
been logged into JIRA (including one by myself) but there does not
seem to be any activity on the project what so ever.
Is there a better alternative to commons
51 matches
Mail list logo
