1) Ian, I just ponder: Why does it need JBDS and not just eclipse? Because the idea was that eventually it would become a full-fledged JBDS project plugin so it made sense to automatically pick up all of their existing dependencies. I have not looked at this in like two months, it is likely the parent version needs to update if JBDS has come out with any new version.

2) Ian, Max, do I need JBDS source or can I find the artifacts somewhere? I only found 0.0.4-SNAPSHOT From any of the jboss tools plugins you can get a link to https://community.jboss.org/wiki/HowToBuildJBossTools33WithMaven3 which tells you how to set up your maven preferences to be able to build a JBDS plugin, basically need to add the correct repos. Though I also see now there is a how to do it with Maven 4, so another thing to look at.

I should probably add this link to the read me of the windup-eclipse-plugin, https://github.com/windup/windup-eclipse-plugin/issues/9. 3) Max, where do I get JBDS source code? I only found in [1] that it's in customer portal. Based on number two, you should not need the JBDS source code. ------------------- As for all your build errors. This is all extending from https://github.com/windup/windup-eclipse-plugin/issues/6. Where I left off with development is figuring out how to get those dang JUnits to compile. So the way I have been compiling it to get the main plugin is run the "mvn clean verify" from the "......\windup-eclipse-plugin\plugins" directory rather than the parent " ...\windup-eclipse-plugin" directory to avoid building the tests.

To debug you right click on the plugin project in eclipse and select to "Debug As... -> Eclipse Application" and that should work. https://github.com/windup/windup-eclipse-plugin/issues/10 ------------------- Sorry the documentation is so lacking, I have just not had time to work on this. I was originally going to be on the bench for the next 2 and a half weeks and was going to really hunker down on this, but then plans changed and now I won't be on the bench for another two weeks and then only for half a week. But I still hope during those few days I can resolve all the compile issues, and then maybe address couple of the outstanding enhancements I have open. https://github.com/windup/windup-eclipse-plugin/issues ------------------ If you need any more help please do not hesitate to ask. ~Ian -----Original Message----- From: Ondrej Zizka [mailto:ozizka@redhat.com] Sent: Tuesday, September 24, 2013 10:15 PM To: Max Rydahl Andersen; Ian Tewksbury; windup-dev(a)lists.jboss.org Subject: Building Windup JBDS plugin Adding windup-dev list. On 25.9.2013 04:09, Ondrej Zizka wrote: > When $SUBJ, I see an exception from Eclipse, see below. The range is > in MANIFEST.MF. > > ondra@lenovo:~/work/JBDS/windup-eclipse-plugin$ git grep 4.8.1 > tests/org.jboss.tools.windup.core.tests/META-INF/MANIFEST.MF: > org.junit4;bundle-version="[4.8.1,5.0.0)" How can I solve this? Thanks, Ondra > > > [ERROR] Internal error: java.lang.RuntimeException: "No solution found > because the problem is unsatisfiable.": ["Unable to satisfy dependency > from org.jboss.tools.windup.core.test 1.0.0.qualifier to bundle > org.junit4 [4.8.1,5.0.0).", "No solution found because the problem is > unsatisfiable."] -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: > java.lang.RuntimeException: "No solution found because the problem is > unsatisfiable.": ["Unable to satisfy dependency from > org.jboss.tools.windup.core.test 1.0.0.qualifier to bundle org.junit4 > [4.8.1,5.0.0).", "No solution found because the problem is > unsatisfiable."] > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm pl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher. java:290) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230 ) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launche r.java:409) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:3 > 52) Caused by: java.lang.RuntimeException: "No solution found because > the problem is unsatisfiable.": ["Unable to satisfy dependency from > org.jboss.tools.windup.core.test 1.0.0.qualifier to bundle org.junit4 > [4.8.1,5.0.0).", "No solution found because the problem is > unsatisfiable."] > at > org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionExce ption(AbstractResolutionStrategy.java:98) > at > org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(Projecto rResolutionStrategy.java:88) > at > org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.resolve(AbstractR esolutionStrategy.java:63) > at > org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2Re solverImpl.java:126) > at > org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2Re solverImpl.java:81) > at > org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P 2TargetPlatformResolver.java:374) > at > org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies (P2TargetPlatformResolver.java:350) > at > org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProj ect(DefaultTychoDependencyResolver.java:109) > at > org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsR ead(TychoMavenLifecycleParticipant.java:82) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > ... 11 more > > > > On 25.9.2013 04:02, Ondrej Zizka wrote: >> Ian, I've built jbosstools-base 4.1.0.Final since Alpha2 build was >> missing something 4.30.5.yadayada Now I get: >> >> [ERROR] Missing requirement: org.jboss.tools.windup.core.test >> 1.0.0.qualifier requires 'bundle org.junit4 [4.8.1,5.0.0)' but it >> could not be found >> >> Isn't that the infamous maven version ranges bug? Did you hit it >> ever? Mvn 3.0.4 >> >> Thx >> >> >> >> On 25.9.2013 03:36, Ondrej Zizka wrote: >>> >>> On 25.9.2013 03:28, Ondrej Zizka wrote: >>>> Hi Ian, >>>> >>>> I see that windup eclipse plugin needs org.jboss.tools:parent >>>> 4.1.0.Alpha2-SNAPSHOT. >>>> >>>> 1) Ian, I just ponder: Why does it need JBDS and not just eclipse? >>>> 2) Ian, Max, do I need JBDS source or can I find the artifacts >>>> somewhere? I only found 0.0.4-SNAPSHOT >>>> 3) Max, where do I get JBDS source code? I only found in [1] that >>>> it's in customer portal. >>> Found on GitHub. Now, could you please send a "how to build" >>> link? Like, which all repos do I need to clone etc. to get the basic >>> eclipse api to build windup against. Thx >>>> >>>> Thanks, Ondra >>>> >>>> [1] >>>> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_De >>>> veloper_Studio/7.0/pdf/Release_Notes_7.0.0/Red_Hat_JBoss_Developer_ >>>> Studio-7.0-Release_Notes_7.0.0-en-US.pdf >>>> >>> >> >

