From lincolnbaxter at gmail.com  Mon Dec  1 10:45:05 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 1 Dec 2014 10:45:05 -0500
Subject: [windup-dev] XML rules test failure
In-Reply-To: <5476BE44.9080809@redhat.com>
References: <5476BE44.9080809@redhat.com>
Message-ID: <CAEp_U4EeBRXQjt18YXBjzGOzxQh4_e-=LzB15=iMiK6xzzpqNg@mail.gmail.com>

Just off the top of my head. Are you sure your local work is sync'd with
what is in the repo? These look like old failures from a long time ago. Hm.
Either that or you somehow managed to reproduce a phantom problem I had
recently in your test environment.

On Thu, Nov 27, 2014 at 1:01 AM, Ondrej Zizka <ozizka at redhat.com> wrote:

> Hi,
>
> this is what I get with current master.
> However on Jenkins it's ok.
> Any idea what can be wrong?
>
> Thanks,
> Ondra
>
>
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 18.532
> sec <<< FAILURE! - in
> org.jboss.windup.rules.xml.XMLTransformationXMLRulesTest
>
> testXSLTTransformation(org.jboss.windup.rules.xml.XMLTransformationXMLRulesTest)
> Time elapsed: 6.247 sec  <<< FAILURE!
> java.lang.AssertionError: null
>      at org.junit.Assert.fail(Assert.java:86)
>      at org.junit.Assert.assertTrue(Assert.java:41)
>      at org.junit.Assert.assertTrue(Assert.java:52)
>      at
>
> org.jboss.windup.rules.xml.XMLTransformationXMLRulesTest.testXSLTTransformation(XMLTransformationXMLRulesTest.java:118)
>
>
> Results :
>
> Failed tests:
>    XMLTransformationTest.testXSLTTransformation:126 null
> GroovyExtensionXmlRulesTest.testHintsAndClassificationOperation:120
> expected:<2> but was:<0>
>    XMLFileNestedConditionTest.testNestedCondition:128 expected:<1> but
> was:<0>
>    XMLHintsClassificationsTest.testHintAndClassificationOperation:130
> expected:<2> but was:<0>
>    XMLTransformationXMLRulesTest.testXSLTTransformation:118 null
> _______________________________________________
> 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/20141201/e04ac35b/attachment.html 

From lincolnbaxter at gmail.com  Mon Dec  1 17:02:53 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 1 Dec 2014 17:02:53 -0500
Subject: [windup-dev] XmlFile vs. XmlFileCondition
In-Reply-To: <5473BCE5.4020806@redhat.com>
References: <5473BCE5.4020806@redhat.com>
Message-ID: <CAEp_U4Fhk5BDSFyc2goOV+0ZWgXs1SNUmrX_paXby7mYXz6WpQ@mail.gmail.com>

Not sure I think that changing the name to be different than what shows up
in the rule "stringification". I think what we have now is fairly
straightforward unless I misunderstood you. It's already in the
".condition." package afaik.

On Mon, Nov 24, 2014 at 6:19 PM, Ondrej Zizka <ozizka at redhat.com> wrote:

> Hi,
>
> wouldn't it be better to split XmlFile's static code from what should
> really be a XmlCondition? For the sake of code readability and
> debugging. From user's PoV it would be the same - he would still see
>
>      .when(XmlFile.matchesXpath("//catalog/chain | //catalog/chains"))
>
> 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/20141201/d46a8acc/attachment.html 

From ozizka at redhat.com  Mon Dec  1 22:27:47 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Tue, 02 Dec 2014 04:27:47 +0100
Subject: [windup-dev] Reliably getting class name of a RuleProvider?
Message-ID: <547D31B3.1000404@redhat.com>

     Hi,

I want to filter the rule providers.
Due to modularization, the Class object may not equal().
Due to Javassist, the class name is org.foo.Bar_$$_javassist_....

How can I reliably identify the class of the Rule provider?

Thanks,
Ondra

From ozizka at redhat.com  Mon Dec  1 23:46:52 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Tue, 02 Dec 2014 05:46:52 +0100
Subject: [windup-dev] XML rules test failure
In-Reply-To: <CAEp_U4EeBRXQjt18YXBjzGOzxQh4_e-=LzB15=iMiK6xzzpqNg@mail.gmail.com>
References: <5476BE44.9080809@redhat.com>
	<CAEp_U4EeBRXQjt18YXBjzGOzxQh4_e-=LzB15=iMiK6xzzpqNg@mail.gmail.com>
Message-ID: <547D443C.8080000@redhat.com>

It happenned in master, and did not on Beta 5.

Could you share what was the problem about? I didn't go through the 
graph to check what is actually missing and why (rather continued coding 
Victims).
Let's discuss on IRC today.

Regards,
Ondra


On 1.12.2014 16:45, Lincoln Baxter, III wrote:
> Just off the top of my head. Are you sure your local work is sync'd 
> with what is in the repo? These look like old failures from a long 
> time ago. Hm. Either that or you somehow managed to reproduce a 
> phantom problem I had recently in your test environment.
>
> On Thu, Nov 27, 2014 at 1:01 AM, Ondrej Zizka <ozizka at redhat.com 
> <mailto:ozizka at redhat.com>> wrote:
>
>     Hi,
>
>     this is what I get with current master.
>     However on Jenkins it's ok.
>     Any idea what can be wrong?
>
>     Thanks,
>     Ondra
>
>
>     Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 18.532
>     sec <<< FAILURE! - in
>     org.jboss.windup.rules.xml.XMLTransformationXMLRulesTest
>     testXSLTTransformation(org.jboss.windup.rules.xml.XMLTransformationXMLRulesTest)
>     Time elapsed: 6.247 sec  <<< FAILURE!
>     java.lang.AssertionError: null
>          at org.junit.Assert.fail(Assert.java:86)
>          at org.junit.Assert.assertTrue(Assert.java:41)
>          at org.junit.Assert.assertTrue(Assert.java:52)
>          at
>     org.jboss.windup.rules.xml.XMLTransformationXMLRulesTest.testXSLTTransformation(XMLTransformationXMLRulesTest.java:118)
>
>
>     Results :
>
>     Failed tests:
>        XMLTransformationTest.testXSLTTransformation:126 null
>     GroovyExtensionXmlRulesTest.testHintsAndClassificationOperation:120
>     expected:<2> but was:<0>
>        XMLFileNestedConditionTest.testNestedCondition:128 expected:<1> but
>     was:<0>
>      XMLHintsClassificationsTest.testHintAndClassificationOperation:130
>     expected:<2> but was:<0>
>        XMLTransformationXMLRulesTest.testXSLTTransformation:118 null
>     _______________________________________________
>     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/20141202/ec0aa90f/attachment.html 

From ozizka at redhat.com  Tue Dec  2 01:03:16 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Tue, 02 Dec 2014 07:03:16 +0100
Subject: [windup-dev] What's the difference between ArchiveModel
	#archiveName and #fileName?
Message-ID: <547D5624.3010101@redhat.com>

What's the difference between ArchiveModel #archiveName and #fileName?

Thanks,
Ondra

From jsightle at redhat.com  Tue Dec  2 09:56:52 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Tue, 02 Dec 2014 09:56:52 -0500
Subject: [windup-dev] What's the difference between ArchiveModel
 #archiveName and #fileName?
In-Reply-To: <547D5624.3010101@redhat.com>
References: <547D5624.3010101@redhat.com>
Message-ID: <547DD334.3050500@redhat.com>

I don't think there really is one. It looks like we are always setting 
archiveName to the filename.

On 12/02/2014 01:03 AM, Ondrej Zizka wrote:
> What's the difference between ArchiveModel #archiveName and #fileName?
>
> Thanks,
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev


From lincolnbaxter at gmail.com  Wed Dec  3 11:40:26 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 3 Dec 2014 11:40:26 -0500
Subject: [windup-dev] Windup meeting minutes - 2014-12-03
Message-ID: <CAEp_U4EdTNJKUXwZq7kwugxtHSXDMGcsvDT2k1jFbm-yO0hO_w@mail.gmail.com>

Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-12-03-15.04.html

Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-12-03-15.04.txt

Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-12-03-15.04.log.html

Meeting summary
---------------
* Agenda  (lincolnthree, 15:04:09)

* Status Reports  (lincolnthree, 15:08:29)
  * last week I was on PTO. (I am off again on Friday)  (lincolnthree,
    15:09:08)
  * This week I've reviewed some PRs and resumed work on the pr for
    WINDUP-377  (lincolnthree, 15:09:23)
  * I should have an integrated PR by this afternoon. I'm pretty close.
    (lincolnthree, 15:09:40)
  * I plan on finishing that up and doing general housekeeping for the
    rest of the week.  (lincolnthree, 15:11:12)
  * I have fixed WINDUP-321 (internal tool for iterating over frames as
    if they were just vertices), WINDUP-371 (crasher bug with some input
    ears), and WINDUP-391 (Iteration support for the XML rules format)
    (jsightler, 15:15:43)
  * Also, the decompilation threading thing is finished (thanks mbriskar
    for getting that going), and there is work in progress to really
    speed up TypeInterestFactory  (jsightler, 15:16:26)
  * I am still migrating the rules from java to xml. I gathered the
    functionality requests and put it inside the WINDUP-401 that is
    already merged  (mbriskar, 15:21:52)
  * so now I continue and fixing some small issues, the xmls look almost
    done, I am just perfectionalist because don't want to miss something
    there (otherwise it would be just lost probably)  (mbriskar,
    15:22:35)
  * plus trying to record the screencast for forge (but this does
    nothing with windup)  (mbriskar, 15:23:37)
  * WINDUP-355 Victi.ms - finished, including report.  (ozizka,
    15:35:21)
  * WINDUP-400 Renaming some methods - suggestion.  (ozizka, 15:35:21)
  * Looked shortly into XML tests crashing locally, didn't figure out
    (ozizka, 15:35:21)
  * Did WINDUP-395  Review rules metadata - IDs, categories etc.
    (ozizka, 15:36:35)
  * Did WINDUP-394                  Support default value in
    WindupConfigurationOption  (ozizka, 15:37:05)
  * Spent some time on wiki docs again, trying to systemize the Rulesets
    subset  (ozizka, 15:38:41)
  * I Will need help from the team.  I'm suggesting some structure, and
    until automated (when Windup core is ready to give that),  some
    basic data will need to be added manually  (ozizka, 15:39:44)
  * Did WINDUP-411                  Report multiple rules sorting
    metadata errors at once  (ozizka, 15:40:28)
  * Did WINDUP-410                  Weird wording of after/before vs.
    phase constraints exceptions    - not sure if PR was sent, if not, I
    will  (ozizka, 15:41:35)
  * Fixed WINDUP-404                  Returning this from Model setter
    doesn't always work (at least for my case it works ;-)  (ozizka,
    15:42:37)
  * I'd like to work on WINDUP-398 Rules request: Ignored jars by G:A:V
    and hashes - another possible speedup. JBoss.org team works on a
    tool from which we could get data automatically regularly.  (ozizka,
    15:48:13)
  * IDEA: WINDUP-398 Rules request: Ignored jars by G:A:V and hashes
    (ozizka, 15:48:14)
  * IDEA: WINDUP-396 Automate copying options to graph  (ozizka,
    15:48:14)
  * IDEA: WINDUP-387 Add to UI: "run this rule and all that it depends
    on"  (ozizka, 15:48:14)
  * IDEA: WINDUP-384 Iteration.over(Foo.class) to load Foo's if none
    found on varstack.  (ozizka, 15:48:14)
  * IDEA: WINDUP-409 Allow rules metadata to annotations - @Rules( phase
    = ..., ...)  (ozizka, 15:48:14)
  * IDEA: WINDUP-403 Add "supported version range" to ruleset metadata
    (ozizka, 15:48:14)
  * IDEA: WINDUP-402 Change ruleset category metadata to tag-like system
    (make it a set of strings)  (ozizka, 15:48:14)
  * IDEA: WINDUP-400 Rename some model methods  (ozizka, 15:48:15)
  * IDEA: WINDUP-397 Split XmlFileCondition from XmlFile  (ozizka,
    15:48:15)

* Project Priorities  (lincolnthree, 15:52:23)
  * Priorities remain unchanged. Performance and stability improvement
    is #1  (lincolnthree, 15:52:39)
  * Usability improvements #2 (including rules syntax/functionality)
    (lincolnthree, 15:52:59)
  * General enhancements and quality improvement / simplifications /
    refactoring #3 (I think)  (lincolnthree, 15:53:27)

* Hint.in vs Classification.of  (lincolnthree, 15:54:19)

* Iteration.over() behaviour  (lincolnthree, 15:58:40)

* WINDUP-399                  Conditions and Operations in XML syntax
  derived from class (without a need for wrapper)  (ozizka, 16:07:19)

* Java vs xml rules  (ozizka, 16:07:58)
  * About XML vs. Java  - I often see some statements like "users prefer
    that" or "that will better be done with XML syntax", but I do not
    know about any bigger to-the-point document or discussion of these
    statements. I don't know what the XML syntax will cover, whether it
    will have a generic nature or rather specialized, backed by a
    Ruleset / Conditions / Operations  (ozizka, 16:08:02)

Meeting ended at 16:28:11 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/20141203/47a4f3c9/attachment-0001.html 

From lincoln at redhat.com  Wed Dec  3 13:44:35 2014
From: lincoln at redhat.com (Lincoln Baxter, III)
Date: Wed, 3 Dec 2014 13:44:35 -0500 (EST)
Subject: [windup-dev] Missing items from reports
In-Reply-To: <1024959008.26657458.1417632225096.JavaMail.zimbra@redhat.com>
Message-ID: <1075317223.26657954.1417632275025.JavaMail.zimbra@redhat.com>

Hey Marc,

You'd mentioned that there was some missing information on the reports from Windup 2, could you give some examples of that? We'd like to get that fixed if possible!

Thanks,
Lincoln

--
Lincoln Baxter, III
JBoss, by Red Hat
lbaxter at redhat.com

"If you want something, you'll find a way; if you don't, you'll find an excuse."

From ozizka at redhat.com  Tue Dec  9 18:08:12 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 10 Dec 2014 00:08:12 +0100
Subject: [windup-dev] Meeting topic: Parametrization
Message-ID: <548780DC.8070504@redhat.com>

Hi all,

I don't get the parametrization. Could we please include that on 
tomorrow's meeting and discuss it a bit deeper than a link to 
uncommented PR or code snippet? It may feel geeky to avoid creating a 
normal text containing what should be achieved and what are the 
available alternatives, but forgive me, I prefer to have it, at least 
for such key concepts.

Thanks for understanding :)
Ondra

From ozizka at redhat.com  Tue Dec  9 19:16:58 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 10 Dec 2014 01:16:58 +0100
Subject: [windup-dev] Meeting topic: Parametrization
In-Reply-To: <548780DC.8070504@redhat.com>
References: <548780DC.8070504@redhat.com>
Message-ID: <548790FA.9070900@redhat.com>

To sum up what I know:

* It is not related to the "graph write, then query" paradigm
* Supposedly not substituting it(?), the addressed task can not be done 
using the mentioned paradigm(?)
* Used only in XPath(?)
* Should carry values both in and out of XPath
* Can't be achieved using standard XPath parametrization (namely the 
"out" part - ?)

Ondra


On 10.12.2014 00:08, Ondrej Zizka wrote:
> Hi all,
>
> I don't get the parametrization. Could we please include that on
> tomorrow's meeting and discuss it a bit deeper than a link to
> uncommented PR or code snippet? It may feel geeky to avoid creating a
> normal text containing what should be achieved and what are the
> available alternatives, but forgive me, I prefer to have it, at least
> for such key concepts.
>
> Thanks for understanding :)
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev


