FAQ
Hi folks,

what's the current state of documentation migration?

Cheers,

Siegfried Goeschl


-------- Original Message --------
Subject: Fw: The bitter end of rsync-backed site management is coming Jan 1.
Date: Mon, 10 Dec 2012 07:17:40 -0800 (PST)
From: Joe Schaefer <joe_schaefer@yahoo.com>
Reply-To: private@commons.apache.org, Joe Schaefer <joe_schaefer@yahoo.com>
To: undisclosed recipients: ;

It has come to my attention that some of the projects
that really need to see this message have failed to
pass it through moderation, so I've subbed myself to
all the relevant allow lists and resubmitted here.
If you've seen it already feel free to ignore this message.



----- Forwarded Message -----
From: Joe Schaefer <joe_schaefer@yahoo.com>
To: Apache Infrastructure <infrastructure@apache.org>
Sent: Sunday, December 9, 2012 9:17 PM
Subject: The bitter end of rsync-backed site management is coming Jan 1.


NOTE: If your project's site is using the CMS or svnpubsub
right now you may disregard this note.


If you project is listed below, you have yet to migrate your
site to either the CMS or svnpubsub, which becomes mandatory
starting January 1. This note will serve as your FINAL reminder
to start the process of filing a JIRA ticket with INFRA to
request a migration to one of those two options prior to
January 1, or face a hasty unannounced withdrawal of support
for your website during the month of January upon processing
of all remaining timely outstanding requests filed before Jan 1.


Thanks for your diligence in this matter, further questions
may be addressed to infrastructure@apache.org.


SANTA'S NAUGHTY LIST:
activemq.apache.org
apr.apache.org
archive.apache.org
buildr.apache.org
click.apache.org
commons.apache.org
db.apache.org
directory.apache.org
favicon.ico
felix.apache.org
forrest.apache.org
geronimo.apache.org
hadoop.apache.org
hbase.apache.org
hc.apache.org
hive.apache.org
jackrabbit.apache.org
jmeter.apache.org
juddi.apache.org
karaf.apache.org
lenya.apache.org
maven.apache.org
ode.apache.org
openjpa.apache.org
openwebbeans.apache.org
perl.apache.org
pig.apache.org
poi.apache.org
portals.apache.org
roller.apache.org
santuario.apache.org
shiro.apache.org
sling.apache.org
spamassassin.apache.org
struts.apache.org
synapse.apache.org
tapestry.apache.org
tcl.apache.org
tiles.apache.org
turbine.apache.org
tuscany.apache.org
uima.apache.org
velocity.apache.org
whirr.apache.org
wiki.apache.org
ws.apache.org
xerce
s.apache.org
xml.apache.org
xmlbeans.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org

