From ozizka at redhat.com  Wed Apr  1 11:37:27 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 01 Apr 2015 17:37:27 +0200
Subject: [windup-dev] Windup Meeting Minutes - 2015-04-01
In-Reply-To: <CAEp_U4GNTAsriOXMmgMyC=jHcPsQOx5xg5vAdnuWe134z78Ugw@mail.gmail.com>
References: <CAEp_U4GNTAsriOXMmgMyC=jHcPsQOx5xg5vAdnuWe134z78Ugw@mail.gmail.com>
Message-ID: <551C10B7.1050000@redhat.com>

(17:23:53)jbott:Minutes:http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-04-01-14.49.html
(17:23:53)jbott:Minutes (text):http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-04-01-14.49.txt
(17:23:54)jbott:Log:http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-04-01-14.49.log.html


Meeting summary
---------------
* Windup team meeting  (ozizka, 14:49:50)
* Status reports  (ozizka, 14:50:51)
   * Worked on MIGR-198 (update rulesets). It works and it contains a
     test. PR is here https://github.com/windup/windup/pull/514
     (mbriskar, 14:56:01)
   * Firstly was also working on FORGE-2283 with PR here
     https://github.com/forge/core/pull/547. It took some time because
     test needed to mock maven repo in order to validate updating
     (mbriskar, 14:56:31)
   * Wrote a reproducer for a bug found in Furnace-cdi FURNACE-35, PR is
     here https://github.com/forge/furnace-cdi/pull/4  (mbriskar,
     14:57:01)
   * Worked on a bug found: Furnace was started twice, always. These was
     a problem because some events about it starting were fired twice.
     WINDUP-545 with PR
     https://github.com/windup/windup/commit/3f209764941461b336205bca7ceab50db6895fdb
     (already merged)  (mbriskar, 14:57:14)
   * I helped a little with documentation  (mbriskar, 14:57:27)

   * Tried big OS1 instance (can't get it work). Added few Jenkins jobs
     to target windup-quickstarts and windup-rulesets.  (ozizka,
     14:59:00)
   * Server config rules - prototyping. Some work will be soon (next
     week) in windup-rulesets-server  (ozizka, 14:59:01)
   * Cleaned up quickstarts  (ozizka, 14:59:01)
   * Did the 2.2.0 QS version but Sande was faster :)  (ozizka, 14:59:01)
   * Edited the documentation - added few missing bits, like --userRulesDirectory  (ozizka, 14:59:01)
   * Generated Javadoc  (ozizka, 14:59:01)
   * Few smaller pull requests like Forge upgrade to 2.15.2.  (ozizka, 14:59:01)
   * The windup-umbrella repo with `git submodules` to build it all at
     once.  (ozizka, 14:59:02)
   * PTO Thu and Fri this week.  (ozizka, 14:59:02)
   * LINK: https://github.com/windup/windup-distribution/pull/1
     (mbriskar, 15:12:15)
   * And - Monday is a holiday in Czech republic. I (and Matej too,
     perhaps?) will be AFK.  (ozizka, 15:12:32)
   * One more thing - we also had a meeting with Matt and discussed
     possoble report improvements. See WINDUP-555 for few suggestions.
     (ozizka, 15:16:41)
   * See https://issues.jboss.org/browse/WINDUP/component/12319543/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel
     for reporting issues list.  (ozizka, 15:16:54)

   * WINDUP-544 (StackOverflow Exception on some applications)
     (jsightler, 15:15:33)
   * I have also worked on a few other bugs for the release and on
     getting the windup-core-PR-dependents-check jobs in jenkins to work
     (jsightler, 15:16:11)
   * I have started working on the eclipse plugin, and will be working on
     that for the next week as well as starting to look at performance
     issues  (jsightler, 15:16:34)

   * Updated the documentation to use the term 'add-on' instead of
     'addon'  (sgilda, 15:21:50)
   * Released the 2.2.0.Final windup quickstarts  (sgilda, 15:22:15)
   * Figured out how to generate PDF versions of the doc. Will push them
     to the latest release site  (sgilda, 15:22:54)


* Priorities  (lincolnthree, 15:29:15)  (ozizka, 15:21:05)
   * 1. Performance  (lincolnthree, 15:29:43)  (ozizka, 15:21:05)
   * 2. Server config migration  (lincolnthree, 15:29:53)  (ozizka,
     15:21:05)
   * 3. Examples and Quickstarts  (lincolnthree, 15:30:32)  (ozizka,
     15:21:05)
   * 4. Eclipse tooling  (lincolnthree, 15:30:39)  (ozizka, 15:21:05)

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

From jsightle at redhat.com  Wed Apr  1 23:07:28 2015
From: jsightle at redhat.com (Jess Sightler)
Date: Wed, 01 Apr 2015 23:07:28 -0400
Subject: [windup-dev] Furnace not finding Windup FileService
In-Reply-To: <924206620.5768611.1427494918353.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>	<CAEp_U4Fqnsz860XjFXhBkayw9zR3_x_yjS9wJodzyRb9Nsaaag@mail.gmail.com>
	<924206620.5768611.1427494918353.JavaMail.zimbra@redhat.com>
Message-ID: <551CB270.3080308@redhat.com>

Hi Lincoln,

I have done some work on this over the past few days. Most of the work 
was me banging my head on the wall learning Eclipse and how the forge 
tools interact with it. :)

But I believe that I have made significant progress. Here is the first PR:

https://github.com/jbosstools/jbosstools-forge/pull/139

This enables the export of the Proxy interface (and other methods within 
the same package). If you include code in WindupRuntimePlugin that 
references these classes, you will see a compile error from the tycho 
compiler's OSGI validator. That's because the previous export didn't 
export the full package (including subpackages) for some reason, and it 
doesn't work at runtime either.

I have pushed my changes to the plugin here:
https://github.com/windup/windup-eclipse-plugin/tree/windup2-jess

The current error is as follows:

java.lang.NoClassDefFoundError: 
com/tinkerpop/blueprints/util/wrappers/event/EventGraph
     at java.lang.Class.getDeclaredMethods0(Native Method)
     at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
     at java.lang.Class.getDeclaredMethods(Class.java:1975)
     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_900cc211-7ad7-4a83-9359-b7518a7734e3.create(GraphContextFactory_$$_javassist_900cc211-7ad7-4a83-9359-b7518a7734e3.java)
     at 
org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:247)
     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.ClassNotFoundException: 
com.tinkerpop.blueprints.util.wrappers.event.EventGraph cannot be found 
by org.jboss.tools.windup.runtime_3.1.0.Alpha2-v20150402-0253
     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)
     ... 22 more


This one actually seems pretty clear. I think the real fix here is to 
quit exposing so much to the client, but rather to expose a more 
friendly API service. I will work on that soon.



On 03/27/2015 06:21 PM, Lincoln Baxter, III wrote:
> 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
>
>
> ------------------------------------------------------------------------
> *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 
> <mailto: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
>     <mailto:lincoln at redhat.com>>
>     *To: *"Ian Tewksbury" <itewk at redhat.com <mailto:itewk at redhat.com>>
>     *Cc: *"Robb Greathouse" <robb.greathouse at redhat.com
>     <mailto:robb.greathouse at redhat.com>>, "George Gastaldi"
>     <ggastald at redhat.com <mailto:ggastald at redhat.com>>, "Windup-dev
>     List" <windup-dev at lists.jboss.org <mailto: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 <mailto:itewk at redhat.com>>
>     *To: *"Lincoln Baxter" <lbaxter at redhat.com
>     <mailto:lbaxter at redhat.com>>
>     *Cc: *"Robb Greathouse" <robb.greathouse at redhat.com
>     <mailto: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 <http://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 <mailto:itewk at redhat.com>>
>     *To: *"Lincoln Baxter" <lbaxter at redhat.com
>     <mailto:lbaxter at redhat.com>>
>     *Cc: *"Robb Greathouse" <robb.greathouse at redhat.com
>     <mailto: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 <mailto:itewk at redhat.com>>
>     *To: *"Lincoln Baxter" <lbaxter at redhat.com
>     <mailto:lbaxter at redhat.com>>
>     *Cc: *"Robb Greathouse" <robb.greathouse at redhat.com
>     <mailto: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 <mailto:itewk at redhat.com>>
>     *To: *"Lincoln Baxter" <lbaxter at redhat.com
>     <mailto:lbaxter at redhat.com>>, "Robb Greathouse"
>     <robb.greathouse at redhat.com <mailto: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 <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

-- 
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/20150401/ad15ffb4/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 172297 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150401/ad15ffb4/attachment-0001.png 

From jsightle at redhat.com  Thu Apr  2 11:15:34 2015
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 02 Apr 2015 11:15:34 -0400
Subject: [windup-dev] Furnace not finding Windup FileService
In-Reply-To: <551CB270.3080308@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>	<CAEp_U4Fqnsz860XjFXhBkayw9zR3_x_yjS9wJodzyRb9Nsaaag@mail.gmail.com>	<924206620.5768611.1427494918353.JavaMail.zimbra@redhat.com>
	<551CB270.3080308@redhat.com>
Message-ID: <551D5D16.7040800@redhat.com>

Ok, I pushed a fix for the graphcontext issue below. Reports can be 
generated now, although I suspect there are still plenty of other bugs. 
Feel free to give it a try!


On 04/01/2015 11:07 PM, Jess Sightler wrote:
> Hi Lincoln,
>
> I have done some work on this over the past few days. Most of the work 
> was me banging my head on the wall learning Eclipse and how the forge 
> tools interact with it. :)
>
> But I believe that I have made significant progress. Here is the first PR:
>
> https://github.com/jbosstools/jbosstools-forge/pull/139
>
> This enables the export of the Proxy interface (and other methods 
> within the same package). If you include code in WindupRuntimePlugin 
> that references these classes, you will see a compile error from the 
> tycho compiler's OSGI validator. That's because the previous export 
> didn't export the full package (including subpackages) for some 
> reason, and it doesn't work at runtime either.
>
> I have pushed my changes to the plugin here:
> https://github.com/windup/windup-eclipse-plugin/tree/windup2-jess
>
> The current error is as follows:
>
> java.lang.NoClassDefFoundError: 
> com/tinkerpop/blueprints/util/wrappers/event/EventGraph
>     at java.lang.Class.getDeclaredMethods0(Native Method)
>     at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
>     at java.lang.Class.getDeclaredMethods(Class.java:1975)
>     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_900cc211-7ad7-4a83-9359-b7518a7734e3.create(GraphContextFactory_$$_javassist_900cc211-7ad7-4a83-9359-b7518a7734e3.java)
>     at 
> org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:247)
>     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.ClassNotFoundException: 
> com.tinkerpop.blueprints.util.wrappers.event.EventGraph cannot be 
> found by org.jboss.tools.windup.runtime_3.1.0.Alpha2-v20150402-0253
>     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)
>     ... 22 more
>
>
> This one actually seems pretty clear. I think the real fix here is to 
> quit exposing so much to the client, but rather to expose a more 
> friendly API service. I will work on that soon.
>
>
>
> On 03/27/2015 06:21 PM, Lincoln Baxter, III wrote:
>> 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
>>
>>
>> ------------------------------------------------------------------------
>> *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 
>> <mailto: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
>>     <mailto:lincoln at redhat.com>>
>>     *To: *"Ian Tewksbury" <itewk at redhat.com <mailto:itewk at redhat.com>>
>>     *Cc: *"Robb Greathouse" <robb.greathouse at redhat.com
>>     <mailto:robb.greathouse at redhat.com>>, "George Gastaldi"
>>     <ggastald at redhat.com <mailto:ggastald at redhat.com>>, "Windup-dev
>>     List" <windup-dev at lists.jboss.org
>>     <mailto: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 <mailto:itewk at redhat.com>>
>>     *To: *"Lincoln Baxter" <lbaxter at redhat.com
>>     <mailto:lbaxter at redhat.com>>
>>     *Cc: *"Robb Greathouse" <robb.greathouse at redhat.com
>>     <mailto: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 <http://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 <mailto:itewk at redhat.com>>
>>     *To: *"Lincoln Baxter" <lbaxter at redhat.com
>>     <mailto:lbaxter at redhat.com>>
>>     *Cc: *"Robb Greathouse" <robb.greathouse at redhat.com
>>     <mailto: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 <mailto:itewk at redhat.com>>
>>     *To: *"Lincoln Baxter" <lbaxter at redhat.com
>>     <mailto:lbaxter at redhat.com>>
>>     *Cc: *"Robb Greathouse" <robb.greathouse at redhat.com
>>     <mailto: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 <mailto:itewk at redhat.com>>
>>     *To: *"Lincoln Baxter" <lbaxter at redhat.com
>>     <mailto:lbaxter at redhat.com>>, "Robb Greathouse"
>>     <robb.greathouse at redhat.com <mailto: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 <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
>
> -- 
> 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

-- 
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/20150402/a7faac16/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 172297 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150402/a7faac16/attachment-0001.png 

From jsightle at redhat.com  Thu Apr  2 19:23:53 2015
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 02 Apr 2015 19:23:53 -0400
Subject: [windup-dev] Furnace not finding Windup FileService
In-Reply-To: <551D5D16.7040800@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>	<CAEp_U4Fqnsz860XjFXhBkayw9zR3_x_yjS9wJodzyRb9Nsaaag@mail.gmail.com>	<924206620.5768611.1427494918353.JavaMail.zimbra@redhat.com>	<551CB270.3080308@redhat.com>
	<551D5D16.7040800@redhat.com>
Message-ID: <551DCF89.4090204@redhat.com>

Ok, my PR for jbosstools caused issues, but fortunately gastaldi fixed 
them. :)

This all appears to work now! Thanks everyone!

On 04/02/2015 11:15 AM, Jess Sightler wrote:
> Ok, I pushed a fix for the graphcontext issue below. Reports can be 
> generated now, although I suspect there are still plenty of other 
> bugs. Feel free to give it a try!
>
>
> On 04/01/2015 11:07 PM, Jess Sightler wrote:
>> Hi Lincoln,
>>
>> I have done some work on this over the past few days. Most of the 
>> work was me banging my head on the wall learning Eclipse and how the 
>> forge tools interact with it. :)
>>
>> But I believe that I have made significant progress. Here is the 
>> first PR:
>>
>> https://github.com/jbosstools/jbosstools-forge/pull/139
>>
>> This enables the export of the Proxy interface (and other methods 
>> within the same package). If you include code in WindupRuntimePlugin 
>> that references these classes, you will see a compile error from the 
>> tycho compiler's OSGI validator. That's because the previous export 
>> didn't export the full package (including subpackages) for some 
>> reason, and it doesn't work at runtime either.
>>
>> I have pushed my changes to the plugin here:
>> https://github.com/windup/windup-eclipse-plugin/tree/windup2-jess
>>
>> The current error is as follows:
>>
>> java.lang.NoClassDefFoundError: 
>> com/tinkerpop/blueprints/util/wrappers/event/EventGraph
>>     at java.lang.Class.getDeclaredMethods0(Native Method)
>>     at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
>>     at java.lang.Class.getDeclaredMethods(Class.java:1975)
>>     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_900cc211-7ad7-4a83-9359-b7518a7734e3.create(GraphContextFactory_$$_javassist_900cc211-7ad7-4a83-9359-b7518a7734e3.java)
>>     at 
>> org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:247)
>>     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.ClassNotFoundException: 
>> com.tinkerpop.blueprints.util.wrappers.event.EventGraph cannot be 
>> found by org.jboss.tools.windup.runtime_3.1.0.Alpha2-v20150402-0253
>>     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)
>>     ... 22 more
>>
>>
>> This one actually seems pretty clear. I think the real fix here is to 
>> quit exposing so much to the client, but rather to expose a more 
>> friendly API service. I will work on that soon.
>>
>>
>>
>> On 03/27/2015 06:21 PM, Lincoln Baxter, III wrote:
>>> 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
>>>
>>>
>>> ------------------------------------------------------------------------
>>> *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 
>>> <mailto: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
>>>     <mailto:lincoln at redhat.com>>
>>>     *To: *"Ian Tewksbury" <itewk at redhat.com <mailto:itewk at redhat.com>>
>>>     *Cc: *"Robb Greathouse" <robb.greathouse at redhat.com
>>>     <mailto:robb.greathouse at redhat.com>>, "George Gastaldi"
>>>     <ggastald at redhat.com <mailto:ggastald at redhat.com>>, "Windup-dev
>>>     List" <windup-dev at lists.jboss.org
>>>     <mailto: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 <mailto:itewk at redhat.com>>
>>>     *To: *"Lincoln Baxter" <lbaxter at redhat.com
>>>     <mailto:lbaxter at redhat.com>>
>>>     *Cc: *"Robb Greathouse" <robb.greathouse at redhat.com
>>>     <mailto: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 <http://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 <mailto:itewk at redhat.com>>
>>>     *To: *"Lincoln Baxter" <lbaxter at redhat.com
>>>     <mailto:lbaxter at redhat.com>>
>>>     *Cc: *"Robb Greathouse" <robb.greathouse at redhat.com
>>>     <mailto: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 <mailto:itewk at redhat.com>>
>>>     *To: *"Lincoln Baxter" <lbaxter at redhat.com
>>>     <mailto:lbaxter at redhat.com>>
>>>     *Cc: *"Robb Greathouse" <robb.greathouse at redhat.com
>>>     <mailto: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 <mailto:itewk at redhat.com>>
>>>     *To: *"Lincoln Baxter" <lbaxter at redhat.com
>>>     <mailto:lbaxter at redhat.com>>, "Robb Greathouse"
>>>     <robb.greathouse at redhat.com <mailto: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 <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
>>
>> -- 
>> 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
>
> -- 
> 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

-- 
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/20150402/da820bce/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 172297 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150402/da820bce/attachment-0001.png 

From jsightle at redhat.com  Tue Apr  7 09:29:47 2015
From: jsightle at redhat.com (Jess Sightler)
Date: Tue, 07 Apr 2015 09:29:47 -0400
Subject: [windup-dev] Auto-discard notification
In-Reply-To: <mailman.29774.1428391298.2681.windup-dev@lists.jboss.org>
References: <mailman.29774.1428391298.2681.windup-dev@lists.jboss.org>
Message-ID: <5523DBCB.5070300@redhat.com>

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


From lincolnbaxter at gmail.com  Wed Apr 15 10:46:32 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 15 Apr 2015 10:46:32 -0400
Subject: [windup-dev] Windup meeting minutes - 2015-04-05
Message-ID: <CAEp_U4GS5FuqSZ97y2r28cK0gBpeeGYeMJ2BAocxHDSqXJcmWA@mail.gmail.com>

Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-04-15-14.02.html

Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-04-15-14.02.txt

Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-04-15-14.02.log.html

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."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150415/260431d4/attachment.html 

From lincolnbaxter at gmail.com  Wed Apr 15 13:00:30 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 15 Apr 2015 13:00:30 -0400
Subject: [windup-dev] Auto-discard notification
In-Reply-To: <F2D96CDB-DD4C-4A6D-B8FE-D12AE35B8D18@redhat.com>
References: <mailman.29774.1428391298.2681.windup-dev@lists.jboss.org>
	<CAEp_U4EdGPn2LngPR=Wd5pD4kgkO4GaRZuadTvRq4LRyncsTLA@mail.gmail.com>
	<F2D96CDB-DD4C-4A6D-B8FE-D12AE35B8D18@redhat.com>
Message-ID: <CAEp_U4FdcUstgjV-rFi176avYQ5Y0dBb9zNRgDU1Ydz79j-hUQ@mail.gmail.com>

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 at 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 at lists.jboss.org>
>> wrote:
>>
>>  The attached message has been automatically discarded.
>>>
>>> ---------- Forwarded message ----------
>>> From: Max Rydahl Andersen <manderse at redhat.com>
>>> To: Pete Muir <pmuir at redhat.com>
>>> Cc: Ian Tewksbury <itewk at redhat.com>, Windup-dev List <
>>> windup-dev at lists.jboss.org>, Tobias Hartwig <thartwig at redhat.com>,
>>> Lincoln Baxter III <lbaxter at redhat.com>, Jess Sightler <
>>> jsightle at redhat.com>, Koen Aers <kaers at redhat.com>, George Gastaldi <
>>> ggastald at 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 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
>>>>>>
>>>>>>
>>>>>>
>>>> /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."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150415/303fd970/attachment-0001.html 

