From itewksbu at redhat.com  Fri May  1 10:51:46 2015
From: itewksbu at redhat.com (Ian Tewksbury)
Date: Fri, 1 May 2015 10:51:46 -0400 (EDT)
Subject: [windup-dev] SOA-P Migration infinite log message
In-Reply-To: <1266279939.6434941.1430489955497.JavaMail.zimbra@redhat.com>
References: <1266279939.6434941.1430489955497.JavaMail.zimbra@redhat.com>
Message-ID: <A8CC6902-CA31-4A2C-9322-74EB32F97E64@redhat.com>

Shumon,

I am passing your question along to the windup DEV team mailing list.

Windup devs, can you please address  Shumon's question below.

-Ian

> On May 1, 2015, at 10:19 AM, Shumon Sharif <ssharif at redhat.com> wrote:
> 
> Hi Ian,
> 
> Hope you're doing well.  I am trying to use Windup to evaluate possibilities for a SOA-P migration.
> 
> I'm seeing the below print indefinitely - it kept printing for close to 2 hours, and I had to kill the process as it was time to go home.
> DOES THIS STILL HAPPEN?
> 
> I tracked down the log statement to the following class:
> https://github.com/windup/windup/blob/master/config/api/src/main/java/org/jboss/windup/config/parameters/ParameterizedGraphCondition.java
> 
> Could you please advise whether the log statement can be ignored?  Looking at the code, I'm almost certain that it's not stuck in a loop - and will break out eventually - but can I expect a full Windup analysis to still occur? 
> 
> Thanks so much!!
> 
> Shumon Sharif
> Senior Consultant, Red Hat
> 347-586-9611 (M)
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150501/453f6793/attachment.html 

From lincolnbaxter at gmail.com  Fri May  1 14:59:04 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 1 May 2015 14:59:04 -0400
Subject: [windup-dev] SOA-P Migration infinite log message
In-Reply-To: <A8CC6902-CA31-4A2C-9322-74EB32F97E64@redhat.com>
References: <1266279939.6434941.1430489955497.JavaMail.zimbra@redhat.com>
	<A8CC6902-CA31-4A2C-9322-74EB32F97E64@redhat.com>
Message-ID: <CAEp_U4H2MOe8Grs6BhNisVVmg=8JLVWCMoPxyMV1i3RpajP48Q@mail.gmail.com>

Hi Shumon,

It's not stuck in a loop, as you mentioned, but it's possible that it's
processing something *really* big.

It would help if we knew which files it were currently analyzing, so that
we could help more. (More coming in an offline email.)

~Lincoln

On Fri, May 1, 2015 at 10:51 AM, Ian Tewksbury <itewksbu at redhat.com> wrote:

> Shumon,
>
> I am passing your question along to the windup DEV team mailing list.
>
> Windup devs, can you please address  Shumon's question below.
>
> -Ian
>
> On May 1, 2015, at 10:19 AM, Shumon Sharif <ssharif at redhat.com> wrote:
>
> Hi Ian,
>
> Hope you're doing well.  I am trying to use Windup to evaluate
> possibilities for a SOA-P migration.
>
> I'm seeing the below print indefinitely - it kept printing for close to 2
> hours, and I had to kill the process as it was time to go home.
> DOES THIS STILL HAPPEN?
>
> I tracked down the log statement to the following class:
>
> https://github.com/windup/windup/blob/master/config/api/src/main/java/org/jboss/windup/config/parameters/ParameterizedGraphCondition.java
>
> Could you please advise whether the log statement can be ignored?  Looking
> at the code, I'm almost certain that it's not stuck in a loop - and will
> break out eventually - but can I expect a full Windup analysis to still
> occur?
>
> Thanks so much!!
>
> Shumon Sharif
> Senior Consultant, Red Hat
> 347-586-9611 (M)
>
>
> _______________________________________________
> 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/20150501/94110ebd/attachment-0001.html 

From lincolnbaxter at gmail.com  Fri May  1 15:23:35 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 1 May 2015 15:23:35 -0400
Subject: [windup-dev] Discussion of WildFly Legacy subsystem migration
Message-ID: <CAEp_U4EXeJi5t7KoRBS57oOFY0Bpk5fSfoOs3MqOLSdGqFQy+g@mail.gmail.com>

Hey Ondra, Matej,

Here is the thread on the wildfly-dev at lists.jboss.org email list that is
discussing the legacy migration functionality from the wildfly side of
things.

As you continue to build the server-migration functionality, could you two
please stay familiar with what is happening here and provide your thoughts
and ideas on what, if anything, we can use from this, and any changes you
think we might need them to make in order to make use of it?

http://wildfly-development.1055759.n5.nabble.com/Management-operation-for-legacy-subsystem-migration-td5715801.html

Thank you,
Lincoln

-- 
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/20150501/11760a9f/attachment.html 

From mbriskar at redhat.com  Mon May  4 07:14:53 2015
From: mbriskar at redhat.com (Matej Briskar)
Date: Mon, 4 May 2015 07:14:53 -0400 (EDT)
Subject: [windup-dev] Discussion of WildFly Legacy subsystem migration
In-Reply-To: <CAEp_U4EXeJi5t7KoRBS57oOFY0Bpk5fSfoOs3MqOLSdGqFQy+g@mail.gmail.com>
References: <CAEp_U4EXeJi5t7KoRBS57oOFY0Bpk5fSfoOs3MqOLSdGqFQy+g@mail.gmail.com>
Message-ID: <527986883.9075553.1430738093897.JavaMail.zimbra@redhat.com>

I was reading that, I am not sure I understand correctly everything, because there is a lot of different subsystems that I have never heard of.
I will need to study them so I have a basic understanding.

Are we going to migrate the data also now? (For example JMS)

----- Original Message -----
From: Lincoln Baxter, III <lincolnbaxter at gmail.com>
To: Windup-dev List <windup-dev at lists.jboss.org>, Ondra ?i?ka <ozizka at redhat.com>, Matej Briskar <mbriskar at redhat.com>
Sent: Fri, 01 May 2015 15:23:35 -0400 (EDT)
Subject: Discussion of WildFly Legacy subsystem migration

Hey Ondra, Matej,

Here is the thread on the wildfly-dev at lists.jboss.org email list that is
discussing the legacy migration functionality from the wildfly side of
things.

As you continue to build the server-migration functionality, could you two
please stay familiar with what is happening here and provide your thoughts
and ideas on what, if anything, we can use from this, and any changes you
think we might need them to make in order to make use of it?

http://wildfly-development.1055759.n5.nabble.com/Management-operation-for-legacy-subsystem-migration-td5715801.html

Thank you,
Lincoln

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



From lincolnbaxter at gmail.com  Mon May  4 15:19:01 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 4 May 2015 15:19:01 -0400
Subject: [windup-dev] Discussion of WildFly Legacy subsystem migration
In-Reply-To: <527986883.9075553.1430738093897.JavaMail.zimbra@redhat.com>
References: <CAEp_U4EXeJi5t7KoRBS57oOFY0Bpk5fSfoOs3MqOLSdGqFQy+g@mail.gmail.com>
	<527986883.9075553.1430738093897.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4HVefyBD1EjKkzPP3QCjOszcFA8x4nzJzock+nfabUinQ@mail.gmail.com>

No, I don't think we're worrying about migrating the data itself at this
point - that would be... another level of migration. All we are currently
worried about right now is the server configuration.

On Mon, May 4, 2015 at 7:14 AM, Matej Briskar <mbriskar at redhat.com> wrote:

> I was reading that, I am not sure I understand correctly everything,
> because there is a lot of different subsystems that I have never heard of.
> I will need to study them so I have a basic understanding.
>
> Are we going to migrate the data also now? (For example JMS)
>
> ----- Original Message -----
> From: Lincoln Baxter, III <lincolnbaxter at gmail.com>
> To: Windup-dev List <windup-dev at lists.jboss.org>, Ondra ?i?ka <
> ozizka at redhat.com>, Matej Briskar <mbriskar at redhat.com>
> Sent: Fri, 01 May 2015 15:23:35 -0400 (EDT)
> Subject: Discussion of WildFly Legacy subsystem migration
>
> Hey Ondra, Matej,
>
> Here is the thread on the wildfly-dev at lists.jboss.org email list that is
> discussing the legacy migration functionality from the wildfly side of
> things.
>
> As you continue to build the server-migration functionality, could you two
> please stay familiar with what is happening here and provide your thoughts
> and ideas on what, if anything, we can use from this, and any changes you
> think we might need them to make in order to make use of it?
>
>
> http://wildfly-development.1055759.n5.nabble.com/Management-operation-for-legacy-subsystem-migration-td5715801.html
>
> Thank you,
> Lincoln
>
> --
> 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/20150504/c87145bf/attachment.html 

From ozizka at redhat.com  Wed May  6 09:06:17 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 06 May 2015 15:06:17 +0200
Subject: [windup-dev] Performance of file lookup in archives
Message-ID: <554A11C9.5030302@redhat.com>

Hi all,

in the ArchiveService, a file lookup work like this:

    Get next path element; query all directory files vertices; iterate 
them and find the one which matches the path element; get next path element.

That's quite inefficient way to do that. It should query for the vertex 
by a query using the name, which is indexed.

I guess that's in the area of what Jess is working on now?

Ondra

From lincolnbaxter at gmail.com  Wed May  6 11:20:18 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 6 May 2015 11:20:18 -0400
Subject: [windup-dev] Windup meeting minutes - 2015-05-05
Message-ID: <CAEp_U4Ew7HQ0Pj38zGvmfby2svhzcHQ-OWdY3rtZosYP0QWsUg@mail.gmail.com>

Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-05-06-14.03.html

Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-05-06-14.03.txt

Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-05-06-14.03.log.html

Meeting summary
---------------
* Agenda  (lincolnthree, 14:03:31)

