Windup usage Issue
by b.jayaraman＠accenturefederal.com
Hi
I'm trying to port an application that is currently hosted on Websphere 8.5 running on JDK 1.7 to JBoss EAP 6.4. I downloaded and installed Windup and tested with default provided ear file conversion, things worked fine, however, if I try to run through my app, I get zero story points for one app and for another app, I get only one story point. When windup runs, I see that websphere rules gets executed but still no results. I also tried to explode one of the war file and run through windup, it did not go through the files under WEB-INF/classes directory. I have created the issue in JIRA as well (https://issues.jboss.org/browse/WINDUP-567 & https://developer.jboss.org/message/926645#926645 ) . I can open the ear file and start double checking against the windup results but before that I just want to check with you for any additional hints or installation verification steps.
Thanks for your time,
-Babu
10 years, 10 months
Unclassified Files
by Samuel Tauil
Hi,
I understand the Unclassified Files section in the report as a list of all files which were decompiled properly by Procyon but weren't captured by any rules, so the user can check and see which resources need to be checked again and generate specific rules or not. Is that correct?
Thanks
Samuel
10 years, 10 months
Sugested Fix Hints
by Ian Tewksbury
All,
Do any of the hints have a "suggested fix" built into them. I was looking at the hint API but didnt see such a thing, but I know it had been talked about in the past.
If such a thing exists I want to detect hints with "suggested code fixes" and auto generate Eclipse quick fixes for those hints so people can easily apply the quick fixes to knock out the easy stuff in an automated fashion.
~Ian
10 years, 10 months
JBoss EAP 5 to JBoss EAP 6 Rules
by Ian Tewksbury
All,
Are there any rules already created for a JBoss 5 to JBoss 6 migration?
My customer is looking for tool to help streamline the migration.
Blue Skies,
~Ian
10 years, 11 months
Windup Meeting Minutes - 2015-04-29
by Lincoln Baxter, III
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup....
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup....
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup....
Meeting summary
---------------
* Agenda (ozizka, 14:03:20)
* Status reports (lincolnthree, 14:03:42)
* LINK:
https://docs.google.com/a/redhat.com/spreadsheets/d/1yAZYUulz7MsSU7tOCba9...
(ozizka, 14:07:57)
* I've implemented WINDUP-562 (ozizka, 14:10:38)
* (mbriskar) I was working on enhancing the updating functionality,
where new issues were introduced (FORGE-2308). However I didn't
finish it in order to be able to start working on the server
migration (lincolnthree, 14:10:57)
* (mbriskar) Now I am on 2-days RH internal soft-skills course.
(lincolnthree, 14:10:57)
* (mbriskar) We agreed with Ondra that I will provide some
functionality tests that will show which way to implement the
marking of the FileModels (edge vs property). (lincolnthree,
14:10:57)
* (mbriskar) After that I will work on the functionality to provide
operations to build CLICommands with an api like
CLICommand.on("subsystem").run("some command").withParam("param",
"value").withParam("param", "value") or similar. Firstly I will need
to study deeper about this, because I don't have much knowledge
about how it works (subsystems&CLI). (lincolnthree, 14:10:57)
* Now working on WINDUP-566 (ozizka, 14:11:02)
* And also working on F2F organization - rooms, L&L, agenda (ozizka,
14:11:49)
* Added a prescan filter to improve performance to TypeInterestFactory
(jsightler, 14:15:03)
* Also, worked with brad and lincoln to integrate performance PRs
related to improving decompilation and xml caching (jsightler,
14:15:23)
* (and to test lincoln's ast batching branch) (jsightler, 14:15:38)
* Reviewed several PRs (lincolnthree, 14:15:57)
* Worked on performance tuning and got distracted by refactoring
(still working on a PR here locally) (lincolnthree, 14:15:57)
* Worked on building a PoC XML document cache with Brad
(lincolnthree, 14:15:57)
* Worked on the AST batch processing performance (lincolnthree,
14:15:57)
* Plan on continuing to work on my refactoring and also review the
auto-update PR and other new functionality (lincolnthree, 14:15:57)
* Going forward, I am experimenting with not unzipping the lowest
level archives within an input application. (jsightler, 14:15:58)
* We also had a "whiteboard session" with Matej, talking about server
migration - goals, design, implementation, etc. (ozizka, 14:20:59)
* Worked with the Customer Portal team to build the Windup User Guide
and Windup Rules Development Guide using the new Drupal process.
They are now on Doc Stage and can be pushed to the portal any time
(sgilda, 14:21:15)
* F2F meeting agenda (lincolnthree, 14:21:26)
* WINDUP-574 ? (ozizka, 14:29:35)
* Generating these docs from runtime info is the best option,
(ozizka, 14:30:56)
* but we have other priorities now. (ozizka, 14:31:11)
* Server migration, the big picture (ozizka, 14:31:19)
* Holidays in CZ, PTOs (ozizka, 14:33:44)
* Priorities (ozizka, 14:34:50)
* Server Config, Performance, Ecliple Plugin, Quickstarts and Examples
(lincolnthree, 14:35:17)
* Server Config - In progress (Ondra, Matej) (lincolnthree, 14:35:28)
* Performance - In progress (Jess, Lincoln) (lincolnthree, 14:35:38)
* Eclipse Plugin - In progress (Jess, Lincoln, Ian) (lincolnthree,
14:35:54)
* Quickstarts and Examples - Not started (Lincoln) (lincolnthree,
14:36:12)
* LINK:
https://drive.google.com/a/redhat.com/file/d/0B6TharS7fpqGMV9OZUdnUjVYYWs...
(ozizka, 14:36:47)
* Version comparisons - is it needed? (lincolnthree, 14:37:02)
* Could users want to downgrade? (ozizka, 14:38:51)
* How about AS vs. EAP (ozizka, 14:39:21)
* AGREED: We will not worry about minor/micro versions. We will focus
on Major version to Major version comparisons only. (lincolnthree,
14:41:48)
* LINK:
https://drive.google.com/a/redhat.com/file/d/0B6TharS7fpqGMV9OZUdnUjVYYWs...
(ozizka, 14:43:37)
* Presented the big picture. (ozizka, 14:59:20)
* Nice job, looks good so far ozizka :) (lincolnthree, 14:59:28)
Meeting ended at 15:00:17 UTC.
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
10 years, 11 months
Server migration, the big picture
by Ondrej Zizka
Hi all,
as I promised, hereby I am proposing how the migration should look like
in the bigger picture.
I don't say we need all the described parts, but I have a good reason to
believe we do.
Details are described in respective Jira issues. The root Jira issue is
MIGR-229.
See the attached whiteboard photo for an overview. Slightly chaotic, as
drawn on the fly, and it's not complete anyway. Let's make a better one
on F2F.
General:
======
1) Server rules in it's own ruleset. Probably also in separated git repo
(as it is now).
2) The ruleset will reuse certain operations from other rulesets:
XPath query to XML documents,
.properties parsing,
possibly decompilation and analysis of classes - e.g. Tomcat
valves, maybe Spring beans, JMX mBeans (esp. for EAP 4), implementations
of various interfaces used for EAP 5, etc.
3) The ruleset will provide certain new
conditions, like CLI parsing,
and operations, like
CLI operations export, in a form of WINDUP-565
<https://issues.jboss.org/browse/WINDUP-565>
CLI commands in the report, with comments, highlights
of the source it was derived form, links to EAP/WildFly docs, etc.;
CLI commands script;
CLI commands execution against some running server
Adding a module to EAP 6 target
Installing a fresh target server (if handy)
We can look at Eduardo's WINDUP-550
<https://issues.jboss.org/browse/WINDUP-550> to see what we can reuse
for these.
4) The server ruleset will probably have a bit stronger source/target
technology split, in terms of respective rules being more organized into
individual addons. Not sure about this, depends on the mechanism we use
to enable/disable them.
5) To prevent running the app rules against server files, resp. to
support running app and server rules together, we need to update the
queries of some app rules to only focus on appropriate files. WINDUP-564
<https://issues.jboss.org/browse/WINDUP-564> and WINDUP-563
<https://issues.jboss.org/browse/WINDUP-563> . This is what I would
like to work on next. Now working on WINDUP-566
<https://issues.jboss.org/browse/WINDUP-566> .
Parts:
====
Target technologies:
So far, we consider EAP 6 as target server. The long-term goal of EAP
6 is to cover configuration with CLI. Not sure about current state, but
it needed some additional actions - direct file manipulation (e.g. modules).
Maybe some other target technologies? Depends on what is Windup used
for. SOA? Drools? Containers for these might require additional
configuration.
Source technologies:
The platforms we target long-term. It will be mostly XML and
.properties. But could also be more tricky parts, like, digging data
from EAP 5's ProfileService, mod_cluster config?, etc.
Platform identification and files comparison: WINDUP-562
<https://issues.jboss.org/browse/WINDUP-562> (Done)
As discussed during last status meeting, it will be useful to
recognize the server version - the user may not know the exact
version, which we need to know the default configuration (in case of CLI
script migration which just skips the defaults.)
recognize which files were changed compared to the distribution
of that version - i.e. which configuration files changed (and we don't
handle them) and which .jars are changed.
-------------
Those are rough boundaries. Anything to add or remove? And priorities?
Ondra
10 years, 11 months
Eclipse Plugin - When to regenerate validation markers
by Ian Tewksbury
All,
With old Windup 1.0 there was a way to regenerate the hints for a single file. Do to the redesign of Windup 2.0 I understand this is currently not possible, and doing so is an undertaking no one has attempted yet, so in the mean time I have a quandary of what to do.
Typically in eclipse when you edit a file you re-generate the validation markers for that file, so if you fix a validation marker it doesn't still show as busted. Currently without being able to regenerate the hints for a specific file I am unsure what the best option is.
Options I can think of are:
1. do nothing, and just allow stale validation markers to sit on the file even if they have been addressed
2. regenerate the entire windup graph every time a file is edited
1. could do this just on save rather then on every character type
2. how expensive is it to generate the graph? Are there any statistics?
3.
Once a file is changed mark all the windup markers as stale with a message that the graph needs to be regenerated to update them
4. Simply remove all windup markers from the edited file until such time as the graph is regenerated
It used to be that my validator would auto run windup on a project as soon as the validation kicked off. Currently the validator has been changed such that if windup has not been run it simply does not report any windup hints.
Any thoughts on adding back the bit to at least run windup the first time when validation first kicks off? Right now the user doesn't have any way of knowing that the only reason they are not seeing windup validation markers is they have not manually generated a report. In the old plugin design the generation of an HTML report and the validaton markers were two different actions. It is rather an Eclipse anti practice to have to invoke a secondary menu action, "Windup Generate Report" in this case, to then allow a validator to run correctly.
Blue Skies,
~Ian
10 years, 11 months
