[JBoss JIRA] (JBIDE-14597) ng-app AngularJS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14597?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-14597:
----------------------------------------
Fix Version/s: 4.1.2.CR1
(was: 4.2.x)
> ng-app AngularJS
> ----------------
>
> Key: JBIDE-14597
> URL: https://issues.jboss.org/browse/JBIDE-14597
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Reporter: Burr Sutter
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.1.2.CR1
>
> Attachments: 2013-05-23_0752.png, 2013-05-23_1548.png, html5_demo.fsh, Screen Shot 2013-05-23 at 3.51.53 PM.png
>
>
> Warning:
> Undefined attribute name (ng-app).
> Undefined attribute name (ng-controller).
> AngularJS is part of the new HTML5 Scaffolding feature in Forge 1.3
> forge install-plugin angularjs
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-14426) Add arquillian support dialog is too bare-bones
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14426?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-14426:
---------------------------------------
I have created a new "Add Arquillian support" dialog. See http://screencast.com/t/74xdiaQQZxOK.
Now, a user can control updating the entire pom.xml file, the dependencies, build and profiles sections.
There is also a preview so that a user can review changes in the pom.xml file.
> Add arquillian support dialog is too bare-bones
> -----------------------------------------------
>
> Key: JBIDE-14426
> URL: https://issues.jboss.org/browse/JBIDE-14426
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Fix For: 4.2.0.Alpha2
>
>
> Using Configure Arquillian Support just asks if I want to add Arquillian support + link to global arquillian settings.
> Following thing should be done IMO,
> A) When saying yes, it should preview what changes are going to happen (changing pom.xml by default)
> B) I should be able to say no, don't change pom, and just have arquillian nature added (i.e. assume the classpath contain what is needed, warn if possible problems) - optimally not require Maven to be on the project.
> C) On the "next" page let user configure the settings he wish applied (now I have to go to global preferences first and change those which might not be what one wants)
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-14426) Add arquillian support dialog is too bare-bones
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14426?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-14426:
----------------------------------
Fix Version/s: 4.2.0.Alpha2
(was: 4.1.x)
> Add arquillian support dialog is too bare-bones
> -----------------------------------------------
>
> Key: JBIDE-14426
> URL: https://issues.jboss.org/browse/JBIDE-14426
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Fix For: 4.2.0.Alpha2
>
>
> Using Configure Arquillian Support just asks if I want to add Arquillian support + link to global arquillian settings.
> Following thing should be done IMO,
> A) When saying yes, it should preview what changes are going to happen (changing pom.xml by default)
> B) I should be able to say no, don't change pom, and just have arquillian nature added (i.e. assume the classpath contain what is needed, warn if possible problems) - optimally not require Maven to be on the project.
> C) On the "next" page let user configure the settings he wish applied (now I have to go to global preferences first and change those which might not be what one wants)
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-16351) FixClasspathConfigurator isn't obliged in a newer m2e
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16351?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-16351:
---------------------------------------
I have tested the old Seam 2 projects as well as WFK Seam 2.3 demo. FixClasspathConfigurator doesn't affect those projects because m2e, now, copies resources placed outside the project source tree to the project's output folder.
Old Seam 2 projects (especially test project) don't work with JBT 4.1 with or without this configurator. You can create a separate jira related to that issue.
WFK Seam demo projects work properly.
{quote}
Shouldn't it be enough to just apply FixClasspathConfigurator on projects having the seam nature, then check if seam version < 2.3?
{quote}
That would unnecessarily decrease performance and wouldn't solve anything.
> FixClasspathConfigurator isn't obliged in a newer m2e
> -----------------------------------------------------
>
> Key: JBIDE-16351
> URL: https://issues.jboss.org/browse/JBIDE-16351
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: maven
> Affects Versions: 4.2.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
>
> The FixClasspathConfigurator configurator has been introduced to solve https://issues.sonatype.org/browse/MNGECLIPSE-2433.
> The issue happens with a mavenized seam 2 project that has a flat layout structure.
> This configurator refreshes the old maven facade causing m2e to solve dependencies twice when ever building a project.
> It is the configurator for maven-compiler-plugin so it is called for every Java project.
> Since solving dependencies can take a long, it can slow down building projects up to 15% (depends on the project's dependencies)
> The solution:
> - removing the configurator. The issue is only related to the mavenized Seam projects that aren't included into project examples anymore and a required classpath entry can be manually added(newer m2 versions won't remove the existing classpath entry).
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-16351) FixClasspathConfigurator isn't obliged in a newer m2e
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16351?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-16351:
-------------------------------------
My fear is we'll break old Seam 2-based projects.
Shouldn't it be enough to just apply FixClasspathConfigurator on projects having the seam nature, then check if seam version < 2.3?
> FixClasspathConfigurator isn't obliged in a newer m2e
> -----------------------------------------------------
>
> Key: JBIDE-16351
> URL: https://issues.jboss.org/browse/JBIDE-16351
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: maven
> Affects Versions: 4.2.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
>
> The FixClasspathConfigurator configurator has been introduced to solve https://issues.sonatype.org/browse/MNGECLIPSE-2433.
> The issue happens with a mavenized seam 2 project that has a flat layout structure.
> This configurator refreshes the old maven facade causing m2e to solve dependencies twice when ever building a project.
> It is the configurator for maven-compiler-plugin so it is called for every Java project.
> Since solving dependencies can take a long, it can slow down building projects up to 15% (depends on the project's dependencies)
> The solution:
> - removing the configurator. The issue is only related to the mavenized Seam projects that aren't included into project examples anymore and a required classpath entry can be manually added(newer m2 versions won't remove the existing classpath entry).
--
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
12 years, 5 months
[JBoss JIRA] (JBDS-2881) Make clear the distinction between update.zip and central.zip on access.redhat
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2881?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2881:
----------------------------------
Yes, though you can also install from the Update Zip into JBDS (not just Eclipse) and from the Central Zip into Eclipse (not just JBDS). So I'd reword things a little...
Update zip:
"It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 (Kepler) or JBoss Developer Studio 7.x installation, if working offline."
Central zip:
"It can be used to install additional JBoss Developer Studio and third-party features available from JBoss Central into your existing Eclipse 4.3 (Kepler) or JBoss Developer Studio 7.x installation, if working offline."
> Make clear the distinction between update.zip and central.zip on access.redhat
> ------------------------------------------------------------------------------
>
> Key: JBDS-2881
> URL: https://issues.jboss.org/browse/JBDS-2881
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: build, updatesite
> Affects Versions: 7.1.0.GA
> Reporter: Michelle Murray
>
> [1] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof...
> [2] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof...
> On the download pages for individual JBDS zips, we need to make clear the distinction between update.zip and central.zip.
> update.zip and central.zip Detailed Description both read: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation."
> Can the text [1] for update.zip be modified to: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation if working offline."
> Can the text [2] for central.zip be modified to read something like: "It can be used to install additional JBoss Developer Studio and third-party features available from JBoss Central into JBoss Developer Studio if working offline."
--
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
12 years, 5 months
[JBoss JIRA] (JBTIS-236) Problem with BPMN when updated to newer version
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBTIS-236?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated JBTIS-236:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1059217
> Problem with BPMN when updated to newer version
> -----------------------------------------------
>
> Key: JBTIS-236
> URL: https://issues.jboss.org/browse/JBTIS-236
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 7.0.0.Final-JBDSIS
> Reporter: Andrej Podhradsky
> Priority: Minor
> Attachments: bpmn_editor.png, jbds.log
>
>
> Assume a user has JBDS-IS of version 7.0.0.Beta4 and then he wants to update his/her JBDS-IS to current version. But after updating there are issues with BPMN as follows
> 1. Creating new SwitchYard project causes the following error:
> Plug-in org.eclipse.bpmn2.modeler.runtime.example was unable to load class org.eclipse.bpmn2.modeler.runtime.example.SampleCustomTaskFeatureContainer
> (See the attachment for full log)
> 2. BPMN editor is without colors (see the attachment)
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-16407) Decouple openshift from legacy astools code
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16407?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16407:
---------------------------------------------
we got several openshift requests about providing alternative publishing - like binary deployment support, hotdeploy via scp and others.
If this change is done will we have to later revert back or how ?
> Decouple openshift from legacy astools code
> -------------------------------------------
>
> Key: JBIDE-16407
> URL: https://issues.jboss.org/browse/JBIDE-16407
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Rob Stryker
> Assignee: Andre Dietisheim
>
> With coming changes to astools, openshift depends on classes that will most likely be deprecated and removed.
> Even if its not, openshift is currently using an astools framework that is really geared for servers that can change behavior heavily based on various settings. It's not quite appropriate for openshift which has only one core behavior in terms of publishing etc.
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-16407) Decouple openshift from legacy astools code
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-16407:
-----------------------------------
Summary: Decouple openshift from legacy astools code
Key: JBIDE-16407
URL: https://issues.jboss.org/browse/JBIDE-16407
Project: Tools (JBoss Tools)
Issue Type: Task
Components: openshift
Affects Versions: 4.2.0.Alpha1
Reporter: Rob Stryker
Assignee: Andre Dietisheim
With coming changes to astools, openshift depends on classes that will most likely be deprecated and removed.
Even if its not, openshift is currently using an astools framework that is really geared for servers that can change behavior heavily based on various settings. It's not quite appropriate for openshift which has only one core behavior in terms of publishing etc.
--
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
12 years, 5 months
[JBoss JIRA] (JBTIS-236) Problem with BPMN when updated to newer version
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-236?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-236:
------------------------------------
Priority: Minor (was: Major)
> Problem with BPMN when updated to newer version
> -----------------------------------------------
>
> Key: JBTIS-236
> URL: https://issues.jboss.org/browse/JBTIS-236
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 7.0.0.Final-JBDSIS
> Reporter: Andrej Podhradsky
> Priority: Minor
> Attachments: bpmn_editor.png, jbds.log
>
>
> Assume a user has JBDS-IS of version 7.0.0.Beta4 and then he wants to update his/her JBDS-IS to current version. But after updating there are issues with BPMN as follows
> 1. Creating new SwitchYard project causes the following error:
> Plug-in org.eclipse.bpmn2.modeler.runtime.example was unable to load class org.eclipse.bpmn2.modeler.runtime.example.SampleCustomTaskFeatureContainer
> (See the attachment for full log)
> 2. BPMN editor is without colors (see the attachment)
--
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
12 years, 5 months