From itewk at redhat.com  Mon Apr 20 08:40:21 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Mon, 20 Apr 2015 08:40:21 -0400 (EDT)
Subject: [windup-dev] Furnace not finding Windup FileService
In-Reply-To: <551DCF89.4090204@redhat.com>
References: <662321974.765317.1427014663076.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>
	<924206620.5768611.1427494918353.JavaMail.zimbra@redhat.com>
	<551CB270.3080308@redhat.com> <551D5D16.7040800@redhat.com>
	<551DCF89.4090204@redhat.com>
Message-ID: <66151272.2219289.1429533621302.JavaMail.zimbra@redhat.com>

Jess and Lincoln, 

You all are my heros! 

I will take what you all have done and merge in and see where we are at tonight! 

Licoln, did you solve your OSGi error yet? If not that should be a simple fix. And yes, I need the FIleService. 

~Ian 


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

From: "Jess Sightler" <jsightle at redhat.com> 
To: windup-dev at lists.jboss.org 
Sent: Thursday, April 2, 2015 7:23:53 PM 
Subject: Re: [windup-dev] Furnace not finding Windup FileService 

Ok, my PR for jbosstools caused issues, but fortunately gastaldi fixed them. :) 

This all appears to work now! Thanks everyone! 

On 04/02/2015 11:15 AM, Jess Sightler wrote: 


Ok, I pushed a fix for the graphcontext issue below. Reports can be generated now, although I suspect there are still plenty of other bugs. Feel free to give it a try! 


On 04/01/2015 11:07 PM, Jess Sightler wrote: 

<blockquote>
Hi Lincoln, 

I have done some work on this over the past few days. Most of the work was me banging my head on the wall learning Eclipse and how the forge tools interact with it. :) 

But I believe that I have made significant progress. Here is the first PR: 

https://github.com/jbosstools/jbosstools-forge/pull/139 

This enables the export of the Proxy interface (and other methods within the same package). If you include code in WindupRuntimePlugin that references these classes, you will see a compile error from the tycho compiler's OSGI validator. That's because the previous export didn't export the full package (including subpackages) for some reason, and it doesn't work at runtime either. 

I have pushed my changes to the plugin here: 
https://github.com/windup/windup-eclipse-plugin/tree/windup2-jess 

The current error is as follows: 

java.lang.NoClassDefFoundError: com/tinkerpop/blueprints/util/wrappers/event/EventGraph 
at java.lang.Class.getDeclaredMethods0(Native Method) 
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) 
at java.lang.Class.getDeclaredMethods(Class.java:1975) 
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_900cc211-7ad7-4a83-9359-b7518a7734e3.create(GraphContextFactory_$$_javassist_900cc211-7ad7-4a83-9359-b7518a7734e3.java) 
at org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:247) 
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.ClassNotFoundException: com.tinkerpop.blueprints.util.wrappers.event.EventGraph cannot be found by org.jboss.tools.windup.runtime_3.1.0.Alpha2-v20150402-0253 
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) 
... 22 more 


This one actually seems pretty clear. I think the real fix here is to quit exposing so much to the client, but rather to expose a more friendly API service. I will work on that soon. 



On 03/27/2015 06:21 PM, Lincoln Baxter, III wrote: 

<blockquote>

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: 

<blockquote>

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



_______________________________________________
windup-dev mailing list windup-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/windup-dev 

</blockquote>

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

</blockquote>

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

</blockquote>

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150420/be63193e/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 172297 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150420/be63193e/attachment-0001.png 

From lincolnbaxter at gmail.com  Tue Apr 21 11:54:02 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 21 Apr 2015 11:54:02 -0400
Subject: [windup-dev] Furnace not finding Windup FileService
In-Reply-To: <66151272.2219289.1429533621302.JavaMail.zimbra@redhat.com>
References: <662321974.765317.1427014663076.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>
	<924206620.5768611.1427494918353.JavaMail.zimbra@redhat.com>
	<551CB270.3080308@redhat.com> <551D5D16.7040800@redhat.com>
	<551DCF89.4090204@redhat.com>
	<66151272.2219289.1429533621302.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4E+BJv+uWMRERduJdyb8iqmwGPa2c9sYeAcdUCSpeHxGw@mail.gmail.com>

Ian,

Thanks! We it would have been a long hard road to get here without your
work :) The OSGi error is solved as long as you have the most recent
JBossTools Forge master (it didn't make it into the JBDS 8.1 release.)

What do you need FileService for? We'll need to introduce an API in the
windup tooling API for what you need.

~Lincoln

On Mon, Apr 20, 2015 at 8:40 AM, Ian Tewksbury <itewk at redhat.com> wrote:

> Jess and Lincoln,
>
> You all are my heros!
>
> I will take what you all have done and merge in and see where we are at
> tonight!
>
> Licoln, did you solve your OSGi error yet? If not that should be a simple
> fix.  And yes, I need the FIleService.
>
> ~Ian
>
>
> ------------------------------
> *From: *"Jess Sightler" <jsightle at redhat.com>
> *To: *windup-dev at lists.jboss.org
> *Sent: *Thursday, April 2, 2015 7:23:53 PM
>
> *Subject: *Re: [windup-dev] Furnace not finding Windup FileService
>
> Ok, my PR for jbosstools caused issues, but fortunately gastaldi fixed
> them. :)
>
> This all appears to work now! Thanks everyone!
>
> On 04/02/2015 11:15 AM, Jess Sightler wrote:
>
> Ok, I pushed a fix for the graphcontext issue below. Reports can be
> generated now, although I suspect there are still plenty of other bugs.
> Feel free to give it a try!
>
>
> On 04/01/2015 11:07 PM, Jess Sightler wrote:
>
> Hi Lincoln,
>
> I have done some work on this over the past few days. Most of the work was
> me banging my head on the wall learning Eclipse and how the forge tools
> interact with it. :)
>
> But I believe that I have made significant progress. Here is the first PR:
>
> https://github.com/jbosstools/jbosstools-forge/pull/139
>
> This enables the export of the Proxy interface (and other methods within
> the same package). If you include code in WindupRuntimePlugin that
> references these classes, you will see a compile error from the tycho
> compiler's OSGI validator. That's because the previous export didn't export
> the full package (including subpackages) for some reason, and it doesn't
> work at runtime either.
>
> I have pushed my changes to the plugin here:
> https://github.com/windup/windup-eclipse-plugin/tree/windup2-jess
>
> The current error is as follows:
>
> java.lang.NoClassDefFoundError:
> com/tinkerpop/blueprints/util/wrappers/event/EventGraph
>     at java.lang.Class.getDeclaredMethods0(Native Method)
>     at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
>     at java.lang.Class.getDeclaredMethods(Class.java:1975)
>     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_900cc211-7ad7-4a83-9359-b7518a7734e3.create(GraphContextFactory_$$_javassist_900cc211-7ad7-4a83-9359-b7518a7734e3.java)
>     at
> org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:247)
>     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.ClassNotFoundException:
> com.tinkerpop.blueprints.util.wrappers.event.EventGraph cannot be found by
> org.jboss.tools.windup.runtime_3.1.0.Alpha2-v20150402-0253
>     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)
>     ... 22 more
>
>
> This one actually seems pretty clear. I think the real fix here is to quit
> exposing so much to the client, but rather to expose a more friendly API
> service. I will work on that soon.
>
>
>
> On 03/27/2015 06:21 PM, Lincoln Baxter, III wrote:
>
>  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
>
>  ------------------------------
> *From: *"Lincoln Baxter, III" <lincolnbaxter at gmail.com>
> <lincolnbaxter at gmail.com>
> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
> <windup-dev at lists.jboss.org>
> *Cc: *"Lincoln Baxter, III" <lincoln at redhat.com> <lincoln at redhat.com>,
> "George Gastaldi" <ggastald at redhat.com> <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."
>
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://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 listwindup-dev at lists.jboss.orghttps://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 listwindup-dev at lists.jboss.orghttps://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/20150421/09c427af/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 172297 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150421/09c427af/attachment-0001.png 

From lincolnbaxter at gmail.com  Tue Apr 21 12:11:35 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 21 Apr 2015 12:11:35 -0400
Subject: [windup-dev] Furnace not finding Windup FileService
In-Reply-To: <CAEp_U4E+BJv+uWMRERduJdyb8iqmwGPa2c9sYeAcdUCSpeHxGw@mail.gmail.com>
References: <662321974.765317.1427014663076.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>
	<924206620.5768611.1427494918353.JavaMail.zimbra@redhat.com>
	<551CB270.3080308@redhat.com> <551D5D16.7040800@redhat.com>
	<551DCF89.4090204@redhat.com>
	<66151272.2219289.1429533621302.JavaMail.zimbra@redhat.com>
	<CAEp_U4E+BJv+uWMRERduJdyb8iqmwGPa2c9sYeAcdUCSpeHxGw@mail.gmail.com>
Message-ID: <CAEp_U4EJ31-_mqaZfcqG_SAtwP+55VUNZe3x_HpP+XaxwY531g@mail.gmail.com>

Well* it would have been.

On Tue, Apr 21, 2015 at 11:54 AM, Lincoln Baxter, III <
lincolnbaxter at gmail.com> wrote:

> Ian,
>
> Thanks! We it would have been a long hard road to get here without your
> work :) The OSGi error is solved as long as you have the most recent
> JBossTools Forge master (it didn't make it into the JBDS 8.1 release.)
>
> What do you need FileService for? We'll need to introduce an API in the
> windup tooling API for what you need.
>
> ~Lincoln
>
> On Mon, Apr 20, 2015 at 8:40 AM, Ian Tewksbury <itewk at redhat.com> wrote:
>
>> Jess and Lincoln,
>>
>> You all are my heros!
>>
>> I will take what you all have done and merge in and see where we are at
>> tonight!
>>
>> Licoln, did you solve your OSGi error yet? If not that should be a simple
>> fix.  And yes, I need the FIleService.
>>
>> ~Ian
>>
>>
>> ------------------------------
>> *From: *"Jess Sightler" <jsightle at redhat.com>
>> *To: *windup-dev at lists.jboss.org
>> *Sent: *Thursday, April 2, 2015 7:23:53 PM
>>
>> *Subject: *Re: [windup-dev] Furnace not finding Windup FileService
>>
>> Ok, my PR for jbosstools caused issues, but fortunately gastaldi fixed
>> them. :)
>>
>> This all appears to work now! Thanks everyone!
>>
>> On 04/02/2015 11:15 AM, Jess Sightler wrote:
>>
>> Ok, I pushed a fix for the graphcontext issue below. Reports can be
>> generated now, although I suspect there are still plenty of other bugs.
>> Feel free to give it a try!
>>
>>
>> On 04/01/2015 11:07 PM, Jess Sightler wrote:
>>
>> Hi Lincoln,
>>
>> I have done some work on this over the past few days. Most of the work
>> was me banging my head on the wall learning Eclipse and how the forge tools
>> interact with it. :)
>>
>> But I believe that I have made significant progress. Here is the first PR:
>>
>> https://github.com/jbosstools/jbosstools-forge/pull/139
>>
>> This enables the export of the Proxy interface (and other methods within
>> the same package). If you include code in WindupRuntimePlugin that
>> references these classes, you will see a compile error from the tycho
>> compiler's OSGI validator. That's because the previous export didn't export
>> the full package (including subpackages) for some reason, and it doesn't
>> work at runtime either.
>>
>> I have pushed my changes to the plugin here:
>> https://github.com/windup/windup-eclipse-plugin/tree/windup2-jess
>>
>> The current error is as follows:
>>
>> java.lang.NoClassDefFoundError:
>> com/tinkerpop/blueprints/util/wrappers/event/EventGraph
>>     at java.lang.Class.getDeclaredMethods0(Native Method)
>>     at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
>>     at java.lang.Class.getDeclaredMethods(Class.java:1975)
>>     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_900cc211-7ad7-4a83-9359-b7518a7734e3.create(GraphContextFactory_$$_javassist_900cc211-7ad7-4a83-9359-b7518a7734e3.java)
>>     at
>> org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:247)
>>     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.ClassNotFoundException:
>> com.tinkerpop.blueprints.util.wrappers.event.EventGraph cannot be found by
>> org.jboss.tools.windup.runtime_3.1.0.Alpha2-v20150402-0253
>>     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)
>>     ... 22 more
>>
>>
>> This one actually seems pretty clear. I think the real fix here is to
>> quit exposing so much to the client, but rather to expose a more friendly
>> API service. I will work on that soon.
>>
>>
>>
>> On 03/27/2015 06:21 PM, Lincoln Baxter, III wrote:
>>
>>  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
>>
>>  ------------------------------
>> *From: *"Lincoln Baxter, III" <lincolnbaxter at gmail.com>
>> <lincolnbaxter at gmail.com>
>> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
>> <windup-dev at lists.jboss.org>
>> *Cc: *"Lincoln Baxter, III" <lincoln at redhat.com> <lincoln at redhat.com>,
>> "George Gastaldi" <ggastald at redhat.com> <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."
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing listwindup-dev at lists.jboss.orghttps://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 listwindup-dev at lists.jboss.orghttps://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 listwindup-dev at lists.jboss.orghttps://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."
>



-- 
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/20150421/9970eba5/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 172297 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150421/9970eba5/attachment-0001.png 

From lincolnbaxter at gmail.com  Wed Apr 22 11:20:14 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 22 Apr 2015 11:20:14 -0400
Subject: [windup-dev] Windup Meeting Minutes - 2015-04-22
Message-ID: <CAEp_U4HBK7y+kHxvCjyUc_ukfgOE2wTp4GGEkw09WAc2zxJemA@mail.gmail.com>

Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-04-22-14.05.html

Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-04-22-14.05.txt

Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-04-22-14.05.log.html

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/4ef5c983947b6221334747dcca1ddb3f0a48570b/tests/src/test/java/test/org/jboss/forge/furnace/harness/AutomaticAddonDependenciesTest.java
    (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."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150422/5ea1ff8a/attachment.html 

From itewk at redhat.com  Thu Apr 23 12:29:24 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Thu, 23 Apr 2015 12:29:24 -0400 (EDT)
Subject: [windup-dev] Furnace not finding Windup FileService
In-Reply-To: <CAEp_U4EJ31-_mqaZfcqG_SAtwP+55VUNZe3x_HpP+XaxwY531g@mail.gmail.com>
References: <662321974.765317.1427014663076.JavaMail.zimbra@redhat.com>
	<924206620.5768611.1427494918353.JavaMail.zimbra@redhat.com>
	<551CB270.3080308@redhat.com> <551D5D16.7040800@redhat.com>
	<551DCF89.4090204@redhat.com>
	<66151272.2219289.1429533621302.JavaMail.zimbra@redhat.com>
	<CAEp_U4E+BJv+uWMRERduJdyb8iqmwGPa2c9sYeAcdUCSpeHxGw@mail.gmail.com>
	<CAEp_U4EJ31-_mqaZfcqG_SAtwP+55VUNZe3x_HpP+XaxwY531g@mail.gmail.com>
Message-ID: <1959724051.3669901.1429806564232.JavaMail.zimbra@redhat.com>

Liconln, 

Should I be looking at your branch on git? 

Do i need to run with the latest version of furenace? 

Just trying to get my environment set up the same as yours so it works for me too :) 

Now that you got the hard part working I want to add bells and whistles :) 

~Ian 

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

From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com> 
To: "Windup-dev List" <windup-dev at lists.jboss.org> 
Sent: Tuesday, April 21, 2015 12:11:35 PM 
Subject: Re: [windup-dev] Furnace not finding Windup FileService 

Well* it would have been. 

On Tue, Apr 21, 2015 at 11:54 AM, Lincoln Baxter, III < lincolnbaxter at gmail.com > wrote: 



Ian, 

Thanks! We it would have been a long hard road to get here without your work :) The OSGi error is solved as long as you have the most recent JBossTools Forge master (it didn't make it into the JBDS 8.1 release.) 

What do you need FileService for? We'll need to introduce an API in the windup tooling API for what you need. 

~Lincoln 

On Mon, Apr 20, 2015 at 8:40 AM, Ian Tewksbury < itewk at redhat.com > wrote: 

<blockquote>

Jess and Lincoln, 

You all are my heros! 

I will take what you all have done and merge in and see where we are at tonight! 

Licoln, did you solve your OSGi error yet? If not that should be a simple fix. And yes, I need the FIleService. 

~Ian 



From: "Jess Sightler" < jsightle at redhat.com > 
To: windup-dev at lists.jboss.org 
Sent: Thursday, April 2, 2015 7:23:53 PM 

Subject: Re: [windup-dev] Furnace not finding Windup FileService 

Ok, my PR for jbosstools caused issues, but fortunately gastaldi fixed them. :) 

This all appears to work now! Thanks everyone! 

On 04/02/2015 11:15 AM, Jess Sightler wrote: 

<blockquote>
Ok, I pushed a fix for the graphcontext issue below. Reports can be generated now, although I suspect there are still plenty of other bugs. Feel free to give it a try! 


On 04/01/2015 11:07 PM, Jess Sightler wrote: 

<blockquote>
Hi Lincoln, 

I have done some work on this over the past few days. Most of the work was me banging my head on the wall learning Eclipse and how the forge tools interact with it. :) 

But I believe that I have made significant progress. Here is the first PR: 

https://github.com/jbosstools/jbosstools-forge/pull/139 

This enables the export of the Proxy interface (and other methods within the same package). If you include code in WindupRuntimePlugin that references these classes, you will see a compile error from the tycho compiler's OSGI validator. That's because the previous export didn't export the full package (including subpackages) for some reason, and it doesn't work at runtime either. 

I have pushed my changes to the plugin here: 
https://github.com/windup/windup-eclipse-plugin/tree/windup2-jess 

The current error is as follows: 

java.lang.NoClassDefFoundError: com/tinkerpop/blueprints/util/wrappers/event/EventGraph 
at java.lang.Class.getDeclaredMethods0(Native Method) 
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) 
at java.lang.Class.getDeclaredMethods(Class.java:1975) 
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_900cc211-7ad7-4a83-9359-b7518a7734e3.create(GraphContextFactory_$$_javassist_900cc211-7ad7-4a83-9359-b7518a7734e3.java) 
at org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:247) 
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.ClassNotFoundException: com.tinkerpop.blueprints.util.wrappers.event.EventGraph cannot be found by org.jboss.tools.windup.runtime_3.1.0.Alpha2-v20150402-0253 
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) 
... 22 more 


This one actually seems pretty clear. I think the real fix here is to quit exposing so much to the client, but rather to expose a more friendly API service. I will work on that soon. 



On 03/27/2015 06:21 PM, Lincoln Baxter, III wrote: 

<blockquote>

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 


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: 

<blockquote>

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



_______________________________________________
windup-dev mailing list windup-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/windup-dev 

</blockquote>

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

</blockquote>

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

</blockquote>

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

</blockquote>




-- 
Lincoln Baxter, III 
http://ocpsoft.org 
"Simpler is better." 

</blockquote>




-- 
Lincoln Baxter, III 
http://ocpsoft.org 
"Simpler is better." 

_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150423/824f60a5/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 172297 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150423/824f60a5/attachment-0001.png 

