Yes,  using the maven site plugin is probably the best way.  We dont want
to do it manually.

You can take it up if you'd like.  If not, I can work on it.  Do let me
know.

Thanks,
Om


On Dec 31, 2016 5:02 AM, "Christofer Dutz" <[email protected]>
wrote:

Hi Om,

Well I guess I would have an idea how to do this using maven and the site
plugin. I would suggest to go down that road for the TourDeFlexJS.

This way we could also bring in the documentation, sources and output of
each example in a standard way.

I don’t know if it would be possible to do this manually as Infra can’t
just give commit rights to any job (just imagine what could be done with
this just by setting the publish address to the git repo of another project
…) Even if I have not tested site build jobs on Jenkins yet, I bet that it
will work with the site-plugin, but I wouldn’t guarantee it to work with
others.

Chris


Am 31.12.16, 04:33 schrieb "[email protected] im Auftrag von OmPrakash
Muppirala" <[email protected] im Auftrag von [email protected]>:

    I can work on the permanent solution after I wrap up the Flex team page
app
    (i.e. soon)

    Chris, I am thinking of setting up a Jenkins web hook that builds and
posts
    a new TourDeFlexJS web app every time a commit is made to a new
    TourDeFlexJS git repo.

    The website can be my personal github site for now.  We can figure out
if
    we want to do a new website or new subdomain on apache.org or simply a
    folder on flex.apache.org later.

    What do you think?

    Thanks,
    Om

    On Dec 30, 2016 2:08 PM, "Alex Harui" <[email protected]> wrote:

    >
    >
    > On 12/30/16, 10:24 AM, "piotrz" <[email protected]> wrote:
    >
    > >PKumar,
    > >
    > >I think that may be our last step once we finished all work on
components
    > >[1] itself.
    > >
    > >[1] https://cwiki.apache.org/confluence/display/FLEX/Table+
Of+Components
    >
    > Any volunteer is welcome to start now.  Should we create a new git
repo
    > for a TourDeFlexJS?  Seems like it should be a different release so
it can
    > be updated independently of the FlexJS SDK?  Or should it all be in
one
    > bundle?
    >
    > Thoughts?
    > -Alex
    >
    >

Reply via email to