[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [tigerstripe-dev] TIP Meeting report
|
Title: Re: [tigerstripe-dev] TIP Meeting report
We are talking crossed purposes here..
We have the feature you describe for the GENERATED files -
but these messages below are in the "internal" tigerstripe .java files - that
contain the ManagedEntity, Datatype definitions...
I think you are right. I would expect the open source
generators to not include a copyright statement in the generated artifacts...
but maybe have a property to set one.
Within Cisco, for instance, we would want to include
a Cisco copyright statement on *our* generated artifacts.
Steve
Steve,
thanks for this.
There is still one area where I think we are
confused/confusing...
The .java files that we use to store the artifacts has
this as a header:
/*******************************************************************************
* Created with
Tigerstripe(tm) Workbench v.0.4.5.qualifier
* Copyright (c) 2007
Cisco Systems, Inc.
* All rights reserved. This
program and the accompanying materials
* are made available under
the terms of the Eclipse Public License v1.0
* which accompanies this
distribution, and is available at
*
http://www.eclipse.org/legal/epl-v10.html
*
* DO NOT EDIT THIS FILE -
Created with Tigerstripe(tm) Workbench
*
*******************************************************************************/
This
seems wrong to me, as the content is what the user has generated, admittedly by
using our "program", but I fail to see how we need a copyright statement in
there.
Am I
missing something? I guess we might claim copyright of the format - but for a
.java file that seems unlikely as well!
Richard
So, Richard.
I can answer the license and copyright issues (with the
proviso that I am not a lawyer...)..
So for each file, there is an author. That author (in
this case Cisco) owns the copyright for the file. If others also
author changes to the file then they get to add there name to the list of
copyright owners...
License to use is a separate issue and is covered by
the Eclipse Public License. There are two documents:
Steve
HI Richard and all,
Thanks for the update.
A
quick note on the bugs reported below:
- Can't DnD from a module
onto a diagram. - Bug 259165, fixed. Will be in next 0.4.5 build.
- Can't open the
Tigerstripe.xml in a Module – Bug 259150, fixed. Will be in next 0.4.5
build.
- When exporting a module,
you can check a box to include the annotations, but when browsing the
artifacts, the annotations are not shown against the artifacts.
Investigating
- M0 generators have no name
when deployed. Investigating.
Eric
On 12/17/08 8:59 AM,
"Richard Craddock (rcraddoc)" <rcraddoc@xxxxxxxxx>
wrote:
All,
notes
from a meeting I held today with Craig and Tapelo from the TIP Implementation
team,
We will
probably look to meet up again some time in the new year.
(Let me
know if I got any of this wrong!)
Richard
Progress
Tapelo
and Craig have made some good progress in putting together a build process
based around Tigerstripe. They have a series of Maven projects to generate
hibernate configs from a model project, and then to create the db and run some
tests (among other things). They are working on packaging to be able to
produce maven consumable jars as the output from the whole process. I am
impressed with the progress they have made so far, and confident that they
will continue to make god progress.
They are
not using the Tigerstripe Maven plugin because they could not quite get it to
do what they wanted. They have some questions about running/deploying
generators from the command line. I requested that they raise any issues with
the Maven plugin on the mailing list, and contribute back any improved
versions that they come up with. I suggest Jim be involved here as he is the
man for this kind of stuff :-)
Discussion items / Questions
1.
Command Line/build
How to
deploy plugins from command line?
How to deploy
profiles from command line?
In the
tutorial example, there are these line
:
REM Use below to define
referenced
projects
REM set
REFERENCE_ONE=
PROJECT_IMPORT=%WORKSPACE%\ReferencedProjectOne
REM
set REFERENCE_TWO=
PROJECT_IMPORT=%WORKSPACE%\ReferencedProjectTwo
What do they mean - is there
anything specific required to handle referenced project? Why do they not just
get picked up?
Generally the tutorial pages for this
area need to be updated....
2.
Use of Modules for "common" resources
I demonstrated the use of modules ( saw some bugs
on 0.4.5 - see below)
Some
observations
Diagrams do
not get packed up in the module - this would be very useful.
3.
Profiles & Stereotypes
This was generally a demonstration/discussion of
what is possible - no real Issues
4.
Annotations
A quick demo again - something for
"later".
Can you put
Annotations on instances?
5.
M0 Generators
We recognised that
I didn't know much about this :-)
Tapelo would like
to use Instance Diagrams to capture data for test cases. However you can only
run an M0 generate from the diagram "context". Is it possible to do this so
that we effectively run the M0 generator for all diagrams - using the diagram
name for scoping if necessary?
Other
issues:
The export-xml schema doesn't seem to have
any info about references or modules - this would be useful, so that a
project pattern could determine that a module is required (would be even
better if the module could also be added, but that is more
complex!)
The licensing issue of eclipse needs to
explained to the TMF user community.
On that
note, the copyright statement in the header of artifact files references
Cisco, and the eclipse licence. Is that actually correct? It is misleading as
it implies that the content is Copyright Cisco.
I highlighted to Craig/Tapelo that they should
raise any questions or bugs through formal channels so that we can capture and
work on them. This includes outdated/unclear tutorials &
documentation.
Bugs To raise/review (these are against the 0.4.5 version in my WS,
so need to check that are valid for the proper build!)
1. Can't
DnD from a module onto a diagram.
2. Can't open the Tigerstripe.xml in a
Module
3. When exporting a module, you can check a box to include the
annotations, but when browsing the artifacts, the annotations are not shown
against the artifacts.
4. M0 generators have no name when deployed.
Bug
221560 would be very useful (Schema for tigerstripe.xml)
"This e-mail may contain confidential and privileged material for
the sole use of the intended recipient. Any review, use, distribution or
disclosure by others is strictly prohibited. If you are not the intended
recipient (or authorized to receive for the recipient), please contact the
sender by reply e-mail and delete all copies of this message."
"Cisco
Systems Limited (Company Number: 02558939), is registered in England and Wales
with its registered office at 1 Callaghan Square, Cardiff, South Glamorgan
CF10 5BT"
_______________________________________________
tigerstripe-dev
mailing list
tigerstripe-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tigerstripe-dev