[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [iam-dev] Re: Error on updating dependencis
|
After your feedback I installed the team plugin and checked out the
project using check out maven project... worked like a charm :-)
On Wed, Apr 7, 2010 at 10:35 AM, Richard Hauswald
<richard.hauswald@xxxxxxxxxxxxxx> wrote:
> Yes. We don't share project/eclipse settings over svn because of
> path/naming problems of jdk and tomcat runtimes etc. So if I check out
> a project its just a project without any relation to java. verified
> this doing:
> 1. new Project...
> 2. General -> Project -> Next
> 3. Name: admintool.fe -> Finish
> 4. manually copied src folder and pom into the project
> 5. right click -> maven2 -> Use maven dependency management
>
> I guess it's the same as checking out a project without any
> settings/classpath/project settings.
>
> Keep up the good work!
> Richard
>
> On Wed, Apr 7, 2010 at 10:27 AM, Abel Muiño Vizcaino <amuino@xxxxxxxxx> wrote:
>> One additional clarification: you were enabling maven support on a "simple
>> project"? (that is, a non-java project)
>>
>> El 07/04/2010, a las 10:25, Carlos Sanchez escribió:
>>
>>> we'll fix it, it's just that we expected people to import the projects
>>> directly from IAM and we didnt consider this use case.
>>>
>>> On Tue, Apr 6, 2010 at 10:24 PM, Richard Hauswald
>>> <richard.hauswald@xxxxxxxxxxxxxx> wrote:
>>>>
>>>> That did the trick :-) Thanks for your support! Anyway: Is this a bug
>>>> going to be fixed or the way the plugin is intended to be used?
>>>>
>>>> On Wed, Apr 7, 2010 at 10:18 AM, Carlos Sanchez <carlos@xxxxxxxxxx>
>>>> wrote:
>>>>>
>>>>> I think the issue is enabling Maven in the project that is already in
>>>>> the workspace. Try deleting the project from eclipse and eclipse
>>>>> specific file/folders (.settings,.classpath,.project) from the file
>>>>> system, and then importing using "Import - Maven project"
>>>>>
>>>>> Or alternatively, check out from svn outside of eclipse and then
>>>>> import with "Import - Maven project"
>>>>>
>>>>> I believe the issue is enabling IAM on projects that are already in
>>>>> the workspace imported using other methods than the IAM importer
>>>>>
>>>>> On Tue, Apr 6, 2010 at 10:14 PM, Richard Hauswald
>>>>> <richard.hauswald@xxxxxxxxxxxxxx> wrote:
>>>>>>
>>>>>> Ok, I can reproduce the error... Here are your details:
>>>>>> 1. Downloaded eclipse-jee-galileo-SR2-win32.zip
>>>>>> 2. extracted to a folder
>>>>>> 3. Since I'm running a 64Bit Windows 7 added the -vm pathTo32BitJdk
>>>>>> parameter to the shortcut
>>>>>> 4. starting the first time, choosing fresh workspace
>>>>>> 5. installing subversive -> restarting
>>>>>> 6. installing svnkit 1.3.0 -> restarting
>>>>>> 7. adding svn repo and check out project without any eclipse specific
>>>>>> file/folders (.settings,.classpath,.project)
>>>>>> 8. verified that eclipse does not know anything about this project, no
>>>>>> dependencies, no source folders, no red bubbles, etc
>>>>>> 9. right click the project, use maven dependency management
>>>>>> 10 successfully received error message and .log file entry
>>>>>> 11. Removed and Readded maven dependency management, same error
>>>>>>
>>>>>> Let me know if you need something to trace this problem.
>>>>>>
>>>>>> Here is my log:
>>>>>> !SESSION 2010-04-07 10:01:03.651
>>>>>> -----------------------------------------------
>>>>>> eclipse.buildId=unknown
>>>>>> java.version=1.6.0_16
>>>>>> java.vendor=Sun Microsystems Inc.
>>>>>> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
>>>>>> Framework arguments: -product org.eclipse.epp.package.jee.product
>>>>>> -product org.eclipse.epp.package.jee.product
>>>>>> Command-line arguments: -os win32 -ws win32 -arch x86 -product
>>>>>> org.eclipse.epp.package.jee.product -data
>>>>>> C:\Users\Richard.Hauswald\workspaces\mavendwh -product
>>>>>> org.eclipse.epp.package.jee.product
>>>>>>
>>>>>> !ENTRY org.eclipse.equinox.registry 2 0 2010-04-07 10:01:06.031
>>>>>> !MESSAGE The extensions and extension-points from the bundle
>>>>>> "org.aspectj.runtime" are ignored. The bundle is not marked as
>>>>>> singleton.
>>>>>>
>>>>>> !ENTRY org.eclipse.core.jobs 4 2 2010-04-07 10:04:14.031
>>>>>> !MESSAGE An internal error occurred during: "Updating classpath
>>>>>> container: admintool.fe".
>>>>>> !STACK 0
>>>>>> java.lang.NullPointerException
>>>>>> at
>>>>>> org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.removeLink(VirtualResource.java:300)
>>>>>> at
>>>>>> org.eclipse.iam.wtp.core.internal.war.MavenWarClasspathListener.addOverlayWarFolders(MavenWarClasspathListener.java:89)
>>>>>> at
>>>>>> org.eclipse.iam.wtp.core.internal.war.MavenWarClasspathListener.resolved(MavenWarClasspathListener.java:57)
>>>>>> at
>>>>>> org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.resolveArtifacts(MavenClasspathContainer.java:272)
>>>>>> at
>>>>>> org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.refreshClasspath(MavenClasspathContainer.java:141)
>>>>>> at
>>>>>> org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.newClasspath(MavenClasspathContainer.java:181)
>>>>>> at
>>>>>> org.eclipse.iam.jdt.core.classpath.container.UpdateClasspathJob.runInWorkspace(UpdateClasspathJob.java:80)
>>>>>> at
>>>>>> org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
>>>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>>>>>
>>>>>> !ENTRY org.eclipse.core.jobs 4 2 2010-04-07 10:04:15.524
>>>>>> !MESSAGE An internal error occurred during: "Updating classpath
>>>>>> container: admintool.fe".
>>>>>> !STACK 0
>>>>>> java.lang.NullPointerException
>>>>>> at
>>>>>> org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.removeLink(VirtualResource.java:300)
>>>>>> at
>>>>>> org.eclipse.iam.wtp.core.internal.war.MavenWarClasspathListener.addOverlayWarFolders(MavenWarClasspathListener.java:89)
>>>>>> at
>>>>>> org.eclipse.iam.wtp.core.internal.war.MavenWarClasspathListener.resolved(MavenWarClasspathListener.java:57)
>>>>>> at
>>>>>> org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.resolveArtifacts(MavenClasspathContainer.java:272)
>>>>>> at
>>>>>> org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.refreshClasspath(MavenClasspathContainer.java:141)
>>>>>> at
>>>>>> org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.newClasspath(MavenClasspathContainer.java:181)
>>>>>> at
>>>>>> org.eclipse.iam.jdt.core.classpath.container.UpdateClasspathJob.runInWorkspace(UpdateClasspathJob.java:80)
>>>>>> at
>>>>>> org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
>>>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>>>>>
>>>>>> !ENTRY org.eclipse.iam.search.core 4 0 2010-04-07 10:04:52.503
>>>>>> !MESSAGE Cannot init search providers: Plug-in org.eclipse.iam.ui was
>>>>>> unable to load class
>>>>>> org.eclipse.iam.ui.core.BuiltinArtifactSearchProvider.
>>>>>>
>>>>>> !ENTRY org.eclipse.core.jobs 4 2 2010-04-07 10:05:02.626
>>>>>> !MESSAGE An internal error occurred during: "Updating classpath
>>>>>> container: admintool.fe".
>>>>>> !STACK 0
>>>>>> java.lang.NullPointerException
>>>>>> at
>>>>>> org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.removeLink(VirtualResource.java:300)
>>>>>> at
>>>>>> org.eclipse.iam.wtp.core.internal.war.MavenWarClasspathListener.addOverlayWarFolders(MavenWarClasspathListener.java:89)
>>>>>> at
>>>>>> org.eclipse.iam.wtp.core.internal.war.MavenWarClasspathListener.resolved(MavenWarClasspathListener.java:57)
>>>>>> at
>>>>>> org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.resolveArtifacts(MavenClasspathContainer.java:272)
>>>>>> at
>>>>>> org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.refreshClasspath(MavenClasspathContainer.java:141)
>>>>>> at
>>>>>> org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.newClasspath(MavenClasspathContainer.java:181)
>>>>>> at
>>>>>> org.eclipse.iam.jdt.core.classpath.container.UpdateClasspathJob.runInWorkspace(UpdateClasspathJob.java:80)
>>>>>> at
>>>>>> org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
>>>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>>>>>
>>>>>> !ENTRY org.eclipse.core.jobs 4 2 2010-04-07 10:05:03.580
>>>>>> !MESSAGE An internal error occurred during: "Updating classpath
>>>>>> container: admintool.fe".
>>>>>> !STACK 0
>>>>>> java.lang.NullPointerException
>>>>>> at
>>>>>> org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.removeLink(VirtualResource.java:300)
>>>>>> at
>>>>>> org.eclipse.iam.wtp.core.internal.war.MavenWarClasspathListener.addOverlayWarFolders(MavenWarClasspathListener.java:89)
>>>>>> at
>>>>>> org.eclipse.iam.wtp.core.internal.war.MavenWarClasspathListener.resolved(MavenWarClasspathListener.java:57)
>>>>>> at
>>>>>> org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.resolveArtifacts(MavenClasspathContainer.java:272)
>>>>>> at
>>>>>> org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.refreshClasspath(MavenClasspathContainer.java:141)
>>>>>> at
>>>>>> org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.newClasspath(MavenClasspathContainer.java:181)
>>>>>> at
>>>>>> org.eclipse.iam.jdt.core.classpath.container.UpdateClasspathJob.runInWorkspace(UpdateClasspathJob.java:80)
>>>>>> at
>>>>>> org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
>>>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Apr 7, 2010 at 9:58 AM, Richard Hauswald
>>>>>> <richard.hauswald@xxxxxxxxxxxxxx> wrote:
>>>>>>>
>>>>>>> Damnit, forgot the pom:
>>>>>>> <project xmlns="http://maven.apache.org/POM/4.0.0";
>>>>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>>>>>> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>>>>>>> http://maven.apache.org/maven-v4_0_0.xsd";>
>>>>>>> <modelVersion>4.0.0</modelVersion>
>>>>>>> <groupId>de.dser</groupId>
>>>>>>> <artifactId>admintool.fe</artifactId>
>>>>>>> <packaging>war</packaging>
>>>>>>> <version>1.0-SNAPSHOT</version>
>>>>>>> <name>admintool.fe Maven Webapp</name>
>>>>>>> <url>http://maven.apache.org</url>
>>>>>>> <dependencies>
>>>>>>> <dependency>
>>>>>>> <groupId>junit</groupId>
>>>>>>> <artifactId>junit</artifactId>
>>>>>>> <version>4.8.1</version>
>>>>>>> <scope>test</scope>
>>>>>>> </dependency>
>>>>>>> <!-- Logging -->
>>>>>>> <dependency>
>>>>>>> <groupId>org.slf4j</groupId>
>>>>>>> <artifactId>slf4j-api</artifactId>
>>>>>>> <version>1.5.11</version>
>>>>>>> <scope>provided</scope>
>>>>>>> </dependency>
>>>>>>> <!-- Stripes -->
>>>>>>> <dependency>
>>>>>>> <groupId>net.sourceforge.stripes</groupId>
>>>>>>> <artifactId>stripes</artifactId>
>>>>>>> <version>1.5</version>
>>>>>>> <scope>runtime</scope>
>>>>>>> <exclusions>
>>>>>>> <exclusion>
>>>>>>>
>>>>>>> <artifactId>commons-logging</artifactId>
>>>>>>>
>>>>>>> <groupId>commons-logging</groupId>
>>>>>>> </exclusion>
>>>>>>> </exclusions>
>>>>>>> </dependency>
>>>>>>> <dependency>
>>>>>>> <groupId>org.slf4j</groupId>
>>>>>>> <artifactId>jcl-over-slf4j</artifactId>
>>>>>>> <version>1.5.11</version>
>>>>>>> <scope>provided</scope>
>>>>>>> </dependency>
>>>>>>> <!-- Web Libs -->
>>>>>>> <dependency>
>>>>>>> <groupId>javax.servlet</groupId>
>>>>>>> <artifactId>servlet-api</artifactId>
>>>>>>> <version>2.4</version>
>>>>>>> <scope>provided</scope>
>>>>>>> </dependency>
>>>>>>> <dependency>
>>>>>>> <groupId>servlets.com</groupId>
>>>>>>> <artifactId>cos</artifactId>
>>>>>>> <version>05Nov2002</version>
>>>>>>> <scope>provided</scope>
>>>>>>> </dependency>
>>>>>>> <!-- Guice -->
>>>>>>> <dependency>
>>>>>>>
>>>>>>> <groupId>com.silvermindsoftware.stripes</groupId>
>>>>>>> <artifactId>stripes-guice</artifactId>
>>>>>>> <version>1.5.0</version>
>>>>>>> <scope>compile</scope>
>>>>>>> </dependency>
>>>>>>> <dependency>
>>>>>>> <groupId>com.google.inject</groupId>
>>>>>>> <artifactId>guice</artifactId>
>>>>>>> <version>2.0</version>
>>>>>>> <scope>runtime</scope>
>>>>>>> </dependency>
>>>>>>> <dependency>
>>>>>>> <groupId>com.google.inject.extensions</groupId>
>>>>>>> <artifactId>guice-servlet</artifactId>
>>>>>>> <version>2.0</version>
>>>>>>> <scope>compile</scope>
>>>>>>> </dependency>
>>>>>>> <dependency>
>>>>>>> <groupId>javax.servlet</groupId>
>>>>>>> <artifactId>jstl</artifactId>
>>>>>>> <version>1.1.2</version>
>>>>>>> <scope>runtime</scope>
>>>>>>> </dependency>
>>>>>>> <dependency>
>>>>>>> <groupId>taglibs</groupId>
>>>>>>> <artifactId>standard</artifactId>
>>>>>>> <version>1.1.2</version>
>>>>>>> <scope>runtime</scope>
>>>>>>> </dependency>
>>>>>>> <dependency>
>>>>>>> <groupId>javax.servlet.jsp</groupId>
>>>>>>> <artifactId>jsp-api</artifactId>
>>>>>>> <version>2.1</version>
>>>>>>> <scope>provided</scope>
>>>>>>> </dependency>
>>>>>>> </dependencies>
>>>>>>> <!-- stripes-guice repository -->
>>>>>>> <repositories>
>>>>>>> <repository>
>>>>>>> <id>silvermindsoftware.repo</id>
>>>>>>> <name>Silvermind Software Release Repo</name>
>>>>>>>
>>>>>>> <url>http://m2.silvermindsoftware.com/repo/</url>
>>>>>>> <releases>
>>>>>>> <enabled>true</enabled>
>>>>>>> <checksumPolicy>fail</checksumPolicy>
>>>>>>> <updatePolicy>never</updatePolicy>
>>>>>>> </releases>
>>>>>>> <snapshots>
>>>>>>> <enabled>false</enabled>
>>>>>>> </snapshots>
>>>>>>> </repository>
>>>>>>> <repository>
>>>>>>> <id>silvermindsoftware.snapshot</id>
>>>>>>> <name>Silvermind Software Snapshot Repo</name>
>>>>>>>
>>>>>>> <url>http://m2.silvermindsoftware.com/snapshot/</url>
>>>>>>> <releases>
>>>>>>> <enabled>false</enabled>
>>>>>>> <checksumPolicy>fail</checksumPolicy>
>>>>>>> </releases>
>>>>>>> <snapshots>
>>>>>>> <enabled>true</enabled>
>>>>>>> </snapshots>
>>>>>>> </repository>
>>>>>>>
>>>>>>> </repositories>
>>>>>>> <build>
>>>>>>> <finalName>admintool.fe</finalName>
>>>>>>> <plugins>
>>>>>>> <plugin>
>>>>>>>
>>>>>>> <groupId>org.apache.maven.plugins</groupId>
>>>>>>>
>>>>>>> <artifactId>maven-compiler-plugin</artifactId>
>>>>>>> <version>2.0.2</version>
>>>>>>> <configuration>
>>>>>>> <source>1.6</source>
>>>>>>> <target>1.6</target>
>>>>>>> </configuration>
>>>>>>> </plugin>
>>>>>>> </plugins>
>>>>>>> </build>
>>>>>>> </project>
>>>>>>>
>>>>>>> On Wed, Apr 7, 2010 at 9:58 AM, Richard Hauswald
>>>>>>> <richard.hauswald@xxxxxxxxxxxxxx> wrote:
>>>>>>>>
>>>>>>>> On Wed, Apr 7, 2010 at 9:42 AM, Abel Muiño Vizcaino
>>>>>>>> <amuino@xxxxxxxxx> wrote:
>>>>>>>>>
>>>>>>>>> Yes, it is something in WTP support (I suppose the admintool.fe
>>>>>>>>> project is a
>>>>>>>>> web project?).
>>>>>>>>
>>>>>>>> Sorry for not mentioning it. Yes it is a web project.
>>>>>>>>
>>>>>>>>> The exception is raised from the component supporting the war
>>>>>>>>> overlay... are
>>>>>>>>> you using that maven feature?
>>>>>>>>
>>>>>>>> To be honest: I don't know what a war overlay feature is. I'm using
>>>>>>>> only default settings in eclipse so I guess you will find the answer
>>>>>>>> to your question in the projects pom. I put its contents at the end
>>>>>>>> of
>>>>>>>> this mail.
>>>>>>>>
>>>>>>>>> From your email, I am not sure if this started happening "without
>>>>>>>>> reason" or
>>>>>>>>> if you did some changes to the project pom (or reimported the
>>>>>>>>> project or any
>>>>>>>>> other action). Do you have any idea of what could have changed to
>>>>>>>>> start
>>>>>>>>> reporting this error?
>>>>>>>>
>>>>>>>> Not really since its a fresh eclipse and workspace. But I have to
>>>>>>>> admit that I've done horrible things to this eclipse: Opened a
>>>>>>>> workspace of another eclipse installation accidentally -> switched to
>>>>>>>> new one -> checked out the project of the svn, noticed project
>>>>>>>> settings has been committed too, deleted them and then added maven
>>>>>>>> support. I'm currently setting up everything again. If the error can
>>>>>>>> be reproduced I can provide you with detailed information.
>>>>>>>>
>>>>>>>>
>>>>>>>>> El 07/04/2010, a las 9:37, Richard Hauswald escribió:
>>>>>>>>>
>>>>>>>>>> Update:
>>>>>>>>>> I uninstalled the Eclipse IAM Web tools support and now the
>>>>>>>>>> dependencies are being resolved without errors. So I guess the
>>>>>>>>>> error
>>>>>>>>>> is located in the wtp support plugin.
>>>>>>>>>>
>>>>>>>>>> On Wed, Apr 7, 2010 at 9:33 AM, Richard Hauswald
>>>>>>>>>> <richard.hauswald@xxxxxxxxxxxxxx> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hello list,
>>>>>>>>>>> please excuse my silence in the last post - I didn't get the
>>>>>>>>>>> chance to
>>>>>>>>>>> try the hints. I'll respond as soon as I tried it. Today in ran
>>>>>>>>>>> into
>>>>>>>>>>> another error. When refreshing my dependencies i get the following
>>>>>>>>>>> error in my .log file:
>>>>>>>>>>> !SESSION 2010-04-07 09:28:12.433
>>>>>>>>>>> -----------------------------------------------
>>>>>>>>>>> eclipse.buildId=unknown
>>>>>>>>>>> java.version=1.6.0_16
>>>>>>>>>>> java.vendor=Sun Microsystems Inc.
>>>>>>>>>>> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
>>>>>>>>>>> Framework arguments: -product org.eclipse.epp.package.jee.product
>>>>>>>>>>> Command-line arguments: -os win32 -ws win32 -arch x86 -product
>>>>>>>>>>> org.eclipse.epp.package.jee.product
>>>>>>>>>>>
>>>>>>>>>>> !ENTRY org.eclipse.equinox.registry 2 0 2010-04-07 09:28:14.833
>>>>>>>>>>> !MESSAGE The extensions and extension-points from the bundle
>>>>>>>>>>> "org.aspectj.runtime" are ignored. The bundle is not marked as
>>>>>>>>>>> singleton.
>>>>>>>>>>>
>>>>>>>>>>> !ENTRY org.eclipse.core.jobs 4 2 2010-04-07 09:29:01.849
>>>>>>>>>>> !MESSAGE An internal error occurred during: "Updating classpath
>>>>>>>>>>> container: admintool.fe".
>>>>>>>>>>> !STACK 0
>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>>> org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.removeLink(VirtualResource.java:300)
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>>> org.eclipse.iam.wtp.core.internal.war.MavenWarClasspathListener.addOverlayWarFolders(MavenWarClasspathListener.java:89)
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>>> org.eclipse.iam.wtp.core.internal.war.MavenWarClasspathListener.resolved(MavenWarClasspathListener.java:57)
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>>> org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.resolveArtifacts(MavenClasspathContainer.java:272)
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>>> org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.refreshClasspath(MavenClasspathContainer.java:141)
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>>> org.eclipse.iam.jdt.core.classpath.container.MavenClasspathContainer.newClasspath(MavenClasspathContainer.java:181)
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>>> org.eclipse.iam.jdt.core.classpath.container.UpdateClasspathJob.runInWorkspace(UpdateClasspathJob.java:80)
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>>> org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
>>>>>>>>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>>>>>>>>>>
>>>>>>>>>>> Any hints on this?
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>> Richard
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Richard Hauswald
>>>>>>>>>>> Blog: http://tnfstacc.blogspot.com/
>>>>>>>>>>> LinkedIn: http://www.linkedin.com/in/richardhauswald
>>>>>>>>>>> Xing: http://www.xing.com/profile/Richard_Hauswald
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Richard Hauswald
>>>>>>>>>> Blog: http://tnfstacc.blogspot.com/
>>>>>>>>>> LinkedIn: http://www.linkedin.com/in/richardhauswald
>>>>>>>>>> Xing: http://www.xing.com/profile/Richard_Hauswald
>>>>>>>>>> _______________________________________________
>>>>>>>>>> iam-dev mailing list
>>>>>>>>>> iam-dev@xxxxxxxxxxx
>>>>>>>>>> https://dev.eclipse.org/mailman/listinfo/iam-dev
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Abel Muiño - http://ramblingabout.wordpress.com/
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> iam-dev mailing list
>>>>>>>>> iam-dev@xxxxxxxxxxx
>>>>>>>>> https://dev.eclipse.org/mailman/listinfo/iam-dev
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Richard Hauswald
>>>>>>>> Blog: http://tnfstacc.blogspot.com/
>>>>>>>> LinkedIn: http://www.linkedin.com/in/richardhauswald
>>>>>>>> Xing: http://www.xing.com/profile/Richard_Hauswald
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Richard Hauswald
>>>>>>> Blog: http://tnfstacc.blogspot.com/
>>>>>>> LinkedIn: http://www.linkedin.com/in/richardhauswald
>>>>>>> Xing: http://www.xing.com/profile/Richard_Hauswald
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Richard Hauswald
>>>>>> Blog: http://tnfstacc.blogspot.com/
>>>>>> LinkedIn: http://www.linkedin.com/in/richardhauswald
>>>>>> Xing: http://www.xing.com/profile/Richard_Hauswald
>>>>>> _______________________________________________
>>>>>> iam-dev mailing list
>>>>>> iam-dev@xxxxxxxxxxx
>>>>>> https://dev.eclipse.org/mailman/listinfo/iam-dev
>>>>>>
>>>>> _______________________________________________
>>>>> iam-dev mailing list
>>>>> iam-dev@xxxxxxxxxxx
>>>>> https://dev.eclipse.org/mailman/listinfo/iam-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Richard Hauswald
>>>> Blog: http://tnfstacc.blogspot.com/
>>>> LinkedIn: http://www.linkedin.com/in/richardhauswald
>>>> Xing: http://www.xing.com/profile/Richard_Hauswald
>>>> _______________________________________________
>>>> iam-dev mailing list
>>>> iam-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/iam-dev
>>>>
>>> _______________________________________________
>>> iam-dev mailing list
>>> iam-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/iam-dev
>>
>> --
>> Abel Muiño - http://ramblingabout.wordpress.com/
>>
>> _______________________________________________
>> iam-dev mailing list
>> iam-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/iam-dev
>>
>
>
>
> --
> Richard Hauswald
> Blog: http://tnfstacc.blogspot.com/
> LinkedIn: http://www.linkedin.com/in/richardhauswald
> Xing: http://www.xing.com/profile/Richard_Hauswald
>
--
Richard Hauswald
Blog: http://tnfstacc.blogspot.com/
LinkedIn: http://www.linkedin.com/in/richardhauswald
Xing: http://www.xing.com/profile/Richard_Hauswald
