From ozizka at redhat.com Thu Jul 9 07:33:56 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 09 Jul 2015 13:33:56 +0200
Subject: [windup-dev] Freemarker usage
Message-ID: <559E5C24.4090003@redhat.com>
Hi,
I have few questions regarding Freemarker usage.
There are many places where we duplicate the functionality already
available in Freemarker.
I wonder if it's necessary, as it makes the code less readable.
1)
For example, sometimes the iterable needs to become a collection. And
then needs to be sorted.
We have this:
<#list
sortFilesByPathAscending(projectModel.fileModelsNoDirectories) as fileModel>
<@fileModelRenderer fileModel/>
</#list>
sortFilesByPathAscending() is a FM function created just for this one
single case (or there's a second one).
Wouldn't it be better to just make projectModel.fileModelsNoDirectories
a collection using some toList(projectModel.fileModelsNoDirectories) and
sort it in FM?
Did something prevent this kind of usage?
<#list
toList(projectModel.fileModelsNoDirectories)?sort_by("filePath") as
fileModel>
Or, better, having it sorted right in the database, which is probably
better place to do so as it may have indexes available for it?
2)
iterableHasContent(...) - again, wouldn't it be better, instead of
<#if iterableHasContent(projectModel.fileModelsNoDirectories)>
...
<#list
sortFilesByPathAscending(projectModel.fileModelsNoDirectories) as fileModel>
to do
<#assign myList = toList(projectModel.fileModelsNoDirectories)
<#if myList?has_content>
<#list myList?sort_by("filePath") as fileModel>
The only addition of iterableHasContent() is that it measures the time
for the function call. Is that the reason for it?
Just asking.
Ondra
From jsightle at redhat.com Thu Jul 9 10:56:24 2015
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 9 Jul 2015 10:56:24 -0400
Subject: [windup-dev] Freemarker usage
In-Reply-To: <559E5C24.4090003@redhat.com>
References: <559E5C24.4090003@redhat.com>
Message-ID: <559E8B98.8070403@redhat.com>
On 07/09/2015 07:33 AM, Ondrej Zizka wrote:
> Hi,
>
> I have few questions regarding Freemarker usage.
>
> There are many places where we duplicate the functionality already
> available in Freemarker.
> I wonder if it's necessary, as it makes the code less readable.
>
> 1)
> For example, sometimes the iterable needs to become a collection. And
> then needs to be sorted.
> We have this:
>
> <#list
> sortFilesByPathAscending(projectModel.fileModelsNoDirectories) as fileModel>
> <@fileModelRenderer fileModel/>
> </#list>
>
> sortFilesByPathAscending() is a FM function created just for this one
> single case (or there's a second one).
>
> Wouldn't it be better to just make projectModel.fileModelsNoDirectories
> a collection using some toList(projectModel.fileModelsNoDirectories) and
> sort it in FM?
> Did something prevent this kind of usage?
>
> <#list
> toList(projectModel.fileModelsNoDirectories)?sort_by("filePath") as
> fileModel>
>
> Or, better, having it sorted right in the database, which is probably
> better place to do so as it may have indexes available for it?
That would "work", but the sorting wouldn't look very nice.
Instead of:
com.example.Foo
com.example.Zoo
com.example.apples.Potato
com.example.bar.Baz
com.example.zoo.Animals
You would get something like this:
com.example.apples.Potato
com.example.bar.Baz
com.example.Foo
com.example.Zoo
com.example.zoo.Animals
It's just not the natural way to sort directories and package paths,
since they are hierarchical.
>
> 2)
> iterableHasContent(...) - again, wouldn't it be better, instead of
>
> <#if iterableHasContent(projectModel.fileModelsNoDirectories)>
> ...
> <#list
> sortFilesByPathAscending(projectModel.fileModelsNoDirectories) as fileModel>
> to do
> <#assign myList = toList(projectModel.fileModelsNoDirectories)
> <#if myList?has_content>
> <#list myList?sort_by("filePath") as fileModel>
>
> The only addition of iterableHasContent() is that it measures the time
> for the function call. Is that the reason for it?
I didn't write this one, so I don't know why it was written this way. I
think I agree with you, though, that method seems unnecessary.
Feel free to try it. :)
From jsightle at redhat.com Thu Jul 9 19:16:33 2015
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 9 Jul 2015 19:16:33 -0400
Subject: [windup-dev] Screenshot of feedback form for feedback
Message-ID: <559F00D1.50700@redhat.com>
Attached... let me know what you think, please.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2015-07-09 19-15-37.png
Type: image/png
Size: 105012 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150709/e35886f9/attachment-0001.png
From rruss at redhat.com Thu Jul 9 19:22:22 2015
From: rruss at redhat.com (Rodney Russ)
Date: Thu, 09 Jul 2015 17:22:22 -0600
Subject: [windup-dev] Screenshot of feedback form for feedback
In-Reply-To: <559F00D1.50700@redhat.com>
References: <559F00D1.50700@redhat.com>
Message-ID: <E0A77986-C0A9-4C4E-B2EA-66787B27E073@redhat.com>
Would you need to know where it's used, both file/class and perhaps
application?
On 9 Jul 2015, at 17:16, Jess Sightler wrote:
> Attached... let me know what you think, please.
>
> [Screenshot from 2015-07-09 19-15-37.png]
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From bdavis at redhat.com Thu Jul 9 22:52:38 2015
From: bdavis at redhat.com (Brad Davis)
Date: Thu, 9 Jul 2015 22:52:38 -0400 (EDT)
Subject: [windup-dev] Screenshot of feedback form for feedback
In-Reply-To: <E0A77986-C0A9-4C4E-B2EA-66787B27E073@redhat.com>
References: <559F00D1.50700@redhat.com>
<E0A77986-C0A9-4C4E-B2EA-66787B27E073@redhat.com>
Message-ID: <259117102.26147279.1436496758131.JavaMail.zimbra@redhat.com>
Definitely a great start, Jess! Where does the data push to on the backend?
To Rodney's point of detailed info on a migration, we could add in Meta Information on the source code report's highlighted lines that don't have hints, and then put a button to Submit Hint. (Like when we highlight a line that we know uses Websphere classes, but we don't have information on its migration path.) In that case, we could take the Meta Information around the highlighted line, maybe the line itself, the fully resolved classes on the line, etc.
One thing I considered in the past as well was adding the ability to submit anonymous analytics to assist the Windup team. That could include: what vendor classes are used in the application? If we had that information along with a SHA256 of the archive it came from, we could much better plan for things that customers are seeing in the field that we haven't yet gotten rules in place for. It would have to be an opt in type of thing due to the European regulations and requirements around "offline" functionality for high security customers.
Getting more feedback and allowing people to contribute without contributing code is absolutely key. Good job Jess!
Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Rodney Russ" <rruss at redhat.com>
To: "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Thursday, July 9, 2015 7:22:22 PM
Subject: Re: [windup-dev] Screenshot of feedback form for feedback
Would you need to know where it's used, both file/class and perhaps
application?
On 9 Jul 2015, at 17:16, Jess Sightler wrote:
> Attached... let me know what you think, please.
>
> [Screenshot from 2015-07-09 19-15-37.png]
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
From bdavis at redhat.com Thu Jul 9 22:55:36 2015
From: bdavis at redhat.com (Brad Davis)
Date: Thu, 9 Jul 2015 22:55:36 -0400 (EDT)
Subject: [windup-dev] Screenshot of feedback form for feedback
In-Reply-To: <259117102.26147279.1436496758131.JavaMail.zimbra@redhat.com>
References: <559F00D1.50700@redhat.com>
<E0A77986-C0A9-4C4E-B2EA-66787B27E073@redhat.com>
<259117102.26147279.1436496758131.JavaMail.zimbra@redhat.com>
Message-ID: <1375230139.26150282.1436496936005.JavaMail.zimbra@redhat.com>
* For the anonymous analytics, my plan was to leverage Google Analytics. The JBoss Developers Studio team (Max specicifically) already does some of this, so we could leverage his knowledge for API and regulations.
Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Brad Davis" <bdavis at redhat.com>
To: "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Thursday, July 9, 2015 10:52:38 PM
Subject: Re: [windup-dev] Screenshot of feedback form for feedback
Definitely a great start, Jess! Where does the data push to on the backend?
To Rodney's point of detailed info on a migration, we could add in Meta Information on the source code report's highlighted lines that don't have hints, and then put a button to Submit Hint. (Like when we highlight a line that we know uses Websphere classes, but we don't have information on its migration path.) In that case, we could take the Meta Information around the highlighted line, maybe the line itself, the fully resolved classes on the line, etc.
One thing I considered in the past as well was adding the ability to submit anonymous analytics to assist the Windup team. That could include: what vendor classes are used in the application? If we had that information along with a SHA256 of the archive it came from, we could much better plan for things that customers are seeing in the field that we haven't yet gotten rules in place for. It would have to be an opt in type of thing due to the European regulations and requirements around "offline" functionality for high security customers.
Getting more feedback and allowing people to contribute without contributing code is absolutely key. Good job Jess!
Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Rodney Russ" <rruss at redhat.com>
To: "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Thursday, July 9, 2015 7:22:22 PM
Subject: Re: [windup-dev] Screenshot of feedback form for feedback
Would you need to know where it's used, both file/class and perhaps
application?
On 9 Jul 2015, at 17:16, Jess Sightler wrote:
> Attached... let me know what you think, please.
>
> [Screenshot from 2015-07-09 19-15-37.png]
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
From rruss at redhat.com Fri Jul 10 01:20:46 2015
From: rruss at redhat.com (Rodney Russ)
Date: Thu, 09 Jul 2015 23:20:46 -0600
Subject: [windup-dev] Screenshot of feedback form for feedback
In-Reply-To: <1375230139.26150282.1436496936005.JavaMail.zimbra@redhat.com>
References: <559F00D1.50700@redhat.com>
<E0A77986-C0A9-4C4E-B2EA-66787B27E073@redhat.com>
<259117102.26147279.1436496758131.JavaMail.zimbra@redhat.com>
<1375230139.26150282.1436496936005.JavaMail.zimbra@redhat.com>
Message-ID: <32A3C435-54EE-4C5C-9B53-0D1BD6695A2E@redhat.com>
On 9 Jul 2015, at 20:55, Brad Davis wrote:
> * For the anonymous analytics, my plan was to leverage Google
> Analytics. The JBoss Developers Studio team (Max specicifically)
> already does some of this, so we could leverage his knowledge for API
> and regulations.
I know from a legal perspective, we needed to ensure that the default
was opt-out and the user would have to explicitly opt-in to allow
feedback. There are also some limitations as well. It would be good to
start a conversation with Max once analytics begins to bubble to the top
of the backlog.
>
> Brad Davis
> Senior Manager, Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Brad Davis" <bdavis at redhat.com>
> To: "Windup-dev List" <windup-dev at lists.jboss.org>
> Sent: Thursday, July 9, 2015 10:52:38 PM
> Subject: Re: [windup-dev] Screenshot of feedback form for feedback
>
> Definitely a great start, Jess! Where does the data push to on the
> backend?
>
> To Rodney's point of detailed info on a migration, we could add in
> Meta Information on the source code report's highlighted lines that
> don't have hints, and then put a button to Submit Hint. (Like when we
> highlight a line that we know uses Websphere classes, but we don't
> have information on its migration path.) In that case, we could take
> the Meta Information around the highlighted line, maybe the line
> itself, the fully resolved classes on the line, etc.
>
> One thing I considered in the past as well was adding the ability to
> submit anonymous analytics to assist the Windup team. That could
> include: what vendor classes are used in the application? If we had
> that information along with a SHA256 of the archive it came from, we
> could much better plan for things that customers are seeing in the
> field that we haven't yet gotten rules in place for. It would have to
> be an opt in type of thing due to the European regulations and
> requirements around "offline" functionality for high security
> customers.
>
> Getting more feedback and allowing people to contribute without
> contributing code is absolutely key. Good job Jess!
>
> Brad Davis
> Senior Manager, Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Rodney Russ" <rruss at redhat.com>
> To: "Windup-dev List" <windup-dev at lists.jboss.org>
> Sent: Thursday, July 9, 2015 7:22:22 PM
> Subject: Re: [windup-dev] Screenshot of feedback form for feedback
>
> Would you need to know where it's used, both file/class and perhaps
> application?
>
> On 9 Jul 2015, at 17:16, Jess Sightler wrote:
>
>> Attached... let me know what you think, please.
>>
>> [Screenshot from 2015-07-09 19-15-37.png]
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From mzottner at redhat.com Fri Jul 10 02:50:34 2015
From: mzottner at redhat.com (Marc Zottner)
Date: Fri, 10 Jul 2015 02:50:34 -0400 (EDT)
Subject: [windup-dev] Screenshot of feedback form for feedback
In-Reply-To: <1375230139.26150282.1436496936005.JavaMail.zimbra@redhat.com>
References: <559F00D1.50700@redhat.com>
<E0A77986-C0A9-4C4E-B2EA-66787B27E073@redhat.com>
<259117102.26147279.1436496758131.JavaMail.zimbra@redhat.com>
<1375230139.26150282.1436496936005.JavaMail.zimbra@redhat.com>
Message-ID: <322868842.26208746.1436511034677.JavaMail.zimbra@redhat.com>
Hi Brad!
Getting feedback from the customer is great. Currently I do not know a single customer looking forward to allowing an upload of its usage statistics. (Maybe the German/Austrians/French are a little bit too sensitive about this ...) If such a feature is included, I strongly recommend to explicitly communicate it to the user and provide an easy way to disable it.
I like the feedback pop-up. What about adding a check-box to also allow the user to upload the statistics of his reports if he likes to do so? It would be also great to add 1-2 sentences explaining what is happening to the feedback and that we are grateful for it.
best regards,
Marc
----- Urspr?ngliche Mail -----
Von: "Brad Davis" <bdavis at redhat.com>
An: "Windup-dev List" <windup-dev at lists.jboss.org>
Gesendet: Freitag, 10. Juli 2015 04:55:36
Betreff: Re: [windup-dev] Screenshot of feedback form for feedback
* For the anonymous analytics, my plan was to leverage Google Analytics. The JBoss Developers Studio team (Max specicifically) already does some of this, so we could leverage his knowledge for API and regulations.
Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Brad Davis" <bdavis at redhat.com>
To: "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Thursday, July 9, 2015 10:52:38 PM
Subject: Re: [windup-dev] Screenshot of feedback form for feedback
Definitely a great start, Jess! Where does the data push to on the backend?
To Rodney's point of detailed info on a migration, we could add in Meta Information on the source code report's highlighted lines that don't have hints, and then put a button to Submit Hint. (Like when we highlight a line that we know uses Websphere classes, but we don't have information on its migration path.) In that case, we could take the Meta Information around the highlighted line, maybe the line itself, the fully resolved classes on the line, etc.
One thing I considered in the past as well was adding the ability to submit anonymous analytics to assist the Windup team. That could include: what vendor classes are used in the application? If we had that information along with a SHA256 of the archive it came from, we could much better plan for things that customers are seeing in the field that we haven't yet gotten rules in place for. It would have to be an opt in type of thing due to the European regulations and requirements around "offline" functionality for high security customers.
Getting more feedback and allowing people to contribute without contributing code is absolutely key. Good job Jess!
Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Rodney Russ" <rruss at redhat.com>
To: "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Thursday, July 9, 2015 7:22:22 PM
Subject: Re: [windup-dev] Screenshot of feedback form for feedback
Would you need to know where it's used, both file/class and perhaps
application?
On 9 Jul 2015, at 17:16, Jess Sightler wrote:
> Attached... let me know what you think, please.
>
> [Screenshot from 2015-07-09 19-15-37.png]
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150710/3a7026da/attachment.html
From bdavis at redhat.com Fri Jul 10 08:48:58 2015
From: bdavis at redhat.com (Brad Davis)
Date: Fri, 10 Jul 2015 08:48:58 -0400 (EDT)
Subject: [windup-dev] Screenshot of feedback form for feedback
In-Reply-To: <322868842.26208746.1436511034677.JavaMail.zimbra@redhat.com>
References: <559F00D1.50700@redhat.com>
<E0A77986-C0A9-4C4E-B2EA-66787B27E073@redhat.com>
<259117102.26147279.1436496758131.JavaMail.zimbra@redhat.com>
<1375230139.26150282.1436496936005.JavaMail.zimbra@redhat.com>
<322868842.26208746.1436511034677.JavaMail.zimbra@redhat.com>
Message-ID: <8A72AE97-17F4-4D57-AAAF-03936BBE57B6@redhat.com>
Hey Marc;
I know the services team in the states would be easily open to running the analytics during our engagements. All of our customers have an NDA in place with Red Hat so as long as we aren't exposing those analytics or providing any identifying information, not sure why they'd care. They upload archives to the support portal and logs all the time.
I'd imagine with analytics, we could just add a flag that can be set during execution so that it's opt in. It's invaluable info to the cause and planning.
Brad
Sent from my iPhone
> On Jul 10, 2015, at 2:50 AM, Marc Zottner <mzottner at redhat.com> wrote:
>
> Hi Brad!
>
> Getting feedback from the customer is great. Currently I do not know a single customer looking forward to allowing an upload of its usage statistics. (Maybe the German/Austrians/French are a little bit too sensitive about this ...) If such a feature is included, I strongly recommend to explicitly communicate it to the user and provide an easy way to disable it.
>
> I like the feedback pop-up. What about adding a check-box to also allow the user to upload the statistics of his reports if he likes to do so? It would be also great to add 1-2 sentences explaining what is happening to the feedback and that we are grateful for it.
>
> best regards,
>
> Marc
>
> Von: "Brad Davis" <bdavis at redhat.com>
> An: "Windup-dev List" <windup-dev at lists.jboss.org>
> Gesendet: Freitag, 10. Juli 2015 04:55:36
> Betreff: Re: [windup-dev] Screenshot of feedback form for feedback
>
> * For the anonymous analytics, my plan was to leverage Google Analytics. The JBoss Developers Studio team (Max specicifically) already does some of this, so we could leverage his knowledge for API and regulations.
>
> Brad Davis
> Senior Manager, Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Brad Davis" <bdavis at redhat.com>
> To: "Windup-dev List" <windup-dev at lists.jboss.org>
> Sent: Thursday, July 9, 2015 10:52:38 PM
> Subject: Re: [windup-dev] Screenshot of feedback form for feedback
>
> Definitely a great start, Jess! Where does the data push to on the backend?
>
> To Rodney's point of detailed info on a migration, we could add in Meta Information on the source code report's highlighted lines that don't have hints, and then put a button to Submit Hint. (Like when we highlight a line that we know uses Websphere classes, but we don't have information on its migration path.) In that case, we could take the Meta Information around the highlighted line, maybe the line itself, the fully resolved classes on the line, etc.
>
> One thing I considered in the past as well was adding the ability to submit anonymous analytics to assist the Windup team. That could include: what vendor classes are used in the application? If we had that information along with a SHA256 of the archive it came from, we could much better plan for things that customers are seeing in the field that we haven't yet gotten rules in place for. It would have to be an opt in type of thing due to the European regulations and requirements around "offline" functionality for high security customers.
>
> Getting more feedback and allowing people to contribute without contributing code is absolutely key. Good job Jess!
>
> Brad Davis
> Senior Manager, Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Rodney Russ" <rruss at redhat.com>
> To: "Windup-dev List" <windup-dev at lists.jboss.org>
> Sent: Thursday, July 9, 2015 7:22:22 PM
> Subject: Re: [windup-dev] Screenshot of feedback form for feedback
>
> Would you need to know where it's used, both file/class and perhaps
> application?
>
> On 9 Jul 2015, at 17:16, Jess Sightler wrote:
>
> > Attached... let me know what you think, please.
> >
> > [Screenshot from 2015-07-09 19-15-37.png]
> > _______________________________________________
> > windup-dev mailing list
> > windup-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150710/6873ce31/attachment-0001.html
From jsightle at redhat.com Fri Jul 10 18:47:25 2015
From: jsightle at redhat.com (Jess Sightler)
Date: Fri, 10 Jul 2015 18:47:25 -0400
Subject: [windup-dev] Screenshot of feedback form for feedback
In-Reply-To: <259117102.26147279.1436496758131.JavaMail.zimbra@redhat.com>
References: <559F00D1.50700@redhat.com>
<E0A77986-C0A9-4C4E-B2EA-66787B27E073@redhat.com>
<259117102.26147279.1436496758131.JavaMail.zimbra@redhat.com>
Message-ID: <55A04B7D.9040101@redhat.com>
Yes, I think we can pull in the application name and file path
information by default.
I agree that it would be nice to put in a clickable link for feedback on
hints. I think we can do this regardless of whether the hint is a
fallback hint or not, as this could be used for general.
The backend is currently still being decided and designed. This is just
the frontend component.
Should we go ahead with development with the feedback from Rodney and
Brad incorporated?
Thanks,
Jess
On 07/09/2015 10:52 PM, Brad Davis wrote:
> Definitely a great start, Jess! Where does the data push to on the backend?
>
> To Rodney's point of detailed info on a migration, we could add in Meta Information on the source code report's highlighted lines that don't have hints, and then put a button to Submit Hint. (Like when we highlight a line that we know uses Websphere classes, but we don't have information on its migration path.) In that case, we could take the Meta Information around the highlighted line, maybe the line itself, the fully resolved classes on the line, etc.
>
> One thing I considered in the past as well was adding the ability to submit anonymous analytics to assist the Windup team. That could include: what vendor classes are used in the application? If we had that information along with a SHA256 of the archive it came from, we could much better plan for things that customers are seeing in the field that we haven't yet gotten rules in place for. It would have to be an opt in type of thing due to the European regulations and requirements around "offline" functionality for high security customers.
>
> Getting more feedback and allowing people to contribute without contributing code is absolutely key. Good job Jess!
>
> Brad Davis
> Senior Manager, Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Rodney Russ" <rruss at redhat.com>
> To: "Windup-dev List" <windup-dev at lists.jboss.org>
> Sent: Thursday, July 9, 2015 7:22:22 PM
> Subject: Re: [windup-dev] Screenshot of feedback form for feedback
>
> Would you need to know where it's used, both file/class and perhaps
> application?
>
> On 9 Jul 2015, at 17:16, Jess Sightler wrote:
>
>> Attached... let me know what you think, please.
>>
>> [Screenshot from 2015-07-09 19-15-37.png]
>> _______________________________________________
>> 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
From bdavis at redhat.com Sat Jul 11 10:07:13 2015
From: bdavis at redhat.com (Brad Davis)
Date: Sat, 11 Jul 2015 10:07:13 -0400 (EDT)
Subject: [windup-dev] Screenshot of feedback form for feedback
In-Reply-To: <55A04B7D.9040101@redhat.com>
References: <559F00D1.50700@redhat.com>
<E0A77986-C0A9-4C4E-B2EA-66787B27E073@redhat.com>
<259117102.26147279.1436496758131.JavaMail.zimbra@redhat.com>
<55A04B7D.9040101@redhat.com>
Message-ID: <103368295.26680946.1436623633865.JavaMail.zimbra@redhat.com>
I will run with taking a first crack at the Analytics piece. WINDUP-690
Thanks,
Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Jess Sightler" <jsightle at redhat.com>
To: windup-dev at lists.jboss.org
Sent: Friday, July 10, 2015 6:47:25 PM
Subject: Re: [windup-dev] Screenshot of feedback form for feedback
Yes, I think we can pull in the application name and file path
information by default.
I agree that it would be nice to put in a clickable link for feedback on
hints. I think we can do this regardless of whether the hint is a
fallback hint or not, as this could be used for general.
The backend is currently still being decided and designed. This is just
the frontend component.
Should we go ahead with development with the feedback from Rodney and
Brad incorporated?
Thanks,
Jess
On 07/09/2015 10:52 PM, Brad Davis wrote:
> Definitely a great start, Jess! Where does the data push to on the backend?
>
> To Rodney's point of detailed info on a migration, we could add in Meta Information on the source code report's highlighted lines that don't have hints, and then put a button to Submit Hint. (Like when we highlight a line that we know uses Websphere classes, but we don't have information on its migration path.) In that case, we could take the Meta Information around the highlighted line, maybe the line itself, the fully resolved classes on the line, etc.
>
> One thing I considered in the past as well was adding the ability to submit anonymous analytics to assist the Windup team. That could include: what vendor classes are used in the application? If we had that information along with a SHA256 of the archive it came from, we could much better plan for things that customers are seeing in the field that we haven't yet gotten rules in place for. It would have to be an opt in type of thing due to the European regulations and requirements around "offline" functionality for high security customers.
>
> Getting more feedback and allowing people to contribute without contributing code is absolutely key. Good job Jess!
>
> Brad Davis
> Senior Manager, Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Rodney Russ" <rruss at redhat.com>
> To: "Windup-dev List" <windup-dev at lists.jboss.org>
> Sent: Thursday, July 9, 2015 7:22:22 PM
> Subject: Re: [windup-dev] Screenshot of feedback form for feedback
>
> Would you need to know where it's used, both file/class and perhaps
> application?
>
> On 9 Jul 2015, at 17:16, Jess Sightler wrote:
>
>> Attached... let me know what you think, please.
>>
>> [Screenshot from 2015-07-09 19-15-37.png]
>> _______________________________________________
>> 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
From lincolnbaxter at gmail.com Wed Jul 15 11:08:39 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 15 Jul 2015 11:08:39 -0400
Subject: [windup-dev] Windup Meeting Minutes - 2015-07-15
Message-ID: <CAEp_U4G-H1Lx6PKoTrw2rX29g-cL8bNz46Oz8XzBExnmotzJpQ@mail.gmail.com>
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-07-15-14.01.html
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-07-15-14.01.txt
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2015/windup.2015-07-15-14.01.log.html
Meeting summary
---------------
* Agenda (lincolnthree, 14:01:49)
* Status reports (lincolnthree, 14:04:20)
* LINK:
https://plus.google.com/hangouts/_/gzeiu5f7fuxrtkbtemqlzxmmfea?hl=en
? (ozizka, 14:04:56)
* I have worked on finishing up PRs for a couple of things (including
a report that is keyed on issues rather than filenames) (jsightler,
14:05:52)
* I have also worked on a mockup of the feedback form, though I think
that may change depending upon the outcome of the meeting about the
server component (authentication, etc) (jsightler, 14:06:34)
* I have also been starting some research into openshift (setting up a
local OSE instance for some testing being the main thing there) to
start learning what is new (err, everything :)) (jsightler,
14:07:07)
* Next, I will return to the feedback form stuff and hopefully start
working on some of the tasks for it (jsightler, 14:07:34)
* I sent https://github.com/windup/windup/pull/635 for small fix in
reports (marekn, 14:07:48)
* also was discovering more sources in windup core (marekn, 14:07:48)
* and collected existing feedback for windup reports from rob and marc
(marekn, 14:07:48)
* continue on Marc's responce to my questions wrt reports (marekn,
14:09:56)
* and probably will try to implement jsf/jsp report ? (marekn,
14:10:20)
* Last week/few days I've been working on the usual PR review.
(lincolnthree, 14:11:51)
* I' also did a bunch of research on agile tools and worked on getting
us set up in Taiga (lincolnthree, 14:12:10)
* I've been working on Story 3 - reviewing the remaining non-QAd
rules/rulesets (lincolnthree, 14:12:31)
* That's done now, waiting on the discussion about which rulesets to
review/include. (lincolnthree, 14:12:46)
* I also started to engage the legal team about how we do this
feedback form and stay within the law (lincolnthree, 14:13:09)
* I plan to continue working on those things today, more PR review,
management meeting, etc. (lincolnthree, 14:13:23)
* no blockers for me (lincolnthree, 14:13:30)
* Been working on WINDUP-679, currently making the test work. See PR
633. (ozizka, 14:13:43)
* Hit and reported FURNACE-59. Then I was having difficulties with a
classloading problem - JBL LogManagager was missing in random
addons. Added to root pom as test dependency. (ozizka, 14:13:43)
* Also implemented WINDUP-665 - PR after meeting (but there's no use
of it yet). (ozizka, 14:13:44)
* Next: Finishing WINDUP-679, then I'll take one of stories. (ozizka,
14:13:44)
* I was reviewing few PRs (mbriskar, 14:19:51)
* I added File condition for the cases where file content is not
important and we want to match on the file as a whole (mbriskar,
14:19:51)
* I made rexster more convenient to work with. Now it should start
everytime you run test with -Dmaven.surefire.debug ! :) (mbriskar,
14:20:21)
* LINK: https://github.com/tinkerpop/rexster/wiki/RexPro (mbriskar,
14:23:08)
* I finished working on exporting CSV file and I am about to start
working on the server service accepting requests (mbriskar,
14:24:26)
* Meeting format (lincolnthree, 14:27:26)
* rest server service (lincolnthree, 14:34:53)
* LINK:
https://docs.google.com/a/redhat.com/drawings/d/1bMRYzEPMvyPksOhm5FBJf7g3OtY2AYyVEd1H75Vl0gk/edit?usp=sharing
(ozizka, 14:57:22)
Meeting ended at 15:04:53 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/20150715/7c66e36f/attachment.html
From ozizka at redhat.com Wed Jul 22 11:04:22 2015
From: ozizka at redhat.com (ozizka at redhat.com)
Date: Wed, 22 Jul 2015 15:04:22 +0000
Subject: [windup-dev] Canceled Event: Windup Status Meeting @ Weekly from
16:00 to 17:00 on Wednesday (Windup Project Calendar)
Message-ID: <047d7b8746c4fec834051b7815d0@google.com>
This event has been canceled and removed from your calendar.
Title: Windup Status Meeting
When: Weekly from 16:00 to 17:00 on Wednesday Central European Time - Prague
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
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.
Forwarding this invitation could allow any recipient to modify your RSVP
response. Learn more at
https://support.google.com/calendar/answer/37135#forwarding
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150722/d3f587d0/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 2204 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150722/d3f587d0/attachment-0002.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: application/ics
Size: 2262 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150722/d3f587d0/attachment-0003.bin
From ozizka at redhat.com Wed Jul 22 11:04:22 2015
From: ozizka at redhat.com (ozizka at redhat.com)
Date: Wed, 22 Jul 2015 15:04:22 +0000
Subject: [windup-dev] Canceled Event: Windup Status Meeting @ Weekly from
16:00 to 17:00 on Wednesday (Windup Project Calendar)
Message-ID: <047d7bb040a2fe4cba051b7815d2@google.com>
This event has been canceled and removed from your calendar.
Title: Windup Status Meeting
When: Weekly from 16:00 to 17:00 on Wednesday Central European Time - Prague
Where: #windup on irc.freenode.net
Calendar: Windup Project Calendar
Who:
* Lincoln Baxter, III - creator
* pmuir at redhat.com
* jsightle at redhat.com
* Robb Greathouse
* windup-dev at lists.jboss.org
* Brad Davis
* bgeorges at redhat.com
* Ondra ?i?ka
* Jesse Sightler
* Robb Greathouse
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.
Forwarding this invitation could allow any recipient to modify your RSVP
response. Learn more at
https://support.google.com/calendar/answer/37135#forwarding
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20150722/ce03ea56/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 2198 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150722/ce03ea56/attachment.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: application/ics
Size: 2256 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/windup-dev/attachments/20150722/ce03ea56/attachment-0001.bin
From mnovotny at redhat.com Thu Jul 23 02:04:25 2015
From: mnovotny at redhat.com (Marek Novotny)
Date: Thu, 23 Jul 2015 08:04:25 +0200
Subject: [windup-dev] Fwd: Re: Tattletale future?
In-Reply-To: <55AFAB0B.1020701@redhat.com>
References: <55AFAB0B.1020701@redhat.com>
Message-ID: <55B083E9.3060701@redhat.com>
Hi windup devs,
I asked Jesper what is the plan with tattletale and below is his response.
I think we probably need replace the features by merging it into our
codebase or just fork tattletale as its future is stalled and that means
our fork won't need updates from upstream/original tattletale stream.
Are you fine with that? I am asking due this related issue
https://issues.jboss.org/browse/WINDUP-699, but there will be probably
more reasons, list your own if you have any ;)
-------- Forwarded Message --------
Subject: Re: Tattletale future?
Date: Wed, 22 Jul 2015 10:39:07 -0400
From: Jesper Pedersen <jpederse at redhat.com>
Organization: JBoss, by Red Hat
To: mnovotny at redhat.com
Hi,
On 07/22/2015 10:30 AM, Marek Novotny wrote:
> I was looking in Tattletale github repository and it seems it is a long
> time from the last commit
Project has been dead for 3 years now.
> and PRs are were waiting in a queue.
>
Likely because they are incomplete or wrong - but whatever works for
people. I'm not spending time on it though.
> What's the plan for Tattletale project?
>
There are no plans to activate the project again.
Best regards,
Jesper
From lincolnbaxter at gmail.com Thu Jul 23 16:36:10 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 23 Jul 2015 16:36:10 -0400
Subject: [windup-dev] Fwd: Re: Tattletale future?
In-Reply-To: <55B083E9.3060701@redhat.com>
References: <55AFAB0B.1020701@redhat.com>
<55B083E9.3060701@redhat.com>
Message-ID: <CAEp_U4G0Wb9rJ9Hyj7NK9+CSnyJGmxERZVMYHe=qwptJiq_6FA@mail.gmail.com>
I guess in principle I'm fine with forking Tattletale into our repo, and
publishing it under a different artifact, but in reality, I don't know that
it's at all useful. I think we might better spend our time figuring out why
people want it (if they want it) and then deciding if it's worth
maintaining it.
Do we have any users that actually use this feature? Robb, why did you want
Tattletale? Marc? Brad? Tobias? Thoughts?
~Lincoln
On Thu, Jul 23, 2015 at 2:04 AM, Marek Novotny <mnovotny at redhat.com> wrote:
> Hi windup devs,
>
> I asked Jesper what is the plan with tattletale and below is his response.
>
> I think we probably need replace the features by merging it into our
> codebase or just fork tattletale as its future is stalled and that means
> our fork won't need updates from upstream/original tattletale stream.
>
> Are you fine with that? I am asking due this related issue
> https://issues.jboss.org/browse/WINDUP-699, but there will be probably
> more reasons, list your own if you have any ;)
>
> -------- Forwarded Message --------
> Subject: Re: Tattletale future?
> Date: Wed, 22 Jul 2015 10:39:07 -0400
> From: Jesper Pedersen <jpederse at redhat.com>
> Organization: JBoss, by Red Hat
> To: mnovotny at redhat.com
>
> Hi,
>
> On 07/22/2015 10:30 AM, Marek Novotny wrote:
> > I was looking in Tattletale github repository and it seems it is a long
> > time from the last commit
>
> Project has been dead for 3 years now.
>
> > and PRs are were waiting in a queue.
> >
>
> Likely because they are incomplete or wrong - but whatever works for
> people. I'm not spending time on it though.
>
> > What's the plan for Tattletale project?
> >
>
> There are no plans to activate the project again.
>
> Best regards,
> Jesper
>
>
>
> _______________________________________________
> 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/20150723/51b91785/attachment.html
From bdavis at redhat.com Thu Jul 23 16:48:18 2015
From: bdavis at redhat.com (Brad Davis)
Date: Thu, 23 Jul 2015 16:48:18 -0400 (EDT)
Subject: [windup-dev] Fwd: Re: Tattletale future?
In-Reply-To: <CAEp_U4G0Wb9rJ9Hyj7NK9+CSnyJGmxERZVMYHe=qwptJiq_6FA@mail.gmail.com>
References: <55AFAB0B.1020701@redhat.com> <55B083E9.3060701@redhat.com>
<CAEp_U4G0Wb9rJ9Hyj7NK9+CSnyJGmxERZVMYHe=qwptJiq_6FA@mail.gmail.com>
Message-ID: <2048673886.2792409.1437684498940.JavaMail.zimbra@redhat.com>
Tattletale was useful because it provided proactive reporting on classloader issues that are common with migrations. The codebase isn't worth reusing -- he embedded most of the logic quickly into the UI code.
The main functionality that matters is:
* Take all of the classes in the application: APPLICATION_CLASSES
* Take all of the classes exposed to the application from the app server: MODULE_CLASSES
* Take all of the classes that are part of your Java platform: JAVA_PLATFORM_CLASSES
(These are all classes provided to the Application) AVAILABLE
* Take all of the classes referenced in the application
(These are all classes consumed by the Application) CONSUMED
Create the following reports:
CONSUMED - AVAILABLE = That will show you if your application is likely to have a classloader issue.
Intersection of APPLICATION_CLASSES & MODULE_CLASSES = The JAR files that you might be able to drop from your application if you add in the appropriate JBoss Module Configuration
Intersection of APPLICATION_CLASSES & JAVA_PLATFORM_CLASSES = The JAR files you can and should drop from your application
In order to do this, we would have to have an index of Java Classes:
* For all versions of Java JDK : 1.6+
* For all versions of JBoss EAP 6.X
* Indexed to include the module providing the class
Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com>
To: "Marek Novotny" <mnovotny at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>, "Marc Zottner" <mzottner at redhat.com>, "Robb Greathouse" <rgreatho at redhat.com>, "Tobias Hartwig" <thartwig at redhat.com>, "Brad Davis" <bdavis at redhat.com>
Sent: Thursday, July 23, 2015 4:36:10 PM
Subject: Re: [windup-dev] Fwd: Re: Tattletale future?
I guess in principle I'm fine with forking Tattletale into our repo, and
publishing it under a different artifact, but in reality, I don't know that
it's at all useful. I think we might better spend our time figuring out why
people want it (if they want it) and then deciding if it's worth
maintaining it.
Do we have any users that actually use this feature? Robb, why did you want
Tattletale? Marc? Brad? Tobias? Thoughts?
~Lincoln
On Thu, Jul 23, 2015 at 2:04 AM, Marek Novotny <mnovotny at redhat.com> wrote:
> Hi windup devs,
>
> I asked Jesper what is the plan with tattletale and below is his response.
>
> I think we probably need replace the features by merging it into our
> codebase or just fork tattletale as its future is stalled and that means
> our fork won't need updates from upstream/original tattletale stream.
>
> Are you fine with that? I am asking due this related issue
> https://issues.jboss.org/browse/WINDUP-699, but there will be probably
> more reasons, list your own if you have any ;)
>
> -------- Forwarded Message --------
> Subject: Re: Tattletale future?
> Date: Wed, 22 Jul 2015 10:39:07 -0400
> From: Jesper Pedersen <jpederse at redhat.com>
> Organization: JBoss, by Red Hat
> To: mnovotny at redhat.com
>
> Hi,
>
> On 07/22/2015 10:30 AM, Marek Novotny wrote:
> > I was looking in Tattletale github repository and it seems it is a long
> > time from the last commit
>
> Project has been dead for 3 years now.
>
> > and PRs are were waiting in a queue.
> >
>
> Likely because they are incomplete or wrong - but whatever works for
> people. I'm not spending time on it though.
>
> > What's the plan for Tattletale project?
> >
>
> There are no plans to activate the project again.
>
> Best regards,
> Jesper
>
>
>
> _______________________________________________
> 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."
From mnovotny at redhat.com Fri Jul 24 07:04:38 2015
From: mnovotny at redhat.com (Marek Novotny)
Date: Fri, 24 Jul 2015 13:04:38 +0200
Subject: [windup-dev] Fwd: Re: Tattletale future?
In-Reply-To: <CAEp_U4G0Wb9rJ9Hyj7NK9+CSnyJGmxERZVMYHe=qwptJiq_6FA@mail.gmail.com>
References: <55AFAB0B.1020701@redhat.com> <55B083E9.3060701@redhat.com>
<CAEp_U4G0Wb9rJ9Hyj7NK9+CSnyJGmxERZVMYHe=qwptJiq_6FA@mail.gmail.com>
Message-ID: <55B21BC6.2040709@redhat.com>
On 23.7.2015 22:36, Lincoln Baxter, III wrote:
> I guess in principle I'm fine with forking Tattletale into our repo, and
> publishing it under a different artifact, but in reality, I don't know
> that it's at all useful. I think we might better spend our time figuring
> out why people want it (if they want it) and then deciding if it's worth
> maintaining it.
I would agree as it needs additionally conversion from ant+ivy build
system Maven to be able smooth integration like other forks in windup are.
So the question is if we need it or we need to re-implement those
features we consider as required.
>
> Do we have any users that actually use this feature? Robb, why did you
> want Tattletale? Marc? Brad? Tobias? Thoughts?
>
> ~Lincoln
>
> On Thu, Jul 23, 2015 at 2:04 AM, Marek Novotny <mnovotny at redhat.com
> <mailto:mnovotny at redhat.com>> wrote:
>
> Hi windup devs,
>
> I asked Jesper what is the plan with tattletale and below is his
> response.
>
> I think we probably need replace the features by merging it into our
> codebase or just fork tattletale as its future is stalled and that means
> our fork won't need updates from upstream/original tattletale stream.
>
> Are you fine with that? I am asking due this related issue
> https://issues.jboss.org/browse/WINDUP-699, but there will be probably
> more reasons, list your own if you have any ;)
>
> -------- Forwarded Message --------
> Subject: Re: Tattletale future?
> Date: Wed, 22 Jul 2015 10:39:07 -0400
> From: Jesper Pedersen <jpederse at redhat.com <mailto:jpederse at redhat.com>>
> Organization: JBoss, by Red Hat
> To: mnovotny at redhat.com <mailto:mnovotny at redhat.com>
>
> Hi,
>
> On 07/22/2015 10:30 AM, Marek Novotny wrote:
> > I was looking in Tattletale github repository and it seems it is
> a long
> > time from the last commit
>
> Project has been dead for 3 years now.
>
> > and PRs are were waiting in a queue.
> >
>
> Likely because they are incomplete or wrong - but whatever works for
> people. I'm not spending time on it though.
>
> > What's the plan for Tattletale project?
> >
>
> There are no plans to activate the project again.
>
> Best regards,
> Jesper
>
>
>
> _______________________________________________
> 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."
--
Marek Novotny
--
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
From lincolnbaxter at gmail.com Fri Jul 24 12:41:52 2015
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Fri, 24 Jul 2015 12:41:52 -0400
Subject: [windup-dev] Fwd: Re: Tattletale future?
In-Reply-To: <2048673886.2792409.1437684498940.JavaMail.zimbra@redhat.com>
References: <55AFAB0B.1020701@redhat.com> <55B083E9.3060701@redhat.com>
<CAEp_U4G0Wb9rJ9Hyj7NK9+CSnyJGmxERZVMYHe=qwptJiq_6FA@mail.gmail.com>
<2048673886.2792409.1437684498940.JavaMail.zimbra@redhat.com>
Message-ID: <CAEp_U4GeXeHU1HSuxdHbwvb2YzVBktJ2AD226D987Jbt7_FD+A@mail.gmail.com>
I think that what Jess has done with the "Unresolved classes" detection, is
already a more useful start than the Tattletale reports. I'd love to see
this as the basis for the new report. This can even be rectified against a
server profile (such as an EAP6 snapshot) - Ondra was working on this a
little while ago before we de-prioritized the server migration stuff in
favor of summit prep.
On Thu, Jul 23, 2015 at 4:48 PM, Brad Davis <bdavis at redhat.com> wrote:
> Tattletale was useful because it provided proactive reporting on
> classloader issues that are common with migrations. The codebase isn't
> worth reusing -- he embedded most of the logic quickly into the UI code.
>
> The main functionality that matters is:
> * Take all of the classes in the application: APPLICATION_CLASSES
> * Take all of the classes exposed to the application from the app server:
> MODULE_CLASSES
> * Take all of the classes that are part of your Java platform:
> JAVA_PLATFORM_CLASSES
> (These are all classes provided to the Application) AVAILABLE
>
> * Take all of the classes referenced in the application
> (These are all classes consumed by the Application) CONSUMED
>
> Create the following reports:
> CONSUMED - AVAILABLE = That will show you if your application is likely
> to have a classloader issue.
> Intersection of APPLICATION_CLASSES & MODULE_CLASSES = The JAR files that
> you might be able to drop from your application if you add in the
> appropriate JBoss Module Configuration
> Intersection of APPLICATION_CLASSES & JAVA_PLATFORM_CLASSES = The JAR
> files you can and should drop from your application
>
>
> In order to do this, we would have to have an index of Java Classes:
> * For all versions of Java JDK : 1.6+
> * For all versions of JBoss EAP 6.X
> * Indexed to include the module providing the class
>
>
>
>
> Brad Davis
> Senior Manager, Red Hat Consulting
> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com>
> To: "Marek Novotny" <mnovotny at redhat.com>, "Windup-dev List" <
> windup-dev at lists.jboss.org>, "Marc Zottner" <mzottner at redhat.com>, "Robb
> Greathouse" <rgreatho at redhat.com>, "Tobias Hartwig" <thartwig at redhat.com>,
> "Brad Davis" <bdavis at redhat.com>
> Sent: Thursday, July 23, 2015 4:36:10 PM
> Subject: Re: [windup-dev] Fwd: Re: Tattletale future?
>
> I guess in principle I'm fine with forking Tattletale into our repo, and
> publishing it under a different artifact, but in reality, I don't know that
> it's at all useful. I think we might better spend our time figuring out why
> people want it (if they want it) and then deciding if it's worth
> maintaining it.
>
> Do we have any users that actually use this feature? Robb, why did you want
> Tattletale? Marc? Brad? Tobias? Thoughts?
>
> ~Lincoln
>
> On Thu, Jul 23, 2015 at 2:04 AM, Marek Novotny <mnovotny at redhat.com>
> wrote:
>
> > Hi windup devs,
> >
> > I asked Jesper what is the plan with tattletale and below is his
> response.
> >
> > I think we probably need replace the features by merging it into our
> > codebase or just fork tattletale as its future is stalled and that means
> > our fork won't need updates from upstream/original tattletale stream.
> >
> > Are you fine with that? I am asking due this related issue
> > https://issues.jboss.org/browse/WINDUP-699, but there will be probably
> > more reasons, list your own if you have any ;)
> >
> > -------- Forwarded Message --------
> > Subject: Re: Tattletale future?
> > Date: Wed, 22 Jul 2015 10:39:07 -0400
> > From: Jesper Pedersen <jpederse at redhat.com>
> > Organization: JBoss, by Red Hat
> > To: mnovotny at redhat.com
> >
> > Hi,
> >
> > On 07/22/2015 10:30 AM, Marek Novotny wrote:
> > > I was looking in Tattletale github repository and it seems it is a
> long
> > > time from the last commit
> >
> > Project has been dead for 3 years now.
> >
> > > and PRs are were waiting in a queue.
> > >
> >
> > Likely because they are incomplete or wrong - but whatever works for
> > people. I'm not spending time on it though.
> >
> > > What's the plan for Tattletale project?
> > >
> >
> > There are no plans to activate the project again.
> >
> > Best regards,
> > Jesper
> >
> >
> >
> > _______________________________________________
> > 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/20150724/09349f7c/attachment.html
From mnovotny at redhat.com Tue Jul 28 04:27:56 2015
From: mnovotny at redhat.com (Marek Novotny)
Date: Tue, 28 Jul 2015 10:27:56 +0200
Subject: [windup-dev] Automatic upgrading (of the whole app) discussion
In-Reply-To: <55B6DE51.40207@redhat.com>
References: <55B6DE51.40207@redhat.com>
Message-ID: <55B73D0C.1020501@redhat.com>
First of all I think this gather to windup-dev list.
Secondly I think the safest way is to clone the current distribution and
do the upgrade on it and then before shutdown the furnace just copy
cloned and upgraded distro back to current place.
On 28.7.2015 03:43, Ondrej Zizka wrote:
> Hi all,
>
> what should be the approach to upgrading?
>
> Current implementation simply replaces the files on the fly (as a
> command), and it seems it isn't bulletproof. Changing files under
> Furnace's hands seems to break things. I get various FileNotFound and
> dependency failures. Also, we currently do not have a way to run other
> command than windup-migrate-app.
>
> Other approach could be to download the file, unzip to a temp directory,
> and right before Windup's process shuts down, after Furnace is closed,
> it would swap the existing and the new directories.
> So next time, the new version would boot.
> Would that be ok?
>
> Then we would need to address the possibility of rules changed by the
> user inside of the windup directory.
>
> Ideas?
> Ondra
>
--
Marek Novotny
--
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
From ozizka at redhat.com Wed Jul 29 04:20:08 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 29 Jul 2015 10:20:08 +0200
Subject: [windup-dev] Automatic upgrading (of the whole app) discussion
In-Reply-To: <55B73D0C.1020501@redhat.com>
References: <55B6DE51.40207@redhat.com> <55B73D0C.1020501@redhat.com>
Message-ID: <55B88CB8.6020609@redhat.com>
Ah, here I found this post.
I am not sure about cloning. Only the rules could be potentially needed
to transfer. And maybe the .ignore files.
Hence I'd rather swap the whole distro directories and then transfer the
XML rules. To keep the process simple and to avoid collisions when we
change some dir structure.
WDYT?
Ondra
On 28.7.2015 10:27, Marek Novotny wrote:
> First of all I think this gather to windup-dev list.
>
> Secondly I think the safest way is to clone the current distribution and
> do the upgrade on it and then before shutdown the furnace just copy
> cloned and upgraded distro back to current place.
>
>
>
> On 28.7.2015 03:43, Ondrej Zizka wrote:
>> Hi all,
>>
>> what should be the approach to upgrading?
>>
>> Current implementation simply replaces the files on the fly (as a
>> command), and it seems it isn't bulletproof. Changing files under
>> Furnace's hands seems to break things. I get various FileNotFound and
>> dependency failures. Also, we currently do not have a way to run other
>> command than windup-migrate-app.
>>
>> Other approach could be to download the file, unzip to a temp directory,
>> and right before Windup's process shuts down, after Furnace is closed,
>> it would swap the existing and the new directories.
>> So next time, the new version would boot.
>> Would that be ok?
>>
>> Then we would need to address the possibility of rules changed by the
>> user inside of the windup directory.
>>
>> Ideas?
>> Ondra
>>
>
From mnovotny at redhat.com Thu Jul 30 04:47:17 2015
From: mnovotny at redhat.com (Marek Novotny)
Date: Thu, 30 Jul 2015 10:47:17 +0200
Subject: [windup-dev] Automatic upgrading (of the whole app) discussion
In-Reply-To: <55B88CB8.6020609@redhat.com>
References: <55B6DE51.40207@redhat.com> <55B73D0C.1020501@redhat.com>
<55B88CB8.6020609@redhat.com>
Message-ID: <55B9E495.40307@redhat.com>
well we both probably meant the same way as you said the replacing files
on the fly is problematic.
I would say I am fine with that.
Btw are directory like cache significant too in addition to ignore and
rules directories in end user customization?
On 29.7.2015 10:20, Ondrej Zizka wrote:
> Ah, here I found this post.
>
> I am not sure about cloning. Only the rules could be potentially needed
> to transfer. And maybe the .ignore files.
> Hence I'd rather swap the whole distro directories and then transfer the
> XML rules. To keep the process simple and to avoid collisions when we
> change some dir structure.
>
> WDYT?
> Ondra
>
>
> On 28.7.2015 10:27, Marek Novotny wrote:
>> First of all I think this gather to windup-dev list.
>>
>> Secondly I think the safest way is to clone the current distribution and
>> do the upgrade on it and then before shutdown the furnace just copy
>> cloned and upgraded distro back to current place.
>>
>>
>>
>> On 28.7.2015 03:43, Ondrej Zizka wrote:
>>> Hi all,
>>>
>>> what should be the approach to upgrading?
>>>
>>> Current implementation simply replaces the files on the fly (as a
>>> command), and it seems it isn't bulletproof. Changing files under
>>> Furnace's hands seems to break things. I get various FileNotFound and
>>> dependency failures. Also, we currently do not have a way to run other
>>> command than windup-migrate-app.
>>>
>>> Other approach could be to download the file, unzip to a temp directory,
>>> and right before Windup's process shuts down, after Furnace is closed,
>>> it would swap the existing and the new directories.
>>> So next time, the new version would boot.
>>> Would that be ok?
>>>
>>> Then we would need to address the possibility of rules changed by the
>>> user inside of the windup directory.
>>>
>>> Ideas?
>>> Ondra
>>>
>>
>
> _______________________________________________
> 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 ozizka at redhat.com Thu Jul 30 07:52:18 2015
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 30 Jul 2015 13:52:18 +0200
Subject: [windup-dev] Automatic upgrading (of the whole app) discussion
In-Reply-To: <55B9E495.40307@redhat.com>
References: <55B6DE51.40207@redhat.com>
<55B73D0C.1020501@redhat.com> <55B88CB8.6020609@redhat.com>
<55B9E495.40307@redhat.com>
Message-ID: <55BA0FF2.8050802@redhat.com>
Regarding cache/, as the name hints, it can get recreated, and I'd opt
for that, even if it would take some time - it's more robust approach.
Other dirs, I think what's left is the ignore stuff, I'd convert as
well. But since it's user editable stuff, it might need some merging.
Ondra
On 30.7.2015 10:47, Marek Novotny wrote:
> well we both probably meant the same way as you said the replacing files
> on the fly is problematic.
>
> I would say I am fine with that.
> Btw are directory like cache significant too in addition to ignore and
> rules directories in end user customization?
>
> On 29.7.2015 10:20, Ondrej Zizka wrote:
>> Ah, here I found this post.
>>
>> I am not sure about cloning. Only the rules could be potentially needed
>> to transfer. And maybe the .ignore files.
>> Hence I'd rather swap the whole distro directories and then transfer the
>> XML rules. To keep the process simple and to avoid collisions when we
>> change some dir structure.
>>
>> WDYT?
>> Ondra
>>
>>
>> On 28.7.2015 10:27, Marek Novotny wrote:
>>> First of all I think this gather to windup-dev list.
>>>
>>> Secondly I think the safest way is to clone the current distribution and
>>> do the upgrade on it and then before shutdown the furnace just copy
>>> cloned and upgraded distro back to current place.
>>>
>>>
>>>
>>> On 28.7.2015 03:43, Ondrej Zizka wrote:
>>>> Hi all,
>>>>
>>>> what should be the approach to upgrading?
>>>>
>>>> Current implementation simply replaces the files on the fly (as a
>>>> command), and it seems it isn't bulletproof. Changing files under
>>>> Furnace's hands seems to break things. I get various FileNotFound and
>>>> dependency failures. Also, we currently do not have a way to run other
>>>> command than windup-migrate-app.
>>>>
>>>> Other approach could be to download the file, unzip to a temp directory,
>>>> and right before Windup's process shuts down, after Furnace is closed,
>>>> it would swap the existing and the new directories.
>>>> So next time, the new version would boot.
>>>> Would that be ok?
>>>>
>>>> Then we would need to address the possibility of rules changed by the
>>>> user inside of the windup directory.
>>>>
>>>> Ideas?
>>>> Ondra
>>>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>