[JBoss JIRA] (FORGE-659) MovePlugin fails while moving java classes
by George Gastaldi (JIRA)
George Gastaldi created FORGE-659:
-------------------------------------
Summary: MovePlugin fails while moving java classes
Key: FORGE-659
URL: https://issues.jboss.org/browse/FORGE-659
Project: Forge
Issue Type: Bug
Components: Builtin Plugins
Reporter: George Gastaldi
Fix For: 2.0.0.Alpha1
Having a class in a package, when you try to move that class to another package, the following error is thrown:
{code:java}
[exemplo] model $ ls
Cidade.java UnidadeFederativa.java
[exemplo] model $ mv Cidade.java ex01/Cidade.java
***ERROR*** [mv] no such child: null
{code}
Probably we should give a better description, or say that this feature isn't supported yet.
Moving a class to another package includes refactoring the whole project, in order to avoid compilation errors.
--
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
13 years, 5 months
[JBoss JIRA] (FORGE-601) XML Parser should support inclusion of elements beginning with '<!' (e.g. DTDs)
by Ryan Bradley (JIRA)
Ryan Bradley created FORGE-601:
----------------------------------
Summary: XML Parser should support inclusion of elements beginning with '<!' (e.g. DTDs)
Key: FORGE-601
URL: https://issues.jboss.org/browse/FORGE-601
Project: Forge
Issue Type: Enhancement
Components: Parsers / File Manipulation
Affects Versions: 1.0.5.Final
Environment: Fedora 15 (64-bit), Java 1.7
Reporter: Ryan Bradley
Fix For: Future
In my plugin, I use Apache Tiles, which require a reference to a DTD in their layouts/views XML declaration files. I am trying to create these files from a template, and then add more view/layout definitions later in the plugin's workflow.
However, depending on how the DTD reference (in the format <!....>) is added, it is either omitted from the generated file or causes an exception when the XML Parser tries to parse the file for the root node.
--
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
13 years, 5 months
[JBoss JIRA] (FORGE-699) create a plugin for WildcardImportResolver
by fiorenzo pizza (JIRA)
fiorenzo pizza created FORGE-699:
------------------------------------
Summary: create a plugin for WildcardImportResolver
Key: FORGE-699
URL: https://issues.jboss.org/browse/FORGE-699
Project: Forge
Issue Type: Story
Components: Parsers / File Manipulation
Affects Versions: 1.1.1.Final
Reporter: fiorenzo pizza
Assignee: fiorenzo pizza
Fix For: 1.1.2.Final
general notes
We need to create some WildcardImportResolver (Responsible for providing additional import resolution functionality for situations where classes have referenced a package or wild-card import)
summary:
- when start creation of index --> new-project
- when update the index --> re-open project | add|remove plugins to the project | add|remove maven dependencies | add|remove new class inside forge project
- where save the index --> always
- how information to save for future search --> className, jarName (null if the class is in the project), packageName, absoluteClassName
- how search inside the index --> (ram hashmap? ram db?)
- how generate new entry for the index --> cdi event
general considerations
1) when forge create a new-project we should create some structure to add all classes used referenced by project
2) we need to add all classes required from some plugin (persistence|scaffolding..)
2) we need to add all classes inside maven dependencies
3) we need to add all classes created in the project
4) we need remove all deleted classes
5) we need to remove all classes inside dependecies removed
6) we need to update the index files, when forge project is reopen (the user could modify the project out of forge)
problems
1) with a lot of jars, the indexing process should be slow!!
2) how synchronize the access to index
3) how we should synchronize of index update?
requirements
1) we need some fast library to extract classes from jar files
2) we should use cdi event to start a single jar indexing
HOW CREATE INDEX FROM JAR:
possibile libraries: jandex, tattletale, jarindexer
FIRST CANDIDATE: JANDEX
i started to hack jandex code, because jandex is very fast.
Jandex opens the jar files using java jar utilities: JarFile jar = new JarFile(jarFile);
and for every class generate a ClassInfo object: ClassInfo info = indexer.index(jar.getInputStream(entry));
For my test, i removed some methods inside jandex: we don't care about annotations inside classes. Also i removed the generation of file index.
questions:
1) why don't use H2, the Java SQL database, for memorize all informations about classes?
How memorize for a single class:
1) classname, jar name (with version), package name, complete name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (FORGE-693) Need an auto-update feature for plugins
by George Gastaldi (JIRA)
George Gastaldi created FORGE-693:
-------------------------------------
Summary: Need an auto-update feature for plugins
Key: FORGE-693
URL: https://issues.jboss.org/browse/FORGE-693
Project: Forge
Issue Type: Feature Request
Reporter: George Gastaldi
FORGE-217 auto-updates the core and the core plugins. There should be a way to update the current installed plugins.
Depending on the time taken to check, this could be done in the Forge startup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months