[JBoss JIRA] Updated: (JBIDE-766) EJB Preferences error
by Max Andersen (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-766?page=all ]
Max Andersen updated JBIDE-766:
-------------------------------
Component/s: xdoclet
Assignee: Rob Stryker
I don't think it is the plugin directory you should point to but your xdoclet installation.
Rob - can you confirm?
> EJB Preferences error
> ---------------------
>
> Key: JBIDE-766
> URL: http://jira.jboss.com/jira/browse/JBIDE-766
> Project: JBoss Tools
> Issue Type: Bug
> Components: xdoclet
> Affects Versions: 2.0.0.Beta3
> Environment: WindowsXP SP2
> rhds-win32-1.0.0.ALPHA.jar
> Red Hat Developer Studio
> Version: 1.0.0
> Build id: 1.0.0
> Reporter: Aliaksey Nis
> Assigned To: Rob Stryker
> Attachments: EJBPreferences.JPG
>
>
> Window -> Preferences->Xdoclet
> Look at screen shot.
> 1. I look for location of xdoclet-1.2.3.jar (using search) .
> Selecting version 1.2.3. Setting home folder path from search...
> 2. xdoclet-1.1.jar not included in studio (can't find it with search in studio folder).
> When i try to make something with EJB project - it says that "Annotation provider definition is not valid, please check the preferences."
> After few open-close Preferences, this error message disappear, but nothing still works.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months
[JBoss JIRA] Moved: (JBIDE-766) EJB Preferences error
by Max Andersen (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-766?page=all ]
Max Andersen moved EXIN-264 to JBIDE-766:
-----------------------------------------
Project: JBoss Tools (was: Exadel Integration)
Key: JBIDE-766 (was: EXIN-264)
Component/s: (was: The Lost Functionallity)
Fix Version/s: (was: 1.0.0.beta2)
Affects Version/s: 2.0.0.Beta3
(was: OPENSOURCE)
> EJB Preferences error
> ---------------------
>
> Key: JBIDE-766
> URL: http://jira.jboss.com/jira/browse/JBIDE-766
> Project: JBoss Tools
> Issue Type: Bug
> Affects Versions: 2.0.0.Beta3
> Environment: WindowsXP SP2
> rhds-win32-1.0.0.ALPHA.jar
> Red Hat Developer Studio
> Version: 1.0.0
> Build id: 1.0.0
> Reporter: Aliaksey Nis
> Attachments: EJBPreferences.JPG
>
>
> Window -> Preferences->Xdoclet
> Look at screen shot.
> 1. I look for location of xdoclet-1.2.3.jar (using search) .
> Selecting version 1.2.3. Setting home folder path from search...
> 2. xdoclet-1.1.jar not included in studio (can't find it with search in studio folder).
> When i try to make something with EJB project - it says that "Annotation provider definition is not valid, please check the preferences."
> After few open-close Preferences, this error message disappear, but nothing still works.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months
[JBoss JIRA] Moved: (JBIDE-764) Workspace refreshing problems after manual removing projects .
by Max Andersen (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-764?page=all ]
Max Andersen moved EXIN-269 to JBIDE-764:
-----------------------------------------
Project: JBoss Tools (was: Exadel Integration)
Key: JBIDE-764 (was: EXIN-269)
Component/s: (was: The Lost Functionallity)
Fix Version/s: (was: 1.0.0.beta2)
Affects Version/s: 2.0.0.Beta3
(was: OPENSOURCE)
> Workspace refreshing problems after manual removing projects .
> --------------------------------------------------------------
>
> Key: JBIDE-764
> URL: http://jira.jboss.com/jira/browse/JBIDE-764
> Project: JBoss Tools
> Issue Type: Bug
> Affects Versions: 2.0.0.Beta3
> Reporter: Anton Klimkovich
> Assigned To: Alexey Kazakov
> Attachments: NPE.txt
>
>
> First situation:
> 1 Create JSFKickStart project
> 2 Delete it manualy from workspace
> After deleting workspace will be refreshed in RHDS but some problems and exception will be( java.lang.NullPointerException
> at org.eclipse.jdt.internal.core.JavaProject.getPackageFragmentRoot(JavaProject.java:1789 ...)
> Log attached
> Second situation
> 1 Create JSFKickStart project (name - Test)
> 2 Close RHDS
> 3 Delete project manualy from workspace
> 4 Run RHDS
> 5 Try to create JSFKickStart with the name equal to deleting project. (name - Test)
> You will see the message that the project with such name already exist in workspace.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months
[JBoss JIRA] Moved: (JBIDE-763) Button in JavaClass menu
by Max Andersen (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-763?page=all ]
Max Andersen moved EXIN-286 to JBIDE-763:
-----------------------------------------
Project: JBoss Tools (was: Exadel Integration)
Key: JBIDE-763 (was: EXIN-286)
Component/s: (was: The Lost Functionallity)
Fix Version/s: 2.0.0.Beta4
(was: 1.0.0.beta2)
Affects Version/s: 2.0.0.Beta3
(was: OPENSOURCE)
> Button in JavaClass menu
> ------------------------
>
> Key: JBIDE-763
> URL: http://jira.jboss.com/jira/browse/JBIDE-763
> Project: JBoss Tools
> Issue Type: Bug
> Affects Versions: 2.0.0.Beta3
> Environment: Red Hat Enterprise Linux 5.0
> Reporter: Aliaksey Nis
> Assigned To: Viacheslav Kabanovich
> Priority: Trivial
> Fix For: 2.0.0.Beta4
>
> Attachments: strangebutton.JPG
>
>
> 1. Create new JSF kickstart project.
> 2. Open web.xml, select tree tab.
> 3. Select Filter element, Press button Add to add new filter.
> 4. In menu click on Filter-Class link.
> 5. In menu press Add button (to add interface)
> In "Implemented Interface selection" look at Add button. Field with interface empty, but Add button available to clicking.
> Screenshot attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months
[JBoss JIRA] Commented: (JBIDE-761) Can not run the importing project if it located out of workspace.
by Max Andersen (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-761?page=comments#action_12372210 ]
Max Andersen commented on JBIDE-761:
------------------------------------
1) if it works with the normal wtp adapters it definitly need fixing (created jbide-762 for that)
2/3)
- is there any reason why we don't use Eclipse's standard import functionallity here ?
- and if there is a reason why not provide the default option of just creating the project in the original project folder or copy the project.
I don't see the advantage for using linked folders here it makes things much more complex, linked folders is normally only used if you as a user simply cannot adjust to the eclipse project structures (which are important to support, but should not be something we endorse)
> Can not run the importing project if it located out of workspace.
> -----------------------------------------------------------------
>
> Key: JBIDE-761
> URL: http://jira.jboss.com/jira/browse/JBIDE-761
> Project: JBoss Tools
> Issue Type: Bug
> Components: integration
> Affects Versions: 2.0.0.Beta3
> Reporter: Anton Klimkovich
>
> Create Struts 1.2 Kickstart / JSF 1.2 KickStart
> Delete it from workspace without deleting contents
> Move it from workspace to another place
> Import project into workspace from new place
> After import look at Kickstart.war in server\default\deploy. It will be empty. (Only Web-inf ->lib folders)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months
[JBoss JIRA] Moved: (JBIDE-760) Seeing two different error messages from the July 10th build
by Max Andersen (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-760?page=all ]
Max Andersen moved EXIN-391 to JBIDE-760:
-----------------------------------------
Project: JBoss Tools (was: Exadel Integration)
Key: JBIDE-760 (was: EXIN-391)
Issue Type: Bug (was: Feature Request)
Component/s: Seam
UpStream
(was: Seam)
Fix Version/s: (was: 1.0.0.beta2)
Affects Version/s: 2.0.0.Beta3
(was: 1.0.0.beta1)
> Seeing two different error messages from the July 10th build
> ------------------------------------------------------------
>
> Key: JBIDE-760
> URL: http://jira.jboss.com/jira/browse/JBIDE-760
> Project: JBoss Tools
> Issue Type: Bug
> Components: Seam, UpStream
> Affects Versions: 2.0.0.Beta3
> Environment: Fedora Core 6, JBoss AS 4.0.5 EJB 3, Seam 1.2.1
> Reporter: Jim Tyrrell
> Attachments: Screenshot-Ant Build Failed .png, Screenshot-Lazy tree error .png
>
>
> When running Seam-Gen commands I get and Ant Build error message that I will attach. This happens I think around deployment time, but I can can click on deploy and then my new application will deploy. I also am seeing a JPA environment exception also attached so I can not use the Hibernate tooling to look at Connections etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months