[JBoss JIRA] (JBIDE-10173) VPE source navigation: open css file for my custom tag implementation does not work (Ctrl + left mouse button)
by Vitali Yemialyanchyk (Created) (JIRA)
VPE source navigation: open css file for my custom tag implementation does not work (Ctrl + left mouse button)
--------------------------------------------------------------------------------------------------------------
Key: JBIDE-10173
URL: https://issues.jboss.org/browse/JBIDE-10173
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jsp/jsf/xml source editing
Affects Versions: 3.3.0.M4
Reporter: Vitali Yemialyanchyk
Assignee: Alexey Kazakov
Priority: Minor
1) extract 2 demo projects from projects.zip in some folder on you PC intended for such things;
a) stopka-ui-base - this project contains implementation of several tags which I use in other project stopka-ui-test. stopka-ui-base contains maven build script so you can easy assemble stopka-ui-base-1.0.1.jar to use it in stopka-ui-test;
b) stopka-ui-test - is a jsp demo project, which is use stopka-ui-base as a custom templates library;
c) stopka-ui-test\src\main\webapp\WEB-INF\lib\stopka-taglib-0.9.jar - tld description of custom tag for testing;
2) stopka-ui-base - to assemble stopka-ui-base-1.0.1.jar with maven - use:
{code}
mvn clean install
{code}
3) stopka-ui-test\src\main\webapp\WEB-INF\lib contains stopka-taglib-0.9.jar and stopka-ui-base-1.0.1.jar
for test purposes you should install these jars into you maven repository - stopka-ui-test\install-ui.sh this script contains necessary instructions:
run
{code}
mvn install:install-file -Dfile=stopka-taglib-0.9.jar -DgroupId=stopka.us -DartifactId=ui-components -Dversion=0.9 -Dpackaging=jar
mvn install:install-file -Dfile=stopka-ui-base-1.0.1.jar -DgroupId=stopka.us -DartifactId=stopka-ui-base -Dversion=1.0.1 -Dpackaging=jar
{code}
from stopka-ui-test\src\main\webapp\WEB-INF\lib as a current directory
4) run Eclipse with JBossTools;
5) import stopka-ui-test\pom.xml as a maven project;
6) open stopka-ui-test\src\main\webapp\test.jspx page with VPE:
{code}
<stopka:page xmlns="http://www.w3.org/1999/xhtml"
xmlns:stopka="http://stopka.us"
xmlns:jsp="http://java.sun.com/JSP/Page"
xmlns:c="http://java.sun.com/jsp/jstl/core"
xmlns:utils="http://stopka.us/ui/utils">
<jsp:output xmlns:jsp="http://java.sun.com/JSP/Page" omit-xml-declaration="yes"/>
<c:set var="bannerType" scope="page" value="simple"/>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-us">
<head>
<title>StopKa filemanager</title>
<stopka:css file="system/styles/stopka.css" />
<utils:common-head-data/>
<stopka:css file="system/styles/filemanager.css" />
</head>
<body>
<div class="component">
<div class="subitem">
</div>
</div>
<div class="article"/>
<div class="in_stopka">
</div>
<div class="in_filemanager">
</div>
</body>
</html>
</stopka:page>
{code}
7) try to open css files
{code}
<stopka:css file="system/styles/stopka.css" />
{code}
and
{code}
<stopka:css file="system/styles/filemanager.css" />
{code}
with Ctrl + left mouse button click it does not work;
I expect VPE context assist could open css files in any case, i.e. if I make an error:
{code}
<stopka:dss file="system/styles/filemanager.css" />
{code}
VPE context assist should work and should open filemanager.css.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (JBIDE-10070) Creating OpenShift Express App via JBossTools - "Plugin execution not covered by lifecycle configuration"
by Len DiMaggio (Created) (JIRA)
Creating OpenShift Express App via JBossTools - "Plugin execution not covered by lifecycle configuration"
---------------------------------------------------------------------------------------------------------
Key: JBIDE-10070
URL: https://issues.jboss.org/browse/JBIDE-10070
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.M4
Environment: RHEL6
Firefox 3.6.23
Version: Indigo Release
Build id: 20110615-0604
JBoss Tools 3.3.0.M4
java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.10) (rhel-1.40.1.9.10.el6_1-x86_64)
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
Reporter: Len DiMaggio
Assignee: Andre Dietisheim
Fix For: 3.3.0.Beta1
The app is created, but this error is reported in Eclipse:
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (execution: default-compile, phase: compile)
Line 6 - what's the issue here with the war packaging?
------
<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>testApp3</groupId>
<artifactId>testApp3</artifactId>
<packaging>war</packaging>
<version>1.0</version>
<name>testApp3</name>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
<!--<dependencies>
<dependency>
<groupId>org.jboss.spec</groupId>
<artifactId>jboss-javaee-6.0</artifactId>
<version>1.0.0.Final</version>
<type>pom</type>
<scope>provided</scope>
</dependency>
</dependencies>-->
<profiles>
<profile>
<!-- When built in OpenShift the 'openshift' profile will be used when invoking mvn. -->
<!-- Use this profile for any OpenShift specific customization your app will need. -->
<!-- By default that is to put the resulting archive into the 'deployments' folder. -->
<!-- http://maven.apache.org/guides/mini/guide-building-for-different-environm... -->
<id>openshift</id>
<build>
<finalName>testApp3</finalName>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<version>2.1.1</version>
<configuration>
<outputDirectory>deployments</outputDirectory>
<warName>ROOT</warName>
</configuration>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months