From ozizka at redhat.com Fri Apr 15 19:02:41 2016
From: ozizka at redhat.com (Ondrej Zizka)
Date: Sat, 16 Apr 2016 01:02:41 +0200
Subject: [windup-dev] Deps in windup-rules-java-api
Message-ID: <57117311.2000106@redhat.com>
Hi,
I've noticed that in the pom.xml of $subj, there is:
<dependency>
<groupId>org.jboss.windup.ast</groupId>
<artifactId>windup-java-ast</artifactId>
<classifier>forge-addon</classifier>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.jboss.windup.rules.apps</groupId>
<artifactId>windup-rules-base</artifactId>
<classifier>forge-addon</classifier>
<scope>compile</scope>
</dependency>
Shouldn't that be of scope provided, and listed in ../addon/pom.xml ?
Ondra
From mnovotny at redhat.com Mon Apr 18 04:29:17 2016
From: mnovotny at redhat.com (Marek Novotny)
Date: Mon, 18 Apr 2016 10:29:17 +0200
Subject: [windup-dev] Deps in windup-rules-java-api
In-Reply-To: <57117311.2000106@redhat.com>
References: <57117311.2000106@redhat.com>
Message-ID: <57149ADD.7030909@redhat.com>
Ondra,
as
https://github.com/windup/windup/wiki/Rules-Create-a-Basic-Java-based-Rule-Add-on
shows a template for new add-on, forge-addon should be in provided scope.
I think we probably need to review the whole project if that is correct
everywhere.
I don't see a reason why it could require it in compile scope.
On 16.4.2016 01:02, Ondrej Zizka wrote:
> Hi,
>
> I've noticed that in the pom.xml of $subj, there is:
>
> <dependency>
> <groupId>org.jboss.windup.ast</groupId>
> <artifactId>windup-java-ast</artifactId>
> <classifier>forge-addon</classifier>
> <scope>compile</scope>
> </dependency>
> <dependency>
> <groupId>org.jboss.windup.rules.apps</groupId>
> <artifactId>windup-rules-base</artifactId>
> <classifier>forge-addon</classifier>
> <scope>compile</scope>
> </dependency>
>
>
> Shouldn't that be of scope provided, and listed in ../addon/pom.xml ?
>
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Marek Novotny
--
Windup team member and Seam Project Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
From jsightle at redhat.com Mon Apr 18 08:54:55 2016
From: jsightle at redhat.com (Jess Sightler)
Date: Mon, 18 Apr 2016 08:54:55 -0400
Subject: [windup-dev] Deps in windup-rules-java-api
In-Reply-To: <57117311.2000106@redhat.com>
References: <57117311.2000106@redhat.com>
Message-ID: <5714D91F.5020308@redhat.com>
Feel free to try it. "provided" is generally what we would do in those
cases.
On 04/15/2016 07:02 PM, Ondrej Zizka wrote:
> Hi,
>
> I've noticed that in the pom.xml of $subj, there is:
>
> <dependency>
> <groupId>org.jboss.windup.ast</groupId>
> <artifactId>windup-java-ast</artifactId>
> <classifier>forge-addon</classifier>
> <scope>compile</scope>
> </dependency>
> <dependency>
> <groupId>org.jboss.windup.rules.apps</groupId>
> <artifactId>windup-rules-base</artifactId>
> <classifier>forge-addon</classifier>
> <scope>compile</scope>
> </dependency>
>
>
> Shouldn't that be of scope provided, and listed in ../addon/pom.xml ?
>
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Tue Apr 19 07:28:02 2016
From: ozizka at redhat.com (Ondrej Zizka)
Date: Tue, 19 Apr 2016 13:28:02 +0200
Subject: [windup-dev] Deps in windup-rules-java-api
In-Reply-To: <5714D91F.5020308@redhat.com>
References: <57117311.2000106@redhat.com> <5714D91F.5020308@redhat.com>
Message-ID: <57161642.2060400@redhat.com>
There's a difference whether it's in the addon or in the submodule.
Submodule can have a compile time dependency. Addon should have provided.
The rules for addon pom.xml deps are quite complex, once I wrote down
what I knew to those pages on wiki, but there are blank spots.
+1 that we could review the deps. At least we would refresh how it
should be.
Ondra
On 18.4.2016 14:54, Jess Sightler wrote:
> Feel free to try it. "provided" is generally what we would do in those
> cases.
>
> On 04/15/2016 07:02 PM, Ondrej Zizka wrote:
>> Hi,
>>
>> I've noticed that in the pom.xml of $subj, there is:
>>
>> <dependency>
>> <groupId>org.jboss.windup.ast</groupId>
>> <artifactId>windup-java-ast</artifactId>
>> <classifier>forge-addon</classifier>
>> <scope>compile</scope>
>> </dependency>
>> <dependency>
>> <groupId>org.jboss.windup.rules.apps</groupId>
>> <artifactId>windup-rules-base</artifactId>
>> <classifier>forge-addon</classifier>
>> <scope>compile</scope>
>> </dependency>
>>
>>
>> Shouldn't that be of scope provided, and listed in ../addon/pom.xml ?
>>
>> Ondra
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From jsightle at redhat.com Tue Apr 19 08:18:37 2016
From: jsightle at redhat.com (Jess Sightler)
Date: Tue, 19 Apr 2016 08:18:37 -0400 (EDT)
Subject: [windup-dev] Deps in windup-rules-java-api
In-Reply-To: <57161642.2060400@redhat.com>
References: <57117311.2000106@redhat.com> <5714D91F.5020308@redhat.com>
<57161642.2060400@redhat.com>
Message-ID: <1922557820.53180177.1461068317806.JavaMail.zimbra@redhat.com>
The detailed documentation on how forge module scopes correlate with maven scopes is here:
https://forge.jboss.org/document/develop-an-addon
----- Original Message -----
> From: "Ondrej Zizka" <ozizka at redhat.com>
> To: windup-dev at lists.jboss.org
> Sent: Tuesday, April 19, 2016 7:28:02 AM
> Subject: Re: [windup-dev] Deps in windup-rules-java-api
>
> There's a difference whether it's in the addon or in the submodule.
> Submodule can have a compile time dependency. Addon should have provided.
>
> The rules for addon pom.xml deps are quite complex, once I wrote down
> what I knew to those pages on wiki, but there are blank spots.
> +1 that we could review the deps. At least we would refresh how it
> should be.
>
> Ondra
>
>
> On 18.4.2016 14:54, Jess Sightler wrote:
> > Feel free to try it. "provided" is generally what we would do in those
> > cases.
> >
> > On 04/15/2016 07:02 PM, Ondrej Zizka wrote:
> >> Hi,
> >>
> >> I've noticed that in the pom.xml of $subj, there is:
> >>
> >> <dependency>
> >> <groupId>org.jboss.windup.ast</groupId>
> >> <artifactId>windup-java-ast</artifactId>
> >> <classifier>forge-addon</classifier>
> >> <scope>compile</scope>
> >> </dependency>
> >> <dependency>
> >> <groupId>org.jboss.windup.rules.apps</groupId>
> >> <artifactId>windup-rules-base</artifactId>
> >> <classifier>forge-addon</classifier>
> >> <scope>compile</scope>
> >> </dependency>
> >>
> >>
> >> Shouldn't that be of scope provided, and listed in ../addon/pom.xml ?
> >>
> >> Ondra
> >> _______________________________________________
> >> windup-dev mailing list
> >> windup-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/windup-dev
> > _______________________________________________
> > windup-dev mailing list
> > windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
From mnovotny at redhat.com Tue Apr 19 08:37:11 2016
From: mnovotny at redhat.com (Marek Novotny)
Date: Tue, 19 Apr 2016 14:37:11 +0200
Subject: [windup-dev] Deps in windup-rules-java-api
In-Reply-To: <1922557820.53180177.1461068317806.JavaMail.zimbra@redhat.com>
References: <57117311.2000106@redhat.com> <5714D91F.5020308@redhat.com>
<57161642.2060400@redhat.com>
<1922557820.53180177.1461068317806.JavaMail.zimbra@redhat.com>
Message-ID: <57162677.7050700@redhat.com>
The question is why windup add-on should expose an API of an add-on
through another add-on. That would create problematic dependencies I think.
On 19.4.2016 14:18, Jess Sightler wrote:
> The detailed documentation on how forge module scopes correlate with maven scopes is here:
> https://forge.jboss.org/document/develop-an-addon
>
> ----- Original Message -----
>> From: "Ondrej Zizka" <ozizka at redhat.com>
>> To: windup-dev at lists.jboss.org
>> Sent: Tuesday, April 19, 2016 7:28:02 AM
>> Subject: Re: [windup-dev] Deps in windup-rules-java-api
>>
>> There's a difference whether it's in the addon or in the submodule.
>> Submodule can have a compile time dependency. Addon should have provided.
>>
>> The rules for addon pom.xml deps are quite complex, once I wrote down
>> what I knew to those pages on wiki, but there are blank spots.
>> +1 that we could review the deps. At least we would refresh how it
>> should be.
>>
>> Ondra
>>
>>
>> On 18.4.2016 14:54, Jess Sightler wrote:
>>> Feel free to try it. "provided" is generally what we would do in those
>>> cases.
>>>
>>> On 04/15/2016 07:02 PM, Ondrej Zizka wrote:
>>>> Hi,
>>>>
>>>> I've noticed that in the pom.xml of $subj, there is:
>>>>
>>>> <dependency>
>>>> <groupId>org.jboss.windup.ast</groupId>
>>>> <artifactId>windup-java-ast</artifactId>
>>>> <classifier>forge-addon</classifier>
>>>> <scope>compile</scope>
>>>> </dependency>
>>>> <dependency>
>>>> <groupId>org.jboss.windup.rules.apps</groupId>
>>>> <artifactId>windup-rules-base</artifactId>
>>>> <classifier>forge-addon</classifier>
>>>> <scope>compile</scope>
>>>> </dependency>
>>>>
>>>>
>>>> Shouldn't that be of scope provided, and listed in ../addon/pom.xml ?
>>>>
>>>> Ondra
>>>> _______________________________________________
>>>> 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
>>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Marek Novotny
--
Windup team member and Seam Project Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
From mnovotny at redhat.com Wed Apr 20 09:49:31 2016
From: mnovotny at redhat.com (Marek Novotny)
Date: Wed, 20 Apr 2016 15:49:31 +0200
Subject: [windup-dev] Fwd: [WindUp] Regular expression to detect filesystem
paths
In-Reply-To: <CAHFLeqv9fU1zpp7d1sGsmQru-MgtM_VS1Ut0YzsdnLEuOL9rnA@mail.gmail.com>
References: <CAHFLeqv9fU1zpp7d1sGsmQru-MgtM_VS1Ut0YzsdnLEuOL9rnA@mail.gmail.com>
Message-ID: <571788EB.5000707@redhat.com>
adding windup-dev ml as this could be interested to Windup community.
Romain,
I would go with simplified pattern for every unique occurrence to more
more general one.
So try to use <or></or> and condition patterns in it.
Something like the following:
<rule id="filesystem-paths-properties">
<when>
<or>
<filecontent filename="{*}.{extensions}"
pattern="{filesystem}" />
<filecontent filename="{*}.{extensions}"
pattern="{netfilesystem}" />
<filecontent filename="{*}.{extensions}"
pattern="page import="{filesystem}" />
</or>
</when>
<perform>
<hint message="File system properties" effort="1"
severity="mandatory">
<message>
TODO
</message>
</hint>
</perform>
<where param="extensions">
<matches pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
</where>
<where param="filesystem">
<matches pattern="(\S:[\\|/])" />
</where>
<where param="netfilesystem">
<matches pattern="(\\\\ntfileserver\)" />
</where>
<where param="netfilesystem">
<matches pattern="" />
</where>
</rule>
-------- Forwarded Message --------
Subject: [WindUp] Regular expression to detect filesystem paths
Date: Wed, 20 Apr 2016 15:29:03 +0200
From: Roman Martin Gil <rmarting at redhat.com>
To: Marek Novotny <mnovotny at redhat.com>
Hi,
I am very obfuscated to create a rule to identify some filesystem paths
patterns. I am trying to detect when the code (.java, .properties) have
the following entries:
* "c:\\"
* "e:\\"
* "c:/"
* "e:/"
* "\\\\ntfileserver\"
* "page import="""
My first approach is similar to:
<rule id="filesystem-paths-properties">
<when>
<filecontent filename="{*}.{extensions}"
pattern="{filesystem}" />
</when>
<perform>
<hint message="File system properties" effort="1"
severity="mandatory">
<message>
TODO
</message>
</hint>
</perform>
<where param="extensions">
<matches pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
</where>
<where param="filesystem">
<matches pattern="((c|e):|[\\])" />
</where>
</rule>
However I am detecting cases as "Message: " as a pattern. How could I
create a rule to identify these cases?
Thank you very much in advance
PD: What is the better mail list to send it?
--
Saludos/Best regards
______________________________________________________________________
*Jose Roman Martin Gil *
/MW Senior Architect/ | +34 605 926 271 | roman.martin at redhat.com
<mailto:roman.martin at redhat.com>
/**/*Red Hat* Iberia
C/ Jos? Bardasano Baos, 9, Edif. Gorbea 3, planta 3?D, 28016 Madrid, Spain
______________________________________________________________________
From bdavis at redhat.com Wed Apr 20 10:01:05 2016
From: bdavis at redhat.com (Brad Davis)
Date: Wed, 20 Apr 2016 10:01:05 -0400 (EDT)
Subject: [windup-dev] Fwd: [WindUp] Regular expression to detect
filesystem paths
In-Reply-To: <571788EB.5000707@redhat.com>
References: <CAHFLeqv9fU1zpp7d1sGsmQru-MgtM_VS1Ut0YzsdnLEuOL9rnA@mail.gmail.com>
<571788EB.5000707@redhat.com>
Message-ID: <1841929557.52201796.1461160865600.JavaMail.zimbra@redhat.com>
+1 -- it is not only important for Windows to Linux, but also for identifying file read / writes that need to be mounted for cloud deployments to things like OpenShift.
Brad Davis
Director of FSI Solutions, Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Marek Novotny" <mnovotny at redhat.com>
To: "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Wednesday, April 20, 2016 9:49:31 AM
Subject: [windup-dev] Fwd: [WindUp] Regular expression to detect filesystem paths
adding windup-dev ml as this could be interested to Windup community.
Romain,
I would go with simplified pattern for every unique occurrence to more
more general one.
So try to use <or></or> and condition patterns in it.
Something like the following:
<rule id="filesystem-paths-properties">
<when>
<or>
<filecontent filename="{*}.{extensions}"
pattern="{filesystem}" />
<filecontent filename="{*}.{extensions}"
pattern="{netfilesystem}" />
<filecontent filename="{*}.{extensions}"
pattern="page import="{filesystem}" />
</or>
</when>
<perform>
<hint message="File system properties" effort="1"
severity="mandatory">
<message>
TODO
</message>
</hint>
</perform>
<where param="extensions">
<matches pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
</where>
<where param="filesystem">
<matches pattern="(\S:[\\|/])" />
</where>
<where param="netfilesystem">
<matches pattern="(\\\\ntfileserver\)" />
</where>
<where param="netfilesystem">
<matches pattern="" />
</where>
</rule>
-------- Forwarded Message --------
Subject: [WindUp] Regular expression to detect filesystem paths
Date: Wed, 20 Apr 2016 15:29:03 +0200
From: Roman Martin Gil <rmarting at redhat.com>
To: Marek Novotny <mnovotny at redhat.com>
Hi,
I am very obfuscated to create a rule to identify some filesystem paths
patterns. I am trying to detect when the code (.java, .properties) have
the following entries:
* "c:\\"
* "e:\\"
* "c:/"
* "e:/"
* "\\\\ntfileserver\"
* "page import="""
My first approach is similar to:
<rule id="filesystem-paths-properties">
<when>
<filecontent filename="{*}.{extensions}"
pattern="{filesystem}" />
</when>
<perform>
<hint message="File system properties" effort="1"
severity="mandatory">
<message>
TODO
</message>
</hint>
</perform>
<where param="extensions">
<matches pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
</where>
<where param="filesystem">
<matches pattern="((c|e):|[\\])" />
</where>
</rule>
However I am detecting cases as "Message: " as a pattern. How could I
create a rule to identify these cases?
Thank you very much in advance
PD: What is the better mail list to send it?
--
Saludos/Best regards
______________________________________________________________________
*Jose Roman Martin Gil *
/MW Senior Architect/ | +34 605 926 271 | roman.martin at redhat.com
<mailto:roman.martin at redhat.com>
/**/*Red Hat* Iberia
C/ Jos? Bardasano Baos, 9, Edif. Gorbea 3, planta 3?D, 28016 Madrid, Spain
______________________________________________________________________
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
From mnovotny at redhat.com Wed Apr 20 10:02:56 2016
From: mnovotny at redhat.com (Marek Novotny)
Date: Wed, 20 Apr 2016 16:02:56 +0200
Subject: [windup-dev] Fwd: [WindUp] Regular expression to detect
filesystem paths
In-Reply-To: <1841929557.52201796.1461160865600.JavaMail.zimbra@redhat.com>
References: <CAHFLeqv9fU1zpp7d1sGsmQru-MgtM_VS1Ut0YzsdnLEuOL9rnA@mail.gmail.com>
<571788EB.5000707@redhat.com>
<1841929557.52201796.1461160865600.JavaMail.zimbra@redhat.com>
Message-ID: <57178C10.4010804@redhat.com>
forgot to include Romain in CC
On 20.4.2016 16:01, Brad Davis wrote:
> +1 -- it is not only important for Windows to Linux, but also for identifying file read / writes that need to be mounted for cloud deployments to things like OpenShift.
>
> Brad Davis
> Director of FSI Solutions, Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
> ----- Original Message -----
> From: "Marek Novotny" <mnovotny at redhat.com>
> To: "Windup-dev List" <windup-dev at lists.jboss.org>
> Sent: Wednesday, April 20, 2016 9:49:31 AM
> Subject: [windup-dev] Fwd: [WindUp] Regular expression to detect filesystem paths
>
> adding windup-dev ml as this could be interested to Windup community.
>
>
> Romain,
>
> I would go with simplified pattern for every unique occurrence to more
> more general one.
>
> So try to use <or></or> and condition patterns in it.
> Something like the following:
>
> <rule id="filesystem-paths-properties">
> <when>
> <or>
> <filecontent filename="{*}.{extensions}"
> pattern="{filesystem}" />
> <filecontent filename="{*}.{extensions}"
> pattern="{netfilesystem}" />
> <filecontent filename="{*}.{extensions}"
> pattern="page import="{filesystem}" />
> </or>
> </when>
> <perform>
> <hint message="File system properties" effort="1"
> severity="mandatory">
> <message>
> TODO
> </message>
> </hint>
> </perform>
> <where param="extensions">
> <matches pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
> </where>
> <where param="filesystem">
> <matches pattern="(\S:[\\|/])" />
> </where>
> <where param="netfilesystem">
> <matches pattern="(\\\\ntfileserver\)" />
> </where>
> <where param="netfilesystem">
> <matches pattern="" />
> </where>
> </rule>
>
> -------- Forwarded Message --------
> Subject: [WindUp] Regular expression to detect filesystem paths
> Date: Wed, 20 Apr 2016 15:29:03 +0200
> From: Roman Martin Gil <rmarting at redhat.com>
> To: Marek Novotny <mnovotny at redhat.com>
>
>
>
> Hi,
>
> I am very obfuscated to create a rule to identify some filesystem paths
> patterns. I am trying to detect when the code (.java, .properties) have
> the following entries:
>
> * "c:\\"
> * "e:\\"
> * "c:/"
> * "e:/"
> * "\\\\ntfileserver\"
> * "page import="""
>
>
> My first approach is similar to:
>
> <rule id="filesystem-paths-properties">
> <when>
> <filecontent filename="{*}.{extensions}"
> pattern="{filesystem}" />
> </when>
> <perform>
> <hint message="File system properties" effort="1"
> severity="mandatory">
> <message>
> TODO
> </message>
> </hint>
> </perform>
> <where param="extensions">
> <matches pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
> </where>
> <where param="filesystem">
> <matches pattern="((c|e):|[\\])" />
> </where>
> </rule>
>
> However I am detecting cases as "Message: " as a pattern. How could I
> create a rule to identify these cases?
>
> Thank you very much in advance
>
> PD: What is the better mail list to send it?
>
>
--
Marek Novotny
--
Windup team member and Seam Project Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
From ozizka at redhat.com Wed Apr 20 22:58:14 2016
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 21 Apr 2016 04:58:14 +0200
Subject: [windup-dev] Fwd: [WindUp] Regular expression to detect
filesystem paths
In-Reply-To: <57178C10.4010804@redhat.com>
References: <CAHFLeqv9fU1zpp7d1sGsmQru-MgtM_VS1Ut0YzsdnLEuOL9rnA@mail.gmail.com>
<571788EB.5000707@redhat.com>
<1841929557.52201796.1461160865600.JavaMail.zimbra@redhat.com>
<57178C10.4010804@redhat.com>
Message-ID: <571841C6.9070806@redhat.com>
For the cases like "Message: ", i'd suggest to use negative lookbehind:
(?<!\w)[a-z]:[\\\\|/]
Which basically says, make sure there's no word character prior to the
potential drive letter.
Ondra
On 20.4.2016 16:02, Marek Novotny wrote:
> forgot to include Romain in CC
>
> On 20.4.2016 16:01, Brad Davis wrote:
>> +1 -- it is not only important for Windows to Linux, but also for identifying file read / writes that need to be mounted for cloud deployments to things like OpenShift.
>>
>> Brad Davis
>> Director of FSI Solutions, Red Hat Consulting
>> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>>
>> ----- Original Message -----
>> From: "Marek Novotny" <mnovotny at redhat.com>
>> To: "Windup-dev List" <windup-dev at lists.jboss.org>
>> Sent: Wednesday, April 20, 2016 9:49:31 AM
>> Subject: [windup-dev] Fwd: [WindUp] Regular expression to detect filesystem paths
>>
>> adding windup-dev ml as this could be interested to Windup community.
>>
>>
>> Romain,
>>
>> I would go with simplified pattern for every unique occurrence to more
>> more general one.
>>
>> So try to use <or></or> and condition patterns in it.
>> Something like the following:
>>
>> <rule id="filesystem-paths-properties">
>> <when>
>> <or>
>> <filecontent filename="{*}.{extensions}"
>> pattern="{filesystem}" />
>> <filecontent filename="{*}.{extensions}"
>> pattern="{netfilesystem}" />
>> <filecontent filename="{*}.{extensions}"
>> pattern="page import="{filesystem}" />
>> </or>
>> </when>
>> <perform>
>> <hint message="File system properties" effort="1"
>> severity="mandatory">
>> <message>
>> TODO
>> </message>
>> </hint>
>> </perform>
>> <where param="extensions">
>> <matches pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
>> </where>
>> <where param="filesystem">
>> <matches pattern="(\S:[\\|/])" />
>> </where>
>> <where param="netfilesystem">
>> <matches pattern="(\\\\ntfileserver\)" />
>> </where>
>> <where param="netfilesystem">
>> <matches pattern="" />
>> </where>
>> </rule>
>>
>> -------- Forwarded Message --------
>> Subject: [WindUp] Regular expression to detect filesystem paths
>> Date: Wed, 20 Apr 2016 15:29:03 +0200
>> From: Roman Martin Gil <rmarting at redhat.com>
>> To: Marek Novotny <mnovotny at redhat.com>
>>
>>
>>
>> Hi,
>>
>> I am very obfuscated to create a rule to identify some filesystem paths
>> patterns. I am trying to detect when the code (.java, .properties) have
>> the following entries:
>>
>> * "c:\\"
>> * "e:\\"
>> * "c:/"
>> * "e:/"
>> * "\\\\ntfileserver\"
>> * "page import="""
>>
>>
>> My first approach is similar to:
>>
>> <rule id="filesystem-paths-properties">
>> <when>
>> <filecontent filename="{*}.{extensions}"
>> pattern="{filesystem}" />
>> </when>
>> <perform>
>> <hint message="File system properties" effort="1"
>> severity="mandatory">
>> <message>
>> TODO
>> </message>
>> </hint>
>> </perform>
>> <where param="extensions">
>> <matches pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
>> </where>
>> <where param="filesystem">
>> <matches pattern="((c|e):|[\\])" />
>> </where>
>> </rule>
>>
>> However I am detecting cases as "Message: " as a pattern. How could I
>> create a rule to identify these cases?
>>
>> Thank you very much in advance
>>
>> PD: What is the better mail list to send it?
>>
>>
>
From mnovotny at redhat.com Thu Apr 21 03:54:22 2016
From: mnovotny at redhat.com (Marek Novotny)
Date: Thu, 21 Apr 2016 09:54:22 +0200
Subject: [windup-dev] Fwd: [WindUp] Regular expression to detect
filesystem paths
In-Reply-To: <CAHFLequvgS2bOkkfUS_k56fkzHKV7KBs5ghLMzG++VZ4YV=JRQ@mail.gmail.com>
References: <CAHFLeqv9fU1zpp7d1sGsmQru-MgtM_VS1Ut0YzsdnLEuOL9rnA@mail.gmail.com>
<571788EB.5000707@redhat.com>
<1841929557.52201796.1461160865600.JavaMail.zimbra@redhat.com>
<57178C10.4010804@redhat.com> <571841C6.9070806@redhat.com>
<CAHFLequvgS2bOkkfUS_k56fkzHKV7KBs5ghLMzG++VZ4YV=JRQ@mail.gmail.com>
Message-ID: <5718872E.1000003@redhat.com>
Cool, I read your yesterday email and suggested " instead of " and
now I see you made it yourself, great!
On 21.4.2016 09:40, Roman Martin Gil wrote:
> Thanks Ondrej, my latest rule version is working as I want.
>
> Now I create a new rule to identify page import definitions empty (<%@
> page import="" %>, .... this line in WAS is working successfully ? but
> in EAP not (compile error).
>
> <rule id="jsp-empty-imports">
> <when>
> <filecontent filename="{*}.jsp" pattern="import={emptyString}" />
> </when>
> <perform>
> <hint message="Empty imports definition in a jsp" effort="1"
> severity="mandatory">
> <message>
> Empty import definitions in .jsp or .jspf files
> will fail in compilation time. It is needed to
> remove them.
> </message>
> </hint>
> </perform>
> <where param="emptyString">
> <matches pattern="("")" />
> </where>
> </rule>
>
>
> I think that rule is also important in other migrations so WindUp could
> introduce in its global rules. What do you think?
>
> Regards
>
> On Thu, Apr 21, 2016 at 4:58 AM, Ondrej Zizka <ozizka at redhat.com
> <mailto:ozizka at redhat.com>> wrote:
>
> For the cases like "Message: ", i'd suggest to use negative lookbehind:
>
> (?<!\w)[a-z]:[\\\\|/]
>
> Which basically says, make sure there's no word character prior to
> the potential drive letter.
>
> Ondra
>
>
>
> On 20.4.2016 16:02, Marek Novotny wrote:
>
> forgot to include Romain in CC
>
> On 20.4.2016 16:01, Brad Davis wrote:
>
> +1 -- it is not only important for Windows to Linux, but
> also for identifying file read / writes that need to be
> mounted for cloud deployments to things like OpenShift.
>
> Brad Davis
> Director of FSI Solutions, Red Hat Consulting
> Email: bdavis at redhat.com <mailto:bdavis at redhat.com> | c:
> 980.226.7865 <tel:980.226.7865> | http://www.redhat.com
>
> ----- Original Message -----
> From: "Marek Novotny" <mnovotny at redhat.com
> <mailto:mnovotny at redhat.com>>
> To: "Windup-dev List" <windup-dev at lists.jboss.org
> <mailto:windup-dev at lists.jboss.org>>
> Sent: Wednesday, April 20, 2016 9:49:31 AM
> Subject: [windup-dev] Fwd: [WindUp] Regular expression to
> detect filesystem paths
>
> adding windup-dev ml as this could be interested to Windup
> community.
>
>
> Romain,
>
> I would go with simplified pattern for every unique
> occurrence to more
> more general one.
>
> So try to use <or></or> and condition patterns in it.
> Something like the following:
>
> <rule id="filesystem-paths-properties">
> <when>
> <or>
> <filecontent filename="{*}.{extensions}"
> pattern="{filesystem}" />
> <filecontent filename="{*}.{extensions}"
> pattern="{netfilesystem}" />
> <filecontent filename="{*}.{extensions}"
> pattern="page import="{filesystem}" />
> </or>
> </when>
> <perform>
> <hint message="File system properties"
> effort="1"
> severity="mandatory">
> <message>
> TODO
> </message>
> </hint>
> </perform>
> <where param="extensions">
> <matches
> pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
> </where>
> <where param="filesystem">
> <matches pattern="(\S:[\\|/])" />
> </where>
> <where param="netfilesystem">
> <matches pattern="(\\\\ntfileserver\)" />
> </where>
> <where param="netfilesystem">
> <matches pattern="" />
> </where>
> </rule>
>
> -------- Forwarded Message --------
> Subject: [WindUp] Regular expression to detect
> filesystem paths
> Date: Wed, 20 Apr 2016 15:29:03 +0200
> From: Roman Martin Gil <rmarting at redhat.com
> <mailto:rmarting at redhat.com>>
> To: Marek Novotny <mnovotny at redhat.com
> <mailto:mnovotny at redhat.com>>
>
>
>
> Hi,
>
> I am very obfuscated to create a rule to identify some
> filesystem paths
> patterns. I am trying to detect when the code (.java,
> .properties) have
> the following entries:
>
> * "c:\\"
> * "e:\\"
> * "c:/"
> * "e:/"
> * "\\\\ntfileserver\"
> * "page import="""
>
>
> My first approach is similar to:
>
> <rule id="filesystem-paths-properties">
> <when>
> <filecontent filename="{*}.{extensions}"
> pattern="{filesystem}" />
> </when>
> <perform>
> <hint message="File system properties"
> effort="1"
> severity="mandatory">
> <message>
> TODO
> </message>
> </hint>
> </perform>
> <where param="extensions">
> <matches
> pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
> </where>
> <where param="filesystem">
> <matches pattern="((c|e):|[\\])" />
> </where>
> </rule>
>
> However I am detecting cases as "Message: " as a pattern.
> How could I
> create a rule to identify these cases?
>
> Thank you very much in advance
>
> PD: What is the better mail list to send it?
>
>
>
>
>
>
>
> --
>
> Saludos/Best regards
> ______________________________________________________________________
> *Jose Roman Martin Gil *
> /MW Senior Architect/ | +34 605 926 271 | roman.martin at redhat.com
> <mailto:roman.martin at redhat.com>
>
> /**/*Red Hat* Iberia
> C/ Jos? Bardasano Baos, 9, Edif. Gorbea 3, planta 3?D, 28016 Madrid, Spain
> ______________________________________________________________________
>
--
Marek Novotny
--
Windup team member and Seam Project Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
From ozizka at redhat.com Sun Apr 24 17:45:35 2016
From: ozizka at redhat.com (Ondrej Zizka)
Date: Sun, 24 Apr 2016 23:45:35 +0200
Subject: [windup-dev] Fwd: [WindUp] Regular expression to detect
filesystem paths
In-Reply-To: <CAHFLequvgS2bOkkfUS_k56fkzHKV7KBs5ghLMzG++VZ4YV=JRQ@mail.gmail.com>
References: <CAHFLeqv9fU1zpp7d1sGsmQru-MgtM_VS1Ut0YzsdnLEuOL9rnA@mail.gmail.com>
<571788EB.5000707@redhat.com>
<1841929557.52201796.1461160865600.JavaMail.zimbra@redhat.com>
<57178C10.4010804@redhat.com> <571841C6.9070806@redhat.com>
<CAHFLequvgS2bOkkfUS_k56fkzHKV7KBs5ghLMzG++VZ4YV=JRQ@mail.gmail.com>
Message-ID: <571D3E7F.5070507@redhat.com>
Hi Roman,
1) Yes, the rule seems useful, thanks! You can create a PR, or shall I?
2) How about leaving out the <where>:
<filecontent filename="{*}.jsp" pattern="import=""" />
<where> is generally useful if you need to match a regex, or refer to
the value somewhere else in the rule.
Ondra
On 21.4.2016 09:40, Roman Martin Gil wrote:
> Thanks Ondrej, my latest rule version is working as I want.
>
> Now I create a new rule to identify page import definitions empty (<%@
> page import="" %>, .... this line in WAS is working
> successfully ? but in EAP not (compile error).
>
> <rule id="jsp-empty-imports">
> <when>
> <filecontent filename="{*}.jsp" pattern="import={emptyString}" />
> </when>
> <perform>
> <hint message="Empty imports definition in a jsp" effort="1"
> severity="mandatory">
> <message>
> Empty import definitions in .jsp or .jspf
> files will fail in compilation time. It is needed to
> remove them.
> </message>
> </hint>
> </perform>
> <where param="emptyString">
> <matches pattern="("")" />
> </where>
> </rule>
>
>
> I think that rule is also important in other migrations so WindUp
> could introduce in its global rules. What do you think?
>
> Regards
>
> On Thu, Apr 21, 2016 at 4:58 AM, Ondrej Zizka <ozizka at redhat.com
> <mailto:ozizka at redhat.com>> wrote:
>
> For the cases like "Message: ", i'd suggest to use negative
> lookbehind:
>
> (?<!\w)[a-z]:[\\\\|/]
>
> Which basically says, make sure there's no word character prior to
> the potential drive letter.
>
> Ondra
>
>
>
> On 20.4.2016 16:02, Marek Novotny wrote:
>
> forgot to include Romain in CC
>
> On 20.4.2016 16:01, Brad Davis wrote:
>
> +1 -- it is not only important for Windows to Linux, but
> also for identifying file read / writes that need to be
> mounted for cloud deployments to things like OpenShift.
>
> Brad Davis
> Director of FSI Solutions, Red Hat Consulting
> Email: bdavis at redhat.com <mailto:bdavis at redhat.com> | c:
> 980.226.7865 <tel:980.226.7865> | http://www.redhat.com
>
> ----- Original Message -----
> From: "Marek Novotny" <mnovotny at redhat.com
> <mailto:mnovotny at redhat.com>>
> To: "Windup-dev List" <windup-dev at lists.jboss.org
> <mailto:windup-dev at lists.jboss.org>>
> Sent: Wednesday, April 20, 2016 9:49:31 AM
> Subject: [windup-dev] Fwd: [WindUp] Regular expression to
> detect filesystem paths
>
> adding windup-dev ml as this could be interested to Windup
> community.
>
>
> Romain,
>
> I would go with simplified pattern for every unique
> occurrence to more
> more general one.
>
> So try to use <or></or> and condition patterns in it.
> Something like the following:
>
> <rule id="filesystem-paths-properties">
> <when>
> <or>
> <filecontent
> filename="{*}.{extensions}"
> pattern="{filesystem}" />
> <filecontent
> filename="{*}.{extensions}"
> pattern="{netfilesystem}" />
> <filecontent
> filename="{*}.{extensions}"
> pattern="page import="{filesystem}" />
> </or>
> </when>
> <perform>
> <hint message="File system properties"
> effort="1"
> severity="mandatory">
> <message>
> TODO
> </message>
> </hint>
> </perform>
> <where param="extensions">
> <matches
> pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
> </where>
> <where param="filesystem">
> <matches pattern="(\S:[\\|/])" />
> </where>
> <where param="netfilesystem">
> <matches pattern="(\\\\ntfileserver\)" />
> </where>
> <where param="netfilesystem">
> <matches pattern="" />
> </where>
> </rule>
>
> -------- Forwarded Message --------
> Subject: [WindUp] Regular expression to detect
> filesystem paths
> Date: Wed, 20 Apr 2016 15:29:03 +0200
> From: Roman Martin Gil <rmarting at redhat.com
> <mailto:rmarting at redhat.com>>
> To: Marek Novotny <mnovotny at redhat.com
> <mailto:mnovotny at redhat.com>>
>
>
>
> Hi,
>
> I am very obfuscated to create a rule to identify some
> filesystem paths
> patterns. I am trying to detect when the code (.java,
> .properties) have
> the following entries:
>
> * "c:\\"
> * "e:\\"
> * "c:/"
> * "e:/"
> * "\\\\ntfileserver\"
> * "page import="""
>
>
> My first approach is similar to:
>
> <rule id="filesystem-paths-properties">
> <when>
> <filecontent filename="{*}.{extensions}"
> pattern="{filesystem}" />
> </when>
> <perform>
> <hint message="File system properties"
> effort="1"
> severity="mandatory">
> <message>
> TODO
> </message>
> </hint>
> </perform>
> <where param="extensions">
> <matches
> pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
> </where>
> <where param="filesystem">
> <matches pattern="((c|e):|[\\])" />
> </where>
> </rule>
>
> However I am detecting cases as "Message: " as a pattern.
> How could I
> create a rule to identify these cases?
>
> Thank you very much in advance
>
> PD: What is the better mail list to send it?
>
>
>
>
>
>
>
> --
>
> Saludos/Best regards
> ______________________________________________________________________
> *Jose Roman Martin Gil *
> /MW Senior Architect/ | +34 605 926 271 | roman.martin at redhat.com
> <mailto:roman.martin at redhat.com>
>
> //*Red Hat* Iberia
> C/ Jos? Bardasano Baos, 9, Edif. Gorbea 3, planta 3?D, 28016 Madrid, Spain
> ______________________________________________________________________
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20160424/8be68ebd/attachment-0001.html
From mnovotny at redhat.com Mon Apr 25 03:23:28 2016
From: mnovotny at redhat.com (Marek Novotny)
Date: Mon, 25 Apr 2016 09:23:28 +0200
Subject: [windup-dev] Fwd: [WindUp] Regular expression to detect
filesystem paths
In-Reply-To: <571D3E7F.5070507@redhat.com>
References: <CAHFLeqv9fU1zpp7d1sGsmQru-MgtM_VS1Ut0YzsdnLEuOL9rnA@mail.gmail.com>
<571788EB.5000707@redhat.com>
<1841929557.52201796.1461160865600.JavaMail.zimbra@redhat.com>
<57178C10.4010804@redhat.com> <571841C6.9070806@redhat.com>
<CAHFLequvgS2bOkkfUS_k56fkzHKV7KBs5ghLMzG++VZ4YV=JRQ@mail.gmail.com>
<571D3E7F.5070507@redhat.com>
Message-ID: <571DC5F0.2030309@redhat.com>
On 24.4.2016 23:45, Ondrej Zizka wrote:
> Hi Roman,
>
> 1) Yes, the rule seems useful, thanks! You can create a PR, or shall I?
FYI i already created https://issues.jboss.org/browse/WINDUPRULE-150
>
--
Marek Novotny
--
Windup team member and Seam Project Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
From ozizka at redhat.com Tue Apr 26 21:23:10 2016
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 27 Apr 2016 03:23:10 +0200
Subject: [windup-dev] Deployment / run exceptions analysis use case // Fwd:
Re: Java_opts, memory, cannot reset buffer???
In-Reply-To: <CAFa4ssVEJGkTK8An8gY1p+jC92Xp-E9jW7wyzD5S2MpTTo0Nxw@mail.gmail.com>
References: <CAFa4ssVEJGkTK8An8gY1p+jC92Xp-E9jW7wyzD5S2MpTTo0Nxw@mail.gmail.com>
Message-ID: <5720147E.40407@redhat.com>
On the F2F meeting, I suggested to include the deployment / run
exceptions analysis amongst long term goals for Windup.
This is a use case.
Ondra
-------- Forwarded Message --------
Subject: Re: Java_opts, memory, cannot reset buffer???
Date: Tue, 26 Apr 2016 18:04:15 +0200
From: Oscar Arribas <oscar at redhat.com>
To: Qadeer Khan <qkhan at redhat.com>
CC: jboss-migration at redhat.com
Hi Qadeer,
see https://access.redhat.com/solutions/30513
Best regards,
Oscar.
On Tue, Apr 26, 2016 at 5:49 PM, Qadeer Khan <qkhan at redhat.com
<mailto:qkhan at redhat.com>> wrote:
We are getting these error messages during run time on EAP 6.4
server. We recently migrated an application from EAP 5 to EAP 6.4
------------------------------
1. ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/wac-ia].[jsp]]
(http-127.0.0.1/127.0.0.1:8080-4) JBWEB000236: Servlet.service() for
servlet jsp threw exception: javax.servlet.jsp.JspException:
JBWEB004062: Unable to compile class for JSP:
2. JBWEB004061: An error occurred at line: 90 in the generated java
file:
C:\jboss6\standalone\tmp\work\jboss.web\default-host\wac-ia\org\apache\jsp\pages\content\credit_005frisk_005fdecision_005fcontent_jsp.java
The code of method _jspService(HttpServletRequest,
HttpServletResponse) is exceeding the 65535 bytes limit
3. ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]]
(http-127.0.0.1/127.0.0.1:8080-4) JBWEB000313: Exception processing
error page /prepareExceptionOccured.do:
java.lang.IllegalStateException: JBWEB000029: Cannot reset buffer
after response has been committed
-------------------------------
I am not sure if it is related to JAVA_OPTS setting but that's what
we have for JAVA_OPTS
"JAVA_OPTS=-Xms256m -Xmx1024m -XX:MaxPermSize=256m.
We are using servlet version 3.0 and server RAM is 6G.
Appreciate any insight into the problem and any recommendation on
how to resolve it?
Regards
Qadeer Khan - RHCJA,RHCSA
RedHat Consulting - Public Sector
Senior Consultant
Mobile: 703-798-5621
Email: qkhan at redhat.com <mailto:qkhan at redhat.com>
http://www.redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20160427/841b9664/attachment.html
From ozizka at redhat.com Thu Apr 28 02:34:45 2016
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 28 Apr 2016 08:34:45 +0200
Subject: [windup-dev] BOM in central fails to download
Message-ID: <5721AF05.4090608@redhat.com>
Looks like something went wrong:
https://repo.maven.apache.org/maven2/org/jboss/windup/windup-bom/2.5.0.CR3/
https://repo.maven.apache.org/maven2/org/jboss/windup/windup-bom/2.5.0.CR3/windup-bom-2.5.0.CR3.pom
--> 404
This breaks the build...
Ondra
From ozizka at redhat.com Thu Apr 28 03:42:53 2016
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 28 Apr 2016 09:42:53 +0200
Subject: [windup-dev] Lucene CCEx - ClassCastException: class
org.apache.lucene.codecs.lucene40.Lucene40PostingsFormat
Message-ID: <5721BEFD.4070502@redhat.com>
Hi team,
after rebase, I started getting this Lucene exception.
Did we change the version of Lucene used?
Caused by: java.lang.ClassCastException: class
org.apache.lucene.codecs.lucene40.Lucene40PostingsFormat
at java.lang.Class.asSubclass(Class.java:3404)
at
org.apache.lucene.util.SPIClassIterator.next(SPIClassIterator.java:141)
at
org.apache.lucene.util.NamedSPILoader.reload(NamedSPILoader.java:65)
at
org.apache.lucene.util.NamedSPILoader.<init>(NamedSPILoader.java:47)
at
org.apache.lucene.util.NamedSPILoader.<init>(NamedSPILoader.java:37)
at
org.apache.lucene.codecs.PostingsFormat.<clinit>(PostingsFormat.java:44)
... 47 more
From mnovotny at redhat.com Thu Apr 28 03:46:13 2016
From: mnovotny at redhat.com (Marek Novotny)
Date: Thu, 28 Apr 2016 09:46:13 +0200
Subject: [windup-dev] BOM in central fails to download
In-Reply-To: <5721AF05.4090608@redhat.com>
References: <5721AF05.4090608@redhat.com>
Message-ID: <10e65b6b-2784-e6a8-791e-d37058308dd8@redhat.com>
Check your connection or config. I tried to build CR3 and it works just
fine.
((2.5.0.CR3)) mvn clean package
[INFO] Scanning for projects...
Downloading:
https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/windup/windup-bom/2.5.0.CR3/windup-bom-2.5.0.CR3.pom
Downloaded:
https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/windup/windup-bom/2.5.0.CR3/windup-bom-2.5.0.CR3.pom
(13 KB at 7.3 KB/sec)
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building Windup - Distribution Build 2.5.0.CR3
[INFO]
------------------------------------------------------------------------
On 28.4.2016 08:34, Ondrej Zizka wrote:
> Looks like something went wrong:
>
> https://repo.maven.apache.org/maven2/org/jboss/windup/windup-bom/2.5.0.CR3/
> https://repo.maven.apache.org/maven2/org/jboss/windup/windup-bom/2.5.0.CR3/windup-bom-2.5.0.CR3.pom
> --> 404
>
> This breaks the build...
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Marek Novotny
--
Windup team member and Seam Project Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
From mnovotny at redhat.com Thu Apr 28 08:26:30 2016
From: mnovotny at redhat.com (Marek Novotny)
Date: Thu, 28 Apr 2016 14:26:30 +0200
Subject: [windup-dev] Enum and Enum constants as a javaclass condition
Message-ID: <0a4f2de9-dac7-ce05-cf9c-44943a295176@redhat.com>
Windup team,
I am looking for a help/advice how to create Javaclass condition for
usages of Enums and more specifically Enum constants.
It seems that current features supported in
org.jboss.windup.ast.java.data.TypeReferenceLocation is not enough to
recognize Enums outside import declaration.
Am I something overlooking or it is not just implemented - created
https://issues.jboss.org/browse/WINDUP-1002 for the follow up.
--
Marek Novotny
--
Windup team member and Seam Project Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
From jsightle at redhat.com Thu Apr 28 10:16:20 2016
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 28 Apr 2016 10:16:20 -0400
Subject: [windup-dev] Lucene CCEx - ClassCastException: class
org.apache.lucene.codecs.lucene40.Lucene40PostingsFormat
In-Reply-To: <5721BEFD.4070502@redhat.com>
References: <5721BEFD.4070502@redhat.com>
Message-ID: <57221B34.30807@redhat.com>
I don't think so. Perhaps you pulled in a different version while
changing the POMs?
On 04/28/2016 03:42 AM, Ondrej Zizka wrote:
> Hi team,
>
> after rebase, I started getting this Lucene exception.
>
> Did we change the version of Lucene used?
>
>
> Caused by: java.lang.ClassCastException: class
> org.apache.lucene.codecs.lucene40.Lucene40PostingsFormat
> at java.lang.Class.asSubclass(Class.java:3404)
> at
> org.apache.lucene.util.SPIClassIterator.next(SPIClassIterator.java:141)
> at
> org.apache.lucene.util.NamedSPILoader.reload(NamedSPILoader.java:65)
> at
> org.apache.lucene.util.NamedSPILoader.<init>(NamedSPILoader.java:47)
> at
> org.apache.lucene.util.NamedSPILoader.<init>(NamedSPILoader.java:37)
> at
> org.apache.lucene.codecs.PostingsFormat.<clinit>(PostingsFormat.java:44)
> ... 47 more
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Thu Apr 28 11:22:41 2016
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 28 Apr 2016 17:22:41 +0200
Subject: [windup-dev] Lucene CCEx - ClassCastException: class
org.apache.lucene.codecs.lucene40.Lucene40PostingsFormat
In-Reply-To: <57221B34.30807@redhat.com>
References: <5721BEFD.4070502@redhat.com> <57221B34.30807@redhat.com>
Message-ID: <57222AC1.1000108@redhat.com>
The thing is that I made indexer-data produce a jar besides the zip, and
made it a dependency of rules-java-basic-api.
And it seems to somehow collide. I'll try make the indexer-data an addon.
I paused that effort, working on testing now; but I'd like to discuss
that later today if possible
Ondra
On 28.4.2016 16:16, Jess Sightler wrote:
> I don't think so. Perhaps you pulled in a different version while
> changing the POMs?
>
> On 04/28/2016 03:42 AM, Ondrej Zizka wrote:
>> Hi team,
>>
>> after rebase, I started getting this Lucene exception.
>>
>> Did we change the version of Lucene used?
>>
>>
>> Caused by: java.lang.ClassCastException: class
>> org.apache.lucene.codecs.lucene40.Lucene40PostingsFormat
>> at java.lang.Class.asSubclass(Class.java:3404)
>> at
>> org.apache.lucene.util.SPIClassIterator.next(SPIClassIterator.java:141)
>> at
>> org.apache.lucene.util.NamedSPILoader.reload(NamedSPILoader.java:65)
>> at
>> org.apache.lucene.util.NamedSPILoader.<init>(NamedSPILoader.java:47)
>> at
>> org.apache.lucene.util.NamedSPILoader.<init>(NamedSPILoader.java:37)
>> at
>> org.apache.lucene.codecs.PostingsFormat.<clinit>(PostingsFormat.java:44)
>> ... 47 more
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From ozizka at redhat.com Thu Apr 28 11:23:44 2016
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 28 Apr 2016 17:23:44 +0200
Subject: [windup-dev] BOM in central fails to download
In-Reply-To: <10e65b6b-2784-e6a8-791e-d37058308dd8@redhat.com>
References: <5721AF05.4090608@redhat.com>
<10e65b6b-2784-e6a8-791e-d37058308dd8@redhat.com>
Message-ID: <57222B00.2000406@redhat.com>
Works for me too now.
Still, should this be fixed?
https://github.com/windup/windup-rulesets/pull/138 (one way or the
other (Marek's ))
Ondra
On 28.4.2016 09:46, Marek Novotny wrote:
> Check your connection or config. I tried to build CR3 and it works just
> fine.
>
> ((2.5.0.CR3)) mvn clean package
> [INFO] Scanning for projects...
> Downloading:
> https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/windup/windup-bom/2.5.0.CR3/windup-bom-2.5.0.CR3.pom
> Downloaded:
> https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/windup/windup-bom/2.5.0.CR3/windup-bom-2.5.0.CR3.pom
> (13 KB at 7.3 KB/sec)
> [INFO]
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building Windup - Distribution Build 2.5.0.CR3
> [INFO]
> ------------------------------------------------------------------------
>
>
> On 28.4.2016 08:34, Ondrej Zizka wrote:
>> Looks like something went wrong:
>>
>> https://repo.maven.apache.org/maven2/org/jboss/windup/windup-bom/2.5.0.CR3/
>> https://repo.maven.apache.org/maven2/org/jboss/windup/windup-bom/2.5.0.CR3/windup-bom-2.5.0.CR3.pom
>> --> 404
>>
>> This breaks the build...
>> Ondra
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>
From ozizka at redhat.com Thu Apr 28 11:28:51 2016
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 28 Apr 2016 17:28:51 +0200
Subject: [windup-dev] BOM in central fails to download
In-Reply-To: <57222B00.2000406@redhat.com>
References: <5721AF05.4090608@redhat.com>
<10e65b6b-2784-e6a8-791e-d37058308dd8@redhat.com>
<57222B00.2000406@redhat.com>
Message-ID: <57222C33.9080602@redhat.com>
Oops, please ignore, I have read the other thread now.
Ondra
On 28.4.2016 17:23, Ondrej Zizka wrote:
> Works for me too now.
>
> Still, should this be fixed?
> https://github.com/windup/windup-rulesets/pull/138 (one way or the
> other (Marek's ))
>
> Ondra
>
> On 28.4.2016 09:46, Marek Novotny wrote:
>> Check your connection or config. I tried to build CR3 and it works just
>> fine.
>>
>> ((2.5.0.CR3)) mvn clean package
>> [INFO] Scanning for projects...
>> Downloading:
>> https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/windup/windup-bom/2.5.0.CR3/windup-bom-2.5.0.CR3.pom
>> Downloaded:
>> https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/windup/windup-bom/2.5.0.CR3/windup-bom-2.5.0.CR3.pom
>> (13 KB at 7.3 KB/sec)
>> [INFO]
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building Windup - Distribution Build 2.5.0.CR3
>> [INFO]
>> ------------------------------------------------------------------------
>>
>>
>> On 28.4.2016 08:34, Ondrej Zizka wrote:
>>> Looks like something went wrong:
>>>
>>> https://repo.maven.apache.org/maven2/org/jboss/windup/windup-bom/2.5.0.CR3/
>>> https://repo.maven.apache.org/maven2/org/jboss/windup/windup-bom/2.5.0.CR3/windup-bom-2.5.0.CR3.pom
>>> --> 404
>>>
>>> This breaks the build...
>>> Ondra
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From jsightle at redhat.com Thu Apr 28 11:49:21 2016
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 28 Apr 2016 11:49:21 -0400
Subject: [windup-dev] Lucene CCEx - ClassCastException: class
org.apache.lucene.codecs.lucene40.Lucene40PostingsFormat
In-Reply-To: <57222AC1.1000108@redhat.com>
References: <5721BEFD.4070502@redhat.com> <57221B34.30807@redhat.com>
<57222AC1.1000108@redhat.com>
Message-ID: <57223101.8050908@redhat.com>
Sure, we can discuss it today if you'd like.
Why would you have made it a jar? I'm a little confused about that?
On 04/28/2016 11:22 AM, Ondrej Zizka wrote:
> The thing is that I made indexer-data produce a jar besides the zip, and
> made it a dependency of rules-java-basic-api.
> And it seems to somehow collide. I'll try make the indexer-data an addon.
>
> I paused that effort, working on testing now; but I'd like to discuss
> that later today if possible
>
> Ondra
>
>
>
> On 28.4.2016 16:16, Jess Sightler wrote:
>> I don't think so. Perhaps you pulled in a different version while
>> changing the POMs?
>>
>> On 04/28/2016 03:42 AM, Ondrej Zizka wrote:
>>> Hi team,
>>>
>>> after rebase, I started getting this Lucene exception.
>>>
>>> Did we change the version of Lucene used?
>>>
>>>
>>> Caused by: java.lang.ClassCastException: class
>>> org.apache.lucene.codecs.lucene40.Lucene40PostingsFormat
>>> at java.lang.Class.asSubclass(Class.java:3404)
>>> at
>>> org.apache.lucene.util.SPIClassIterator.next(SPIClassIterator.java:141)
>>> at
>>> org.apache.lucene.util.NamedSPILoader.reload(NamedSPILoader.java:65)
>>> at
>>> org.apache.lucene.util.NamedSPILoader.<init>(NamedSPILoader.java:47)
>>> at
>>> org.apache.lucene.util.NamedSPILoader.<init>(NamedSPILoader.java:37)
>>> at
>>> org.apache.lucene.codecs.PostingsFormat.<clinit>(PostingsFormat.java:44)
>>> ... 47 more
>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From rgreatho at redhat.com Thu Apr 28 13:15:46 2016
From: rgreatho at redhat.com (Robb Greathouse)
Date: Thu, 28 Apr 2016 11:15:46 -0600
Subject: [windup-dev] Deployment / run exceptions analysis use case //
Fwd: Re: Java_opts, memory, cannot reset buffer???
In-Reply-To: <5720147E.40407@redhat.com>
References: <CAFa4ssVEJGkTK8An8gY1p+jC92Xp-E9jW7wyzD5S2MpTTo0Nxw@mail.gmail.com>
<5720147E.40407@redhat.com>
Message-ID: <CAJ=9MxeTT4nmLPG17Sn5dCtf_Cn5hiQxOU3JT+ah9B88TbaANg@mail.gmail.com>
I agree. In the case of WebSphere there are deployment parameters that are
specific to WebSphere. Some of them don't break a deployment to JBoss; but
the expected behavior is not enabled.
On Tue, Apr 26, 2016 at 7:23 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
> On the F2F meeting, I suggested to include the deployment / run exceptions
> analysis amongst long term goals for Windup.
> This is a use case.
>
> Ondra
>
>
> -------- Forwarded Message --------
> Subject: Re: Java_opts, memory, cannot reset buffer???
> Date: Tue, 26 Apr 2016 18:04:15 +0200
> From: Oscar Arribas <oscar at redhat.com> <oscar at redhat.com>
> To: Qadeer Khan <qkhan at redhat.com> <qkhan at redhat.com>
> CC: jboss-migration at redhat.com
>
>
> Hi Qadeer,
>
> see https://access.redhat.com/solutions/30513
>
> Best regards,
> Oscar.
>
>
>
> On Tue, Apr 26, 2016 at 5:49 PM, Qadeer Khan <qkhan at redhat.com> wrote:
>
>> We are getting these error messages during run time on EAP 6.4 server. We
>> recently migrated an application from EAP 5 to EAP 6.4
>>
>> ------------------------------
>> 1. ERROR
>> [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/wac-ia].[jsp]]
>> (http-127.0.0.1/127.0.0.1:8080-4) JBWEB000236: Servlet.service() for
>> servlet jsp threw exception: javax.servlet.jsp.JspException: JBWEB004062:
>> Unable to compile class for JSP:
>>
>> 2. JBWEB004061: An error occurred at line: 90 in the generated java file:
>> C:\jboss6\standalone\tmp\work\jboss.web\default-host\wac-ia\org\apache\jsp\pages\content\credit_005frisk_005fdecision_005fcontent_jsp.java
>> The code of method _jspService(HttpServletRequest, HttpServletResponse)
>> is exceeding the 65535 bytes limit
>>
>>
>> 3. ERROR
>> [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]]
>> (http-127.0.0.1/127.0.0.1:8080-4) JBWEB000313: Exception processing
>> error page /prepareExceptionOccured.do: java.lang.IllegalStateException:
>> JBWEB000029: Cannot reset buffer after response has been committed
>> -------------------------------
>>
>>
>> I am not sure if it is related to JAVA_OPTS setting but that's what we
>> have for JAVA_OPTS
>>
>> "JAVA_OPTS=-Xms256m -Xmx1024m -XX:MaxPermSize=256m.
>>
>> We are using servlet version 3.0 and server RAM is 6G.
>>
>> Appreciate any insight into the problem and any recommendation on how to
>> resolve it?
>>
>> Regards
>>
>> Qadeer Khan - RHCJA,RHCSA
>> RedHat Consulting - Public Sector
>> Senior Consultant
>> Mobile: 703-798-5621
>> Email: qkhan at redhat.com
>> http://www.redhat.com
>>
>>
>>
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Robb Greathouse
Middleware BU
505-507-4906
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20160428/82acae16/attachment.html
From jsightle at redhat.com Thu Apr 28 17:23:54 2016
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 28 Apr 2016 17:23:54 -0400
Subject: [windup-dev] New fernflower fork project
Message-ID: <57227F6A.5050706@redhat.com>
I have created a new project within Windup for maintaining a fork of
Fernflower with Java 7 compatibility and a Maven pom. Maybe we can start
releasing and keeping this up to date separately from windup core?
It is here:
https://github.com/windup/windup-fernflower
I think we can switch Windup to use this as part of 2.6.0, if noone
objects to that.
From rgreatho at redhat.com Thu Apr 28 17:37:46 2016
From: rgreatho at redhat.com (Robb Greathouse)
Date: Thu, 28 Apr 2016 15:37:46 -0600
Subject: [windup-dev] New fernflower fork project
In-Reply-To: <57227F6A.5050706@redhat.com>
References: <57227F6A.5050706@redhat.com>
Message-ID: <CAJ=9Mxc=j_vS7ECM916RRu=rrviDgE3zwxUQH1oOWkg1W6CJjQ@mail.gmail.com>
Good solution.
On Thu, Apr 28, 2016 at 3:23 PM, Jess Sightler <jsightle at redhat.com> wrote:
> I have created a new project within Windup for maintaining a fork of
> Fernflower with Java 7 compatibility and a Maven pom. Maybe we can start
> releasing and keeping this up to date separately from windup core?
>
> It is here:
> https://github.com/windup/windup-fernflower
>
> I think we can switch Windup to use this as part of 2.6.0, if noone
> objects to that.
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Robb Greathouse
Middleware BU
505-507-4906
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20160428/7c7a8807/attachment.html
From mnovotny at redhat.com Fri Apr 29 03:58:36 2016
From: mnovotny at redhat.com (Marek Novotny)
Date: Fri, 29 Apr 2016 09:58:36 +0200
Subject: [windup-dev] New fernflower fork project
In-Reply-To: <57227F6A.5050706@redhat.com>
References: <57227F6A.5050706@redhat.com>
Message-ID: <79cb0635-402b-c2f5-2dc6-76490d08b219@redhat.com>
Just to confirm for myself, that is based on what we have here
https://github.com/windup/windup/tree/master/forks/fernflower, right?
On 28.4.2016 23:23, Jess Sightler wrote:
> I have created a new project within Windup for maintaining a fork of
> Fernflower with Java 7 compatibility and a Maven pom. Maybe we can start
> releasing and keeping this up to date separately from windup core?
>
> It is here:
> https://github.com/windup/windup-fernflower
>
> I think we can switch Windup to use this as part of 2.6.0, if noone
> objects to that.
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Marek Novotny
--
Windup team member
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
From jsightle at redhat.com Fri Apr 29 09:30:47 2016
From: jsightle at redhat.com (Jess Sightler)
Date: Fri, 29 Apr 2016 09:30:47 -0400
Subject: [windup-dev] New fernflower fork project
In-Reply-To: <79cb0635-402b-c2f5-2dc6-76490d08b219@redhat.com>
References: <57227F6A.5050706@redhat.com>
<79cb0635-402b-c2f5-2dc6-76490d08b219@redhat.com>
Message-ID: <57236207.1060305@redhat.com>
Sort of. The code is all directly from the upstream repo (with history).
The pom is a slightly modified version of the one we have in
windup/forks/fernflower.
On 04/29/2016 03:58 AM, Marek Novotny wrote:
> Just to confirm for myself, that is based on what we have here
> https://github.com/windup/windup/tree/master/forks/fernflower, right?
>
> On 28.4.2016 23:23, Jess Sightler wrote:
>> I have created a new project within Windup for maintaining a fork of
>> Fernflower with Java 7 compatibility and a Maven pom. Maybe we can start
>> releasing and keeping this up to date separately from windup core?
>>
>> It is here:
>> https://github.com/windup/windup-fernflower
>>
>> I think we can switch Windup to use this as part of 2.6.0, if noone
>> objects to that.
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>