[JBoss JIRA] (JBIDE-14527) Add source option to 'generate deployment method' on abstract classes
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14527?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-14527:
----------------------------------
Fix Version/s: 4.1.1.Alpha1
(was: 4.1.1.Final)
> Add source option to 'generate deployment method' on abstract classes
> ---------------------------------------------------------------------
>
> Key: JBIDE-14527
> URL: https://issues.jboss.org/browse/JBIDE-14527
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Aslak Knutsen
> Assignee: Snjezana Peco
> Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1
>
>
> {code}
> @RunWith(Arquillian.class)
> public abstract class AbstractTest
> {
> @Test
> public void testa() {}
> }
> {code}
> This should show no warning on 'missing deployment method' since it's a common pattern to have @Test's in a superclass with multiple sub classes that define deployments, but it's also a common pattern to have the deployment defined in a super class and multiple sub classes with different testing scenarios.
> Given a abstract class
> When there is no deployment method
> Then give the 'source' option to 'generate deployment method'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBIDE-15173) Typo: cheatsheets > cheat sheets
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15173?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-15173:
----------------------------------
Fix Version/s: 4.1.1.Alpha1
(was: 4.1.1.Final)
> Typo: cheatsheets > cheat sheets
> --------------------------------
>
> Key: JBIDE-15173
> URL: https://issues.jboss.org/browse/JBIDE-15173
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.1.0.CR1
> Reporter: Michelle Murray
> Assignee: Snjezana Peco
> Fix For: 4.1.1.Alpha1
>
> Attachments: Central_CheatSheets.png
>
>
> Typo under Window > Preferences > JBoss Tools > Project Examples (screen capture attached):
> 'Show included *cheatsheet(s)*' > 'Show included *cheat sheet(s)*'
> Cheat sheet is two words. For example, see 'Help > Cheat Sheets'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBIDE-15388) Compute whether to publish or not based on output signature rather than commits
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-15388:
--------------------------------------
Summary: Compute whether to publish or not based on output signature rather than commits
Key: JBIDE-15388
URL: https://issues.jboss.org/browse/JBIDE-15388
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: LATER
[Assuming we already have reproducible qualifiers...]
Currently, the CI jobs publish the output of a build if a change was detected in the Git repo since last publication.
However there are some case not correctly supported:
* Job configuration changed and caused changes in build output. In that case, we would like build output to be re-published, but it won't happen
* Job source changed but not build output (eg a change in a pom.xml or any non-included file), then we don't need to republish output whereas current mechanism would republish it.
instead, it would make sense to compare what's already published and what is to publish in order to decide or not whether this has to be published. Looking at signatures of update site zip would probably be enough.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBIDE-15197) Wizard for exporting mobile application out of a Hybrid Mobile project
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15197?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-15197:
---------------------------------
Fix Version/s: 4.1.1.Alpha1
(was: 4.1.x)
(was: 4.2.x)
> Wizard for exporting mobile application out of a Hybrid Mobile project
> ----------------------------------------------------------------------
>
> Key: JBIDE-15197
> URL: https://issues.jboss.org/browse/JBIDE-15197
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Priority: Minor
> Fix For: 4.1.1.Alpha1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Implement an export wizard that can create native platform's mobile application binary format. The wizard should do a "RELEASE" build to create the binaries.
> We may try to support code signing as well, however on some platforms it may actually be easier to run the native tools to complete the signing. Prototype code signing and create a separate task for it if it should be pursued further.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBIDE-15197) Wizard for exporting mobile application out of a Hybrid Mobile project
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15197?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-15197.
----------------------------------
Resolution: Done
> Wizard for exporting mobile application out of a Hybrid Mobile project
> ----------------------------------------------------------------------
>
> Key: JBIDE-15197
> URL: https://issues.jboss.org/browse/JBIDE-15197
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Priority: Minor
> Fix For: 4.1.1.Alpha1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Implement an export wizard that can create native platform's mobile application binary format. The wizard should do a "RELEASE" build to create the binaries.
> We may try to support code signing as well, however on some platforms it may actually be easier to run the native tools to complete the signing. Prototype code signing and create a separate task for it if it should be pursued further.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBDS-2414) Mylyn dialog editing - changes to server field automatically and incompletely reflected in label field
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2414?page=com.atlassian.jira.plugin.... ]
Mickael Istria reassigned JBDS-2414:
------------------------------------
Assignee: Len DiMaggio
[~ldimaggio] Assigning to you. If it's not already reported to bugs.eclipse.org, you should do it ASAP to get a chance to get it part of Luna or Kepler SR1.
> Mylyn dialog editing - changes to server field automatically and incompletely reflected in label field
> -------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2414
> URL: https://issues.jboss.org/browse/JBDS-2414
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification
> Affects Versions: 6.0.0.CR1
> Environment: Version: 6.0.0.CR1
> Build id: CR1-v20121125-1229-B133
> Build date: 20121125-1229
> Reporter: Len DiMaggio
> Assignee: Len DiMaggio
> Priority: Minor
> Fix For: 7.1.x
>
> Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot-3.png, Screenshot-4.png
>
>
> See the attached screenshots - when the user edits the server field in the Mylyn Add Task Repo dialog, the label field is automatically edited in response - but the editing is incomplete.
> The user is then left with an incomplete label field to clean up;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months