From ozizka at redhat.com  Thu Oct  2 06:51:31 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 02 Oct 2014 12:51:31 +0200
Subject: [windup-dev] JARchitect - Tattletale-like jar analysis
Message-ID: <542D2E33.1090901@redhat.com>

Sharing for inspiration.

http://www.jarchitect.com/SampleReports/WildFly/JArchitectReport.html#Main

Ondra

From bdavis at redhat.com  Thu Oct  2 08:08:26 2014
From: bdavis at redhat.com (Brad Davis)
Date: Thu, 2 Oct 2014 08:08:26 -0400 (EDT)
Subject: [windup-dev] JARchitect - Tattletale-like jar analysis
In-Reply-To: <542D2E33.1090901@redhat.com>
References: <542D2E33.1090901@redhat.com>
Message-ID: <8546F692-D689-49AB-9895-3F6736A58449@redhat.com>

There is also a platform by sonatype that scans apps and reports on vulnerabilities and open source licenses. 

http://www.sonatype.com/take-a-tour/clm-tour

It'd be nice to offer this functionality in the future. 

Brad Davis
Red Hat Consulting
Email: bdavis at redhat.com | c:980.226.7865 |http://www.redhat.com 

> On Oct 2, 2014, at 6:51 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
> 
> Sharing for inspiration.
> 
> http://www.jarchitect.com/SampleReports/WildFly/JArchitectReport.html#Main
> 
> Ondra
> _______________________________________________
> 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/20141002/507ebe28/attachment.html 

From jsightle at redhat.com  Thu Oct  2 13:44:56 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 02 Oct 2014 13:44:56 -0400
Subject: [windup-dev] Windup 2.0.0.Beta1 release
Message-ID: <542D8F18.803@redhat.com>

The downloadable offline .zip is here:
http://repository.jboss.org/nexus/content/groups/public/org/jboss/windup/windup-distribution/2.0.0.Beta1/windup-distribution-2.0.0.Beta1-offline.zip

The rest of the artifacts are here:
http://repository.jboss.org/nexus/content/groups/public/org/jboss/windup/


Example usage:

unzip windup-distribution-2.0.0.Beta1-offline.zip
cd windup-distribution-2.0.0.Beta1/bin
./windup

At the prompt:
windup-migrate-app --input 
/home/jsightler/project/migration/software/windup/test-files/src_example 
--output /tmp/Windup/beta1/


For further usage instructions, execute:
"man windup-migrate-app"



From sgilda at redhat.com  Thu Oct  2 13:49:46 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 02 Oct 2014 13:49:46 -0400
Subject: [windup-dev] Windup 2.0.0.Beta1 release
In-Reply-To: <542D8F18.803@redhat.com>
References: <542D8F18.803@redhat.com>
Message-ID: <542D903A.5030208@redhat.com>

I assume this will replace the instructions here: 
https://github.com/windup/windup/wiki/Execute-Windup ?

Do we want to keep the old instructions for developers and testing purposes?

On 10/02/2014 01:44 PM, Jess Sightler wrote:
> The downloadable offline .zip is here:
> http://repository.jboss.org/nexus/content/groups/public/org/jboss/windup/windup-distribution/2.0.0.Beta1/windup-distribution-2.0.0.Beta1-offline.zip
>
> The rest of the artifacts are here:
> http://repository.jboss.org/nexus/content/groups/public/org/jboss/windup/
>
>
> Example usage:
>
> unzip windup-distribution-2.0.0.Beta1-offline.zip
> cd windup-distribution-2.0.0.Beta1/bin
> ./windup
>
> At the prompt:
> windup-migrate-app --input
> /home/jsightler/project/migration/software/windup/test-files/src_example
> --output /tmp/Windup/beta1/
>
>
> For further usage instructions, execute:
> "man windup-migrate-app"
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev


From jsightle at redhat.com  Thu Oct  2 14:05:53 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 02 Oct 2014 14:05:53 -0400
Subject: [windup-dev] Windup 2.0.0.Beta1 release
In-Reply-To: <542D903A.5030208@redhat.com>
References: <542D8F18.803@redhat.com> <542D903A.5030208@redhat.com>
Message-ID: <542D9401.8000401@redhat.com>

Do you think it would be better to have them download it in those 
instructions?

In either case, those do need to be updated. Currently building from 
source does generate an offline distribution that is easier to use than 
those instructions indicate. It's built under dist/target/ at the moment.

On 10/02/2014 01:49 PM, Sande Gilda wrote:
> I assume this will replace the instructions here:
> https://github.com/windup/windup/wiki/Execute-Windup ?
>
> Do we want to keep the old instructions for developers and testing purposes?
>
> On 10/02/2014 01:44 PM, Jess Sightler wrote:
>> The downloadable offline .zip is here:
>> http://repository.jboss.org/nexus/content/groups/public/org/jboss/windup/windup-distribution/2.0.0.Beta1/windup-distribution-2.0.0.Beta1-offline.zip
>>
>> The rest of the artifacts are here:
>> http://repository.jboss.org/nexus/content/groups/public/org/jboss/windup/
>>
>>
>> Example usage:
>>
>> unzip windup-distribution-2.0.0.Beta1-offline.zip
>> cd windup-distribution-2.0.0.Beta1/bin
>> ./windup
>>
>> At the prompt:
>> windup-migrate-app --input
>> /home/jsightler/project/migration/software/windup/test-files/src_example
>> --output /tmp/Windup/beta1/
>>
>>
>> For further usage instructions, execute:
>> "man windup-migrate-app"
>>
>>
>> _______________________________________________
>> 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 lincolnbaxter at gmail.com  Fri Oct  3 14:10:59 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 3 Oct 2014 11:10:59 -0700
Subject: [windup-dev] JARchitect - Tattletale-like jar analysis
In-Reply-To: <8546F692-D689-49AB-9895-3F6736A58449@redhat.com>
References: <542D2E33.1090901@redhat.com>
	<8546F692-D689-49AB-9895-3F6736A58449@redhat.com>
Message-ID: <CAEp_U4EA-9Cwownr76WX9BNQOtSgU4EnV861LQe3NuZ1zL-Lvw@mail.gmail.com>

We have our own such functionality provided by the Red Hat "Victims"
project. I'm sure we could re-use functionality from that, too:
http://github.com/victims

On Thu, Oct 2, 2014 at 5:08 AM, Brad Davis <bdavis at redhat.com> wrote:

> There is also a platform by sonatype that scans apps and reports on
> vulnerabilities and open source licenses.
>
> http://www.sonatype.com/take-a-tour/clm-tour
>
> It'd be nice to offer this functionality in the future.
>
> Brad Davis
> Red Hat Consulting
> Email: bdavis at redhat.com | c:980.226.7865 |http://www.redhat.com
>
> On Oct 2, 2014, at 6:51 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
>
> Sharing for inspiration.
>
> http://www.jarchitect.com/SampleReports/WildFly/JArchitectReport.html#Main
>
> 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
>



-- 
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/20141003/fca75c38/attachment.html 

From bgeorges at redhat.com  Tue Oct  7 03:37:05 2014
From: bgeorges at redhat.com (Bruno Georges)
Date: Tue, 7 Oct 2014 03:37:05 -0400 (EDT)
Subject: [windup-dev] JARchitect - Tattletale-like jar analysis
In-Reply-To: <CAEp_U4EA-9Cwownr76WX9BNQOtSgU4EnV861LQe3NuZ1zL-Lvw@mail.gmail.com>
References: <542D2E33.1090901@redhat.com>
	<8546F692-D689-49AB-9895-3F6736A58449@redhat.com>
	<CAEp_U4EA-9Cwownr76WX9BNQOtSgU4EnV861LQe3NuZ1zL-Lvw@mail.gmail.com>
Message-ID: <DA743602-6917-4996-B268-D4F20CE92079@redhat.com>

I believe there is also a plugin from the SRT team that does static code analysis. It would be a nice value add during a migration. Certifying ones code to be "safe"

Bruno. 

Sent from my iPhone

> On 4 Oct 2014, at 07:11, Lincoln Baxter, III <lincolnbaxter at gmail.com> wrote:
> 
> We have our own such functionality provided by the Red Hat "Victims" project. I'm sure we could re-use functionality from that, too: http://github.com/victims 
> 
>> On Thu, Oct 2, 2014 at 5:08 AM, Brad Davis <bdavis at redhat.com> wrote:
>> There is also a platform by sonatype that scans apps and reports on vulnerabilities and open source licenses. 
>> 
>> http://www.sonatype.com/take-a-tour/clm-tour
>> 
>> It'd be nice to offer this functionality in the future. 
>> 
>> Brad Davis
>> Red Hat Consulting
>> Email: bdavis at redhat.com | c:980.226.7865 |http://www.redhat.com 
>> 
>>> On Oct 2, 2014, at 6:51 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
>>> 
>>> Sharing for inspiration.
>>> 
>>> http://www.jarchitect.com/SampleReports/WildFly/JArchitectReport.html#Main
>>> 
>>> 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
> 
> 
> 
> -- 
> 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/20141007/80eac03d/attachment.html 

From robb.greathouse at redhat.com  Tue Oct  7 12:53:50 2014
From: robb.greathouse at redhat.com (Robb Greathouse)
Date: Tue, 7 Oct 2014 12:53:50 -0400 (EDT)
Subject: [windup-dev] JARchitect - Tattletale-like jar analysis
In-Reply-To: <DA743602-6917-4996-B268-D4F20CE92079@redhat.com>
References: <542D2E33.1090901@redhat.com>
	<8546F692-D689-49AB-9895-3F6736A58449@redhat.com>
	<CAEp_U4EA-9Cwownr76WX9BNQOtSgU4EnV861LQe3NuZ1zL-Lvw@mail.gmail.com>
	<DA743602-6917-4996-B268-D4F20CE92079@redhat.com>
Message-ID: <1406794520.5296682.1412700830671.JavaMail.zimbra@redhat.com>

We decided to build Windup 2.0 with/on Furnace in part to make 3rd party plugins possible. This will allow us to wrap third party apps and have them interact with Windup or other 3rd party apps. 

Robb Greathouse 
Chief Evangelist 
Middleware Business Unit 
JBoss, a Division of Red Hat 
cellphone 505-507-4906 

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

> I believe there is also a plugin from the SRT team that does static code
> analysis. It would be a nice value add during a migration. Certifying ones
> code to be "safe"

> Bruno.

> Sent from my iPhone

> On 4 Oct 2014, at 07:11, Lincoln Baxter, III < lincolnbaxter at gmail.com >
> wrote:

