Daniel F. Savarese | 10 Mar 2011 17:16
Favicon

www.apache.org/dist


For anyone who didn't see the original thread, the PMC received instructions
to review their release distribution areas in www.apache.org/dist and
remove any old releases.  sebb removed some older releases, and I asked
if the oro tree could be removed entirely since it has moved to the attic.
However, the same is true for ecs and taglibs, so I'm expanding this topic
to cover ECS, ORO, and Taglibs, all of which have been attic'ed, but still
have directory trees in dist/.

In message <AANLkTiniasa54oRhFzQOYLuSRwpCju=zXMxxcUHe=JHJ <at> mail.gmail.com>, sebb
 writes:
>Perhaps we should update the websites of such projects to make it
>possible to find releases?
>At present, there are no working download links for ORO.

After looking into it, I can't find any download links off of
attic.apache.org for the above projects pointing visitors to
archive.apache.org/dist/.  I may have simply missed it.

>Probably my fault when I cleared up the downloads site definitions.

I don't think you missed anything (and thanks for all the work you did
by the way).  Everything at http://attic.apache.org/process.html
appears to have been done.  I think we should remove the download links
on the dead project pages and leave it up to the Attic PMC to decide whether
they should place a link to archive.apache.org/dist/ on their site
(it's probably there somehwere and I just couldn't find it).

Whatever the case may be, I'd still like to remove
www.apache.org/dist/jakarta/{ecs,oro,taglibs} if there are no objections.
(Continue reading)

Daniel F. Savarese | 12 Mar 2011 03:00
Favicon

www.apache.org/dist


I wrote:
>Whatever the case may be, I'd still like to remove
>www.apache.org/dist/jakarta/{ecs,oro,taglibs} if there are no objections.
...
>that in?), I can remove the "Downloads" link from the oro and ecs pages.

Since there were no objections, I executed the above actions.

daniel
Daniel F. Savarese | 12 Mar 2011 03:09
Favicon

Re: [RESULT][VOTE][LAZY] Move ECS, ORO and Regexp to Attic


In message <AANLkTinRs=hkw5jFZ5Aqww-G9Xwbvcg84LRdogFGMj_8 <at> mail.gmail.com>, Rahu
l Akolkar writes:
>We will not move Regexp at this time as vgritsenko has expressed some
>interest in a recent bugfix (his vote to move Regexp to the Attic was
>+0). Lets revisit Regexp in 6 months time if there isn't much
>activity.

Six months have passed and there hasn't been much activity.
Should we revisit this now?  Someone recently offered to contribute some
code on regexp-user <at> , but it didn't generate enough interest for anyone
to reply. 

daniel
Ian Darwin | 12 Mar 2011 16:33
Picon
Favicon
Gravatar

Re: [RESULT][VOTE][LAZY] Move ECS, ORO and Regexp to Attic


> Six months have passed and there hasn't been much activity.
> Should we revisit this now?  Someone recently offered to contribute some
> code on regexp-user <at> , but it didn't generate enough interest for anyone
> to reply. 
> 
> daniel

No-one's even interested in replying to Daniel's mail :-)

I guess that means it should go to the Attic.
Rahul Akolkar | 12 Mar 2011 19:13
Picon

Re: Regexp (was: Move ECS, ORO and Regexp to Attic)

On Sat, Mar 12, 2011 at 10:33 AM, Ian Darwin <ian <at> darwinsys.com> wrote:
>
>> Six months have passed and there hasn't been much activity.
>> Should we revisit this now?  Someone recently offered to contribute some
>> code on regexp-user <at> , but it didn't generate enough interest for anyone
>> to reply.
>>
>> daniel
>
> No-one's even interested in replying to Daniel's mail :-)
>
> I guess that means it should go to the Attic.
>
<snip/>

Barring strong objections at this time, I'll initiate the process in
one week (as we did for ECS and ORO, starting with a lazy consensus
vote).

-Rahul
Vadim Gritsenko | 14 Mar 2011 13:09

Re: Regexp (was: Move ECS, ORO and Regexp to Attic)

On Mar 12, 2011, at 1:13 PM, Rahul Akolkar wrote:

> On Sat, Mar 12, 2011 at 10:33 AM, Ian Darwin <ian <at> darwinsys.com> wrote:
>> 
>>> Six months have passed and there hasn't been much activity.
>>> Should we revisit this now?  Someone recently offered to contribute some
>>> code on regexp-user <at> , but it didn't generate enough interest for anyone
>>> to reply.
>>> 
>>> daniel
>> 
>> No-one's even interested in replying to Daniel's mail :-)

On Friday night? Bah!

>> I guess that means it should go to the Attic.
>> 
> <snip/>
> 
> Barring strong objections at this time, I'll initiate the process in
> one week (as we did for ECS and ORO, starting with a lazy consensus
> vote).

I don't think I'll get to it within next few months, so will not object to moving it.

Vadim
Vadim Gritsenko | 14 Mar 2011 13:11

Re: [RESULT][VOTE][LAZY] Move ECS, ORO and Regexp to Attic

On Mar 11, 2011, at 9:09 PM, Daniel F. Savarese wrote:

> Someone recently offered to contribute some code on regexp-user <at> ,

Daniel -

Unless I miss something... regexp-user is dead though? Was replaced by general a good while ago.

Vadim
sebb | 14 Mar 2011 14:02
Picon

Re: [RESULT][VOTE][LAZY] Move ECS, ORO and Regexp to Attic

On 14 March 2011 12:11, Vadim Gritsenko <vadim <at> reverycodes.com> wrote:
> On Mar 11, 2011, at 9:09 PM, Daniel F. Savarese wrote:
>
>> Someone recently offered to contribute some code on regexp-user <at> ,
>
> Daniel -
>
> Unless I miss something... regexp-user is dead though? Was replaced by general a good while ago.

It was the Jakarta dev lists that were merged. The user lists are
still independent.

> Vadim
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe <at> jakarta.apache.org
> For additional commands, e-mail: general-help <at> jakarta.apache.org
>
>
Goyo | 21 Mar 2011 10:52

Can't move files using symbolic links (allowLinking=true)

Hi.
I need to use a symbolic link to access a certain path in my server, where
I'm using Jakarta Tomcat 4.1.18.
We stablished a symbolic link to another path. At first, tomcat didn't see
this path through the symlink, but we searched for it and found the
allowLinking=true feature.
Now, it sees the path. However, and here comes the problem, it doesn't allow
to move files to this path.
We've tried to move files manually with the same user of tomcat and it works
well, but it doesn't via the web application. Besides, this feature worked
perfect before making this folder reachable through a symlink.

And we don't know what we have done wrong. Any help?

This is our config.xml:

       <Context path="/documents" docBase="/opt/rware/sgidoc/data" debug="0"
                 reloadable="true" crossContext="true">
                      <Resources
className="org.apache.naming.resources.FileDirContext"
                         allowLinking="true" />
        </Context>

        <Context path="/documents/temp" docBase="/opt/rware/my_app/pdf_mark"
debug="0"
                 reloadable="true" crossContext="true"/>

        <Context  path="/my_app" docBase="sgidoc"  debug="5"
reloadable="true" crossContext="true">
                <Resources
(Continue reading)

sebb | 21 Mar 2011 14:02
Picon

Re: Can't move files using symbolic links (allowLinking=true)

On 21 March 2011 09:52, Goyo <goyocasero <at> gmail.com> wrote:
> Hi.
> I need to use a symbolic link to access a certain path in my server, where
> I'm using Jakarta Tomcat 4.1.18.

Jakarta Tomcat is now an independent project, see

http://tomcat.apache.org/

where you will find documentation and details of how to subscribe to
their user mailing list.

> We stablished a symbolic link to another path. At first, tomcat didn't see
> this path through the symlink, but we searched for it and found the
> allowLinking=true feature.
> Now, it sees the path. However, and here comes the problem, it doesn't allow
> to move files to this path.
> We've tried to move files manually with the same user of tomcat and it works
> well, but it doesn't via the web application. Besides, this feature worked
> perfect before making this folder reachable through a symlink.
>
> And we don't know what we have done wrong. Any help?
>
> This is our config.xml:
>
>       <Context path="/documents" docBase="/opt/rware/sgidoc/data" debug="0"
>                 reloadable="true" crossContext="true">
>                      <Resources
> className="org.apache.naming.resources.FileDirContext"
>                         allowLinking="true" />
(Continue reading)


Gmane