* Status Reports  (lincolnthree, 14:08:23)
  * WINDUP-566  (ozizka, 14:10:17)
  * (WIP)  (ozizka, 14:10:27)
  * Friday was Holiday here in CZ and I took PTO on monday  (ozizka,
    14:11:38)
  * I did a performance tests for Property vs. edge, it looks like
    property is faster and cleaner  (mbriskar_, 14:12:13)
  * studying wildfly 8 docs to be able to work on server migration
    afterwards  (mbriskar_, 14:12:28)
  * I have been working on preparing the summit materials with Brad
    (lincolnthree, 14:12:42)
  * I reviewed the training lab materials at the request of thartwig
    (lincolnthree, 14:12:42)
  * I've reviewed / merged several PRs  (lincolnthree, 14:12:42)
  * I've been fixing some of the issues that I found during the summit
    preparation  (lincolnthree, 14:12:42)
  * I've also been working on some of the AST performance stuff, but
    making debatable progress  (lincolnthree, 14:12:42)
  * Due to possible name change, tested use of variables for product
    name. Found and reported on a number of issues.  (sgilda, 14:16:23)
  * Started marking empty Wiki pages with an 'OBSOLETE-' prefix
    (sgilda, 14:16:23)
  * Planning to go through the Windup training materials  (sgilda,
    14:16:23)
  * I have worked on type interest factory optimization, changing the
    unzip procedure to not unzip all the files (the leaf nodes remain
    zipped), and on finishing up lincoln's batch ast  (jsightler,
    14:17:29)
  * This week, I plan to finish up the batch ast, and then do testing on
    the unzip changes  (jsightler, 14:17:44)

* Priorities  (lincolnthree, 14:17:51)
  * Server configuration - discussion to follow in next topic
    (lincolnthree, 14:19:39)
  * Performance - ongoing, we've done quite a bit here, but still have
    room to improve in the AST.  (lincolnthree, 14:19:59)
  * Quickstarts and Examples - Still unstarted  (lincolnthree, 14:20:12)
  * Eclipse Plugin - mostly finished, just need to see what is going on
    with file markers  (lincolnthree, 14:20:29)

* Server configuration discussion  (lincolnthree, 14:20:47)
  * Server identification is done  (lincolnthree, 14:22:22)
  * Changes in WINDUP-566 still required to be able to process the
    server files without conflicting with existing rules  (lincolnthree,
    14:22:43)
  * Matej is looking in to Wildfly CLI, how it works, how to use it to
    configure the server  (lincolnthree, 14:23:13)
  * Next steps ? Create operations / functionality that will store
    operations in the graph and mimic CLI functionality  (lincolnthree,
    14:24:51)
  * Next steps - Limit existing rules to operate on application files
    only.  (lincolnthree, 14:25:26)
  * Next steps - Then can begin creating conditions to query the source
    platforms and gather information and create rules to do the actual
    server migration.  (lincolnthree, 14:27:44)
  * ACTION: Lincoln needs to find out which server should focused on
    first  (lincolnthree, 14:27:56)
  * Then the information will need to be added to the report to display
    hints/steps/links of what was done/still needs to be done. (if
    something could not be configured by Windup)  (lincolnthree,
    14:28:49)
  * LINK: irc://irc.freenode.net:6667/#addtopic WINDUP-566 and Jess's
    work  (lincolnthree, 14:30:38)

* WINDUP-566 and Jess's work  (lincolnthree, 14:30:50)
  * LINK:
    http://wildfly-development.1055759.n5.nabble.com/Management-operation-for-legacy-subsystem-migration-td5715801.html
    (lincolnthree, 15:13:06)

Meeting ended at 15:17:57 UTC.




Action Items
------------
* Lincoln needs to find out which server should focused on first




Action Items, by person
-----------------------
* **UNASSIGNED**
  * Lincoln needs to find out which server should focused on first




People Present (lines said)
---------------------------
* lincolnthree (36)
* jbott (10)
* ozizka (8)
* sgilda (7)
* jbossbot (7)
* mbriskar_ (5)
* jsightler (3)
* mbriskar (0)
* ozizka- (0)


-- 
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/20150506/91fb1f13/attachment.html 

From ozizka at redhat.com  Wed May  6 11:47:41 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 06 May 2015 17:47:41 +0200
Subject: [windup-dev] Rules and Ruleset filtering (how to prevent app rules
 from running on server)
Message-ID: <554A379D.8060203@redhat.com>

Hi all,

for the approach using rules filtering, we need to:

1) Add the proper metadata to all app-only rules,
2) Figure out how to determine whether we are scanning a server or 
something else,
3) Update the filtering mechanism to support "exclude" and "include" 
filters.


Ad 1)  This includes Java-based rules and XML-based rules.

Ad 2)
    a) Either scan using server identification
    b) Use different user parameter, like, --serverPath instead of 
--inputPath.

    Ad a) In case we would not identify the server, app rules would run, 
and the result would be interesting but unexpected.
             Also, it would need a change in the filter API, so we could 
dynamically change the RuleProvider filters when already executing 
RuleProviders.
             That might lead to future problems when we do some 
preprocessing of RuleProviders, i.e. creating a list of those which will 
run prior to executing them, which I think is likely to happen in the 
future.

    Ad b) This is what I  currently have implemented for the server 
ident rules.

Ad 3) I think good enough solution could be some kind of 
MetadataExcludeRuleProviderFilter, which would say "no" to anything that 
has tag "xyz".

WDYT?
Ondra

From ozizka at redhat.com  Mon May 11 08:44:10 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 11 May 2015 14:44:10 +0200
Subject: [windup-dev] Discussion of WildFly Legacy subsystem migration
In-Reply-To: <CAEp_U4EXeJi5t7KoRBS57oOFY0Bpk5fSfoOs3MqOLSdGqFQy+g@mail.gmail.com>
References: <CAEp_U4EXeJi5t7KoRBS57oOFY0Bpk5fSfoOs3MqOLSdGqFQy+g@mail.gmail.com>
Message-ID: <5550A41A.9070309@redhat.com>

Is it now Jeff working on that migration code?
Or is it like before, which means, individual subsystems take care of 
their own migration, only this time it's through a :migrate operation?
And Eduardo's code will call that in a batch?

I guess these are questions for WildFly team anyway.

Ondra



On 1.5.2015 21:23, Lincoln Baxter, III wrote:
> Hey Ondra, Matej,
>
> Here is the thread on the wildfly-dev at lists.jboss.org 
> <mailto:wildfly-dev at lists.jboss.org> email list that is discussing the 
> legacy migration functionality from the wildfly side of things.
>
> As you continue to build the server-migration functionality, could you 
> two please stay familiar with what is happening here and provide your 
> thoughts and ideas on what, if anything, we can use from this, and any 
> changes you think we might need them to make in order to make use of it?
>
> http://wildfly-development.1055759.n5.nabble.com/Management-operation-for-legacy-subsystem-migration-td5715801.html
>
> Thank you,
> Lincoln
>
> -- 
> 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/20150511/75fed1fe/attachment.html 

From lincolnbaxter at gmail.com  Wed May 20 10:15:13 2015
From: lincolnbaxter at gmail.com (lincolnbaxter at gmail.com)
Date: Wed, 20 May 2015 14:15:13 +0000
Subject: [windup-dev] Updated Invitation: Windup Status Meeting @ Weekly
 from 10am to 11am on Wednesday (Windup Project Calendar)
Message-ID: <f46d044287ca3089d20516840e5f@google.com>

This event has been changed.

Title: Windup Status Meeting
When: Weekly from 10am to 11am on Wednesday Eastern Time (changed)
Where: #windup on irc.freenode.net
Calendar: Windup Project Calendar
Who:
     * Lincoln Baxter, III - creator
     * windup-dev at lists.jboss.org
     * jsightle at redhat.com
     * Ondra ?i?ka
     * Robb Greathouse
     * pmuir at redhat.com
     * Robb Greathouse
     * Jesse Sightler
     * Brad Davis
     * bgeorges at redhat.com

Event details:  
https://www.google.com/calendar/event?action=VIEW&eid=cGpqZ2tvdmNxbmIydWJlZjFhYXVjZXJsZ28gd2luZHVwLWRldkBsaXN0cy5qYm9zcy5vcmc&tok=NTIjbThxYjFhZTZyYTJtZWZqNmc4Y2c3bHVlOTRAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbWEyODJmNmRhZmNjZTBmOWM0NDhhMmQ2MWI5MDZjNTRiZGExYzY2ZTI&ctz=America/New_York&hl=en

Invitation from Google Calendar: https://www.google.com/calendar/

You are receiving this courtesy email at the account  
windup-dev at lists.jboss.org because you are an attendee of this event.

To stop receiving future updates for this event, decline this event.  
Alternatively you can sign up for a Google account at  
https://www.google.com/calendar/ and control your notification settings for  
your entire calendar.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150520/da1c08d8/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 2586 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150520/da1c08d8/attachment-0002.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: application/ics
Size: 2649 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150520/da1c08d8/attachment-0003.bin 

From lincolnbaxter at gmail.com  Wed May 20 10:15:13 2015
From: lincolnbaxter at gmail.com (lincolnbaxter at gmail.com)
Date: Wed, 20 May 2015 14:15:13 +0000
Subject: [windup-dev] Updated Invitation: Windup Status Meeting @ Weekly
 from 11am to 12pm on Wednesday from Wed May 13 to Tue May 19 (Windup
 Project Calendar)
Message-ID: <f46d04374a0d3122960516840e62@google.com>

This event has been changed.

Title: Windup Status Meeting
When: Weekly from 11am to 12pm on Wednesday from Wed May 13 to Tue May 19  
Eastern Time (changed)
Where: #windup on irc.freenode.net
Calendar: Windup Project Calendar
Who:
     * Lincoln Baxter, III - creator
     * windup-dev at lists.jboss.org
     * jsightle at redhat.com
     * Ondra ?i?ka
     * Robb Greathouse
     * pmuir at redhat.com
     * Robb Greathouse
     * Jesse Sightler
     * Brad Davis
     * bgeorges at redhat.com

