On Mon, 2003-10-06 at 13:00, Craig Walls wrote:
> > Was there a JIRA issue for it? It's just that if there isn't, there
> > won't be anything about it in the Change Log
> > (http://opensource.atlassian.com/projects/xdoclet/secure/BrowsePro
> > ject.jspa?id=1&report=changelog) for the final rel
> Was there a JIRA issue for it? It's just that if there isn't, there
> won't be anything about it in the Change Log
> (http://opensource.atlassian.com/projects/xdoclet/secure/BrowsePro
> ject.jspa?id=1&report=changelog) for the final release...
>
No, there wasn't a JIRA issue for it...I just
On Sat, 2003-10-04 at 22:55, Craig Walls wrote:
> For those who haven't noticed, a few weeks ago, I checked in a
> JSR-168/Portlet module in to generate JSR-168 compliant portlet.xml files.
Was there a JIRA issue for it? It's just that if there isn't, there
won't be anything about it in the Chang
For those who haven't noticed, a few weeks ago, I checked in a
JSR-168/Portlet module in to generate JSR-168 compliant portlet.xml files.
I've waited until today to announce it because I have been waiting to see
how the JSR-168 spec shapes up. On Monday, the JCP will likely vote it in as
final an
