[JBoss Tools Users] - Web Resources folder is empty
by htfv
If I import a Maven Web-project in Eclipse 3.5.1 with JBoss Tools 3.1.0.M4 installed, I can see the "Web Resources : src/main/webapp" folder in Project Explorer, but it is always empty.
The same problem was in Eclipse 3.5.0 with JBoss Tools 3.1.0.M3. m2eclipse 0.9.9 Development release was used in both cases. If I use Eclipse 3.4.2 + JBoss Tools 3.0.1 + m2eclipse 0.9.8, I can expand the "Web Resources : src/main/webapp" folder in Project Explorer and see the files from the src/main/webapp folder.
Both Eclipse 3.5.1/JBoss Tools 3.1.0.M4 and Eclipse 3.4.2/JBoss Tools 3.0.1 generate the same .project, .classpath and .settings/* files. The only difference is that 3.1.0.M4 inserts the following line into org.eclipse.jdt.core.prefs and 3.0.1 does not:
| org.eclipse.jdt.core.compiler.problem.forbiddenReference=warning
|
The problem can be reproduced by importing a simple POM; no other files are needed:
| <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>org.htfv.test</groupId>
| <artifactId>web-resources-test</artifactId>
| <version>0.0.1-SNAPSHOT</version>
| <packaging>war</packaging>
|
| <build>
| <plugins>
| <plugin>
| <groupId>org.apache.maven.plugins</groupId>
| <artifactId>maven-compiler-plugin</artifactId>
| <configuration>
| <source>1.6</source>
| <target>1.6</target>
| </configuration>
| </plugin>
| </plugins>
| </build>
| </project>
|
Whose problem is this? Is this a problem of JBoss Tools, m2eclipse, or Eclipse? Do I do something wrong? Shall I file a bug against JBoss Tools or m2eclipse?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268395#4268395
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268395
16 years
[JBoss Cache Users] - Re: Undeterministic error:
by vnmbatista
Hi,
I have done compile time weaving configuring my pom.xml the following way:
| <plugin>
| <groupId>org.jboss.maven.plugins</groupId>
| <artifactId>maven-jbossaop-plugin</artifactId>
| <version>1.0.0.GA</version>
|
| <executions>
| <execution>
| <id>compile</id>
| <configuration>
| <!--
| if you want to include dependencies from the current module (only needed if a class
| inherits a class thats not defined in this module
| -->
| <includeProjectDependency>true</includeProjectDependency>
| <aoppaths>
| <aoppath>src/main/resources/jboss-aop.xml</aoppath>
| </aoppaths>
| <!-- You can specify to only aopc a specific set of classes -->
| <includes>
| <include>com/foo/bar/entities/*.class</include>
| </includes>
|
| </configuration>
| <goals>
| <goal>compile</goal>
| </goals>
| </execution>
| </executions>
| </plugin>
|
With jboss-aop-1.5.6.GA (which comes bundled with my JBoss) it didn't work (Missing method, ... ). I upgrades JBossAOP to version 2.1.5.GA and it starts working.
Although I had problems compiling my project:
I have POJO A and POJOs B and C, both extending A. I had the @PojoCacheable annotation on the three POJOs. Compilation crashed with
| .../src/main/java/com/foo/bar/services/imports/alert/Alerts.java:297: cannot access org.jboss.aop.Advised
| class file for org.jboss.aop.Advised not found
| productsList.add(service);
|
I tried having A with the annotation @InstanceOfPojoCacheable. It crashed also with the same error both if I had the @PojoCacheable annotation on B,C or if I had B and C without any annotation. It only worked when I removed the @PojoCacheable annotation from A. As a matter of fact I don't need to put A explicitly on the cache. If I needed I would have to refactor my code. Is the configuration which I get working normal?
On the production system I won't be able to run the AOP upgrade script. To upgrade I will need to replace the production files with the upgrades ones:
JBOSS_BIN: pluggable-instrumentator.jar;
JBOSS_LIB: javassist.jar
JBOSS_DEPLOY: jboss-aop-jdk50.deployer/
Is this correct? Am I missing any thing?
I would feel much more comfortable with Load Time Weaving, because I would have guarantees that the same binary would work on different version of JBossAOP. I finished without knowing the reason for my problem with load time weaving :(
Thank you very much for your help.
Best regards,
Victor Batista
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268374#4268374
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268374
16 years