So I had successfully created a .desktop file to launch Eclipse from Gnome. I also found it no problem making it a favorite. The problem I was having was every time I launched Eclipse I ended up with 2 icons. The Favorite and one for the running process. The trick to making not getting this is to make sure the .desktop name matches the xwindows WM_CLASS property. You can get this value by running:
xprop WM_CLASS
Next click on the window of the Java application you are interested in. In the case of Eclipse the value is "Eclipse" so the file needs to be named Eclipse.desktop.
CSS
Showing posts with label eclipse. Show all posts
Showing posts with label eclipse. Show all posts
Wednesday, April 19, 2017
Friday, July 22, 2011
Eclipse, JBoss and Javaee6 Maven Archtype
I created a new JBoss Java EE 6 project using the jboss-javaee6-webapp archtype. I had to problems. It had a Missing artifact org.apache.xalan:xalan:jar:2.7.1-1.jbossorg:provided error which I fixed by editing the pom.xml file. Here is the change
<dependency>
<groupId>org.jboss.spec</groupId>
<artifactId>jboss-javaee-web-6.0</artifactId>
<version>2.0.0.Final</version>
<type>pom</type>
<scope>provided</scope>
<exclusions>
<exclusion>
<groupId>org.apache.xalan</groupId>
<artifactId>xalan</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>xalan</groupId>
<artifactId>xalan</artifactId>
<version>2.7.1</version>
</dependency>
By excluding the problem dependency and adding in the generic dependency for xlan it built fine.
The harder problem was to get Eclipse to properly run the application on my JBoss server. I am using Eclipse Indigo and I went back and forth with m2eclipse and the eclipse project m2e. Neither one seemed to do the trick.
In the end I used the mvn -Dwtpversion=2.0 eclipse:eclipse from the command line
<dependency>
<groupId>org.jboss.spec</groupId>
<artifactId>jboss-javaee-web-6.0</artifactId>
<version>2.0.0.Final</version>
<type>pom</type>
<scope>provided</scope>
<exclusions>
<exclusion>
<groupId>org.apache.xalan</groupId>
<artifactId>xalan</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>xalan</groupId>
<artifactId>xalan</artifactId>
<version>2.7.1</version>
</dependency>
By excluding the problem dependency and adding in the generic dependency for xlan it built fine.
The harder problem was to get Eclipse to properly run the application on my JBoss server. I am using Eclipse Indigo and I went back and forth with m2eclipse and the eclipse project m2e. Neither one seemed to do the trick.
In the end I used the mvn -Dwtpversion=2.0 eclipse:eclipse from the command line
Subscribe to:
Posts (Atom)