Search Discussions

  • Siegfried Goeschl at Dec 12, 2012 at 8:43 pm
    Subject: Fwd: Fw: The bitter end of rsync-backed site management is
    coming Jan 1.
    Date: Wed, 12 Dec 2012 21:42:57 +0100
    From: Siegfried Goeschl <sgoeschl@gmx.at>
    Reply-To: sgoeschl@gmx.at
    To: Turbine Developers List <dev@turbine.apache.org>

    Hi folks,

    what's the current state of documentation migration?

    Cheers,

    Siegfried Goeschl


    -------- Original Message --------
    Subject: Fw: The bitter end of rsync-backed site management is coming Jan 1.
    Date: Mon, 10 Dec 2012 07:17:40 -0800 (PST)
    From: Joe Schaefer <joe_schaefer@yahoo.com>
    Reply-To: private@commons.apache.org, Joe Schaefer <joe_schaefer@yahoo.com>
    To: undisclosed recipients: ;

    It has come to my attention that some of the projects
    that really need to see this message have failed to
    pass it through moderation, so I've subbed myself to
    all the relevant allow lists and resubmitted here.
    If you've seen it already feel free to ignore this message.



    ----- Forwarded Message -----
    From: Joe Schaefer <joe_schaefer@yahoo.com>
    To: Apache Infrastructure <infrastructure@apache.org>
    Sent: Sunday, December 9, 2012 9:17 PM
    Subject: The bitter end of rsync-backed site management is coming Jan 1.


    NOTE: If your project's site is using the CMS or svnpubsub
    right now you may disregard this note.


    If you project is listed below, you have yet to migrate your
    site to either the CMS or svnpubsub, which becomes mandatory
    starting January 1. This note will serve as your FINAL reminder
    to start the process of filing a JIRA ticket with INFRA to
    request a migration to one of those two options prior to
    January 1, or face a hasty unannounced withdrawal of support
    for your website during the month of January upon processing
    of all remaining timely outstanding requests filed before Jan 1.


    Thanks for your diligence in this matter, further questions
    may be addressed to infrastructure@apache.org.


    SANTA'S NAUGHTY LIST:
    activemq.apache.org
    apr.apache.org
    archive.apache.org
    buildr.apache.org
    click.apache.org
    commons.apache.org
    db.apache.org
    directory.apache.org
    favicon.ico
    felix.apache.org
    forrest.apache.org
    geronimo.apache.org
    hadoop.apache.org
    hbase.apache.org
    hc.apache.org
    hive.apache.org
    jackrabbit.apache.org
    jmeter.apache.org
    juddi.apache.org
    karaf.apache.org
    lenya.apache.org
    maven.apache.org
    ode.apache.org
    openjpa.apache.org
    openwebbeans.apache.org
    perl.apache.org
    pig.apache.org
    poi.apache.org
    portals.apache.org
    roller.apache.org
    santuario.apache.org
    shiro.apache.org
    sling.apache.org
    spamassassin.apache.org
    struts.apache.org
    synapse.apache.org
    tapestry.apache.org
    tcl.apache.org
    tiles.apache.org
    turbine.apache.org
    tuscany.apache.org
    uima.apache.org
    velocity.apache.org
    whirr.apache.org
    wiki.apache.org
    ws.apache.org
    xerce
    s.apache.org
    xml.apache.org
    xmlbeans.apache.org






    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
    For additional commands, e-mail: dev-help@turbine.apache.org
  • Georg Kallidis at Dec 19, 2012 at 4:07 pm
    Hi there,

    I have a working example of a Jersey (Version 1.16)
    RolesAllowedResourceFilter integration with Jetspeed-1, which could work
    in Turbine similar. It allows having role restricted access to JAXB or
    Jackson annotated classes in Turbine/Jetspeed to get JSON (or XML)
    content - outside the Turbine screen processing. The benefit would be to
    have very much control of JSON - secured by the Turbine authentication;
    on the other side a bunch more dependencies need to be included.

    Does this seem as anything, which the Turbine project could be
    interested in (plain code or just documentation)? Role management issues
    may be are more related to Jetspeed-1 ...

    Background:

    The prototype:
    https://svn.atlassian.com/svn/public/atlassian/vendor/jersey/trunk/osgi/functional-tests/src/test/java/com/sun/jersey/osgi/tests/grizzly/RolesAllowedTest.java
    .

    The question boils down to where to get the user (from session) and how
    to check the role?

    To get the user I just call
    org.apache.turbine.services.rundata.DefaultTurbineRunData.getUserFromSession
    (HttpSession) to get the user session (creating a Rundata object does
    not make much sense outside Turbine, at last I could not see it, why).

    To get the role I am using RoleMangement [1] -which is a Turbine Service
    in Jetspeed-1. What could it be for Turbine core? May
    beorg.apache.turbine.util.SecurityCheck.hasRole(String) or
    straightforward Torque (?)..

    Best regards, Georg

    [1] Cft
    http://portals.apache.org/jetspeed-1/apidocs/org/apache/jetspeed/services/security/RoleManagement.html
    (which provides an TurbineRoleManagement)




    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
    For additional commands, e-mail: dev-help@turbine.apache.org
  • Georg Kallidis at Dec 14, 2012 at 10:43 am
    seems like it have to be done. May be the maven-scm-publish-plugin would
    be the (easiest) way to go?

    This discussion may be helpful:
    http://mail-archives.apache.org/mod_mbox/maven-dev/201205.mbox/%3C668763170.AiMcQ0VOS3@bigmax%3E

    I am not completely clear with that, though..

    Best regards, Georg




    Von: Siegfried Goeschl <sgoeschl@gmx.at>

    An: Turbine Developers List <dev@turbine.apache.org>,

    Datum: 12.12.2012 21:43

    Betreff: Fwd: Fw: The bitter end of rsync-backed site management is coming Jan 1.






    Hi folks,

    what's the current state of documentation migration?

    Cheers,

    Siegfried Goeschl


    -------- Original Message --------
    Subject: Fw: The bitter end of rsync-backed site management is coming
    Jan 1.
    Date: Mon, 10 Dec 2012 07:17:40 -0800 (PST)
    From: Joe Schaefer <joe_schaefer@yahoo.com>
    Reply-To: private@commons.apache.org, Joe Schaefer
    <joe_schaefer@yahoo.com>
    To: undisclosed recipients: ;

    It has come to my attention that some of the projects
    that really need to see this message have failed to
    pass it through moderation, so I've subbed myself to
    all the relevant allow lists and resubmitted here.
    If you've seen it already feel free to ignore this message.



    ----- Forwarded Message -----
    From: Joe Schaefer <joe_schaefer@yahoo.com>
    To: Apache Infrastructure <infrastructure@apache.org>
    Sent: Sunday, December 9, 2012 9:17 PM
    Subject: The bitter end of rsync-backed site management is coming Jan 1.

    NOTE: If your project's site is using the CMS or svnpubsub
    right now you may disregard this note.


    If you project is listed below, you have yet to migrate your
    site to either the CMS or svnpubsub, which becomes mandatory
    starting January 1. This note will serve as your FINAL reminder
    to start the process of filing a JIRA ticket with INFRA to
    request a migration to one of those two options prior to
    January 1, or face a hasty unannounced withdrawal of support
    for your website during the month of January upon processing
    of all remaining timely outstanding requests filed before Jan 1.


    Thanks for your diligence in this matter, further questions
    may be addressed to infrastructure@apache.org.


    SANTA'S NAUGHTY LIST:
    activemq.apache.org
    apr.apache.org
    archive.apache.org
    buildr.apache.org
    click.apache.org
    commons.apache.org
    db.apache.org
    directory.apache.org
    favicon.ico
    felix.apache.org
    forrest.apache.org
    geronimo.apache.org
    hadoop.apache.org
    hbase.apache.org
    hc.apache.org
    hive.apache.org
    jackrabbit.apache.org
    jmeter.apache.org
    juddi.apache.org
    karaf.apache.org
    lenya.apache.org
    maven.apache.org
    ode.apache.org
    openjpa.apache.org
    openwebbeans.apache.org
    perl.apache.org
    pig.apache.org
    poi.apache.org
    portals.apache.org
    roller.apache.org
    santuario.apache.org
    shiro.apache.org
    sling.apache.org
    spamassassin.apache.org
    struts.apache.org
    synapse.apache.org
    tapestry.apache.org
    tcl.apache.org
    tiles.apache.org
    turbine.apache.org
    tuscany.apache.org
    uima.apache.org
    velocity.apache.org
    whirr.apache.org
    wiki.apache.org
    ws.apache.org
    xerce
    s.apache.org
    xml.apache.org
    xmlbeans.apache.org




    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
    For additional commands, e-mail: dev-help@turbine.apache.org





    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
    For additional commands, e-mail: dev-help@turbine.apache.org
  • Thomas Vandahl at Dec 16, 2012 at 9:47 pm

    On 12.12.12 21:42, Siegfried Goeschl wrote:
    Hi folks,

    what's the current state of documentation migration?
    I guess the state is best described as "waiting for someone to take
    action"... For what I've learned from DB, it's supposedly an
    all-or-nothing-approach. We should be fine since everything we publish
    is a maven site. I'll try to start a JIRA with Infra next week to do the
    preparations.

    Bye, Thomas.

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
    For additional commands, e-mail: dev-help@turbine.apache.org

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupdev @
categoriesturbine
postedDec 12, '12 at 8:43p
activeDec 19, '12 at 4:07p
posts5
users4
websiteturbine.apache.org

People

Translate

site design / logo © 2018 Grokbase