> > We have our own such functionality provided by the Red Hat "Victims"
> > project.
> > I'm sure we could re-use functionality from that, too:
> > http://github.com/victims
> 

> > On Thu, Oct 2, 2014 at 5:08 AM, Brad Davis < bdavis at redhat.com > wrote:
> 

> > > There is also a platform by sonatype that scans apps and reports on
> > > vulnerabilities and open source licenses.
> > 
> 

> > > http://www.sonatype.com/take-a-tour/clm-tour
> > 
> 

> > > It'd be nice to offer this functionality in the future.
> > 
> 

> > > Brad Davis
> > 
> 
> > > Red Hat Consulting
> > 
> 
> > > Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
> > 
> 

> > > On Oct 2, 2014, at 6:51 AM, Ondrej Zizka < ozizka at redhat.com > wrote:
> > 
> 

> > > > Sharing for inspiration.
> > > 
> > 
> 

> > > > http://www.jarchitect.com/SampleReports/WildFly/JArchitectReport.html#Main
> > > 
> > 
> 

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

> > --
> 
> > 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/20141007/42257e2f/attachment.html 

From lincolnbaxter at gmail.com  Wed Oct  8 10:56:52 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 8 Oct 2014 10:56:52 -0400
Subject: [windup-dev] Windup Meeting Minutes - 2014-10-08
Message-ID: <CAEp_U4HqGS+sC5Sy+vP7oCsu8rkyrawA21EZ48jwmZ=P+t5-Ew@mail.gmail.com>

Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-10-08-14.15.html

Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-10-08-14.15.txt

Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-10-08-14.15.log.html

Meeting summary
---------------
* Agenda  (lincolnthree, 14:16:00)

* Status Reports  (lincolnthree, 14:18:10)
  * I worked on the following JIRAs last week  (jsightler, 14:19:26)
  * WINDUP-290 - Made the toString() on frame instances return a
    meaningful result containing the properties of the frame (instead of
    just a numeric id)  (jsightler, 14:20:00)
  * WINDUP-308 - Cleaned up some formatting of the informational panel
    in the source report template  (jsightler, 14:20:27)
  * WINDUP-318 - Made procyon use explicit imports instead of wildcards
    (this actually makes a lot of the scanning rules work better)
    (jsightler, 14:20:59)
  * WINDUP-323 - Added a bunch of toString methods to rules themselves
    to make printing out a rule clearer  (jsightler, 14:21:22)
  * I have also worked on a JIRA from Robb that was causing windup to
    crash on some soa examples and some other miscellaneous things (eg,
    WINDUP-131)  (jsightler, 14:21:57)
  * Beta1 release testing  (ozizka, 14:22:46)
  * Made CI work  (ozizka, 14:22:46)
  * Created demo videos  (ozizka, 14:22:46)
  * Rebased old PRs, fixing to conform the reviewers comments  (ozizka,
    14:22:46)
  * Was at JavaOne last week, so not much to report. Spent a lot of time
    last 2 days getting caught up on emails and expense reports.
    (lincolnthree, 14:25:53)
  * Reviewed some PRs (and incorrectly merged one)  (lincolnthree,
    14:26:07)
  * Had a few meetings already with the BU about future plannnig (next
    topic)  (lincolnthree, 14:26:46)
  * Also spent a while preparing information for Tobias and Robb to
    present to Craig  (lincolnthree, 14:27:16)
  * The remainder of this week, I will be working on some forge issues
    and trying to catch up with windup PRs (and doing anything else as
    needed)  (lincolnthree, 14:28:09)
  * George is on vacation for 2 or 3 weeks, so I will be covering for
    him on Forge, which will make this.. interesting.  (lincolnthree,
    14:28:35)
  * I'm also taking PTO every friday for the rest of the year, plus two
    weeks (one at thanksgiving time in november, and then one for
    christmas and the holiday shutdown)  (lincolnthree, 14:29:15)
  * LINK: https://home.corp.redhat.com/node/68087   (sgilda, 14:33:57)

* Project Goals and Timeline  (lincolnthree, 14:36:58)
  * Shooting for a February public release  (lincolnthree, 14:39:00)
  * Between now and then, we'll be releasing probably once weekly, but
    more if required (there is a release script we can use to do that
    efficiently)  (lincolnthree, 14:39:05)
  * We will be beginning limited internal trials of Windup2 with Red Hat
    consulting in the next week or so. (We'll all get on a hangout and
    give a virtual training session and lab, with breakouts to help
    individual people as needed.)  (lincolnthree, 14:40:00)


-- 
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/20141008/b616aef0/attachment-0001.html 

From ozizka at redhat.com  Wed Oct  8 19:11:09 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 09 Oct 2014 01:11:09 +0200
Subject: [windup-dev] Demo videos
Message-ID: <5435C48D.6060305@redhat.com>

Hi all,

two new videos about Windup:
1) Clone and build Windup, download and install Forge, install Windup 
addons and run in Forge
2) Clone and build Windup, unzip and run from the dist archive.

Both linked at my blog:
https://developer.jboss.org/people/ozizka/blog

Later I plan something on rules authoring.

Regards,
Ondra

From ozizka at redhat.com  Thu Oct  9 09:25:20 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 09 Oct 2014 15:25:20 +0200
Subject: [windup-dev] Travis - PR auto-testing
Message-ID: <54368CC0.1070007@redhat.com>

Hi,

I wanted to do something with the fact that some PR's fail, and it's 
tedious to test each manually, and ineffective to kill one's machine for 
an hour with the testsuite.

Before installing Lightning, I gave Travis a try:
https://travis-ci.org/profile/windup

It needs a config file in the project's root.
Let's see how it works.

Ondra


From ozizka at redhat.com  Mon Oct 13 04:50:31 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 13 Oct 2014 10:50:31 +0200
Subject: [windup-dev] Travis CI?
Message-ID: <543B9257.3050901@redhat.com>

Hi all,

just to let you know - Travis is too limited in free version.
Now that we have working CI with OS1, I guess we don't need it, correct?

Two questions:

1) Shall we have a test profile which would run a subset of tests? Some 
kind of smoke tests. That could run in Travis.

2) When trying to make Travis build faster, I've hit this when skipping 
priming build..

     Happens in org.jboss.windup.rules.xml.XMLTransformationTest. Can't 
reproduce locally, not necessary do deal with it, just curious what 
could cause it - any idea?


Ondra


Downloaded: 
https://oss.sonatype.org/content/repositories/releases/org/codehaus/groovy/groovy-all/2.3.1/groovy-all-2.3.1.jar 
(7074 KB at 6035.6 KB/sec)

java.io.FileNotFoundException: Source 
'/home/travis/build/OndraZizka/windup/rules-xml/../config-groovy/target/classes' 
does not exist

at org.jboss.forge.furnace.impl.util.Files.copyFile(Files.java:206)

at 
org.jboss.forge.furnace.impl.util.Files.copyFileToDirectory(Files.java:175)

at 
org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl$1.call(AddonRepositoryImpl.java:146)

at 
org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl$1.call(AddonRepositoryImpl.java:122)

at 
org.jboss.forge.furnace.impl.LockManagerImpl.performLocked(LockManagerImpl.java:48)

at 
org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl.deploy(AddonRepositoryImpl.java:121)

at 
org.jboss.forge.furnace.manager.impl.request.DeployRequestImpl.deploy(DeployRequestImpl.java:72)

at 
org.jboss.forge.furnace.manager.impl.request.DeployRequestImpl$1.call(DeployRequestImpl.java:49)

at 
org.jboss.forge.furnace.impl.LockManagerImpl.performLocked(LockManagerImpl.java:48)

at 
org.jboss.forge.furnace.manager.impl.request.DeployRequestImpl.execute(DeployRequestImpl.java:44)

at 
org.jboss.forge.furnace.manager.impl.request.AbstractAddonActionRequest.perform(AbstractAddonActionRequest.java:57)

at 
org.jboss.forge.furnace.manager.impl.request.InstallRequestImpl.perform(InstallRequestImpl.java:39)

at 
org.jboss.forge.arquillian.ForgeDeployableContainer.deploy(ForgeDeployableContainer.java:114)

at 
org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)

...

From ozizka at redhat.com  Tue Oct 14 11:55:17 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Tue, 14 Oct 2014 17:55:17 +0200
Subject: [windup-dev] Windows Issues
Message-ID: <543D4765.6000302@redhat.com>

Hi,

I've tried on Windows 7 64bit, Oracle JDK 1.7.0_67.

The tests fail with WINDUP-335 
<https://issues.jboss.org/browse/WINDUP-335> and WINDUP-332 
<https://issues.jboss.org/browse/WINDUP-332> .
The run against Tim's EAR get stuck on Decompilation for about 8 hours, 
seems it's in an endless loop. WINDUP-337 
<https://issues.jboss.org/browse/WINDUP-337>


Is Windows a priority? Do we have estimation on what portion of users 
will run on Windows?

Ondra


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

From bdavis at redhat.com  Tue Oct 14 13:42:09 2014
From: bdavis at redhat.com (Brad Davis)
Date: Tue, 14 Oct 2014 13:42:09 -0400 (EDT)
Subject: [windup-dev] Windows Issues
In-Reply-To: <543D4765.6000302@redhat.com>
References: <543D4765.6000302@redhat.com>
Message-ID: <1218849334.44405190.1413308529628.JavaMail.zimbra@redhat.com>

I think we could maybe create the decompiler as a runnable, and interrupt the thread with a timeout if the decompiler takes more than a minute for a class, which should be plenty of time.  We should log this, though, to make sure they are aware that one of the classes did not successfully decompile.

Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com 


----- Original Message -----
From: "Ondrej Zizka" <ozizka at redhat.com>
To: "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Tuesday, October 14, 2014 11:55:17 AM
Subject: [windup-dev] Windows Issues

Hi, 

I've tried on Windows 7 64bit, Oracle JDK 1.7.0_67. 

The tests fail with WINDUP-335 and WINDUP-332 . 
The run against Tim's EAR get stuck on Decompilation for about 8 hours, seems it's in an endless loop. WINDUP-337 


Is Windows a priority? Do we have estimation on what portion of users will run on Windows? 

Ondra 



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

From lincolnbaxter at gmail.com  Tue Oct 14 14:52:26 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 14 Oct 2014 14:52:26 -0400
Subject: [windup-dev] Windows Issues
In-Reply-To: <1218849334.44405190.1413308529628.JavaMail.zimbra@redhat.com>
References: <543D4765.6000302@redhat.com>
	<1218849334.44405190.1413308529628.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4Gh8paei0vbu8E8ggP=D=5oduCjYnW1KB3csQLk0KJf+A@mail.gmail.com>

