I think you are using an outdated version of Windup. Run "which windup" and
see where the old version is, and replace it with the new version.
On Fri, Mar 27, 2015 at 10:06 AM, Robb Greathouse <
robb.greathouse(a)redhat.com> wrote:
Congrats.
When it starts up it says that it is 2.0.0-beta 7,
JBoss Windup, version [ 2.0.0.Beta7 ] - JBoss, by Red Hat, Inc. [
http://windup.jboss.org ]
Is that appropriate?
Robb Greathouse
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
------------------------------
I am proud to announce the release of Windup 2.2.0.Final, which includes
the following features/enhanvements/and bugfixes.
Great job team!
~Lincoln
Bug
- [WINDUP-510 <
https://issues.jboss.org/browse/WINDUP-510>] - Build
fails with BOM missing
- [WINDUP-511 <
https://issues.jboss.org/browse/WINDUP-511>] -
Quickstarts tests fail with a NPE
- [WINDUP-516 <
https://issues.jboss.org/browse/WINDUP-516>] -
[Performance] Multiple valueStores even if the rule does not use parameters
- [WINDUP-517 <
https://issues.jboss.org/browse/WINDUP-517>] -
Application Index page lacks technology list and effort information
- [WINDUP-518 <
https://issues.jboss.org/browse/WINDUP-518>] - XML
Handlers do not support nested rules
- [WINDUP-524 <
https://issues.jboss.org/browse/WINDUP-524>] - Fix the
cyclic dependency between windup and windup-rulesets
- [WINDUP-542 <
https://issues.jboss.org/browse/WINDUP-542>] - Fix
severe regression in AST performance
- [WINDUP-544 <
https://issues.jboss.org/browse/WINDUP-544>] -
StackOverflowException when generating Application report
Enhancement
- [WINDUP-409 <
https://issues.jboss.org/browse/WINDUP-409>] - Allow
rules metadata to be specified with annotations - @Rules( phase = ..., ...)
- [WINDUP-470 <
https://issues.jboss.org/browse/WINDUP-470>] - Classes
in java.lang package may differ in how they are parsed
- [WINDUP-506 <
https://issues.jboss.org/browse/WINDUP-506>] - Identify
Archives Ruleset: Improve memory footprint
- [WINDUP-508 <
https://issues.jboss.org/browse/WINDUP-508>] -
WindupRuleProvider should contain a location/origin field (to indicate
where it was defined)
- [WINDUP-515 <
https://issues.jboss.org/browse/WINDUP-515>] - Add
Severity to Hint
- [WINDUP-520 <
https://issues.jboss.org/browse/WINDUP-520>] - Rule
Externalization - Introduce a Rule, RuleProvider and RulesetMetadata API
- [WINDUP-529 <
https://issues.jboss.org/browse/WINDUP-529>] -
Performance issue: Query requires iterating over all vertices
[(ClassificationModel:classification = ...)]
Feature Request
- [WINDUP-402 <
https://issues.jboss.org/browse/WINDUP-402>] - Change
ruleset category metadata to tag-like system (make it a set of strings)
- [WINDUP-521 <
https://issues.jboss.org/browse/WINDUP-521>] - Rule
Externalization - Create XML Handlers for Rule metadata
- [WINDUP-522 <
https://issues.jboss.org/browse/WINDUP-522>] - Rule
Externalization - Create user-interface for selecting source/target
platforms
- [WINDUP-523 <
https://issues.jboss.org/browse/WINDUP-523>] - Rule
Externalization - Allow filtering of RuleProviders by tags (categories)
Task
- [WINDUP-512 <
https://issues.jboss.org/browse/WINDUP-512>] - Rename
Implicit to Dependent
- [WINDUP-513 <
https://issues.jboss.org/browse/WINDUP-513>] - Phase
pseudo-RuleProviders to have ~Phase suffix
- [WINDUP-530 <
https://issues.jboss.org/browse/WINDUP-530>] - Rename
the module "utils" to "windup-utils"
Sub-task
- [WINDUP-464 <
https://issues.jboss.org/browse/WINDUP-464>] - Expand
all addons with simple layout to use full api/impl/tests structure
- [WINDUP-465 <
https://issues.jboss.org/browse/WINDUP-465>] - Review
all rules, organize into an external repository, and add useful hint
information with links to knowledge articles
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."