August 2014 - windup-dev - Jboss List Archives

by Ondrej Zizka

Lincoln, before I forget, I wanted to ask what are the problems with CWD in target/ . Maven may be convention-based, but 1) the default may not match the conventions, 2) the conventions are not always good practice. Just now, I am writing test for the bootstrap class, and not having it running in target is really bad idea. Ondra

11 years, 10 months

2
1
0 / 0

Leave IDE files in place please

by "Ing. Ondřej Žižka"

https://github.com/jsight/windup/commit/75e4da40b504bdc688fb4e06785f25885... Why can't NetBeans file stay? Why eclipse file can then? Regards, Ondra

11 years, 10 months

4
6
0 / 0

Let's use relative paths

by Ondrej Zizka

Hi, I suggest we use relative paths. For the reports, using full paths may get overly verbose and make the reports unreadable. Relative paths are usually not, that much. Compare e.g.: INFO: Unzipping /home/ondra/work/Migration/Windup/tests/core/target/../../../test-files/Windup1x-javaee-example.war to /home/ondra/work/Migration/Windup/tests/core/target/windupreport/archives/Windup1x-javaee-example.war vs. INFO: Unzipping ../../../test-files/Windup1x-javaee-example.war to windupreport/archives/Windup1x-javaee-example.war The base path may be stated just once somewhere else. From my experience, using relative paths may get tricky, needing to carry the base path(s) along with the relative, but still, is worth the work. my2c, Ondra

11 years, 10 months

4
7
0 / 0

Windup JIRA Triage Part 1 - Meeting Notes

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 --------------- * JIRA Triage Round 1 (lincolnthree, 14:44:03) * LINK: https://issues.jboss.org/issues/?jql=project%20%3D%20WINDUP%20AND%20statu... (ozizka, 14:46:22) * AGREED: WINDUP-1 closed complete (lincolnthree, 14:49:24) * AGREED: WINDUP-3 closed out of date (lincolnthree, 14:50:08) * AGREED: WINDUP-3 closed out of date (lincolnthree, 14:50:23) * AGREED: WINDUP-12 closed out of date (lincolnthree, 14:52:42) * AGREED: WINDUP-14 needs more information (lincolnthree, 14:54:39) * AGREED: WINDUP-15 closed out of date (lincolnthree, 14:54:56) * AGREED: WINDUP-19 closed out of date (lincolnthree, 15:02:10) * AGREED: WINDUP-27 closed out of date (lincolnthree, 15:11:50) * AGREED: WINDUP-29 closed out of date (lincolnthree, 15:12:10) * AGREED: WINDUP-36 closed as duplicate of WINDUP-25 (lincolnthree, 15:20:56) * AGREED: WINDUP-44 closed as resolved (lincolnthree, 15:25:56) * AGREED: WINDUP-46 closed as resolved (lincolnthree, 15:27:31) * AGREED: WINDUP-47 closed as resolved (lincolnthree, 15:28:18) * AGREED: WINDUP-51 closed as resolved (lincolnthree, 15:34:12) * AGREED: WINDUP-52 closed as deferred (lincolnthree, 15:34:53) * AGREED: WINDUP-53 closed as deferred (lincolnthree, 15:35:33) * AGREED: WINDUP-59 closed as rejected (lincolnthree, 15:43:54) * AGREED: WINDUP-59 closed as rejected (lincolnthree, 15:44:33) * AGREED: WINDUP-61 closed as resolved (lincolnthree, 15:46:41) * AGREED: WINDUP-63 closed as resolved (lincolnthree, 15:47:58) * AGREED: WINDUP-67 closed as out of date (lincolnthree, 15:50:44) * AGREED: WINDUP-73 closed as duplicate (lincolnthree, 15:56:43) * AGREED: WINDUP-75 closed as resolved (lincolnthree, 16:00:28) Meeting ended at 16:28:54 UTC. -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better."

11 years, 10 months

1
0
0 / 0

