[zzzz8]

I’m attempting to run XDoclet on a project that is using CM Synergy 6.3 (Build 3285) for version control, Eclipse 3.1 M4 (200412162000), and MyEclipse 3.8.4BetaFor3.1. I was previously able to generate the web.xml file on a simple project that was not connected to a versioning control system (albeit with the schema error as listed in my previous message).

I right click on my project, click MyEclipse, then “Run XDoclet.” When I do so, I get the following dialog box:

An internal error occurred during: “XDoclet Generation.”

The error log shows:

!ENTRY org.eclipse.core.runtime 4 2 2005-02-28 14:56:24.355
!MESSAGE An internal error occurred during: “XDoclet Generation”.
!STACK 0
java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: P/TestProject
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:183)
at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:95)
at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:1629)
at org.eclipse.core.internal.resources.File.create(File.java:106)
at org.eclipse.core.internal.resources.File.create(File.java:182)
at org.jboss.ide.eclipse.xdoclet.run.util.ProjectUtil.transformBuildFile(Unknown Source)
at org.jboss.ide.eclipse.xdoclet.run.ui.XDocletRunAction$2.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)

What’s going on here? Any ideas?

[Riyad Kalla]

java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: P/TestProject

Is your project actually named TestProject or did you rename it? Are you letting MyEclipse dynamically generate the xdoclet build file or did you set it to generate the file and dump it in your project root? (Do you see a xdoclet-build.xml file?)

[zzzz8]

The project is actually named TestProject (actually, I changed it for the forum post, but I did not rename it during the XDoclet generation). I’m letting MyEclipse dynamically generate the XDoclet build file so it’s not dumping an xdoclet-build.xml file (it’s creating something like a .xdoclet-build.xml.tmp file that gets deleted after each time I run “Run XDoclet.”

[Greg]

If you refresh the project manually, “hit F5 on project root”, do you see the new xdoclet generated files?

[zzzz8]

No – the web.xml is never generated… Oops, actually, the .xdoclet-build.xml.tmp file is never generated. Sorry about that misinformation. So nothing is generated… I’ve tried this on another project (a simple one) and it does work – however, this project does not use the CM Synergy plugin.

[Riyad Kalla]

Can you turn that plugin on in the simple project and see if it breaks all the sudden?

[garysargent]

Hi,

I too am having this problem.

As soon as I select the “Share Project” option under “Team” for a project, and select “Perforce” (our Source Control system), then the MyDoclet generation stops working with the error in the original post above.

If I delete the project from the workspace and re-add it, XDoclet works fine. But then when I share the project again it stops working.

I’m using the latest 3.1 M6 versions for Eclipse and MyEclipseIDE.

Any ideas what is going on?

Thanks,

Gary.

[Riyad Kalla]

Gary,
We aren’t farmiliar with Perforce or know what the plugin does… is it necessary to be using 3.1 while it is still in beta? I wonder if using 3.0.2 and MyEclipse 3.8.4 GA would give you a more stable experience. You could try doing a parallel install into a temp folder of those releases and seeing if ti was any better.

[garysargent]

It doesn’t sound like it is a bug specific to Perforce though as this is now the second source control system this issue has been reported with.

Seems to be a general problem when you are sharing a project for source control management.

I’ve just tried installing Eclipse 3.0.2 and MyEclipse 3.8.4 GA and I got exactly the same issue. Stack trace from this installation setup is:

java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: P/ATT-EJB
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.prepareOperation(Workspace.java:1628)
at org.eclipse.core.internal.resources.File.create(File.java:106)
at org.eclipse.core.internal.resources.File.create(File.java:182)
at org.jboss.ide.eclipse.xdoclet.run.util.ProjectUtil.transformBuildFile(Unknown Source)
at org.jboss.ide.eclipse.xdoclet.run.ui.XDocletRunAction$2.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)

Bit of an issue for us so if anything can be done to fix this it would be much appreciated!

I notice other issues with source control – for example if I go into project properties and try to change the location of the hibernate config file, then it does not work if the .myhibernatedata file is read-only. It doesn’t try to check out the file from source control like it does when I just say edit a java file.

Thanks,

Gary.

[Riyad Kalla]