Event details:  
https://www.google.com/calendar/event?action=VIEW&eid=dDRoOGZqbHE0ZGljZ2dtcXFpc2RsZzh2ZGcgd2luZHVwLWRldkBsaXN0cy5qYm9zcy5vcmc&tok=NTIjbThxYjFhZTZyYTJtZWZqNmc4Y2c3bHVlOTRAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbWE1YThjYmEyZmVhYTBlNGVhZDQ4YWQwOGM0MTFhYmYzODA5YWMyMDI&ctz=America/New_York&hl=en

Invitation from Google Calendar: https://www.google.com/calendar/

You are receiving this courtesy email at the account  
windup-dev at lists.jboss.org because you are an attendee of this event.

To stop receiving future updates for this event, decline this event.  
Alternatively you can sign up for a Google account at  
https://www.google.com/calendar/ and control your notification settings for  
your entire calendar.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150520/6663e8ea/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 2598 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150520/6663e8ea/attachment-0002.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: application/ics
Size: 2661 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150520/6663e8ea/attachment-0003.bin 

From lincolnbaxter at gmail.com  Wed May 20 10:42:39 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 20 May 2015 10:42:39 -0400
Subject: [windup-dev] Windup meeting minutes - 2015-05-20
Message-ID: <CAEp_U4HkkhaktBQnUYWZ6f9otDMFnV1EEg-nFPTSHKb+Tihvsg@mail.gmail.com>

Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-05-20-14.12.html

Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-05-20-14.12.txt

Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-05-20-14.12.log.html

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



* Status reports  (lincolnthree, 14:29:02)

* LINK: https://plus.google.com/hangouts/_/gu6zkbb3tqudeao22m2yj6iu4ma?hl=en
(ozizka, 14:13:49) * WINDUP-592 and WINDUP-592, both done but not yet
tried, (ozizka, 14:17:44) * jira [WINDUP-592] Console UI WARNING if no
"customer packages" specified [Pull Request Sent (Unresolved) Enhancement,
Major, Ondrej Zizka] (ozizka, 14:18:03) * Correction: WINDUP-595 (ozizka,
14:18:14) * [WINDUP-595] If file size is >10 MB, display a warning - "this
may take a long time." [Pull Request Sent (Unresolved) Enhancement, Major,
Ondrej Zizka] (ozizka, 14:18:27) * Working on the Rules Development Guide.
Added a "Write Your First Rule" topic and removed the instructions for
Java-based rules (sgilda, 14:20:51) * last week we were at the F2F meeting,
so we worked a lot on requirements gathering and goal setting for the
project. we also worked out a plan for being ready for summit.
(lincolnthree, 14:20:55) * this week I have been working on catching up
with project emails (lincolnthree, 14:20:55) * worked with brad on a
feature for JBPM reporting (lincolnthree, 14:20:55) * going to finish the
rule quality definition today and also continue merging some PRs
(lincolnthree, 14:20:55) * Updating the User and Rules guide topic screen
shots to match the latest Windup executions. (sgilda, 14:21:35) * Will try
to get builds on DocStage in the next few days so they are available for
review. (sgilda, 14:22:04) * WINDUP-589 - Incorrect lines highlighted by
xpath -- rules fixes PR sent (jsightler, 14:26:51) * I have worked on some
pull request review, testing issues from Zottner (the ones that are not
rules related were already fixed in master).... (jsightler, 14:27:28) * And
I am starting to work on WINDUP-415 (better progress monitoring)
(jsightler, 14:28:26) * Once we get the "good rule" definition, I would
like to assist with getting that planned out and start to work on rules and
tests (jsightler, 14:28:27) * I worked on XSD Schema, it is already merged
and updated. I updated documentation to write there a way how to run xsd on
the whole directory of the rules (using some external java open-source
projects that runs xerces) (mbriskar, 14:29:03) * Summit preparation
(lincolnthree, 14:29:12) * I was experimenting with XMLFile but without any
improvement (mbriskar, 14:29:21) * My plan: Test my PR's practically, and
then "adjust existing and implement new reports" from F2F action list for
summit. (ozizka, 14:30:54) * We will begin reviewing rules as soon as I
have finished the "Rule quality definition" (lincolnthree, 14:32:02) *
LINK:
https://github.com/forge/furnace/blob/master/container/src/main/java/org/jboss/forge/furnace/impl/FurnaceImpl.java#L63
(lincolnthree, 14:33:54)

  * ACTION: For "adjust existing and implement new reports", I will post
    to jboss-migration-team@, asking for input on what should be done.
    (ozizka, 14:40:12)
  * ACTION: Lincoln will complete rule quality definition and send to
    the team today with a plan for how to break up the work and
    implement it.  (lincolnthree, 14:40:53)

Meeting ended at 14:40:57 UTC.




Action Items
------------
* For "adjust existing and implement new reports", I will post to
  jboss-migration-team@, asking for input on what should be done.
* Lincoln will complete rule quality definition and send to the team
  today with a plan for how to break up the work and implement it.

-- 
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/20150520/96b2e6cf/attachment.html 

From lincolnbaxter at gmail.com  Fri May 22 11:50:04 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 22 May 2015 11:50:04 -0400
Subject: [windup-dev] Schema tweaks
Message-ID: <CAEp_U4ECiQ_Cbnu4K6xMZAAhUMZ6ts4_Bfm-7AyqnEt_C43nkw@mail.gmail.com>

Hey Matej,

I'm going through the XML schema, I'll let you know what tweaks we need.
Looks like there are still a few missing elements:

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

~Lincoln

-- 
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/20150522/69f84bcb/attachment.html 

From ozizka at redhat.com  Mon May 25 13:18:12 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 25 May 2015 19:18:12 +0200
Subject: [windup-dev] Namespaces and URLs
Message-ID: <55635954.7010703@redhat.com>

Hi,

the namespaces, filenames and URLs need to be informative and "scale" in 
the future.

1) It needs to say windup, so people know what namespace they are 
dealing with.

2) Same goes for the filename - when people download it. Therefore, 
rule-schema-1.0.xsd is not good IMO.

3) I suggest to align the XSD version with the Windup core version, 
since the XSD describes what the core accepts.
     "1.0" is not fortunate, as people will confuse it with legacy Windup.
     The version string should be the same as Windup version, so we can 
automate things. Different formats are source of human errors.

4) It doesn't need to say "schema" - XSD is saying that.

5) It's not rule - it's a ruleset. Could be misleading.

I suggest the URL for the current XSD to be:
     http://windup.jboss.org/schema/windup-ruleset-2.3.0.Final.xsd

And the namespace:
     Either the same,
     http://windup.jboss.org/schema/windup-ruleset-2.3.0.Final.xsd
     or,
     http://windup.jboss.org/ns/ruleset/2.3.0.Final , and that would be 
handled by the site (e.g., redirect to docs).

Sounds good?
Ondra

From ozizka at redhat.com  Mon May 25 13:33:52 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Mon, 25 May 2015 19:33:52 +0200
Subject: [windup-dev] Sugested Fix Hints
In-Reply-To: <CAEp_U4HM-kCuu9hrt0LAiP7NKe1_y8pVWyVrNvU_ymd7R_hcPg@mail.gmail.com>
References: <34285553.4971460.1430137378250.JavaMail.zimbra@redhat.com>	<941980513.4971941.1430137452508.JavaMail.zimbra@redhat.com>	<CAEp_U4E1yh3bx=L0T82D+TCFucCaojOmHMyy7gEeADO7RNcDpQ@mail.gmail.com>	<1602348342.5867308.1430237851491.JavaMail.zimbra@redhat.com>
	<CAEp_U4HM-kCuu9hrt0LAiP7NKe1_y8pVWyVrNvU_ymd7R_hcPg@mail.gmail.com>
Message-ID: <55635D00.4060203@redhat.com>

IIUC, one of cases is when a custom API becomes standardized.  I.e. 
com.ibm.javax.foo.Bar  ->  javax.foo.Bar.
E.g. com.ibm.ws.javax.activity.*   (not sure, but looks like that's what 
happened with it)

Ondra




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

From mnovotny at redhat.com  Tue May 26 06:46:10 2015
From: mnovotny at redhat.com (Marek Novotny)
Date: Tue, 26 May 2015 12:46:10 +0200
Subject: [windup-dev] Namespaces and URLs
In-Reply-To: <55635954.7010703@redhat.com>
References: <55635954.7010703@redhat.com>
Message-ID: <55644EF2.6020307@redhat.com>

On 25.5.2015 19:18, Ondrej Zizka wrote:
> Hi,
> 
> the namespaces, filenames and URLs need to be informative and "scale" in 
> the future.
> 
> 1) It needs to say windup, so people know what namespace they are 
> dealing with.
> 
> 2) Same goes for the filename - when people download it. Therefore, 
> rule-schema-1.0.xsd is not good IMO.
> 
> 3) I suggest to align the XSD version with the Windup core version, 
> since the XSD describes what the core accepts.
>      "1.0" is not fortunate, as people will confuse it with legacy Windup.
>      The version string should be the same as Windup version, so we can 
> automate things. Different formats are source of human errors.
> 
> 4) It doesn't need to say "schema" - XSD is saying that.
> 
> 5) It's not rule - it's a ruleset. Could be misleading.
> 
> I suggest the URL for the current XSD to be:
>      http://windup.jboss.org/schema/windup-ruleset-2.3.0.Final.xsd
> 
> And the namespace:
>      Either the same,
>      http://windup.jboss.org/schema/windup-ruleset-2.3.0.Final.xsd
>      or,
>      http://windup.jboss.org/ns/ruleset/2.3.0.Final , and that would be 
> handled by the site (e.g., redirect to docs).
I am not really sure if it is good idea to have version in namespace
> 
> Sounds good?
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
> 

I would agree with almost all, but why won't we have so long version
string in that filename/schema?

micro version identificator is imho not necessary as you should not
change the schema in micro releases.
So http://windup.jboss.org/schema/windup-ruleset-2_3.xsd should work
better IMO.

-- 
Marek Novotny
--
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno

From sgilda at redhat.com  Tue May 26 14:13:18 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Tue, 26 May 2015 14:13:18 -0400
Subject: [windup-dev] Namespaces and URLs
In-Reply-To: <55644EF2.6020307@redhat.com>
References: <55635954.7010703@redhat.com> <55644EF2.6020307@redhat.com>
Message-ID: <5564B7BE.1060503@redhat.com>

Hi Marek,



On 05/26/2015 06:46 AM, Marek Novotny wrote:
> On 25.5.2015 19:18, Ondrej Zizka wrote:
>> Hi,
>>
>> the namespaces, filenames and URLs need to be informative and "scale" in
>> the future.
>>
>> 1) It needs to say windup, so people know what namespace they are
>> dealing with.
Agreed.
>>
>> 2) Same goes for the filename - when people download it. Therefore,
>> rule-schema-1.0.xsd is not good IMO.
Agreed.
>>
>> 3) I suggest to align the XSD version with the Windup core version,
>> since the XSD describes what the core accepts.
>>       "1.0" is not fortunate, as people will confuse it with legacy Windup.
>>       The version string should be the same as Windup version, so we can
>> automate things. Different formats are source of human errors.
I went with _1_0.xsd to follow the patterns JBoss uses. If you look in 
http://www.jboss.org/schema/jbossas/, you'll see none of the JBoss 
related schemas use the JBoss EAP release number. For example:

http://www.jboss.org/schema/jbossas/jboss-as-mail_1_1.xsd
http://www.jboss.org/schema/jbossas/jboss-as-logging_2_0.xsd
http://www.jboss.org/schema/jbossas/jboss-deployment-structure-1_2.xsd
http://www.jboss.org/schema/jbossas/jboss-ejb-client_1_2.xsd

Will the schema change with every release of Windup? I would expect it 
to be more stable than that.

Won't it be a maintenance nightmare to update the rules schema location 
in the XML for the rules for every release?
>> 4) It doesn't need to say "schema" - XSD is saying that.
Agreed.
>>
>> 5) It's not rule - it's a ruleset. Could be misleading.
>>
>> I suggest the URL for the current XSD to be:
>>       http://windup.jboss.org/schema/windup-ruleset-2.3.0.Final.xsd
Again, I'm not sure I like using the Windup release and I definitely 
don't like the 'Final'.
I'd prefer windup-ruleset_1_0.xsd or something like that.
>> And the namespace:
>>       Either the same,
>>       http://windup.jboss.org/schema/windup-ruleset-2.3.0.Final.xsd
>>       or,
>>       http://windup.jboss.org/ns/ruleset/2.3.0.Final , and that would be
>> handled by the site (e.g., redirect to docs).
> I am not really sure if it is good idea to have version in namespace
>> Sounds good?
>> Ondra
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
> I would agree with almost all, but why won't we have so long version
> string in that filename/schema?
>
> micro version identificator is imho not necessary as you should not
> change the schema in micro releases.
> So http://windup.jboss.org/schema/windup-ruleset-2_3.xsd should work
> better IMO.
>


From ozizka at redhat.com  Tue May 26 20:46:55 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 27 May 2015 02:46:55 +0200
Subject: [windup-dev] Namespaces and URLs
In-Reply-To: <5564B7BE.1060503@redhat.com>
References: <55635954.7010703@redhat.com> <55644EF2.6020307@redhat.com>
	<5564B7BE.1060503@redhat.com>
Message-ID: <556513FF.2050905@redhat.com>

Hi Sande, Marek,

I know that all are used to -X_Y, but IMO it's a wrong tradition, let me 
explain why.

The rule schema rules location will change with every change of the 
schema. The older schema needs to stay where it is. The old rules will 
refer to that schema. We might change our rules, but those rules which 
are outside our reach will have to refer to a valid schema URL.

I remember that in QE dept, these a-b_c-D-e_F.G_h schemas were a source 
of bugs surprisingly often. Even your examples are inconsistent:

http://www.jboss.org/schema/jbossas/jboss-as-logging_2_0.xsd
http://www.jboss.org/schema/jbossas/jboss-deployment-structure-1_2.xsd


Nobody really can tell why there's a - or _ or . .
If we simply use the same version string and only use '-' before it, 
it's all clear.
And, as I said - *the schema only expresses the constraint that is 
effectively inside of the released implementation*. So it's  really 
*directly related to the particular release*.

The fact that we would use 2.3.0.Final for a XSD url or namespace 
doesn't imply or suggest that it has to change for every release. The 
string is in 2 places so far, in general:
1) The Windup source, where it should be a single constant in 
config-xml, referenced form it's dependees.
2) The XML rules, where it can simply stay the same until next review of 
the rule.

Therefore I don't think it would create any maintainance that would not 
be needed if we use arbitrary version string scheme.

The only reason I can see to keep 1_1 is to align with what someone 
coined up 10 years ago, which for me equals to sticking to a wrong 
solution. YMMV :)

>> I am not really sure if it is good idea to have version in namespace
Is there some other way for versioning the schema and the rules?


On 26.5.2015 20:13, Sande Gilda wrote:
>>> 3) I suggest to align the XSD version with the Windup core version,
>>> since the XSD describes what the core accepts.
>>>        "1.0" is not fortunate, as people will confuse it with legacy Windup.
>>>        The version string should be the same as Windup version, so we can
>>> automate things. Different formats are source of human errors.
> I went with _1_0.xsd to follow the patterns JBoss uses. If you look in
> http://www.jboss.org/schema/jbossas/, you'll see none of the JBoss
> related schemas use the JBoss EAP release number. For example:
>
> http://www.jboss.org/schema/jbossas/jboss-as-mail_1_1.xsd
> http://www.jboss.org/schema/jbossas/jboss-as-logging_2_0.xsd
> http://www.jboss.org/schema/jbossas/jboss-deployment-structure-1_2.xsd
> http://www.jboss.org/schema/jbossas/jboss-ejb-client_1_2.xsd
>
> Will the schema change with every release of Windup? I would expect it
> to be more stable than that.
>
> Won't it be a maintenance nightmare to update the rules schema location
> in the XML for the rules for every release?


From ozizka at redhat.com  Tue May 26 20:53:44 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 27 May 2015 02:53:44 +0200
Subject: [windup-dev] Building and installing whole Windup
	(windup-distribution)
In-Reply-To: <553E4886.4000901@redhat.com>
References: <297971927.4700897.1429969044617.JavaMail.zimbra@redhat.com>	<328794499.4701305.1429969643677.JavaMail.zimbra@redhat.com>	<484943168.4701566.1429971167539.JavaMail.zimbra@redhat.com>	<CAEp_U4FAuFbCftWiE2uFLSitf+3aSFAvbZXK-PW9AYQiCWiykw@mail.gmail.com>	<553E1622.5080406@redhat.com>	<1185704303.4971101.1430137294031.JavaMail.zimbra@redhat.com>	<553E2E7F.4080303@redhat.com>
	<553E4886.4000901@redhat.com>
Message-ID: <55651598.60003@redhat.com>

Hi all,

building the whole Windup from scratch is a bit trickier than just 2 
modules.
Try to build with -Dmaven.repo.local=localRepo and you'll get into troubles.

I have tried to address this with windup-umbrella, and used git's 
submodules for it.
However there are some issues with it - not just that it's not usable 
for committing / pushing, but even just fetching all the submodules 
doesn't work for me.

Still, that solution looks good to me at least for getting all most 
recent artifact one needs for building Windup, instead of going around 
in circles, figuring out what's missing now and where is its repo.
So I am reaching out to git experts to tell me what's wrong with 
windup-umbrella.

Regards,
Ondra



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

From ozizka at redhat.com  Wed May 27 09:16:44 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 27 May 2015 15:16:44 +0200
Subject: [windup-dev] Windup rule IDs scheme
In-Reply-To: <1833E791-7DDE-4997-9EC7-F0AC1FF49E20@redhat.com>
References: <556526A4.3040608@redhat.com>
	<1833E791-7DDE-4997-9EC7-F0AC1FF49E20@redhat.com>
Message-ID: <5565C3BC.7010603@redhat.com>

Correct, apologies :) Moving

On 27.5.2015 13:46, Pete Muir wrote:
> Exactly the kind of discussion that *doesn?t* need to be on 
> jboss-migration-team. There is nothing confidential here, probably 
> nothing internal. I would move this to windup-dev?
>
>> On 27 May 2015, at 03:06, Ondrej Zizka <ozizka at redhat.com 
>> <mailto:ozizka at redhat.com>> wrote:
>>
>> (19:45:09) LincolnThree: *ok guys/gal, let's discuss rule ID syntax 
>> (ozizka, jsightler, sgilda)*
>> (19:45:15) LincolnThree: we need a standard
>> (19:45:23) sgilda: yes, we do
>> (19:45:45) LincolnThree: I think we have a few things to consider:
>> (19:45:48) LincolnThree: 1) uniqueness
>> (19:45:51) LincolnThree: 2) descriptiveness
>> (19:45:58) LincolnThree: anything else?
>> (19:46:06) LincolnThree: 3) searchability
>> (19:46:39) LincolnThree: or we can discuss this tomorrow during the 
>> meeting.
>>
>> Sorry, I missed that conversation.
>> My view:
>>
>> 1) Uniqueness, no doubt.
>> 2) Decriptiveness - to a minimal level.  It will be useful when 
>> getting user feedback (bugs, I suspect :)
>>
>> So that when something goes wrong and the user will send the 
>> stacktrace, we will know what rule caused it right away.
>>
>> 3) Searchability - I'd rely on metadata for searches.
>>
>> Additionally, an ID could contain the main source and target technology.
>>
>>
>> E.g.  "weblogic>eap:asynchbeans.Work-6bcvk" for
>>
>>         <rule id="weblogic>eap:asynchbeans.Work-6bcvk">
>>             <when>
>>                 <javaclass 
>> references="com.ibm.websphere.asynchbeans.Work" as="default">
>> <location>INHERITANCE</location>
>>                 </javaclass>
>>             </when>
>>
>

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

