[JBoss JIRA] (JBIDE-13602) Backport to 4.0.x - Null Java EE Web Project Archetype
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13602?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-13602:
-----------------------------------------
This has been noted as a bug by a user trying to recreate TicketMonster:
http://www.jboss.org/jdf/examples/ticket-monster/tutorial/Introduction/#c...
"When I make: new "Java EE Web Project", I see at the end of description: "Project based on the null:null:null Maven archetype", so when I create the project I get the error: "Project based on the null:null:null Maven archetype"
How can I fix this?
Thanks a lot!"
So it needs a release note.
> Backport to 4.0.x - Null Java EE Web Project Archetype
> ------------------------------------------------------
>
> Key: JBIDE-13602
> URL: https://issues.jboss.org/browse/JBIDE-13602
> 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: Fred Bricon
> Assignee: Denis Golovin
> Priority: Minor
> Labels: maven
> Fix For: 4.0.1.Final
>
>
> 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
13 years, 1 month
[JBoss JIRA] (JBDS-2470) Confusing error message when defining JPP 6.0.0.CR01.1 runtime
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2470?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2470:
--------------------------------
Attachment: jppserver-runtime-dialog.png
> Confusing error message when defining JPP 6.0.0.CR01.1 runtime
> --------------------------------------------------------------
>
> Key: JBDS-2470
> URL: https://issues.jboss.org/browse/JBDS-2470
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: runtime
> Affects Versions: 6.0.0.GA
> Environment: jboss-jpp-6.0.0.CR01.1.zip
> jbdevstudio-product-universal-6.0.0.GA-v20121206-1855-B186.jar
> Reporter: Len DiMaggio
> Assignee: Max Rydahl Andersen
> Fix For: 6.0.1.GA, 7.0.0.Alpha2
>
> Attachments: jppserver-runtime-dialog.png, Screenshot-1.png
>
>
> See attached screenshot - the error displayed to the user when creating a new JPP 6.0.0 runtime is:
> This server type expects a version of 6. but the server directory is of version 7.1.3.Final-redhat-4.
--
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, 1 month
[JBoss JIRA] (JBDS-2470) Confusing error message when defining JPP 6.0.0.CR01.1 runtime
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2470?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-2470:
-------------------------------------
seems to be fixed in latest JBDS 6.0.1.GA B338
!jppserver-runtime-dialog.png!
> Confusing error message when defining JPP 6.0.0.CR01.1 runtime
> --------------------------------------------------------------
>
> Key: JBDS-2470
> URL: https://issues.jboss.org/browse/JBDS-2470
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: runtime
> Affects Versions: 6.0.0.GA
> Environment: jboss-jpp-6.0.0.CR01.1.zip
> jbdevstudio-product-universal-6.0.0.GA-v20121206-1855-B186.jar
> Reporter: Len DiMaggio
> Assignee: Max Rydahl Andersen
> Fix For: 6.0.1.GA, 7.0.0.Alpha2
>
> Attachments: jppserver-runtime-dialog.png, Screenshot-1.png
>
>
> See attached screenshot - the error displayed to the user when creating a new JPP 6.0.0 runtime is:
> This server type expects a version of 6. but the server directory is of version 7.1.3.Final-redhat-4.
--
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, 1 month
[JBoss JIRA] (JBIDE-13712) TP should not contain old org.mortbay.jetty plugins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13712?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13712:
------------------------------------
[~xcoulon], [~maxandersen] Is this a problem for JBT 4.0 and 4.1?
> TP should not contain old org.mortbay.jetty plugins
> ----------------------------------------------------
>
> Key: JBIDE-13712
> URL: https://issues.jboss.org/browse/JBIDE-13712
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.0.0.Final
> Reporter: Xavier Coulon
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
>
> I'm hitting a problem where a plugin I'm working on cannot be loaded at startup.
> {code}
> ENTRY org.eclipse.osgi 2 0 2013-03-05 09:17:56.748
> !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2013-03-05 09:17:56.748
> !MESSAGE Bundle com.google.gdt.eclipse.platform.e42_3.1.3.v201212122042-rel-r42 [46] was not resolved.
> !SUBENTRY 2 com.google.gdt.eclipse.platform.e42 2 0 2013-03-05 09:17:56.749
> !MESSAGE Package uses conflict: Require-Bundle: org.eclipse.jetty.servlet; bundle-version="0.0.0"
> !SUBENTRY 2 com.google.gdt.eclipse.platform.e42 2 0 2013-03-05 09:17:56.749
> !MESSAGE Package uses conflict: Require-Bundle: org.eclipse.jetty.server; bundle-version="0.0.0"
> !SUBENTRY 1 org.eclipse.osgi 2 0 2013-03-05 09:17:56.749
> !MESSAGE Bundle org.eclipse.equinox.http.servletbridge_1.0.300.v20120912-125810 [477] was not resolved.
> !SUBENTRY 2 org.eclipse.equinox.http.servletbridge 2 0 2013-03-05 09:17:56.750
> !MESSAGE Missing imported package org.eclipse.equinox.servletbridge_1.0.0.
> !SUBENTRY 2 org.eclipse.equinox.http.servletbridge 2 0 2013-03-05 09:17:56.750
> !MESSAGE Missing required capability Require-Capability: osgi.ee; filter="(|(&(osgi.ee=CDC/Foundation)(version=1.0))(&(osgi.ee=JavaSE)(version=1.3)))".
> !SUBENTRY 1 org.eclipse.osgi 2 0 2013-03-05 09:17:56.750
> !MESSAGE Bundle org.eclipse.wst.server.preview_1.1.102.v20130123_1813 [949] was not resolved.
> !SUBENTRY 2 org.eclipse.wst.server.preview 2 0 2013-03-05 09:17:56.751
> !MESSAGE Package uses conflict: Require-Bundle: org.eclipse.jetty.server; bundle-version="[8.0.4,9.0.0)"
> !SUBENTRY 2 org.eclipse.wst.server.preview 2 0 2013-03-05 09:17:56.751
> !MESSAGE Package uses conflict: Require-Bundle: org.eclipse.jetty.servlet; bundle-version="[8.0.4,9.0.0)"
> !SUBENTRY 1 org.eclipse.osgi 2 0 2013-03-05 09:17:56.751
> !MESSAGE Bundle org.jboss.tools.web.pagereloader_1.0.0.qualifier [1101] was not resolved.
> !SUBENTRY 2 org.jboss.tools.web.pagereloader 2 0 2013-03-05 09:17:56.751
> !MESSAGE Package uses conflict: Require-Bundle: org.eclipse.jetty.continuation; bundle-version="8.1.3"
> {code}
> After a bit of investigation, I managed get it started by removing the old org.mortbay.jetty plugins from the TP of the runtime workbench
> Furthermore, Max found this: http://www.eclipse.org/eclipse/development/porting/4.2/incompatibilities....
> BUT
> Attlassian Connector v3.0.7 depends on the org.mortbay.jetty bundles, and they have an open issue to migrate to the recommended org.eclipse.jetty bundles: https://ecosystem.atlassian.net/browse/PLE-1405
--
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, 1 month