About using 3rd party code in JBoss Tools
by Max Rydahl Andersen
Hi,
Since we've had a few recent questions/incidents concerning usage of 3rd party code in JBoss Tools i'm sending out this again ;)
Remember it all depends on the license of the thing you are copying from and what you
are copying it to. The rules are hard to summarize, but as a general rule we should do:
1. ALWAYS look at the license of where you are copying from and see if it is compatible with the license the relevant plugin is under, if in doubt raise the question on jbosstools dev.
2. (required) Copied code must contain original comment with links to license or html/text file with license text.
3. If you are using EPL code in a LGPL project (the plugins from before Exadel is still LGPL, e.g. hibernate tools) you should
put the code in a directory named .xpl in the end and this code is not allowed to call back to the LGPL project (the EPL code must be independent)
In general Mozilla, ASL is ok to use as long as #2 is obeyed above.
CPL, EPL and LGPL is fine as long as we obey #2 and #3 above.
GPL is not possible to use directly from our plugins because of the virality of GPL.
BSD can be used directly.
..but do remember, if in doubt raise it at jbosstools dev.
Thus anything outside ASL, CPL, EPL and LGPL or in doubt -> raise it on jbosstools dev!
--
/max
13 years, 10 months
N&N deadline is wednesday
by Max Rydahl Andersen
Hi,
A good set of N&N are already in, but some are still outstanding - deadline for those is Wednesday so I
have time to cleanup and merge them all before the actual release.
Outstanding ones according to JBIDE-11011 are:
Usage
AS
Forge
OpenShift
Teiid and jBPM is still open too but I assume they are just not having any content this time and will be rejected.
/max
13 years, 10 months
Re: [jbosstools-dev] New Plugins
by Nick Boldt
Try building against our target platform. If that doesn't help, then
we'll need to add new stuff to your soon-to-be created SOA Tooling
parent pom (JBIDE-11121).
mvn clean -Pdefault
The existing JBT Core TP contains these features/plugins:
http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.SR2/
On 02/29/2012 12:52 PM, Daniel Florian wrote:
> Want to check in new plugins today. But wanted to show you the console log I get when I run my tests. Log shows there are missing plugins and was wondering what you think I should do. I'm am using a target platform that I built so maybe this won't be a problem with the JBT build. Thanks for your help. Here is the log:
>
> !SESSION 2012-02-29 06:47:10.527 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.6.0_29
> java.vendor=Apple Inc.
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
> Framework arguments: -version 3 -port 59330 -testLoaderClass org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader -loaderpluginname org.eclipse.jdt.junit4.runtime -testNameFile /var/folders/lw/k5mf3ljd0gn9s5sbk7pm76jc0000gn/T/testNames2526011090659595010.txt -application org.eclipse.pde.junit.runtime.coretestapplication -testpluginname org.jboss.tools.modeshape.jcr
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -consoleLog -version 3 -port 59330 -testLoaderClass org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader -loaderpluginname org.eclipse.jdt.junit4.runtime -testNameFile /var/folders/lw/k5mf3ljd0gn9s5sbk7pm76jc0000gn/T/testNames2526011090659595010.txt -application org.eclipse.pde.junit.runtime.coretestapplication -data /Users/dan/Work/Workspaces/teiid-designer/trunk/../junit-workspace -dev file:/Users/dan/Work/Workspaces/teiid-designer/trunk/.metadata/.plugins/org.eclipse.pde.core/pde-junit/dev.properties -os macosx -ws cocoa -arch x86_64 -consoleLog -testpluginname org.jboss.tools.modeshape.jcr
>
> !ENTRY org.eclipse.osgi 2 0 2012-02-29 06:47:21.418
> !MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.418
> !MESSAGE Bundle reference:file:/Users/dan/Work/TargetPlatforms/eclipse3.7.2SR2/eclipse/plugins/org.eclipse.jst.ws.jaxws.core_1.0.100.v201104031139.jar was not resolved.
> !SUBENTRY 2 org.eclipse.jst.ws.jaxws.core 2 0 2012-02-29 06:47:21.418
> !MESSAGE Missing imported package org.jdom.input_1.0.0.
> !SUBENTRY 2 org.eclipse.jst.ws.jaxws.core 2 0 2012-02-29 06:47:21.419
> !MESSAGE Missing imported package org.jdom_1.0.0.
> !SUBENTRY 2 org.eclipse.jst.ws.jaxws.core 2 0 2012-02-29 06:47:21.419
> !MESSAGE Missing imported package org.jdom.output_1.0.0.
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.419
> !MESSAGE Bundle reference:file:/Users/dan/Work/TargetPlatforms/eclipse3.7.2SR2/eclipse/plugins/org.apache.velocity_1.5.0.v200905192330.jar was not resolved.
> !SUBENTRY 2 org.apache.velocity 2 0 2012-02-29 06:47:21.419
> !MESSAGE Missing imported package org.jdom_[1.0.0,2.0.0).
> !SUBENTRY 2 org.apache.velocity 2 0 2012-02-29 06:47:21.420
> !MESSAGE Missing imported package org.jdom.output_[1.0.0,2.0.0).
> !SUBENTRY 2 org.apache.velocity 2 0 2012-02-29 06:47:21.420
> !MESSAGE Missing imported package org.jdom.input_[1.0.0,2.0.0).
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.420
> !MESSAGE Bundle reference:file:/Users/dan/Work/TargetPlatforms/eclipse3.7.2SR2/eclipse/plugins/org.eclipse.jst.ws.cxf.core_1.0.100.v201104022153.jar was not resolved.
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.core 2 0 2012-02-29 06:47:21.420
> !MESSAGE Missing imported package org.jdom.input_1.0.0.
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.core 2 0 2012-02-29 06:47:21.420
> !MESSAGE Missing imported package org.jdom.output_1.0.0.
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.core 2 0 2012-02-29 06:47:21.421
> !MESSAGE Missing imported package org.jdom_1.0.0.
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.421
> !MESSAGE Bundle reference:file:/Users/dan/Work/TargetPlatforms/eclipse3.7.2SR2/eclipse/plugins/org.eclipse.jst.ws.jaxws.ui_1.0.100.v201104032053.jar was not resolved.
> !SUBENTRY 2 org.eclipse.jst.ws.jaxws.ui 2 0 2012-02-29 06:47:21.421
> !MESSAGE Missing imported package org.jdom_1.0.0.
> !SUBENTRY 2 org.eclipse.jst.ws.jaxws.ui 2 0 2012-02-29 06:47:21.421
> !MESSAGE Missing imported package org.jdom.input_1.0.0.
>
> !ENTRY org.eclipse.osgi 2 0 2012-02-29 06:47:21.571
> !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.577
> !MESSAGE Bundle org.apache.velocity_1.5.0.v200905192330 [47] was not resolved.
> !SUBENTRY 2 org.apache.velocity 2 0 2012-02-29 06:47:21.577
> !MESSAGE Missing optionally imported package org.apache.log_[1.0.1,1.0.1].
> !SUBENTRY 2 org.apache.velocity 2 0 2012-02-29 06:47:21.578
> !MESSAGE Missing optionally imported package org.apache.log.format_[1.0.1,1.0.1].
> !SUBENTRY 2 org.apache.velocity 2 0 2012-02-29 06:47:21.578
> !MESSAGE Missing optionally imported package org.apache.log.output.io_[1.0.1,1.0.1].
> !SUBENTRY 2 org.apache.velocity 2 0 2012-02-29 06:47:21.579
> !MESSAGE Missing optionally imported package org.apache.tools.ant_[1.7.0,2.0.0).
> !SUBENTRY 2 org.apache.velocity 2 0 2012-02-29 06:47:21.579
> !MESSAGE Missing optionally imported package org.apache.tools.ant.taskdefs_[1.7.0,2.0.0).
> !SUBENTRY 2 org.apache.velocity 2 0 2012-02-29 06:47:21.581
> !MESSAGE Missing imported package org.jdom_[1.0.0,2.0.0).
> !SUBENTRY 2 org.apache.velocity 2 0 2012-02-29 06:47:21.581
> !MESSAGE Missing imported package org.jdom.input_[1.0.0,2.0.0).
> !SUBENTRY 2 org.apache.velocity 2 0 2012-02-29 06:47:21.581
> !MESSAGE Missing imported package org.jdom.output_[1.0.0,2.0.0).
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.581
> !MESSAGE Bundle org.eclipse.jpt.jpa.eclipselink.ui_2.0.1.v201108080010 [370] was not resolved.
> !SUBENTRY 2 org.eclipse.jpt.jpa.eclipselink.ui 2 0 2012-02-29 06:47:21.582
> !MESSAGE Missing required bundle org.eclipse.jpt.jpa.ui_[3.0.0,4.0.0).
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.582
> !MESSAGE Bundle org.eclipse.jpt.jpa.gen_2.0.1.v201201260000 [371] was not resolved.
> !SUBENTRY 2 org.eclipse.jpt.jpa.gen 2 0 2012-02-29 06:47:21.582
> !MESSAGE Missing required bundle org.apache.velocity_1.5.0.
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.582
> !MESSAGE Bundle org.eclipse.jpt.jpa.ui_3.0.2.v201201243020 [372] was not resolved.
> !SUBENTRY 2 org.eclipse.jpt.jpa.ui 2 0 2012-02-29 06:47:21.582
> !MESSAGE Missing required bundle org.eclipse.jpt.jpa.gen_[2.0.0,3.0.0).
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.583
> !MESSAGE Bundle org.eclipse.jpt.jpadiagrameditor.ui_1.0.1.v201109150000 [375] was not resolved.
> !SUBENTRY 2 org.eclipse.jpt.jpadiagrameditor.ui 2 0 2012-02-29 06:47:21.583
> !MESSAGE Missing required bundle org.eclipse.jpt.jpa.ui_[3.0.0,4.0.0).
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.583
> !MESSAGE Bundle org.eclipse.jst.ws.cxf.consumption.core_1.0.0.v201003222311 [466] was not resolved.
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.consumption.core 2 0 2012-02-29 06:47:21.583
> !MESSAGE Missing required bundle org.eclipse.jst.ws.cxf.core_0.4.3.
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.consumption.core 2 0 2012-02-29 06:47:21.583
> !MESSAGE Missing required bundle org.eclipse.jst.ws.jaxws.core_[1.0.0,1.1.0).
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.584
> !MESSAGE Bundle org.eclipse.jst.ws.cxf.consumption.ui_1.0.0.v201003222311 [467] was not resolved.
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.consumption.ui 2 0 2012-02-29 06:47:21.584
> !MESSAGE Missing required bundle org.eclipse.jst.ws.cxf.consumption.core_[1.0.0,1.1.0).
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.consumption.ui 2 0 2012-02-29 06:47:21.584
> !MESSAGE Missing required bundle org.eclipse.jst.ws.cxf.core_[1.0.0,1.1.0).
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.consumption.ui 2 0 2012-02-29 06:47:21.584
> !MESSAGE Missing required bundle org.eclipse.jst.ws.cxf.ui_[1.0.0,1.1.0).
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.consumption.ui 2 0 2012-02-29 06:47:21.585
> !MESSAGE Missing required bundle org.eclipse.jst.ws.jaxws.core_[1.0.0,1.1.0).
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.585
> !MESSAGE Bundle org.eclipse.jst.ws.cxf.core_1.0.100.v201104022153 [468] was not resolved.
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.core 2 0 2012-02-29 06:47:21.585
> !MESSAGE Missing required bundle org.eclipse.jst.ws.jaxws.core_[1.0.0,1.1.0).
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.core 2 0 2012-02-29 06:47:21.585
> !MESSAGE Missing required bundle org.eclipse.jst.ws.jaxws.ui_[1.0.0,1.1.0).
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.core 2 0 2012-02-29 06:47:21.586
> !MESSAGE Missing imported package org.jdom_1.0.0.
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.core 2 0 2012-02-29 06:47:21.586
> !MESSAGE Missing imported package org.jdom.input_1.0.0.
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.core 2 0 2012-02-29 06:47:21.586
> !MESSAGE Missing imported package org.jdom.output_1.0.0.
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.586
> !MESSAGE Bundle org.eclipse.jst.ws.cxf.creation.core_1.0.100.v201104022153 [469] was not resolved.
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.creation.core 2 0 2012-02-29 06:47:21.586
> !MESSAGE Missing required bundle org.eclipse.jst.ws.cxf.core_[1.0.0,1.1.0).
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.creation.core 2 0 2012-02-29 06:47:21.587
> !MESSAGE Missing required bundle org.eclipse.jst.ws.jaxws.core_[1.0.0,1.1.0).
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.587
> !MESSAGE Bundle org.eclipse.jst.ws.cxf.creation.ui_1.0.100.v201104022153 [470] was not resolved.
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.creation.ui 2 0 2012-02-29 06:47:21.587
> !MESSAGE Missing required bundle org.eclipse.jst.ws.cxf.core_[1.0.0,1.1.0).
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.creation.ui 2 0 2012-02-29 06:47:21.613
> !MESSAGE Missing required bundle org.eclipse.jst.ws.cxf.creation.core_[1.0.0,1.1.0).
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.creation.ui 2 0 2012-02-29 06:47:21.623
> !MESSAGE Missing required bundle org.eclipse.jst.ws.cxf.ui_[1.0.0,1.1.0).
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.creation.ui 2 0 2012-02-29 06:47:21.626
> !MESSAGE Missing required bundle org.eclipse.jst.ws.cxf.consumption.ui_[1.0.0,1.1.0).
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.creation.ui 2 0 2012-02-29 06:47:21.628
> !MESSAGE Missing required bundle org.eclipse.jst.ws.jaxws.core_[1.0.0,1.1.0).
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.630
> !MESSAGE Bundle org.eclipse.jst.ws.cxf.ui_1.0.0.v201004171919 [472] was not resolved.
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.ui 2 0 2012-02-29 06:47:21.630
> !MESSAGE Missing required bundle org.eclipse.jst.ws.cxf.core_[1.0.0,1.1.0).
> !SUBENTRY 2 org.eclipse.jst.ws.cxf.ui 2 0 2012-02-29 06:47:21.631
> !MESSAGE Missing required bundle org.eclipse.jst.ws.jaxws.core_[1.0.0,1.1.0).
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.632
> !MESSAGE Bundle org.eclipse.jst.ws.jaxws.core_1.0.100.v201104031139 [478] was not resolved.
> !SUBENTRY 2 org.eclipse.jst.ws.jaxws.core 2 0 2012-02-29 06:47:21.632
> !MESSAGE Missing imported package org.jdom_1.0.0.
> !SUBENTRY 2 org.eclipse.jst.ws.jaxws.core 2 0 2012-02-29 06:47:21.633
> !MESSAGE Missing imported package org.jdom.input_1.0.0.
> !SUBENTRY 2 org.eclipse.jst.ws.jaxws.core 2 0 2012-02-29 06:47:21.635
> !MESSAGE Missing imported package org.jdom.output_1.0.0.
> !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-29 06:47:21.635
> !MESSAGE Bundle org.eclipse.jst.ws.jaxws.ui_1.0.100.v201104032053 [485] was not resolved.
> !SUBENTRY 2 org.eclipse.jst.ws.jaxws.ui 2 0 2012-02-29 06:47:21.636
> !MESSAGE Missing required bundle org.eclipse.jst.ws.jaxws.core_[1.0.0,1.1.0).
> !SUBENTRY 2 org.eclipse.jst.ws.jaxws.ui 2 0 2012-02-29 06:47:21.637
> !MESSAGE Missing imported package org.jdom_1.0.0.
> !SUBENTRY 2 org.eclipse.jst.ws.jaxws.ui 2 0 2012-02-29 06:47:21.638
> !MESSAGE Missing imported package org.jdom.input_1.0.0.
>
> ----- Original Message -----
>> Resending what I sent earlier so you'll have it in this thread too:
>>
>> (07:26:16 PM) danflo: yo Nick, got time for a quick discussion?
>> (07:30:09 PM) danflo: I've created 3 new plugins in modeshape tools.
>> These plugin will be part of a new feature I'm adding. The feature
>> has a
>> lot more development but I want to get these 3 new plugins (one of
>> which
>> has tests) into the trunk build.
>> (07:30:42 PM) danflo: So if I put references in the parent pom and
>> not
>> have any feature reference them is that all I need to do?
>>
>> You must follow this containment:
>>
>> 1. plugin is ref'd by the plugins/pom.xml and is contained by a
>> 2. feature is ref'd by the features/pom.xml and is contained by a
>> 3. site references the new feature (site.xml) and
>> 4. any downstream sites which need this feature (JBT SOA Tooling,
>> JBDS
>> SOA Tooling) also need to include the new feature in its site.xml.
>>
>> See also: http://cheezburger.com/nickboldt/lolz/View/5054000384
>>
>> (07:33:15 PM) danflo: I've also noticed that someone has put emma
>> properties in my test plugin. Should I add the same in the new test
>> plugin?
>>
>> Sure, if you want.
>>
>>
>>
>>
>> On 02/27/2012 09:55 PM, Daniel Florian wrote:
>>> Hi Nick,
>>>
>>> I missed you on IRC today. I want to double-check some things with
>>> you so I don't mess the build up.
>>>
>>> I've created 3 new plugins in modeshape tools. These plugin will be
>>> part of a new feature I'm adding. The feature has a lot more
>>> development but I want to get these 3 new plugins checked into the
>>> trunk build.
>>>
>>> I've put references to the 3 new plugins into the parent pom. I
>>> have NOT included any of the new plugins in any feature. Is that
>>> all I need to do? Can I check them in tomorrow.
>>>
>>> I've also noticed that someone has put "emma" properties in my test
>>> plugin. One of my new plugins is a test plugin. Should I add the
>>> same "emma" properties in that new test plugin?
>>>
>>> Much thanks
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools& Dev Studio
>> http://nick.divbyzero.com
>>
--
Nick Boldt :: http://nick.divbyzero.com
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
13 years, 10 months
