[
https://issues.jboss.org/browse/JBIDE-13339?page=com.atlassian.jira.plugi...
]
Fred Bricon resolved JBIDE-13339.
---------------------------------
Fix Version/s: 4.1.0.Alpha1
Resolution: Done
I couldn't reproduce, but found a path were the stacks instance could be null (even
though I'm not sure what could cause that).
Anyway I made sure a stacks instance is *always* returned
https://github.com/jbosstools/jbosstools-central/commit/aa0efbc9d811fb467...
(yeah egit f*ed up the commit by changing all line endings)
Null Java EE Web Project Archetype
----------------------------------
Key: JBIDE-13339
URL:
https://issues.jboss.org/browse/JBIDE-13339
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.0.0.Final
Environment: Windows 7 64b, Eclipse Juno Service Release 1 Build id:
20120920-0800, Java 1.7_07, JBoss Tools 4.0.0.Final
Reporter: Claudinei Jr
Assignee: Fred Bricon
Priority: Minor
Labels: maven
Fix For: 4.1.0.Alpha1
When trying to create a new Java EE Web Project, the following description is presented:
{quote}
This is your project! It's a sample, deployable Maven 3 project to help you get your
foot in the door developing with Java EE 6 on JBoss Enterprise Application Platform 6 or
JBoss Application Server 7.1.
This project is setup to allow you to create a compliant Java EE 6 application using JSF
2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0.
Project based on the *null:null:null* Maven archetype
{quote}
If I go forward with the creation of the project, I get the following error message:
{quote}
Failed to create project.
Root cause: For artifact null:null:null:pom : The group id cannot be empty.
{quote}
--
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