From jsightle at redhat.com  Wed May 27 09:34:49 2015
From: jsightle at redhat.com (Jess Sightler)
Date: Wed, 27 May 2015 09:34:49 -0400
Subject: [windup-dev] Windup rule IDs scheme
In-Reply-To: <5565C3BC.7010603@redhat.com>
References: <556526A4.3040608@redhat.com>	<1833E791-7DDE-4997-9EC7-F0AC1FF49E20@redhat.com>
	<5565C3BC.7010603@redhat.com>
Message-ID: <5565C7F9.1070505@redhat.com>



On 05/27/2015 09:16 AM, Ondrej Zizka wrote:
>
>>
>>> On 27 May 2015, at 03:06, Ondrej Zizka <ozizka at redhat.com 
>>> <mailto:ozizka at redhat.com>> wrote:
>>>
>>> (19:45:09) LincolnThree: *ok guys/gal, let's discuss rule ID syntax 
>>> (ozizka, jsightler, sgilda)*
>>> (19:45:15) LincolnThree: we need a standard
>>> (19:45:23) sgilda: yes, we do
>>> (19:45:45) LincolnThree: I think we have a few things to consider:
>>> (19:45:48) LincolnThree: 1) uniqueness
>>> (19:45:51) LincolnThree: 2) descriptiveness
>>> (19:45:58) LincolnThree: anything else?
>>> (19:46:06) LincolnThree: 3) searchability
>>> (19:46:39) LincolnThree: or we can discuss this tomorrow during the 
>>> meeting.
>>>
>>> Sorry, I missed that conversation.
>>> My view:
>>>
>>> 1) Uniqueness, no doubt.
>>> 2) Decriptiveness - to a minimal level.  It will be useful when 
>>> getting user feedback (bugs, I suspect :)
>>>
>>> So that when something goes wrong and the user will send the 
>>> stacktrace, we will know what rule caused it right away.

This is exactly what we mean by searchability. If you have the rule id, 
it should be easy to find the rule itself.

>>> E.g. "weblogic>eap:asynchbeans.Work-6bcvk" for
>>>
>>>         <rule id="weblogic>eap:asynchbeans.Work-6bcvk">
>>>             <when>
>>>                 <javaclass 
>>> references="com.ibm.websphere.asynchbeans.Work" as="default">
>>> <location>INHERITANCE</location>
>>>                 </javaclass>
>>>             </when>
>>>
>>

In theory, I think this is great, but in practice I think it will be 
very awkward. For example, your example has a ">" in it, which can often 
cause complications. I'd prefer something simple, unique, searchable, 
and easy to use as a global id (for example, even in HTML at times) over 
hoping that we can always have some great semantic meaning in and of itself.

Just my $.02 :)

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

From lincolnbaxter at gmail.com  Wed May 27 13:10:22 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 27 May 2015 13:10:22 -0400
Subject: [windup-dev] Windup Meeting Minutes - 2015-05-27
Message-ID: <CAEp_U4HdivTZvdaBM3BFxHbHu33YaHwqRRN9OKEDo4rye6F0OA@mail.gmail.com>

Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-05-27-14.03.html

Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-05-27-14.03.txt

Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-05-27-14.03.log.html
Meeting summary
---------------
* Agenda  (lincolnthree, 14:05:10)

* Status Reports  (lincolnthree, 14:07:43)
  * Worked on rule review, finishing defining requirements around "what
    makes a good rule", also touched up the required metadata and
    information for rules. I will be working on PRs today, then back on
    rule review.  (lincolnthree, 14:11:16)
  * - Started working on Rule Review  (jsightler, 14:11:49)
  * I also worked on fixing mbriskar's parameterization bug that he
    found, which meant releasing a new version of Rewrite, currently
    working on snapshot, still need to release an actual version before
    we can cut a releaase of windup  (lincolnthree, 14:11:53)
  * Removed Java rule information from the Rules Development Guide
    (sgilda, 14:11:55)
  * Updated the quickstarts to replace deprecated code and updated the
    XML rules to include schema information.  (sgilda, 14:11:56)
  * - I have found a bug in the ast handling that was breaking a few
    rules, so I have sent a PR for that  (jsightler, 14:12:09)
  * - Also, I have a windup-rulesets pr nearly ready to make it possible
    to test in the rules-reviewed folder  (jsightler, 14:12:44)
  * Worked on WINDUP-611, WINDUP-612. The main task is WINDUP-610.
    (ozizka, 14:13:05)
  * During that, I did some research about what the rules are like, what
    do they cover, what are the typical sources covering the topics, how
    to capture them in the rules.  (ozizka, 14:13:05)
  * Then some administrative things like WINDUPRULES- jira, looking
    around in salesforce, getting my RH KB access, and put few ideas to
    mailing list and to jira.  (ozizka, 14:13:05)
  * went through

https://docs.google.com/spreadsheets/d/1XJ1LNqhtT8ijZTFROx5OjezOii8TBDI4Us7M9q1rQLo/edit#gid=0
    and reviewing xml rules  (marekn, 14:13:23)
  * LINK:

https://docs.google.com/spreadsheets/d/1hJCTf5U4XNnN795MuQXgFGHK0aj3ZG6daGpydPq6DdU/edit#gid=0
    (lincolnthree, 14:19:39)
  * worked on WINDUP-596, specifically on tests/fixes. There is PR and
    will probably need some small adjustments  (mbriskar_, 14:20:07)
  * went through "Migration Guide Rules Spreadsheet" and helped adding
    new rules or eliminating duplicates etc.  (mbriskar_, 14:20:51)
  * : Updated the XML rules documentation to include latest schema
    information  (sgilda, 14:28:05)

* Rule ID conventions for rule review  (lincolnthree, 14:32:26)
  * AGREED: Rule ID == ruleset_id + unique_ID  (lincolnthree, 14:48:17)
  * VOTE DASH or UNDERSCORE  (lincolnthree, 14:58:22)
  * brad: dash  (lincolnthree, 14:58:39)
  * underscore  (lincolnthree, 14:58:44)
  * DASH  (sgilda, 14:59:37)
  * AGREED: DASH: weblogic-security-0100  (lincolnthree, 15:00:28)
  * how many characters for the unique rule GUID?  (lincolnthree,
    15:02:51)
  * 8  (sgilda, 15:03:01)
  * AGREED: Ruleset ID has no UID, RuleID ?> weblogic-security-01000
    (leaving enough space for 10s of thousands.)  (lincolnthree,
    15:07:52)

* XML rules schema  (lincolnthree, 15:08:20)
  * Schema versioning  (lincolnthree, 15:08:53)
  * windup-jboss-schema-2.3.0.Final.xsd ?  (lincolnthree, 15:10:39)
  * windup-jboss-2.3.0.Final.xsd ?  (lincolnthree, 15:11:03)
  * windup-jboss-2.3.0.Final.xsd for schema name (also provide
    versionless schema that stays up to date: windup-jboss.xsd for
    schema name?  (lincolnthree, 15:19:36)
  * LINK: http://www.springframework.org/schema/context/   (marekn,
    15:19:38)
  * AGREED: windup-jboss-2.3.0.Final.xsd for schema name (also provide
    versionless schema that stays up to date: windup-jboss.xsd for
    schema name  (lincolnthree, 15:20:54)
  * LINK:

https://github.com/windup/windup/blob/master/config-xml/tests/src/test/resources/testxml/metadata.windup.xml
    (lincolnthree, 15:22:08)
  * LINK:

https://docs.google.com/document/d/1zPWmiFK7YQiZ7_zYot__3PoobwSA7dS29Y4aQ303b4U
    ?  (mbriskar_, 15:23:00)
  * IDEA: We could add tags to <classification tags="spring,
    webservices" ...> to allow filtering and grouping by that in the
    report  (ozizka, 15:31:13)
  * LINK:

https://docs.google.com/document/d/1zPWmiFK7YQiZ7_zYot__3PoobwSA7dS29Y4aQ303b4U/edit#
    (lincolnthree, 15:32:48)
  * LINK: http://pastebin.com/t96HN9nB   (ozizka, 15:42:09)

* JBDS plugin state? (Briefly)  (lincolnthree, 16:05:53)
  * pending, not being worked on except critical bugfixes that interfere
    with demos  (lincolnthree, 16:06:15)

* Links to community websites  (lincolnthree, 16:06:18)
  * create KB articles for information that is contained in community
    answers sites  (lincolnthree, 16:06:48)

* Hint vs. classification - where to put what links, wording, Mardown
  usage, mixed content  (lincolnthree, 16:06:53)
  * discussed and fixed in schema definition: documented
    (
https://docs.google.com/document/d/1zPWmiFK7YQiZ7_zYot__3PoobwSA7dS29Y4aQ303b4U/edit#
)
    (lincolnthree, 16:07:16)

* <TODO/> for the missing KBs?  (lincolnthree, 16:07:19)
  * Create KB articles when the hint message will be too long.
    (lincolnthree, 16:09:02)
  * JIRAs for missing documentation to be created in respective projects
    issue tracker (e.g. EAP7)  (lincolnthree, 16:09:49)
  * JIRA will be assigned to Sande  (lincolnthree, 16:09:57)
  * AGREED: We can use EAP docs jira to create KB requests  (ozizka,
    16:09:59)

* Gilles Bardouillet's use case - how to write into a XML rule?
  (lincolnthree, 16:10:16)

Meeting ended at 16:14:54 UTC.
-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150527/7547c7f3/attachment-0001.html 

From lincolnbaxter at gmail.com  Wed May 27 13:11:52 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 27 May 2015 13:11:52 -0400
Subject: [windup-dev] Namespaces and URLs
In-Reply-To: <556513FF.2050905@redhat.com>
References: <55635954.7010703@redhat.com> <55644EF2.6020307@redhat.com>
	<5564B7BE.1060503@redhat.com> <556513FF.2050905@redhat.com>
Message-ID: <CAEp_U4GzwgK27VxQUpOk0jsza0DmwL7JDwszMSiD6QerVc1YUg@mail.gmail.com>

We agreed the schema name will be:

windup-jboss-2.3.0.Final.xsd

On Tue, May 26, 2015 at 8:46 PM, Ondrej Zizka <ozizka at redhat.com> wrote:

> Hi Sande, Marek,
>
> I know that all are used to -X_Y, but IMO it's a wrong tradition, let me
> explain why.
>
> The rule schema rules location will change with every change of the
> schema. The older schema needs to stay where it is. The old rules will
> refer to that schema. We might change our rules, but those rules which
> are outside our reach will have to refer to a valid schema URL.
>
> I remember that in QE dept, these a-b_c-D-e_F.G_h schemas were a source
> of bugs surprisingly often. Even your examples are inconsistent:
>
> http://www.jboss.org/schema/jbossas/jboss-as-logging_2_0.xsd
> http://www.jboss.org/schema/jbossas/jboss-deployment-structure-1_2.xsd
>
>
> Nobody really can tell why there's a - or _ or . .
> If we simply use the same version string and only use '-' before it,
> it's all clear.
> And, as I said - *the schema only expresses the constraint that is
> effectively inside of the released implementation*. So it's  really
> *directly related to the particular release*.
>
> The fact that we would use 2.3.0.Final for a XSD url or namespace
> doesn't imply or suggest that it has to change for every release. The
> string is in 2 places so far, in general:
> 1) The Windup source, where it should be a single constant in
> config-xml, referenced form it's dependees.
> 2) The XML rules, where it can simply stay the same until next review of
> the rule.
>
> Therefore I don't think it would create any maintainance that would not
> be needed if we use arbitrary version string scheme.
>
> The only reason I can see to keep 1_1 is to align with what someone
> coined up 10 years ago, which for me equals to sticking to a wrong
> solution. YMMV :)
>
> >> I am not really sure if it is good idea to have version in namespace
> Is there some other way for versioning the schema and the rules?
>
>
> On 26.5.2015 20:13, Sande Gilda wrote:
> >>> 3) I suggest to align the XSD version with the Windup core version,
> >>> since the XSD describes what the core accepts.
> >>>        "1.0" is not fortunate, as people will confuse it with legacy
> Windup.
> >>>        The version string should be the same as Windup version, so we
> can
> >>> automate things. Different formats are source of human errors.
> > I went with _1_0.xsd to follow the patterns JBoss uses. If you look in
> > http://www.jboss.org/schema/jbossas/, you'll see none of the JBoss
> > related schemas use the JBoss EAP release number. For example:
> >
> > http://www.jboss.org/schema/jbossas/jboss-as-mail_1_1.xsd
> > http://www.jboss.org/schema/jbossas/jboss-as-logging_2_0.xsd
> > http://www.jboss.org/schema/jbossas/jboss-deployment-structure-1_2.xsd
> > http://www.jboss.org/schema/jbossas/jboss-ejb-client_1_2.xsd
> >
> > Will the schema change with every release of Windup? I would expect it
> > to be more stable than that.
> >
> > Won't it be a maintenance nightmare to update the rules schema location
> > in the XML for the rules for every release?
>
> _______________________________________________
> 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/20150527/4016f3a7/attachment.html 