From lincolnbaxter at gmail.com  Tue Dec  9 23:50:58 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 9 Dec 2014 23:50:58 -0500
Subject: [windup-dev] Problems with XML
Message-ID: <CAEp_U4H93t3iHsGkYaa0VO6b4fvDUFCbdc3ZqyTnA8wavXuBDQ@mail.gmail.com>

Matej,

This XML is repeated in almost all the rules we have so far...

> <perform>
>    <iteration>
>         <hint .... >
>    </iteration>
> </perform>

This XML mayactually be creating a nested iteration over no elements. One
iteration created by default in the <perform> method, the next one by the
subsequent <iteration>...

Iteration is implied if omitted, so this may be the problem, not sure.
I am going to look into this more tomorrow. But if you get to it before I
do, this may be a place to start looking. Try removing the <iteration> tags
and putting the child nodes into <perform> directly.

-- 
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/20141209/37f719ec/attachment.html 

From lincolnbaxter at gmail.com  Tue Dec  9 23:56:35 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 9 Dec 2014 23:56:35 -0500
Subject: [windup-dev] Meeting topic: Parametrization
In-Reply-To: <548790FA.9070900@redhat.com>
References: <548780DC.8070504@redhat.com>
	<548790FA.9070900@redhat.com>
Message-ID: <CAEp_U4HbOACYTJ75t3uR2ZjL-6J3Jr4y52mhKcxpoKJZjsbNjA@mail.gmail.com>

Sure, we can discuss during the meeting.

First, please read the following documentation:
http://ocpsoft.org/rewrite/docs/configuration/parameters

This describes how the parameter system works at a general level. It should
be fairly clear how this works in the PR code that I sent previously -->
Look at the following test case to see an example of how this can be used
in our code:
https://github.com/windup/windup/pull/335/files?diff=split#diff-cb609dbaa9c00a99e875750fa8a13ec5R208

In short:

Conditions extract and constrain by the parameter values. Operations use
the extracted parameter values to generate output/results.

~Lincoln

On Tue, Dec 9, 2014 at 7:16 PM, Ondrej Zizka <ozizka at redhat.com> wrote:

> To sum up what I know:
>
> * It is not related to the "graph write, then query" paradigm
> * Supposedly not substituting it(?), the addressed task can not be done
> using the mentioned paradigm(?)
> * Used only in XPath(?)
> * Should carry values both in and out of XPath
> * Can't be achieved using standard XPath parametrization (namely the
> "out" part - ?)
>
> Ondra
>
>
> On 10.12.2014 00:08, Ondrej Zizka wrote:
> > Hi all,
> >
> > I don't get the parametrization. Could we please include that on
> > tomorrow's meeting and discuss it a bit deeper than a link to
> > uncommented PR or code snippet? It may feel geeky to avoid creating a
> > normal text containing what should be achieved and what are the
> > available alternatives, but forgive me, I prefer to have it, at least
> > for such key concepts.
> >
> > Thanks for understanding :)
> > 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/20141209/3e9e67d5/attachment.html 

From lincolnbaxter at gmail.com  Wed Dec 10 00:01:17 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 10 Dec 2014 00:01:17 -0500
Subject: [windup-dev] XML rules test failure
In-Reply-To: <547D443C.8080000@redhat.com>
References: <5476BE44.9080809@redhat.com>
	<CAEp_U4EeBRXQjt18YXBjzGOzxQh4_e-=LzB15=iMiK6xzzpqNg@mail.gmail.com>
	<547D443C.8080000@redhat.com>
Message-ID: <CAEp_U4FTRMWk7jeXkRpX7um1RpV=yy5BYu5m=X--dtwdrcKUXw@mail.gmail.com>

I don't know exactly what the problem was, but it occurred on my branch
where I was doing a bunch of refactoring. It occurred then did not and I
could not reproduce it, and without seeing the root cause of your issue,
it's hard to theorize on what is wrong. Try checking what the assertion is
failing on, and debugging to find the root cause if necessary.

On Mon, Dec 1, 2014 at 11:46 PM, Ondrej Zizka <ozizka at redhat.com> wrote:

>  It happenned in master, and did not on Beta 5.
>
> Could you share what was the problem about? I didn't go through the graph
> to check what is actually missing and why (rather continued coding Victims).
> Let's discuss on IRC today.
>
> Regards,
> Ondra
>
>
>
> On 1.12.2014 16:45, Lincoln Baxter, III wrote:
>
> Just off the top of my head. Are you sure your local work is sync'd with
> what is in the repo? These look like old failures from a long time ago. Hm.
> Either that or you somehow managed to reproduce a phantom problem I had
> recently in your test environment.
>
> On Thu, Nov 27, 2014 at 1:01 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
>
>> Hi,
>>
>> this is what I get with current master.
>> However on Jenkins it's ok.
>> Any idea what can be wrong?
>>
>> Thanks,
>> Ondra
>>
>>
>> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 18.532
>> sec <<< FAILURE! - in
>> org.jboss.windup.rules.xml.XMLTransformationXMLRulesTest
>>
>> testXSLTTransformation(org.jboss.windup.rules.xml.XMLTransformationXMLRulesTest)
>> Time elapsed: 6.247 sec  <<< FAILURE!
>> java.lang.AssertionError: null
>>      at org.junit.Assert.fail(Assert.java:86)
>>      at org.junit.Assert.assertTrue(Assert.java:41)
>>      at org.junit.Assert.assertTrue(Assert.java:52)
>>      at
>>
>> org.jboss.windup.rules.xml.XMLTransformationXMLRulesTest.testXSLTTransformation(XMLTransformationXMLRulesTest.java:118)
>>
>>
>> Results :
>>
>> Failed tests:
>>    XMLTransformationTest.testXSLTTransformation:126 null
>> GroovyExtensionXmlRulesTest.testHintsAndClassificationOperation:120
>> expected:<2> but was:<0>
>>    XMLFileNestedConditionTest.testNestedCondition:128 expected:<1> but
>> was:<0>
>>    XMLHintsClassificationsTest.testHintAndClassificationOperation:130
>> expected:<2> but was:<0>
>>    XMLTransformationXMLRulesTest.testXSLTTransformation:118 null
>> _______________________________________________
>> 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/20141210/ae0cc414/attachment.html 

From bdavis at redhat.com  Wed Dec 10 09:57:54 2014
From: bdavis at redhat.com (Brad Davis)
Date: Wed, 10 Dec 2014 09:57:54 -0500 (EST)
Subject: [windup-dev] Problems with XML
In-Reply-To: <CAEp_U4H93t3iHsGkYaa0VO6b4fvDUFCbdc3ZqyTnA8wavXuBDQ@mail.gmail.com>
References: <CAEp_U4H93t3iHsGkYaa0VO6b4fvDUFCbdc3ZqyTnA8wavXuBDQ@mail.gmail.com>
Message-ID: <13641383.24153866.1418223474579.JavaMail.zimbra@redhat.com>

I think maybe the processor itself would be aware of whether it should be iterative or single.  For example, Classification should know "I may get a set of results, but I only need one result to properly classify this resource".  While, Hints should know "If I get a set of results, I should add it to each one." 

That is my thought anyway.

Brad Davis
Senior Manager, 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: "Matej Briskar" <mbriskar at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Tuesday, December 9, 2014 11:50:58 PM
Subject: [windup-dev] Problems with XML



Matej, 

This XML is repeated in almost all the rules we have so far... 

<perform> 
<iteration> 
<hint .... > 
</iteration> 
</perform> 

This XML mayactually be creating a nested iteration over no elements. One iteration created by default in the <perform> method, the next one by the subsequent <iteration>... 

Iteration is implied if omitted, so this may be the problem, not sure. 
I am going to look into this more tomorrow. But if you get to it before I do, this may be a place to start looking. Try removing the <iteration> tags and putting the child nodes into <perform> directly. 

-- 
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 lincolnbaxter at gmail.com  Wed Dec 10 10:33:58 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 10 Dec 2014 10:33:58 -0500
Subject: [windup-dev] Problems with XML
In-Reply-To: <13641383.24153866.1418223474579.JavaMail.zimbra@redhat.com>
References: <CAEp_U4H93t3iHsGkYaa0VO6b4fvDUFCbdc3ZqyTnA8wavXuBDQ@mail.gmail.com>
	<13641383.24153866.1418223474579.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4H5unmJE+29i4M0oDpkK9EbnxXVSjoZJKN5HAGuOa1K+g@mail.gmail.com>

Yeah, everything is iterated over, even if there is only a single result.
The problem here is that for some reason no result frames are being passed
to the operations. Not so much an architectural issue, rather a bug.

On Wed, Dec 10, 2014 at 9:57 AM, Brad Davis <bdavis at redhat.com> wrote:

> I think maybe the processor itself would be aware of whether it should be
> iterative or single.  For example, Classification should know "I may get a
> set of results, but I only need one result to properly classify this
> resource".  While, Hints should know "If I get a set of results, I should
> add it to each one."
>
> That is my thought anyway.
>
> Brad Davis
> Senior Manager, 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: "Matej Briskar" <mbriskar at redhat.com>, "Windup-dev List" <
> windup-dev at lists.jboss.org>
> Sent: Tuesday, December 9, 2014 11:50:58 PM
> Subject: [windup-dev] Problems with XML
>
>
>
> Matej,
>
> This XML is repeated in almost all the rules we have so far...
>
> <perform>
> <iteration>
> <hint .... >
> </iteration>
> </perform>
>
> This XML mayactually be creating a nested iteration over no elements. One
> iteration created by default in the <perform> method, the next one by the
> subsequent <iteration>...
>
> Iteration is implied if omitted, so this may be the problem, not sure.
> I am going to look into this more tomorrow. But if you get to it before I
> do, this may be a place to start looking. Try removing the <iteration> tags
> and putting the child nodes into <perform> directly.
>
> --
> 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
>



-- 
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/20141210/1259ed26/attachment.html 

From lincolnbaxter at gmail.com  Wed Dec 10 11:22:19 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 10 Dec 2014 11:22:19 -0500
Subject: [windup-dev] Windup Meeting Minutes - 2014-12-10
Message-ID: <CAEp_U4FmMw-tdfdtDjLewCsmJ9ky7EHdRv41HtODSRRBdwOGoQ@mail.gmail.com>

Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-12-10-15.01.html

Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-12-10-15.01.txt

Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-12-10-15.01.log.html

Meeting summary
---------------
* Agenda  (lincolnthree, 15:02:08)

* Status Reports  (lincolnthree, 15:02:14)

* Agenda  (lincolnthree, 15:02:21)

* Status Reports  (lincolnthree, 15:04:24)
  * Nothing spectacular from me. I am working on merging the rule
    parameterization and XML rule conversion, but running into a few
    roadblocks (something not right with XML rules at the moment,) but
    working on figuring it out. Seems like something simple.
    (lincolnthree, 15:06:19)
  * Once that is done (WINDUP-377) I plan on working on refactoring and
    simplifying / reviewing UX.  (lincolnthree, 15:06:43)
  * I have resolved WINDUP-340 (report of freemarker functions and
    directives)  (jsightler, 15:09:21)
  * WINDUP-382 - Increase defaults for permgen and codecachesize
    (improves performance and avoids some common out of memory errors
    with the defaults)  (jsightler, 15:09:46)
  * WINDUP-406 - TypeInterestFactory perf improvement
    (typeinterestfactory is no longer our slowest point :) )
    (jsightler, 15:10:11)
  * And WINDUP-416 (memory usage reduction)  (jsightler, 15:10:40)
  * I'm planning to look over the current parameterization stuff soon,
    and then hopefully continue with some performance stuff (maybe
    multithreading in a couple of key places)  (jsightler, 15:12:00)
  * still playing with migrating legacy rules to XML, besides started to
    work on WINDUP-407 ...  (mbriskar, 15:12:38)
  * Worked on the PRs as per comments:  (ozizka, 15:20:20)
  * Review rules metadata WINDUP-395  (ozizka, 15:20:21)
  * WINDUP-394 Support default value in WindupConfigurationOption
    (ozizka, 15:20:21)
  * WINDUP-411 Report multiple rules sorting metadata errors at once
    (ozizka, 15:20:21)
  * WINDUP-417 WindupRuleProviderSorter - make the error message
    clearer, shorten  (ozizka, 15:20:21)
  * Been working on a Ruleset for automated archives ignoring, the part
    of getting data from JBoss Nexus  (ozizka, 15:20:21)
  * New Javadoc 2.0.0.Beta6 online  (ozizka, 15:20:21)
  * WINDUP-422 Make Javadoc crosslink with Forge  (ozizka, 15:20:22)
  * WINDUP-409 Allow rules metadata to annotations - @Rules (test not
    finished, was not a priority)  (ozizka, 15:20:22)

* Priorities  (lincolnthree, 15:24:59)
  * Priorities are unchanged:  (lincolnthree, 15:28:54)
  * 1. Rules parameterization & Usability improvements  (lincolnthree,
    15:29:10)
  * 2. Performance enhancements  (lincolnthree, 15:29:20)
  * 3. Stability improvements  (lincolnthree, 15:30:44)

* Rule Parameterization  (lincolnthree, 15:31:26)
  * LINK:
    https://github.com/lincolnthree/windup/blob/PARAMETERIZED_RULES/rules-java/src/main/java/org/jboss/windup/rules/apps/java/condition/JavaClass.java#L188
    (jsightler, 16:11:41)

-- 
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/20141210/2aa61f62/attachment.html 

From mbriskar at redhat.com  Wed Dec 10 11:58:42 2014
From: mbriskar at redhat.com (Matej Briskar)
Date: Wed, 10 Dec 2014 11:58:42 -0500 (EST)
Subject: [windup-dev] Problems with XML
In-Reply-To: <CAEp_U4H5unmJE+29i4M0oDpkK9EbnxXVSjoZJKN5HAGuOa1K+g@mail.gmail.com>
References: <CAEp_U4H93t3iHsGkYaa0VO6b4fvDUFCbdc3ZqyTnA8wavXuBDQ@mail.gmail.com>
	<13641383.24153866.1418223474579.JavaMail.zimbra@redhat.com>
	<CAEp_U4H5unmJE+29i4M0oDpkK9EbnxXVSjoZJKN5HAGuOa1K+g@mail.gmail.com>
Message-ID: <1983652290.11630536.1418230722855.JavaMail.zimbra@redhat.com>

I think there is already a fix online in the PR. The problem was in Handler processing the xmls. (as discussed on IRC)

----- Original Message -----
From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com>
To: "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Wednesday, December 10, 2014 4:33:58 PM
Subject: Re: [windup-dev] Problems with XML

Yeah, everything is iterated over, even if there is only a single result. The problem here is that for some reason no result frames are being passed to the operations. Not so much an architectural issue, rather a bug. 

On Wed, Dec 10, 2014 at 9:57 AM, Brad Davis < bdavis at redhat.com > wrote: 


I think maybe the processor itself would be aware of whether it should be iterative or single. For example, Classification should know "I may get a set of results, but I only need one result to properly classify this resource". While, Hints should know "If I get a set of results, I should add it to each one." 

That is my thought anyway. 

Brad Davis 
Senior Manager, 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: "Matej Briskar" < mbriskar at redhat.com >, "Windup-dev List" < windup-dev at lists.jboss.org > 
Sent: Tuesday, December 9, 2014 11:50:58 PM 
Subject: [windup-dev] Problems with XML 



Matej, 

This XML is repeated in almost all the rules we have so far... 

<perform> 
<iteration> 
<hint .... > 
</iteration> 
</perform> 

This XML mayactually be creating a nested iteration over no elements. One iteration created by default in the <perform> method, the next one by the subsequent <iteration>... 

Iteration is implied if omitted, so this may be the problem, not sure. 
I am going to look into this more tomorrow. But if you get to it before I do, this may be a place to start looking. Try removing the <iteration> tags and putting the child nodes into <perform> directly. 

-- 
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 



