[JBoss JIRA] Resolved: (JBIDE-764) Workspace refreshing problems after manual removing projects .
by Alexey Kazakov (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-764?page=all ]
Alexey Kazakov resolved JBIDE-764.
----------------------------------
Resolution: Rejected
> 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, 7 months
[JBoss JIRA] Closed: (JBIDE-60) Xdoclet Subtasks order
by Max Andersen (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-60?page=all ]
Max Andersen closed JBIDE-60.
-----------------------------
Resolution: Out of Date
report if still relevant/an issue in a current version of jboss tools
> Xdoclet Subtasks order
> ----------------------
>
> Key: JBIDE-60
> URL: http://jira.jboss.com/jira/browse/JBIDE-60
> Project: JBoss Tools
> Issue Type: Bug
> Reporter: SourceForge User
> Priority: Critical
>
> SourceForge Submitter: furykid .
> using the "XDoclet configuration"
> ist is NOT possible to change the sequence of subtasks.
> ( they are all ordered alphabetically !?).
> In some scenarios it is vital(!) to have a manually
> definable sequence of subtasks.
> for example in the "ejbdoclet" task the "session"
> subtask has to be run before the "deploymentdescriptor"
> ( in case of an abstract implementation) otherwise the
> deploymentdescriptor is generated incorrectly.
--
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, 7 months
[JBoss JIRA] Closed: (JBIDE-116) Conflict between JBoss-IDE plugin and Rational ClearCase SCM
by Max Andersen (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-116?page=all ]
Max Andersen closed JBIDE-116.
------------------------------
Resolution: Out of Date
If this is still an issue against a more current version of jboss tools - let us know (we can't reproduce the issue here )
> Conflict between JBoss-IDE plugin and Rational ClearCase SCM
> ------------------------------------------------------------
>
> Key: JBIDE-116
> URL: http://jira.jboss.com/jira/browse/JBIDE-116
> Project: JBoss Tools
> Issue Type: Bug
> Reporter: SourceForge User
>
> SourceForge Submitter: ericeberry .
> I have been getting this exception when trying to Run
> XDoclet with JBoss-IDE 1.4.0 and Eclipse 3.0.1.
> !ENTRY org.eclipse.core.runtime 4 2 Nov 08, 2004
> 09:07:29.742
> !MESSAGE An internal error occurred during: "XDoclet
> Generation".
> !STACK 0
> java.lang.IllegalArgumentException: Attempted to
> beginRule: R/, does not match outer scope rule:
> P/bnc1.5
> at org.eclipse.core.internal.runtime.Assert.isLegal
> (Assert.java:58)
> at org.eclipse.core.internal.jobs.ThreadJob.illegalPush
> (ThreadJob.java:106)
> at org.eclipse.core.internal.jobs.ThreadJob.push
> (ThreadJob.java:200)
> at org.eclipse.core.internal.jobs.ImplicitJobs.begin
> (ImplicitJobs.java:80)
> at org.eclipse.core.internal.jobs.JobManager.beginRule
> (JobManager.java:170)
> at
> org.eclipse.core.internal.resources.WorkManager.checkIn
> (WorkManager.java:95)
> at
> org.eclipse.core.internal.resources.Workspace.prepareOp
> eration(Workspace.java:1628)
> at
> org.eclipse.core.internal.resources.Resource.refreshLocal
> (Resource.java:1224)
> at
> org.jboss.ide.eclipse.xdoclet.run.ui.actions.XDocletRunAct
> ion$1.run(XDocletRunAction.java:191)
> at org.eclipse.core.internal.jobs.Worker.run
> (Worker.java:66)
> It turns out there is a conflict between the JBoss-IDE
> plugin and the Rational ClearCase SCM Adapter 6.0.24
> plugin. Becuase this plugin is "always on", we can't turn
> the plugin off. We have to disable the plugin to turn it
> off. I disabled the plugin and I was able to run xdoclet
> every time. As soon as I re-enabled the plugin. Run
> XDoclet stopped working.
--
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, 7 months
[JBoss JIRA] Commented: (JBIDE-779) JSF 1.2 with Facelets KickStart error
by Alexey Kazakov (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-779?page=comments#action_12372241 ]
Alexey Kazakov commented on JBIDE-779:
--------------------------------------
Even through we could disabled some wst validators then we will lose some benefits.
For example html/jsp validators do a lot of good work.
> JSF 1.2 with Facelets KickStart error
> -------------------------------------
>
> Key: JBIDE-779
> URL: http://jira.jboss.com/jira/browse/JBIDE-779
> 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
> Fix For: 2.0.0.Beta4
>
> Attachments: WarningsScreen.JPG
>
>
> 1. Web projects View -> New JSF Project
> 2. Enter as JSF Environment JSF 1.2 with Facelets, as template - FaceletsKickStart, Press Finish
> 3. Open inputname.jsp
> 5 warnings appear at lines:
> 17(jsfc="h:form"), 19(jsfc="h:inputText"), 19(required="true"), 20(jsfc="h:commandButton"), 21(action="greeting").
> So KickStart project can't be runned at server.
--
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, 7 months