From ozizka at redhat.com Sat Aug 2 00:23:48 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Sat, 02 Aug 2014 06:23:48 +0200
Subject: [windup-dev] Forge-related issues - logging, exceptions
Message-ID: <53DC67D4.8000203@redhat.com>
Hi,
it's so adventurous to develop something with limited or no access to
information on what's happening in runtime.
When I get some exception, it's typically something like:
org.jboss.....WindupException$----$javassist@!#4138329859842740987598974105762985734109852984675091:
null
at org.jboss.forge.FooClass
at org.jboss.forge.BarClass
...
The real exception is swallowed somehow, and I can only find it
somewhere in the log. *If I am lucky.* Because logging is broken as well.
Every time I suggest to put fixing logging as priority, I am told "use
JUL". But that's not a solution.
I can use JUL, or print to std err for that matter, but other parts and
libraries will use SLF4J, Log4j, Commons Logging, JBoss logging.
These frameworks mostly do not perform well in modularized environment,
and either
1) Format logging in a really weird way (2 lines, date/time format
like from Abraham Lincoln's diary)
2) Log everything up to INFO level (see Forge's insanely long
relatively irrelevant information)
3) Even worse, log everything up to DEBUG level (see Forge's insanely
long relatively irrelevant information)
4) Even worse, do not log at all (see the long periods of silence in
our test runs).
With these two combined, I can spend hours and hours, solving mysteries.
But that gets monotonous over time. I'd rather develop some
functionality faster.
I have spent one evening trying various ways to fix logging, but without
luck - since the frameworks are initiated at random places, I would have
to add their deps and config to every addon used in the project,
including non-Windup.
Could we please fix logging and exception handling?
See e.g. https://issues.jboss.org/browse/FORGE-1964, or whatever it takes.
Thanks,
Ondra
From ozizka at redhat.com Sat Aug 2 07:20:12 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Sat, 02 Aug 2014 13:20:12 +0200
Subject: [windup-dev] Github PR rebase script // Fwd: Re: Git pull request
automation?
In-Reply-To: <517FD978.9070700@redhat.com>
References: <517FD978.9070700@redhat.com>
Message-ID: <53DCC96C.2070806@redhat.com>
Here is a script which Brian uses to rebase and merge selected PR's.
Could be handy.
HTH,
Ondra
-------- Original Message --------
Subject: Re: Git pull request automation?
Date: Tue, 30 Apr 2013 09:47:20 -0500
From: Brian Stansberry <brian.stansberry at redhat.com>
To: Ondrej Zizka <ozizka at redhat.com>
CC: Carlo de Wolf <cdewolf at redhat.com>
AIUI Carlo's team is building some automation around this for EAP.
I have a simple script I use to bring down a bunch of pull requests into
a single branch.[1] I then push that branch to upstream master-ignore.
Lightning and Tomaz Cerar's team city test that branch whenever changes
are made. If that goes well, I merge the branch to master and push.
The other mergers do similar things, probably with better scripts for
the first bit.
I don't use the requester's remote; the PR is available via the wildfly
github repo. See the script for details.
[1]
pull() {
cmd="git fetch upstream master "
for var in "$@"
do
cmd="$cmd pull/$var/head:pullRequest$var"
done
$cmd
git branch -D pulls
git checkout master
git rebase upstream/master
git checkout -b pulls
for var in "$@"
do
git checkout pullRequest$var
git rebase pulls
git checkout pulls
git merge pullRequest$var
git branch -D pullRequest$var
done
}
On 4/30/13 9:16 AM, Ondrej Zizka wrote:
> Hi Brian,
>
> if I want to test and review the pull request before merging, it seems
> that I have to add the requester's remote, fetch it, check out his
> branch, then do what I want.
>
> With the pace of PRs to AS, I assume you have some automation for this,
> perhaps through GitHub API. Is that available somewhere?
> Or how do you proceed when you need to check something in an IDE, or
> test something not covered by the testsuite, etc?
>
> Thanks,
> Ondra
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140802/df796220/attachment.html
From ozizka at redhat.com Sun Aug 3 18:35:29 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 04 Aug 2014 00:35:29 +0200
Subject: [windup-dev] Forge 2.7.3?
Message-ID: <53DEB931.106@redhat.com>
Hi, I am hitting FORGE-1199, can we use Forge 2.7.3-SNAPSHOT until it is
released?
Thanks,
Ondra
From ozizka at redhat.com Mon Aug 4 08:26:10 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 04 Aug 2014 14:26:10 +0200
Subject: [windup-dev] LinkageError: previously loaded "FramedGraph"
Message-ID: <53DF7BE2.30100@redhat.com>
Hi,
I am getting this in a test:
java.lang.LinkageError: loader constraint violation: loader (instance of
org/jboss/modules/ModuleClassLoader) previously initiated loading for a
different type with name "com/tinkerpop/frames/FramedGraph"
Any idea why? This should be prevented by modular classloading... anyone
willing to try?
Thanks,
Ondra
From ozizka at redhat.com Mon Aug 4 10:37:05 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 04 Aug 2014 16:37:05 +0200
Subject: [windup-dev] LinkageError: previously loaded "FramedGraph"
In-Reply-To: <53DF7BE2.30100@redhat.com>
References: <53DF7BE2.30100@redhat.com>
Message-ID: <53DF9A91.7040700@redhat.com>
Found this:
https://issues.jboss.org/browse/FORGE-908
Although I need some more explanation. Does that mean that I can't have
the tests right next to the tested addon?
Ondra
On 4.8.2014 14:26, Ondrej Zizka wrote:
> Hi,
>
> I am getting this in a test:
>
> java.lang.LinkageError: loader constraint violation: loader (instance of
> org/jboss/modules/ModuleClassLoader) previously initiated loading for a
> different type with name "com/tinkerpop/frames/FramedGraph"
>
> Any idea why? This should be prevented by modular classloading... anyone
> willing to try?
>
> Thanks,
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From lbaxter at redhat.com Mon Aug 4 15:23:16 2014
From: lbaxter at redhat.com (Lincoln Baxter)
Date: Mon, 4 Aug 2014 15:23:16 -0400 (EDT)
Subject: [windup-dev] .when( new True() )
In-Reply-To: <53DA8410.1020101@redhat.com>
References: <53DA8410.1020101@redhat.com>
Message-ID: <1991939644.32258166.1407180196777.JavaMail.zimbra@redhat.com>
Not sure why it would be executed more than once per-execution of Windup. We should look into this when we build out more of the Groovy support.
Not sure what information you want to get out of the API. You'd probably have to step-debug it.
~Lincoln
----- Original Message -----
From: "Ondrej Zizka" <ozizka at redhat.com>
To: "Windup-dev List" <windup-dev at lists.jboss.org>, "Lincoln Baxter" <lbaxter at redhat.com>, "Jess Sightler" <jsightle at redhat.com>
Sent: Thursday, July 31, 2014 1:59:44 PM
Subject: .when( new True() )
Hi,
I found this rule being invoked many many times.
Since there's just .when( new True() ) and not some iteration, I wonder
what are the elements that it executes over so many times.
And how do I get this information from the current API?
Thanks,
Ondra
ruleSet("ExampleGroovyRule").setPhase(RulePhase.MIGRATION_RULES)
.addRule()
.when(
new True()
)
.perform(
new GraphOperation () {
public void perform(GraphRewrite event, EvaluationContext
context) {
//System.out.println("Performing rewrite operation")
Logging.of(this.getClass()).info("Performing rewrite
operation in ExampleGroovyRule");
}
}
From ozizka at redhat.com Wed Aug 6 03:36:35 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 06 Aug 2014 09:36:35 +0200
Subject: [windup-dev] Half day PTO
Message-ID: <53E1DB03.9040508@redhat.com>
Sorry, sent from wrong account... correction.
Hi,
I need to take a half-day PTO. I'll be back for the meeting.
Regards,
Ondra
From zizka at seznam.cz Wed Aug 6 03:35:21 2014
From: zizka at seznam.cz (=?UTF-8?B?IkluZy4gT25kxZllaiDFvWnFvmthIg==?=)
Date: Wed, 06 Aug 2014 09:35:21 +0200
Subject: [windup-dev] Half day PTO
Message-ID: <53E1DAB9.5060502@seznam.cz>
Hi,
I need to take a half-day PTO. I'll be back for the meeting.
Regards,
Ondra
From lincolnbaxter at gmail.com Wed Aug 6 11:17:36 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 6 Aug 2014 11:17:36 -0400
Subject: [windup-dev] Windup Meeting Minutes - 2014-08-05
Message-ID: <CAEp_U4G_qC_zZy-=Bs+0vLuvPJc2xxGo7xeG50bhM37-7i-PSQ@mail.gmail.com>
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-08-06-14.11.html
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-08-06-14.11.txt
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-08-06-14.11.log.html
Meeting summary
---------------
* Agenda (lincolnthree1, 14:11:27)
* Status Updates (lincolnthree1, 14:15:14)
* Last week I was on vacation and completely ignored anything from
work, so now I have a pile of stuff to get through and issues to
resolve. (lincolnthree1, 14:15:41)
* I'm going to be working on ozizka's classloading issues and also the
WINDUP- 133 refactoring (lincolnthree1, 14:16:08)
* Since WINDUP-133 not being resolved, I stopped the work on the
migration and started to work on adding some new tests and thinking
about how to simplify the rules (mbriskar, 14:17:14)
* According to the simplification, with Jess we came up with
WINDUP-156, which now has it's PR in the windup (mbriskar,
14:18:11)
* according to the tests, I was adding the tests to the upcoming
issues or places I thought some test could be present. So I added
test for the upcoming WINDUP-167 and also for the GraphService
(which didn't have some basic tests). (mbriskar, 14:19:57)
* I was on vacation and am starting back today. (jsightler, 14:22:22)
* I was working on reporting and get into few issues (ozizka,
14:25:09)
* Mostly with classloading. Going to fix with Lincoln's help (ozizka,
14:25:37)
* Besides that, I worked on the server-side rules, (ozizka, 14:26:09)
* and again, wiki (ozizka, 14:26:51)
* Classloader issues (summary and how to reproduce) (lincolnthree1,
14:29:40)
* LINK: https://issues.jboss.org/browse/WINDUP-178 (ozizka,
14:29:48)
* Steps to reproduce: (lincolnthree1, 14:33:04)
* 1. Checkout and build:
https://github.com/OndraZizka/windup/tree/ReportCommons (skip tests)
(lincolnthree1, 14:34:21)
* 2. Run tests in "windup-reporting-xslt" sub-module. (lincolnthree1,
14:34:39)
* Related issue: https://issues.jboss.org/browse/FORGE-1969
(lincolnthree1, 14:36:09)
* WINDUP-133 (lincolnthree1, 14:36:58)
* Logging (lincolnthree1, 14:55:31)
* WINDUP-168 (lincolnthree1, 15:01:19)
Meeting ended at 15:16:30 UTC.
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140806/e47dffb7/attachment.html
From lincolnbaxter at gmail.com Wed Aug 6 17:03:42 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 6 Aug 2014 17:03:42 -0400
Subject: [windup-dev] Force-pushed a rebased upstream master repo.
Message-ID: <CAEp_U4Gb5KW_1kcc9QyTsdmJnfzWpqOw-p3rgchVduaWsiMOUA@mail.gmail.com>
In order to clean up some accidental commits to the repo, I had to
force-push, meaning we all need to use the folowing process to re-sync our
local forks:
http://ocpsoft.org/tutorials/git/reset-and-sync-local-respository-with-remote-branch/
Please let me know if you have any trouble.
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140806/9a62c936/attachment.html
From lincolnbaxter at gmail.com Thu Aug 7 13:58:22 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 7 Aug 2014 13:58:22 -0400
Subject: [windup-dev] LinkageError: previously loaded "FramedGraph"
In-Reply-To: <53DF9A91.7040700@redhat.com>
References: <53DF7BE2.30100@redhat.com>
<53DF9A91.7040700@redhat.com>
Message-ID: <CAEp_U4GsTdhBLDTRsoBGqbp=EuMx6OkdeSOruJ6b9-NZF3hvXQ@mail.gmail.com>
Not sure exactly what you are asking, but this issue was resolved and is no
longer a problem. The only way you'd see something like this is if you
include duplicate classes in your test case. Don't import entire packages
or libraries, for instance.
On Mon, Aug 4, 2014 at 10:37 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
> Found this:
>
> https://issues.jboss.org/browse/FORGE-908
>
> Although I need some more explanation. Does that mean that I can't have
> the tests right next to the tested addon?
>
> Ondra
>
>
> On 4.8.2014 14:26, Ondrej Zizka wrote:
> > Hi,
> >
> > I am getting this in a test:
> >
> > java.lang.LinkageError: loader constraint violation: loader (instance of
> > org/jboss/modules/ModuleClassLoader) previously initiated loading for a
> > different type with name "com/tinkerpop/frames/FramedGraph"
> >
> > Any idea why? This should be prevented by modular classloading... anyone
> > willing to try?
> >
> > Thanks,
> > Ondra
> > _______________________________________________
> > windup-dev mailing list
> > windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140807/f33a7d73/attachment.html
From lincolnbaxter at gmail.com Thu Aug 7 14:05:54 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 7 Aug 2014 14:05:54 -0400
Subject: [windup-dev] Forge 2.7.3?
In-Reply-To: <53DEB931.106@redhat.com>
References: <53DEB931.106@redhat.com>
Message-ID: <CAEp_U4FNCNtCpEGiBVbZ1wyk4-5vyiaRf7JiSR6C2-ZMdGir8g@mail.gmail.com>
Yep. Sure can.
On Sun, Aug 3, 2014 at 6:35 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
> Hi, I am hitting FORGE-1199, can we use Forge 2.7.3-SNAPSHOT until it is
> released?
>
> Thanks,
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140807/a97e9407/attachment.html
From lincolnbaxter at gmail.com Thu Aug 7 14:08:09 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 7 Aug 2014 14:08:09 -0400
Subject: [windup-dev] Github PR rebase script // Fwd: Re: Git pull
request automation?
In-Reply-To: <53DCC96C.2070806@redhat.com>
References: <517FD978.9070700@redhat.com>
<53DCC96C.2070806@redhat.com>
Message-ID: <CAEp_U4Hq9VZismuRK1CEjy9v4GkXAUoOq-rhVTrRg46Z+2eBYA@mail.gmail.com>
Whatever works for you :)
You don't need to add the remote, just copy the text from Github... it
tells you how to do it right in the PR (just click "Use thh command line"
to see the instructions)
git checkout -b lincolnthree-WINDUP-133 master
git pull https://github.com/lincolnthree/windup.git WINDUP-133
Then run the tests "mvn clean install", and if they pass:
git checkout master
git merge --no-ff lincolnthree-WINDUP-133
git push origin master
Hope this helps,
~Lincoln
On Sat, Aug 2, 2014 at 7:20 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
> Here is a script which Brian uses to rebase and merge selected PR's.
> Could be handy.
>
> HTH,
> Ondra
>
>
>
>
> -------- Original Message -------- Subject: Re: Git pull request
> automation? Date: Tue, 30 Apr 2013 09:47:20 -0500 From: Brian
> Stansberry <brian.stansberry at redhat.com> <brian.stansberry at redhat.com> To:
> Ondrej Zizka <ozizka at redhat.com> <ozizka at redhat.com> CC: Carlo de Wolf
> <cdewolf at redhat.com> <cdewolf at redhat.com>
>
> AIUI Carlo's team is building some automation around this for EAP.
>
> I have a simple script I use to bring down a bunch of pull requests into
> a single branch.[1] I then push that branch to upstream master-ignore.
> Lightning and Tomaz Cerar's team city test that branch whenever changes
> are made. If that goes well, I merge the branch to master and push.
>
> The other mergers do similar things, probably with better scripts for
> the first bit.
>
> I don't use the requester's remote; the PR is available via the wildfly
> github repo. See the script for details.
>
> [1]
>
> pull() {
> cmd="git fetch upstream master "
> for var in "$@"
> do
> cmd="$cmd pull/$var/head:pullRequest$var"
> done
>
> $cmd
>
> git branch -D pulls
> git checkout master
> git rebase upstream/master
> git checkout -b pulls
>
> for var in "$@"
> do
> git checkout pullRequest$var
> git rebase pulls
> git checkout pulls
> git merge pullRequest$var
> git branch -D pullRequest$var
> done
> }
>
> On 4/30/13 9:16 AM, Ondrej Zizka wrote:
> > Hi Brian,
> >
> > if I want to test and review the pull request before merging, it seems
> > that I have to add the requester's remote, fetch it, check out his
> > branch, then do what I want.
> >
> > With the pace of PRs to AS, I assume you have some automation for this,
> > perhaps through GitHub API. Is that available somewhere?
> > Or how do you proceed when you need to check something in an IDE, or
> > test something not covered by the testsuite, etc?
> >
> > Thanks,
> > Ondra
>
>
> --
> Brian Stansberry
> Principal Software Engineer
> JBoss by Red Hat
>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140807/1a392b8a/attachment-0001.html
From jsightle at redhat.com Thu Aug 7 14:47:51 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 07 Aug 2014 14:47:51 -0400
Subject: [windup-dev] Negative queries?
In-Reply-To: <53DAA713.8010700@redhat.com>
References: <53DAA713.8010700@redhat.com>
Message-ID: <53E3C9D7.1080104@redhat.com>
On 07/31/2014 04:29 PM, Ondrej Zizka wrote:
> When talking to Robb, we discussed the ability to query for POJO classes
> - i.e. those which do not have any vendor-specific extension, do not use
> blacklisted classes, do not extend something "dirty", etc.
>
> Which brings us to interesting concept - querying for something "not
> being a lot of things".
>
> We have discussed this briefly on F2F with Brad.
> The first shot could be:
>
> * creating a method which will query for vertexes that have some frame
> type (JavaClass), but not any other, or a set of other types
> (WebLogicContextListener).
One issue here is that the Titan Text predicate does not directly
support negations. I am not sure how easy it would be to add this in a
performant manner for a negated type search.
I agree that this is a need, though for certain types of queries.
>
> * querying for vertices which are not linked to vertices in sevral
> blacklists
> For example, querying for JavaClass'es not linked to a list of
> other JavaClass'es by an "extends" edge.
> This will need some way to keep the blacklists in the graph, and
> then, I can imagine Gremlin taking the part in filtering out the
> vertices linked to them by a set of edge types ("extends", "implements",
> "annotatedBy", "calls", "imports", ...)
>
> And creating a disjunction of all these results, by narrowing the set of
> candidate vertices, step by step.
I think that things like require gremlin queries. It would be logical
for us to build some building blocks for complex queries like this so
that users don't have to fully understand gremlin (and the rather
complex graph structure) for more common operations. For an example, see
the FindClassifiedFilesGremlinCriterion class.
> What I think is a BAD approach, is this kind of rules (outside of Java
> basic analysis):
>
> Query.find(JavaClassModel.class).as("javaClasses")
>
> Iteration.over("javaClasses").as("javaClass").perform(
> ...
> )
>
>
I don't think that anyone has advocated for that type of approach,
outside of the cases where you actually want to iterate over all of the
JavaClassModels in the graph.
From lincolnbaxter at gmail.com Thu Aug 7 14:52:37 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 7 Aug 2014 14:52:37 -0400
Subject: [windup-dev] Negative queries?
In-Reply-To: <53E3C9D7.1080104@redhat.com>
References: <53DAA713.8010700@redhat.com>
<53E3C9D7.1080104@redhat.com>
Message-ID: <CAEp_U4GF4u=XYja6i_ttCYavPFmUh-6Giuzt1vUZp0GB3O9_jA@mail.gmail.com>
I think that negative queries could be added, just like I added
multi-queries in WINDUP-133:
https://github.com/lincolnthree/windup/blob/WINDUP-133/config/api/src/main/java/org/jboss/windup/config/query/QueryPropertyCriterion.java#L33
On Thu, Aug 7, 2014 at 2:47 PM, Jess Sightler <jsightle at redhat.com> wrote:
>
> On 07/31/2014 04:29 PM, Ondrej Zizka wrote:
> > When talking to Robb, we discussed the ability to query for POJO classes
> > - i.e. those which do not have any vendor-specific extension, do not use
> > blacklisted classes, do not extend something "dirty", etc.
> >
> > Which brings us to interesting concept - querying for something "not
> > being a lot of things".
> >
> > We have discussed this briefly on F2F with Brad.
> > The first shot could be:
> >
> > * creating a method which will query for vertexes that have some frame
> > type (JavaClass), but not any other, or a set of other types
> > (WebLogicContextListener).
>
> One issue here is that the Titan Text predicate does not directly
> support negations. I am not sure how easy it would be to add this in a
> performant manner for a negated type search.
>
> I agree that this is a need, though for certain types of queries.
>
> >
> > * querying for vertices which are not linked to vertices in sevral
> > blacklists
> > For example, querying for JavaClass'es not linked to a list of
> > other JavaClass'es by an "extends" edge.
> > This will need some way to keep the blacklists in the graph, and
> > then, I can imagine Gremlin taking the part in filtering out the
> > vertices linked to them by a set of edge types ("extends", "implements",
> > "annotatedBy", "calls", "imports", ...)
> >
> > And creating a disjunction of all these results, by narrowing the set of
> > candidate vertices, step by step.
>
> I think that things like require gremlin queries. It would be logical
> for us to build some building blocks for complex queries like this so
> that users don't have to fully understand gremlin (and the rather
> complex graph structure) for more common operations. For an example, see
> the FindClassifiedFilesGremlinCriterion class.
>
> > What I think is a BAD approach, is this kind of rules (outside of Java
> > basic analysis):
> >
> > Query.find(JavaClassModel.class).as("javaClasses")
> >
> > Iteration.over("javaClasses").as("javaClass").perform(
> > ...
> > )
> >
> >
>
> I don't think that anyone has advocated for that type of approach,
> outside of the cases where you actually want to iterate over all of the
> JavaClassModels in the graph.
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140807/85a39afd/attachment.html
From jsightle at redhat.com Thu Aug 7 15:05:40 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 07 Aug 2014 15:05:40 -0400
Subject: [windup-dev] Negative queries?
In-Reply-To: <CAEp_U4GF4u=XYja6i_ttCYavPFmUh-6Giuzt1vUZp0GB3O9_jA@mail.gmail.com>
References: <53DAA713.8010700@redhat.com> <53E3C9D7.1080104@redhat.com>
<CAEp_U4GF4u=XYja6i_ttCYavPFmUh-6Giuzt1vUZp0GB3O9_jA@mail.gmail.com>
Message-ID: <53E3CE04.906@redhat.com>
I don't think that will be faster than just returning all of the
elements and manually filtering in code, though. A positive search will
hit the lucene index and is generally much faster.
On 08/07/2014 02:52 PM, Lincoln Baxter, III wrote:
> I think that negative queries could be added, just like I added
> multi-queries in WINDUP-133:
> https://github.com/lincolnthree/windup/blob/WINDUP-133/config/api/src/main/java/org/jboss/windup/config/query/QueryPropertyCriterion.java#L33
>
>
> On Thu, Aug 7, 2014 at 2:47 PM, Jess Sightler <jsightle at redhat.com
> <mailto:jsightle at redhat.com>> wrote:
>
>
> On 07/31/2014 04:29 PM, Ondrej Zizka wrote:
> > When talking to Robb, we discussed the ability to query for POJO
> classes
> > - i.e. those which do not have any vendor-specific extension, do
> not use
> > blacklisted classes, do not extend something "dirty", etc.
> >
> > Which brings us to interesting concept - querying for something "not
> > being a lot of things".
> >
> > We have discussed this briefly on F2F with Brad.
> > The first shot could be:
> >
> > * creating a method which will query for vertexes that have some
> frame
> > type (JavaClass), but not any other, or a set of other types
> > (WebLogicContextListener).
>
> One issue here is that the Titan Text predicate does not directly
> support negations. I am not sure how easy it would be to add this in a
> performant manner for a negated type search.
>
> I agree that this is a need, though for certain types of queries.
>
> >
> > * querying for vertices which are not linked to vertices in sevral
> > blacklists
> > For example, querying for JavaClass'es not linked to a list of
> > other JavaClass'es by an "extends" edge.
> > This will need some way to keep the blacklists in the
> graph, and
> > then, I can imagine Gremlin taking the part in filtering out the
> > vertices linked to them by a set of edge types ("extends",
> "implements",
> > "annotatedBy", "calls", "imports", ...)
> >
> > And creating a disjunction of all these results, by narrowing
> the set of
> > candidate vertices, step by step.
>
> I think that things like require gremlin queries. It would be logical
> for us to build some building blocks for complex queries like this so
> that users don't have to fully understand gremlin (and the rather
> complex graph structure) for more common operations. For an
> example, see
> the FindClassifiedFilesGremlinCriterion class.
>
> > What I think is a BAD approach, is this kind of rules (outside
> of Java
> > basic analysis):
> >
> > Query.find(JavaClassModel.class).as("javaClasses")
> >
> > Iteration.over("javaClasses").as("javaClass").perform(
> > ...
> > )
> >
> >
>
> I don't think that anyone has advocated for that type of approach,
> outside of the cases where you actually want to iterate over all
> of the
> JavaClassModels in the graph.
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140807/09d78bb7/attachment.html
From pmuir at redhat.com Thu Aug 7 16:00:39 2014
From: pmuir at redhat.com (Peter Muir)
Date: Thu, 7 Aug 2014 16:00:39 -0400 (EDT)
Subject: [windup-dev] Github PR rebase script // Fwd: Re: Git
pull request automation?
In-Reply-To: <CAEp_U4Hq9VZismuRK1CEjy9v4GkXAUoOq-rhVTrRg46Z+2eBYA@mail.gmail.com>
References: <517FD978.9070700@redhat.com> <53DCC96C.2070806@redhat.com>
<CAEp_U4Hq9VZismuRK1CEjy9v4GkXAUoOq-rhVTrRg46Z+2eBYA@mail.gmail.com>
Message-ID: <1769844729.37171372.1407441639770.JavaMail.zimbra@zmail15.collab.prod.int.phx2.redhat.com>
What Brian is doing is better IMO. With your approach you avoid a few commands but its just syntactic sugar. You still end up with the same thing in your local git (the remote added and the branch downloaded). The PR branch is already in the upstream remote but not fetched by default. Brian is fetching from that, avoiding adding the remote. Though nowadays I've been converted to the way of the big green button. On 7 Aug 2014 19:08, "Lincoln Baxter, III" <lincolnbaxter at gmail.com> wrote:
Whatever works for you :)
You don't need to add the remote, just copy the text from Github... it
tells you how to do it right in the PR (just click "Use thh command line"
to see the instructions)
git checkout -b lincolnthree-WINDUP-133 master
git pull https://github.com/lincolnthree/windup.git WINDUP-133
Then run the tests "mvn clean install", and if they pass:
git checkout master
git merge --no-ff lincolnthree-WINDUP-133
git push origin master
Hope this helps,
~Lincoln
On Sat, Aug 2, 2014 at 7:20 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
> Here is a script which Brian uses to rebase and merge selected PR's.
> Could be handy.
>
> HTH,
> Ondra
>
>
>
>
> -------- Original Message -------- Subject: Re: Git pull request
> automation? Date: Tue, 30 Apr 2013 09:47:20 -0500 From: Brian
> Stansberry <brian.stansberry at redhat.com> <brian.stansberry at redhat.com> To:
> Ondrej Zizka <ozizka at redhat.com> <ozizka at redhat.com> CC: Carlo de Wolf
> <cdewolf at redhat.com> <cdewolf at redhat.com>
>
> AIUI Carlo's team is building some automation around this for EAP.
>
> I have a simple script I use to bring down a bunch of pull requests into
> a single branch.[1] I then push that branch to upstream master-ignore.
> Lightning and Tomaz Cerar's team city test that branch whenever changes
> are made. If that goes well, I merge the branch to master and push.
>
> The other mergers do similar things, probably with better scripts for
> the first bit.
>
> I don't use the requester's remote; the PR is available via the wildfly
> github repo. See the script for details.
>
> [1]
>
> pull() {
> cmd="git fetch upstream master "
> for var in "$@"
> do
> cmd="$cmd pull/$var/head:pullRequest$var"
> done
>
> $cmd
>
> git branch -D pulls
> git checkout master
> git rebase upstream/master
> git checkout -b pulls
>
> for var in "$@"
> do
> git checkout pullRequest$var
> git rebase pulls
> git checkout pulls
> git merge pullRequest$var
> git branch -D pullRequest$var
> done
> }
>
> On 4/30/13 9:16 AM, Ondrej Zizka wrote:
> > Hi Brian,
> >
> > if I want to test and review the pull request before merging, it seems
> > that I have to add the requester's remote, fetch it, check out his
> > branch, then do what I want.
> >
> > With the pace of PRs to AS, I assume you have some automation for this,
> > perhaps through GitHub API. Is that available somewhere?
> > Or how do you proceed when you need to check something in an IDE, or
> > test something not covered by the testsuite, etc?
> >
> > Thanks,
> > Ondra
>
>
> --
> Brian Stansberry
> Principal Software Engineer
> JBoss by Red Hat
>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140807/49d62530/attachment-0001.html
-------------- next part --------------
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Thu Aug 7 20:56:29 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Fri, 08 Aug 2014 02:56:29 +0200
Subject: [windup-dev] 100 MB demo app
Message-ID: <53E4203D.7060209@redhat.com>
Found an interesting relatively large app:
http://sourceforge.net/projects/jbilling/files/latest/download
App: 20 MB
Libs: 80 MB
Includes: Java EE, Spring, JSP, web services, Struts, Grails, Drools,
SiteMesh, Hubernate.
Also what makes it interesting that it contains quite a lot of classes
generated by Grails.
Could be a nice minefield for java stuff - decompiler, BCEL.
Wanna give it a try? :)
Ondra
From lincolnbaxter at gmail.com Fri Aug 8 00:37:09 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 8 Aug 2014 00:37:09 -0400
Subject: [windup-dev] Github PR rebase script // Fwd: Re: Git pull
request automation?
In-Reply-To: <1769844729.37171372.1407441639770.JavaMail.zimbra@zmail15.collab.prod.int.phx2.redhat.com>
References: <517FD978.9070700@redhat.com> <53DCC96C.2070806@redhat.com>
<CAEp_U4Hq9VZismuRK1CEjy9v4GkXAUoOq-rhVTrRg46Z+2eBYA@mail.gmail.com>
<1769844729.37171372.1407441639770.JavaMail.zimbra@zmail15.collab.prod.int.phx2.redhat.com>
Message-ID: <CAEp_U4GC3UYJRbYBDzx-0=+D1pFrRr1RMpLPTvSpdiz+ABSQZQ@mail.gmail.com>
This doesn't add the remote either :)
On Thu, Aug 7, 2014 at 4:00 PM, Peter Muir <pmuir at redhat.com> wrote:
> What Brian is doing is better IMO. With your approach you avoid a few
> commands but its just syntactic sugar. You still end up with the same thing
> in your local git (the remote added and the branch downloaded).
>
> The PR branch is already in the upstream remote but not fetched by
> default. Brian is fetching from that, avoiding adding the remote.
>
> Though nowadays I've been converted to the way of the big green button.
> On 7 Aug 2014 19:08, "Lincoln Baxter, III" <lincolnbaxter at gmail.com>
> wrote:
>
> Whatever works for you :)
>
> You don't need to add the remote, just copy the text from Github... it
> tells you how to do it right in the PR (just click "Use thh command line"
> to see the instructions)
>
> git checkout -b lincolnthree-WINDUP-133 master
> git pull https://github.com/lincolnthree/windup.git WINDUP-133
>
>
> Then run the tests "mvn clean install", and if they pass:
>
> git checkout master
> git merge --no-ff lincolnthree-WINDUP-133
> git push origin master
>
>
> Hope this helps,
> ~Lincoln
>
> On Sat, Aug 2, 2014 at 7:20 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
>
>> Here is a script which Brian uses to rebase and merge selected PR's.
>> Could be handy.
>>
>> HTH,
>> Ondra
>>
>>
>>
>>
>> -------- Original Message -------- Subject: Re: Git pull request
>> automation? Date: Tue, 30 Apr 2013 09:47:20 -0500 From: Brian
>> Stansberry <brian.stansberry at redhat.com> <brian.stansberry at redhat.com> To:
>> Ondrej Zizka <ozizka at redhat.com> <ozizka at redhat.com> CC: Carlo de Wolf
>> <cdewolf at redhat.com> <cdewolf at redhat.com>
>>
>> AIUI Carlo's team is building some automation around this for EAP.
>>
>> I have a simple script I use to bring down a bunch of pull requests into
>> a single branch.[1] I then push that branch to upstream master-ignore.
>> Lightning and Tomaz Cerar's team city test that branch whenever changes
>> are made. If that goes well, I merge the branch to master and push.
>>
>> The other mergers do similar things, probably with better scripts for
>> the first bit.
>>
>> I don't use the requester's remote; the PR is available via the wildfly
>> github repo. See the script for details.
>>
>> [1]
>>
>> pull() {
>> cmd="git fetch upstream master "
>> for var in "$@"
>> do
>> cmd="$cmd pull/$var/head:pullRequest$var"
>> done
>>
>> $cmd
>>
>> git branch -D pulls
>> git checkout master
>> git rebase upstream/master
>> git checkout -b pulls
>>
>> for var in "$@"
>> do
>> git checkout pullRequest$var
>> git rebase pulls
>> git checkout pulls
>> git merge pullRequest$var
>> git branch -D pullRequest$var
>> done
>> }
>>
>> On 4/30/13 9:16 AM, Ondrej Zizka wrote:
>> > Hi Brian,
>> >
>> > if I want to test and review the pull request before merging, it seems
>> > that I have to add the requester's remote, fetch it, check out his
>> > branch, then do what I want.
>> >
>> > With the pace of PRs to AS, I assume you have some automation for this,
>> > perhaps through GitHub API. Is that available somewhere?
>> > Or how do you proceed when you need to check something in an IDE, or
>> > test something not covered by the testsuite, etc?
>> >
>> > Thanks,
>> > Ondra
>>
>>
>> --
>> Brian Stansberry
>> Principal Software Engineer
>> JBoss by Red Hat
>>
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140808/e9525b62/attachment.html
From lincolnbaxter at gmail.com Fri Aug 8 00:37:30 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 8 Aug 2014 00:37:30 -0400
Subject: [windup-dev] Github PR rebase script // Fwd: Re: Git pull
request automation?
In-Reply-To: <CAEp_U4GC3UYJRbYBDzx-0=+D1pFrRr1RMpLPTvSpdiz+ABSQZQ@mail.gmail.com>
References: <517FD978.9070700@redhat.com> <53DCC96C.2070806@redhat.com>
<CAEp_U4Hq9VZismuRK1CEjy9v4GkXAUoOq-rhVTrRg46Z+2eBYA@mail.gmail.com>
<1769844729.37171372.1407441639770.JavaMail.zimbra@zmail15.collab.prod.int.phx2.redhat.com>
<CAEp_U4GC3UYJRbYBDzx-0=+D1pFrRr1RMpLPTvSpdiz+ABSQZQ@mail.gmail.com>
Message-ID: <CAEp_U4EbAwFOB0kJkGr7dfd3SL5=g=mpczR9xyGAMBziOFCvTA@mail.gmail.com>
I just use the button, too, unless I want to run tests.
On Fri, Aug 8, 2014 at 12:37 AM, Lincoln Baxter, III <
lincolnbaxter at gmail.com> wrote:
> This doesn't add the remote either :)
>
>
> On Thu, Aug 7, 2014 at 4:00 PM, Peter Muir <pmuir at redhat.com> wrote:
>
>> What Brian is doing is better IMO. With your approach you avoid a few
>> commands but its just syntactic sugar. You still end up with the same thing
>> in your local git (the remote added and the branch downloaded).
>>
>> The PR branch is already in the upstream remote but not fetched by
>> default. Brian is fetching from that, avoiding adding the remote.
>>
>> Though nowadays I've been converted to the way of the big green button.
>> On 7 Aug 2014 19:08, "Lincoln Baxter, III" <lincolnbaxter at gmail.com>
>> wrote:
>>
>> Whatever works for you :)
>>
>> You don't need to add the remote, just copy the text from Github... it
>> tells you how to do it right in the PR (just click "Use thh command line"
>> to see the instructions)
>>
>> git checkout -b lincolnthree-WINDUP-133 master
>> git pull https://github.com/lincolnthree/windup.git WINDUP-133
>>
>>
>> Then run the tests "mvn clean install", and if they pass:
>>
>> git checkout master
>> git merge --no-ff lincolnthree-WINDUP-133
>> git push origin master
>>
>>
>> Hope this helps,
>> ~Lincoln
>>
>> On Sat, Aug 2, 2014 at 7:20 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
>>
>>> Here is a script which Brian uses to rebase and merge selected PR's.
>>> Could be handy.
>>>
>>> HTH,
>>> Ondra
>>>
>>>
>>>
>>>
>>> -------- Original Message -------- Subject: Re: Git pull request
>>> automation? Date: Tue, 30 Apr 2013 09:47:20 -0500 From: Brian
>>> Stansberry <brian.stansberry at redhat.com> <brian.stansberry at redhat.com> To:
>>> Ondrej Zizka <ozizka at redhat.com> <ozizka at redhat.com> CC: Carlo de Wolf
>>> <cdewolf at redhat.com> <cdewolf at redhat.com>
>>>
>>> AIUI Carlo's team is building some automation around this for EAP.
>>>
>>> I have a simple script I use to bring down a bunch of pull requests into
>>> a single branch.[1] I then push that branch to upstream master-ignore.
>>> Lightning and Tomaz Cerar's team city test that branch whenever changes
>>> are made. If that goes well, I merge the branch to master and push.
>>>
>>> The other mergers do similar things, probably with better scripts for
>>> the first bit.
>>>
>>> I don't use the requester's remote; the PR is available via the wildfly
>>> github repo. See the script for details.
>>>
>>> [1]
>>>
>>> pull() {
>>> cmd="git fetch upstream master "
>>> for var in "$@"
>>> do
>>> cmd="$cmd pull/$var/head:pullRequest$var"
>>> done
>>>
>>> $cmd
>>>
>>> git branch -D pulls
>>> git checkout master
>>> git rebase upstream/master
>>> git checkout -b pulls
>>>
>>> for var in "$@"
>>> do
>>> git checkout pullRequest$var
>>> git rebase pulls
>>> git checkout pulls
>>> git merge pullRequest$var
>>> git branch -D pullRequest$var
>>> done
>>> }
>>>
>>> On 4/30/13 9:16 AM, Ondrej Zizka wrote:
>>> > Hi Brian,
>>> >
>>> > if I want to test and review the pull request before merging, it seems
>>> > that I have to add the requester's remote, fetch it, check out his
>>> > branch, then do what I want.
>>> >
>>> > With the pace of PRs to AS, I assume you have some automation for this,
>>> > perhaps through GitHub API. Is that available somewhere?
>>> > Or how do you proceed when you need to check something in an IDE, or
>>> > test something not covered by the testsuite, etc?
>>> >
>>> > Thanks,
>>> > Ondra
>>>
>>>
>>> --
>>> Brian Stansberry
>>> Principal Software Engineer
>>> JBoss by Red Hat
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
>>
>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140808/670e7378/attachment.html
From lincolnbaxter at gmail.com Fri Aug 8 01:16:39 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 8 Aug 2014 01:16:39 -0400
Subject: [windup-dev] Negative queries?
In-Reply-To: <53E3CE04.906@redhat.com>
References: <53DAA713.8010700@redhat.com> <53E3C9D7.1080104@redhat.com>
<CAEp_U4GF4u=XYja6i_ttCYavPFmUh-6Giuzt1vUZp0GB3O9_jA@mail.gmail.com>
<53E3CE04.906@redhat.com>
Message-ID: <CAEp_U4GsJ+Kb1FDjujjtQs_v-QMGYf_dsz4LMwO7JKF_7kWKxQ@mail.gmail.com>
No, definitely won't ;)
On Thu, Aug 7, 2014 at 3:05 PM, Jess Sightler <jsightle at redhat.com> wrote:
> I don't think that will be faster than just returning all of the elements
> and manually filtering in code, though. A positive search will hit the
> lucene index and is generally much faster.
>
>
> On 08/07/2014 02:52 PM, Lincoln Baxter, III wrote:
>
> I think that negative queries could be added, just like I added
> multi-queries in WINDUP-133:
> https://github.com/lincolnthree/windup/blob/WINDUP-133/config/api/src/main/java/org/jboss/windup/config/query/QueryPropertyCriterion.java#L33
>
>
> On Thu, Aug 7, 2014 at 2:47 PM, Jess Sightler <jsightle at redhat.com> wrote:
>
>>
>> On 07/31/2014 04:29 PM, Ondrej Zizka wrote:
>> > When talking to Robb, we discussed the ability to query for POJO classes
>> > - i.e. those which do not have any vendor-specific extension, do not use
>> > blacklisted classes, do not extend something "dirty", etc.
>> >
>> > Which brings us to interesting concept - querying for something "not
>> > being a lot of things".
>> >
>> > We have discussed this briefly on F2F with Brad.
>> > The first shot could be:
>> >
>> > * creating a method which will query for vertexes that have some frame
>> > type (JavaClass), but not any other, or a set of other types
>> > (WebLogicContextListener).
>>
>> One issue here is that the Titan Text predicate does not directly
>> support negations. I am not sure how easy it would be to add this in a
>> performant manner for a negated type search.
>>
>> I agree that this is a need, though for certain types of queries.
>>
>> >
>> > * querying for vertices which are not linked to vertices in sevral
>> > blacklists
>> > For example, querying for JavaClass'es not linked to a list of
>> > other JavaClass'es by an "extends" edge.
>> > This will need some way to keep the blacklists in the graph, and
>> > then, I can imagine Gremlin taking the part in filtering out the
>> > vertices linked to them by a set of edge types ("extends", "implements",
>> > "annotatedBy", "calls", "imports", ...)
>> >
>> > And creating a disjunction of all these results, by narrowing the set of
>> > candidate vertices, step by step.
>>
>> I think that things like require gremlin queries. It would be logical
>> for us to build some building blocks for complex queries like this so
>> that users don't have to fully understand gremlin (and the rather
>> complex graph structure) for more common operations. For an example, see
>> the FindClassifiedFilesGremlinCriterion class.
>>
>> > What I think is a BAD approach, is this kind of rules (outside of Java
>> > basic analysis):
>> >
>> > Query.find(JavaClassModel.class).as("javaClasses")
>> >
>> > Iteration.over("javaClasses").as("javaClass").perform(
>> > ...
>> > )
>> >
>> >
>>
>> I don't think that anyone has advocated for that type of approach,
>> outside of the cases where you actually want to iterate over all of the
>> JavaClassModels in the graph.
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140808/c3f92377/attachment-0001.html
From pmuir at redhat.com Fri Aug 8 05:37:47 2014
From: pmuir at redhat.com (Pete Muir)
Date: Fri, 8 Aug 2014 10:37:47 +0100
Subject: [windup-dev] Github PR rebase script // Fwd: Re: Git pull
request automation?
In-Reply-To: <CAEp_U4GC3UYJRbYBDzx-0=+D1pFrRr1RMpLPTvSpdiz+ABSQZQ@mail.gmail.com>
References: <517FD978.9070700@redhat.com> <53DCC96C.2070806@redhat.com>
<CAEp_U4Hq9VZismuRK1CEjy9v4GkXAUoOq-rhVTrRg46Z+2eBYA@mail.gmail.com>
<1769844729.37171372.1407441639770.JavaMail.zimbra@zmail15.collab.prod.int.phx2.redhat.com>
<CAEp_U4GC3UYJRbYBDzx-0=+D1pFrRr1RMpLPTvSpdiz+ABSQZQ@mail.gmail.com>
Message-ID: <0FFC6097-3F87-4E7B-9A15-421433CF3DE7@redhat.com>
Who knew! (well, not me, but obviously Lincoln ;-).
On 8 Aug 2014, at 05:37, Lincoln Baxter, III <lincolnbaxter at gmail.com> wrote:
> This doesn't add the remote either :)
>
>
> On Thu, Aug 7, 2014 at 4:00 PM, Peter Muir <pmuir at redhat.com> wrote:
> What Brian is doing is better IMO. With your approach you avoid a few commands but its just syntactic sugar. You still end up with the same thing in your local git (the remote added and the branch downloaded).
>
> The PR branch is already in the upstream remote but not fetched by default. Brian is fetching from that, avoiding adding the remote.
>
> Though nowadays I've been converted to the way of the big green button.
>
> On 7 Aug 2014 19:08, "Lincoln Baxter, III" <lincolnbaxter at gmail.com> wrote:
>
> Whatever works for you :)
>
> You don't need to add the remote, just copy the text from Github... it tells you how to do it right in the PR (just click "Use thh command line" to see the instructions)
>
> git checkout -b lincolnthree-WINDUP-133 master
> git pull
> https://github.com/lincolnthree/windup.git WINDUP-133
>
> Then run the tests "mvn clean install", and if they pass:
>
> git checkout master
> git merge --no-ff lincolnthree-WINDUP-133
> git push origin master
>
>
> Hope this helps,
> ~Lincoln
>
> On Sat, Aug 2, 2014 at 7:20 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
> Here is a script which Brian uses to rebase and merge selected PR's.
> Could be handy.
>
> HTH,
> Ondra
>
>
>
>
> -------- Original Message --------
> Subject: Re: Git pull request automation?
> Date: Tue, 30 Apr 2013 09:47:20 -0500
> From: Brian Stansberry <brian.stansberry at redhat.com>
> To: Ondrej Zizka <ozizka at redhat.com>
> CC: Carlo de Wolf <cdewolf at redhat.com>
>
> AIUI Carlo's team is building some automation around this for EAP.
>
> I have a simple script I use to bring down a bunch of pull requests into
> a single branch.[1] I then push that branch to upstream master-ignore.
> Lightning and Tomaz Cerar's team city test that branch whenever changes
> are made. If that goes well, I merge the branch to master and push.
>
> The other mergers do similar things, probably with better scripts for
> the first bit.
>
> I don't use the requester's remote; the PR is available via the wildfly
> github repo. See the script for details.
>
> [1]
>
> pull() {
> cmd="git fetch upstream master "
> for var in "$@"
> do
> cmd="$cmd pull/$var/head:pullRequest$var"
> done
>
> $cmd
>
> git branch -D pulls
> git checkout master
> git rebase upstream/master
> git checkout -b pulls
>
> for var in "$@"
> do
> git checkout pullRequest$var
> git rebase pulls
> git checkout pulls
> git merge pullRequest$var
> git branch -D pullRequest$var
> done
> }
>
> On 4/30/13 9:16 AM, Ondrej Zizka wrote:
> > Hi Brian,
> >
> > if I want to test and review the pull request before merging, it seems
> > that I have to add the requester's remote, fetch it, check out his
> > branch, then do what I want.
> >
> > With the pace of PRs to AS, I assume you have some automation for this,
> > perhaps through GitHub API. Is that available somewhere?
> > Or how do you proceed when you need to check something in an IDE, or
> > test something not covered by the testsuite, etc?
> >
> > Thanks,
> > Ondra
>
>
> --
> Brian Stansberry
> Principal Software Engineer
> JBoss by Red Hat
>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From windup-dev at lists.jboss.org Sat Aug 9 18:07:21 2014
From: windup-dev at lists.jboss.org (windup-dev at lists.jboss.org)
Date: Sat, 09 Aug 2014 18:07:21 EDT
Subject: [windup-dev] Is windup for real?
Message-ID: <1584565155.01407622073010.JavaMail.jive@jive-app01.app.mwc.hst.phx2.redhat.com>
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
From bdavis at redhat.com Sat Aug 9 18:41:17 2014
From: bdavis at redhat.com (Brad Davis)
Date: Sat, 9 Aug 2014 18:41:17 -0400 (EDT)
Subject: [windup-dev] Is windup for real?
In-Reply-To: <1584565155.01407622073010.JavaMail.jive@jive-app01.app.mwc.hst.phx2.redhat.com>
References: <1584565155.01407622073010.JavaMail.jive@jive-app01.app.mwc.hst.phx2.redhat.com>
Message-ID: <C6EDD587-D968-490C-ADDD-43D737FC26B7@redhat.com>
We are happy to look at your stack trace and solving that if you would rather. Otherwise, if you want to DEVELOP windup, check out the source, solve the stack trace, and send a pull request.
Brad Davis
Red Hat Consulting
Email: bdavis at redhat.com | c:980.226.7865 |http://www.redhat.com
> On Aug 9, 2014, at 6:07 PM, windup-dev at lists.jboss.org wrote:
>
> 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
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140809/97fcf55c/attachment.html
From ozizka at redhat.com Sun Aug 10 19:28:27 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 11 Aug 2014 01:28:27 +0200
Subject: [windup-dev] Is windup for real?
In-Reply-To: <C6EDD587-D968-490C-ADDD-43D737FC26B7@redhat.com>
References: <1584565155.01407622073010.JavaMail.jive@jive-app01.app.mwc.hst.phx2.redhat.com>
<C6EDD587-D968-490C-ADDD-43D737FC26B7@redhat.com>
Message-ID: <53E8001B.5090905@redhat.com>
Steve,
I don't have your address, so just sending to the list.
In addition to Brad's reply:
You probably used what we call Windup-legacy, which could be useful for
your current task.
Then there is Windup 2.0, currently under development.
Sparse information at https://github.com/windup/windup/wiki/ .
To advance the state of the art, for now we would be glad if you
collected notes about what and how was migrated, so we can capture it in
the automated rules when Windup 2.0 gets released.
Regards,
Ondra
On 10.8.2014 00:41, Brad Davis wrote:
> We are happy to look at your stack trace and solving that if you would
> rather. Otherwise, if you want to DEVELOP windup, check out the
> source, solve the stack trace, and send a pull request.
>
> Brad Davis
> Red Hat Consulting
> Email: bdavis at redhat.com <mailto:bdavis at redhat.com> | c:980.226.7865
> <tel:980.226.7865> |http://www.redhat.com <http://www.redhat.com/>
>
> On Aug 9, 2014, at 6:07 PM, windup-dev at lists.jboss.org
> <mailto:windup-dev at lists.jboss.org> wrote:
>
>> 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
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140811/f630979b/attachment.html
From ozizka at redhat.com Sun Aug 10 23:00:19 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 11 Aug 2014 05:00:19 +0200
Subject: [windup-dev] Let's use relative paths
Message-ID: <53E831C3.7080903@redhat.com>
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
From ozizka at redhat.com Sun Aug 10 23:30:16 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 11 Aug 2014 05:30:16 +0200
Subject: [windup-dev] Reporting exceptions
Message-ID: <53E838C8.10206@redhat.com>
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
From ozizka at redhat.com Mon Aug 11 02:05:38 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 11 Aug 2014 08:05:38 +0200
Subject: [windup-dev] EventGraph
Message-ID: <53E85D32.7000106@redhat.com>
Hi,
what do we need EventGraph for?
GraphContextImpl.java:
this.titanGraph = TitanFactory.open(conf);
this.eventGraph = new EventGraph<TitanGraph>(this.titanGraph);
Thanks,
Ondra
From ozizka at redhat.com Mon Aug 11 02:05:59 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 11 Aug 2014 08:05:59 +0200
Subject: [windup-dev] Iteration using Java's for?
In-Reply-To: <53D293BF.4050603@redhat.com>
References: <53D29346.3090601@redhat.com> <53D293BF.4050603@redhat.com>
Message-ID: <53E85D47.1080308@redhat.com>
On 25.7.2014 19:28, Ondrej Zizka wrote:
> Subquestions:
> Do we want to / can we restrict the Groovy DSL syntax anyhow?
> Will we aim for alternative XML-based rules which would translate to the
> API?
>
>
> On 25.7.2014 19:26, Ondrej Zizka wrote:
>> 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
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From bdavis at redhat.com Mon Aug 11 09:52:31 2014
From: bdavis at redhat.com (Brad Davis)
Date: Mon, 11 Aug 2014 09:52:31 -0400 (EDT)
Subject: [windup-dev] Is windup for real?
In-Reply-To: <C6EDD587-D968-490C-ADDD-43D737FC26B7@redhat.com>
References: <1584565155.01407622073010.JavaMail.jive@jive-app01.app.mwc.hst.phx2.redhat.com>
<C6EDD587-D968-490C-ADDD-43D737FC26B7@redhat.com>
Message-ID: <1036228334.9090695.1407765151953.JavaMail.zimbra@redhat.com>
Steve,
I wanted to readdress your issues today.
1) You can download the Windup 1.x executable from windup.jboss.org
- Click "Download Now" @ http://windup.jboss.org/download.html
2) Watch this video on how to Run Windup:
- https://www.youtube.com/embed/NwbTmWxZ3XI
3) There are other videos on the Guides page that describe how you read the reports.
- http://windup.jboss.org/guides.html
4) There are two modes for running Windup: You can run against the source, or you can run against the deployable. Both are documented on the guides page at the bottom:
- URL: http://windup.jboss.org/guides.html
- See: Quick Guide: Running Windup on Source
- See: Quick Guide: Running Windup on Archives
Let me know if you run into problems with the Windup 1.x executable. The 2.x codebase on Github is the alpha branch, and isn't anticipated for final release until October.
Thanks,
Brad Davis
Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Brad Davis" <bdavis at redhat.com>
To: windup-dev at lists.jboss.org
Sent: Saturday, August 9, 2014 6:41:17 PM
Subject: Re: [windup-dev] Is windup for real?
We are happy to look at your stack trace and solving that if you would rather. Otherwise, if you want to DEVELOP windup, check out the source, solve the stack trace, and send a pull request.
Brad Davis
Red Hat Consulting
Email: bdavis at redhat.com | c:980.226.7865 |http://www.redhat.com
> On Aug 9, 2014, at 6:07 PM, windup-dev at lists.jboss.org wrote:
>
> 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
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From lincolnbaxter at gmail.com Mon Aug 11 09:55:16 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 11 Aug 2014 09:55:16 -0400
Subject: [windup-dev] Let's use relative paths
In-Reply-To: <53E831C3.7080903@redhat.com>
References: <53E831C3.7080903@redhat.com>
Message-ID: <CAEp_U4Gm02MZ02z8GPua=6TDQHFHehR0FPCdcXMwgeBbXrq+2A@mail.gmail.com>
I agree that relative paths are a good idea. +1
On Sun, Aug 10, 2014 at 11:00 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
> 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
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140811/5a62117f/attachment.html
From bdavis at redhat.com Mon Aug 11 10:22:18 2014
From: bdavis at redhat.com (Brad Davis)
Date: Mon, 11 Aug 2014 10:22:18 -0400 (EDT)
Subject: [windup-dev] Let's use relative paths
In-Reply-To: <CAEp_U4Gm02MZ02z8GPua=6TDQHFHehR0FPCdcXMwgeBbXrq+2A@mail.gmail.com>
References: <53E831C3.7080903@redhat.com>
<CAEp_U4Gm02MZ02z8GPua=6TDQHFHehR0FPCdcXMwgeBbXrq+2A@mail.gmail.com>
Message-ID: <131056505.9111601.1407766938546.JavaMail.zimbra@redhat.com>
+1.
Brad Davis
Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com>
To: "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Monday, August 11, 2014 9:55:16 AM
Subject: Re: [windup-dev] Let's use relative paths
I agree that relative paths are a good idea. +1
On Sun, Aug 10, 2014 at 11:00 PM, Ondrej Zizka < ozizka at redhat.com > wrote:
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
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
From jsightle at redhat.com Mon Aug 11 10:38:38 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Mon, 11 Aug 2014 10:38:38 -0400
Subject: [windup-dev] Let's use relative paths
In-Reply-To: <53E831C3.7080903@redhat.com>
References: <53E831C3.7080903@redhat.com>
Message-ID: <53E8D56E.1050203@redhat.com>
For presentation to the user, I agree. I assume that is what you are
talking about here?
On 08/10/2014 11:00 PM, Ondrej Zizka wrote:
> 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
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From jsightle at redhat.com Mon Aug 11 10:42:46 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Mon, 11 Aug 2014 10:42:46 -0400
Subject: [windup-dev] EventGraph
In-Reply-To: <53E85D32.7000106@redhat.com>
References: <53E85D32.7000106@redhat.com>
Message-ID: <53E8D666.3030706@redhat.com>
You seemed pretty interested in them a while back (when you were talking
about RuleModel, etc). :)
On 08/11/2014 02:05 AM, Ondrej Zizka wrote:
> Hi,
>
> what do we need EventGraph for?
>
> GraphContextImpl.java:
>
> this.titanGraph = TitanFactory.open(conf);
> this.eventGraph = new EventGraph<TitanGraph>(this.titanGraph);
>
> Thanks,
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From jsightle at redhat.com Mon Aug 11 11:00:43 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Mon, 11 Aug 2014 11:00:43 -0400
Subject: [windup-dev] Reporting exceptions
In-Reply-To: <53E838C8.10206@redhat.com>
References: <53E838C8.10206@redhat.com>
Message-ID: <53E8DA9B.1000008@redhat.com>
Yes, I think if the exception came from malformed input files (invalid
XML, invalid Java source, etc), then this is definitely what we should
be doing.
On 08/10/2014 11:30 PM, Ondrej Zizka wrote:
> 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
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Tue Aug 12 01:11:33 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Tue, 12 Aug 2014 07:11:33 +0200
Subject: [windup-dev] Let's use relative paths
In-Reply-To: <53E8D56E.1050203@redhat.com>
References: <53E831C3.7080903@redhat.com> <53E8D56E.1050203@redhat.com>
Message-ID: <53E9A205.1000309@redhat.com>
Yes, in the end, it's for presentation.
But that means we need to use them internally too, otherwise they would
get lost on the way.
For example:
We have archive foo.war.
Extract it to $CWD/tmp/appsExtracted/foo.war/ (made up)
It has a lib.jar, to be extracted to
$CWD/tmp/appsExtracted/foo.war-lib.jar (made up).
To keep the relative information, we need to carry the relative paths,
and the context of what belongs under what.
Otherwise we would have to re-compute the paths during reporting phase,
which would be even harder to do right, IMO.
Ondra
On 11.8.2014 16:38, Jess Sightler wrote:
> For presentation to the user, I agree. I assume that is what you are
> talking about here?
>
> On 08/10/2014 11:00 PM, Ondrej Zizka wrote:
>> 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
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Tue Aug 12 01:16:29 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Tue, 12 Aug 2014 07:16:29 +0200
Subject: [windup-dev] EventGraph
In-Reply-To: <53E8D666.3030706@redhat.com>
References: <53E85D32.7000106@redhat.com> <53E8D666.3030706@redhat.com>
Message-ID: <53E9A32D.5050602@redhat.com>
I'm not sure I was specifically interested in events, I'd use those for
a long-running multi-user app, but for Windup...
But maybe I was, let me think... :)
Either way, what I ment was - do we need them now? AKA, do we use them?
Thanks,
Ondra
On 11.8.2014 16:42, Jess Sightler wrote:
> You seemed pretty interested in them a while back (when you were talking
> about RuleModel, etc). :)
>
> On 08/11/2014 02:05 AM, Ondrej Zizka wrote:
>> Hi,
>>
>> what do we need EventGraph for?
>>
>> GraphContextImpl.java:
>>
>> this.titanGraph = TitanFactory.open(conf);
>> this.eventGraph = new EventGraph<TitanGraph>(this.titanGraph);
>>
>> Thanks,
>> Ondra
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From zizka at seznam.cz Tue Aug 12 01:47:32 2014
From: zizka at seznam.cz (=?UTF-8?B?IkluZy4gT25kxZllaiDFvWnFvmthIg==?=)
Date: Tue, 12 Aug 2014 07:47:32 +0200
Subject: [windup-dev] Leave IDE files in place please
Message-ID: <53E9AA74.3090405@seznam.cz>
https://github.com/jsight/windup/commit/75e4da40b504bdc688fb4e06785f25885610c657
Why can't NetBeans file stay?
Why eclipse file can then?
Regards,
Ondra
From lincolnbaxter at gmail.com Tue Aug 12 11:16:16 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 12 Aug 2014 11:16:16 -0400
Subject: [windup-dev] Leave IDE files in place please
In-Reply-To: <53E9AA74.3090405@seznam.cz>
References: <53E9AA74.3090405@seznam.cz>
Message-ID: <CAEp_U4FpSvP=pAN8DTi_VgBZ8an4s1u3j9a8UtPisE+g+=_RUQ@mail.gmail.com>
Hey Ondra,
Which eclipse files are you referring to? We shouldn't have any eclipse
project metadata in the repository.
Thanks!
~Lincoln
On Tue, Aug 12, 2014 at 1:47 AM, "Ing. Ond?ej ?i?ka" <zizka at seznam.cz>
wrote:
>
> https://github.com/jsight/windup/commit/75e4da40b504bdc688fb4e06785f25885610c657
>
>
> Why can't NetBeans file stay?
> Why eclipse file can then?
>
> Regards,
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140812/2eb694db/attachment.html
From jsightle at redhat.com Tue Aug 12 14:15:48 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Tue, 12 Aug 2014 14:15:48 -0400
Subject: [windup-dev] Leave IDE files in place please
In-Reply-To: <CAEp_U4FpSvP=pAN8DTi_VgBZ8an4s1u3j9a8UtPisE+g+=_RUQ@mail.gmail.com>
References: <53E9AA74.3090405@seznam.cz>
<CAEp_U4FpSvP=pAN8DTi_VgBZ8an4s1u3j9a8UtPisE+g+=_RUQ@mail.gmail.com>
Message-ID: <53EA59D4.8040600@redhat.com>
We have an Eclipse formatting profile, and that is the only one that I
am aware of. If there is something of similar value that would be
helpful for opening the project in Netbeans, I wouldn't be opposed to it
personally.
I would prefer a separate PR, though (with some justification).
On 08/12/2014 11:16 AM, Lincoln Baxter, III wrote:
> Hey Ondra,
>
> Which eclipse files are you referring to? We shouldn't have any
> eclipse project metadata in the repository.
>
> Thanks!
> ~Lincoln
>
>
> On Tue, Aug 12, 2014 at 1:47 AM, "Ing. Ondr(ej Z(iz(ka"
> <zizka at seznam.cz <mailto:zizka at seznam.cz>> wrote:
>
> https://github.com/jsight/windup/commit/75e4da40b504bdc688fb4e06785f25885610c657
>
>
> Why can't NetBeans file stay?
> Why eclipse file can then?
>
> Regards,
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140812/e59c8758/attachment.html
From jsightle at redhat.com Tue Aug 12 14:24:56 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Tue, 12 Aug 2014 14:24:56 -0400
Subject: [windup-dev] EventGraph
In-Reply-To: <53E9A32D.5050602@redhat.com>
References: <53E85D32.7000106@redhat.com> <53E8D666.3030706@redhat.com>
<53E9A32D.5050602@redhat.com>
Message-ID: <53EA5BF8.9060108@redhat.com>
Because this type of thing leaks into the public API with
Tinkerpop/Titan, I would prefer to merge something like this earlier
rather than later. Otherwise it involves more refactoring down the road.
Your previous email said this:
"1) A reference to the rule being executed could be made accessible from
a context.
2) Some layer above Frames could catch any creation/alteration of
vertices and link them.
Haven't seen Frames guts, perhaps not doable easily at the moment."
If that wasn't talking about event handling, I don't know what it was
talking about. :)
On 08/12/2014 01:16 AM, Ondrej Zizka wrote:
> I'm not sure I was specifically interested in events, I'd use those for
> a long-running multi-user app, but for Windup...
> But maybe I was, let me think... :)
>
> Either way, what I ment was - do we need them now? AKA, do we use them?
>
> Thanks,
> Ondra
>
>
> On 11.8.2014 16:42, Jess Sightler wrote:
>> You seemed pretty interested in them a while back (when you were talking
>> about RuleModel, etc). :)
>>
>> On 08/11/2014 02:05 AM, Ondrej Zizka wrote:
>>> Hi,
>>>
>>> what do we need EventGraph for?
>>>
>>> GraphContextImpl.java:
>>>
>>> this.titanGraph = TitanFactory.open(conf);
>>> this.eventGraph = new EventGraph<TitanGraph>(this.titanGraph);
>>>
>>> Thanks,
>>> Ondra
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From jsightle at redhat.com Tue Aug 12 14:27:13 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Tue, 12 Aug 2014 14:27:13 -0400
Subject: [windup-dev] Let's use relative paths
In-Reply-To: <53E9A205.1000309@redhat.com>
References: <53E831C3.7080903@redhat.com> <53E8D56E.1050203@redhat.com>
<53E9A205.1000309@redhat.com>
Message-ID: <53EA5C81.9030604@redhat.com>
For the most part, we should be using absolute (canonicalized) paths
internally, as otherwise path comparisons can become difficult. You are
definitely right that we need to track things like archive
relationships, though (we already do this), as we need to be able to
figure out the relative paths later on.
Fortunately, we already do that. :)
On 08/12/2014 01:11 AM, Ondrej Zizka wrote:
> Yes, in the end, it's for presentation.
> But that means we need to use them internally too, otherwise they would
> get lost on the way.
>
> For example:
> We have archive foo.war.
> Extract it to $CWD/tmp/appsExtracted/foo.war/ (made up)
> It has a lib.jar, to be extracted to
> $CWD/tmp/appsExtracted/foo.war-lib.jar (made up).
> To keep the relative information, we need to carry the relative paths,
> and the context of what belongs under what.
> Otherwise we would have to re-compute the paths during reporting phase,
> which would be even harder to do right, IMO.
>
> Ondra
>
>
> On 11.8.2014 16:38, Jess Sightler wrote:
>> For presentation to the user, I agree. I assume that is what you are
>> talking about here?
>>
>> On 08/10/2014 11:00 PM, Ondrej Zizka wrote:
>>> 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
>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Wed Aug 13 05:49:42 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 13 Aug 2014 11:49:42 +0200
Subject: [windup-dev] Leave IDE files in place please
In-Reply-To: <53EA59D4.8040600@redhat.com>
References: <53E9AA74.3090405@seznam.cz> <CAEp_U4FpSvP=pAN8DTi_VgBZ8an4s1u3j9a8UtPisE+g+=_RUQ@mail.gmail.com>
<53EA59D4.8040600@redhat.com>
Message-ID: <53EB34B6.6020203@redhat.com>
That file contains maping of IDE actions (build, clean & build) to maven
goals and properties. This makes launching tests, debugging, rebuilding
etc. a bit easier.
Not necessary to be in repo, but helps.
Just asking about the policy.
Thanks,
Ondra
On 12.8.2014 20:15, Jess Sightler wrote:
> We have an Eclipse formatting profile, and that is the only one that I
> am aware of. If there is something of similar value that would be
> helpful for opening the project in Netbeans, I wouldn't be opposed to
> it personally.
>
> I would prefer a separate PR, though (with some justification).
>
> On 08/12/2014 11:16 AM, Lincoln Baxter, III wrote:
>> Hey Ondra,
>>
>> Which eclipse files are you referring to? We shouldn't have any
>> eclipse project metadata in the repository.
>>
>> Thanks!
>> ~Lincoln
>>
>>
>> On Tue, Aug 12, 2014 at 1:47 AM, "Ing. Ondr(ej Z(iz(ka"
>> <zizka at seznam.cz <mailto:zizka at seznam.cz>> wrote:
>>
>> https://github.com/jsight/windup/commit/75e4da40b504bdc688fb4e06785f25885610c657
>>
>>
>> Why can't NetBeans file stay?
>> Why eclipse file can then?
>>
>> Regards,
>> Ondra
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140813/e3e01b52/attachment-0001.html
From ozizka at redhat.com Wed Aug 13 05:53:06 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 13 Aug 2014 11:53:06 +0200
Subject: [windup-dev] EventGraph
In-Reply-To: <53EA5BF8.9060108@redhat.com>
References: <53E85D32.7000106@redhat.com>
<53E8D666.3030706@redhat.com> <53E9A32D.5050602@redhat.com>
<53EA5BF8.9060108@redhat.com>
Message-ID: <53EB3582.6020202@redhat.com>
On 12.8.2014 20:24, Jess Sightler wrote:
> Your previous email said this:
> "1) A reference to the rule being executed could be made accessible from
> a context.
> 2) Some layer above Frames could catch any creation/alteration of
> vertices and link them.
>
> Haven't seen Frames guts, perhaps not doable easily at the moment."
>
> If that wasn't talking about event handling, I don't know what it was
> talking about. :)
Aaah right. Thanks for reminding :) Will try soon.
Ondra
>
>
> On 08/12/2014 01:16 AM, Ondrej Zizka wrote:
>> I'm not sure I was specifically interested in events, I'd use those for
>> a long-running multi-user app, but for Windup...
>> But maybe I was, let me think... :)
>>
>> Either way, what I ment was - do we need them now? AKA, do we use them?
>>
>> Thanks,
>> Ondra
>>
>>
>> On 11.8.2014 16:42, Jess Sightler wrote:
>>> You seemed pretty interested in them a while back (when you were talking
>>> about RuleModel, etc). :)
>>>
>>> On 08/11/2014 02:05 AM, Ondrej Zizka wrote:
>>>> Hi,
>>>>
>>>> what do we need EventGraph for?
>>>>
>>>> GraphContextImpl.java:
>>>>
>>>> this.titanGraph = TitanFactory.open(conf);
>>>> this.eventGraph = new EventGraph<TitanGraph>(this.titanGraph);
>>>>
>>>> Thanks,
>>>> Ondra
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Wed Aug 13 06:28:38 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 13 Aug 2014 12:28:38 +0200
Subject: [windup-dev] Let's use relative paths
In-Reply-To: <53EA5C81.9030604@redhat.com>
References: <53E831C3.7080903@redhat.com>
<53E8D56E.1050203@redhat.com> <53E9A205.1000309@redhat.com>
<53EA5C81.9030604@redhat.com>
Message-ID: <53EB3DD6.2070408@redhat.com>
On 12.8.2014 20:27, Jess Sightler wrote:
> For the most part, we should be using absolute (canonicalized) paths
> internally, as otherwise path comparisons can become difficult.
I don't think so.
We basically only have these paths:
* User input (archives, source dirs, server dirs) - should be kept both
relative and absolute. [1]
* Any path under these - should be kept relative.
* Unzipped archives temp dirs - should be kept absolute.
* Any path under these - should be kept relative.
[1] - the user will put relative path to the archive, e.g. bin/windup.sh
../apps/MyApp.war
and may expect to see this path in the report, too.
Reasons to keep the paths relative:
1) Shorter, more effective to store.
2) Shorter, less space wasted.
3) No need to relativize paths across different archives.
4) Path comparisons of relative sub-paths are as difficult as doing that
with absolute paths.
5) The paths in archives are given by the archive, not by location of
our unzipped temp file. Showing relative path makes it less transparent.
Working with absolute and then cutting them by the temp dir doesn't give
any advantage.
my2c,
Ondra
> You are
> definitely right that we need to track things like archive
> relationships, though (we already do this), as we need to be able to
> figure out the relative paths later on.
>
> Fortunately, we already do that. :)
>
>
> On 08/12/2014 01:11 AM, Ondrej Zizka wrote:
>> Yes, in the end, it's for presentation.
>> But that means we need to use them internally too, otherwise they would
>> get lost on the way.
>>
>> For example:
>> We have archive foo.war.
>> Extract it to $CWD/tmp/appsExtracted/foo.war/ (made up)
>> It has a lib.jar, to be extracted to
>> $CWD/tmp/appsExtracted/foo.war-lib.jar (made up).
>> To keep the relative information, we need to carry the relative paths,
>> and the context of what belongs under what.
>> Otherwise we would have to re-compute the paths during reporting phase,
>> which would be even harder to do right, IMO.
>>
>> Ondra
>>
>>
>> On 11.8.2014 16:38, Jess Sightler wrote:
>>> For presentation to the user, I agree. I assume that is what you are
>>> talking about here?
>>>
>>> On 08/10/2014 11:00 PM, Ondrej Zizka wrote:
>>>> 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
>>>>
>>>> _______________________________________________
>>>> windup-dev mailing list
>>>> windup-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Wed Aug 13 07:33:36 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 13 Aug 2014 13:33:36 +0200
Subject: [windup-dev] Leave IDE files in place please
In-Reply-To: <53EB34B6.6020203@redhat.com>
References: <53E9AA74.3090405@seznam.cz> <CAEp_U4FpSvP=pAN8DTi_VgBZ8an4s1u3j9a8UtPisE+g+=_RUQ@mail.gmail.com> <53EA59D4.8040600@redhat.com>
<53EB34B6.6020203@redhat.com>
Message-ID: <53EB4D10.4010009@redhat.com>
Or let me cite from the deleted file:
<!--
This file contains additional configuration written by modules in the
NetBeans IDE.
The configuration is intended to be shared among all the users of
project and
therefore it is assumed to be part of version control checkout.
Without this configuration present, some functionality in the IDE may be
limited or fail altogether.
-->
On 13.8.2014 11:49, Ondrej Zizka wrote:
> That file contains maping of IDE actions (build, clean & build) to
> maven goals and properties. This makes launching tests, debugging,
> rebuilding etc. a bit easier.
> Not necessary to be in repo, but helps.
> Just asking about the policy.
>
> Thanks,
> Ondra
>
>
> On 12.8.2014 20:15, Jess Sightler wrote:
>> We have an Eclipse formatting profile, and that is the only one that
>> I am aware of. If there is something of similar value that would be
>> helpful for opening the project in Netbeans, I wouldn't be opposed to
>> it personally.
>>
>> I would prefer a separate PR, though (with some justification).
>>
>> On 08/12/2014 11:16 AM, Lincoln Baxter, III wrote:
>>> Hey Ondra,
>>>
>>> Which eclipse files are you referring to? We shouldn't have any
>>> eclipse project metadata in the repository.
>>>
>>> Thanks!
>>> ~Lincoln
>>>
>>>
>>> On Tue, Aug 12, 2014 at 1:47 AM, "Ing. Ondr(ej Z(iz(ka"
>>> <zizka at seznam.cz <mailto:zizka at seznam.cz>> wrote:
>>>
>>> https://github.com/jsight/windup/commit/75e4da40b504bdc688fb4e06785f25885610c657
>>>
>>>
>>> Why can't NetBeans file stay?
>>> Why eclipse file can then?
>>>
>>> Regards,
>>> Ondra
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
>>>
>>>
>>>
>>> --
>>> Lincoln Baxter, III
>>> http://ocpsoft.org
>>> "Simpler is better."
>>>
>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140813/f55faa8a/attachment.html
From ozizka at redhat.com Wed Aug 13 07:34:39 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 13 Aug 2014 13:34:39 +0200
Subject: [windup-dev] Bootstrap
Message-ID: <53EB4D4F.7080302@redhat.com>
I'd like to discuss:
WINDUP-204 Implement normal bootstrap
<https://issues.jboss.org/browse/WINDUP-204>
Ondra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140813/5df9c24f/attachment.html
From jsightle at redhat.com Wed Aug 13 10:12:16 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Wed, 13 Aug 2014 10:12:16 -0400
Subject: [windup-dev] Leave IDE files in place please
In-Reply-To: <53EB34B6.6020203@redhat.com>
References: <53E9AA74.3090405@seznam.cz> <CAEp_U4FpSvP=pAN8DTi_VgBZ8an4s1u3j9a8UtPisE+g+=_RUQ@mail.gmail.com> <53EA59D4.8040600@redhat.com>
<53EB34B6.6020203@redhat.com>
Message-ID: <53EB7240.4050401@redhat.com>
I don't have an issue with that file being in the repo. I can see
potential value there. WDYT Lincoln?
On 08/13/2014 05:49 AM, Ondrej Zizka wrote:
> That file contains maping of IDE actions (build, clean & build) to
> maven goals and properties. This makes launching tests, debugging,
> rebuilding etc. a bit easier.
> Not necessary to be in repo, but helps.
> Just asking about the policy.
>
> Thanks,
> Ondra
>
>
> On 12.8.2014 20:15, Jess Sightler wrote:
>> We have an Eclipse formatting profile, and that is the only one that
>> I am aware of. If there is something of similar value that would be
>> helpful for opening the project in Netbeans, I wouldn't be opposed to
>> it personally.
>>
>> I would prefer a separate PR, though (with some justification).
>>
>> On 08/12/2014 11:16 AM, Lincoln Baxter, III wrote:
>>> Hey Ondra,
>>>
>>> Which eclipse files are you referring to? We shouldn't have any
>>> eclipse project metadata in the repository.
>>>
>>> Thanks!
>>> ~Lincoln
>>>
>>>
>>> On Tue, Aug 12, 2014 at 1:47 AM, "Ing. Ondr(ej Z(iz(ka"
>>> <zizka at seznam.cz <mailto:zizka at seznam.cz>> wrote:
>>>
>>> https://github.com/jsight/windup/commit/75e4da40b504bdc688fb4e06785f25885610c657
>>>
>>>
>>> Why can't NetBeans file stay?
>>> Why eclipse file can then?
>>>
>>> Regards,
>>> Ondra
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
>>>
>>>
>>>
>>> --
>>> Lincoln Baxter, III
>>> http://ocpsoft.org
>>> "Simpler is better."
>>>
>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140813/02c95493/attachment-0001.html
From lincolnbaxter at gmail.com Wed Aug 13 11:49:10 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 13 Aug 2014 11:49:10 -0400
Subject: [windup-dev] Windup Meeting Minutes - 2014-08-13
Message-ID: <CAEp_U4FZ8MGwyiwhS6RVKG93diGbqiJ-eRhF27LC8WiQ1X7fRQ@mail.gmail.com>
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-08-13-14.14.html
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-08-13-14.14.txt
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-08-13-14.14.log.html
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."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140813/c0707e7f/attachment.html
From ozizka at redhat.com Thu Aug 14 02:27:56 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 14 Aug 2014 08:27:56 +0200
Subject: [windup-dev] CWD in target/ - what are the issues?
Message-ID: <53EC56EC.9010409@redhat.com>
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
From ozizka at redhat.com Thu Aug 14 04:43:12 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 14 Aug 2014 10:43:12 +0200
Subject: [windup-dev] Jira module: Bootstrap
Message-ID: <53EC76A0.4060306@redhat.com>
Lincoln, could you please add Bootstrap jira module?
Thx,Ondra
From lincolnbaxter at gmail.com Thu Aug 14 16:01:24 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 14 Aug 2014 16:01:24 -0400
Subject: [windup-dev] Windup JIRA Triage Part 1 - Meeting Notes
Message-ID: <CAEp_U4FxmPGcH0f_s8y12Uqn-TW_Fe23Hbz-_1kuoJgKCF7qPw@mail.gmail.com>
Minutes: \
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-08-14-14.43.html
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-08-14-14.43.txt
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-08-14-14.43.log.html
Meeting summary
---------------
* JIRA Triage Round 1 (lincolnthree, 14:44:03)
* LINK:
https://issues.jboss.org/issues/?jql=project%20%3D%20WINDUP%20AND%20status%20in%20%28Open%2C%20%22Coding%20In%20Progress%22%2C%20Reopened%2C%20Resolved%2C%20%22Pull%20Request%20Sent%22%29
(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."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140814/61bab7f1/attachment.html
From ozizka at redhat.com Fri Aug 15 00:01:34 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Fri, 15 Aug 2014 06:01:34 +0200
Subject: [windup-dev] Resources loading - how to limit to an addon?
Message-ID: <53ED861E.9020005@redhat.com>
Hi,
let's say I want to look for a class, but only in given Addon's scope.
I.e. not in it's dependencies.
How would I do that, in an effective way?
addon.getClassLoader().loadClass() would give me (I suppose) transitive
classloaders' results too.
addon.getRepository().getAddonResources(addon.getId()) and traversing
the results seems to be ugly solution.
Anything better?
Thanks,
Ondra
From lincolnbaxter at gmail.com Mon Aug 18 14:10:57 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 18 Aug 2014 14:10:57 -0400
Subject: [windup-dev] Let's use relative paths
In-Reply-To: <53EB3DD6.2070408@redhat.com>
References: <53E831C3.7080903@redhat.com> <53E8D56E.1050203@redhat.com>
<53E9A205.1000309@redhat.com> <53EA5C81.9030604@redhat.com>
<53EB3DD6.2070408@redhat.com>
Message-ID: <CAEp_U4FH2cTHLoa-Uy28P99Mrnv3LiXGbKnyAAv6HdOi0XeoXQ@mail.gmail.com>
IMO. We should be using full paths in the internals of the system wherever
possible. Relative paths for presentation (and as needed) is fine. But
losing this information on storage seems premature to me. I don't foresee
any amount of real extra work to use absolute paths, it's just a different
approach that requires the same amount of work in a different way.
On Wed, Aug 13, 2014 at 6:28 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
>
>
>
>
> On 12.8.2014 20:27, Jess Sightler wrote:
> > For the most part, we should be using absolute (canonicalized) paths
> > internally, as otherwise path comparisons can become difficult.
> I don't think so.
> We basically only have these paths:
>
> * User input (archives, source dirs, server dirs) - should be kept both
> relative and absolute. [1]
> * Any path under these - should be kept relative.
>
> * Unzipped archives temp dirs - should be kept absolute.
> * Any path under these - should be kept relative.
>
> [1] - the user will put relative path to the archive, e.g. bin/windup.sh
> ../apps/MyApp.war
> and may expect to see this path in the report, too.
>
> Reasons to keep the paths relative:
> 1) Shorter, more effective to store.
> 2) Shorter, less space wasted.
> 3) No need to relativize paths across different archives.
> 4) Path comparisons of relative sub-paths are as difficult as doing that
> with absolute paths.
> 5) The paths in archives are given by the archive, not by location of
> our unzipped temp file. Showing relative path makes it less transparent.
> Working with absolute and then cutting them by the temp dir doesn't give
> any advantage.
>
> my2c,
> Ondra
>
>
>
> > You are
> > definitely right that we need to track things like archive
> > relationships, though (we already do this), as we need to be able to
> > figure out the relative paths later on.
> >
> > Fortunately, we already do that. :)
> >
> >
> > On 08/12/2014 01:11 AM, Ondrej Zizka wrote:
> >> Yes, in the end, it's for presentation.
> >> But that means we need to use them internally too, otherwise they would
> >> get lost on the way.
> >>
> >> For example:
> >> We have archive foo.war.
> >> Extract it to $CWD/tmp/appsExtracted/foo.war/ (made up)
> >> It has a lib.jar, to be extracted to
> >> $CWD/tmp/appsExtracted/foo.war-lib.jar (made up).
> >> To keep the relative information, we need to carry the relative paths,
> >> and the context of what belongs under what.
> >> Otherwise we would have to re-compute the paths during reporting phase,
> >> which would be even harder to do right, IMO.
> >>
> >> Ondra
> >>
> >>
> >> On 11.8.2014 16:38, Jess Sightler wrote:
> >>> For presentation to the user, I agree. I assume that is what you are
> >>> talking about here?
> >>>
> >>> On 08/10/2014 11:00 PM, Ondrej Zizka wrote:
> >>>> 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
> >>>>
> >>>> _______________________________________________
> >>>> windup-dev mailing list
> >>>> windup-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/windup-dev
> >>> _______________________________________________
> >>> windup-dev mailing list
> >>> windup-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/windup-dev
> >> _______________________________________________
> >> windup-dev mailing list
> >> windup-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/windup-dev
> > _______________________________________________
> > windup-dev mailing list
> > windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140818/e83796ac/attachment-0001.html
From lincolnbaxter at gmail.com Mon Aug 18 14:13:01 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 18 Aug 2014 14:13:01 -0400
Subject: [windup-dev] Leave IDE files in place please
In-Reply-To: <53EB7240.4050401@redhat.com>
References: <53E9AA74.3090405@seznam.cz>
<CAEp_U4FpSvP=pAN8DTi_VgBZ8an4s1u3j9a8UtPisE+g+=_RUQ@mail.gmail.com>
<53EA59D4.8040600@redhat.com> <53EB34B6.6020203@redhat.com>
<53EB7240.4050401@redhat.com>
Message-ID: <CAEp_U4FFJy6rJujZMEAGRQMqPRj4623Ej4UgH9vKuoiW4_anXQ@mail.gmail.com>
IMO. It doesn't really matter, because we are using Maven as the build
system. I'm not going to debate this one. I don't really care :) But less
in the repo is better IMO. Eclipse does the same thing and we don't include
that.
On Wed, Aug 13, 2014 at 10:12 AM, Jess Sightler <jsightle at redhat.com> wrote:
> I don't have an issue with that file being in the repo. I can see
> potential value there. WDYT Lincoln?
>
>
> On 08/13/2014 05:49 AM, Ondrej Zizka wrote:
>
> That file contains maping of IDE actions (build, clean & build) to maven
> goals and properties. This makes launching tests, debugging, rebuilding
> etc. a bit easier.
> Not necessary to be in repo, but helps.
> Just asking about the policy.
>
> Thanks,
> Ondra
>
>
> On 12.8.2014 20:15, Jess Sightler wrote:
>
> We have an Eclipse formatting profile, and that is the only one that I am
> aware of. If there is something of similar value that would be helpful for
> opening the project in Netbeans, I wouldn't be opposed to it personally.
>
> I would prefer a separate PR, though (with some justification).
>
> On 08/12/2014 11:16 AM, Lincoln Baxter, III wrote:
>
> Hey Ondra,
>
> Which eclipse files are you referring to? We shouldn't have any eclipse
> project metadata in the repository.
>
> Thanks!
> ~Lincoln
>
>
> On Tue, Aug 12, 2014 at 1:47 AM, "Ing. Ond?ej ?i?ka" <zizka at seznam.cz>
> wrote:
>
>>
>> https://github.com/jsight/windup/commit/75e4da40b504bdc688fb4e06785f25885610c657
>>
>>
>> Why can't NetBeans file stay?
>> Why eclipse file can then?
>>
>> Regards,
>> Ondra
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140818/db575f37/attachment.html
From lincolnbaxter at gmail.com Mon Aug 18 14:14:44 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 18 Aug 2014 14:14:44 -0400
Subject: [windup-dev] CWD in target/ - what are the issues?
In-Reply-To: <53EC56EC.9010409@redhat.com>
References: <53EC56EC.9010409@redhat.com>
Message-ID: <CAEp_U4GdjOhQj4L0e+3tN6QMXb3Ba+17ViPkHba6PKp7MY-T+Q@mail.gmail.com>
Hey Ondra,
If you need the bootstrap class to run in a separate directory, then pass
in an input to set the directory. We shouldn't assume that the directory
Java is running in is the directory that work should be done in.
Also, regarding the work you've done so far in bootstrap. I don't think
this is something we should be focusing on right now. Focus on the Forge
UI, which will be what we are delivering in 6 weeks.
~Lincoln
On Thu, Aug 14, 2014 at 2:27 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
> 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
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140818/56124bd9/attachment.html
From lincolnbaxter at gmail.com Mon Aug 18 14:16:21 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 18 Aug 2014 14:16:21 -0400
Subject: [windup-dev] Resources loading - how to limit to an addon?
In-Reply-To: <53ED861E.9020005@redhat.com>
References: <53ED861E.9020005@redhat.com>
Message-ID: <CAEp_U4EniXCjSQ88jOOrmS3RpMTe5npmwCKE6=EV68jkJyJrEw@mail.gmail.com>
Use ClassLoaders.ownsClass(loader, targetClass) to identify which
ClassLoader owns a given class. Basically compare
MyClass.class.getClassLoader() to addon.getClassLoader().
On Fri, Aug 15, 2014 at 12:01 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
> Hi,
>
> let's say I want to look for a class, but only in given Addon's scope.
> I.e. not in it's dependencies.
> How would I do that, in an effective way?
>
> addon.getClassLoader().loadClass() would give me (I suppose) transitive
> classloaders' results too.
>
> addon.getRepository().getAddonResources(addon.getId()) and traversing
> the results seems to be ugly solution.
>
> Anything better?
>
> Thanks,
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140818/aec77976/attachment.html
From lincolnbaxter at gmail.com Mon Aug 18 14:17:06 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 18 Aug 2014 14:17:06 -0400
Subject: [windup-dev] Jira module: Bootstrap
In-Reply-To: <53EC76A0.4060306@redhat.com>
References: <53EC76A0.4060306@redhat.com>
Message-ID: <CAEp_U4EHwNBeBM3YWjqmGhSw3R-RWM6T2ZdYkN-sZvp+qQN+1g@mail.gmail.com>
Sure, but again, we should be working on the Forge UI right now.
On Thu, Aug 14, 2014 at 4:43 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
> Lincoln, could you please add Bootstrap jira module?
>
> Thx,Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140818/94f6647a/attachment.html
From sgilda at redhat.com Mon Aug 18 21:58:40 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Mon, 18 Aug 2014 21:58:40 -0400
Subject: [windup-dev] Fwd: Re: Migration Notes
In-Reply-To: <1646011176.25719531.1408400634001.JavaMail.zimbra@redhat.com>
References: <1646011176.25719531.1408400634001.JavaMail.zimbra@redhat.com>
Message-ID: <53F2AF50.3070204@redhat.com>
Hi Eric,
Thanks so much for sharing your notes. I will try to update the JBoss
Migration Guide with this information. I am also copying the Windup
development team for addition to the rules repository.
Thanks again,
Sande
-------- Original Message --------
Subject: Re: Migration Notes
Date: Mon, 18 Aug 2014 18:23:54 -0400 (EDT)
From: Eric Sauer <esauer at redhat.com>
To: Sande Gilda <sgilda at redhat.com>
CC: Brad Davis <bdavis at redhat.com>
Ok, this is one of the migration notes wiki pages we left with the customer. It contains what we ultimately had to do to get WS-Security working when moving from JBossWS Native in AS 4.2.3 to JBossCXF in EAP 6.2.3+. The plus sign is there because we had to also get a BZ created for us to fix two bugs we exposed while working with support to get them migrated. The BZs were installed as cumulative patches on top of CP 6.2.3.
There were a lot of community resources for CXF and the WS-Security spec that we had to use to figure out how to get to the final product we ended up with. I will pull those out of the support case and try to formulate something on mojo hopefully in the coming week.
Eric Sauer
Red Hat Consulting
www.redhat.com
eric at redhat.com | t. 773.318.3036
----- Original Message -----
From: "Eric Sauer" <esauer at redhat.com>
To: "Sande Gilda" <sgilda at redhat.com>
Cc: "Brad Davis" <bdavis at redhat.com>
Sent: Monday, August 18, 2014 5:32:58 PM
Subject: Re: Migration Notes
Hey Guys,
I will get a copy of the documents I left with the customer around what needed changing during migration. We also have a support case around the CXF WS-Security migration which we could easily grab some notes from.
Eric Sauer
Red Hat Consulting
www.redhat.com
eric at redhat.com | t. 773.318.3036
----- Original Message -----
From: "Sande Gilda" <sgilda at redhat.com>
To: "Brad Davis" <bdavis at redhat.com>, "Eric Sauer" <esauer at redhat.com>
Sent: Monday, August 11, 2014 11:42:31 AM
Subject: Re: Migration Notes
Eric, any information you can provide would be extremely valuable!
Thanks Brad!
On 08/11/2014 08:34 AM, Brad Davis wrote:
> Eric,
> Sande takes care of migration documentation for JBoss. Can you pass
> along any notes on web service migration, security context migration,
> and other notes from the AAP project?
>
> Thanks,
> Brad Davis
> Red Hat Consulting
> Email: bdavis at redhat.com <mailto:bdavis at redhat.com> | c:980.226.7865
> <tel:980.226.7865> |http://www.redhat.com <http://www.redhat.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140818/b5688c86/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: b2b migration changes.pdf
Type: application/pdf
Size: 84038 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20140818/b5688c86/attachment-0001.pdf
From lincolnbaxter at gmail.com Tue Aug 19 08:36:25 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 19 Aug 2014 08:36:25 -0400
Subject: [windup-dev] Java-gate?
Message-ID: <CAEp_U4F6xsKvEDPR8x=ce8cswZ9aZg9G8J3kyNLyQyhXZJ=B3A@mail.gmail.com>
Hey Brad, could you please explain java-gate? We are a little confused what
it does. Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140819/bb9deddb/attachment.html
From bdavis at redhat.com Tue Aug 19 08:39:26 2014
From: bdavis at redhat.com (Brad Davis)
Date: Tue, 19 Aug 2014 08:39:26 -0400 (EDT)
Subject: [windup-dev] Java-gate?
In-Reply-To: <CAEp_U4F6xsKvEDPR8x=ce8cswZ9aZg9G8J3kyNLyQyhXZJ=B3A@mail.gmail.com>
References: <CAEp_U4F6xsKvEDPR8x=ce8cswZ9aZg9G8J3kyNLyQyhXZJ=B3A@mail.gmail.com>
Message-ID: <B5938322-7947-4B63-9AC1-0FD6383720B1@redhat.com>
It was a base filter that says "if this regex representing a class is presence within the source, continue processing the pipeline."
So "if source contains reference to x"
Brad Davis
Red Hat Consulting
Email: bdavis at redhat.com | c:980.226.7865 |http://www.redhat.com
> On Aug 19, 2014, at 8:36 AM, "Lincoln Baxter, III" <lincolnbaxter at gmail.com> wrote:
>
> Hey Brad, could you please explain java-gate? We are a little confused what it does. Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140819/b631183f/attachment.html
From robb.greathouse at redhat.com Tue Aug 19 10:33:40 2014
From: robb.greathouse at redhat.com (Robb Greathouse)
Date: Tue, 19 Aug 2014 10:33:40 -0400 (EDT)
Subject: [windup-dev] Fwd: Re: Migration Notes
In-Reply-To: <53F2AF50.3070204@redhat.com>
References: <1646011176.25719531.1408400634001.JavaMail.zimbra@redhat.com>
<53F2AF50.3070204@redhat.com>
Message-ID: <1036363795.8464371.1408458820068.JavaMail.zimbra@redhat.com>
Will this get posted to migration.jboss.org?
Robb Greathouse
Chief Evangelist
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
----- Original Message -----
> Hi Eric,
> Thanks so much for sharing your notes. I will try to update the JBoss
> Migration Guide with this information. I am also copying the Windup
> development team for addition to the rules repository.
> Thanks again,
> Sande
> -------- Original Message --------
> Subject: Re: Migration Notes
> Date: Mon, 18 Aug 2014 18:23:54 -0400 (EDT)
> From: Eric Sauer <esauer at redhat.com>
> To: Sande Gilda <sgilda at redhat.com>
> CC: Brad Davis <bdavis at redhat.com>
> Ok, this is one of the migration notes wiki pages we left with the customer.
> It contains what we ultimately had to do to get WS-Security working when
> moving from JBossWS Native in AS 4.2.3 to JBossCXF in EAP 6.2.3+. The plus
> sign is there because we had to also get a BZ created for us to fix two bugs
> we exposed while working with support to get them migrated. The BZs were
> installed as cumulative patches on top of CP 6.2.3.
> There were a lot of community resources for CXF and the WS-Security spec that
> we had to use to figure out how to get to the final product we ended up
> with. I will pull those out of the support case and try to formulate
> something on mojo hopefully in the coming week.
> Eric Sauer
> Red Hat Consulting www.redhat.com eric at redhat.com | t. 773.318.3036
> ----- Original Message -----
> From: "Eric Sauer" <esauer at redhat.com> To: "Sande Gilda" <sgilda at redhat.com>
> Cc: "Brad Davis" <bdavis at redhat.com> Sent: Monday, August 18, 2014 5:32:58
> PM
> Subject: Re: Migration Notes
> Hey Guys,
> I will get a copy of the documents I left with the customer around what
> needed changing during migration. We also have a support case around the CXF
> WS-Security migration which we could easily grab some notes from.
> Eric Sauer
> Red Hat Consulting www.redhat.com eric at redhat.com | t. 773.318.3036
> ----- Original Message -----
> From: "Sande Gilda" <sgilda at redhat.com> To: "Brad Davis" <bdavis at redhat.com>
> , "Eric Sauer" <esauer at redhat.com> Sent: Monday, August 11, 2014 11:42:31 AM
> Subject: Re: Migration Notes
> Eric, any information you can provide would be extremely valuable!
> Thanks Brad!
> On 08/11/2014 08:34 AM, Brad Davis wrote:
> > Eric,
> > Sande takes care of migration documentation for JBoss. Can you pass
> > along any notes on web service migration, security context migration,
> > and other notes from the AAP project?
> >
> > Thanks,
> > Brad Davis
> > Red Hat Consulting
> > Email: bdavis at redhat.com <mailto:bdavis at redhat.com> | c:980.226.7865
> > <tel:980.226.7865> | http://www.redhat.com <http://www.redhat.com/>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140819/65e5b3ba/attachment.html
From sgilda at redhat.com Tue Aug 19 11:03:37 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 19 Aug 2014 11:03:37 -0400
Subject: [windup-dev] Fwd: Re: Migration Notes
In-Reply-To: <1036363795.8464371.1408458820068.JavaMail.zimbra@redhat.com>
References: <1646011176.25719531.1408400634001.JavaMail.zimbra@redhat.com> <53F2AF50.3070204@redhat.com>
<1036363795.8464371.1408458820068.JavaMail.zimbra@redhat.com>
Message-ID: <53F36749.6080506@redhat.com>
I will try, but it is really had to keep multiple versions of the doc up
to date. :-)
On 08/19/2014 10:33 AM, Robb Greathouse wrote:
> Will this get posted to migration.jboss.org?
>
>
> Robb Greathouse
> Chief Evangelist
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
>
> ------------------------------------------------------------------------
>
> Hi Eric,
>
> Thanks so much for sharing your notes. I will try to update the
> JBoss Migration Guide with this information. I am also copying the
> Windup development team for addition to the rules repository.
>
> Thanks again,
> Sande
>
>
> -------- Original Message --------
> Subject: Re: Migration Notes
> Date: Mon, 18 Aug 2014 18:23:54 -0400 (EDT)
> From: Eric Sauer <esauer at redhat.com>
> To: Sande Gilda <sgilda at redhat.com>
> CC: Brad Davis <bdavis at redhat.com>
>
>
>
> Ok, this is one of the migration notes wiki pages we left with the customer. It contains what we ultimately had to do to get WS-Security working when moving from JBossWS Native in AS 4.2.3 to JBossCXF in EAP 6.2.3+. The plus sign is there because we had to also get a BZ created for us to fix two bugs we exposed while working with support to get them migrated. The BZs were installed as cumulative patches on top of CP 6.2.3.
>
> There were a lot of community resources for CXF and the WS-Security spec that we had to use to figure out how to get to the final product we ended up with. I will pull those out of the support case and try to formulate something on mojo hopefully in the coming week.
>
> Eric Sauer
> Red Hat Consulting
> www.redhat.com
> eric at redhat.com | t. 773.318.3036
>
> ----- Original Message -----
> From: "Eric Sauer"<esauer at redhat.com>
> To: "Sande Gilda"<sgilda at redhat.com>
> Cc: "Brad Davis"<bdavis at redhat.com>
> Sent: Monday, August 18, 2014 5:32:58 PM
> Subject: Re: Migration Notes
>
> Hey Guys,
>
> I will get a copy of the documents I left with the customer around what needed changing during migration. We also have a support case around the CXF WS-Security migration which we could easily grab some notes from.
>
> Eric Sauer
> Red Hat Consulting
> www.redhat.com
> eric at redhat.com | t. 773.318.3036
>
> ----- Original Message -----
> From: "Sande Gilda"<sgilda at redhat.com>
> To: "Brad Davis"<bdavis at redhat.com>, "Eric Sauer"<esauer at redhat.com>
> Sent: Monday, August 11, 2014 11:42:31 AM
> Subject: Re: Migration Notes
>
> Eric, any information you can provide would be extremely valuable!
>
> Thanks Brad!
>
> On 08/11/2014 08:34 AM, Brad Davis wrote:
> > Eric,
> > Sande takes care of migration documentation for JBoss. Can you pass
> > along any notes on web service migration, security context migration,
> > and other notes from the AAP project?
> >
> > Thanks,
> > Brad Davis
> > Red Hat Consulting
> > Email:bdavis at redhat.com <mailto:bdavis at redhat.com> | c:980.226.7865
> > <tel:980.226.7865> |http://www.redhat.com <http://www.redhat.com/>
>
>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140819/70f966ce/attachment-0001.html
From robb.greathouse at redhat.com Tue Aug 19 11:34:15 2014
From: robb.greathouse at redhat.com (Robb Greathouse)
Date: Tue, 19 Aug 2014 11:34:15 -0400 (EDT)
Subject: [windup-dev] Fwd: Re: Migration Notes
In-Reply-To: <53F36749.6080506@redhat.com>
References: <1646011176.25719531.1408400634001.JavaMail.zimbra@redhat.com>
<53F2AF50.3070204@redhat.com>
<1036363795.8464371.1408458820068.JavaMail.zimbra@redhat.com>
<53F36749.6080506@redhat.com>
Message-ID: <548195458.8517478.1408462455094.JavaMail.zimbra@redhat.com>
Could we just put a link to the doc?
Just want to get everything we have on migration linked up and in one spot. Kenny Peeples is pulling together everything over on mojo.
Robb Greathouse
Chief Evangelist
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
----- Original Message -----
> I will try, but it is really had to keep multiple versions of the doc up to
> date. :-)
> On 08/19/2014 10:33 AM, Robb Greathouse wrote:
> > Will this get posted to migration.jboss.org?
>
> > Robb Greathouse
>
> > Chief Evangelist
>
> > Middleware Business Unit
>
> > JBoss, a Division of Red Hat
>
> > cellphone 505-507-4906
>
> > ----- Original Message -----
>
> > > Hi Eric,
> >
>
> > > Thanks so much for sharing your notes. I will try to update the JBoss
> > > Migration Guide with this information. I am also copying the Windup
> > > development team for addition to the rules repository.
> >
>
> > > Thanks again,
> >
>
> > > Sande
> >
>
> > > -------- Original Message --------
> >
>
> > > Subject: Re: Migration Notes
> >
>
> > > Date: Mon, 18 Aug 2014 18:23:54 -0400 (EDT)
> >
>
> > > From: Eric Sauer <esauer at redhat.com>
> >
>
> > > To: Sande Gilda <sgilda at redhat.com>
> >
>
> > > CC: Brad Davis <bdavis at redhat.com>
> >
>
> > > Ok, this is one of the migration notes wiki pages we left with the
> > > customer.
> > > It contains what we ultimately had to do to get WS-Security working when
> > > moving from JBossWS Native in AS 4.2.3 to JBossCXF in EAP 6.2.3+. The
> > > plus
> > > sign is there because we had to also get a BZ created for us to fix two
> > > bugs
> > > we exposed while working with support to get them migrated. The BZs were
> > > installed as cumulative patches on top of CP 6.2.3.
> >
>
> > > There were a lot of community resources for CXF and the WS-Security spec
> > > that
> > > we had to use to figure out how to get to the final product we ended up
> > > with. I will pull those out of the support case and try to formulate
> > > something on mojo hopefully in the coming week.
> >
>
> > > Eric Sauer
> >
>
> > > Red Hat Consulting www.redhat.com eric at redhat.com | t. 773.318.3036
> >
>
> > > ----- Original Message -----
> >
>
> > > From: "Eric Sauer" <esauer at redhat.com> To: "Sande Gilda"
> > > <sgilda at redhat.com>
> > > Cc: "Brad Davis" <bdavis at redhat.com> Sent: Monday, August 18, 2014
> > > 5:32:58
> > > PM
> >
>
> > > Subject: Re: Migration Notes
> >
>
> > > Hey Guys,
> >
>
> > > I will get a copy of the documents I left with the customer around what
> > > needed changing during migration. We also have a support case around the
> > > CXF
> > > WS-Security migration which we could easily grab some notes from.
> >
>
> > > Eric Sauer
> >
>
> > > Red Hat Consulting www.redhat.com eric at redhat.com | t. 773.318.3036
> >
>
> > > ----- Original Message -----
> >
>
> > > From: "Sande Gilda" <sgilda at redhat.com> To: "Brad Davis"
> > > <bdavis at redhat.com>
> > > , "Eric Sauer" <esauer at redhat.com> Sent: Monday, August 11, 2014 11:42:31
> > > AM
> >
>
> > > Subject: Re: Migration Notes
> >
>
> > > Eric, any information you can provide would be extremely valuable!
> >
>
> > > Thanks Brad!
> >
>
> > > On 08/11/2014 08:34 AM, Brad Davis wrote:
> >
>
> > > > Eric,
> >
>
> > > > Sande takes care of migration documentation for JBoss. Can you pass
> >
>
> > > > along any notes on web service migration, security context migration,
> >
>
> > > > and other notes from the AAP project?
> >
>
> > > >
> >
>
> > > > Thanks,
> >
>
> > > > Brad Davis
> >
>
> > > > Red Hat Consulting
> >
>
> > > > Email: bdavis at redhat.com <mailto:bdavis at redhat.com> | c:980.226.7865
> >
>
> > > > <tel:980.226.7865> | http://www.redhat.com <http://www.redhat.com/>
> >
>
> > > _______________________________________________
> >
>
> > > windup-dev mailing list
> >
>
> > > windup-dev at lists.jboss.org
> >
>
> > > https://lists.jboss.org/mailman/listinfo/windup-dev
> >
>
> > _______________________________________________
>
> > windup-dev mailing list windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140819/f82f24d1/attachment.html
From lincolnbaxter at gmail.com Tue Aug 19 13:30:44 2014
From: lincolnbaxter at gmail.com (lincolnbaxter at gmail.com)
Date: Tue, 19 Aug 2014 17:30:44 +0000
Subject: [windup-dev] Invitation: Windup Dev Q&A Checkpoint Meeting @ Mon
Aug 25, 2014 10am - 11am (Windup Project Calendar)
Message-ID: <20cf3010e73be561620500fed8e1@google.com>
You have been invited to the following event.
Title: Windup Dev Q&A Checkpoint Meeting
To discuss any questions about the code, or follow-up on pull requests that
need review/questions that haven't been answered on the email list/etc.
When: Mon Aug 25, 2014 10am - 11am Eastern Time
Where: #windup on irc.freenode.net
Calendar: Windup Project Calendar
Who:
* Lincoln Baxter, III - creator
* ozizka at redhat.com
* Robb Greathouse
* windup-dev at lists.jboss.org
* mbriskar at redhat.com
* sgilda at redhat.com
* pmuir at redhat.com
* jsightle at redhat.com
Event details:
https://www.google.com/calendar/event?action=VIEW&eid=cm83YmZoZjFqNjk1azNhNmtkNnJjZWozMDAgd2luZHVwLWRldkBsaXN0cy5qYm9zcy5vcmc&tok=NTIjbThxYjFhZTZyYTJtZWZqNmc4Y2c3bHVlOTRAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbTY0YjhkZTczODAwYzcwN2JmMTcyNzcwNjQ2NzZmNDA3MGRkMDUxN2M&ctz=America/New_York&hl=en
Invitation from Google Calendar: https://www.google.com/calendar/
You are receiving this courtesy email at the account
windup-dev at lists.jboss.org because you are an attendee of this event.
To stop receiving future notifications for this event, decline this event.
Alternatively you can sign up for a Google account at
https://www.google.com/calendar/ and control your notification settings for
your entire calendar.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140819/e4058a2f/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 2054 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20140819/e4058a2f/attachment-0002.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: application/ics
Size: 2096 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20140819/e4058a2f/attachment-0003.bin
From sgilda at redhat.com Tue Aug 19 14:22:13 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 19 Aug 2014 14:22:13 -0400
Subject: [windup-dev] Fwd: Re: Migration Notes
In-Reply-To: <548195458.8517478.1408462455094.JavaMail.zimbra@redhat.com>
References: <1646011176.25719531.1408400634001.JavaMail.zimbra@redhat.com>
<53F2AF50.3070204@redhat.com>
<1036363795.8464371.1408458820068.JavaMail.zimbra@redhat.com>
<53F36749.6080506@redhat.com>
<548195458.8517478.1408462455094.JavaMail.zimbra@redhat.com>
Message-ID: <53F395D5.8030103@redhat.com>
The problem is that the WebLogic and WebSphere Migration Guides exist
only in the internal content management system. I could never find
anyone to review them or give approval. I'm not sure we want to link to
an internal document, so I will try to maintain the public Wiki pages in
addition to the product updates.
If you could find some SMEs to review what's there, I am willing to
publish them with limited content with John Doyle's approval. :-)
On 08/19/2014 11:34 AM, Robb Greathouse wrote:
> Could we just put a link to the doc?
>
> Just want to get everything we have on migration linked up and in one
> spot. Kenny Peeples is pulling together everything over on mojo.
>
>
> Robb Greathouse
> Chief Evangelist
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
>
> ------------------------------------------------------------------------
>
> I will try, but it is really had to keep multiple versions of the
> doc up to date. :-)
>
> On 08/19/2014 10:33 AM, Robb Greathouse wrote:
>
> Will this get posted to migration.jboss.org?
>
>
> Robb Greathouse
> Chief Evangelist
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
>
> ------------------------------------------------------------------------
>
> Hi Eric,
>
> Thanks so much for sharing your notes. I will try to
> update the JBoss Migration Guide with this information. I
> am also copying the Windup development team for addition
> to the rules repository.
>
> Thanks again,
> Sande
>
>
> -------- Original Message --------
> Subject: Re: Migration Notes
> Date: Mon, 18 Aug 2014 18:23:54 -0400 (EDT)
> From: Eric Sauer <esauer at redhat.com>
> To: Sande Gilda <sgilda at redhat.com>
> CC: Brad Davis <bdavis at redhat.com>
>
>
>
> Ok, this is one of the migration notes wiki pages we left with the customer. It contains what we ultimately had to do to get WS-Security working when moving from JBossWS Native in AS 4.2.3 to JBossCXF in EAP 6.2.3+. The plus sign is there because we had to also get a BZ created for us to fix two bugs we exposed while working with support to get them migrated. The BZs were installed as cumulative patches on top of CP 6.2.3.
>
> There were a lot of community resources for CXF and the WS-Security spec that we had to use to figure out how to get to the final product we ended up with. I will pull those out of the support case and try to formulate something on mojo hopefully in the coming week.
>
> Eric Sauer
> Red Hat Consulting
> www.redhat.com
> eric at redhat.com | t. 773.318.3036
>
> ----- Original Message -----
> From: "Eric Sauer"<esauer at redhat.com>
> To: "Sande Gilda"<sgilda at redhat.com>
> Cc: "Brad Davis"<bdavis at redhat.com>
> Sent: Monday, August 18, 2014 5:32:58 PM
> Subject: Re: Migration Notes
>
> Hey Guys,
>
> I will get a copy of the documents I left with the customer around what needed changing during migration. We also have a support case around the CXF WS-Security migration which we could easily grab some notes from.
>
> Eric Sauer
> Red Hat Consulting
> www.redhat.com
> eric at redhat.com | t. 773.318.3036
>
> ----- Original Message -----
> From: "Sande Gilda"<sgilda at redhat.com>
> To: "Brad Davis"<bdavis at redhat.com>, "Eric Sauer"<esauer at redhat.com>
> Sent: Monday, August 11, 2014 11:42:31 AM
> Subject: Re: Migration Notes
>
> Eric, any information you can provide would be extremely valuable!
>
> Thanks Brad!
>
> On 08/11/2014 08:34 AM, Brad Davis wrote:
> > Eric,
> > Sande takes care of migration documentation for JBoss. Can you pass
> > along any notes on web service migration, security context migration,
> > and other notes from the AAP project?
> >
> > Thanks,
> > Brad Davis
> > Red Hat Consulting
> > Email:bdavis at redhat.com <mailto:bdavis at redhat.com> | c:980.226.7865
> > <tel:980.226.7865> |http://www.redhat.com <http://www.redhat.com/>
>
>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140819/b5c9a1fe/attachment.html
From robb.greathouse at redhat.com Tue Aug 19 14:36:33 2014
From: robb.greathouse at redhat.com (Robb Greathouse)
Date: Tue, 19 Aug 2014 14:36:33 -0400 (EDT)
Subject: [windup-dev] Fwd: Re: Migration Notes
In-Reply-To: <53F395D5.8030103@redhat.com>
References: <1646011176.25719531.1408400634001.JavaMail.zimbra@redhat.com>
<53F2AF50.3070204@redhat.com>
<1036363795.8464371.1408458820068.JavaMail.zimbra@redhat.com>
<53F36749.6080506@redhat.com>
<548195458.8517478.1408462455094.JavaMail.zimbra@redhat.com>
<53F395D5.8030103@redhat.com>
Message-ID: <451310137.8629509.1408473393682.JavaMail.zimbra@redhat.com>
I'll be discussing WebSphere migration with one of the lead consultants tomorrow. I'll bring this up. Maybe they could review and then John could approve.
Robb Greathouse
Chief Evangelist
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
----- Original Message -----
> The problem is that the WebLogic and WebSphere Migration Guides exist only in
> the internal content management system. I could never find anyone to review
> them or give approval. I'm not sure we want to link to an internal document,
> so I will try to maintain the public Wiki pages in addition to the product
> updates.
> If you could find some SMEs to review what's there, I am willing to publish
> them with limited content with John Doyle's approval. :-)
> On 08/19/2014 11:34 AM, Robb Greathouse wrote:
> > Could we just put a link to the doc?
>
> > Just want to get everything we have on migration linked up and in one spot.
> > Kenny Peeples is pulling together everything over on mojo.
>
> > Robb Greathouse
>
> > Chief Evangelist
>
> > Middleware Business Unit
>
> > JBoss, a Division of Red Hat
>
> > cellphone 505-507-4906
>
> > ----- Original Message -----
>
> > > I will try, but it is really had to keep multiple versions of the doc up
> > > to
> > > date. :-)
> >
>
> > > On 08/19/2014 10:33 AM, Robb Greathouse wrote:
> >
>
> > > > Will this get posted to migration.jboss.org?
> > >
> >
>
> > > > Robb Greathouse
> > >
> >
>
> > > > Chief Evangelist
> > >
> >
>
> > > > Middleware Business Unit
> > >
> >
>
> > > > JBoss, a Division of Red Hat
> > >
> >
>
> > > > cellphone 505-507-4906
> > >
> >
>
> > > > ----- Original Message -----
> > >
> >
>
> > > > > Hi Eric,
> > > >
> > >
> >
>
> > > > > Thanks so much for sharing your notes. I will try to update the JBoss
> > > > > Migration Guide with this information. I am also copying the Windup
> > > > > development team for addition to the rules repository.
> > > >
> > >
> >
>
> > > > > Thanks again,
> > > >
> > >
> >
>
> > > > > Sande
> > > >
> > >
> >
>
> > > > > -------- Original Message --------
> > > >
> > >
> >
>
> > > > > Subject: Re: Migration Notes
> > > >
> > >
> >
>
> > > > > Date: Mon, 18 Aug 2014 18:23:54 -0400 (EDT)
> > > >
> > >
> >
>
> > > > > From: Eric Sauer <esauer at redhat.com>
> > > >
> > >
> >
>
> > > > > To: Sande Gilda <sgilda at redhat.com>
> > > >
> > >
> >
>
> > > > > CC: Brad Davis <bdavis at redhat.com>
> > > >
> > >
> >
>
> > > > > Ok, this is one of the migration notes wiki pages we left with the
> > > > > customer.
> > > > > It contains what we ultimately had to do to get WS-Security working
> > > > > when
> > > > > moving from JBossWS Native in AS 4.2.3 to JBossCXF in EAP 6.2.3+. The
> > > > > plus
> > > > > sign is there because we had to also get a BZ created for us to fix
> > > > > two
> > > > > bugs
> > > > > we exposed while working with support to get them migrated. The BZs
> > > > > were
> > > > > installed as cumulative patches on top of CP 6.2.3.
> > > >
> > >
> >
>
> > > > > There were a lot of community resources for CXF and the WS-Security
> > > > > spec
> > > > > that
> > > > > we had to use to figure out how to get to the final product we ended
> > > > > up
> > > > > with. I will pull those out of the support case and try to formulate
> > > > > something on mojo hopefully in the coming week.
> > > >
> > >
> >
>
> > > > > Eric Sauer
> > > >
> > >
> >
>
> > > > > Red Hat Consulting www.redhat.com eric at redhat.com | t. 773.318.3036
> > > >
> > >
> >
>
> > > > > ----- Original Message -----
> > > >
> > >
> >
>
> > > > > From: "Eric Sauer" <esauer at redhat.com> To: "Sande Gilda"
> > > > > <sgilda at redhat.com>
> > > > > Cc: "Brad Davis" <bdavis at redhat.com> Sent: Monday, August 18, 2014
> > > > > 5:32:58
> > > > > PM
> > > >
> > >
> >
>
> > > > > Subject: Re: Migration Notes
> > > >
> > >
> >
>
> > > > > Hey Guys,
> > > >
> > >
> >
>
> > > > > I will get a copy of the documents I left with the customer around
> > > > > what
> > > > > needed changing during migration. We also have a support case around
> > > > > the
> > > > > CXF
> > > > > WS-Security migration which we could easily grab some notes from.
> > > >
> > >
> >
>
> > > > > Eric Sauer
> > > >
> > >
> >
>
> > > > > Red Hat Consulting www.redhat.com eric at redhat.com | t. 773.318.3036
> > > >
> > >
> >
>
> > > > > ----- Original Message -----
> > > >
> > >
> >
>
> > > > > From: "Sande Gilda" <sgilda at redhat.com> To: "Brad Davis"
> > > > > <bdavis at redhat.com>
> > > > > , "Eric Sauer" <esauer at redhat.com> Sent: Monday, August 11, 2014
> > > > > 11:42:31
> > > > > AM
> > > >
> > >
> >
>
> > > > > Subject: Re: Migration Notes
> > > >
> > >
> >
>
> > > > > Eric, any information you can provide would be extremely valuable!
> > > >
> > >
> >
>
> > > > > Thanks Brad!
> > > >
> > >
> >
>
> > > > > On 08/11/2014 08:34 AM, Brad Davis wrote:
> > > >
> > >
> >
>
> > > > > > Eric,
> > > >
> > >
> >
>
> > > > > > Sande takes care of migration documentation for JBoss. Can you pass
> > > >
> > >
> >
>
> > > > > > along any notes on web service migration, security context
> > > > > > migration,
> > > >
> > >
> >
>
> > > > > > and other notes from the AAP project?
> > > >
> > >
> >
>
> > > > > >
> > > >
> > >
> >
>
> > > > > > Thanks,
> > > >
> > >
> >
>
> > > > > > Brad Davis
> > > >
> > >
> >
>
> > > > > > Red Hat Consulting
> > > >
> > >
> >
>
> > > > > > Email: bdavis at redhat.com <mailto:bdavis at redhat.com> |
> > > > > > c:980.226.7865
> > > >
> > >
> >
>
> > > > > > <tel:980.226.7865> | http://www.redhat.com <http://www.redhat.com/>
> > > >
> > >
> >
>
> > > > > _______________________________________________
> > > >
> > >
> >
>
> > > > > windup-dev mailing list
> > > >
> > >
> >
>
> > > > > windup-dev at lists.jboss.org
> > > >
> > >
> >
>
> > > > > https://lists.jboss.org/mailman/listinfo/windup-dev
> > > >
> > >
> >
>
> > > > _______________________________________________
> > >
> >
>
> > > > windup-dev mailing list windup-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/windup-dev
> > >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140819/0a2473dd/attachment-0001.html
From lincolnbaxter at gmail.com Wed Aug 20 11:55:30 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 20 Aug 2014 11:55:30 -0400
Subject: [windup-dev] Windup Meeting Minutes: 2014-08-20
Message-ID: <CAEp_U4HZbwiRV06DbFppO2X1j2CmYXTMRxi6ZaJGcGJPm8afPg@mail.gmail.com>
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-08-20-14.02.html
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-08-20-14.02.txt
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-08-20-14.02.log.html
Meeting summary
---------------
* Agenda (lincolnthree, 14:03:57)
* Status Reports (lincolnthree, 14:06:14)
* I've been working on XML rule syntax. (lincolnthree, 14:08:01)
* Along the way I've started simplifying the
Iteration.over().perform(?) default behavior even farther
(lincolnthree, 14:08:20)
* so that iterations will be implied if not specified at the base
level (working on the correct pre-conditions to activate this)
(lincolnthree, 14:09:15)
* Iteration simplification ?> http://paste2.org/0k7OHt7I
(lincolnthree, 14:11:33)
* other than that I've been dealing with a lot of meetings because of
our release date change, people are a little too eager imo
(lincolnthree, 14:17:17)
* I was working with Robb and Sande on docs. (ozizka, 14:18:01)
* I paused work on PRs as I am a bit confused about the requirements
and priorities. Hopefully resuming when clarified. (ozizka,
14:18:01)
* I have worked on some design work for per-ruleset configuration
(with lincoln and ozizka) (jsightler, 14:19:35)
* I have also added some basic pie charts and effort point reports to
the windup report (jsightler, 14:19:51)
* And I added the per-ruleset metadata implementation (just ruleset id
for now) (jsightler, 14:20:16)
* Worked on migrating java legacy rules, I believe they are complete
now. However didn't test it that it really contains all of the
legacy rules (mbriskar, 14:24:08)
* Since now, please add prefix "Test" to all Models, Operations,
Conditions and Rules that are for the testing purpose only.
(mbriskar, 14:24:50)
* Created a rule creating tutorial and a "quickstart" for the purposes
of demo for sgilda and robbg (ozizka, 14:27:28)
* per-ruleset configuration (lincolnthree, 14:35:23)
* The per-ruleset configuration document is here:
https://docs.google.com/document/d/1tjJF3Temh8_xLe__yoGEx0wRwtrh8qPwmBHSZAKNBmY/edit
(WINDUP-131) (jsightler, 14:36:35)
* Release priorities (lincolnthree, 14:40:57)
* LINK: https://github.com/forge/core/tree/master/dist
(lincolnthree, 14:43:03)
* LINK: https://issues.jboss.org/browse/WINDUP-88 (lincolnthree,
14:43:59)
* AGREED: Users will run Windup through Forge for the Tech Preview
release (lincolnthree, 14:59:01)
* Ensure feature parity with Windup 1.x rules (lincolnthree,
15:00:27)
* Ensure feature parity with Windup 1.x reporting (lincolnthree,
15:00:40)
* Externalized rules - Groovy (lincolnthree, 15:03:19)
* Team Focus (lincolnthree, 15:32:29)
* mbriskar is working on renaming tests and test models and migrating
windup 1.x XML-inspection rules to the new Java dSL syntax
(lincolnthree, 15:35:52)
* I am working on loading Groovy files from an external folder
dynamically at the moment (jsightler, 15:42:18)
* I am finishing up https://github.com/windup/windup/pull/197 before
the groovy stuff... hopefully today (jsightler, 15:45:28)
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140820/001c6cd1/attachment.html
From lincolnbaxter at gmail.com Wed Aug 20 17:21:41 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 20 Aug 2014 17:21:41 -0400
Subject: [windup-dev] Fwd: Re: Migration Notes
In-Reply-To: <451310137.8629509.1408473393682.JavaMail.zimbra@redhat.com>
References: <1646011176.25719531.1408400634001.JavaMail.zimbra@redhat.com>
<53F2AF50.3070204@redhat.com>
<1036363795.8464371.1408458820068.JavaMail.zimbra@redhat.com>
<53F36749.6080506@redhat.com>
<548195458.8517478.1408462455094.JavaMail.zimbra@redhat.com>
<53F395D5.8030103@redhat.com>
<451310137.8629509.1408473393682.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4F1jBVe12wJrWVk+d5toOXeJyrFXXH086G7r8cDzMWk8Q@mail.gmail.com>
Please add a JIRA in WINDUP using the following issue as a template:
https://issues.jboss.org/browse/WINDUP-23
Also please attach the document and provide as much detail as possible in
the description if anything in the document is missing or unclear. Thank
you!
~Lincoln
On Tue, Aug 19, 2014 at 2:36 PM, Robb Greathouse <robb.greathouse at redhat.com
> wrote:
> I'll be discussing WebSphere migration with one of the lead consultants
> tomorrow. I'll bring this up. Maybe they could review and then John could
> approve.
>
>
> Robb Greathouse
> Chief Evangelist
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
>
> ------------------------------
>
> The problem is that the WebLogic and WebSphere Migration Guides exist only
> in the internal content management system. I could never find anyone to
> review them or give approval. I'm not sure we want to link to an internal
> document, so I will try to maintain the public Wiki pages in addition to
> the product updates.
>
> If you could find some SMEs to review what's there, I am willing to
> publish them with limited content with John Doyle's approval. :-)
>
> On 08/19/2014 11:34 AM, Robb Greathouse wrote:
>
> Could we just put a link to the doc?
>
> Just want to get everything we have on migration linked up and in one
> spot. Kenny Peeples is pulling together everything over on mojo.
>
>
> Robb Greathouse
> Chief Evangelist
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
>
> ------------------------------
>
> I will try, but it is really had to keep multiple versions of the doc up
> to date. :-)
>
> On 08/19/2014 10:33 AM, Robb Greathouse wrote:
>
> Will this get posted to migration.jboss.org?
>
>
> Robb Greathouse
> Chief Evangelist
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
>
> ------------------------------
>
> Hi Eric,
>
> Thanks so much for sharing your notes. I will try to update the JBoss
> Migration Guide with this information. I am also copying the Windup
> development team for addition to the rules repository.
>
> Thanks again,
> Sande
>
>
> -------- Original Message -------- Subject: Re: Migration Notes Date: Mon,
> 18 Aug 2014 18:23:54 -0400 (EDT) From: Eric Sauer <esauer at redhat.com>
> <esauer at redhat.com> To: Sande Gilda <sgilda at redhat.com>
> <sgilda at redhat.com> CC: Brad Davis <bdavis at redhat.com>
> <bdavis at redhat.com>
>
> Ok, this is one of the migration notes wiki pages we left with the customer. It contains what we ultimately had to do to get WS-Security working when moving from JBossWS Native in AS 4.2.3 to JBossCXF in EAP 6.2.3+. The plus sign is there because we had to also get a BZ created for us to fix two bugs we exposed while working with support to get them migrated. The BZs were installed as cumulative patches on top of CP 6.2.3.
>
> There were a lot of community resources for CXF and the WS-Security spec that we had to use to figure out how to get to the final product we ended up with. I will pull those out of the support case and try to formulate something on mojo hopefully in the coming week.
>
> Eric Sauer
> Red Hat Consultingwww.redhat.comeric at redhat.com | t. 773.318.3036
>
> ----- Original Message -----
> From: "Eric Sauer" <esauer at redhat.com> <esauer at redhat.com>
> To: "Sande Gilda" <sgilda at redhat.com> <sgilda at redhat.com>
> Cc: "Brad Davis" <bdavis at redhat.com> <bdavis at redhat.com>
> Sent: Monday, August 18, 2014 5:32:58 PM
> Subject: Re: Migration Notes
>
> Hey Guys,
>
> I will get a copy of the documents I left with the customer around what needed changing during migration. We also have a support case around the CXF WS-Security migration which we could easily grab some notes from.
>
> Eric Sauer
> Red Hat Consultingwww.redhat.comeric at redhat.com | t. 773.318.3036
>
> ----- Original Message -----
> From: "Sande Gilda" <sgilda at redhat.com> <sgilda at redhat.com>
> To: "Brad Davis" <bdavis at redhat.com> <bdavis at redhat.com>, "Eric Sauer" <esauer at redhat.com> <esauer at redhat.com>
> Sent: Monday, August 11, 2014 11:42:31 AM
> Subject: Re: Migration Notes
>
> Eric, any information you can provide would be extremely valuable!
>
> Thanks Brad!
>
> On 08/11/2014 08:34 AM, Brad Davis wrote:
> > Eric,
> > Sande takes care of migration documentation for JBoss. Can you pass
> > along any notes on web service migration, security context migration,
> > and other notes from the AAP project?
> >
> > Thanks,
> > Brad Davis
> > Red Hat Consulting
> > Email: bdavis at redhat.com <mailto:bdavis at redhat.com> <bdavis at redhat.com> | c:980.226.7865
> > <tel:980.226.7865> |http://www.redhat.com <http://www.redhat.com/> <http://www.redhat.com/>
>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140820/26901518/attachment.html
From sgilda at redhat.com Thu Aug 21 05:52:42 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 21 Aug 2014 05:52:42 -0400
Subject: [windup-dev] Fwd: Re: Migration Notes
In-Reply-To: <CAEp_U4F1jBVe12wJrWVk+d5toOXeJyrFXXH086G7r8cDzMWk8Q@mail.gmail.com>
References: <1646011176.25719531.1408400634001.JavaMail.zimbra@redhat.com> <53F2AF50.3070204@redhat.com> <1036363795.8464371.1408458820068.JavaMail.zimbra@redhat.com> <53F36749.6080506@redhat.com> <548195458.8517478.1408462455094.JavaMail.zimbra@redhat.com> <53F395D5.8030103@redhat.com> <451310137.8629509.1408473393682.JavaMail.zimbra@redhat.com>
<CAEp_U4F1jBVe12wJrWVk+d5toOXeJyrFXXH086G7r8cDzMWk8Q@mail.gmail.com>
Message-ID: <53F5C16A.1090109@redhat.com>
Done.
Attached Eric's document to the JIRA and provided a link to my bug [1]
to add the information to the JBoss Migration Guide.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1131493
Sande
On 08/20/2014 05:21 PM, Lincoln Baxter, III wrote:
> Please add a JIRA in WINDUP using the following issue as a template:
>
> https://issues.jboss.org/browse/WINDUP-23
>
> Also please attach the document and provide as much detail as possible
> in the description if anything in the document is missing or unclear.
> Thank you!
>
> ~Lincoln
>
>
> On Tue, Aug 19, 2014 at 2:36 PM, Robb Greathouse
> <robb.greathouse at redhat.com <mailto:robb.greathouse at redhat.com>> wrote:
>
> I'll be discussing WebSphere migration with one of the lead
> consultants tomorrow. I'll bring this up. Maybe they could
> review and then John could approve.
>
>
> Robb Greathouse
> Chief Evangelist
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906 <tel:505-507-4906>
>
> ------------------------------------------------------------------------
>
> The problem is that the WebLogic and WebSphere Migration
> Guides exist only in the internal content management system. I
> could never find anyone to review them or give approval. I'm
> not sure we want to link to an internal document, so I will
> try to maintain the public Wiki pages in addition to the
> product updates.
>
> If you could find some SMEs to review what's there, I am
> willing to publish them with limited content with John Doyle's
> approval. :-)
>
> On 08/19/2014 11:34 AM, Robb Greathouse wrote:
>
> Could we just put a link to the doc?
>
> Just want to get everything we have on migration linked up
> and in one spot. Kenny Peeples is pulling together
> everything over on mojo.
>
>
> Robb Greathouse
> Chief Evangelist
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906 <tel:505-507-4906>
>
> ------------------------------------------------------------------------
>
> I will try, but it is really had to keep multiple
> versions of the doc up to date. :-)
>
> On 08/19/2014 10:33 AM, Robb Greathouse wrote:
>
> Will this get posted to migration.jboss.org
> <http://migration.jboss.org>?
>
>
> Robb Greathouse
> Chief Evangelist
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906 <tel:505-507-4906>
>
> ------------------------------------------------------------------------
>
> Hi Eric,
>
> Thanks so much for sharing your notes. I will
> try to update the JBoss Migration Guide with
> this information. I am also copying the Windup
> development team for addition to the rules
> repository.
>
> Thanks again,
> Sande
>
>
> -------- Original Message --------
> Subject: Re: Migration Notes
> Date: Mon, 18 Aug 2014 18:23:54 -0400 (EDT)
> From: Eric Sauer <esauer at redhat.com>
> <mailto:esauer at redhat.com>
> To: Sande Gilda <sgilda at redhat.com>
> <mailto:sgilda at redhat.com>
> CC: Brad Davis <bdavis at redhat.com>
> <mailto:bdavis at redhat.com>
>
>
>
> Ok, this is one of the migration notes wiki pages we left with the customer. It contains what we ultimately had to do to get WS-Security working when moving from JBossWS Native in AS 4.2.3 to JBossCXF in EAP 6.2.3+. The plus sign is there because we had to also get a BZ created for us to fix two bugs we exposed while working with support to get them migrated. The BZs were installed as cumulative patches on top of CP 6.2.3.
>
> There were a lot of community resources for CXF and the WS-Security spec that we had to use to figure out how to get to the final product we ended up with. I will pull those out of the support case and try to formulate something on mojo hopefully in the coming week.
>
> Eric Sauer
> Red Hat Consulting
> www.redhat.com <http://www.redhat.com>
> eric at redhat.com <mailto:eric at redhat.com> | t.773.318.3036 <tel:773.318.3036>
>
> ----- Original Message -----
> From: "Eric Sauer"<esauer at redhat.com> <mailto:esauer at redhat.com>
> To: "Sande Gilda"<sgilda at redhat.com> <mailto:sgilda at redhat.com>
> Cc: "Brad Davis"<bdavis at redhat.com> <mailto:bdavis at redhat.com>
> Sent: Monday, August 18, 2014 5:32:58 PM
> Subject: Re: Migration Notes
>
> Hey Guys,
>
> I will get a copy of the documents I left with the customer around what needed changing during migration. We also have a support case around the CXF WS-Security migration which we could easily grab some notes from.
>
> Eric Sauer
> Red Hat Consulting
> www.redhat.com <http://www.redhat.com>
> eric at redhat.com <mailto:eric at redhat.com> | t.773.318.3036 <tel:773.318.3036>
>
> ----- Original Message -----
> From: "Sande Gilda"<sgilda at redhat.com> <mailto:sgilda at redhat.com>
> To: "Brad Davis"<bdavis at redhat.com> <mailto:bdavis at redhat.com>, "Eric Sauer"<esauer at redhat.com> <mailto:esauer at redhat.com>
> Sent: Monday, August 11, 2014 11:42:31 AM
> Subject: Re: Migration Notes
>
> Eric, any information you can provide would be extremely valuable!
>
> Thanks Brad!
>
> On 08/11/2014 08:34 AM, Brad Davis wrote:
> > Eric,
> > Sande takes care of migration documentation for JBoss. Can you pass
> > along any notes on web service migration, security context migration,
> > and other notes from the AAP project?
> >
> > Thanks,
> > Brad Davis
> > Red Hat Consulting
> > Email:bdavis at redhat.com <mailto:bdavis at redhat.com> <mailto:bdavis at redhat.com> <mailto:bdavis at redhat.com> | c:980.226.7865 <tel:980.226.7865>
> > <tel:980.226.7865 <tel:980.226.7865>> |http://www.redhat.com <http://www.redhat.com/> <http://www.redhat.com/>
>
>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140821/97b0253b/attachment-0001.html
From sgilda at redhat.com Thu Aug 21 06:15:26 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 21 Aug 2014 06:15:26 -0400
Subject: [windup-dev] Fwd: Re: Migration Notes
In-Reply-To: <53F5C16A.1090109@redhat.com>
References: <1646011176.25719531.1408400634001.JavaMail.zimbra@redhat.com> <53F2AF50.3070204@redhat.com> <1036363795.8464371.1408458820068.JavaMail.zimbra@redhat.com> <53F36749.6080506@redhat.com> <548195458.8517478.1408462455094.JavaMail.zimbra@redhat.com> <53F395D5.8030103@redhat.com> <451310137.8629509.1408473393682.JavaMail.zimbra@redhat.com>
<CAEp_U4F1jBVe12wJrWVk+d5toOXeJyrFXXH086G7r8cDzMWk8Q@mail.gmail.com>
<53F5C16A.1090109@redhat.com>
Message-ID: <53F5C6BE.1020501@redhat.com>
I realized the attachment contains customer data and I don't know how to
make it private in JIRA, so I removed it. I do point to the Bugzilla,
which does contain the attachment marked private.
On 08/21/2014 05:52 AM, Sande Gilda wrote:
> Done.
>
> Attached Eric's document to the JIRA and provided a link to my bug [1]
> to add the information to the JBoss Migration Guide.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1131493
>
> Sande
>
> On 08/20/2014 05:21 PM, Lincoln Baxter, III wrote:
>> Please add a JIRA in WINDUP using the following issue as a template:
>>
>> https://issues.jboss.org/browse/WINDUP-23
>>
>> Also please attach the document and provide as much detail as
>> possible in the description if anything in the document is missing or
>> unclear. Thank you!
>>
>> ~Lincoln
>>
>>
>> On Tue, Aug 19, 2014 at 2:36 PM, Robb Greathouse
>> <robb.greathouse at redhat.com <mailto:robb.greathouse at redhat.com>> wrote:
>>
>> I'll be discussing WebSphere migration with one of the lead
>> consultants tomorrow. I'll bring this up. Maybe they could
>> review and then John could approve.
>>
>>
>> Robb Greathouse
>> Chief Evangelist
>> Middleware Business Unit
>> JBoss, a Division of Red Hat
>> cellphone 505-507-4906 <tel:505-507-4906>
>>
>> ------------------------------------------------------------------------
>>
>> The problem is that the WebLogic and WebSphere Migration
>> Guides exist only in the internal content management system.
>> I could never find anyone to review them or give approval.
>> I'm not sure we want to link to an internal document, so I
>> will try to maintain the public Wiki pages in addition to the
>> product updates.
>>
>> If you could find some SMEs to review what's there, I am
>> willing to publish them with limited content with John
>> Doyle's approval. :-)
>>
>> On 08/19/2014 11:34 AM, Robb Greathouse wrote:
>>
>> Could we just put a link to the doc?
>>
>> Just want to get everything we have on migration linked
>> up and in one spot. Kenny Peeples is pulling together
>> everything over on mojo.
>>
>>
>> Robb Greathouse
>> Chief Evangelist
>> Middleware Business Unit
>> JBoss, a Division of Red Hat
>> cellphone 505-507-4906 <tel:505-507-4906>
>>
>> ------------------------------------------------------------------------
>>
>> I will try, but it is really had to keep multiple
>> versions of the doc up to date. :-)
>>
>> On 08/19/2014 10:33 AM, Robb Greathouse wrote:
>>
>> Will this get posted to migration.jboss.org
>> <http://migration.jboss.org>?
>>
>>
>> Robb Greathouse
>> Chief Evangelist
>> Middleware Business Unit
>> JBoss, a Division of Red Hat
>> cellphone 505-507-4906 <tel:505-507-4906>
>>
>> ------------------------------------------------------------------------
>>
>> Hi Eric,
>>
>> Thanks so much for sharing your notes. I will
>> try to update the JBoss Migration Guide with
>> this information. I am also copying the
>> Windup development team for addition to the
>> rules repository.
>>
>> Thanks again,
>> Sande
>>
>>
>> -------- Original Message --------
>> Subject: Re: Migration Notes
>> Date: Mon, 18 Aug 2014 18:23:54 -0400 (EDT)
>> From: Eric Sauer <esauer at redhat.com>
>> <mailto:esauer at redhat.com>
>> To: Sande Gilda <sgilda at redhat.com>
>> <mailto:sgilda at redhat.com>
>> CC: Brad Davis <bdavis at redhat.com>
>> <mailto:bdavis at redhat.com>
>>
>>
>>
>> Ok, this is one of the migration notes wiki pages we left with the customer. It contains what we ultimately had to do to get WS-Security working when moving from JBossWS Native in AS 4.2.3 to JBossCXF in EAP 6.2.3+. The plus sign is there because we had to also get a BZ created for us to fix two bugs we exposed while working with support to get them migrated. The BZs were installed as cumulative patches on top of CP 6.2.3.
>>
>> There were a lot of community resources for CXF and the WS-Security spec that we had to use to figure out how to get to the final product we ended up with. I will pull those out of the support case and try to formulate something on mojo hopefully in the coming week.
>>
>> Eric Sauer
>> Red Hat Consulting
>> www.redhat.com <http://www.redhat.com>
>> eric at redhat.com <mailto:eric at redhat.com> | t.773.318.3036 <tel:773.318.3036>
>>
>> ----- Original Message -----
>> From: "Eric Sauer"<esauer at redhat.com> <mailto:esauer at redhat.com>
>> To: "Sande Gilda"<sgilda at redhat.com> <mailto:sgilda at redhat.com>
>> Cc: "Brad Davis"<bdavis at redhat.com> <mailto:bdavis at redhat.com>
>> Sent: Monday, August 18, 2014 5:32:58 PM
>> Subject: Re: Migration Notes
>>
>> Hey Guys,
>>
>> I will get a copy of the documents I left with the customer around what needed changing during migration. We also have a support case around the CXF WS-Security migration which we could easily grab some notes from.
>>
>> Eric Sauer
>> Red Hat Consulting
>> www.redhat.com <http://www.redhat.com>
>> eric at redhat.com <mailto:eric at redhat.com> | t.773.318.3036 <tel:773.318.3036>
>>
>> ----- Original Message -----
>> From: "Sande Gilda"<sgilda at redhat.com> <mailto:sgilda at redhat.com>
>> To: "Brad Davis"<bdavis at redhat.com> <mailto:bdavis at redhat.com>, "Eric Sauer"<esauer at redhat.com> <mailto:esauer at redhat.com>
>> Sent: Monday, August 11, 2014 11:42:31 AM
>> Subject: Re: Migration Notes
>>
>> Eric, any information you can provide would be extremely valuable!
>>
>> Thanks Brad!
>>
>> On 08/11/2014 08:34 AM, Brad Davis wrote:
>> > Eric,
>> > Sande takes care of migration documentation for JBoss. Can you pass
>> > along any notes on web service migration, security context migration,
>> > and other notes from the AAP project?
>> >
>> > Thanks,
>> > Brad Davis
>> > Red Hat Consulting
>> > Email:bdavis at redhat.com <mailto:bdavis at redhat.com> <mailto:bdavis at redhat.com> <mailto:bdavis at redhat.com> | c:980.226.7865 <tel:980.226.7865>
>> > <tel:980.226.7865 <tel:980.226.7865>> |http://www.redhat.com <http://www.redhat.com/> <http://www.redhat.com/>
>>
>>
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> <mailto:windup-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140821/1a6997d2/attachment.html
From ozizka at redhat.com Tue Aug 26 19:40:34 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 27 Aug 2014 01:40:34 +0200
Subject: [windup-dev] WU1 runs, WU2 profiling
Message-ID: <53FD1AF2.5010300@redhat.com>
The separator for packages is colon, not coma.
When I use the right one, jad fails for me, too.
Unlike Jess, I don't know how to fix that.
So I at least wrote few scripts to automate running.
Profiling - my previous session crashed with OOME, twice (I thought 2,5
GB could be enough) so I set to 6 GB, hopefully that will pass. If not,
I'm out of hw resources to profile the big apps.
Ondra
From lincolnbaxter at gmail.com Wed Aug 27 10:41:58 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 27 Aug 2014 10:41:58 -0400
Subject: [windup-dev] Windup Meeting Minutes - 2014-08-27
Message-ID: <CAEp_U4Fe5FQKjm75Yk9Rre4O+OYbWV-LpoTC-1wfunv_mt74kA@mail.gmail.com>
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-08-27-14.08.html
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-08-27-14.08.txt
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-08-27-14.08.log.html
Meeting summary
---------------
* Agenda (lincolnthree, 14:08:46)
* Status Reports (lincolnthree, 14:11:53)
* Java-legacy rules are still not merged, always some problem
occurred, waiting for the the review (mbriskar, 14:12:46)
* XML-legacy rules API is almost ready, just needs fixing a
classloader's issue (mbriskar, 14:13:27)
* Worked on fixing WINDUP-233 over the past 2 days, work is now
complete with some help from jsightler (lincolnthree, 14:16:14)
* I'm now working on adding progress information to the Windup UI and
APIs - WINDUP-92 (lincolnthree, 14:16:52)
* Also working on reviewing the rules PRs from mbriskar
(lincolnthree, 14:17:24)
* I worked with lincolnthree some on WINDUP-233 (jsightler, 14:17:50)
* I have also been working on testing WU1.x vs WU 2.x (jsightler,
14:19:08)
* And I fixed WINDUP-231 (Classification details are not appearing in
Source reports) (jsightler, 14:19:40)
* Profiling: Even with 4 GB, it runs into OOME every time with bigger
app. With a small one, it runs for a while, but sometimes hits OOME
too. But before that, I am able to see some information. Mostly
decompiler calls. Nothing surprising found. (ozizka1, 14:19:57)
* Regarding test apps runs (with proper packages separator...), I have
quite some results, which I am processing into that table at google
docs. (ozizka1, 14:19:57)
* I've been looking for more apps, found few RH internal, which also
give interesting results. (ozizka1, 14:21:07)
* Focus and tasks (lincolnthree, 14:24:23)
* LINK: https://github.com/mbriskar/windup/pull/3 (jsightler,
14:35:45)
Meeting ended at 14:40:05 UTC.
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140827/41086cef/attachment.html
From jsightle at redhat.com Wed Aug 27 11:43:41 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Wed, 27 Aug 2014 11:43:41 -0400
Subject: [windup-dev] WU1 runs, WU2 profiling
In-Reply-To: <53FD1AF2.5010300@redhat.com>
References: <53FD1AF2.5010300@redhat.com>
Message-ID: <53FDFCAD.4050808@redhat.com>
For windup-legacy, I added the following (before the catch for
IOException) to JadretroDecompilerAdapter:
} catch (ExecuteException e) {
LOG.error("Expected decompiled source:
"+sourceOutputLocation.getAbsolutePath()+"; But failed with error: " +
e.getExitValue() + " message: " + e.getMessage());
}
This seemed to allow it to proceed (albeit with not all files decompiled).
On 08/26/2014 07:40 PM, Ondrej Zizka wrote:
> The separator for packages is colon, not coma.
> When I use the right one, jad fails for me, too.
> Unlike Jess, I don't know how to fix that.
> So I at least wrote few scripts to automate running.
>
> Profiling - my previous session crashed with OOME, twice (I thought 2,5
> GB could be enough) so I set to 6 GB, hopefully that will pass. If not,
> I'm out of hw resources to profile the big apps.
>
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Sat Aug 30 22:10:27 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Sun, 31 Aug 2014 04:10:27 +0200
Subject: [windup-dev] WU1 runs, WU2 profiling
In-Reply-To: <53FDFCAD.4050808@redhat.com>
References: <53FD1AF2.5010300@redhat.com> <53FDFCAD.4050808@redhat.com>
Message-ID: <54028413.4080303@redhat.com>
Ah, I see. I thought there was some trick with Jad itself.
Thanks.
On 27.8.2014 17:43, Jess Sightler wrote:
> For windup-legacy, I added the following (before the catch for
> IOException) to JadretroDecompilerAdapter:
>
> } catch (ExecuteException e) {
> LOG.error("Expected decompiled source:
> "+sourceOutputLocation.getAbsolutePath()+"; But failed with error: " +
> e.getExitValue() + " message: " + e.getMessage());
> }
>
> This seemed to allow it to proceed (albeit with not all files decompiled).
>
> On 08/26/2014 07:40 PM, Ondrej Zizka wrote:
>> The separator for packages is colon, not coma.
>> When I use the right one, jad fails for me, too.
>> Unlike Jess, I don't know how to fix that.
>> So I at least wrote few scripts to automate running.
>>
>> Profiling - my previous session crashed with OOME, twice (I thought 2,5
>> GB could be enough) so I set to 6 GB, hopefully that will pass. If not,
>> I'm out of hw resources to profile the big apps.
>>
>> Ondra
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Sun Aug 31 18:46:28 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 01 Sep 2014 00:46:28 +0200
Subject: [windup-dev] Windup 1 vs 2 comparison - automated
Message-ID: <5403A5C4.7030400@redhat.com>
Hi all,
I've finished automation of $subj.
In terms of speed, memory, and links to the reports and logs next to
each other, in a matrix.
Check the results here:
http://www.qa.jboss.com/~ozizka/Windup/compar/WindupComparison02/Results.html
http://www.qa.jboss.com/~ozizka/Windup/compar/WindupComparison02.zip
There are some issues with Windup 2.x - namely, failing with exceptions
inside of rules, not reacting to multiple --packages.
It needs a bit of setup - the test apps need to be at given relative paths.
Let me know if you are interested in running this for yourself.
I hope you'll find this useful.
Ondra
From kpeeples at redhat.com Tue Aug 19 11:50:31 2014
From: kpeeples at redhat.com (Kenny Peeples)
Date: Tue, 19 Aug 2014 11:50:31 -0400 (EDT)
Subject: [windup-dev] Fwd: Re: Migration Notes
In-Reply-To: <548195458.8517478.1408462455094.JavaMail.zimbra@redhat.com>
References: <1646011176.25719531.1408400634001.JavaMail.zimbra@redhat.com>
<53F2AF50.3070204@redhat.com>
<1036363795.8464371.1408458820068.JavaMail.zimbra@redhat.com>
<53F36749.6080506@redhat.com>
<548195458.8517478.1408462455094.JavaMail.zimbra@redhat.com>
Message-ID: <5368925.1995.1408463423986.JavaMail.kpeeples@kpeeples-laptop>
I will update you on this later this week for your feedback. pulling together customer deck to go along with the decks on the landing page and getting those over to a JBoss Migration World mojo space.
V/r
Kenneth W. Peeples, C|HFI, Security+
JBoss Technology Evangelist
OASIS and OMG Member
Cell: 843.754.6248
kpeeples at redhat.com
http://www.redhat.com
----- Original Message -----
From: "Robb Greathouse" <robb.greathouse at redhat.com>
To: "Sande Gilda" <sgilda at redhat.com>
Cc: "Windup-dev List" <windup-dev at lists.jboss.org>, "Eric Sauer" <esauer at redhat.com>, "Lincoln Baxter" <lbaxter at redhat.com>, "Kenny Peeples" <kpeeples at redhat.com>
Sent: Tuesday, August 19, 2014 11:34:15 AM
Subject: Re: [windup-dev] Fwd: Re: Migration Notes
Could we just put a link to the doc?
Just want to get everything we have on migration linked up and in one spot. Kenny Peeples is pulling together everything over on mojo.
Robb Greathouse
Chief Evangelist
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
----- Original Message -----
I will try, but it is really had to keep multiple versions of the doc up to date. :-)
On 08/19/2014 10:33 AM, Robb Greathouse wrote:
Will this get posted to migration.jboss.org?
Robb Greathouse
Chief Evangelist
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
----- Original Message -----
Hi Eric,
Thanks so much for sharing your notes. I will try to update the JBoss Migration Guide with this information. I am also copying the Windup development team for addition to the rules repository.
Thanks again,
Sande
-------- Original Message --------
Subject: Re: Migration Notes
Date: Mon, 18 Aug 2014 18:23:54 -0400 (EDT)
From: Eric Sauer <esauer at redhat.com>
To: Sande Gilda <sgilda at redhat.com>
CC: Brad Davis <bdavis at redhat.com>
Ok, this is one of the migration notes wiki pages we left with the customer. It contains what we ultimately had to do to get WS-Security working when moving from JBossWS Native in AS 4.2.3 to JBossCXF in EAP 6.2.3+. The plus sign is there because we had to also get a BZ created for us to fix two bugs we exposed while working with support to get them migrated. The BZs were installed as cumulative patches on top of CP 6.2.3.
There were a lot of community resources for CXF and the WS-Security spec that we had to use to figure out how to get to the final product we ended up with. I will pull those out of the support case and try to formulate something on mojo hopefully in the coming week.
Eric Sauer
Red Hat Consulting www.redhat.com eric at redhat.com | t. 773.318.3036
----- Original Message -----
From: "Eric Sauer" <esauer at redhat.com> To: "Sande Gilda" <sgilda at redhat.com> Cc: "Brad Davis" <bdavis at redhat.com> Sent: Monday, August 18, 2014 5:32:58 PM
Subject: Re: Migration Notes
Hey Guys,
I will get a copy of the documents I left with the customer around what needed changing during migration. We also have a support case around the CXF WS-Security migration which we could easily grab some notes from.
Eric Sauer
Red Hat Consulting www.redhat.com eric at redhat.com | t. 773.318.3036
----- Original Message -----
From: "Sande Gilda" <sgilda at redhat.com> To: "Brad Davis" <bdavis at redhat.com> , "Eric Sauer" <esauer at redhat.com> Sent: Monday, August 11, 2014 11:42:31 AM
Subject: Re: Migration Notes
Eric, any information you can provide would be extremely valuable!
Thanks Brad!
On 08/11/2014 08:34 AM, Brad Davis wrote:
> Eric,
> Sande takes care of migration documentation for JBoss. Can you pass
> along any notes on web service migration, security context migration,
> and other notes from the AAP project?
>
> Thanks,
> Brad Davis
> Red Hat Consulting
> Email: bdavis at redhat.com <mailto:bdavis at redhat.com> | c:980.226.7865
> <tel:980.226.7865> | http://www.redhat.com <http://www.redhat.com/>
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list windup-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/windup-dev
From lincolnbaxter at gmail.com Fri Aug 29 16:32:50 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 29 Aug 2014 16:32:50 -0400
Subject: [windup-dev] Reports looking a little odd:
Message-ID: <CAEp_U4EDwoU2QVXBZ_OW4OYqw2Of4gF4qiWdRVioEEO8XpfZTg@mail.gmail.com>
See screen shots.. but good news is that we are actually generating
information that shows up! Let's keep up the good work!
[image: Inline image 2][image: Inline image 1]
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140829/4114792c/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2014-08-29 at 4.31.26 PM.png
Type: image/png
Size: 795898 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20140829/4114792c/attachment-0002.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2014-08-29 at 4.32.19 PM.png
Type: image/png
Size: 960413 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20140829/4114792c/attachment-0003.png