geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Kirby (JIRA)" <>
Subject [jira] Commented: (GERONIMODEVTOOLS-518) Update GEP code with new Devtools URL
Date Sat, 20 Sep 2008 00:27:44 GMT


Ted Kirby commented on GERONIMODEVTOOLS-518:

I put work into
to make it a generic devtools subproject page.  However, it is still a wiki page, with no
left nav bar, or news on the bottom.

Tim, Ashish and I discussed doc issues in GERONIMODEVTOOLS-461.  We went to a wiki page because
it was easier to edit.

I didn't know how to change before. 

I know how to do that now. :-)

So, I'll change  into a generic page, and
move it's child pages in GMOxSITE to GMOxDOC20, where I think they belong.  They are now old
pages that describe how to use GEP 2.0.0.  Turning
 into a generic page will essentially fix the JIRA, as well as keep all previous releases

In terms of moving to GMOxDOC20, maybe Devtools should get its own wiki space.

It seems we have maybe 10 pages.  The pre-reqs and install page will change for each release,
but the other pages may be longer lived.

That directory page gives too much press to subprojects, I think.  We don't need big buttons
at the top of our main page for them.  But, they probably deserve more attention than links
at the bottom of the left nav bar...  I agree Samples and Devtools are important.  It is how
users/developers can start using the server quickly!  We should probably get more links, info
and press at the top of our page to get folks started.

> Update GEP code with new Devtools URL
> -------------------------------------
>                 Key: GERONIMODEVTOOLS-518
>                 URL:
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>    Affects Versions: 2.1.3, 2.2.0
>            Reporter: Ted Kirby
>            Assignee: Ted Kirby
>             Fix For: 2.2.0
> Recently, the devtools sub-project homepage was changed from
> I have just found some references in the code to the old page that need to be updated.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message