It doesn’t sound like it is a bug specific to Perforce though as this is now the second source control system this issue has been reported with.

What is the other system? Clearcase?

Seems to be a general problem when you are sharing a project for source control management.

Hmm haven’t seen it with CVS or SVN yet, but it could have something to do with the nature of VSS-like SCM software.

at org.jboss.ide.eclipse.xdoclet.run.util.ProjectUtil.transformBuildFile(Unknown Source)
at org.jboss.ide.eclipse.xdoclet.run.ui.XDocletRunAction$2.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)

Do you have JBossIDE installed (<eclipse dir>\plugins\org.jboss.* plugin directories?)

[garysargent]

The other product mentioned by the original author of this thread is Synergy/CM: http://www.telelogic.com/products/synergy/cmsynergy/index.cfm

No I don’t have any org.jboss.* files in the plugin folder – should I?!

[garysargent]

I’m using WebSphere 6 app server by the way.

[garysargent]

The stack trace in my Eclipse 3.1 setup does not say Unknown Source….

java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: P/ATT-EJB
at org.eclipse.core.internal.runtime.Assert.isLegal(Assert.java:58)
at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:107)
at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:201)
at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:81)
at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:186)
at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:96)
at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:1669)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1709)
at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:771)
at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:2739)
at org.eclipse.jdt.core.JavaCore$3.run(JavaCore.java:3852)
at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:34)
at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:710)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1714)
at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:3665)
at org.eclipse.jdt.core.JavaCore.setClasspathContainer(JavaCore.java:3835)
at org.eclipse.jdt.internal.launching.JREContainerInitializer.initialize(JREContainerInitializer.java:54)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:1281)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:1246)
at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:853)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:1313)
at org.jboss.ide.eclipse.xdoclet.run.util.ProjectUtil.populateClassPath(ProjectUtil.java:156)
at org.jboss.ide.eclipse.xdoclet.run.util.ProjectUtil.populateClassPath(ProjectUtil.java:99)
at org.jboss.ide.eclipse.xdoclet.run.util.ProjectUtil.getClassPathAsXml(ProjectUtil.java:67)
at org.jboss.ide.eclipse.xdoclet.run.util.ProjectUtil.transformBuildFile(ProjectUtil.java:401)
at org.jboss.ide.eclipse.xdoclet.run.ui.XDocletRunAction$2.run(XDocletRunAction.java:319)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:67)

[garysargent]

And here is a slightly different stack trace I’ve got:

!SESSION 2005-04-22 17:20:24.165 ———————————————–
eclipse.buildId=I20050401-1645
java.version=1.4.2_07
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
Command-line arguments: -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.core.runtime 4 2 2005-04-22 17:20:24.165
!MESSAGE An internal error occurred during: “XDoclet Generation”.
!STACK 0
java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: P/ATT-EJB
at org.eclipse.core.internal.runtime.Assert.isLegal(Assert.java:58)
at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:107)
at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:201)
at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:81)
at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:186)
at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:96)
at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:1669)
at org.eclipse.core.internal.resources.File.create(File.java:107)
at org.eclipse.core.internal.resources.File.create(File.java:183)
at org.jboss.ide.eclipse.xdoclet.run.util.ProjectUtil.transformBuildFile(ProjectUtil.java:411)
at org.jboss.ide.eclipse.xdoclet.run.ui.XDocletRunAction$2.run(XDocletRunAction.java:319)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:67)

[Riyad Kalla]

I have filed this issue for investigation, MyEclipse integrates parts of JBossIDE for XDoclet processing, and in the process we inheritied this bug.

I found some information on this, aparently JBossIDE suffers from it:
http://www.eclipse-plugins.info/eclipse/plugin_comments.jsp?id=255
and
http://www.mail-archive.com/jboss-development@lists.sourceforge.net/msg63556.html
and the bug report to JBoss forums here:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=56437

Here are the JIRA bug entries for this in JBossIDE:
http://jira.jboss.com/jira/browse/JBIDE-116
and
http://jira.jboss.com/jira/browse/JBIDE-96

We will track this and see if we can get a fix in, but if you read the thread of 116 it suggests a workaround of ClearCase Lite and I believe one of the developers comments that the problem is with the internal Eclipse API, we will see if this is the case.

[Author]

Posts