In theory, this is a good idea, we probably do want to limit the amount of
time spent on each class.

However, simply running decompilation in a separate thread will likely not
allow us to interrupt the thread. We'll need to figure out where Procyon is
running, and if it actually responds to Thread.interrupt() (I'm betting it
doesn't.) (And how to make sure that it does, which will likely take some
extension or modification of Procyon itself.)

This is definitely something to look in to over the next few weeks/months
as we harden this first version of the tool.

On Tue, Oct 14, 2014 at 1:42 PM, Brad Davis <bdavis at redhat.com> wrote:

> I think we could maybe create the decompiler as a runnable, and interrupt
> the thread with a timeout if the decompiler takes more than a minute for a
> class, which should be plenty of time.  We should log this, though, to make
> sure they are aware that one of the classes did not successfully decompile.
>
> Brad Davis
> Senior Manager, Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Ondrej Zizka" <ozizka at redhat.com>
> To: "Windup-dev List" <windup-dev at lists.jboss.org>
> Sent: Tuesday, October 14, 2014 11:55:17 AM
> Subject: [windup-dev] Windows Issues
>
> Hi,
>
> I've tried on Windows 7 64bit, Oracle JDK 1.7.0_67.
>
> The tests fail with WINDUP-335 and WINDUP-332 .
> The run against Tim's EAR get stuck on Decompilation for about 8 hours,
> seems it's in an endless loop. WINDUP-337
>
>
> Is Windows a priority? Do we have estimation on what portion of users will
> run on Windows?
>
> 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
>



-- 
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/20141014/13a5e2d5/attachment.html 

From jsightle at redhat.com  Tue Oct 14 14:53:42 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Tue, 14 Oct 2014 14:53:42 -0400
Subject: [windup-dev] Windows Issues
In-Reply-To: <CAEp_U4Gh8paei0vbu8E8ggP=D=5oduCjYnW1KB3csQLk0KJf+A@mail.gmail.com>
References: <543D4765.6000302@redhat.com>	<1218849334.44405190.1413308529628.JavaMail.zimbra@redhat.com>
	<CAEp_U4Gh8paei0vbu8E8ggP=D=5oduCjYnW1KB3csQLk0KJf+A@mail.gmail.com>
Message-ID: <543D7136.8080501@redhat.com>

We also need to know whether it is actually getting stuck (and taking >1 
minute/class). Do we maintain any stats like that at the moment?

On 10/14/2014 02:52 PM, Lincoln Baxter, III wrote:
> In theory, this is a good idea, we probably do want to limit the 
> amount of time spent on each class.
>
> However, simply running decompilation in a separate thread will likely 
> not allow us to interrupt the thread. We'll need to figure out where 
> Procyon is running, and if it actually responds to Thread.interrupt() 
> (I'm betting it doesn't.) (And how to make sure that it does, which 
> will likely take some extension or modification of Procyon itself.)
>
> This is definitely something to look in to over the next few 
> weeks/months as we harden this first version of the tool.
>
> On Tue, Oct 14, 2014 at 1:42 PM, Brad Davis <bdavis at redhat.com 
> <mailto:bdavis at redhat.com>> wrote:
>
>     I think we could maybe create the decompiler as a runnable, and
>     interrupt the thread with a timeout if the decompiler takes more
>     than a minute for a class, which should be plenty of time.  We
>     should log this, though, to make sure they are aware that one of
>     the classes did not successfully decompile.
>
>     Brad Davis
>     Senior Manager, 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: "Ondrej Zizka" <ozizka at redhat.com <mailto:ozizka at redhat.com>>
>     To: "Windup-dev List" <windup-dev at lists.jboss.org
>     <mailto:windup-dev at lists.jboss.org>>
>     Sent: Tuesday, October 14, 2014 11:55:17 AM
>     Subject: [windup-dev] Windows Issues
>
>     Hi,
>
>     I've tried on Windows 7 64bit, Oracle JDK 1.7.0_67.
>
>     The tests fail with WINDUP-335 and WINDUP-332 .
>     The run against Tim's EAR get stuck on Decompilation for about 8
>     hours, seems it's in an endless loop. WINDUP-337
>
>
>     Is Windows a priority? Do we have estimation on what portion of
>     users will run on Windows?
>
>     Ondra
>
>
>
>     _______________________________________________
>     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/20141014/8fd0488f/attachment-0001.html 

From ozizka at redhat.com  Wed Oct 15 10:06:28 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 15 Oct 2014 16:06:28 +0200
Subject: [windup-dev] Windows Issues
In-Reply-To: <543D7136.8080501@redhat.com>
References: <543D4765.6000302@redhat.com>	<1218849334.44405190.1413308529628.JavaMail.zimbra@redhat.com>	<CAEp_U4Gh8paei0vbu8E8ggP=D=5oduCjYnW1KB3csQLk0KJf+A@mail.gmail.com>
	<543D7136.8080501@redhat.com>
Message-ID: <543E7F64.5000103@redhat.com>

I am getting to it tomorrow (going to a JBUG with Mark Little today).
I have a SSD on linux and HDD on Windows. Not sure how I/O heavy 
decompilation is, I assume not much. I don't have/know any free I/O 
analysis tools on Windows. But I'll set up breakpoints and check what's 
going on.

Ondra



On 14.10.2014 20:53, Jess Sightler wrote:
> We also need to know whether it is actually getting stuck (and taking 
> >1 minute/class). Do we maintain any stats like that at the moment?
>
> On 10/14/2014 02:52 PM, Lincoln Baxter, III wrote:
>> In theory, this is a good idea, we probably do want to limit the 
>> amount of time spent on each class.
>>
>> However, simply running decompilation in a separate thread will 
>> likely not allow us to interrupt the thread. We'll need to figure out 
>> where Procyon is running, and if it actually responds to 
>> Thread.interrupt() (I'm betting it doesn't.) (And how to make sure 
>> that it does, which will likely take some extension or modification 
>> of Procyon itself.)
>>
>> This is definitely something to look in to over the next few 
>> weeks/months as we harden this first version of the tool.
>>
>> On Tue, Oct 14, 2014 at 1:42 PM, Brad Davis <bdavis at redhat.com 
>> <mailto:bdavis at redhat.com>> wrote:
>>
>>     I think we could maybe create the decompiler as a runnable, and
>>     interrupt the thread with a timeout if the decompiler takes more
>>     than a minute for a class, which should be plenty of time.  We
>>     should log this, though, to make sure they are aware that one of
>>     the classes did not successfully decompile.
>>
>>     Brad Davis
>>     Senior Manager, 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: "Ondrej Zizka" <ozizka at redhat.com <mailto:ozizka at redhat.com>>
>>     To: "Windup-dev List" <windup-dev at lists.jboss.org
>>     <mailto:windup-dev at lists.jboss.org>>
>>     Sent: Tuesday, October 14, 2014 11:55:17 AM
>>     Subject: [windup-dev] Windows Issues
>>
>>     Hi,
>>
>>     I've tried on Windows 7 64bit, Oracle JDK 1.7.0_67.
>>
>>     The tests fail with WINDUP-335 and WINDUP-332 .
>>     The run against Tim's EAR get stuck on Decompilation for about 8
>>     hours, seems it's in an endless loop. WINDUP-337
>>
>>
>>     Is Windows a priority? Do we have estimation on what portion of
>>     users will run on Windows?
>>
>>     Ondra
>>
>>
>>
>>     _______________________________________________
>>     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/20141015/0d12dcc4/attachment.html 

From jsightle at redhat.com  Wed Oct 15 12:14:44 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Wed, 15 Oct 2014 12:14:44 -0400
Subject: [windup-dev] Windows Issues
In-Reply-To: <543E7F64.5000103@redhat.com>
References: <543D4765.6000302@redhat.com>	<1218849334.44405190.1413308529628.JavaMail.zimbra@redhat.com>	<CAEp_U4Gh8paei0vbu8E8ggP=D=5oduCjYnW1KB3csQLk0KJf+A@mail.gmail.com>	<543D7136.8080501@redhat.com>
	<543E7F64.5000103@redhat.com>
Message-ID: <543E9D74.1000805@redhat.com>

When I ran it on Windows with decompiling set to all packages (as I 
assumed you did), it hung while decompiling xercesImpl.jar (I could tell 
this from the logs). Looking on disk, there was a 0 byte file 
CoreDocumentImpl.java that appeared to be the last thing it was working on.

So, I ran both Procyon 0.5.25 and 0.5.26 on it on Fedora, and both have 
hung in exactly the same place. This is obviously not a platform 
specific bug. I'll try to file this upstream with the procyon maintainer.

On 10/15/2014 10:06 AM, Ondrej Zizka wrote:
> I am getting to it tomorrow (going to a JBUG with Mark Little today).
> I have a SSD on linux and HDD on Windows. Not sure how I/O heavy 
> decompilation is, I assume not much. I don't have/know any free I/O 
> analysis tools on Windows. But I'll set up breakpoints and check 
> what's going on.
>
> Ondra
>
>
>
> On 14.10.2014 20:53, Jess Sightler wrote:
>> We also need to know whether it is actually getting stuck (and taking 
>> >1 minute/class). Do we maintain any stats like that at the moment?
>>
>> On 10/14/2014 02:52 PM, Lincoln Baxter, III wrote:
>>> In theory, this is a good idea, we probably do want to limit the 
>>> amount of time spent on each class.
>>>
>>> However, simply running decompilation in a separate thread will 
>>> likely not allow us to interrupt the thread. We'll need to figure 
>>> out where Procyon is running, and if it actually responds to 
>>> Thread.interrupt() (I'm betting it doesn't.) (And how to make sure 
>>> that it does, which will likely take some extension or modification 
>>> of Procyon itself.)
>>>
>>> This is definitely something to look in to over the next few 
>>> weeks/months as we harden this first version of the tool.
>>>
>>> On Tue, Oct 14, 2014 at 1:42 PM, Brad Davis <bdavis at redhat.com 
>>> <mailto:bdavis at redhat.com>> wrote:
>>>
>>>     I think we could maybe create the decompiler as a runnable, and
>>>     interrupt the thread with a timeout if the decompiler takes more
>>>     than a minute for a class, which should be plenty of time.  We
>>>     should log this, though, to make sure they are aware that one of
>>>     the classes did not successfully decompile.
>>>
>>>     Brad Davis
>>>     Senior Manager, 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: "Ondrej Zizka" <ozizka at redhat.com <mailto:ozizka at redhat.com>>
>>>     To: "Windup-dev List" <windup-dev at lists.jboss.org
>>>     <mailto:windup-dev at lists.jboss.org>>
>>>     Sent: Tuesday, October 14, 2014 11:55:17 AM
>>>     Subject: [windup-dev] Windows Issues
>>>
>>>     Hi,
>>>
>>>     I've tried on Windows 7 64bit, Oracle JDK 1.7.0_67.
>>>
>>>     The tests fail with WINDUP-335 and WINDUP-332 .
>>>     The run against Tim's EAR get stuck on Decompilation for about 8
>>>     hours, seems it's in an endless loop. WINDUP-337
>>>
>>>
>>>     Is Windows a priority? Do we have estimation on what portion of
>>>     users will run on Windows?
>>>
>>>     Ondra
>>>
>>>
>>>
>>>     _______________________________________________
>>>     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

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