From jsightle at redhat.com  Thu Apr 23 12:33:49 2015
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 23 Apr 2015 12:33:49 -0400
Subject: [windup-dev] Furnace not finding Windup FileService
In-Reply-To: <1959724051.3669901.1429806564232.JavaMail.zimbra@redhat.com>
References: <662321974.765317.1427014663076.JavaMail.zimbra@redhat.com>	<924206620.5768611.1427494918353.JavaMail.zimbra@redhat.com>	<551CB270.3080308@redhat.com>
	<551D5D16.7040800@redhat.com>	<551DCF89.4090204@redhat.com>	<66151272.2219289.1429533621302.JavaMail.zimbra@redhat.com>	<CAEp_U4E+BJv+uWMRERduJdyb8iqmwGPa2c9sYeAcdUCSpeHxGw@mail.gmail.com>	<CAEp_U4EJ31-_mqaZfcqG_SAtwP+55VUNZe3x_HpP+XaxwY531g@mail.gmail.com>
	<1959724051.3669901.1429806564232.JavaMail.zimbra@redhat.com>
Message-ID: <55391EED.5060606@redhat.com>

Hi Ian,

You should be able to work from master. I've just merged the latest changes.

https://github.com/windup/windup-eclipse-plugin

You will need the latest version of the forge-eclipse-plugin.

Thanks!
Jess


On 04/23/2015 12:29 PM, Ian Tewksbury wrote:
> Liconln,
>
> Should I be looking at your branch on git?
>
> Do i need to run with the latest version of furenace?
>
> Just trying to get my environment set up the same as yours so it works 
> for me too :)
>
> Now that you got the hard part working I want to add bells and whistles :)
>
> ~Ian
>
> ------------------------------------------------------------------------
> *From: *"Lincoln Baxter, III" <lincolnbaxter at gmail.com>
> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
> *Sent: *Tuesday, April 21, 2015 12:11:35 PM
> *Subject: *Re: [windup-dev] Furnace not finding Windup FileService
>
> Well* it would have been.
>
> On Tue, Apr 21, 2015 at 11:54 AM, Lincoln Baxter, III 
> <lincolnbaxter at gmail.com <mailto:lincolnbaxter at gmail.com>> wrote:
>
>     Ian,
>
>     Thanks! We it would have been a long hard road to get here without
>     your work :) The OSGi error is solved as long as you have the most
>     recent JBossTools Forge master (it didn't make it into the JBDS
>     8.1 release.)
>
>     What do you need FileService for? We'll need to introduce an API
>     in the windup tooling API for what you need.
>
>     ~Lincoln
>
>     On Mon, Apr 20, 2015 at 8:40 AM, Ian Tewksbury <itewk at redhat.com
>     <mailto:itewk at redhat.com>> wrote:
>
>         Jess and Lincoln,
>
>         You all are my heros!
>
>         I will take what you all have done and merge in and see where
>         we are at tonight!
>
>         Licoln, did you solve your OSGi error yet? If not that should
>         be a simple fix.  And yes, I need the FIleService.
>
>         ~Ian
>
>
>         ------------------------------------------------------------------------
>         *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: *Thursday, April 2, 2015 7:23:53 PM
>
>         *Subject: *Re: [windup-dev] Furnace not finding Windup FileService
>
>         Ok, my PR for jbosstools caused issues, but fortunately
>         gastaldi fixed them. :)
>
>         This all appears to work now! Thanks everyone!
>
>         On 04/02/2015 11:15 AM, Jess Sightler wrote:
>
>             Ok, I pushed a fix for the graphcontext issue below.
>             Reports can be generated now, although I suspect there are
>             still plenty of other bugs. Feel free to give it a try!
>
>
>             On 04/01/2015 11:07 PM, Jess Sightler wrote:
>
>                 Hi Lincoln,
>
>                 I have done some work on this over the past few days.
>                 Most of the work was me banging my head on the wall
>                 learning Eclipse and how the forge tools interact with
>                 it. :)
>
>                 But I believe that I have made significant progress.
>                 Here is the first PR:
>
>                 https://github.com/jbosstools/jbosstools-forge/pull/139
>
>                 This enables the export of the Proxy interface (and
>                 other methods within the same package). If you include
>                 code in WindupRuntimePlugin that references these
>                 classes, you will see a compile error from the tycho
>                 compiler's OSGI validator. That's because the previous
>                 export didn't export the full package (including
>                 subpackages) for some reason, and it doesn't work at
>                 runtime either.
>
>                 I have pushed my changes to the plugin here:
>                 https://github.com/windup/windup-eclipse-plugin/tree/windup2-jess
>
>                 The current error is as follows:
>
>                 java.lang.NoClassDefFoundError:
>                 com/tinkerpop/blueprints/util/wrappers/event/EventGraph
>                     at java.lang.Class.getDeclaredMethods0(Native Method)
>                     at
>                 java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
>                     at java.lang.Class.getDeclaredMethods(Class.java:1975)
>                     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_900cc211-7ad7-4a83-9359-b7518a7734e3.create(GraphContextFactory_$$_javassist_900cc211-7ad7-4a83-9359-b7518a7734e3.java)
>                     at
>                 org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:247)
>                     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.ClassNotFoundException:
>                 com.tinkerpop.blueprints.util.wrappers.event.EventGraph cannot
>                 be found by
>                 org.jboss.tools.windup.runtime_3.1.0.Alpha2-v20150402-0253
>                     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)
>                     ... 22 more
>
>
>                 This one actually seems pretty clear. I think the real
>                 fix here is to quit exposing so much to the client,
>                 but rather to expose a more friendly API service. I
>                 will work on that soon.
>
>
>
>                 On 03/27/2015 06:21 PM, Lincoln Baxter, III wrote:
>
>                     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
>                     <http://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
>
>
>                     ------------------------------------------------------------------------
>                     *From: *"Lincoln Baxter, III"
>                     <lincolnbaxter at gmail.com>
>                     <mailto:lincolnbaxter at gmail.com>
>                     *To: *"Windup-dev List"
>                     <windup-dev at lists.jboss.org>
>                     <mailto:windup-dev at lists.jboss.org>
>                     *Cc: *"Lincoln Baxter, III" <lincoln at redhat.com>
>                     <mailto:lincoln at redhat.com>, "George Gastaldi"
>                     <ggastald at redhat.com> <mailto: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 <mailto: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 <mailto:lincoln at redhat.com>>
>                         *To: *"Ian Tewksbury" <itewk at redhat.com
>                         <mailto:itewk at redhat.com>>
>                         *Cc: *"Robb Greathouse"
>                         <robb.greathouse at redhat.com
>                         <mailto:robb.greathouse at redhat.com>>, "George
>                         Gastaldi" <ggastald at redhat.com
>                         <mailto:ggastald at redhat.com>>, "Windup-dev
>                         List" <windup-dev at lists.jboss.org
>                         <mailto: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
>                         <mailto:itewk at redhat.com>>
>                         *To: *"Lincoln Baxter" <lbaxter at redhat.com
>                         <mailto:lbaxter at redhat.com>>
>                         *Cc: *"Robb Greathouse"
>                         <robb.greathouse at redhat.com
>                         <mailto: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
>                         <http://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
>                         <mailto:itewk at redhat.com>>
>                         *To: *"Lincoln Baxter" <lbaxter at redhat.com
>                         <mailto:lbaxter at redhat.com>>
>                         *Cc: *"Robb Greathouse"
>                         <robb.greathouse at redhat.com
>                         <mailto: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
>                         <mailto:itewk at redhat.com>>
>                         *To: *"Lincoln Baxter" <lbaxter at redhat.com
>                         <mailto:lbaxter at redhat.com>>
>                         *Cc: *"Robb Greathouse"
>                         <robb.greathouse at redhat.com
>                         <mailto: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
>                         <mailto:itewk at redhat.com>>
>                         *To: *"Lincoln Baxter" <lbaxter at redhat.com
>                         <mailto:lbaxter at redhat.com>>, "Robb
>                         Greathouse" <robb.greathouse at redhat.com
>                         <mailto: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
>                         <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  <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
>
>
>             -- 
>             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
>
>
>         -- 
>         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."
>
>
>
>
> -- 
> 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

-- 
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/20150423/38d535a4/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 172297 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150423/38d535a4/attachment-0001.png 

From itewk at redhat.com  Thu Apr 23 12:34:37 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Thu, 23 Apr 2015 12:34:37 -0400 (EDT)
Subject: [windup-dev] Furnace not finding Windup FileService
In-Reply-To: <55391EED.5060606@redhat.com>
References: <662321974.765317.1427014663076.JavaMail.zimbra@redhat.com>
	<551D5D16.7040800@redhat.com> <551DCF89.4090204@redhat.com>
	<66151272.2219289.1429533621302.JavaMail.zimbra@redhat.com>
	<CAEp_U4E+BJv+uWMRERduJdyb8iqmwGPa2c9sYeAcdUCSpeHxGw@mail.gmail.com>
	<CAEp_U4EJ31-_mqaZfcqG_SAtwP+55VUNZe3x_HpP+XaxwY531g@mail.gmail.com>
	<1959724051.3669901.1429806564232.JavaMail.zimbra@redhat.com>
	<55391EED.5060606@redhat.com>
Message-ID: <1495485778.3671195.1429806877786.JavaMail.zimbra@redhat.com>

Jess, 

Thanks! 

~Ian 

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

From: "Jess Sightler" <jsightle at redhat.com> 
To: windup-dev at lists.jboss.org, "Ian Tewksbury" <itewk at redhat.com> 
Sent: Thursday, April 23, 2015 12:33:49 PM 
Subject: Re: [windup-dev] Furnace not finding Windup FileService 

Hi Ian, 

You should be able to work from master. I've just merged the latest changes. 

https://github.com/windup/windup-eclipse-plugin 

You will need the latest version of the forge-eclipse-plugin. 

Thanks! 
Jess 


On 04/23/2015 12:29 PM, Ian Tewksbury wrote: 



Liconln, 

Should I be looking at your branch on git? 

Do i need to run with the latest version of furenace? 

Just trying to get my environment set up the same as yours so it works for me too :) 

Now that you got the hard part working I want to add bells and whistles :) 

~Ian 

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

From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com> 
To: "Windup-dev List" <windup-dev at lists.jboss.org> 
Sent: Tuesday, April 21, 2015 12:11:35 PM 
Subject: Re: [windup-dev] Furnace not finding Windup FileService 

Well* it would have been. 

On Tue, Apr 21, 2015 at 11:54 AM, Lincoln Baxter, III < lincolnbaxter at gmail.com > wrote: 

<blockquote>

Ian, 

Thanks! We it would have been a long hard road to get here without your work :) The OSGi error is solved as long as you have the most recent JBossTools Forge master (it didn't make it into the JBDS 8.1 release.) 

What do you need FileService for? We'll need to introduce an API in the windup tooling API for what you need. 

~Lincoln 

On Mon, Apr 20, 2015 at 8:40 AM, Ian Tewksbury < itewk at redhat.com > wrote: 

<blockquote>

Jess and Lincoln, 

You all are my heros! 

I will take what you all have done and merge in and see where we are at tonight! 

Licoln, did you solve your OSGi error yet? If not that should be a simple fix. And yes, I need the FIleService. 

~Ian 



From: "Jess Sightler" < jsightle at redhat.com > 
To: windup-dev at lists.jboss.org 
Sent: Thursday, April 2, 2015 7:23:53 PM 

Subject: Re: [windup-dev] Furnace not finding Windup FileService 

Ok, my PR for jbosstools caused issues, but fortunately gastaldi fixed them. :) 

This all appears to work now! Thanks everyone! 

On 04/02/2015 11:15 AM, Jess Sightler wrote: 

<blockquote>
Ok, I pushed a fix for the graphcontext issue below. Reports can be generated now, although I suspect there are still plenty of other bugs. Feel free to give it a try! 


On 04/01/2015 11:07 PM, Jess Sightler wrote: 

<blockquote>
Hi Lincoln, 

I have done some work on this over the past few days. Most of the work was me banging my head on the wall learning Eclipse and how the forge tools interact with it. :) 

But I believe that I have made significant progress. Here is the first PR: 

https://github.com/jbosstools/jbosstools-forge/pull/139 

This enables the export of the Proxy interface (and other methods within the same package). If you include code in WindupRuntimePlugin that references these classes, you will see a compile error from the tycho compiler's OSGI validator. That's because the previous export didn't export the full package (including subpackages) for some reason, and it doesn't work at runtime either. 

I have pushed my changes to the plugin here: 
https://github.com/windup/windup-eclipse-plugin/tree/windup2-jess 

The current error is as follows: 

java.lang.NoClassDefFoundError: com/tinkerpop/blueprints/util/wrappers/event/EventGraph 
at java.lang.Class.getDeclaredMethods0(Native Method) 
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) 
at java.lang.Class.getDeclaredMethods(Class.java:1975) 
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_900cc211-7ad7-4a83-9359-b7518a7734e3.create(GraphContextFactory_$$_javassist_900cc211-7ad7-4a83-9359-b7518a7734e3.java) 
at org.jboss.tools.windup.core.WindupService.generateGraph(WindupService.java:247) 
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.ClassNotFoundException: com.tinkerpop.blueprints.util.wrappers.event.EventGraph cannot be found by org.jboss.tools.windup.runtime_3.1.0.Alpha2-v20150402-0253 
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) 
... 22 more 


This one actually seems pretty clear. I think the real fix here is to quit exposing so much to the client, but rather to expose a more friendly API service. I will work on that soon. 



On 03/27/2015 06:21 PM, Lincoln Baxter, III wrote: 

<blockquote>

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 


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: 

<blockquote>

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



_______________________________________________
windup-dev mailing list windup-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/windup-dev 

</blockquote>

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

</blockquote>

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

</blockquote>

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

</blockquote>




-- 
Lincoln Baxter, III 
http://ocpsoft.org 
"Simpler is better." 

</blockquote>




-- 
Lincoln Baxter, III 
http://ocpsoft.org 
"Simpler is better." 

_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 



_______________________________________________
windup-dev mailing list windup-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/windup-dev 

</blockquote>

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150423/38d888a3/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 172297 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150423/38d888a3/attachment-0001.png 

From itewk at redhat.com  Sat Apr 25 09:37:24 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Sat, 25 Apr 2015 09:37:24 -0400 (EDT)
Subject: [windup-dev] Could not find artifact
 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
 jboss-public-repository-group
In-Reply-To: <1782889413.4700886.1429968999727.JavaMail.zimbra@redhat.com>
Message-ID: <297971927.4700897.1429969044617.JavaMail.zimbra@redhat.com>



Trying to get the latest master branch of the plugin compiling. 




What am I missing? 




[ERROR] Failed to execute goal on project org.jboss.tools.windup.runtime: Could not resolve dependencies for project org.jboss.tools.windup.plugins:org.jboss.tools.windup.runtime:eclipse-plugin:3.1.0-SNAPSHOT: Could not find artifact org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] 







Blue Skies, 

~Ian 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150425/b2a3b3b2/attachment.html 

From itewk at redhat.com  Sat Apr 25 09:47:23 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Sat, 25 Apr 2015 09:47:23 -0400 (EDT)
Subject: [windup-dev] Could not find artifact
 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
 jboss-public-repository-group
In-Reply-To: <297971927.4700897.1429969044617.JavaMail.zimbra@redhat.com>
References: <297971927.4700897.1429969044617.JavaMail.zimbra@redhat.com>
Message-ID: <328794499.4701305.1429969643677.JavaMail.zimbra@redhat.com>

I found the windup-distribution project on git. But trying to build that I get: 

[ERROR] Failed to execute goal on project windup-distribution: Could not resolve dependencies for project org.jboss.windup:windup-distribution:pom:2.3.0-SNAPSHOT: Could not find artifact org.jboss.windup.rules:windup-rulesets:jar:2.3.0-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) 

I know I am missing something dumb here. 

~Ian 

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

From: "Ian Tewksbury" <itewk at redhat.com> 
To: "Windup-dev List" <windup-dev at lists.jboss.org> 
Sent: Saturday, April 25, 2015 9:37:24 AM 
Subject: [windup-dev] Could not find artifact org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in jboss-public-repository-group 



Trying to get the latest master branch of the plugin compiling. 




What am I missing? 




[ERROR] Failed to execute goal on project org.jboss.tools.windup.runtime: Could not resolve dependencies for project org.jboss.tools.windup.plugins:org.jboss.tools.windup.runtime:eclipse-plugin:3.1.0-SNAPSHOT: Could not find artifact org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] 







Blue Skies, 

~Ian 


_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150425/936ab4b0/attachment.html 

From itewk at redhat.com  Sat Apr 25 10:12:47 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Sat, 25 Apr 2015 10:12:47 -0400 (EDT)
Subject: [windup-dev] Could not find artifact
 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
 jboss-public-repository-group
In-Reply-To: <328794499.4701305.1429969643677.JavaMail.zimbra@redhat.com>
References: <297971927.4700897.1429969044617.JavaMail.zimbra@redhat.com>
	<328794499.4701305.1429969643677.JavaMail.zimbra@redhat.com>
Message-ID: <484943168.4701566.1429971167539.JavaMail.zimbra@redhat.com>

Nevermind. 

I found the rulesets project too. 

Compiling and all tests passing. 

Woot. Thank you guys so much for getting this working. 

Now for the fun bits. 

~Ian 

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

From: "Ian Tewksbury" <itewk at redhat.com> 
To: "Windup-dev List" <windup-dev at lists.jboss.org> 
Sent: Saturday, April 25, 2015 9:47:23 AM 
Subject: Re: [windup-dev] Could not find artifact org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in jboss-public-repository-group 

I found the windup-distribution project on git. But trying to build that I get: 

[ERROR] Failed to execute goal on project windup-distribution: Could not resolve dependencies for project org.jboss.windup:windup-distribution:pom:2.3.0-SNAPSHOT: Could not find artifact org.jboss.windup.rules:windup-rulesets:jar:2.3.0-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) 

I know I am missing something dumb here. 

~Ian 

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

From: "Ian Tewksbury" <itewk at redhat.com> 
To: "Windup-dev List" <windup-dev at lists.jboss.org> 
Sent: Saturday, April 25, 2015 9:37:24 AM 
Subject: [windup-dev] Could not find artifact org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in jboss-public-repository-group 



Trying to get the latest master branch of the plugin compiling. 




What am I missing? 




[ERROR] Failed to execute goal on project org.jboss.tools.windup.runtime: Could not resolve dependencies for project org.jboss.tools.windup.plugins:org.jboss.tools.windup.runtime:eclipse-plugin:3.1.0-SNAPSHOT: Could not find artifact org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] 







Blue Skies, 

~Ian 


_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 


_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150425/d43620b7/attachment.html 

From lincolnbaxter at gmail.com  Sat Apr 25 12:01:41 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Sat, 25 Apr 2015 12:01:41 -0400
Subject: [windup-dev] Could not find artifact
 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
 jboss-public-repository-group
In-Reply-To: <484943168.4701566.1429971167539.JavaMail.zimbra@redhat.com>
References: <297971927.4700897.1429969044617.JavaMail.zimbra@redhat.com>
	<328794499.4701305.1429969643677.JavaMail.zimbra@redhat.com>
	<484943168.4701566.1429971167539.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4FAuFbCftWiE2uFLSitf+3aSFAvbZXK-PW9AYQiCWiykw@mail.gmail.com>

Haha, yes, we moved things around a bit ;) Glad you got if found and
working, you're very welcome. Jess and George really did the hard work.

On Sat, Apr 25, 2015 at 10:12 AM, Ian Tewksbury <itewk at redhat.com> wrote:

> Nevermind.
>
> I found the rulesets project too.
>
> Compiling and all tests passing.
>
> Woot. Thank you guys so much for getting this working.
>
> Now for the fun bits.
>
> ~Ian
>
> ------------------------------
> *From: *"Ian Tewksbury" <itewk at redhat.com>
> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
> *Sent: *Saturday, April 25, 2015 9:47:23 AM
> *Subject: *Re: [windup-dev] Could not find artifact
> org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
> jboss-public-repository-group
>
>
> I found the windup-distribution project on git. But trying to build that I
> get:
>
> [ERROR] Failed to execute goal on project windup-distribution: Could not
> resolve dependencies for project
> org.jboss.windup:windup-distribution:pom:2.3.0-SNAPSHOT: Could not find
> artifact org.jboss.windup.rules:windup-rulesets:jar:2.3.0-SNAPSHOT in
> jboss-public-repository-group (
> http://repository.jboss.org/nexus/content/groups/public/)
>
> I know I am missing something dumb here.
>
> ~Ian
>
> ------------------------------
> *From: *"Ian Tewksbury" <itewk at redhat.com>
> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
> *Sent: *Saturday, April 25, 2015 9:37:24 AM
> *Subject: *[windup-dev] Could not find artifact
> org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
> jboss-public-repository-group
>
> Trying to get the latest master branch of the plugin compiling.
>
>
> What am I missing?
>
>
> [ERROR] Failed to execute goal on project org.jboss.tools.windup.runtime:
> Could not resolve dependencies for project
> org.jboss.tools.windup.plugins:org.jboss.tools.windup.runtime:eclipse-plugin:3.1.0-SNAPSHOT:
> Could not find artifact
> org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
> jboss-public-repository-group (
> http://repository.jboss.org/nexus/content/groups/public/) -> [Help 1]
>
>
>
> Blue Skies,
>
> ~Ian
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
> _______________________________________________
> 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/20150425/917aaba4/attachment.html 

From sgilda at redhat.com  Mon Apr 27 06:57:38 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Mon, 27 Apr 2015 06:57:38 -0400
Subject: [windup-dev] Could not find artifact
 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
 jboss-public-repository-group
In-Reply-To: <CAEp_U4FAuFbCftWiE2uFLSitf+3aSFAvbZXK-PW9AYQiCWiykw@mail.gmail.com>
References: <297971927.4700897.1429969044617.JavaMail.zimbra@redhat.com>	<328794499.4701305.1429969643677.JavaMail.zimbra@redhat.com>	<484943168.4701566.1429971167539.JavaMail.zimbra@redhat.com>
	<CAEp_U4FAuFbCftWiE2uFLSitf+3aSFAvbZXK-PW9AYQiCWiykw@mail.gmail.com>
Message-ID: <553E1622.5080406@redhat.com>

This reminds me! I believe I need to update the Wiki documentation [1] 
to talk about the windup-rulesets repository.

Ian, Is there anything else I need to update to prevent confusion for 
others?

[1] https://github.com/windup/windup/wiki/Dev-Get-the-Windup-Source-Code

On 04/25/2015 12:01 PM, Lincoln Baxter, III wrote:
> Haha, yes, we moved things around a bit ;) Glad you got if found and 
> working, you're very welcome. Jess and George really did the hard work.
>
> On Sat, Apr 25, 2015 at 10:12 AM, Ian Tewksbury <itewk at redhat.com 
> <mailto:itewk at redhat.com>> wrote:
>
>     Nevermind.
>
>     I found the rulesets project too.
>
>     Compiling and all tests passing.
>
>     Woot. Thank you guys so much for getting this working.
>
>     Now for the fun bits.
>
>     ~Ian
>
>     ------------------------------------------------------------------------
>     *From: *"Ian Tewksbury" <itewk at redhat.com <mailto:itewk at redhat.com>>
>     *To: *"Windup-dev List" <windup-dev at lists.jboss.org
>     <mailto:windup-dev at lists.jboss.org>>
>     *Sent: *Saturday, April 25, 2015 9:47:23 AM
>     *Subject: *Re: [windup-dev] Could not find artifact
>     org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
>     jboss-public-repository-group
>
>
>     I found the windup-distribution project on git. But trying to
>     build that I get:
>
>     [ERROR] Failed to execute goal on project windup-distribution:
>     Could not resolve dependencies for project
>     org.jboss.windup:windup-distribution:pom:2.3.0-SNAPSHOT: Could not
>     find artifact
>     org.jboss.windup.rules:windup-rulesets:jar:2.3.0-SNAPSHOT in
>     jboss-public-repository-group
>     (http://repository.jboss.org/nexus/content/groups/public/)
>
>     I know I am missing something dumb here.
>
>     ~Ian
>
>     ------------------------------------------------------------------------
>     *From: *"Ian Tewksbury" <itewk at redhat.com <mailto:itewk at redhat.com>>
>     *To: *"Windup-dev List" <windup-dev at lists.jboss.org
>     <mailto:windup-dev at lists.jboss.org>>
>     *Sent: *Saturday, April 25, 2015 9:37:24 AM
>     *Subject: *[windup-dev] Could not find artifact
>     org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
>     jboss-public-repository-group
>
>     Trying to get the latest master branch of the plugin compiling.
>
>
>     What am I missing?
>
>
>     [ERROR] Failed to execute goal on project
>     org.jboss.tools.windup.runtime: Could not resolve dependencies for
>     project
>     org.jboss.tools.windup.plugins:org.jboss.tools.windup.runtime:eclipse-plugin:3.1.0-SNAPSHOT:
>     Could not find artifact
>     org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
>     jboss-public-repository-group
>     (http://repository.jboss.org/nexus/content/groups/public/) -> [Help 1]
>
>
>
>     Blue Skies,
>
>     ~Ian
>
>
>
>     _______________________________________________
>     windup-dev mailing list
>     windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>     _______________________________________________
>     windup-dev mailing list
>     windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>     _______________________________________________
>     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/20150427/0e8d6f5d/attachment-0001.html 

From itewk at redhat.com  Mon Apr 27 08:21:34 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Mon, 27 Apr 2015 08:21:34 -0400 (EDT)
Subject: [windup-dev] Could not find artifact
 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
 jboss-public-repository-group
In-Reply-To: <553E1622.5080406@redhat.com>
References: <297971927.4700897.1429969044617.JavaMail.zimbra@redhat.com>
	<328794499.4701305.1429969643677.JavaMail.zimbra@redhat.com>
	<484943168.4701566.1429971167539.JavaMail.zimbra@redhat.com>
	<CAEp_U4FAuFbCftWiE2uFLSitf+3aSFAvbZXK-PW9AYQiCWiykw@mail.gmail.com>
	<553E1622.5080406@redhat.com>
Message-ID: <1185704303.4971101.1430137294031.JavaMail.zimbra@redhat.com>

Sande, 

Documentation of the windup-distribution project would be useful. 

~Ian 

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

From: "Sande Gilda" <sgilda at redhat.com> 
To: "Windup-dev List" <windup-dev at lists.jboss.org>, "George Gastaldi" <ggastald at redhat.com> 
Sent: Monday, April 27, 2015 6:57:38 AM 
Subject: Re: [windup-dev] Could not find artifact org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in jboss-public-repository-group 

This reminds me! I believe I need to update the Wiki documentation [1] to talk about the windup-rulesets repository. 

Ian, Is there anything else I need to update to prevent confusion for others? 

[1] https://github.com/windup/windup/wiki/Dev-Get-the-Windup-Source-Code 

On 04/25/2015 12:01 PM, Lincoln Baxter, III wrote: 



Haha, yes, we moved things around a bit ;) Glad you got if found and working, you're very welcome. Jess and George really did the hard work. 

On Sat, Apr 25, 2015 at 10:12 AM, Ian Tewksbury < itewk at redhat.com > wrote: 

<blockquote>

Nevermind. 

I found the rulesets project too. 

Compiling and all tests passing. 

Woot. Thank you guys so much for getting this working. 

Now for the fun bits. 

~Ian 


From: "Ian Tewksbury" < itewk at redhat.com > 
To: "Windup-dev List" < windup-dev at lists.jboss.org > 
Sent: Saturday, April 25, 2015 9:47:23 AM 
Subject: Re: [windup-dev] Could not find artifact org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in jboss-public-repository-group 


I found the windup-distribution project on git. But trying to build that I get: 

[ERROR] Failed to execute goal on project windup-distribution: Could not resolve dependencies for project org.jboss.windup:windup-distribution:pom:2.3.0-SNAPSHOT: Could not find artifact org.jboss.windup.rules:windup-rulesets:jar:2.3.0-SNAPSHOT in jboss-public-repository-group ( http://repository.jboss.org/nexus/content/groups/public/ ) 

I know I am missing something dumb here. 

~Ian 


From: "Ian Tewksbury" < itewk at redhat.com > 
To: "Windup-dev List" < windup-dev at lists.jboss.org > 
Sent: Saturday, April 25, 2015 9:37:24 AM 
Subject: [windup-dev] Could not find artifact org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in jboss-public-repository-group 



Trying to get the latest master branch of the plugin compiling. 




What am I missing? 




[ERROR] Failed to execute goal on project org.jboss.tools.windup.runtime: Could not resolve dependencies for project org.jboss.tools.windup.plugins:org.jboss.tools.windup.runtime:eclipse-plugin:3.1.0-SNAPSHOT: Could not find artifact org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in jboss-public-repository-group ( http://repository.jboss.org/nexus/content/groups/public/ ) -> [Help 1] 







Blue Skies, 

~Ian 


_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 


_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 


_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 






-- 
Lincoln Baxter, III 
http://ocpsoft.org 
"Simpler is better." 


_______________________________________________
windup-dev mailing list windup-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/windup-dev 

</blockquote>


_______________________________________________ 
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/20150427/78cd5943/attachment.html 

From itewk at redhat.com  Mon Apr 27 08:22:27 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Mon, 27 Apr 2015 08:22:27 -0400 (EDT)
Subject: [windup-dev] Ruleset Location API
Message-ID: <97752043.4971307.1430137347398.JavaMail.zimbra@redhat.com>

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 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150427/829edd51/attachment.html 

From itewk at redhat.com  Mon Apr 27 08:24:12 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Mon, 27 Apr 2015 08:24:12 -0400 (EDT)
Subject: [windup-dev] Sugested Fix Hints
In-Reply-To: <34285553.4971460.1430137378250.JavaMail.zimbra@redhat.com>
Message-ID: <941980513.4971941.1430137452508.JavaMail.zimbra@redhat.com>

All, 

Do any of the hints have a "suggested fix" built into them. I was looking at the hint API but didnt see such a thing, but I know it had been talked about in the past. 

If such a thing exists I want to detect hints with "suggested code fixes" and auto generate Eclipse quick fixes for those hints so people can easily apply the quick fixes to knock out the easy stuff in an automated fashion. 

~Ian 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150427/0764f39e/attachment.html 

From itewk at redhat.com  Mon Apr 27 08:31:31 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Mon, 27 Apr 2015 08:31:31 -0400 (EDT)
Subject: [windup-dev] Eclipse Plugin - When to regenerate validation markers
In-Reply-To: <1584136349.4972206.1430137521908.JavaMail.zimbra@redhat.com>
Message-ID: <1626933510.4974726.1430137891179.JavaMail.zimbra@redhat.com>

All, 

With old Windup 1.0 there was a way to regenerate the hints for a single file. Do to the redesign of Windup 2.0 I understand this is currently not possible, and doing so is an undertaking no one has attempted yet, so in the mean time I have a quandary of what to do. 

Typically in eclipse when you edit a file you re-generate the validation markers for that file, so if you fix a validation marker it doesn't still show as busted. Currently without being able to regenerate the hints for a specific file I am unsure what the best option is. 

Options I can think of are: 



    1. do nothing, and just allow stale validation markers to sit on the file even if they have been addressed 
    2. regenerate the entire windup graph every time a file is edited 


        1. could do this just on save rather then on every character type 
        2. how expensive is it to generate the graph? Are there any statistics? 
    3. 
Once a file is changed mark all the windup markers as stale with a message that the graph needs to be regenerated to update them 
    4. Simply remove all windup markers from the edited file until such time as the graph is regenerated 

It used to be that my validator would auto run windup on a project as soon as the validation kicked off. Currently the validator has been changed such that if windup has not been run it simply does not report any windup hints. 

Any thoughts on adding back the bit to at least run windup the first time when validation first kicks off? Right now the user doesn't have any way of knowing that the only reason they are not seeing windup validation markers is they have not manually generated a report. In the old plugin design the generation of an HTML report and the validaton markers were two different actions. It is rather an Eclipse anti practice to have to invoke a secondary menu action, "Windup Generate Report" in this case, to then allow a validator to run correctly. 

Blue Skies, 
~Ian 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150427/bcb1d511/attachment.html 

From itewk at redhat.com  Mon Apr 27 08:32:44 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Mon, 27 Apr 2015 08:32:44 -0400 (EDT)
Subject: [windup-dev] Eclipse Plugin - allow user to specify ignored files
Message-ID: <1151659169.4975202.1430137964430.JavaMail.zimbra@redhat.com>

All, 

Currently the eclipse plugin is hard coded to only ignore .class$ files. Would it make sense to add a preference dialog where users could specify other ignore rules? 

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

From sgilda at redhat.com  Mon Apr 27 08:41:35 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Mon, 27 Apr 2015 08:41:35 -0400
Subject: [windup-dev] Could not find artifact
 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
 jboss-public-repository-group
In-Reply-To: <1185704303.4971101.1430137294031.JavaMail.zimbra@redhat.com>
References: <297971927.4700897.1429969044617.JavaMail.zimbra@redhat.com>
	<328794499.4701305.1429969643677.JavaMail.zimbra@redhat.com>
	<484943168.4701566.1429971167539.JavaMail.zimbra@redhat.com>
	<CAEp_U4FAuFbCftWiE2uFLSitf+3aSFAvbZXK-PW9AYQiCWiykw@mail.gmail.com>
	<553E1622.5080406@redhat.com>
	<1185704303.4971101.1430137294031.JavaMail.zimbra@redhat.com>
Message-ID: <553E2E7F.4080303@redhat.com>

Hi Ian,

Are you referring to the download distribution described here: 
https://github.com/windup/windup/wiki/Install-Windup ?

What kind of information are you looking for? A description of the 
directory structure? Something else?

Thanks,
Sande

On 04/27/2015 08:21 AM, Ian Tewksbury wrote:
> Sande,
>
> Documentation of the windup-distribution project would be useful.
>
> ~Ian
>
> ------------------------------------------------------------------------
> *From: *"Sande Gilda" <sgilda at redhat.com>
> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>, "George 
> Gastaldi" <ggastald at redhat.com>
> *Sent: *Monday, April 27, 2015 6:57:38 AM
> *Subject: *Re: [windup-dev] Could not find artifact 
> org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in 
> jboss-public-repository-group
>
> This reminds me! I believe I need to update the Wiki documentation [1] 
> to talk about the windup-rulesets repository.
>
> Ian, Is there anything else I need to update to prevent confusion for 
> others?
>
> [1] https://github.com/windup/windup/wiki/Dev-Get-the-Windup-Source-Code
>
> On 04/25/2015 12:01 PM, Lincoln Baxter, III wrote:
>
>     Haha, yes, we moved things around a bit ;) Glad you got if found
>     and working, you're very welcome. Jess and George really did the
>     hard work.
>
>     On Sat, Apr 25, 2015 at 10:12 AM, Ian Tewksbury <itewk at redhat.com
>     <mailto:itewk at redhat.com>> wrote:
>
>         Nevermind.
>
>         I found the rulesets project too.
>
>         Compiling and all tests passing.
>
>         Woot. Thank you guys so much for getting this working.
>
>         Now for the fun bits.
>
>         ~Ian
>
>         ------------------------------------------------------------------------
>         *From: *"Ian Tewksbury" <itewk at redhat.com
>         <mailto:itewk at redhat.com>>
>         *To: *"Windup-dev List" <windup-dev at lists.jboss.org
>         <mailto:windup-dev at lists.jboss.org>>
>         *Sent: *Saturday, April 25, 2015 9:47:23 AM
>         *Subject: *Re: [windup-dev] Could not find artifact
>         org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
>         jboss-public-repository-group
>
>
>         I found the windup-distribution project on git. But trying to
>         build that I get:
>
>         [ERROR] Failed to execute goal on project windup-distribution:
>         Could not resolve dependencies for project
>         org.jboss.windup:windup-distribution:pom:2.3.0-SNAPSHOT: Could
>         not find artifact
>         org.jboss.windup.rules:windup-rulesets:jar:2.3.0-SNAPSHOT in
>         jboss-public-repository-group
>         (http://repository.jboss.org/nexus/content/groups/public/)
>
>         I know I am missing something dumb here.
>
>         ~Ian
>
>         ------------------------------------------------------------------------
>         *From: *"Ian Tewksbury" <itewk at redhat.com
>         <mailto:itewk at redhat.com>>
>         *To: *"Windup-dev List" <windup-dev at lists.jboss.org
>         <mailto:windup-dev at lists.jboss.org>>
>         *Sent: *Saturday, April 25, 2015 9:37:24 AM
>         *Subject: *[windup-dev] Could not find artifact
>         org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
>         jboss-public-repository-group
>
>         Trying to get the latest master branch of the plugin compiling.
>
>
>         What am I missing?
>
>
>         [ERROR] Failed to execute goal on project
>         org.jboss.tools.windup.runtime: Could not resolve dependencies
>         for project
>         org.jboss.tools.windup.plugins:org.jboss.tools.windup.runtime:eclipse-plugin:3.1.0-SNAPSHOT:
>         Could not find artifact
>         org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
>         jboss-public-repository-group
>         (http://repository.jboss.org/nexus/content/groups/public/) ->
>         [Help 1]
>
>
>
>         Blue Skies,
>
>         ~Ian
>
>
>
>         _______________________________________________
>         windup-dev mailing list
>         windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>         https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>         _______________________________________________
>         windup-dev mailing list
>         windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>         https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>         _______________________________________________
>         windup-dev mailing list
>         windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>         https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
>     -- 
>     Lincoln Baxter, III
>     http://ocpsoft.org
>     "Simpler is better."
>
>
>     _______________________________________________
>     windup-dev mailing list
>     windup-dev at lists.jboss.org
>     https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150427/4fe465cb/attachment.html 

From jsightle at redhat.com  Mon Apr 27 10:32:38 2015
From: jsightle at redhat.com (Jess Sightler)
Date: Mon, 27 Apr 2015 10:32:38 -0400
Subject: [windup-dev] Could not find artifact
 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
 jboss-public-repository-group
In-Reply-To: <553E2E7F.4080303@redhat.com>
References: <297971927.4700897.1429969044617.JavaMail.zimbra@redhat.com>	<328794499.4701305.1429969643677.JavaMail.zimbra@redhat.com>	<484943168.4701566.1429971167539.JavaMail.zimbra@redhat.com>	<CAEp_U4FAuFbCftWiE2uFLSitf+3aSFAvbZXK-PW9AYQiCWiykw@mail.gmail.com>	<553E1622.5080406@redhat.com>	<1185704303.4971101.1430137294031.JavaMail.zimbra@redhat.com>
	<553E2E7F.4080303@redhat.com>
Message-ID: <553E4886.4000901@redhat.com>

I think that he means documentation of how to get the source code and 
build it. windup-distribution is a required module now and is separat_e 
from the other two._

On 04/27/2015 08:41 AM, Sande Gilda wrote:
> Hi Ian,
>
> Are you referring to the download distribution described here: 
> https://github.com/windup/windup/wiki/Install-Windup ?
>
> What kind of information are you looking for? A description of the 
> directory structure? Something else?
>
> Thanks,
> Sande
>
> On 04/27/2015 08:21 AM, Ian Tewksbury wrote:
>> Sande,
>>
>> Documentation of the windup-distribution project would be useful.
>>
>> ~Ian
>>
>> ------------------------------------------------------------------------
>> *From: *"Sande Gilda" <sgilda at redhat.com>
>> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>, "George 
>> Gastaldi" <ggastald at redhat.com>
>> *Sent: *Monday, April 27, 2015 6:57:38 AM
>> *Subject: *Re: [windup-dev] Could not find artifact 
>> org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in 
>> jboss-public-repository-group
>>
>> This reminds me! I believe I need to update the Wiki documentation 
>> [1] to talk about the windup-rulesets repository.
>>
>> Ian, Is there anything else I need to update to prevent confusion for 
>> others?
>>
>> [1] https://github.com/windup/windup/wiki/Dev-Get-the-Windup-Source-Code
>>
>> On 04/25/2015 12:01 PM, Lincoln Baxter, III wrote:
>>
>>     Haha, yes, we moved things around a bit ;) Glad you got if found
>>     and working, you're very welcome. Jess and George really did the
>>     hard work.
>>
>>     On Sat, Apr 25, 2015 at 10:12 AM, Ian Tewksbury <itewk at redhat.com
>>     <mailto:itewk at redhat.com>> wrote:
>>
>>         Nevermind.
>>
>>         I found the rulesets project too.
>>
>>         Compiling and all tests passing.
>>
>>         Woot. Thank you guys so much for getting this working.
>>
>>         Now for the fun bits.
>>
>>         ~Ian
>>
>>         ------------------------------------------------------------------------
>>         *From: *"Ian Tewksbury" <itewk at redhat.com
>>         <mailto:itewk at redhat.com>>
>>         *To: *"Windup-dev List" <windup-dev at lists.jboss.org
>>         <mailto:windup-dev at lists.jboss.org>>
>>         *Sent: *Saturday, April 25, 2015 9:47:23 AM
>>         *Subject: *Re: [windup-dev] Could not find artifact
>>         org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT
>>         in jboss-public-repository-group
>>
>>
>>         I found the windup-distribution project on git. But trying to
>>         build that I get:
>>
>>         [ERROR] Failed to execute goal on project
>>         windup-distribution: Could not resolve dependencies for
>>         project
>>         org.jboss.windup:windup-distribution:pom:2.3.0-SNAPSHOT:
>>         Could not find artifact
>>         org.jboss.windup.rules:windup-rulesets:jar:2.3.0-SNAPSHOT in
>>         jboss-public-repository-group
>>         (http://repository.jboss.org/nexus/content/groups/public/)
>>
>>         I know I am missing something dumb here.
>>
>>         ~Ian
>>
>>         ------------------------------------------------------------------------
>>         *From: *"Ian Tewksbury" <itewk at redhat.com
>>         <mailto:itewk at redhat.com>>
>>         *To: *"Windup-dev List" <windup-dev at lists.jboss.org
>>         <mailto:windup-dev at lists.jboss.org>>
>>         *Sent: *Saturday, April 25, 2015 9:37:24 AM
>>         *Subject: *[windup-dev] Could not find artifact
>>         org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT
>>         in jboss-public-repository-group
>>
>>         Trying to get the latest master branch of the plugin compiling.
>>
>>
>>         What am I missing?
>>
>>
>>         [ERROR] Failed to execute goal on project
>>         org.jboss.tools.windup.runtime: Could not resolve
>>         dependencies for project
>>         org.jboss.tools.windup.plugins:org.jboss.tools.windup.runtime:eclipse-plugin:3.1.0-SNAPSHOT:
>>         Could not find artifact
>>         org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT
>>         in jboss-public-repository-group
>>         (http://repository.jboss.org/nexus/content/groups/public/) ->
>>         [Help 1]
>>
>>
>>
>>         Blue Skies,
>>
>>         ~Ian
>>
>>
>>
>>         _______________________________________________
>>         windup-dev mailing list
>>         windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>>         https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>         _______________________________________________
>>         windup-dev mailing list
>>         windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>>         https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>         _______________________________________________
>>         windup-dev mailing list
>>         windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>>         https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>>
>>     -- 
>>     Lincoln Baxter, III
>>     http://ocpsoft.org
>>     "Simpler is better."
>>
>>
>>     _______________________________________________
>>     windup-dev mailing list
>>     windup-dev at lists.jboss.org
>>     https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev

-- 
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/20150427/bbaf3331/attachment-0001.html 

From itewk at redhat.com  Mon Apr 27 10:45:01 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Mon, 27 Apr 2015 10:45:01 -0400 (EDT)
Subject: [windup-dev] Could not find artifact
 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
 jboss-public-repository-group
In-Reply-To: <553E4886.4000901@redhat.com>
References: <297971927.4700897.1429969044617.JavaMail.zimbra@redhat.com>
	<328794499.4701305.1429969643677.JavaMail.zimbra@redhat.com>
	<484943168.4701566.1429971167539.JavaMail.zimbra@redhat.com>
	<CAEp_U4FAuFbCftWiE2uFLSitf+3aSFAvbZXK-PW9AYQiCWiykw@mail.gmail.com>
	<553E1622.5080406@redhat.com>
	<1185704303.4971101.1430137294031.JavaMail.zimbra@redhat.com>
	<553E2E7F.4080303@redhat.com> <553E4886.4000901@redhat.com>
Message-ID: <334217888.5051117.1430145901444.JavaMail.zimbra@redhat.com>

Sande, 

Jess is correct. Currently the windup-distribution project has no README. Then we need some additions to the eclipse plugin README to include how to build, need to download the three windup projects, make sure you have the latest forge. So forth and so on. 

~Ian 


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

From: "Jess Sightler" <jsightle at redhat.com> 
To: windup-dev at lists.jboss.org 
Sent: Monday, April 27, 2015 10:32:38 AM 
Subject: Re: [windup-dev] Could not find artifact org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in jboss-public-repository-group 

I think that he means documentation of how to get the source code and build it. windup-distribution is a required module now and is separat e from the other two. 

On 04/27/2015 08:41 AM, Sande Gilda wrote: 


Hi Ian, 

Are you referring to the download distribution described here: https://github.com/windup/windup/wiki/Install-Windup ? 

What kind of information are you looking for? A description of the directory structure? Something else? 

Thanks, 
Sande 

On 04/27/2015 08:21 AM, Ian Tewksbury wrote: 

<blockquote>

Sande, 

Documentation of the windup-distribution project would be useful. 

~Ian 

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

From: "Sande Gilda" <sgilda at redhat.com> 
To: "Windup-dev List" <windup-dev at lists.jboss.org> , "George Gastaldi" <ggastald at redhat.com> 
Sent: Monday, April 27, 2015 6:57:38 AM 
Subject: Re: [windup-dev] Could not find artifact org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in jboss-public-repository-group 

This reminds me! I believe I need to update the Wiki documentation [1] to talk about the windup-rulesets repository. 

Ian, Is there anything else I need to update to prevent confusion for others? 

[1] https://github.com/windup/windup/wiki/Dev-Get-the-Windup-Source-Code 

On 04/25/2015 12:01 PM, Lincoln Baxter, III wrote: 

<blockquote>

Haha, yes, we moved things around a bit ;) Glad you got if found and working, you're very welcome. Jess and George really did the hard work. 

On Sat, Apr 25, 2015 at 10:12 AM, Ian Tewksbury < itewk at redhat.com > wrote: 

<blockquote>

Nevermind. 

I found the rulesets project too. 

Compiling and all tests passing. 

Woot. Thank you guys so much for getting this working. 

Now for the fun bits. 

~Ian 


From: "Ian Tewksbury" < itewk at redhat.com > 
To: "Windup-dev List" < windup-dev at lists.jboss.org > 
Sent: Saturday, April 25, 2015 9:47:23 AM 
Subject: Re: [windup-dev] Could not find artifact org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in jboss-public-repository-group 


I found the windup-distribution project on git. But trying to build that I get: 

[ERROR] Failed to execute goal on project windup-distribution: Could not resolve dependencies for project org.jboss.windup:windup-distribution:pom:2.3.0-SNAPSHOT: Could not find artifact org.jboss.windup.rules:windup-rulesets:jar:2.3.0-SNAPSHOT in jboss-public-repository-group ( http://repository.jboss.org/nexus/content/groups/public/ ) 

I know I am missing something dumb here. 

~Ian 


From: "Ian Tewksbury" < itewk at redhat.com > 
To: "Windup-dev List" < windup-dev at lists.jboss.org > 
Sent: Saturday, April 25, 2015 9:37:24 AM 
Subject: [windup-dev] Could not find artifact org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in jboss-public-repository-group 



Trying to get the latest master branch of the plugin compiling. 




What am I missing? 




[ERROR] Failed to execute goal on project org.jboss.tools.windup.runtime: Could not resolve dependencies for project org.jboss.tools.windup.plugins:org.jboss.tools.windup.runtime:eclipse-plugin:3.1.0-SNAPSHOT: Could not find artifact org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in jboss-public-repository-group ( http://repository.jboss.org/nexus/content/groups/public/ ) -> [Help 1] 







Blue Skies, 

~Ian 


_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 


_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 


_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 






-- 
Lincoln Baxter, III 
http://ocpsoft.org 
"Simpler is better." 


_______________________________________________
windup-dev mailing list windup-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/windup-dev 

</blockquote>


_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 


</blockquote>



_______________________________________________
windup-dev mailing list windup-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/windup-dev 

</blockquote>

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150427/2ee9b0fb/attachment.html 

From sgilda at redhat.com  Mon Apr 27 11:28:44 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Mon, 27 Apr 2015 11:28:44 -0400
Subject: [windup-dev] Could not find artifact
 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
 jboss-public-repository-group
In-Reply-To: <334217888.5051117.1430145901444.JavaMail.zimbra@redhat.com>
References: <297971927.4700897.1429969044617.JavaMail.zimbra@redhat.com>	<328794499.4701305.1429969643677.JavaMail.zimbra@redhat.com>	<484943168.4701566.1429971167539.JavaMail.zimbra@redhat.com>	<CAEp_U4FAuFbCftWiE2uFLSitf+3aSFAvbZXK-PW9AYQiCWiykw@mail.gmail.com>	<553E1622.5080406@redhat.com>	<1185704303.4971101.1430137294031.JavaMail.zimbra@redhat.com>	<553E2E7F.4080303@redhat.com>
	<553E4886.4000901@redhat.com>
	<334217888.5051117.1430145901444.JavaMail.zimbra@redhat.com>
Message-ID: <553E55AC.1070100@redhat.com>

These are 2 different things.

How to get the source code and build it is documented here: 
https://github.com/windup/windup/wiki/Core-Development-Guide#prepare-your-development-environment

A README file for the distribution is a different thing. It doesn't look 
like we do that for other products. I just unzipped the JBoss EAP 6.4 
distribution and verified that. In most cases, won't they be finding the 
distribution location from the Wiki or from the documentation? One thing 
to keeps in mind is that the target audience for the Windup distribution 
can vary. Would inclusion of a README that contains links to existing 
documentation be sufficient? Or do you think something more?

Sande


On 04/27/2015 10:45 AM, Ian Tewksbury wrote:
> Sande,
>
> Jess is correct. Currently the windup-distribution project has no 
> README. Then we need some additions to the eclipse plugin README to 
> include how to build, need to download the three windup projects, make 
> sure you have the latest forge. So forth and so on.
>
> ~Ian
>
>
> ------------------------------------------------------------------------
> *From: *"Jess Sightler" <jsightle at redhat.com>
> *To: *windup-dev at lists.jboss.org
> *Sent: *Monday, April 27, 2015 10:32:38 AM
> *Subject: *Re: [windup-dev] Could not find artifact 
> org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in 
> jboss-public-repository-group
>
> I think that he means documentation of how to get the source code and 
> build it. windup-distribution is a required module now and is separate 
> from the other two.
>
> On 04/27/2015 08:41 AM, Sande Gilda wrote:
>
>     Hi Ian,
>
>     Are you referring to the download distribution described here:
>     https://github.com/windup/windup/wiki/Install-Windup ?
>
>     What kind of information are you looking for? A description of the
>     directory structure? Something else?
>
>     Thanks,
>     Sande
>
>     On 04/27/2015 08:21 AM, Ian Tewksbury wrote:
>
>         Sande,
>
>         Documentation of the windup-distribution project would be useful.
>
>         ~Ian
>
>         ------------------------------------------------------------------------
>         *From: *"Sande Gilda" <sgilda at redhat.com>
>         *To: *"Windup-dev List" <windup-dev at lists.jboss.org>, "George
>         Gastaldi" <ggastald at redhat.com>
>         *Sent: *Monday, April 27, 2015 6:57:38 AM
>         *Subject: *Re: [windup-dev] Could not find artifact
>         org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
>         jboss-public-repository-group
>
>         This reminds me! I believe I need to update the Wiki
>         documentation [1] to talk about the windup-rulesets repository.
>
>         Ian, Is there anything else I need to update to prevent
>         confusion for others?
>
>         [1]
>         https://github.com/windup/windup/wiki/Dev-Get-the-Windup-Source-Code
>
>         On 04/25/2015 12:01 PM, Lincoln Baxter, III wrote:
>
>             Haha, yes, we moved things around a bit ;) Glad you got if
>             found and working, you're very welcome. Jess and George
>             really did the hard work.
>
>             On Sat, Apr 25, 2015 at 10:12 AM, Ian Tewksbury
>             <itewk at redhat.com <mailto:itewk at redhat.com>> wrote:
>
>                 Nevermind.
>
>                 I found the rulesets project too.
>
>                 Compiling and all tests passing.
>
>                 Woot. Thank you guys so much for getting this working.
>
>                 Now for the fun bits.
>
>                 ~Ian
>
>                 ------------------------------------------------------------------------
>                 *From: *"Ian Tewksbury" <itewk at redhat.com
>                 <mailto:itewk at redhat.com>>
>                 *To: *"Windup-dev List" <windup-dev at lists.jboss.org
>                 <mailto:windup-dev at lists.jboss.org>>
>                 *Sent: *Saturday, April 25, 2015 9:47:23 AM
>                 *Subject: *Re: [windup-dev] Could not find artifact
>                 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT
>                 in jboss-public-repository-group
>
>
>                 I found the windup-distribution project on git. But
>                 trying to build that I get:
>
>                 [ERROR] Failed to execute goal on project
>                 windup-distribution: Could not resolve dependencies
>                 for project
>                 org.jboss.windup:windup-distribution:pom:2.3.0-SNAPSHOT:
>                 Could not find artifact
>                 org.jboss.windup.rules:windup-rulesets:jar:2.3.0-SNAPSHOT
>                 in jboss-public-repository-group
>                 (http://repository.jboss.org/nexus/content/groups/public/)
>
>
>                 I know I am missing something dumb here.
>
>                 ~Ian
>
>                 ------------------------------------------------------------------------
>                 *From: *"Ian Tewksbury" <itewk at redhat.com
>                 <mailto:itewk at redhat.com>>
>                 *To: *"Windup-dev List" <windup-dev at lists.jboss.org
>                 <mailto:windup-dev at lists.jboss.org>>
>                 *Sent: *Saturday, April 25, 2015 9:37:24 AM
>                 *Subject: *[windup-dev] Could not find artifact
>                 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT
>                 in jboss-public-repository-group
>
>                 Trying to get the latest master branch of the plugin
>                 compiling.
>
>
>                 What am I missing?
>
>
>                 [ERROR] Failed to execute goal on project
>                 org.jboss.tools.windup.runtime: Could not resolve
>                 dependencies for project
>                 org.jboss.tools.windup.plugins:org.jboss.tools.windup.runtime:eclipse-plugin:3.1.0-SNAPSHOT:
>                 Could not find artifact
>                 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT
>                 in jboss-public-repository-group
>                 (http://repository.jboss.org/nexus/content/groups/public/)
>                 -> [Help 1]
>
>
>
>                 Blue Skies,
>
>                 ~Ian
>
>
>
>                 _______________________________________________
>                 windup-dev mailing list
>                 windup-dev at lists.jboss.org
>                 <mailto:windup-dev at lists.jboss.org>
>                 https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>                 _______________________________________________
>                 windup-dev mailing list
>                 windup-dev at lists.jboss.org
>                 <mailto:windup-dev at lists.jboss.org>
>                 https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>                 _______________________________________________
>                 windup-dev mailing list
>                 windup-dev at lists.jboss.org
>                 <mailto:windup-dev at lists.jboss.org>
>                 https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
>             -- 
>             Lincoln Baxter, III
>             http://ocpsoft.org
>             "Simpler is better."
>
>
>             _______________________________________________
>             windup-dev mailing list
>             windup-dev at lists.jboss.org
>             https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>         _______________________________________________
>         windup-dev mailing list
>         windup-dev at lists.jboss.org
>         https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
>     _______________________________________________
>     windup-dev mailing list
>     windup-dev at lists.jboss.org
>     https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
> -- 
> 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

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

From jsightle at redhat.com  Mon Apr 27 11:48:44 2015
From: jsightle at redhat.com (Jess Sightler)
Date: Mon, 27 Apr 2015 11:48:44 -0400
Subject: [windup-dev] Could not find artifact
 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
 jboss-public-repository-group
In-Reply-To: <553E55AC.1070100@redhat.com>
References: <297971927.4700897.1429969044617.JavaMail.zimbra@redhat.com>	<328794499.4701305.1429969643677.JavaMail.zimbra@redhat.com>	<484943168.4701566.1429971167539.JavaMail.zimbra@redhat.com>	<CAEp_U4FAuFbCftWiE2uFLSitf+3aSFAvbZXK-PW9AYQiCWiykw@mail.gmail.com>	<553E1622.5080406@redhat.com>	<1185704303.4971101.1430137294031.JavaMail.zimbra@redhat.com>	<553E2E7F.4080303@redhat.com>	<553E4886.4000901@redhat.com>	<334217888.5051117.1430145901444.JavaMail.zimbra@redhat.com>
	<553E55AC.1070100@redhat.com>
Message-ID: <553E5A5C.2010000@redhat.com>

Hi Sande,

We are referring to this:
https://github.com/windup/windup-distribution/

This project is part of the windup source code and is consumed by the 
windup-eclipse-plugin as a build dependency as well.

Without this, it isn't possible to build a running copy of windup. So 
this should be part of the build instructions, right?

Thanks,
Jess


On 04/27/2015 11:28 AM, Sande Gilda wrote:
> These are 2 different things.
>
> How to get the source code and build it is documented here: 
> https://github.com/windup/windup/wiki/Core-Development-Guide#prepare-your-development-environment
>
> A README file for the distribution is a different thing. It doesn't 
> look like we do that for other products. I just unzipped the JBoss EAP 
> 6.4 distribution and verified that. In most cases, won't they be 
> finding the distribution location from the Wiki or from the 
> documentation? One thing to keeps in mind is that the target audience 
> for the Windup distribution can vary. Would inclusion of a README that 
> contains links to existing documentation be sufficient? Or do you 
> think something more?
>
> Sande
>
>
> On 04/27/2015 10:45 AM, Ian Tewksbury wrote:
>> Sande,
>>
>> Jess is correct. Currently the windup-distribution project has no 
>> README. Then we need some additions to the eclipse plugin README to 
>> include how to build, need to download the three windup projects, 
>> make sure you have the latest forge. So forth and so on.
>>
>> ~Ian
>>
>>
>> ------------------------------------------------------------------------
>> *From: *"Jess Sightler" <jsightle at redhat.com>
>> *To: *windup-dev at lists.jboss.org
>> *Sent: *Monday, April 27, 2015 10:32:38 AM
>> *Subject: *Re: [windup-dev] Could not find artifact 
>> org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in 
>> jboss-public-repository-group
>>
>> I think that he means documentation of how to get the source code and 
>> build it. windup-distribution is a required module now and is 
>> separate from the other two.
>>
>> On 04/27/2015 08:41 AM, Sande Gilda wrote:
>>
>>     Hi Ian,
>>
>>     Are you referring to the download distribution described here:
>>     https://github.com/windup/windup/wiki/Install-Windup ?
>>
>>     What kind of information are you looking for? A description of
>>     the directory structure? Something else?
>>
>>     Thanks,
>>     Sande
>>
>>     On 04/27/2015 08:21 AM, Ian Tewksbury wrote:
>>
>>         Sande,
>>
>>         Documentation of the windup-distribution project would be useful.
>>
>>         ~Ian
>>
>>         ------------------------------------------------------------------------
>>         *From: *"Sande Gilda" <sgilda at redhat.com>
>>         *To: *"Windup-dev List" <windup-dev at lists.jboss.org>, "George
>>         Gastaldi" <ggastald at redhat.com>
>>         *Sent: *Monday, April 27, 2015 6:57:38 AM
>>         *Subject: *Re: [windup-dev] Could not find artifact
>>         org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT
>>         in jboss-public-repository-group
>>
>>         This reminds me! I believe I need to update the Wiki
>>         documentation [1] to talk about the windup-rulesets repository.
>>
>>         Ian, Is there anything else I need to update to prevent
>>         confusion for others?
>>
>>         [1]
>>         https://github.com/windup/windup/wiki/Dev-Get-the-Windup-Source-Code
>>
>>         On 04/25/2015 12:01 PM, Lincoln Baxter, III wrote:
>>
>>             Haha, yes, we moved things around a bit ;) Glad you got
>>             if found and working, you're very welcome. Jess and
>>             George really did the hard work.
>>
>>             On Sat, Apr 25, 2015 at 10:12 AM, Ian Tewksbury
>>             <itewk at redhat.com <mailto:itewk at redhat.com>> wrote:
>>
>>                 Nevermind.
>>
>>                 I found the rulesets project too.
>>
>>                 Compiling and all tests passing.
>>
>>                 Woot. Thank you guys so much for getting this working.
>>
>>                 Now for the fun bits.
>>
>>                 ~Ian
>>
>>                 ------------------------------------------------------------------------
>>                 *From: *"Ian Tewksbury" <itewk at redhat.com
>>                 <mailto:itewk at redhat.com>>
>>                 *To: *"Windup-dev List" <windup-dev at lists.jboss.org
>>                 <mailto:windup-dev at lists.jboss.org>>
>>                 *Sent: *Saturday, April 25, 2015 9:47:23 AM
>>                 *Subject: *Re: [windup-dev] Could not find artifact
>>                 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT
>>                 in jboss-public-repository-group
>>
>>
>>                 I found the windup-distribution project on git. But
>>                 trying to build that I get:
>>
>>                 [ERROR] Failed to execute goal on project
>>                 windup-distribution: Could not resolve dependencies
>>                 for project
>>                 org.jboss.windup:windup-distribution:pom:2.3.0-SNAPSHOT:
>>                 Could not find artifact
>>                 org.jboss.windup.rules:windup-rulesets:jar:2.3.0-SNAPSHOT
>>                 in jboss-public-repository-group
>>                 (http://repository.jboss.org/nexus/content/groups/public/)
>>
>>
>>                 I know I am missing something dumb here.
>>
>>                 ~Ian
>>
>>                 ------------------------------------------------------------------------
>>                 *From: *"Ian Tewksbury" <itewk at redhat.com
>>                 <mailto:itewk at redhat.com>>
>>                 *To: *"Windup-dev List" <windup-dev at lists.jboss.org
>>                 <mailto:windup-dev at lists.jboss.org>>
>>                 *Sent: *Saturday, April 25, 2015 9:37:24 AM
>>                 *Subject: *[windup-dev] Could not find artifact
>>                 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT
>>                 in jboss-public-repository-group
>>
>>                 Trying to get the latest master branch of the plugin
>>                 compiling.
>>
>>
>>                 What am I missing?
>>
>>
>>                 [ERROR] Failed to execute goal on project
>>                 org.jboss.tools.windup.runtime: Could not resolve
>>                 dependencies for project
>>                 org.jboss.tools.windup.plugins:org.jboss.tools.windup.runtime:eclipse-plugin:3.1.0-SNAPSHOT:
>>                 Could not find artifact
>>                 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT
>>                 in jboss-public-repository-group
>>                 (http://repository.jboss.org/nexus/content/groups/public/)
>>                 -> [Help 1]
>>
>>
>>
>>                 Blue Skies,
>>
>>                 ~Ian
>>
>>
>>
>>                 _______________________________________________
>>                 windup-dev mailing list
>>                 windup-dev at lists.jboss.org
>>                 <mailto:windup-dev at lists.jboss.org>
>>                 https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>                 _______________________________________________
>>                 windup-dev mailing list
>>                 windup-dev at lists.jboss.org
>>                 <mailto:windup-dev at lists.jboss.org>
>>                 https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>                 _______________________________________________
>>                 windup-dev mailing list
>>                 windup-dev at lists.jboss.org
>>                 <mailto:windup-dev at lists.jboss.org>
>>                 https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>>
>>             -- 
>>             Lincoln Baxter, III
>>             http://ocpsoft.org
>>             "Simpler is better."
>>
>>
>>             _______________________________________________
>>             windup-dev mailing list
>>             windup-dev at lists.jboss.org
>>             https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>>         _______________________________________________
>>         windup-dev mailing list
>>         windup-dev at lists.jboss.org
>>         https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>>
>>     _______________________________________________
>>     windup-dev mailing list
>>     windup-dev at lists.jboss.org
>>     https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>> -- 
>> 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
>
>
>
> _______________________________________________
> 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/20150427/ca5297bb/attachment-0001.html 

From lincolnbaxter at gmail.com  Tue Apr 28 11:06:14 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 28 Apr 2015 11:06:14 -0400
Subject: [windup-dev] Sugested Fix Hints
In-Reply-To: <941980513.4971941.1430137452508.JavaMail.zimbra@redhat.com>
References: <34285553.4971460.1430137378250.JavaMail.zimbra@redhat.com>
	<941980513.4971941.1430137452508.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4E1yh3bx=L0T82D+TCFucCaojOmHMyy7gEeADO7RNcDpQ@mail.gmail.com>

Hey Ian,

Hints are just HTML/Markdown, and don't provide anything that would really
be useful for a quick fix at this point, but... they should have the
ability to include Links/HREFs as well. If you look at the
windup-tooling-api, you should see Hint, Classification, and Link.

How do you envision the quick fix stuff working? What type of information
would we need to give you?

Does that answer your question?

Thanks!
~Lincoln

On Mon, Apr 27, 2015 at 8:24 AM, Ian Tewksbury <itewk at redhat.com> wrote:

> All,
>
> Do any of the hints have a "suggested fix" built into them. I was looking
> at the hint API but didnt see such a thing, but I know it had been talked
> about in the past.
>
> If such a thing exists I want to detect hints with "suggested code fixes"
> and auto generate Eclipse quick fixes for those hints so people can easily
> apply the quick fixes to knock out the easy stuff in an automated fashion.
>
> ~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/20150428/bfc095bd/attachment.html 

From lincolnbaxter at gmail.com  Tue Apr 28 11:11:55 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 28 Apr 2015 11:11:55 -0400
Subject: [windup-dev] Ruleset Location API
In-Reply-To: <97752043.4971307.1430137347398.JavaMail.zimbra@redhat.com>
References: <97752043.4971307.1430137347398.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4Gc-TBe4zodPjDae37uFnOf3GP1yQLctuUV8yigxS-SaA@mail.gmail.com>

Hey Ian,

That's a great idea. Right now I do not believe so, but we can certainly
add that.

https://issues.jboss.org/browse/WINDUP-570

~Lincoln

On Mon, Apr 27, 2015 at 8:22 AM, Ian Tewksbury <itewk at redhat.com> wrote:

> 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
>
> _______________________________________________
> 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/20150428/96384000/attachment.html 

From lincolnbaxter at gmail.com  Tue Apr 28 11:18:41 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 28 Apr 2015 11:18:41 -0400
Subject: [windup-dev] Eclipse Plugin - allow user to specify ignored
	files
In-Reply-To: <1151659169.4975202.1430137964430.JavaMail.zimbra@redhat.com>
References: <1151659169.4975202.1430137964430.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4EG9BSFrFKnzfdPrH2VYZDHzXx_wFPm9NQ-v4u60+A=_w@mail.gmail.com>

Hey Ian,

I think that makes a LOT of sense. Allowing users to ignore custom files
right in the IDE would greatly simplify how they configure the tool. I see
a lot of potential for using this approach to configure other parts of the
system.

~Lincoln

On Mon, Apr 27, 2015 at 8:32 AM, Ian Tewksbury <itewk at redhat.com> wrote:

> All,
>
> Currently the eclipse plugin is hard coded to only ignore .class$ files.
> Would it make sense to add a preference dialog where users could specify
> other ignore rules?
>
> ~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/20150428/b81fc09a/attachment.html 

From lincolnbaxter at gmail.com  Tue Apr 28 11:30:17 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 28 Apr 2015 11:30:17 -0400
Subject: [windup-dev] Could not find artifact
 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
 jboss-public-repository-group
In-Reply-To: <553E5A5C.2010000@redhat.com>
References: <297971927.4700897.1429969044617.JavaMail.zimbra@redhat.com>
	<328794499.4701305.1429969643677.JavaMail.zimbra@redhat.com>
	<484943168.4701566.1429971167539.JavaMail.zimbra@redhat.com>
	<CAEp_U4FAuFbCftWiE2uFLSitf+3aSFAvbZXK-PW9AYQiCWiykw@mail.gmail.com>
	<553E1622.5080406@redhat.com>
	<1185704303.4971101.1430137294031.JavaMail.zimbra@redhat.com>
	<553E2E7F.4080303@redhat.com> <553E4886.4000901@redhat.com>
	<334217888.5051117.1430145901444.JavaMail.zimbra@redhat.com>
	<553E55AC.1070100@redhat.com> <553E5A5C.2010000@redhat.com>
Message-ID: <CAEp_U4GPem9DF_h3M=g=aZC_6ZhTx2sf=nSh1iRdX1CvArvdLw@mail.gmail.com>

Agreed, windup-distribution and windup-rulesets should be part of the build
instructions. Volunteer for making that happen?

On Mon, Apr 27, 2015 at 11:48 AM, Jess Sightler <jsightle at redhat.com> wrote:

>  Hi Sande,
>
> We are referring to this:
> https://github.com/windup/windup-distribution/
>
> This project is part of the windup source code and is consumed by the
> windup-eclipse-plugin as a build dependency as well.
>
> Without this, it isn't possible to build a running copy of windup. So this
> should be part of the build instructions, right?
>
> Thanks,
> Jess
>
>
>
> On 04/27/2015 11:28 AM, Sande Gilda wrote:
>
> These are 2 different things.
>
> How to get the source code and build it is documented here:
> https://github.com/windup/windup/wiki/Core-Development-Guide#prepare-your-development-environment
>
> A README file for the distribution is a different thing. It doesn't look
> like we do that for other products. I just unzipped the JBoss EAP 6.4
> distribution and verified that. In most cases, won't they be finding the
> distribution location from the Wiki or from the documentation? One thing to
> keeps in mind is that the target audience for the Windup distribution can
> vary. Would inclusion of a README that contains links to existing
> documentation be sufficient? Or do you think something more?
>
> Sande
>
>
> On 04/27/2015 10:45 AM, Ian Tewksbury wrote:
>
>  Sande,
>
>  Jess is correct. Currently the windup-distribution project has no
> README. Then we need some additions to the eclipse plugin README to include
> how to build, need to download the three windup projects, make sure you
> have the latest forge. So forth and so on.
>
> ~Ian
>
>
>  ------------------------------
> *From: *"Jess Sightler" <jsightle at redhat.com> <jsightle at redhat.com>
> *To: *windup-dev at lists.jboss.org
> *Sent: *Monday, April 27, 2015 10:32:38 AM
> *Subject: *Re: [windup-dev] Could not find artifact
> org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
> jboss-public-repository-group
>
>  I think that he means documentation of how to get the source code and
> build it. windup-distribution is a required module now and is separate
> from the other two.
>
> On 04/27/2015 08:41 AM, Sande Gilda wrote:
>
> Hi Ian,
>
> Are you referring to the download distribution described here:
> https://github.com/windup/windup/wiki/Install-Windup ?
>
> What kind of information are you looking for? A description of the
> directory structure? Something else?
>
> Thanks,
> Sande
>
> On 04/27/2015 08:21 AM, Ian Tewksbury wrote:
>
>  Sande,
>
>  Documentation of the windup-distribution project would be useful.
>
>  ~Ian
>
>  ------------------------------
> *From: *"Sande Gilda" <sgilda at redhat.com> <sgilda at redhat.com>
> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
> <windup-dev at lists.jboss.org>, "George Gastaldi" <ggastald at redhat.com>
> <ggastald at redhat.com>
> *Sent: *Monday, April 27, 2015 6:57:38 AM
> *Subject: *Re: [windup-dev] Could not find artifact
> org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
> jboss-public-repository-group
>
>  This reminds me! I believe I need to update the Wiki documentation [1] to
> talk about the windup-rulesets repository.
>
> Ian, Is there anything else I need to update to prevent confusion for
> others?
>
> [1] https://github.com/windup/windup/wiki/Dev-Get-the-Windup-Source-Code
>
> On 04/25/2015 12:01 PM, Lincoln Baxter, III wrote:
>
> Haha, yes, we moved things around a bit ;) Glad you got if found and
> working, you're very welcome. Jess and George really did the hard work.
>
> On Sat, Apr 25, 2015 at 10:12 AM, Ian Tewksbury <itewk at redhat.com> wrote:
>
>>  Nevermind.
>>
>>  I found the rulesets project too.
>>
>>  Compiling and all tests passing.
>>
>>  Woot. Thank you guys so much for getting this working.
>>
>>  Now for the fun bits.
>>
>> ~Ian
>>
>>  ------------------------------
>> *From: *"Ian Tewksbury" <itewk at redhat.com>
>> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
>> *Sent: *Saturday, April 25, 2015 9:47:23 AM
>> *Subject: *Re: [windup-dev] Could not find artifact
>> org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
>> jboss-public-repository-group
>>
>>
>>  I found the windup-distribution project on git. But trying to build
>> that I get:
>>
>>  [ERROR] Failed to execute goal on project windup-distribution: Could
>> not resolve dependencies for project
>> org.jboss.windup:windup-distribution:pom:2.3.0-SNAPSHOT: Could not find
>> artifact org.jboss.windup.rules:windup-rulesets:jar:2.3.0-SNAPSHOT in
>> jboss-public-repository-group (
>> http://repository.jboss.org/nexus/content/groups/public/)
>>
>>  I know I am missing something dumb here.
>>
>> ~Ian
>>
>>  ------------------------------
>> *From: *"Ian Tewksbury" <itewk at redhat.com>
>> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
>> *Sent: *Saturday, April 25, 2015 9:37:24 AM
>> *Subject: *[windup-dev] Could not find artifact
>> org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
>> jboss-public-repository-group
>>
>>  Trying to get the latest master branch of the plugin compiling.
>>
>>
>>  What am I missing?
>>
>>
>>  [ERROR] Failed to execute goal on project
>> org.jboss.tools.windup.runtime: Could not resolve dependencies for project
>> org.jboss.tools.windup.plugins:org.jboss.tools.windup.runtime:eclipse-plugin:3.1.0-SNAPSHOT:
>> Could not find artifact
>> org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
>> jboss-public-repository-group (
>> http://repository.jboss.org/nexus/content/groups/public/) -> [Help 1]
>>
>>
>>
>>  Blue Skies,
>>
>> ~Ian
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>
>
>
>  --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://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 listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
> --
> 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
>



-- 
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/20150428/0bfb97c9/attachment-0001.html 

From lincolnbaxter at gmail.com  Tue Apr 28 11:32:53 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 28 Apr 2015 11:32:53 -0400
Subject: [windup-dev] Eclipse Plugin - When to regenerate validation
	markers
In-Reply-To: <1626933510.4974726.1430137891179.JavaMail.zimbra@redhat.com>
References: <1584136349.4972206.1430137521908.JavaMail.zimbra@redhat.com>
	<1626933510.4974726.1430137891179.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4GCEQGu_39cwcqu8jbO3pfpr9D4s5enRro=WSGN2omdzA@mail.gmail.com>

My first and simplest thought for this is just to allow people to clear
markers and not regenerate the file. Markers may subsequently reappear if
Windup is run on the app again. I think that regenerating and re-running
all of windup on each file-save would be too performance prohibitive.

This is really a feature that we need to implement as part of a more
incremental process of analysis, e.g. to support something like a web-app
where you can "explore" the app file-by-file after the initial core
analysis has been completed the first time. The ETA for this is not soon,
unfortunately.

Thoughts?

~Lincoln

On Mon, Apr 27, 2015 at 8:31 AM, Ian Tewksbury <itewk at redhat.com> wrote:

> All,
>
> With old Windup 1.0 there was a way to regenerate the hints for a single
> file. Do to the redesign of Windup 2.0 I understand this is currently not
> possible, and doing so is an undertaking no one has attempted yet, so in
> the mean time I have a quandary of what to do.
>
> Typically in eclipse when you edit a file you re-generate the validation
> markers for that file, so if you fix a validation marker it doesn't still
> show as busted. Currently without being able to regenerate the hints for a
> specific file I am unsure what the best option is.
>
> Options I can think of are:
>
>
>    1. do nothing, and just allow stale validation markers to sit on the
>    file even if they have been addressed
>    2. regenerate the entire windup graph every time a file is edited
>       1. could do this just on save rather then on every character type
>       2. how expensive is it to generate the graph? Are there any
>       statistics?
>       3. Once a file is changed mark all the windup markers as stale with
>    a message that the graph needs to be regenerated to update them
>    4. Simply remove all windup markers from the edited file until such
>    time as the graph is regenerated
>
>
> It used to be that my validator would auto run windup on a project as soon
> as the validation kicked off. Currently the validator has been changed such
> that if windup has not been run it simply does not report any windup hints.
>
> Any thoughts on adding back the bit to at least run windup the first time
> when validation first kicks off? Right now the user doesn't have any way of
> knowing that the only reason they are not seeing windup validation markers
> is they have not manually generated a report. In the old plugin design the
> generation of an HTML report and the validaton markers were two different
> actions. It is rather an Eclipse anti practice to have to invoke a
> secondary menu action, "Windup Generate Report" in this case, to then allow
> a validator to run correctly.
>
> Blue Skies,
> ~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/20150428/b5f868e0/attachment.html 

From sgilda at redhat.com  Tue Apr 28 11:38:56 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 28 Apr 2015 11:38:56 -0400
Subject: [windup-dev] Could not find artifact
 org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
 jboss-public-repository-group
In-Reply-To: <CAEp_U4GPem9DF_h3M=g=aZC_6ZhTx2sf=nSh1iRdX1CvArvdLw@mail.gmail.com>
References: <297971927.4700897.1429969044617.JavaMail.zimbra@redhat.com>	<328794499.4701305.1429969643677.JavaMail.zimbra@redhat.com>	<484943168.4701566.1429971167539.JavaMail.zimbra@redhat.com>	<CAEp_U4FAuFbCftWiE2uFLSitf+3aSFAvbZXK-PW9AYQiCWiykw@mail.gmail.com>	<553E1622.5080406@redhat.com>	<1185704303.4971101.1430137294031.JavaMail.zimbra@redhat.com>	<553E2E7F.4080303@redhat.com>
	<553E4886.4000901@redhat.com>	<334217888.5051117.1430145901444.JavaMail.zimbra@redhat.com>	<553E55AC.1070100@redhat.com>
	<553E5A5C.2010000@redhat.com>
	<CAEp_U4GPem9DF_h3M=g=aZC_6ZhTx2sf=nSh1iRdX1CvArvdLw@mail.gmail.com>
Message-ID: <553FA990.5050905@redhat.com>

Lincoln, I'll look into it and see if I can figure it out.

On 04/28/2015 11:30 AM, Lincoln Baxter, III wrote:
> Agreed, windup-distribution and windup-rulesets should be part of the 
> build instructions. Volunteer for making that happen?
>
> On Mon, Apr 27, 2015 at 11:48 AM, Jess Sightler <jsightle at redhat.com 
> <mailto:jsightle at redhat.com>> wrote:
>
>     Hi Sande,
>
>     We are referring to this:
>     https://github.com/windup/windup-distribution/
>
>     This project is part of the windup source code and is consumed by
>     the windup-eclipse-plugin as a build dependency as well.
>
>     Without this, it isn't possible to build a running copy of windup.
>     So this should be part of the build instructions, right?
>
>     Thanks,
>     Jess
>
>
>
>     On 04/27/2015 11:28 AM, Sande Gilda wrote:
>>     These are 2 different things.
>>
>>     How to get the source code and build it is documented here:
>>     https://github.com/windup/windup/wiki/Core-Development-Guide#prepare-your-development-environment
>>
>>     A README file for the distribution is a different thing. It
>>     doesn't look like we do that for other products. I just unzipped
>>     the JBoss EAP 6.4 distribution and verified that. In most cases,
>>     won't they be finding the distribution location from the Wiki or
>>     from the documentation? One thing to keeps in mind is that the
>>     target audience for the Windup distribution can vary. Would
>>     inclusion of a README that contains links to existing
>>     documentation be sufficient? Or do you think something more?
>>
>>     Sande
>>
>>
>>     On 04/27/2015 10:45 AM, Ian Tewksbury wrote:
>>>     Sande,
>>>
>>>     Jess is correct. Currently the windup-distribution project has
>>>     no README. Then we need some additions to the eclipse plugin
>>>     README to include how to build, need to download the three
>>>     windup projects, make sure you have the latest forge. So forth
>>>     and so on.
>>>
>>>     ~Ian
>>>
>>>
>>>     ------------------------------------------------------------------------
>>>     *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, April 27, 2015 10:32:38 AM
>>>     *Subject: *Re: [windup-dev] Could not find artifact
>>>     org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT
>>>     in jboss-public-repository-group
>>>
>>>     I think that he means documentation of how to get the source
>>>     code and build it. windup-distribution is a required module now
>>>     and is separate from the other two.
>>>
>>>     On 04/27/2015 08:41 AM, Sande Gilda wrote:
>>>
>>>         Hi Ian,
>>>
>>>         Are you referring to the download distribution described
>>>         here: https://github.com/windup/windup/wiki/Install-Windup ?
>>>
>>>         What kind of information are you looking for? A description
>>>         of the directory structure? Something else?
>>>
>>>         Thanks,
>>>         Sande
>>>
>>>         On 04/27/2015 08:21 AM, Ian Tewksbury wrote:
>>>
>>>             Sande,
>>>
>>>             Documentation of the windup-distribution project would
>>>             be useful.
>>>
>>>             ~Ian
>>>
>>>             ------------------------------------------------------------------------
>>>             *From: *"Sande Gilda" <sgilda at redhat.com>
>>>             <mailto:sgilda at redhat.com>
>>>             *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
>>>             <mailto:windup-dev at lists.jboss.org>, "George Gastaldi"
>>>             <ggastald at redhat.com> <mailto:ggastald at redhat.com>
>>>             *Sent: *Monday, April 27, 2015 6:57:38 AM
>>>             *Subject: *Re: [windup-dev] Could not find artifact
>>>             org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT
>>>             in jboss-public-repository-group
>>>
>>>             This reminds me! I believe I need to update the Wiki
>>>             documentation [1] to talk about the windup-rulesets
>>>             repository.
>>>
>>>             Ian, Is there anything else I need to update to prevent
>>>             confusion for others?
>>>
>>>             [1]
>>>             https://github.com/windup/windup/wiki/Dev-Get-the-Windup-Source-Code
>>>
>>>             On 04/25/2015 12:01 PM, Lincoln Baxter, III wrote:
>>>
>>>                 Haha, yes, we moved things around a bit ;) Glad you
>>>                 got if found and working, you're very welcome. Jess
>>>                 and George really did the hard work.
>>>
>>>                 On Sat, Apr 25, 2015 at 10:12 AM, Ian Tewksbury
>>>                 <itewk at redhat.com <mailto:itewk at redhat.com>> wrote:
>>>
>>>                     Nevermind.
>>>
>>>                     I found the rulesets project too.
>>>
>>>                     Compiling and all tests passing.
>>>
>>>                     Woot. Thank you guys so much for getting this
>>>                     working.
>>>
>>>                     Now for the fun bits.
>>>
>>>                     ~Ian
>>>
>>>                     ------------------------------------------------------------------------
>>>                     *From: *"Ian Tewksbury" <itewk at redhat.com
>>>                     <mailto:itewk at redhat.com>>
>>>                     *To: *"Windup-dev List"
>>>                     <windup-dev at lists.jboss.org
>>>                     <mailto:windup-dev at lists.jboss.org>>
>>>                     *Sent: *Saturday, April 25, 2015 9:47:23 AM
>>>                     *Subject: *Re: [windup-dev] Could not find
>>>                     artifact
>>>                     org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT
>>>                     in jboss-public-repository-group
>>>
>>>
>>>                     I found the windup-distribution project on git.
>>>                     But trying to build that I get:
>>>
>>>                     [ERROR] Failed to execute goal on project
>>>                     windup-distribution: Could not resolve
>>>                     dependencies for project
>>>                     org.jboss.windup:windup-distribution:pom:2.3.0-SNAPSHOT:
>>>                     Could not find artifact
>>>                     org.jboss.windup.rules:windup-rulesets:jar:2.3.0-SNAPSHOT
>>>                     in jboss-public-repository-group
>>>                     (http://repository.jboss.org/nexus/content/groups/public/)
>>>
>>>
>>>                     I know I am missing something dumb here.
>>>
>>>                     ~Ian
>>>
>>>                     ------------------------------------------------------------------------
>>>                     *From: *"Ian Tewksbury" <itewk at redhat.com
>>>                     <mailto:itewk at redhat.com>>
>>>                     *To: *"Windup-dev List"
>>>                     <windup-dev at lists.jboss.org
>>>                     <mailto:windup-dev at lists.jboss.org>>
>>>                     *Sent: *Saturday, April 25, 2015 9:37:24 AM
>>>                     *Subject: *[windup-dev] Could not find artifact
>>>                     org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT
>>>                     in jboss-public-repository-group
>>>
>>>                     Trying to get the latest master branch of the
>>>                     plugin compiling.
>>>
>>>
>>>                     What am I missing?
>>>
>>>
>>>                     [ERROR] Failed to execute goal on project
>>>                     org.jboss.tools.windup.runtime: Could not
>>>                     resolve dependencies for project
>>>                     org.jboss.tools.windup.plugins:org.jboss.tools.windup.runtime:eclipse-plugin:3.1.0-SNAPSHOT:
>>>                     Could not find artifact
>>>                     org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT
>>>                     in jboss-public-repository-group
>>>                     (http://repository.jboss.org/nexus/content/groups/public/)
>>>                     -> [Help 1]
>>>
>>>
>>>
>>>                     Blue Skies,
>>>
>>>                     ~Ian
>>>
>>>
>>>
>>>                     _______________________________________________
>>>                     windup-dev mailing list
>>>                     windup-dev at lists.jboss.org
>>>                     <mailto:windup-dev at lists.jboss.org>
>>>                     https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
>>>
>>>                     _______________________________________________
>>>                     windup-dev mailing list
>>>                     windup-dev at lists.jboss.org
>>>                     <mailto:windup-dev at lists.jboss.org>
>>>                     https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
>>>
>>>                     _______________________________________________
>>>                     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  <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
>>
>>
>>
>>     _______________________________________________
>>     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
>
>
>
>
> -- 
> 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/20150428/088d0513/attachment-0001.html 

From itewk at redhat.com  Tue Apr 28 12:17:31 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Tue, 28 Apr 2015 12:17:31 -0400 (EDT)
Subject: [windup-dev] Sugested Fix Hints
In-Reply-To: <CAEp_U4E1yh3bx=L0T82D+TCFucCaojOmHMyy7gEeADO7RNcDpQ@mail.gmail.com>
References: <34285553.4971460.1430137378250.JavaMail.zimbra@redhat.com>
	<941980513.4971941.1430137452508.JavaMail.zimbra@redhat.com>
	<CAEp_U4E1yh3bx=L0T82D+TCFucCaojOmHMyy7gEeADO7RNcDpQ@mail.gmail.com>
Message-ID: <1602348342.5867308.1430237851491.JavaMail.zimbra@redhat.com>

Liconln, 

I plan on including the links in the Warning/Error messages. 

As far as quick fix, for the dead simple low hanging fruit it would need to be replace the detected code with this code. Maybe there isnt such any cases. 

The next more complicated case is replace detected code with this code template, then we can use the template API in eclipse to fill out the template based on other information. 

Then the last level up is to add an action to apply all the windup quick fixes at once. 

So there would really just need to be one new API, "getSuggestedReplacment" (or something like that). WHich would then return a block of code to replace the detected code with. Later we can figure out how we could do Templating through that. 

Do you think there are any cases where a template would not be needed? 

~Ian 


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

From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com> 
To: "Windup-dev List" <windup-dev at lists.jboss.org> 
Sent: Tuesday, April 28, 2015 11:06:14 AM 
Subject: Re: [windup-dev] Sugested Fix Hints 

Hey Ian, 

Hints are just HTML/Markdown, and don't provide anything that would really be useful for a quick fix at this point, but... they should have the ability to include Links/HREFs as well. If you look at the windup-tooling-api, you should see Hint, Classification, and Link. 

How do you envision the quick fix stuff working? What type of information would we need to give you? 

Does that answer your question? 

Thanks! 
~Lincoln 

On Mon, Apr 27, 2015 at 8:24 AM, Ian Tewksbury < itewk at redhat.com > wrote: 



All, 

Do any of the hints have a "suggested fix" built into them. I was looking at the hint API but didnt see such a thing, but I know it had been talked about in the past. 

If such a thing exists I want to detect hints with "suggested code fixes" and auto generate Eclipse quick fixes for those hints so people can easily apply the quick fixes to knock out the easy stuff in an automated fashion. 

~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." 

_______________________________________________ 
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/20150428/742eeca2/attachment.html 

From itewk at redhat.com  Tue Apr 28 12:22:56 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Tue, 28 Apr 2015 12:22:56 -0400 (EDT)
Subject: [windup-dev] Ruleset Location API
In-Reply-To: <CAEp_U4Gc-TBe4zodPjDae37uFnOf3GP1yQLctuUV8yigxS-SaA@mail.gmail.com>
References: <97752043.4971307.1430137347398.JavaMail.zimbra@redhat.com>
	<CAEp_U4Gc-TBe4zodPjDae37uFnOf3GP1yQLctuUV8yigxS-SaA@mail.gmail.com>
Message-ID: <639956697.5868698.1430238176005.JavaMail.zimbra@redhat.com>

Lincoln, 

Created https://issues.jboss.org/browse/WINDUP-571 to follow up after you all knock out 570. 

Thanks, 
~Ian 


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

From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com> 
To: "Windup-dev List" <windup-dev at lists.jboss.org> 
Sent: Tuesday, April 28, 2015 11:11:55 AM 
Subject: Re: [windup-dev] Ruleset Location API 

Hey Ian, 

That's a great idea. Right now I do not believe so, but we can certainly add that. 

https://issues.jboss.org/browse/WINDUP-570 

~Lincoln 

On Mon, Apr 27, 2015 at 8:22 AM, Ian Tewksbury < itewk at redhat.com > wrote: 



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 

_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 






-- 
Lincoln Baxter, III 
http://ocpsoft.org 
"Simpler is better." 

_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150428/d7602b51/attachment.html 

From itewk at redhat.com  Tue Apr 28 12:25:01 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Tue, 28 Apr 2015 12:25:01 -0400 (EDT)
Subject: [windup-dev] Eclipse Plugin - allow user to specify
	ignored	files
In-Reply-To: <CAEp_U4EG9BSFrFKnzfdPrH2VYZDHzXx_wFPm9NQ-v4u60+A=_w@mail.gmail.com>
References: <1151659169.4975202.1430137964430.JavaMail.zimbra@redhat.com>
	<CAEp_U4EG9BSFrFKnzfdPrH2VYZDHzXx_wFPm9NQ-v4u60+A=_w@mail.gmail.com>
Message-ID: <1099145881.5869480.1430238301754.JavaMail.zimbra@redhat.com>

Lincoln, 

Cool. Created https://issues.jboss.org/browse/WINDUP-572 . 

Once I get an initial preference framework set up, likely with this item, adding any other preferences will become far more trivial. 

~Ian 


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

From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com> 
To: "Windup-dev List" <windup-dev at lists.jboss.org> 
Sent: Tuesday, April 28, 2015 11:18:41 AM 
Subject: Re: [windup-dev] Eclipse Plugin - allow user to specify ignored files 

Hey Ian, 

I think that makes a LOT of sense. Allowing users to ignore custom files right in the IDE would greatly simplify how they configure the tool. I see a lot of potential for using this approach to configure other parts of the system. 

~Lincoln 

On Mon, Apr 27, 2015 at 8:32 AM, Ian Tewksbury < itewk at redhat.com > wrote: 



All, 

Currently the eclipse plugin is hard coded to only ignore .class$ files. Would it make sense to add a preference dialog where users could specify other ignore rules? 

~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." 

_______________________________________________ 
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/20150428/7cad2baa/attachment.html 

From itewk at redhat.com  Tue Apr 28 12:28:39 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Tue, 28 Apr 2015 12:28:39 -0400 (EDT)
Subject: [windup-dev] Eclipse Plugin - When to regenerate
	validation	markers
In-Reply-To: <CAEp_U4GCEQGu_39cwcqu8jbO3pfpr9D4s5enRro=WSGN2omdzA@mail.gmail.com>
References: <1584136349.4972206.1430137521908.JavaMail.zimbra@redhat.com>
	<1626933510.4974726.1430137891179.JavaMail.zimbra@redhat.com>
	<CAEp_U4GCEQGu_39cwcqu8jbO3pfpr9D4s5enRro=WSGN2omdzA@mail.gmail.com>
Message-ID: <260022568.5870345.1430238519528.JavaMail.zimbra@redhat.com>

Liconln, 

I have to think on it. Created https://issues.jboss.org/browse/WINDUP-573 for those thoughts. 

~Ian 


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

From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com> 
To: "Windup-dev List" <windup-dev at lists.jboss.org> 
Sent: Tuesday, April 28, 2015 11:32:53 AM 
Subject: Re: [windup-dev] Eclipse Plugin - When to regenerate validation markers 

My first and simplest thought for this is just to allow people to clear markers and not regenerate the file. Markers may subsequently reappear if Windup is run on the app again. I think that regenerating and re-running all of windup on each file-save would be too performance prohibitive. 

This is really a feature that we need to implement as part of a more incremental process of analysis, e.g. to support something like a web-app where you can "explore" the app file-by-file after the initial core analysis has been completed the first time. The ETA for this is not soon, unfortunately. 

Thoughts? 

~Lincoln 

On Mon, Apr 27, 2015 at 8:31 AM, Ian Tewksbury < itewk at redhat.com > wrote: 



All, 

With old Windup 1.0 there was a way to regenerate the hints for a single file. Do to the redesign of Windup 2.0 I understand this is currently not possible, and doing so is an undertaking no one has attempted yet, so in the mean time I have a quandary of what to do. 

Typically in eclipse when you edit a file you re-generate the validation markers for that file, so if you fix a validation marker it doesn't still show as busted. Currently without being able to regenerate the hints for a specific file I am unsure what the best option is. 

Options I can think of are: 



    1. do nothing, and just allow stale validation markers to sit on the file even if they have been addressed 
    2. regenerate the entire windup graph every time a file is edited 


        1. could do this just on save rather then on every character type 
        2. how expensive is it to generate the graph? Are there any statistics? 
    3. 
Once a file is changed mark all the windup markers as stale with a message that the graph needs to be regenerated to update them 
    4. Simply remove all windup markers from the edited file until such time as the graph is regenerated 

It used to be that my validator would auto run windup on a project as soon as the validation kicked off. Currently the validator has been changed such that if windup has not been run it simply does not report any windup hints. 

Any thoughts on adding back the bit to at least run windup the first time when validation first kicks off? Right now the user doesn't have any way of knowing that the only reason they are not seeing windup validation markers is they have not manually generated a report. In the old plugin design the generation of an HTML report and the validaton markers were two different actions. It is rather an Eclipse anti practice to have to invoke a secondary menu action, "Windup Generate Report" in this case, to then allow a validator to run correctly. 

Blue Skies, 
~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." 

_______________________________________________ 
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/20150428/f38f83bd/attachment-0001.html 

From lincolnbaxter at gmail.com  Tue Apr 28 13:52:27 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 28 Apr 2015 13:52:27 -0400
Subject: [windup-dev] Sugested Fix Hints
In-Reply-To: <1602348342.5867308.1430237851491.JavaMail.zimbra@redhat.com>
References: <34285553.4971460.1430137378250.JavaMail.zimbra@redhat.com>
	<941980513.4971941.1430137452508.JavaMail.zimbra@redhat.com>
	<CAEp_U4E1yh3bx=L0T82D+TCFucCaojOmHMyy7gEeADO7RNcDpQ@mail.gmail.com>
	<1602348342.5867308.1430237851491.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4HM-kCuu9hrt0LAiP7NKe1_y8pVWyVrNvU_ymd7R_hcPg@mail.gmail.com>

Mostly, I'm having trouble thinking of any cases where we actually know the
code that we could replace. I think this is something we could begin to do,
but it is largely a rule quality issue. We just don't have the expert
knowledge to supply this kind of info yet. It's a problem we're thinking
about. That said, having the functionality in place for it might be a good
idea.

Can templates be provided programmatically?

On Tue, Apr 28, 2015 at 12:17 PM, Ian Tewksbury <itewk at redhat.com> wrote:

> Liconln,
>
> I plan on including the links in the Warning/Error messages.
>
> As far as quick fix, for the dead simple low hanging fruit it would need
> to be replace the detected code with this code. Maybe there isnt such any
> cases.
>
> The next more complicated case is replace detected code with this code
> template, then we can use the template API in eclipse to fill out the
> template based on other information.
>
> Then the last level up is to add an action to apply all the windup quick
> fixes at once.
>
> So there would really just need to be one new API,
> "getSuggestedReplacment" (or something like that). WHich would then return
> a block of code to replace the detected code with. Later we can figure out
> how we could do Templating through that.
>
> Do you think there are any cases where a template would not be needed?
>
> ~Ian
>
>
> ------------------------------
> *From: *"Lincoln Baxter, III" <lincolnbaxter at gmail.com>
> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
> *Sent: *Tuesday, April 28, 2015 11:06:14 AM
> *Subject: *Re: [windup-dev] Sugested Fix Hints
>
>
> Hey Ian,
>
> Hints are just HTML/Markdown, and don't provide anything that would really
> be useful for a quick fix at this point, but... they should have the
> ability to include Links/HREFs as well. If you look at the
> windup-tooling-api, you should see Hint, Classification, and Link.
>
> How do you envision the quick fix stuff working? What type of information
> would we need to give you?
>
> Does that answer your question?
>
> Thanks!
> ~Lincoln
>
> On Mon, Apr 27, 2015 at 8:24 AM, Ian Tewksbury <itewk at redhat.com> wrote:
>
>> All,
>>
>> Do any of the hints have a "suggested fix" built into them. I was looking
>> at the hint API but didnt see such a thing, but I know it had been talked
>> about in the past.
>>
>> If such a thing exists I want to detect hints with "suggested code fixes"
>> and auto generate Eclipse quick fixes for those hints so people can easily
>> apply the quick fixes to knock out the easy stuff in an automated fashion.
>>
>> ~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."
>
> _______________________________________________
> 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/20150428/1dd29723/attachment.html 

From itewk at redhat.com  Tue Apr 28 15:14:28 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Tue, 28 Apr 2015 15:14:28 -0400 (EDT)
Subject: [windup-dev] Sugested Fix Hints
In-Reply-To: <CAEp_U4HM-kCuu9hrt0LAiP7NKe1_y8pVWyVrNvU_ymd7R_hcPg@mail.gmail.com>
References: <34285553.4971460.1430137378250.JavaMail.zimbra@redhat.com>
	<941980513.4971941.1430137452508.JavaMail.zimbra@redhat.com>
	<CAEp_U4E1yh3bx=L0T82D+TCFucCaojOmHMyy7gEeADO7RNcDpQ@mail.gmail.com>
	<1602348342.5867308.1430237851491.JavaMail.zimbra@redhat.com>
	<CAEp_U4HM-kCuu9hrt0LAiP7NKe1_y8pVWyVrNvU_ymd7R_hcPg@mail.gmail.com>
Message-ID: <1379809344.5953337.1430248468966.JavaMail.zimbra@redhat.com>

Lincoln, 

1) I agree that we should get the framework in case and try to find at least one rule we can test the basic functionality on, even if its a fake custom rule that replaces <hello></hello> with <world></world> 

2) From the Eclipse point of view I would need an API I could call that would say based on this current input you give me what to replace it with. Then if memory severs correctly what your API could return is a template that then Eclipse UI asks the user to fill out, like here is what we are going to replace the code with, but give me thge name of this variable or method or property that I can't infer from the existing code. Make sense? 

~Ian 


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

From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com> 
To: "Windup-dev List" <windup-dev at lists.jboss.org> 
Sent: Tuesday, April 28, 2015 1:52:27 PM 
Subject: Re: [windup-dev] Sugested Fix Hints 

Mostly, I'm having trouble thinking of any cases where we actually know the code that we could replace. I think this is something we could begin to do, but it is largely a rule quality issue. We just don't have the expert knowledge to supply this kind of info yet. It's a problem we're thinking about. That said, having the functionality in place for it might be a good idea. 

Can templates be provided programmatically? 

On Tue, Apr 28, 2015 at 12:17 PM, Ian Tewksbury < itewk at redhat.com > wrote: 



Liconln, 

I plan on including the links in the Warning/Error messages. 

As far as quick fix, for the dead simple low hanging fruit it would need to be replace the detected code with this code. Maybe there isnt such any cases. 

The next more complicated case is replace detected code with this code template, then we can use the template API in eclipse to fill out the template based on other information. 

Then the last level up is to add an action to apply all the windup quick fixes at once. 

So there would really just need to be one new API, "getSuggestedReplacment" (or something like that). WHich would then return a block of code to replace the detected code with. Later we can figure out how we could do Templating through that. 

Do you think there are any cases where a template would not be needed? 

~Ian 



From: "Lincoln Baxter, III" < lincolnbaxter at gmail.com > 
To: "Windup-dev List" < windup-dev at lists.jboss.org > 
Sent: Tuesday, April 28, 2015 11:06:14 AM 
Subject: Re: [windup-dev] Sugested Fix Hints 


Hey Ian, 

Hints are just HTML/Markdown, and don't provide anything that would really be useful for a quick fix at this point, but... they should have the ability to include Links/HREFs as well. If you look at the windup-tooling-api, you should see Hint, Classification, and Link. 

How do you envision the quick fix stuff working? What type of information would we need to give you? 

Does that answer your question? 

Thanks! 
~Lincoln 

On Mon, Apr 27, 2015 at 8:24 AM, Ian Tewksbury < itewk at redhat.com > wrote: 

<blockquote>

All, 

Do any of the hints have a "suggested fix" built into them. I was looking at the hint API but didnt see such a thing, but I know it had been talked about in the past. 

If such a thing exists I want to detect hints with "suggested code fixes" and auto generate Eclipse quick fixes for those hints so people can easily apply the quick fixes to knock out the easy stuff in an automated fashion. 

~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." 

_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 


_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 

</blockquote>




-- 
Lincoln Baxter, III 
http://ocpsoft.org 
"Simpler is better." 

_______________________________________________ 
windup-dev mailing list 
windup-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/windup-dev 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150428/4b2c796c/attachment.html 

From ozizka at redhat.com  Wed Apr 29 10:32:40 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 29 Apr 2015 16:32:40 +0200
Subject: [windup-dev] Server migration, the big picture
In-Reply-To: <553FC4A1.20400@redhat.com>
References: <1gYj.tLP.5uaCVm3xMmp.1LFgtc@seznam.cz> <553FC4A1.20400@redhat.com>
Message-ID: <5540EB88.9010705@redhat.com>



On 28.4.2015 19:34, Ondrej Zizka wrote:
> Hi all,
>
> as I promised, hereby I am proposing how the migration should look 
> like in the bigger picture.
> I don't say we need all the described parts, but I have a good reason 
> to believe we do.
> Details are described in respective Jira issues. The root Jira issue 
> is MIGR-229.
>
> See the attached whiteboard photo for an overview. Slightly chaotic, 
> as drawn on the fly, and it's not complete anyway. Let's make a better 
> one on F2F.
>
> General:
> ======
>
> 1) Server rules in it's own ruleset. Probably also in separated git 
> repo (as it is now).
>
> 2) The ruleset will reuse certain operations from other rulesets:
>       XPath query to XML documents,
>       .properties parsing,
>       possibly decompilation and analysis of classes - e.g. Tomcat 
> valves, maybe Spring beans, JMX mBeans (esp. for EAP 4), 
> implementations of various interfaces used for EAP 5, etc.
>
> 3) The ruleset will provide certain new
>        conditions, like CLI parsing,
>        and operations, like
>            CLI operations export, in a form of WINDUP-565 
> <https://issues.jboss.org/browse/WINDUP-565>
>                 CLI commands in the report, with comments, highlights 
> of the source it was derived form, links to EAP/WildFly docs, etc.;
>                 CLI commands script;
>                 CLI commands execution against some running server
>            Adding a module to EAP 6 target
>            Installing a fresh target server  (if handy)
>        We can look at Eduardo's WINDUP-550 
> <https://issues.jboss.org/browse/WINDUP-550> to see what we can reuse 
> for these.
>
> 4) The server ruleset will probably have a bit stronger source/target 
> technology split, in terms of respective rules being more organized 
> into individual addons. Not sure about this, depends on the mechanism 
> we use to enable/disable them.
>
> 5) To prevent running the app rules against server files, resp. to 
> support running app and server rules together, we need to update the 
> queries of some app rules to only focus on appropriate files. 
> WINDUP-564 <https://issues.jboss.org/browse/WINDUP-564> and WINDUP-563 
> <https://issues.jboss.org/browse/WINDUP-563> .  This is what I would 
> like to work on next. Now working on WINDUP-566 
> <https://issues.jboss.org/browse/WINDUP-566> .
>
>
>
> Parts:
> ====
> Target technologies:
>   So far, we consider EAP 6 as target server. The long-term goal of 
> EAP 6 is to cover configuration with CLI. Not sure about current 
> state, but it needed some additional actions - direct file 
> manipulation (e.g. modules).
>   Maybe some other target technologies? Depends on what is Windup used 
> for. SOA? Drools? Containers for these might require additional 
> configuration.
>
> Source technologies:
>   The platforms we target long-term. It will be mostly XML and 
> .properties. But could also be more tricky parts, like, digging data 
> from EAP 5's ProfileService, mod_cluster config?, etc.
>
> Platform identification and files comparison: WINDUP-562 
> <https://issues.jboss.org/browse/WINDUP-562> (Done)
>   As discussed during last status meeting, it will be useful to
>       recognize the server version - the user may not know the exact 
> version, which we need to know the default configuration (in case of 
> CLI script migration which just skips the defaults.)
>       recognize which files were changed compared to the distribution 
> of that version - i.e. which configuration files changed (and we don't 
> handle them) and which .jars are changed.
>
> -------------
> Those are rough boundaries. Anything to add or remove? And priorities?
>
>
> Ondra
>
>
>
>

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

From itewk at redhat.com  Wed Apr 29 10:37:47 2015
From: itewk at redhat.com (Ian Tewksbury)
Date: Wed, 29 Apr 2015 10:37:47 -0400 (EDT)
Subject: [windup-dev] JBoss EAP 5 to JBoss EAP 6 Rules
In-Reply-To: <1096869647.6246242.1430318257733.JavaMail.zimbra@redhat.com>
Message-ID: <1328083013.6246367.1430318267247.JavaMail.zimbra@redhat.com>

All, 

Are there any rules already created for a JBoss 5 to JBoss 6 migration? 

My customer is looking for tool to help streamline the migration. 

Blue Skies, 
~Ian 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150429/ed41a859/attachment.html 

From lincolnbaxter at gmail.com  Wed Apr 29 11:01:56 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 29 Apr 2015 11:01:56 -0400
Subject: [windup-dev] Windup Meeting Minutes - 2015-04-29
Message-ID: <CAEp_U4HfmogviYo3var5xyKwLsxSdC36+=ErS3d+TVG+p+oUhA@mail.gmail.com>

Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-04-29-14.01.html

Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-04-29-14.01.txt

Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-04-29-14.01.log.html

Meeting summary
---------------
* Agenda  (ozizka, 14:03:20)

* Status reports  (lincolnthree, 14:03:42)
  * LINK:
    https://docs.google.com/a/redhat.com/spreadsheets/d/1yAZYUulz7MsSU7tOCba9K7wHOfr9VTyWN5p_PQQHRZw/edit#gid=2066204444
    (ozizka, 14:07:57)
  * I've implemented WINDUP-562  (ozizka, 14:10:38)
  * (mbriskar) I was working on enhancing the updating functionality,
    where new issues were introduced (FORGE-2308). However I didn't
    finish it in order to be able to start working on the server
    migration  (lincolnthree, 14:10:57)
  * (mbriskar) Now I am on 2-days RH internal soft-skills course.
    (lincolnthree, 14:10:57)
  * (mbriskar) We agreed with Ondra that I will provide some
    functionality tests that will show which way to implement the
    marking of the FileModels (edge vs property).  (lincolnthree,
    14:10:57)
  * (mbriskar) After that I will work on the functionality to provide
    operations to build CLICommands with an api like
    CLICommand.on("subsystem").run("some command").withParam("param",
    "value").withParam("param", "value") or similar. Firstly I will need
    to study deeper about this, because I don't have much knowledge
    about how it works (subsystems&CLI).  (lincolnthree, 14:10:57)
  * Now working on WINDUP-566  (ozizka, 14:11:02)
  * And also working on F2F organization - rooms, L&L, agenda  (ozizka,
    14:11:49)
  * Added a prescan filter to improve performance to TypeInterestFactory
    (jsightler, 14:15:03)
  * Also, worked with brad and lincoln to integrate performance PRs
    related to improving decompilation and xml caching  (jsightler,
    14:15:23)
  * (and to test lincoln's ast batching branch)  (jsightler, 14:15:38)
  * Reviewed several PRs  (lincolnthree, 14:15:57)
  * Worked on performance tuning and got distracted by refactoring
    (still working on a PR here locally)  (lincolnthree, 14:15:57)
  * Worked on building a PoC XML document cache with Brad
    (lincolnthree, 14:15:57)
  * Worked on the AST batch processing performance  (lincolnthree,
    14:15:57)
  * Plan on continuing to work on my refactoring and also review the
    auto-update PR and other new functionality  (lincolnthree, 14:15:57)
  * Going forward, I am experimenting with not unzipping the lowest
    level archives within an input application.  (jsightler, 14:15:58)
  * We also had a "whiteboard session" with Matej, talking about server
    migration - goals, design, implementation, etc.  (ozizka, 14:20:59)
  * Worked with the Customer Portal team to build the Windup User Guide
    and Windup Rules Development Guide using the new Drupal process.
    They are now on Doc Stage and can be pushed to the portal any time
    (sgilda, 14:21:15)

* F2F meeting agenda  (lincolnthree, 14:21:26)

* WINDUP-574 ?  (ozizka, 14:29:35)
  * Generating these docs from runtime info is the best option,
    (ozizka, 14:30:56)
  * but we have other priorities now.  (ozizka, 14:31:11)

* Server migration, the big picture  (ozizka, 14:31:19)

* Holidays in CZ, PTOs  (ozizka, 14:33:44)

* Priorities  (ozizka, 14:34:50)
  * Server Config, Performance, Ecliple Plugin, Quickstarts and Examples
    (lincolnthree, 14:35:17)
  * Server Config - In progress (Ondra, Matej)  (lincolnthree, 14:35:28)
  * Performance - In progress (Jess, Lincoln)  (lincolnthree, 14:35:38)
  * Eclipse Plugin - In progress (Jess, Lincoln, Ian)  (lincolnthree,
    14:35:54)
  * Quickstarts and Examples - Not started (Lincoln)  (lincolnthree,
    14:36:12)
  * LINK:
    https://drive.google.com/a/redhat.com/file/d/0B6TharS7fpqGMV9OZUdnUjVYYWs/view?usp=sharing
    (ozizka, 14:36:47)

* Version comparisons - is it needed?  (lincolnthree, 14:37:02)
  * Could users want to downgrade?  (ozizka, 14:38:51)
  * How about AS vs. EAP  (ozizka, 14:39:21)
  * AGREED: We will not worry about minor/micro versions. We will focus
    on Major version to Major version comparisons only.  (lincolnthree,
    14:41:48)
  * LINK:
    https://drive.google.com/a/redhat.com/file/d/0B6TharS7fpqGMV9OZUdnUjVYYWs/view?usp=sharing
    (ozizka, 14:43:37)
  * Presented the big picture.  (ozizka, 14:59:20)
  * Nice job, looks good so far ozizka :)  (lincolnthree, 14:59:28)

Meeting ended at 15:00:17 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/20150429/1dfb7f7c/attachment.html 

From lincolnbaxter at gmail.com  Thu Apr 30 10:43:06 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 30 Apr 2015 10:43:06 -0400
Subject: [windup-dev] JBoss EAP 5 to JBoss EAP 6 Rules
In-Reply-To: <1328083013.6246367.1430318267247.JavaMail.zimbra@redhat.com>
References: <1096869647.6246242.1430318257733.JavaMail.zimbra@redhat.com>
	<1328083013.6246367.1430318267247.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4E97joiZEHpZqdgb+n+=0wbVrbUFgHKxyjyyY+G553eMg@mail.gmail.com>

Hey Ian,

I don't think we really have a good set of rules for EAP5 to EAP6 -
https://github.com/windup/windup-rulesets/tree/master/rules/jboss-eap

You can try running Windup on it, but chances are, it will be pretty
general results (if any).

Sorry,
~Lincoln

On Wed, Apr 29, 2015 at 10:37 AM, Ian Tewksbury <itewk at redhat.com> wrote:

> All,
>
> Are there any rules already created for a JBoss 5 to JBoss 6 migration?
>
> My customer is looking for tool to help streamline the migration.
>
> Blue Skies,
> ~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/20150430/dba49239/attachment.html 

From akash.prajapati at tcs.com  Mon Apr 13 02:23:58 2015
From: akash.prajapati at tcs.com (Akash Prajapati)
Date: Mon, 13 Apr 2015 06:23:58 -0000
Subject: [windup-dev] Windup 2.0 - Custom rule creation
Message-ID: <OF355D512D.F37315F0-ON65257E26.0022B347-65257E26.002324C0@tcs.com>

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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150413/4dbffe6d/attachment-0001.html 

From b.jayaraman at accenturefederal.com  Mon Apr 27 12:20:56 2015
From: b.jayaraman at accenturefederal.com (b.jayaraman at accenturefederal.com)
Date: Mon, 27 Apr 2015 16:20:56 -0000
Subject: [windup-dev] Windup usage Issue
Message-ID: <52438C265F8F8A4A9F099395055B389838775D34@AFSMAILMB008.us.accenturefederal.com>

Hi
         I'm trying to port an application that is currently hosted on Websphere 8.5 running on JDK 1.7 to JBoss EAP 6.4. I downloaded and installed Windup and tested with default provided ear file conversion, things worked fine, however, if I try to run through my app, I get zero story points for one app and for another app, I get only one story point. When windup runs, I see that websphere rules gets executed but still no results. I also tried to explode one of the war file and run through windup, it did not go through the files under WEB-INF/classes directory. I have created the issue in JIRA as well (https://issues.jboss.org/browse/WINDUP-567 & https://developer.jboss.org/message/926645#926645  ) . I can open the ear file and start double checking against the windup results but before that I just want to check with you for any additional hints or installation verification steps.

Thanks for your time,
-Babu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150427/b17f38b0/attachment-0001.html 

From ozizka at redhat.com  Tue Apr 28 13:34:34 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Tue, 28 Apr 2015 17:34:34 -0000
Subject: [windup-dev] Server migration, the big picture
In-Reply-To: <1gYj.tLP.5uaCVm3xMmp.1LFgtc@seznam.cz>
References: <1gYj.tLP.5uaCVm3xMmp.1LFgtc@seznam.cz>
Message-ID: <553FC4A1.20400@redhat.com>

Hi all,

as I promised, hereby I am proposing how the migration should look like 
in the bigger picture.
I don't say we need all the described parts, but I have a good reason to 
believe we do.
Details are described in respective Jira issues. The root Jira issue is 
MIGR-229.

See the attached whiteboard photo for an overview. Slightly chaotic, as 
drawn on the fly, and it's not complete anyway. Let's make a better one 
on F2F.

General:
======

1) Server rules in it's own ruleset. Probably also in separated git repo 
(as it is now).

2) The ruleset will reuse certain operations from other rulesets:
       XPath query to XML documents,
       .properties parsing,
       possibly decompilation and analysis of classes - e.g. Tomcat 
valves, maybe Spring beans, JMX mBeans (esp. for EAP 4), implementations 
of various interfaces used for EAP 5, etc.

3) The ruleset will provide certain new
        conditions, like CLI parsing,
        and operations, like
            CLI operations export, in a form of WINDUP-565 
<https://issues.jboss.org/browse/WINDUP-565>
                 CLI commands in the report, with comments, highlights 
of the source it was derived form, links to EAP/WildFly docs, etc.;
                 CLI commands script;
                 CLI commands execution against some running server
            Adding a module to EAP 6 target
            Installing a fresh target server  (if handy)
        We can look at Eduardo's WINDUP-550 
<https://issues.jboss.org/browse/WINDUP-550> to see what we can reuse 
for these.

4) The server ruleset will probably have a bit stronger source/target 
technology split, in terms of respective rules being more organized into 
individual addons. Not sure about this, depends on the mechanism we use 
to enable/disable them.

