March 2013 - jbosstools-issues - Jboss List Archives

[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

1
0
0 / 0

[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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13682) Investigate use of Atlassian 3.0.7 or 3.2 in JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13682?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13682: ------------------------------------ Max also found a version 3.2, but it contains a different set of features: {code:title=http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/} com.atlassian.connector.commons.feature.group com.atlassian.connector.eclipse.bamboo.feature.group com.atlassian.connector.eclipse.commons.feature.group com.atlassian.connector.eclipse.directclickthrough.feature.group com.atlassian.connector.eclipse.feature.group com.atlassian.connector.eclipse.jira.feature.group com.atlassian.connector.eclipse.monitor.feature.group {code} > Investigate use of Atlassian 3.0.7 or 3.2 in JBoss Central > ---------------------------------------------------------- > > Key: JBIDE-13682 > URL: https://issues.jboss.org/browse/JBIDE-13682 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 4.1.0.Alpha2 > > > Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno. > There is also a 3.2 available: > https://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+fo... > available from http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/ -- 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

1
0
0 / 0

[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

1
0
0 / 0

[JBoss JIRA] (JBDS-2490) migrate JBT and JBDS discovery plugins to new github repo, jbosstools-discovery

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2490: -------------------------------- Summary: migrate JBT and JBDS discovery plugins to new github repo, jbosstools-discovery Key: JBDS-2490 URL: https://issues.jboss.org/browse/JBDS-2490 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: central Affects Versions: 6.0.1.GA, 7.0.0.Alpha1 Reporter: Nick Boldt Assignee: Max Rydahl Andersen Fix For: 6.0.1.GA, 7.0.0.Alpha2 Migrate 3 branches of git sources (including history): https://github.com/jbosstools/jbosstools-central/tree/master/central/plug... https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.1.0.Al... https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.0.x/ce... and 3 branches of svn sources (including history): http://svn.jboss.org/repos/devstudio/trunk/product/plugins/com.jboss.jbds... http://svn.jboss.org/repos/devstudio/branches/devstudio-7.0.0.Alpha1/prod... http://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product/plu... to a new Github project called "jbosstools-discovery" under which there would be: * plugins/ ** com.jboss.jbds.central.discovery/ ** org.jboss.tools.central.discovery/ -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13670) Can't install some Atlassian connector from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13670?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-13670. ------------------------------ Labels: respin-c (was: ) Resolution: Partially Completed For Alpha1/Alpha2, *Atlassian Connector for Eclipse* and *Mylyn Issue Tracker Connectors* have been removed (JBIDE-13724). For Alpha2 and onward, we can investigate if we want to include 3.0.7, 3.2.0, or something else. See linked issues for followup work. > Can't install some Atlassian connector from Central > --------------------------------------------------- > > Key: JBIDE-13670 > URL: https://issues.jboss.org/browse/JBIDE-13670 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Mickael Istria > Assignee: Nick Boldt > Labels: respin-c > Fix For: 4.1.0.Alpha2 > > > Can't install Atlassian from Central > * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > * Contains: Missing requirement: Atlassian Connector for Eclipse Usage Monitoring 3.0.6.v20120628 (com.atlassian.connector.eclipse.monitor.feature.group 3.0.6.v20120628) requires 'org.eclipse.update.ui 0.0.0' but it could not be found > 2 solutions possible, by order of preference: > # Use a more recent version of Atlassian connectors compliant with Kepler > # Remove Atlassian stuff from Central until we have a good version -- 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

1
0
0 / 0

[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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13724) remove Atlassian + RH BZ/JB JIRA connectors from JBT & JBDS Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13724?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13724: ------------------------------------ Spinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=15 > remove Atlassian + RH BZ/JB JIRA connectors from JBT & JBDS Central > ------------------------------------------------------------------- > > Key: JBIDE-13724 > URL: https://issues.jboss.org/browse/JBIDE-13724 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: respin-c > Fix For: 4.1.0.Alpha1 > > > Because Atlassian 3.0.6/3.0.7 are bad, and 3.2 is untested, we need to (temporarily?) remove anything that depends on it from Central for now. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13724) remove Atlassian + RH BZ/JB JIRA connectors from JBT & JBDS Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13724?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13724: ------------------------------------ @maxandersen applied PR 73 in both 410Alpha1x and master branches. > remove Atlassian + RH BZ/JB JIRA connectors from JBT & JBDS Central > ------------------------------------------------------------------- > > Key: JBIDE-13724 > URL: https://issues.jboss.org/browse/JBIDE-13724 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: respin-c > Fix For: 4.1.0.Alpha1 > > > Because Atlassian 3.0.6/3.0.7 are bad, and 3.2 is untested, we need to (temporarily?) remove anything that depends on it from Central for now. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13724) remove Atlassian + RH BZ/JB JIRA connectors from JBT & JBDS Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13724?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13724: ------------------------------------ Commented out Mylyn Issue Tracker Connectors and Atlassian Connector for Eclipse in jbds svn (trunk and 410Alpha1 branch). > remove Atlassian + RH BZ/JB JIRA connectors from JBT & JBDS Central > ------------------------------------------------------------------- > > Key: JBIDE-13724 > URL: https://issues.jboss.org/browse/JBIDE-13724 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: respin-c > Fix For: 4.1.0.Alpha1 > > > Because Atlassian 3.0.6/3.0.7 are bad, and 3.2 is untested, we need to (temporarily?) remove anything that depends on it from Central for now. -- 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2013