From bdavis at redhat.com  Wed Oct 15 15:34:26 2014
From: bdavis at redhat.com (Brad Davis)
Date: Wed, 15 Oct 2014 15:34:26 -0400 (EDT)
Subject: [windup-dev] Windows Issues
In-Reply-To: <543E9D74.1000805@redhat.com>
References: <543D4765.6000302@redhat.com>
	<1218849334.44405190.1413308529628.JavaMail.zimbra@redhat.com>
	<CAEp_U4Gh8paei0vbu8E8ggP=D=5oduCjYnW1KB3csQLk0KJf+A@mail.gmail.com>
	<543D7136.8080501@redhat.com> <543E7F64.5000103@redhat.com>
	<543E9D74.1000805@redhat.com>
Message-ID: <1686867102.45444500.1413401666442.JavaMail.zimbra@redhat.com>

Just curious, why is it trying to decomplile xerces?  Do we not filter on customer packages yet?

Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com 


----- Original Message -----
From: "Jess Sightler" <jsightle at redhat.com>
To: windup-dev at lists.jboss.org
Sent: Wednesday, October 15, 2014 12:14:44 PM
Subject: Re: [windup-dev] Windows Issues

When I ran it on Windows with decompiling set to all packages (as I assumed you did), it hung while decompiling xercesImpl.jar (I could tell this from the logs). Looking on disk, there was a 0 byte file CoreDocumentImpl.java that appeared to be the last thing it was working on. 

So, I ran both Procyon 0.5.25 and 0.5.26 on it on Fedora, and both have hung in exactly the same place. This is obviously not a platform specific bug. I'll try to file this upstream with the procyon maintainer. 

On 10/15/2014 10:06 AM, Ondrej Zizka wrote: 


I am getting to it tomorrow (going to a JBUG with Mark Little today). 
I have a SSD on linux and HDD on Windows. Not sure how I/O heavy decompilation is, I assume not much. I don't have/know any free I/O analysis tools on Windows. But I'll set up breakpoints and check what's going on. 

Ondra 



On 14.10.2014 20:53, Jess Sightler wrote: 


We also need to know whether it is actually getting stuck (and taking >1 minute/class). Do we maintain any stats like that at the moment? 

On 10/14/2014 02:52 PM, Lincoln Baxter, III wrote: 



In theory, this is a good idea, we probably do want to limit the amount of time spent on each class. 

However, simply running decompilation in a separate thread will likely not allow us to interrupt the thread. We'll need to figure out where Procyon is running, and if it actually responds to Thread.interrupt() (I'm betting it doesn't.) (And how to make sure that it does, which will likely take some extension or modification of Procyon itself.) 

This is definitely something to look in to over the next few weeks/months as we harden this first version of the tool. 

On Tue, Oct 14, 2014 at 1:42 PM, Brad Davis < bdavis at redhat.com > wrote: 


I think we could maybe create the decompiler as a runnable, and interrupt the thread with a timeout if the decompiler takes more than a minute for a class, which should be plenty of time. We should log this, though, to make sure they are aware that one of the classes did not successfully decompile. 

Brad Davis 
Senior Manager, Red Hat Consulting 
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com 


----- Original Message ----- 
From: "Ondrej Zizka" < ozizka at redhat.com > 
To: "Windup-dev List" < windup-dev at lists.jboss.org > 
Sent: Tuesday, October 14, 2014 11:55:17 AM 
Subject: [windup-dev] Windows Issues 

Hi, 

I've tried on Windows 7 64bit, Oracle JDK 1.7.0_67. 

The tests fail with WINDUP-335 and WINDUP-332 . 
The run against Tim's EAR get stuck on Decompilation for about 8 hours, seems it's in an endless loop. WINDUP-337 


Is Windows a priority? Do we have estimation on what portion of users will run on Windows? 

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 



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


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

From jsightle at redhat.com  Wed Oct 15 15:43:55 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Wed, 15 Oct 2014 15:43:55 -0400
Subject: [windup-dev] Windows Issues
In-Reply-To: <1686867102.45444500.1413401666442.JavaMail.zimbra@redhat.com>
References: <543D4765.6000302@redhat.com>	<1218849334.44405190.1413308529628.JavaMail.zimbra@redhat.com>	<CAEp_U4Gh8paei0vbu8E8ggP=D=5oduCjYnW1KB3csQLk0KJf+A@mail.gmail.com>	<543D7136.8080501@redhat.com>
	<543E7F64.5000103@redhat.com>	<543E9D74.1000805@redhat.com>
	<1686867102.45444500.1413401666442.JavaMail.zimbra@redhat.com>
Message-ID: <543ECE7B.2000007@redhat.com>

We do, but he was running it with it set to decompile everything. It 
worked when I ran it with the customer package parameter set to the 
customer's package name.

On 10/15/2014 03:34 PM, Brad Davis wrote:
> Just curious, why is it trying to decomplile xerces?  Do we not filter on customer packages yet?
>
> Brad Davis
> Senior Manager, Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Jess Sightler" <jsightle at redhat.com>
> To: windup-dev at lists.jboss.org
> Sent: Wednesday, October 15, 2014 12:14:44 PM
> Subject: Re: [windup-dev] Windows Issues
>
> When I ran it on Windows with decompiling set to all packages (as I assumed you did), it hung while decompiling xercesImpl.jar (I could tell this from the logs). Looking on disk, there was a 0 byte file CoreDocumentImpl.java that appeared to be the last thing it was working on.
>
> So, I ran both Procyon 0.5.25 and 0.5.26 on it on Fedora, and both have hung in exactly the same place. This is obviously not a platform specific bug. I'll try to file this upstream with the procyon maintainer.
>
> On 10/15/2014 10:06 AM, Ondrej Zizka wrote:
>
>
> I am getting to it tomorrow (going to a JBUG with Mark Little today).
> I have a SSD on linux and HDD on Windows. Not sure how I/O heavy decompilation is, I assume not much. I don't have/know any free I/O analysis tools on Windows. But I'll set up breakpoints and check what's going on.
>
> Ondra
>
>
>
> On 14.10.2014 20:53, Jess Sightler wrote:
>
>
> We also need to know whether it is actually getting stuck (and taking >1 minute/class). Do we maintain any stats like that at the moment?
>
> On 10/14/2014 02:52 PM, Lincoln Baxter, III wrote:
>
>
>
> In theory, this is a good idea, we probably do want to limit the amount of time spent on each class.
>
> However, simply running decompilation in a separate thread will likely not allow us to interrupt the thread. We'll need to figure out where Procyon is running, and if it actually responds to Thread.interrupt() (I'm betting it doesn't.) (And how to make sure that it does, which will likely take some extension or modification of Procyon itself.)
>
> This is definitely something to look in to over the next few weeks/months as we harden this first version of the tool.
>
> On Tue, Oct 14, 2014 at 1:42 PM, Brad Davis < bdavis at redhat.com > wrote:
>
>
> I think we could maybe create the decompiler as a runnable, and interrupt the thread with a timeout if the decompiler takes more than a minute for a class, which should be plenty of time. We should log this, though, to make sure they are aware that one of the classes did not successfully decompile.
>
> Brad Davis
> Senior Manager, Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Ondrej Zizka" < ozizka at redhat.com >
> To: "Windup-dev List" < windup-dev at lists.jboss.org >
> Sent: Tuesday, October 14, 2014 11:55:17 AM
> Subject: [windup-dev] Windows Issues
>
> Hi,
>
> I've tried on Windows 7 64bit, Oracle JDK 1.7.0_67.
>
> The tests fail with WINDUP-335 and WINDUP-332 .
> The run against Tim's EAR get stuck on Decompilation for about 8 hours, seems it's in an endless loop. WINDUP-337
>
>
> Is Windows a priority? Do we have estimation on what portion of users will run on Windows?
>
> 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 bdavis at redhat.com  Wed Oct 15 16:03:52 2014
From: bdavis at redhat.com (Brad Davis)
Date: Wed, 15 Oct 2014 16:03:52 -0400 (EDT)
Subject: [windup-dev] Windows Issues
In-Reply-To: <543ECE7B.2000007@redhat.com>
References: <543D4765.6000302@redhat.com>
	<1218849334.44405190.1413308529628.JavaMail.zimbra@redhat.com>
	<CAEp_U4Gh8paei0vbu8E8ggP=D=5oduCjYnW1KB3csQLk0KJf+A@mail.gmail.com>
	<543D7136.8080501@redhat.com> <543E7F64.5000103@redhat.com>
	<543E9D74.1000805@redhat.com>
	<1686867102.45444500.1413401666442.JavaMail.zimbra@redhat.com>
	<543ECE7B.2000007@redhat.com>
Message-ID: <659079402.45454023.1413403432651.JavaMail.zimbra@redhat.com>

I think Mike from the Procyon team will be pretty responsive to the bug if you file it with Xerces and the specific package + class it is stuck on.  Good work tracking it down!

Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com 


----- Original Message -----
From: "Jess Sightler" <jsightle at redhat.com>
To: windup-dev at lists.jboss.org
Sent: Wednesday, October 15, 2014 3:43:55 PM
Subject: Re: [windup-dev] Windows Issues

We do, but he was running it with it set to decompile everything. It 
worked when I ran it with the customer package parameter set to the 
customer's package name.

