Got Windup to extract variables and handle nested Xpaths
by Robb Greathouse
Hi,
I was able to update Windup to extract multiple variables with XPath and handle unbounded nesting of xpath-value objects.
Robb Greathouse
Partner Enablement
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
12 years, 12 months
Maven consumable build of windup
by Ian Tewksbury
Am I correct in assuming that as of right now windup is not being built on
any nightly build server and then being deployed to a maven repository?
I am looking to setup the maven-eclipse-plugin project on the JBoss Tools
CI but because the plugin has a dependency on windup right now the only
way I am able to build it is by manually downloading windup and compiling
it locally. This strategy won't work for a CI build, I am therefor on the
hunt for a solution.
I was also thinking it may be about time to start handling releases of
windup better, which would coincide nicely with having a nightly build
server. Right now we do active development in what looks like release
version of Windup rather than using the maven standard of -SNAPSHOT
releases. As a project that depends on the Windup project this
inconsistency in build versions does make life a bit trickery.
Thoughts?
Blue Skies,
~Ian
13 years
add CDATA inline hint for XPATH find
by Rebecca Searls
I'm looking for a rule that allows me to add CDATA to an XPATH based rule?
I only find that java-hint supports this. Have I missed something?
<windup:xpath-value description="MDB's Bean-specific instance pool can be set with one line in management CLI"
xpath="//jboss/container-configurations/container-configuration[@extends='Standard Message Driven Bean']"
inline="true">
</windup:xpath-value>
13 years
windup-eclipse-plugin finally stable!
by Ian Tewksbury
Hi All,
I just thought I would share with you all that I finally had the time to
sit down and fix the test plugin compile issues and add some JUnits to the
project.
So now not only does the project finally build from the root, but it also
runs two valid JUnits!
This was my first time combining Maven and Eclipse builds and it was an
exciting adventure figuring out just the right way to do it.
My next step will likely be to clean up the readmes for the project.
Blue Skies,
~Ian
13 years
Building Windup JBDS plugin
by Ondrej Zizka
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(DelegatingMethodAccessorImpl.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(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> 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.newResolutionException(AbstractResolutionStrategy.java:98)
> at
> org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:88)
> at
> org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63)
> at
> org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:126)
> at
> org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:81)
> at
> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:374)
> at
> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:350)
> at
> org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:109)
> at
> org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(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_Develope...
>>>>
>>>
>>
>
13 years
Migrating SyncServiceInvoker from esb to switchyard
by Robb Greathouse
Hi,
Have client that wants a rule to give them hint on how to migrate the ESB SyncServiceInvoker to the Switchyard equivalent.
It appears that the best practice would be to migrate this to camel. The likely candidate is the camel DelegateSyncProcessor.
Was wondering if you had any knowledge regarding this?
Robb Greathouse
Partner Enablement
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
13 years
