[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class
by fede pia (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ]
fede pia commented on JBIDE-18128:
----------------------------------
[~maxandersen] I installed the nightly builds and the issue still persists. I can send you a join.me link to show you my desktop. The same project doesn't start on Eclipse Luna whilst it does on Eclipse Kepler. I can't provide my project because of company policies but I can tell you that is a backend project using Jersey 1.8, Java 6, Jboss 7.1, Spring 3.1:
<properties>
<java-version>1.6</java-version>
<org.springframework-version>3.1.1.RELEASE</org.springframework-version>
<org.aspectj-version>1.7.3</org.aspectj-version>
<org.slf4j-version>1.6.6</org.slf4j-version>
<querydsl.version>2.7.2</querydsl.version>
<derby.version>10.10.1.1</derby.version>
</properties>
As a note the class that is always missing is my only aspect. So, as a sample you could try using an aspect weaved using AspectJ maven plugin. I use this configuration:
<!-- AspectJ configuration -->
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>aspectj-maven-plugin</artifactId>
<!-- Version 1.5 is for Java 6, Version 1.6 is for Java 7, Version 1.7 is for Java 8 -->
<version>1.5</version>
<configuration>
<complianceLevel>${java-version}</complianceLevel>
<source>${java-version}</source>
<target>${java-version}</target>
</configuration>
<executions>
<execution>
<goals>
<goal>compile</goal>
<goal>test-compile</goal>
</goals>
</execution>
</executions>
</plugin>
Anything you need just let me know
> Jboss Eclipse Luna plugin doesn't deploy all .class
> ---------------------------------------------------
>
> Key: JBIDE-18128
> URL: https://issues.jboss.org/browse/JBIDE-18128
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Reporter: fede pia
> Assignee: Rob Stryker
> Priority: Blocker
>
> The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException.
> I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random.
> For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean
> As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1.
> I also tried building the war outside Eclipse and deployed manually to JBoss and everything works fine.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18152) For JBIDE 4.2.0.CR1: Code Freeze + Branch [VPE]
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18152?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov closed JBIDE-18152.
------------------------------------------
Resolution: Done
> For JBIDE 4.2.0.CR1: Code Freeze + Branch [VPE]
> -----------------------------------------------
>
> Key: JBIDE-18152
> URL: https://issues.jboss.org/browse/JBIDE-18152
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: visual-page-editor-core
> Reporter: Mickael Istria
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [VPE]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
> [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
> {code}
> git fetch origin master
> git checkout FETCH_HEAD
> git checkout -b jbosstools-4.2.x
> git push origin jbosstools-4.2.x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18161) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Forge]
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18161?page=com.atlassian.jira.plugi... ]
Koen Aers closed JBIDE-18161.
-----------------------------
Resolution: Done
> For JBIDE 4.2.0.CR1: Code Freeze + Branch [Forge]
> -------------------------------------------------
>
> Key: JBIDE-18161
> URL: https://issues.jboss.org/browse/JBIDE-18161
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: forge
> Reporter: Mickael Istria
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [Forge]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
> [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
> {code}
> git fetch origin master
> git checkout FETCH_HEAD
> git checkout -b jbosstools-4.2.x
> git push origin jbosstools-4.2.x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18156) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Hibernate]
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18156?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-18156:
------------------------------
Assignee: Koen Aers
> For JBIDE 4.2.0.CR1: Code Freeze + Branch [Hibernate]
> -----------------------------------------------------
>
> Key: JBIDE-18156
> URL: https://issues.jboss.org/browse/JBIDE-18156
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: hibernate
> Reporter: Mickael Istria
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [Hibernate]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
> [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
> {code}
> git fetch origin master
> git checkout FETCH_HEAD
> git checkout -b jbosstools-4.2.x
> git push origin jbosstools-4.2.x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months