[jbosstools-dev] ACTION REQUIRED: Beta2 Code Freeze Task JIRAs / Code Freeze is tomorrow Thurs July 16

[Nick Boldt]

The only things we've changed are the version (so it's greater than the 
version in 4.2.x), the license address (using the new license feature) 
[1], and the use of JUnit 4.12 instead of 3.8 (because of Mars TP 
changes) in the test plugins.

Nothing FUNCTIONAL in Portlet's actual (non-test) plugins has changed 
since 4.2.x. All the above changes were done JUST IN CASE we had actual 
code to change so that this meta-work wouldn't stand in the way of doing 
maintenance if needed.

[1] https://issues.jboss.org/browse/JBIDE-19826

As portlet's not part of the base JBDS install (only a connector in 
JBT/JBDS Central) no one installing JBDS BYOE or JBT via Marketplace 
will see a disparity of license terms (eg., when installing two 
different JBT features simultaneously).

Only someone who intentionally chooses to install it from the WebTools 
category of the update site (or selects ALL features from the update 
site) or selects the Central connector will even get it installed, and 
see the old license address.

---

So I would say no, unless we REALLY need the new license's contact address.

Max, Richard, would you agree? Or do we need to rebuild Portlet simply 
to update its license's contact address?

(Related: do we need to rebuild Xulrunner and Locus too?)


On 07/15/2015 02:34 PM, Snjezana Peco wrote:
> Should we create a branch for portlet?
>
> Snjeza
>
> On 7/15/2015 4:29 PM, Nick Boldt wrote:
>> Here are your task jiras. Note that to reduce email clutter, you don't
>> need to assign these to yourself & then click "Start Progress".
>>
>> You can just do the work and close them when done, which produces only a
>> single JIRA email instead of 2 or 3.
>>
>> Aerogear          : https://issues.jboss.org/browse/JBIDE-20268
>> VPE               : https://issues.jboss.org/browse/JBIDE-20270
>> Integration Tests : https://issues.jboss.org/browse/JBIDE-20271
>> Server            : https://issues.jboss.org/browse/JBIDE-20273
>> Hibernate         : https://issues.jboss.org/browse/JBIDE-20274
>> Base              : https://issues.jboss.org/browse/JBIDE-20275
>> OpenShift         : https://issues.jboss.org/browse/JBIDE-20276
>> Playground        : https://issues.jboss.org/browse/JBIDE-20277
>> JavaEE            : https://issues.jboss.org/browse/JBIDE-20278
>> JST               : https://issues.jboss.org/browse/JBIDE-20279
>> Forge             : https://issues.jboss.org/browse/JBIDE-20280
>> Birt              : https://issues.jboss.org/browse/JBIDE-20281
>> BrowserSim        : https://issues.jboss.org/browse/JBIDE-20282
>> Webservices       : https://issues.jboss.org/browse/JBIDE-20283
>> Arquillian        : https://issues.jboss.org/browse/JBIDE-20284
>> Freemarker        : https://issues.jboss.org/browse/JBIDE-20285
>> Central           : https://issues.jboss.org/browse/JBIDE-20286
>> LiveReload        : https://issues.jboss.org/browse/JBIDE-20287
>>
>> and for me:
>>
>> JBDS              : https://issues.jboss.org/browse/JBDS-3483
>> JBoss Tools       : https://issues.jboss.org/browse/JBIDE-20267
>> Central Discovery : https://issues.jboss.org/browse/JBIDE-20269
>> build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc,
>> versionwatch: https://issues.jboss.org/browse/JBIDE-20272
>>
>> Cheers,
>>
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com