-- 
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 lincoln at redhat.com  Thu Dec 11 10:19:00 2014
From: lincoln at redhat.com (Lincoln Baxter, III)
Date: Thu, 11 Dec 2014 10:19:00 -0500 (EST)
Subject: [windup-dev] LogOperation?
In-Reply-To: <54879AF6.9090001@redhat.com>
References: <54879AF6.9090001@redhat.com>
Message-ID: <2033999199.34540481.1418311140118.JavaMail.zimbra@redhat.com>

org.jboss.windup.config.operation.Log

It just needs to be extended to take a java.util.logging.Logger as an argument as an alternative to using its own.

E.g. we currently have:


    public static Log message(Level level, String message)
    {
        return new Log(level, message);
    }

We need:

    public static Log message(Logger log, Level level, String message)
    {
        return new Log(log, level, message);
    }

~Lincoln

----- Original Message -----
From: "Ondrej Zizka" <ozizka at redhat.com>
To: "Lincoln Baxter" <lbaxter at redhat.com>
Sent: Tuesday, December 9, 2014 7:59:34 PM
Subject: LogOperation?

Hi Lincoln,

IIUC, you said we have some LogOperation, right?
I can't find it.
Normal logging can only be included in the operation itself, which is 
not always desirable, hence the need for LogOperation. Or not?

Thanks,
Ondra

From ozizka at redhat.com  Thu Dec 11 18:28:37 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Fri, 12 Dec 2014 00:28:37 +0100
Subject: [windup-dev] Script to copy HTML docs to online docs
Message-ID: <548A28A5.60604@redhat.com>