5) To prevent running the app rules against server files, resp. to 
support running app and server rules together, we need to update the 
queries of some app rules to only focus on appropriate files. WINDUP-564 
<https://issues.jboss.org/browse/WINDUP-564> and WINDUP-563 
<https://issues.jboss.org/browse/WINDUP-563> .  This is what I would 
like to work on next. Now working on WINDUP-566 
<https://issues.jboss.org/browse/WINDUP-566> .



Parts:
====
Target technologies:
   So far, we consider EAP 6 as target server. The long-term goal of EAP 
6 is to cover configuration with CLI. Not sure about current state, but 
it needed some additional actions - direct file manipulation (e.g. modules).
   Maybe some other target technologies? Depends on what is Windup used 
for. SOA? Drools? Containers for these might require additional 
configuration.

Source technologies:
   The platforms we target long-term. It will be mostly XML and 
.properties. But could also be more tricky parts, like, digging data 
from EAP 5's ProfileService, mod_cluster config?, etc.

Platform identification and files comparison: WINDUP-562 
<https://issues.jboss.org/browse/WINDUP-562> (Done)
   As discussed during last status meeting, it will be useful to
       recognize the server version - the user may not know the exact 
version, which we need to know the default configuration (in case of CLI 
script migration which just skips the defaults.)
       recognize which files were changed compared to the distribution 
of that version - i.e. which configuration files changed (and we don't 
handle them) and which .jars are changed.

-------------
Those are rough boundaries. Anything to add or remove? And priorities?


Ondra




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150428/f871aab3/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMAG6306.jpg
Type: image/jpeg
Size: 1431079 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150428/f871aab3/attachment-0001.jpg