Windup Meeting Minutes - 2014-08-13

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, 14:14:31) * Status Reports (lincolnthree, 14:18:37) * I've been working on WINDUP-133 mostly this week, it is now merged with some patches from jsightler (lincolnthree, 14:19:12) * Reviewed about 100 PRs and github discussions. (lincolnthree, 14:19:30) * Now working on the Forge exception hiding issue, and one other classloading issue (not windup related), but will probably abandon if I can't figure them out soon because we need to keep implementing functionality. (lincolnthree, 14:20:12) * that issue is FORGE-1969 (lincolnthree, 14:20:23) * Regardless of the smaller issues, I was working on the simplification of the rules. This led to two PRs, both of which are now merged (mbriskar, 14:21:23) * The first simplification is the implementation of default values if not specified for Iteration, WINDUP-156 (mbriskar, 14:22:19) * The second simplification is passing the variable names from Iteration to condition/operations, WINDUP-199. (mbriskar, 14:22:53) * mbriskar: Yeah those are great improvements! Very good job! (lincolnthree, 14:23:42) * right now trying to simplify the result of Windup-133 and maybe after this continue on migration of the legacy rules (mbriskar, 14:24:08) * I have been working on reviewing & merging some PRs as well (jsightler, 14:25:30) * I merged a PR yesterday from brad davis that improved our performance quite a bit (from 20-50% depending on the test) (jsightler, 14:26:33) * I am also working on JIRAs (168 - fixes some cases with method annotations, and working on fixing where we store the graph (WINDUP-200)) (jsightler, 14:28:08) * I divided my time between rebasing old PRs, doing expenses round 2 for the F2F meeting (most of them were rejected), reviewing other PRs, filling jira, doing test harness basis, and in the remaining time, (ozizka, 14:32:39) * I pushed reporting a bit - I have working PoC for XML/HTML generation out of annotated frames. (ozizka, 14:33:25) * But not a whole report yet, just snippets. (ozizka, 14:33:39) * And did more of wiki docs. (ozizka, 14:34:51) * I asked ozizka to be our point contact for docs organization and field trials teams at customers - making sure they have the info they need to get started and also gather their feedback when the time comes. (lincolnthree, 14:35:53) * Test working directory (lincolnthree, 14:39:25) * AGREED: CWD will remain . for now and we will address appropriately at the time it becomes an issue (lincolnthree, 14:56:03) * Next steps (lincolnthree, 14:56:33) * I estimate that we are 1 month behind our delivery schedule. (lincolnthree, 14:57:37) * I've already notified management and the business and we are pushing our delivery date back by 1 month. This has been updated in the engineering schedule document int he admin folder on google drive. (lincolnthree, 14:58:08) * We MUST focus on implementing functionality, docs, and other project tasks that move us toward our release. (ozizka, 15:02:44) * Rules syntax, Groovy simplified rules, Reporting, User input, and functionality that has business value. (ozizka, 15:02:44) * XML Inspection/Hinting Rules (lincolnthree, 15:14:23) * Running windup and accepting user input (lincolnthree, 15:14:29) * Groovy syntax for "provided" rules. (lincolnthree, 15:14:39) * A way to load groovy rules dynamically form a directory (lincolnthree, 15:14:51) * Generating a useful report (lincolnthree, 15:15:03) * WINDUP-204 (lincolnthree, 15:18:41) * AGREED: JIRA Triage will be tomorrow at 10am EST (lincolnthree, 15:44:03) -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better."

11 years, 10 months

1
0
0 / 0

Bootstrap

by Ondrej Zizka

I'd like to discuss: WINDUP-204 Implement normal bootstrap <https://issues.jboss.org/browse/WINDUP-204> Ondra

11 years, 10 months

1
0
0 / 0

EventGraph

by Ondrej Zizka

Hi, what do we need EventGraph for? GraphContextImpl.java: this.titanGraph = TitanFactory.open(conf); this.eventGraph = new EventGraph<TitanGraph>(this.titanGraph); Thanks, Ondra

11 years, 10 months

2
4
0 / 0

Reporting exceptions

by Ondrej Zizka

Hi all, Some thoughts for the future: Windup is that kind of tool that should be robust and try to do something sensible even with malformed input. Currently, we throw an exception whenever something unexpected happen, and halt the app. I think we should rather continue processing other items, and then include even those failed in the report, saying why it failed. Therefore, we should capture the exceptions in the rules, at different levels, into collections if needed, then turn them into vertices, and link them to the item during whose processing the exception occured. Then add it to the report. Duplicated exceptions can be just summarized. This is how it worked in WindRide. Ondra

11 years, 10 months

2
1
0 / 0

Is windup for real?

by windup-dev＠lists.jboss.org

Windup sounds like a perfect fit for exactly the job I have to do - we're porting a WebLogic application to JBoss. I know next to nothing about this application - I didn't develop any part of it, although I am newly part of a team that developed it. I downloaded the binary downloadable from the site to try it out and it quickly crapped out on our source code. NullPointerException. Oh well. I then followed the instructions to Build windup and after some difficulty, got the build to work. (Maven 3.1 required? guess I was behind the times, but okay). It built a whole bunch of stuff, none of which looks anything like the downloadable package. I don't want to DEVELOP windup, but I understand open source and don't mind doing my part to advance the state of the art. But where to start? There's no easily findable documentation telling me what, in this massive directory tree I've built, to do if I want to USE windup, and that's what I need now. Can someone please point me at this information? Or would my team be better off forgetting about windup and slogging through the port the old-fashioned way? I'd like to use windup but I need some initial guidance. Thanks, Steve Posted by forums Original post: https://community.jboss.org/message/884033#884033

11 years, 10 months

3
3
0 / 0

Iteration using Java's for?

by Ondrej Zizka

Hi, is there a reason against querying the graph, storing it to Java variable, iterating it using for( Foo foo : foos ), and skipping the varstack and when() etc? Basically, the current rules structure is appropriate for e.g. XML based rules whose XSD would translate to this structure, but if we provide Java and Groovy, the above way would be shorter to write, and users might tend to do that. Thanks, Ondra

11 years, 10 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

windup-dev August 2014