[
https://issues.jboss.org/browse/FORGE-1898?page=com.atlassian.jira.plugin...
]
Matej Briskar commented on FORGE-1898:
--------------------------------------
The problem is only with the projects containing the java keyword separated by dashes,
because MavenMetadataFacet uses groupId to generate the package without checking for them.
There are 2 possible solutions:
1) Create our own checker, for example similar to this:
http://forum.codecall.net/topic/62656-java-identifier-checker/
2) Use some 3rd party library like
http://commons.apache.org/sandbox/commons-classscan/apidocs/org/apache/co...
Dashes in the project name makes jpa-new-entity execution to fail
-----------------------------------------------------------------
Key: FORGE-1898
URL:
https://issues.jboss.org/browse/FORGE-1898
Project: Forge
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Java EE
Affects Versions: 2.6.0.Final
Reporter: George Gastaldi
Assignee: Matej Briskar
Fix For: 2.x Future
Create a project named {{a-project-with-dashes}} and create a new JPA Entity. It should
fail with a Roaster error.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)