January 2009 - jbosstools-commits

JBoss Tools SVN: r13129 - trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template.

by jbosstools-commits＠lists.jboss.org

Author: yradtsevich Date: 2009-01-19 12:18:14 -0500 (Mon, 19 Jan 2009) New Revision: 13129 Modified: trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template/RichFacesEditorTemplate.java Log: CODING IN PROGRESS - issue JBIDE-3555: VPE templates for new components in RichFaces 3.3. https://jira.jboss.org/jira/browse/JBIDE-3555 - method isRecreateAtAttrChange has been overridden. Modified: trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template/RichFacesEditorTemplate.java =================================================================== --- trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template/RichFacesEditorTemplate.java 2009-01-19 17:16:48 UTC (rev 13128) +++ trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template/RichFacesEditorTemplate.java 2009-01-19 17:18:14 UTC (rev 13129) @@ -39,6 +39,13 @@ VpeCreationData creationData = new VpeCreationData(mainElement); return creationData; } + + @Override + public boolean isRecreateAtAttrChange(VpePageContext pageContext, + Element sourceElement, nsIDOMDocument visualDocument, + nsIDOMElement visualNode, Object data, String name, String value) { + return true; + } } /**

15 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r13128 - in workspace/max/jpaap: javax.persistence and 3 other directories.

by jbosstools-commits＠lists.jboss.org