On 10/15/2014 03:34 PM, Brad Davis wrote:
> Just curious, why is it trying to decomplile xerces?  Do we not filter on customer packages yet?
>
> Brad Davis
> Senior Manager, Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Jess Sightler" <jsightle at redhat.com>
> To: windup-dev at lists.jboss.org
> Sent: Wednesday, October 15, 2014 12:14:44 PM
> Subject: Re: [windup-dev] Windows Issues
>
> When I ran it on Windows with decompiling set to all packages (as I assumed you did), it hung while decompiling xercesImpl.jar (I could tell this from the logs). Looking on disk, there was a 0 byte file CoreDocumentImpl.java that appeared to be the last thing it was working on.
>
> So, I ran both Procyon 0.5.25 and 0.5.26 on it on Fedora, and both have hung in exactly the same place. This is obviously not a platform specific bug. I'll try to file this upstream with the procyon maintainer.
>
> On 10/15/2014 10:06 AM, Ondrej Zizka wrote:
>
>
> I am getting to it tomorrow (going to a JBUG with Mark Little today).
> I have a SSD on linux and HDD on Windows. Not sure how I/O heavy decompilation is, I assume not much. I don't have/know any free I/O analysis tools on Windows. But I'll set up breakpoints and check what's going on.
>
> Ondra
>
>
>
> On 14.10.2014 20:53, Jess Sightler wrote:
>
>
> We also need to know whether it is actually getting stuck (and taking >1 minute/class). Do we maintain any stats like that at the moment?
>
> On 10/14/2014 02:52 PM, Lincoln Baxter, III wrote:
>
>
>
> In theory, this is a good idea, we probably do want to limit the amount of time spent on each class.
>
> However, simply running decompilation in a separate thread will likely not allow us to interrupt the thread. We'll need to figure out where Procyon is running, and if it actually responds to Thread.interrupt() (I'm betting it doesn't.) (And how to make sure that it does, which will likely take some extension or modification of Procyon itself.)
>
> This is definitely something to look in to over the next few weeks/months as we harden this first version of the tool.
>
> On Tue, Oct 14, 2014 at 1:42 PM, Brad Davis < bdavis at redhat.com > wrote:
>
>
> I think we could maybe create the decompiler as a runnable, and interrupt the thread with a timeout if the decompiler takes more than a minute for a class, which should be plenty of time. We should log this, though, to make sure they are aware that one of the classes did not successfully decompile.
>
> Brad Davis
> Senior Manager, Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Ondrej Zizka" < ozizka at redhat.com >
> To: "Windup-dev List" < windup-dev at lists.jboss.org >
> Sent: Tuesday, October 14, 2014 11:55:17 AM
> Subject: [windup-dev] Windows Issues
>
> Hi,
>
> I've tried on Windows 7 64bit, Oracle JDK 1.7.0_67.
>
> The tests fail with WINDUP-335 and WINDUP-332 .
> The run against Tim's EAR get stuck on Decompilation for about 8 hours, seems it's in an endless loop. WINDUP-337
>
>
> Is Windows a priority? Do we have estimation on what portion of users will run on Windows?
>
> 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 jsightle at redhat.com  Wed Oct 15 16:15:02 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Wed, 15 Oct 2014 16:15:02 -0400
Subject: [windup-dev] Windows Issues
In-Reply-To: <659079402.45454023.1413403432651.JavaMail.zimbra@redhat.com>
References: <543D4765.6000302@redhat.com>	<1218849334.44405190.1413308529628.JavaMail.zimbra@redhat.com>	<CAEp_U4Gh8paei0vbu8E8ggP=D=5oduCjYnW1KB3csQLk0KJf+A@mail.gmail.com>	<543D7136.8080501@redhat.com>
	<543E7F64.5000103@redhat.com>	<543E9D74.1000805@redhat.com>	<1686867102.45444500.1413401666442.JavaMail.zimbra@redhat.com>	<543ECE7B.2000007@redhat.com>
	<659079402.45454023.1413403432651.JavaMail.zimbra@redhat.com>
Message-ID: <543ED5C6.4050609@redhat.com>

He does seem to be pretty responsive. Here is the issue report:
https://bitbucket.org/mstrobel/procyon/issue/215/decompiler-hangs-on-xercesimpl-test-jar


On 10/15/2014 04:03 PM, Brad Davis wrote:
> I think Mike from the Procyon team will be pretty responsive to the bug if you file it with Xerces and the specific package + class it is stuck on.  Good work tracking it down!
>
> Brad Davis
> Senior Manager, Red Hat Consulting
>
>
> ----- Original Message -----
> From: "Jess Sightler" <jsightle at redhat.com>
> To: windup-dev at lists.jboss.org
> Sent: Wednesday, October 15, 2014 3:43:55 PM
> Subject: Re: [windup-dev] Windows Issues
>
> We do, but he was running it with it set to decompile everything. It
> worked when I ran it with the customer package parameter set to the
> customer's package name.
>
> On 10/15/2014 03:34 PM, Brad Davis wrote:
>> Just curious, why is it trying to decomplile xerces?  Do we not filter on customer packages yet?
>>
>> Brad Davis
>> Senior Manager, Red Hat Consulting
>>
>>
>> ----- Original Message -----
>> From: "Jess Sightler" <jsightle at redhat.com>
>> To: windup-dev at lists.jboss.org
>> Sent: Wednesday, October 15, 2014 12:14:44 PM
>> Subject: Re: [windup-dev] Windows Issues
>>
>> When I ran it on Windows with decompiling set to all packages (as I assumed you did), it hung while decompiling xercesImpl.jar (I could tell this from the logs). Looking on disk, there was a 0 byte file CoreDocumentImpl.java that appeared to be the last thing it was working on.
>>
>> So, I ran both Procyon 0.5.25 and 0.5.26 on it on Fedora, and both have hung in exactly the same place. This is obviously not a platform specific bug. I'll try to file this upstream with the procyon maintainer.
>>
>> On 10/15/2014 10:06 AM, Ondrej Zizka wrote:
>>
>>
>> I am getting to it tomorrow (going to a JBUG with Mark Little today).
>> I have a SSD on linux and HDD on Windows. Not sure how I/O heavy decompilation is, I assume not much. I don't have/know any free I/O analysis tools on Windows. But I'll set up breakpoints and check what's going on.
>>
>> Ondra
>>
>>
>>
>> On 14.10.2014 20:53, Jess Sightler wrote:
>>
>>
>> We also need to know whether it is actually getting stuck (and taking >1 minute/class). Do we maintain any stats like that at the moment?
>>
>> On 10/14/2014 02:52 PM, Lincoln Baxter, III wrote:
>>
>>
>>
>> In theory, this is a good idea, we probably do want to limit the amount of time spent on each class.
>>
>> However, simply running decompilation in a separate thread will likely not allow us to interrupt the thread. We'll need to figure out where Procyon is running, and if it actually responds to Thread.interrupt() (I'm betting it doesn't.) (And how to make sure that it does, which will likely take some extension or modification of Procyon itself.)
>>
>> This is definitely something to look in to over the next few weeks/months as we harden this first version of the tool.
>>
>> On Tue, Oct 14, 2014 at 1:42 PM, Brad Davis < bdavis at redhat.com > wrote:
>>
>>
>> I think we could maybe create the decompiler as a runnable, and interrupt the thread with a timeout if the decompiler takes more than a minute for a class, which should be plenty of time. We should log this, though, to make sure they are aware that one of the classes did not successfully decompile.
>>
>> Brad Davis
>> Senior Manager, Red Hat Consulting
>>
>>
>> ----- Original Message -----
>> From: "Ondrej Zizka" < ozizka at redhat.com >
>> To: "Windup-dev List" < windup-dev at lists.jboss.org >
>> Sent: Tuesday, October 14, 2014 11:55:17 AM
>> Subject: [windup-dev] Windows Issues
>>
>> Hi,
>>
>> I've tried on Windows 7 64bit, Oracle JDK 1.7.0_67.
>>
>> The tests fail with WINDUP-335 and WINDUP-332 .
>> The run against Tim's EAR get stuck on Decompilation for about 8 hours, seems it's in an endless loop. WINDUP-337
>>
>>
>> Is Windows a priority? Do we have estimation on what portion of users will run on Windows?
>>
>> 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


From zizka at seznam.cz  Mon Oct 20 17:56:12 2014
From: zizka at seznam.cz (=?UTF-8?B?IkluZy4gT25kxZllaiDFvWnFvmthIg==?=)
Date: Mon, 20 Oct 2014 23:56:12 +0200
Subject: [windup-dev] Windup BOM
Message-ID: <544584FC.6010709@seznam.cz>

Hi all,

we're introducing Windup BOM (Build of Materials).

A BOM is basically a declaration of versions of artifact that you may 
need when building Windup 2 rulesets.
By adding it to your ruleset's pom.xml, you avoid setting wrong versions 
and maintaining them when upgrading.

Usage:

     <properties>
         ...
         <version.windup>2.0.0.Beta2</version.windup>
     </properties>

     <dependencyManagement>
         <dependencies>

             <!-- Windup BOM -->
             <dependency>
                 <groupId>org.jboss.windup</groupId>
<artifactId>windup-rulesets-bom</artifactId>
                 <version>${version.windup}</version>
                 <type>pom</type>
                 <scope>import</scope>
             </dependency>

         </dependencies>
     </dependencyManagement>

See the Windup QuickStarts for an example.

Enjoy :)
Ondra

TIP: Parallelized Maven builds: `mvn -T 1C clean install` speeds up esp. 
the initial downloading of dependencies.


From ozizka at redhat.com  Mon Oct 20 17:57:10 2014
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 20 Oct 2014 23:57:10 +0200
Subject: [windup-dev] Windup BOM
Message-ID: <54458536.3090102@redhat.com>

Hi all,

we're introducing Windup BOM (Build of Materials).

A BOM is basically a declaration of versions of artifact that you may 
need when building Windup 2 rulesets.
By adding it to your ruleset's pom.xml, you avoid setting wrong versions 
and maintaining them when upgrading.

Usage:

     <properties>
         ...
         <version.windup>2.0.0.Beta2</version.windup>
     </properties>

     <dependencyManagement>
         <dependencies>

             <!-- Windup BOM -->
             <dependency>
                 <groupId>org.jboss.windup</groupId>
<artifactId>windup-rulesets-bom</artifactId>
                 <version>${version.windup}</version>
                 <type>pom</type>
                 <scope>import</scope>
             </dependency>

         </dependencies>
     </dependencyManagement>

See the Windup QuickStarts for an example.

Enjoy :)
Ondra

TIP: Parallelized Maven builds: `mvn -T 1C clean install` speeds up esp. 
the initial downloading of dependencies.