Max, You mention " btw. jbosstools-dev is a great way to get answers to such issues :)" is a great place to get some build problems answered. Is that a mailing list? Where do I sign up, I don't see it listed in the postoffice. I am having a new build issue. ~Ian -----Original Message----- From: Max Rydahl Andersen [mailto:manderse@redhat.com] Sent: Wednesday, September 25, 2013 2:01 PM To: Ian Tewksbury Cc: Ondrej Zizka; windup-dev(a)lists.jboss.org Subject: Re: Building Windup JBDS plugin >1) Ian, I just ponder: Why does it need JBDS and not just eclipse? > >Because the idea was that eventually it would become a full-fledged >JBDS project plugin so it made sense to automatically pick up all of >their existing dependencies. I have not looked at this in like two >months, it is likely the parent version needs to update if JBDS has >come out with any new version. Yes, use the final version instead. btw. it is *not* dependent on JBDS, it is dependent on JBoss Tools parent pom - thats all. Might make sense to actually be dependent on some things but for now not relevant besides common build and dependencies setup to be compatible. >2) Ian, Max, do I need JBDS source or can I find the artifacts somewhere? >I only found 0.0.4-SNAPSHOT > >From any of the jboss tools plugins you can get a link to >https://community.jboss.org/wiki/HowToBuildJBossTools33WithMaven3 which >tells you how to set up your maven preferences to be able to build a >JBDS plugin, basically need to add the correct repos. Though I also see >now there is a how to do it with Maven 4, so another thing to look at. Maven 4 ? >I should probably add this link to the read me of the >windup-eclipse-plugin, >https://github.com/windup/windup-eclipse-plugin/issues/9. > >3) Max, where do I get JBDS source code? I only found in [1] that it's >in customer portal. > >Based on number two, you should not need the JBDS source code. > >------------------- > >As for all your build errors. This is all extending from >https://github.com/windup/windup-eclipse-plugin/issues/6. > >Where I left off with development is figuring out how to get those dang >JUnits to compile. So the way I have been compiling it to get the main >plugin is run the "mvn clean verify" from the >"......\windup-eclipse-plugin\plugins" directory rather than the parent " >...\windup-eclipse-plugin" directory to avoid building the tests. simply dont use org.junit4, use org.junit. btw. jbosstools-dev is a great way to get answers to such issues :) >To debug you right click on the plugin project in eclipse and select to >"Debug As... -> Eclipse Application" and that should work. >https://github.com/windup/windup-eclipse-plugin/issues/10 > >------------------- > >Sorry the documentation is so lacking, I have just not had time to work >on this. I was originally going to be on the bench for the next 2 and a >half weeks and was going to really hunker down on this, but then plans >changed and now I won't be on the bench for another two weeks and then >only for half a week. But I still hope during those few days I can >resolve all the compile issues, and then maybe address couple of the >outstanding enhancements I have open. >https://github.com/windup/windup-eclipse-plugin/issues > >------------------ > >If you need any more help please do not hesitate to ask. > >~Ian > >-----Original Message----- >From: Ondrej Zizka [mailto:ozizka@redhat.com] >Sent: Tuesday, September 24, 2013 10:15 PM >To: Max Rydahl Andersen; Ian Tewksbury; windup-dev(a)lists.jboss.org >Subject: Building Windup JBDS plugin > >Adding windup-dev list. > > >On 25.9.2013 04:09, Ondrej Zizka wrote: >> When $SUBJ, I see an exception from Eclipse, see below. The range is >> in MANIFEST.MF. >> >> ondra@lenovo:~/work/JBDS/windup-eclipse-plugin$ git grep 4.8.1 >> tests/org.jboss.tools.windup.core.tests/META-INF/MANIFEST.MF: >> org.junit4;bundle-version="[4.8.1,5.0.0)" > >How can I solve this? > >Thanks, >Ondra >> >> >> [ERROR] Internal error: java.lang.RuntimeException: "No solution >> found because the problem is unsatisfiable.": ["Unable to satisfy >> dependency from org.jboss.tools.windup.core.test 1.0.0.qualifier to >> bundle >> org.junit4 [4.8.1,5.0.0).", "No solution found because the problem is >> unsatisfiable."] -> [Help 1] >> org.apache.maven.InternalErrorException: Internal error: >> java.lang.RuntimeException: "No solution found because the problem is >> unsatisfiable.": ["Unable to satisfy dependency from >> org.jboss.tools.windup.core.test 1.0.0.qualifier to bundle org.junit4 >> [4.8.1,5.0.0).", "No solution found because the problem is >> unsatisfiable."] >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168) >> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) >> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java : >57) >> at >> >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso >rIm >pl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:606) >> at >> >org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher . >java:290) >> at >> >org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java: >230 >) >> at >> >org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Laun >che >r.java:409) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java: >> 3 >> 52) Caused by: java.lang.RuntimeException: "No solution found because >> the problem is unsatisfiable.": ["Unable to satisfy dependency from >> org.jboss.tools.windup.core.test 1.0.0.qualifier to bundle org.junit4 >> [4.8.1,5.0.0).", "No solution found because the problem is >> unsatisfiable."] >> at >> >org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionE >xce >ption(AbstractResolutionStrategy.java:98) >> at >> >org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(Proje >cto >rResolutionStrategy.java:88) >> at >> >org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.resolve(Abstra >ctR >esolutionStrategy.java:63) >> at >> >org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P >2Re >solverImpl.java:126) >> at >> >org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P >2Re >solverImpl.java:81) >> at >> >org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatfor >m(P >2TargetPlatformResolver.java:374) >> at >> >org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependenc >ies >(P2TargetPlatformResolver.java:350) >> at >> >org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveP >roj >ect(DefaultTychoDependencyResolver.java:109) >> at >> >org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjec >tsR >ead(TychoMavenLifecycleParticipant.java:82) >> at >org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) >> ... 11 more >> >> >> >> On 25.9.2013 04:02, Ondrej Zizka wrote: >>> Ian, I've built jbosstools-base 4.1.0.Final since Alpha2 build was >>> missing something 4.30.5.yadayada Now I get: >>> >>> [ERROR] Missing requirement: org.jboss.tools.windup.core.test >>> 1.0.0.qualifier requires 'bundle org.junit4 [4.8.1,5.0.0)' but it >>> could not be found >>> >>> Isn't that the infamous maven version ranges bug? Did you hit it >>> ever? Mvn 3.0.4 >>> >>> Thx >>> >>> >>> >>> On 25.9.2013 03:36, Ondrej Zizka wrote: >>>> >>>> On 25.9.2013 03:28, Ondrej Zizka wrote: >>>>> Hi Ian, >>>>> >>>>> I see that windup eclipse plugin needs org.jboss.tools:parent >>>>> 4.1.0.Alpha2-SNAPSHOT. >>>>> >>>>> 1) Ian, I just ponder: Why does it need JBDS and not just eclipse? >>>>> 2) Ian, Max, do I need JBDS source or can I find the artifacts >>>>> somewhere? I only found 0.0.4-SNAPSHOT >>>>> 3) Max, where do I get JBDS source code? I only found in [1] that >>>>> it's in customer portal. >>>> Found on GitHub. Now, could you please send a "how to build" >>>> link? Like, which all repos do I need to clone etc. to get the >>>> basic eclipse api to build windup against. Thx >>>>> >>>>> Thanks, Ondra >>>>> >>>>> [1] >>>>> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_D >>>>> e >>>>> veloper_Studio/7.0/pdf/Release_Notes_7.0.0/Red_Hat_JBoss_Developer >>>>> _ Studio-7.0-Release_Notes_7.0.0-en-US.pdf >>>>> >>>> >>> >> >