Windup meeting minutes: 2014-06-16
by Lincoln Baxter, III
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup....
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup....
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup....
Meeting summary
---------------
* Agenda (lincolnthree, 13:50:44)
* Status updates (lincolnthree, 13:50:55)
* Alpha2 release checkin (lincolnthree, 13:51:29)
* Progress checkin (lincolnthree, 13:51:48)
* Reporting (lincolnthree, 13:53:33)
* Externalizing legacy rules data (lincolnthree, 13:53:41)
* Documentation (lincolnthree, 13:54:14)
* LINK: irc://irc.freenode.net:6667/#info Status updates
(lincolnthree, 13:56:17)
* Status Updates (lincolnthree, 13:56:24)
* Migration-base models and first rules are already merged (mbriskar,
13:57:53)
* Pull request for migrating java legacy rules is already there
(mbriskar, 13:58:09)
* there is only need to migrate XML rules and the migration should be
done (mbriskar, 13:59:34)
* Did some cleanup of the codebase last week (lincolnthree, 14:00:55)
* Helped with cleanup up the JavaClassModel relationships, and did a
big refactor to clean up the remaining DAO designs (DAOs are now all
*Services) (lincolnthree, 14:01:57)
* working next on proxies issue, then after that, writing tests for
existing features and probably getting sucked into more refactoring
(lincolnthree, 14:05:50)
* Proxies issue - FORGE-1877 (lincolnthree, 14:06:13)
* I have been working on WINDUP-117 (jsightler, 14:06:56)
* The goal here is to produce an initial report based upon the
classifications placed in the graph by the blacklists (jsightler,
14:07:31)
* I also added the ability to store Adjacent Vertices as a Map via an
annotation on the Frame (jsightler, 14:08:44)
* Ondra was on PTO. (ozizka, 14:11:22)
* Then resumed work on Reporting. Which I will discuss in topic.
(ozizka, 14:11:49)
* Also cleaning the wiki. (ozizka, 14:12:06)
* Alpha2 release checkin (lincolnthree, 14:13:38)
* ACTION: Lincoln will add JIRA issues to the Alpha2 release, which
will occur when those issues are complete (lincolnthree, 14:22:05)
* Progress checkpoint (lincolnthree, 14:23:18)
* Java rules API - implemented, working well (lincolnthree, 14:24:04)
* Tagging/categorizing rules - supported, not extremely simple but
working (lincolnthree, 14:24:36)
* Data model able to represent migration domain - in progress,
blacklist, project, java class, maven project, and report models are
in place - still improving (lincolnthree, 14:25:16)
* APIs for use in tools, known but not implemented yet. waiting on
more functionality (lincolnthree, 14:25:45)
* Reporting infrastructure is in place, working on building
classification/blacklist report to demonstrate API usage
(lincolnthree, 14:27:33)
* Performance under observation, will need to do some optimization
before releasing (lincolnthree, 14:28:21)
* Reporting (lincolnthree, 14:28:44)
* LINK:
http://ondrazizka.github.io/jboss-migration/reports/0.10.4/MigrationRepor...
(ozizka, 14:36:23)
* LINK:
https://github.com/OndraZizka/jboss-migration/blob/master/engine/src/main...
(ozizka, 14:40:07)
* LINK: https://issues.jboss.org/browse/WINDUP-91 (ozizka, 16:21:27)
* Reports discussion ran super long. Last topics will wait until next
week. (lincolnthree, 16:44:59)
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
10 years, 5 months
Reporting support in models - common grounds, denotion
by Ondrej Zizka
Hi,
for reporting, we will need some common grounds in the model classes.
We already had the @Label annotation, but that was removed.
Here's my suggestion:
@Title String - Title of the reported item. Not Name, that is overused
(e.g. all the EE resources will have names).
@Description String / class - longer description.
@Icon("resource/path.png") class - Graphical symbol to make the reports
more appealing.
@FoundBy List<Rule> - rules which found the item.
@Solutions List<Solution> - links to a solutions for given problem -
knowledge base?
@References List<Reference> - links to references for given problem.
URLs to docs.
@Properties Properties / Map<String, String>:
Many resources will have lists of information, e.g. generic
properties, like datasources.
These properties are not known in advance - they are DB specific,
JDBC driver specific, AS specific.
So instead of having a java property for each, it's way better to
have Properties or Map.
Properties won't be present in all models, but will be quite common,
so it should have support in core.
JIRA: https://issues.jboss.org/browse/WINDUP-120
There are few related:
WINDUP-103 Create report data model
WINDUP-109 Refactor model classes to support an abstract project model
WINDUP-117 Update reporting to use the new project meta-model for
producing reports (including blacklist reports)
WINDUP-114 Replace ArchiveModelPointer with a
@ArchiveType(value=".war") annotation on the model classes themselves
Ondra
10 years, 5 months
Windup legacy rules rewriting
by Ondrej Zizka
Hi,
just a note on $SUBJ. I may be wrong, but I recall we agreed that the
old rules, since being so monotonous, could have one rule, which would
load the simple data from a static file(s), and one rule which would
execute them. E.g. a simple .csv file with regex, hint, reference. Or
JSON/XML if needed.
Now Matej creates one java rule per each legacy regex.
Is there some change in the previous plan?
Both solutions have obvious advantages, I just want to know what was the
decision.
Thanks,
Ondra
10 years, 5 months
Migration Meeting Minutes - 2014-06-09
by Lincoln Baxter, III
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup....
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup....
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup....
Meeting summary
---------------
* Agenda (lincolnthree, 13:49:54)
* Status Updates (lincolnthree, 13:52:22)
* did a major refactoring yesterday as part of WINDUP-109
(lincolnthree, 13:53:19)
* fixed the impl/api splits ( (lincolnthree, 13:53:25)
* moved most of the model classes into rules-java (lincolnthree,
13:53:43)
* groovy java rules tests are not working for some reason but still
working on that (lincolnthree, 13:54:07)
* I have worked on refactoring the project data model classes (as part
of WINDUP-109) (jsightler, 13:57:41)
* I am also working on refactoring our gremlin query API support as
part of WINDUP-113 (jsightler, 13:58:21)
* Read wikis for Windup (probably mostly deprecated), Gremlin, Frames
and watched all the episodes about jboss windup on youtube.
(mbriskar, 14:03:43)
* added a method to generalize adding criterions ( WINDUP-112 )
(mbriskar, 14:04:21)
* Prepared a prototype rule for java that adds a hint, however it is
done yet. (
https://github.com/mbriskar/windup/commit/0596beb9eb87c0af0e2166b74572549...
) (mbriskar, 14:06:53)
* Upcoming Alpha2 release goals (lincolnthree, 14:20:59)
* Goal 1: Prototype rule format in Java/Groovy - (java is complete,
groovy in progress) (lincolnthree, 14:22:11)
* Goal 2: Begin work on rule distribution/installation/auto-upgrade
strategy (looks like this goal is not going to make this release)
(lincolnthree, 14:30:20)
* Goal 3: Begin to find integration points for tools. This is
basically done, but we can't implement until things are a bit more
stable.
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
10 years, 5 months
windup-legacy: Test runner could not locate test class [org.jboss.windup.test.WindupLegacyWizardTest] in any deployed Addon
by Ian Tewksbury
All,
When trying to run "mvn clean install" on the Windup Legacy project I am getting the following error. Anyone have a resolution for this?
java.lang.IllegalStateException: Test runner could not locate test class [org.jboss.windup.test.WindupLegacyWizardTest] in any deployed Addon.
at org.jboss.forge.arquillian.ForgeTestMethodExecutor.invoke(ForgeTestMethodExecutor.java:222)
at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...
Blue Skies,
~Ian
10 years, 5 months
Could not find artifact com.tinkerpop:frames:jar:2.6.0-jsight-SNAPSHOT
by Ian Tewksbury
All,
I just pulled the latest from master and am getting this error, anyone know how to resolve?
Failed to execute goal on project windup-graph-api: Could not resolve dependencies for project org.jboss.windup.graph:windup-graph-api:jar:2.0.0-SNAPSHOT: Could not find artifact com.tinkerpop:frames:jar:2.6.0-jsight-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/)
Looks like Jesse may have built his own version of com.tinkerpop:frames:jar which Windup now depends on and can not find.
Blue Skies,
~Ian
10 years, 5 months
Migration Meeting Minutes - 2014-06-02
by Lincoln Baxter, III
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup....
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup....
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup....
Meeting summary
---------------
* Agenda (lincolnthree, 13:49:48)
* Status reports (lincolnthree, 13:52:44)
* Lincoln is working on implementing Rule metadata - ability to trace
rules to their origin, and retrieve information such as categories,
tags, etc. (lincolnthree, 13:54:25)
* Now using a new pull request workflow (lincolnthree, 14:12:42)
* We've moved to a new git pull request workflow for all non-trivial
contributions. This will facilitate communication and discussion
about changes being made to core code, and provide a digital paper
trail of progress. (lincolnthree, 14:13:29)
* Welcome Matej Briskar, new team member (lincolnthree, 14:13:39)
* We are happy to welcome Matej Briskar to the Migration team. He will
initially be working on porting existing windup 1.x rules to the new
windup 2.x format/api. (lincolnthree, 14:14:22)
* Migration actions (lincolnthree, 14:14:41)
* Github Wiki (ozizka, 14:20:12)
* Github Wiki (lincolnthree, 14:20:47)
* ozizka moved original windup code to windup/windup-legacy repository
(lincolnthree, 14:21:33)
* AGREED: We will use JIRA, IRC, and the Mailing List for design
discussions (lincolnthree, 14:25:24)
* Demos (lincolnthree, 14:26:44)
* We will be demoing/reviewing the reporting/rules metadata work
tomorrow via hangout (lincolnthree, 14:27:04)
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
10 years, 6 months
Please clean up unused branches in windup/windup
by Lincoln Baxter, III
If you have created branches in windup/windup that are no longer required,
please remove them now. We have moved to a "pull request required"
contribution model, so branches in upstream should no longer be required
(you should use a branch in your own fork)
I will be performing branch cleanup on Friday, so if there is a branch that
you do not want deleted, please reply to this thread and let me know. Thank
you.
Thank you!
~Lincoln
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
10 years, 6 months
