2013/2/14 Dave Newton :
> Including the wiki doc links, like the "themes and templates" off the
> "guides" homepate.
>
> http://struts.apache.org/2.x/docs/guides.html
>
> Links to (non-working) themes and templates docs:
>
> http://struts.apache.org/development/2.x/docs/themes-and-templates.html
R
2013/2/14 Dave Newton :
> Including the wiki doc links, like the "themes and templates" off the
> "guides" homepate.
>
> http://struts.apache.org/2.x/docs/guides.html
>
> Links to (non-working) themes and templates docs:
>
> http://struts.apache.org/development/2.x/docs/themes-and-templates.html
>
(I take that back a little--the link target itself is correct, but it
redirects.)
On Wed, Feb 13, 2013 at 8:48 PM, Dave Newton wrote:
> Including the wiki doc links, like the "themes and templates" off the
> "guides" homepate.
>
> http://struts.apache.org/2.x/docs/guides.html
>
> Links to (non-
Including the wiki doc links, like the "themes and templates" off the
"guides" homepate.
http://struts.apache.org/2.x/docs/guides.html
Links to (non-working) themes and templates docs:
http://struts.apache.org/development/2.x/docs/themes-and-templates.html
Removing the "development" chunk actua
2013/2/13 Lukasz Lenart :
> F..k! Download does not work :/
>
> http://struts.apache.org/download.cgi#struts238
And there are other problems with the links :\
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
-
To u
F..k! Download does not work :/
http://struts.apache.org/download.cgi#struts238
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands,
The site is fully migrated to CMS/SvnPubSub, even my script to update
the Draft Docs is working :-)
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For ad
Uff... finally I've migrated subsites as well
http://people.apache.org/~lukaszlenart/
Please remember that the .htaccess doesn't work correctly here as it
was configured to redirect /2.x into /development/2.x so if you want
to see the subsites you must manually update the link, eg.:
http://peopl
On Sat, Jan 19, 2013 at 5:00 PM, Rene Gielen wrote:
> Great job! :)
+1!
Thanks!
> Am 19.01.13 14:24, schrieb Lukasz Lenart:
>> Success!
>> http://struts.staging.apache.org/
>>
>> Subsites left ;-)
>>
>>
>> Regards
>>
>
>
> --
> René Gielen
> http://twitter.com/rgielen
>
> --
Great job! :)
Am 19.01.13 14:24, schrieb Lukasz Lenart:
> Success!
> http://struts.staging.apache.org/
>
> Subsites left ;-)
>
>
> Regards
>
--
René Gielen
http://twitter.com/rgielen
-
To unsubscribe, e-mail: dev-unsubscr.
Success!
http://struts.staging.apache.org/
Subsites left ;-)
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/1/18 Lukasz Lenart :
> I'm discussing over INFRA list how to solve our problem
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2013/1/18 L
I'm discussing over INFRA list how to solve our problem
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/1/18 Lukasz Lenart :
> Hope, that's the answer :-)
>
> http://maven.apache.org/plugins/maven-scm-publish-plugin/examples/one-module-configuration.html
>
>
> Regards
> --
> Ł
Hope, that's the answer :-)
http://maven.apache.org/plugins/maven-scm-publish-plugin/examples/one-module-configuration.html
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/1/18 Lukasz Lenart :
> I totally don't understand how does it work, at all :/
>
> I thought, when I comm
I totally don't understand how does it work, at all :/
I thought, when I commit something to [1] then this will be reflected
in [2], but there are maven site related files in [1] and in [2] is
something like half of what Maven Site plugin is doing :\
[1] https://svn.apache.org/repos/asf/struts/si
2013/1/18 Rene Gielen :
> Did you run some maven build to fill the actual content in the svn space
> to publish?
No, I don't know which goal to execute :\
> Someone might correct me if I'm wrong, but would we would need to do now
> is to change site-pom to use maven-scm-publish plugin for distrib
Hi,
actually it looks to me as "expected".
I think we can now configure Maven to run with the mainsite, while the
rest needs to be committed manually (using extpath)
Here is some sample configuration of maven:
http://apache.org/dev/cmsadoption.html
Unfortunately I will not find time the next we
Did you run some maven build to fill the actual content in the svn space
to publish?
Someone might correct me if I'm wrong, but would we would need to do now
is to change site-pom to use maven-scm-publish plugin for distribution
management and run the site build to publish something - right?
See
Ermhhh ... yes, I think I would share this opinion :)
Actually it looks pretty much like what I expected from my understanding
of the process Joe implied...
Christian?
Have to run, more time this evening
- René
Am 17.01.13 08:08, schrieb Lukasz Lenart:
> The site was migrated to SvnSubPub but d
The site was migrated to SvnSubPub but doesn't look good right now :P
http://struts.staging.apache.org/
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2012/12/16 Rene Gielen :
>
> Am 16.12.12 14:21, schrieb Christian Grobmeier:
>> On Sun, Dec 16, 2012 at 12:41 PM, Rene Gielen wr
Am 16.12.12 14:21, schrieb Christian Grobmeier:
> On Sun, Dec 16, 2012 at 12:41 PM, Rene Gielen wrote:
> [...]
>> If I understand this right, we have two options to deal with our "main
>> site", which is basically everything on s.a.o excluding the confluence
>> exports:
>> - move to CMS
>> - main
On Sun, Dec 16, 2012 at 12:41 PM, Rene Gielen wrote:
>> Do we vote on the website if we release a new version?
>>
> We do not vote in general about our website changes. For changes induced
> by project releases, the release manager usually takes the plunge to
> update the site. We trust our commit
Am 15.12.12 09:12, schrieb Christian Grobmeier:
> Hi all,
>
> I just created the Infra issue:
> https://issues.apache.org/jira/browse/INFRA-5659
>
> Before I have asked on the infra list if the plan using "mvn site" for
> the main site and committing the subsites manually would work. It
> seems
See inline ...
Am 10.12.12 10:14, schrieb Christian Grobmeier:
> On Mon, Dec 10, 2012 at 9:45 AM, Lukasz Lenart wrote:
>
>> 2012/12/10 Christian Grobmeier :
>>> we are listed as project using an page publishing system which will stop
>>> working in 3 weeks. I never saw a cms discussion here... di
Hi all,
I just created the Infra issue:
https://issues.apache.org/jira/browse/INFRA-5659
Before I have asked on the infra list if the plan using "mvn site" for
the main site and committing the subsites manually would work. It
seems it does, so I pushed it now.
Cheers
Christian
On Wed, Dec 12,
2012/12/10 Christian Grobmeier :
> Looking at our main site, I would say there is an option to use the
> CMS for it. With your (Lukasz) CMS snippet it should be easy to update
> it. But at the moment we were working on fluido and the use of maven.
> I didn't consider the svnpubsub.
>
> Here is the
On Mon, Dec 10, 2012 at 11:38 AM, Lukasz Lenart wrote:
>> Do we vote on the website if we release a new version?
>
> It's always connected with a vote for release.
Ok, I just found this too:
http://struts.apache.org/downloads.html#PriorReleases
So we keep old versions of the site.
>> - request
I've developed a tiny Chrome extension to add instead Scriplet a small
button to edit pages with ASF CMS ;-)
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.o
2012/12/10 Christian Grobmeier :
> Confluence as a wiki is untouched, its just not possible to use it as "main
> site", whatever it means. The requirement is that we store our website
> somewhere in an svn tree.
Anyway will have to adjust our release process as we deploy exported
docs as a part of
On Mon, Dec 10, 2012 at 10:14 AM, Maurizio Cucchiara
wrote:
>
> I might be also interesting to know if, on January 1st:
> * it will not be possible to update the site (we could wait for the next
> release)
> * or the current website will be no more visible.
>
I don't know. But it does not sound l
I might be also interesting to know if, on January 1st:
* it will not be possible to update the site (we could wait for the next
release)
* or the current website will be no more visible.
Twitter :http://www.twitter.com/m_cucchiara
G+ :https://plus.google.com/107903711540963855921
Lin
On Mon, Dec 10, 2012 at 9:45 AM, Lukasz Lenart wrote:
> 2012/12/10 Christian Grobmeier :
> > we are listed as project using an page publishing system which will stop
> > working in 3 weeks. I never saw a cms discussion here... did i miss it?
> we
> > need to act pretty quickly. I am far from an ex
Lukasz,
> I'm not sure if I understand that correctly - do we have to move the
> whole documentation from Confluence as well ?
I'm afraid we'll have to do it, take a look at [1]
> Or is it just related to
> the site ? But what about our release process... confused :\
>
> I guess we should change
2012/12/10 Christian Grobmeier :
> we are listed as project using an page publishing system which will stop
> working in 3 weeks. I never saw a cms discussion here... did i miss it? we
> need to act pretty quickly. I am far from an expert in that area but have
> helped with logging migration and mi
On Mon, Dec 10, 2012 at 9:03 AM, Christian Grobmeier wrote:
> Folks,
>
> we are listed as project using an page publishing system which will stop
> working in 3 weeks. I never saw a cms discussion here... did i miss it? we
> need to act pretty quickly. I am far from an expert in that area but have
Folks,
we are listed as project using an page publishing system which will stop
working in 3 weeks. I never saw a cms discussion here... did i miss it? we
need to act pretty quickly. I am far from an expert in that area but have
helped with logging migration and might be able to add a few cents if
35 matches
Mail list logo
