Ruleset Location API
by Ian Tewksbury
All,
Is there an API for specifying an extra location for loading Windup rules?
I want to add a preference dialog to the Eclipse plugin to allow the user to select at least one if not multiple additional locations to load rule sets from.
~Ian
9 years, 8 months
Re: [windup-dev] Furnace not finding Windup FileService
by Lincoln Baxter, III
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(a)redhat.com>
To: "Lincoln Baxter" <lbaxter(a)redhat.com>
Cc: "Robb Greathouse" <robb.greathouse(a)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(a)redhat.com>
To: "Lincoln Baxter" <lbaxter(a)redhat.com>
Cc: "Robb Greathouse" <robb.greathouse(a)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(a)redhat.com>
To: "Lincoln Baxter" <lbaxter(a)redhat.com>
Cc: "Robb Greathouse" <robb.greathouse(a)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/... , 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(a)redhat.com>
To: "Lincoln Baxter" <lbaxter(a)redhat.com>, "Robb Greathouse" <robb.greathouse(a)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
9 years, 8 months
Windup Meeting Minutes - 2015-04-22
by Lincoln Baxter, III
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup....
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup....
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup....
Meeting summary
---------------
* Agenda (lincolnthree, 14:05:21)
* Status Reports (lincolnthree, 14:07:04)
* Update windup.jboss.org for Windup 2 (fix download links and guides)
(lincolnthree, 14:10:45)
* Reviewed several PRs and provided feedback (lincolnthree, 14:10:45)
* Worked on FURNACE-43 to simplify test case authoring (lincolnthree,
14:10:45)
* LINK:
https://github.com/forge/furnace-cdi/blob/4ef5c983947b6221334747dcca1ddb3...
(lincolnthree, 14:12:26)
* Server identification implementation (ozizka, 14:17:50)
* and documenting that on wiki. (ozizka, 14:17:50)
* EAP CLI rules syntax consderation. I'll work with Eduardo to make
sure we reuse whatever we can from the CLI API and utils, and his
current work. (ozizka, 14:17:50)
* Model update for FileModel related stuff - PathModel,
DirectoryModel, FileModel, ResourceModel, UserPathInputModel.
(ozizka, 14:17:50)
* LINK: https://issues.jboss.org/browse/MIGR-229 (ozizka, 14:21:07)
* I am working on updating, again, after gastaldi pointed out to a
problem that will occur on the windows side. FORGE-2283/MIGR-198
(mbriskar_, 14:32:00)
* WINDUP-528 (quieter logging for unparsable xml files), WINDUP-531
(parsing errors not appearing in the report), and WINDUP-561 (crash
on an invalid pom) (jsightler, 14:33:41)
* Priorities (lincolnthree, 14:33:57)
* I have also spent some time researching AST performance and will be
working on some threading fixes this week. (jsightler, 14:34:11)
* Priorities unchanged - Performance, Server config migration, Eclipse
Plugin, Quickstarts & Tutorials (lincolnthree, 14:34:32)
* Documentation of Rules (lincolnthree, 14:34:38)
* LINK: https://github.com/windup/windup/wiki/Ruleset:-%28template%29
(ozizka, 14:36:11)
* LINK: https://github.com/windup/windup/wiki/Ruleset-Ruleset-Template
(ozizka, 14:36:54)
* Two audiences: 1) Users 2) Devs. (ozizka, 14:47:39)
* For users: Only the Ruleset level can be sufficient, with a brief
description of the feature it does, (ozizka, 14:48:16)
* with the input it has - WindupConfigurationOption's - (ozizka,
14:48:39)
* and the output - probably a list of reports and examples. (ozizka,
14:49:20)
* ACTION: We may create a prototype of that on Wiki. (ozizka,
14:49:34)
* For devs, it would be nice to have a generated report of Rulesets
which would contain RuleProviders and the Models and the Options
(ozizka, 14:51:11)
* Similar to this template:
https://github.com/windup/windup/wiki/Ruleset-Ruleset-Template
(ozizka, 14:51:30)
* (not critical, TBD later) (ozizka, 14:51:37)
* (2018 :) (ozizka, 14:51:48)
* Procyon AST (lincolnthree, 14:52:08)
* .class -> Procyon objects -> AST -> .java -> Eclipse JDT -> AST
(ozizka, 14:54:04)
* that's what's happening when we are decompiling (ozizka, 14:54:23)
* and then evaluating the java files (ozizka, 14:54:41)
* ACTION: I'll try to measure how much time which part of that process
takes to see if it's worth of furtherinvestigation (ozizka,
15:05:26)
* Running app and server rules togheter (ozizka, 15:11:51)
* The addons for app migration will be reused. (ozizka, 15:12:02)
* The rules should only fire for the files that belong to the source
they should run on. E.g. .jar's of the server won't be decompiled
and analyzed (ozizka, 15:18:38)
Meeting ended at 15:18:59 UTC.
Action Items
------------
* We may create a prototype of that on Wiki.
* I'll try to measure how much time which part of that process takes to
see if it's worth of furtherinvestigation
Action Items, by person
-----------------------
* **UNASSIGNED**
* We may create a prototype of that on Wiki.
* I'll try to measure how much time which part of that process takes
to see if it's worth of furtherinvestigation
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
9 years, 8 months
Re: [windup-dev] Auto-discard notification
by Lincoln Baxter, III
It's in the jbosstools-forge master already.
George, did this fix get merged into the 4.3.0.Alpha branch yet? I'm
assuming it's not in 4.2.x.
Max, if we could get this into 4.2.x, then that would be ideal so that
users could use Windup-Eclipse as of Summit, but I understand that that
release train sailed a few weeks ago, which is why I didn't bother bringing
it up... I didn't think it was an option.
~Lincoln
On Wed, Apr 15, 2015 at 12:35 PM, Max Rydahl Andersen <manderse(a)redhat.com>
wrote:
> On 15 Apr 2015, at 18:20, Lincoln Baxter, III wrote:
>
> Just to follow up on this, Max. We basically need a new release of JBoss
>> Tools to include Forge Tools, which had some bad OSGi configuration that
>> was preventing this from working.
>>
>
> so our next release is code freezing tomorrow for JBDS 9 alpha2. I suggest
> you get that in.
>
> If you need it for JBDS 8/JBoss Tools 4.2.x then that is more of a hassle
> ...
>
> /max
>
>
>
>> We got that fixed in Forge Tools master and it's resolved now.
>>
>> On Tue, Apr 7, 2015 at 3:21 AM, <windup-dev-bounces(a)lists.jboss.org>
>> wrote:
>>
>> The attached message has been automatically discarded.
>>>
>>> ---------- Forwarded message ----------
>>> From: Max Rydahl Andersen <manderse(a)redhat.com>
>>> To: Pete Muir <pmuir(a)redhat.com>
>>> Cc: Ian Tewksbury <itewk(a)redhat.com>, Windup-dev List <
>>> windup-dev(a)lists.jboss.org>, Tobias Hartwig <thartwig(a)redhat.com>,
>>> Lincoln Baxter III <lbaxter(a)redhat.com>, Jess Sightler <
>>> jsightle(a)redhat.com>, Koen Aers <kaers(a)redhat.com>, George Gastaldi <
>>> ggastald(a)redhat.com>
>>> Date: Tue, 07 Apr 2015 09:21:33 +0200
>>> Subject: Re: [windup-dev] previously initiated loading for a different
>>> type with name "org/jboss/forge/furnace/util/Predicate"
>>> Haven't heard anything back on this. Is is solved ?
>>>
>>> Anything I can/need to do ?
>>>
>>> /max
>>>
>>> Is there a bug where we can add/share info instead of email ?
>>>
>>>>
>>>> How do I reproduce this ?
>>>>
>>>> I haven't used the latest windup tooling so could use some guidance.
>>>>
>>>> And I can try take a look after (if lucky during) next week Newcastle
>>>> meetup.
>>>>
>>>> ...but my guess is this is more a Lincoln question since he is the
>>>> Furnace class loader master mind :)
>>>>
>>>> ...btw. any reason why we don't just run windup externally from the
>>>> eclipse tooling and avoid any
>>>> of this stuff ?
>>>>
>>>> /max
>>>>
>>>> Adding Koen and George who may be able to help. Dropping Cat and Burr
>>>> :-)
>>>>
>>>>>
>>>>> On 27 Mar 2015, at 12:38, Ian Tewksbury <itewk(a)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(a)redhat.com>
>>>>>> To: "Lincoln Baxter" <lbaxter(a)redhat.com>, "Jess Sightler" <
>>>>>> jsightle(a)redhat.com>, "Pete Muir" <pmuir(a)redhat.com>
>>>>>> Cc: "Windup-dev List" <windup-dev(a)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(a)lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>>>>
>>>>>>
>>>>>>
>>>> /max
>>>> http://about.me/maxandersen
>>>>
>>>>
>>>
>>> /max
>>> http://about.me/maxandersen
>>>
>>>
>>>
>>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>>
>
>
> /max
> http://about.me/maxandersen
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
9 years, 8 months
Windup meeting minutes - 2015-04-05
by Lincoln Baxter, III
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup....
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup....
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup....
Meeting summary
---------------
* Agenda (lincolnthree, 14:02:39)
* Status Reports (lincolnthree, 14:05:32)
* Last week I worked on reviewing several PRs, and also some documents
for working with internal teams that have privacy constraints.
(lincolnthree, 14:06:56)
* It was a fairly distracted work week unfortunately. (lincolnthree,
14:07:13)
* This week I (still) plan to work on the batch AST processing, then
probably work on reviewing the quickstarts and documentation.
(lincolnthree, 14:07:45)
* I also need to review a few PRs, including the eclipse plugin,
today. (lincolnthree, 14:07:57)
* WINDUP-559 and WINDUP-560 were finished up at the beginning of the
cycle (leaving a thread hanging when decompiling and SHA1->GAV
mapping bugs). (jsightler, 14:09:01)
* Since then, I have been working on the Eclipse plugin. I'm new to
Eclipse development, and to Forge within Eclipse, so this has been a
little slow... (jsightler, 14:09:28)
* But I have written a little tooling API to abstract away Windup...
this simplifies the API for tools and allows data to be easily
accessed from it even after closing the graph (jsightler, 14:10:01)
* That is basically done, and now I am testing the tooling and adding
a feature or two (mainly making the removal of markers easier, I
hope) (jsightler, 14:10:35)
* I was 2 days OOO, in the other days I worked on MIGR-198 that has
it's PR and should be fully tested. (mbriskar, 14:11:33)
* I know want to implement the same thing for furnace and then I am
free to start on something else (mbriskar, 14:11:58)
* Priorities (lincolnthree, 14:21:30)
* Priorities remain unchanged: (lincolnthree, 14:21:40)
* Performance (lincolnthree, 14:21:45)
* Eclipse Tooling (lincolnthree, 14:21:49)
* Quickstarts and Examples (lincolnthree, 14:21:58)
* Server Config migration (lincolnthree, 14:22:08)
* EAP Migration (lincolnthree, 14:24:54)
* We met with emmartins and some of the EAP team yesterday to discuss
integration in this aspect. The current plan is to re-use their
migration management operation to be able to retrieve information in
a dry-run of what would happen, and pull that information into
windup where appropriate. (lincolnthree, 14:25:49)
* But otherwise, we will probably need to re-use the DMR manually,
ourselves, or using the embedded CLI in order todo our work
migrating from other servers to EAP. (lincolnthree, 14:26:19)
* We will be working with the EAP team during the design of this
operation to ensure that we can get some use out of it (if
appropriate) (lincolnthree, 14:27:09)
* Next steps (lincolnthree, 14:33:22)
Meeting ended at 14:38:29 UTC.
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
9 years, 8 months
Windup 2.0 - Custom rule creation
by Akash Prajapati
Hello Team
I'm trying to learn WindUp 2.0 ( windup-distribution-2.1.0.A ) for custom
rule creations and I tried writing it. but when I show the report.
Here is the snipprt which I created for custom rule. Could you please help
on this, where am I wrong ?
This file is put under
<WINDUP_2.0>/rules/new-ext-weblogic-config.windup.xml
<?xml version="1.0"?>
<ruleset xmlns="http://windup.jboss.org/v1/xml" id="XmlFileMappings11">
<!-- The phase in which to run the rules -->
<!--
<phase></phase>
-->
<rules>
<rule id="weblogic_rule_1">
<when>
<javaclass
references="weblogic.servlet.annotation.WLServlet" as="default">
<location>ANNOTATION</location>
</javaclass>
</when>
<perform>
<hint message="Replace the proprietary
WebLogic @WLServlet annotation with the Java EE 6 standard @WebServlet
annotation." effort="2">
<link href="
https://access.redhat.com/articles/1249423" description="Migrate WebLogic
Proprietary Servlet Annotations" />
<lineitem message="Proprietary
WebLogic @WLServlet annotation found in file."/>
</hint>
</perform>
</rule>
<rule id="weblogic_rule_2">
<when>
<javaclass
references="weblogic.servlet.annotation.WLFilter" as="default">
<location>ANNOTATION</location>
</javaclass>
</when>
<perform>
<hint message="Replace the proprietary
WebLogic @WLFilter annotation with the Java EE 6 standard @WebFilter
annotation." effort="2">
<link href="
https://access.redhat.com/articles/1249423" description="Migrate WebLogic
Proprietary Filter Annotations" />
<lineitem message="Proprietary
WebLogic @WLFilter annotation found in file."/>
</hint>
</perform>
</rule>
</rules>
</ruleset>
Rule
Statistics
Executed?
Failed?
Failure Cause
addRule()
.when(And.all(JavaClass.references(weblogic.servlet.annotation.WLServlet)
.at([ANNOTATION]).as(default)) ) .perform(Iteration.over(?).perform(Hint
.withText("Replace the proprietary WebLogic @WLServlet annotation with the
Java E E 6 standard @WebServlet
annotation.").withEffort(2).with([org.jboss.windup
.reporting.config.Link@150e590])) )
withId("GeneratedID_XmlFileMappings11_1")
Vertices Created: 0
Edges Created: 0
Vertices Removed: 0
Edges Removed: 0
no
no
addRule()
.when(And.all(JavaClass.references(weblogic.servlet.annotation.WLFilter)
.at([ANNOTATION]).as(default)) ) .perform(Iteration.over(?).perform(Hint
.withText("Replace the proprietary WebLogic @WLFilter annotation with the
Java EE 6 standard @WebFilter
annotation.").withEffort(2).with([org.jboss.windup
.reporting.config.Link@f8f29])) )
withId("GeneratedID_XmlFileMappings11_2")
Vertices Created: 0
Edges Created: 0
Vertices Removed: 0
Edges Removed: 0
no
no
Thanks in advance!
Thanks
Akash Prajapati
Mailto: akash.prajapati(a)tcs.com
____________________________________________
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
9 years, 8 months
Re: [windup-dev] Auto-discard notification
by Jess Sightler
Yes, I think this was resolved.
> Haven't heard anything back on this. Is is solved ?
>
> Anything I can/need to do ?
>
> /max
>
> Is there a bug where we can add/share info instead of email ?
>
> How do I reproduce this ?
>
> I haven't used the latest windup tooling so could use some guidance.
>
> And I can try take a look after (if lucky during) next week Newcastle
> meetup.
>
> ...but my guess is this is more a Lincoln question since he is the
> Furnace class loader master mind
>
> ...btw. any reason why we don't just run windup externally from the
> eclipse tooling and avoid any
> of this stuff ?
>
> /max
>
>> Adding Koen and George who may be able to help. Dropping Cat and Burr
>>
>>> On 27 Mar 2015, at 12:38, Ian Tewksbury <itewk(a)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(a)redhat.com>
>>> To: "Lincoln Baxter" <lbaxter(a)redhat.com>, "Jess Sightler"
>>> <jsightle(a)redhat.com>, "Pete Muir" <pmuir(a)redhat.com>
>>> Cc: "Windup-dev List" <windup-dev(a)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(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
9 years, 8 months
Windup Meeting Minutes - 2015-03-25
by Lincoln Baxter, III
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup....
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup....
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup....
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."
9 years, 9 months
