[JBoss JIRA] Created: (JBDS-1636) fix copyrights in all features
by Nick Boldt (JIRA)
fix copyrights in all features
------------------------------
Key: JBDS-1636
URL: https://issues.jboss.org/browse/JBDS-1636
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Build, documentation, Requirements
Affects Versions: 4.1.0.M1, 5.0.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.1.0.M1, 5.0.0.M1
>From Richard Fontana:
> If you are under general instructions to use "JBoss by Red Hat" for
marketing or branding purposes that's fine.
> The one place where it is not formally correct is in copyright
statements themselves. Those should at least say "Copyright <year> Red
Hat, Inc." (or, as I often recommend for JBoss source code files,
"Copyright <year> Red Hat, Inc. and/or its affiliates".
> The 'provider name' by contrast doesn't matter from a legal
perspective. It doesn't matter to me if there's some inconsistency
between provider name and copyright holder name.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBIDE-8809) Seam 2.2 DVD Store example not working with EAP 5.1.1
by Martin Malina (JIRA)
Seam 2.2 DVD Store example not working with EAP 5.1.1
-----------------------------------------------------
Key: JBIDE-8809
URL: https://issues.jboss.org/browse/JBIDE-8809
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Affects Versions: 3.2.0.Final
Environment: Mac OS X 10.6.7 Snow Leopard
Apple JDK 1.6
JBDS 4.0
JBoss EAP 5.1.1 ER1
Reporter: Martin Malina
Assignee: Snjezana Peco
The Seam 2.2 DVD Store example is not working with EAP 5.1.1 ER1. It fails to deploy.
We had a similar problem in EAP 5.1 and it was resolved by updating the project-examples to use a newer version of the example. See JBIDE-6696.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBIDE-8476) JBoss Rich Faces Editor causes Java refactoring failures for read/only SCM systems (Perforce)
by joe freeman (JIRA)
JBoss Rich Faces Editor causes Java refactoring failures for read/only SCM systems (Perforce)
---------------------------------------------------------------------------------------------
Key: JBIDE-8476
URL: https://issues.jboss.org/browse/JBIDE-8476
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.2.0.CR1
Environment: 3.2.0 GA Rich Faces Editor Mac and Windows Eclipse 3.6 Perforce (or possibly other READ/ONLY based SCM)
Reporter: joe freeman
Assignee: Alexey Kazakov
We have a large project that uses Perforce as SCM. Perforce leaves files read/only until they have been modified at which point they are checked out and made writable.
Eclipse refactoring modifies files and automatically engages the SCM Eclipse plugins on changes to optionally check the files out. In the case of Perforce, this makes the files writable on modification which allows changes to be saved. This works fine under Eclipse 3.5 with Jboss Tools.
This is broken under Eclipse 3.6, Jboss tools 3.2 when the RichFaces editor is installed and a developer attempts to rename a method using "refactor Method name". You get a set of error messages where it looks like the refactoring is trying to change read-only files. Many of the files listed are not changed by the refactoring. It's almost like the Rich Faces editor/refactor hooks is stat'ing or touching the files maybe without changing. Removing the RichFaces editor stops the problem for occurring.
No work around exists.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months