[JBoss JIRA] Created: (JBIDE-6292) Teiid Designer Update site does not include third party requirements like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
4:42 p.m.
Teiid Designer Update site does not include third party requirements like
http://mvnrepository.com/artifact/net.jcip/jcip-annotations
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-6292
URL: https://jira.jboss.org/jira/browse/JBIDE-6292
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Reporter: Nick Boldt
Assignee: Barry LaFond
Various solutions are possible...
a) don't use them
b) find an update site where that's published and tell p2 (via metadata) how to find
that associate site (like JBT does for m2eclipse, birt2.5, etc.)
c) create a new "third party stuff" feature (or add this/these plugins to an
existing feature) so that the generated site will include them; as such you'll be
**REDISTRIBUTING** them, so be aware of license limitations with doing so
----
if (a)... my work is done.
if (b)... well, the burden of license acceptance is on someone else and not on us... but I
still need to write some code to make the site aggregate the new metadata. Prolly require
Buckminster aggregator
if (c), you need to ensure that the license text in that feature is VERY CLEAR about which
license(s) must be accepted when installing the feature (since they won't all be EPL,
I'm guessing)
---
Frankly, from a simplicity POV, I prefer (c), but ONLY if the license(s) are compatible
and you and PM are cool with that.
Second choice would be (b), as it's more work for me. This only works if there's a
site available (or we create one).
Failing that, I like (a), but that's more work for the Teiid devs -- requiring them to
implement using a different library.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:07 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6292) Teiid Designer Update site does not include third party requirements like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
[
https://jira.jboss.org/browse/JBIDE-6292?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen commented on JBIDE-6292:
--------------------------------------------
is this package an osgi plugin or a simple jar included like many other things or ?
Teiid Designer Update site does not include third party requirements
like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-6292
URL: https://jira.jboss.org/browse/JBIDE-6292
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Reporter: Nick Boldt
Assignee: Barry LaFond
Various solutions are possible...
a) don't use them
b) find an update site where that's published and tell p2 (via metadata) how to find
that associate site (like JBT does for m2eclipse, birt2.5, etc.)
c) create a new "third party stuff" feature (or add this/these plugins to an
existing feature) so that the generated site will include them; as such you'll be
**REDISTRIBUTING** them, so be aware of license limitations with doing so
----
if (a)... my work is done.
if (b)... well, the burden of license acceptance is on someone else and not on us... but
I still need to write some code to make the site aggregate the new metadata. Prolly
require Buckminster aggregator
if (c), you need to ensure that the license text in that feature is VERY CLEAR about
which license(s) must be accepted when installing the feature (since they won't all be
EPL, I'm guessing)
---
Frankly, from a simplicity POV, I prefer (c), but ONLY if the license(s) are compatible
and you and PM are cool with that.
Second choice would be (b), as it's more work for me. This only works if there's
a site available (or we create one).
Failing that, I like (a), but that's more work for the Teiid devs -- requiring them
to implement using a different library.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:36 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6292) Teiid Designer Update site does not include third party requirements like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
[
https://jira.jboss.org/browse/JBIDE-6292?page=com.atlassian.jira.plugin.s...
]
John Verhaeg commented on JBIDE-6292:
-------------------------------------
Yes :-) It's available publicly as a simple jar, but we packaged it within an OSGI
plug-in so any of our projects can make use of it. The jar just offers informational
concurrency-related tags for marking code as immutable, threadsafe, etc. It's
doesn't affect the application in any way, but it's very useful for ensuring our
code adheres to what concurrency policy was initially setup for particular classes.
We'll go after c) first and investigate the license, and if that fails, we'll
probably just opt for a).
Teiid Designer Update site does not include third party requirements
like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-6292
URL: https://jira.jboss.org/browse/JBIDE-6292
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Reporter: Nick Boldt
Assignee: Barry LaFond
Various solutions are possible...
a) don't use them
b) find an update site where that's published and tell p2 (via metadata) how to find
that associate site (like JBT does for m2eclipse, birt2.5, etc.)
c) create a new "third party stuff" feature (or add this/these plugins to an
existing feature) so that the generated site will include them; as such you'll be
**REDISTRIBUTING** them, so be aware of license limitations with doing so
----
if (a)... my work is done.
if (b)... well, the burden of license acceptance is on someone else and not on us... but
I still need to write some code to make the site aggregate the new metadata. Prolly
require Buckminster aggregator
if (c), you need to ensure that the license text in that feature is VERY CLEAR about
which license(s) must be accepted when installing the feature (since they won't all be
EPL, I'm guessing)
---
Frankly, from a simplicity POV, I prefer (c), but ONLY if the license(s) are compatible
and you and PM are cool with that.
Second choice would be (b), as it's more work for me. This only works if there's
a site available (or we create one).
Failing that, I like (a), but that's more work for the Teiid devs -- requiring them
to implement using a different library.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:17 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6292) Teiid Designer Update site does not include third party requirements like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
[
https://jira.jboss.org/browse/JBIDE-6292?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-6292:
-----------------------------------
I have temporarily added the jcip.annotations plugin to both teiid features. This solves
the p2 installation problem, but does not address the licensing issue.
As such, you may still want to go with option (c) - create a new feature to house this
plugin and make it available on the update site.
Let me know when you've created the new feature, and I can assist in wiring up the
update site if needed (just add the new feature ID to the site/site.xml file). You'll
also want to make sure the new feature is added to the features/pom.xml and that
there's a pom.xml in the root of the new feature itself.
Teiid Designer Update site does not include third party requirements
like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-6292
URL: https://jira.jboss.org/browse/JBIDE-6292
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Reporter: Nick Boldt
Assignee: Barry LaFond
Various solutions are possible...
a) don't use them
b) find an update site where that's published and tell p2 (via metadata) how to find
that associate site (like JBT does for m2eclipse, birt2.5, etc.)
c) create a new "third party stuff" feature (or add this/these plugins to an
existing feature) so that the generated site will include them; as such you'll be
**REDISTRIBUTING** them, so be aware of license limitations with doing so
----
if (a)... my work is done.
if (b)... well, the burden of license acceptance is on someone else and not on us... but
I still need to write some code to make the site aggregate the new metadata. Prolly
require Buckminster aggregator
if (c), you need to ensure that the license text in that feature is VERY CLEAR about
which license(s) must be accepted when installing the feature (since they won't all be
EPL, I'm guessing)
---
Frankly, from a simplicity POV, I prefer (c), but ONLY if the license(s) are compatible
and you and PM are cool with that.
Second choice would be (b), as it's more work for me. This only works if there's
a site available (or we create one).
Failing that, I like (a), but that's more work for the Teiid devs -- requiring them
to implement using a different library.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:46 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6292) Teiid Designer Update site does not include third party requirements like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
[
https://jira.jboss.org/browse/JBIDE-6292?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen updated JBIDE-6292:
---------------------------------------
Fix Version/s: 3.2.next
Priority: Critical (was: Major)
what is the resultant osgi package name for this package ?
How are we going to satisfy their "mention the souce" license ? is it enough to
mention it in the plugin license/description ?
Teiid Designer Update site does not include third party requirements
like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-6292
URL: https://jira.jboss.org/browse/JBIDE-6292
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Reporter: Nick Boldt
Assignee: Barry LaFond
Priority: Critical
Fix For: 3.2.next
Various solutions are possible...
a) don't use them
b) find an update site where that's published and tell p2 (via metadata) how to find
that associate site (like JBT does for m2eclipse, birt2.5, etc.)
c) create a new "third party stuff" feature (or add this/these plugins to an
existing feature) so that the generated site will include them; as such you'll be
**REDISTRIBUTING** them, so be aware of license limitations with doing so
----
if (a)... my work is done.
if (b)... well, the burden of license acceptance is on someone else and not on us... but
I still need to write some code to make the site aggregate the new metadata. Prolly
require Buckminster aggregator
if (c), you need to ensure that the license text in that feature is VERY CLEAR about
which license(s) must be accepted when installing the feature (since they won't all be
EPL, I'm guessing)
---
Frankly, from a simplicity POV, I prefer (c), but ONLY if the license(s) are compatible
and you and PM are cool with that.
Second choice would be (b), as it's more work for me. This only works if there's
a site available (or we create one).
Failing that, I like (a), but that's more work for the Teiid devs -- requiring them
to implement using a different library.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:46 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6292) Teiid Designer Update site does not include third party requirements like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
[
https://jira.jboss.org/browse/JBIDE-6292?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen commented on JBIDE-6292:
--------------------------------------------
reason I ask for the osgi package is to know if we are overlapping with net.jcip osgi
names or prefxing it with something to avoid collision or doubt about where the plugin is
actually from
Teiid Designer Update site does not include third party requirements
like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-6292
URL: https://jira.jboss.org/browse/JBIDE-6292
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Reporter: Nick Boldt
Assignee: Barry LaFond
Priority: Critical
Fix For: 3.2.next
Various solutions are possible...
a) don't use them
b) find an update site where that's published and tell p2 (via metadata) how to find
that associate site (like JBT does for m2eclipse, birt2.5, etc.)
c) create a new "third party stuff" feature (or add this/these plugins to an
existing feature) so that the generated site will include them; as such you'll be
**REDISTRIBUTING** them, so be aware of license limitations with doing so
----
if (a)... my work is done.
if (b)... well, the burden of license acceptance is on someone else and not on us... but
I still need to write some code to make the site aggregate the new metadata. Prolly
require Buckminster aggregator
if (c), you need to ensure that the license text in that feature is VERY CLEAR about
which license(s) must be accepted when installing the feature (since they won't all be
EPL, I'm guessing)
---
Frankly, from a simplicity POV, I prefer (c), but ONLY if the license(s) are compatible
and you and PM are cool with that.
Second choice would be (b), as it's more work for me. This only works if there's
a site available (or we create one).
Failing that, I like (a), but that's more work for the Teiid devs -- requiring them
to implement using a different library.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:37 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-6292) Teiid Designer Update site does not include third party requirements like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
[
https://jira.jboss.org/browse/JBIDE-6292?page=com.atlassian.jira.plugin.s...
]
John Verhaeg resolved JBIDE-6292.
---------------------------------
Assignee: John Verhaeg (was: Barry LaFond)
Resolution: Done
The Teiid Designer feature now includes the JCIP annotations plug-in and I've added
license file with copyright and reference to Creative Commons license.
Teiid Designer Update site does not include third party requirements
like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-6292
URL: https://jira.jboss.org/browse/JBIDE-6292
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Reporter: Nick Boldt
Assignee: John Verhaeg
Priority: Critical
Fix For: 3.2.next
Various solutions are possible...
a) don't use them
b) find an update site where that's published and tell p2 (via metadata) how to find
that associate site (like JBT does for m2eclipse, birt2.5, etc.)
c) create a new "third party stuff" feature (or add this/these plugins to an
existing feature) so that the generated site will include them; as such you'll be
**REDISTRIBUTING** them, so be aware of license limitations with doing so
----
if (a)... my work is done.
if (b)... well, the burden of license acceptance is on someone else and not on us... but
I still need to write some code to make the site aggregate the new metadata. Prolly
require Buckminster aggregator
if (c), you need to ensure that the license text in that feature is VERY CLEAR about
which license(s) must be accepted when installing the feature (since they won't all be
EPL, I'm guessing)
---
Frankly, from a simplicity POV, I prefer (c), but ONLY if the license(s) are compatible
and you and PM are cool with that.
Second choice would be (b), as it's more work for me. This only works if there's
a site available (or we create one).
Failing that, I like (a), but that's more work for the Teiid devs -- requiring them
to implement using a different library.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:39 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6292) Teiid Designer Update site does not include third party requirements like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
[
https://jira.jboss.org/browse/JBIDE-6292?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-6292:
-----------------------------------
You can see what we're producing using Tycho here:
http://download.jboss.org/jbosstools/builds/nightly/3.2.helios/
SNAPSHOT-named zips have the same contents as the timestamped/numbered ones, but by having
non-changing names allow me to grab the lastest from a well-known URL (like we did for the
last release for bpel, jbpm3/4, and pi4soa).
Teiid Designer Update site does not include third party requirements
like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-6292
URL: https://jira.jboss.org/browse/JBIDE-6292
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Reporter: Nick Boldt
Assignee: John Verhaeg
Priority: Critical
Fix For: 3.2.next
Various solutions are possible...
a) don't use them
b) find an update site where that's published and tell p2 (via metadata) how to find
that associate site (like JBT does for m2eclipse, birt2.5, etc.)
c) create a new "third party stuff" feature (or add this/these plugins to an
existing feature) so that the generated site will include them; as such you'll be
**REDISTRIBUTING** them, so be aware of license limitations with doing so
----
if (a)... my work is done.
if (b)... well, the burden of license acceptance is on someone else and not on us... but
I still need to write some code to make the site aggregate the new metadata. Prolly
require Buckminster aggregator
if (c), you need to ensure that the license text in that feature is VERY CLEAR about
which license(s) must be accepted when installing the feature (since they won't all be
EPL, I'm guessing)
---
Frankly, from a simplicity POV, I prefer (c), but ONLY if the license(s) are compatible
and you and PM are cool with that.
Second choice would be (b), as it's more work for me. This only works if there's
a site available (or we create one).
Failing that, I like (a), but that's more work for the Teiid devs -- requiring them
to implement using a different library.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:28 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6292) Teiid Designer Update site does not include third party requirements like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
[
https://jira.jboss.org/browse/JBIDE-6292?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen updated JBIDE-6292:
---------------------------------------
Fix Version/s: 3.2.0.M1
(was: 3.2.x)
Teiid Designer Update site does not include third party requirements
like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-6292
URL: https://jira.jboss.org/browse/JBIDE-6292
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Reporter: Nick Boldt
Assignee: John Verhaeg
Priority: Critical
Fix For: 3.2.0.M1
Various solutions are possible...
a) don't use them
b) find an update site where that's published and tell p2 (via metadata) how to find
that associate site (like JBT does for m2eclipse, birt2.5, etc.)
c) create a new "third party stuff" feature (or add this/these plugins to an
existing feature) so that the generated site will include them; as such you'll be
**REDISTRIBUTING** them, so be aware of license limitations with doing so
----
if (a)... my work is done.
if (b)... well, the burden of license acceptance is on someone else and not on us... but
I still need to write some code to make the site aggregate the new metadata. Prolly
require Buckminster aggregator
if (c), you need to ensure that the license text in that feature is VERY CLEAR about
which license(s) must be accepted when installing the feature (since they won't all be
EPL, I'm guessing)
---
Frankly, from a simplicity POV, I prefer (c), but ONLY if the license(s) are compatible
and you and PM are cool with that.
Second choice would be (b), as it's more work for me. This only works if there's
a site available (or we create one).
Failing that, I like (a), but that's more work for the Teiid devs -- requiring them
to implement using a different library.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:24 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-6292) Teiid Designer Update site does not include third party requirements like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
[
https://jira.jboss.org/browse/JBIDE-6292?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen resolved JBIDE-6292.
----------------------------------------
Resolution: Done
Teiid Designer Update site does not include third party requirements
like http://mvnrepository.com/artifact/net.jcip/jcip-annotations
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-6292
URL: https://jira.jboss.org/browse/JBIDE-6292
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Reporter: Nick Boldt
Assignee: John Verhaeg
Priority: Critical
Fix For: 3.2.0.M1
Various solutions are possible...
a) don't use them
b) find an update site where that's published and tell p2 (via metadata) how to find
that associate site (like JBT does for m2eclipse, birt2.5, etc.)
c) create a new "third party stuff" feature (or add this/these plugins to an
existing feature) so that the generated site will include them; as such you'll be
**REDISTRIBUTING** them, so be aware of license limitations with doing so
----
if (a)... my work is done.
if (b)... well, the burden of license acceptance is on someone else and not on us... but
I still need to write some code to make the site aggregate the new metadata. Prolly
require Buckminster aggregator
if (c), you need to ensure that the license text in that feature is VERY CLEAR about
which license(s) must be accepted when installing the feature (since they won't all be
EPL, I'm guessing)
---
Frankly, from a simplicity POV, I prefer (c), but ONLY if the license(s) are compatible
and you and PM are cool with that.
Second choice would be (b), as it's more work for me. This only works if there's
a site available (or we create one).
Failing that, I like (a), but that's more work for the Teiid devs -- requiring them
to implement using a different library.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5261
days inactive
5292
days old
jbosstools-issues@lists.jboss.org
9 comments
3 participants
participants (3)
-
John Verhaeg (JIRA) -
Max Rydahl Andersen (JIRA)
-
Nick Boldt (JIRA)