You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Mladen Turk <mt...@apache.org> on 2009/11/25 10:52:27 UTC
Publishing sandbox project
Hi,
I'd like to list the sandbox/runtime on the main commons page.
What's needed for that (given that I have xdocs directory and
index.xml in there)
IMHO the project-template should include the skeleton
index.xml and sample resources (if that's how it's done)
If anyone can explain how to create and publish that, I'd
be happy to update the project-template.
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Publishing sandbox project
Posted by Phil Steitz <ph...@gmail.com>.
Mladen Turk wrote:
> On 11/26/2009 03:48 AM, Niall Pemberton wrote:
>>
>> I re-enabled the site and generated an issue tracking page and
>> re-deployed the site:
>>
>> http://commons.apache.org/sandbox/runtime/
>>
>> Niall
>>> Phil
>
> Thanks guys. Much appreciated!
>
> I suppose I can just copy the ant produced javadocs to
> target/apidocs before doing mvn site:deploy which should
> be just fine for the moment.
>
Yes, that should work. You can also just scp them manually to
p.a.o:/www/commons.apache.org/sandbox/runtime/apidocs
If you do the latter, remember to make the files group writable.
Phil
>
> Cheers
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Publishing sandbox project
Posted by Mladen Turk <mt...@apache.org>.
On 11/26/2009 03:48 AM, Niall Pemberton wrote:
>
> I re-enabled the site and generated an issue tracking page and
> re-deployed the site:
>
> http://commons.apache.org/sandbox/runtime/
>
> Niall
>> Phil
Thanks guys. Much appreciated!
I suppose I can just copy the ant produced javadocs to
target/apidocs before doing mvn site:deploy which should
be just fine for the moment.
Cheers
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Publishing sandbox project
Posted by Niall Pemberton <ni...@gmail.com>.
On Wed, Nov 25, 2009 at 11:09 PM, Phil Steitz <ph...@gmail.com> wrote:
> Niall Pemberton wrote:
>> On Wed, Nov 25, 2009 at 10:55 PM, Mladen Turk <mt...@apache.org> wrote:
>>> On 11/25/2009 10:26 PM, Phil Steitz wrote:
>>>> Done now. The site is up at http://commons.apache.org/sandbox/runtime/
>>>> and the main commons site menus and component table have been
>>>> updated (will take an hour or so to replicate).
>>>>
>>> Excellent. Many thanks.
>>
>> Currently the build is set up to NOT compile the java classes - is this correct?
>
> Ant is the build tool and the maven compile was failing, so I
> disabled the maven build. The one negative consequence of this is
> that javadoc is not generated, so this needs to be uploaded directly
> to the location pointed to by the (currently broken) link on the
> menu, unless we want to maintain a working maven code build.
https://issues.apache.org/jira/browse/SANDBOX-317
>> Also the site isn't generating the standard bug/svn/mailing list etc
>> type pages - I'm going to try and fix that.
>
> Ugh. I did not realize those links were broken. Turning report
> generation back on will probably fix that, but then we get all of
> the other reports specified in the parent pom. Would be great if we
> could disable selectively, but I do not know how to do that.
> Personally, I have never liked having reports in the parent pom for
> exactly this reason.
I re-enabled the site and generated an issue tracking page and
re-deployed the site:
http://commons.apache.org/sandbox/runtime/
Niall
> Phil
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Publishing sandbox project
Posted by Phil Steitz <ph...@gmail.com>.
Niall Pemberton wrote:
> On Wed, Nov 25, 2009 at 10:55 PM, Mladen Turk <mt...@apache.org> wrote:
>> On 11/25/2009 10:26 PM, Phil Steitz wrote:
>>> Done now. The site is up at http://commons.apache.org/sandbox/runtime/
>>> and the main commons site menus and component table have been
>>> updated (will take an hour or so to replicate).
>>>
>> Excellent. Many thanks.
>
> Currently the build is set up to NOT compile the java classes - is this correct?
Ant is the build tool and the maven compile was failing, so I
disabled the maven build. The one negative consequence of this is
that javadoc is not generated, so this needs to be uploaded directly
to the location pointed to by the (currently broken) link on the
menu, unless we want to maintain a working maven code build.
>
> Also the site isn't generating the standard bug/svn/mailing list etc
> type pages - I'm going to try and fix that.
Ugh. I did not realize those links were broken. Turning report
generation back on will probably fix that, but then we get all of
the other reports specified in the parent pom. Would be great if we
could disable selectively, but I do not know how to do that.
Personally, I have never liked having reports in the parent pom for
exactly this reason.
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Publishing sandbox project
Posted by Niall Pemberton <ni...@gmail.com>.
On Wed, Nov 25, 2009 at 10:55 PM, Mladen Turk <mt...@apache.org> wrote:
> On 11/25/2009 10:26 PM, Phil Steitz wrote:
>>>
>> Done now. The site is up at http://commons.apache.org/sandbox/runtime/
>> and the main commons site menus and component table have been
>> updated (will take an hour or so to replicate).
>>
>
> Excellent. Many thanks.
Currently the build is set up to NOT compile the java classes - is this correct?
Also the site isn't generating the standard bug/svn/mailing list etc
type pages - I'm going to try and fix that.
Niall
>>
>> Sorry the template was misleading and out of date.
>>
>
> NP. I'm currently in the usual maven problem:
> You have to download the entire internet before you can
> do anything with it :)
>
>
> Cheers
> --
> ^TM
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Publishing sandbox project
Posted by Mladen Turk <mt...@apache.org>.
On 11/25/2009 10:26 PM, Phil Steitz wrote:
>>
> Done now. The site is up at http://commons.apache.org/sandbox/runtime/
> and the main commons site menus and component table have been
> updated (will take an hour or so to replicate).
>
Excellent. Many thanks.
>
> Sorry the template was misleading and out of date.
>
NP. I'm currently in the usual maven problem:
You have to download the entire internet before you can
do anything with it :)
Cheers
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Publishing sandbox project
Posted by Phil Steitz <ph...@gmail.com>.
Mladen Turk wrote:
> On 11/25/2009 06:42 PM, Phil Steitz wrote:
>>
>> Would you be OK with maven 2 to build the runtime site?
>
> I really don't care. If maven2 is required, fine with me.
>
>>
>> I can set this up for you, but to maintain it you will need maven 2.
>>
>
> That would be perfect.
>
Done now. The site is up at http://commons.apache.org/sandbox/runtime/
and the main commons site menus and component table have been
updated (will take an hour or so to replicate).
To update the site, do "mvn site" (need maven 2 set up), look at it
and then "mvn site:deploy". Nav links for the site are in site.xml,
content comes from xdocs. I had to cut out the trademark entity
refs because m2 choked on them for some reason.
If you have trouble updating, just check in the xdocs and ping.
Sorry the template was misleading and out of date.
Phil
>
> Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Publishing sandbox project
Posted by Mladen Turk <mt...@apache.org>.
On 11/25/2009 06:42 PM, Phil Steitz wrote:
>
> Would you be OK with maven 2 to build the runtime site?
I really don't care. If maven2 is required, fine with me.
>
> I can set this up for you, but to maintain it you will need maven 2.
>
That would be perfect.
Thanks
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Publishing sandbox project
Posted by Phil Steitz <ph...@gmail.com>.
Mladen Turk wrote:
> On 11/25/2009 04:02 PM, Phil Steitz wrote:
>>
>> Looks like [runtime] has a Maven 1 build.
>
> It doesn't. Those are generated files.
> Build system will use ant with Runtime's own
> ant extensions for making custom .jar files
> containing both Java and Native components.
>
>>
>> Let me know if you have problems, do not have Maven 1, etc. and I
>> can take care of it.
>>
>
> I'd appreciate if you could make the needed
> changes to maven so I can use maven 1.1 for
> further uploads.
Would you be OK with maven 2 to build the runtime site? We have
working ways to get commons sites generated and deployed using maven
1.0.4 and maven 2 (preferred), but IIRC there are problems with 1.1.
>
> The site root is inside runtime/trunk/xdocs
> I suppose the site.xml is needed as well?
That is needed for a maven 2 site. You can copy the POM and overall
setup for maven 2 from, say nabla. Site inheritance will take care
of the commons menus, etc. for you that way.
I can set this up for you, but to maintain it you will need maven 2.
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Publishing sandbox project
Posted by Mladen Turk <mt...@apache.org>.
On 11/25/2009 04:02 PM, Phil Steitz wrote:
>
> Looks like [runtime] has a Maven 1 build.
It doesn't. Those are generated files.
Build system will use ant with Runtime's own
ant extensions for making custom .jar files
containing both Java and Native components.
>
> Let me know if you have problems, do not have Maven 1, etc. and I
> can take care of it.
>
I'd appreciate if you could make the needed
changes to maven so I can use maven 1.1 for
further uploads.
The site root is inside runtime/trunk/xdocs
I suppose the site.xml is needed as well?
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Publishing sandbox project
Posted by Phil Steitz <ph...@gmail.com>.
Mladen Turk wrote:
> Hi,
>
> I'd like to list the sandbox/runtime on the main commons page.
> What's needed for that (given that I have xdocs directory and
> index.xml in there)
>
> IMHO the project-template should include the skeleton
> index.xml and sample resources (if that's how it's done)
>
> If anyone can explain how to create and publish that, I'd
> be happy to update the project-template.
>
Looks like [runtime] has a Maven 1 build. The first thing to do is
to generate and deploy a site for [runtime]. Assuming you have Maven
1 set up and you can build the site using "maven site:generate",
then you should be able to deploy it using
maven -Dmaven.username=yourapacheid site:deploy
Alternatively, you could take this opportunity to convert the site
to Maven 2 by adding a POM.
Next, get it linked on the main commons site. Here ye olde Maven 1
is still the only option (do I hear anyone volunteering to convert
to M2?) The steps are
1) Check out commons/proper/commons-build/trunk
2) update parts/sandbox-table.ent
3) update menus/sandbox-items.ent
4) maven site:generate (look at the menus and sandbox components to
verify)
5) maven -Dmaven.username=yourapacheid site:deploy
Let me know if you have problems, do not have Maven 1, etc. and I
can take care of it.
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Publishing sandbox project
Posted by Rahul Akolkar <ra...@gmail.com>.
On Wed, Nov 25, 2009 at 4:52 AM, Mladen Turk <mt...@apache.org> wrote:
> Hi,
>
> I'd like to list the sandbox/runtime on the main commons page.
> What's needed for that (given that I have xdocs directory and
> index.xml in there)
>
<snip/>
Its slightly arcane, I'm afraid. Brief pointers below (I'm in a rush),
feel free to follow-up on bits that need more info. The much-followed
recipe here is:
* Build the runtime site using maven2 and deploy to:
http://commons.apache.org/sandbox/runtime/
* Update the menus, sandbox components table in the main Commons site
using maven1 (1.0.4 is known to work) and redeploy it -- main site
sources are here:
http://svn.apache.org/repos/asf/commons/proper/commons-build/trunk/
-Rahul
> IMHO the project-template should include the skeleton
> index.xml and sample resources (if that's how it's done)
>
> If anyone can explain how to create and publish that, I'd
> be happy to update the project-template.
>
>
> Regards
> --
> ^TM
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org