It appears that jira related messages are not archived in the same
manner
as user-posts to river-dev, so my reply to the "[jira] Created ..."
message
was the wrong approach to sending out the included message.
Therefore, I'm
going to repost the message under a new subject, so please respond to
that
repost instead of the initial posting.
Frank
On Sep 19, 2007, at 12:46 PM, Frank Barnaby wrote:
As many of you are aware, the ServiceUI source tree includes the
following files:
LICENSE
NOTICE
COPYRIGHT
A decision needs to be made with regard to the fate of these files.
Jim Hurley
and I feel that this aspect of this JIRA issue is important enough
to involve
the community.
First, dealing with the LICENSE file is simple. It's identical to
the one in
the JTSK tree, so this copy can be excluded from the migration.
Second, the NOTICE file contains text that I believe must be
included in the
JTSK's NOTICE file. Here's the existing text of ServiceUI's NOTICE
file:
The ServiceUI API
Copyright 2007 The Apache Software Foundation
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
Portions of this software were developed by Bill Venners of
Artima, Inc., who
led the ServiceUI project. The ServiceUI project, which was hosted
at jini.org,
was tasked with defining a "standard" approach to attaching UIs to
Jini services.
The ServiceUI specification and API represent the best
amalgamation of the ideas
contributed by all the people who participated in the serviceui
project.
The original two releases of the ServiceUI API, including
specifications
and code, are available from:
http://www.artima.com/jini/serviceui/index.html
I believe the first line should be excluded because the JTSK's
NOTICE file applies
to the entire River distribution. The 2nd-4th lines already exist
in the JTSK's
NOTICE file, so those lines can be excluded. The remaining portion
of the file
should be carried forward to the JTSK's NOTICE file, resulting in
the following
combined text:
Apache River
Copyright 2007 The Apache Software Foundation
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
| Portions of this software were developed by Bill Venners of
Artima, Inc., who
| led the ServiceUI project. The ServiceUI project, which was
hosted at jini.org,
| was tasked with defining a "standard" approach to attaching UIs
to Jini services.
| The ServiceUI specification and API represent the best
amalgamation of the ideas
| contributed by all the people who participated in the serviceui
project.
|
| The original two releases of the ServiceUI API, including
specifications
| and code, are available from:
|
| http://www.artima.com/jini/serviceui/index.html
Copyright 2005 Sun Microsystems, Inc.
This product includes material developed by Sun Microsystems, Inc.
(http://www.sun.com).
Copyright 2002-2005 Geoffrey Arnold (http://www.geoffreyarnold.com)
This product contains code derived from the Ant build script
contributed
to the Jini Community by Geoffrey Arnold (http://
www.geoffreyarnold.com).
Lastly, the COPYRIGHT file contains the following text:
The following copyright notice was affixed to portions of the
code with which this file is now or was at one time distributed and
is placed here unaltered.
Copyright 2000-2005 Artima Software, Inc.
Jim and I agree that the Copyright line should be appended to the
JTSK's NOTICE
file, but the COPYRIGHT file and its remaining text should be
excluded from the
migration.
Please respond if you have any concerns regarding this proposal.
Frank
On Sep 14, 2007, at 11:39 AM, Jim Hurley (JIRA) wrote:
integrate serviceui sources into jtsk trunk
-------------------------------------------
Key: RIVER-264
URL: https://issues.apache.org/jira/browse/RIVER-264
Project: River
Issue Type: Task
Components: build
Affects Versions: jtsk_2.1
Reporter: Jim Hurley
Assignee: Frank Barnaby
Priority: Minor
Fix For: AR1
move the ServiceUI classes directly into the jtsk tree. Include
in both
jsk-lib.jar and jsk-dl.jar, and (at least temporarily for
convenience for
those using it) keep a serviceui.jar.
Basically:
* integrate serviceui sources into jtsk trunk
* create build target for serviceui.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