From lincolnbaxter at gmail.com  Tue Oct 21 14:04:57 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 21 Oct 2014 14:04:57 -0400
Subject: [windup-dev] Windup 2.0.0.Beta3 Released
Message-ID: <CAEp_U4HXXtQ-eUub2LENFYXG1GfaLUz+w+odUrVP6qkO1urYGA@mail.gmail.com>

https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=releases&g=org.jboss.windup&a=windup-distribution&v=2.0.0.Beta3&e=zip&c=offline

Bug

   - [WINDUP-344 <https://issues.jboss.org/browse/WINDUP-344>] - Error
   running rule against exmple app

Feature Request

   - [WINDUP-217 <https://issues.jboss.org/browse/WINDUP-217>] - Short
   unique IDs for rulesets
   - [WINDUP-352 <https://issues.jboss.org/browse/WINDUP-352>] - Windup
   should look for external rules files in dist/rules/ and ~/.windup/rules
   folders automatically

Task

   - [WINDUP-165 <https://issues.jboss.org/browse/WINDUP-165>] - Rename all
   test Models, Operations and Rules with Test~ prefix
   - [WINDUP-184 <https://issues.jboss.org/browse/WINDUP-184>] - Unify the
   way to define Models' property name constants.


-- 
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/20141021/dec825ed/attachment.html 

From sgilda at redhat.com  Tue Oct 21 14:41:32 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 21 Oct 2014 14:41:32 -0400
Subject: [windup-dev] Windup 2.0.0.Beta3 Released
In-Reply-To: <CAEp_U4HXXtQ-eUub2LENFYXG1GfaLUz+w+odUrVP6qkO1urYGA@mail.gmail.com>
References: <CAEp_U4HXXtQ-eUub2LENFYXG1GfaLUz+w+odUrVP6qkO1urYGA@mail.gmail.com>
Message-ID: <5446A8DC.1050901@redhat.com>

Thanks Lincoln!

On 10/21/2014 02:04 PM, Lincoln Baxter, III wrote:
> https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=releases&g=org.jboss.windup&a=windup-distribution&v=2.0.0.Beta3&e=zip&c=offline 
>
>
>
>     Bug
>
>   * [WINDUP-344 <https://issues.jboss.org/browse/WINDUP-344>] - Error
>     running rule against exmple app
>
>
>     Feature Request
>
>   * [WINDUP-217 <https://issues.jboss.org/browse/WINDUP-217>] - Short
>     unique IDs for rulesets
>   * [WINDUP-352 <https://issues.jboss.org/browse/WINDUP-352>] - Windup
>     should look for external rules files in dist/rules/ and
>     ~/.windup/rules folders automatically
>
>
>     Task
>
>   * [WINDUP-165 <https://issues.jboss.org/browse/WINDUP-165>] - Rename
>     all test Models, Operations and Rules with Test~ prefix
>   * [WINDUP-184 <https://issues.jboss.org/browse/WINDUP-184>] - Unify
>     the way to define Models' property name constants.
>
>
> -- 
> 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/20141021/80047c3a/attachment-0001.html 

From sgilda at redhat.com  Tue Oct 21 19:13:42 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 21 Oct 2014 19:13:42 -0400
Subject: [windup-dev] Problem installing the quickstart rule into Windup
Message-ID: <5446E8A6.1070901@redhat.com>

The command to install the quickstart seems to hang here:

    [windup-distribution-2.0.0.Beta3]$ addon-install
    Coordinate (The addon's "groupId:artifactId,version" coordinate):
    org.jboss.windup.quickstarts:windup-weblogic-javaee-servlet,2.0.0.Beta3

I issued the command at 5:42 PM. It's now 7:11 PM.

I successfully ran 'mvn clean install' on the quickstart. The source is 
located here: 
https://github.com/windup/windup-quickstarts/tree/master/weblogic-javaee-servlet

Any idea what I'm doing wrong?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20141021/cab78d72/attachment.html 

From lincolnbaxter at gmail.com  Wed Oct 22 11:02:09 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 22 Oct 2014 11:02:09 -0400
Subject: [windup-dev] Problem installing the quickstart rule into Windup
In-Reply-To: <5446E8A6.1070901@redhat.com>
References: <5446E8A6.1070901@redhat.com>
Message-ID: <CAEp_U4E81_gZezewpTiN10cDwBcxWEM-GuNa6PEnSYEMmDakSw@mail.gmail.com>

Turns out the solution to this was to upgrade to Java 7u60. (For the
record.)

On Tue, Oct 21, 2014 at 7:13 PM, Sande Gilda <sgilda at redhat.com> wrote:

>  The command to install the quickstart seems to hang here:
>
> [windup-distribution-2.0.0.Beta3]$ addon-install
> Coordinate (The addon's "groupId:artifactId,version" coordinate):
> org.jboss.windup.quickstarts:windup-weblogic-javaee-servlet,2.0.0.Beta3
>
> I issued the command at 5:42 PM. It's now 7:11 PM.
>
> I successfully ran 'mvn clean install' on the quickstart. The source is
> located here:
> https://github.com/windup/windup-quickstarts/tree/master/weblogic-javaee-servlet
>
> Any idea what I'm doing wrong?
>
> _______________________________________________
> 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/20141022/d4193d33/attachment.html 

From sgilda at redhat.com  Wed Oct 22 11:16:32 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Wed, 22 Oct 2014 11:16:32 -0400
Subject: [windup-dev] Problem installing the quickstart rule into Windup
In-Reply-To: <CAEp_U4E81_gZezewpTiN10cDwBcxWEM-GuNa6PEnSYEMmDakSw@mail.gmail.com>
References: <5446E8A6.1070901@redhat.com>
	<CAEp_U4E81_gZezewpTiN10cDwBcxWEM-GuNa6PEnSYEMmDakSw@mail.gmail.com>
Message-ID: <5447CA50.2090207@redhat.com>

Right. Thanks Lincoln. It seems that java version "1.7.0_51" was the issue.

On 10/22/2014 11:02 AM, Lincoln Baxter, III wrote:
> Turns out the solution to this was to upgrade to Java 7u60. (For the 
> record.)
>
> On Tue, Oct 21, 2014 at 7:13 PM, Sande Gilda <sgilda at redhat.com 
> <mailto:sgilda at redhat.com>> wrote:
>
>     The command to install the quickstart seems to hang here:
>
>         [windup-distribution-2.0.0.Beta3]$ addon-install
>         Coordinate (The addon's "groupId:artifactId,version"
>         coordinate):
>         org.jboss.windup.quickstarts:windup-weblogic-javaee-servlet,2.0.0.Beta3
>
>     I issued the command at 5:42 PM. It's now 7:11 PM.
>
>     I successfully ran 'mvn clean install' on the quickstart. The
>     source is located here:
>     https://github.com/windup/windup-quickstarts/tree/master/weblogic-javaee-servlet
>
>     Any idea what I'm doing wrong?
>
>     _______________________________________________
>     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/20141022/6a404b2e/attachment.html 

From sgilda at redhat.com  Wed Oct 22 11:50:06 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Wed, 22 Oct 2014 11:50:06 -0400
Subject: [windup-dev] Fwd: My WebLogic file
In-Reply-To: <5447CE8D.4040903@redhat.com>
References: <5447CE8D.4040903@redhat.com>
Message-ID: <5447D22E.50301@redhat.com>




-------- Forwarded Message --------
Subject: 	My WebLogic file
Date: 	Wed, 22 Oct 2014 11:34:37 -0400
From: 	Sande Gilda <sgilda at redhat.com>
To: 	Ond?ej ?i?ka <ozizka at redhat.com>
CC: 	Robb Greathouse <robb.greathouse at redhat.com>



Ondra,

Copy the attached file into your windup source 
'test-files/src_example/src/main/java/org/windup/examples/servlet/' 
directory.

That directory will now have 2 files: SampleServlet.java and 
SampleWebLogicServlet.java

I used the instructions in the quickstart README file here: 
https://github.com/windup/windup-quickstarts/blob/master/weblogic-javaee-servlet/README.md

I installed the rule, added it to windup, and ran:

    windup-migrate-app --input
    /home/sgilda/GitRepos/windup/test-files/src_example/ --output
    /home/sgilda/temp/WindupOutput/src_example_report --packages
    weblogic.servlet

My report has 0 story points and looks like the following. I expected to 
see story points for the WebLogic servlet annotations and this hint: 
"Migrate to Java EE 6 @WebServlet."

It doesn't appear to be evaluating my java/ directory at all. Any idea 
what I am doing wrong?

Thanks,
Sande








-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20141022/36b5eec8/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 43713 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20141022/36b5eec8/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 92157 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20141022/36b5eec8/attachment-0003.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SampleWebLogicServlet.java
Type: text/x-java
Size: 868 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20141022/36b5eec8/attachment-0001.bin 

From lincolnbaxter at gmail.com  Wed Oct 22 19:32:51 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 22 Oct 2014 19:32:51 -0400
Subject: [windup-dev] Files from the Windup Training Demo (Round 1)
Message-ID: <CAEp_U4HajWiaoGaNB1XtFhDeNYkhkiHK-bsJc5+g+sV0=j3U6Q@mail.gmail.com>

Attached are the files that I put together for the Windup Training session.

*The following files go into ~/.windup/rules/*
sample.windup.xml
sample.xsl

*The sample-windup-ruleset project needs to be installed as a rule addon.*

I've included the sample application for which the rules were written.

Cheers!
-- 
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/20141022/58e6c364/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: windup-demo.zip
Type: application/zip
Size: 1097197 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20141022/58e6c364/attachment-0001.zip 

From sgilda at redhat.com  Tue Oct 28 16:27:36 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 28 Oct 2014 16:27:36 -0400
Subject: [windup-dev] Windup quickstart
Message-ID: <544FFC38.3050400@redhat.com>

I have made some enhancements to Ondra's quickstart located here:

    https://github.com/windup/windup-quickstarts/tree/master/weblogic-javaee-servlet

This quickstart looks for WebLogic proprietary servlet annotations.

I added a couple more rules. I also created a kbase article on the Red 
Hat Customer portal [1] and added that link to the hints.

The instructions are located in the README file.  If you have time, I 
would love to get some feedback on how to improve it.

Do you think it would be a good idea to create an XML-based rule that 
does the same thing as a comparison?

[1] https://access.redhat.com/articles/1249423

Thanks,
Sande



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

From jsightle at redhat.com  Tue Oct 28 17:32:46 2014
From: jsightle at redhat.com (Jess Sightler)
Date: Tue, 28 Oct 2014 17:32:46 -0400
Subject: [windup-dev] Windup quickstart
In-Reply-To: <544FFC38.3050400@redhat.com>
References: <544FFC38.3050400@redhat.com>
Message-ID: <54500B7E.6050200@redhat.com>


On 10/28/2014 04:27 PM, Sande Gilda wrote:
> I have made some enhancements to Ondra's quickstart located here:
>
>     https://github.com/windup/windup-quickstarts/tree/master/weblogic-javaee-servlet
>
> This quickstart looks for WebLogic proprietary servlet annotations.
>
> I added a couple more rules. I also created a kbase article on the Red 
> Hat Customer portal [1] and added that link to the hints.
>


This looks very good to me!


> The instructions are located in the README file.  If you have time, I 
> would love to get some feedback on how to improve it.
>
> Do you think it would be a good idea to create an XML-based rule that 
> does the same thing as a comparison?
>


IMO, Yes.

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

From sgilda at redhat.com  Tue Oct 28 18:08:54 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 28 Oct 2014 18:08:54 -0400
Subject: [windup-dev] Windup quickstart
In-Reply-To: <54500B7E.6050200@redhat.com>
References: <544FFC38.3050400@redhat.com> <54500B7E.6050200@redhat.com>
Message-ID: <545013F6.3060207@redhat.com>

Thanks Jess!

On 10/28/2014 05:32 PM, Jess Sightler wrote:
>
> On 10/28/2014 04:27 PM, Sande Gilda wrote:
>> I have made some enhancements to Ondra's quickstart located here:
>>
>>     https://github.com/windup/windup-quickstarts/tree/master/weblogic-javaee-servlet
>>
>> This quickstart looks for WebLogic proprietary servlet annotations.
>>
>> I added a couple more rules. I also created a kbase article on the 
>> Red Hat Customer portal [1] and added that link to the hints.
>>
>
>
> This looks very good to me!
>
>
>> The instructions are located in the README file.  If you have time, I 
>> would love to get some feedback on how to improve it.
>>
>> Do you think it would be a good idea to create an XML-based rule that 
>> does the same thing as a comparison?
>>
>
>
> IMO, Yes.
>
>
>
> _______________________________________________
> 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/20141028/b884dd32/attachment.html 

From danielsoro at gmail.com  Tue Oct 28 19:20:42 2014
From: danielsoro at gmail.com (Daniel Cunha)
Date: Tue, 28 Oct 2014 21:20:42 -0200
Subject: [windup-dev] Build Problem
Message-ID: <CAHLHu47bnW6OH2sVdWYpwXO7xD5q5YcP0twkivN23nitvuH11Q@mail.gmail.com>

Hi folks,

I had this problem with my build:
https://www.irccloud.com/pastebin/e4EvaA1y

I would like simulate this problem:
https://issues.jboss.org/browse/WINDUP-305
Maybe is a problem on ?sh. I can fix it. :)

-- 
Daniel Cunha (soro) <http://www.cejug.net>
Blog: http://www.danielsoro.com.br
Twitter: https://twitter.com/dvlc_
GitHub: https://github.com/danielsoro
LinkedIn:  http://www.linkedin.com/in/danielvlcunha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20141028/102e1722/attachment.html 

From lincolnbaxter at gmail.com  Tue Oct 28 23:32:11 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 28 Oct 2014 23:32:11 -0400
Subject: [windup-dev] Build Problem
In-Reply-To: <CAHLHu47bnW6OH2sVdWYpwXO7xD5q5YcP0twkivN23nitvuH11Q@mail.gmail.com>
References: <CAHLHu47bnW6OH2sVdWYpwXO7xD5q5YcP0twkivN23nitvuH11Q@mail.gmail.com>
Message-ID: <CAEp_U4FWiappkKwYMUV9KUq2m8W+xffjU5KmcL-OvLG0Qvj3PA@mail.gmail.com>

This happened to me recently, and in the end I think I didn't find a
solution, but it hasn't happened since. What happens if you skip the tests?

On Tue, Oct 28, 2014 at 7:20 PM, Daniel Cunha <danielsoro at gmail.com> wrote:

> Hi folks,
>
> I had this problem with my build:
> https://www.irccloud.com/pastebin/e4EvaA1y
>
> I would like simulate this problem:
> https://issues.jboss.org/browse/WINDUP-305
> Maybe is a problem on ?sh. I can fix it. :)
>
> --
> Daniel Cunha (soro) <http://www.cejug.net>
> Blog: http://www.danielsoro.com.br
> Twitter: https://twitter.com/dvlc_
> GitHub: https://github.com/danielsoro
> LinkedIn:  http://www.linkedin.com/in/danielvlcunha
>
> _______________________________________________
> 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/20141028/2e80ec6e/attachment.html 

From lincolnbaxter at gmail.com  Wed Oct 29 00:41:17 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 29 Oct 2014 00:41:17 -0400
Subject: [windup-dev] Build Problem
In-Reply-To: <CAEp_U4FWiappkKwYMUV9KUq2m8W+xffjU5KmcL-OvLG0Qvj3PA@mail.gmail.com>
References: <CAHLHu47bnW6OH2sVdWYpwXO7xD5q5YcP0twkivN23nitvuH11Q@mail.gmail.com>
	<CAEp_U4FWiappkKwYMUV9KUq2m8W+xffjU5KmcL-OvLG0Qvj3PA@mail.gmail.com>
Message-ID: <CAEp_U4FMB9nn-7nsZuFLXb0zumjMwjde=XfY3o0kdowEjP3N9g@mail.gmail.com>

Also, what is your Java version and OS?

On Tue, Oct 28, 2014 at 11:32 PM, Lincoln Baxter, III <
lincolnbaxter at gmail.com> wrote:

> This happened to me recently, and in the end I think I didn't find a
> solution, but it hasn't happened since. What happens if you skip the tests?
>
> On Tue, Oct 28, 2014 at 7:20 PM, Daniel Cunha <danielsoro at gmail.com>
> wrote:
>
>> Hi folks,
>>
>> I had this problem with my build:
>> https://www.irccloud.com/pastebin/e4EvaA1y
>>
>> I would like simulate this problem:
>> https://issues.jboss.org/browse/WINDUP-305
>> Maybe is a problem on ?sh. I can fix it. :)
>>
>> --
>> Daniel Cunha (soro) <http://www.cejug.net>
>> Blog: http://www.danielsoro.com.br
>> Twitter: https://twitter.com/dvlc_
>> GitHub: https://github.com/danielsoro
>> LinkedIn:  http://www.linkedin.com/in/danielvlcunha
>>
>> _______________________________________________
>> 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/20141029/a327dccb/attachment.html 

From danielsoro at gmail.com  Wed Oct 29 05:05:26 2014
From: danielsoro at gmail.com (Daniel Cunha)
Date: Wed, 29 Oct 2014 07:05:26 -0200
Subject: [windup-dev] Build Problem
In-Reply-To: <CAEp_U4FMB9nn-7nsZuFLXb0zumjMwjde=XfY3o0kdowEjP3N9g@mail.gmail.com>
References: <CAHLHu47bnW6OH2sVdWYpwXO7xD5q5YcP0twkivN23nitvuH11Q@mail.gmail.com>
	<CAEp_U4FWiappkKwYMUV9KUq2m8W+xffjU5KmcL-OvLG0Qvj3PA@mail.gmail.com>
	<CAEp_U4FMB9nn-7nsZuFLXb0zumjMwjde=XfY3o0kdowEjP3N9g@mail.gmail.com>
Message-ID: <CAHLHu44AMw6EKHWcH18FJunMcbnQ=i632H3Z60+cte-DaLFHkQ@mail.gmail.com>

When I skip tests I have same problem.

Linux Xubuntu 32bits
Kernel 3.13.0-37
JDK 1.7.0_72

On Wed, Oct 29, 2014 at 2:41 AM, Lincoln Baxter, III <
lincolnbaxter at gmail.com> wrote:

> Also, what is your Java version and OS?
>
> On Tue, Oct 28, 2014 at 11:32 PM, Lincoln Baxter, III <
> lincolnbaxter at gmail.com> wrote:
>
>> This happened to me recently, and in the end I think I didn't find a
>> solution, but it hasn't happened since. What happens if you skip the tests?
>>
>> On Tue, Oct 28, 2014 at 7:20 PM, Daniel Cunha <danielsoro at gmail.com>
>> wrote:
>>
>>> Hi folks,
>>>
>>> I had this problem with my build:
>>> https://www.irccloud.com/pastebin/e4EvaA1y
>>>
>>> I would like simulate this problem:
>>> https://issues.jboss.org/browse/WINDUP-305
>>> Maybe is a problem on ?sh. I can fix it. :)
>>>
>>> --
>>> Daniel Cunha (soro) <http://www.cejug.net>
>>> Blog: http://www.danielsoro.com.br
>>> Twitter: https://twitter.com/dvlc_
>>> GitHub: https://github.com/danielsoro
>>> LinkedIn:  http://www.linkedin.com/in/danielvlcunha
>>>
>>> _______________________________________________
>>> 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."
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>



-- 
Daniel Cunha (soro) <http://www.cejug.net>
Blog: http://www.danielsoro.com.br
Twitter: https://twitter.com/dvlc_
GitHub: https://github.com/danielsoro
LinkedIn:  http://www.linkedin.com/in/danielvlcunha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20141029/5067cf77/attachment-0001.html 

From lincolnbaxter at gmail.com  Wed Oct 29 09:08:09 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 29 Oct 2014 09:08:09 -0400
Subject: [windup-dev] Windup quickstart
In-Reply-To: <545013F6.3060207@redhat.com>
References: <544FFC38.3050400@redhat.com> <54500B7E.6050200@redhat.com>
	<545013F6.3060207@redhat.com>
Message-ID: <CAEp_U4FtcQx2yBKEHoLz0=iiuG-Vhnm+mPC_XsFhRq6G4ARjig@mail.gmail.com>

Yeah, definitely good to show XML as an alternative here, I think. We
should probably favor XM. As it matures, it will be far more durable and
sustainable than the Java config..

On Tue, Oct 28, 2014 at 6:08 PM, Sande Gilda <sgilda at redhat.com> wrote:

>  Thanks Jess!
>
>
> On 10/28/2014 05:32 PM, Jess Sightler wrote:
>
>
> On 10/28/2014 04:27 PM, Sande Gilda wrote:
>
> I have made some enhancements to Ondra's quickstart located here:
>
>
> https://github.com/windup/windup-quickstarts/tree/master/weblogic-javaee-servlet
>
> This quickstart looks for WebLogic proprietary servlet annotations.
>
> I added a couple more rules. I also created a kbase article on the Red Hat
> Customer portal [1] and added that link to the hints.
>
>
>
> This looks very good to me!
>
>
>  The instructions are located in the README file.  If you have time, I
> would love to get some feedback on how to improve it.
>
> Do you think it would be a good idea to create an XML-based rule that does
> the same thing as a comparison?
>
>
>
> IMO, Yes.
>
>
>
> _______________________________________________
> 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
>



-- 
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/20141029/368eb0f8/attachment.html 

From lincolnbaxter at gmail.com  Wed Oct 29 10:44:14 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 29 Oct 2014 10:44:14 -0400
Subject: [windup-dev] Windup Meeting Minutes - 2014-10-29
Message-ID: <CAEp_U4HkkE4PP49pG=c3qY4Z59CNX4-a0A19coQreurZzK5hQg@mail.gmail.com>

Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-10-29-14.04.html

Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-10-29-14.04.txt

Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup.2014-10-29-14.04.log.html


Meeting summary
---------------
* Agenda  (lincolnthree, 14:04:12)

* Status Reports  (lincolnthree, 14:06:11)
  * Last week, I worked on WINDUP-345: Make the commitPeriodically from
    IndexClassFilesRuleProvider a normal operation  (jsightler,
    14:07:34)
  * WINDUP-360: XmlFile fails to load all lines from the file in some
    cases (this exception should be ignored) (crash bug)  (jsightler,
    14:08:02)
  * WINDUP-365: JavaClass should be able to start from an existing
    Variable  (jsightler, 14:08:23)
  * I also sent a PR with some ideas for improving implicit iteration
    variable names: https://github.com/windup/windup/pull/332
    (jsightler, 14:09:10)
  * Last week I worked a lot on getting windup ready for the initial
    internal training sessions. Found a number of issues with the XML
    config (fixed a few of them), and also created a few small demos to
    give the training session.  (lincolnthree, 14:09:45)
  * this week, so far I worked on prototyping a parameter implementation
    for rules (which is not going too well)  (lincolnthree, 14:10:08)
  * I'll be prepping for the next training session (probably) and also
    working more on parameters and reviewing some more PRs
    (lincolnthree, 14:11:25)

* Performance  (lincolnthree, 14:19:22)
  * I have been working on investigating our performance with the
    current beta release  (jsightler, 14:23:48)

* Next Release Priorities  (lincolnthree, 14:37:53)
  * continuing to improve performance and stability is #1
    (lincolnthree, 14:38:09)
  * working on improving interop of rules is #2  (lincolnthree,
    14:38:28)
  * fixing some of our internal mess is #3  (lincolnthree, 14:38:45)
  * being responsive to feedback from the field is a general "always
    important thing"  (lincolnthree, 14:39:07)


-- 
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/20141029/9d9c01be/attachment.html 

From lincolnbaxter at gmail.com  Fri Oct 17 12:49:52 2014
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 17 Oct 2014 16:49:52 -0000
Subject: [windup-dev] Windup 2.0.0.Beta2 Released
Message-ID: <CAEp_U4ECrKu5nMJBxfRYgT-Xe1u_sX4txuFcxo0XDVzAqH4Kvw@mail.gmail.com>

https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=releases&g=org.jboss.windup&a=windup-distribution&v=2.0.0.Beta2&e=zip&c=offline

The whole team did a great job to get the bug-fixes, enhancements, and new
features into this release!
Bug

   - [WINDUP-226 <https://issues.jboss.org/browse/WINDUP-226>] -
   Classification adds multiple fileModels even though they are the same
   - [WINDUP-323 <https://issues.jboss.org/browse/WINDUP-323>] - More
   toString() methods are needed as this makes the rules easier to read/debug
   - [WINDUP-326 <https://issues.jboss.org/browse/WINDUP-326>] - Rule blows
   up when running against SOA5 example.
   - [WINDUP-339 <https://issues.jboss.org/browse/WINDUP-339>] -
   CssJsResourceRenderingRuleProvider does not appear to be copying files
   correctly on Windows
   - [WINDUP-348 <https://issues.jboss.org/browse/WINDUP-348>] - Errors
   running Windup against EJB 2.1 example app

Enhancement

   - [WINDUP-135 <https://issues.jboss.org/browse/WINDUP-135>] - Refactor -
   Move WindupConfigurationModel#*ScanJavaPackages() etc to Java Basic module.
   - [WINDUP-152 <https://issues.jboss.org/browse/WINDUP-152>] - Add
   support for Map<String, String> in Frames to store in vertex'es properties.
   - [WINDUP-160 <https://issues.jboss.org/browse/WINDUP-160>] - Support
   implicit phases
   - [WINDUP-254 <https://issues.jboss.org/browse/WINDUP-254>] - Improve
   error message in RuleSubset.
   - [WINDUP-334 <https://issues.jboss.org/browse/WINDUP-334>] - windup.bat
   should use CRLF as the line separator

Feature Request

   - [WINDUP-167 <https://issues.jboss.org/browse/WINDUP-167>] - Check for
   duplicate @TypeValues
   - [WINDUP-183 <https://issues.jboss.org/browse/WINDUP-183>] - XML-based
   syntax for rules.
   - [WINDUP-218 <https://issues.jboss.org/browse/WINDUP-218>] - Further
   simplification of iteration in rules

Task

   - [WINDUP-181 <https://issues.jboss.org/browse/WINDUP-181>] - Separate
   ApplicationArchiveModel from ApplicationModel
   - [WINDUP-324 <https://issues.jboss.org/browse/WINDUP-324>] - Demo video
   with 2.0.0.Beta1 using dist standalone app (no Forge)
   - [WINDUP-327 <https://issues.jboss.org/browse/WINDUP-327>] - Set up
   Travis CI - automatic PR testing



-- 
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/20141017/f8aaf4c7/attachment.html 

From rruss at redhat.com  Tue Oct 21 15:46:04 2014
From: rruss at redhat.com (Rodney Russ)
Date: Tue, 21 Oct 2014 19:46:04 -0000
Subject: [windup-dev] Windup 2.0.0.Beta3 Released
In-Reply-To: <CAEp_U4HXXtQ-eUub2LENFYXG1GfaLUz+w+odUrVP6qkO1urYGA@mail.gmail.com>
References: <CAEp_U4HXXtQ-eUub2LENFYXG1GfaLUz+w+odUrVP6qkO1urYGA@mail.gmail.com>
Message-ID: <1277300487.212.1413920759998.JavaMail.rruss@MacBook-Pro.local>

Nice, only one bug in the last week? :) 

Great work on keeping the cadence! 

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

> From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com>
> To: "Windup-dev List" <windup-dev at lists.jboss.org>,
> windup-users at lists.jboss.org
> Cc: "Pete Muir" <pmuir at redhat.com>, "Tobias Hartwig"
> <thartwig at redhat.com>, "Robb Greathouse"
> <robb.greathouse at redhat.com>, "Rodney Russ" <rruss at redhat.com>
> Sent: Tuesday, October 21, 2014 12:04:57 PM
> Subject: Windup 2.0.0.Beta3 Released

> https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=releases&g=org.jboss.windup&a=windup-distribution&v=2.0.0.Beta3&e=zip&c=offline

> Bug

> * [ WINDUP-344 ] - Error running rule against exmple app

> Feature Request

> * [ WINDUP-217 ] - Short unique IDs for rulesets
> * [ WINDUP-352 ] - Windup should look for external rules files in
> dist/rules/ and ~/.windup/rules folders automatically

> Task

> * [ WINDUP-165 ] - Rename all test Models, Operations and Rules with
> Test~ prefix
> * [ WINDUP-184 ] - Unify the way to define Models' property name
> constants.

> --
> 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/20141021/fb8c377e/attachment.html 

From bgeorges at redhat.com  Sat Oct 18 08:18:18 2014
From: bgeorges at redhat.com (Bruno Georges)
Date: Sat, 18 Oct 2014 12:18:18 -0000
Subject: [windup-dev] Windup 2.0.0.Beta2 Released
In-Reply-To: <CAEp_U4ECrKu5nMJBxfRYgT-Xe1u_sX4txuFcxo0XDVzAqH4Kvw@mail.gmail.com>
References: <CAEp_U4ECrKu5nMJBxfRYgT-Xe1u_sX4txuFcxo0XDVzAqH4Kvw@mail.gmail.com>
Message-ID: <91605478-3C85-47DC-B203-DB58CD803824@redhat.com>

Congratulations to the entire Migration team.
I am very pleased with the progress. 

Keep up the great work.

Best Regards

Bruno. 

Sent from my iPhone

> On 17/10/2014, at 11:49 pm, Lincoln Baxter, III <lincolnbaxter at gmail.com> wrote:
> 
> https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=releases&g=org.jboss.windup&a=windup-distribution&v=2.0.0.Beta2&e=zip&c=offline
> 
> The whole team did a great job to get the bug-fixes, enhancements, and new features into this release!
> Bug
> [WINDUP-226] - Classification adds multiple fileModels even though they are the same
> [WINDUP-323] - More toString() methods are needed as this makes the rules easier to read/debug
> [WINDUP-326] - Rule blows up when running against SOA5 example.
> [WINDUP-339] - CssJsResourceRenderingRuleProvider does not appear to be copying files correctly on Windows
> [WINDUP-348] - Errors running Windup against EJB 2.1 example app
> Enhancement
> [WINDUP-135] - Refactor - Move WindupConfigurationModel#*ScanJavaPackages() etc to Java Basic module.
> [WINDUP-152] - Add support for Map<String, String> in Frames to store in vertex'es properties.
> [WINDUP-160] - Support implicit phases
> [WINDUP-254] - Improve error message in RuleSubset.
> [WINDUP-334] - windup.bat should use CRLF as the line separator
> Feature Request
> [WINDUP-167] - Check for duplicate @TypeValues
> [WINDUP-183] - XML-based syntax for rules.
> [WINDUP-218] - Further simplification of iteration in rules
> Task
> [WINDUP-181] - Separate ApplicationArchiveModel from ApplicationModel
> [WINDUP-324] - Demo video with 2.0.0.Beta1 using dist standalone app (no Forge)
> [WINDUP-327] - Set up Travis CI - automatic PR testing
> 
> 
> -- 
> 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/20141018/92d9af7c/attachment-0001.html