From stauil at redhat.com Sun Mar 1 06:39:40 2015
From: stauil at redhat.com (Samuel Tauil)
Date: Sun, 1 Mar 2015 06:39:40 -0500 (EST)
Subject: [windup-dev] Choose between xml, groovy or java based rules
Message-ID: <2131305185.333.1425209976030.JavaMail.samueltauil@redhat-sardinha.local>
Hi,
Why are the advantages and disadvantages of creating a XML or Groovy based rule script as opposed to creating a Java Rule Add-on ?
When would one approach be recommended over another ?
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/20150301/5d5edc5c/attachment.html
From ozizka at redhat.com Mon Mar 2 07:37:03 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 02 Mar 2015 13:37:03 +0100
Subject: [windup-dev] Choose between xml, groovy or java based rules
In-Reply-To: <2131305185.333.1425209976030.JavaMail.samueltauil@redhat-sardinha.local>
References: <2131305185.333.1425209976030.JavaMail.samueltauil@redhat-sardinha.local>
Message-ID: <54F4596F.6090007@redhat.com>
Hi,
I'll try to sum up, someone may add or correct.
Groovy: That was an experiment, currently not finished AFAIK.
XML:
Pros: Should be easy and shorter, no need for recompilation, picked up
automatically from a known paths.
Cons: Only supports a subset of conditions and operations (simplier
ones); does not allow direct custom graph data manipulation.
Java:
Pros: Allows pretty much anything; easier debugging; IDE code completion
for Windup API;
Cons: Needs to be an full Forge addon (if not added to Windup core
codebase); needs more code (some of it boilerplate);
A bit more complex - author needs to know more of Windup
internals.
HTH,
Ondra
On 1.3.2015 12:39, Samuel Tauil wrote:
>
> Hi,
>
>
> Why are the advantages and disadvantages of creating a XML or Groovy
> based rule script as opposed to creating a Java Rule Add-on ?
>
> When would one approach be recommended over another ?
>
>
>
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150302/e01dc593/attachment-0001.html
From sgilda at redhat.com Mon Mar 2 07:57:10 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Mon, 02 Mar 2015 07:57:10 -0500
Subject: [windup-dev] Choose between xml, groovy or java based rules
In-Reply-To: <54F4596F.6090007@redhat.com>
References: <2131305185.333.1425209976030.JavaMail.samueltauil@redhat-sardinha.local>
<54F4596F.6090007@redhat.com>
Message-ID: <54F45E26.8070801@redhat.com>
Ondra, isn't the intent to try to continually improve the XML rules so
they have more and more of the functionality of the Java rules?
On 03/02/2015 07:37 AM, Ondrej Zizka wrote:
> Hi,
>
> I'll try to sum up, someone may add or correct.
>
> Groovy: That was an experiment, currently not finished AFAIK.
>
> XML:
> Pros: Should be easy and shorter, no need for recompilation, picked up
> automatically from a known paths.
> Cons: Only supports a subset of conditions and operations (simplier
> ones); does not allow direct custom graph data manipulation.
>
> Java:
> Pros: Allows pretty much anything; easier debugging; IDE code
> completion for Windup API;
> Cons: Needs to be an full Forge addon (if not added to Windup core
> codebase); needs more code (some of it boilerplate);
> A bit more complex - author needs to know more of Windup
> internals.
>
> HTH,
> Ondra
>
>
>
>
> On 1.3.2015 12:39, Samuel Tauil wrote:
>>
>> Hi,
>>
>>
>> Why are the advantages and disadvantages of creating a XML or Groovy
>> based rule script as opposed to creating a Java Rule Add-on ?
>>
>> When would one approach be recommended over another ?
>>
>>
>>
>> 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
>
>
>
> _______________________________________________
> 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/20150302/ece049c0/attachment.html
From stauil at redhat.com Mon Mar 2 08:38:25 2015
From: stauil at redhat.com (Samuel Tauil)
Date: Mon, 2 Mar 2015 08:38:25 -0500 (EST)
Subject: [windup-dev] Unclassified files
Message-ID: <BB5B0541-BF19-4F12-A9FF-9A61296E1153@redhat.com>
Hi,
I understand the Unclassified Files section in the report as a list of all files which were decompiled properly by Procyon but weren't captured by any rules, so the user can check and see which resources need to be checked again and generate specific rules or not. Is that correct?
Thanks
Samuel
From jsightle at redhat.com Mon Mar 2 09:43:48 2015
From: jsightle at redhat.com (Jess Sightler)
Date: Mon, 02 Mar 2015 09:43:48 -0500
Subject: [windup-dev] Choose between xml, groovy or java based rules
In-Reply-To: <54F45E26.8070801@redhat.com>
References: <2131305185.333.1425209976030.JavaMail.samueltauil@redhat-sardinha.local> <54F4596F.6090007@redhat.com>
<54F45E26.8070801@redhat.com>
Message-ID: <54F47724.50309@redhat.com>
I don't expect that the XML rules will ever be as powerful as the Java
rules. I think that making them that powerful would actually make them
more complicated to use than the Java rules.
Having said that, if there are common cases that are requiring Java, we
would like to know that. We would like as many rules as possible to be
easy to write in the XML format.
On 03/02/2015 07:57 AM, Sande Gilda wrote:
> Ondra, isn't the intent to try to continually improve the XML rules so
> they have more and more of the functionality of the Java rules?
>
> On 03/02/2015 07:37 AM, Ondrej Zizka wrote:
>> Hi,
>>
>> I'll try to sum up, someone may add or correct.
>>
>> Groovy: That was an experiment, currently not finished AFAIK.
>>
>> XML:
>> Pros: Should be easy and shorter, no need for recompilation, picked
>> up automatically from a known paths.
>> Cons: Only supports a subset of conditions and operations (simplier
>> ones); does not allow direct custom graph data manipulation.
>>
>> Java:
>> Pros: Allows pretty much anything; easier debugging; IDE code
>> completion for Windup API;
>> Cons: Needs to be an full Forge addon (if not added to Windup core
>> codebase); needs more code (some of it boilerplate);
>> A bit more complex - author needs to know more of Windup
>> internals.
>>
>> HTH,
>> Ondra
>>
>>
>>
>>
>> On 1.3.2015 12:39, Samuel Tauil wrote:
>>>
>>> Hi,
>>>
>>>
>>> Why are the advantages and disadvantages of creating a XML or Groovy
>>> based rule script as opposed to creating a Java Rule Add-on ?
>>>
>>> When would one approach be recommended over another ?
>>>
>>>
>>>
>>> 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
>>
>>
>>
>> _______________________________________________
>> 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
--
Calendar Free/Busy: https://www.google.com/calendar/embed?src=jsightle%40redhat.com&ctz=America/New_York
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150302/0f94ebc6/attachment.html
From bdavis at redhat.com Mon Mar 2 10:51:14 2015
From: bdavis at redhat.com (Brad Davis)
Date: Mon, 2 Mar 2015 10:51:14 -0500 (EST)
Subject: [windup-dev] Choose between xml, groovy or java based rules
In-Reply-To: <54F47724.50309@redhat.com>
References: <2131305185.333.1425209976030.JavaMail.samueltauil@redhat-sardinha.local>
<54F4596F.6090007@redhat.com> <54F45E26.8070801@redhat.com>
<54F47724.50309@redhat.com>
Message-ID: <831306638.17845415.1425311474492.JavaMail.zimbra@redhat.com>
The XML rules basically provide a short cut for creating rules for Java and XML files.
* If you need to create a new report, you will need to write in Java.
* If you need to extend functionality beyond what the XML rules provide, you will need to write in Java.
* But, if you are trying to just highlight a specific area of a Java code or XML files and provide hints, fall back to leveraging the XML rules.
Thanks! Look forward to seeing your rules Samuel!
Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Jess Sightler" <jsightle at redhat.com>
To: windup-dev at lists.jboss.org
Sent: Monday, March 2, 2015 9:43:48 AM
Subject: Re: [windup-dev] Choose between xml, groovy or java based rules
I don't expect that the XML rules will ever be as powerful as the Java rules. I think that making them that powerful would actually make them more complicated to use than the Java rules.
Having said that, if there are common cases that are requiring Java, we would like to know that. We would like as many rules as possible to be easy to write in the XML format.
On 03/02/2015 07:57 AM, Sande Gilda wrote:
Ondra, isn't the intent to try to continually improve the XML rules so they have more and more of the functionality of the Java rules?
On 03/02/2015 07:37 AM, Ondrej Zizka wrote:
Hi,
I'll try to sum up, someone may add or correct.
Groovy: That was an experiment, currently not finished AFAIK.
XML:
Pros: Should be easy and shorter, no need for recompilation, picked up automatically from a known paths.
Cons: Only supports a subset of conditions and operations (simplier ones); does not allow direct custom graph data manipulation.
Java:
Pros: Allows pretty much anything; easier debugging; IDE code completion for Windup API;
Cons: Needs to be an full Forge addon (if not added to Windup core codebase); needs more code (some of it boilerplate);
A bit more complex - author needs to know more of Windup internals.
HTH,
Ondra
On 1.3.2015 12:39, Samuel Tauil wrote:
Hi,
Why are the advantages and disadvantages of creating a XML or Groovy based rule script as opposed to creating a Java Rule Add-on ?
When would one approach be recommended over another ?
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
_______________________________________________
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
--
Calendar Free/Busy: https://www.google.com/calendar/embed?src=jsightle%40redhat.com&ctz=America/New_York
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
From lincolnbaxter at gmail.com Mon Mar 2 11:02:20 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 2 Mar 2015 11:02:20 -0500
Subject: [windup-dev] Unclassified files
In-Reply-To: <BB5B0541-BF19-4F12-A9FF-9A61296E1153@redhat.com>
References: <BB5B0541-BF19-4F12-A9FF-9A61296E1153@redhat.com>
Message-ID: <CAEp_U4GSZQRHQHHP2Lm7geH2EdxTg=1xwxnwH8ShPUkVsc21Gw@mail.gmail.com>
Unclassified files is a page that shows every single file in the
application that do not have any hints or any categories in them. This is
generally useful for seeing if any files were missed and should have new
rules written (or existing rules fixed). Correct :)
On Mon, Mar 2, 2015 at 8:38 AM, Samuel Tauil <stauil at redhat.com> wrote:
>
> Hi,
>
> I understand the Unclassified Files section in the report as a list of all
> files which were decompiled properly by Procyon but weren't captured by any
> rules, so the user can check and see which resources need to be checked
> again and generate specific rules or not. Is that correct?
>
> Thanks
>
> Samuel
>
>
>
> _______________________________________________
> 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/20150302/4f07faff/attachment.html
From lincolnbaxter at gmail.com Mon Mar 2 11:04:46 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 2 Mar 2015 11:04:46 -0500
Subject: [windup-dev] Choose between xml, groovy or java based rules
In-Reply-To: <831306638.17845415.1425311474492.JavaMail.zimbra@redhat.com>
References: <2131305185.333.1425209976030.JavaMail.samueltauil@redhat-sardinha.local>
<54F4596F.6090007@redhat.com> <54F45E26.8070801@redhat.com>
<54F47724.50309@redhat.com>
<831306638.17845415.1425311474492.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4EXh=zA1RZQ1t8ZkKOvyDch_udUvs4AjgqgJy=YXAy5zQ@mail.gmail.com>
Samuel is writing a hands-on-lab :) even better.
You are all correct! :D Great replies.
On Mon, Mar 2, 2015 at 10:51 AM, Brad Davis <bdavis at redhat.com> wrote:
> The XML rules basically provide a short cut for creating rules for Java
> and XML files.
>
> * If you need to create a new report, you will need to write in Java.
> * If you need to extend functionality beyond what the XML rules provide,
> you will need to write in Java.
> * But, if you are trying to just highlight a specific area of a Java code
> or XML files and provide hints, fall back to leveraging the XML rules.
>
> Thanks! Look forward to seeing your rules Samuel!
>
> Brad Davis
> Senior Manager, Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Jess Sightler" <jsightle at redhat.com>
> To: windup-dev at lists.jboss.org
> Sent: Monday, March 2, 2015 9:43:48 AM
> Subject: Re: [windup-dev] Choose between xml, groovy or java based rules
>
> I don't expect that the XML rules will ever be as powerful as the Java
> rules. I think that making them that powerful would actually make them more
> complicated to use than the Java rules.
>
> Having said that, if there are common cases that are requiring Java, we
> would like to know that. We would like as many rules as possible to be easy
> to write in the XML format.
>
> On 03/02/2015 07:57 AM, Sande Gilda wrote:
>
>
> Ondra, isn't the intent to try to continually improve the XML rules so
> they have more and more of the functionality of the Java rules?
>
> On 03/02/2015 07:37 AM, Ondrej Zizka wrote:
>
>
> Hi,
>
> I'll try to sum up, someone may add or correct.
>
> Groovy: That was an experiment, currently not finished AFAIK.
>
> XML:
> Pros: Should be easy and shorter, no need for recompilation, picked up
> automatically from a known paths.
> Cons: Only supports a subset of conditions and operations (simplier ones);
> does not allow direct custom graph data manipulation.
>
> Java:
> Pros: Allows pretty much anything; easier debugging; IDE code completion
> for Windup API;
> Cons: Needs to be an full Forge addon (if not added to Windup core
> codebase); needs more code (some of it boilerplate);
> A bit more complex - author needs to know more of Windup internals.
>
> HTH,
> Ondra
>
>
>
>
> On 1.3.2015 12:39, Samuel Tauil wrote:
>
>
>
>
>
> Hi,
>
>
>
>
>
> Why are the advantages and disadvantages of creating a XML or Groovy based
> rule script as opposed to creating a Java Rule Add-on ?
>
> When would one approach be recommended over another ?
>
>
> 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
>
>
>
> _______________________________________________
> 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
>
> --
> Calendar Free/Busy:
> https://www.google.com/calendar/embed?src=jsightle%40redhat.com&ctz=America/New_York
>
> _______________________________________________
> 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/20150302/ee11d8fa/attachment-0001.html
From lincolnbaxter at gmail.com Mon Mar 2 13:37:59 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 2 Mar 2015 13:37:59 -0500
Subject: [windup-dev] Windup 2.1.0.Final - EAP 6.x integration
(Windup-as-a-Service)
In-Reply-To: <1199396207.17541845.1425250138317.JavaMail.zimbra@redhat.com>
References: <etPan.54edadd4.2eb141f2.af2@RedBook.fritz.box>
<CAEp_U4GiLWhOS_xtw+YM+_gHQ+DRrD=J6SAXoBETKBzsxYq+vw@mail.gmail.com>
<1199396207.17541845.1425250138317.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4HgQwgbMdz8zygVd2xg-R0MCt=pWac1JWpNRa8A2A-Fkw@mail.gmail.com>
Hey Marc,
(Copying Windup dev so everyone can see what's going on - the are some
valuable examples here.)
First, I didn't see anything borrowed from George's project other than
possibly some config in the POM (which created some duplicate dependencies
and included a LOT of stuff you don't need.) I've gone ahead and updated
the project for you and hosted it within the Windup organization. *You can
find the code here:*
https://github.com/windup/windup-web
*To run the example*, you will need to *first update the path here* to
point to your local project directory (where the project is checked out.)
If the server is not doing exploded deployments, this should be updated to
actually extract the addon-repository from WEB-INF/addon-repository to a
temp directory and point to that temp directory (I'll leave that to you, if
necessary):
https://github.com/windup/windup-web/blob/master/src/main/java/org/jboss/windup/rest/startup/StartupListener.java#L34
*Then run a build:*
mvn clean install
*Now deploy the application and run it *on EAP6.2+ - you can execute Windup
via the REST endpoint (make sure to update the URL to the right local
paths) :
http://192.168.1.6:8080/windup-web/rest/windup?inputPath=....../projects/windup/test-files/jee-example-app-1.0.0.ear&outputPath=....../Desktop/windup-web-report
*The web service endpoint code is here:*
https://github.com/windup/windup-web/blob/master/src/main/java/org/jboss/windup/rest/WindupService.java
I've also updated the server.log so you can see the output from my test
execution on my local machine. Everything ran successfully and the report
was generated :)
I hope this helps,
Lincoln
On Sun, Mar 1, 2015 at 5:48 PM, Marc Zottner <mzottner at redhat.com> wrote:
> Hi Lincoln!
>
> Last Wednesday I spent a couple of hours trying to run Windup 2.1.0.Final
> on EAP 6 without success. I started from scratch using the example of
> Georges that you mentioned. The example itself worked very well. As soon as
> I bound the windup libraries / add-ons, I had several issues.
>
> Here is the latest exception I was not able to fix:
>
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408
> Unsatisfied dependencies for type [AddonRegistry] with qualifiers
> [@Default] at injection point [[parameter 3] of [method] public
> org.jboss.windup.config.furnace.FurnaceHolder.setFurnace(PostStartup,
> Furnace, AddonRegistry)]
> at
> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:315)
> at
> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:284)
> at
> org.jboss.weld.bootstrap.Validator.validateObserverMethods(Validator.java:560)
> at
> org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:376)
> at
> org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:379)
> at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:64)
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980)
> [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913)
> [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> ... 3 more
>
> (cf. https://github.com/Maarc/forge-rest-service/blob/master/server.log)
>
> Do you know what could be the issue here? I checked the project in
> https://github.com/Maarc/forge-rest-service/.
> <https://github.com/Maarc/forge-rest-service/>
>
> best regards and have a great start in your week,
>
> Marc
>
>
>
>
>
>
>
>
>
> ------------------------------
> *Von: *"Lincoln Baxter, III" <lincolnbaxter at gmail.com>
> *An: *"Marc Zottner" <mzottner at redhat.com>
> *Gesendet: *Mittwoch, 25. Februar 2015 17:32:41
> *Betreff: *Re: Fw: Windup 2.1.0.Final - EAP 6.x integration
> (Windup-as-a-Service)
>
>
> Hey Marc,
>
> I'm trying to figure out what exactly you are trying to do here. It looks
> like you are somehow attempting to deploy Windup as a JBoss Module? That
> definitely won't work. (I can explain why if you are really interested, but
> basically Windup runs inside Furnace, and the way you've wired things up,
> you're not running it inside Furnace. https://github.com/forge/furnace)
>
> You need to embed Windup by doing something like this:
>
> https://github.com/windup/windup/blob/master/bootstrap/src/main/java/org/jboss/windup/bootstrap/Bootstrap.java
>
> That means you'll need to install windup into your application via the
> furnace-maven-plugin and probably unzip that folder from the WAR to a
> folder on disk at startup (for offline use):
> https://github.com/windup/windup/blob/master/dist/pom.xml#L28
>
> Alternatively if you want to depend on an internet connection, you can do
> this at runtime:
> https://github.com/forge/furnace#usage
>
> I hope this helps,
> ~Lincoln
>
>
> On Wed, Feb 25, 2015 at 6:11 AM, Marc Zottner <mzottner at redhat.com> wrote:
>
>> Hi Lincoln!
>>
>> I am quite far with the integration of windup 2 and EAP. However I am
>> getting something like that:
>>
>> ______
>>
>> 11:42:04,894 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-13)
>> MSC000001: Failed to start service
>> jboss.deployment.unit."winddrop.ear".WeldStartService:
>> org.jboss.msc.service.StartException in service
>> jboss.deployment.unit."winddrop.ear".WeldStartService: Failed to start
>> service
>> at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1936)
>> [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> [rt.jar:1.7.0_71]
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> [rt.jar:1.7.0_71]
>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
>> Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List
>> with 1 exceptions:
>> Exception 0 :
>> java.lang.IllegalArgumentException: Coordinates must be of the form
>> 'name,version' or 'name,version,api-version
>> at org.jboss.forge.furnace.addons.AddonId.fromCoordinates(AddonId.java:78)
>> at
>> org.jboss.forge.addon.ui.impl.extension.AnnotatedCommandExtension.observeAnnotationMethods(AnnotatedCommandExtension.java:33)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:267)
>> at
>> org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52)
>> at
>> org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137)
>> at
>> org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:263)
>> at
>> org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:164)
>> at
>> org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:51)
>> at
>> org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:154)
>> at
>> org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:245)
>> at
>> org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:233)
>> at
>> org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:213)
>> at
>> org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:117)
>> at
>> org.jboss.weld.event.TransactionalObserverNotifier.notifyObserver(TransactionalObserverNotifier.java:44)
>> at
>> org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:85)
>> at
>> org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:75)
>> at
>> org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:60)
>> at
>> org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:38)
>> at
>> org.jboss.weld.bootstrap.events.ProcessAnnotatedTypeImpl.fire(ProcessAnnotatedTypeImpl.java:41)
>> at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:83)
>> at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:137)
>> at
>> org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:184)
>> at
>> org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:349)
>> at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:63)
>> at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980)
>> at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:745)
>>
>> at
>> org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:40)
>> at
>> org.jboss.weld.bootstrap.events.ProcessAnnotatedTypeImpl.fire(ProcessAnnotatedTypeImpl.java:41)
>> at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:83)
>> at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:137)
>> at
>> org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:184)
>> at
>> org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:349)
>> at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:63)
>> at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980)
>> [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
>> at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913)
>> [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
>> ... 3 more
>> ______
>>
>>
>> Attached you will find my module.xml and I am starting EAP passing the
>> following parameters:
>>
>> /bin/standalone.sh -c standalone-full.xml
>> -Dcom.sun.jersey.server.impl.cdi.lookupExtensionInBeanManager=true
>> -Dforge.standalone=true
>> -Dforge.home=/opt/jboss/jboss-eap-6.3/modules/system/layers/base/org/jboss/windup/2.1.0.Final
>> -Dwindup.home=/opt/jboss/jboss-eap-6.3/modules/system/layers/base/org/jboss/windup/2.1.0.Final
>>
>>
>> Do you have any idea what could be wrong or missing?
>>
>>
>> best regards,
>>
>> Marc
>>
>>
>>
>>
>>
>> On 25 Feb 2015 at 11:59:40, Marc Zottner (mzottner at redhat.com) wrote:
>>
>>
>> Hi everyone,
>>
>> I hope you are doing great. Yesterday I had a look at the latest version
>> of Windup (2.1.0.Final) and I really like it :) It seem way faster than the
>> previous releases I tested.
>>
>>
>> Yesterday I updated the windup-as-a-service fronted (
>> https://github.com/Maarc/windup-as-a-service), made some cleanup and
>> fixed issues with chrome. It is basically an EAP 6 web application running
>> windup 0.7. During the last weeks, I installed this in combination with
>> custom rules for a customer having hundreds of developers. Do not hesitate
>> to have a look at it and give me some feedback.
>>
>>
>> I started to integrated the windup-as-a-service fronted with Windup
>> 2.1.0.Final and would be glad to have your support.
>>
>>
>> *BUILD*
>>
>> In order to be able to build Windup 2.1.0.Final, I had to
>>
>> - add <skipTests>true</skipTests> to the grand-father-pom
>> - import manually ?indexer-core-6.0.WINDUP.jar? in my local
>> repository from the standalone/offline build (
>> https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/windup/windup-distribution/2.1.0.A/
>> )
>> - add the "
>> https://repository.jboss.org/nexus/content/repositories/releases?
>> maven repository to my dependencies
>>
>> It would be great to document it.
>>
>> However my built client in the ?dist? directory has less jars than in the
>> "windup-distribution-2.1.0.A-offline.zip? and I was not able to run it.
>>
>>
>> *INTEGRATION in EAP 6.x*
>>
>> In order to integrate Windup 2.1.0.Final in EAP, I tried to follow the
>> same way that worked for windup 0.7:
>> - define a custom jboss-module containing most of the windup and add ons
>> libraries (expected the weld ones)
>> - control the loaded dependencies with a custom
>> jboss-deployment-structure.xml
>>
>> So far it does not work and I am not sure this approach is really a good
>> idea. Forge has not been designed to be executed in EAP 6 directly. Do you
>> have some hints for doing this?
>>
>>
>> Maybe using a java wrapper and calling the standalone windup installation
>> would be a better idea ...
>>
>>
>> best regards,
>>
>> Marc
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> 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/20150302/cc6a5069/attachment-0001.html
From mzottner at redhat.com Mon Mar 2 16:18:33 2015
From: mzottner at redhat.com (Marc Zottner)
Date: Mon, 2 Mar 2015 22:18:33 +0100
Subject: [windup-dev] Windup 2.1.0.Final - EAP 6.x integration
(Windup-as-a-Service)
In-Reply-To: <CAEp_U4HgQwgbMdz8zygVd2xg-R0MCt=pWac1JWpNRa8A2A-Fkw@mail.gmail.com>
References: <etPan.54edadd4.2eb141f2.af2@RedBook.fritz.box>
<CAEp_U4GiLWhOS_xtw+YM+_gHQ+DRrD=J6SAXoBETKBzsxYq+vw@mail.gmail.com>
<1199396207.17541845.1425250138317.JavaMail.zimbra@redhat.com>
<CAEp_U4HgQwgbMdz8zygVd2xg-R0MCt=pWac1JWpNRa8A2A-Fkw@mail.gmail.com>
Message-ID: <etPan.54f4d3a9.4e6afb66.6885@RedBook.fritz.box>
Fantastic :) I looks really good. Thanks a lot Lincoln!
I will test and integrate this with the other web-fronted later this week.
best regards,
Marc
On 2 Mar 2015 at 19:38:05, Lincoln Baxter, III (lincolnbaxter at gmail.com) wrote:
Hey Marc,
(Copying Windup dev so everyone can see what's going on - the are some valuable examples here.)
First, I didn't see anything borrowed from George's project other than possibly some config in the POM (which created some duplicate dependencies and included a LOT of stuff you don't need.) I've gone ahead and updated the project for you and hosted it within the Windup organization. You can find the code here:
? ? https://github.com/windup/windup-web?
To run the example, you will need to first update the path here to point to your local project directory (where the project is checked out.) If the server is not doing exploded deployments, this should be updated to actually extract the addon-repository from WEB-INF/addon-repository to a temp directory and point to that temp directory (I'll leave that to you, if necessary):
? ? https://github.com/windup/windup-web/blob/master/src/main/java/org/jboss/windup/rest/startup/StartupListener.java#L34
Then run a build:
? ? mvn clean install
Now deploy the application and run it on EAP6.2+ - you can execute Windup via the REST endpoint (make sure to update the URL to the right local paths) :
http://192.168.1.6:8080/windup-web/rest/windup?inputPath=....../projects/windup/test-files/jee-example-app-1.0.0.ear&outputPath=....../Desktop/windup-web-report
The web service endpoint code is here:
https://github.com/windup/windup-web/blob/master/src/main/java/org/jboss/windup/rest/WindupService.java
I've also updated the server.log so you can see the output from my test execution on my local machine. Everything ran successfully and the report was generated :)
I hope this helps,
Lincoln
On Sun, Mar 1, 2015 at 5:48 PM, Marc Zottner <mzottner at redhat.com> wrote:
Hi Lincoln!
Last Wednesday I spent a couple of hours trying to run Windup 2.1.0.Final on EAP 6 without success. I started from scratch using the example of Georges that you mentioned. The example itself worked very well. As soon as I bound the windup libraries / add-ons, I had several issues.
Here is the latest exception I was not able to fix:?
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [AddonRegistry] with qualifiers [@Default] at injection point [[parameter 3] of [method] public org.jboss.windup.config.furnace.FurnaceHolder.setFurnace(PostStartup, Furnace, AddonRegistry)]
?? ?at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:315)
?? ?at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:284)
?? ?at org.jboss.weld.bootstrap.Validator.validateObserverMethods(Validator.java:560)
?? ?at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:376)
?? ?at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:379)
?? ?at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:64)
?? ?at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
?? ?at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
?? ?... 3 more
(cf. https://github.com/Maarc/forge-rest-service/blob/master/server.log)?
Do you know what could be the issue here? I checked the project in https://github.com/Maarc/forge-rest-service/.
best regards and have a great start in your week,
Marc
Von: "Lincoln Baxter, III" <lincolnbaxter at gmail.com>
An: "Marc Zottner" <mzottner at redhat.com>
Gesendet: Mittwoch, 25. Februar 2015 17:32:41
Betreff: Re: Fw: Windup 2.1.0.Final - EAP 6.x integration (Windup-as-a-Service)
Hey Marc,
I'm trying to figure out what exactly you are trying to do here. It looks like you are somehow attempting to deploy Windup as a JBoss Module? That definitely won't work. (I can explain why if you are really interested, but basically Windup runs inside Furnace, and the way you've wired things up, you're not running it inside Furnace. https://github.com/forge/furnace)
You need to embed Windup by doing something like this:
https://github.com/windup/windup/blob/master/bootstrap/src/main/java/org/jboss/windup/bootstrap/Bootstrap.java
That means you'll need to install windup into your application via the furnace-maven-plugin and probably unzip that folder from the WAR to a folder on disk at startup (for offline use):
https://github.com/windup/windup/blob/master/dist/pom.xml#L28
Alternatively if you want to depend on an internet connection, you can do this at runtime:
https://github.com/forge/furnace#usage
I hope this helps,
~Lincoln?
On Wed, Feb 25, 2015 at 6:11 AM, Marc Zottner <mzottner at redhat.com> wrote:
Hi Lincoln!
I am quite far with the integration of windup 2 and EAP. However I am getting something like that:
______
11:42:04,894 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-13) MSC000001: Failed to start service jboss.deployment.unit."winddrop.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."winddrop.ear".WeldStartService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1936) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_71]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
Exception 0 :
java.lang.IllegalArgumentException: Coordinates must be of the form 'name,version' or 'name,version,api-version
at org.jboss.forge.furnace.addons.AddonId.fromCoordinates(AddonId.java:78)
at org.jboss.forge.addon.ui.impl.extension.AnnotatedCommandExtension.observeAnnotationMethods(AnnotatedCommandExtension.java:33)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:267)
at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52)
at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137)
at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:263)
at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:164)
at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:51)
at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:154)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:245)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:233)
at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:213)
at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:117)
at org.jboss.weld.event.TransactionalObserverNotifier.notifyObserver(TransactionalObserverNotifier.java:44)
at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:85)
at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:75)
at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:60)
at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:38)
at org.jboss.weld.bootstrap.events.ProcessAnnotatedTypeImpl.fire(ProcessAnnotatedTypeImpl.java:41)
at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:83)
at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:137)
at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:184)
at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:349)
at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:63)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:40)
at org.jboss.weld.bootstrap.events.ProcessAnnotatedTypeImpl.fire(ProcessAnnotatedTypeImpl.java:41)
at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:83)
at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:137)
at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:184)
at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:349)
at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:63)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
... 3 more
______
Attached you will find my module.xml and I am starting EAP passing the following parameters:
/bin/standalone.sh -c standalone-full.xml -Dcom.sun.jersey.server.impl.cdi.lookupExtensionInBeanManager=true -Dforge.standalone=true -Dforge.home=/opt/jboss/jboss-eap-6.3/modules/system/layers/base/org/jboss/windup/2.1.0.Final -Dwindup.home=/opt/jboss/jboss-eap-6.3/modules/system/layers/base/org/jboss/windup/2.1.0.Final
Do you have any idea what could be wrong or missing?
best regards,
Marc
On 25 Feb 2015 at 11:59:40, Marc Zottner (mzottner at redhat.com) wrote:
Hi everyone,
I hope you are doing great. Yesterday I had a look at the latest version of Windup (2.1.0.Final) and I really like it :) It seem way faster than the previous releases I tested.
Yesterday I updated the windup-as-a-service fronted (https://github.com/Maarc/windup-as-a-service), made some cleanup and fixed issues with chrome. It is basically an EAP 6 web application running windup 0.7. During the last weeks, I installed this in combination with custom rules for a customer having hundreds of developers. Do not hesitate to have a look at it and give me some feedback.
I started to integrated the?windup-as-a-service fronted?with Windup 2.1.0.Final and would be glad to have your support.?
BUILD
In order to be able to build Windup 2.1.0.Final, I had to
add?<skipTests>true</skipTests> to the grand-father-pom
import manually ?indexer-core-6.0.WINDUP.jar? in my local repository from the standalone/offline build (https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/windup/windup-distribution/2.1.0.A/)
add the "https://repository.jboss.org/nexus/content/repositories/releases? maven repository to my dependencies
It would be great to document it.
However my built client in the ?dist? directory has less jars than in the "windup-distribution-2.1.0.A-offline.zip? and I was not able to run it.
INTEGRATION in EAP 6.x
In order to integrate Windup 2.1.0.Final in EAP, I tried to follow the same way that worked for windup 0.7:
- define a custom jboss-module containing most of the windup and add ons libraries (expected the weld ones)
- control the loaded dependencies with a custom jboss-deployment-structure.xml
So far it does not work and I am not sure this approach is really a good idea. Forge has not been designed to be executed in EAP 6 directly. Do you have some hints for doing this?
Maybe using a java wrapper and calling the standalone windup installation would be a better idea ...
best regards,
Marc
?
--
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/20150302/5ef57f85/attachment-0001.html
From ozizka at redhat.com Tue Mar 3 13:54:47 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Tue, 03 Mar 2015 19:54:47 +0100
Subject: [windup-dev] RuleProvider's and Rule's metadata
In-Reply-To: <CAEp_U4GY8rngd6WQm=8SEPgNCJ3Bq+NHKPuCyCsEX4HyDrssQg@mail.gmail.com>
References: <54E5EB43.8060001@redhat.com>
<CAEp_U4GY8rngd6WQm=8SEPgNCJ3Bq+NHKPuCyCsEX4HyDrssQg@mail.gmail.com>
Message-ID: <54F60377.3050408@redhat.com>
After today's meeting dedicated to this topic, we
* Updated
https://docs.google.com/document/d/1F07dzjkAwupZ7-FusBP6OQXDkQzwwKqnqL7gEvw7nrc/edit#
* Created https://issues.jboss.org/browse/WINDUP-520
* Split these tasks:
1.
Implement categories / fix the PR - Ondra
2.
Metadata API - Lincoln
3.
Filtering and selection (UI) - Jess
4. XML handlers to actually define rules metadata in XML - Matej?
The rest inline.
On 19.2.2015 23:12, Lincoln Baxter, III wrote:
> Hey Ondra,
>
> For now, let's continue using Rule objects as Contexts. Once the
> prototype is working and tested, we can look at ways to add a real API
> onto the Rule objects (or possibly add some indirection or abstraction.)
+1, step-by-step, no rushing :) But eventually. ;-)
>
> Keep in mind that you shouldn't be focused too much on the individual
> Rule objects, you probably should be focused on the Rule Providers
> that they are loaded from (since we do most of our filtering on the
> RuleProviders themselves, not on the rules.) I would be a lot more
> willing to change the RuleProvider API to add the getMetadata() method
> that you are looking for than I would be changing the Rule API in Rewrite.
Right, rules themselves won't probably have much specific metadata for
now. They will rather "inherit" from the higher structures.
--
Ondra
>
> ~Lincoln
>
> On Thu, Feb 19, 2015 at 8:55 AM, Ondrej Zizka <ozizka at redhat.com
> <mailto:ozizka at redhat.com>> wrote:
>
> Hi all,
>
> I am working on the categories.
> I think we all agree that this should have a nice API since every rule
> will work with that, directly or indirectly.
> We will get more metadata, and "hiding" them into various places,
> untyped hashmaps of lists of strings, really seems like a bad way
> to do it.
>
> After some work on the subject, I think we should abandon the current
> unfortunate approach of Rules acting like a map through being a
> Rule and
> Context at the same time, needing conditional retyping. And the other
> way of overriding methods like enhanceMetadata() is not fortunate
> either
> as every subclass needs to be aware of what's going on in the
> superclasses.
>
> Instead, we should follow the *conventions*, take the *standard*
> approach, and let Rules have a normal getMetadata(), which would
> return
> an object with all the metadata at one place. This could be subclassed
> to match the needs of individual addons but provide type-safe and
> easy-to-use API for shared metadata.
>
> getPhase(), getExecute*(), getCategories() etc. could
> a) still return what they return, being executed by the loader as now,
> and put to that object, or
> b) let the rule initialize this object in rule's init() (which we
> don't
> have) or a construtor;
> I would drop get*() but we could tunel them to that object for
> backwards compatibility.
>
> I think this goes beyond the scope of Windup and would need a
> rewrite of
> Rewrite (well, not real rewrite, but I liked the pun :).
>
> Other option is to keep scattering metadata in various places, untyped
> hashmaps of lists of strings. Not recommended.
>
> WDYT?
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150303/e63012d6/attachment.html
From lincolnbaxter at gmail.com Tue Mar 3 15:04:22 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 3 Mar 2015 15:04:22 -0500
Subject: [windup-dev] Windup 2.2.0.Final Release Date - 17/Mar/2015
Message-ID: <CAEp_U4Goxu8ZdpK3moNMaZheXURL3mmDfjOYJV04a+GXsPHUZg@mail.gmail.com>
I checked the project calendar and we are on schedule for a 17/Mar/2015
release of 2.2.0.Final
The primary goal of this release (among other things), is enablement of
rule-set storage, categorization, and selection.
More updates tomorrow during the weekly meeting.
--
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/20150303/d1c71b16/attachment.html
From ozizka at redhat.com Tue Mar 3 23:48:46 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 04 Mar 2015 05:48:46 +0100
Subject: [windup-dev] Windup 2.2.0.Final Release Date - 17/Mar/2015
In-Reply-To: <CAEp_U4Goxu8ZdpK3moNMaZheXURL3mmDfjOYJV04a+GXsPHUZg@mail.gmail.com>
References: <CAEp_U4Goxu8ZdpK3moNMaZheXURL3mmDfjOYJV04a+GXsPHUZg@mail.gmail.com>
Message-ID: <54F68EAE.4010302@redhat.com>
I started working on selection. WINDUP-523
Multi-categories PR works (tests passed).
https://github.com/windup/windup/pull/485
WRT metadata API, I suggest it simply copies the structure of the
proposed XML at
https://docs.google.com/document/d/1F07dzjkAwupZ7-FusBP6OQXDkQzwwKqnqL7gEvw7nrc/edit#heading=h.rcjo3iqrs8g8
Note that I don't mean copying in terms of data classes, only the API,
and take the "Javascript prototypal inheritance" approach - bubble up
through Rule, RuleProvider, Ruleset, [user defaults, Windup defaults?]
until a value is found.
One note on possible necessity for a hashmap of random uncontrolled
values of unknown type: If there's such need, how about simply putting
it inside of the metadata - i.e. .getMetadata().getCustomData() or such?
Lastly, are we going to stay with "category" or change the naming to
tags? I would prefer tags - it's more general and I think users will use
this feature to more than just categories.
Ondra
On 3.3.2015 21:04, Lincoln Baxter, III wrote:
> I checked the project calendar and we are on schedule for a
> 17/Mar/2015 release of 2.2.0.Final
>
> The primary goal of this release (among other things), is enablement
> of rule-set storage, categorization, and selection.
>
> More updates tomorrow during the weekly meeting.
>
> --
> 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/20150304/cd695145/attachment.html
From lincolnbaxter at gmail.com Wed Mar 4 00:53:51 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 4 Mar 2015 00:53:51 -0500
Subject: [windup-dev] Windup 2.2.0.Final Release Date - 17/Mar/2015
In-Reply-To: <54F68EAE.4010302@redhat.com>
References: <CAEp_U4Goxu8ZdpK3moNMaZheXURL3mmDfjOYJV04a+GXsPHUZg@mail.gmail.com>
<54F68EAE.4010302@redhat.com>
Message-ID: <CAEp_U4FevYQ0RxYpeMMGKYU6So2MFNgJTL0cvKmSaQ4LnKpsDQ@mail.gmail.com>
I'm fine with calling them tags. I think how this is used will ultimately
determine what they are called. What do the others think?
On Tue, Mar 3, 2015 at 11:48 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
> I started working on selection. WINDUP-523
>
> Multi-categories PR works (tests passed).
> https://github.com/windup/windup/pull/485
>
> WRT metadata API, I suggest it simply copies the structure of the proposed
> XML at
> https://docs.google.com/document/d/1F07dzjkAwupZ7-FusBP6OQXDkQzwwKqnqL7gEvw7nrc/edit#heading=h.rcjo3iqrs8g8
> Note that I don't mean copying in terms of data classes, only the API, and
> take the "Javascript prototypal inheritance" approach - bubble up through
> Rule, RuleProvider, Ruleset, [user defaults, Windup defaults?] until a
> value is found.
>
> One note on possible necessity for a hashmap of random uncontrolled values
> of unknown type: If there's such need, how about simply putting it inside
> of the metadata - i.e. .getMetadata().getCustomData() or such?
>
> Lastly, are we going to stay with "category" or change the naming to tags?
> I would prefer tags - it's more general and I think users will use this
> feature to more than just categories.
>
> Ondra
>
>
>
>
>
> On 3.3.2015 21:04, Lincoln Baxter, III wrote:
>
> I checked the project calendar and we are on schedule for a 17/Mar/2015
> release of 2.2.0.Final
>
> The primary goal of this release (among other things), is enablement of
> rule-set storage, categorization, and selection.
>
> More updates tomorrow during the weekly meeting.
>
> --
> 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/20150304/5a3e450c/attachment-0001.html
From ozizka at redhat.com Wed Mar 4 06:14:57 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 04 Mar 2015 12:14:57 +0100
Subject: [windup-dev] Wiki page <---- Re: Choose between xml,
groovy or java based rules
In-Reply-To: <CAEp_U4EXh=zA1RZQ1t8ZkKOvyDch_udUvs4AjgqgJy=YXAy5zQ@mail.gmail.com>
References: <2131305185.333.1425209976030.JavaMail.samueltauil@redhat-sardinha.local> <54F4596F.6090007@redhat.com>
<54F45E26.8070801@redhat.com> <54F47724.50309@redhat.com> <831306638.17845415.1425311474492.JavaMail.zimbra@redhat.com>
<CAEp_U4EXh=zA1RZQ1t8ZkKOvyDch_udUvs4AjgqgJy=YXAy5zQ@mail.gmail.com>
Message-ID: <54F6E931.5000600@redhat.com>
I think these questions will appear again as it's a bit confusing
subject (Java rules in XML, XML rules in XML, Java rules in Java, ...)
So here's a new wiki page where I compiled what was written here. Feel
free to edit:
https://github.com/windup/windup/wiki/Rules-Difference-Between-XML-based-and-Java-based-Rules
(Sande - I hope it doesn't duplicate some such page - ?)
HTH,
Ondra
On 2.3.2015 17:04, Lincoln Baxter, III wrote:
> Samuel is writing a hands-on-lab :) even better.
>
> You are all correct! :D Great replies.
>
> On Mon, Mar 2, 2015 at 10:51 AM, Brad Davis <bdavis at redhat.com
> <mailto:bdavis at redhat.com>> wrote:
>
> The XML rules basically provide a short cut for creating rules for
> Java and XML files.
>
> * If you need to create a new report, you will need to write in Java.
> * If you need to extend functionality beyond what the XML rules
> provide, you will need to write in Java.
> * But, if you are trying to just highlight a specific area of a
> Java code or XML files and provide hints, fall back to leveraging
> the XML rules.
>
> Thanks! Look forward to seeing your rules Samuel!
>
> Brad Davis
> Senior Manager, Red Hat Consulting
> Email: bdavis at redhat.com <mailto:bdavis at redhat.com> | c:
> 980.226.7865 <tel:980.226.7865> | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Jess Sightler" <jsightle at redhat.com
> <mailto:jsightle at redhat.com>>
> To: windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
> Sent: Monday, March 2, 2015 9:43:48 AM
> Subject: Re: [windup-dev] Choose between xml, groovy or java based
> rules
>
> I don't expect that the XML rules will ever be as powerful as the
> Java rules. I think that making them that powerful would actually
> make them more complicated to use than the Java rules.
>
> Having said that, if there are common cases that are requiring
> Java, we would like to know that. We would like as many rules as
> possible to be easy to write in the XML format.
>
> On 03/02/2015 07:57 AM, Sande Gilda wrote:
>
>
> Ondra, isn't the intent to try to continually improve the XML
> rules so they have more and more of the functionality of the Java
> rules?
>
> On 03/02/2015 07:37 AM, Ondrej Zizka wrote:
>
>
> Hi,
>
> I'll try to sum up, someone may add or correct.
>
> Groovy: That was an experiment, currently not finished AFAIK.
>
> XML:
> Pros: Should be easy and shorter, no need for recompilation,
> picked up automatically from a known paths.
> Cons: Only supports a subset of conditions and operations
> (simplier ones); does not allow direct custom graph data manipulation.
>
> Java:
> Pros: Allows pretty much anything; easier debugging; IDE code
> completion for Windup API;
> Cons: Needs to be an full Forge addon (if not added to Windup core
> codebase); needs more code (some of it boilerplate);
> A bit more complex - author needs to know more of Windup internals.
>
> HTH,
> Ondra
>
>
>
>
> On 1.3.2015 12:39, Samuel Tauil wrote:
>
>
>
>
>
> Hi,
>
>
>
>
>
> Why are the advantages and disadvantages of creating a XML or
> Groovy based rule script as opposed to creating a Java Rule Add-on ?
>
> When would one approach be recommended over another ?
>
>
> 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 <tel:%2B55%2011%203524-6191>
>
>
> _______________________________________________
> windup-dev mailing list windup-dev at lists.jboss.org
> <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list windup-dev at lists.jboss.org
> <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list windup-dev at lists.jboss.org
> <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> --
> Calendar Free/Busy:
> https://www.google.com/calendar/embed?src=jsightle%40redhat.com&ctz=America/New_York
>
> _______________________________________________
> 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/20150304/05252af6/attachment.html
From sgilda at redhat.com Wed Mar 4 08:06:08 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Wed, 04 Mar 2015 08:06:08 -0500
Subject: [windup-dev] Wiki page <---- Re: Choose between xml,
groovy or java based rules
In-Reply-To: <54F6E931.5000600@redhat.com>
References: <2131305185.333.1425209976030.JavaMail.samueltauil@redhat-sardinha.local> <54F4596F.6090007@redhat.com>
<54F45E26.8070801@redhat.com> <54F47724.50309@redhat.com> <831306638.17845415.1425311474492.JavaMail.zimbra@redhat.com>
<CAEp_U4EXh=zA1RZQ1t8ZkKOvyDch_udUvs4AjgqgJy=YXAy5zQ@mail.gmail.com>
<54F6E931.5000600@redhat.com>
Message-ID: <54F70340.9060908@redhat.com>
Great minds Ondra! I was thinking about creating a page like this when I
was lying awake last night. You beat me to it! :-)
Thanks!
On 03/04/2015 06:14 AM, Ondrej Zizka wrote:
> I think these questions will appear again as it's a bit confusing
> subject (Java rules in XML, XML rules in XML, Java rules in Java, ...)
>
> So here's a new wiki page where I compiled what was written here. Feel
> free to edit:
> https://github.com/windup/windup/wiki/Rules-Difference-Between-XML-based-and-Java-based-Rules
>
> (Sande - I hope it doesn't duplicate some such page - ?)
>
> HTH,
> Ondra
>
>
> On 2.3.2015 17:04, Lincoln Baxter, III wrote:
>> Samuel is writing a hands-on-lab :) even better.
>>
>> You are all correct! :D Great replies.
>>
>> On Mon, Mar 2, 2015 at 10:51 AM, Brad Davis <bdavis at redhat.com
>> <mailto:bdavis at redhat.com>> wrote:
>>
>> The XML rules basically provide a short cut for creating rules
>> for Java and XML files.
>>
>> * If you need to create a new report, you will need to write in Java.
>> * If you need to extend functionality beyond what the XML rules
>> provide, you will need to write in Java.
>> * But, if you are trying to just highlight a specific area of a
>> Java code or XML files and provide hints, fall back to leveraging
>> the XML rules.
>>
>> Thanks! Look forward to seeing your rules Samuel!
>>
>> Brad Davis
>> Senior Manager, Red Hat Consulting
>> Email: bdavis at redhat.com <mailto:bdavis at redhat.com> | c:
>> 980.226.7865 <tel:980.226.7865> | http://www.redhat.com
>>
>>
>> ----- Original Message -----
>> From: "Jess Sightler" <jsightle at redhat.com
>> <mailto:jsightle at redhat.com>>
>> To: windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>> Sent: Monday, March 2, 2015 9:43:48 AM
>> Subject: Re: [windup-dev] Choose between xml, groovy or java
>> based rules
>>
>> I don't expect that the XML rules will ever be as powerful as the
>> Java rules. I think that making them that powerful would actually
>> make them more complicated to use than the Java rules.
>>
>> Having said that, if there are common cases that are requiring
>> Java, we would like to know that. We would like as many rules as
>> possible to be easy to write in the XML format.
>>
>> On 03/02/2015 07:57 AM, Sande Gilda wrote:
>>
>>
>> Ondra, isn't the intent to try to continually improve the XML
>> rules so they have more and more of the functionality of the Java
>> rules?
>>
>> On 03/02/2015 07:37 AM, Ondrej Zizka wrote:
>>
>>
>> Hi,
>>
>> I'll try to sum up, someone may add or correct.
>>
>> Groovy: That was an experiment, currently not finished AFAIK.
>>
>> XML:
>> Pros: Should be easy and shorter, no need for recompilation,
>> picked up automatically from a known paths.
>> Cons: Only supports a subset of conditions and operations
>> (simplier ones); does not allow direct custom graph data
>> manipulation.
>>
>> Java:
>> Pros: Allows pretty much anything; easier debugging; IDE code
>> completion for Windup API;
>> Cons: Needs to be an full Forge addon (if not added to Windup
>> core codebase); needs more code (some of it boilerplate);
>> A bit more complex - author needs to know more of Windup internals.
>>
>> HTH,
>> Ondra
>>
>>
>>
>>
>> On 1.3.2015 12:39, Samuel Tauil wrote:
>>
>>
>>
>>
>>
>> Hi,
>>
>>
>>
>>
>>
>> Why are the advantages and disadvantages of creating a XML or
>> Groovy based rule script as opposed to creating a Java Rule Add-on ?
>>
>> When would one approach be recommended over another ?
>>
>>
>> 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 <tel:%2B55%2011%203524-6191>
>>
>>
>> _______________________________________________
>> windup-dev mailing list windup-dev at lists.jboss.org
>> <mailto:windup-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list windup-dev at lists.jboss.org
>> <mailto:windup-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list windup-dev at lists.jboss.org
>> <mailto:windup-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>> --
>> Calendar Free/Busy:
>> https://www.google.com/calendar/embed?src=jsightle%40redhat.com&ctz=America/New_York
>>
>> _______________________________________________
>> 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/20150304/41a49e95/attachment-0001.html
From ozizka at redhat.com Thu Mar 5 02:10:06 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 05 Mar 2015 08:10:06 +0100
Subject: [windup-dev] WindupRuleMetadata
Message-ID: <54F8014E.7020805@redhat.com>
Hi,
1) WindupRuleMetadata should IMO be named RuleProvidersRegistry.
2) WindupRuleMetadata has:
private final List<WindupRuleProvider> providers = new ArrayList<>();
private final IdentityHashMap<WindupRuleProvider, List<Rule>>
providersToRules = new IdentityHashMap<>();
private Configuration configuration;
Isn't the first redundant? It can be acquired simply by
providersToRules.getKeys().
And WRT configuration - that one only has
public List<Rule> getRules();
Is that another redundancy, since rules are in the map? It could be
retrieved as merge of getValues().
Ondra
From jsightle at redhat.com Thu Mar 5 14:39:00 2015
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 05 Mar 2015 14:39:00 -0500
Subject: [windup-dev] WindupRuleMetadata
In-Reply-To: <54F8014E.7020805@redhat.com>
References: <54F8014E.7020805@redhat.com>
Message-ID: <54F8B0D4.7030802@redhat.com>
On 03/05/2015 02:10 AM, Ondrej Zizka wrote:
> Hi,
>
> 1) WindupRuleMetadata should IMO be named RuleProvidersRegistry.
>
> 2) WindupRuleMetadata has:
>
> private final List<WindupRuleProvider> providers = new ArrayList<>();
> private final IdentityHashMap<WindupRuleProvider, List<Rule>>
> providersToRules = new IdentityHashMap<>();
> private Configuration configuration;
>
> Isn't the first redundant? It can be acquired simply by
> providersToRules.getKeys().
>
> And WRT configuration - that one only has
>
> public List<Rule> getRules();
>
> Is that another redundancy, since rules are in the map? It could be
> retrieved as merge of getValues().
The current metadata PR renames it to "LoadedRules". I think that I like
the name RuleProviderRegistry better than that, though.
The reason for multiple stores is the ordering. The Map is not an
ordered map (though it could probably be replaced with one that is). I'm
not really sure what would be gained by getting rid of the Configuration
object itself. That is ultimately what WindupProcessorImpl uses to
execute the rules. I guess that it could call getRules() directly and
create that later, but I'm not sure if that is really an improvement.
From lincolnbaxter at gmail.com Fri Mar 6 10:08:01 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 6 Mar 2015 10:08:01 -0500
Subject: [windup-dev] WindupRuleMetadata
In-Reply-To: <54F8B0D4.7030802@redhat.com>
References: <54F8014E.7020805@redhat.com>
<54F8B0D4.7030802@redhat.com>
Message-ID: <CAEp_U4FY+KQMq9E+gTorVqvHcTUqpGwpJ1Dqs8qRt=3nFS4TrQ@mail.gmail.com>
RuleProviderRegistry seems fine. I'll change it to that.
---
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
On Mar 5, 2015 2:39 PM, "Jess Sightler" <jsightle at redhat.com> wrote:
>
> On 03/05/2015 02:10 AM, Ondrej Zizka wrote:
> > Hi,
> >
> > 1) WindupRuleMetadata should IMO be named RuleProvidersRegistry.
> >
> > 2) WindupRuleMetadata has:
> >
> > private final List<WindupRuleProvider> providers = new
> ArrayList<>();
> > private final IdentityHashMap<WindupRuleProvider, List<Rule>>
> > providersToRules = new IdentityHashMap<>();
> > private Configuration configuration;
> >
> > Isn't the first redundant? It can be acquired simply by
> > providersToRules.getKeys().
> >
> > And WRT configuration - that one only has
> >
> > public List<Rule> getRules();
> >
> > Is that another redundancy, since rules are in the map? It could be
> > retrieved as merge of getValues().
>
>
> The current metadata PR renames it to "LoadedRules". I think that I like
> the name RuleProviderRegistry better than that, though.
>
> The reason for multiple stores is the ordering. The Map is not an
> ordered map (though it could probably be replaced with one that is). I'm
> not really sure what would be gained by getting rid of the Configuration
> object itself. That is ultimately what WindupProcessorImpl uses to
> execute the rules. I guess that it could call getRules() directly and
> create that later, but I'm not sure if that is really an improvement.
> _______________________________________________
> 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/20150306/47321322/attachment.html
From ozizka at redhat.com Mon Mar 9 09:18:49 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 09 Mar 2015 14:18:49 +0100
Subject: [windup-dev] WindupRuleMetadata
In-Reply-To: <54F8B0D4.7030802@redhat.com>
References: <54F8014E.7020805@redhat.com> <54F8B0D4.7030802@redhat.com>
Message-ID: <54FD9DB9.7020400@redhat.com>
My point is that generally, duplicating the collections and relying on
"we don't manipulate it much after creating it" can later lead to
inconsistency and nasty bugs.
YMMV :) If it's better this way for some reason, then be it.
Ondra
On 5.3.2015 20:39, Jess Sightler wrote:
> On 03/05/2015 02:10 AM, Ondrej Zizka wrote:
>> Hi,
>>
>> 1) WindupRuleMetadata should IMO be named RuleProvidersRegistry.
>>
>> 2) WindupRuleMetadata has:
>>
>> private final List<WindupRuleProvider> providers = new ArrayList<>();
>> private final IdentityHashMap<WindupRuleProvider, List<Rule>>
>> providersToRules = new IdentityHashMap<>();
>> private Configuration configuration;
>>
>> Isn't the first redundant? It can be acquired simply by
>> providersToRules.getKeys().
>>
>> And WRT configuration - that one only has
>>
>> public List<Rule> getRules();
>>
>> Is that another redundancy, since rules are in the map? It could be
>> retrieved as merge of getValues().
>
> The current metadata PR renames it to "LoadedRules". I think that I like
> the name RuleProviderRegistry better than that, though.
>
> The reason for multiple stores is the ordering. The Map is not an
> ordered map (though it could probably be replaced with one that is). I'm
> not really sure what would be gained by getting rid of the Configuration
> object itself. That is ultimately what WindupProcessorImpl uses to
> execute the rules. I guess that it could call getRules() directly and
> create that later, but I'm not sure if that is really an improvement.
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From lincolnbaxter at gmail.com Mon Mar 9 12:16:59 2015
From: lincolnbaxter at gmail.com (lincolnbaxter at gmail.com)
Date: Mon, 09 Mar 2015 16:16:59 +0000
Subject: [windup-dev] Updated Invitation: Windup Status Meeting @ Weekly
from 11am to 12pm on Wednesday (Windup Project Calendar)
Message-ID: <089e013d20241f2af60510dd5db2@google.com>
This event has been changed.
Title: Windup Status Meeting
When: Weekly from 11am to 12pm on Wednesday Eastern Time (changed)
Where: #windup on irc.freenode.net
Calendar: Windup Project Calendar
Who:
* Lincoln Baxter, III - creator
* windup-dev at lists.jboss.org
* jsightle at redhat.com
* Ondra ?i?ka
* Robb Greathouse
* pmuir at redhat.com
* Robb Greathouse
* Jesse Sightler
* Brad Davis
* bgeorges at redhat.com
Event details:
https://www.google.com/calendar/event?action=VIEW&eid=dDRoOGZqbHE0ZGljZ2dtcXFpc2RsZzh2ZGcgd2luZHVwLWRldkBsaXN0cy5qYm9zcy5vcmc&tok=NTIjbThxYjFhZTZyYTJtZWZqNmc4Y2c3bHVlOTRAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbWE1YThjYmEyZmVhYTBlNGVhZDQ4YWQwOGM0MTFhYmYzODA5YWMyMDI&ctz=America/New_York&hl=en
Invitation from Google Calendar: https://www.google.com/calendar/
You are receiving this courtesy email at the account
windup-dev at lists.jboss.org because you are an attendee of this event.
To stop receiving future updates for this event, decline this event.
Alternatively you can sign up for a Google account at
https://www.google.com/calendar/ and control your notification settings for
your entire calendar.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150309/262795dc/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 2586 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150309/262795dc/attachment-0002.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: application/ics
Size: 2649 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150309/262795dc/attachment-0003.bin
From lincolnbaxter at gmail.com Mon Mar 9 12:16:59 2015
From: lincolnbaxter at gmail.com (lincolnbaxter at gmail.com)
Date: Mon, 09 Mar 2015 16:16:59 +0000
Subject: [windup-dev] Updated Invitation: Windup Status Meeting @ Weekly
from 10am to 11am on Wednesday from Wed Jun 11,
2014 to Tue May 12 (Windup Project Calendar)
Message-ID: <001a1134999a1e0a410510dd5dca@google.com>
This event has been changed.
Title: Windup Status Meeting
When: Weekly from 10am to 11am on Wednesday from Wed Jun 11, 2014 to Tue
May 12 Eastern Time (changed)
Where: #windup on irc.freenode.net
Calendar: Windup Project Calendar
Who:
* Lincoln Baxter, III - creator
* windup-dev at lists.jboss.org
* jsightle at redhat.com
* Ondra ?i?ka
* Robb Greathouse
* pmuir at redhat.com
* Robb Greathouse
* Jesse Sightler
* Brad Davis
* bgeorges at redhat.com
Event details:
https://www.google.com/calendar/event?action=VIEW&eid=bGQzb2FiYmE3Z2s3dmlmYWYyZmZlNTBhdmcgd2luZHVwLWRldkBsaXN0cy5qYm9zcy5vcmc&tok=NTIjbThxYjFhZTZyYTJtZWZqNmc4Y2c3bHVlOTRAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbTYwZDQxYTA2MDQyYTY2NjZlODQyMDI5MGQwNzVmN2I5MmJiNzFkNTM&ctz=America/New_York&hl=en
Invitation from Google Calendar: https://www.google.com/calendar/
You are receiving this courtesy email at the account
windup-dev at lists.jboss.org because you are an attendee of this event.
To stop receiving future updates for this event, decline this event.
Alternatively you can sign up for a Google account at
https://www.google.com/calendar/ and control your notification settings for
your entire calendar.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150309/30f0582e/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 2609 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150309/30f0582e/attachment.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: application/ics
Size: 2672 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150309/30f0582e/attachment-0001.bin
From lincolnbaxter at gmail.com Mon Mar 9 12:18:58 2015
From: lincolnbaxter at gmail.com (lincolnbaxter at gmail.com)
Date: Mon, 09 Mar 2015 16:18:58 +0000
Subject: [windup-dev] Updated Invitation: Windup Status Meeting @ Weekly
from 11am to 12pm on Wednesday from Wed Jun 11,
2014 to Wed May 6 (Windup Project Calendar)
Message-ID: <047d7ba977aa323b560510dd6437@google.com>
This event has been changed.
Title: Windup Status Meeting
When: Weekly from 11am to 12pm on Wednesday from Wed Jun 11, 2014 to Wed
May 6 Eastern Time (changed)
Where: #windup on irc.freenode.net
Calendar: Windup Project Calendar
Who:
* Lincoln Baxter, III - creator
* windup-dev at lists.jboss.org
* jsightle at redhat.com
* Ondra ?i?ka
* Robb Greathouse
* pmuir at redhat.com
* Robb Greathouse
* Jesse Sightler
* Brad Davis
* bgeorges at redhat.com
Event details:
https://www.google.com/calendar/event?action=VIEW&eid=bGQzb2FiYmE3Z2s3dmlmYWYyZmZlNTBhdmcgd2luZHVwLWRldkBsaXN0cy5qYm9zcy5vcmc&tok=NTIjbThxYjFhZTZyYTJtZWZqNmc4Y2c3bHVlOTRAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbTYwZDQxYTA2MDQyYTY2NjZlODQyMDI5MGQwNzVmN2I5MmJiNzFkNTM&ctz=America/New_York&hl=en
Invitation from Google Calendar: https://www.google.com/calendar/
You are receiving this courtesy email at the account
windup-dev at lists.jboss.org because you are an attendee of this event.
To stop receiving future updates for this event, decline this event.
Alternatively you can sign up for a Google account at
https://www.google.com/calendar/ and control your notification settings for
your entire calendar.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150309/4502edca/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 2609 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150309/4502edca/attachment-0002.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: application/ics
Size: 2672 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150309/4502edca/attachment-0003.bin
From sgilda at redhat.com Tue Mar 10 08:43:10 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 10 Mar 2015 08:43:10 -0400
Subject: [windup-dev] JBoss Migration Community of Practice
In-Reply-To: <54FECDEA.2010108@redhat.com>
References: <54FECDEA.2010108@redhat.com>
Message-ID: <54FEE6DE.7050308@redhat.com>
Thanks Sam! We have worked with many of the people listed on this site,
but I wasn't aware of this page.
I am copying the JBoss migration /Windup team. This may be useful not
only for the docs, but for the Windup rules.
Thanks again,
Sande
On 03/10/2015 06:56 AM, Sam Knuth (Folk-Williams) wrote:
> Hi Sande, Jimmy - I am talking to Red Hat Consulting a bit about ways
> to collaborate on content from all the work that they do hands on with
> customers. I found out they have a community of practice around
> capturing/sharing knowledge for JBoss Migration:
> https://mojo.redhat.com/groups/jboss-migration-community-of-practice
>
> Are you guys aware of this?
>
> Sande - this could be a great resource for content!
>
> -Sam
>
From lincolnbaxter at gmail.com Tue Mar 10 16:57:29 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 10 Mar 2015 16:57:29 -0400
Subject: [windup-dev] You can start the remaining Metadata tasks now :)
Message-ID: <CAEp_U4FJmhnOVTjXibXVFTC8ADFfHA-jfM_OwPjLjuU-TH_rsQ@mail.gmail.com>
As soon as basic metadata API is merged (
https://github.com/windup/windup/pull/493) :
Matej, https://issues.jboss.org/browse/WINDUP-521
Ondra, https://issues.jboss.org/browse/WINDUP-523
Jess, https://issues.jboss.org/browse/WINDUP-522
For now, assume it will be merged as-is, and go ahead with your tasks using
the work in the PR. Should be merged before morning (once tests pass).
Thanks!
Just FYI - We have 8 days left in the sprint :) Should be plenty of time to
accomplish these sub-tasks. (Barring drastic problems.)
--
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/20150310/8508c08e/attachment.html
From lincolnbaxter at gmail.com Wed Mar 11 11:22:20 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 11 Mar 2015 11:22:20 -0400
Subject: [windup-dev] Windup meeting minutes - 2015-03-11
Message-ID: <CAEp_U4GoDrFLpWNCkDNOJmZVQLdy8GWawrjjaryqrcKc9LPMvw@mail.gmail.com>
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-03-11-15.11.html
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-03-11-15.11.txt
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-03-11-15.11.log.html
Meeting summary
---------------
* Agenda (lincolnthree, 15:11:10)
* Status Reports (lincolnthree, 15:12:56)
* Last week I worked a lot on WINDUP-520, which is now done (and I
need to close it) (lincolnthree, 15:13:10)
* I helped Marc Zottner get going with his prototype webapp
(lincolnthree, 15:14:22)
* I reviewed several PRs (lincolnthree, 15:14:32)
* Ok... I worked on WINDUP-522 (source/target options), though I
couldn't do too much yet (it was waiting on WINDUP-520) (jsightler,
15:16:43)
* Also, I have worked on merging some PRs related to the AST, to
improve type resolution, and I have been experimenting to improve
our type resolution process (jsightler, 15:17:17)
* I have sent the first PR related to this
(https://github.com/windup/windup/pull/494), and that simply tries
to extract every detail that is possible from Java @Annotations.
This will probably be a side project for a while to enhance our
support of advanced queries. (jsightler, 15:18:15)
* Priorities (lincolnthree, 15:18:29)
* Finishing work on WINDUP-521, WINDUP-522, WINDUP-523 are top
priority :) I think everyone knows that. (lincolnthree, 15:18:51)
Meeting ended at 15:20:29 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/20150311/9aa081c3/attachment.html
From ozizka at redhat.com Wed Mar 11 19:19:26 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 12 Mar 2015 00:19:26 +0100
Subject: [windup-dev] Quickstarts updated to reflect latest Windup Core
changes - artifactId renames, metadata API, class renames, etc.
Message-ID: <5500CD7E.2000400@redhat.com>
I must say, with metadata in @RuleMetadata, Java rules look much, much
nicer.
There's a danger it will become actually a nice API :)
Ondra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150312/b20098d3/attachment.html
From lincolnbaxter at gmail.com Thu Mar 12 10:52:58 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 12 Mar 2015 10:52:58 -0400
Subject: [windup-dev] Windup: Sprint 4 goals March 18 -> June 5th
(2.3.0.Final)
Message-ID: <CAEp_U4GhGGJ8a05t-ZmV2V6AhAW1F5dbSAK6GU9MPKVTR6PqYw@mail.gmail.com>
Hi everyone,
This is a longer sprint, but we have loftier goals:
1. Performance tuning
2. Server configuration migration (working with EAP team)
3. Examples, quick-starts, and tutorials
4. Eclipse plugin (basic functionality, no refactoring support.)
Please let me know if there are any questions. This is going to be a
critical sprint for getting the features needed to help people migrate
their app-servers!
--
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/20150312/0d7cdca0/attachment.html
From sgilda at redhat.com Mon Mar 16 13:18:54 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Mon, 16 Mar 2015 13:18:54 -0400
Subject: [windup-dev] Unable to access your link
Message-ID: <5507107E.905@redhat.com>
Hi Samuel,
I am not able to access the link you pasted in IRC:
https://github.com/redhat-gpe/windup/blob/master/modules/04_custom_rules/04_custom_java_rule_Lab.adoc
Is that a public repository? If not, I think I need access rights.
Thanks,
Sande
From lincolnbaxter at gmail.com Tue Mar 17 16:45:07 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 17 Mar 2015 16:45:07 -0400
Subject: [windup-dev] Performance component added to JIRA
Message-ID: <CAEp_U4HW5rUEBkoWsMHMUUWfL_8j7N+TsG=j1ZnHccevn0=nMw@mail.gmail.com>
Hey Team,
In preparation for the upcoming sprint, in which performance optimization
is a priority, I've added a "Performance" component to our issue tracker.
You can find this here:
https://issues.jboss.org/browse/WINDUP/component/12321287
Please create an issue for each new performance-related problem or
complaint that we find or receive. We need to track this information and
make sure we are staying on top of all the issues as they come.
I also think this will help us find trends.
Cheers!
--
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/20150317/1633991e/attachment.html
From lincoln at redhat.com Mon Mar 23 10:23:09 2015
From: lincoln at redhat.com (Lincoln Baxter, III)
Date: Mon, 23 Mar 2015 10:23:09 -0400 (EDT)
Subject: [windup-dev] Furnace not finding Windup FileService
In-Reply-To: <848601461.917867.1427075856080.JavaMail.zimbra@redhat.com>
References: <662321974.765317.1427014663076.JavaMail.zimbra@redhat.com>
<806195538.767666.1427015935764.JavaMail.zimbra@redhat.com>
<2124536037.894108.1427068168764.JavaMail.zimbra@redhat.com>
<848601461.917867.1427075856080.JavaMail.zimbra@redhat.com>
Message-ID: <1671296303.1439386.1427120589263.JavaMail.zimbra@redhat.com>
Hey Ian,
(Adding windup-dev.)
I'm not really sure what this issue could be, but it worries me that you needed to add a method to FurnaceService. What did you add? You can't ask Furnace for an instance of a type that is not a Service. (It wouldn't know how to construct it.)
The last error you received worries me specifically because it makes me think that there is something funky going on with the ClassLoader hierarchy itself, and that is never good; however, it could be due to some kind of quirk with what you added (it also may be a bug), so I think I need to see what you are doing.
Could you show me where this code is so that I can take a look?
Thanks!
~Lincoln
----- Original Message -----
From: "Ian Tewksbury" <itewk at redhat.com>
To: "Lincoln Baxter" <lbaxter at redhat.com>
Cc: "Robb Greathouse" <robb.greathouse at redhat.com>
Sent: Sunday, March 22, 2015 9:57:36 PM
Subject: Re: Furnace not finding Windup FileService
Licoln,
Got passed those previous errors. New error now:
!ENTRY org.eclipse.core.jobs 4 2 2015-03-22 21:52:59.403
!MESSAGE An internal error occurred during: "Validating".
!STACK 0
java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/tools/forge/core/internal/furnace/CompositeFurnaceClassLoader) previously initiated loading for a different type with name "org/jboss/forge/furnace/util/Predicate"
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2615)
at java.lang.Class.getDeclaredMethods(Class.java:1860)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.findMethod2(RuntimeSupport.java:134)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.findMethod(RuntimeSupport.java:65)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.find2Methods(RuntimeSupport.java:53)
at org.jboss.windup.exec.configuration.WindupConfiguration_$$_javassist_5effd6de-6f27-4c9d-9f94-b9492b06844c.<clinit>(WindupConfiguration_$$_javassist_5effd6de-6f27-4c9d-9f94-b9492b06844c.java)
at sun.misc.Unsafe.ensureClassInitialized(Native Method)
at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:43)
at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:140)
at java.lang.reflect.Field.acquireFieldAccessor(Field.java:1057)
at java.lang.reflect.Field.getFieldAccessor(Field.java:1038)
at java.lang.reflect.Field.set(Field.java:741)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.setField(ProxyFactory.java:525)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass3(ProxyFactory.java:508)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass2(ProxyFactory.java:492)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass1(ProxyFactory.java:428)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:400)
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:253)
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.forge.furnace.services.Imported_$$_javassist_34707ba1-98fb-4b8a-93ed-559398be971b.get(Imported_$$_javassist_34707ba1-98fb-4b8a-93ed-559398be971b.java)
at org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:96)
at org.jboss.tools.windup.core.WindupService.getServiceFromFurnace(WindupService.java:485)
at org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:226)
at org.jboss.tools.windup.core.WindupService.getGraph(WindupService.java:301)
at org.jboss.tools.windup.core.WindupService.getInlineHints(WindupService.java:103)
at org.jboss.tools.windup.core.internal.validators.WindupValidator.validate(WindupValidator.java:81)
at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134)
at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:68)
at org.eclipse.wst.validation.ui.internal.ManualValidationRunner.runInWorkspace(ManualValidationRunner.java:83)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Blue Skies,
~Ian
----- Original Message -----
From: "Ian Tewksbury" <itewk at redhat.com>
To: "Lincoln Baxter" <lbaxter at redhat.com>
Cc: "Robb Greathouse" <robb.greathouse at redhat.com>
Sent: Sunday, March 22, 2015 7:49:28 PM
Subject: Re: Furnace not finding Windup FileService
Licncoln,
I added some new API to the FurnaceService to be able to lookup a type which got me passed the below errors.
Now I am running into:
java.lang.NoClassDefFoundError: com/tinkerpop/frames/FramedGraph
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2615)
at java.lang.Class.getDeclaredMethods(Class.java:1860)
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:1096)
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.graph.GraphContextFactory_$$_javassist_2a504b60-d6e3-450e-87b5-f41eb849ab81.create(GraphContextFactory_$$_javassist_2a504b60-d6e3-450e-87b5-f41eb849ab81.java)
at org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:235)
at org.jboss.tools.windup.core.WindupService.getGraph(WindupService.java:303)
at org.jboss.tools.windup.core.WindupService.getInlineHints(WindupService.java:103)
at org.jboss.tools.windup.core.internal.validators.WindupValidator.validate(WindupValidator.java:81)
at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134)
at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:68)
at org.eclipse.wst.validation.ui.internal.ManualValidationRunner.runInWorkspace(ManualValidationRunner.java:83)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.ClassNotFoundException: com.tinkerpop.frames.FramedGraph 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)
... 32 more
I have verified that the Furnace add on 'org-jboss-windup-graph-windup-graph' is being loaded and contains the windup-frames JAR so I am not clear why furnace is not able to load the class.
Ideas?
Blue Skies,
~Ian
----- Original Message -----
From: "Ian Tewksbury" <itewk at redhat.com>
To: "Lincoln Baxter" <lbaxter at redhat.com>
Cc: "Robb Greathouse" <robb.greathouse at redhat.com>
Sent: Sunday, March 22, 2015 5:18:55 AM
Subject: Re: Furnace not finding Windup FileService
Lioncoln,
Looking here, http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/releases/org.jboss.forge.furnace.container/cdi-impl/2.10.1.Final/org/jboss/forge/furnace/container/cdi/impl/WeldServiceRegistry.java#WeldServiceRegistry.getExportedInstances%28java.lang.Class%29 , and debuging through eclipse without source, I have figured out it is choking on like 189. It appears this #getExportedInstances method is only for loading beans. I see a #getExportedType which is what I am guessing I need, but the only Furnace API I see is FurnaceService.INSTANCE.lookup(clazz) which ends up doing this bean lookup rather then a type lookup. Am I missing something here? Is there just missing API to look up a type and not a bean via Furnace?
Blue Skies,
~Ian
----- Original Message -----
From: "Ian Tewksbury" <itewk at redhat.com>
To: "Lincoln Baxter" <lbaxter at redhat.com>, "Robb Greathouse" <robb.greathouse at redhat.com>
Sent: Sunday, March 22, 2015 4:57:43 AM
Subject: Furnace not finding Windup FileService
Lincoln,
I can not figure out why Furnance is reporting that it can not find the Windup FileService despite the fact that it is reporting it loaded the graph-api addon. Any ideas?
Please see attached for the log. It clearly shows the graph-api addon being loaded. And I have verified that addon contains the graph-api.jar which contains the FileService. I have tried to debug the furnace stuff but I keep running into source not found issues and getting lost. I have been able to tell that ImportedImpl#getExportedInstances is getting called and it is looping over the graph-api addon. But it does not seem to find the class in there, but I have not been able to debug into furnace beyond that point.
Looking at the variable state the WeldServiceRegistery instance for the graph-api addon shows the FIleService there. For some reason it is just not being retrevied. I have attached a screenshoot of the variable state from within ImportedImpl#getExportedInstances. Can you think of any reason serviceRegistry.getExportedInstances(type) would be failing giving all of this?
~Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150323/7d87a2a0/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: windup.png
Type: image/png
Size: 172297 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150323/7d87a2a0/attachment-0001.png
From ozizka at redhat.com Tue Mar 24 21:00:05 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 25 Mar 2015 02:00:05 +0100
Subject: [windup-dev] PreRulesetEvaluation?
Message-ID: <55120895.6040801@redhat.com>
Hi,
PreRulesetEvaluation is used in WindupProcessorImpl - called on all
Rules that imlement that, before calling
ruleSubset.perform(event, createEvaluationContext());
Is this where we technically initialize the rule subset?
Because if it can be for each rule, then it would be, effectively,
another phase, before Initialize.
In that case, wouldn't it be a cleaner design to let this happen in rule
subset specific class?
Regards,
Ondra
From ozizka at redhat.com Tue Mar 24 21:31:23 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 25 Mar 2015 02:31:23 +0100
Subject: [windup-dev] FileMapping.getId()
Message-ID: <55120FEB.5030601@redhat.com>
@Override
public String getId()
{
return this.getClass().getName() + "_" +
UUID.randomUUID().toString();
}
Isn't it a potential problem that this returns different values on each
call?
Shouldn't it store a value once called? Or derive the value from, say, a
class object? Or just use Class#hashCode()?
And maybe this method's default impl should move to GraphRule?
What if we refrained from using UUID which gives unnecessary long
strings, and used RandomStringUtils.randomAlphanumeric(6) or such?
And lastly, this could be
Regards,
Ondra
From jsightle at redhat.com Wed Mar 25 11:28:33 2015
From: jsightle at redhat.com (Jess Sightler)
Date: Wed, 25 Mar 2015 11:28:33 -0400
Subject: [windup-dev] FileMapping.getId()
In-Reply-To: <55120FEB.5030601@redhat.com>
References: <55120FEB.5030601@redhat.com>
Message-ID: <5512D421.4080506@redhat.com>
On 03/24/2015 09:31 PM, Ondrej Zizka wrote:
> @Override
> public String getId()
> {
> return this.getClass().getName() + "_" +
> UUID.randomUUID().toString();
> }
>
> Isn't it a potential problem that this returns different values on each
> call?
> Shouldn't it store a value once called? Or derive the value from, say, a
> class object? Or just use Class#hashCode()?
I agree. It seems like a mistake that repeated calls to the same object
here will return different values.
From lincolnbaxter at gmail.com Wed Mar 25 11:56:21 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 25 Mar 2015 11:56:21 -0400
Subject: [windup-dev] Windup Meeting Minutes - 2015-03-25
Message-ID: <CAEp_U4GNTAsriOXMmgMyC=jHcPsQOx5xg5vAdnuWe134z78Ugw@mail.gmail.com>
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-03-25-15.07.html
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-03-25-15.07.txt
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-03-25-15.07.log.html
Meeting summary
---------------
* Agenda (lincolnthree, 15:08:03)
* Status reports (lincolnthree, 15:08:16)
* Priorities (lincolnthree, 15:08:19)
* 2.2.0.Final Release (lincolnthree, 15:08:32)
* Status Reports (lincolnthree, 15:10:25)
* I worked on WINDUP-544 (crash with some applications) (jsightler,
15:16:56)
* I also fixed a major AST performance regression with larger
applications (jsightler, 15:17:10)
* WINDUP-523 Rule Externalization - Allow filtering of
RuleProviders by tags (categories) (ozizka, 15:17:24)
* Set up windup-rulesets Jenkins job - triggers after pr job succeeds
(ozizka, 15:17:24)
* Trying to find out a way to run the tests faster - maybe tmpfs both
on OS1 and locally. (ozizka, 15:17:24)
* WINDUP-460 RuleMetadata.TREAT_EXCEPTIONS_AS_FATAL is unimplemented
(ozizka, 15:17:24)
* Starting work on MIGR-229 Server configuration migration (ozizka,
15:17:24)
* I ran several (ozizka, 15:17:25)
* And I have done some work on reviewing and merging PRs for the
release (jsightler, 15:17:27)
* I was mainly working on FORGE-2283/MIGR-198 (addons updating in
Forge/Windup) that led me to find potential bugs like WINDUP-545,
FURNACE-35 (mbriskar_, 15:18:38)
* I worked on reviewing several PRs and doing some merges.
(lincolnthree, 15:29:06)
* I also worked on writing copy for the website ux prototypes with
Sande (lincolnthree, 15:29:07)
* I did profiling work on the Decompiler (and Windup as a whole) with
Jess (lincolnthree, 15:29:07)
* Also worked with jess and Sande to book travel for F2F so that we
all arrive at the same time (lincolnthree, 15:29:07)
* My next goal is to get the 2.2.0.Final release done (lincolnthree,
15:29:07)
* After that, I will work on enabling graph indexes by annotation
(lincolnthree, 15:29:07)
* Priorities (lincolnthree, 15:29:15)
* 1. Performance (lincolnthree, 15:29:43)
* 2. Server config migration (lincolnthree, 15:29:53)
* 3. Examples and Quickstarts (lincolnthree, 15:30:32)
* 4. Eclipse tooling (lincolnthree, 15:30:39)
* ACTION: Look at possibility to use javac instead of JDT? (ozizka,
15:43:37)
* ACTION: Option to skip decompilation and parsing? (ozizka,
15:46:08)
* 2.2.0.Final Release (lincolnthree, 15:46:15)
* I will be working on the 2.2.0.Final release immediately after this
meeting (lincolnthree, 15:46:34)
* Matt UX meeting? (lincolnthree, 15:46:50)
* Java AST sync session? (lincolnthree, 15:48:30)
--
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/20150325/b67026a9/attachment.html
From itewk at redhat.com Wed Mar 25 12:33:16 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Wed, 25 Mar 2015 12:33:16 -0400 (EDT)
Subject: [windup-dev] Furnace not finding Windup FileService
In-Reply-To: <1671296303.1439386.1427120589263.JavaMail.zimbra@redhat.com>
References: <662321974.765317.1427014663076.JavaMail.zimbra@redhat.com>
<806195538.767666.1427015935764.JavaMail.zimbra@redhat.com>
<2124536037.894108.1427068168764.JavaMail.zimbra@redhat.com>
<848601461.917867.1427075856080.JavaMail.zimbra@redhat.com>
<1671296303.1439386.1427120589263.JavaMail.zimbra@redhat.com>
Message-ID: <1962890038.2398764.1427301196084.JavaMail.zimbra@redhat.com>
Lincoln,
Sorry. I just saw this. My email filters took over when you added the windup mailing list and it got filtered out of my main inbox.
The Furnace method I added was:
public <S> S lookupType(Class<S> service) {
S instance = null;
if (furnace != null) {
Set<Class<S>> types = null;
types = furnace.getAddonRegistry().getExportedTypes(service);
if (types != null && !types.isEmpty()) {
for(Class<S> type : types) {
try {
instance = type.newInstance();
break;
} catch (Exception e) {
e.getMessage();
//skip to next instance if this one did not work
}
}
}
}
return instance;
}
My issue was with loading "FileService.class". Calling "lookup" could not find it, but calling my new "lookupType" it could find it.
Blue Skies,
~Ian
----- Original Message -----
From: "Lincoln Baxter, III" <lincoln at redhat.com>
To: "Ian Tewksbury" <itewk at redhat.com>
Cc: "Robb Greathouse" <robb.greathouse at redhat.com>, "George Gastaldi" <ggastald at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Monday, March 23, 2015 10:23:09 AM
Subject: Re: Furnace not finding Windup FileService
Hey Ian,
(Adding windup-dev.)
I'm not really sure what this issue could be, but it worries me that you needed to add a method to FurnaceService. What did you add? You can't ask Furnace for an instance of a type that is not a Service. (It wouldn't know how to construct it.)
The last error you received worries me specifically because it makes me think that there is something funky going on with the ClassLoader hierarchy itself, and that is never good; however, it could be due to some kind of quirk with what you added (it also may be a bug), so I think I need to see what you are doing.
Could you show me where this code is so that I can take a look?
Thanks!
~Lincoln
----- Original Message -----
From: "Ian Tewksbury" <itewk at redhat.com>
To: "Lincoln Baxter" <lbaxter at redhat.com>
Cc: "Robb Greathouse" <robb.greathouse at redhat.com>
Sent: Sunday, March 22, 2015 9:57:36 PM
Subject: Re: Furnace not finding Windup FileService
Licoln,
Got passed those previous errors. New error now:
!ENTRY org.eclipse.core.jobs 4 2 2015-03-22 21:52:59.403
!MESSAGE An internal error occurred during: "Validating".
!STACK 0
java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/tools/forge/core/internal/furnace/CompositeFurnaceClassLoader) previously initiated loading for a different type with name "org/jboss/forge/furnace/util/Predicate"
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2615)
at java.lang.Class.getDeclaredMethods(Class.java:1860)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.findMethod2(RuntimeSupport.java:134)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.findMethod(RuntimeSupport.java:65)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.find2Methods(RuntimeSupport.java:53)
at org.jboss.windup.exec.configuration.WindupConfiguration_$$_javassist_5effd6de-6f27-4c9d-9f94-b9492b06844c.<clinit>(WindupConfiguration_$$_javassist_5effd6de-6f27-4c9d-9f94-b9492b06844c.java)
at sun.misc.Unsafe.ensureClassInitialized(Native Method)
at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:43)
at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:140)
at java.lang.reflect.Field.acquireFieldAccessor(Field.java:1057)
at java.lang.reflect.Field.getFieldAccessor(Field.java:1038)
at java.lang.reflect.Field.set(Field.java:741)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.setField(ProxyFactory.java:525)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass3(ProxyFactory.java:508)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass2(ProxyFactory.java:492)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass1(ProxyFactory.java:428)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:400)
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:253)
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.forge.furnace.services.Imported_$$_javassist_34707ba1-98fb-4b8a-93ed-559398be971b.get(Imported_$$_javassist_34707ba1-98fb-4b8a-93ed-559398be971b.java)
at org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:96)
at org.jboss.tools.windup.core.WindupService.getServiceFromFurnace(WindupService.java:485)
at org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:226)
at org.jboss.tools.windup.core.WindupService.getGraph(WindupService.java:301)
at org.jboss.tools.windup.core.WindupService.getInlineHints(WindupService.java:103)
at org.jboss.tools.windup.core.internal.validators.WindupValidator.validate(WindupValidator.java:81)
at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134)
at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:68)
at org.eclipse.wst.validation.ui.internal.ManualValidationRunner.runInWorkspace(ManualValidationRunner.java:83)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Blue Skies,
~Ian
----- Original Message -----
From: "Ian Tewksbury" <itewk at redhat.com>
To: "Lincoln Baxter" <lbaxter at redhat.com>
Cc: "Robb Greathouse" <robb.greathouse at redhat.com>
Sent: Sunday, March 22, 2015 7:49:28 PM
Subject: Re: Furnace not finding Windup FileService
Licncoln,
I added some new API to the FurnaceService to be able to lookup a type which got me passed the below errors.
Now I am running into:
java.lang.NoClassDefFoundError: com/tinkerpop/frames/FramedGraph
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2615)
at java.lang.Class.getDeclaredMethods(Class.java:1860)
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:1096)
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.graph.GraphContextFactory_$$_javassist_2a504b60-d6e3-450e-87b5-f41eb849ab81.create(GraphContextFactory_$$_javassist_2a504b60-d6e3-450e-87b5-f41eb849ab81.java)
at org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:235)
at org.jboss.tools.windup.core.WindupService.getGraph(WindupService.java:303)
at org.jboss.tools.windup.core.WindupService.getInlineHints(WindupService.java:103)
at org.jboss.tools.windup.core.internal.validators.WindupValidator.validate(WindupValidator.java:81)
at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134)
at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:68)
at org.eclipse.wst.validation.ui.internal.ManualValidationRunner.runInWorkspace(ManualValidationRunner.java:83)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.ClassNotFoundException: com.tinkerpop.frames.FramedGraph 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)
... 32 more
I have verified that the Furnace add on 'org-jboss-windup-graph-windup-graph' is being loaded and contains the windup-frames JAR so I am not clear why furnace is not able to load the class.
Ideas?
Blue Skies,
~Ian
----- Original Message -----
From: "Ian Tewksbury" <itewk at redhat.com>
To: "Lincoln Baxter" <lbaxter at redhat.com>
Cc: "Robb Greathouse" <robb.greathouse at redhat.com>
Sent: Sunday, March 22, 2015 5:18:55 AM
Subject: Re: Furnace not finding Windup FileService
Lioncoln,
Looking here, http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/releases/org.jboss.forge.furnace.container/cdi-impl/2.10.1.Final/org/jboss/forge/furnace/container/cdi/impl/WeldServiceRegistry.java#WeldServiceRegistry.getExportedInstances%28java.lang.Class%29 , and debuging through eclipse without source, I have figured out it is choking on like 189. It appears this #getExportedInstances method is only for loading beans. I see a #getExportedType which is what I am guessing I need, but the only Furnace API I see is FurnaceService.INSTANCE.lookup(clazz) which ends up doing this bean lookup rather then a type lookup. Am I missing something here? Is there just missing API to look up a type and not a bean via Furnace?
Blue Skies,
~Ian
----- Original Message -----
From: "Ian Tewksbury" <itewk at redhat.com>
To: "Lincoln Baxter" <lbaxter at redhat.com>, "Robb Greathouse" <robb.greathouse at redhat.com>
Sent: Sunday, March 22, 2015 4:57:43 AM
Subject: Furnace not finding Windup FileService
Lincoln,
I can not figure out why Furnance is reporting that it can not find the Windup FileService despite the fact that it is reporting it loaded the graph-api addon. Any ideas?
Please see attached for the log. It clearly shows the graph-api addon being loaded. And I have verified that addon contains the graph-api.jar which contains the FileService. I have tried to debug the furnace stuff but I keep running into source not found issues and getting lost. I have been able to tell that ImportedImpl#getExportedInstances is getting called and it is looping over the graph-api addon. But it does not seem to find the class in there, but I have not been able to debug into furnace beyond that point.
Looking at the variable state the WeldServiceRegistery instance for the graph-api addon shows the FIleService there. For some reason it is just not being retrevied. I have attached a screenshoot of the variable state from within ImportedImpl#getExportedInstances. Can you think of any reason serviceRegistry.getExportedInstances(type) would be failing giving all of this?
~Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150325/5fdbab90/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: windup.png
Type: image/png
Size: 172297 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150325/5fdbab90/attachment-0001.png
From lincolnbaxter at gmail.com Thu Mar 26 15:39:13 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 26 Mar 2015 15:39:13 -0400
Subject: [windup-dev] Windup 2.2.0.Final Released
Message-ID: <CAEp_U4H9NYdg2KPTTD2Da0E7acawwL=WXwA9E2R+vXanEY0HEA@mail.gmail.com>
I am proud to announce the release of Windup 2.2.0.Final, which includes
the following features/enhanvements/and bugfixes.
Great job team!
~Lincoln
Bug
- [WINDUP-510 <https://issues.jboss.org/browse/WINDUP-510>] - Build
fails with BOM missing
- [WINDUP-511 <https://issues.jboss.org/browse/WINDUP-511>] -
Quickstarts tests fail with a NPE
- [WINDUP-516 <https://issues.jboss.org/browse/WINDUP-516>] -
[Performance] Multiple valueStores even if the rule does not use parameters
- [WINDUP-517 <https://issues.jboss.org/browse/WINDUP-517>] -
Application Index page lacks technology list and effort information
- [WINDUP-518 <https://issues.jboss.org/browse/WINDUP-518>] - XML
Handlers do not support nested rules
- [WINDUP-524 <https://issues.jboss.org/browse/WINDUP-524>] - Fix the
cyclic dependency between windup and windup-rulesets
- [WINDUP-542 <https://issues.jboss.org/browse/WINDUP-542>] - Fix severe
regression in AST performance
- [WINDUP-544 <https://issues.jboss.org/browse/WINDUP-544>] -
StackOverflowException when generating Application report
Enhancement
- [WINDUP-409 <https://issues.jboss.org/browse/WINDUP-409>] - Allow
rules metadata to be specified with annotations - @Rules( phase = ..., ...)
- [WINDUP-470 <https://issues.jboss.org/browse/WINDUP-470>] - Classes in
java.lang package may differ in how they are parsed
- [WINDUP-506 <https://issues.jboss.org/browse/WINDUP-506>] - Identify
Archives Ruleset: Improve memory footprint
- [WINDUP-508 <https://issues.jboss.org/browse/WINDUP-508>] -
WindupRuleProvider should contain a location/origin field (to indicate
where it was defined)
- [WINDUP-515 <https://issues.jboss.org/browse/WINDUP-515>] - Add
Severity to Hint
- [WINDUP-520 <https://issues.jboss.org/browse/WINDUP-520>] - Rule
Externalization - Introduce a Rule, RuleProvider and RulesetMetadata API
- [WINDUP-529 <https://issues.jboss.org/browse/WINDUP-529>] -
Performance issue: Query requires iterating over all vertices
[(ClassificationModel:classification = ...)]
Feature Request
- [WINDUP-402 <https://issues.jboss.org/browse/WINDUP-402>] - Change
ruleset category metadata to tag-like system (make it a set of strings)
- [WINDUP-521 <https://issues.jboss.org/browse/WINDUP-521>] - Rule
Externalization - Create XML Handlers for Rule metadata
- [WINDUP-522 <https://issues.jboss.org/browse/WINDUP-522>] - Rule
Externalization - Create user-interface for selecting source/target
platforms
- [WINDUP-523 <https://issues.jboss.org/browse/WINDUP-523>] - Rule
Externalization - Allow filtering of RuleProviders by tags (categories)
Task
- [WINDUP-512 <https://issues.jboss.org/browse/WINDUP-512>] - Rename
Implicit to Dependent
- [WINDUP-513 <https://issues.jboss.org/browse/WINDUP-513>] - Phase
pseudo-RuleProviders to have ~Phase suffix
- [WINDUP-530 <https://issues.jboss.org/browse/WINDUP-530>] - Rename the
module "utils" to "windup-utils"
Sub-task
- [WINDUP-464 <https://issues.jboss.org/browse/WINDUP-464>] - Expand all
addons with simple layout to use full api/impl/tests structure
- [WINDUP-465 <https://issues.jboss.org/browse/WINDUP-465>] - Review all
rules, organize into an external repository, and add useful hint
information with links to knowledge articles
--
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/20150326/e17abe72/attachment.html
From itewk at redhat.com Fri Mar 27 08:35:15 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Fri, 27 Mar 2015 08:35:15 -0400 (EDT)
Subject: [windup-dev] previously initiated loading for a different type with
name "org/jboss/forge/furnace/util/Predicate"
In-Reply-To: <1636015576.3558253.1427458728820.JavaMail.zimbra@redhat.com>
Message-ID: <2043165694.3578175.1427459715403.JavaMail.zimbra@redhat.com>
Lincoln and Jess,
I have spent another evening trying to defeat this class loading error with no luck.
What I have tried:
1. Debugging CompositeFurnaceClassLoader
1. changed #loadClass to #findClass as per ClassLoader suggestion , didn't help
2. put break point in #findClass to see how many times it is called for org.jboss.forge.furnace.util.Predicate, it is only being called once, and on that one call it is failing with the LinkageError, this makes 0 sense to me since the error says that it has already been loaded
3. Tried various combinations of checking to see if the class has already been loaded, no luck
4. Tried creating a cache of already loaded classes, didn't help, which makes sense because the #findClass method (or #loadClass if you dont use my change) only gets called once for this class.
2.
I have updated the windup-eclipse plugin to use the latest furnace version, 2.15.2.Final, didn't make a difference 3. I have updated the windup-eclipse plugin to use the latest Windup 2.2.0 Release, plus my changes to add default constructor to WindupService and FileService
4. I have stopped using my custom loadType function I was talking about earlier, that was a red hearing I believe
5. I have spent hours googling this error message with no solution path to be fund
At this point I am totally blocked. I don't know what to try next.
My latest code is here:
plugin - https://github.com/windup/windup-eclipse-plugin/tree/windup2
windup - https://github.com/itewk/windup/tree/windup-eclipse
* as a reminder you can't use SNAPSHOT versions for WINDUP when compiling the windup eclipse plugin with local changes to Windup because it will always pull the snapshot from the remote repository and ignore your local changes, unless using releases in which case maven looks at the local repo first
Has anyone been able to try and reproduce this themselves yet?
Has anyone been able to look over my WindupServices class to make sure I am properly using Forge/Furnace to access Windup?
I am either doing something really dumb on my end when trying to access Windup or there is a bug/logic error with the CompositeFurnaceClassLoader.
Blue Skies,
~Ian
!ENTRY org.eclipse.core.jobs 4 2 2015-03-27 08:04:51.234
!MESSAGE An internal error occurred during: "Validating".
!STACK 0
java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/tools/forge/core/internal/furnace/CompositeFurnaceClassLoader) previously initiated loading for a different type with name "org/jboss/forge/furnace/util/Predicate"
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2615)
at java.lang.Class.getDeclaredMethods(Class.java:1860)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.findMethod2(RuntimeSupport.java:134)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.findMethod(RuntimeSupport.java:65)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.find2Methods(RuntimeSupport.java:53)
at org.jboss.windup.exec.configuration.WindupConfiguration_$$_javassist_bdf99157-4ab9-4bb9-a9ec-03565e9d16d6.<clinit>(WindupConfiguration_$$_javassist_bdf99157-4ab9-4bb9-a9ec-03565e9d16d6.java)
at sun.misc.Unsafe.ensureClassInitialized(Native Method)
at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:43)
at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:140)
at java.lang.reflect.Field.acquireFieldAccessor(Field.java:1057)
at java.lang.reflect.Field.getFieldAccessor(Field.java:1038)
at java.lang.reflect.Field.set(Field.java:741)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.setField(ProxyFactory.java:525)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass3(ProxyFactory.java:508)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass2(ProxyFactory.java:492)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass1(ProxyFactory.java:428)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:400)
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:253)
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.forge.furnace.services.Imported_$$_javassist_48ac554d-8d60-4d09-8f17-c0a42f2c85b7.get(Imported_$$_javassist_48ac554d-8d60-4d09-8f17-c0a42f2c85b7.java)
at org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:96)
at org.jboss.tools.windup.core.WindupService.getServiceFromFurnace(WindupService.java:485)
at org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:226)
at org.jboss.tools.windup.core.WindupService.getGraph(WindupService.java:301)
at org.jboss.tools.windup.core.WindupService.getInlineHints(WindupService.java:103)
at org.jboss.tools.windup.core.internal.validators.WindupValidator.validate(WindupValidator.java:81)
at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134)
at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:68)
at org.eclipse.wst.validation.ui.internal.ManualValidationRunner.runInWorkspace(ManualValidationRunner.java:83)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150327/39d48f28/attachment-0001.html
From itewk at redhat.com Fri Mar 27 08:38:39 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Fri, 27 Mar 2015 08:38:39 -0400 (EDT)
Subject: [windup-dev] previously initiated loading for a different type
with name "org/jboss/forge/furnace/util/Predicate"
In-Reply-To: <2043165694.3578175.1427459715403.JavaMail.zimbra@redhat.com>
References: <2043165694.3578175.1427459715403.JavaMail.zimbra@redhat.com>
Message-ID: <170796846.3582655.1427459919617.JavaMail.zimbra@redhat.com>
Adding resources from the JBDS team in case they were interested in trying to help solve these class loading issues.
Blue Skies,
~Ian
----- Original Message -----
From: "Ian Tewksbury" <itewk at redhat.com>
To: "Lincoln Baxter" <lbaxter at redhat.com>, "Jess Sightler" <jsightle at redhat.com>, "Pete Muir" <pmuir at redhat.com>
Cc: "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Friday, March 27, 2015 8:35:15 AM
Subject: [windup-dev] previously initiated loading for a different type with name "org/jboss/forge/furnace/util/Predicate"
Lincoln and Jess,
I have spent another evening trying to defeat this class loading error with no luck.
What I have tried:
1. Debugging CompositeFurnaceClassLoader
1. changed #loadClass to #findClass as per ClassLoader suggestion , didn't help
2. put break point in #findClass to see how many times it is called for org.jboss.forge.furnace.util.Predicate, it is only being called once, and on that one call it is failing with the LinkageError, this makes 0 sense to me since the error says that it has already been loaded
3. Tried various combinations of checking to see if the class has already been loaded, no luck
4. Tried creating a cache of already loaded classes, didn't help, which makes sense because the #findClass method (or #loadClass if you dont use my change) only gets called once for this class.
2.
I have updated the windup-eclipse plugin to use the latest furnace version, 2.15.2.Final, didn't make a difference 3. I have updated the windup-eclipse plugin to use the latest Windup 2.2.0 Release, plus my changes to add default constructor to WindupService and FileService
4. I have stopped using my custom loadType function I was talking about earlier, that was a red hearing I believe
5. I have spent hours googling this error message with no solution path to be fund
At this point I am totally blocked. I don't know what to try next.
My latest code is here:
plugin - https://github.com/windup/windup-eclipse-plugin/tree/windup2
windup - https://github.com/itewk/windup/tree/windup-eclipse
* as a reminder you can't use SNAPSHOT versions for WINDUP when compiling the windup eclipse plugin with local changes to Windup because it will always pull the snapshot from the remote repository and ignore your local changes, unless using releases in which case maven looks at the local repo first
Has anyone been able to try and reproduce this themselves yet?
Has anyone been able to look over my WindupServices class to make sure I am properly using Forge/Furnace to access Windup?
I am either doing something really dumb on my end when trying to access Windup or there is a bug/logic error with the CompositeFurnaceClassLoader.
Blue Skies,
~Ian
!ENTRY org.eclipse.core.jobs 4 2 2015-03-27 08:04:51.234
!MESSAGE An internal error occurred during: "Validating".
!STACK 0
java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/tools/forge/core/internal/furnace/CompositeFurnaceClassLoader) previously initiated loading for a different type with name "org/jboss/forge/furnace/util/Predicate"
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2615)
at java.lang.Class.getDeclaredMethods(Class.java:1860)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.findMethod2(RuntimeSupport.java:134)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.findMethod(RuntimeSupport.java:65)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.find2Methods(RuntimeSupport.java:53)
at org.jboss.windup.exec.configuration.WindupConfiguration_$$_javassist_bdf99157-4ab9-4bb9-a9ec-03565e9d16d6.<clinit>(WindupConfiguration_$$_javassist_bdf99157-4ab9-4bb9-a9ec-03565e9d16d6.java)
at sun.misc.Unsafe.ensureClassInitialized(Native Method)
at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:43)
at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:140)
at java.lang.reflect.Field.acquireFieldAccessor(Field.java:1057)
at java.lang.reflect.Field.getFieldAccessor(Field.java:1038)
at java.lang.reflect.Field.set(Field.java:741)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.setField(ProxyFactory.java:525)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass3(ProxyFactory.java:508)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass2(ProxyFactory.java:492)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass1(ProxyFactory.java:428)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:400)
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:253)
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.forge.furnace.services.Imported_$$_javassist_48ac554d-8d60-4d09-8f17-c0a42f2c85b7.get(Imported_$$_javassist_48ac554d-8d60-4d09-8f17-c0a42f2c85b7.java)
at org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:96)
at org.jboss.tools.windup.core.WindupService.getServiceFromFurnace(WindupService.java:485)
at org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:226)
at org.jboss.tools.windup.core.WindupService.getGraph(WindupService.java:301)
at org.jboss.tools.windup.core.WindupService.getInlineHints(WindupService.java:103)
at org.jboss.tools.windup.core.internal.validators.WindupValidator.validate(WindupValidator.java:81)
at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134)
at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:68)
at org.eclipse.wst.validation.ui.internal.ManualValidationRunner.runInWorkspace(ManualValidationRunner.java:83)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
_______________________________________________
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/20150327/1f14342e/attachment.html
From pmuir at redhat.com Fri Mar 27 08:52:38 2015
From: pmuir at redhat.com (Pete Muir)
Date: Fri, 27 Mar 2015 12:52:38 +0000
Subject: [windup-dev] previously initiated loading for a different type
with name "org/jboss/forge/furnace/util/Predicate"
In-Reply-To: <170796846.3582655.1427459919617.JavaMail.zimbra@redhat.com>
References: <2043165694.3578175.1427459715403.JavaMail.zimbra@redhat.com>
<170796846.3582655.1427459919617.JavaMail.zimbra@redhat.com>
Message-ID: <65F66041-DEAF-4DC0-A570-498C8FA79564@redhat.com>
Adding Koen and George who may be able to help. Dropping Cat and Burr :-)
> On 27 Mar 2015, at 12:38, Ian Tewksbury <itewk at redhat.com> wrote:
>
> Adding resources from the JBDS team in case they were interested in trying to help solve these class loading issues.
>
> Blue Skies,
> ~Ian
>
> From: "Ian Tewksbury" <itewk at redhat.com>
> To: "Lincoln Baxter" <lbaxter at redhat.com>, "Jess Sightler" <jsightle at redhat.com>, "Pete Muir" <pmuir at redhat.com>
> Cc: "Windup-dev List" <windup-dev at lists.jboss.org>
> Sent: Friday, March 27, 2015 8:35:15 AM
> Subject: [windup-dev] previously initiated loading for a different type with name "org/jboss/forge/furnace/util/Predicate"
>
> Lincoln and Jess,
>
> I have spent another evening trying to defeat this class loading error with no luck.
>
> What I have tried:
> Debugging CompositeFurnaceClassLoader
> changed #loadClass to #findClass as per ClassLoader suggestion, didn't help
> put break point in #findClass to see how many times it is called for org.jboss.forge.furnace.util.Predicate, it is only being called once, and on that one call it is failing with the LinkageError, this makes 0 sense to me since the error says that it has already been loaded
> Tried various combinations of checking to see if the class has already been loaded, no luck
> Tried creating a cache of already loaded classes, didn't help, which makes sense because the #findClass method (or #loadClass if you dont use my change) only gets called once for this class.
> I have updated the windup-eclipse plugin to use the latest furnace version, 2.15.2.Final, didn't make a difference
> I have updated the windup-eclipse plugin to use the latest Windup 2.2.0 Release, plus my changes to add default constructor to WindupService and FileService
> I have stopped using my custom loadType function I was talking about earlier, that was a red hearing I believe
> I have spent hours googling this error message with no solution path to be fund
> At this point I am totally blocked. I don't know what to try next.
>
> My latest code is here:
>
> plugin - https://github.com/windup/windup-eclipse-plugin/tree/windup2 <https://github.com/windup/windup-eclipse-plugin/tree/windup2>
> windup - https://github.com/itewk/windup/tree/windup-eclipse <https://github.com/itewk/windup/tree/windup-eclipse>
> * as a reminder you can't use SNAPSHOT versions for WINDUP when compiling the windup eclipse plugin with local changes to Windup because it will always pull the snapshot from the remote repository and ignore your local changes, unless using releases in which case maven looks at the local repo first
>
> Has anyone been able to try and reproduce this themselves yet?
> Has anyone been able to look over my WindupServices class to make sure I am properly using Forge/Furnace to access Windup?
>
> I am either doing something really dumb on my end when trying to access Windup or there is a bug/logic error with the CompositeFurnaceClassLoader.
>
> Blue Skies,
> ~Ian
>
> !ENTRY org.eclipse.core.jobs 4 2 2015-03-27 08:04:51.234
> !MESSAGE An internal error occurred during: "Validating".
> !STACK 0
> java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/tools/forge/core/internal/furnace/CompositeFurnaceClassLoader) previously initiated loading for a different type with name "org/jboss/forge/furnace/util/Predicate"
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2615)
> at java.lang.Class.getDeclaredMethods(Class.java:1860)
> at org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30)
> at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.findMethod2(RuntimeSupport.java:134)
> at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.findMethod(RuntimeSupport.java:65)
> at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.find2Methods(RuntimeSupport.java:53)
> at org.jboss.windup.exec.configuration.WindupConfiguration_$$_javassist_bdf99157-4ab9-4bb9-a9ec-03565e9d16d6.<clinit>(WindupConfiguration_$$_javassist_bdf99157-4ab9-4bb9-a9ec-03565e9d16d6.java)
> at sun.misc.Unsafe.ensureClassInitialized(Native Method)
> at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:43)
> at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:140)
> at java.lang.reflect.Field.acquireFieldAccessor(Field.java:1057)
> at java.lang.reflect.Field.getFieldAccessor(Field.java:1038)
> at java.lang.reflect.Field.set(Field.java:741)
> at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.setField(ProxyFactory.java:525)
> at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass3(ProxyFactory.java:508)
> at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass2(ProxyFactory.java:492)
> at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass1(ProxyFactory.java:428)
> at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:400)
> 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:253)
> 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.forge.furnace.services.Imported_$$_javassist_48ac554d-8d60-4d09-8f17-c0a42f2c85b7.get(Imported_$$_javassist_48ac554d-8d60-4d09-8f17-c0a42f2c85b7.java)
> at org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:96)
> at org.jboss.tools.windup.core.WindupService.getServiceFromFurnace(WindupService.java:485)
> at org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:226)
> at org.jboss.tools.windup.core.WindupService.getGraph(WindupService.java:301)
> at org.jboss.tools.windup.core.WindupService.getInlineHints(WindupService.java:103)
> at org.jboss.tools.windup.core.internal.validators.WindupValidator.validate(WindupValidator.java:81)
> at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134)
> at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:68)
> at org.eclipse.wst.validation.ui.internal.ManualValidationRunner.runInWorkspace(ManualValidationRunner.java:83)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
>
> _______________________________________________
> 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/20150327/48bb6fd2/attachment-0001.html
From lincolnbaxter at gmail.com Fri Mar 27 09:51:13 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 27 Mar 2015 09:51:13 -0400
Subject: [windup-dev] previously initiated loading for a different type
with name "org/jboss/forge/furnace/util/Predicate"
In-Reply-To: <2043165694.3578175.1427459715403.JavaMail.zimbra@redhat.com>
References: <1636015576.3558253.1427458728820.JavaMail.zimbra@redhat.com>
<2043165694.3578175.1427459715403.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4H6OS_2BnTAD-53uKyYqfWK9FzTMt3nF1jv6er9pg8omw@mail.gmail.com>
Hey Ian,
I'm taking a look at this now. I'll have more information for you soon.
~Lincoln
On Fri, Mar 27, 2015 at 8:35 AM, Ian Tewksbury <itewk at redhat.com> wrote:
> Lincoln and Jess,
>
>
> I have spent another evening trying to defeat this class loading error
> with no luck.
>
>
> What I have tried:
>
> 1. Debugging CompositeFurnaceClassLoader
> 1. changed #loadClass to #findClass as per ClassLoader suggestion,
> didn't help
> 2. put break point in #findClass to see how many times it is called
> for org.jboss.forge.furnace.util.Predicate, it is only being called once,
> and on that one call it is failing with the LinkageError, this makes 0
> sense to me since the error says that it has already been loaded
> 3. Tried various combinations of checking to see if the class has
> already been loaded, no luck
> 4. Tried creating a cache of already loaded classes, didn't help,
> which makes sense because the #findClass method (or #loadClass if you dont
> use my change) only gets called once for this class.
> 2. I have updated the windup-eclipse plugin to use the latest furnace
> version, 2.15.2.Final, didn't make a difference
> 3. I have updated the windup-eclipse plugin to use the latest Windup
> 2.2.0 Release, plus my changes to add default constructor to WindupService
> and FileService
> 4. I have stopped using my custom loadType function I was talking
> about earlier, that was a red hearing I believe
> 5. I have spent hours googling this error message with no solution
> path to be fund
>
> At this point I am totally blocked. I don't know what to try next.
>
> My latest code is here:
>
> plugin - https://github.com/windup/windup-eclipse-plugin/tree/windup2
> windup - https://github.com/itewk/windup/tree/windup-eclipse
> * as a reminder you can't use SNAPSHOT versions for WINDUP when
> compiling the windup eclipse plugin with local changes to Windup because it
> will always pull the snapshot from the remote repository and ignore your
> local changes, unless using releases in which case maven looks at the local
> repo first
>
> Has anyone been able to try and reproduce this themselves yet?
> Has anyone been able to look over my WindupServices class to make sure I
> am properly using Forge/Furnace to access Windup?
>
> I am either doing something really dumb on my end when trying to access
> Windup or there is a bug/logic error with the CompositeFurnaceClassLoader.
>
>
> Blue Skies,
>
> ~Ian
>
>
> !ENTRY org.eclipse.core.jobs 4 2 2015-03-27 08:04:51.234
> !MESSAGE An internal error occurred during: "Validating".
> !STACK 0
> java.lang.LinkageError: loader constraint violation: loader (instance of
> org/jboss/tools/forge/core/internal/furnace/CompositeFurnaceClassLoader)
> previously initiated loading for a different type with name
> "org/jboss/forge/furnace/util/Predicate"
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2615)
> at java.lang.Class.getDeclaredMethods(Class.java:1860)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.findMethod2(RuntimeSupport.java:134)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.findMethod(RuntimeSupport.java:65)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.find2Methods(RuntimeSupport.java:53)
> at
> org.jboss.windup.exec.configuration.WindupConfiguration_$$_javassist_bdf99157-4ab9-4bb9-a9ec-03565e9d16d6.<clinit>(WindupConfiguration_$$_javassist_bdf99157-4ab9-4bb9-a9ec-03565e9d16d6.java)
> at sun.misc.Unsafe.ensureClassInitialized(Native Method)
> at
> sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:43)
> at
> sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:140)
> at java.lang.reflect.Field.acquireFieldAccessor(Field.java:1057)
> at java.lang.reflect.Field.getFieldAccessor(Field.java:1038)
> at java.lang.reflect.Field.set(Field.java:741)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.setField(ProxyFactory.java:525)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass3(ProxyFactory.java:508)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass2(ProxyFactory.java:492)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass1(ProxyFactory.java:428)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:400)
> 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:253)
> 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.forge.furnace.services.Imported_$$_javassist_48ac554d-8d60-4d09-8f17-c0a42f2c85b7.get(Imported_$$_javassist_48ac554d-8d60-4d09-8f17-c0a42f2c85b7.java)
> at
> org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:96)
> at
> org.jboss.tools.windup.core.WindupService.getServiceFromFurnace(WindupService.java:485)
> at
> org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:226)
> at
> org.jboss.tools.windup.core.WindupService.getGraph(WindupService.java:301)
> at
> org.jboss.tools.windup.core.WindupService.getInlineHints(WindupService.java:103)
> at
> org.jboss.tools.windup.core.internal.validators.WindupValidator.validate(WindupValidator.java:81)
> at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
> at
> org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at
> org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at
> org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
> at
> org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at
> org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134)
> at
> org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:68)
> at
> org.eclipse.wst.validation.ui.internal.ManualValidationRunner.runInWorkspace(ManualValidationRunner.java:83)
> at
> org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
>
> _______________________________________________
> 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/20150327/77ac9abe/attachment.html
From robb.greathouse at redhat.com Fri Mar 27 10:06:53 2015
From: robb.greathouse at redhat.com (Robb Greathouse)
Date: Fri, 27 Mar 2015 10:06:53 -0400 (EDT)
Subject: [windup-dev] Windup 2.2.0.Final Released
In-Reply-To: <CAEp_U4H9NYdg2KPTTD2Da0E7acawwL=WXwA9E2R+vXanEY0HEA@mail.gmail.com>
References: <CAEp_U4H9NYdg2KPTTD2Da0E7acawwL=WXwA9E2R+vXanEY0HEA@mail.gmail.com>
Message-ID: <1836170192.4389982.1427465213692.JavaMail.zimbra@redhat.com>
Congrats.
When it starts up it says that it is 2.0.0-beta 7,
JBoss Windup, version [ 2.0.0.Beta7 ] - JBoss, by Red Hat, Inc. [ http://windup.jboss.org ]
Is that appropriate?
Robb Greathouse
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
----- Original Message -----
> I am proud to announce the release of Windup 2.2.0.Final, which includes the
> following features/enhanvements/and bugfixes.
> Great job team!
> ~Lincoln
> Bug
> * [ WINDUP-510 ] - Build fails with BOM missing
> * [ WINDUP-511 ] - Quickstarts tests fail with a NPE
> * [ WINDUP-516 ] - [Performance] Multiple valueStores even if the rule does
> not use parameters
> * [ WINDUP-517 ] - Application Index page lacks technology list and effort
> information
> * [ WINDUP-518 ] - XML Handlers do not support nested rules
> * [ WINDUP-524 ] - Fix the cyclic dependency between windup and
> windup-rulesets
> * [ WINDUP-542 ] - Fix severe regression in AST performance
> * [ WINDUP-544 ] - StackOverflowException when generating Application report
> Enhancement
> * [ WINDUP-409 ] - Allow rules metadata to be specified with annotations -
> @Rules( phase = ..., ...)
> * [ WINDUP-470 ] - Classes in java.lang package may differ in how they are
> parsed
> * [ WINDUP-506 ] - Identify Archives Ruleset: Improve memory footprint
> * [ WINDUP-508 ] - WindupRuleProvider should contain a location/origin field
> (to indicate where it was defined)
> * [ WINDUP-515 ] - Add Severity to Hint
> * [ WINDUP-520 ] - Rule Externalization - Introduce a Rule, RuleProvider and
> RulesetMetadata API
> * [ WINDUP-529 ] - Performance issue: Query requires iterating over all
> vertices [(ClassificationModel:classification = ...)]
> Feature Request
> * [ WINDUP-402 ] - Change ruleset category metadata to tag-like system (make
> it a set of strings)
> * [ WINDUP-521 ] - Rule Externalization - Create XML Handlers for Rule
> metadata
> * [ WINDUP-522 ] - Rule Externalization - Create user-interface for selecting
> source/target platforms
> * [ WINDUP-523 ] - Rule Externalization - Allow filtering of RuleProviders by
> tags (categories)
> Task
> * [ WINDUP-512 ] - Rename Implicit to Dependent
> * [ WINDUP-513 ] - Phase pseudo-RuleProviders to have ~Phase suffix
> * [ WINDUP-530 ] - Rename the module "utils" to "windup-utils"
> Sub-task
> * [ WINDUP-464 ] - Expand all addons with simple layout to use full
> api/impl/tests structure
> * [ WINDUP-465 ] - Review all rules, organize into an external repository,
> and add useful hint information with links to knowledge articles
> --
> 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/20150327/2ab3e20c/attachment-0001.html
From lincolnbaxter at gmail.com Fri Mar 27 10:07:51 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 27 Mar 2015 10:07:51 -0400
Subject: [windup-dev] Windup 2.2.0.Final Released
In-Reply-To: <1836170192.4389982.1427465213692.JavaMail.zimbra@redhat.com>
References: <CAEp_U4H9NYdg2KPTTD2Da0E7acawwL=WXwA9E2R+vXanEY0HEA@mail.gmail.com>
<1836170192.4389982.1427465213692.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4Enm5Dzx672shvY_Bi6X4p9PSAR2Hjs8BqneZ72xuA-=g@mail.gmail.com>
I think you are using an outdated version of Windup. Run "which windup" and
see where the old version is, and replace it with the new version.
On Fri, Mar 27, 2015 at 10:06 AM, Robb Greathouse <
robb.greathouse at redhat.com> wrote:
> Congrats.
>
> When it starts up it says that it is 2.0.0-beta 7,
>
> JBoss Windup, version [ 2.0.0.Beta7 ] - JBoss, by Red Hat, Inc. [
> http://windup.jboss.org ]
>
>
> Is that appropriate?
>
>
> Robb Greathouse
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
>
> ------------------------------
>
> I am proud to announce the release of Windup 2.2.0.Final, which includes
> the following features/enhanvements/and bugfixes.
> Great job team!
>
> ~Lincoln
> Bug
>
> - [WINDUP-510 <https://issues.jboss.org/browse/WINDUP-510>] - Build
> fails with BOM missing
> - [WINDUP-511 <https://issues.jboss.org/browse/WINDUP-511>] -
> Quickstarts tests fail with a NPE
> - [WINDUP-516 <https://issues.jboss.org/browse/WINDUP-516>] -
> [Performance] Multiple valueStores even if the rule does not use parameters
> - [WINDUP-517 <https://issues.jboss.org/browse/WINDUP-517>] -
> Application Index page lacks technology list and effort information
> - [WINDUP-518 <https://issues.jboss.org/browse/WINDUP-518>] - XML
> Handlers do not support nested rules
> - [WINDUP-524 <https://issues.jboss.org/browse/WINDUP-524>] - Fix the
> cyclic dependency between windup and windup-rulesets
> - [WINDUP-542 <https://issues.jboss.org/browse/WINDUP-542>] - Fix
> severe regression in AST performance
> - [WINDUP-544 <https://issues.jboss.org/browse/WINDUP-544>] -
> StackOverflowException when generating Application report
>
> Enhancement
>
> - [WINDUP-409 <https://issues.jboss.org/browse/WINDUP-409>] - Allow
> rules metadata to be specified with annotations - @Rules( phase = ..., ...)
> - [WINDUP-470 <https://issues.jboss.org/browse/WINDUP-470>] - Classes
> in java.lang package may differ in how they are parsed
> - [WINDUP-506 <https://issues.jboss.org/browse/WINDUP-506>] - Identify
> Archives Ruleset: Improve memory footprint
> - [WINDUP-508 <https://issues.jboss.org/browse/WINDUP-508>] -
> WindupRuleProvider should contain a location/origin field (to indicate
> where it was defined)
> - [WINDUP-515 <https://issues.jboss.org/browse/WINDUP-515>] - Add
> Severity to Hint
> - [WINDUP-520 <https://issues.jboss.org/browse/WINDUP-520>] - Rule
> Externalization - Introduce a Rule, RuleProvider and RulesetMetadata API
> - [WINDUP-529 <https://issues.jboss.org/browse/WINDUP-529>] -
> Performance issue: Query requires iterating over all vertices
> [(ClassificationModel:classification = ...)]
>
> Feature Request
>
> - [WINDUP-402 <https://issues.jboss.org/browse/WINDUP-402>] - Change
> ruleset category metadata to tag-like system (make it a set of strings)
> - [WINDUP-521 <https://issues.jboss.org/browse/WINDUP-521>] - Rule
> Externalization - Create XML Handlers for Rule metadata
> - [WINDUP-522 <https://issues.jboss.org/browse/WINDUP-522>] - Rule
> Externalization - Create user-interface for selecting source/target
> platforms
> - [WINDUP-523 <https://issues.jboss.org/browse/WINDUP-523>] - Rule
> Externalization - Allow filtering of RuleProviders by tags (categories)
>
> Task
>
> - [WINDUP-512 <https://issues.jboss.org/browse/WINDUP-512>] - Rename
> Implicit to Dependent
> - [WINDUP-513 <https://issues.jboss.org/browse/WINDUP-513>] - Phase
> pseudo-RuleProviders to have ~Phase suffix
> - [WINDUP-530 <https://issues.jboss.org/browse/WINDUP-530>] - Rename
> the module "utils" to "windup-utils"
>
> Sub-task
>
> - [WINDUP-464 <https://issues.jboss.org/browse/WINDUP-464>] - Expand
> all addons with simple layout to use full api/impl/tests structure
> - [WINDUP-465 <https://issues.jboss.org/browse/WINDUP-465>] - Review
> all rules, organize into an external repository, and add useful hint
> information with links to knowledge articles
>
>
> --
> 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/20150327/53f23f0b/attachment.html
From sgilda at redhat.com Fri Mar 27 10:23:18 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Fri, 27 Mar 2015 10:23:18 -0400
Subject: [windup-dev] Windup 2.2.0.Final Released
In-Reply-To: <CAEp_U4Enm5Dzx672shvY_Bi6X4p9PSAR2Hjs8BqneZ72xuA-=g@mail.gmail.com>
References: <CAEp_U4H9NYdg2KPTTD2Da0E7acawwL=WXwA9E2R+vXanEY0HEA@mail.gmail.com> <1836170192.4389982.1427465213692.JavaMail.zimbra@redhat.com>
<CAEp_U4Enm5Dzx672shvY_Bi6X4p9PSAR2Hjs8BqneZ72xuA-=g@mail.gmail.com>
Message-ID: <551567D6.30306@redhat.com>
I see: JBoss Windup, version [ 2.2.0.Final ]
On 03/27/2015 10:07 AM, Lincoln Baxter, III wrote:
> I think you are using an outdated version of Windup. Run "which
> windup" and see where the old version is, and replace it with the new
> version.
>
> On Fri, Mar 27, 2015 at 10:06 AM, Robb Greathouse
> <robb.greathouse at redhat.com <mailto:robb.greathouse at redhat.com>> wrote:
>
> Congrats.
>
> When it starts up it says that it is 2.0.0-beta 7,
>
> JBoss Windup, version [ 2.0.0.Beta7 ] - JBoss, by Red Hat, Inc. [
> http://windup.jboss.org ]
>
>
> Is that appropriate?
>
>
>
> Robb Greathouse
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906 <tel:505-507-4906>
>
> ------------------------------------------------------------------------
>
>
> I am proud to announce the release of Windup 2.2.0.Final,
> which includes the following features/enhanvements/and
> bugfixes.
>
> Great job team!
>
> ~Lincoln
>
>
> Bug
>
> * [WINDUP-510 <https://issues.jboss.org/browse/WINDUP-510>]
> - Build fails with BOM missing
> * [WINDUP-511 <https://issues.jboss.org/browse/WINDUP-511>]
> - Quickstarts tests fail with a NPE
> * [WINDUP-516 <https://issues.jboss.org/browse/WINDUP-516>]
> - [Performance] Multiple valueStores even if the rule does
> not use parameters
> * [WINDUP-517 <https://issues.jboss.org/browse/WINDUP-517>]
> - Application Index page lacks technology list and effort
> information
> * [WINDUP-518 <https://issues.jboss.org/browse/WINDUP-518>]
> - XML Handlers do not support nested rules
> * [WINDUP-524 <https://issues.jboss.org/browse/WINDUP-524>]
> - Fix the cyclic dependency between windup and windup-rulesets
> * [WINDUP-542 <https://issues.jboss.org/browse/WINDUP-542>]
> - Fix severe regression in AST performance
> * [WINDUP-544 <https://issues.jboss.org/browse/WINDUP-544>]
> - StackOverflowException when generating Application report
>
>
> Enhancement
>
> * [WINDUP-409 <https://issues.jboss.org/browse/WINDUP-409>]
> - Allow rules metadata to be specified with annotations -
> @Rules( phase = ..., ...)
> * [WINDUP-470 <https://issues.jboss.org/browse/WINDUP-470>]
> - Classes in java.lang package may differ in how they are
> parsed
> * [WINDUP-506 <https://issues.jboss.org/browse/WINDUP-506>]
> - Identify Archives Ruleset: Improve memory footprint
> * [WINDUP-508 <https://issues.jboss.org/browse/WINDUP-508>]
> - WindupRuleProvider should contain a location/origin
> field (to indicate where it was defined)
> * [WINDUP-515 <https://issues.jboss.org/browse/WINDUP-515>]
> - Add Severity to Hint
> * [WINDUP-520 <https://issues.jboss.org/browse/WINDUP-520>]
> - Rule Externalization - Introduce a Rule, RuleProvider
> and RulesetMetadata API
> * [WINDUP-529 <https://issues.jboss.org/browse/WINDUP-529>]
> - Performance issue: Query requires iterating over all
> vertices [(ClassificationModel:classification = ...)]
>
>
> Feature Request
>
> * [WINDUP-402 <https://issues.jboss.org/browse/WINDUP-402>]
> - Change ruleset category metadata to tag-like system
> (make it a set of strings)
> * [WINDUP-521 <https://issues.jboss.org/browse/WINDUP-521>]
> - Rule Externalization - Create XML Handlers for Rule metadata
> * [WINDUP-522 <https://issues.jboss.org/browse/WINDUP-522>]
> - Rule Externalization - Create user-interface for
> selecting source/target platforms
> * [WINDUP-523 <https://issues.jboss.org/browse/WINDUP-523>]
> - Rule Externalization - Allow filtering of RuleProviders
> by tags (categories)
>
>
> Task
>
> * [WINDUP-512 <https://issues.jboss.org/browse/WINDUP-512>]
> - Rename Implicit to Dependent
> * [WINDUP-513 <https://issues.jboss.org/browse/WINDUP-513>]
> - Phase pseudo-RuleProviders to have ~Phase suffix
> * [WINDUP-530 <https://issues.jboss.org/browse/WINDUP-530>]
> - Rename the module "utils" to "windup-utils"
>
>
> Sub-task
>
> * [WINDUP-464 <https://issues.jboss.org/browse/WINDUP-464>]
> - Expand all addons with simple layout to use full
> api/impl/tests structure
> * [WINDUP-465 <https://issues.jboss.org/browse/WINDUP-465>]
> - Review all rules, organize into an external repository,
> and add useful hint information with links to knowledge
> articles
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
>
>
>
> --
> 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/20150327/c7ec0738/attachment-0001.html
From lincolnbaxter at gmail.com Fri Mar 27 12:13:03 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 27 Mar 2015 12:13:03 -0400
Subject: [windup-dev] Furnace not finding Windup FileService
In-Reply-To: <1962890038.2398764.1427301196084.JavaMail.zimbra@redhat.com>
References: <662321974.765317.1427014663076.JavaMail.zimbra@redhat.com>
<806195538.767666.1427015935764.JavaMail.zimbra@redhat.com>
<2124536037.894108.1427068168764.JavaMail.zimbra@redhat.com>
<848601461.917867.1427075856080.JavaMail.zimbra@redhat.com>
<1671296303.1439386.1427120589263.JavaMail.zimbra@redhat.com>
<1962890038.2398764.1427301196084.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4Fqnsz860XjFXhBkayw9zR3_x_yjS9wJodzyRb9Nsaaag@mail.gmail.com>
Ah, well one issue is that the "*ModelServices" like FileService are not
actually Furnace services.. That's unfortunate... Do you need access to the
FileService?
On Wed, Mar 25, 2015 at 12:33 PM, Ian Tewksbury <itewk at redhat.com> wrote:
> Lincoln,
>
> Sorry. I just saw this. My email filters took over when you added the
> windup mailing list and it got filtered out of my main inbox.
>
> The Furnace method I added was:
>
> public <S> S lookupType(Class<S> service) {
> S instance = null;
> if (furnace != null) {
> Set<Class<S>> types = null;
> types = furnace.getAddonRegistry().getExportedTypes(service);
>
> if (types != null && !types.isEmpty()) {
> for(Class<S> type : types) {
> try {
> instance = type.newInstance();
> break;
> } catch (Exception e) {
> e.getMessage();
> //skip to next instance if this one did not work
> }
> }
> }
> }
>
> return instance;
> }
>
> My issue was with loading "FileService.class". Calling "lookup" could not
> find it, but calling my new "lookupType" it could find it.
>
> Blue Skies,
> ~Ian
>
> ------------------------------
> *From: *"Lincoln Baxter, III" <lincoln at redhat.com>
> *To: *"Ian Tewksbury" <itewk at redhat.com>
> *Cc: *"Robb Greathouse" <robb.greathouse at redhat.com>, "George Gastaldi" <
> ggastald at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>
> *Sent: *Monday, March 23, 2015 10:23:09 AM
>
> *Subject: *Re: Furnace not finding Windup FileService
>
> Hey Ian,
>
> (Adding windup-dev.)
>
> I'm not really sure what this issue could be, but it worries me that you
> needed to add a method to FurnaceService. What did you add? You can't ask
> Furnace for an instance of a type that is not a Service. (It wouldn't know
> how to construct it.)
>
> The last error you received worries me specifically because it makes me
> think that there is something funky going on with the ClassLoader hierarchy
> itself, and that is never good; however, it could be due to some kind of
> quirk with what you added (it also may be a bug), so I think I need to see
> what you are doing.
>
> Could you show me where this code is so that I can take a look?
>
> Thanks!
> ~Lincoln
>
> ------------------------------
> *From: *"Ian Tewksbury" <itewk at redhat.com>
> *To: *"Lincoln Baxter" <lbaxter at redhat.com>
> *Cc: *"Robb Greathouse" <robb.greathouse at redhat.com>
> *Sent: *Sunday, March 22, 2015 9:57:36 PM
> *Subject: *Re: Furnace not finding Windup FileService
>
> Licoln,
>
> Got passed those previous errors. New error now:
>
> !ENTRY org.eclipse.core.jobs 4 2 2015-03-22 21:52:59.403
> !MESSAGE An internal error occurred during: "Validating".
> !STACK 0
> java.lang.LinkageError: loader constraint violation: loader (instance of
> org/jboss/tools/forge/core/internal/furnace/CompositeFurnaceClassLoader)
> previously initiated loading for a different type with name
> "org/jboss/forge/furnace/util/Predicate"
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2615)
> at java.lang.Class.getDeclaredMethods(Class.java:1860)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.findMethod2(RuntimeSupport.java:134)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.findMethod(RuntimeSupport.java:65)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.find2Methods(RuntimeSupport.java:53)
> at
> org.jboss.windup.exec.configuration.WindupConfiguration_$$_javassist_5effd6de-6f27-4c9d-9f94-b9492b06844c.<clinit>(WindupConfiguration_$$_javassist_5effd6de-6f27-4c9d-9f94-b9492b06844c.java)
> at sun.misc.Unsafe.ensureClassInitialized(Native Method)
> at
> sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:43)
> at
> sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:140)
> at java.lang.reflect.Field.acquireFieldAccessor(Field.java:1057)
> at java.lang.reflect.Field.getFieldAccessor(Field.java:1038)
> at java.lang.reflect.Field.set(Field.java:741)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.setField(ProxyFactory.java:525)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass3(ProxyFactory.java:508)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass2(ProxyFactory.java:492)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass1(ProxyFactory.java:428)
> at
> org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:400)
> 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:253)
> 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.forge.furnace.services.Imported_$$_javassist_34707ba1-98fb-4b8a-93ed-559398be971b.get(Imported_$$_javassist_34707ba1-98fb-4b8a-93ed-559398be971b.java)
> at
> org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:96)
> at
> org.jboss.tools.windup.core.WindupService.getServiceFromFurnace(WindupService.java:485)
> at
> org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:226)
> at
> org.jboss.tools.windup.core.WindupService.getGraph(WindupService.java:301)
> at
> org.jboss.tools.windup.core.WindupService.getInlineHints(WindupService.java:103)
> at
> org.jboss.tools.windup.core.internal.validators.WindupValidator.validate(WindupValidator.java:81)
> at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
> at
> org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at
> org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at
> org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
> at
> org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at
> org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134)
> at
> org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:68)
> at
> org.eclipse.wst.validation.ui.internal.ManualValidationRunner.runInWorkspace(ManualValidationRunner.java:83)
> at
> org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
>
>
>
> Blue Skies,
> ~Ian
>
> ------------------------------
> *From: *"Ian Tewksbury" <itewk at redhat.com>
> *To: *"Lincoln Baxter" <lbaxter at redhat.com>
> *Cc: *"Robb Greathouse" <robb.greathouse at redhat.com>
> *Sent: *Sunday, March 22, 2015 7:49:28 PM
> *Subject: *Re: Furnace not finding Windup FileService
>
> Licncoln,
>
> I added some new API to the FurnaceService to be able to lookup a type
> which got me passed the below errors.
>
> Now I am running into:
>
> java.lang.NoClassDefFoundError: com/tinkerpop/frames/FramedGraph
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2615)
> at java.lang.Class.getDeclaredMethods(Class.java:1860)
> 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:1096)
> 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.graph.GraphContextFactory_$$_javassist_2a504b60-d6e3-450e-87b5-f41eb849ab81.create(GraphContextFactory_$$_javassist_2a504b60-d6e3-450e-87b5-f41eb849ab81.java)
> at
> org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:235)
> at
> org.jboss.tools.windup.core.WindupService.getGraph(WindupService.java:303)
> at
> org.jboss.tools.windup.core.WindupService.getInlineHints(WindupService.java:103)
> at
> org.jboss.tools.windup.core.internal.validators.WindupValidator.validate(WindupValidator.java:81)
> at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
> at
> org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at
> org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at
> org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
> at
> org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at
> org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134)
>
> at
> org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:68)
> at
> org.eclipse.wst.validation.ui.internal.ManualValidationRunner.runInWorkspace(ManualValidationRunner.java:83)
> at
> org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.lang.ClassNotFoundException:
> com.tinkerpop.frames.FramedGraph 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)
> ... 32 more
>
>
> I have verified that the Furnace add on
> 'org-jboss-windup-graph-windup-graph' is being loaded and contains the
> windup-frames JAR so I am not clear why furnace is not able to load the
> class.
>
>
> Ideas?
>
>
> Blue Skies,
>
> ~Ian
>
> ------------------------------
> *From: *"Ian Tewksbury" <itewk at redhat.com>
> *To: *"Lincoln Baxter" <lbaxter at redhat.com>
> *Cc: *"Robb Greathouse" <robb.greathouse at redhat.com>
> *Sent: *Sunday, March 22, 2015 5:18:55 AM
> *Subject: *Re: Furnace not finding Windup FileService
>
> Lioncoln,
>
> Looking here,
> http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/releases/org.jboss.forge.furnace.container/cdi-impl/2.10.1.Final/org/jboss/forge/furnace/container/cdi/impl/WeldServiceRegistry.java#WeldServiceRegistry.getExportedInstances%28java.lang.Class%29, and
> debuging through eclipse without source, I have figured out it is choking
> on like 189. It appears this #getExportedInstances method is only for
> loading beans. I see a #getExportedType which is what I am guessing I need,
> but the only Furnace API I see is FurnaceService.INSTANCE.lookup(clazz)
> which ends up doing this bean lookup rather then a type lookup. Am I
> missing something here? Is there just missing API to look up a type and not
> a bean via Furnace?
>
> Blue Skies,
> ~Ian
>
> ------------------------------
> *From: *"Ian Tewksbury" <itewk at redhat.com>
> *To: *"Lincoln Baxter" <lbaxter at redhat.com>, "Robb Greathouse" <
> robb.greathouse at redhat.com>
> *Sent: *Sunday, March 22, 2015 4:57:43 AM
> *Subject: *Furnace not finding Windup FileService
>
> Lincoln,
>
> I can not figure out why Furnance is reporting that it can not find the
> Windup FileService despite the fact that it is reporting it loaded the
> graph-api addon. Any ideas?
>
> Please see attached for the log. It clearly shows the graph-api addon
> being loaded. And I have verified that addon contains the graph-api.jar
> which contains the FileService. I have tried to debug the furnace stuff but
> I keep running into source not found issues and getting lost. I have been
> able to tell that ImportedImpl#getExportedInstances is getting called and
> it is looping over the graph-api addon. But it does not seem to find the
> class in there, but I have not been able to debug into furnace beyond that
> point.
>
> Looking at the variable state the WeldServiceRegistery instance for the
> graph-api addon shows the FIleService there. For some reason it is just not
> being retrevied. I have attached a screenshoot of the variable state from
> within ImportedImpl#getExportedInstances. Can you think of any
> reason serviceRegistry.getExportedInstances(type) would be failing giving
> all of this?
>
>
> ~Ian
>
>
>
>
>
>
> _______________________________________________
> 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/20150327/7df1c367/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: windup.png
Type: image/png
Size: 172297 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150327/7df1c367/attachment-0001.png
From robb.greathouse at redhat.com Fri Mar 27 14:48:42 2015
From: robb.greathouse at redhat.com (Robb Greathouse)
Date: Fri, 27 Mar 2015 14:48:42 -0400 (EDT)
Subject: [windup-dev] Windup 2.2.0.Final Released
In-Reply-To: <CAEp_U4H9NYdg2KPTTD2Da0E7acawwL=WXwA9E2R+vXanEY0HEA@mail.gmail.com>
References: <CAEp_U4H9NYdg2KPTTD2Da0E7acawwL=WXwA9E2R+vXanEY0HEA@mail.gmail.com>
Message-ID: <1176810837.4605771.1427482122124.JavaMail.zimbra@redhat.com>
Cudos.
Running against the 300~mb test file and restricting it to look at packages com.clarify it runs in about 40 minutes vs the old time of 20 hours plus. Definite performance improvement.
Robb Greathouse
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
----- Original Message -----
> I am proud to announce the release of Windup 2.2.0.Final, which includes the
> following features/enhanvements/and bugfixes.
> Great job team!
> ~Lincoln
> Bug
> * [ WINDUP-510 ] - Build fails with BOM missing
> * [ WINDUP-511 ] - Quickstarts tests fail with a NPE
> * [ WINDUP-516 ] - [Performance] Multiple valueStores even if the rule does
> not use parameters
> * [ WINDUP-517 ] - Application Index page lacks technology list and effort
> information
> * [ WINDUP-518 ] - XML Handlers do not support nested rules
> * [ WINDUP-524 ] - Fix the cyclic dependency between windup and
> windup-rulesets
> * [ WINDUP-542 ] - Fix severe regression in AST performance
> * [ WINDUP-544 ] - StackOverflowException when generating Application report
> Enhancement
> * [ WINDUP-409 ] - Allow rules metadata to be specified with annotations -
> @Rules( phase = ..., ...)
> * [ WINDUP-470 ] - Classes in java.lang package may differ in how they are
> parsed
> * [ WINDUP-506 ] - Identify Archives Ruleset: Improve memory footprint
> * [ WINDUP-508 ] - WindupRuleProvider should contain a location/origin field
> (to indicate where it was defined)
> * [ WINDUP-515 ] - Add Severity to Hint
> * [ WINDUP-520 ] - Rule Externalization - Introduce a Rule, RuleProvider and
> RulesetMetadata API
> * [ WINDUP-529 ] - Performance issue: Query requires iterating over all
> vertices [(ClassificationModel:classification = ...)]
> Feature Request
> * [ WINDUP-402 ] - Change ruleset category metadata to tag-like system (make
> it a set of strings)
> * [ WINDUP-521 ] - Rule Externalization - Create XML Handlers for Rule
> metadata
> * [ WINDUP-522 ] - Rule Externalization - Create user-interface for selecting
> source/target platforms
> * [ WINDUP-523 ] - Rule Externalization - Allow filtering of RuleProviders by
> tags (categories)
> Task
> * [ WINDUP-512 ] - Rename Implicit to Dependent
> * [ WINDUP-513 ] - Phase pseudo-RuleProviders to have ~Phase suffix
> * [ WINDUP-530 ] - Rename the module "utils" to "windup-utils"
> Sub-task
> * [ WINDUP-464 ] - Expand all addons with simple layout to use full
> api/impl/tests structure
> * [ WINDUP-465 ] - Review all rules, organize into an external repository,
> and add useful hint information with links to knowledge articles
> --
> 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/20150327/5482a063/attachment.html
From lincolnbaxter at gmail.com Fri Mar 27 15:56:38 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 27 Mar 2015 15:56:38 -0400
Subject: [windup-dev] Windup 2.2.0.Final Released
In-Reply-To: <1176810837.4605771.1427482122124.JavaMail.zimbra@redhat.com>
References: <CAEp_U4H9NYdg2KPTTD2Da0E7acawwL=WXwA9E2R+vXanEY0HEA@mail.gmail.com>
<1176810837.4605771.1427482122124.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4G0J018PXH8UcMgv6DyhTXy0t=ZxG7XDABuFhwiqWh7+g@mail.gmail.com>
Great! Thank you for confirming this! We definitely wanted to get these
improvements into this release, so thank you for your patience as we sorted
out some of the issues!
~Lincoln
On Fri, Mar 27, 2015 at 2:48 PM, Robb Greathouse <robb.greathouse at redhat.com
> wrote:
> Cudos.
>
> Running against the 300~mb test file and restricting it to look at
> packages com.clarify it runs in about 40 minutes vs the old time of 20
> hours plus. Definite performance improvement.
>
>
>
> Robb Greathouse
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
>
> ------------------------------
>
> I am proud to announce the release of Windup 2.2.0.Final, which includes
> the following features/enhanvements/and bugfixes.
> Great job team!
>
> ~Lincoln
> Bug
>
> - [WINDUP-510 <https://issues.jboss.org/browse/WINDUP-510>] - Build
> fails with BOM missing
> - [WINDUP-511 <https://issues.jboss.org/browse/WINDUP-511>] -
> Quickstarts tests fail with a NPE
> - [WINDUP-516 <https://issues.jboss.org/browse/WINDUP-516>] -
> [Performance] Multiple valueStores even if the rule does not use parameters
> - [WINDUP-517 <https://issues.jboss.org/browse/WINDUP-517>] -
> Application Index page lacks technology list and effort information
> - [WINDUP-518 <https://issues.jboss.org/browse/WINDUP-518>] - XML
> Handlers do not support nested rules
> - [WINDUP-524 <https://issues.jboss.org/browse/WINDUP-524>] - Fix the
> cyclic dependency between windup and windup-rulesets
> - [WINDUP-542 <https://issues.jboss.org/browse/WINDUP-542>] - Fix
> severe regression in AST performance
> - [WINDUP-544 <https://issues.jboss.org/browse/WINDUP-544>] -
> StackOverflowException when generating Application report
>
> Enhancement
>
> - [WINDUP-409 <https://issues.jboss.org/browse/WINDUP-409>] - Allow
> rules metadata to be specified with annotations - @Rules( phase = ..., ...)
> - [WINDUP-470 <https://issues.jboss.org/browse/WINDUP-470>] - Classes
> in java.lang package may differ in how they are parsed
> - [WINDUP-506 <https://issues.jboss.org/browse/WINDUP-506>] - Identify
> Archives Ruleset: Improve memory footprint
> - [WINDUP-508 <https://issues.jboss.org/browse/WINDUP-508>] -
> WindupRuleProvider should contain a location/origin field (to indicate
> where it was defined)
> - [WINDUP-515 <https://issues.jboss.org/browse/WINDUP-515>] - Add
> Severity to Hint
> - [WINDUP-520 <https://issues.jboss.org/browse/WINDUP-520>] - Rule
> Externalization - Introduce a Rule, RuleProvider and RulesetMetadata API
> - [WINDUP-529 <https://issues.jboss.org/browse/WINDUP-529>] -
> Performance issue: Query requires iterating over all vertices
> [(ClassificationModel:classification = ...)]
>
> Feature Request
>
> - [WINDUP-402 <https://issues.jboss.org/browse/WINDUP-402>] - Change
> ruleset category metadata to tag-like system (make it a set of strings)
> - [WINDUP-521 <https://issues.jboss.org/browse/WINDUP-521>] - Rule
> Externalization - Create XML Handlers for Rule metadata
> - [WINDUP-522 <https://issues.jboss.org/browse/WINDUP-522>] - Rule
> Externalization - Create user-interface for selecting source/target
> platforms
> - [WINDUP-523 <https://issues.jboss.org/browse/WINDUP-523>] - Rule
> Externalization - Allow filtering of RuleProviders by tags (categories)
>
> Task
>
> - [WINDUP-512 <https://issues.jboss.org/browse/WINDUP-512>] - Rename
> Implicit to Dependent
> - [WINDUP-513 <https://issues.jboss.org/browse/WINDUP-513>] - Phase
> pseudo-RuleProviders to have ~Phase suffix
> - [WINDUP-530 <https://issues.jboss.org/browse/WINDUP-530>] - Rename
> the module "utils" to "windup-utils"
>
> Sub-task
>
> - [WINDUP-464 <https://issues.jboss.org/browse/WINDUP-464>] - Expand
> all addons with simple layout to use full api/impl/tests structure
> - [WINDUP-465 <https://issues.jboss.org/browse/WINDUP-465>] - Review
> all rules, organize into an external repository, and add useful hint
> information with links to knowledge articles
>
>
> --
> 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/20150327/db9deb79/attachment-0001.html
From sgilda at redhat.com Fri Mar 27 16:02:00 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Fri, 27 Mar 2015 16:02:00 -0400
Subject: [windup-dev] Windup 2.2.0.Final Released
In-Reply-To: <CAEp_U4G0J018PXH8UcMgv6DyhTXy0t=ZxG7XDABuFhwiqWh7+g@mail.gmail.com>
References: <CAEp_U4H9NYdg2KPTTD2Da0E7acawwL=WXwA9E2R+vXanEY0HEA@mail.gmail.com> <1176810837.4605771.1427482122124.JavaMail.zimbra@redhat.com>
<CAEp_U4G0J018PXH8UcMgv6DyhTXy0t=ZxG7XDABuFhwiqWh7+g@mail.gmail.com>
Message-ID: <5515B738.4090906@redhat.com>
Wow! That's a huge (30x) improvement! Way to go!
On 03/27/2015 03:56 PM, Lincoln Baxter, III wrote:
> Great! Thank you for confirming this! We definitely wanted to get
> these improvements into this release, so thank you for your patience
> as we sorted out some of the issues!
>
> ~Lincoln
>
> On Fri, Mar 27, 2015 at 2:48 PM, Robb Greathouse
> <robb.greathouse at redhat.com <mailto:robb.greathouse at redhat.com>> wrote:
>
> Cudos.
>
> Running against the 300~mb test file and restricting it to look at
> packages com.clarify it runs in about 40 minutes vs the old time
> of 20 hours plus. Definite performance improvement.
>
>
>
> Robb Greathouse
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906 <tel:505-507-4906>
>
> ------------------------------------------------------------------------
>
>
> I am proud to announce the release of Windup 2.2.0.Final,
> which includes the following features/enhanvements/and
> bugfixes.
>
> Great job team!
>
> ~Lincoln
>
>
> Bug
>
> * [WINDUP-510 <https://issues.jboss.org/browse/WINDUP-510>]
> - Build fails with BOM missing
> * [WINDUP-511 <https://issues.jboss.org/browse/WINDUP-511>]
> - Quickstarts tests fail with a NPE
> * [WINDUP-516 <https://issues.jboss.org/browse/WINDUP-516>]
> - [Performance] Multiple valueStores even if the rule does
> not use parameters
> * [WINDUP-517 <https://issues.jboss.org/browse/WINDUP-517>]
> - Application Index page lacks technology list and effort
> information
> * [WINDUP-518 <https://issues.jboss.org/browse/WINDUP-518>]
> - XML Handlers do not support nested rules
> * [WINDUP-524 <https://issues.jboss.org/browse/WINDUP-524>]
> - Fix the cyclic dependency between windup and windup-rulesets
> * [WINDUP-542 <https://issues.jboss.org/browse/WINDUP-542>]
> - Fix severe regression in AST performance
> * [WINDUP-544 <https://issues.jboss.org/browse/WINDUP-544>]
> - StackOverflowException when generating Application report
>
>
> Enhancement
>
> * [WINDUP-409 <https://issues.jboss.org/browse/WINDUP-409>]
> - Allow rules metadata to be specified with annotations -
> @Rules( phase = ..., ...)
> * [WINDUP-470 <https://issues.jboss.org/browse/WINDUP-470>]
> - Classes in java.lang package may differ in how they are
> parsed
> * [WINDUP-506 <https://issues.jboss.org/browse/WINDUP-506>]
> - Identify Archives Ruleset: Improve memory footprint
> * [WINDUP-508 <https://issues.jboss.org/browse/WINDUP-508>]
> - WindupRuleProvider should contain a location/origin
> field (to indicate where it was defined)
> * [WINDUP-515 <https://issues.jboss.org/browse/WINDUP-515>]
> - Add Severity to Hint
> * [WINDUP-520 <https://issues.jboss.org/browse/WINDUP-520>]
> - Rule Externalization - Introduce a Rule, RuleProvider
> and RulesetMetadata API
> * [WINDUP-529 <https://issues.jboss.org/browse/WINDUP-529>]
> - Performance issue: Query requires iterating over all
> vertices [(ClassificationModel:classification = ...)]
>
>
> Feature Request
>
> * [WINDUP-402 <https://issues.jboss.org/browse/WINDUP-402>]
> - Change ruleset category metadata to tag-like system
> (make it a set of strings)
> * [WINDUP-521 <https://issues.jboss.org/browse/WINDUP-521>]
> - Rule Externalization - Create XML Handlers for Rule metadata
> * [WINDUP-522 <https://issues.jboss.org/browse/WINDUP-522>]
> - Rule Externalization - Create user-interface for
> selecting source/target platforms
> * [WINDUP-523 <https://issues.jboss.org/browse/WINDUP-523>]
> - Rule Externalization - Allow filtering of RuleProviders
> by tags (categories)
>
>
> Task
>
> * [WINDUP-512 <https://issues.jboss.org/browse/WINDUP-512>]
> - Rename Implicit to Dependent
> * [WINDUP-513 <https://issues.jboss.org/browse/WINDUP-513>]
> - Phase pseudo-RuleProviders to have ~Phase suffix
> * [WINDUP-530 <https://issues.jboss.org/browse/WINDUP-530>]
> - Rename the module "utils" to "windup-utils"
>
>
> Sub-task
>
> * [WINDUP-464 <https://issues.jboss.org/browse/WINDUP-464>]
> - Expand all addons with simple layout to use full
> api/impl/tests structure
> * [WINDUP-465 <https://issues.jboss.org/browse/WINDUP-465>]
> - Review all rules, organize into an external repository,
> and add useful hint information with links to knowledge
> articles
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
>
>
>
> --
> 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/20150327/f06ad186/attachment.html
From lincoln at redhat.com Fri Mar 27 18:21:58 2015
From: lincoln at redhat.com (Lincoln Baxter, III)
Date: Fri, 27 Mar 2015 18:21:58 -0400 (EDT)
Subject: [windup-dev] Furnace not finding Windup FileService
In-Reply-To: <CAEp_U4Fqnsz860XjFXhBkayw9zR3_x_yjS9wJodzyRb9Nsaaag@mail.gmail.com>
References: <662321974.765317.1427014663076.JavaMail.zimbra@redhat.com>
<806195538.767666.1427015935764.JavaMail.zimbra@redhat.com>
<2124536037.894108.1427068168764.JavaMail.zimbra@redhat.com>
<848601461.917867.1427075856080.JavaMail.zimbra@redhat.com>
<1671296303.1439386.1427120589263.JavaMail.zimbra@redhat.com>
<1962890038.2398764.1427301196084.JavaMail.zimbra@redhat.com>
<CAEp_U4Fqnsz860XjFXhBkayw9zR3_x_yjS9wJodzyRb9Nsaaag@mail.gmail.com>
Message-ID: <924206620.5768611.1427494918353.JavaMail.zimbra@redhat.com>
Hey Ian,
I've pushed up some "work" on the Windup Eclipse Plugin. I've simplified the dependencies, updated to Windup 2.2.0.Final, and removed dependencies that I do not believe belong in the OSGi bundles.
https://github.com/windup/windup-eclipse-plugin/tree/windup2-lincoln
Unfortunately I am not an OSGi expert, and I am getting an exception that I'm hoping you can help me with. I need to know why this class is not being exported from the "org.jboss.tools.forge.runtime" bundle, or why it is not being imported where it should be. We don't have this problem with the Forge Eclipse Plugin, so something must be different with our imports/exports. I tried to add this manually in several places, but to no avail. (See trace below message.)
I think that we will have more success if we are in more constant communication about these issues. You can help with the OSGi issues, I can help with the Furnace issues, and the team can help add new APIs that you'll need to do your work.
My recommendation once we get this CNFE resolved (assuming that's the last issue with what's currently in my branch,) is that we begin building specific interfaces for use in the Eclipse plugin and provide them via a Windup service. I also recommend sticking entirely to interfaces where possible. That will make this go a lot more smoothly because Furnace is really best at proxying interfaces across the ClassLoader boundary. Proxying concrete classes is never really safe because you can't always guarantee a sane/proxiable inheritance hierarchy.
What are your thoughts?
~Lincoln
!ENTRY org.eclipse.core.jobs 4 2 2015-03-27 17:45:55.754
!MESSAGE An internal error occurred during: "Generate Windup Report".
!STACK 0
org.jboss.forge.furnace.exception.ContainerException : Failed to create proxy for type [class org.jboss.windup.graph.GraphContextFactoryImpl]
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance( ClassLoaderAdapterCallback.java:1034 )
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceResult( ClassLoaderAdapterCallback.java:253 )
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.forge.furnace.services.Imported_$$_javassist_e21290d9-1468-4bd4-98c1-073a2776670c.get(Imported_$$_javassist_e21290d9-1468-4bd4-98c1-073a2776670c.java)
at org.jboss.tools.forge.core.furnace.FurnaceService.lookup( FurnaceService.java:95 )
at org.jboss.tools.windup.core.WindupService.getServiceFromFurnace( WindupService.java:525 )
at org.jboss.tools.windup.core.WindupService.generateGraph( WindupService.java:241 )
at org.jboss.tools.windup.core.WindupService.generateGraph( WindupService.java:168 )
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.RuntimeException : by java.lang.NoClassDefFoundError: org/jboss/forge/furnace/proxy/javassist/util/proxy/Proxy
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass3( ProxyFactory.java:515 )
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass2( ProxyFactory.java:492 )
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass1( ProxyFactory.java:428 )
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass( ProxyFactory.java:400 )
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 )
... 12 more
Caused by: org.jboss.forge.furnace.proxy.javassist.CannotCompileException : by java.lang.NoClassDefFoundError: org/jboss/forge/furnace/proxy/javassist/util/proxy/Proxy
at org.jboss.forge.furnace.proxy.javassist.util.proxy.FactoryHelper.toClass( FactoryHelper.java:170 )
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass3( ProxyFactory.java:507 )
... 18 more
Caused by: java.lang.NoClassDefFoundError: org/jboss/forge/furnace/proxy/javassist/util/proxy/Proxy
at java.lang.ClassLoader.defineClass1( Native Method )
at java.lang.ClassLoader.defineClass( ClassLoader.java:760 )
at sun.reflect.GeneratedMethodAccessor95.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:43 )
at java.lang.reflect.Method.invoke( Method.java:483 )
at org.jboss.forge.furnace.proxy.javassist.util.proxy.FactoryHelper.toClass2( FactoryHelper.java:182 )
at org.jboss.forge.furnace.proxy.javassist.util.proxy.FactoryHelper.toClass( FactoryHelper.java:164 )
... 19 more
Caused by: java.lang.ClassNotFoundException : org.jboss.forge.furnace.proxy.javassist.util.proxy.Proxy 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:357 )
... 26 more
----- Original Message -----
From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com>
To: "Windup-dev List" <windup-dev at lists.jboss.org>
Cc: "Lincoln Baxter, III" <lincoln at redhat.com>, "George Gastaldi" <ggastald at redhat.com>
Sent: Friday, March 27, 2015 12:13:03 PM
Subject: Re: [windup-dev] Furnace not finding Windup FileService
Ah, well one issue is that the "*ModelServices" like FileService are not actually Furnace services.. That's unfortunate... Do you need access to the FileService?
On Wed, Mar 25, 2015 at 12:33 PM, Ian Tewksbury < itewk at redhat.com > wrote:
Lincoln,
Sorry. I just saw this. My email filters took over when you added the windup mailing list and it got filtered out of my main inbox.
The Furnace method I added was:
public <S> S lookupType(Class<S> service) {
S instance = null;
if (furnace != null) {
Set<Class<S>> types = null;
types = furnace.getAddonRegistry().getExportedTypes(service);
if (types != null && !types.isEmpty()) {
for(Class<S> type : types) {
try {
instance = type.newInstance();
break;
} catch (Exception e) {
e.getMessage();
//skip to next instance if this one did not work
}
}
}
}
return instance;
}
My issue was with loading "FileService.class". Calling "lookup" could not find it, but calling my new "lookupType" it could find it.
Blue Skies,
~Ian
From: "Lincoln Baxter, III" < lincoln at redhat.com >
To: "Ian Tewksbury" < itewk at redhat.com >
Cc: "Robb Greathouse" < robb.greathouse at redhat.com >, "George Gastaldi" < ggastald at redhat.com >, "Windup-dev List" < windup-dev at lists.jboss.org >
Sent: Monday, March 23, 2015 10:23:09 AM
Subject: Re: Furnace not finding Windup FileService
Hey Ian,
(Adding windup-dev.)
I'm not really sure what this issue could be, but it worries me that you needed to add a method to FurnaceService. What did you add? You can't ask Furnace for an instance of a type that is not a Service. (It wouldn't know how to construct it.)
The last error you received worries me specifically because it makes me think that there is something funky going on with the ClassLoader hierarchy itself, and that is never good; however, it could be due to some kind of quirk with what you added (it also may be a bug), so I think I need to see what you are doing.
Could you show me where this code is so that I can take a look?
Thanks!
~Lincoln
From: "Ian Tewksbury" < itewk at redhat.com >
To: "Lincoln Baxter" < lbaxter at redhat.com >
Cc: "Robb Greathouse" < robb.greathouse at redhat.com >
Sent: Sunday, March 22, 2015 9:57:36 PM
Subject: Re: Furnace not finding Windup FileService
Licoln,
Got passed those previous errors. New error now:
!ENTRY org.eclipse.core.jobs 4 2 2015-03-22 21:52:59.403
!MESSAGE An internal error occurred during: "Validating".
!STACK 0
java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/tools/forge/core/internal/furnace/CompositeFurnaceClassLoader) previously initiated loading for a different type with name "org/jboss/forge/furnace/util/Predicate"
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2615)
at java.lang.Class.getDeclaredMethods(Class.java:1860)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.findMethod2(RuntimeSupport.java:134)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.findMethod(RuntimeSupport.java:65)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport.find2Methods(RuntimeSupport.java:53)
at org.jboss.windup.exec.configuration.WindupConfiguration_$$_javassist_5effd6de-6f27-4c9d-9f94-b9492b06844c.<clinit>(WindupConfiguration_$$_javassist_5effd6de-6f27-4c9d-9f94-b9492b06844c.java)
at sun.misc.Unsafe.ensureClassInitialized(Native Method)
at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:43)
at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:140)
at java.lang.reflect.Field.acquireFieldAccessor(Field.java:1057)
at java.lang.reflect.Field.getFieldAccessor(Field.java:1038)
at java.lang.reflect.Field.set(Field.java:741)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.setField(ProxyFactory.java:525)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass3(ProxyFactory.java:508)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass2(ProxyFactory.java:492)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass1(ProxyFactory.java:428)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:400)
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:253)
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.forge.furnace.services.Imported_$$_javassist_34707ba1-98fb-4b8a-93ed-559398be971b.get(Imported_$$_javassist_34707ba1-98fb-4b8a-93ed-559398be971b.java)
at org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:96)
at org.jboss.tools.windup.core.WindupService.getServiceFromFurnace(WindupService.java:485)
at org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:226)
at org.jboss.tools.windup.core.WindupService.getGraph(WindupService.java:301)
at org.jboss.tools.windup.core.WindupService.getInlineHints(WindupService.java:103)
at org.jboss.tools.windup.core.internal.validators.WindupValidator.validate(WindupValidator.java:81)
at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134)
at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:68)
at org.eclipse.wst.validation.ui.internal.ManualValidationRunner.runInWorkspace(ManualValidationRunner.java:83)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Blue Skies,
~Ian
From: "Ian Tewksbury" < itewk at redhat.com >
To: "Lincoln Baxter" < lbaxter at redhat.com >
Cc: "Robb Greathouse" < robb.greathouse at redhat.com >
Sent: Sunday, March 22, 2015 7:49:28 PM
Subject: Re: Furnace not finding Windup FileService
Licncoln,
I added some new API to the FurnaceService to be able to lookup a type which got me passed the below errors.
Now I am running into:
java.lang.NoClassDefFoundError: com/tinkerpop/frames/FramedGraph
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2615)
at java.lang.Class.getDeclaredMethods(Class.java:1860)
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:1096)
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.graph.GraphContextFactory_$$_javassist_2a504b60-d6e3-450e-87b5-f41eb849ab81.create(GraphContextFactory_$$_javassist_2a504b60-d6e3-450e-87b5-f41eb849ab81.java)
at org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:235)
at org.jboss.tools.windup.core.WindupService.getGraph(WindupService.java:303)
at org.jboss.tools.windup.core.WindupService.getInlineHints(WindupService.java:103)
at org.jboss.tools.windup.core.internal.validators.WindupValidator.validate(WindupValidator.java:81)
at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134)
at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:68)
at org.eclipse.wst.validation.ui.internal.ManualValidationRunner.runInWorkspace(ManualValidationRunner.java:83)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.ClassNotFoundException: com.tinkerpop.frames.FramedGraph 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)
... 32 more
I have verified that the Furnace add on 'org-jboss-windup-graph-windup-graph' is being loaded and contains the windup-frames JAR so I am not clear why furnace is not able to load the class.
Ideas?
Blue Skies,
~Ian
From: "Ian Tewksbury" < itewk at redhat.com >
To: "Lincoln Baxter" < lbaxter at redhat.com >
Cc: "Robb Greathouse" < robb.greathouse at redhat.com >
Sent: Sunday, March 22, 2015 5:18:55 AM
Subject: Re: Furnace not finding Windup FileService
Lioncoln,
Looking here, http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/releases/org.jboss.forge.furnace.container/cdi-impl/2.10.1.Final/org/jboss/forge/furnace/container/cdi/impl/WeldServiceRegistry.java#WeldServiceRegistry.getExportedInstances%28java.lang.Class%29 , and debuging through eclipse without source, I have figured out it is choking on like 189. It appears this #getExportedInstances method is only for loading beans. I see a #getExportedType which is what I am guessing I need, but the only Furnace API I see is FurnaceService.INSTANCE.lookup(clazz) which ends up doing this bean lookup rather then a type lookup. Am I missing something here? Is there just missing API to look up a type and not a bean via Furnace?
Blue Skies,
~Ian
From: "Ian Tewksbury" < itewk at redhat.com >
To: "Lincoln Baxter" < lbaxter at redhat.com >, "Robb Greathouse" < robb.greathouse at redhat.com >
Sent: Sunday, March 22, 2015 4:57:43 AM
Subject: Furnace not finding Windup FileService
Lincoln,
I can not figure out why Furnance is reporting that it can not find the Windup FileService despite the fact that it is reporting it loaded the graph-api addon. Any ideas?
Please see attached for the log. It clearly shows the graph-api addon being loaded. And I have verified that addon contains the graph-api.jar which contains the FileService. I have tried to debug the furnace stuff but I keep running into source not found issues and getting lost. I have been able to tell that ImportedImpl#getExportedInstances is getting called and it is looping over the graph-api addon. But it does not seem to find the class in there, but I have not been able to debug into furnace beyond that point.
Looking at the variable state the WeldServiceRegistery instance for the graph-api addon shows the FIleService there. For some reason it is just not being retrevied. I have attached a screenshoot of the variable state from within ImportedImpl#getExportedInstances. Can you think of any reason serviceRegistry.getExportedInstances(type) would be failing giving all of this?
~Ian
_______________________________________________
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/20150327/bdb341ec/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: windup.png
Type: image/png
Size: 172297 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150327/bdb341ec/attachment-0001.png
From lincolnbaxter at gmail.com Fri Mar 27 19:03:05 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 27 Mar 2015 19:03:05 -0400
Subject: [windup-dev] Windup 2.2.0.Final Released
In-Reply-To: <5515B738.4090906@redhat.com>
References: <CAEp_U4H9NYdg2KPTTD2Da0E7acawwL=WXwA9E2R+vXanEY0HEA@mail.gmail.com>
<1176810837.4605771.1427482122124.JavaMail.zimbra@redhat.com>
<CAEp_U4G0J018PXH8UcMgv6DyhTXy0t=ZxG7XDABuFhwiqWh7+g@mail.gmail.com>
<5515B738.4090906@redhat.com>
Message-ID: <CAEp_U4G6V+2yVes=kjod5ND=a=xDsEmD8yuOP-RMdVwiG=CM-w@mail.gmail.com>
(Points to the team.)
On Fri, Mar 27, 2015 at 4:02 PM, Sande Gilda <sgilda at redhat.com> wrote:
> Wow! That's a huge (30x) improvement! Way to go!
>
>
> On 03/27/2015 03:56 PM, Lincoln Baxter, III wrote:
>
> Great! Thank you for confirming this! We definitely wanted to get these
> improvements into this release, so thank you for your patience as we sorted
> out some of the issues!
>
> ~Lincoln
>
> On Fri, Mar 27, 2015 at 2:48 PM, Robb Greathouse <
> robb.greathouse at redhat.com> wrote:
>
>> Cudos.
>>
>> Running against the 300~mb test file and restricting it to look at
>> packages com.clarify it runs in about 40 minutes vs the old time of 20
>> hours plus. Definite performance improvement.
>>
>>
>>
>> Robb Greathouse
>> Middleware Business Unit
>> JBoss, a Division of Red Hat
>> cellphone 505-507-4906
>>
>> ------------------------------
>>
>> I am proud to announce the release of Windup 2.2.0.Final, which
>> includes the following features/enhanvements/and bugfixes.
>> Great job team!
>>
>> ~Lincoln
>> Bug
>>
>> - [WINDUP-510 <https://issues.jboss.org/browse/WINDUP-510>] - Build
>> fails with BOM missing
>> - [WINDUP-511 <https://issues.jboss.org/browse/WINDUP-511>] -
>> Quickstarts tests fail with a NPE
>> - [WINDUP-516 <https://issues.jboss.org/browse/WINDUP-516>] -
>> [Performance] Multiple valueStores even if the rule does not use parameters
>> - [WINDUP-517 <https://issues.jboss.org/browse/WINDUP-517>] -
>> Application Index page lacks technology list and effort information
>> - [WINDUP-518 <https://issues.jboss.org/browse/WINDUP-518>] - XML
>> Handlers do not support nested rules
>> - [WINDUP-524 <https://issues.jboss.org/browse/WINDUP-524>] - Fix the
>> cyclic dependency between windup and windup-rulesets
>> - [WINDUP-542 <https://issues.jboss.org/browse/WINDUP-542>] - Fix
>> severe regression in AST performance
>> - [WINDUP-544 <https://issues.jboss.org/browse/WINDUP-544>] -
>> StackOverflowException when generating Application report
>>
>> Enhancement
>>
>> - [WINDUP-409 <https://issues.jboss.org/browse/WINDUP-409>] - Allow
>> rules metadata to be specified with annotations - @Rules( phase = ..., ...)
>> - [WINDUP-470 <https://issues.jboss.org/browse/WINDUP-470>] - Classes
>> in java.lang package may differ in how they are parsed
>> - [WINDUP-506 <https://issues.jboss.org/browse/WINDUP-506>] -
>> Identify Archives Ruleset: Improve memory footprint
>> - [WINDUP-508 <https://issues.jboss.org/browse/WINDUP-508>] -
>> WindupRuleProvider should contain a location/origin field (to indicate
>> where it was defined)
>> - [WINDUP-515 <https://issues.jboss.org/browse/WINDUP-515>] - Add
>> Severity to Hint
>> - [WINDUP-520 <https://issues.jboss.org/browse/WINDUP-520>] - Rule
>> Externalization - Introduce a Rule, RuleProvider and RulesetMetadata API
>> - [WINDUP-529 <https://issues.jboss.org/browse/WINDUP-529>] -
>> Performance issue: Query requires iterating over all vertices
>> [(ClassificationModel:classification = ...)]
>>
>> Feature Request
>>
>> - [WINDUP-402 <https://issues.jboss.org/browse/WINDUP-402>] - Change
>> ruleset category metadata to tag-like system (make it a set of strings)
>> - [WINDUP-521 <https://issues.jboss.org/browse/WINDUP-521>] - Rule
>> Externalization - Create XML Handlers for Rule metadata
>> - [WINDUP-522 <https://issues.jboss.org/browse/WINDUP-522>] - Rule
>> Externalization - Create user-interface for selecting source/target
>> platforms
>> - [WINDUP-523 <https://issues.jboss.org/browse/WINDUP-523>] - Rule
>> Externalization - Allow filtering of RuleProviders by tags (categories)
>>
>> Task
>>
>> - [WINDUP-512 <https://issues.jboss.org/browse/WINDUP-512>] - Rename
>> Implicit to Dependent
>> - [WINDUP-513 <https://issues.jboss.org/browse/WINDUP-513>] - Phase
>> pseudo-RuleProviders to have ~Phase suffix
>> - [WINDUP-530 <https://issues.jboss.org/browse/WINDUP-530>] - Rename
>> the module "utils" to "windup-utils"
>>
>> Sub-task
>>
>> - [WINDUP-464 <https://issues.jboss.org/browse/WINDUP-464>] - Expand
>> all addons with simple layout to use full api/impl/tests structure
>> - [WINDUP-465 <https://issues.jboss.org/browse/WINDUP-465>] - Review
>> all rules, organize into an external repository, and add useful hint
>> information with links to knowledge articles
>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>>
>>
>>
>
>
> --
> 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/20150327/1f2a879e/attachment.html
From lincolnbaxter at gmail.com Fri Mar 27 19:11:44 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 27 Mar 2015 19:11:44 -0400
Subject: [windup-dev] FileMapping.getId()
In-Reply-To: <5512D421.4080506@redhat.com>
References: <55120FEB.5030601@redhat.com>
<5512D421.4080506@redhat.com>
Message-ID: <CAEp_U4ETD6kcKaH8MxBgcVifjgbaGQPOFJ+3GJ+Ct0beQpEDfg@mail.gmail.com>
Yep, that seems like a problem.
On Wed, Mar 25, 2015 at 11:28 AM, Jess Sightler <jsightle at redhat.com> wrote:
>
> On 03/24/2015 09:31 PM, Ondrej Zizka wrote:
> > @Override
> > public String getId()
> > {
> > return this.getClass().getName() + "_" +
> > UUID.randomUUID().toString();
> > }
> >
> > Isn't it a potential problem that this returns different values on each
> > call?
> > Shouldn't it store a value once called? Or derive the value from, say, a
> > class object? Or just use Class#hashCode()?
>
> I agree. It seems like a mistake that repeated calls to the same object
> here will return different values.
> _______________________________________________
> 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/20150327/9a7a51b2/attachment.html
From ozizka at redhat.com Sat Mar 28 21:41:48 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Sun, 29 Mar 2015 03:41:48 +0200
Subject: [windup-dev] Out ouf space?
Message-ID: <5517585C.1070808@redhat.com>
Hi,
when running against the app on OS1, I am seeing a weird error:
Caused by: java.io.FileNotFoundException:
/home/cloud-user/migr/apps/ATTEARFiles/ClfyAgent.ear.report/graph/titangraph/00000001.jdb
(No space left on device)
at java.io.RandomAccessFile.open(Native Method)
at
java.io.RandomAccessFile.<init>(RandomAccessFile.java:241)
at
java.io.RandomAccessFile.<init>(RandomAccessFile.java:122)
at
com.sleepycat.je.log.FileManager$DefaultRandomAccessFile.<init>(FileManager.java:3209)
although there was still over 10 GB free.
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 22G 7,3G 15G 34% /
The app runs for a while and when Berkeley is about to create 2nd .jdb
file, it crashes with this.
Is there any limitation of OS1 that could cause this?
Regards,
Ondra
JBoss Windup, version [ 2.3.0-SNAPSHOT ] - JBoss, by Red Hat, Inc. [
http://windup.jboss.org ]
[migr]$ export VERBOSE=true
[migr]$ windup-migrate-app --input apps/***/****Agent.ear
Using user rules dir:
/home/cloud-user/migr/windup-distribution-2.3.0-SNAPSHOT/rules
Using user rules dir: /home/cloud-user/.windup/rules
***INFO*** Executing Rules: [0/1202] ...
***INFO*** Executing Rules:
:GeneratedID_IgnoredArchivesConfigLoadingRuleProvider_1: class
org.jboss.windup.config.phase.InitializationPhase -
IgnoredArchivesConfigLoadingRuleProvider [] [0/1202] ...
***INFO*** Executing Rules:
:GeneratedID_ArchiveIdentificationConfigLoadingRuleProvider_1: class
org.jboss.windup.config.phase.InitializationPhase -
ArchiveIdentificationConfigLoadingRuleProvider [] [1/1202] ...
***INFO*** Executing Rules:
:GeneratedID_CopyJavaConfigToGraphRuleProvider_1: class
org.jboss.windup.config.phase.InitializationPhase -
CopyJavaConfigToGraphRuleProvider [] [2/1202] ...
***INFO*** Executing Rules:
:GeneratedID_GatherIgnoredFileNamesRuleProvider_1: class
org.jboss.windup.config.phase.InitializationPhase -
GatherIgnoredFileNamesRuleProvider [] [3/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DiscoverFilesAndTypesRuleProvider_1: class
org.jboss.windup.config.phase.DiscoveryPhase -
DiscoverFilesAndTypesRuleProvider [] [4/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DiscoverFilesAndTypesRuleProvider_2: class
org.jboss.windup.config.phase.DiscoveryPhase -
DiscoverFilesAndTypesRuleProvider [] [5/1202] ...
***INFO*** Executing Rules:
:GeneratedID_UnzipArchivesToOutputRuleProvider_1: class
org.jboss.windup.config.phase.ArchiveExtractionPhase -
UnzipArchivesToOutputRuleProvider [] [6/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DiscoverArchiveTypesRuleProvider_1: class
org.jboss.windup.config.phase.ArchiveMetadataExtractionPhase -
DiscoverArchiveTypesRuleProvider [] [6/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DiscoverArchiveManifestFilesRuleProvider_1: class
org.jboss.windup.config.phase.ArchiveMetadataExtractionPhase -
DiscoverArchiveManifestFilesRuleProvider [] [6/1202] ...
***INFO*** Executing Rules:
:org.jboss.windup.rules.files.FileMapping_d19ee966-a786-476c-9bf4-04412c77b56c:
class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
DiscoverXmlFilesRuleProvider [] [6/1202] ...
***INFO*** Executing Rules: :GeneratedID_DiscoverXmlFilesRuleProvider_2:
class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
DiscoverXmlFilesRuleProvider [] [7/1202] ...
***INFO*** Executing Rules:
:GeneratedID_IndexJavaClassFilesRuleProvider_1: class
org.jboss.windup.config.phase.ClassifyFileTypesPhase -
IndexJavaClassFilesRuleProvider [] [7/1202] ...
***INFO*** Executing Rules:
:org.jboss.windup.rules.files.FileMapping_22305a06-08ea-4d36-bb71-b9ac14738d1c:
class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
JavaFileMappingRuleProvider [] [7/1202] ...
***INFO*** Executing Rules:
:org.jboss.windup.rules.files.FileMapping_d1767fb8-5aa5-4a7e-8c55-6c655d777600:
class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
JavaFileMappingRuleProvider [] [8/1202] ...
***INFO*** Executing Rules:
:GeneratedID_IndexJavaSourceFilesRuleProvider_1: class
org.jboss.windup.config.phase.ClassifyFileTypesPhase -
IndexJavaSourceFilesRuleProvider [] [9/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DiscoverPropertiesFilesRuleProvider_1: class
org.jboss.windup.config.phase.ClassifyFileTypesPhase -
DiscoverPropertiesFilesRuleProvider [] [9/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DiscoverMavenProjectsRuleProvider_1: class
org.jboss.windup.config.phase.DiscoverProjectStructurePhase -
DiscoverMavenProjectsRuleProvider [] [9/1202] ...
***ERROR*** Error while executing 'Windup Migrate App'
org.jboss.windup.util.exception.WindupException: Error encountered while
evaluating rule:
.addRule().when(Query.find(org.jboss.windup.rules.apps.xml.model.XmlFileModel).gremlin().has(fileName,EQUALS,pom.xml).as(default)).perform(Iteration.over(?).perform(ScanMavenProject)).withId("GeneratedID_DiscoverMavenProjectsRuleProvider_1")
From:
org.jboss.windup.rules.apps.java.scan.provider.DiscoverMavenProjectsRuleProvider
loaded from ModuleClassLoader for Module
"org.jboss.windup.rules.apps.windup-rules-java:2.3.0-SNAPSHOT_b5a66f3a-64a8-4833-89e3-3605a77cb86f"
from AddonModuleLoader
Defined in:
org.jboss.windup.rules.apps.java.scan.provider.DiscoverMavenProjectsRuleProvider.getConfiguration(DiscoverMavenProjectsRuleProvider.java:124)
at org.jboss.windup.config.RuleSubset.perform(RuleSubset.java:313)
at
org.jboss.windup.exec.WindupProcessorImpl.execute(WindupProcessorImpl.java:128)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
at
org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at
org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
at
org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_974cc22d-87d3-4d6d-aabd-d7b720f1bef9.execute(WindupProcessorImpl_$$_javassist_974cc22d-87d3-4d6d-aabd-d7b720f1bef9.java)
at
org.jboss.windup.ui.WindupCommand.execute(WindupCommand.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
at
org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at
org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
at
org.jboss.windup.ui.WindupCommand_$$_javassist_7dfce685-96b6-42c2-9c63-b8d7e1d377d1.execute(WindupCommand_$$_javassist_7dfce685-96b6-42c2-9c63-b8d7e1d377d1.java)
at
org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:90)
at
org.jboss.forge.addon.shell.aesh.CommandAdapter.execute(CommandAdapter.java:82)
at
org.jboss.aesh.console.AeshConsoleImpl$AeshConsoleCallbackImpl.execute(AeshConsoleImpl.java:325)
at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:40)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Suppressed: com.thinkaurelius.titan.core.TitanException: Could
not execute operation due to backend exception
at
com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:44)
at
com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:144)
at
com.thinkaurelius.titan.diskstorage.configuration.backend.KCVSConfiguration.set(KCVSConfiguration.java:145)
at
com.thinkaurelius.titan.diskstorage.configuration.backend.KCVSConfiguration.set(KCVSConfiguration.java:122)
at
com.thinkaurelius.titan.diskstorage.configuration.backend.KCVSConfiguration.remove(KCVSConfiguration.java:163)
at
com.thinkaurelius.titan.diskstorage.configuration.ModifiableConfiguration.remove(ModifiableConfiguration.java:42)
at
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.shutdownInternal(StandardTitanGraph.java:169)
at
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.shutdown(StandardTitanGraph.java:158)
at
org.jboss.windup.graph.GraphContextImpl.close(GraphContextImpl.java:243)
at
org.jboss.windup.ui.WindupCommand.execute(WindupCommand.java:252)
... 15 more
Caused by:
com.thinkaurelius.titan.diskstorage.PermanentBackendException: Could not
start BerkeleyJE transaction
at
com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:144)
at
com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:34)
at
com.thinkaurelius.titan.diskstorage.keycolumnvalue.keyvalue.OrderedKeyValueStoreManagerAdapter.beginTransaction(OrderedKeyValueStoreManagerAdapter.java:52)
at
com.thinkaurelius.titan.diskstorage.Backend$2.openTx(Backend.java:270)
at
com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:131)
at
com.thinkaurelius.titan.diskstorage.util.BackendOperation$1.call(BackendOperation.java:147)
at
com.thinkaurelius.titan.diskstorage.util.BackendOperation.executeDirect(BackendOperation.java:56)
at
com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:42)
... 24 more
Caused by: com.sleepycat.je.EnvironmentFailureException: (JE
5.0.73) Environment must be closed, caused by:
com.sleepycat.je.EnvironmentFailureException: Environment invalid
because of previous exception: (JE 5.0.73)
/home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
/home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
java.io.FileNotFoundException:
/home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
(No space left on device) LOG_INTEGRITY: Log information is incorrect,
problem is likely persistent. UNEXPECTED_EXCEPTION_FATAL: Unexpected
internal Exception, unable to continue. Environment is invalid and must
be closed.
at
com.sleepycat.je.EnvironmentFailureException.wrapSelf(EnvironmentFailureException.java:196)
at
com.sleepycat.je.dbi.EnvironmentImpl.checkIfInvalid(EnvironmentImpl.java:1512)
at
com.sleepycat.je.Environment.checkEnv(Environment.java:2185)
at
com.sleepycat.je.Environment.beginTransactionInternal(Environment.java:1313)
at
com.sleepycat.je.Environment.beginTransaction(Environment.java:1284)
at
com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:134)
... 31 more
Caused by: com.sleepycat.je.EnvironmentFailureException:
Environment invalid because of previous exception: (JE 5.0.73)
/home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
/home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
java.io.FileNotFoundException:
/home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
(No space left on device) LOG_INTEGRITY: Log information is incorrect,
problem is likely persistent. UNEXPECTED_EXCEPTION_FATAL: Unexpected
internal Exception, unable to continue. Environment is invalid and must
be closed.
at
com.sleepycat.je.EnvironmentFailureException.unexpectedException(EnvironmentFailureException.java:301)
at
com.sleepycat.je.log.LogManager.serialLogInternal(LogManager.java:505)
at
com.sleepycat.je.log.SyncedLogManager.serialLog(SyncedLogManager.java:42)
at
com.sleepycat.je.log.LogManager.multiLog(LogManager.java:395)
at com.sleepycat.je.log.LogManager.log(LogManager.java:335)
at com.sleepycat.je.tree.IN.logInternal(IN.java:3534)
at com.sleepycat.je.tree.IN.optionalLog(IN.java:3481)
at com.sleepycat.je.tree.IN.splitInternal(IN.java:2724)
at com.sleepycat.je.tree.IN.split(IN.java:2522)
at com.sleepycat.je.tree.Tree.forceSplit(Tree.java:1984)
at
com.sleepycat.je.tree.Tree.searchSubTreeSplitsAllowed(Tree.java:1767)
at
com.sleepycat.je.tree.Tree.searchSplitsAllowed(Tree.java:1318)
at
com.sleepycat.je.tree.Tree.findBinForInsert(Tree.java:2230)
at
com.sleepycat.je.dbi.CursorImpl.putInternal(CursorImpl.java:866)
at com.sleepycat.je.dbi.CursorImpl.put(CursorImpl.java:811)
at
com.sleepycat.je.Cursor.putAllowPhantoms(Cursor.java:2243)
at com.sleepycat.je.Cursor.putNoNotify(Cursor.java:2200)
at com.sleepycat.je.Cursor.putNotify(Cursor.java:2117)
at com.sleepycat.je.Cursor.putNoDups(Cursor.java:2052)
at com.sleepycat.je.Cursor.putInternal(Cursor.java:2020)
at
com.sleepycat.je.Database.putInternal(Database.java:1302)
at com.sleepycat.je.Database.put(Database.java:1172)
at
com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEKeyValueStore.insert(BerkeleyJEKeyValueStore.java:194)
at
com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEKeyValueStore.insert(BerkeleyJEKeyValueStore.java:183)
at
com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.mutateMany(BerkeleyJEStoreManager.java:193)
at
com.thinkaurelius.titan.diskstorage.keycolumnvalue.keyvalue.OrderedKeyValueStoreManagerAdapter.mutateMany(OrderedKeyValueStoreManagerAdapter.java:100)
at
com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction$1.call(CacheTransaction.java:89)
at
com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction$1.call(CacheTransaction.java:86)
at
com.thinkaurelius.titan.diskstorage.util.BackendOperation.executeDirect(BackendOperation.java:56)
at
com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:42)
at
com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction.persist(CacheTransaction.java:86)
at
com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction.flushInternal(CacheTransaction.java:140)
at
com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction.commit(CacheTransaction.java:197)
at
com.thinkaurelius.titan.diskstorage.BackendTransaction.commitStorage(BackendTransaction.java:117)
at
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.commit(StandardTitanGraph.java:670)
at
com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1337)
at
com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)
at
org.jboss.windup.config.RuleSubset.perform(RuleSubset.java:275)
at
org.jboss.windup.exec.WindupProcessorImpl.execute(WindupProcessorImpl.java:128)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
at
org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at
org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
at
org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_974cc22d-87d3-4d6d-aabd-d7b720f1bef9.execute(WindupProcessorImpl_$$_javassist_974cc22d-87d3-4d6d-aabd-d7b720f1bef9.java)
at
org.jboss.windup.ui.WindupCommand.execute(WindupCommand.java:243)
... 15 more
Caused by: com.sleepycat.je.EnvironmentFailureException: (JE
5.0.73)
/home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
java.io.FileNotFoundException:
/home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
(No space left on device) LOG_INTEGRITY: Log information is incorrect,
problem is likely persistent.
at
com.sleepycat.je.log.FileManager$LogEndFileDescriptor.getWritableFile(FileManager.java:3009)
at
com.sleepycat.je.log.FileManager$LogEndFileDescriptor.access$200(FileManager.java:2710)
at
com.sleepycat.je.log.FileManager.writeLogBuffer(FileManager.java:1609)
at
com.sleepycat.je.log.LogBufferPool.writeBufferToFile(LogBufferPool.java:260)
at
com.sleepycat.je.log.LogBufferPool.getWriteBuffer(LogBufferPool.java:197)
at
com.sleepycat.je.log.LogManager.serialLogWork(LogManager.java:639)
at
com.sleepycat.je.log.LogManager.serialLogInternal(LogManager.java:493)
... 61 more
Caused by: java.io.FileNotFoundException:
/home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
(No space left on device)
at java.io.RandomAccessFile.open(Native Method)
at
java.io.RandomAccessFile.<init>(RandomAccessFile.java:241)
at
java.io.RandomAccessFile.<init>(RandomAccessFile.java:122)
at
com.sleepycat.je.log.FileManager$DefaultRandomAccessFile.<init>(FileManager.java:3209)
at
com.sleepycat.je.log.FileManager$6.createFile(FileManager.java:3237)
at
com.sleepycat.je.log.FileManager.openFileHandle(FileManager.java:1280)
at
com.sleepycat.je.log.FileManager.makeFileHandle(FileManager.java:1247)
at
com.sleepycat.je.log.FileManager.access$1500(FileManager.java:75)
at
com.sleepycat.je.log.FileManager$LogEndFileDescriptor.getWritableFile(FileManager.java:2987)
... 67 more
Caused by: com.thinkaurelius.titan.core.TitanException: Could not start
new transaction
at
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.newTransaction(StandardTitanGraph.java:276)
at
com.thinkaurelius.titan.graphdb.transaction.StandardTransactionBuilder.start(StandardTransactionBuilder.java:220)
at
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.newThreadBoundTransaction(StandardTitanGraph.java:265)
at
com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.getAutoStartTx(TitanBlueprintsGraph.java:104)
at
com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.addVertex(TitanBlueprintsGraph.java:155)
at
com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.addVertex(TitanBlueprintsGraph.java:27)
at
com.tinkerpop.blueprints.util.wrappers.event.EventGraph.addVertex(EventGraph.java:95)
at com.tinkerpop.frames.FramedGraph.addVertex(FramedGraph.java:242)
at com.tinkerpop.frames.FramedGraph.addVertex(FramedGraph.java:258)
at
org.jboss.windup.graph.service.GraphService$3.execute(GraphService.java:92)
at
org.jboss.windup.graph.service.GraphService$3.execute(GraphService.java:88)
at
org.jboss.windup.util.ExecutionStatistics.performBenchmarked(ExecutionStatistics.java:90)
at
org.jboss.windup.graph.service.GraphService.create(GraphService.java:87)
at
org.jboss.windup.config.RuleSubset.logTimeTakenByRuleProvider(RuleSubset.java:120)
at org.jboss.windup.config.RuleSubset.perform(RuleSubset.java:283)
... 25 more
Caused by:
com.thinkaurelius.titan.diskstorage.PermanentBackendException: Could not
start BerkeleyJE transaction
at
com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:144)
at
com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:34)
at
com.thinkaurelius.titan.diskstorage.keycolumnvalue.keyvalue.OrderedKeyValueStoreManagerAdapter.beginTransaction(OrderedKeyValueStoreManagerAdapter.java:52)
at
com.thinkaurelius.titan.diskstorage.Backend.beginTransaction(Backend.java:465)
at
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.openBackendTransaction(StandardTitanGraph.java:282)
at
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.newTransaction(StandardTitanGraph.java:272)
... 39 more
Caused by: com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
Environment must be closed, caused by:
com.sleepycat.je.EnvironmentFailureException: Environment invalid
because of previous exception: (JE 5.0.73)
/home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
/home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
java.io.FileNotFoundException:
/home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
(No space left on device) LOG_INTEGRITY: Log information is incorrect,
problem is likely persistent. UNEXPECTED_EXCEPTION_FATAL: Unexpected
internal Exception, unable to continue. Environment is invalid and must
be closed.
at
com.sleepycat.je.EnvironmentFailureException.wrapSelf(EnvironmentFailureException.java:196)
at
com.sleepycat.je.dbi.EnvironmentImpl.checkIfInvalid(EnvironmentImpl.java:1512)
at com.sleepycat.je.Environment.checkEnv(Environment.java:2185)
at
com.sleepycat.je.Environment.beginTransactionInternal(Environment.java:1313)
at
com.sleepycat.je.Environment.beginTransaction(Environment.java:1284)
at
com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:134)
... 44 more
[CIRCULAR
REFERENCE:com.sleepycat.je.EnvironmentFailureException: Environment
invalid because of previous exception: (JE 5.0.73)
/home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
/home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
java.io.FileNotFoundException:
/home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
(No space left on device) LOG_INTEGRITY: Log information is incorrect,
problem is likely persistent. UNEXPECTED_EXCEPTION_FATAL: Unexpected
internal Exception, unable to continue. Environment is invalid and must
be closed.]
***ERROR*** Error encountered while evaluating rule:
.addRule().when(Query.find(org.jboss.windup.rules.apps.xml.model.XmlFileModel).gremlin().has(fileName,EQUALS,pom.xml).as(default)).perform(Iteration.over(?).perform(ScanMavenProject)).withId("GeneratedID_DiscoverMavenProjectsRuleProvider_1")
From:
org.jboss.windup.rules.apps.java.scan.provider.DiscoverMavenProjectsRuleProvider
loaded from ModuleClassLoader for Module
"org.jboss.windup.rules.apps.windup-rules-java:2.3.0-SNAPSHOT_b5a66f3a-64a8-4833-89e3-3605a77cb86f"
from AddonModuleLoader
Defined in:
org.jboss.windup.rules.apps.java.scan.provider.DiscoverMavenProjectsRuleProvider.getConfiguration(DiscoverMavenProjectsRuleProvider.java:124)
[migr]$
From ozizka at redhat.com Sat Mar 28 21:52:16 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Sun, 29 Mar 2015 03:52:16 +0200
Subject: [windup-dev] Out ouf space?
In-Reply-To: <5517585C.1070808@redhat.com>
References: <5517585C.1070808@redhat.com>
Message-ID: <55175AD0.60700@redhat.com>
After a while, other system apps started to throw such errors.
It seems OS1 is somehow broken - like if it shown 20 GB filesystem but
limited me at around 6 GB. (There's enough quota for the group - almost
1 TB left)
Regrets,
Ondra
On 29.3.2015 03:41, Ondrej Zizka wrote:
> Hi,
>
> when running against the app on OS1, I am seeing a weird error:
>
> Caused by: java.io.FileNotFoundException:
> /home/cloud-user/migr/apps/ATTEARFiles/ClfyAgent.ear.report/graph/titangraph/00000001.jdb
> (No space left on device)
> at java.io.RandomAccessFile.open(Native Method)
> at
> java.io.RandomAccessFile.<init>(RandomAccessFile.java:241)
> at
> java.io.RandomAccessFile.<init>(RandomAccessFile.java:122)
> at
> com.sleepycat.je.log.FileManager$DefaultRandomAccessFile.<init>(FileManager.java:3209)
>
> although there was still over 10 GB free.
>
> Filesystem Size Used Avail Use% Mounted on
> /dev/sda1 22G 7,3G 15G 34% /
>
> The app runs for a while and when Berkeley is about to create 2nd .jdb
> file, it crashes with this.
> Is there any limitation of OS1 that could cause this?
>
> Regards,
> Ondra
>
>
>
>
> JBoss Windup, version [ 2.3.0-SNAPSHOT ] - JBoss, by Red Hat, Inc. [
> http://windup.jboss.org ]
>
> [migr]$ export VERBOSE=true
> [migr]$ windup-migrate-app --input apps/***/****Agent.ear
> Using user rules dir:
> /home/cloud-user/migr/windup-distribution-2.3.0-SNAPSHOT/rules
> Using user rules dir: /home/cloud-user/.windup/rules
> ***INFO*** Executing Rules: [0/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_IgnoredArchivesConfigLoadingRuleProvider_1: class
> org.jboss.windup.config.phase.InitializationPhase -
> IgnoredArchivesConfigLoadingRuleProvider [] [0/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_ArchiveIdentificationConfigLoadingRuleProvider_1: class
> org.jboss.windup.config.phase.InitializationPhase -
> ArchiveIdentificationConfigLoadingRuleProvider [] [1/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_CopyJavaConfigToGraphRuleProvider_1: class
> org.jboss.windup.config.phase.InitializationPhase -
> CopyJavaConfigToGraphRuleProvider [] [2/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_GatherIgnoredFileNamesRuleProvider_1: class
> org.jboss.windup.config.phase.InitializationPhase -
> GatherIgnoredFileNamesRuleProvider [] [3/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_DiscoverFilesAndTypesRuleProvider_1: class
> org.jboss.windup.config.phase.DiscoveryPhase -
> DiscoverFilesAndTypesRuleProvider [] [4/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_DiscoverFilesAndTypesRuleProvider_2: class
> org.jboss.windup.config.phase.DiscoveryPhase -
> DiscoverFilesAndTypesRuleProvider [] [5/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_UnzipArchivesToOutputRuleProvider_1: class
> org.jboss.windup.config.phase.ArchiveExtractionPhase -
> UnzipArchivesToOutputRuleProvider [] [6/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_DiscoverArchiveTypesRuleProvider_1: class
> org.jboss.windup.config.phase.ArchiveMetadataExtractionPhase -
> DiscoverArchiveTypesRuleProvider [] [6/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_DiscoverArchiveManifestFilesRuleProvider_1: class
> org.jboss.windup.config.phase.ArchiveMetadataExtractionPhase -
> DiscoverArchiveManifestFilesRuleProvider [] [6/1202] ...
> ***INFO*** Executing Rules:
> :org.jboss.windup.rules.files.FileMapping_d19ee966-a786-476c-9bf4-04412c77b56c:
> class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
> DiscoverXmlFilesRuleProvider [] [6/1202] ...
> ***INFO*** Executing Rules: :GeneratedID_DiscoverXmlFilesRuleProvider_2:
> class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
> DiscoverXmlFilesRuleProvider [] [7/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_IndexJavaClassFilesRuleProvider_1: class
> org.jboss.windup.config.phase.ClassifyFileTypesPhase -
> IndexJavaClassFilesRuleProvider [] [7/1202] ...
> ***INFO*** Executing Rules:
> :org.jboss.windup.rules.files.FileMapping_22305a06-08ea-4d36-bb71-b9ac14738d1c:
> class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
> JavaFileMappingRuleProvider [] [7/1202] ...
> ***INFO*** Executing Rules:
> :org.jboss.windup.rules.files.FileMapping_d1767fb8-5aa5-4a7e-8c55-6c655d777600:
> class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
> JavaFileMappingRuleProvider [] [8/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_IndexJavaSourceFilesRuleProvider_1: class
> org.jboss.windup.config.phase.ClassifyFileTypesPhase -
> IndexJavaSourceFilesRuleProvider [] [9/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_DiscoverPropertiesFilesRuleProvider_1: class
> org.jboss.windup.config.phase.ClassifyFileTypesPhase -
> DiscoverPropertiesFilesRuleProvider [] [9/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_DiscoverMavenProjectsRuleProvider_1: class
> org.jboss.windup.config.phase.DiscoverProjectStructurePhase -
> DiscoverMavenProjectsRuleProvider [] [9/1202] ...
> ***ERROR*** Error while executing 'Windup Migrate App'
> org.jboss.windup.util.exception.WindupException: Error encountered while
> evaluating rule:
> .addRule().when(Query.find(org.jboss.windup.rules.apps.xml.model.XmlFileModel).gremlin().has(fileName,EQUALS,pom.xml).as(default)).perform(Iteration.over(?).perform(ScanMavenProject)).withId("GeneratedID_DiscoverMavenProjectsRuleProvider_1")
> From:
> org.jboss.windup.rules.apps.java.scan.provider.DiscoverMavenProjectsRuleProvider
> loaded from ModuleClassLoader for Module
> "org.jboss.windup.rules.apps.windup-rules-java:2.3.0-SNAPSHOT_b5a66f3a-64a8-4833-89e3-3605a77cb86f"
> from AddonModuleLoader
> Defined in:
> org.jboss.windup.rules.apps.java.scan.provider.DiscoverMavenProjectsRuleProvider.getConfiguration(DiscoverMavenProjectsRuleProvider.java:124)
> at org.jboss.windup.config.RuleSubset.perform(RuleSubset.java:313)
> at
> org.jboss.windup.exec.WindupProcessorImpl.execute(WindupProcessorImpl.java:128)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
> at
> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
> at
> org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_974cc22d-87d3-4d6d-aabd-d7b720f1bef9.execute(WindupProcessorImpl_$$_javassist_974cc22d-87d3-4d6d-aabd-d7b720f1bef9.java)
> at
> org.jboss.windup.ui.WindupCommand.execute(WindupCommand.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
> at
> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
> at
> org.jboss.windup.ui.WindupCommand_$$_javassist_7dfce685-96b6-42c2-9c63-b8d7e1d377d1.execute(WindupCommand_$$_javassist_7dfce685-96b6-42c2-9c63-b8d7e1d377d1.java)
> at
> org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:90)
> at
> org.jboss.forge.addon.shell.aesh.CommandAdapter.execute(CommandAdapter.java:82)
> at
> org.jboss.aesh.console.AeshConsoleImpl$AeshConsoleCallbackImpl.execute(AeshConsoleImpl.java:325)
> at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Suppressed: com.thinkaurelius.titan.core.TitanException: Could
> not execute operation due to backend exception
> at
> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:44)
> at
> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:144)
> at
> com.thinkaurelius.titan.diskstorage.configuration.backend.KCVSConfiguration.set(KCVSConfiguration.java:145)
> at
> com.thinkaurelius.titan.diskstorage.configuration.backend.KCVSConfiguration.set(KCVSConfiguration.java:122)
> at
> com.thinkaurelius.titan.diskstorage.configuration.backend.KCVSConfiguration.remove(KCVSConfiguration.java:163)
> at
> com.thinkaurelius.titan.diskstorage.configuration.ModifiableConfiguration.remove(ModifiableConfiguration.java:42)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.shutdownInternal(StandardTitanGraph.java:169)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.shutdown(StandardTitanGraph.java:158)
> at
> org.jboss.windup.graph.GraphContextImpl.close(GraphContextImpl.java:243)
> at
> org.jboss.windup.ui.WindupCommand.execute(WindupCommand.java:252)
> ... 15 more
> Caused by:
> com.thinkaurelius.titan.diskstorage.PermanentBackendException: Could not
> start BerkeleyJE transaction
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:144)
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:34)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.keyvalue.OrderedKeyValueStoreManagerAdapter.beginTransaction(OrderedKeyValueStoreManagerAdapter.java:52)
> at
> com.thinkaurelius.titan.diskstorage.Backend$2.openTx(Backend.java:270)
> at
> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:131)
> at
> com.thinkaurelius.titan.diskstorage.util.BackendOperation$1.call(BackendOperation.java:147)
> at
> com.thinkaurelius.titan.diskstorage.util.BackendOperation.executeDirect(BackendOperation.java:56)
> at
> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:42)
> ... 24 more
> Caused by: com.sleepycat.je.EnvironmentFailureException: (JE
> 5.0.73) Environment must be closed, caused by:
> com.sleepycat.je.EnvironmentFailureException: Environment invalid
> because of previous exception: (JE 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> java.io.FileNotFoundException:
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
> (No space left on device) LOG_INTEGRITY: Log information is incorrect,
> problem is likely persistent. UNEXPECTED_EXCEPTION_FATAL: Unexpected
> internal Exception, unable to continue. Environment is invalid and must
> be closed.
> at
> com.sleepycat.je.EnvironmentFailureException.wrapSelf(EnvironmentFailureException.java:196)
> at
> com.sleepycat.je.dbi.EnvironmentImpl.checkIfInvalid(EnvironmentImpl.java:1512)
> at
> com.sleepycat.je.Environment.checkEnv(Environment.java:2185)
> at
> com.sleepycat.je.Environment.beginTransactionInternal(Environment.java:1313)
> at
> com.sleepycat.je.Environment.beginTransaction(Environment.java:1284)
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:134)
> ... 31 more
> Caused by: com.sleepycat.je.EnvironmentFailureException:
> Environment invalid because of previous exception: (JE 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> java.io.FileNotFoundException:
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
> (No space left on device) LOG_INTEGRITY: Log information is incorrect,
> problem is likely persistent. UNEXPECTED_EXCEPTION_FATAL: Unexpected
> internal Exception, unable to continue. Environment is invalid and must
> be closed.
> at
> com.sleepycat.je.EnvironmentFailureException.unexpectedException(EnvironmentFailureException.java:301)
> at
> com.sleepycat.je.log.LogManager.serialLogInternal(LogManager.java:505)
> at
> com.sleepycat.je.log.SyncedLogManager.serialLog(SyncedLogManager.java:42)
> at
> com.sleepycat.je.log.LogManager.multiLog(LogManager.java:395)
> at com.sleepycat.je.log.LogManager.log(LogManager.java:335)
> at com.sleepycat.je.tree.IN.logInternal(IN.java:3534)
> at com.sleepycat.je.tree.IN.optionalLog(IN.java:3481)
> at com.sleepycat.je.tree.IN.splitInternal(IN.java:2724)
> at com.sleepycat.je.tree.IN.split(IN.java:2522)
> at com.sleepycat.je.tree.Tree.forceSplit(Tree.java:1984)
> at
> com.sleepycat.je.tree.Tree.searchSubTreeSplitsAllowed(Tree.java:1767)
> at
> com.sleepycat.je.tree.Tree.searchSplitsAllowed(Tree.java:1318)
> at
> com.sleepycat.je.tree.Tree.findBinForInsert(Tree.java:2230)
> at
> com.sleepycat.je.dbi.CursorImpl.putInternal(CursorImpl.java:866)
> at com.sleepycat.je.dbi.CursorImpl.put(CursorImpl.java:811)
> at
> com.sleepycat.je.Cursor.putAllowPhantoms(Cursor.java:2243)
> at com.sleepycat.je.Cursor.putNoNotify(Cursor.java:2200)
> at com.sleepycat.je.Cursor.putNotify(Cursor.java:2117)
> at com.sleepycat.je.Cursor.putNoDups(Cursor.java:2052)
> at com.sleepycat.je.Cursor.putInternal(Cursor.java:2020)
> at
> com.sleepycat.je.Database.putInternal(Database.java:1302)
> at com.sleepycat.je.Database.put(Database.java:1172)
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEKeyValueStore.insert(BerkeleyJEKeyValueStore.java:194)
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEKeyValueStore.insert(BerkeleyJEKeyValueStore.java:183)
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.mutateMany(BerkeleyJEStoreManager.java:193)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.keyvalue.OrderedKeyValueStoreManagerAdapter.mutateMany(OrderedKeyValueStoreManagerAdapter.java:100)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction$1.call(CacheTransaction.java:89)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction$1.call(CacheTransaction.java:86)
> at
> com.thinkaurelius.titan.diskstorage.util.BackendOperation.executeDirect(BackendOperation.java:56)
> at
> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:42)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction.persist(CacheTransaction.java:86)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction.flushInternal(CacheTransaction.java:140)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction.commit(CacheTransaction.java:197)
> at
> com.thinkaurelius.titan.diskstorage.BackendTransaction.commitStorage(BackendTransaction.java:117)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.commit(StandardTitanGraph.java:670)
> at
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1337)
> at
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)
> at
> org.jboss.windup.config.RuleSubset.perform(RuleSubset.java:275)
> at
> org.jboss.windup.exec.WindupProcessorImpl.execute(WindupProcessorImpl.java:128)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
> at
> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
> at
> org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_974cc22d-87d3-4d6d-aabd-d7b720f1bef9.execute(WindupProcessorImpl_$$_javassist_974cc22d-87d3-4d6d-aabd-d7b720f1bef9.java)
> at
> org.jboss.windup.ui.WindupCommand.execute(WindupCommand.java:243)
> ... 15 more
> Caused by: com.sleepycat.je.EnvironmentFailureException: (JE
> 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> java.io.FileNotFoundException:
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
> (No space left on device) LOG_INTEGRITY: Log information is incorrect,
> problem is likely persistent.
> at
> com.sleepycat.je.log.FileManager$LogEndFileDescriptor.getWritableFile(FileManager.java:3009)
> at
> com.sleepycat.je.log.FileManager$LogEndFileDescriptor.access$200(FileManager.java:2710)
> at
> com.sleepycat.je.log.FileManager.writeLogBuffer(FileManager.java:1609)
> at
> com.sleepycat.je.log.LogBufferPool.writeBufferToFile(LogBufferPool.java:260)
> at
> com.sleepycat.je.log.LogBufferPool.getWriteBuffer(LogBufferPool.java:197)
> at
> com.sleepycat.je.log.LogManager.serialLogWork(LogManager.java:639)
> at
> com.sleepycat.je.log.LogManager.serialLogInternal(LogManager.java:493)
> ... 61 more
> Caused by: java.io.FileNotFoundException:
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
> (No space left on device)
> at java.io.RandomAccessFile.open(Native Method)
> at
> java.io.RandomAccessFile.<init>(RandomAccessFile.java:241)
> at
> java.io.RandomAccessFile.<init>(RandomAccessFile.java:122)
> at
> com.sleepycat.je.log.FileManager$DefaultRandomAccessFile.<init>(FileManager.java:3209)
> at
> com.sleepycat.je.log.FileManager$6.createFile(FileManager.java:3237)
> at
> com.sleepycat.je.log.FileManager.openFileHandle(FileManager.java:1280)
> at
> com.sleepycat.je.log.FileManager.makeFileHandle(FileManager.java:1247)
> at
> com.sleepycat.je.log.FileManager.access$1500(FileManager.java:75)
> at
> com.sleepycat.je.log.FileManager$LogEndFileDescriptor.getWritableFile(FileManager.java:2987)
> ... 67 more
> Caused by: com.thinkaurelius.titan.core.TitanException: Could not start
> new transaction
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.newTransaction(StandardTitanGraph.java:276)
> at
> com.thinkaurelius.titan.graphdb.transaction.StandardTransactionBuilder.start(StandardTransactionBuilder.java:220)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.newThreadBoundTransaction(StandardTitanGraph.java:265)
> at
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.getAutoStartTx(TitanBlueprintsGraph.java:104)
> at
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.addVertex(TitanBlueprintsGraph.java:155)
> at
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.addVertex(TitanBlueprintsGraph.java:27)
> at
> com.tinkerpop.blueprints.util.wrappers.event.EventGraph.addVertex(EventGraph.java:95)
> at com.tinkerpop.frames.FramedGraph.addVertex(FramedGraph.java:242)
> at com.tinkerpop.frames.FramedGraph.addVertex(FramedGraph.java:258)
> at
> org.jboss.windup.graph.service.GraphService$3.execute(GraphService.java:92)
> at
> org.jboss.windup.graph.service.GraphService$3.execute(GraphService.java:88)
> at
> org.jboss.windup.util.ExecutionStatistics.performBenchmarked(ExecutionStatistics.java:90)
> at
> org.jboss.windup.graph.service.GraphService.create(GraphService.java:87)
> at
> org.jboss.windup.config.RuleSubset.logTimeTakenByRuleProvider(RuleSubset.java:120)
> at org.jboss.windup.config.RuleSubset.perform(RuleSubset.java:283)
> ... 25 more
> Caused by:
> com.thinkaurelius.titan.diskstorage.PermanentBackendException: Could not
> start BerkeleyJE transaction
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:144)
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:34)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.keyvalue.OrderedKeyValueStoreManagerAdapter.beginTransaction(OrderedKeyValueStoreManagerAdapter.java:52)
> at
> com.thinkaurelius.titan.diskstorage.Backend.beginTransaction(Backend.java:465)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.openBackendTransaction(StandardTitanGraph.java:282)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.newTransaction(StandardTitanGraph.java:272)
> ... 39 more
> Caused by: com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
> Environment must be closed, caused by:
> com.sleepycat.je.EnvironmentFailureException: Environment invalid
> because of previous exception: (JE 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> java.io.FileNotFoundException:
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
> (No space left on device) LOG_INTEGRITY: Log information is incorrect,
> problem is likely persistent. UNEXPECTED_EXCEPTION_FATAL: Unexpected
> internal Exception, unable to continue. Environment is invalid and must
> be closed.
> at
> com.sleepycat.je.EnvironmentFailureException.wrapSelf(EnvironmentFailureException.java:196)
> at
> com.sleepycat.je.dbi.EnvironmentImpl.checkIfInvalid(EnvironmentImpl.java:1512)
> at com.sleepycat.je.Environment.checkEnv(Environment.java:2185)
> at
> com.sleepycat.je.Environment.beginTransactionInternal(Environment.java:1313)
> at
> com.sleepycat.je.Environment.beginTransaction(Environment.java:1284)
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:134)
> ... 44 more
> [CIRCULAR
> REFERENCE:com.sleepycat.je.EnvironmentFailureException: Environment
> invalid because of previous exception: (JE 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> java.io.FileNotFoundException:
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
> (No space left on device) LOG_INTEGRITY: Log information is incorrect,
> problem is likely persistent. UNEXPECTED_EXCEPTION_FATAL: Unexpected
> internal Exception, unable to continue. Environment is invalid and must
> be closed.]
> ***ERROR*** Error encountered while evaluating rule:
> .addRule().when(Query.find(org.jboss.windup.rules.apps.xml.model.XmlFileModel).gremlin().has(fileName,EQUALS,pom.xml).as(default)).perform(Iteration.over(?).perform(ScanMavenProject)).withId("GeneratedID_DiscoverMavenProjectsRuleProvider_1")
> From:
> org.jboss.windup.rules.apps.java.scan.provider.DiscoverMavenProjectsRuleProvider
> loaded from ModuleClassLoader for Module
> "org.jboss.windup.rules.apps.windup-rules-java:2.3.0-SNAPSHOT_b5a66f3a-64a8-4833-89e3-3605a77cb86f"
> from AddonModuleLoader
> Defined in:
> org.jboss.windup.rules.apps.java.scan.provider.DiscoverMavenProjectsRuleProvider.getConfiguration(DiscoverMavenProjectsRuleProvider.java:124)
> [migr]$
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From lincolnbaxter at gmail.com Mon Mar 30 08:25:14 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 30 Mar 2015 08:25:14 -0400
Subject: [windup-dev] SignatureParser enhancement submitted back to Procyon
Message-ID: <CAEp_U4Fu4RMtLE4h9yNA2Nj-JvgwQL9JDCsV3RvJorJcQXnu4Q@mail.gmail.com>
https://bitbucket.org/mstrobel/procyon/issue/252/fix-performance-of-signatureparser
--
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/20150330/cfe42fac/attachment.html
From jsightle at redhat.com Mon Mar 30 09:32:02 2015
From: jsightle at redhat.com (Jess Sightler)
Date: Mon, 30 Mar 2015 09:32:02 -0400
Subject: [windup-dev] Out ouf space?
In-Reply-To: <5517585C.1070808@redhat.com>
References: <5517585C.1070808@redhat.com>
Message-ID: <55195052.3030109@redhat.com>
It sounds like you ran out of file handles. Perhaps check "df -i"? It
could also be a ulimit issue, although I don't think Java would report
that in the same way. I definitely don't think it is a VM issue.
On 03/28/2015 09:41 PM, Ondrej Zizka wrote:
> Hi,
>
> when running against the app on OS1, I am seeing a weird error:
>
> Caused by: java.io.FileNotFoundException:
> /home/cloud-user/migr/apps/ATTEARFiles/ClfyAgent.ear.report/graph/titangraph/00000001.jdb
> (No space left on device)
> at java.io.RandomAccessFile.open(Native Method)
> at
> java.io.RandomAccessFile.<init>(RandomAccessFile.java:241)
> at
> java.io.RandomAccessFile.<init>(RandomAccessFile.java:122)
> at
> com.sleepycat.je.log.FileManager$DefaultRandomAccessFile.<init>(FileManager.java:3209)
>
> although there was still over 10 GB free.
>
> Filesystem Size Used Avail Use% Mounted on
> /dev/sda1 22G 7,3G 15G 34% /
>
> The app runs for a while and when Berkeley is about to create 2nd .jdb
> file, it crashes with this.
> Is there any limitation of OS1 that could cause this?
>
> Regards,
> Ondra
>
>
>
>
> JBoss Windup, version [ 2.3.0-SNAPSHOT ] - JBoss, by Red Hat, Inc. [
> http://windup.jboss.org ]
>
> [migr]$ export VERBOSE=true
> [migr]$ windup-migrate-app --input apps/***/****Agent.ear
> Using user rules dir:
> /home/cloud-user/migr/windup-distribution-2.3.0-SNAPSHOT/rules
> Using user rules dir: /home/cloud-user/.windup/rules
> ***INFO*** Executing Rules: [0/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_IgnoredArchivesConfigLoadingRuleProvider_1: class
> org.jboss.windup.config.phase.InitializationPhase -
> IgnoredArchivesConfigLoadingRuleProvider [] [0/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_ArchiveIdentificationConfigLoadingRuleProvider_1: class
> org.jboss.windup.config.phase.InitializationPhase -
> ArchiveIdentificationConfigLoadingRuleProvider [] [1/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_CopyJavaConfigToGraphRuleProvider_1: class
> org.jboss.windup.config.phase.InitializationPhase -
> CopyJavaConfigToGraphRuleProvider [] [2/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_GatherIgnoredFileNamesRuleProvider_1: class
> org.jboss.windup.config.phase.InitializationPhase -
> GatherIgnoredFileNamesRuleProvider [] [3/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_DiscoverFilesAndTypesRuleProvider_1: class
> org.jboss.windup.config.phase.DiscoveryPhase -
> DiscoverFilesAndTypesRuleProvider [] [4/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_DiscoverFilesAndTypesRuleProvider_2: class
> org.jboss.windup.config.phase.DiscoveryPhase -
> DiscoverFilesAndTypesRuleProvider [] [5/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_UnzipArchivesToOutputRuleProvider_1: class
> org.jboss.windup.config.phase.ArchiveExtractionPhase -
> UnzipArchivesToOutputRuleProvider [] [6/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_DiscoverArchiveTypesRuleProvider_1: class
> org.jboss.windup.config.phase.ArchiveMetadataExtractionPhase -
> DiscoverArchiveTypesRuleProvider [] [6/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_DiscoverArchiveManifestFilesRuleProvider_1: class
> org.jboss.windup.config.phase.ArchiveMetadataExtractionPhase -
> DiscoverArchiveManifestFilesRuleProvider [] [6/1202] ...
> ***INFO*** Executing Rules:
> :org.jboss.windup.rules.files.FileMapping_d19ee966-a786-476c-9bf4-04412c77b56c:
> class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
> DiscoverXmlFilesRuleProvider [] [6/1202] ...
> ***INFO*** Executing Rules: :GeneratedID_DiscoverXmlFilesRuleProvider_2:
> class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
> DiscoverXmlFilesRuleProvider [] [7/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_IndexJavaClassFilesRuleProvider_1: class
> org.jboss.windup.config.phase.ClassifyFileTypesPhase -
> IndexJavaClassFilesRuleProvider [] [7/1202] ...
> ***INFO*** Executing Rules:
> :org.jboss.windup.rules.files.FileMapping_22305a06-08ea-4d36-bb71-b9ac14738d1c:
> class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
> JavaFileMappingRuleProvider [] [7/1202] ...
> ***INFO*** Executing Rules:
> :org.jboss.windup.rules.files.FileMapping_d1767fb8-5aa5-4a7e-8c55-6c655d777600:
> class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
> JavaFileMappingRuleProvider [] [8/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_IndexJavaSourceFilesRuleProvider_1: class
> org.jboss.windup.config.phase.ClassifyFileTypesPhase -
> IndexJavaSourceFilesRuleProvider [] [9/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_DiscoverPropertiesFilesRuleProvider_1: class
> org.jboss.windup.config.phase.ClassifyFileTypesPhase -
> DiscoverPropertiesFilesRuleProvider [] [9/1202] ...
> ***INFO*** Executing Rules:
> :GeneratedID_DiscoverMavenProjectsRuleProvider_1: class
> org.jboss.windup.config.phase.DiscoverProjectStructurePhase -
> DiscoverMavenProjectsRuleProvider [] [9/1202] ...
> ***ERROR*** Error while executing 'Windup Migrate App'
> org.jboss.windup.util.exception.WindupException: Error encountered while
> evaluating rule:
> .addRule().when(Query.find(org.jboss.windup.rules.apps.xml.model.XmlFileModel).gremlin().has(fileName,EQUALS,pom.xml).as(default)).perform(Iteration.over(?).perform(ScanMavenProject)).withId("GeneratedID_DiscoverMavenProjectsRuleProvider_1")
> From:
> org.jboss.windup.rules.apps.java.scan.provider.DiscoverMavenProjectsRuleProvider
> loaded from ModuleClassLoader for Module
> "org.jboss.windup.rules.apps.windup-rules-java:2.3.0-SNAPSHOT_b5a66f3a-64a8-4833-89e3-3605a77cb86f"
> from AddonModuleLoader
> Defined in:
> org.jboss.windup.rules.apps.java.scan.provider.DiscoverMavenProjectsRuleProvider.getConfiguration(DiscoverMavenProjectsRuleProvider.java:124)
> at org.jboss.windup.config.RuleSubset.perform(RuleSubset.java:313)
> at
> org.jboss.windup.exec.WindupProcessorImpl.execute(WindupProcessorImpl.java:128)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
> at
> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
> at
> org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_974cc22d-87d3-4d6d-aabd-d7b720f1bef9.execute(WindupProcessorImpl_$$_javassist_974cc22d-87d3-4d6d-aabd-d7b720f1bef9.java)
> at
> org.jboss.windup.ui.WindupCommand.execute(WindupCommand.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
> at
> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
> at
> org.jboss.windup.ui.WindupCommand_$$_javassist_7dfce685-96b6-42c2-9c63-b8d7e1d377d1.execute(WindupCommand_$$_javassist_7dfce685-96b6-42c2-9c63-b8d7e1d377d1.java)
> at
> org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:90)
> at
> org.jboss.forge.addon.shell.aesh.CommandAdapter.execute(CommandAdapter.java:82)
> at
> org.jboss.aesh.console.AeshConsoleImpl$AeshConsoleCallbackImpl.execute(AeshConsoleImpl.java:325)
> at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Suppressed: com.thinkaurelius.titan.core.TitanException: Could
> not execute operation due to backend exception
> at
> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:44)
> at
> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:144)
> at
> com.thinkaurelius.titan.diskstorage.configuration.backend.KCVSConfiguration.set(KCVSConfiguration.java:145)
> at
> com.thinkaurelius.titan.diskstorage.configuration.backend.KCVSConfiguration.set(KCVSConfiguration.java:122)
> at
> com.thinkaurelius.titan.diskstorage.configuration.backend.KCVSConfiguration.remove(KCVSConfiguration.java:163)
> at
> com.thinkaurelius.titan.diskstorage.configuration.ModifiableConfiguration.remove(ModifiableConfiguration.java:42)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.shutdownInternal(StandardTitanGraph.java:169)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.shutdown(StandardTitanGraph.java:158)
> at
> org.jboss.windup.graph.GraphContextImpl.close(GraphContextImpl.java:243)
> at
> org.jboss.windup.ui.WindupCommand.execute(WindupCommand.java:252)
> ... 15 more
> Caused by:
> com.thinkaurelius.titan.diskstorage.PermanentBackendException: Could not
> start BerkeleyJE transaction
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:144)
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:34)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.keyvalue.OrderedKeyValueStoreManagerAdapter.beginTransaction(OrderedKeyValueStoreManagerAdapter.java:52)
> at
> com.thinkaurelius.titan.diskstorage.Backend$2.openTx(Backend.java:270)
> at
> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:131)
> at
> com.thinkaurelius.titan.diskstorage.util.BackendOperation$1.call(BackendOperation.java:147)
> at
> com.thinkaurelius.titan.diskstorage.util.BackendOperation.executeDirect(BackendOperation.java:56)
> at
> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:42)
> ... 24 more
> Caused by: com.sleepycat.je.EnvironmentFailureException: (JE
> 5.0.73) Environment must be closed, caused by:
> com.sleepycat.je.EnvironmentFailureException: Environment invalid
> because of previous exception: (JE 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> java.io.FileNotFoundException:
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
> (No space left on device) LOG_INTEGRITY: Log information is incorrect,
> problem is likely persistent. UNEXPECTED_EXCEPTION_FATAL: Unexpected
> internal Exception, unable to continue. Environment is invalid and must
> be closed.
> at
> com.sleepycat.je.EnvironmentFailureException.wrapSelf(EnvironmentFailureException.java:196)
> at
> com.sleepycat.je.dbi.EnvironmentImpl.checkIfInvalid(EnvironmentImpl.java:1512)
> at
> com.sleepycat.je.Environment.checkEnv(Environment.java:2185)
> at
> com.sleepycat.je.Environment.beginTransactionInternal(Environment.java:1313)
> at
> com.sleepycat.je.Environment.beginTransaction(Environment.java:1284)
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:134)
> ... 31 more
> Caused by: com.sleepycat.je.EnvironmentFailureException:
> Environment invalid because of previous exception: (JE 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> java.io.FileNotFoundException:
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
> (No space left on device) LOG_INTEGRITY: Log information is incorrect,
> problem is likely persistent. UNEXPECTED_EXCEPTION_FATAL: Unexpected
> internal Exception, unable to continue. Environment is invalid and must
> be closed.
> at
> com.sleepycat.je.EnvironmentFailureException.unexpectedException(EnvironmentFailureException.java:301)
> at
> com.sleepycat.je.log.LogManager.serialLogInternal(LogManager.java:505)
> at
> com.sleepycat.je.log.SyncedLogManager.serialLog(SyncedLogManager.java:42)
> at
> com.sleepycat.je.log.LogManager.multiLog(LogManager.java:395)
> at com.sleepycat.je.log.LogManager.log(LogManager.java:335)
> at com.sleepycat.je.tree.IN.logInternal(IN.java:3534)
> at com.sleepycat.je.tree.IN.optionalLog(IN.java:3481)
> at com.sleepycat.je.tree.IN.splitInternal(IN.java:2724)
> at com.sleepycat.je.tree.IN.split(IN.java:2522)
> at com.sleepycat.je.tree.Tree.forceSplit(Tree.java:1984)
> at
> com.sleepycat.je.tree.Tree.searchSubTreeSplitsAllowed(Tree.java:1767)
> at
> com.sleepycat.je.tree.Tree.searchSplitsAllowed(Tree.java:1318)
> at
> com.sleepycat.je.tree.Tree.findBinForInsert(Tree.java:2230)
> at
> com.sleepycat.je.dbi.CursorImpl.putInternal(CursorImpl.java:866)
> at com.sleepycat.je.dbi.CursorImpl.put(CursorImpl.java:811)
> at
> com.sleepycat.je.Cursor.putAllowPhantoms(Cursor.java:2243)
> at com.sleepycat.je.Cursor.putNoNotify(Cursor.java:2200)
> at com.sleepycat.je.Cursor.putNotify(Cursor.java:2117)
> at com.sleepycat.je.Cursor.putNoDups(Cursor.java:2052)
> at com.sleepycat.je.Cursor.putInternal(Cursor.java:2020)
> at
> com.sleepycat.je.Database.putInternal(Database.java:1302)
> at com.sleepycat.je.Database.put(Database.java:1172)
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEKeyValueStore.insert(BerkeleyJEKeyValueStore.java:194)
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEKeyValueStore.insert(BerkeleyJEKeyValueStore.java:183)
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.mutateMany(BerkeleyJEStoreManager.java:193)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.keyvalue.OrderedKeyValueStoreManagerAdapter.mutateMany(OrderedKeyValueStoreManagerAdapter.java:100)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction$1.call(CacheTransaction.java:89)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction$1.call(CacheTransaction.java:86)
> at
> com.thinkaurelius.titan.diskstorage.util.BackendOperation.executeDirect(BackendOperation.java:56)
> at
> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:42)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction.persist(CacheTransaction.java:86)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction.flushInternal(CacheTransaction.java:140)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction.commit(CacheTransaction.java:197)
> at
> com.thinkaurelius.titan.diskstorage.BackendTransaction.commitStorage(BackendTransaction.java:117)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.commit(StandardTitanGraph.java:670)
> at
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1337)
> at
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)
> at
> org.jboss.windup.config.RuleSubset.perform(RuleSubset.java:275)
> at
> org.jboss.windup.exec.WindupProcessorImpl.execute(WindupProcessorImpl.java:128)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
> at
> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at
> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
> at
> org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_974cc22d-87d3-4d6d-aabd-d7b720f1bef9.execute(WindupProcessorImpl_$$_javassist_974cc22d-87d3-4d6d-aabd-d7b720f1bef9.java)
> at
> org.jboss.windup.ui.WindupCommand.execute(WindupCommand.java:243)
> ... 15 more
> Caused by: com.sleepycat.je.EnvironmentFailureException: (JE
> 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> java.io.FileNotFoundException:
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
> (No space left on device) LOG_INTEGRITY: Log information is incorrect,
> problem is likely persistent.
> at
> com.sleepycat.je.log.FileManager$LogEndFileDescriptor.getWritableFile(FileManager.java:3009)
> at
> com.sleepycat.je.log.FileManager$LogEndFileDescriptor.access$200(FileManager.java:2710)
> at
> com.sleepycat.je.log.FileManager.writeLogBuffer(FileManager.java:1609)
> at
> com.sleepycat.je.log.LogBufferPool.writeBufferToFile(LogBufferPool.java:260)
> at
> com.sleepycat.je.log.LogBufferPool.getWriteBuffer(LogBufferPool.java:197)
> at
> com.sleepycat.je.log.LogManager.serialLogWork(LogManager.java:639)
> at
> com.sleepycat.je.log.LogManager.serialLogInternal(LogManager.java:493)
> ... 61 more
> Caused by: java.io.FileNotFoundException:
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
> (No space left on device)
> at java.io.RandomAccessFile.open(Native Method)
> at
> java.io.RandomAccessFile.<init>(RandomAccessFile.java:241)
> at
> java.io.RandomAccessFile.<init>(RandomAccessFile.java:122)
> at
> com.sleepycat.je.log.FileManager$DefaultRandomAccessFile.<init>(FileManager.java:3209)
> at
> com.sleepycat.je.log.FileManager$6.createFile(FileManager.java:3237)
> at
> com.sleepycat.je.log.FileManager.openFileHandle(FileManager.java:1280)
> at
> com.sleepycat.je.log.FileManager.makeFileHandle(FileManager.java:1247)
> at
> com.sleepycat.je.log.FileManager.access$1500(FileManager.java:75)
> at
> com.sleepycat.je.log.FileManager$LogEndFileDescriptor.getWritableFile(FileManager.java:2987)
> ... 67 more
> Caused by: com.thinkaurelius.titan.core.TitanException: Could not start
> new transaction
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.newTransaction(StandardTitanGraph.java:276)
> at
> com.thinkaurelius.titan.graphdb.transaction.StandardTransactionBuilder.start(StandardTransactionBuilder.java:220)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.newThreadBoundTransaction(StandardTitanGraph.java:265)
> at
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.getAutoStartTx(TitanBlueprintsGraph.java:104)
> at
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.addVertex(TitanBlueprintsGraph.java:155)
> at
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.addVertex(TitanBlueprintsGraph.java:27)
> at
> com.tinkerpop.blueprints.util.wrappers.event.EventGraph.addVertex(EventGraph.java:95)
> at com.tinkerpop.frames.FramedGraph.addVertex(FramedGraph.java:242)
> at com.tinkerpop.frames.FramedGraph.addVertex(FramedGraph.java:258)
> at
> org.jboss.windup.graph.service.GraphService$3.execute(GraphService.java:92)
> at
> org.jboss.windup.graph.service.GraphService$3.execute(GraphService.java:88)
> at
> org.jboss.windup.util.ExecutionStatistics.performBenchmarked(ExecutionStatistics.java:90)
> at
> org.jboss.windup.graph.service.GraphService.create(GraphService.java:87)
> at
> org.jboss.windup.config.RuleSubset.logTimeTakenByRuleProvider(RuleSubset.java:120)
> at org.jboss.windup.config.RuleSubset.perform(RuleSubset.java:283)
> ... 25 more
> Caused by:
> com.thinkaurelius.titan.diskstorage.PermanentBackendException: Could not
> start BerkeleyJE transaction
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:144)
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:34)
> at
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.keyvalue.OrderedKeyValueStoreManagerAdapter.beginTransaction(OrderedKeyValueStoreManagerAdapter.java:52)
> at
> com.thinkaurelius.titan.diskstorage.Backend.beginTransaction(Backend.java:465)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.openBackendTransaction(StandardTitanGraph.java:282)
> at
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.newTransaction(StandardTitanGraph.java:272)
> ... 39 more
> Caused by: com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
> Environment must be closed, caused by:
> com.sleepycat.je.EnvironmentFailureException: Environment invalid
> because of previous exception: (JE 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> java.io.FileNotFoundException:
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
> (No space left on device) LOG_INTEGRITY: Log information is incorrect,
> problem is likely persistent. UNEXPECTED_EXCEPTION_FATAL: Unexpected
> internal Exception, unable to continue. Environment is invalid and must
> be closed.
> at
> com.sleepycat.je.EnvironmentFailureException.wrapSelf(EnvironmentFailureException.java:196)
> at
> com.sleepycat.je.dbi.EnvironmentImpl.checkIfInvalid(EnvironmentImpl.java:1512)
> at com.sleepycat.je.Environment.checkEnv(Environment.java:2185)
> at
> com.sleepycat.je.Environment.beginTransactionInternal(Environment.java:1313)
> at
> com.sleepycat.je.Environment.beginTransaction(Environment.java:1284)
> at
> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:134)
> ... 44 more
> [CIRCULAR
> REFERENCE:com.sleepycat.je.EnvironmentFailureException: Environment
> invalid because of previous exception: (JE 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
> java.io.FileNotFoundException:
> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
> (No space left on device) LOG_INTEGRITY: Log information is incorrect,
> problem is likely persistent. UNEXPECTED_EXCEPTION_FATAL: Unexpected
> internal Exception, unable to continue. Environment is invalid and must
> be closed.]
> ***ERROR*** Error encountered while evaluating rule:
> .addRule().when(Query.find(org.jboss.windup.rules.apps.xml.model.XmlFileModel).gremlin().has(fileName,EQUALS,pom.xml).as(default)).perform(Iteration.over(?).perform(ScanMavenProject)).withId("GeneratedID_DiscoverMavenProjectsRuleProvider_1")
> From:
> org.jboss.windup.rules.apps.java.scan.provider.DiscoverMavenProjectsRuleProvider
> loaded from ModuleClassLoader for Module
> "org.jboss.windup.rules.apps.windup-rules-java:2.3.0-SNAPSHOT_b5a66f3a-64a8-4833-89e3-3605a77cb86f"
> from AddonModuleLoader
> Defined in:
> org.jboss.windup.rules.apps.java.scan.provider.DiscoverMavenProjectsRuleProvider.getConfiguration(DiscoverMavenProjectsRuleProvider.java:124)
> [migr]$
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
--
Calendar Free/Busy: https://www.google.com/calendar/embed?src=jsightle%40redhat.com&ctz=America/New_York
From ozizka at redhat.com Mon Mar 30 09:55:31 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 30 Mar 2015 15:55:31 +0200
Subject: [windup-dev] Out ouf space?
In-Reply-To: <55195052.3030109@redhat.com>
References: <5517585C.1070808@redhat.com> <55195052.3030109@redhat.com>
Message-ID: <551955D3.2020900@redhat.com>
I checked all of that, but the numbers looked okay. File descriptors
limit is around 22 000, used was under 1600.
When I rebooted the machine (and deleted my other OS1 instance which was
stopped), the same run failed with:
ClassNotFoundException: org.eclipse.text.edits.MalformedTreeException
which might be caused by the same thing, maybe?
Ondra
[migr]$ windup-migrate-app --input apps/***EARFiles/****Agent.ear
? Overwrite all contents of
"/home/cloud-user/migr/apps/***EARFiles/****Agent.ear.report" (anything
already in the directory will be deleted)? [y/N]: y
Using user rules dir:
/home/cloud-user/migr/windup-distribution-2.3.0-SNAPSHOT/rules
Using user rules dir: /home/cloud-user/.windup/rules
***INFO*** Executing Rules: [0/1202] ...
***INFO*** Executing Rules:
:GeneratedID_ArchiveIdentificationConfigLoadingRuleProvider_1: class
org.jboss.windup.config.phase.InitializationPhase -
ArchiveIdentificationConfigLoadingRuleProvider [] [0/1202] ...
***INFO*** Executing Rules:
:GeneratedID_IgnoredArchivesConfigLoadingRuleProvider_1: class
org.jboss.windup.config.phase.InitializationPhase -
IgnoredArchivesConfigLoadingRuleProvider [] [1/1202] ...
***INFO*** Executing Rules:
:GeneratedID_CopyJavaConfigToGraphRuleProvider_1: class
org.jboss.windup.config.phase.InitializationPhase -
CopyJavaConfigToGraphRuleProvider [] [2/1202] ...
***INFO*** Executing Rules:
:GeneratedID_GatherIgnoredFileNamesRuleProvider_1: class
org.jboss.windup.config.phase.InitializationPhase -
GatherIgnoredFileNamesRuleProvider [] [3/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DiscoverFilesAndTypesRuleProvider_1: class
org.jboss.windup.config.phase.DiscoveryPhase -
DiscoverFilesAndTypesRuleProvider [] [4/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DiscoverFilesAndTypesRuleProvider_2: class
org.jboss.windup.config.phase.DiscoveryPhase -
DiscoverFilesAndTypesRuleProvider [] [5/1202] ...
***INFO*** Executing Rules:
:GeneratedID_UnzipArchivesToOutputRuleProvider_1: class
org.jboss.windup.config.phase.ArchiveExtractionPhase -
UnzipArchivesToOutputRuleProvider [] [6/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DiscoverArchiveManifestFilesRuleProvider_1: class
org.jboss.windup.config.phase.ArchiveMetadataExtractionPhase -
DiscoverArchiveManifestFilesRuleProvider [] [6/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DiscoverArchiveTypesRuleProvider_1: class
org.jboss.windup.config.phase.ArchiveMetadataExtractionPhase -
DiscoverArchiveTypesRuleProvider [] [7/1202] ...
***INFO*** Executing Rules:
:org.jboss.windup.rules.files.FileMapping_14883752-ea63-41f5-9fc6-7dc1e263fac8:
class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
DiscoverXmlFilesRuleProvider [] [8/1202] ...
***INFO*** Executing Rules: :GeneratedID_DiscoverXmlFilesRuleProvider_2:
class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
DiscoverXmlFilesRuleProvider [] [9/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DiscoverPropertiesFilesRuleProvider_1: class
org.jboss.windup.config.phase.ClassifyFileTypesPhase -
DiscoverPropertiesFilesRuleProvider [] [10/1202] ...
***INFO*** Executing Rules:
:GeneratedID_IndexJavaSourceFilesRuleProvider_1: class
org.jboss.windup.config.phase.ClassifyFileTypesPhase -
IndexJavaSourceFilesRuleProvider [] [11/1202] ...
***INFO*** Executing Rules:
:org.jboss.windup.rules.files.FileMapping_71b36c84-26cf-42d2-974c-8643b65022b2:
class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
JavaFileMappingRuleProvider [] [12/1202] ...
***INFO*** Executing Rules:
:org.jboss.windup.rules.files.FileMapping_d6d0a872-0c2b-4398-8d06-d42e724d6aa0:
class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
JavaFileMappingRuleProvider [] [13/1202] ...
***INFO*** Executing Rules:
:GeneratedID_IndexJavaClassFilesRuleProvider_1: class
org.jboss.windup.config.phase.ClassifyFileTypesPhase -
IndexJavaClassFilesRuleProvider [] [14/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DiscoverMavenProjectsRuleProvider_1: class
org.jboss.windup.config.phase.DiscoverProjectStructurePhase -
DiscoverMavenProjectsRuleProvider [] [15/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DiscoverNonMavenArchiveProjectsRuleProvider_1: class
org.jboss.windup.config.phase.DiscoverProjectStructurePhase -
DiscoverNonMavenArchiveProjectsRuleProvider [] [16/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DiscoverNonMavenSourceProjectsRuleProvider_1: class
org.jboss.windup.config.phase.DiscoverProjectStructurePhase -
DiscoverNonMavenSourceProjectsRuleProvider [] [17/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DiscoverMavenHierarchyRuleProvider_1: class
org.jboss.windup.config.phase.DiscoverProjectStructurePhase -
DiscoverMavenHierarchyRuleProvider [] [18/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DecompileArchivesRuleProvider_1: class
org.jboss.windup.config.phase.DecompilationPhase -
DecompileArchivesRuleProvider [] [19/1202] ...
***INFO*** Executing Rules:
:GeneratedID_DecompileArchivesRuleProvider_2: class
org.jboss.windup.config.phase.DecompilationPhase -
DecompileArchivesRuleProvider [] [20/1202] ...
***INFO*** Executing Rules: :GeneratedID_AnalyzeJavaFilesRuleProvider_1:
class org.jboss.windup.config.phase.InitialAnalysisPhase -
AnalyzeJavaFilesRuleProvider [] [21/1202] ...
***ERROR*** Error while executing 'Windup Migrate App'
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
at
org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at
org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
at
org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_1ac571bd-422d-42c4-9cb8-c46b400159fc.execute(WindupProcessorImpl_$$_javassist_1ac571bd-422d-42c4-9cb8-c46b400159fc.java)
at
org.jboss.windup.ui.WindupCommand.execute(WindupCommand.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
at
org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at
org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
at
org.jboss.windup.ui.WindupCommand_$$_javassist_4a37e360-4403-4c81-aa21-7c4515fad06e.execute(WindupCommand_$$_javassist_4a37e360-4403-4c81-aa21-7c4515fad06e.java)
at
org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:90)
at
org.jboss.forge.addon.shell.aesh.CommandAdapter.execute(CommandAdapter.java:82)
at
org.jboss.aesh.console.AeshConsoleImpl$AeshConsoleCallbackImpl.execute(AeshConsoleImpl.java:325)
at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:40)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NoClassDefFoundError:
org/eclipse/text/edits/MalformedTreeException
at
org.eclipse.jdt.core.dom.TypeBinding.getInterfaces(TypeBinding.java:516)
at
org.jboss.windup.ast.java.ASTProcessor.visit(ASTProcessor.java:752)
at
org.eclipse.jdt.core.dom.MethodInvocation.accept0(MethodInvocation.java:231)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2759)
at
org.eclipse.jdt.core.dom.ExpressionStatement.accept0(ExpressionStatement.java:145)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
at
org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2782)
at org.eclipse.jdt.core.dom.Block.accept0(Block.java:137)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2759)
at
org.eclipse.jdt.core.dom.IfStatement.accept0(IfStatement.java:191)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
at
org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2782)
at org.eclipse.jdt.core.dom.Block.accept0(Block.java:137)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2759)
at
org.eclipse.jdt.core.dom.TryStatement.accept0(TryStatement.java:250)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
at
org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2782)
at org.eclipse.jdt.core.dom.Block.accept0(Block.java:137)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2759)
at
org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:635)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
at
org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2782)
at
org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:470)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
at
org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2782)
at
org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:212)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
at
org.jboss.windup.ast.java.ASTProcessor.analyzeFile(ASTProcessor.java:216)
at
org.jboss.windup.rules.apps.java.scan.provider.AnalyzeJavaFilesRuleProvider$ParseSourceOperation.perform(AnalyzeJavaFilesRuleProvider.java:151)
at
org.jboss.windup.rules.apps.java.scan.provider.AnalyzeJavaFilesRuleProvider$ParseSourceOperation.perform(AnalyzeJavaFilesRuleProvider.java:99)
at
org.jboss.windup.config.operation.iteration.AbstractIterationOperation.perform(AbstractIterationOperation.java:65)
at
org.jboss.windup.config.operation.GraphOperation.perform(GraphOperation.java:24)
at
org.ocpsoft.rewrite.config.DefaultOperationBuilder$DefaultOperationBuilderInternal.perform(DefaultOperationBuilder.java:54)
at
org.ocpsoft.rewrite.config.DefaultOperationBuilder$DefaultOperationBuilderInternal.perform(DefaultOperationBuilder.java:54)
at
org.jboss.windup.config.operation.Iteration.perform(Iteration.java:236)
at
org.jboss.windup.config.operation.Iteration.perform(Iteration.java:200)
at
org.ocpsoft.rewrite.config.DefaultOperationBuilder$DefaultOperationBuilderInternal.perform(DefaultOperationBuilder.java:54)
at
org.ocpsoft.rewrite.config.RuleBuilder.perform(RuleBuilder.java:168)
at org.jboss.windup.config.RuleSubset.perform(RuleSubset.java:241)
at
org.jboss.windup.exec.WindupProcessorImpl.execute(WindupProcessorImpl.java:128)
... 24 more
Caused by: java.lang.ClassNotFoundException:
org.eclipse.text.edits.MalformedTreeException from [Module
"org.jboss.windup.ast.windup-java-ast:2.3.0-SNAPSHOT_158cdc45-6430-42f7-823f-0596e0b6eeee"
from AddonModuleLoader]
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:197)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373)
at
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118)
... 68 more
On 30.3.2015 15:32, Jess Sightler wrote:
> It sounds like you ran out of file handles. Perhaps check "df -i"? It
> could also be a ulimit issue, although I don't think Java would report
> that in the same way. I definitely don't think it is a VM issue.
>
> On 03/28/2015 09:41 PM, Ondrej Zizka wrote:
>> Hi,
>>
>> when running against the app on OS1, I am seeing a weird error:
>>
>> Caused by: java.io.FileNotFoundException:
>> /home/cloud-user/migr/apps/***EARFiles/****Agent.ear.report/graph/titangraph/00000001.jdb
>> (No space left on device)
>> at java.io.RandomAccessFile.open(Native Method)
>> at
>> java.io.RandomAccessFile.<init>(RandomAccessFile.java:241)
>> at
>> java.io.RandomAccessFile.<init>(RandomAccessFile.java:122)
>> at
>> com.sleepycat.je.log.FileManager$DefaultRandomAccessFile.<init>(FileManager.java:3209)
>>
>> although there was still over 10 GB free.
>>
>> Filesystem Size Used Avail Use% Mounted on
>> /dev/sda1 22G 7,3G 15G 34% /
>>
>> The app runs for a while and when Berkeley is about to create 2nd .jdb
>> file, it crashes with this.
>> Is there any limitation of OS1 that could cause this?
>>
>> Regards,
>> Ondra
>>
>>
>>
>>
>> JBoss Windup, version [ 2.3.0-SNAPSHOT ] - JBoss, by Red Hat, Inc. [
>> http://windup.jboss.org ]
>>
>> [migr]$ export VERBOSE=true
>> [migr]$ windup-migrate-app --input apps/***/****Agent.ear
>> Using user rules dir:
>> /home/cloud-user/migr/windup-distribution-2.3.0-SNAPSHOT/rules
>> Using user rules dir: /home/cloud-user/.windup/rules
>> ***INFO*** Executing Rules: [0/1202] ...
>> ***INFO*** Executing Rules:
>> :GeneratedID_IgnoredArchivesConfigLoadingRuleProvider_1: class
>> org.jboss.windup.config.phase.InitializationPhase -
>> IgnoredArchivesConfigLoadingRuleProvider [] [0/1202] ...
>> ***INFO*** Executing Rules:
>> :GeneratedID_ArchiveIdentificationConfigLoadingRuleProvider_1: class
>> org.jboss.windup.config.phase.InitializationPhase -
>> ArchiveIdentificationConfigLoadingRuleProvider [] [1/1202] ...
>> ***INFO*** Executing Rules:
>> :GeneratedID_CopyJavaConfigToGraphRuleProvider_1: class
>> org.jboss.windup.config.phase.InitializationPhase -
>> CopyJavaConfigToGraphRuleProvider [] [2/1202] ...
>> ***INFO*** Executing Rules:
>> :GeneratedID_GatherIgnoredFileNamesRuleProvider_1: class
>> org.jboss.windup.config.phase.InitializationPhase -
>> GatherIgnoredFileNamesRuleProvider [] [3/1202] ...
>> ***INFO*** Executing Rules:
>> :GeneratedID_DiscoverFilesAndTypesRuleProvider_1: class
>> org.jboss.windup.config.phase.DiscoveryPhase -
>> DiscoverFilesAndTypesRuleProvider [] [4/1202] ...
>> ***INFO*** Executing Rules:
>> :GeneratedID_DiscoverFilesAndTypesRuleProvider_2: class
>> org.jboss.windup.config.phase.DiscoveryPhase -
>> DiscoverFilesAndTypesRuleProvider [] [5/1202] ...
>> ***INFO*** Executing Rules:
>> :GeneratedID_UnzipArchivesToOutputRuleProvider_1: class
>> org.jboss.windup.config.phase.ArchiveExtractionPhase -
>> UnzipArchivesToOutputRuleProvider [] [6/1202] ...
>> ***INFO*** Executing Rules:
>> :GeneratedID_DiscoverArchiveTypesRuleProvider_1: class
>> org.jboss.windup.config.phase.ArchiveMetadataExtractionPhase -
>> DiscoverArchiveTypesRuleProvider [] [6/1202] ...
>> ***INFO*** Executing Rules:
>> :GeneratedID_DiscoverArchiveManifestFilesRuleProvider_1: class
>> org.jboss.windup.config.phase.ArchiveMetadataExtractionPhase -
>> DiscoverArchiveManifestFilesRuleProvider [] [6/1202] ...
>> ***INFO*** Executing Rules:
>> :org.jboss.windup.rules.files.FileMapping_d19ee966-a786-476c-9bf4-04412c77b56c:
>> class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
>> DiscoverXmlFilesRuleProvider [] [6/1202] ...
>> ***INFO*** Executing Rules: :GeneratedID_DiscoverXmlFilesRuleProvider_2:
>> class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
>> DiscoverXmlFilesRuleProvider [] [7/1202] ...
>> ***INFO*** Executing Rules:
>> :GeneratedID_IndexJavaClassFilesRuleProvider_1: class
>> org.jboss.windup.config.phase.ClassifyFileTypesPhase -
>> IndexJavaClassFilesRuleProvider [] [7/1202] ...
>> ***INFO*** Executing Rules:
>> :org.jboss.windup.rules.files.FileMapping_22305a06-08ea-4d36-bb71-b9ac14738d1c:
>> class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
>> JavaFileMappingRuleProvider [] [7/1202] ...
>> ***INFO*** Executing Rules:
>> :org.jboss.windup.rules.files.FileMapping_d1767fb8-5aa5-4a7e-8c55-6c655d777600:
>> class org.jboss.windup.config.phase.ClassifyFileTypesPhase -
>> JavaFileMappingRuleProvider [] [8/1202] ...
>> ***INFO*** Executing Rules:
>> :GeneratedID_IndexJavaSourceFilesRuleProvider_1: class
>> org.jboss.windup.config.phase.ClassifyFileTypesPhase -
>> IndexJavaSourceFilesRuleProvider [] [9/1202] ...
>> ***INFO*** Executing Rules:
>> :GeneratedID_DiscoverPropertiesFilesRuleProvider_1: class
>> org.jboss.windup.config.phase.ClassifyFileTypesPhase -
>> DiscoverPropertiesFilesRuleProvider [] [9/1202] ...
>> ***INFO*** Executing Rules:
>> :GeneratedID_DiscoverMavenProjectsRuleProvider_1: class
>> org.jboss.windup.config.phase.DiscoverProjectStructurePhase -
>> DiscoverMavenProjectsRuleProvider [] [9/1202] ...
>> ***ERROR*** Error while executing 'Windup Migrate App'
>> org.jboss.windup.util.exception.WindupException: Error encountered while
>> evaluating rule:
>> .addRule().when(Query.find(org.jboss.windup.rules.apps.xml.model.XmlFileModel).gremlin().has(fileName,EQUALS,pom.xml).as(default)).perform(Iteration.over(?).perform(ScanMavenProject)).withId("GeneratedID_DiscoverMavenProjectsRuleProvider_1")
>> From:
>> org.jboss.windup.rules.apps.java.scan.provider.DiscoverMavenProjectsRuleProvider
>> loaded from ModuleClassLoader for Module
>> "org.jboss.windup.rules.apps.windup-rules-java:2.3.0-SNAPSHOT_b5a66f3a-64a8-4833-89e3-3605a77cb86f"
>> from AddonModuleLoader
>> Defined in:
>> org.jboss.windup.rules.apps.java.scan.provider.DiscoverMavenProjectsRuleProvider.getConfiguration(DiscoverMavenProjectsRuleProvider.java:124)
>> at org.jboss.windup.config.RuleSubset.perform(RuleSubset.java:313)
>> at
>> org.jboss.windup.exec.WindupProcessorImpl.execute(WindupProcessorImpl.java:128)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
>> at
>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
>> at
>> org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_974cc22d-87d3-4d6d-aabd-d7b720f1bef9.execute(WindupProcessorImpl_$$_javassist_974cc22d-87d3-4d6d-aabd-d7b720f1bef9.java)
>> at
>> org.jboss.windup.ui.WindupCommand.execute(WindupCommand.java:243)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
>> at
>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
>> at
>> org.jboss.windup.ui.WindupCommand_$$_javassist_7dfce685-96b6-42c2-9c63-b8d7e1d377d1.execute(WindupCommand_$$_javassist_7dfce685-96b6-42c2-9c63-b8d7e1d377d1.java)
>> at
>> org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:90)
>> at
>> org.jboss.forge.addon.shell.aesh.CommandAdapter.execute(CommandAdapter.java:82)
>> at
>> org.jboss.aesh.console.AeshConsoleImpl$AeshConsoleCallbackImpl.execute(AeshConsoleImpl.java:325)
>> at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:40)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:745)
>> Suppressed: com.thinkaurelius.titan.core.TitanException: Could
>> not execute operation due to backend exception
>> at
>> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:44)
>> at
>> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:144)
>> at
>> com.thinkaurelius.titan.diskstorage.configuration.backend.KCVSConfiguration.set(KCVSConfiguration.java:145)
>> at
>> com.thinkaurelius.titan.diskstorage.configuration.backend.KCVSConfiguration.set(KCVSConfiguration.java:122)
>> at
>> com.thinkaurelius.titan.diskstorage.configuration.backend.KCVSConfiguration.remove(KCVSConfiguration.java:163)
>> at
>> com.thinkaurelius.titan.diskstorage.configuration.ModifiableConfiguration.remove(ModifiableConfiguration.java:42)
>> at
>> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.shutdownInternal(StandardTitanGraph.java:169)
>> at
>> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.shutdown(StandardTitanGraph.java:158)
>> at
>> org.jboss.windup.graph.GraphContextImpl.close(GraphContextImpl.java:243)
>> at
>> org.jboss.windup.ui.WindupCommand.execute(WindupCommand.java:252)
>> ... 15 more
>> Caused by:
>> com.thinkaurelius.titan.diskstorage.PermanentBackendException: Could not
>> start BerkeleyJE transaction
>> at
>> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:144)
>> at
>> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:34)
>> at
>> com.thinkaurelius.titan.diskstorage.keycolumnvalue.keyvalue.OrderedKeyValueStoreManagerAdapter.beginTransaction(OrderedKeyValueStoreManagerAdapter.java:52)
>> at
>> com.thinkaurelius.titan.diskstorage.Backend$2.openTx(Backend.java:270)
>> at
>> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:131)
>> at
>> com.thinkaurelius.titan.diskstorage.util.BackendOperation$1.call(BackendOperation.java:147)
>> at
>> com.thinkaurelius.titan.diskstorage.util.BackendOperation.executeDirect(BackendOperation.java:56)
>> at
>> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:42)
>> ... 24 more
>> Caused by: com.sleepycat.je.EnvironmentFailureException: (JE
>> 5.0.73) Environment must be closed, caused by:
>> com.sleepycat.je.EnvironmentFailureException: Environment invalid
>> because of previous exception: (JE 5.0.73)
>> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
>> com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
>> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
>> java.io.FileNotFoundException:
>> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
>> (No space left on device) LOG_INTEGRITY: Log information is incorrect,
>> problem is likely persistent. UNEXPECTED_EXCEPTION_FATAL: Unexpected
>> internal Exception, unable to continue. Environment is invalid and must
>> be closed.
>> at
>> com.sleepycat.je.EnvironmentFailureException.wrapSelf(EnvironmentFailureException.java:196)
>> at
>> com.sleepycat.je.dbi.EnvironmentImpl.checkIfInvalid(EnvironmentImpl.java:1512)
>> at
>> com.sleepycat.je.Environment.checkEnv(Environment.java:2185)
>> at
>> com.sleepycat.je.Environment.beginTransactionInternal(Environment.java:1313)
>> at
>> com.sleepycat.je.Environment.beginTransaction(Environment.java:1284)
>> at
>> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:134)
>> ... 31 more
>> Caused by: com.sleepycat.je.EnvironmentFailureException:
>> Environment invalid because of previous exception: (JE 5.0.73)
>> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
>> com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
>> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
>> java.io.FileNotFoundException:
>> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
>> (No space left on device) LOG_INTEGRITY: Log information is incorrect,
>> problem is likely persistent. UNEXPECTED_EXCEPTION_FATAL: Unexpected
>> internal Exception, unable to continue. Environment is invalid and must
>> be closed.
>> at
>> com.sleepycat.je.EnvironmentFailureException.unexpectedException(EnvironmentFailureException.java:301)
>> at
>> com.sleepycat.je.log.LogManager.serialLogInternal(LogManager.java:505)
>> at
>> com.sleepycat.je.log.SyncedLogManager.serialLog(SyncedLogManager.java:42)
>> at
>> com.sleepycat.je.log.LogManager.multiLog(LogManager.java:395)
>> at com.sleepycat.je.log.LogManager.log(LogManager.java:335)
>> at com.sleepycat.je.tree.IN.logInternal(IN.java:3534)
>> at com.sleepycat.je.tree.IN.optionalLog(IN.java:3481)
>> at com.sleepycat.je.tree.IN.splitInternal(IN.java:2724)
>> at com.sleepycat.je.tree.IN.split(IN.java:2522)
>> at com.sleepycat.je.tree.Tree.forceSplit(Tree.java:1984)
>> at
>> com.sleepycat.je.tree.Tree.searchSubTreeSplitsAllowed(Tree.java:1767)
>> at
>> com.sleepycat.je.tree.Tree.searchSplitsAllowed(Tree.java:1318)
>> at
>> com.sleepycat.je.tree.Tree.findBinForInsert(Tree.java:2230)
>> at
>> com.sleepycat.je.dbi.CursorImpl.putInternal(CursorImpl.java:866)
>> at com.sleepycat.je.dbi.CursorImpl.put(CursorImpl.java:811)
>> at
>> com.sleepycat.je.Cursor.putAllowPhantoms(Cursor.java:2243)
>> at com.sleepycat.je.Cursor.putNoNotify(Cursor.java:2200)
>> at com.sleepycat.je.Cursor.putNotify(Cursor.java:2117)
>> at com.sleepycat.je.Cursor.putNoDups(Cursor.java:2052)
>> at com.sleepycat.je.Cursor.putInternal(Cursor.java:2020)
>> at
>> com.sleepycat.je.Database.putInternal(Database.java:1302)
>> at com.sleepycat.je.Database.put(Database.java:1172)
>> at
>> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEKeyValueStore.insert(BerkeleyJEKeyValueStore.java:194)
>> at
>> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEKeyValueStore.insert(BerkeleyJEKeyValueStore.java:183)
>> at
>> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.mutateMany(BerkeleyJEStoreManager.java:193)
>> at
>> com.thinkaurelius.titan.diskstorage.keycolumnvalue.keyvalue.OrderedKeyValueStoreManagerAdapter.mutateMany(OrderedKeyValueStoreManagerAdapter.java:100)
>> at
>> com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction$1.call(CacheTransaction.java:89)
>> at
>> com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction$1.call(CacheTransaction.java:86)
>> at
>> com.thinkaurelius.titan.diskstorage.util.BackendOperation.executeDirect(BackendOperation.java:56)
>> at
>> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:42)
>> at
>> com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction.persist(CacheTransaction.java:86)
>> at
>> com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction.flushInternal(CacheTransaction.java:140)
>> at
>> com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction.commit(CacheTransaction.java:197)
>> at
>> com.thinkaurelius.titan.diskstorage.BackendTransaction.commitStorage(BackendTransaction.java:117)
>> at
>> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.commit(StandardTitanGraph.java:670)
>> at
>> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1337)
>> at
>> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)
>> at
>> org.jboss.windup.config.RuleSubset.perform(RuleSubset.java:275)
>> at
>> org.jboss.windup.exec.WindupProcessorImpl.execute(WindupProcessorImpl.java:128)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
>> at
>> org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
>> at
>> org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
>> at
>> org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_974cc22d-87d3-4d6d-aabd-d7b720f1bef9.execute(WindupProcessorImpl_$$_javassist_974cc22d-87d3-4d6d-aabd-d7b720f1bef9.java)
>> at
>> org.jboss.windup.ui.WindupCommand.execute(WindupCommand.java:243)
>> ... 15 more
>> Caused by: com.sleepycat.je.EnvironmentFailureException: (JE
>> 5.0.73)
>> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
>> java.io.FileNotFoundException:
>> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
>> (No space left on device) LOG_INTEGRITY: Log information is incorrect,
>> problem is likely persistent.
>> at
>> com.sleepycat.je.log.FileManager$LogEndFileDescriptor.getWritableFile(FileManager.java:3009)
>> at
>> com.sleepycat.je.log.FileManager$LogEndFileDescriptor.access$200(FileManager.java:2710)
>> at
>> com.sleepycat.je.log.FileManager.writeLogBuffer(FileManager.java:1609)
>> at
>> com.sleepycat.je.log.LogBufferPool.writeBufferToFile(LogBufferPool.java:260)
>> at
>> com.sleepycat.je.log.LogBufferPool.getWriteBuffer(LogBufferPool.java:197)
>> at
>> com.sleepycat.je.log.LogManager.serialLogWork(LogManager.java:639)
>> at
>> com.sleepycat.je.log.LogManager.serialLogInternal(LogManager.java:493)
>> ... 61 more
>> Caused by: java.io.FileNotFoundException:
>> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
>> (No space left on device)
>> at java.io.RandomAccessFile.open(Native Method)
>> at
>> java.io.RandomAccessFile.<init>(RandomAccessFile.java:241)
>> at
>> java.io.RandomAccessFile.<init>(RandomAccessFile.java:122)
>> at
>> com.sleepycat.je.log.FileManager$DefaultRandomAccessFile.<init>(FileManager.java:3209)
>> at
>> com.sleepycat.je.log.FileManager$6.createFile(FileManager.java:3237)
>> at
>> com.sleepycat.je.log.FileManager.openFileHandle(FileManager.java:1280)
>> at
>> com.sleepycat.je.log.FileManager.makeFileHandle(FileManager.java:1247)
>> at
>> com.sleepycat.je.log.FileManager.access$1500(FileManager.java:75)
>> at
>> com.sleepycat.je.log.FileManager$LogEndFileDescriptor.getWritableFile(FileManager.java:2987)
>> ... 67 more
>> Caused by: com.thinkaurelius.titan.core.TitanException: Could not start
>> new transaction
>> at
>> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.newTransaction(StandardTitanGraph.java:276)
>> at
>> com.thinkaurelius.titan.graphdb.transaction.StandardTransactionBuilder.start(StandardTransactionBuilder.java:220)
>> at
>> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.newThreadBoundTransaction(StandardTitanGraph.java:265)
>> at
>> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.getAutoStartTx(TitanBlueprintsGraph.java:104)
>> at
>> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.addVertex(TitanBlueprintsGraph.java:155)
>> at
>> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.addVertex(TitanBlueprintsGraph.java:27)
>> at
>> com.tinkerpop.blueprints.util.wrappers.event.EventGraph.addVertex(EventGraph.java:95)
>> at com.tinkerpop.frames.FramedGraph.addVertex(FramedGraph.java:242)
>> at com.tinkerpop.frames.FramedGraph.addVertex(FramedGraph.java:258)
>> at
>> org.jboss.windup.graph.service.GraphService$3.execute(GraphService.java:92)
>> at
>> org.jboss.windup.graph.service.GraphService$3.execute(GraphService.java:88)
>> at
>> org.jboss.windup.util.ExecutionStatistics.performBenchmarked(ExecutionStatistics.java:90)
>> at
>> org.jboss.windup.graph.service.GraphService.create(GraphService.java:87)
>> at
>> org.jboss.windup.config.RuleSubset.logTimeTakenByRuleProvider(RuleSubset.java:120)
>> at org.jboss.windup.config.RuleSubset.perform(RuleSubset.java:283)
>> ... 25 more
>> Caused by:
>> com.thinkaurelius.titan.diskstorage.PermanentBackendException: Could not
>> start BerkeleyJE transaction
>> at
>> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:144)
>> at
>> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:34)
>> at
>> com.thinkaurelius.titan.diskstorage.keycolumnvalue.keyvalue.OrderedKeyValueStoreManagerAdapter.beginTransaction(OrderedKeyValueStoreManagerAdapter.java:52)
>> at
>> com.thinkaurelius.titan.diskstorage.Backend.beginTransaction(Backend.java:465)
>> at
>> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.openBackendTransaction(StandardTitanGraph.java:282)
>> at
>> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.newTransaction(StandardTitanGraph.java:272)
>> ... 39 more
>> Caused by: com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
>> Environment must be closed, caused by:
>> com.sleepycat.je.EnvironmentFailureException: Environment invalid
>> because of previous exception: (JE 5.0.73)
>> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
>> com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
>> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
>> java.io.FileNotFoundException:
>> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
>> (No space left on device) LOG_INTEGRITY: Log information is incorrect,
>> problem is likely persistent. UNEXPECTED_EXCEPTION_FATAL: Unexpected
>> internal Exception, unable to continue. Environment is invalid and must
>> be closed.
>> at
>> com.sleepycat.je.EnvironmentFailureException.wrapSelf(EnvironmentFailureException.java:196)
>> at
>> com.sleepycat.je.dbi.EnvironmentImpl.checkIfInvalid(EnvironmentImpl.java:1512)
>> at com.sleepycat.je.Environment.checkEnv(Environment.java:2185)
>> at
>> com.sleepycat.je.Environment.beginTransactionInternal(Environment.java:1313)
>> at
>> com.sleepycat.je.Environment.beginTransaction(Environment.java:1284)
>> at
>> com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager.beginTransaction(BerkeleyJEStoreManager.java:134)
>> ... 44 more
>> [CIRCULAR
>> REFERENCE:com.sleepycat.je.EnvironmentFailureException: Environment
>> invalid because of previous exception: (JE 5.0.73)
>> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
>> com.sleepycat.je.EnvironmentFailureException: (JE 5.0.73)
>> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph
>> java.io.FileNotFoundException:
>> /home/cloud-user/migr/apps/***/****Agent.ear.report/graph/titangraph/00000001.jdb
>> (No space left on device) LOG_INTEGRITY: Log information is incorrect,
>> problem is likely persistent. UNEXPECTED_EXCEPTION_FATAL: Unexpected
>> internal Exception, unable to continue. Environment is invalid and must
>> be closed.]
>> ***ERROR*** Error encountered while evaluating rule:
>> .addRule().when(Query.find(org.jboss.windup.rules.apps.xml.model.XmlFileModel).gremlin().has(fileName,EQUALS,pom.xml).as(default)).perform(Iteration.over(?).perform(ScanMavenProject)).withId("GeneratedID_DiscoverMavenProjectsRuleProvider_1")
>> From:
>> org.jboss.windup.rules.apps.java.scan.provider.DiscoverMavenProjectsRuleProvider
>> loaded from ModuleClassLoader for Module
>> "org.jboss.windup.rules.apps.windup-rules-java:2.3.0-SNAPSHOT_b5a66f3a-64a8-4833-89e3-3605a77cb86f"
>> from AddonModuleLoader
>> Defined in:
>> org.jboss.windup.rules.apps.java.scan.provider.DiscoverMavenProjectsRuleProvider.getConfiguration(DiscoverMavenProjectsRuleProvider.java:124)
>> [migr]$
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
From robb.greathouse at redhat.com Mon Mar 30 10:20:11 2015
From: robb.greathouse at redhat.com (Robb Greathouse)
Date: Mon, 30 Mar 2015 10:20:11 -0400 (EDT)
Subject: [windup-dev] Windup 2.2.0.Final Released
In-Reply-To: <CAEp_U4G0J018PXH8UcMgv6DyhTXy0t=ZxG7XDABuFhwiqWh7+g@mail.gmail.com>
References: <CAEp_U4H9NYdg2KPTTD2Da0E7acawwL=WXwA9E2R+vXanEY0HEA@mail.gmail.com>
<1176810837.4605771.1427482122124.JavaMail.zimbra@redhat.com>
<CAEp_U4G0J018PXH8UcMgv6DyhTXy0t=ZxG7XDABuFhwiqWh7+g@mail.gmail.com>
Message-ID: <1974715710.5470442.1427725211221.JavaMail.zimbra@redhat.com>
We still need to justify the additional 30 minutes to clients. At this point it is appears to give the same report that Windup .7 gave. What can we add to the report to demonstrate value added for those additional minute?
Robb Greathouse
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
----- Original Message -----
> Great! Thank you for confirming this! We definitely wanted to get these
> improvements into this release, so thank you for your patience as we sorted
> out some of the issues!
> ~Lincoln
> On Fri, Mar 27, 2015 at 2:48 PM, Robb Greathouse < robb.greathouse at redhat.com
> > wrote:
> > Cudos.
>
> > Running against the 300~mb test file and restricting it to look at packages
> > com.clarify it runs in about 40 minutes vs the old time of 20 hours plus.
> > Definite performance improvement.
>
> > Robb Greathouse
>
> > Middleware Business Unit
>
> > JBoss, a Division of Red Hat
>
> > cellphone 505-507-4906
>
> > > I am proud to announce the release of Windup 2.2.0.Final, which includes
> > > the
> > > following features/enhanvements/and bugfixes.
> >
>
> > > Great job team!
> >
>
> > > ~Lincoln
> >
>
> > > Bug
> >
>
> > > * [ WINDUP-510 ] - Build fails with BOM missing
> >
>
> > > * [ WINDUP-511 ] - Quickstarts tests fail with a NPE
> >
>
> > > * [ WINDUP-516 ] - [Performance] Multiple valueStores even if the rule
> > > does
> > > not use parameters
> >
>
> > > * [ WINDUP-517 ] - Application Index page lacks technology list and
> > > effort
> > > information
> >
>
> > > * [ WINDUP-518 ] - XML Handlers do not support nested rules
> >
>
> > > * [ WINDUP-524 ] - Fix the cyclic dependency between windup and
> > > windup-rulesets
> >
>
> > > * [ WINDUP-542 ] - Fix severe regression in AST performance
> >
>
> > > * [ WINDUP-544 ] - StackOverflowException when generating Application
> > > report
> >
>
> > > Enhancement
> >
>
> > > * [ WINDUP-409 ] - Allow rules metadata to be specified with annotations
> > > -
> > > @Rules( phase = ..., ...)
> >
>
> > > * [ WINDUP-470 ] - Classes in java.lang package may differ in how they
> > > are
> > > parsed
> >
>
> > > * [ WINDUP-506 ] - Identify Archives Ruleset: Improve memory footprint
> >
>
> > > * [ WINDUP-508 ] - WindupRuleProvider should contain a location/origin
> > > field
> > > (to indicate where it was defined)
> >
>
> > > * [ WINDUP-515 ] - Add Severity to Hint
> >
>
> > > * [ WINDUP-520 ] - Rule Externalization - Introduce a Rule, RuleProvider
> > > and
> > > RulesetMetadata API
> >
>
> > > * [ WINDUP-529 ] - Performance issue: Query requires iterating over all
> > > vertices [(ClassificationModel:classification = ...)]
> >
>
> > > Feature Request
> >
>
> > > * [ WINDUP-402 ] - Change ruleset category metadata to tag-like system
> > > (make
> > > it a set of strings)
> >
>
> > > * [ WINDUP-521 ] - Rule Externalization - Create XML Handlers for Rule
> > > metadata
> >
>
> > > * [ WINDUP-522 ] - Rule Externalization - Create user-interface for
> > > selecting
> > > source/target platforms
> >
>
> > > * [ WINDUP-523 ] - Rule Externalization - Allow filtering of
> > > RuleProviders
> > > by
> > > tags (categories)
> >
>
> > > Task
> >
>
> > > * [ WINDUP-512 ] - Rename Implicit to Dependent
> >
>
> > > * [ WINDUP-513 ] - Phase pseudo-RuleProviders to have ~Phase suffix
> >
>
> > > * [ WINDUP-530 ] - Rename the module "utils" to "windup-utils"
> >
>
> > > Sub-task
> >
>
> > > * [ WINDUP-464 ] - Expand all addons with simple layout to use full
> > > api/impl/tests structure
> >
>
> > > * [ WINDUP-465 ] - Review all rules, organize into an external
> > > repository,
> > > and add useful hint information with links to knowledge articles
> >
>
> > > --
> >
>
> > > Lincoln Baxter, III
> >
>
> > > http://ocpsoft.org
> >
>
> > > "Simpler is better."
> >
>
> --
> 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/20150330/57d4c452/attachment.html
From ozizka at redhat.com Mon Mar 30 14:10:09 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 30 Mar 2015 20:10:09 +0200
Subject: [windup-dev] Windup 2.2.0.Final Released
In-Reply-To: <1974715710.5470442.1427725211221.JavaMail.zimbra@redhat.com>
References: <CAEp_U4H9NYdg2KPTTD2Da0E7acawwL=WXwA9E2R+vXanEY0HEA@mail.gmail.com> <1176810837.4605771.1427482122124.JavaMail.zimbra@redhat.com> <CAEp_U4G0J018PXH8UcMgv6DyhTXy0t=ZxG7XDABuFhwiqWh7+g@mail.gmail.com>
<1974715710.5470442.1427725211221.JavaMail.zimbra@redhat.com>
Message-ID: <55199181.9080605@redhat.com>
1) More complex rules querying more complex Java constructs / transitive
relations etc.
2) Easier and more powerful rules.
Since we first only converted the Windup 1 rules, Windup 2 doesn't give
much over that.
I believe it will as the new rules start coming.
Ondra
On 30.3.2015 16:20, Robb Greathouse wrote:
> We still need to justify the additional 30 minutes to clients. At
> this point it is appears to give the same report that Windup .7 gave.
> What can we add to the report to demonstrate value added for those
> additional minute?
>
>
> Robb Greathouse
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
>
> ------------------------------------------------------------------------
>
> Great! Thank you for confirming this! We definitely wanted to get
> these improvements into this release, so thank you for your
> patience as we sorted out some of the issues!
>
> ~Lincoln
>
> On Fri, Mar 27, 2015 at 2:48 PM, Robb Greathouse
> <robb.greathouse at redhat.com <mailto:robb.greathouse at redhat.com>>
> wrote:
>
> Cudos.
>
> Running against the 300~mb test file and restricting it to
> look at packages com.clarify it runs in about 40 minutes vs
> the old time of 20 hours plus. Definite performance improvement.
>
>
>
> Robb Greathouse
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906 <tel:505-507-4906>
>
> ------------------------------------------------------------------------
>
>
> I am proud to announce the release of Windup
> 2.2.0.Final, which includes the following
> features/enhanvements/and bugfixes.
>
> Great job team!
>
> ~Lincoln
>
>
> Bug
>
> * [WINDUP-510
> <https://issues.jboss.org/browse/WINDUP-510>] - Build
> fails with BOM missing
> * [WINDUP-511
> <https://issues.jboss.org/browse/WINDUP-511>] -
> Quickstarts tests fail with a NPE
> * [WINDUP-516
> <https://issues.jboss.org/browse/WINDUP-516>] -
> [Performance] Multiple valueStores even if the rule
> does not use parameters
> * [WINDUP-517
> <https://issues.jboss.org/browse/WINDUP-517>] -
> Application Index page lacks technology list and
> effort information
> * [WINDUP-518
> <https://issues.jboss.org/browse/WINDUP-518>] - XML
> Handlers do not support nested rules
> * [WINDUP-524
> <https://issues.jboss.org/browse/WINDUP-524>] - Fix
> the cyclic dependency between windup and windup-rulesets
> * [WINDUP-542
> <https://issues.jboss.org/browse/WINDUP-542>] - Fix
> severe regression in AST performance
> * [WINDUP-544
> <https://issues.jboss.org/browse/WINDUP-544>] -
> StackOverflowException when generating Application report
>
>
> Enhancement
>
> * [WINDUP-409
> <https://issues.jboss.org/browse/WINDUP-409>] - Allow
> rules metadata to be specified with annotations -
> @Rules( phase = ..., ...)
> * [WINDUP-470
> <https://issues.jboss.org/browse/WINDUP-470>] -
> Classes in java.lang package may differ in how they
> are parsed
> * [WINDUP-506
> <https://issues.jboss.org/browse/WINDUP-506>] -
> Identify Archives Ruleset: Improve memory footprint
> * [WINDUP-508
> <https://issues.jboss.org/browse/WINDUP-508>] -
> WindupRuleProvider should contain a location/origin
> field (to indicate where it was defined)
> * [WINDUP-515
> <https://issues.jboss.org/browse/WINDUP-515>] - Add
> Severity to Hint
> * [WINDUP-520
> <https://issues.jboss.org/browse/WINDUP-520>] - Rule
> Externalization - Introduce a Rule, RuleProvider and
> RulesetMetadata API
> * [WINDUP-529
> <https://issues.jboss.org/browse/WINDUP-529>] -
> Performance issue: Query requires iterating over all
> vertices [(ClassificationModel:classification = ...)]
>
>
> Feature Request
>
> * [WINDUP-402
> <https://issues.jboss.org/browse/WINDUP-402>] - Change
> ruleset category metadata to tag-like system (make it
> a set of strings)
> * [WINDUP-521
> <https://issues.jboss.org/browse/WINDUP-521>] - Rule
> Externalization - Create XML Handlers for Rule metadata
> * [WINDUP-522
> <https://issues.jboss.org/browse/WINDUP-522>] - Rule
> Externalization - Create user-interface for selecting
> source/target platforms
> * [WINDUP-523
> <https://issues.jboss.org/browse/WINDUP-523>] - Rule
> Externalization - Allow filtering of RuleProviders by
> tags (categories)
>
>
> Task
>
> * [WINDUP-512
> <https://issues.jboss.org/browse/WINDUP-512>] - Rename
> Implicit to Dependent
> * [WINDUP-513
> <https://issues.jboss.org/browse/WINDUP-513>] - Phase
> pseudo-RuleProviders to have ~Phase suffix
> * [WINDUP-530
> <https://issues.jboss.org/browse/WINDUP-530>] - Rename
> the module "utils" to "windup-utils"
>
>
> Sub-task
>
> * [WINDUP-464
> <https://issues.jboss.org/browse/WINDUP-464>] - Expand
> all addons with simple layout to use full
> api/impl/tests structure
> * [WINDUP-465
> <https://issues.jboss.org/browse/WINDUP-465>] - Review
> all rules, organize into an external repository, and
> add useful hint information with links to knowledge
> articles
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150330/31ca5b90/attachment-0001.html
From bdavis at redhat.com Mon Mar 30 15:05:28 2015
From: bdavis at redhat.com (Brad Davis)
Date: Mon, 30 Mar 2015 15:05:28 -0400 (EDT)
Subject: [windup-dev] Windup 2.2.0.Final Released
In-Reply-To: <55199181.9080605@redhat.com>
References: <CAEp_U4H9NYdg2KPTTD2Da0E7acawwL=WXwA9E2R+vXanEY0HEA@mail.gmail.com>
<1176810837.4605771.1427482122124.JavaMail.zimbra@redhat.com>
<CAEp_U4G0J018PXH8UcMgv6DyhTXy0t=ZxG7XDABuFhwiqWh7+g@mail.gmail.com>
<1974715710.5470442.1427725211221.JavaMail.zimbra@redhat.com>
<55199181.9080605@redhat.com>
Message-ID: <490177770.7328197.1427742328851.JavaMail.zimbra@redhat.com>
This would require reports, but we should have the info for these things below that we wouldn't have had info for in Windup 1:
We can push the functionality for EJB reporting & Resource reporting --- Database and Queues. Assist folks with generating them in Jboss (either linking to docs for setting up database or JMS queues or the IBM MQ Resource adapter). Those tasks would show the value clearly.
* Resources we should generate the XML chunk that should go in JBoss's Standalone.xml if possible, maybe JBoss CLI as well & link to relevant JBoss documentation (JMS or Datasource Setup)
* IBM MQ Queues would indicate we need to setup the IBM MQ Resource Adapter and link to the product docs on doing so with JBoss.
* If an EJB is tied to a Queue, we have that info now in Windup.
* If a message listener is bound in Spring to a Queue, we can get that info in Windup.
* If a Hibernate file leverages a Oracle Dialect & references a named JNDI datasource, we know it needs to be setup in JBoss.
* If the code manually looks up a datasource, we could write an extractor to pull that out into the graph as well.
Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Ondrej Zizka" <ozizka at redhat.com>
To: windup-dev at lists.jboss.org
Sent: Monday, March 30, 2015 2:10:09 PM
Subject: Re: [windup-dev] Windup 2.2.0.Final Released
1) More complex rules querying more complex Java constructs / transitive relations etc.
2) Easier and more powerful rules.
Since we first only converted the Windup 1 rules, Windup 2 doesn't give much over that.
I believe it will as the new rules start coming.
Ondra
On 30.3.2015 16:20, Robb Greathouse wrote:
We still need to justify the additional 30 minutes to clients. At this point it is appears to give the same report that Windup .7 gave. What can we add to the report to demonstrate value added for those additional minute?
Robb Greathouse
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
Great! Thank you for confirming this! We definitely wanted to get these improvements into this release, so thank you for your patience as we sorted out some of the issues!
~Lincoln
On Fri, Mar 27, 2015 at 2:48 PM, Robb Greathouse < robb.greathouse at redhat.com > wrote:
Cudos.
Running against the 300~mb test file and restricting it to look at packages com.clarify it runs in about 40 minutes vs the old time of 20 hours plus. Definite performance improvement.
Robb Greathouse
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
I am proud to announce the release of Windup 2.2.0.Final, which includes the following features/enhanvements/and bugfixes.
Great job team!
~Lincoln
Bug
* [ WINDUP-510 ] - Build fails with BOM missing
* [ WINDUP-511 ] - Quickstarts tests fail with a NPE
* [ WINDUP-516 ] - [Performance] Multiple valueStores even if the rule does not use parameters
* [ WINDUP-517 ] - Application Index page lacks technology list and effort information
* [ WINDUP-518 ] - XML Handlers do not support nested rules
* [ WINDUP-524 ] - Fix the cyclic dependency between windup and windup-rulesets
* [ WINDUP-542 ] - Fix severe regression in AST performance
* [ WINDUP-544 ] - StackOverflowException when generating Application report
Enhancement
* [ WINDUP-409 ] - Allow rules metadata to be specified with annotations - @Rules( phase = ..., ...)
* [ WINDUP-470 ] - Classes in java.lang package may differ in how they are parsed
* [ WINDUP-506 ] - Identify Archives Ruleset: Improve memory footprint
* [ WINDUP-508 ] - WindupRuleProvider should contain a location/origin field (to indicate where it was defined)
* [ WINDUP-515 ] - Add Severity to Hint
* [ WINDUP-520 ] - Rule Externalization - Introduce a Rule, RuleProvider and RulesetMetadata API
* [ WINDUP-529 ] - Performance issue: Query requires iterating over all vertices [(ClassificationModel:classification = ...)]
Feature Request
* [ WINDUP-402 ] - Change ruleset category metadata to tag-like system (make it a set of strings)
* [ WINDUP-521 ] - Rule Externalization - Create XML Handlers for Rule metadata
* [ WINDUP-522 ] - Rule Externalization - Create user-interface for selecting source/target platforms
* [ WINDUP-523 ] - Rule Externalization - Allow filtering of RuleProviders by tags (categories)
Task
* [ WINDUP-512 ] - Rename Implicit to Dependent
* [ WINDUP-513 ] - Phase pseudo-RuleProviders to have ~Phase suffix
* [ WINDUP-530 ] - Rename the module "utils" to "windup-utils"
Sub-task
* [ WINDUP-464 ] - Expand all addons with simple layout to use full api/impl/tests structure
* [ WINDUP-465 ] - Review all rules, organize into an external repository, and add useful hint information with links to knowledge articles
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list windup-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
From robb.greathouse at redhat.com Mon Mar 30 15:26:07 2015
From: robb.greathouse at redhat.com (Robb Greathouse)
Date: Mon, 30 Mar 2015 15:26:07 -0400 (EDT)
Subject: [windup-dev] Windup 2.2.0.Final Released
In-Reply-To: <55199181.9080605@redhat.com>
References: <CAEp_U4H9NYdg2KPTTD2Da0E7acawwL=WXwA9E2R+vXanEY0HEA@mail.gmail.com>
<1176810837.4605771.1427482122124.JavaMail.zimbra@redhat.com>
<CAEp_U4G0J018PXH8UcMgv6DyhTXy0t=ZxG7XDABuFhwiqWh7+g@mail.gmail.com>
<1974715710.5470442.1427725211221.JavaMail.zimbra@redhat.com>
<55199181.9080605@redhat.com>
Message-ID: <1034913801.5686464.1427743567569.JavaMail.zimbra@redhat.com>
Hi,
Yes, exactly. We need to come up with rules and reports that can take advantage of the data graph and other features.
One thought I had that got shot down; but might still be possible would be to use the complex graph to type whole classes or packages by the complexity of migration activities that would required to migrate. We could have a report that grouped packages and classes by the migration work to be done. So, JSP pages would be grouped together and note that knowledge of Tomahawk would also be necessary. Classes extending the same WebSphere base class could be reported together, etc.
We need some concrete use cases.
Robb Greathouse
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
----- Original Message -----
> 1) More complex rules querying more complex Java constructs / transitive
> relations etc.
> 2) Easier and more powerful rules.
> Since we first only converted the Windup 1 rules, Windup 2 doesn't give much
> over that.
> I believe it will as the new rules start coming.
> Ondra
> On 30.3.2015 16:20, Robb Greathouse wrote:
> > We still need to justify the additional 30 minutes to clients. At this
> > point
> > it is appears to give the same report that Windup .7 gave. What can we add
> > to the report to demonstrate value added for those additional minute?
>
> > Robb Greathouse
>
> > Middleware Business Unit
>
> > JBoss, a Division of Red Hat
>
> > cellphone 505-507-4906
>
> > ----- Original Message -----
>
> > > Great! Thank you for confirming this! We definitely wanted to get these
> > > improvements into this release, so thank you for your patience as we
> > > sorted
> > > out some of the issues!
> >
>
> > > ~Lincoln
> >
>
> > > On Fri, Mar 27, 2015 at 2:48 PM, Robb Greathouse <
> > > robb.greathouse at redhat.com
> > > > wrote:
> >
>
> > > > Cudos.
> > >
> >
>
> > > > Running against the 300~mb test file and restricting it to look at
> > > > packages
> > > > com.clarify it runs in about 40 minutes vs the old time of 20 hours
> > > > plus.
> > > > Definite performance improvement.
> > >
> >
>
> > > > Robb Greathouse
> > >
> >
>
> > > > Middleware Business Unit
> > >
> >
>
> > > > JBoss, a Division of Red Hat
> > >
> >
>
> > > > cellphone 505-507-4906
> > >
> >
>
> > > > > I am proud to announce the release of Windup 2.2.0.Final, which
> > > > > includes
> > > > > the
> > > > > following features/enhanvements/and bugfixes.
> > > >
> > >
> >
>
> > > > > Great job team!
> > > >
> > >
> >
>
> > > > > ~Lincoln
> > > >
> > >
> >
>
> > > > > Bug
> > > >
> > >
> >
>
> > > > > * [ WINDUP-510 ] - Build fails with BOM missing
> > > >
> > >
> >
>
> > > > > * [ WINDUP-511 ] - Quickstarts tests fail with a NPE
> > > >
> > >
> >
>
> > > > > * [ WINDUP-516 ] - [Performance] Multiple valueStores even if the
> > > > > rule
> > > > > does
> > > > > not use parameters
> > > >
> > >
> >
>
> > > > > * [ WINDUP-517 ] - Application Index page lacks technology list and
> > > > > effort
> > > > > information
> > > >
> > >
> >
>
> > > > > * [ WINDUP-518 ] - XML Handlers do not support nested rules
> > > >
> > >
> >
>
> > > > > * [ WINDUP-524 ] - Fix the cyclic dependency between windup and
> > > > > windup-rulesets
> > > >
> > >
> >
>
> > > > > * [ WINDUP-542 ] - Fix severe regression in AST performance
> > > >
> > >
> >
>
> > > > > * [ WINDUP-544 ] - StackOverflowException when generating Application
> > > > > report
> > > >
> > >
> >
>
> > > > > Enhancement
> > > >
> > >
> >
>
> > > > > * [ WINDUP-409 ] - Allow rules metadata to be specified with
> > > > > annotations
> > > > > -
> > > > > @Rules( phase = ..., ...)
> > > >
> > >
> >
>
> > > > > * [ WINDUP-470 ] - Classes in java.lang package may differ in how
> > > > > they
> > > > > are
> > > > > parsed
> > > >
> > >
> >
>
> > > > > * [ WINDUP-506 ] - Identify Archives Ruleset: Improve memory
> > > > > footprint
> > > >
> > >
> >
>
> > > > > * [ WINDUP-508 ] - WindupRuleProvider should contain a
> > > > > location/origin
> > > > > field
> > > > > (to indicate where it was defined)
> > > >
> > >
> >
>
> > > > > * [ WINDUP-515 ] - Add Severity to Hint
> > > >
> > >
> >
>
> > > > > * [ WINDUP-520 ] - Rule Externalization - Introduce a Rule,
> > > > > RuleProvider
> > > > > and
> > > > > RulesetMetadata API
> > > >
> > >
> >
>
> > > > > * [ WINDUP-529 ] - Performance issue: Query requires iterating over
> > > > > all
> > > > > vertices [(ClassificationModel:classification = ...)]
> > > >
> > >
> >
>
> > > > > Feature Request
> > > >
> > >
> >
>
> > > > > * [ WINDUP-402 ] - Change ruleset category metadata to tag-like
> > > > > system
> > > > > (make
> > > > > it a set of strings)
> > > >
> > >
> >
>
> > > > > * [ WINDUP-521 ] - Rule Externalization - Create XML Handlers for
> > > > > Rule
> > > > > metadata
> > > >
> > >
> >
>
> > > > > * [ WINDUP-522 ] - Rule Externalization - Create user-interface for
> > > > > selecting
> > > > > source/target platforms
> > > >
> > >
> >
>
> > > > > * [ WINDUP-523 ] - Rule Externalization - Allow filtering of
> > > > > RuleProviders
> > > > > by
> > > > > tags (categories)
> > > >
> > >
> >
>
> > > > > Task
> > > >
> > >
> >
>
> > > > > * [ WINDUP-512 ] - Rename Implicit to Dependent
> > > >
> > >
> >
>
> > > > > * [ WINDUP-513 ] - Phase pseudo-RuleProviders to have ~Phase suffix
> > > >
> > >
> >
>
> > > > > * [ WINDUP-530 ] - Rename the module "utils" to "windup-utils"
> > > >
> > >
> >
>
> > > > > Sub-task
> > > >
> > >
> >
>
> > > > > * [ WINDUP-464 ] - Expand all addons with simple layout to use full
> > > > > api/impl/tests structure
> > > >
> > >
> >
>
> > > > > * [ WINDUP-465 ] - Review all rules, organize into an external
> > > > > repository,
> > > > > and add useful hint information with links to knowledge articles
> > > >
> > >
> >
>
> > > > > --
> > > >
> > >
> >
>
> > > > > Lincoln Baxter, III
> > > >
> > >
> >
>
> > > > > http://ocpsoft.org
> > > >
> > >
> >
>
> > > > > "Simpler is better."
> > > >
> > >
> >
>
> > > --
> >
>
> > > Lincoln Baxter, III
> >
>
> > > http://ocpsoft.org
> >
>
> > > "Simpler is better."
> >
>
> > > _______________________________________________
> >
>
> > > windup-dev mailing list
> >
>
> > > windup-dev at lists.jboss.org
> >
>
> > > https://lists.jboss.org/mailman/listinfo/windup-dev
> >
>
> > _______________________________________________
>
> > windup-dev mailing list windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150330/5c4f8c9c/attachment-0001.html
From lincolnbaxter at gmail.com Tue Mar 31 11:53:41 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 31 Mar 2015 11:53:41 -0400
Subject: [windup-dev] Windup 2.2.0.Final Released
In-Reply-To: <1034913801.5686464.1427743567569.JavaMail.zimbra@redhat.com>
References: <CAEp_U4H9NYdg2KPTTD2Da0E7acawwL=WXwA9E2R+vXanEY0HEA@mail.gmail.com>
<1176810837.4605771.1427482122124.JavaMail.zimbra@redhat.com>
<CAEp_U4G0J018PXH8UcMgv6DyhTXy0t=ZxG7XDABuFhwiqWh7+g@mail.gmail.com>
<1974715710.5470442.1427725211221.JavaMail.zimbra@redhat.com>
<55199181.9080605@redhat.com>
<1034913801.5686464.1427743567569.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4ErXEkTfseHhgxEQ6DcXUXL4BSW0gcwxWvEb51C0JhTRw@mail.gmail.com>
>> We need some concrete use cases.
+1
On Mon, Mar 30, 2015 at 3:26 PM, Robb Greathouse <robb.greathouse at redhat.com
> wrote:
> Hi,
>
> Yes, exactly. We need to come up with rules and reports that can take
> advantage of the data graph and other features.
>
> One thought I had that got shot down; but might still be possible would be
> to use the complex graph to type whole classes or packages by the
> complexity of migration activities that would required to migrate. We
> could have a report that grouped packages and classes by the migration work
> to be done. So, JSP pages would be grouped together and note that
> knowledge of Tomahawk would also be necessary. Classes extending the same
> WebSphere base class could be reported together, etc.
>
> We need some concrete use cases.
>
>
> Robb Greathouse
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
>
> ------------------------------
>
> 1) More complex rules querying more complex Java constructs / transitive
> relations etc.
> 2) Easier and more powerful rules.
>
> Since we first only converted the Windup 1 rules, Windup 2 doesn't give
> much over that.
> I believe it will as the new rules start coming.
>
> Ondra
>
>
> On 30.3.2015 16:20, Robb Greathouse wrote:
>
> We still need to justify the additional 30 minutes to clients. At this
> point it is appears to give the same report that Windup .7 gave. What can
> we add to the report to demonstrate value added for those additional minute?
>
>
> Robb Greathouse
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
>
> ------------------------------
>
> Great! Thank you for confirming this! We definitely wanted to get these
> improvements into this release, so thank you for your patience as we sorted
> out some of the issues!
>
> ~Lincoln
>
> On Fri, Mar 27, 2015 at 2:48 PM, Robb Greathouse <
> robb.greathouse at redhat.com> wrote:
>
>> Cudos.
>>
>> Running against the 300~mb test file and restricting it to look at
>> packages com.clarify it runs in about 40 minutes vs the old time of 20
>> hours plus. Definite performance improvement.
>>
>>
>>
>> Robb Greathouse
>> Middleware Business Unit
>> JBoss, a Division of Red Hat
>> cellphone 505-507-4906
>>
>> ------------------------------
>>
>> I am proud to announce the release of Windup 2.2.0.Final, which
>> includes the following features/enhanvements/and bugfixes.
>> Great job team!
>>
>> ~Lincoln
>> Bug
>>
>> - [WINDUP-510 <https://issues.jboss.org/browse/WINDUP-510>] - Build
>> fails with BOM missing
>> - [WINDUP-511 <https://issues.jboss.org/browse/WINDUP-511>] -
>> Quickstarts tests fail with a NPE
>> - [WINDUP-516 <https://issues.jboss.org/browse/WINDUP-516>] -
>> [Performance] Multiple valueStores even if the rule does not use parameters
>> - [WINDUP-517 <https://issues.jboss.org/browse/WINDUP-517>] -
>> Application Index page lacks technology list and effort information
>> - [WINDUP-518 <https://issues.jboss.org/browse/WINDUP-518>] - XML
>> Handlers do not support nested rules
>> - [WINDUP-524 <https://issues.jboss.org/browse/WINDUP-524>] - Fix the
>> cyclic dependency between windup and windup-rulesets
>> - [WINDUP-542 <https://issues.jboss.org/browse/WINDUP-542>] - Fix
>> severe regression in AST performance
>> - [WINDUP-544 <https://issues.jboss.org/browse/WINDUP-544>] -
>> StackOverflowException when generating Application report
>>
>> Enhancement
>>
>> - [WINDUP-409 <https://issues.jboss.org/browse/WINDUP-409>] - Allow
>> rules metadata to be specified with annotations - @Rules( phase = ..., ...)
>> - [WINDUP-470 <https://issues.jboss.org/browse/WINDUP-470>] - Classes
>> in java.lang package may differ in how they are parsed
>> - [WINDUP-506 <https://issues.jboss.org/browse/WINDUP-506>] -
>> Identify Archives Ruleset: Improve memory footprint
>> - [WINDUP-508 <https://issues.jboss.org/browse/WINDUP-508>] -
>> WindupRuleProvider should contain a location/origin field (to indicate
>> where it was defined)
>> - [WINDUP-515 <https://issues.jboss.org/browse/WINDUP-515>] - Add
>> Severity to Hint
>> - [WINDUP-520 <https://issues.jboss.org/browse/WINDUP-520>] - Rule
>> Externalization - Introduce a Rule, RuleProvider and RulesetMetadata API
>> - [WINDUP-529 <https://issues.jboss.org/browse/WINDUP-529>] -
>> Performance issue: Query requires iterating over all vertices
>> [(ClassificationModel:classification = ...)]
>>
>> Feature Request
>>
>> - [WINDUP-402 <https://issues.jboss.org/browse/WINDUP-402>] - Change
>> ruleset category metadata to tag-like system (make it a set of strings)
>> - [WINDUP-521 <https://issues.jboss.org/browse/WINDUP-521>] - Rule
>> Externalization - Create XML Handlers for Rule metadata
>> - [WINDUP-522 <https://issues.jboss.org/browse/WINDUP-522>] - Rule
>> Externalization - Create user-interface for selecting source/target
>> platforms
>> - [WINDUP-523 <https://issues.jboss.org/browse/WINDUP-523>] - Rule
>> Externalization - Allow filtering of RuleProviders by tags (categories)
>>
>> Task
>>
>> - [WINDUP-512 <https://issues.jboss.org/browse/WINDUP-512>] - Rename
>> Implicit to Dependent
>> - [WINDUP-513 <https://issues.jboss.org/browse/WINDUP-513>] - Phase
>> pseudo-RuleProviders to have ~Phase suffix
>> - [WINDUP-530 <https://issues.jboss.org/browse/WINDUP-530>] - Rename
>> the module "utils" to "windup-utils"
>>
>> Sub-task
>>
>> - [WINDUP-464 <https://issues.jboss.org/browse/WINDUP-464>] - Expand
>> all addons with simple layout to use full api/impl/tests structure
>> - [WINDUP-465 <https://issues.jboss.org/browse/WINDUP-465>] - Review
>> all rules, organize into an external repository, and add useful hint
>> information with links to knowledge articles
>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>>
>>
>>
>
>
> --
> 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 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
>
>
>
> _______________________________________________
> 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/20150331/a764107d/attachment.html
From samueltauil at icloud.com Mon Mar 2 08:12:39 2015
From: samueltauil at icloud.com (Samuel Tauil)
Date: Mon, 02 Mar 2015 13:12:39 -0000
Subject: [windup-dev] Unclassified Files
Message-ID: <B3BEB6B9-CA75-41C1-A7C0-3C945CE51E72@icloud.com>
Hi,
I understand the Unclassified Files section in the report as a list of all files which were decompiled properly by Procyon but weren't captured by any rules, so the user can check and see which resources need to be checked again and generate specific rules or not. Is that correct?
Thanks
Samuel
From dhodge at redhat.com Mon Mar 16 10:41:35 2015
From: dhodge at redhat.com (Dan Hodge)
Date: Mon, 16 Mar 2015 14:41:35 -0000
Subject: [windup-dev] Windup 2.x for oracle service bus??
In-Reply-To: <28231849.163.1426516837062.JavaMail.dhodge@dhodge.csb>
Message-ID: <14608098.167.1426516891652.JavaMail.dhodge@dhodge.csb>
anyone,
does windup 2.x have any rules for the oracle service bus artifacts? do we have any experience with the oracle service bus artifacts?
Dan
Dan Hodge
Sr. Middleware Solutions Architect
dhodge at redhat.com
+1 (416) 587-2647 (Mobile)
http://www.redhat.com/jboss/getunstuck/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150316/fddedbec/attachment-0001.html