Author: hardy.ferentschik Date: 2009-01-19 12:16:48 -0500 (Mon, 19 Jan 2009) New Revision: 13128 Removed: workspace/max/jpaap/javax.persistence/META-INF/ workspace/max/jpaap/javax.persistence/build.properties workspace/max/jpaap/jpaap/META-INF/ workspace/max/jpaap/jpaap/build.properties workspace/max/jpaap/jpaap/jpaap.jar workspace/max/jpaap/test/gen-src/ workspace/max/jpaap/test/jpa-build.xml workspace/max/jpaap/test/lib/ Modified: workspace/max/jpaap/ workspace/max/jpaap/javax.persistence/ workspace/max/jpaap/javax.persistence/build.xml workspace/max/jpaap/jpaap/ workspace/max/jpaap/jpaap/build.xml workspace/max/jpaap/jpaap/src/org/jboss/jpa/metamodel/ap/MetaEntity.java workspace/max/jpaap/test/ workspace/max/jpaap/test/build.xml workspace/max/jpaap/test/readme.txt Log: some build script cleanup Property changes on: workspace/max/jpaap ___________________________________________________________________ Name: svn:ignore + *.iml target Property changes on: workspace/max/jpaap/javax.persistence ___________________________________________________________________ Name: svn:ignore + bin target Deleted: workspace/max/jpaap/javax.persistence/build.properties =================================================================== --- workspace/max/jpaap/javax.persistence/build.properties 2009-01-19 17:13:50 UTC (rev 13127) +++ workspace/max/jpaap/javax.persistence/build.properties 2009-01-19 17:16:48 UTC (rev 13128) @@ -1,3 +0,0 @@ -source.. = src/ -bin.includes = META-INF/,\ - . Modified: workspace/max/jpaap/javax.persistence/build.xml =================================================================== --- workspace/max/jpaap/javax.persistence/build.xml 2009-01-19 17:13:50 UTC (rev 13127) +++ workspace/max/jpaap/javax.persistence/build.xml 2009-01-19 17:16:48 UTC (rev 13128) @@ -1,45 +1,42 @@ <?xml version="1.0" encoding="UTF-8" standalone="no"?> - -<project basedir="." default="build" name="javax.persistence"> - <property environment="env"/> - <property name="jpaap.location" value="../jpaap"/> - <property name="test.location" value="../test"/> - <property name="debuglevel" value="source,lines,vars"/> - <property name="target" value="1.6"/> - <property name="source" value="1.6"/> - <path id="Plug-in Dependencies.libraryclasspath"/> - <path id="javax.persistence.classpath"> - <pathelement location="classes"/> - <pathelement location="bin"/> - <path refid="Plug-in Dependencies.libraryclasspath"/> - </path> + + +<project name="Persistence API" default="jar" basedir="."> + <target name="init"> - <mkdir dir="bin"/> - <copy includeemptydirs="false" todir="bin"> - <fileset dir="src" excludes="**/*.launch, **/*.java"/> - </copy> + <property name="debuglevel" value="source,lines,vars"/> + <property name="target" value="1.6"/> + <property name="source" value="1.6"/> + <property name="src.dir" value="${basedir}/src"/> + <property name="build.dir" value="${basedir}/target"/> + <property name="classes.dir" value="${build.dir}/classes"/> + <property name="jar.name" value="jpa"/> + <tstamp/> </target> - <target name="clean"> - <delete dir="bin"/> + +  + <target name="clean" depends="init"> + <delete dir="${build.dir}"/> </target> - <target depends="clean" name="cleanall"/> - <target depends="build-subprojects,build-project" name="build"/> - <target name="build-subprojects"/> - <target depends="init" name="build-project"> + +  + <target name="compile" depends="init,clean"> + <mkdir dir="${classes.dir}"/> <echo message="${ant.project.name}: ${ant.file}"/> - <javac debug="true" debuglevel="${debuglevel}" destdir="bin" source="${source}" target="${target}"> + <javac debug="true" debuglevel="${debuglevel}" destdir="${classes.dir}" source="${source}" target="${target}"> <src path="src"/> - <classpath refid="javax.persistence.classpath"/> </javac> </target> - <target description="Build all projects which reference this project. Useful to propagate changes." name="build-refprojects"> - <ant antfile="${jpaap.location}/build.xml" inheritAll="false" target="clean"/> - <ant antfile="${jpaap.location}/build.xml" inheritAll="false" target="build"/> - <ant antfile="${test.location}/build.xml" inheritAll="false" target="clean"/> - <ant antfile="${test.location}/build.xml" inheritAll="false" target="build"/> + + +  + <target name="jar" depends="compile"> + <jar basedir="${classes.dir}" + jarfile="${build.dir}/${jar.name}.jar" + includes="**/*.*"> + <manifest> + <attribute name="Built-By" value="${user.name}"/> + </manifest> + </jar> </target> </project> Property changes on: workspace/max/jpaap/jpaap ___________________________________________________________________ Name: svn:ignore - bin + bin target Deleted: workspace/max/jpaap/jpaap/build.properties =================================================================== --- workspace/max/jpaap/jpaap/build.properties 2009-01-19 17:13:50 UTC (rev 13127) +++ workspace/max/jpaap/jpaap/build.properties 2009-01-19 17:16:48 UTC (rev 13128) @@ -1,4 +0,0 @@ -source.jpaap.jar = src/ -bin.includes = META-INF/,\ - jpaap.jar -source.jpaap.jar = src/ Modified: workspace/max/jpaap/jpaap/build.xml =================================================================== --- workspace/max/jpaap/jpaap/build.xml 2009-01-19 17:13:50 UTC (rev 13127) +++ workspace/max/jpaap/jpaap/build.xml 2009-01-19 17:16:48 UTC (rev 13128) @@ -1,53 +1,58 @@ <?xml version="1.0" encoding="UTF-8" standalone="no"?> - -<project basedir="." default="build" name="jpaap"> - <property environment="env"/> - <property name="test.location" value="../test"/> - <property name="javax.persistence.location" value="../javax.persistence"/> - <property name="debuglevel" value="source,lines,vars"/> - <property name="target" value="1.6"/> - <property name="source" value="1.6"/> - <path id="Plug-in Dependencies.libraryclasspath"/> - <path id="javax.persistence.classpath"> - <pathelement location="${javax.persistence.location}/classes"/> - <pathelement location="${javax.persistence.location}/bin"/> - <path refid="Plug-in Dependencies.libraryclasspath"/> - </path> - <path id="jpaap.classpath"> - <pathelement location="bin"/> - <path refid="Plug-in Dependencies.libraryclasspath"/> - <path refid="javax.persistence.classpath"/> - </path> + + +<project name="Persistence Annotation Processor" default="jar" basedir="."> + <target name="init"> - <mkdir dir="bin"/> - <copy includeemptydirs="false" todir="bin"> - <fileset dir="src" excludes="**/*.launch, **/*.java"/> - </copy> + <property name="debuglevel" value="source,lines,vars"/> + <property name="target" value="1.6"/> + <property name="source" value="1.6"/> + <property name="src.dir" value="${basedir}/src"/> + <property name="build.dir" value="${basedir}/target"/> + <property name="classes.dir" value="${build.dir}/classes"/> + <property name="jar.name" value="jpaap"/> + <tstamp/> + <condition property="persistence.available"> + <available classname="javax.persistence.spi.PersistenceProvider"/> + </condition> + <path id="lib.path"> + <fileset dir="${basedir}/../javax.persistence/target"> + <include name="**/*.jar"/> + </fileset> + </path> </target> - <target name="clean"> - <delete dir="bin"/> + +  + <target name="clean" depends="init"> + <delete dir="${build.dir}"/> </target> - <target depends="clean" name="cleanall"> - <ant antfile="${javax.persistence.location}/build.xml" inheritAll="false" target="clean"/> + +  + <target name="compile-dependend" unless="${persistence.available}"> + <ant dir="../javax.persistence" inheritall="false"/> </target> - <target depends="build-subprojects,build-project" name="build"/> - <target name="build-subprojects"> - <ant antfile="${javax.persistence.location}/build.xml" inheritAll="false" target="build-project"/> - </target> - <target depends="init" name="build-project"> + +  + <target name="compile" depends="init,compile-dependend"> + <mkdir dir="${classes.dir}"/> <echo message="${ant.project.name}: ${ant.file}"/> - <javac debug="true" debuglevel="${debuglevel}" destdir="bin" source="${source}" target="${target}"> - <compilerarg value="-proc:none"/> - <src path="src"/> - <classpath refid="jpaap.classpath"/> + <javac debug="true" debuglevel="${debuglevel}" destdir="${classes.dir}" source="${source}" target="${target}"> + <src path="${src.dir}"/> + <classpath refid="lib.path"/> </javac> + <copy todir="${classes.dir}/META-INF"> + <fileset dir="${src.dir}/META-INF"/> + </copy> </target> - <target description="Build all projects which reference this project. Useful to propagate changes." name="build-refprojects"> - <ant antfile="${test.location}/build.xml" inheritAll="false" target="clean"/> - <ant antfile="${test.location}/build.xml" inheritAll="false" target="build"/> + +  + <target name="jar" depends="compile"> + <jar basedir="${classes.dir}" + jarfile="${build.dir}/${jar.name}.jar" + includes="**/*.*"> + <manifest> + <attribute name="Built-By" value="${user.name}"/> + </manifest> + </jar> </target> </project> Deleted: workspace/max/jpaap/jpaap/jpaap.jar =================================================================== (Binary files differ) Modified: workspace/max/jpaap/jpaap/src/org/jboss/jpa/metamodel/ap/MetaEntity.java =================================================================== --- workspace/max/jpaap/jpaap/src/org/jboss/jpa/metamodel/ap/MetaEntity.java 2009-01-19 17:13:50 UTC (rev 13127) +++ workspace/max/jpaap/jpaap/src/org/jboss/jpa/metamodel/ap/MetaEntity.java 2009-01-19 17:16:48 UTC (rev 13128) @@ -23,202 +23,195 @@ public class MetaEntity implements ImportContext { - final TypeElement element; - final protected ProcessingEnvironment pe; + final TypeElement element; + final protected ProcessingEnvironment pe; - final ImportContext importContext; - - public MetaEntity(ProcessingEnvironment pe, TypeElement element) { - this.element = element; - this.pe = pe; - importContext = new ImportContextImpl(getPackageName().toString()); - } + final ImportContext importContext; - public Name getSimpleName() { - return element.getSimpleName(); - } + public MetaEntity(ProcessingEnvironment pe, TypeElement element) { + this.element = element; + this.pe = pe; + importContext = new ImportContextImpl(getPackageName().toString()); + } - public Element getOriginalElement() { - return element; - } + public Name getSimpleName() { + return element.getSimpleName(); + } - public Name getQualifiedName() { - return element.getQualifiedName(); - } + public Element getOriginalElement() { + return element; + } - public Name getPackageName() { - PackageElement packageOf = pe.getElementUtils().getPackageOf(element); - return pe.getElementUtils().getName(packageOf.getQualifiedName() + ".metamodel"); - } + public Name getQualifiedName() { + return element.getQualifiedName(); + } - public List<MetaMember> getMembers() { - - List<MetaMember> members = new ArrayList<MetaMember>(); - - if(useFields()) { - - List<? extends Element> myMembers = ElementFilter.fieldsIn(element.getEnclosedElements()); - - System.out.println("Scanning " + myMembers.size() + " field s for " + element.toString()); - - for (Element mymember : myMembers) { + public Name getPackageName() { + PackageElement packageOf = pe.getElementUtils().getPackageOf(element); + return pe.getElementUtils().getName(packageOf.getQualifiedName() + ".metamodel"); + } - MetaMember result = mymember.asType().accept(new TypeVisitor(this), mymember); - if(result!=null) { - members.add(result); - } else { - pe.getMessager().printMessage(Kind.WARNING, "Could not find valid info for JPA property", mymember); - } - } - - } else { + public List<MetaMember> getMembers() { - - List<? extends Element> myMembers = ElementFilter.methodsIn(element.getEnclosedElements()); + List<MetaMember> members = new ArrayList<MetaMember>(); - System.out.println("Scanning " + myMembers.size() + " methods for " + element.toString()); - for (Element mymember : myMembers) { + if (useFields()) { - MetaMember result = mymember.asType().accept(new TypeVisitor(this), mymember); - if(result!=null) { - members.add(result); - } else { - //pe.getMessager().printMessage(Kind.WARNING, "Not a valid JPA property", mymember); - } - } - - } + List<? extends Element> myMembers = ElementFilter.fieldsIn(element.getEnclosedElements()); - if(members.size()==0) { - pe.getMessager().printMessage(Kind.WARNING, "No properties found on " + element, element); - } - return members; - } + System.out.println("Scanning " + myMembers.size() + " field s for " + element.toString()); - - //TODO: Find more efficient way to identify wether we should use fields or properties - private boolean useFields() { - List<? extends Element> myMembers = element.getEnclosedElements(); - for (Element element : myMembers) { - List<? extends AnnotationMirror> entityAnnotations = - pe.getElementUtils().getAllAnnotationMirrors(element); - - for (Iterator<?> iterator = entityAnnotations.iterator(); iterator - .hasNext();) { - AnnotationMirror annotationMirror = (AnnotationMirror) iterator - .next(); - - final String annotationType = annotationMirror.getAnnotationType().toString(); + for (Element mymember : myMembers) { - if ( annotationType.equals(javax.persistence.Id.class.getName()) || - annotationType.equals(javax.persistence.EmbeddedId.class.getName())) - { - if(element.getKind()==ElementKind.FIELD) { - return true; - } - } - } - } - - return false; - } - - + MetaMember result = mymember.asType().accept(new TypeVisitor(this), mymember); + if (result != null) { + members.add(result); + } else { + pe.getMessager().printMessage(Kind.WARNING, "Could not find valid info for JPA property", mymember); + } + } - static Map<String, String> COLLECTIONS = new HashMap<String, String>(); - static { - COLLECTIONS.put("java.util.Collection", "javax.jpa.metamodel.Collection"); - COLLECTIONS.put("java.util.Set", "javax.jpa.metamodel.Set"); - COLLECTIONS.put("java.util.List", "javax.jpa.metamodel.List"); - COLLECTIONS.put("java.util.Map", "javax.jpa.metamodel.Map"); - } - - class TypeVisitor extends SimpleTypeVisitor6<MetaMember, Element> { - - MetaEntity parent; - - TypeVisitor(MetaEntity parent) { - this.parent = parent; - } - - @Override - protected MetaMember defaultAction(TypeMirror e, Element p) { - //System.out.println("Default action for: " + e + " on " + p); - //new Exception().printStackTrace(); - return super.defaultAction(e, p); - } - @Override - public MetaMember visitPrimitive(PrimitiveType t, Element p) { - return new MetaAttribute(parent, p, TypeUtils.toTypeString(t)); - } - - + } else { - @Override - public MetaMember visitDeclared(DeclaredType t, Element p) { - TypeElement e = (TypeElement) pe.getTypeUtils().asElement(t); - - String collection = COLLECTIONS.get(e.getQualifiedName().toString()); // WARNING: .toString() is necessary here since Name equals does not compare to String - if(collection!=null) { - if(collection.equals("javax.jpa.metamodel.Map")) { - return new MetaMap(parent, p, collection, getKeyType(t), getElementType(t)); - } else { - return new MetaCollection(parent, p, collection, getElementType(t)); - } - } else { - return new MetaAttribute(parent, p, e.getQualifiedName().toString()); - } - } - - - - @Override - public MetaMember visitExecutable(ExecutableType t, Element p) { - String string = p.getSimpleName().toString(); - // TODO: implement proper property get/is/boolean detection - if(string.startsWith("get") || string.startsWith("is")) { - TypeMirror returnType = t.getReturnType(); + List<? extends Element> myMembers = ElementFilter.methodsIn(element.getEnclosedElements()); - return returnType.accept(this, p); - } else { - return null; - } - } - } + System.out.println("Scanning " + myMembers.size() + " methods for " + element.toString()); + for (Element mymember : myMembers) { - @Override - public String generateImports() { - return importContext.generateImports(); - } + MetaMember result = mymember.asType().accept(new TypeVisitor(this), mymember); + if (result != null) { + members.add(result); + } else { + //pe.getMessager().printMessage(Kind.WARNING, "Not a valid JPA property", mymember); + } + } - @Override - public String importType(String fqcn) { - return importContext.importType(fqcn); - } + } - @Override - public String staticImport(String fqcn, String member) { - return importContext.staticImport(fqcn, member); - } + if (members.size() == 0) { + pe.getMessager().printMessage(Kind.WARNING, "No properties found on " + element, element); + } + return members; + } - public String importType(Name qualifiedName) { - return importType(qualifiedName.toString()); - } - private String getKeyType(DeclaredType t) { - System.out.println("key type" + t); - return t.getTypeArguments().get(0).toString(); - } + //TODO: Find more efficient way to identify wether we should use fields or properties + private boolean useFields() { + List<? extends Element> myMembers = element.getEnclosedElements(); + for (Element element : myMembers) { + List<? extends AnnotationMirror> entityAnnotations = + pe.getElementUtils().getAllAnnotationMirrors(element); - - private String getElementType(DeclaredType declaredType) { - if(declaredType.getTypeArguments().size()==1) { - return declaredType.getTypeArguments().get(0).toString(); - } else { - return declaredType.getTypeArguments().get(1).toString(); - } - } + for (Iterator<?> iterator = entityAnnotations.iterator(); iterator + .hasNext();) { + AnnotationMirror annotationMirror = (AnnotationMirror) iterator + .next(); - + final String annotationType = annotationMirror.getAnnotationType().toString(); + + if (annotationType.equals(javax.persistence.Id.class.getName()) || + annotationType.equals(javax.persistence.EmbeddedId.class.getName())) { + if (element.getKind() == ElementKind.FIELD) { + return true; + } + } + } + } + + return false; + } + + + static Map<String, String> COLLECTIONS = new HashMap<String, String>(); + + static { + COLLECTIONS.put("java.util.Collection", "javax.jpa.metamodel.Collection"); + COLLECTIONS.put("java.util.Set", "javax.jpa.metamodel.Set"); + COLLECTIONS.put("java.util.List", "javax.jpa.metamodel.List"); + COLLECTIONS.put("java.util.Map", "javax.jpa.metamodel.Map"); + } + + class TypeVisitor extends SimpleTypeVisitor6<MetaMember, Element> { + + MetaEntity parent; + + TypeVisitor(MetaEntity parent) { + this.parent = parent; + } + + @Override + protected MetaMember defaultAction(TypeMirror e, Element p) { + //System.out.println("Default action for: " + e + " on " + p); + //new Exception().printStackTrace(); + return super.defaultAction(e, p); + } + + @Override + public MetaMember visitPrimitive(PrimitiveType t, Element p) { + return new MetaAttribute(parent, p, TypeUtils.toTypeString(t)); + } + + + @Override + public MetaMember visitDeclared(DeclaredType t, Element p) { + TypeElement e = (TypeElement) pe.getTypeUtils().asElement(t); + + String collection = COLLECTIONS.get(e.getQualifiedName().toString()); // WARNING: .toString() is necessary here since Name equals does not compare to String + if (collection != null) { + if (collection.equals("javax.jpa.metamodel.Map")) { + return new MetaMap(parent, p, collection, getKeyType(t), getElementType(t)); + } else { + return new MetaCollection(parent, p, collection, getElementType(t)); + } + } else { + return new MetaAttribute(parent, p, e.getQualifiedName().toString()); + } + } + + + @Override + public MetaMember visitExecutable(ExecutableType t, Element p) { + String string = p.getSimpleName().toString(); + + // TODO: implement proper property get/is/boolean detection + if (string.startsWith("get") || string.startsWith("is")) { + TypeMirror returnType = t.getReturnType(); + + return returnType.accept(this, p); + } else { + return null; + } + } + } + + public String generateImports() { + return importContext.generateImports(); + } + + public String importType(String fqcn) { + return importContext.importType(fqcn); + } + + public String staticImport(String fqcn, String member) { + return importContext.staticImport(fqcn, member); + } + + public String importType(Name qualifiedName) { + return importType(qualifiedName.toString()); + } + + private String getKeyType(DeclaredType t) { + System.out.println("key type" + t); + return t.getTypeArguments().get(0).toString(); + } + + + private String getElementType(DeclaredType declaredType) { + if (declaredType.getTypeArguments().size() == 1) { + return declaredType.getTypeArguments().get(0).toString(); + } else { + return declaredType.getTypeArguments().get(1).toString(); + } + } } Property changes on: workspace/max/jpaap/test ___________________________________________________________________ Name: svn:ignore - build bin + build bin target Modified: workspace/max/jpaap/test/build.xml =================================================================== --- workspace/max/jpaap/test/build.xml 2009-01-19 17:13:50 UTC (rev 13127) +++ workspace/max/jpaap/test/build.xml 2009-01-19 17:16:48 UTC (rev 13128) @@ -1,73 +1,68 @@ <?xml version="1.0" encoding="UTF-8" standalone="no"?> - -<project basedir="." default="build" name="test"> - <property environment="env"/> - <property name="javax.persistence.location" value="../javax.persistence"/> - <property name="jpaap.location" value="../jpaap"/> - <property name="debuglevel" value="source,lines,vars"/> - <property name="target" value="1.6"/> - <property name="source" value="1.6"/> - <path id="Plug-in Dependencies.libraryclasspath"/> - <path id="javax.persistence.classpath"> - <pathelement location="${javax.persistence.location}/classes"/> - <pathelement location="${javax.persistence.location}/bin"/> - <path refid="Plug-in Dependencies.libraryclasspath"/> - </path> - <path id="jpaap.classpath"> - <pathelement location="${jpaap.location}/bin"/> - <path refid="Plug-in Dependencies.libraryclasspath"/> - <path refid="javax.persistence.classpath"/> - </path> - <path id="test.classpath"> - <pathelement location="bin"/> - <path refid="javax.persistence.classpath"/> - <path refid="jpaap.classpath"/> - </path> +<project name="Test JPA2 Project" default="jar" basedir="."> + <target name="init"> - <mkdir dir="bin"/> - <mkdir dir="build/classes"/> - <copy includeemptydirs="false" todir="bin"> - <fileset dir="build/classes" excludes="**/*.launch, **/*.java"/> - </copy> - <copy includeemptydirs="false" todir="bin"> - <fileset dir="src" excludes="**/*.launch, **/*.java"/> - </copy> - <copy includeemptydirs="false" todir="bin"> - <fileset dir="gen-src" excludes="**/*.launch, **/*.java"/> - </copy> + <property name="debuglevel" value="source,lines,vars"/> + <property name="target" value="1.6"/> + <property name="source" value="1.6"/> + <property name="src.dir" value="${basedir}/src"/> + <property name="build.dir" value="${basedir}/target"/> + <property name="gen.dir" value="${build.dir}/gen-src"/> + <property name="classes.dir" value="${build.dir}/classes"/> + <property name="jar.name" value="jpaap"/> + <tstamp/> + <condition property="jpaap.available"> + <available classname="org.jboss.jpa.metamodel.ap.JPAMetaModelEntityProcessor"/> + </condition> + <path id="lib.path"> + <pathelement location="${classes.dir}"/> + <fileset dir="${basedir}/../javax.persistence/target"> + <include name="**/*.jar"/> + </fileset> + <fileset dir="${basedir}/../jpaap/target"> + <include name="**/*.jar"/> + </fileset> + </path> </target> - <target name="clean"> - <delete dir="bin"/> + +  + <target name="clean" depends="init"> + <delete dir="${build.dir}"/> </target> - <target depends="clean" name="cleanall"> - <ant antfile="${javax.persistence.location}/build.xml" inheritAll="false" target="clean"/> - <ant antfile="${jpaap.location}/build.xml" inheritAll="false" target="clean"/> + + <target name="clean-all" depends="init"> + <delete dir="${build.dir}"/> + <ant dir="../javax.persistence" inheritall="false" target="clean"/> + <ant dir="../jpaap" inheritall="false" target="clean"/> </target> - <target depends="build-subprojects,build-project" name="build"/> - <target name="build-subprojects"> - <ant antfile="${javax.persistence.location}/build.xml" inheritAll="false" target="build-project"/> - <ant antfile="${jpaap.location}/build.xml" inheritAll="false" target="build-project"/> + +  + <target name="compile-dependend" unless="${jpaap.available}"> + <ant dir="../jpaap" inheritall="false"/> </target> - <target depends="init" name="build-project"> + +  + <target name="compile" depends="init,compile-dependend"> + <mkdir dir="${classes.dir}"/> + <mkdir dir="${gen.dir}"/> <echo message="${ant.project.name}: ${ant.file}"/> - <mkdir dir="build/classes" /> - - <javac debug="true" debuglevel="${debuglevel}" destdir="bin" source="${source}" target="${target}"> - <src path="build/classes"/> - <classpath refid="test.classpath"/> + <javac debug="true" debuglevel="${debuglevel}" destdir="${classes.dir}" source="${source}" target="${target}"> + <src path="${src.dir}"/> + <classpath refid="lib.path"/> </javac> - <javac debug="true" debuglevel="${debuglevel}" destdir="bin" source="${source}" target="${target}"> - <src path="src"/> - <classpath refid="test.classpath"/> - </javac> - <javac debug="true" debuglevel="${debuglevel}" destdir="bin" source="${source}" target="${target}"> - <src path="gen-src"/> - <classpath refid="test.classpath"/> - </javac> </target> - <target description="Build all projects which reference this project. Useful to propagate changes." name="build-refprojects"/> + +  + <target name="jar" depends="compile"> + <jar basedir="${classes.dir}" + jarfile="${build.dir}/${jar.name}.jar" + includes="**/*.*"> + <manifest> + <attribute name="Built-By" value="${user.name}"/> + </manifest> + </jar> + </target> </project> + + + Deleted: workspace/max/jpaap/test/jpa-build.xml =================================================================== --- workspace/max/jpaap/test/jpa-build.xml 2009-01-19 17:13:50 UTC (rev 13127) +++ workspace/max/jpaap/test/jpa-build.xml 2009-01-19 17:16:48 UTC (rev 13128) @@ -1,26 +0,0 @@ -<?xml version="1.0" encoding="UTF-8" standalone="no"?> -<project basedir="." default="build" name="jpa-test"> - <import file="build.xml"/> - - - - <target depends="init" name="build-project"> - <echo message="${ant.project.name}: ${ant.file}"/> -  - <delete dir="build/classes" /> - <mkdir dir="build/classes"/> - - - <javac debug="true" debuglevel="${debuglevel}" destdir="build/classes" source="${source}" target="${target}"> - - - <src path="src"/> - - <classpath refid="test.classpath"/> - </javac> - </target> - <target description="Build all projects which reference this project. Useful to propagate changes." name="build-refprojects"/> - - -</project> Modified: workspace/max/jpaap/test/readme.txt =================================================================== --- workspace/max/jpaap/test/readme.txt 2009-01-19 17:13:50 UTC (rev 13127) +++ workspace/max/jpaap/test/readme.txt 2009-01-19 17:16:48 UTC (rev 13128) @@ -2,9 +2,9 @@ src/ contains code that uses the Criteria API and depends on a metamodel to be generated. Without it there will be compile errors. -jpa-build.xml - Ant file that compiles via javac src/ with jpaap.jar on classpath resulting in generation of metamodel into build/classes +build.xml - Ant file that compiles via javac src/ with jpaap.jar on classpath resulting in generation of metamodel into build/classes -gen-src/ will be created if you enable APT processing in Eclipse +/target/gen-src/ will be created if you enable APT processing goal/ example of what should be generated

15 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r13126 - trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/template/expression.

by jbosstools-commits＠lists.jboss.org

Author: yradtsevich Date: 2009-01-19 12:11:26 -0500 (Mon, 19 Jan 2009) New Revision: 13126 Modified: trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/template/expression/VpeFunctionTldVersionCheck.java Log: RESOLVED - issue JBIDE-3586: java.lang.NumberFormatException then calling rich:editor. https://jira.jboss.org/jira/browse/JBIDE-3586 Modified: trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/template/expression/VpeFunctionTldVersionCheck.java =================================================================== --- trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/template/expression/VpeFunctionTldVersionCheck.java 2009-01-19 15:56:30 UTC (rev 13125) +++ trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/template/expression/VpeFunctionTldVersionCheck.java 2009-01-19 17:11:26 UTC (rev 13126) @@ -10,8 +10,6 @@ ******************************************************************************/ package org.jboss.tools.vpe.editor.template.expression; -import java.text.DecimalFormat; -import java.text.ParseException; import java.util.List; import org.eclipse.core.resources.IProject; @@ -95,7 +93,7 @@ double tldVersionNumber =0; if(tldVersion!=null) { - tldVersionNumber = Double.parseDouble(tldVersion); + tldVersionNumber = stringVersionToDouble(tldVersion); } else { //here we getting tld version for xhtml files @@ -116,7 +114,7 @@ xm); if(tldVersion!=null) { - tldVersionNumber = Double.parseDouble(tldVersion); + tldVersionNumber = stringVersionToDouble(tldVersion); } else { tldVersionNumber = 0; } @@ -135,7 +133,7 @@ try { if(tagValue.indexOf(MIN_VERSION_KEYWORD)!=-1){ - return Double.parseDouble(tagValue.substring(tagValue.indexOf(MIN_VERSION_KEYWORD)+4)); + return stringVersionToDouble(tagValue.substring(tagValue.indexOf(MIN_VERSION_KEYWORD)+4)); } else { return (-1)*Double.MAX_VALUE; @@ -151,7 +149,7 @@ try{ if(tagValue.indexOf(MAX_VERSION_KEYWORD)!=-1) { - return Double.parseDouble(tagValue.substring(tagValue.indexOf(MAX_VERSION_KEYWORD)+4)); + return stringVersionToDouble(tagValue.substring(tagValue.indexOf(MAX_VERSION_KEYWORD)+4)); }else { return Double.MAX_VALUE; } @@ -160,4 +158,38 @@ } return Double.MAX_VALUE; } + + /** + * Converts {@code sVersion} representing version of a library to + * {@code double} value. + * + * @deprecated it does not make difference between incremental versions + * like 1.2.0 and 1.2.1. This method have to be replaced by a more complicated + * version-comparator like [<a href="http://maven.apache.org/ref/current/maven-artifact/apidocs/org/apache/mav...">http://maven.apache.org/ref/current/maven-artifact/apidocs/org/apache/mav...</a>] + */ + private double stringVersionToDouble(String sVersion) { + String tokens[] = sVersion.split("\\."); + + String parseableVersion; + switch (tokens.length) { + case 0: + parseableVersion = "0"; //$NON-NLS-N$ + break; + case 1: + parseableVersion = tokens[0]; + break; + case 2: default: + parseableVersion = tokens[0] + '.' + tokens[1]; + break; + } + + double dVersion; + try { + dVersion = Double.parseDouble(parseableVersion); + } catch (Exception e) { + dVersion = 0.0; + } + + return dVersion; + } }

15 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r13125 - trunk/jst/plugins/org.jboss.tools.jst.jsp/src/org/jboss/tools/jst/jsp/outline/cssdialog.

by jbosstools-commits＠lists.jboss.org

Author: sdzmitrovich Date: 2009-01-19 10:56:30 -0500 (Mon, 19 Jan 2009) New Revision: 13125 Modified: trunk/jst/plugins/org.jboss.tools.jst.jsp/src/org/jboss/tools/jst/jsp/outline/cssdialog/CSSClassDialog.java Log: https://jira.jboss.org/jira/browse/JBIDE-3588 Modified: trunk/jst/plugins/org.jboss.tools.jst.jsp/src/org/jboss/tools/jst/jsp/outline/cssdialog/CSSClassDialog.java =================================================================== --- trunk/jst/plugins/org.jboss.tools.jst.jsp/src/org/jboss/tools/jst/jsp/outline/cssdialog/CSSClassDialog.java 2009-01-19 15:53:00 UTC (rev 13124) +++ trunk/jst/plugins/org.jboss.tools.jst.jsp/src/org/jboss/tools/jst/jsp/outline/cssdialog/CSSClassDialog.java 2009-01-19 15:56:30 UTC (rev 13125) @@ -599,9 +599,10 @@ boolean inputNewClass = classCombo.indexOf(currentClassStyle) == -1; // if new css was added - applyButton.setEnabled(inputNewClass); - classCombo.add(currentClassStyle); - + if (inputNewClass) { + applyButton.setEnabled(inputNewClass); + classCombo.add(currentClassStyle); + } styleComposite.revertPreview(); updateStyleComposite(); styleAttributes.setCssSelector(currentClassStyle);

15 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r13124 - trunk/common/plugins/org.jboss.tools.common.model/resources/help.

by jbosstools-commits＠lists.jboss.org

Author: scabanovich Date: 2009-01-19 10:53:00 -0500 (Mon, 19 Jan 2009) New Revision: 13124 Modified: trunk/common/plugins/org.jboss.tools.common.model/resources/help/keys-model-lists.properties Log: JBIDE-3581 Modified: trunk/common/plugins/org.jboss.tools.common.model/resources/help/keys-model-lists.properties =================================================================== --- trunk/common/plugins/org.jboss.tools.common.model/resources/help/keys-model-lists.properties 2009-01-19 15:39:31 UTC (rev 13123) +++ trunk/common/plugins/org.jboss.tools.common.model/resources/help/keys-model-lists.properties 2009-01-19 15:53:00 UTC (rev 13124) @@ -51,3 +51,20 @@ Model.lists.coincides=coincides Model.lists.contains=contains Model.lists.is_contained=is contained + +#Specific values of model objects used as names of tabs in preference pages +lists.Editors=Editors +lists.JSF_Flow_Diagram=JSF Flow Diagram +lists.Struts_Flow_Diagram=Struts Flow Diagram +lists.Seam_Pages_Diagram=Seam Pages Diagram +lists.Add_Page=Add Page +lists.Add_View=Add View +lists.New_Project=New Project +lists.Import_Project=Import Project +lists.Struts_Support_1.2=Struts Support 1.2 +lists.Struts_Support_1.1=Struts Support 1.1 +lists.Struts_Support_1.0=Struts Support 1.0 +lists.Default_Error_Messages=Default Error Messages +lists.Tiles=Tiles +lists.Validators=Validators +lists.Verification=Options

15 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r13123 - trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/objecteditor.

by jbosstools-commits＠lists.jboss.org

Author: scabanovich Date: 2009-01-19 10:39:31 -0500 (Mon, 19 Jan 2009) New Revision: 13123 Modified: trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/objecteditor/Messages.java trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/objecteditor/XChildrenEditor.java trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/objecteditor/messages.properties Log: Rolling-back strings which are internal model constants. Modified: trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/objecteditor/Messages.java =================================================================== --- trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/objecteditor/Messages.java 2009-01-19 15:24:27 UTC (rev 13122) +++ trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/objecteditor/Messages.java 2009-01-19 15:39:31 UTC (rev 13123) @@ -4,10 +4,6 @@ public class Messages extends NLS { private static final String BUNDLE_NAME = "org.jboss.tools.common.model.ui.objecteditor.messages"; //$NON-NLS-1$ - public static String XChildrenEditor_10; - public static String XChildrenEditor_11; - public static String XChildrenEditor_12; - public static String XChildrenEditor_9; public static String XChildrenEditor_Add; public static String XChildrenEditor_Delete; public static String XChildrenEditor_Down; Modified: trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/objecteditor/XChildrenEditor.java =================================================================== --- trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/objecteditor/XChildrenEditor.java 2009-01-19 15:24:27 UTC (rev 13122) +++ trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/objecteditor/XChildrenEditor.java 2009-01-19 15:39:31 UTC (rev 13123) @@ -247,7 +247,7 @@ } protected String getAddActionPath() { - return Messages.XChildrenEditor_9; + return "CreateActions.AddKeyPair"; //$NON-NLS-1$ } protected void updateBar() { @@ -270,9 +270,9 @@ public void callAction(XModelObject o, String path) { Properties p = new Properties(); - p.put(Messages.XChildrenEditor_10, bar.getControl().getShell()); + p.put("shell", bar.getControl().getShell()); //$NON-NLS-1$ int i = xtable.getSelectionIndex(); - p.put(Messages.XChildrenEditor_11, Integer.valueOf(i)); + p.put("insertAfter", Integer.valueOf(i)); //$NON-NLS-1$ XActionInvoker.invoke(path, o, getTargets(), p); } @@ -372,7 +372,7 @@ } public void drop(Properties p) { - XModelObject draggedObject = (XModelObject)p.get(Messages.XChildrenEditor_12); + XModelObject draggedObject = (XModelObject)p.get("draggedObject"); //$NON-NLS-1$ if(draggedObject == null) return; update(); xtable.getViewer().setSelection(new StructuredSelection(draggedObject)); Modified: trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/objecteditor/messages.properties =================================================================== --- trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/objecteditor/messages.properties 2009-01-19 15:24:27 UTC (rev 13122) +++ trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/objecteditor/messages.properties 2009-01-19 15:39:31 UTC (rev 13123) @@ -1,7 +1,3 @@ -XChildrenEditor_10=shell -XChildrenEditor_11=insertAfter -XChildrenEditor_12=draggedObject -XChildrenEditor_9=CreateActions.AddKeyPair XChildrenEditor_Add=&Add XChildrenEditor_Delete=&Delete XChildrenEditor_Down=Do&wn

15 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r13122 - trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/preferences.

by jbosstools-commits＠lists.jboss.org

Author: scabanovich Date: 2009-01-19 10:24:27 -0500 (Mon, 19 Jan 2009) New Revision: 13122 Modified: trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/preferences/XMOBasedPreferencesPage.java Log: JBIDE-3581 Modified: trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/preferences/XMOBasedPreferencesPage.java =================================================================== --- trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/preferences/XMOBasedPreferencesPage.java 2009-01-19 15:16:50 UTC (rev 13121) +++ trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/preferences/XMOBasedPreferencesPage.java 2009-01-19 15:24:27 UTC (rev 13122) @@ -21,6 +21,7 @@ import org.eclipse.ui.IWorkbenchPreferencePage; import org.jboss.tools.common.meta.action.XEntityData; +import org.jboss.tools.common.meta.key.WizardKeys; import org.jboss.tools.common.model.XModel; import org.jboss.tools.common.model.XModelObject; import org.jboss.tools.common.model.options.impl.SharableElementImpl; @@ -52,9 +53,16 @@ support = null; } - public String getTitle() { - return support.getTitle(); - } + public String getTitle() { + String value = support.getTitle(); + if(object != null) { + String s = WizardKeys.getVisualListValue(object.getModelEntity().getAttribute("name"), value); + if(s != null) { + return s; + } + } + return value; + } public void init(IWorkbench workbench) { }

15 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r13121 - trunk/jst/plugins/org.jboss.tools.jst.jsp/src/org/jboss/tools/jst/jsp/outline/cssdialog.

by jbosstools-commits＠lists.jboss.org

Author: sdzmitrovich Date: 2009-01-19 10:16:50 -0500 (Mon, 19 Jan 2009) New Revision: 13121 Modified: trunk/jst/plugins/org.jboss.tools.jst.jsp/src/org/jboss/tools/jst/jsp/outline/cssdialog/CSSClassDialog.java Log: https://jira.jboss.org/jira/browse/JBIDE-3579 Modified: trunk/jst/plugins/org.jboss.tools.jst.jsp/src/org/jboss/tools/jst/jsp/outline/cssdialog/CSSClassDialog.java =================================================================== --- trunk/jst/plugins/org.jboss.tools.jst.jsp/src/org/jboss/tools/jst/jsp/outline/cssdialog/CSSClassDialog.java 2009-01-19 14:46:55 UTC (rev 13120) +++ trunk/jst/plugins/org.jboss.tools.jst.jsp/src/org/jboss/tools/jst/jsp/outline/cssdialog/CSSClassDialog.java 2009-01-19 15:16:50 UTC (rev 13121) @@ -597,8 +597,7 @@ // update current class style value currentClassStyle = classCombo.getText().trim(); - boolean inputNewClass = Arrays.binarySearch(classCombo.getItems(), - currentClassStyle) < 0; + boolean inputNewClass = classCombo.indexOf(currentClassStyle) == -1; // if new css was added applyButton.setEnabled(inputNewClass); classCombo.add(currentClassStyle);

15 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r13120 - trunk/as/docs/reference/en/modules.

by jbosstools-commits＠lists.jboss.org

Author: ochikvina Date: 2009-01-19 09:46:55 -0500 (Mon, 19 Jan 2009) New Revision: 13120 Modified: trunk/as/docs/reference/en/modules/perspective.xml trunk/as/docs/reference/en/modules/quick_start.xml Log: https://jira.jboss.org/jira/browse/JBDS-480 - updating and reorganizing the "JBoss Server View" section; Modified: trunk/as/docs/reference/en/modules/perspective.xml =================================================================== --- trunk/as/docs/reference/en/modules/perspective.xml 2009-01-19 14:45:48 UTC (rev 13119) +++ trunk/as/docs/reference/en/modules/perspective.xml 2009-01-19 14:46:55 UTC (rev 13120) @@ -12,27 +12,26 @@ </chapterinfo> <title>JBoss AS Perspective</title> - <para>This chapter tells how to manage installed JBoss Servers via <property>JBoss AS - Perspective</property>.</para> + <para>This chapter tells how to manage installed <property>JBoss Server</property> via + <property>JBoss AS perspective</property>.</para> - <para>The <property>JBoss AS Perspective</property> is similar to the <property>Java - Perspective</property>, but it contains a few additional views. Two of the additional - views are standard views, specifically the <property>Console View</property> and the - <property>Properties View</property>. The other two views that are added are the - <property>Project Archives View</property> and the <property>JBoss Server + <para>The <property>JBoss AS perspective</property> is similar to the <property>Java + perspective</property>, but it contains a few additional views. Two of the additional + views are standard views, specifically the <property>Console view</property> and the + <property>Properties view</property>. The other two views that are added are the + <property>Project archives view</property> and the <property>JBoss Server View</property>.</para> <section id="JBossServerView" role="updated"> <?dbhtml filename="JBossServerView.html"?> <title>The JBoss Server View</title> + + <para>The <property>JBoss Server View</property> is built on Common Navigator Framework + allowing extensions and is using label decorators what makes the UI enough compact + without loosing the vital information.</para> + <para>Let's have a look at the <property>JBoss Server View</property> and inspect in detail all parts it consists of. </para> - - <para>The <property>JBoss Server View</property> is based on the WTP view, Server View. The - top part of the <property>JBoss Servers View</property> essentially embeds the original - Server View directly into it, making slight changes to the context menu. A second part - was added to provide additional information about the server selected in the top part. </para> - <figure> <title>The JBoss Server View</title> <mediaobject> @@ -42,55 +41,62 @@ </mediaobject> </figure> + <section id="jbossserver_view_toolbar"> + <title>JBoss Server View Toolbar</title> + <para>In the right top corner of the <property>JBoss Server View</property> there is a + special toolbar which provides a quick access to starting a server (in debug mode, + run mode, or profile mode), restarting a server, stopping a server, publishing to a + server and a possibility to clean a server.</para> - <para>The view's toolbar provides quick access to starting a server (in debug mode, run - mode, or profile mode), restarting a server, stopping a server, or publishing to a - server.</para> - <figure> - <title>The JBoss Server View Toolbar</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_2.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>The JBoss Server View Toolbar</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_2.png"/> + </imageobject> + </mediaobject> + </figure> - <para>In order to debug your applications or EJB's that are deployed to the server, you must - start the server in debug mode. By starting the server in debug mode, eclipse will allow - you to set breakpoints on code in your workspace and step through the code.</para> + <para>In order to debug your applications or EJB's that are deployed to the server, you + must start the server in debug mode. By starting the server in debug mode, eclipse + will allow you to set breakpoints on code in your workspace and step through the + code.</para> - <para><emphasis> - <property>Start the server in profiling mode</property> - </emphasis> button allows to enable profiling actions for your application. For more - details on how to start using TPTP profiling with <property>JBoss Tools</property> refer - to <link linkend="tptp_support">TPTP Support</link> chapter.</para> + <para><emphasis> + <property>Start the server in profiling mode</property> + </emphasis> button allows to enable profiling actions for your application. For more + details on how to start using TPTP profiling with <property>JBoss Tools</property> + refer to <link linkend="tptp_support">TPTP Support</link> chapter.</para> - <para><emphasis> - <property>Publish to the server</property> - </emphasis> button on the extreme right will republish any modules where it has - determined the workspace is out of sync with the server. It will attempt to do an - incremental publish if it turns out that the module in question is capable of doing - one.</para> + <para><emphasis> + <property>Publish to the server</property> + </emphasis> button will republish any modules where it has determined the workspace + is out of sync with the server. It will attempt to do an incremental publish if it + turns out that the module in question is capable of doing one.</para> - <para>Now, let's get to know with both of the <property>JBoss Server - View</property> parts.</para> - <section> - <title>Top Part of the JBoss Server View</title> - <para>In the top part of the <property>JBoss Server View</property> all declared servers - are represented as well as their current states, that is, whether they are started - or stopped. </para> + <para>Press <emphasis> + <property>Clean</property> + </emphasis> if you need to clean projects published on the server, i.e. remove + invalid resources from the server.</para> + </section> + + <section id="jbossserver_view_structure"> + <title>JBoss Server View Structure</title> + <para>The <property>JBoss Server View</property> displays all declared servers as well + as their current states (that is whether they are started or stopped) and statuses + in the square brackets next to a server name.</para> + <figure> - <title>Server Publish Status</title> + <title>The JBoss Server View</title> <mediaobject> <imageobject> - <imagedata fileref="images/perspective/perspective_3.png"/> + <imagedata fileref="images/perspective/perspective_1.png"/> </imageobject> </mediaobject> </figure> - <para>The top part also shows the server's publish status. The fallowing table - lists possible statuses.</para> + <para>The following table lists possible server statuses.</para> <table> <title>Server Publish Status</title> @@ -141,88 +147,10 @@ </tgroup> </table> - <para>By double-clicking on any server, an editor window will appear allowing you to - edit parts of that server. On the figure you can see that a username/password is - available in the UI when configuring the server. If you get an SecurityException - when trying to launch the server, it is most likely because your server is protected - and hence you need to fill the username/password fields with appropriate - values.</para> + <para>You can control a server behavior as well as adjust some server preferences with + the help of the context menu commands.</para> <figure> - <title>Preferences Page for the Chosen Server</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_4.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>It should be pointed out that our server adapter by default tries to automatically - detect the ports it needs for integrating with a <property>JBoss server</property>. - Sometimes it can though be relevant to override this automatic detection if you are - using some custom configuration. For this purposes the <emphasis> - <property>Server Ports</property> - </emphasis> section in the <property>Server editor</property> is provided where the - port settings are configurable. Click the <emphasis> - <property>Configure...</property> - </emphasis> link to bring up the wizard for adjusting the settings for the - Ports.</para> - - <figure> - <title>Server Ports Preferences</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_5.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>Press <emphasis> - <property>Edit XPath</property> - </emphasis> button for the chosen Port to configure its XPath's values.</para> - - <figure> - <title>XPath Pattern for a Server Port</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_6.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>The settings related to <emphasis> - <property>Publishing</property> - </emphasis>, <emphasis> - <property>Timeouts</property> - </emphasis> or <emphasis> - <property>Server Polling</property> - </emphasis> can be also adjusted in the <property>Server editor</property>.</para> - - <para id="com_line_arg"><property>Server editor</property> makes it also possible to - modify the server's launch configuration. It's just after clicking <emphasis> - <property>Open launch configuration</property> - </emphasis> link. In the open window there are the tabs for setting command line - arguments and other things that are relevant to launching the server.</para> - - <figure> - <title>Launch Configuration Properties</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_7.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>Look up <ulink - url="http://docs.jboss.org/jbossas/guides/installguide/r1/en/html/start-stop.html" - >here</ulink> to find parameters which can be specified for <property>JBoss - Server</property>.</para> - - <para>As the JBoss Servers have few properties to modify in this editor, a shortcut to - the launch configuration has been provided in the context menu when right-clicking - on a server.</para> - - <figure> <title>Twiddle Server</title> <mediaobject> <imageobject> @@ -231,7 +159,7 @@ </mediaobject> </figure> - <para>The following table describes all these additional properties.</para> + <para>All available context menu commands are described in the following table.</para> <table> <title>Server Properties through the Context Menu</title> <tgroup cols="2"> @@ -262,6 +190,26 @@ <row> <entry> + <para>Open</para> + </entry> + <entry> + <para>The option opens the Server editor</para> + </entry> + </row> + + <row> + <entry> + <para>Show in</para> + </entry> + <entry> + <para>You can monitor the currant server behavior with the help of + the other views: Console, Debug view, Server Log or MBean + Explorer</para> + </entry> + </row> + + <row> + <entry> <para>Delete</para> </entry> <entry> @@ -317,86 +265,46 @@ <row> <entry> - <para>Twiddle Server</para> + <para>Add and Remove Projects</para> </entry> <entry> - <para>The option provides a dialog for running Twiddle commands - against the Twiddle Server</para> + <para>The option allows to publish a new project to the server (if + its type is supported)</para> </entry> </row> <row> <entry> - <para>Edit Launch Configuration</para> + <para>Monitoring</para> </entry> <entry> - <para>The option that provides an editor for editing launch - configuration properties of the proper server</para> + <para>Possibility to add ports to be monitored on the currant + server</para> </entry> </row> <row> <entry> - <para>Add and Remove Projects</para> + <para>Properties</para> </entry> <entry> - <para>The option allows to publish a new project to the server (if - its type is supported)</para> + <para>Opens the window to adjust the currant server + preferences</para> </entry> </row> + </tbody> </tgroup> </table> - <para>Mentioned above Twiddle is a JMX library that comes with JBoss, and you can use it - to access any variables that exposed via the JBoss JMX interfaces.</para> - </section> + <para>Under the server element in the <property>JBoss Server View</property>, you can + see currently deployed to the server modules and some server extensions which + provide the additional information on the server.</para> - <section> - <title>Bottom Part of the JBoss Server View</title> + <para>The context menu for any module allows you to remove it from the server, force a + full or incremental republish upon it.</para> - <para>Here, we dwell on the bottom part of the <property>JBoss Server - View</property>.</para> - <para>First, we should say that the bottom part is meant to provide additional - functionality relevant to the server selected in the top part of the view. If a - standard server element is selected from above, some of the extensions may still - provide the additional information. Others may not. So, let's look at the - currently available extensions to the bottom part of the <property>JBoss Server - View</property>.</para> - <figure> - <title>View Extensions</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_9.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>In order to access the view's preferences, you should access <emphasis> - <property>Window > Preferences > JBoss Tools > JBoss - Servers > View</property> - </emphasis>. This preference page allows you to select which view extensions you - want on or off, the order they appear in the view, as well as any other - extension-specific preferences that may be available.</para> - - <figure> - <title>View Preferences</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_10.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>The first view extension is <emphasis> - <property>Modules</property> - </emphasis> section. It shows which modules are currently deployed to the server, - and allows you to remove them from the server, or force a full republish upon them. - It only shows which modules have been deployed through Eclipse, not any and all - modules that happen to be in the deploy directory.</para> - - <figure> <title>Modules Action</title> <mediaobject> <imageobject> @@ -406,53 +314,13 @@ </figure> <para>The <emphasis> - <property>Event Log</property> - </emphasis> will show relevant information to your server's startup, - shutdown, and publish processes. This allows you to keep an eye on what's - going on (such as automatic incremental deployment if you have it enabled). The only - action available is to clear the <emphasis> - <property>Event Log</property> - </emphasis>. However, if the <property>Properties View</property> is opened, you can - receive further information on each <emphasis> - <property>Event Log</property> - </emphasis> item (when available).</para> - - <figure> - <title>Event Log Actions</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_12.png"/> - </imageobject> - </mediaobject> - </figure> - - <figure> - <title>Starting the Server</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_13.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>The <emphasis> <property>XML Configuration</property> </emphasis> category allows you to quickly browse to descriptor files in your - server's deploy directory and check or change the values. Its use requires the - <property>Properties view</property>. Basically, <emphasis> + server's deploy directory and check or change the values. Basically, <emphasis> <property>XML Configuration</property> </emphasis> includes XML XPaths where a xpath is a path used to access some specific part of an xml document. </para> - <figure> - <title>XML Configuration and Properties View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_14.png"/> - </imageobject> - </mediaobject> - </figure> - <note> <title>Note:</title> <para>You are assumed to be familiar with XPath. If not, we highly suggested that @@ -464,13 +332,25 @@ </emphasis> category itself contains only a list of categories. <emphasis> <property>Ports</property> </emphasis> are provided by default and is filled with many of the most commonly - used ports in the <property>JBoss Server</property>. In the <property>Properties + used ports in the <property>JBoss Server</property>.</para> + + <figure> + <title>XML Configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_14.png"/> + </imageobject> + </mediaobject> + </figure> + + +  - <para> By right-clicking on <emphasis> + <para>By right-clicking on <emphasis> <property>XML Configuration</property>, </emphasis> you can create a new category. Besides, context menu for <emphasis> <property>XML Configuration</property> @@ -573,38 +453,206 @@ </mediaobject> </figure> - <para>As part of the <property>JBoss Server View</property> there is a <emphasis> - <property>JMX Console</property> - </emphasis> section which allows you to browse and use the JMX exposed beans on the - server.</para> + </section> + + <section id="server_log"> + <title>Server Log View</title> + + <para>You can monitor the currant server behavior with the help of the <property>Server + Log</property>. To open a server in the <property>Server Log + view</property> you should right-click on the server and follow to <emphasis> + <property>Open in > Server Log</property>.</emphasis></para> + + <para>The <emphasis> + <property>Server Log</property> + </emphasis> shows relevant information to your server's startup, + shutdown, and publish processes. This allows you to keep an eye on what's + going on (such as automatic incremental deployment if you have it enabled).</para> + <figure> - <title>JMX Console</title> + <title>Event Log Actions</title> <mediaobject> <imageobject> - <imagedata fileref="images/perspective/perspective_20.png"/> + <imagedata fileref="images/perspective/perspective_12.png"/> </imageobject> </mediaobject> </figure> - <section> - <title>Relevant Resources Links</title> - <para>Find more about XPath in the <ulink url="http://www.w3.org/TR/xpath20/">XPath - Documentation</ulink>.</para> - </section> + <para>The <property>Server Log</property> toolbar contains several icons that perform the following actions:</para> + + <table> + <title>Server Log Toolbar Icons</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> + + <thead> + <row> + <entry align="center"> + <para>Name</para> + </entry> + + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> + + <tbody> + <row> + <entry> + <para>Export Log</para> + </entry> + <entry> + <para>Possibility to export the log into a text file</para> + </entry> + </row> + + <row> + <entry> + <para>Clear Log Viewer</para> + </entry> + <entry> + <para>The option clears the currant server log</para> + </entry> + </row> + + <row> + <entry> + <para>Delete Log</para> + </entry> + <entry> + <para>Click to delete the server log</para> + </entry> + </row> + + <row> + <entry> + <para>Open Log</para> + </entry> + <entry> + <para>Click to open the server log text file</para> + </entry> + </row> + + <row> + <entry> + <para>Restore Log</para> + </entry> + <entry> + <para>Click to restore the server log</para> + </entry> + </row> + + </tbody> + </tgroup> + </table> + </section> + <section id="server_editor"> + <title>Server Editor</title> + <para>By double-clicking on any server, an editor window will appear allowing you to + edit parts of that server.</para> + + <figure> + <title>Preferences Page for the Chosen Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_4.png"/> + </imageobject> + </mediaobject> + </figure> + + <tip> + <title>Tip:</title> + <para>On the figure you can see that a username/password is available in the UI when + configuring the server. If you get an SecurityException when trying to launch + the server, it is most likely because your server is protected and hence you + need to fill the username/password fields with appropriate values.</para> + </tip> + + <para>It should be pointed out that our server adapter by default tries to automatically + detect the ports it needs for integrating with a <property>JBoss Server</property>. + Sometimes it can though be relevant to override this automatic detection if you are + using some custom configuration. For this purposes the <emphasis> + <property>Server Ports</property> + </emphasis> section in the <property>Server editor</property> is provided where the + port settings are configurable. Click the <emphasis> + <property>Configure...</property> + </emphasis> link to bring up the wizard for adjusting the settings for the + ports.</para> + + <figure> + <title>Server Ports Preferences</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_5.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>Press <emphasis> + <property>Edit XPath</property> + </emphasis> button for the chosen port to configure its XPath's values.</para> + + <figure> + <title>XPath Pattern for a Server Port</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_6.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>The settings related to <emphasis> + <property>Publishing</property> + </emphasis>, <emphasis> + <property>Timeouts</property> + </emphasis> or <emphasis> + <property>Server Polling</property> + </emphasis> can be also adjusted in the <property>Server editor</property>.</para> + + <para id="com_line_arg"><property>Server editor</property> makes it also possible to + modify the server's launch configuration. It's just after clicking <emphasis> + <property>Open launch configuration</property> + </emphasis> link. In the open window there are the tabs for setting command line + arguments and other things that are relevant to launching the server.</para> + + <figure> + <title>Launch Configuration Properties</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_7.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>Look up <ulink + url="http://docs.jboss.org/jbossas/guides/installguide/r1/en/html/start-stop.html" + >here</ulink> to find parameters which can be specified for <property>JBoss + Server</property>.</para> + </section> + + <section> + <title>Relevant Resources Links</title> + <para>Find more about XPath in the <ulink url="http://www.w3.org/TR/xpath20/">XPath + Documentation</ulink>.</para> + </section> </section> <section id="Project_archivesView" role="updated"> <title>Project Archives View</title> <para>Every application, whether Plain Old Java, J2EE, or some other language altogether, - needs to be packaged in some way. In Java-related projects, many people use ANT. </para> + needs to be packaged in some way. In Java-related projects, many people use ANT. </para> <note> <title>Note:</title> - <para>Those who use ANT will appreciate how the Project Archives Ant task is now improved: it supports variables and gives more informative error/logging messages when something goes wrong.</para> + <para>Those who use ANT will appreciate how the Project Archives Ant task is now + improved: it supports variables and gives more informative error/logging messages + when something goes wrong.</para> </note> - - <para>But <property>JBoss Tools</property> come with our own Archives tool with a bit easier + + <para>But <property>JBoss Tools</property> come with our own Archives tool with a bit easier and less-verbose XML and a handy user interface. The Project Archives plugin consists primarily of a view, that is <property>Project Archives view</property>, to set up each packaging configuration.</para> @@ -701,8 +749,8 @@ </mediaobject> </figure> - <para>The page is pretty simple. First it asks to set the name of your new archive - and a destination.</para> + <para>The page is pretty simple. First it asks to set the name of your new archive and a + destination.</para> <para>The destination of an archive can be anywhere on the file system, anywhere in the workspace, inside some other archive, or inside a folder declared inside an archive. @@ -732,7 +780,8 @@ proper chechbox in the <emphasis> <property>Archive type</property> </emphasis> section.</para> - <para>If a build or incremental update fails Project Archives will show an error dialog:</para> + <para>If a build or incremental update fails Project Archives will show an error + dialog:</para> <figure> <title>Selecting the destination in the workspace</title> <mediaobject> @@ -741,7 +790,9 @@ </imageobject> </mediaobject> </figure> - <para>Click in <emphasis><property>Details</property></emphasis> to see detailed information about what caused the error.</para> + <para>Click in <emphasis> + <property>Details</property> + </emphasis> to see detailed information about what caused the error.</para> <para>In the <property>Package Explorer</property> you can observe the created archive.</para> @@ -754,9 +805,9 @@ </mediaobject> </figure> - <para>If you use the exploded type of archiving, instead of a single file archive the result put into a - folder is displayed in the <property>Package - Explorer</property>.</para> + <para>If you use the exploded type of archiving, instead of a single file archive the + result put into a folder is displayed in the <property>Package + Explorer</property>.</para> <figure> <title>The Exploded Archive in the Package Explorer</title> <mediaobject> @@ -794,7 +845,8 @@ pattern. As you type in either of these fields, the preview viewer should update itself with which files are matched.</para> - <para>You can create a Fileset with flattenning or without it. Look at the difference on the figure below.</para> + <para>You can create a Fileset with flattenning or without it. Look at the + difference on the figure below.</para> <figure> <title>The FileSet with flattenning and without it</title> Modified: trunk/as/docs/reference/en/modules/quick_start.xml =================================================================== --- trunk/as/docs/reference/en/modules/quick_start.xml 2009-01-19 14:45:48 UTC (rev 13119) +++ trunk/as/docs/reference/en/modules/quick_start.xml 2009-01-19 14:46:55 UTC (rev 13120) @@ -2,21 +2,32 @@ <chapter id="quick_start"> <title>Quick Start with JBoss Server</title> - <para>This chapter covers the basics of working with the JBoss server. If you already have - installed JBoss server and runtime you can quickly learn how to configure, start, stop the - server, to know deployment and archiving processes. How to install runtimes and servers read in - the <link linkend="runtimes_servers">Runtimes and Servers in the JBoss AS plugin</link> chapter.</para> + <para>This chapter covers the basics of working with the <property>JBoss Server</property>. If you + already have installed JBoss server and runtime you can quickly learn how to configure, start, + stop the server, to know deployment and archiving processes. How to install runtimes and servers + read in the <link linkend="runtimes_servers">Runtimes and Servers in the JBoss AS plugin</link> + chapter.</para> <para>To start working with JBoss AS, select a <property>JBoss AS Perspective</property> via - <emphasis><property>Window > Open Perspective > Other > JBoss AS</property>.</emphasis></para> + <emphasis><property>Window > Open Perspective > Other > JBoss + AS</property>.</emphasis></para> <section id="starting"> - <title>Starting JBoss server</title> + <title>Starting JBoss Server</title> - <para>Starting JBoss server is quite simple. You can control the server behaviour with the help - of a special toolbar in the <property>JBoss Server View</property> where you could - <property>start</property> it in a regular or debug mode, <property>stop</property> it or - <property>restart</property> it, <property>publish</property> to the server.</para> + <para>Starting <property>JBoss Server</property> is quite simple. You can control the server + behaviour with the help of a special toolbar in the <property>JBoss Server View</property> + where you could <emphasis> + <property>start</property> + </emphasis> it in a regular or debug mode, <emphasis> + <property>stop</property> + </emphasis> it or <emphasis> + <property>restart</property> + </emphasis> it, <emphasis> + <property>publish</property> + </emphasis> to the server, <emphasis> + <property>clean</property> + </emphasis> the server.</para> <figure> <title>JBoss Server Toolbar</title> @@ -29,9 +40,9 @@ <para>To launch the server click the green-with-white-arrow icon on the <property>JBoss Server View </property>or right click server name in this view and select <emphasis> - <property>Start</property> - </emphasis>. If this view is not open, select <emphasis><property>Window > Show View - > Other > Server > JBoss Server View</property>.</emphasis></para> + <property>Start</property>. </emphasis> If this view is not open, select + <emphasis><property>Window > Show View > Other > Server > + JBoss Server View</property>.</emphasis></para> <figure> <title>Start JBoss Server</title> @@ -47,8 +58,10 @@ <section id="stopping"> <title>Stopping JBoss Server</title> - <para>To stop the server, click the <property>Stop</property> icon in JBoss Server View or right - click the server name and press <property>Stop</property>.</para> + <para>To stop the server, click the <emphasis> + <property>Stop</property> + </emphasis> icon in the <property>JBoss Server View</property> or right click the server name + and press <emphasis><property>Stop</property>.</emphasis></para> <figure> <title>Stop JBoss Server</title> @@ -59,21 +72,23 @@ </mediaobject> </figure> - <para>When the server is stopped you will see <property>Stopped</property> next to its name in - the State column.</para> - <para>Learn more about the JBoss Server View <link linkend="JBossServerView">here</link>.</para> + <para>When the server is stopped you will see <emphasis> + <property>Stopped</property> + </emphasis> state next to its name in the square brackets.</para> + <para>Learn more about the <property>JBoss Server View</property> + <link linkend="JBossServerView">here</link>.</para> </section> <section id="archiving"> <title>Project Archiving</title> - <para>JBoss Tools comes with our own archives tool. The Project Archives plugin consists - primarily of a view to set up each packaging configuration (<emphasis> - <property>Window > Show View > Other > JBoss Tools > Project archives</property> - </emphasis>).</para> - <para>Right clicking in the <property>Project Archives View</property> you can create War, EJB - War or EAR archive.</para> + <para><property>JBoss Tools</property> comes with our own archives tool. The Project Archives + plugin consists primarily of a view to set up each packaging configuration <emphasis>( + <property>Window > Show View > Other > JBoss Tools > Project archives</property>). + </emphasis></para> + <para>Right clicking in the <property>Project archives view</property> you can create War, + EJB War, EAR or JAR archive.</para> <figure> <title>Archive Creating</title> @@ -84,9 +99,9 @@ </mediaobject> </figure> - <para>Using the context menu on the item you can initiate a full <property>build</property> on - archive, <property>edit</property>, <property>delete</property> or - <property>publish</property> it.</para> + <para>Using the context menu on the item you can initiate a <emphasis><property>full build</property></emphasis> on + archive, <emphasis><property>edit</property>,</emphasis> <emphasis><property>delete</property></emphasis> or + <emphasis><property>publish</property></emphasis> it.</para> <figure> <title>Context Menu on the Item</title> @@ -130,7 +145,7 @@ </imageobject> </mediaobject> </figure> - + <figure> <title>Runtime and Server Sections in the Import Project Wizard</title> <mediaobject> @@ -141,8 +156,8 @@ </figure> <para>You can deploy an existing application to a server by right-clicking the target defined - server in the <property>JBoss Servers View</property> and then selecting <property>Add and - Remove Projects</property> from the context menu.</para> + server in the <property>JBoss Servers View</property> and then selecting <emphasis><property>Add and + Remove Projects</property></emphasis> from the context menu.</para> <figure> <title>Add and Remove Projects From the Context Menu.</title> @@ -167,16 +182,19 @@ </figure> <para>Here, we have just performed the basic steps you should know to quick start with JBoss - server. In fact, there are more functionalities which you can make use of. Further we will talk about them in detail.</para> + server. In fact, there are more functionalities which you can make use of. Further we will + talk about them in detail.</para> </section> - - + + <section> <title>Other relevant resources on the topic</title> - - <para>All JBoss Developer Studio/JBoss Tools documentation you can find <ulink url="http://docs.jboss.org/tools/2.1.0.GA">here</ulink>.</para> - <para>The latest documentation builds are available <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">here</ulink>.</para> - + + <para>All JBoss Developer Studio/JBoss Tools documentation you can find <ulink + url="http://docs.jboss.org/tools/2.1.0.GA">here</ulink>.</para> + <para>The latest documentation builds are available <ulink + url="http://download.jboss.org/jbosstools/nightly-docs/">here</ulink>.</para> + </section> - + </chapter>

15 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r13119 - trunk/as/docs/reference/en/images/tptp_support.

by jbosstools-commits＠lists.jboss.org

Author: ochikvina Date: 2009-01-19 09:45:48 -0500 (Mon, 19 Jan 2009) New Revision: 13119 Modified: trunk/as/docs/reference/en/images/tptp_support/tptp_support_1.png Log: https://jira.jboss.org/jira/browse/JBDS-480 - updating the screens; Modified: trunk/as/docs/reference/en/images/tptp_support/tptp_support_1.png =================================================================== (Binary files differ)

15 years, 12 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbosstools-commits January 2009