From lincolnbaxter at gmail.com  Wed May 27 13:13:12 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 27 May 2015 13:13:12 -0400
Subject: [windup-dev] Namespaces and URLs
In-Reply-To: <CAEp_U4GzwgK27VxQUpOk0jsza0DmwL7JDwszMSiD6QerVc1YUg@mail.gmail.com>
References: <55635954.7010703@redhat.com> <55644EF2.6020307@redhat.com>
	<5564B7BE.1060503@redhat.com> <556513FF.2050905@redhat.com>
	<CAEp_U4GzwgK27VxQUpOk0jsza0DmwL7JDwszMSiD6QerVc1YUg@mail.gmail.com>
Message-ID: <CAEp_U4GkXnNwdc68ramTuUUaeyrBt3SYJ2yRstNuYTRxuSd6Qw@mail.gmail.com>

We will also attempt to keep an unversioned schema (or symlink) that is
always pointing to the latest version.

windup-jboss.xsd

On Wed, May 27, 2015 at 1:11 PM, Lincoln Baxter, III <
lincolnbaxter at gmail.com> wrote:

> We agreed the schema name will be:
>
> windup-jboss-2.3.0.Final.xsd
>
> On Tue, May 26, 2015 at 8:46 PM, Ondrej Zizka <ozizka at redhat.com> wrote:
>
>> Hi Sande, Marek,
>>
>> I know that all are used to -X_Y, but IMO it's a wrong tradition, let me
>> explain why.
>>
>> The rule schema rules location will change with every change of the
>> schema. The older schema needs to stay where it is. The old rules will
>> refer to that schema. We might change our rules, but those rules which
>> are outside our reach will have to refer to a valid schema URL.
>>
>> I remember that in QE dept, these a-b_c-D-e_F.G_h schemas were a source
>> of bugs surprisingly often. Even your examples are inconsistent:
>>
>> http://www.jboss.org/schema/jbossas/jboss-as-logging_2_0.xsd
>> http://www.jboss.org/schema/jbossas/jboss-deployment-structure-1_2.xsd
>>
>>
>> Nobody really can tell why there's a - or _ or . .
>> If we simply use the same version string and only use '-' before it,
>> it's all clear.
>> And, as I said - *the schema only expresses the constraint that is
>> effectively inside of the released implementation*. So it's  really
>> *directly related to the particular release*.
>>
>> The fact that we would use 2.3.0.Final for a XSD url or namespace
>> doesn't imply or suggest that it has to change for every release. The
>> string is in 2 places so far, in general:
>> 1) The Windup source, where it should be a single constant in
>> config-xml, referenced form it's dependees.
>> 2) The XML rules, where it can simply stay the same until next review of
>> the rule.
>>
>> Therefore I don't think it would create any maintainance that would not
>> be needed if we use arbitrary version string scheme.
>>
>> The only reason I can see to keep 1_1 is to align with what someone
>> coined up 10 years ago, which for me equals to sticking to a wrong
>> solution. YMMV :)
>>
>> >> I am not really sure if it is good idea to have version in namespace
>> Is there some other way for versioning the schema and the rules?
>>
>>
>> On 26.5.2015 20:13, Sande Gilda wrote:
>> >>> 3) I suggest to align the XSD version with the Windup core version,
>> >>> since the XSD describes what the core accepts.
>> >>>        "1.0" is not fortunate, as people will confuse it with legacy
>> Windup.
>> >>>        The version string should be the same as Windup version, so we
>> can
>> >>> automate things. Different formats are source of human errors.
>> > I went with _1_0.xsd to follow the patterns JBoss uses. If you look in
>> > http://www.jboss.org/schema/jbossas/, you'll see none of the JBoss
>> > related schemas use the JBoss EAP release number. For example:
>> >
>> > http://www.jboss.org/schema/jbossas/jboss-as-mail_1_1.xsd
>> > http://www.jboss.org/schema/jbossas/jboss-as-logging_2_0.xsd
>> > http://www.jboss.org/schema/jbossas/jboss-deployment-structure-1_2.xsd
>> > http://www.jboss.org/schema/jbossas/jboss-ejb-client_1_2.xsd
>> >
>> > Will the schema change with every release of Windup? I would expect it
>> > to be more stable than that.
>> >
>> > Won't it be a maintenance nightmare to update the rules schema location
>> > in the XML for the rules for every release?
>>
>> _______________________________________________
>> 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/20150527/13489c4d/attachment.html 

From lincolnbaxter at gmail.com  Wed May 27 14:28:21 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 27 May 2015 14:28:21 -0400
Subject: [windup-dev] Building and installing whole Windup
	(windup-distribution)
In-Reply-To: <55651598.60003@redhat.com>
References: <297971927.4700897.1429969044617.JavaMail.zimbra@redhat.com>
	<328794499.4701305.1429969643677.JavaMail.zimbra@redhat.com>
	<484943168.4701566.1429971167539.JavaMail.zimbra@redhat.com>
	<CAEp_U4FAuFbCftWiE2uFLSitf+3aSFAvbZXK-PW9AYQiCWiykw@mail.gmail.com>
	<553E1622.5080406@redhat.com>
	<1185704303.4971101.1430137294031.JavaMail.zimbra@redhat.com>
	<553E2E7F.4080303@redhat.com> <553E4886.4000901@redhat.com>
	<55651598.60003@redhat.com>
Message-ID: <CAEp_U4EHegafOuN-GN8c9zhzq9JhsSqpSr7kc-owNb26VxGs9g@mail.gmail.com>

I don't know what is wrong with windup umbrella. Umbrella git projects
don't really support this. Last I heard progress stopped here:
http://git.661346.n2.nabble.com/organizing-multiple-repositories-with-dependencies-td7469712.html


These also frequently cause complications with Maven.
~Lincoln

I just use a shell script like this:

#!/bin/sh
> if [ -f "$HOME/.profile" ]
> then
>    . $HOME/.profile
> fi
> java7
> echo Updating Windup Nexus Repository Indexer...
> cd ~/projects/jboss-migration/nexus-repository-indexer && git pull && mvn
> clean install -DskipTests=true > /dev/null
> echo Updating Windup...
> cd ~/projects/jboss-migration/windup && git pull && mvn clean install
> -DskipTests=true > /dev/null
> echo Updating Windup Rulesets...
> cd ~/projects/jboss-migration/windup-rulesets && git pull && mvn clean
> install -DskipTests=true > /dev/null
> echo Updating Windup Distribution...
> cd ~/projects/jboss-migration/windup-dist && git pull && mvn clean install
> -DskipTests=true > /dev/null
> echo Updating Windup Quickstarts...
> cd ~/projects/jboss-migration/windup-quickstarts && git pull && mvn clean
> install -DskipTests=true > /dev/null
> echo Updating Windup: Eclipse Plugin...
> cd ~/projects/jboss-migration/windup-eclipse-plugin && git pull && mvn
> clean install -DskipTests=true > /dev/null
>
>

On Tue, May 26, 2015 at 8:53 PM, Ondrej Zizka <ozizka at redhat.com> wrote:

>  Hi all,
>
> building the whole Windup from scratch is a bit trickier than just 2
> modules.
> Try to build with -Dmaven.repo.local=localRepo and you'll get into
> troubles.
>
> I have tried to address this with windup-umbrella, and used git's
> submodules for it.
> However there are some issues with it - not just that it's not usable for
> committing / pushing, but even just fetching all the submodules doesn't
> work for me.
>
> Still, that solution looks good to me at least for getting all most recent
> artifact one needs for building Windup, instead of going around in circles,
> figuring out what's missing now and where is its repo.
> So I am reaching out to git experts to tell me what's wrong with
> windup-umbrella.
>
> Regards,
> Ondra
>
>
>
> On 27.4.2015 16:32, Jess Sightler wrote:
>
> I think that he means documentation of how to get the source code and
> build it. windup-distribution is a required module now and is separat*e
> from the other two.*
>
> On 04/27/2015 08:41 AM, Sande Gilda wrote:
>
> Hi Ian,
>
> Are you referring to the download distribution described here:
> https://github.com/windup/windup/wiki/Install-Windup ?
>
> What kind of information are you looking for? A description of the
> directory structure? Something else?
>
> Thanks,
> Sande
>
> On 04/27/2015 08:21 AM, Ian Tewksbury wrote:
>
>  Sande,
>
>  Documentation of the windup-distribution project would be useful.
>
>  ~Ian
>
>  ------------------------------
> *From: *"Sande Gilda" <sgilda at redhat.com> <sgilda at redhat.com>
> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
> <windup-dev at lists.jboss.org>, "George Gastaldi" <ggastald at redhat.com>
> <ggastald at redhat.com>
> *Sent: *Monday, April 27, 2015 6:57:38 AM
> *Subject: *Re: [windup-dev] Could not find artifact
> org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
> jboss-public-repository-group
>
>  This reminds me! I believe I need to update the Wiki documentation [1] to
> talk about the windup-rulesets repository.
>
> Ian, Is there anything else I need to update to prevent confusion for
> others?
>
> [1] https://github.com/windup/windup/wiki/Dev-Get-the-Windup-Source-Code
>
> On 04/25/2015 12:01 PM, Lincoln Baxter, III wrote:
>
> Haha, yes, we moved things around a bit ;) Glad you got if found and
> working, you're very welcome. Jess and George really did the hard work.
>
> On Sat, Apr 25, 2015 at 10:12 AM, Ian Tewksbury <itewk at redhat.com> wrote:
>
>>  Nevermind.
>>
>>  I found the rulesets project too.
>>
>>  Compiling and all tests passing.
>>
>>  Woot. Thank you guys so much for getting this working.
>>
>>  Now for the fun bits.
>>
>> ~Ian
>>
>>  ------------------------------
>> *From: *"Ian Tewksbury" <itewk at redhat.com>
>> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
>> *Sent: *Saturday, April 25, 2015 9:47:23 AM
>> *Subject: *Re: [windup-dev] Could not find artifact
>> org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
>> jboss-public-repository-group
>>
>>
>>  I found the windup-distribution project on git. But trying to build
>> that I get:
>>
>>  [ERROR] Failed to execute goal on project windup-distribution: Could
>> not resolve dependencies for project
>> org.jboss.windup:windup-distribution:pom:2.3.0-SNAPSHOT: Could not find
>> artifact org.jboss.windup.rules:windup-rulesets:jar:2.3.0-SNAPSHOT in
>> jboss-public-repository-group (
>> http://repository.jboss.org/nexus/content/groups/public/)
>>
>>  I know I am missing something dumb here.
>>
>> ~Ian
>>
>>  ------------------------------
>> *From: *"Ian Tewksbury" <itewk at redhat.com>
>> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
>> *Sent: *Saturday, April 25, 2015 9:37:24 AM
>> *Subject: *[windup-dev] Could not find artifact
>> org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
>> jboss-public-repository-group
>>
>>  Trying to get the latest master branch of the plugin compiling.
>>
>>
>>  What am I missing?
>>
>>
>>  [ERROR] Failed to execute goal on project
>> org.jboss.tools.windup.runtime: Could not resolve dependencies for project
>> org.jboss.tools.windup.plugins:org.jboss.tools.windup.runtime:eclipse-plugin:3.1.0-SNAPSHOT:
>> Could not find artifact
>> org.jboss.windup:windup-distribution:zip:offline:2.3.0-SNAPSHOT in
>> jboss-public-repository-group (
>> http://repository.jboss.org/nexus/content/groups/public/) -> [Help 1]
>>
>>
>>
>>  Blue Skies,
>>
>> ~Ian
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>
>
>
>  --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> _______________________________________________
> windup-dev mailing listwindup-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
>
>
> --
> Calendar Free/Busy: https://www.google.com/calendar/embed?src=jsightle%40redhat.com&ctz=America/New_York
>
>
>
> _______________________________________________
> windup-dev mailing 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/20150527/5fb8b4e6/attachment.html 

From lincolnbaxter at gmail.com  Wed May 27 14:29:13 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 27 May 2015 14:29:13 -0400
Subject: [windup-dev] Sugested Fix Hints
In-Reply-To: <55635D00.4060203@redhat.com>
References: <34285553.4971460.1430137378250.JavaMail.zimbra@redhat.com>
	<941980513.4971941.1430137452508.JavaMail.zimbra@redhat.com>
	<CAEp_U4E1yh3bx=L0T82D+TCFucCaojOmHMyy7gEeADO7RNcDpQ@mail.gmail.com>
	<1602348342.5867308.1430237851491.JavaMail.zimbra@redhat.com>
	<CAEp_U4HM-kCuu9hrt0LAiP7NKe1_y8pVWyVrNvU_ymd7R_hcPg@mail.gmail.com>
	<55635D00.4060203@redhat.com>
Message-ID: <CAEp_U4EV7=KcxupuMFxuM1=Cb2YLj-yMKkobXGgT3UPR1Z2tuQ@mail.gmail.com>

Yep. We need to get this in. I suggest we revisit this after summit once we
can spend a little more time on this.

On Mon, May 25, 2015 at 1:33 PM, Ondrej Zizka <ozizka at redhat.com> wrote:

>  IIUC, one of cases is when a custom API becomes standardized.  I.e.
> com.ibm.javax.foo.Bar  ->  javax.foo.Bar.
> E.g. com.ibm.ws.javax.activity.*   (not sure, but looks like that's what
> happened with it)
>
> Ondra
>
>
>
>
>
> On 28.4.2015 19:52, Lincoln Baxter, III wrote:
>
> Mostly, I'm having trouble thinking of any cases where we actually know
> the code that we could replace. I think this is something we could begin to
> do, but it is largely a rule quality issue. We just don't have the expert
> knowledge to supply this kind of info yet. It's a problem we're thinking
> about. That said, having the functionality in place for it might be a good
> idea.
>
>  Can templates be provided programmatically?
>
> On Tue, Apr 28, 2015 at 12:17 PM, Ian Tewksbury <itewk at redhat.com> wrote:
>
>>  Liconln,
>>
>>  I plan on including the links in the Warning/Error messages.
>>
>>  As far as quick fix, for the dead simple low hanging fruit it would
>> need to be replace the detected code with this code. Maybe there isnt such
>> any cases.
>>
>>  The next more complicated case is replace detected code with this code
>> template, then we can use the template API in eclipse to fill out the
>> template based on other information.
>>
>>  Then the last level up is to add an action to apply all the windup
>> quick fixes at once.
>>
>>  So there would really just need to be one new API,
>> "getSuggestedReplacment" (or something like that). WHich would then return
>> a block of code to replace the detected code with. Later we can figure out
>> how we could do Templating through that.
>>
>>  Do you think there are any cases where a template would not be needed?
>>
>> ~Ian
>>
>>
>>  ------------------------------
>> *From: *"Lincoln Baxter, III" <lincolnbaxter at gmail.com>
>> *To: *"Windup-dev List" <windup-dev at lists.jboss.org>
>> *Sent: *Tuesday, April 28, 2015 11:06:14 AM
>> *Subject: *Re: [windup-dev] Sugested Fix Hints
>>
>>
>>  Hey Ian,
>>
>>  Hints are just HTML/Markdown, and don't provide anything that would
>> really be useful for a quick fix at this point, but... they should have the
>> ability to include Links/HREFs as well. If you look at the
>> windup-tooling-api, you should see Hint, Classification, and Link.
>>
>>  How do you envision the quick fix stuff working? What type of
>> information would we need to give you?
>>
>>  Does that answer your question?
>>
>>  Thanks!
>> ~Lincoln
>>
>> On Mon, Apr 27, 2015 at 8:24 AM, Ian Tewksbury <itewk at redhat.com> wrote:
>>
>>>  All,
>>>
>>>  Do any of the hints have a "suggested fix" built into them. I was
>>> looking at the hint API but didnt see such a thing, but I know it had been
>>> talked about in the past.
>>>
>>>  If such a thing exists I want to detect hints with "suggested code
>>> fixes" and auto generate Eclipse quick fixes for those hints so people can
>>> easily apply the quick fixes to knock out the easy stuff in an automated
>>> fashion.
>>>
>>> ~Ian
>>>
>>> _______________________________________________
>>> windup-dev mailing list
>>> windup-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>>
>>
>>
>>
>>  --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>
>
>
>  --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> 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/20150527/30c46d34/attachment-0001.html 

From mnovotny at redhat.com  Thu May 28 04:45:46 2015
From: mnovotny at redhat.com (Marek Novotny)
Date: Thu, 28 May 2015 10:45:46 +0200
Subject: [windup-dev] Windup 2.x for oracle service bus??
In-Reply-To: <14608098.167.1426516891652.JavaMail.dhodge@dhodge.csb>
References: <14608098.167.1426516891652.JavaMail.dhodge@dhodge.csb>
Message-ID: <5566D5BA.5020603@redhat.com>

I think that there is no such rule in current rule set.

I found this Oracle Service Bus Maven Artifact documentation
https://docs.oracle.com/middleware/1213/core/MAVEN/osb_maven_project.htm#MAVEN8968

Did you mean something like this? We probably could create rules to
catch it.

On 16.3.2015 15:41, Dan Hodge wrote:
> anyone,
> 
> does windup 2.x have any rules for the oracle service bus artifacts?  do
> we have any experience with the oracle service bus artifacts? 
> 
> Dan
> 
> 
> Dan Hodge
> Sr. Middleware Solutions Architect
> dhodge at redhat.com
> +1 (416) 587-2647 (Mobile)
> 
> http://www.redhat.com/jboss/getunstuck/
> 
> 
> 
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
> 


-- 
Marek Novotny
--
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno

From mnovotny at redhat.com  Thu May 28 04:48:01 2015
From: mnovotny at redhat.com (Marek Novotny)
Date: Thu, 28 May 2015 10:48:01 +0200
Subject: [windup-dev] Unclassified Files
In-Reply-To: <B3BEB6B9-CA75-41C1-A7C0-3C945CE51E72@icloud.com>
References: <B3BEB6B9-CA75-41C1-A7C0-3C945CE51E72@icloud.com>
Message-ID: <5566D641.90203@redhat.com>

On 2.3.2015 14:12, Samuel Tauil wrote:
> Hi,
> 
> I understand the Unclassified Files section in the report as a list of all files which were decompiled properly by Procyon but weren't captured by any rules, so the user can check and see which resources need to be checked again and generate specific rules or not. Is that correct? 
> 
> Thanks
> 
> Samuel
> 
> 
> 
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
> 

I think that's correct, not sure fully with the "decompiled" specific.


-- 
Marek Novotny
--
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno

From lincolnbaxter at gmail.com  Thu May 28 12:57:48 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 28 May 2015 12:57:48 -0400
Subject: [windup-dev] Unclassified Files
In-Reply-To: <5566D641.90203@redhat.com>
References: <B3BEB6B9-CA75-41C1-A7C0-3C945CE51E72@icloud.com>
	<5566D641.90203@redhat.com>
Message-ID: <CAEp_U4EEtB_AkKaZwNt8_cYOx+KFL8npXuAuhZgn3t9O7WsDsg@mail.gmail.com>

Yes, that is correct.

On Thu, May 28, 2015 at 4:48 AM, Marek Novotny <mnovotny at redhat.com> wrote:

> On 2.3.2015 14:12, Samuel Tauil wrote:
> > Hi,
> >
> > I understand the Unclassified Files section in the report as a list of
> all files which were decompiled properly by Procyon but weren't captured by
> any rules, so the user can check and see which resources need to be checked
> again and generate specific rules or not. Is that correct?
> >
> > Thanks
> >
> > Samuel
> >
> >
> >
> > _______________________________________________
> > windup-dev mailing list
> > windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
> >
>
> I think that's correct, not sure fully with the "decompiled" specific.
>
>
> --
> Marek Novotny
> --
> WFK and Seam Product Lead
>
> Red Hat Czech s.r.o.
> Purkynova 99
> 612 45 Brno
> _______________________________________________
> 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/20150528/7495a10a/attachment.html 

From robb.greathouse at redhat.com  Thu May 28 14:13:28 2015
From: robb.greathouse at redhat.com (Robb Greathouse)
Date: Thu, 28 May 2015 14:13:28 -0400 (EDT)
Subject: [windup-dev] [Windup-users] Windup usage Issue
In-Reply-To: <52438C265F8F8A4A9F099395055B389838775D34@AFSMAILMB008.us.accenturefederal.com>
References: <52438C265F8F8A4A9F099395055B389838775D34@AFSMAILMB008.us.accenturefederal.com>
Message-ID: <283058123.6270547.1432836808522.JavaMail.zimbra@redhat.com>

Can you share the applications with us? We could help with additional rules. 

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

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

> H i

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

> Thanks for your time,

> -Babu

> _______________________________________________
> Windup-users mailing list
> Windup-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150528/5f064bae/attachment.html 

From b.jayaraman at accenturefederal.com  Fri May 29 11:41:05 2015
From: b.jayaraman at accenturefederal.com (b.jayaraman at accenturefederal.com)
Date: Fri, 29 May 2015 15:41:05 +0000
Subject: [windup-dev] [Windup-users] Windup usage Issue
In-Reply-To: <283058123.6270547.1432836808522.JavaMail.zimbra@redhat.com>
References: <52438C265F8F8A4A9F099395055B389838775D34@AFSMAILMB008.us.accenturefederal.com>
	<283058123.6270547.1432836808522.JavaMail.zimbra@redhat.com>
Message-ID: <52438C265F8F8A4A9F099395055B3898387BC86B@AFSMAILMB008.us.accenturefederal.com>

Hi Robb,
         Unfortunately, we could not share our application with any one outside. I?m open to screenshare and show you the issue. Will that work?

Thanks,
Babu

From: Robb Greathouse [mailto:robb.greathouse at redhat.com]
Sent: Thursday, May 28, 2015 2:13 PM
To: Jayaraman, B. [FEI.COM]
Cc: windup-dev at lists.jboss.org
Subject: Re: [Windup-users] Windup usage Issue

Can you share the applications with us?  We could help with additional rules.


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

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

Thanks for your time,
-Babu

_______________________________________________
Windup-users mailing list
Windup-users at lists.jboss.org<mailto:Windup-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/windup-users

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

From ozizka at redhat.com  Fri May 29 12:17:55 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Fri, 29 May 2015 18:17:55 +0200
Subject: [windup-dev] [Windup-users] Windup usage Issue
In-Reply-To: <52438C265F8F8A4A9F099395055B3898387BC86B@AFSMAILMB008.us.accenturefederal.com>
References: <52438C265F8F8A4A9F099395055B389838775D34@AFSMAILMB008.us.accenturefederal.com>	<283058123.6270547.1432836808522.JavaMail.zimbra@redhat.com>
	<52438C265F8F8A4A9F099395055B3898387BC86B@AFSMAILMB008.us.accenturefederal.com>
Message-ID: <55689133.1030600@redhat.com>

Hi Babu,

it's likely that your app uses those things that we do not cover with 
our rules - yet.
I understand that you can't pass the whole .ear.
But could you perhaps send us a stripped version with things that can be 
considered safe to pass to the Windup development team?
If that's acceptable, please send it to my mail (instead of the list)  
if it's under 10 MB, or share with me on Google Drive if it's larger.

Thanks!
Ondra


On 29.5.2015 17:41, b.jayaraman at accenturefederal.com wrote:
>
> Hi Robb,
>
> Unfortunately, we could not share our application with any one 
> outside. I?m open to screenshare and show you the issue. Will that work?
>
> Thanks,
>
> Babu
>
> *From:* Robb Greathouse [mailto:robb.greathouse at redhat.com]
> *Sent:* Thursday, May 28, 2015 2:13 PM
> *To:* Jayaraman, B. [FEI.COM]
> *Cc:* windup-dev at lists.jboss.org
> *Subject:* Re: [Windup-users] Windup usage Issue
>
> Can you share the applications with us?  We could help with additional 
> rules.
>
>
> Robb Greathouse
> Middleware Business Unit
> JBoss, a Division of Red Hat
> cellphone 505-507-4906
>
> ------------------------------------------------------------------------
>
>     Hi
>
>              I?m trying to port an application that is currently
>     hosted on Websphere 8.5 running on JDK 1.7 to JBoss EAP 6.4. I
>     downloaded and installed Windup and tested with default provided
>     ear file conversion, things worked fine, however, if I try to run
>     through my app, I get zero story points for one app and for
>     another app, I get only one story point. When windup runs, I see
>     that websphere rules gets executed but still no results. I also
>     tried to explode one of the war file and run through windup, it
>     did not go through the files under WEB-INF/classes directory. I
>     have created the issue in JIRA as well
>     (https://issues.jboss.org/browse/WINDUP-567 &
>     https://developer.jboss.org/message/926645#926645  ) . I can open
>     the ear file and start double checking against the windup results
>     but before that I just want to check with you for any additional
>     hints or installation verification steps.
>
>     Thanks for your time,
>
>     -Babu
>
>
>     _______________________________________________
>     Windup-users mailing list
>     Windup-users at lists.jboss.org <mailto:Windup-users at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/windup-users
>
>
>
> _______________________________________________
> 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/20150529/dab99b86/attachment.html 

From robb.greathouse at redhat.com  Fri May 29 13:14:42 2015
From: robb.greathouse at redhat.com (Robb Greathouse)
Date: Fri, 29 May 2015 13:14:42 -0400 (EDT)
Subject: [windup-dev] [Windup-users] Windup usage Issue
In-Reply-To: <52438C265F8F8A4A9F099395055B3898387BC86B@AFSMAILMB008.us.accenturefederal.com>
References: <52438C265F8F8A4A9F099395055B389838775D34@AFSMAILMB008.us.accenturefederal.com>
	<283058123.6270547.1432836808522.JavaMail.zimbra@redhat.com>
	<52438C265F8F8A4A9F099395055B3898387BC86B@AFSMAILMB008.us.accenturefederal.com>
Message-ID: <1908075871.7389625.1432919682629.JavaMail.zimbra@redhat.com>

Yes. 

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

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

> Hi Robb,

> Unfortunately, we could not share our application with any one outside. I?m
> open to screenshare and show you the issue. Will that work?

> Thanks,

> Babu

> From: Robb Greathouse [mailto:robb.greathouse at redhat.com]
> Sent: Thursday, May 28, 2015 2:13 PM
> To: Jayaraman, B. [FEI.COM]
> Cc: windup-dev at lists.jboss.org
> Subject: Re: [Windup-users] Windup usage Issue

> Can you share the applications with us? We could help with additional rules.

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

> ----- Original Message -----

> > H i
> 

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

> > Thanks for your time,
> 

> > -Babu
> 

> > _______________________________________________
> 
> > Windup-users mailing list
> 
> > Windup-users at lists.jboss.org
> 
> > https://lists.jboss.org/mailman/listinfo/windup-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150529/9792ddee/attachment.html