git clone https://github.com/windup/windup-documentation.git
git clone https://github.com/windup/windup.git Vindup
cd Vindup
git checkout gh-pages
mkdir -p docs/2.0.0.Beta6/html
cd ../windup-documentation
cp *.html *.css images/* ../Vindup/docs/2.0.0.Beta6/html
cd -
git add docs
git commit -m "HTML docs"
git push upstream gh-pages
firefox 
http://windup.github.io/windup/docs/2.0.0.Beta6/html/WindupUserGuide.html

HTH,
Ondra

From itewksbu at redhat.com  Sat Dec 13 17:37:09 2014
From: itewksbu at redhat.com (Ian Tewksbury)
Date: Sat, 13 Dec 2014 17:37:09 -0500 (EST)
Subject: [windup-dev] GraphServiceTest Error
Message-ID: <407011866.9573588.1418510229402.JavaMail.zimbra@redhat.com>

All, 

I am trying to build windup from master for the first time in a while but running into this error when trying to run a mvn clean install. Am I missing something or are the tests just broken right now? 



------------------------------------------------------------------------------- 
Test set: org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest 
------------------------------------------------------------------------------- 
Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 17.857 sec <<< FAILURE! - in org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest 
testGraphSearchWithoutCommit(org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest) Time elapsed: 0.042 sec <<< ERROR! 
java.lang.IllegalStateException: Test runner could not locate test class [org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest] in any deployed Addon. 




Blue Skies, 

~Ian 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20141213/dfc3d0bd/attachment-0001.html 

From itewksbu at redhat.com  Sat Dec 13 17:49:57 2014
From: itewksbu at redhat.com (Ian Tewksbury)
Date: Sat, 13 Dec 2014 17:49:57 -0500 (EST)
Subject: [windup-dev] GraphServiceTest Error
In-Reply-To: <407011866.9573588.1418510229402.JavaMail.zimbra@redhat.com>
References: <407011866.9573588.1418510229402.JavaMail.zimbra@redhat.com>
Message-ID: <796358623.9573842.1418510997765.JavaMail.zimbra@redhat.com>

All, 

Never mind, I just had to install the latest version of Forge to clear this error. 

But now I am seeing this: 



------------------------------------------------------------------------------- 
Test set: org.jboss.windup.rules.xml.XMLFileNestedConditionTest 
------------------------------------------------------------------------------- 
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 67.486 sec <<< FAILURE! - in org.jboss.windup.rules.xml.XMLFileNestedConditionTest 
testNestedCondition(org.jboss.windup.rules.xml.XMLFileNestedConditionTest) Time elapsed: 9.724 sec <<< FAILURE! 
java.lang.AssertionError: expected:<1> but was:<0> 
at org.junit.Assert.fail(Assert.java:88) 
at org.junit.Assert.failNotEquals(Assert.java:743) 
at org.junit.Assert.assertEquals(Assert.java:118) 
at org.junit.Assert.assertEquals(Assert.java:555) 
at org.junit.Assert.assertEquals(Assert.java:542) 
at org.jboss.windup.rules.xml.XMLFileNestedConditionTest.testNestedCondition(XMLFileNestedConditionTest.java:128) 

Blue Skies, 
~Ian 

----- Original Message -----

From: "Ian Tewksbury" <itewksbu at redhat.com> 
To: windup-dev at lists.jboss.org 
Sent: Saturday, December 13, 2014 5:37:09 PM 
Subject: [windup-dev] GraphServiceTest Error 

All, 

I am trying to build windup from master for the first time in a while but running into this error when trying to run a mvn clean install. Am I missing something or are the tests just broken right now? 



------------------------------------------------------------------------------- 
Test set: org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest 
------------------------------------------------------------------------------- 
Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 17.857 sec <<< FAILURE! - in org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest 
testGraphSearchWithoutCommit(org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest) Time elapsed: 0.042 sec <<< ERROR! 
java.lang.IllegalStateException: Test runner could not locate test class [org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest] in any deployed Addon. 




Blue Skies, 

~Ian 

_______________________________________________ 
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/20141213/609a2d7e/attachment.html 

From itewksbu at redhat.com  Sat Dec 13 19:45:21 2014
From: itewksbu at redhat.com (Ian Tewksbury)
Date: Sat, 13 Dec 2014 19:45:21 -0500 (EST)
Subject: [windup-dev] org.springframework.context.ApplicationContext cannot
 be found by org.jboss.tools.windup.runtime_3.1.0.qualifier
In-Reply-To: <1243236778.9577889.1418517430269.JavaMail.zimbra@redhat.com>
Message-ID: <1801809267.9577967.1418517921739.JavaMail.zimbra@redhat.com>



Linconln, 




I am trying to get Eclipse to be able to load windup legacy with Forge and have run into the error I think I was running into months ago when I last tried this. The legacy-windup-engine depends on ApplicationContext as a maven dependency but Eclipse/Forage does not seem to be able find the dependency. I have honestly forget how Forge is supposed to work at this point. I thought Forge should automatically be finding all the required dependencies of the jars in the add-on. But maybe I am crazy. Does the addon need to include all the jars that the legacy-windup jars depend on? 




Blue Skies, 

~Ian 




java.lang.NoClassDefFoundError: org/springframework/context/ApplicationContext 
at java.lang.Class.getDeclaredMethods0(Native Method) 
at java.lang.Class.privateGetDeclaredMethods(Class.java:2531) 
at java.lang.Class.getDeclaredMethods(Class.java:1855) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1121) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1098) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.makeSortedMethodList(ProxyFactory.java:803) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.computeSignature(ProxyFactory.java:810) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:398) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$3.call(ClassLoaderAdapterCallback.java:987) 
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:900) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:277) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$200(ClassLoaderAdapterCallback.java:37) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124) 
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) 
at org.jboss.windup.WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.createWindupEngine(WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.java) 
at org.jboss.tools.windup.core.WindupService.getWindupEngine(WindupService.java:391) 
at org.jboss.tools.windup.core.WindupService.getWindupReportEngine(WindupService.java:412) 
at org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:250) 
at org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:186) 
at org.jboss.tools.windup.ui.internal.commands.GenerateWindupReportHandler$1.run(GenerateWindupReportHandler.java:78) 
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) 
Caused by: java.lang.ClassNotFoundException: org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier 
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432) 
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345) 
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337) 
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) 
at java.lang.ClassLoader.loadClass(ClassLoader.java:358) 
... 24 more 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20141213/81b0399f/attachment.html 

From itewksbu at redhat.com  Sat Dec 13 19:58:21 2014
From: itewksbu at redhat.com (Ian Tewksbury)
Date: Sat, 13 Dec 2014 19:58:21 -0500 (EST)
Subject: [windup-dev] org.springframework.context.ApplicationContext
 cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier
In-Reply-To: <1801809267.9577967.1418517921739.JavaMail.zimbra@redhat.com>
References: <1801809267.9577967.1418517921739.JavaMail.zimbra@redhat.com>
Message-ID: <982099471.9578203.1418518701260.JavaMail.zimbra@redhat.com>

Lioncoln, 

I put a breakpoint in CompositeFurnaceClassLoader.loadClass and it is never being called to try and load the ApplicaitonContext so that may explain why it can not be found. But I do not know enough about how this CompositeFurnaceClassLoader is injected into the class loading process to know why it is not even being called to load the ApplicaitonContext class. 

Blue Skies, 
~Ian 

----- Original Message -----

From: "Ian Tewksbury" <itewksbu at redhat.com> 
To: "Lincoln Baxter" <lbaxter at redhat.com> 
Cc: "Windup-dev List" <windup-dev at lists.jboss.org> 
Sent: Saturday, December 13, 2014 7:45:21 PM 
Subject: [windup-dev] org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier 



Linconln, 




I am trying to get Eclipse to be able to load windup legacy with Forge and have run into the error I think I was running into months ago when I last tried this. The legacy-windup-engine depends on ApplicationContext as a maven dependency but Eclipse/Forage does not seem to be able find the dependency. I have honestly forget how Forge is supposed to work at this point. I thought Forge should automatically be finding all the required dependencies of the jars in the add-on. But maybe I am crazy. Does the addon need to include all the jars that the legacy-windup jars depend on? 




Blue Skies, 

~Ian 




java.lang.NoClassDefFoundError: org/springframework/context/ApplicationContext 
at java.lang.Class.getDeclaredMethods0(Native Method) 
at java.lang.Class.privateGetDeclaredMethods(Class.java:2531) 
at java.lang.Class.getDeclaredMethods(Class.java:1855) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1121) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1098) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.makeSortedMethodList(ProxyFactory.java:803) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.computeSignature(ProxyFactory.java:810) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:398) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$3.call(ClassLoaderAdapterCallback.java:987) 
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:900) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:277) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$200(ClassLoaderAdapterCallback.java:37) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124) 
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) 
at org.jboss.windup.WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.createWindupEngine(WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.java) 
at org.jboss.tools.windup.core.WindupService.getWindupEngine(WindupService.java:391) 
at org.jboss.tools.windup.core.WindupService.getWindupReportEngine(WindupService.java:412) 
at org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:250) 
at org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:186) 
at org.jboss.tools.windup.ui.internal.commands.GenerateWindupReportHandler$1.run(GenerateWindupReportHandler.java:78) 
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) 
Caused by: java.lang.ClassNotFoundException: org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier 
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432) 
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345) 
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337) 
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) 
at java.lang.ClassLoader.loadClass(ClassLoader.java:358) 
... 24 more 

_______________________________________________ 
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/20141213/844c9b9b/attachment-0001.html 

From itewksbu at redhat.com  Sun Dec 14 10:39:19 2014
From: itewksbu at redhat.com (Ian Tewksbury)
Date: Sun, 14 Dec 2014 10:39:19 -0500 (EST)
Subject: [windup-dev] org.springframework.context.ApplicationContext
 cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier
In-Reply-To: <982099471.9578203.1418518701260.JavaMail.zimbra@redhat.com>
References: <1801809267.9577967.1418517921739.JavaMail.zimbra@redhat.com>
	<982099471.9578203.1418518701260.JavaMail.zimbra@redhat.com>
Message-ID: <519102780.9607700.1418571559026.JavaMail.zimbra@redhat.com>

I posted a question to the Forge forums with more details and in case there is anyone else out there that may have a clue as to what is going on: 

https://developer.jboss.org/message/913521#913521 

Blue Skies, 
~Ian 

----- Original Message -----

From: "Ian Tewksbury" <itewksbu at redhat.com> 
To: "Lincoln Baxter" <lbaxter at redhat.com> 
Cc: "Windup-dev List" <windup-dev at lists.jboss.org> 
Sent: Saturday, December 13, 2014 7:58:21 PM 
Subject: Re: [windup-dev] org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier 

Lioncoln, 

I put a breakpoint in CompositeFurnaceClassLoader.loadClass and it is never being called to try and load the ApplicaitonContext so that may explain why it can not be found. But I do not know enough about how this CompositeFurnaceClassLoader is injected into the class loading process to know why it is not even being called to load the ApplicaitonContext class. 

Blue Skies, 
~Ian 

----- Original Message -----

From: "Ian Tewksbury" <itewksbu at redhat.com> 
To: "Lincoln Baxter" <lbaxter at redhat.com> 
Cc: "Windup-dev List" <windup-dev at lists.jboss.org> 
Sent: Saturday, December 13, 2014 7:45:21 PM 
Subject: [windup-dev] org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier 



Linconln, 




I am trying to get Eclipse to be able to load windup legacy with Forge and have run into the error I think I was running into months ago when I last tried this. The legacy-windup-engine depends on ApplicationContext as a maven dependency but Eclipse/Forage does not seem to be able find the dependency. I have honestly forget how Forge is supposed to work at this point. I thought Forge should automatically be finding all the required dependencies of the jars in the add-on. But maybe I am crazy. Does the addon need to include all the jars that the legacy-windup jars depend on? 




Blue Skies, 

~Ian 




java.lang.NoClassDefFoundError: org/springframework/context/ApplicationContext 
at java.lang.Class.getDeclaredMethods0(Native Method) 
at java.lang.Class.privateGetDeclaredMethods(Class.java:2531) 
at java.lang.Class.getDeclaredMethods(Class.java:1855) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1121) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1098) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.makeSortedMethodList(ProxyFactory.java:803) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.computeSignature(ProxyFactory.java:810) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:398) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$3.call(ClassLoaderAdapterCallback.java:987) 
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:900) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:277) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$200(ClassLoaderAdapterCallback.java:37) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124) 
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) 
at org.jboss.windup.WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.createWindupEngine(WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.java) 
at org.jboss.tools.windup.core.WindupService.getWindupEngine(WindupService.java:391) 
at org.jboss.tools.windup.core.WindupService.getWindupReportEngine(WindupService.java:412) 
at org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:250) 
at org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:186) 
at org.jboss.tools.windup.ui.internal.commands.GenerateWindupReportHandler$1.run(GenerateWindupReportHandler.java:78) 
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) 
Caused by: java.lang.ClassNotFoundException: org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier 
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432) 
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345) 
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337) 
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) 
at java.lang.ClassLoader.loadClass(ClassLoader.java:358) 
... 24 more 

_______________________________________________ 
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/20141214/a75c111f/attachment.html 

From robb.greathouse at redhat.com  Mon Dec 15 11:35:34 2014
From: robb.greathouse at redhat.com (Robb Greathouse)
Date: Mon, 15 Dec 2014 11:35:34 -0500 (EST)
Subject: [windup-dev] org.springframework.context.ApplicationContext
 cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier
In-Reply-To: <1801809267.9577967.1418517921739.JavaMail.zimbra@redhat.com>
References: <1801809267.9577967.1418517921739.JavaMail.zimbra@redhat.com>
Message-ID: <2008717714.30838435.1418661333998.JavaMail.zimbra@redhat.com>

Hi, 

Quick question. How do you use springframework in eclipse? 

Robb Greathouse 
Chief Evangelist 
Middleware Business Unit 
JBoss, a Division of Red Hat 
cellphone 505-507-4906 

----- Original Message -----

> Linconln,

> I am trying to get Eclipse to be able to load windup legacy with Forge and
> have run into the error I think I was running into months ago when I last
> tried this. The legacy-windup-engine depends on ApplicationContext as a
> maven dependency but Eclipse/Forage does not seem to be able find the
> dependency. I have honestly forget how Forge is supposed to work at this
> point. I thought Forge should automatically be finding all the required
> dependencies of the jars in the add-on. But maybe I am crazy. Does the addon
> need to include all the jars that the legacy-windup jars depend on?

> Blue Skies,

> ~Ian

> java.lang.NoClassDefFoundError:
> org/springframework/context/ApplicationContext
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2531)
> at java.lang.Class.getDeclaredMethods(Class.java:1855)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1121)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1098)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.makeSortedMethodList(ProxyFactory.java:803)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.computeSignature(ProxyFactory.java:810)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:398)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$3.call(ClassLoaderAdapterCallback.java:987)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:900)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:277)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$200(ClassLoaderAdapterCallback.java:37)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
> at
> org.jboss.windup.WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.createWindupEngine(WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.java)
> at
> org.jboss.tools.windup.core.WindupService.getWindupEngine(WindupService.java:391)
> at
> org.jboss.tools.windup.core.WindupService.getWindupReportEngine(WindupService.java:412)
> at
> org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:250)
> at
> org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:186)
> at
> org.jboss.tools.windup.ui.internal.commands.GenerateWindupReportHandler$1.run(GenerateWindupReportHandler.java:78)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.lang.ClassNotFoundException:
> org.springframework.context.ApplicationContext cannot be found by
> org.jboss.tools.windup.runtime_3.1.0.qualifier
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337)
> at
> org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> ... 24 more

> _______________________________________________
> 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/20141215/72572d39/attachment-0001.html 

From itewksbu at redhat.com  Mon Dec 15 11:56:03 2014
From: itewksbu at redhat.com (Ian Tewksbury)
Date: Mon, 15 Dec 2014 11:56:03 -0500 (EST)
Subject: [windup-dev] org.springframework.context.ApplicationContext
 cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier
In-Reply-To: <2008717714.30838435.1418661333998.JavaMail.zimbra@redhat.com>
References: <1801809267.9577967.1418517921739.JavaMail.zimbra@redhat.com>
	<2008717714.30838435.1418661333998.JavaMail.zimbra@redhat.com>
Message-ID: <83087081.9928558.1418662563167.JavaMail.zimbra@redhat.com>

Robb, 

I am not using it. Windup is attempting to use it as it is loading its rules. This issue is not really spring specfic, spring just happens to be the first JAR that is having issues being loaded. The issue is indicitive of a larger problem. Forge/Furnace is not getting queried when trying to load classes that are in JARs provided by the addon. 

Blue Skies, 
~Ian 

----- Original Message -----

From: "Robb Greathouse" <robb.greathouse at redhat.com> 
To: "Windup-dev List" <windup-dev at lists.jboss.org> 
Sent: Monday, December 15, 2014 11:35:34 AM 
Subject: Re: [windup-dev] org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier 

Hi, 

Quick question. How do you use springframework in eclipse? 


Robb Greathouse 
Chief Evangelist 
Middleware Business Unit 
JBoss, a Division of Red Hat 
cellphone 505-507-4906 

----- Original Message -----





Linconln, 




I am trying to get Eclipse to be able to load windup legacy with Forge and have run into the error I think I was running into months ago when I last tried this. The legacy-windup-engine depends on ApplicationContext as a maven dependency but Eclipse/Forage does not seem to be able find the dependency. I have honestly forget how Forge is supposed to work at this point. I thought Forge should automatically be finding all the required dependencies of the jars in the add-on. But maybe I am crazy. Does the addon need to include all the jars that the legacy-windup jars depend on? 




Blue Skies, 

~Ian 




java.lang.NoClassDefFoundError: org/springframework/context/ApplicationContext 
at java.lang.Class.getDeclaredMethods0(Native Method) 
at java.lang.Class.privateGetDeclaredMethods(Class.java:2531) 
at java.lang.Class.getDeclaredMethods(Class.java:1855) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1121) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1098) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.makeSortedMethodList(ProxyFactory.java:803) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.computeSignature(ProxyFactory.java:810) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:398) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$3.call(ClassLoaderAdapterCallback.java:987) 
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:900) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:277) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$200(ClassLoaderAdapterCallback.java:37) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124) 
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) 
at org.jboss.windup.WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.createWindupEngine(WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.java) 
at org.jboss.tools.windup.core.WindupService.getWindupEngine(WindupService.java:391) 
at org.jboss.tools.windup.core.WindupService.getWindupReportEngine(WindupService.java:412) 
at org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:250) 
at org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:186) 
at org.jboss.tools.windup.ui.internal.commands.GenerateWindupReportHandler$1.run(GenerateWindupReportHandler.java:78) 
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) 
Caused by: java.lang.ClassNotFoundException: org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier 
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432) 
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345) 
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337) 
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) 
at java.lang.ClassLoader.loadClass(ClassLoader.java:358) 
... 24 more 

_______________________________________________ 
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/20141215/505fb214/attachment.html 

From robb.greathouse at redhat.com  Mon Dec 15 12:24:03 2014
From: robb.greathouse at redhat.com (Robb Greathouse)
Date: Mon, 15 Dec 2014 12:24:03 -0500 (EST)
Subject: [windup-dev] What's the standard approach for Migrating
 WebLogic Work Managers
In-Reply-To: <B9045872-FA94-493F-A22B-B168380F2E0F@redhat.com>
References: <B9045872-FA94-493F-A22B-B168380F2E0F@redhat.com>
Message-ID: <415440943.30870685.1418664243138.JavaMail.zimbra@redhat.com>

Can you send the code example?  We will create a rule for that in Windup.


Robb Greathouse
Chief Evangelist
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906

----- Original Message -----
> Brad/Robb,
> 
> I know of two approaches :
> * create a custom JCA adapter that implements the CommonJ code
> * use JMS queues
> 
> Which one does consulting recommend when migrating?
> 
> Regards,
> Jeremy Davis
> Senior Solution Architect
> jeremy.davis at redhat.com
> 
> 
> 
> 
> 
> 

From lincolnbaxter at gmail.com  Mon Dec 15 16:15:50 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 15 Dec 2014 16:15:50 -0500
Subject: [windup-dev] GraphServiceTest Error
In-Reply-To: <796358623.9573842.1418510997765.JavaMail.zimbra@redhat.com>
References: <407011866.9573588.1418510229402.JavaMail.zimbra@redhat.com>
	<796358623.9573842.1418510997765.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4EeRDKMM1RVQDd=au0LirRZe5yWXPtnFwbf8176619=3w@mail.gmail.com>

Hey Ian,

The test runner failure to locate test class error is unfortunately a
sporadic one. We have not been able to track it down yet, but it is
something that I plan on fixing in the next few weeks. Until it can be
resolved, I'm sorry to say that you'll just have to  "try the build again".

Working on it, sorry for the inconvenience!
~Lincoln

On Sat, Dec 13, 2014 at 5:49 PM, Ian Tewksbury <itewksbu at redhat.com> wrote:

> All,
>
> Never mind, I just had to install the latest version of Forge to clear
> this error.
>
> But now I am seeing this:
>
>
> -------------------------------------------------------------------------------
> Test set: org.jboss.windup.rules.xml.XMLFileNestedConditionTest
>
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 67.486 sec
> <<< FAILURE! - in org.jboss.windup.rules.xml.XMLFileNestedConditionTest
> testNestedCondition(org.jboss.windup.rules.xml.XMLFileNestedConditionTest)
> Time elapsed: 9.724 sec <<< FAILURE!
> java.lang.AssertionError: expected:<1> but was:<0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at
> org.jboss.windup.rules.xml.XMLFileNestedConditionTest.testNestedCondition(XMLFileNestedConditionTest.java:128)
>
> Blue Skies,
> ~Ian
>
> ------------------------------
> *From: *"Ian Tewksbury" <itewksbu at redhat.com>
> *To: *windup-dev at lists.jboss.org
> *Sent: *Saturday, December 13, 2014 5:37:09 PM
> *Subject: *[windup-dev] GraphServiceTest Error
>
>
> All,
>
> I am trying to build windup from master for the first time in a while but
> running into this error when trying to run a mvn clean install. Am I
> missing something or are the tests just broken right now?
>
>
> -------------------------------------------------------------------------------
> Test set: org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest
>
> -------------------------------------------------------------------------------
> Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 17.857 sec
> <<< FAILURE! - in
> org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest
> testGraphSearchWithoutCommit(org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest)
> Time elapsed: 0.042 sec <<< ERROR!
> java.lang.IllegalStateException: Test runner could not locate test class
> [org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest] in any
> deployed Addon.
>
>
> Blue Skies,
>
> ~Ian
>
> _______________________________________________
> 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/20141215/9189b8aa/attachment.html 

From jsightle at redhat.com  Mon Dec 15 16:22:42 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Mon, 15 Dec 2014 16:22:42 -0500
Subject: [windup-dev] GraphServiceTest Error
In-Reply-To: <CAEp_U4EeRDKMM1RVQDd=au0LirRZe5yWXPtnFwbf8176619=3w@mail.gmail.com>
References: <407011866.9573588.1418510229402.JavaMail.zimbra@redhat.com>	<796358623.9573842.1418510997765.JavaMail.zimbra@redhat.com>
	<CAEp_U4EeRDKMM1RVQDd=au0LirRZe5yWXPtnFwbf8176619=3w@mail.gmail.com>
Message-ID: <548F5122.6060202@redhat.com>

I believe that the "XMLFIleNestedConditionTest" is fixed in the latest 
master.

On 12/15/2014 04:15 PM, Lincoln Baxter, III wrote:
> Hey Ian,
>
> The test runner failure to locate test class error is unfortunately a 
> sporadic one. We have not been able to track it down yet, but it is 
> something that I plan on fixing in the next few weeks. Until it can be 
> resolved, I'm sorry to say that you'll just have to  "try the build 
> again".
>
> Working on it, sorry for the inconvenience!
> ~Lincoln
>
> On Sat, Dec 13, 2014 at 5:49 PM, Ian Tewksbury <itewksbu at redhat.com 
> <mailto:itewksbu at redhat.com>> wrote:
>
>     All,
>
>     Never mind, I just had to install the latest version of Forge to
>     clear this error.
>
>     But now I am seeing this:
>
>     -------------------------------------------------------------------------------
>     Test set: org.jboss.windup.rules.xml.XMLFileNestedConditionTest
>     -------------------------------------------------------------------------------
>     Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>     67.486 sec <<< FAILURE! - in
>     org.jboss.windup.rules.xml.XMLFileNestedConditionTest
>     testNestedCondition(org.jboss.windup.rules.xml.XMLFileNestedConditionTest)
>     Time elapsed: 9.724 sec <<< FAILURE!
>     java.lang.AssertionError: expected:<1> but was:<0>
>     at org.junit.Assert.fail(Assert.java:88)
>     at org.junit.Assert.failNotEquals(Assert.java:743)
>     at org.junit.Assert.assertEquals(Assert.java:118)
>     at org.junit.Assert.assertEquals(Assert.java:555)
>     at org.junit.Assert.assertEquals(Assert.java:542)
>     at
>     org.jboss.windup.rules.xml.XMLFileNestedConditionTest.testNestedCondition(XMLFileNestedConditionTest.java:128)
>
>
>     Blue Skies,
>     ~Ian
>
>     ------------------------------------------------------------------------
>     *From: *"Ian Tewksbury" <itewksbu at redhat.com
>     <mailto:itewksbu at redhat.com>>
>     *To: *windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>     *Sent: *Saturday, December 13, 2014 5:37:09 PM
>     *Subject: *[windup-dev] GraphServiceTest Error
>
>
>     All,
>
>     I am trying to build windup from master for the first time in a
>     while but running into this error when trying to run a mvn clean
>     install. Am I missing something or are the tests just broken right
>     now?
>
>     -------------------------------------------------------------------------------
>     Test set:
>     org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest
>     -------------------------------------------------------------------------------
>     Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed:
>     17.857 sec <<< FAILURE! - in
>     org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest
>     testGraphSearchWithoutCommit(org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest)
>     Time elapsed: 0.042 sec <<< ERROR!
>     java.lang.IllegalStateException: Test runner could not locate test
>     class
>     [org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest]
>     in any deployed Addon.
>
>
>     Blue Skies,
>
>     ~Ian
>
>
>     _______________________________________________
>     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."
>
>
> _______________________________________________
> 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/20141215/33e42073/attachment-0001.html 

From lincolnbaxter at gmail.com  Mon Dec 15 16:22:57 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 15 Dec 2014 16:22:57 -0500
Subject: [windup-dev] org.springframework.context.ApplicationContext
 cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier
In-Reply-To: <83087081.9928558.1418662563167.JavaMail.zimbra@redhat.com>
References: <1801809267.9577967.1418517921739.JavaMail.zimbra@redhat.com>
	<2008717714.30838435.1418661333998.JavaMail.zimbra@redhat.com>
	<83087081.9928558.1418662563167.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4Fp_PiwN7WFpyB-cB9pxy-Djf3TSz9SESxh--i=EUP+hw@mail.gmail.com>

Hey Ian,

Glad to see you! Sorry you're having trouble getting this up and running
again (as you said, not sure we ever did get it there.)

At this point, I would abandon using the Legacy windup codebase. We've long
since stopped working on it. My suggestion, now, would be to update to the
Windup 2.0.0.Beta6 (or SNAPSHOT) version, and start picking things up from
there.

As I recall, we weren't ready at the time of your last attempt, to produce
a report, or information that you could consume in Eclipse, but I do
believe we are at that point now.

To answer some of your questions:

   - The addon needs to contain any required JARs from libraries that are
   included. It won't go out and find things on the fly - everything must be
   bundled.
   - The new entry point for Windup is used here in WindupCommand (you
   should be able to use this as an example):
   https://github.com/windup/windup/blob/master/ui/src/main/java/org/jboss/windup/ui/WindupCommand.java#L249
    -
   - You pretty much just need to ask Furnace for instances of:

   org.jboss.windup.graph.GraphContextFactory;
   org.jboss.windup.exec.WindupProcessor;

The rest "should" be self explanatory via the example.


~Lincoln

On Mon, Dec 15, 2014 at 11:56 AM, Ian Tewksbury <itewksbu at redhat.com> wrote:

> Robb,
>
> I am not using it. Windup is attempting to use it as it is loading its
> rules. This issue is not really spring specfic, spring just happens to be
> the first JAR that is having issues being loaded. The issue is indicitive
> of a larger problem. Forge/Furnace is not getting queried when trying to
> load classes that are in JARs provided by the addon.
>
> Blue Skies,
> ~Ian
>
> ------------------------------
> *From: *"Robb Greathouse" <robb.greathouse at redhat.com>
> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
> *Sent: *Monday, December 15, 2014 11:35:34 AM
> *Subject: *Re: [windup-dev]
> org.springframework.context.ApplicationContext cannot be found by
> org.jboss.tools.windup.runtime_3.1.0.qualifier
>
>
> Hi,
>
> Quick question.  How do you use springframework in eclipse?
>
>
> Robb Greathouse
> Chief Evangelist
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
>
> ------------------------------
>
> Linconln,
>
>
> I am trying to get Eclipse to be able to load windup legacy with Forge and
> have run into the error I think I was running into months ago when I last
> tried this. The legacy-windup-engine depends on ApplicationContext as a
> maven dependency but Eclipse/Forage does not seem to be able find the
> dependency. I have honestly forget how Forge is supposed to work at this
> point. I thought Forge should automatically be finding all the required
> dependencies of the jars in the add-on. But maybe I am crazy. Does the
> addon need to include all the jars that the legacy-windup jars depend on?
>
>
> Blue Skies,
>
> ~Ian
>
>
> java.lang.NoClassDefFoundError:
> org/springframework/context/ApplicationContext
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2531)
> at java.lang.Class.getDeclaredMethods(Class.java:1855)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1121)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1098)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.makeSortedMethodList(ProxyFactory.java:803)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.computeSignature(ProxyFactory.java:810)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:398)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$3.call(ClassLoaderAdapterCallback.java:987)
> at
> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:900)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:277)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$200(ClassLoaderAdapterCallback.java:37)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
> at
> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
> at
> org.jboss.windup.WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.createWindupEngine(WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.java)
> at
> org.jboss.tools.windup.core.WindupService.getWindupEngine(WindupService.java:391)
> at
> org.jboss.tools.windup.core.WindupService.getWindupReportEngine(WindupService.java:412)
> at
> org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:250)
> at
> org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:186)
> at
> org.jboss.tools.windup.ui.internal.commands.GenerateWindupReportHandler$1.run(GenerateWindupReportHandler.java:78)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.lang.ClassNotFoundException:
> org.springframework.context.ApplicationContext cannot be found by
> org.jboss.tools.windup.runtime_3.1.0.qualifier
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337)
> at
> org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> ... 24 more
>
> _______________________________________________
> 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/20141215/e29e328f/attachment.html 

From lincolnbaxter at gmail.com  Mon Dec 15 16:23:50 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 15 Dec 2014 16:23:50 -0500
Subject: [windup-dev] org.springframework.context.ApplicationContext
 cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier
In-Reply-To: <CAEp_U4Fp_PiwN7WFpyB-cB9pxy-Djf3TSz9SESxh--i=EUP+hw@mail.gmail.com>
References: <1801809267.9577967.1418517921739.JavaMail.zimbra@redhat.com>
	<2008717714.30838435.1418661333998.JavaMail.zimbra@redhat.com>
	<83087081.9928558.1418662563167.JavaMail.zimbra@redhat.com>
	<CAEp_U4Fp_PiwN7WFpyB-cB9pxy-Djf3TSz9SESxh--i=EUP+hw@mail.gmail.com>
Message-ID: <CAEp_U4HrXrQQrBOeVVmtF-DjsBdY5-NKXno6Cv4Yq_K-8ERp1A@mail.gmail.com>

But please let me know if things are not clear, or not working, and I will
try to help as much as possible!

~Lincoln

On Mon, Dec 15, 2014 at 4:22 PM, Lincoln Baxter, III <
lincolnbaxter at gmail.com> wrote:

> Hey Ian,
>
> Glad to see you! Sorry you're having trouble getting this up and running
> again (as you said, not sure we ever did get it there.)
>
> At this point, I would abandon using the Legacy windup codebase. We've
> long since stopped working on it. My suggestion, now, would be to update to
> the Windup 2.0.0.Beta6 (or SNAPSHOT) version, and start picking things up
> from there.
>
> As I recall, we weren't ready at the time of your last attempt, to produce
> a report, or information that you could consume in Eclipse, but I do
> believe we are at that point now.
>
> To answer some of your questions:
>
>    - The addon needs to contain any required JARs from libraries that are
>    included. It won't go out and find things on the fly - everything must be
>    bundled.
>    - The new entry point for Windup is used here in WindupCommand (you
>    should be able to use this as an example):
>    https://github.com/windup/windup/blob/master/ui/src/main/java/org/jboss/windup/ui/WindupCommand.java#L249
>     -
>    - You pretty much just need to ask Furnace for instances of:
>
>    org.jboss.windup.graph.GraphContextFactory;
>    org.jboss.windup.exec.WindupProcessor;
>
> The rest "should" be self explanatory via the example.
>
>
> ~Lincoln
>
> On Mon, Dec 15, 2014 at 11:56 AM, Ian Tewksbury <itewksbu at redhat.com>
> wrote:
>
>> Robb,
>>
>> I am not using it. Windup is attempting to use it as it is loading its
>> rules. This issue is not really spring specfic, spring just happens to be
>> the first JAR that is having issues being loaded. The issue is indicitive
>> of a larger problem. Forge/Furnace is not getting queried when trying to
>> load classes that are in JARs provided by the addon.
>>
>> Blue Skies,
>> ~Ian
>>
>> ------------------------------
>> *From: *"Robb Greathouse" <robb.greathouse at redhat.com>
>> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
>> *Sent: *Monday, December 15, 2014 11:35:34 AM
>> *Subject: *Re: [windup-dev]
>> org.springframework.context.ApplicationContext cannot be found by
>> org.jboss.tools.windup.runtime_3.1.0.qualifier
>>
>>
>> Hi,
>>
>> Quick question.  How do you use springframework in eclipse?
>>
>>
>> Robb Greathouse
>> Chief Evangelist
>> Middleware Business Unit
>> JBoss, a Division of Red Hat
>> cellphone 505-507-4906
>>
>> ------------------------------
>>
>> Linconln,
>>
>>
>> I am trying to get Eclipse to be able to load windup legacy with Forge
>> and have run into the error I think I was running into months ago when I
>> last tried this. The legacy-windup-engine depends on ApplicationContext as
>> a maven dependency but Eclipse/Forage does not seem to be able find the
>> dependency. I have honestly forget how Forge is supposed to work at this
>> point. I thought Forge should automatically be finding all the required
>> dependencies of the jars in the add-on. But maybe I am crazy. Does the
>> addon need to include all the jars that the legacy-windup jars depend on?
>>
>>
>> Blue Skies,
>>
>> ~Ian
>>
>>
>> java.lang.NoClassDefFoundError:
>> org/springframework/context/ApplicationContext
>> at java.lang.Class.getDeclaredMethods0(Native Method)
>> at java.lang.Class.privateGetDeclaredMethods(Class.java:2531)
>> at java.lang.Class.getDeclaredMethods(Class.java:1855)
>> at
>> org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30)
>> at
>> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1121)
>> at
>> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1098)
>> at
>> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.makeSortedMethodList(ProxyFactory.java:803)
>> at
>> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.computeSignature(ProxyFactory.java:810)
>> at
>> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:398)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$3.call(ClassLoaderAdapterCallback.java:987)
>> at
>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:900)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:277)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$200(ClassLoaderAdapterCallback.java:37)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
>> at
>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
>> at
>> org.jboss.windup.WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.createWindupEngine(WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.java)
>> at
>> org.jboss.tools.windup.core.WindupService.getWindupEngine(WindupService.java:391)
>> at
>> org.jboss.tools.windup.core.WindupService.getWindupReportEngine(WindupService.java:412)
>> at
>> org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:250)
>> at
>> org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:186)
>> at
>> org.jboss.tools.windup.ui.internal.commands.GenerateWindupReportHandler$1.run(GenerateWindupReportHandler.java:78)
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
>> Caused by: java.lang.ClassNotFoundException:
>> org.springframework.context.ApplicationContext cannot be found by
>> org.jboss.tools.windup.runtime_3.1.0.qualifier
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337)
>> at
>> org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>> ... 24 more
>>
>> _______________________________________________
>> 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."
>



-- 
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/20141215/85b3f5d9/attachment-0001.html 

From lincolnbaxter at gmail.com  Mon Dec 15 16:26:26 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 15 Dec 2014 16:26:26 -0500
Subject: [windup-dev] Script to copy HTML docs to online docs
In-Reply-To: <548A28A5.60604@redhat.com>
References: <548A28A5.60604@redhat.com>
Message-ID: <CAEp_U4HrfArzJUsed61eagzfBn6aVM_D6dUsmNLwwh4dG33CMA@mail.gmail.com>

Hey Ondra,

This is good. Could you please post this on a dev page on the Wiki so that
it doesn't get lost?

Thanks!
~Lincoln

On Thu, Dec 11, 2014 at 6:28 PM, Ondrej Zizka <ozizka at redhat.com> wrote:

> git clone https://github.com/windup/windup-documentation.git
> git clone https://github.com/windup/windup.git Vindup
> cd Vindup
> git checkout gh-pages
> mkdir -p docs/2.0.0.Beta6/html
> cd ../windup-documentation
> cp *.html *.css images/* ../Vindup/docs/2.0.0.Beta6/html
> cd -
> git add docs
> git commit -m "HTML docs"
> git push upstream gh-pages
> firefox
> http://windup.github.io/windup/docs/2.0.0.Beta6/html/WindupUserGuide.html
>
> HTH,
> 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/20141215/cde920c6/attachment.html 

From jeremy.davis at redhat.com  Mon Dec 15 12:32:00 2014
From: jeremy.davis at redhat.com (Jeremy Davis)
Date: Mon, 15 Dec 2014 12:32:00 -0500
Subject: [windup-dev] What's the standard approach for Migrating
	WebLogic Work Managers
In-Reply-To: <415440943.30870685.1418664243138.JavaMail.zimbra@redhat.com>
References: <B9045872-FA94-493F-A22B-B168380F2E0F@redhat.com>
	<415440943.30870685.1418664243138.JavaMail.zimbra@redhat.com>
Message-ID: <AD9B9E3E-3266-446D-A350-31804B75E682@redhat.com>

Robb,

I?ll try to get one

Regards,
Jeremy Davis
Senior Solution Architect
jeremy.davis at redhat.com





On Dec 15, 2014, at 12:24 PM, Robb Greathouse <robb.greathouse at redhat.com> wrote:

> Can you send the code example?  We will create a rule for that in Windup.
> 
> 
> Robb Greathouse
> Chief Evangelist
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
> 
> ----- Original Message -----
>> Brad/Robb,
>> 
>> I know of two approaches :
>> * create a custom JCA adapter that implements the CommonJ code
>> * use JMS queues
>> 
>> Which one does consulting recommend when migrating?
>> 
>> Regards,
>> Jeremy Davis
>> Senior Solution Architect
>> jeremy.davis at redhat.com
>> 
>> 
>> 
>> 
>> 
>> 



From stauil at redhat.com  Wed Dec  3 17:42:14 2014
From: stauil at redhat.com (Samuel Tauil)
Date: Wed, 3 Dec 2014 17:42:14 -0500 (EST)
Subject: [windup-dev] Error when tried to run windup from forge plugin in
	JBDS
In-Reply-To: <49959166.438.1417646092002.JavaMail.samueltauil@redhat-sardinha>
Message-ID: <1017668.453.1417646530461.JavaMail.samueltauil@redhat-sardinha>

Hi, 

I'm getting an error when trying to run windup (installed as coordinate) into forge plugin in JBDS8. 

Steps to reproduce: 
- run forge 
- select -> "Install an Addon" 
- specify the coordinates to windup (you will need to run this command once for each coordinate): 
org.jboss.windup:ui,2.0.0.Beta5 
org.jboss.windup.rules.apps:rules-java,2.0.0.Beta5 
org.jboss.windup.rules.apps:rules-java-ee,2.0.0.Beta5 
- then run Windup via Forge in JBDS 
- select "Windup Migrate App" and use the wizard to completion. 
- filled the fields requested with the same values as I did using command line (which worked fine). 
I tested using the the provided app example: http://download.jboss.org/windup/jee-example-app-1.0.0.ear 

I got the NPE as the image here: https://dl.dropboxusercontent.com/u/7034677/npe-windup.png 


Samuel Tauil 
Senior Solution Architect 
Global Partner Enablement 
http://www.redhat.com/partners/partner-enablement 
http://youtu.be/EdsvGcfIoJs 
Ext. 8426191 
Phone +55 11 3524-6191 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20141203/12c16dac/attachment.html 

From lincolnbaxter at gmail.com  Tue Dec 16 09:31:49 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 16 Dec 2014 09:31:49 -0500
Subject: [windup-dev] Error when tried to run windup from forge plugin
	in JBDS
In-Reply-To: <1017668.453.1417646530461.JavaMail.samueltauil@redhat-sardinha>
References: <49959166.438.1417646092002.JavaMail.samueltauil@redhat-sardinha>
	<1017668.453.1417646530461.JavaMail.samueltauil@redhat-sardinha>
Message-ID: <CAEp_U4H-VeUTZKXf4zsyPb+yvbcuH=40EgjxLO1knjJAceapZQ@mail.gmail.com>

Hey Samuel,

Could you please send the full text stack trace of the NPE?

Thanks!
~Lincoln

On Wed, Dec 3, 2014 at 5:42 PM, Samuel Tauil <stauil at redhat.com> wrote:
>
> Hi,
>
> I'm getting an error when trying to run windup (installed as coordinate)
> into forge plugin in JBDS8.
>
> Steps to reproduce:
> - run forge
> - select -> "Install an Addon"
> - specify the coordinates to windup (you will need to run this command
> once for each coordinate):
>     org.jboss.windup:ui,2.0.0.Beta5
>     org.jboss.windup.rules.apps:rules-java,2.0.0.Beta5
>     org.jboss.windup.rules.apps:rules-java-ee,2.0.0.Beta5
> - then run Windup via Forge in JBDS
>    - select "Windup Migrate App" and use the wizard to completion.
>    - filled the fields requested with the same values as I did using
> command line (which worked fine).
> I tested using the the provided app example:
> http://download.jboss.org/windup/jee-example-app-1.0.0.ear
>
> I got the NPE as the image here:
> https://dl.dropboxusercontent.com/u/7034677/npe-windup.png
>
> Samuel Tauil
> Senior Solution Architect
> Global Partner Enablement
> http://www.redhat.com/partners/partner-enablement
> http://youtu.be/EdsvGcfIoJs
> Ext. 8426191
> Phone +55 11 3524-6191
>
> _______________________________________________
> 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/20141216/1b21d9b3/attachment.html 

From danielsoro at gmail.com  Tue Dec 16 09:32:06 2014
From: danielsoro at gmail.com (Daniel Cunha)
Date: Tue, 16 Dec 2014 14:32:06 +0000
Subject: [windup-dev] Windup 2.0.0.Beta2 Released
In-Reply-To: <91605478-3C85-47DC-B203-DB58CD803824@redhat.com>
References: <CAEp_U4ECrKu5nMJBxfRYgT-Xe1u_sX4txuFcxo0XDVzAqH4Kvw@mail.gmail.com>
	<91605478-3C85-47DC-B203-DB58CD803824@redhat.com>
Message-ID: <CAHLHu47x_g3y+At+Rvydni55ZMWSrLkmKtv_hXMkdiReAtcpAQ@mail.gmail.com>

Nice!

On Sat, Oct 18, 2014 at 1:18 PM, Bruno Georges <bgeorges at redhat.com> wrote:
>
> Congratulations to the entire Migration team.
> I am very pleased with the progress.
>
> Keep up the great work.
>
> Best Regards
>
> Bruno.
>
> Sent from my iPhone
>
> On 17/10/2014, at 11:49 pm, Lincoln Baxter, III <lincolnbaxter at gmail.com>
> wrote:
>
>
> https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=releases&g=org.jboss.windup&a=windup-distribution&v=2.0.0.Beta2&e=zip&c=offline
>
> The whole team did a great job to get the bug-fixes, enhancements, and new
> features into this release!
> Bug
>
>    - [WINDUP-226 <https://issues.jboss.org/browse/WINDUP-226>] -
>    Classification adds multiple fileModels even though they are the same
>    - [WINDUP-323 <https://issues.jboss.org/browse/WINDUP-323>] - More
>    toString() methods are needed as this makes the rules easier to read/debug
>    - [WINDUP-326 <https://issues.jboss.org/browse/WINDUP-326>] - Rule
>    blows up when running against SOA5 example.
>    - [WINDUP-339 <https://issues.jboss.org/browse/WINDUP-339>] -
>    CssJsResourceRenderingRuleProvider does not appear to be copying files
>    correctly on Windows
>    - [WINDUP-348 <https://issues.jboss.org/browse/WINDUP-348>] - Errors
>    running Windup against EJB 2.1 example app
>
> Enhancement
>
>    - [WINDUP-135 <https://issues.jboss.org/browse/WINDUP-135>] - Refactor
>    - Move WindupConfigurationModel#*ScanJavaPackages() etc to Java Basic
>    module.
>    - [WINDUP-152 <https://issues.jboss.org/browse/WINDUP-152>] - Add
>    support for Map<String, String> in Frames to store in vertex'es properties.
>    - [WINDUP-160 <https://issues.jboss.org/browse/WINDUP-160>] - Support
>    implicit phases
>    - [WINDUP-254 <https://issues.jboss.org/browse/WINDUP-254>] - Improve
>    error message in RuleSubset.
>    - [WINDUP-334 <https://issues.jboss.org/browse/WINDUP-334>] -
>    windup.bat should use CRLF as the line separator
>
> Feature Request
>
>    - [WINDUP-167 <https://issues.jboss.org/browse/WINDUP-167>] - Check
>    for duplicate @TypeValues
>    - [WINDUP-183 <https://issues.jboss.org/browse/WINDUP-183>] -
>    XML-based syntax for rules.
>    - [WINDUP-218 <https://issues.jboss.org/browse/WINDUP-218>] - Further
>    simplification of iteration in rules
>
> Task
>
>    - [WINDUP-181 <https://issues.jboss.org/browse/WINDUP-181>] - Separate
>    ApplicationArchiveModel from ApplicationModel
>    - [WINDUP-324 <https://issues.jboss.org/browse/WINDUP-324>] - Demo
>    video with 2.0.0.Beta1 using dist standalone app (no Forge)
>    - [WINDUP-327 <https://issues.jboss.org/browse/WINDUP-327>] - Set up
>    Travis CI - automatic PR testing
>
>
>
> --
> 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
>


-- 
Daniel Cunha (soro)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20141216/dc9d7a63/attachment.html 

From lincolnbaxter at gmail.com  Tue Dec 16 09:34:31 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 16 Dec 2014 09:34:31 -0500
Subject: [windup-dev] Error when tried to run windup from forge plugin
	in JBDS
In-Reply-To: <CAEp_U4H-VeUTZKXf4zsyPb+yvbcuH=40EgjxLO1knjJAceapZQ@mail.gmail.com>
References: <49959166.438.1417646092002.JavaMail.samueltauil@redhat-sardinha>
	<1017668.453.1417646530461.JavaMail.samueltauil@redhat-sardinha>
	<CAEp_U4H-VeUTZKXf4zsyPb+yvbcuH=40EgjxLO1knjJAceapZQ@mail.gmail.com>
Message-ID: <CAEp_U4HiQvyx1ZzXZYCpNqK=m9hxAWqokOfOVsPk8WYdvGagUg@mail.gmail.com>

Hmm. I see the stack trace is empty. Looking in to this.

On Tue, Dec 16, 2014 at 9:31 AM, Lincoln Baxter, III <
lincolnbaxter at gmail.com> wrote:
>
> Hey Samuel,
>
> Could you please send the full text stack trace of the NPE?
>
> Thanks!
> ~Lincoln
>
> On Wed, Dec 3, 2014 at 5:42 PM, Samuel Tauil <stauil at redhat.com> wrote:
>
>> Hi,
>>
>> I'm getting an error when trying to run windup (installed as coordinate)
>> into forge plugin in JBDS8.
>>
>> Steps to reproduce:
>> - run forge
>> - select -> "Install an Addon"
>> - specify the coordinates to windup (you will need to run this command
>> once for each coordinate):
>>     org.jboss.windup:ui,2.0.0.Beta5
>>     org.jboss.windup.rules.apps:rules-java,2.0.0.Beta5
>>     org.jboss.windup.rules.apps:rules-java-ee,2.0.0.Beta5
>> - then run Windup via Forge in JBDS
>>    - select "Windup Migrate App" and use the wizard to completion.
>>    - filled the fields requested with the same values as I did using
>> command line (which worked fine).
>> I tested using the the provided app example:
>> http://download.jboss.org/windup/jee-example-app-1.0.0.ear
>>
>> I got the NPE as the image here:
>> https://dl.dropboxusercontent.com/u/7034677/npe-windup.png
>>
>> Samuel Tauil
>> Senior Solution Architect
>> Global Partner Enablement
>> http://www.redhat.com/partners/partner-enablement
>> http://youtu.be/EdsvGcfIoJs
>> Ext. 8426191
>> Phone +55 11 3524-6191
>>
>> _______________________________________________
>> 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/20141216/ab145126/attachment.html 

From itewksbu at redhat.com  Tue Dec 16 09:49:44 2014
From: itewksbu at redhat.com (Ian Tewksbury)
Date: Tue, 16 Dec 2014 09:49:44 -0500 (EST)
Subject: [windup-dev] org.springframework.context.ApplicationContext
 cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier
In-Reply-To: <CAEp_U4Fp_PiwN7WFpyB-cB9pxy-Djf3TSz9SESxh--i=EUP+hw@mail.gmail.com>
References: <1801809267.9577967.1418517921739.JavaMail.zimbra@redhat.com>
	<2008717714.30838435.1418661333998.JavaMail.zimbra@redhat.com>
	<83087081.9928558.1418662563167.JavaMail.zimbra@redhat.com>
	<CAEp_U4Fp_PiwN7WFpyB-cB9pxy-Djf3TSz9SESxh--i=EUP+hw@mail.gmail.com>
Message-ID: <1266274291.10188923.1418741384028.JavaMail.zimbra@redhat.com>

Lincoln, 

I didn't want to try to bite off more then I can chew at once. Hence I want to make sure I can load windup via forge/furnace before I also try to switch over to using the new windup. If I can load one version with forge then I can load any version. But right now I can't load the version I had working, which means if I tried to switch to loading Windup 2.0 I would be dealing with new API and class loading issues at the same time. 

So first goal, load windup 1 via forge, once I can see I can do that, then I can switch out for windup 2. 

I have a hunch about the class loading issues, but I will put that conversation on the forge forum because it seems the best place. 

Blue Skies, 
~Ian 

----- Original Message -----

From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com> 
To: "Windup-dev List" <windup-dev at lists.jboss.org> 
Sent: Monday, December 15, 2014 4:22:57 PM 
Subject: Re: [windup-dev] org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier 

Hey Ian, 

Glad to see you! Sorry you're having trouble getting this up and running again (as you said, not sure we ever did get it there.) 

At this point, I would abandon using the Legacy windup codebase. We've long since stopped working on it. My suggestion, now, would be to update to the Windup 2.0.0.Beta6 (or SNAPSHOT) version, and start picking things up from there. 

As I recall, we weren't ready at the time of your last attempt, to produce a report, or information that you could consume in Eclipse, but I do believe we are at that point now. 

To answer some of your questions: 


    * The addon needs to contain any required JARs from libraries that are included. It won't go out and find things on the fly - everything must be bundled. 
    * The new entry point for Windup is used here in WindupCommand (you should be able to use this as an example): https://github.com/windup/windup/blob/master/ui/src/main/java/org/jboss/windup/ui/WindupCommand.java#L249 - 
    * You pretty much just need to ask Furnace for instances of: 
	org.jboss.windup.graph.GraphContextFactory ; 
	
	org.jboss.windup.exec.WindupProcessor ; 
The rest "should" be self explanatory via the example. 


~Lincoln 

On Mon, Dec 15, 2014 at 11:56 AM, Ian Tewksbury < itewksbu at redhat.com > wrote: 



Robb, 

I am not using it. Windup is attempting to use it as it is loading its rules. This issue is not really spring specfic, spring just happens to be the first JAR that is having issues being loaded. The issue is indicitive of a larger problem. Forge/Furnace is not getting queried when trying to load classes that are in JARs provided by the addon. 

Blue Skies, 
~Ian 


From: "Robb Greathouse" < robb.greathouse at redhat.com > 
To: "Windup-dev List" < windup-dev at lists.jboss.org > 
Sent: Monday, December 15, 2014 11:35:34 AM 
Subject: Re: [windup-dev] org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier 


Hi, 

Quick question. How do you use springframework in eclipse? 


Robb Greathouse 
Chief Evangelist 
Middleware Business Unit 
JBoss, a Division of Red Hat 
cellphone 505-507-4906 



<blockquote>



Linconln, 




I am trying to get Eclipse to be able to load windup legacy with Forge and have run into the error I think I was running into months ago when I last tried this. The legacy-windup-engine depends on ApplicationContext as a maven dependency but Eclipse/Forage does not seem to be able find the dependency. I have honestly forget how Forge is supposed to work at this point. I thought Forge should automatically be finding all the required dependencies of the jars in the add-on. But maybe I am crazy. Does the addon need to include all the jars that the legacy-windup jars depend on? 




Blue Skies, 

~Ian 




java.lang.NoClassDefFoundError: org/springframework/context/ApplicationContext 
at java.lang.Class.getDeclaredMethods0(Native Method) 
at java.lang.Class.privateGetDeclaredMethods(Class.java:2531) 
at java.lang.Class.getDeclaredMethods(Class.java:1855) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1121) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1098) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.makeSortedMethodList(ProxyFactory.java:803) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.computeSignature(ProxyFactory.java:810) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:398) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$3.call(ClassLoaderAdapterCallback.java:987) 
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:900) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:277) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$200(ClassLoaderAdapterCallback.java:37) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124) 
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) 
at org.jboss.windup.WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.createWindupEngine(WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.java) 
at org.jboss.tools.windup.core.WindupService.getWindupEngine(WindupService.java:391) 
at org.jboss.tools.windup.core.WindupService.getWindupReportEngine(WindupService.java:412) 
at org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:250) 
at org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:186) 
at org.jboss.tools.windup.ui.internal.commands.GenerateWindupReportHandler$1.run(GenerateWindupReportHandler.java:78) 
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) 
Caused by: java.lang.ClassNotFoundException: org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier 
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432) 
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345) 
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337) 
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) 
at java.lang.ClassLoader.loadClass(ClassLoader.java:358) 
... 24 more 

_______________________________________________ 
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 

</blockquote>




-- 
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/20141216/6431ec5d/attachment-0001.html 

From lincolnbaxter at gmail.com  Tue Dec 16 10:38:59 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 16 Dec 2014 10:38:59 -0500
Subject: [windup-dev] Error when tried to run windup from forge plugin
	in JBDS
In-Reply-To: <CAEp_U4HiQvyx1ZzXZYCpNqK=m9hxAWqokOfOVsPk8WYdvGagUg@mail.gmail.com>
References: <49959166.438.1417646092002.JavaMail.samueltauil@redhat-sardinha>
	<1017668.453.1417646530461.JavaMail.samueltauil@redhat-sardinha>
	<CAEp_U4H-VeUTZKXf4zsyPb+yvbcuH=40EgjxLO1knjJAceapZQ@mail.gmail.com>
	<CAEp_U4HiQvyx1ZzXZYCpNqK=m9hxAWqokOfOVsPk8WYdvGagUg@mail.gmail.com>
Message-ID: <CAEp_U4GL29hYkpEJjohji1G0m4aGu5D8Yx2fc7dDngV4AdaxUw@mail.gmail.com>

JIRA - https://issues.jboss.org/browse/WINDUP-432

On Tue, Dec 16, 2014 at 9:34 AM, Lincoln Baxter, III <
lincolnbaxter at gmail.com> wrote:
>
> Hmm. I see the stack trace is empty. Looking in to this.
>
> On Tue, Dec 16, 2014 at 9:31 AM, Lincoln Baxter, III <
> lincolnbaxter at gmail.com> wrote:
>>
>> Hey Samuel,
>>
>> Could you please send the full text stack trace of the NPE?
>>
>> Thanks!
>> ~Lincoln
>>
>> On Wed, Dec 3, 2014 at 5:42 PM, Samuel Tauil <stauil at redhat.com> wrote:
>>
>>> Hi,
>>>
>>> I'm getting an error when trying to run windup (installed as coordinate)
>>> into forge plugin in JBDS8.
>>>
>>> Steps to reproduce:
>>> - run forge
>>> - select -> "Install an Addon"
>>> - specify the coordinates to windup (you will need to run this command
>>> once for each coordinate):
>>>     org.jboss.windup:ui,2.0.0.Beta5
>>>     org.jboss.windup.rules.apps:rules-java,2.0.0.Beta5
>>>     org.jboss.windup.rules.apps:rules-java-ee,2.0.0.Beta5
>>> - then run Windup via Forge in JBDS
>>>    - select "Windup Migrate App" and use the wizard to completion.
>>>    - filled the fields requested with the same values as I did using
>>> command line (which worked fine).
>>> I tested using the the provided app example:
>>> http://download.jboss.org/windup/jee-example-app-1.0.0.ear
>>>
>>> I got the NPE as the image here:
>>> https://dl.dropboxusercontent.com/u/7034677/npe-windup.png
>>>
>>> Samuel Tauil
>>> Senior Solution Architect
>>> Global Partner Enablement
>>> http://www.redhat.com/partners/partner-enablement
>>> http://youtu.be/EdsvGcfIoJs
>>> Ext. 8426191
>>> Phone +55 11 3524-6191
>>>
>>> _______________________________________________
>>> 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."
>


-- 
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/20141216/036d3093/attachment.html 

From lincolnbaxter at gmail.com  Tue Dec 16 13:13:01 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 16 Dec 2014 13:13:01 -0500
Subject: [windup-dev] org.springframework.context.ApplicationContext
 cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier
In-Reply-To: <1266274291.10188923.1418741384028.JavaMail.zimbra@redhat.com>
References: <1801809267.9577967.1418517921739.JavaMail.zimbra@redhat.com>
	<2008717714.30838435.1418661333998.JavaMail.zimbra@redhat.com>
	<83087081.9928558.1418662563167.JavaMail.zimbra@redhat.com>
	<CAEp_U4Fp_PiwN7WFpyB-cB9pxy-Djf3TSz9SESxh--i=EUP+hw@mail.gmail.com>
	<1266274291.10188923.1418741384028.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4GWu6zRp7S0E1+U3UJcE9OjUL5yWeP-G-3hiRiAqzYwWg@mail.gmail.com>

Since windup 2.0 is in no way backwards compatible with Windup 1.0, and the
APIs you'll need probably don't exist in Windup 2.0 yet, I suspect that we
will be solving unnecessary problems (like seemingly Spring related issues
such as this one) by trying to stand up Windup 1 at this point, but that's
fine, we can do this first.

~Lincoln

On Tue, Dec 16, 2014 at 9:49 AM, Ian Tewksbury <itewksbu at redhat.com> wrote:
>
> Lincoln,
>
> I didn't want to try to bite off more then I can chew at once. Hence I
> want to make sure I can load windup via forge/furnace before I also try to
> switch over to using the new windup. If I can load one version with forge
> then I can load any version. But right now I can't load the version I had
> working, which means if I tried to switch to loading Windup 2.0 I would be
> dealing with new API and class loading issues at the same time.
>
> So first goal, load windup 1 via forge, once I can see I can do that, then
> I can switch out for windup 2.
>
> I have a hunch about the class loading issues, but I will put that
> conversation on the forge forum because it seems the best place.
>
> Blue Skies,
> ~Ian
>
> ------------------------------
> *From: *"Lincoln Baxter, III" <lincolnbaxter at gmail.com>
> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
> *Sent: *Monday, December 15, 2014 4:22:57 PM
>
> *Subject: *Re: [windup-dev]
> org.springframework.context.ApplicationContext cannot be found by
> org.jboss.tools.windup.runtime_3.1.0.qualifier
>
> Hey Ian,
>
> Glad to see you! Sorry you're having trouble getting this up and running
> again (as you said, not sure we ever did get it there.)
>
> At this point, I would abandon using the Legacy windup codebase. We've
> long since stopped working on it. My suggestion, now, would be to update to
> the Windup 2.0.0.Beta6 (or SNAPSHOT) version, and start picking things up
> from there.
>
> As I recall, we weren't ready at the time of your last attempt, to produce
> a report, or information that you could consume in Eclipse, but I do
> believe we are at that point now.
>
> To answer some of your questions:
>
>    - The addon needs to contain any required JARs from libraries that are
>    included. It won't go out and find things on the fly - everything must be
>    bundled.
>    - The new entry point for Windup is used here in WindupCommand (you
>    should be able to use this as an example):
>    https://github.com/windup/windup/blob/master/ui/src/main/java/org/jboss/windup/ui/WindupCommand.java#L249
>     -
>    - You pretty much just need to ask Furnace for instances of:
>
>    org.jboss.windup.graph.GraphContextFactory;
>    org.jboss.windup.exec.WindupProcessor;
>
> The rest "should" be self explanatory via the example.
>
>
> ~Lincoln
>
> On Mon, Dec 15, 2014 at 11:56 AM, Ian Tewksbury <itewksbu at redhat.com>
> wrote:
>
>> Robb,
>>
>> I am not using it. Windup is attempting to use it as it is loading its
>> rules. This issue is not really spring specfic, spring just happens to be
>> the first JAR that is having issues being loaded. The issue is indicitive
>> of a larger problem. Forge/Furnace is not getting queried when trying to
>> load classes that are in JARs provided by the addon.
>>
>> Blue Skies,
>> ~Ian
>>
>> ------------------------------
>> *From: *"Robb Greathouse" <robb.greathouse at redhat.com>
>> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
>> *Sent: *Monday, December 15, 2014 11:35:34 AM
>> *Subject: *Re: [windup-dev]
>> org.springframework.context.ApplicationContext cannot be found by
>> org.jboss.tools.windup.runtime_3.1.0.qualifier
>>
>>
>> Hi,
>>
>> Quick question.  How do you use springframework in eclipse?
>>
>>
>> Robb Greathouse
>> Chief Evangelist
>> Middleware Business Unit
>> JBoss, a Division of Red Hat
>> cellphone 505-507-4906
>>
>> ------------------------------
>>
>> Linconln,
>>
>>
>> I am trying to get Eclipse to be able to load windup legacy with Forge
>> and have run into the error I think I was running into months ago when I
>> last tried this. The legacy-windup-engine depends on ApplicationContext as
>> a maven dependency but Eclipse/Forage does not seem to be able find the
>> dependency. I have honestly forget how Forge is supposed to work at this
>> point. I thought Forge should automatically be finding all the required
>> dependencies of the jars in the add-on. But maybe I am crazy. Does the
>> addon need to include all the jars that the legacy-windup jars depend on?
>>
>>
>> Blue Skies,
>>
>> ~Ian
>>
>>
>> java.lang.NoClassDefFoundError:
>> org/springframework/context/ApplicationContext
>> at java.lang.Class.getDeclaredMethods0(Native Method)
>> at java.lang.Class.privateGetDeclaredMethods(Class.java:2531)
>> at java.lang.Class.getDeclaredMethods(Class.java:1855)
>> at
>> org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30)
>> at
>> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1121)
>> at
>> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1098)
>> at
>> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.makeSortedMethodList(ProxyFactory.java:803)
>> at
>> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.computeSignature(ProxyFactory.java:810)
>> at
>> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:398)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$3.call(ClassLoaderAdapterCallback.java:987)
>> at
>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:900)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:277)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$200(ClassLoaderAdapterCallback.java:37)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
>> at
>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
>> at
>> org.jboss.windup.WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.createWindupEngine(WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.java)
>> at
>> org.jboss.tools.windup.core.WindupService.getWindupEngine(WindupService.java:391)
>> at
>> org.jboss.tools.windup.core.WindupService.getWindupReportEngine(WindupService.java:412)
>> at
>> org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:250)
>> at
>> org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:186)
>> at
>> org.jboss.tools.windup.ui.internal.commands.GenerateWindupReportHandler$1.run(GenerateWindupReportHandler.java:78)
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
>> Caused by: java.lang.ClassNotFoundException:
>> org.springframework.context.ApplicationContext cannot be found by
>> org.jboss.tools.windup.runtime_3.1.0.qualifier
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337)
>> at
>> org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>> ... 24 more
>>
>> _______________________________________________
>> 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."
>
> _______________________________________________
> 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/20141216/2587832c/attachment-0001.html 

From itewksbu at redhat.com  Tue Dec 16 15:35:47 2014
From: itewksbu at redhat.com (Ian Tewksbury)
Date: Tue, 16 Dec 2014 15:35:47 -0500 (EST)
Subject: [windup-dev] org.springframework.context.ApplicationContext
 cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier
In-Reply-To: <CAEp_U4GWu6zRp7S0E1+U3UJcE9OjUL5yWeP-G-3hiRiAqzYwWg@mail.gmail.com>
References: <1801809267.9577967.1418517921739.JavaMail.zimbra@redhat.com>
	<2008717714.30838435.1418661333998.JavaMail.zimbra@redhat.com>
	<83087081.9928558.1418662563167.JavaMail.zimbra@redhat.com>
	<CAEp_U4Fp_PiwN7WFpyB-cB9pxy-Djf3TSz9SESxh--i=EUP+hw@mail.gmail.com>
	<1266274291.10188923.1418741384028.JavaMail.zimbra@redhat.com>
	<CAEp_U4GWu6zRp7S0E1+U3UJcE9OjUL5yWeP-G-3hiRiAqzYwWg@mail.gmail.com>
Message-ID: <714147616.10388882.1418762147773.JavaMail.zimbra@redhat.com>

My only worry is I am still not understanding how to correctly leverage forge/furnace to do the class loading properly and trying to do that at the same time as switching APIs could make things even more difficult. In both the new windup I am assuming it has third party jar dependencies, just like windup 1.0 does, so I would run into the same issues. IF you think for some reason the design of 2.0 would be such that I am less likely to be hitting these class loading issues I will just bite the bullet and try and do the switch over at the same time. It would just help my brain a lot if I could get 1.0 working so I have a better baseline of comparison when I then break everything to work with 2.0. I am afraid I wont know whether I am debugging API changes or class loading forge/furnace changes if I am doing both at the same time. 

----- Original Message -----

From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com> 
To: "Windup-dev List" <windup-dev at lists.jboss.org> 
Sent: Tuesday, December 16, 2014 1:13:01 PM 
Subject: Re: [windup-dev] org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier 

Since windup 2.0 is in no way backwards compatible with Windup 1.0, and the APIs you'll need probably don't exist in Windup 2.0 yet, I suspect that we will be solving unnecessary problems (like seemingly Spring related issues such as this one) by trying to stand up Windup 1 at this point, but that's fine, we can do this first. 

~Lincoln 

On Tue, Dec 16, 2014 at 9:49 AM, Ian Tewksbury < itewksbu at redhat.com > wrote: 


Lincoln, 

I didn't want to try to bite off more then I can chew at once. Hence I want to make sure I can load windup via forge/furnace before I also try to switch over to using the new windup. If I can load one version with forge then I can load any version. But right now I can't load the version I had working, which means if I tried to switch to loading Windup 2.0 I would be dealing with new API and class loading issues at the same time. 

So first goal, load windup 1 via forge, once I can see I can do that, then I can switch out for windup 2. 

I have a hunch about the class loading issues, but I will put that conversation on the forge forum because it seems the best place. 

Blue Skies, 
~Ian 


From: "Lincoln Baxter, III" < lincolnbaxter at gmail.com > 
To: "Windup-dev List" < windup-dev at lists.jboss.org > 
Sent: Monday, December 15, 2014 4:22:57 PM 

Subject: Re: [windup-dev] org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier 

Hey Ian, 

Glad to see you! Sorry you're having trouble getting this up and running again (as you said, not sure we ever did get it there.) 

At this point, I would abandon using the Legacy windup codebase. We've long since stopped working on it. My suggestion, now, would be to update to the Windup 2.0.0.Beta6 (or SNAPSHOT) version, and start picking things up from there. 

As I recall, we weren't ready at the time of your last attempt, to produce a report, or information that you could consume in Eclipse, but I do believe we are at that point now. 

To answer some of your questions: 


    * The addon needs to contain any required JARs from libraries that are included. It won't go out and find things on the fly - everything must be bundled. 
    * The new entry point for Windup is used here in WindupCommand (you should be able to use this as an example): https://github.com/windup/windup/blob/master/ui/src/main/java/org/jboss/windup/ui/WindupCommand.java#L249 - 
    * You pretty much just need to ask Furnace for instances of: 
	org.jboss.windup.graph.GraphContextFactory ; 
	
	org.jboss.windup.exec.WindupProcessor ; 
The rest "should" be self explanatory via the example. 


~Lincoln 

On Mon, Dec 15, 2014 at 11:56 AM, Ian Tewksbury < itewksbu at redhat.com > wrote: 

<blockquote>

Robb, 

I am not using it. Windup is attempting to use it as it is loading its rules. This issue is not really spring specfic, spring just happens to be the first JAR that is having issues being loaded. The issue is indicitive of a larger problem. Forge/Furnace is not getting queried when trying to load classes that are in JARs provided by the addon. 

Blue Skies, 
~Ian 


From: "Robb Greathouse" < robb.greathouse at redhat.com > 
To: "Windup-dev List" < windup-dev at lists.jboss.org > 
Sent: Monday, December 15, 2014 11:35:34 AM 
Subject: Re: [windup-dev] org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier 


Hi, 

Quick question. How do you use springframework in eclipse? 


Robb Greathouse 
Chief Evangelist 
Middleware Business Unit 
JBoss, a Division of Red Hat 
cellphone 505-507-4906 



<blockquote>



Linconln, 




I am trying to get Eclipse to be able to load windup legacy with Forge and have run into the error I think I was running into months ago when I last tried this. The legacy-windup-engine depends on ApplicationContext as a maven dependency but Eclipse/Forage does not seem to be able find the dependency. I have honestly forget how Forge is supposed to work at this point. I thought Forge should automatically be finding all the required dependencies of the jars in the add-on. But maybe I am crazy. Does the addon need to include all the jars that the legacy-windup jars depend on? 




Blue Skies, 

~Ian 




java.lang.NoClassDefFoundError: org/springframework/context/ApplicationContext 
at java.lang.Class.getDeclaredMethods0(Native Method) 
at java.lang.Class.privateGetDeclaredMethods(Class.java:2531) 
at java.lang.Class.getDeclaredMethods(Class.java:1855) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1121) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1098) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.makeSortedMethodList(ProxyFactory.java:803) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.computeSignature(ProxyFactory.java:810) 
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:398) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$3.call(ClassLoaderAdapterCallback.java:987) 
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:900) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:277) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$200(ClassLoaderAdapterCallback.java:37) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124) 
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) 
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) 
at org.jboss.windup.WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.createWindupEngine(WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.java) 
at org.jboss.tools.windup.core.WindupService.getWindupEngine(WindupService.java:391) 
at org.jboss.tools.windup.core.WindupService.getWindupReportEngine(WindupService.java:412) 
at org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:250) 
at org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:186) 
at org.jboss.tools.windup.ui.internal.commands.GenerateWindupReportHandler$1.run(GenerateWindupReportHandler.java:78) 
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) 
Caused by: java.lang.ClassNotFoundException: org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier 
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432) 
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345) 
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337) 
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) 
at java.lang.ClassLoader.loadClass(ClassLoader.java:358) 
... 24 more 

_______________________________________________ 
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 

</blockquote>




-- 
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 

</blockquote>



-- 
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/20141216/ced82eb3/attachment.html 

From lincolnbaxter at gmail.com  Tue Dec 16 17:54:41 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 16 Dec 2014 17:54:41 -0500
Subject: [windup-dev] org.springframework.context.ApplicationContext
 cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier
In-Reply-To: <714147616.10388882.1418762147773.JavaMail.zimbra@redhat.com>
References: <1801809267.9577967.1418517921739.JavaMail.zimbra@redhat.com>
	<2008717714.30838435.1418661333998.JavaMail.zimbra@redhat.com>
	<83087081.9928558.1418662563167.JavaMail.zimbra@redhat.com>
	<CAEp_U4Fp_PiwN7WFpyB-cB9pxy-Djf3TSz9SESxh--i=EUP+hw@mail.gmail.com>
	<1266274291.10188923.1418741384028.JavaMail.zimbra@redhat.com>
	<CAEp_U4GWu6zRp7S0E1+U3UJcE9OjUL5yWeP-G-3hiRiAqzYwWg@mail.gmail.com>
	<714147616.10388882.1418762147773.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4E3HgrOBJ1+Z-iDqo6+nnQVUZdAXjcaj074cLUnQDBipA@mail.gmail.com>

For the most part, Furnace is a black box that hands you objects :) No
special ClassLoading knowledge required, really. You can include as much as
you want on the OSGi ClassPath and furnace will give you objects just the
same (as long as you actually have those types on your class-path.) But I
think it's fine if we continue to try to get 1.0 working, I just don't want
to deplete your time and energy on this, because I think your time is very
valuable :)

A few things to know:

   - Furnace is just a runtime & container. It handles object instantiation
   and creates a modular classloading environment that is mostly transparent.
   - Anything you take from inside Furnace and use outside, will be a proxy
   of the actual object. This means that objects and services requested from
   and passed in to Furnace must be proxy-able.
   - Furnace can be started and stopped. Once stopped, you should
   immediately drop all references and clean up any lingering registries where
   .class instances might be held (otherwise you will get classloader memory
   leaks.)

But let's continue with the path we are on. I think that simply adding the
spring jars that contain ApplicationContext.class to the OSGi/eclipse
classpath will resolve this problem.

~Lincoln



On Tue, Dec 16, 2014 at 3:35 PM, Ian Tewksbury <itewksbu at redhat.com> wrote:
>
> My only worry is I am still not understanding how to correctly leverage
> forge/furnace to do the class loading properly and trying to do that at the
> same time as switching APIs could make things even more difficult. In both
> the new windup I am assuming it has third party jar dependencies, just like
> windup 1.0 does, so I would run into the same issues. IF you think for some
> reason the design of 2.0 would be such that I am less likely to be hitting
> these class loading issues I will just bite the bullet and try and do the
> switch over at the same time. It would just help my brain a lot if I could
> get 1.0 working so I have a better baseline of comparison when I then break
> everything to work with 2.0. I am afraid I wont know whether I am debugging
> API changes or class loading forge/furnace changes if I am doing both at
> the same time.
>
> ------------------------------
> *From: *"Lincoln Baxter, III" <lincolnbaxter at gmail.com>
> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
> *Sent: *Tuesday, December 16, 2014 1:13:01 PM
>
> *Subject: *Re: [windup-dev]
> org.springframework.context.ApplicationContext cannot be found by
> org.jboss.tools.windup.runtime_3.1.0.qualifier
>
> Since windup 2.0 is in no way backwards compatible with Windup 1.0, and
> the APIs you'll need probably don't exist in Windup 2.0 yet, I suspect that
> we will be solving unnecessary problems (like seemingly Spring related
> issues such as this one) by trying to stand up Windup 1 at this point, but
> that's fine, we can do this first.
>
> ~Lincoln
>
> On Tue, Dec 16, 2014 at 9:49 AM, Ian Tewksbury <itewksbu at redhat.com>
> wrote:
>>
>> Lincoln,
>>
>> I didn't want to try to bite off more then I can chew at once. Hence I
>> want to make sure I can load windup via forge/furnace before I also try to
>> switch over to using the new windup. If I can load one version with forge
>> then I can load any version. But right now I can't load the version I had
>> working, which means if I tried to switch to loading Windup 2.0 I would be
>> dealing with new API and class loading issues at the same time.
>>
>> So first goal, load windup 1 via forge, once I can see I can do that,
>> then I can switch out for windup 2.
>>
>> I have a hunch about the class loading issues, but I will put that
>> conversation on the forge forum because it seems the best place.
>>
>> Blue Skies,
>> ~Ian
>>
>> ------------------------------
>> *From: *"Lincoln Baxter, III" <lincolnbaxter at gmail.com>
>> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
>> *Sent: *Monday, December 15, 2014 4:22:57 PM
>>
>> *Subject: *Re: [windup-dev]
>> org.springframework.context.ApplicationContext cannot be found by
>> org.jboss.tools.windup.runtime_3.1.0.qualifier
>>
>> Hey Ian,
>>
>> Glad to see you! Sorry you're having trouble getting this up and running
>> again (as you said, not sure we ever did get it there.)
>>
>> At this point, I would abandon using the Legacy windup codebase. We've
>> long since stopped working on it. My suggestion, now, would be to update to
>> the Windup 2.0.0.Beta6 (or SNAPSHOT) version, and start picking things up
>> from there.
>>
>> As I recall, we weren't ready at the time of your last attempt, to
>> produce a report, or information that you could consume in Eclipse, but I
>> do believe we are at that point now.
>>
>> To answer some of your questions:
>>
>>    - The addon needs to contain any required JARs from libraries that
>>    are included. It won't go out and find things on the fly - everything must
>>    be bundled.
>>    - The new entry point for Windup is used here in WindupCommand (you
>>    should be able to use this as an example):
>>    https://github.com/windup/windup/blob/master/ui/src/main/java/org/jboss/windup/ui/WindupCommand.java#L249
>>     -
>>    - You pretty much just need to ask Furnace for instances of:
>>
>>    org.jboss.windup.graph.GraphContextFactory;
>>    org.jboss.windup.exec.WindupProcessor;
>>
>> The rest "should" be self explanatory via the example.
>>
>>
>> ~Lincoln
>>
>> On Mon, Dec 15, 2014 at 11:56 AM, Ian Tewksbury <itewksbu at redhat.com>
>> wrote:
>>
>>> Robb,
>>>
>>> I am not using it. Windup is attempting to use it as it is loading its
>>> rules. This issue is not really spring specfic, spring just happens to be
>>> the first JAR that is having issues being loaded. The issue is indicitive
>>> of a larger problem. Forge/Furnace is not getting queried when trying to
>>> load classes that are in JARs provided by the addon.
>>>
>>> Blue Skies,
>>> ~Ian
>>>
>>> ------------------------------
>>> *From: *"Robb Greathouse" <robb.greathouse at redhat.com>
>>> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
>>> *Sent: *Monday, December 15, 2014 11:35:34 AM
>>> *Subject: *Re: [windup-dev]
>>> org.springframework.context.ApplicationContext cannot be found by
>>> org.jboss.tools.windup.runtime_3.1.0.qualifier
>>>
>>>
>>> Hi,
>>>
>>> Quick question.  How do you use springframework in eclipse?
>>>
>>>
>>> Robb Greathouse
>>> Chief Evangelist
>>> Middleware Business Unit
>>> JBoss, a Division of Red Hat
>>> cellphone 505-507-4906
>>>
>>> ------------------------------
>>>
>>> Linconln,
>>>
>>>
>>> I am trying to get Eclipse to be able to load windup legacy with Forge
>>> and have run into the error I think I was running into months ago when I
>>> last tried this. The legacy-windup-engine depends on ApplicationContext as
>>> a maven dependency but Eclipse/Forage does not seem to be able find the
>>> dependency. I have honestly forget how Forge is supposed to work at this
>>> point. I thought Forge should automatically be finding all the required
>>> dependencies of the jars in the add-on. But maybe I am crazy. Does the
>>> addon need to include all the jars that the legacy-windup jars depend on?
>>>
>>>
>>> Blue Skies,
>>>
>>> ~Ian
>>>
>>>
>>> java.lang.NoClassDefFoundError:
>>> org/springframework/context/ApplicationContext
>>> at java.lang.Class.getDeclaredMethods0(Native Method)
>>> at java.lang.Class.privateGetDeclaredMethods(Class.java:2531)
>>> at java.lang.Class.getDeclaredMethods(Class.java:1855)
>>> at
>>> org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30)
>>> at
>>> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1121)
>>> at
>>> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1098)
>>> at
>>> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.makeSortedMethodList(ProxyFactory.java:803)
>>> at
>>> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.computeSignature(ProxyFactory.java:810)
>>> at
>>> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:398)
>>> at
>>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$3.call(ClassLoaderAdapterCallback.java:987)
>>> at
>>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
>>> at
>>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:900)
>>> at
>>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:277)
>>> at
>>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$200(ClassLoaderAdapterCallback.java:37)
>>> at
>>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
>>> at
>>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
>>> at
>>> org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
>>> at
>>> org.jboss.windup.WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.createWindupEngine(WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.java)
>>> at
>>> org.jboss.tools.windup.core.WindupService.getWindupEngine(WindupService.java:391)
>>> at
>>> org.jboss.tools.windup.core.WindupService.getWindupReportEngine(WindupService.java:412)
>>> at
>>> org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:250)
>>> at
>>> org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:186)
>>> at
>>> org.jboss.tools.windup.ui.internal.commands.GenerateWindupReportHandler$1.run(GenerateWindupReportHandler.java:78)
>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
>>> Caused by: java.lang.ClassNotFoundException:
>>> org.springframework.context.ApplicationContext cannot be found by
>>> org.jboss.tools.windup.runtime_3.1.0.qualifier
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432)
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345)
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337)
>>> at
>>> org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>>> ... 24 more
>>>
>>> _______________________________________________
>>> 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."
>>
>> _______________________________________________
>> 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."
>
> _______________________________________________
> 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/20141216/3505dbcb/attachment-0001.html 

From lincolnbaxter at gmail.com  Wed Dec 17 11:27:26 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 17 Dec 2014 11:27:26 -0500
Subject: [windup-dev] Windup Meeting Minutes - 2014-12-17
Message-ID: <CAEp_U4E1gi1LgpLogwnP54miNpzv+=U6qkAxU2bq1as0Musr1g@mail.gmail.com>

Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-12-17-15.01.html

Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-12-17-15.01.txt

Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-12-17-15.01.log.html

Meeting summary
---------------
* Agenda  (lincolnthree, 15:01:57)

* Status Reports  (lincolnthree, 15:04:39)
  * Finished WINDUP-377 with the help of the team. Rules can now be
    {parameterized}.  (lincolnthree, 15:05:48)
  * Fixed WINDUP-432 - There was a bug in our environment util that
    caused windup to break in eclipse.  (lincolnthree, 15:06:29)
  * I plan on doing some demo-type playing with the xml rules for the
    purpose of brainstorming / continuing to look at rule
    parameterization and improving the way it works and how rules work
    together.  (lincolnthree, 15:07:18)
  * I also plan to start looking at our test runner failures to see if I
    can see what's going on there  (lincolnthree, 15:07:36)
  * XML's are already merged, briefly checked that the report is the
    same and it was, but cannot guarantee  (mbriskar, 15:08:03)
  * I played a little with Handlers here and there  (mbriskar, 15:08:40)
  * I tried to make WINDUP-424 with detailed tests so we have handlers
    covered  (mbriskar, 15:09:15)
  * working now on WINDUP-407  (mbriskar, 15:09:40)
  * WINDUP-420 - Switched to caching compiled xpath's for some
    performance improvement. (maybe 20% on the xml portion of the scan
    at most)  (jsightler, 15:11:17)
  * Fixed a bug that caused --overwrite not to be possible from the
    command line (./windup style invocation)  (jsightler, 15:12:02)
  * Fixed WINDUP-428 that was causing some rules to miss in some cases
    (missing links from some source files to JavaClass)  (jsightler,
    15:13:03)
  * , Also fixed WINDUP-427, WINDUP-426, and WINDUP-425 (internal little
    API improvements)  (jsightler, 15:13:25)
  * I am currently working in providing a generalized way to have an
    iteration use threads. This would be enabled via calling
    Iteration.over().threaded() (optionally specifying the number of
    threads)  (jsightler, 15:14:11)
  * there are some roadblocks around the way titan/blueprints handle
    transactions across thread boundaries that are slowing this down at
    the moment, but I'm hoping I can have something in the next day or
    two  (jsightler, 15:14:55)

* Priorities  (lincolnthree, 15:26:46)
  * #1. Performance and stability  (lincolnthree, 15:27:00)
  * #2 Making rules more usable (adding more conditions)  (lincolnthree,
    15:27:26)
  * #3 Making the rules work together better and make more sense to the
    user  (lincolnthree, 15:27:46)

* Weekly Release  (lincolnthree, 15:54:13)
  * We have a weekly release coming up. Just thought i would mention it
    in the meeting.  (lincolnthree, 15:54:28)
  * This will be the first release that encompasses the new rules params
    feature and should be the best performing release yet.
    (lincolnthree, 15:55:13)

* Test coverage  (lincolnthree, 15:57:27)

* Ideas for how to improve windup (brainstorming)  (lincolnthree,
  16:17:42)


-- 
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/20141217/254a980d/attachment.html 

From jsightle at redhat.com  Mon Dec 22 14:41:48 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Mon, 22 Dec 2014 14:41:48 -0500
Subject: [windup-dev] Windup 2.0.0.Beta7 Released
Message-ID: <549873FC.9080403@redhat.com>

Download:
https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/windup/windup-distribution/2.0.0.Beta7/windup-distribution-2.0.0.Beta7-offline.zip

Issues resolved in this release:

Key 	Summary 	
  WINDUP-377 <https://issues.jboss.org/browse/WINDUP-377> 	Support 
parameterization between elements (conditions/operations) in Rules 
<https://issues.jboss.org/browse/WINDUP-377> 	
WINDUP-417 <https://issues.jboss.org/browse/WINDUP-417> 	

WindupRuleProviderSorter - make the error message clearer, shorten 
<https://issues.jboss.org/browse/WINDUP-417>

	
/Actions/ 
<https://issues.jboss.org/rest/api/1.0/issues/12558848/ActionsAndOperations?atl_token=AQZJ-FV3A-N91S-UDEU%7C141e81a1faf3cffc906de6c0c1bc2cf1bab6d9dc%7Clin>
WINDUP-440 <https://issues.jboss.org/browse/WINDUP-440> 	

Rules request: weblogic.net.http.HttpsURLConnection.loadLocalIdentity() 
should be replaced with 
javax.net.ssl.HttpsURLConnection.getLocalPrinciple() 
<https://issues.jboss.org/browse/WINDUP-440>

	
/Actions/ 
<https://issues.jboss.org/rest/api/1.0/issues/12559980/ActionsAndOperations?atl_token=AQZJ-FV3A-N91S-UDEU%7C141e81a1faf3cffc906de6c0c1bc2cf1bab6d9dc%7Clin>
WINDUP-439 <https://issues.jboss.org/browse/WINDUP-439> 	

org.jboss.windup.rules.java.JavaHintsClassificationsTest.testHintsAndClassificationOperation 
is failing in master <https://issues.jboss.org/browse/WINDUP-439>

	
/Actions/ 
<https://issues.jboss.org/rest/api/1.0/issues/12559941/ActionsAndOperations?atl_token=AQZJ-FV3A-N91S-UDEU%7C141e81a1faf3cffc906de6c0c1bc2cf1bab6d9dc%7Clin>
WINDUP-410 <https://issues.jboss.org/browse/WINDUP-410> 	

Weird wording of after/before vs. phase constraints exceptions 
<https://issues.jboss.org/browse/WINDUP-410>

	
/Actions/ 
<https://issues.jboss.org/rest/api/1.0/issues/12558611/ActionsAndOperations?atl_token=AQZJ-FV3A-N91S-UDEU%7C141e81a1faf3cffc906de6c0c1bc2cf1bab6d9dc%7Clin>
WINDUP-431 <https://issues.jboss.org/browse/WINDUP-431> 	

Log operation to take custom logger 
<https://issues.jboss.org/browse/WINDUP-431>

	
/Actions/ 
<https://issues.jboss.org/rest/api/1.0/issues/12559561/ActionsAndOperations?atl_token=AQZJ-FV3A-N91S-UDEU%7C141e81a1faf3cffc906de6c0c1bc2cf1bab6d9dc%7Clin>
WINDUP-432 <https://issues.jboss.org/browse/WINDUP-432> 	

Windup fails to execute if windup.home system property (and others) are 
not set. <https://issues.jboss.org/browse/WINDUP-432>

	
/Actions/ 
<https://issues.jboss.org/rest/api/1.0/issues/12559698/ActionsAndOperations?atl_token=AQZJ-FV3A-N91S-UDEU%7C141e81a1faf3cffc906de6c0c1bc2cf1bab6d9dc%7Clin>
WINDUP-427 <https://issues.jboss.org/browse/WINDUP-427> 	

Rename WindupConfigurationLoaderImpl to WindupRuleLoaderImpl and add 
list support to RuleProviderWithDependenciesPredicate 
<https://issues.jboss.org/browse/WINDUP-427>

	
/Actions/ 
<https://issues.jboss.org/rest/api/1.0/issues/12559192/ActionsAndOperations?atl_token=AQZJ-FV3A-N91S-UDEU%7C141e81a1faf3cffc906de6c0c1bc2cf1bab6d9dc%7Clin>
WINDUP-420 <https://issues.jboss.org/browse/WINDUP-420> 	

Use compiled XPath expressions and cache lookup failures for more speed 
<https://issues.jboss.org/browse/WINDUP-420>

	
/Actions/ 
<https://issues.jboss.org/rest/api/1.0/issues/12559073/ActionsAndOperations?atl_token=AQZJ-FV3A-N91S-UDEU%7C141e81a1faf3cffc906de6c0c1bc2cf1bab6d9dc%7Clin>
WINDUP-426 <https://issues.jboss.org/browse/WINDUP-426> 	

Rename Query.find to Query.fromType 
<https://issues.jboss.org/browse/WINDUP-426>

	
/Actions/ 
<https://issues.jboss.org/rest/api/1.0/issues/12559191/ActionsAndOperations?atl_token=AQZJ-FV3A-N91S-UDEU%7C141e81a1faf3cffc906de6c0c1bc2cf1bab6d9dc%7Clin>
WINDUP-425 <https://issues.jboss.org/browse/WINDUP-425> 	

Make Variables use <? extends WindupVertexFrame> instead of 
<WindupVertexFrame> <https://issues.jboss.org/browse/WINDUP-425>

	
/Actions/ 
<https://issues.jboss.org/rest/api/1.0/issues/12559190/ActionsAndOperations?atl_token=AQZJ-FV3A-N91S-UDEU%7C141e81a1faf3cffc906de6c0c1bc2cf1bab6d9dc%7Clin>
WINDUP-428 <https://issues.jboss.org/browse/WINDUP-428> 	

Fix ruleprovider ordering issues that are causing missing links to 
JavaClass <https://issues.jboss.org/browse/WINDUP-428>

	
/Actions/ 
<https://issues.jboss.org/rest/api/1.0/issues/12559194/ActionsAndOperations?atl_token=AQZJ-FV3A-N91S-UDEU%7C141e81a1faf3cffc906de6c0c1bc2cf1bab6d9dc%7Clin>
WINDUP-421 <https://issues.jboss.org/browse/WINDUP-421> 	

Windup (native) CLI should support --overwrite when files exist in 
report directory <https://issues.jboss.org/browse/WINDUP-421>

	

<https://issues.jboss.org/rest/api/1.0/issues/12559079/ActionsAndOperations?atl_token=AQZJ-FV3A-N91S-UDEU%7C141e81a1faf3cffc906de6c0c1bc2cf1bab6d9dc%7Clin>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20141222/15d77cb5/attachment-0001.html 

From danielsoro at gmail.com  Tue Dec 23 09:11:42 2014
From: danielsoro at gmail.com (Daniel Cunha)
Date: Tue, 23 Dec 2014 14:11:42 +0000
Subject: [windup-dev] Merry Christmas
Message-ID: <CAHLHu47M8-y4bTsEkdAaTFngKMtNOELn4EX02LsZ+u+HcBLudQ@mail.gmail.com>

Hello Folks,

I just want to wish a Merry Christmas to all.

-- 
Daniel Cunha (soro)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20141223/631dc5b9/attachment.html